- openstack-discuss - lists.openstack.org

[horizon] patternfly?
by Mohammed Naser 05 Aug '20

05 Aug '20

Hi everyone, I was wondering if anyone in the community has explored the idea of implementing PatternFly inside Horizon. It seems like it shares a lot of the similar ideas that we use and we could really benefit from using a common library that already exists with a lot of good UX thought behind it. I know it's based on React which is a bit of a leap from where Horizon is today. However, I'd be curious if the Horizon team is interested in figuring out a plan to make a migration to something like this happen. Personally, I think I would be able to provide resources to have someone do this work. However, if this seems like a huge stretch and architecture change where it actually makes more sense to stand this up from scratch (and implement an architecture where the dashboard talks directly to the APIs?), perhaps we should explore that. I also would like to hear more from our extended community too, as I think we really need to improve our user interface experience. Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

11 31

[TC] [PTG] Victoria vPTG Summary of Conversations and Action Items
by Kendall Nelson 05 Aug '20

05 Aug '20

Hello Everyone! I hope you all had a productive and enjoyable PTG! While it’s still reasonably fresh, I wanted to take a moment to summarize discussions and actions that came out of TC discussions. If there is a particular action item you are interested in taking, please reply on this thread! For the long version, check out the etherpad from the PTG[1]. Tuesday ====== Ussuri Retrospective ---------------------------- As usual we accomplished a lot. Some of the things we accomplished were around enumerating operating systems per release (again), removing python2 support, and adding the ideas repository. Towards the end of the release, we had a lot of discussions around what to do with leaderless projects, the role of PTLs, and what to do with projects that were missing PTL candidates for the next release. We discussed office hours, their history and reason for existence, and clarified how we can strengthen communication amongst ourselves, the projects, and the larger community. TC Onboarding -------------------- It was brought up that those elected most recently (and even new members the election before) felt like there wasn’t enough onboarding into the TC. Through discussion about what we can do to better support returning members is to better document the daily, weekly and monthly tasks TC members are supposed to be doing. Kendall Nelson proposed a patch to start adding more detail to a guide for TC members already[2]. It was also proposed that we have a sort of mentorship or shadow program for people interested in joining the TC or new TC members by more experienced TC members. The discussion about the shadow/mentorship program is to be continued. TC/UC Merge ------------------ Thierry gave an update on the merge of the committees. The simplified version is that the current proposal is that UC members are picked from TC members, the UC operates within the TC, and that we are already setup for this given the number of TC members that have AUC status. None of this requires a by-laws change. One next step that has already begun is the merging of the openstack-users ML into openstack-discuss ML. Other next steps are to decide when to do the actual transition (disbanding the separate UC, probably at the next election?) and when to setup AUC’s to be defined as extra-ATC’s to be included in the electorate for elections. For more detail, check out the openstack-discuss ML thread[3]. Wednesday ========= Help Wanted List ----------------------- We settled on a format for the job postings and have several on the list. We talked about how often we want to look through, update or add to it. The proposal is to do this yearly. We need to continue pushing on the board to dedicate contributors at their companies to work on these items, and get them to understand that it's an investment that will take longer than a year in a lot of cases; interns are great, but not enough. TC Position on Foundation Member Community Contributions ---------------------------------------------------------------------------------- The discussion started with a state of things today - the expectations of platinum members, the benefits the members get being on the board and why they should donate contributor resources for these benefits, etc. A variety of proposals were made: either enforce or remove the minimum contribution level, give gold members the chance to have increased visibility (perhaps giving them some of the platinum member advantages) if they supplement their monetary contributions with contributor contributions, etc. The #ACTION that was decided was for Mohammed to take these ideas to the board and see what they think. OpenStack User-facing APIs -------------------------------------- Users are confused about the state of the user facing API’s; they’ve been told to use the OpenStackClient(OSC) but upon use, they discover that there are features missing that exist in the python-*clients. Partial implementation in the OSC is worse than if the service only used their specific CLI. Members of the OpenStackSDK joined discussions and explained that many of the barriers that projects used to have behind implementing certain commands have been resolved. The proposal is to create a pop up team and that they start with fully migrating Nova, documenting the process and collecting any other unresolved blocking issues with the hope that one day we can set the migration of the remaining projects as a community goal. Supplementally, a new idea was proposed- enforcing new functionality to services is only added to the SDK (and optionally the OSC) and not the project’s specific CLI to stop increasing the disparity between the two. The #ACTION here is to start the pop up team, if you are interested, please reply! Additionally, if you disagree with this kind of enforcement, please contact the TC as soon as possible and explain your concerns. PTL Role in OpenStack today & Leaderless Projects --------------------------------------------------------------------- This was a veeeeeeeerrrry long conversation that went in circles a few times. The very short version is that we, the TC, are willing to let project teams decide for themselves if they want to have a more deconstructed kind of PTL role by breaking it into someone responsible for releases and someone responsible for security issues. This new format also comes with setting the expectation that for things like project updates and signing up for PTG time, if someone on the team doesn’t actively take that on, the default assumption is that the project won’t participate. The #ACTION we need someone to take on is to write a resolution about how this will work and how it can be done. Ideally, this would be done before the next technical election, so that teams can choose it at that point. If you are interested in taking on the writing of this resolution, please speak up! Cross Project Work ------------------------- -Pop Up Teams- The two teams we have right now are Encryption and Secure Consistent Policy Groups. Both are making slow progress and will continue. -Reducing Community Goals Per Cycle- Historically we have had two goals per cycle, but for smaller teams this can be a HUGE lift. The #ACTION is to clearly outline the documentation for the goal proposal and selection process to clarify that selecting only one goal is fine. No one has claimed this action item yet. -Victoria Goal Finalization- Currently, we have three proposals and one accepted goal. If we are going to select a second goal, it needs to be done ASAP as Victoria development has already begun. All TC members should review the last proposal requesting selection[4]. -Wallaby Cycle Goal Discussion Kick Off- Firstly, there is a #ACTION that one or two TC members are needed to guide the W goal selection. If you are interested, please reply to this thread! There were a few proposed goals for VIctoria that didn’t make it that could be the starting point for W discussions, in particular, the rootwrap goal which would be good for operators. The OpenStackCLI might be another goal to propose for Wallaby. Detecting Unmaintained Projects Early --------------------------------------------------- The TC liaisons program had been created a few releases ago, but the initial load on TC members was large. We discussed bringing this program back and making the project health checks happen twice a release, either the start or end of the release and once in the middle. TC liaisons will look at previously proposed releases, release activity of the team, the state of tempest plugins, if regular meetings are happening, if there are patches in progress and how busy the project’s IRC channel is to make a determination. Since more than one liaison will be assigned to each project, those liaisons can divvy up the work how they see fit. The other aspect that still needs to be decided is where the health checks will be recorded- in a wiki? In a meeting and meeting logs? That decision is still to be continued. The current #ACTION currently unassigned is that we need to assign liaisons for the Victoria cycle and decide when to do the first health check. Friday ===== Reducing Systems and Friction to Drive Change ---------------------------------------------------------------- This was another conversation that went in circles a bit before realizing that we should make a list of the more specific problems we want to address and then brainstorm solutions for them. The list we created (including things already being worked) are as follows: - TC separate from UC (solution in progress) - Stable releases being approved by a separate team (solution in progress) - Making repository creation faster (especially for established project teams) - Create a process blueprint for project team mergers - Requirements Team being one person - Stable Team - Consolidate the agent experience - Figure out how to improve project <--> openstack client/sdk interaction. If you feel compelled to pick one of these things up and start proposing solutions or add to the list, please do! Monitoring in OpenStack (Ceilometer + Telemetry + Gnocchi State) ----------------------------------------------------------------------------------------- This conversation is also ongoing, but essentially we talked about the state of things right now- largely they are not well maintained and there is added complexity with Ceilometers being partially dependent on Gnocchi. There are a couple of ideas to look into like using oslo.metrics for the interface between all the tools or using Ceilometer without Gnocchi if we can clean up those dependencies. No specific action items here, just please share your thoughts if you have them. Ideas Repo Next Steps ------------------------------- Out of the Ussuri retrospective, it was brought up that we probably needed to talk a little more about what we wanted for this repo. Essentially we just want it to be a place to collect ideas into without worrying about the how. It should be a place to document ideas we have had (old and new) and keep all the discussion in one place as opposed to historic email threads, meetings logs, other IRC logs, etc. We decided it would be good to periodically go through this repo, likely as a forum session at a summit to see if there is any updating that could happen or promotion of ideas to community goals, etc. ‘tc:approved-release’ Tag --------------------------------- This topic was proposed by the Manila team from a discussion they had earlier in the week. We talked about the history of the tag and how usage of tags has evolved. At this point, the proposal is to remove the tag as anything in the releases repo is essentially tc-approved. Ghanshyam has volunteered to document this and do the removal. The board also needs to be notified of this and to look at projects.yaml in the governance repo as the source of truth for TC approved projects. The unassigned #ACTION item is to review remaining tags and see if there are others that need to be modified/removed/added to drive common behavior across OpenSack components. Board Proposals ---------------------- This was a pretty quick summary of all discussions we had that had any impact on the board and largely decided who would mention them. Session Feedback ------------------------ This was also a pretty quick topic compared to many of the others, we talked about how things went across all our discussions (largely we called the PTG a success) logistically. We tried to make good use of the raising hands feature which mostly worked, but it lacks context and its possible that the conversation has moved on by the time it’s your turn (if you even remember what you want to say). OpenStack 2.0: k8s Native ----------------------------------- This topic was brought up at the end of our time so we didn’t have time to discuss it really. Basically Mohammed wanted to start the conversation about adding k8s as a base service[5] and what we would do if a project proposed required k8s. Adding services that work with k8s could open a door to new innovation in OpenStack. Obviously this topic will need to be discussed further as we barely got started before we had to wrap things up. So. The tldr; Here are the #ACTION items we need owners for: - Start the User Facing API Pop Up Team - Write a resolution about how the deconstructed PTL roles will work - Update Goal Selection docs to explain that one or more goals is fine; it doesn’t have to be more than one - Two volunteers to start the W goal selection process - Assign two TC liaisons per project - Review Tags to make sure they are still good for driving common behavior across all openstack projects Here are the things EVERYONE needs to do: - Review last goal proposal so that we can decide to accept or reject it for the V release[4] - Add systems that are barriers to progress in openstack to the Reducing Systems and Friction list - Continue conversations you find important Thanks everyone for your hard work and great conversations :) Enjoy the attached (photoshopped) team photo :) -Kendall (diablo_rojo) [1] TC PTG Etherpad: https://etherpad.opendev.org/p/tc-victoria-ptg [2] TC Guide Patch: https://review.opendev.org/#/c/732983/ [3] UC TC Merge Thread: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014736.html [4] Proposed V Goal: https://review.opendev.org/#/c/731213/ [5] Base Service Description: https://governance.openstack.org/tc/reference/base-services.html

3 2

Re: [nova] If any spec freeze exception now?
by yumeng bao 05 Aug '20

05 Aug '20

Hi gibi and all, I wanna mention the SRIOV SmartNIC Support Spec https://review.opendev.org/#/c/742785 This spec is proposed based on feedback from our PTG discussion, yet there are still open questions need to be nailed down. Since this spec involves nova neutron and cyborg, it will probably take a long time to get ideas from different aspects and reach an agreement. Can we keep this as an exception and keep review it to reach closer to an agreement? Hopefully we can reach an agreement in Victoria, and start to land in W. Xinran and I were trying to attend nova’s weekly meeting to discuss this spec, but the time too late for us. :( We will find if there is any other way to sync and response more actively to all your comments and feedback. And just to point out, nova operations support are still one of cyborg’s high priority goals in Victoria, we will keep focus on it and won’t sacrifice time of this goal. Regards， Yumeng

3 3

[swift][ceph] Container ACLs don't seem to be respected on Ceph RGW
by Jason Anderson 05 Aug '20

05 Aug '20

Hi all, Just scratching my head at this for a while and though I’d ask here in case it saves some time. I’m running a Ceph cluster on the Nautilus release and it’s running Swift via the rgw. I have Keystone authentication turned on. Everything works fine in the normal case of creating containers, uploading files, listing containers, etc. However, I notice that ACLs don’t seem to work. I am not overriding "rgw enforce swift acls”, so it is set to the default of true. I can’t seem to share a container or make it public. (Side note, confusingly, the Ceph implementation has a different syntax for public read/write containers, ‘*’ as opposed to ‘*:*’ for public write for example.) Here’s what I’m doing (as admin) swift post —write-acl ‘*’ —read-acl ‘*’ public-container swift stat public-container Account: v1 Container: public-container Objects: 1 Bytes: 5801 Read ACL: * Write ACL: * Sync To: Sync Key: X-Timestamp: 1595883106.23179 X-Container-Bytes-Used-Actual: 8192 X-Storage-Policy: default-placement X-Storage-Class: STANDARD Last-Modified: Wed, 05 Aug 2020 03:42:11 GMT X-Trans-Id: tx000000000000000662156-005f2a2bea-23478-default X-Openstack-Request-Id: tx000000000000000662156-005f2a2bea-23478-default Accept-Ranges: bytes Content-Type: text/plain; charset=utf-8 (as non-admin) swift upload public-container test.txt Warning: failed to create container 'public-container': 409 Conflict: BucketAlreadyExists Object HEAD failed: https://ceph.example.org:7480/swift/v1/public-container/README.md 403 Forbidden swift list public-container Container GET failed: https://ceph.example.org:7480/swift/v1/public-container?format=json 403 Forbidden [first 60 chars of response] b'{"Code":"AccessDenied","BucketName”:”public-container","RequestId":"tx0' Failed Transaction ID: tx000000000000000662162-005f2a2c2a-23478-default What am I missing? Thanks in advance! /Jason

1 2

[tc][ptl] Proposal: Distributed Project Leadership
by Nate Johnston 05 Aug '20

05 Aug '20

The governing structure for OpenStack projects has long been for a Project Technical Lead (PTL) to be elected to serve as a singular focus for that project. While the PTL role varies significantly from project to project, the PTL has many responsibilities for managing the development and release process for a project as well as representing the project both internally and externally. There have been a number of projects that have expressed an interest in functioning in a mode that would not require a PTL, but would rather devolve the responsibilities of the PTL into various liaison roles, that could in turn be held by one or more contributors. This topic was discussed by the TC at the recent virtual PTG, and we now have a proposal to put forth to the community for comment. Jean-Phillipe Evrard and I worked up a more detailed proposal for everyone to comment on and review. We are calling this the 'distributed project leadership model'. Most importantly, this is an opt-in process where projects interested in pursuing a distributed project leadership model should opt in to it, but for projects satisfied with the status quo nothing would change. I encourage everyone who is interested to examine the proposal and comment: https://review.opendev.org/744995 Thank you, Nate Johnston

1 0

[neutron] Drivers team meetings 7.08.2020 and 14.08.2020
by Slawek Kaplonski 05 Aug '20

05 Aug '20

Hi, I have internal training this Friday and I will be on PTO next Friday. Because of that I will not be able to chair neutron drivers meetings those 2 weeks. Currently we don’t have any new RFES to discuss so lets cancel those meetings and focus on implementation of RFEs already accepted. See You on drivers meeting on Friday, 21.08.2020 — Slawek Kaplonski Principal software engineer Red Hat

1 0

[tc] monthly meeting
by Mohammed Naser 05 Aug '20

05 Aug '20

Hi everyone, Here’s the agenda for our monthly TC meeting. It will happen tomorrow (Thursday the 6th) at 1400 UTC in #openstack-tc and I will be your chair. If you can’t attend, please put your name in the “Apologies for Absence” section. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * ACTIVE INITIATIVES - Follow up on past action items - OpenStack User-facing APIs and CLIs (belmoreira) - W cycle goal selection start - Completion of retirement cleanup (gmann) https://etherpad.opendev.org/p/tc-retirement-cleanup Thank you, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[nova] Change Volume Type Properties
by Marc Vorwerk 05 Aug '20

05 Aug '20

Hi, I'm looking for a way to add the property volume_backend_name to an existing Volume Type which is in use. If I try to change this, I got the following error: root@control01rt:~# openstack volume type show test-type +--------------------+--------------------------------------+ | Field | Value | +--------------------+--------------------------------------+ | access_project_ids | None | | description | None | | id | 68febdad-e7b1-4d41-ba11-72d0e1a1cce0 | | is_public | True | | name | test-type | | properties | | | qos_specs_id | None | +--------------------+--------------------------------------+ root@control01rt:~# openstack volume type set --property volume_backend_name=ceph test-type Failed to set volume type property: Volume Type is currently in use. (HTTP 400) (Request-ID: req-2b8f3829-5c16-42c3-ac57-01199688bd58) Command Failed: One or more of the operations failed root@control01rt:~# Problem what I see is, that there are instances/volumes which use this volume type. Have anybody an idea, how I can add the volume_backend_name property to the existing Volume Type? thanks in advance! Regards Marc

2 1

[kolla] Proposing Michał Nasiadka for kayobe-core
by Mark Goddard 05 Aug '20

05 Aug '20

Hi, I'd like to propose adding Michał Nasiadka to the kayobe-core group. Michał is a valued member of the Kolla core team, and has been providing some good patches and reviews for Kayobe too. Kayobians, please respond with +1/-1. Cheers, Mark

4 4

[placement][gate] functional tests failing
by melanie witt 04 Aug '20

04 Aug '20

Hi all, I recently proposed a change to openstack/placement and found that the functional tests are currently failing. It's because of a recent-ish bump to upper-constraints to allow os-traits 2.4.0: https://review.opendev.org/739330 and placement has a func test that asserts the number of standard traits (more traits are available in 2.4.0). I've proposed a fix for the func test here if anyone could please help review: https://review.opendev.org/744790 Cheers, -melanie

1 1

[nova] Hyper-V hosts
by Eric K. Miller 04 Aug '20

04 Aug '20

Hi, I thought I'd look into support of Hyper-V hosts for Windows Server environments, but it looks like the latest cloudbase Windows Hyper-V OpenStack Installer is for Train, and nothing seems to discuss the use of Hyper-V in Windows Server 2019. Has it been abandoned? Is anyone using Hyper-V with OpenStack successfully? One of the reasons we thought we might support it is to provide nested support for VMs with GPUs and/or vGPUs, and thought this would work better than with KVM, specifically with AMD EPYC systems. It seems that when "options kvm-amd nested=1" is used in a modprobe.d config file, Windows machines lock up when started. I think this has been an issue for a while with AMD processors, but thought it was fixed recently (I don't remember where I saw this, though). Would love to hear about any experiences related to Hyper-V and/or nested hypervisor support on AMD EPYC processors. Thanks! Eric

2 2

[nova] openstack-tox-lower-constraints broken
by Lee Yarwood 04 Aug '20

04 Aug '20

Hello all, $subject, I've raised the following bug: openstack-tox-lower-constraints failing due to unmet dependency on decorator==4.0.0 https://launchpad.net/bugs/1890123 I'm trying to resolve this below but I honestly feel like I'm going around in circles: https://review.opendev.org/#/q/topic:bug/1890123 If anyone has any tooling and/or recommendations for resolving issues like this I'd appreciate it! Cheers, -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76

6 9

[openstack][tempest] Deprecation of scenario.img_dir option
by Martin Kopec 04 Aug '20

04 Aug '20

Hello all, we deprecated *scenario.img_dir* option in Tempest by this patch [1]. *scenario.img_file* should contain the full path of an image from now on. However, to make the transition easier for all the Tempest dependent projects, Tempest currently accepts both behaviors - the old where the path to an image consisted of *scenario.img_dir* + *scenario.img_file* and the new one where *scenario.img_file* contains the full path to an image. It will be accepting both ways for one whole release - 25. I proposed patches to projects I found they use scenario.img_dir option, see this link [2]. If you maintain a project from the list [2], please review. If your project somehow uses scenario.img_dir or img_file option and is not in the list [2], please make appropriate changes. [1] https://review.opendev.org/#/c/710996 [2] https://review.opendev.org/#/q/topic:remove_img_dir+(status:open+OR+status:… Regards, -- Martin Kopec Quality Engineer Red Hat EMEA <https://www.redhat.com> <https://red.ht/sig>

1 0

[tc] weekly update
by Mohammed Naser 04 Aug '20

04 Aug '20

Hi everyone, Here’s an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Declare supported runtimes for Wallaby release https://review.opendev.org/743847 - [draft] Add assert:supports-standalone https://review.opendev.org/722399 - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/736369 - migrate testing to ubuntu focal https://review.opendev.org/740851 ## Project Updates - Add Keystone Kerberos charm to OpenStack charms https://review.opendev.org/743769 - Deprecate os_congress project https://review.opendev.org/742533 - Add Ceph iSCSI charm to OpenStack charms https://review.opendev.org/744480 ## General Changes - Cleanup the remaining osf repos and their data https://review.opendev.org/739291 - [manila] assert:supports-accessible-upgrade https://review.opendev.org/740509 - V goals, Zuul v3 migration: update links and grenade https://review.opendev.org/741987 ## Abandoned Changes - DNM: testing gate on ubuntu focal https://review.opendev.org/743249 # Email Threads - Legacy Zuul Jobs Update 1: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016058.html - Community PyCharm Licenses: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016039.html - Release Countdown R-10: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016243.h… - CloudKitty Status: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016171.html - Migrate CI Jobs to Ubuntu Focal Update: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016222.h… - TC Monthly Meeting Reminder: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016196.html # Other Reminders - Aug 4: CFP for Open Infra Summit Closes Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[neutron] bug deputy report (Jul 27 - Aug 2)
by Akihiro Motoki 04 Aug '20

04 Aug '20

Hi, Sorry for late just before the meeting. This is my bug deputy report last week. General questions ================= * l3-dvr-backlog tag was originally introduced to identify DVR feature gaps. What should we use for OVN L3 feature gaps? * We have no volunteer for FWaaS now. How should we triage fwaas bugs? Needs attentions ================ Both affects neutron behaviors and they are not simple bugs. More opinions would be appreciated. https://bugs.launchpad.net/neutron/+bug/1889631 [OVS][FW] Multicast non-IGMP traffic is allowed by default, not in iptables FW New, Undecided It might be worth RFE. It affects existing deployments. We need more detail discussion on this. https://bugs.launchpad.net/neutron/+bug/1889454 br-int has an unpredictable MTU New, Undecided This is an interesting topic. More opinions would be appreciated. Confirmed ========= [FT][Fullstack] Timeout during OVS bridge creation transaction https://bugs.launchpad.net/neutron/+bug/1889453 Critical, Confirmed In Progress =========== Functional tests neutron.tests.functional.agent.linux.test_linuxbridge_arp_protect failing on Ubuntu 20.04 https://bugs.launchpad.net/neutron/+bug/1889779 High, In Progress CI failture: ImportError: cannot import decorate https://bugs.launchpad.net/neutron/+bug/1890064 High, In Progress, The fix is https://review.opendev.org/#/c/744465/ but blocked by other gate failures Validate subnet when plugging to the router don't works when plugging port https://bugs.launchpad.net/neutron/+bug/1889619 Low, In Progress Won't Fix ========= Functional tests on Ubuntu 20.04 are timed out https://bugs.launchpad.net/neutron/+bug/1889781 High, Won't Fix, it doesn't look like an issue after fixing other issues per slawek ONV feature gaps or cleanups ============================ https://bugs.launchpad.net/neutron/+bug/1889737 [OVN] Stop using neutron.api.rpc.handlers.resources_rpc with OVN as a backend Medium, Confirmed, a kind of cleanup around OVN https://bugs.launchpad.net/neutron/+bug/1889738 [OVN] Stop doing PgDelPortCommand on each router port update Low, Confirmed [OVN] access between Floatings ip and instance with Direct External IP https://bugs.launchpad.net/neutron/+bug/1889388 New, Undecided, OVN feature gap Q: l3-dvr-backlog tag was originally introduced to identify DVR feature gaps. What should we use for OVN L3 feature gaps? FWaaS ====== neutron_tempest_plugin.fwaas.api.test_fwaasv2_extensions failed https://bugs.launchpad.net/neutron/+bug/1889730 New, Undecided, we have no volunteer for FWaaS now. How should we triage fwaas bugs?

1 0

[cinder] victoria virtual mid-cycle next week
by Brian Rosmaita 04 Aug '20

04 Aug '20

The date/time selection poll has closed, and I am happy to announce the unanimous choice. Session Two of the Cinder Victoria virtual mid-cycle will be held: DATE: 12 August 2020 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the etherpad: https://etherpad.opendev.org/p/cinder-victoria-mid-cycles cheers, brian

1 0

Re: [ops] [cinder[ "Services and volumes must have a service UUID."
by Sean McGinnis 04 Aug '20

04 Aug '20

[adding back the ML] On 8/4/20 7:48 AM, Massimo Sgaravatto wrote: > I am afraid I never ran the online data migration > > This cluster ran Ocata > Then we updated to Rocky. We went though Pike and Queens but just to > run the db-syncs > Then we updated from Rocky to train (again, we went though Stein but > just to run the db-syncs) > > Am I in troubles now ? > > Thanks, Massimo I know some folks were handling parts of this by running each version in a container. That may be an option to quickly go through the DB migrations. Let's see if anyone responds with any tips to make this easy.

2 1

[ops] [cinder[ "Services and volumes must have a service UUID."
by Massimo Sgaravatto 04 Aug '20

04 Aug '20

We have just updated a small OpenStack cluster to Train. Everything seems working, but "cinder-status upgrade check" complains that services and volumes must have a service UUID [*]. What does this exactly mean? Thanks, Massimo [*] +--------------------------------------------------------------------+ | Check: Service UUIDs | | Result: Failure | | Details: Services and volumes must have a service UUID. Please fix | | this issue by running Queens online data migrations. |

3 6

[openstack][stein][manila-ui] error
by Ignazio Cassano 04 Aug '20

04 Aug '20

Hello, I installed manila on openstack stein and it works by command line mat the manila ui does not work and in httpd error log I read: [Mon Aug 03 07:45:26.697408 2020] [:error] [pid 3506291] ERROR django.request Internal Server Error: /dashboard/project/shares/ [Mon Aug 03 07:45:26.697437 2020] [:error] [pid 3506291] Traceback (most recent call last): [Mon Aug 03 07:45:26.697442 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/django/core/handlers/exception.py", line 41, in inner [Mon Aug 03 07:45:26.697446 2020] [:error] [pid 3506291] response = get_response(request) [Mon Aug 03 07:45:26.697450 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 187, in _get_response [Mon Aug 03 07:45:26.697453 2020] [:error] [pid 3506291] response = self.process_exception_by_middleware(e, request) [Mon Aug 03 07:45:26.697466 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 185, in _get_response [Mon Aug 03 07:45:26.697471 2020] [:error] [pid 3506291] response = wrapped_callback(request, *callback_args, **callback_kwargs) [Mon Aug 03 07:45:26.697475 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 52, in dec [Mon Aug 03 07:45:26.697479 2020] [:error] [pid 3506291] return view_func(request, *args, **kwargs) [Mon Aug 03 07:45:26.697482 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec [Mon Aug 03 07:45:26.697485 2020] [:error] [pid 3506291] return view_func(request, *args, **kwargs) [Mon Aug 03 07:45:26.697489 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec [Mon Aug 03 07:45:26.697492 2020] [:error] [pid 3506291] return view_func(request, *args, **kwargs) [Mon Aug 03 07:45:26.697496 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 113, in dec [Mon Aug 03 07:45:26.697499 2020] [:error] [pid 3506291] return view_func(request, *args, **kwargs) [Mon Aug 03 07:45:26.697502 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in dec [Mon Aug 03 07:45:26.697506 2020] [:error] [pid 3506291] return view_func(request, *args, **kwargs) [Mon Aug 03 07:45:26.697509 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 68, in view [Mon Aug 03 07:45:26.697513 2020] [:error] [pid 3506291] return self.dispatch(request, *args, **kwargs) [Mon Aug 03 07:45:26.697516 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 88, in dispatch [Mon Aug 03 07:45:26.697520 2020] [:error] [pid 3506291] return handler(request, *args, **kwargs) [Mon Aug 03 07:45:26.697523 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 223, in get [Mon Aug 03 07:45:26.697526 2020] [:error] [pid 3506291] handled = self.construct_tables() [Mon Aug 03 07:45:26.697530 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 214, in construct_tables [Mon Aug 03 07:45:26.697533 2020] [:error] [pid 3506291] handled = self.handle_table(table) [Mon Aug 03 07:45:26.697537 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 123, in handle_table [Mon Aug 03 07:45:26.697540 2020] [:error] [pid 3506291] data = self._get_data_dict() [Mon Aug 03 07:45:26.697544 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 43, in _get_data_dict [Mon Aug 03 07:45:26.697547 2020] [:error] [pid 3506291] data.extend(func()) [Mon Aug 03 07:45:26.697550 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 109, in wrapped [Mon Aug 03 07:45:26.697554 2020] [:error] [pid 3506291] value = cache[key] = func(*args, **kwargs) [Mon Aug 03 07:45:26.697557 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/manila_ui/dashboards/project/shares/views.py", line 57, in get_shares_data [Mon Aug 03 07:45:26.697561 2020] [:error] [pid 3506291] share_nets = manila.share_network_list(self.request) [Mon Aug 03 07:45:26.697564 2020] [:error] [pid 3506291] File "/usr/lib/python2.7/site-packages/manila_ui/api/manila.py", line 280, in share_network_list [Mon Aug 03 07:45:26.697568 2020] [:error] [pid 3506291] return manilaclient(request).share_networks.list(detailed=detailed, [Mon Aug 03 07:45:26.697571 2020] [:error] [pid 3506291] AttributeError: 'NoneType' object has no attribute 'share_networks' Please, anyone could help ? Ignazio

3 10

[ironic][stable] Include ironic-core in ironic-stable-maint ?
by Julia Kreger 04 Aug '20

04 Aug '20

Greetings awesome humans, I have a conundrum, and largely it is over stable branch maintenance. In essence, our stable branch approvers are largely down to Dmitry, Riccardo, and Myself. I think this needs to change and I'd like to propose that we go ahead and change ironic-stable-maint to just include ironic-core in order to prevent the bottleneck and conflict and risk which this presents. I strongly believe that our existing cores would all do the right thing if presented with the question of if a change needed to be merged. So honestly I'm not concerned by this proposal. Plus, some of our sub-projects have operated this way for quite some time. Thoughts, concerns, worries? -Julia

3 2

[Glance] Proposing Dan Smith for glance core
by Abhishek Kekane 03 Aug '20

03 Aug '20

Hi All, I'd like to propose adding Dan Smith to the glance core group. Dan Smith has contributed to stabilize image import workflow as well as multiple stores of glance. He is also contributing in tempest and nova to set up CI/tempest jobs around image import and multiple stores. Being involved on the mailing-list and IRC channels, Dan is always helpful to the community and here to help. Please respond with +1/-1 until 03rd August, 2020 1400 UTC. Cheers, Abhishek

5 5

[openstack-helm] IRC Meeting Canceled 08/04
by Gage Hugo 03 Aug '20

03 Aug '20

Hello everyone, Since I will be unavailable tomorrow and there's currently no agenda, I am going to cancel the meeting for tomorrow. We will meet again next week at the regular time. Thanks.

1 0

CFP Deadline Tomorrow - Virtual Open Infrastructure Summit
by Ashlee Ferguson 03 Aug '20

03 Aug '20

Hi everyone, It’s time to submit your Open Infrastructure virtual Summit presentations[1]! The CFP deadline is tomorrow. Submit sessions featuring open source projects including Airship, Ansible, Ceph, Kata Containers, Kubernetes, ONAP, OpenStack, OPNFV, StarlingX and Zuul. As a reminder, these are the 2020 Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops Open Development Private & Hybrid Cloud Public Cloud Security Get your presentations, panels, and workshops in before August 4 at 11:59 pm PT (August 5 at 6:59 am UTC). The content submission process for the Forum and Project Teams Gathering (PTG) will be managed separately in the upcoming months. The Summit Programming Committee has shared topics by Track for community members interested in speaking at the upcoming Summit. Check out the submission tips[2]! Then don’t forget to register[3] for the virtual Open Infrastructure Summit taking place October 19-23, 2020 at no cost to you. Need more time? Reach out to speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> with any questions or concerns. Cheers, Ashlee [1] https://cfp.openstack.org/ <https://cfp.openstack.org/app/presentations> [2] https://superuser.openstack.org/articles/virtual-open-infrastructure-summit… <https://superuser.openstack.org/articles/virtual-open-infrastructure-summit…> [3] https://openinfrasummit2020.eventbrite.com <https://openinfrasummit2020.eventbrite.com/> Ashlee Ferguson Community & Events Coordinator OpenStack Foundation

1 0

[release] Release countdown for week R-10 August 3 - 7
by Sean McGinnis 03 Aug '20

03 Aug '20

Development Focus ----------------- We are now past the Victoria-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (September 3). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (September 10) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, September 10. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 24) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (October 8) Upcoming Deadlines & Dates -------------------------- Ussuri Cycle-trailing deadline: August 13 (R-9 week) Non-client library freeze: September 3 (R-6 week) Client library freeze: September 10 (R-5 week) Ussuri-3 milestone: September 10 (R-5 week) Victoria release: October 14

1 0

[ironic] let's talk about grenade
by Iury Gregory 03 Aug '20

03 Aug '20

Hello everyone, I'm still on the fight to move our ironic-grenade-dsvm-multinode-multitenant to zuulv3 [1], you can find some of my findings on the etherpad [2] under `Move to Zuul v3 Jobs (Iurygregory)`. If you are interested in helping out we are going to schedule a meeting to discuss about this, please use the doodle in [3]. I will close the doodle on Wed July 29. Thanks! [1] https://review.opendev.org/705030 [2] https://etherpad.openstack.org/p/IronicWhiteBoard [3] https://doodle.com/poll/m69b5zwnsbgcysct -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 2

Re: [openstack-community] Octavia :; Unable to create load balancer
by Monika Samal 03 Aug '20

03 Aug '20

Hey Fabian, Can you please elaborate more about keystone settings, where in need to make changes etc.. I am new to openstack finding it difficult to resolve kind of atuck ________________________________ From: Fabian Zimmermann <dev.faz(a)gmail.com> Sent: Friday, July 31, 2020 1:22 AM To: Monika Samal <monika.samal(a)outlook.com> Cc: Michael Johnson <johnsomor(a)gmail.com>; Amy Marrich <amy(a)demarco.com>; openstack-discuss <openstack-discuss(a)lists.openstack.org>; community(a)lists.openstack.org <community(a)lists.openstack.org> Subject: Re: [openstack-community] Octavia :; Unable to create load balancer Hi, check your keystone auth settings. If i remember correctly there are two different sections to which require valid keystone settings. Fabian Monika Samal <monika.samal(a)outlook.com<mailto:monika.samal@outlook.com>> schrieb am Do., 30. Juli 2020, 21:43: Hello Michael and Amy, As suggested I checked and found below error on Octavia-api logs, but not sure how to resolve and proceed further with this. [cid:a29109eb-08ac-4f9a-92d4-2befba2cc90e] Regards, Moni ________________________________ From: Michael Johnson <johnsomor(a)gmail.com<mailto:johnsomor@gmail.com>> Sent: Thursday, July 30, 2020 9:41 PM To: Amy Marrich <amy(a)demarco.com<mailto:amy@demarco.com>> Cc: Monika Samal <monika.samal(a)outlook.com<mailto:monika.samal@outlook.com>>; openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>>; community(a)lists.openstack.org<mailto:community@lists.openstack.org> <community(a)lists.openstack.org<mailto:community@lists.openstack.org>> Subject: Re: [openstack-community] Octavia :; Unable to create load balancer Thank you for forwarding this Amy. Hi Moni, Can you check the Octavia API process log and the horizon log files to see what is causing the "Internal Server Error"? This sounds like a configuration file problem as Amy mentioned. There should be log messages in one of those two locations that will point to the problem. Michael On Thu, Jul 30, 2020 at 6:10 AM Amy Marrich <amy(a)demarco.com<mailto:amy@demarco.com>> wrote: > > Adding the discuss list where you might get more help, but also double check your config file for any extra spaces or typos. > > Thanks, > > Amy (spotz) > > On Thu, Jul 30, 2020 at 6:30 AM Monika Samal <monika.samal(a)outlook.com<mailto:monika.samal@outlook.com>> wrote: >> >> Hello All, >> >> I have been following https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavi… to deploy Octavia. I was successful in deployin Octavia but when I go to horizon dashboard and create loadbalancer am getting error "9876/v2.0/lbaas/loadbalancers, Internal Server Error". I have checked worker log at /var/log/kola-ansible/Octavia-worker.log and found oslo messaging was refusing connection I fixed it but still getting same error. Kindly help >> >> Regards, >> Moni >> _______________________________________________ >> Community mailing list >> Community(a)lists.openstack.org<mailto:Community@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/community

3 8

[nova] Victoria Milestone 2 Spec Freeze
by Balázs Gibizer 03 Aug '20

03 Aug '20

Hi, Last Thursday we reached Milestone 2 which means Nova is in Spec Freeze now. If you have a spec close to be approved and you wish to request a spec freeze exception then please send a mail to the ML about it. We will make the final decision on the weekly meeting on Thursday. Cheers, gibi

1 0

[nova] If any spec freeze exception now?
by Rambo 03 Aug '20

03 Aug '20

Hi,all:         I have a spec which is support volume backed server rebuild[0].This spec was accepted in Stein, but some of the work did not finish, so repropose it for Victoria.And this spec is depend on the cinder reimage api [1], now the reimage api is almost all completed. So I sincerely wish this spec will approved in Victoria. If this spec is approved, I will achieve it at once. Ref: [0]:https://blueprints.launchpad.net/nova/+spec/volume-backed-server-rebuild [1]:https://blueprints.launchpad.net/cinder/+spec/add-volume-re-image-api Best Regards Rambo

3 2

Two subnets under same network context.
by Anil Jangam 02 Aug '20

02 Aug '20

Hi, I have observed that one can create two subnets under the same network scope. See below an example of the use case. [image: Screen Shot 2020-08-01 at 2.22.15 PM.png] Upon checking the data structures, I saw that the segment type (vlan) and segment id (55) is associated with the "network" object and not with the "subnet" (I was under impression that the segment type (vlan) and segment id (55) would be allocated to the "subnet"). When I create the VM instances, they always pick the IP address from the SUBNET1-2 IP range. If the segment (vlan 55) is associated with "network" then what is the reason two "subnets" are allowed under it? Does it mean that VM instances from both these subnets would be configured under the same VLAN? /anil.

4 4

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal: Week R-11 Update
by Ghanshyam Mann 02 Aug '20

02 Aug '20

Hello Everyone, Please find the week R-11 updates on 'Ubuntu Focal migration' community goal. Tracking: https://storyboard.openstack.org/#!/story/2007865 Progress: ======= * We passed the first deadline which I planned initially but looking at the failure happing it will definitely will take more time. My first goal is "zero downtime in gate", so if we finish it little late (with all repos tested) is ok. * ~80 repos gate have been tested/fixed till now. ** https://review.opendev.org/#/q/topic:migrate-to-focal+(status:abandoned+OR+… * 115 repos are under test and failing. Debugging and fixing are in progress (If you would like to help, please check your project repos if I am late to fix them): ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open * Patches ready to merge: ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open+label%3AV… Bugs Report: ========== Summary: Total 4 (1 fixed, 3 in-progress). 1. Bug#1882521. (IN-PROGRESS) There is open bug for nova/cinder where three tempest tests are failing for volume detach operation. There is no clear root cause found yet -https://bugs.launchpad.net/cinder/+bug/1882521 We have skipped the tests in tempest base patch to proceed with the other projects testing but this is blocking things for the migration. 2. We encountered the nodeset name conflict with x/tobiko. (FIXED) nodeset conflict is resolved now and devstack provides all focal nodes now. 3. Bug#1886296. (IN-PROGRESS) pyflakes till 2.1.0 is not compatible with python 3.8 which is the default python version on ubuntu focal[1]. With pep8 job running on focal faces the issue and fail. We need to bump the pyflakes to 2.1.1 as min version to run pep8 jobs on py3.8. As of now, many projects are using old hacking version so I am explicitly adding pyflakes>=2.1.1 on the project side[2] but for the long term easy maintenance, I am doing it in 'hacking' requirements.txt[3] nd will release a new hacking version. After that project can move to new hacking and do not need to maintain pyflakes version compatibility. 4. Bug#1886298. (IN-PROGRESS) 'Markupsafe' 1.0 is not compatible with the latest version of setuptools[4], We need to bump the lower-constraint for Markupsafe to 1.1.1 to make it work. There are a few more issues[5] with lower-constraint jobs which I am debugging. What work to be done on the project side: ================================ This goal is more of testing the jobs on focal and fixing bugs if any otherwise migrate jobs by switching the nodeset to focal node sets defined in devstack. 1. Start a patch in your repo by making depends-on on either of below: devstack base patch if you are using only devstack base jobs not tempest: Depends-on: https://review.opendev.org/#/c/731207/ OR tempest base patch if you are using the tempest base job (like devstack-tempest): Depends-on: https://review.opendev.org/#/c/734700/ Both have depends-on on the series where I am moving unit/functional/doc/cover/nodejs tox jobs to focal. So you can test the complete gate jobs(unit/functional/doc/integration) together. This and its base patches - https://review.opendev.org/#/c/738328/ Example: https://review.opendev.org/#/c/738126/ 2. If none of your project jobs override the nodeset then above patch will be testing patch(do not merge) otherwise change the nodeset to focal. Example: https://review.opendev.org/#/c/737370/ 3. If the jobs are defined in branchless repo and override the nodeset then you need to override the branches variant to adjust the nodeset so that those jobs run on Focal on victoria onwards only. If no nodeset is overridden then devstack being branched and stable base job using bionic/xenial will take care of this. Example: https://review.opendev.org/#/c/744056/2 4. If no updates need you can abandon the testing patch (https://review.opendev.org/#/c/744341/) If it need updates then modify the same patch with proper commit msg, once it pass the gate then remove the Depends-On so that you can merge your patch before base jobs are switched to focal. This way we make sure no gate downtime in this migration. Example: https://review.opendev.org/#/c/744056/1..2//COMMIT_MSG Once we finish the testing on projects side and no failure then we will merge the devstack and tempest base patches. Important things to note: =================== * Do not forgot to add the story and task link to your patch so that we can track it smoothly. * Use gerrit topic 'migrate-to-focal' * Do not backport any of the patches. References: ========= Goal doc: https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-j… Storyboard tracking: https://storyboard.openstack.org/#!/story/2007865 [1] https://github.com/PyCQA/pyflakes/issues/367 [2] https://review.opendev.org/#/c/739315/ [3] https://review.opendev.org/#/c/739334/ [4] https://github.com/pallets/markupsafe/issues/116 [5] https://zuul.opendev.org/t/openstack/build/7ecd9cf100194bc99b3b70fa1e6de032 -gmann

1 0

[Openstack-Interop] Friday 31 - Updates and Questions for future of Interop?
by prakash RAMCHANDRAN 31 Jul '20

31 Jul '20

Hi all, We looked at OSF and Open-Infra initiatives and for sustaining and enhancing the Interop activity need your support. The current meeting notes are available on the site and will be meeting alternate Fridays Aug 14, 28,... 10 AM PST / 17 UTC - going forward on meetpad: Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting Details in therpadhttps://etherpad.opendev.org/p/interop Do you have suggestions for Branding efforts? Few Question: 1. Interop WG being an OSF or Board Driven, how can Interop work with Projects to ensure Branding Integrated Logo Programs and other Cloud Providers can leverage OpenStack Logo Program? a. We do have role to guide & reviewing refstack reports for Branding. We have decided to decouple Marketplace & Branding programs.Seeking feedback from community on proposed add-on programs for Bare metal(Ironic, MaaS,...) & "Kubernetes-ready OpenStack" b. Refstack hosting / Refstack-client are currently not maintained due to lack of volunteers to support. (seeking volunteers for updates - please reach out to @gmann in TC. c. Await user & operator survey annual reports, but if you have any Branding innovation like to propose or contribute please brainstorm your ideas here and bring it to midweek community meetings next week. ThanksFor Interop WGPrakash

1 0

Re: The Open Infrastructure Summit is Going Virtual!
by Thomas Goirand 31 Jul '20

31 Jul '20

On 7/23/20 6:30 PM, OpenStack Foundation wrote: > *STEP TWO* > *Submit your talks <https://t.e2ma.net/click/2ndfhc/6y85cs/q2gein>!* > The Call For > <https://t.e2ma.net/click/2ndfhc/6y85cs/6uhein>Presentations > <https://t.e2ma.net/click/2ndfhc/6y85cs/mniein>(CFP) deadline is August > 4 at 11:59pm PT, so start drafting your presentations and panels around > Open Infrastructure use cases like AI/Machine Learning, CI/CD, Container > Infrastructure, Edge Computing and of course, Public, Private and Hybrid > Clouds. I can't edit my BIO, as it says the email is invalid, however, I cannot edit it (the field is disabled). Who's in charge of cfp.openstack.org ? Cheers, Thomas Goirand (zigo)

2 7

[octavia] Proposing Ann Taraday and Gregory Thiemonge as Octavia core reviewers
by Michael Johnson 31 Jul '20

31 Jul '20

Hello Octavia community, I would like to propose Ann Taraday (ataraday_) and Gregory Thiemonge (gthiemonge) as core reviewers on the Octavia project. Both Ann and Gregory have made significant contributions to the Octavia code base and have provided quality code reviews. Over the last two release cycles Ann has lead the addition of Taskflow jobboard support to the amphora v2 driver. Gregory has worked on improving our tempest scenario test coverage and enhancing the Octavia OpenStack client plugin. I think that both would make excellent additions to the Octavia core reviewer team. Existing Octavia core reviewers, please reply to this email with your support or concerns with adding Ann and Gregory to the core team. Michael

2 2

Re: [octavia] Proposing Ann Taraday and Gregory Thiemonge as Octavia core reviewers
by German Eichberger 31 Jul '20

31 Jul '20

+1. Great to see some new people. Excellent work so far. Date: Thu, 30 Jul 2020 18:10:10 +0200 From: Carlos Goncalves <cgoncalves(a)redhat.com> To: Michael Johnson <johnsomor(a)gmail.com> Cc: openstack-discuss <OpenStack-discuss(a)lists.openstack.org> Subject: Re: [octavia] Proposing Ann Taraday and Gregory Thiemonge as Octavia core reviewers Message-ID: <CAM7b86j1wr0jfzxfcCjy-yNZZ5oA+iN0z_TPF1suUCmbDqwfPg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" +1. Excellent contributions by both of them -- thank you! On Thu, Jul 30, 2020 at 6:07 PM Michael Johnson <johnsomor(a)gmail.com> wrote: > Hello Octavia community, > > I would like to propose Ann Taraday (ataraday_) and Gregory Thiemonge > (gthiemonge) as core reviewers on the Octavia project. > > Both Ann and Gregory have made significant contributions to the > Octavia code base and have provided quality code reviews. Over the > last two release cycles Ann has lead the addition of Taskflow jobboard > support to the amphora v2 driver. Gregory has worked on improving our > tempest scenario test coverage and enhancing the Octavia OpenStack > client plugin. > > I think that both would make excellent additions to the Octavia core > reviewer team. > > Existing Octavia core reviewers, please reply to this email with your > support or concerns with adding Ann and Gregory to the core team. > > Michael > >

2 1

[all][oslo] Announcing the retirement of devstack-plugin-zmq
by Ken Giusti 31 Jul '20

31 Jul '20

Hi all, The Oslo team is announcing the retirement of the devstack-plugin-zmq project [0]. This plugin was introduced as part of the testing infrastructure for a new transport driver based on the ZeroMQ protocol [1]. The ZeroMQ driver has long been removed from the Oslo.Messaging project repo. The Oslo team is unaware of any deployments making use of it. Patches to remove this project are forthcoming and will use the topic 'retire-devstack-plugin-zmq'. Thanks, [0] https://opendev.org/openstack/devstack-plugin-zmq [1] https://zeromq.org/ -- Ken Giusti (kgiusti(a)gmail.com)

1 0

[tripleo] TripleO CI Summary: Unified Sprint 30
by Rafael Folco 31 Jul '20

31 Jul '20

Greetings, The TripleO CI team has just completed **Unified Sprint 30** (July 09 thru July 29). The following is a summary of completed work during this sprint cycle [1]: - Continued building internal component and integration pipelines for rhos-17 and rhos-16.2. - Switched promoter tests to run on Python3 and adapted molecule scenarios to the new test sequence standard. - Merged QCOW2 promotions and the new configuration engine in the promoter code. - All patches for CentOS-7 -> CentOS-8 stable/train upstream migration are up and merging / under review - https://review.opendev.org/#/q/topic:c7-to-c8-train+(status:open+OR+status:… - CentOS8 component and integration pipelines are done. - Improved Tempest skip list is now in production - https://opendev.org/openstack/openstack-tempest-skiplist - Design improvements to the Tempest scenario manager. - https://etherpad.opendev.org/p/tempest-scenario-manager - Fixed Libvirt bug on CI Zuul reproducer. - Ruck/Rover recorded notes [2]. - Vexxhost jobs have been turned back on for 3rd party CI, mixed results thus far w/ infrastructure stability and quality - Container-pull issues this sprint. Thanks to Alex for debugging w/ the infra team to help resolve the issue https://bugs.launchpad.net/tripleo/+bug/1889122 https://review.opendev.org/#/c/743629/ The planned work for the next sprint extends the work started in the previous sprint and focuses on downstream OSP 16.2 pipeline and on the next-gen promoter changes. The Ruck and Rover for this sprint are Marios Andreou (marios), Chandan Kumar (raukadah). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in hackmd [3]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-30 [2] https://hackmd.io/6Bx0FXwlRNCc75l39NSKvg [3] https://hackmd.io/QnprH9-yRTi6uWlEfaahoQ -- Folco

1 0

[all][oslo] Announcing the retirement of devstack-plugin-pika
by Ken Giusti 31 Jul '20

31 Jul '20

Hi all, The Oslo team is announcing the retirement of the devstack-plugin-pika project [0]. This plugin was introduced as part of the testing infrastructure for a new transport driver based on the Pika client library for RabbitMQ. This driver was developed as an alternative to the existing Kombu based driver. Testing of the new driver failed to show a meaningful improvement over the existing Kombu driver so development was dropped. The Pika driver has long been removed from the Oslo.Messaging project repo. The Oslo team is unaware of any deployments making use of it. Patches to remove this project are forthcoming and will use the topic 'retire-devstack-plugin-pika'. Thanks, [0] https://opendev.org/openstack/devstack-plugin-pika [1] https://github.com/pika/pika -- Ken Giusti (kgiusti(a)gmail.com)

1 0

networking-l2gw
by liuzhenjie＠bonc.com.cn 30 Jul '20

30 Jul '20

您好：我现在想要使用l2gw这个服务。但是，我得环境是通过kolla-ansible部署的，这个服务在neutron-server的容器里起来后，在执行创建资源时报错如下：我得ovsdb server是一台安装了ovs的x86服务器。l2gw服务起来后发现neutron-server和该x86服务器没有建立ovsdb的连接。 ********* 积极主动、认真工作、快乐生活 ********** ***************************************** * 北京东方国信科技股份有限公司数据科学事业部-公有云研发中心 * 姓名：刘镇杰 * 座机：0108486-6996 * 手机：15689961523 * 邮箱：liuzhenjie(a)bonc.com.cn * 网址：http://www.bonc.com.cn * 地址：北京市朝阳区创达三路1号院1号楼东方国信大厦 ***************************************** 系统集成部提供可靠的IT基础设施建设、运维支撑保障服务，确保业务系统稳定、高效运行，降低安全生产风险。为提供便捷的集成服务支持、提升服务品质，从2018年9月1日起开通系统集成服务台作为统一服务入口。服务台邮箱：xtjc(a)bonc.com.cn 服务台门户：http://cloud.bonc.local

2 1

[cinder] new driver merge deadline has passed
by Brian Rosmaita 30 Jul '20

30 Jul '20

This is a notification that the Cinder new driver merge deadline for Victoria has passed [0]. At yesterday's Cinder team meeting, we discussed Walt's work on the ceph-iscsi driver [1], and the team came to a consensus that we will extend the deadline *for this driver only* into the R-9 week (cinder midcycle meeting 2 week), which will make the deadline for the ceph-iscsi driver Thursday 13 August 23:59 UTC. This is an extraordinary step, as traditionally Cinder has strictly enforced the new driver merge deadline. The reasons for this exception are: - this is a community driver - the check/gate jobs for this driver will be run from the cinder zuul configuration, not a third-party CI system, so the cinder team has full transparency into the working state of the CI system I want to emphasize again that this is an extraordinary event, and as such, should not be expected to set a precedent beyond the Victoria development cycle. And, of course, this deadline extension is not a guarantee that the driver will be included in the Victoria release. Thank you for your attention to this matter, brian [0] https://releases.openstack.org/victoria/schedule.html#v-cinder-driver-deadl… [1] https://review.opendev.org/#/q/(topic:ceph-iscsi-zuul+OR+topic:ceph-iscsi)+…

1 0

Looking for recommendation what OS to use for a minimal installation
by Eliezer Croitor 30 Jul '20

30 Jul '20

Hey Everybody, In the last month I have tried to install OpenStack minimal from the docs: https://docs.openstack.org/install-guide/openstack-services.html#minimal-dep loyment-for-train https://docs.openstack.org/install-guide/openstack-services.html#minimal-dep loyment-for-ussuri on CentOS 7 and CentOS 8. With the packages from CentOS I need to "patch" or "fix" the installed conf files of httpd and couple other files around. I have tried DevStack and PackStack before but I want to move to the next step. Any recommendation where to start? What OS to use? Etc. Thanks. Eliezer ---- Eliezer Croitoru Tech Support Mobile: +972-5-28704261 Email: <mailto:ngtech1ltd@gmail.com> ngtech1ltd(a)gmail.com

2 2

[tc] monthly meeting
by Mohammed Naser 30 Jul '20

30 Jul '20

Hi everyone, Our monthly TC meeting is scheduled for next Thursday, August 6th, at 1400 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, August 5, at 1900 UTC. Thank you, Regards, -- Mohammed Naser VEXXHOST, Inc.

1 0

Re: [openstack-community] Octavia :; Unable to create load balancer
by Fabian Zimmermann 30 Jul '20

30 Jul '20

service_auth keystone_authtoken if i read the docs correctly. Maybe you can just paste your config (remove/change passwords) to paste.openstack.org and post the link? Fabian Fabian Zimmermann <dev.faz(a)gmail.com> schrieb am Do., 30. Juli 2020, 21:52: > Hi, > > check your keystone auth settings. > > If i remember correctly there are two different sections to which require > valid keystone settings. > > Fabian > > Monika Samal <monika.samal(a)outlook.com> schrieb am Do., 30. Juli 2020, > 21:43: > >> Hello Michael and Amy, >> >> As suggested I checked and found below error on Octavia-api logs, but not >> sure how to resolve and proceed further with this. >> >> >> Regards, >> Moni >> ------------------------------ >> *From:* Michael Johnson <johnsomor(a)gmail.com> >> *Sent:* Thursday, July 30, 2020 9:41 PM >> *To:* Amy Marrich <amy(a)demarco.com> >> *Cc:* Monika Samal <monika.samal(a)outlook.com>; openstack-discuss < >> openstack-discuss(a)lists.openstack.org>; community(a)lists.openstack.org < >> community(a)lists.openstack.org> >> *Subject:* Re: [openstack-community] Octavia :; Unable to create load >> balancer >> >> Thank you for forwarding this Amy. >> >> Hi Moni, >> >> Can you check the Octavia API process log and the horizon log files to >> see what is causing the "Internal Server Error"? >> >> This sounds like a configuration file problem as Amy mentioned. There >> should be log messages in one of those two locations that will point >> to the problem. >> >> Michael >> >> On Thu, Jul 30, 2020 at 6:10 AM Amy Marrich <amy(a)demarco.com> wrote: >> > >> > Adding the discuss list where you might get more help, but also double >> check your config file for any extra spaces or typos. >> > >> > Thanks, >> > >> > Amy (spotz) >> > >> > On Thu, Jul 30, 2020 at 6:30 AM Monika Samal <monika.samal(a)outlook.com> >> wrote: >> >> >> >> Hello All, >> >> >> >> I have been following >> https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavi… >> to deploy Octavia. I was successful in deployin Octavia but when I go to >> horizon dashboard and create loadbalancer am getting error >> "9876/v2.0/lbaas/loadbalancers, Internal Server Error". I have checked >> worker log at /var/log/kola-ansible/Octavia-worker.log and found oslo >> messaging was refusing connection I fixed it but still getting same error. >> Kindly help >> >> >> >> Regards, >> >> Moni >> >> _______________________________________________ >> >> Community mailing list >> >> Community(a)lists.openstack.org >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/community >> >

2 1

Re: [openstack-community] Octavia :; Unable to create load balancer
by Amy Marrich 30 Jul '20

30 Jul '20

Adding the discuss list where you might get more help, but also double check your config file for any extra spaces or typos. Thanks, Amy (spotz) On Thu, Jul 30, 2020 at 6:30 AM Monika Samal <monika.samal(a)outlook.com> wrote: > Hello All, > > I have been following > https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavi… > to deploy *Octavia. *I was successful in deployin Octavia but when I go > to horizon dashboard and create loadbalancer am getting error *"9876/v2.0/lbaas/loadbalancers, > Internal Server Error". *I have checked worker log* at > /var/log/kola-ansible/Octavia-worker.log *and found oslo messaging was > refusing connection I fixed it but still getting same error. Kindly help > > Regards, > Moni > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community >

3 3

[manila] Please delete some branches
by Goutham Pacha Ravi 30 Jul '20

30 Jul '20

Hello, I'd like to request the deletion of some branches in manila that have now transitioned to EOL. These branches can be removed from openstack/manila, openstack/python-manilaclient and openstack/manila-ui: stable/pike stable/ocata I'd also like to request the deletion of "driverfixes" branches from the openstack/manila repository. These branches were created to host vendor fixes to branches that were no longer being tested; however, with our "extended maintenance" stance, we've effectively removed the need for these branches. These branches will no longer be maintained, and so they can be removed as well: driverfixes/mitaka driverfixes/newton driverfixes/ocata Thank you so much for your assistance! Goutham Pacha Ravi

2 3

[tripleo] manual about TripleO core reviewers
by Emilien Macchi 30 Jul '20

30 Jul '20

Hi people, I've started a documentation patch about our core reviewers. Core or not, please be involved in Gerrit directly. https://review.opendev.org/#/c/743999 Hopefully it'll help people to understand about expectations but also give a refresh to current cores. Note: this was inspired by https://wiki.openstack.org/wiki/Ironic/CoreTeam - Thanks a lot to the Ironic team! Thanks, -- Emilien Macchi

1 0

[neutron] Drivers meeting 31.07.2020 - agenda
by Slawek Kaplonski 30 Jul '20

30 Jul '20

Hi, For tomorrow’s drivers meeting we have couple of items to discuss. Full agenda is at https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda but below is short summary also. RFEs: https://bugs.launchpad.net/neutron/+bug/1889431 - [RFE] Add local-ip-prefix to Neutron metering label rules https://bugs.launchpad.net/neutron/+bug/1880532 - [RFE]L3 Router should support ECMP This one was already discussed in the past but now we know it can be done (almost) without changes in existing API https://bugs.launchpad.net/neutron/+bug/1888487 - Change the default value of "propagate_uplink_status" to True We also have 2 items added by Rodolfo to the "On demand” section: • (ralonsoh) https://bugs.launchpad.net/neutron/+bug/1887523: a good proposal to improve the DB performance, that could be done in parallel to https://review.opendev.org/#/c/739139/ • (ralonsoh) https://bugs.launchpad.net/neutron/+bug/1888829: Improve core plugin extension filtering using the mechanism driver information (in other words: if loaded mech drivers do not support any ML2plugin extension, this extension will be gracefully removed). — Slawek Kaplonski Principal software engineer Red Hat

2 1

[ironic] ironic-python-agent failed to lookup node
by Xiaoyu Min 29 Jul '20

29 Jul '20

Hello Experts: I'm new to the openstack and trying to deploy one baremental node but it failed on "wait call-back" stage. I checked IPA log on deploy image and it reports the following error [1]. I aslo manually run the command [2] it gave me the same error "404". I used the devstack to depoly openstack (stable/ussuri). What's the possible problem? Any suggestion is appreciated. -Jack [1]: DEBUG ironic_python_agent.ironic_api_client [-] Looking up node with addresses 'e4:43:4b:93:4c:12,e4:43:4b:93:4c:10,0c:42:a1:56:b8:c5,e4:43:4b:93:4c:13,e4:43:4b:93:4c:11,0c:42:a1:56:b8:c4' and UUID None at http://10.75.205.241/baremetal _do_lookup /usr/lib/python3.6/site-packages/ironic_python_agent/ironic_api_client.py:163[00m ERROR ironic_python_agent.ironic_api_client [-] An error occurred while attempting to discover the available Ironic API versions, falling back to using version 1.31: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) ERROR ironic_python_agent.ironic_api_client Traceback (most recent call last): ERROR ironic_python_agent.ironic_api_client File "/usr/lib/python3.6/site-packages/ironic_python_agent/ironic_api_client.py", line 97, in _get_ironic_api_version ERROR ironic_python_agent.ironic_api_client data = jsonutils.loads(response.content) ERROR ironic_python_agent.ironic_api_client File "/usr/lib/python3.6/site-packages/oslo_serialization/jsonutils.py", line 248, in loads ERROR ironic_python_agent.ironic_api_client return json.loads(encodeutils.safe_decode(s, encoding), **kwargs) ERROR ironic_python_agent.ironic_api_client File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads ERROR ironic_python_agent.ironic_api_client return _default_decoder.decode(s) ERROR ironic_python_agent.ironic_api_client File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode ERROR ironic_python_agent.ironic_api_client obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ERROR ironic_python_agent.ironic_api_client File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode ERROR ironic_python_agent.ironic_api_client raise JSONDecodeError("Expecting value", s, err.value) from None ERROR ironic_python_agent.ironic_api_client json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) ERROR ironic_python_agent.ironic_api_client [00m WARNING ironic_python_agent.ironic_api_client [-] Failed looking up node with addresses 'e4:43:4b:93:4c:12,e4:43:4b:93:4c:10,0c:42:a1:56:b8:c5,e4:43:4b:93:4c:13,e4:43:4b:93:4c:11,0c:42:a1:56:b8:c4' at http://10.75.205.241/baremetal, status code: 404[00m]]] [2]: curl http://10.75.205.241/baremetal [...snip...] <title>404 Not Found</title>

1 0

[cinder] video + IRC meeting survey
by Brian Rosmaita 29 Jul '20

29 Jul '20

Today we had our first Cinder meeting held simultaneously in videoconference and on IRC. I have posted a quick survey to see if there's support for continuing this monthly experiment. (The next video + IRC meeting would be the last week of August.) https://rosmaita.wufoo.com/forms/r1twmaya13asv1c/ Please respond before 12:00 UTC on Tuesday, 4 August. thanks! brian

1 0

[tripleo] stable/train migration from CentOS-7 to CentOS-8
by Wesley Hayutin 29 Jul '20

29 Jul '20

Greetings, I wanted to give everyone a heads up that the migration of upstream stable/train jobs from CentOS-7 to CentOS-8 [1] is close. CentOS-7 stable/train will continue to be tested in our 3rd party periodic pipeline and builds of CentOS-7 stable/train will be qualified here [2] Please let me know if you have any questions. Thanks! [1] https://review.opendev.org/#/c/738375 [2] https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-integ…

1 1

Neutron bandwidth metering based on remote address
by Jonas Schäfer 29 Jul '20

29 Jul '20

Dear list, We are trying to implement tenant bandwidth metering at the neutron router level. Since some of the network spaces connected to the external interface of the neutron router are supposed to be unmetered, we need to match on the remote address. Conveniently, there exists a --remote-ip-prefix option on meter label create; however, since [1], its meaning was changed to the exact opposite: Instead of matching on the *remote* prefix (towards the external interface), it matches on the *local* prefix (towards the OS tenant network). In an ideal world, we would want to revert that change and instead introduce a --local-ip-prefix option which covers that use-case. I suppose this is not a thing we *should* do though, given that this change made it into a few releases already. Instead, we’ll have to create a new option (which whatever name) + associated database schema + iptables rule patterns to implement the feature. The questions associated with this are now: - Does this make absolutely no sense to anyone? - What is the process for this? I suppose since this change was made intentionally and passed review, our desired change needs to go through a feature request process (blueprints maybe?). kind regards, Jonas Schäfer [1]: https://opendev.org/openstack/neutron/commit/ 92db1d4a2c49b1f675b6a9552a8cc5a417973b64 -- Jonas Schäfer DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 37 jonas.schaefer(a)cloudandheat.com | www.cloudandheat.com New Service: Managed Kubernetes designed for AI & ML https://managed-kubernetes.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann Authorized signatory: Kristina Rübenkamp

2 4