- openstack-discuss - lists.openstack.org

OpenInfra Summit Berlin- CFP Deadline in 24 Hours!
by Erin Disney 09 Feb '22

09 Feb '22

The deadline for the upcoming OpenInfra Summit’s Call for Presentations is in 24 hours! CFP for the Berlin Summit (June 7-9th) is still open until February 9th at 22:59 UTC (4:59 PM CT). Reminder that Summit attendance fees are waived for all accepted speakers. Submit your talk for the OpenInfra Summit here: https://cfp.openinfra.dev/app/berlin-2022 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security More Summit resources: Registration is live at Early Bird pricing: https://openinfrasummitberlin.eventbrite.com/ Sponsorships are available: https://openinfra.dev/summit-sponsor Apply for the Travel Support Program: https://openinfrafoundation.formstack.com/forms/TSP_Berlin2022 Questions or issues with your submission? Email speakersupport(a)openinfra.dev and we will be happy to help you sort it out. Thanks, Erin Erin Disney Event Marketing Open Infrastructure Foundation Erin Disney Event Marketing Open Infrastructure Foundation

1 0

[all][Neutron][Octavia][Nova][Kuryr] Bump pyroute2 version to 0.6.5 in stable/wallaby
by Lucas Alvares Gomes 08 Feb '22

08 Feb '22

Hi, I currently have a patch up for openstack/requirements [0] bumping the version of the pyroute2 library from 0.5.14 to 0.6.5 as the older version have a memory leak issue [1] in the NDB module which can cause the service using the library to be killed by the OOM killer because of an out-of-memory condition. This email was a suggestion by a core reviewer to raise awareness from the broader community to this change/issue. Please if you have any concerning about this version bump let us know here on in the patch itself [0] [0] https://review.opendev.org/c/openstack/requirements/+/828091 [1] https://github.com/svinota/pyroute2/issues/789 Cheers, Lucas

2 2

[ironic]Anaconda deploy interface config
by Carol Bouchard 08 Feb '22

08 Feb '22

Ironic folks: I'm trying to spawn a RHEL7 image using a kickstart file and having issues with stage2 file. First I used bifrost to initially setup a couple of VMs. (There is no openstack/glance). I'm now using one of those VMs to boot up with RHEL7. I changed the VM config with the following: *| deploy_interface | anaconda* * | instance_info | {'kernel': 'http://myip:8080/RHEL7/vmlinuz <http://myip:8080/RHEL7/vmlinuz>', 'ramdisk': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'image_source': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'stage2': 'http://myip:8080/RHEL7/squashfs.img <http://myip:8080/RHEL7/squashfs.img>', 'ks_cfg': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>', 'ks_template': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>'}* ironic.conf changes I made are as follows: *enabled_deploy_interfaces = direct,ramdisk,anaconda* *[anaconda]default_ks_template = file:///etc/ironic/ks.cfg.template* The error I'm getting is as follows: *$ baremetal node show testvm1 --field last_error* *| last_error | Deploy step deploy.deploy failed with IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'.* Tail end of traceback is as follows: * ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/common/pxe_utils.py", line 1245, in cache_ramdisk_kernel ironic-conductor[]: ERROR ironic.conductor.utils deploy_utils.fetch_images(ctx, TFTPImageCache(), list(t_pxe_info.values()), ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/deploy_utils.py", line 240, in fetch_images ironic-conductor[]: ERROR ironic.conductor.utils cache.fetch_image(href, path, ctx=ctx, force_raw=force_raw) ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 120, in fetch_image ironic-conductor[]: ERROR ironic.conductor.utils dest_up_to_date = _delete_dest_path_if_stale(master_path, ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 460, in _delete_dest_path_if_stale ironic-conductor[]: ERROR ironic.conductor.utils os.unlink(dest_path) ironic-conductor[]: ERROR ironic.conductor.utils IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'* Please advise. Carol

3 5

[election][cinder] PTL Candidacy for Z
by Rajat Dhasmana 08 Feb '22

08 Feb '22

Hi All, I would like to announce my candidacy for PTL of the Cinder project for the Z cycle. Since this is the first time I'm proposing my candidacy, I would like to briefly introduce myself. I started contributing to OpenStack back in the Queens release (although not very actively) and started focusing on the Cinder project in the Rocky release. I became a core reviewer in Cinder in the mid of the Stein release and since then I've been actively contributing to the Cinder project in terms of features, bug fixes, reviews etc. I'm also a part of Cinder's core security group and a stable core and currently serving as release liaison for Cinder for the past 3 releases. Coming to the focus for the Z release, Cinder receives an abundance of commits every cycle in terms of new drivers, driver features, core cinder features, bug fixes, improvements etc and we've always faced a shortage in reviews. It is not due to fewer people working actively but more of a priority issue in their respective roles. I would like to encourage contributors to discuss with their managers about the importance of code review in opensource and how it is helpful for the community and the individuals as well. Apart from that, I would like to revisit the security issues backlog since that hasn't been looked upon in quite some time and if we encounter something that needs attention, we can also hold core security meetings from time to time to address the issues. We are also getting active driver contributions every cycle which is a good thing, but sadly the driver implementation patches seem to have a lot of mistakes which are well documented in the driver contribution docs and something I would like to highlight in the Z PTG (as most of the vendors join it and propose their driver ideas). Again, the documentation is not perfect as we discussed in Yoga PTG. Following up upon this and improving it is another focus I support for Cinder. Lastly, I would like to put more emphasis upon the 3rd Party CI compliance check which we haven't done in a while and it would be good to know how many vendors are actually maintaining their CI consistently. There are some new ideas started by Brian in the past releases which I would like to continue. Some examples include the last cinder meeting being a video+IRC meeting and every third Friday of the month, we have a festival of XS reviews which significantly reduced the backlog of open patches. In the end, I would like to say, I want to continue the good trends set in the Cinder community and improve on certain areas where there is not much attention being given. I will do my best to address the above mentioned items during my time as PTL. Thanks for considering me. Rajat Dhasmana (whoami-rajat)

1 0

[election][tc] My TC non-candidacy
by Radosław Piliszek 08 Feb '22

08 Feb '22

Dears, I am hereby announcing my TC non-candidacy. It was a great pleasure to work with you but my personal and professional life has shifted away from OpenStack enough to make it hard for me to dedicate the time the TC deserves. Kind regards, -yoctozepto

4 3

[all][elections][ptl][tc] Combined PTL/TC z cycle Election Nominations Kickoff
by Ghanshyam Mann 08 Feb '22

08 Feb '22

Hello Everyone, Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 15, 2022 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/z/<Project_Name or "TC">/<email_address> (for example, "candidates/z/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Feb 22, 2022 23:45 UTC through to Mar 01, 2022 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Feb 08, 2022 23:45 UTC PTL + TC nomination ends @ Feb 15, 2022 23:45 UTC TC campaigning starts @ Feb 15, 2022 23:45 UTC TC campaigning ends @ Feb 22, 2022 23:45 UTC PTL + TC elections start @ Feb 22, 2022 23:45 UTC PTL + TC elections end @ Mar 01, 2022 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2022-02-15 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -gmann & The OpenStack Technical Election Officials

1 0

[stable] sphinx docs jobs fail on old stable branches (no more py2 support)
by Előd Illés 08 Feb '22

08 Feb '22

Hi stable maintainers, This mail is about to get some attention to build-openstack-sphinx-docs job that recently started to fail on old stable branches (Queens and Pike) and block gates for about ~30 repositories. (The failures are also visible in periodic stable jobs). This is because py27 support from sphinx jobs were removed [1] recently. (Python 3 (py35) support was mostly done in Rocky so that branch is not affected) To unblock the gates I see the following options: 1. fix sphinx jobs to work with py35 (most probably requires some patches to backport - in a squashed patch - and maybe some resolution of requirement conflicts) 2. set sphinx jobs to non-voting (even better to remove them to do not use resources unnecessarily) 3. revert the patch [1] that removed the py2 support of sphinx (maybe the easiest thing to do, though i understand that py2 support is something that shouldn't be kept forever) 4. teams examine their old branches and if they are not really maintained, haven't merged patches recently, then probably it is a good time to propose their EOL transition according to the EOL process [1] Some additional thoughts: - When Extended Maintenance was introduced the community agreed that certain CI jobs can be removed, CI coverage can be reduced as time goes. - To keep open an old branch in Extended Maintenance helps the cooperation between vendors / users as instead of maintaining it by themselves it can be done with a common effort, which could be beneficial for everyone. On the other hand, if there are no maintainers or invested efforts to keep the branch and CI alive, then it is a reasonable decision to transition the branch to End of Life. Please consider the above options and act to eliminate the gate failures / periodic stable job failures. [1] https://review.opendev.org/c/zuul/zuul-jobs/+/827588 <https://review.opendev.org/#/q/I98c3da5b02a4ac7fb9d7bd8e00170762e77b9f40>[2] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l… Thanks, Előd

2 1

[election][ptl][cinder] PTL non-candidacy
by Brian Rosmaita 08 Feb '22

08 Feb '22

Hello Argonauts, With the election season rapidly approaching [0], I want to communicate my intentions to the team, to wit, I will not be standing for PTL for the Z cycle. I've served as PTL for five cycles, which conflicts with my belief that it's good for open source projects to rotate leadership. I think the Cinder project is fairly healthy, but it will be good to have someone take the Cinder helm who has a fresh perspective and who will be as excited to be PTL as I was way back in Ussuri. We have an excellent project team, and I have no doubt that whoever steps up will have plenty of support from the Cinder community (including me, I don't have any intention of going anywhere in the near term). cheers, brian [0] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027070…

7 6

Floating IP issue regarding Latest upgrade to XENA
by Adivya Singh 08 Feb '22

08 Feb '22

Hi Team, We have the latest upgrade to XENA, and we are facing an issue with XENA release , where a few times, even Floating IP attached to the instance are not reachable. I tried various ways to troubleshoot the issue, Regarding The IP is reachable from the router Namespace, The router IP is reachable, L3 agent is working Fine, as other Floating IP are reachable which are hosted through router on L3 agent, All ports are up, Interfaces are up, SNAT and DNAT are working Fine, But as soon as i dissociate and associate the Floating IP , it started working Fine Any Idea, why this Happening , and later on Fixed when Floating IP is dissociate and associate again, and later again starts happening Regards Adivya Singh

1 0

[ironic] Each deploy overwrites the entire target disk
by Radosław Piliszek 08 Feb '22

08 Feb '22

Dears, I have a question regarding the default behaviour of Ironic Python Agent - it seems that each deploy causes the entire target disk to be overwritten. I have noticed this after replacing disks with larger ones, the deployment process started taking considerably longer and I observed that each sector is rewritten on the target device. Is that expected? Can I somehow avoid it? I am using whole-disk, qcow2 images that are much smaller than the disk size (even in raw form). I am running Ironic Wallaby. The deployment method is direct. Kind regards, -yoctozepto

2 4

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 08 Feb '22

08 Feb '22

Hey team, Since there's nothing on the agenda for tomorrow's meeting, it has been cancelled. We will meet again next week.

1 0

[nova][ops] Problem with nova policies for resume operation
by Massimo Sgaravatto 07 Feb '22

07 Feb '22

Dear all I am running a Xena installation I have modified the nova policy fail so that certain operations can be done only by the user who created the instance, or by the administrator This [*] is my policy.yaml file. While the suspend operation works as intended (I can suspend only my instances and I am not allowed to suspend an instance created by another user) I am not able to resume an instance that I own and that I have previously suspended. I get this error: ERROR (Forbidden): Policy doesn't allow os_compute_api:os-suspend-server:suspend to be performed. (HTTP 403) (Request-ID: req-c57458bc-b1ea-4b40-a1d2-0f67608ef673) Only removing the line: "os_compute_api:os-suspend-server:suspend": "rule:admin_api or user_id:%(user_id)s" from the policy file, I am able to resume the instance. I am not able to understand what is wrong with that policy. Any hints ? Thanks, Massimo [*] # Pause a server # POST /servers/{server_id}/action (pause) # Intended scope(s): system, project "os_compute_api:os-pause-server:pause": "rule:admin_api or user_id:%(user_id)s" # Delete a server # DELETE /servers/{server_id} # Intended scope(s): system, project "os_compute_api:servers:delete": "rule:admin_api or user_id:%(user_id)s" # Resize a server # POST /servers/{server_id}/action (resize) # Intended scope(s): system, project "os_compute_api:servers:resize": "rule:admin_api or user_id:%(user_id)s" # Rebuild a server # POST /servers/{server_id}/action (rebuild) # Intended scope(s): system, project "os_compute_api:servers:rebuild": "rule:admin_api or user_id:%(user_id)s" # Stop a server # POST /servers/{server_id}/action (os-stop) # Intended scope(s): system, project "os_compute_api:servers:stop": "rule:admin_api or user_id:%(user_id)s" # Resume suspended server # POST /servers/{server_id}/action (resume) # Intended scope(s): system, project "os_compute_api:os-suspend-server:resume": "rule:admin_api or user_id:%(user_id)s" # Suspend server # POST /servers/{server_id}/action (suspend) # Intended scope(s): system, project "os_compute_api:os-suspend-server:suspend": "rule:admin_api or user_id:%(user_id)s"

4 8

[kolla-ansible][mariadb]error (galera cluster problem ?)
by Franck VEDEL 07 Feb '22

07 Feb '22

Hello, I am in an emergency situation, quite catastrophic situation because I do not know what to do. I have an Openstack cluster with 3 servers (serv1, serv2, serv3). He was doing so well… A network admin came to me and told me to change an MTU on the cards. I knew it shouldn't be done...I shouldn't have done it. I did it. Of course, it didn't work as expected. I went back to my starting configuration and there I have a big problem with mariadb which is set up on serv1 and serv2. Here are my errors: 2022-02-04 17:40:36 0 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out) at gcomm/src/pc.cpp:connect():160 2022-02-04 17:40:36 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():209: Failed to open backend connection: -110 (Connection timed out) 2022-02-04 17:40:36 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1475: Failed to open channel 'openstack' at 'gcomm://10.0.5.109:4567,10.0.5.110:4567': -110 (Connection timed out) 2022-02-04 17:40:36 0 [ERROR] WSREP: gcs connect failed: Connection timed out 2022-02-04 17:40:36 0 [ERROR] WSREP: wsrep::connect(gcomm://10.0.5.109:4567,10.0.5.110:4567) failed: 7 2022-02-04 17:40:36 0 [ERROR] Aborting I do not know what to do. My installation is done with kolla-ansible, mariadb docker restarts every 30 seconds. Can the "kolla-ansible reconfigure mariadb" command be a solution? Could the command "kolla-ansible mariadb recovery" be a solution? Thanks in advance if you can help me. Franck

3 6

[ops][cinder] resource count survey
by Brian Rosmaita 07 Feb '22

07 Feb '22

Hello operators, The Cinder project is working on the cinder quotas system in an effort to improve its accuracy and remove the necessity for operators to go through and clean it up occasionally when it gets out of sync with reality. One way to do this is to use dynamic database counting (instead of storing the usage info in a table where it can become outdated). Whether this will be a good change depends on how many records the database has to process during a transaction, which in turn depends on how many Cinder resources a project has. So we need to get some information from you. Please take this brief survey: https://rosmaita.wufoo.com/forms/cinder-resource-count-survey/ The survey closes on Wednesday 30 March at 1200 UTC, so that we can have data to discuss during the "Z" PTG. But please don't procrastinate, it's only 6 questions and the answers are all positive integers. It shouldn't take long to fill out! Thanks! brian

1 0

Re: Recently Upgraded to XENA and getting this error
by Mohammed Naser 07 Feb '22

07 Feb '22

The fix hasn’t landed yet since then. On Fri, Feb 4, 2022 at 8:38 AM Adivya Singh <adivya1.singh(a)gmail.com> wrote: > hi Mohammed, > > This is for pike release, I am talking about Xena > > Regards > Adivya Singh > > On Thu, Feb 3, 2022 at 4:37 AM Mohammed Naser <mnaser(a)vexxhost.com> wrote: > >> I think you're running into this which has been broken for a hot minute: >> >> https://review.opendev.org/c/openstack/horizon/+/808102 >> >> that patch works for us locally. >> >> On Wed, Feb 2, 2022 at 10:37 AM Adivya Singh <adivya1.singh(a)gmail.com> >> wrote: >> > >> > Hello, >> > >> > We have recently upgraded to XENA release of Openstack, and getting >> this error while trying to Resize instance using GUI, it is telling "Danger >> , Please try Later" >> > Same is working properly from CLI without any issue >> > >> > Any thoughts on this >> > >> > Regards >> > Adivya Singh >> >> >> >> -- >> Mohammed Naser >> VEXXHOST, Inc. >> > -- Mohammed Naser VEXXHOST, Inc.

2 1

[baremetal-sig][ironic] Tue Feb 8, 2022, 2pm UTC: Scaling Ironic
by Arne Wiebalck 07 Feb '22

07 Feb '22

Dear all, The Bare Metal SIG will meet tomorrow Tue Feb 8, 2022, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Julia Kreger on "Scaling Ironic" providing details on the massive performance and scaling improvements Ironic has seen in the latest releases. Come along and bring your questions, everyone is welcome! As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Cheers, Arne

1 0

[all][elections][ptl][tc] Combined PTL/TC Election Feb-Mar 2022 Season
by Ghanshyam Mann 07 Feb '22

07 Feb '22

Hello Everyone! This is time for the Z development cycle Technical elections. Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 8, 2022 23:45. Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. The PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. If teams do not produce any PTL candidate during the nomination period, or are interested in considering alternatives prior to nominations, the TC may consider requests to switch to the new distributed leadership model they recently documented[1]. In keeping with the established plan[1 ] to gradually reduce the size of the Technical Committee, we will only fill five (5) seats in this coming election. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[3] so that we may address your concerns. [1] https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… [2] https://governance.openstack.org/tc/reference/charter.html#number-of-seats-… [3] https://governance.openstack.org/election/#election-officials -gmann & The OpenStack Technical Election Officials

1 0

[designate] Tentative PTG time slots for Designate
by Michael Johnson 05 Feb '22

05 Feb '22

Hello Designate community, I have tentatively put Designate down for two time slots for the PTG. Tuesday April 5th 15:00 - 17:00 UTC Wednesday April 6th 15:00-17:00 UTC Please let me know if those times do not work for you and you would like to attend. Michael

1 0

[release] Release countdown for week R-7, Feb 07-11
by Előd Illés 04 Feb '22

04 Feb '22

Development Focus ----------------- We are entering the last weeks of the Yogadevelopment cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on February 10th, 2022. A quick reminder of the upcoming 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 (February 17th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 24th, 2022) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 24th, 2022. 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 (March 7th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 24th, 2022) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (February 24th, 2022). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Extra-ATC freeze: February 10th, 2022(R-7 week) Non-client library freeze: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Yoga final release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) ElődIllés irc: elodilles

1 0

[oslo] feature freeze - Feb 07 - Feb 11 (R-7)
by Herve Beraud 04 Feb '22

04 Feb '22

Hello Osloers, Just a friendly reminder that oslo's feature freeze will happen next week (R-7 - Feb 07 - Feb 11). It's earlier than everyone else, and if you're wondering why, we have a policy[1] that discusses it. The main thing is that if you have features you want to get into Oslo libraries this cycle, please make sure they merge by Friday. After that we'll need to go through the FFE process and there's no guarantee we can land them. Feel free to ping us on IRC if you need reviews. Thanks for your attention. [1] http://specs.openstack.org/openstack/oslo-specs/specs/policy/feature- freeze.html -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

openstack swift and local path filename
by admin＠gibdev.ru 03 Feb '22

03 Feb '22

I have installed openstack swift 2.25.2 object-server writes and serves local files from disk It receives http requests from a proxy-server, for example: http get: /sdb4/525/AUTH_xxxxxxxxxxxxxxxxxxxxxxxx/panda/2c34a941f581d848e2799e7a0956ea14f3cb27b0e516aef99a438fdaebbd7592 reads a file from disk: /srv/node/sdb4/objects/525/346/835ee70dce07217d8e33147e0864f346/1643910916.71556.data how can I calculate the path by which the file will be read by object-server? thanks

2 1

[PTG] April 2022 Team Signup
by Kendall Nelson 03 Feb '22

03 Feb '22

Hello Everyone! Last week, we announced the next virtual PTG will be held virtually from Monday, April 4th to Friday, April 8th, 2022. We will have the same schedule set up available as last time with three windows of time spread across the day to cover all timezones with breaks in between. To signup your team, you must complete BOTH the survey[1] AND reserve time in the ethercalc[2] by end of day March 11th. We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions with 3 rules/guidelines: 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Again, you need to fill out BOTH the ethercalc AND the survey to complete your team's sign up. If you have any issues with signing up your team, due to conflict or otherwise, please let me know! While we are trying to empower you to make your own decisions as to when you meet and for how long (after all, you know your needs and teams timezones better than we do), we are here to help! Once your team is signed up, please register[3]! And remind your team to register! Registration is free, but it's important that you sign up to let us know you'll be attending because that's how you'll receive event details, passwords, and other relevant information about the PTG. Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/april2022_vptg_survey [2] Ethercalc Signup: https://ethercalc.openstack.org/7yxdas7suqnd [3] PTG Registration: https://openinfra-ptg.eventbrite.com/

1 0

[cinder][drivers] third-party CI compliance check
by Brian Rosmaita 03 Feb '22

03 Feb '22

Hello Argonauts, particularly vendor driver maintainers, This is a reminder that the third-party CI compliance check is imminent [0]. You can prevent any unpleasantness by checking now to verify that your CI is compliant. [0] https://releases.openstack.org/yoga/schedule.html#cinder-3rd-party-ci-compl… [1] https://docs.openstack.org/cinder/latest/drivers-all-about.html#driver-comp…

1 0

[cinder] new driver freeze & exceptions
by Brian Rosmaita 03 Feb '22

03 Feb '22

Hello Argonauts, The new driver merge deadline passed at 20:00 UTC today. I'm extending the new driver merge deadline to Friday 28 January at 20:00 UTC for two drivers: 1. Lightbits: It has both a cinder and os-brick patch, and I want the team to have more time to look at the os-brick patch. I think the driver patch is close to ready; the developers have been quick to respond to comments and make revisions. Also, the third-party CI is functioning and responding on patches. cinder: https://review.opendev.org/c/openstack/cinder/+/821602 os-brick: https://review.opendev.org/c/openstack/os-brick/+/821603 2. NEC Storage V Series: the driver patch has one +2 and the third party CI is functioning and responding on patches; I don't see any reason to make this one wait for the Z release. https://review.opendev.org/c/openstack/cinder/+/815614 Cinder core reviewers: please continue to review the above patches. With respect to the other proposed drivers: - Pure Storage NVMe-RoCE: vendor decided to hold it for Z - Dell EMC PowerStore NFS driver: vendor decided to hold it for Z - HPE XP Storage FC & iSCSI: the code is very straightforward, but the CI is not ready yet, so this will have to wait for Z - YADRO Tatlin.UNIFIED driver: initial patch arrived yesterday (and has a -1 from Zuul); the CI appears to be running, but the cinder team needs to move on to reviewing os-brick and Yoga feature patches, so this will have to wait for Z also cheers, brian

3 4

[neutron] Drivers meeting - Friday 4.2.2022 - cancelled
by Lajos Katona 03 Feb '22

03 Feb '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[nova][gate] test_tagged_attachment failing close to 100% in nova-next
by Artom Lifshitz 03 Feb '22

03 Feb '22

https://bugs.launchpad.net/nova/+bug/1959899 The test times out verifying the tags in the metadata API after attaching a NIC and volume. This is happening almost 100% of the time, but I've seen at least a couple of passing runs as well. We have yet to determine what the exact failure mode is - is the metadata API timing out (unlikely, since every other test passes)? Or are the expected tags just not present (more likely)? I'm trying to figure some things out at [1], but other than that this is very much under investigation with no root cause identified yet. [1] https://review.opendev.org/c/openstack/nova/+/827549

2 1

[nova][tempest] nova-next gate blocker
by Artom Lifshitz 03 Feb '22

03 Feb '22

nova-next (and possibly others) is broken because of https://bugs.launchpad.net/tempest/+bug/1959682 The fix is at https://review.opendev.org/c/openstack/tempest/+/827305, with a Nova DNM patch to exercise it at https://review.opendev.org/c/openstack/nova/+/827306 Please hold your rechecks until this is resolved. Cheers!

2 2

bypass sphinx conf.py from CLI
by Stone, Ronald 03 Feb '22

03 Feb '22

Hi, The StarlingX docs team is implementing the default sphinxcontrib.spelling spelling extension for use from tox via a virtualenv set up for this purpose. We do not want sphinxcontrib.spelling loaded into other tox jobs that won't use it. This means that it cannot be loaded from the standard conf.py. Instead I am bypassing conf.py and setting parameters from the sphinx-build command in the appropriate tox job: sphinx-build -a -E -C --keep-going -d doc/build/doctrees -D extensions=sphinxcontrib.spelling -D spelling_word_list_filename=spelling_wordlist.txt -D rst_prolog="open('./shared/strings.txt', 'r').read()" -t starlingx -t openstack -b spelling doc/source doc/build/spelling {posargs} This works except that we also need to load some strings into the rst prolog for various purposes, and that is failing without warning or errors. I can open the file from a python console. Sphinx-build escapes the single quotes as: open('"'"'./shared/strings.txt'"'"', '"'"'r'"'"').read()' Any suggestions on the correct parameter format appreciated. Ron

3 2

[os-brick][nova][cinder][glance] Question about lock_path
by Radosław Piliszek 03 Feb '22

03 Feb '22

Hello Fellow OpenStackers! I have noticed os-brick started using the file locks (in lock_path) to avoid race conditions. I have a question regarding that lock_path - it seems all the cases I have found use separate lock_paths per service, yet the problematic cases listed in the bug report (and the commit message of [1]) suggest that, in case of co-hosted nova-compute, glance-api, cinder-volume and cinder-backup services (or any combination thereof), the lock_path should be shared. Should the deployment projects adapt to actually fix the race condition issue? [1] https://review.opendev.org/c/openstack/os-brick/+/814139 Kind regards, -yoctozepto

4 7

[stein][neutron] Static rules losed
by Gargano Andrea 03 Feb '22

03 Feb '22

Hi all, we faced an inssue in our openstack, we have some private clouds with static rules, if the controller that own namespace with the static rule goes down, namespace moves to other controller but it loses the rule. I can still see the rules inside the router on openstack but it doesn't work until recreated. Have you seen something like this? Thank you in advance. Andrea Gargano

1 1

[all][tc] Technical Committee next weekly meeting is today (Feb 3rd) at 1500 UTC
by Radosław Piliszek 03 Feb '22

03 Feb '22

Hello OpenStackers, Below is the agenda for today's TC IRC meeting scheduled at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting == Agenda for today's TC meeting == * Roll call * Follow up on past action items * Gate health check ** Fixing Zuul config error in OpenStack *** https://etherpad.opendev.org/p/zuul-config-error-openstack * Progress check on Yoga tracker ** https://etherpad.opendev.org/p/tc-yoga-tracker * Z Release Cycle Name ** Election results: https://civs1.civs.us/cgi-bin/results.pl?id=E_693bd8bbe63ca52f ** Next step, the foundation has started the trademark checks. * Z cycle Technical Elections ** Proposed Election schedule, need to merge it if no objection. *** https://review.opendev.org/c/openstack/election/+/825017 * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -yoctozepto

1 0

[cinder][drivers] stable branch backports
by Brian Rosmaita 02 Feb '22

02 Feb '22

Hello Argonauts, especially vendor driver maintainers: At last week's midcycle meeting, we began a discussion of running third-party CI on stable branch changes. While that continues *not* to be required (it will be re-visited at the Z PTG), we did agree to the following: When a vendor driver patch backport is proposed, we would like to see a clear statement on the gerrit review that the patch has been tested in an appropriate environment. This shouldn't be a big deal because presumably you've done local testing with your backend to ensure that the code works as expected in a stable branch; we're simply asking that this be documented on the backport. cheers, brian

1 0

RE: Openstack VLAN provider Network
by DHilsbos＠performair.com 02 Feb '22

02 Feb '22

Felipe; A lot of this will depend on how you have Neutron configured. We use OpenVSwitch. For OpenVSwitch you want a completely unconfigured interface, for VLANs. If you haven't looked at Server World's tutorial for OpenStack, I would suggest you do so. They can be found here: https://www.server-world.info/en/note?os=Ubuntu_20.04&p=openstack_xena2&f=6 https://www.server-world.info/en/note?os=CentOS_Stream_8&p=openstack_xena2&… Pay particular attention to the names br-eth1 and physnet1, and where and how they are used. You are likely going to need to reference the "Configure Neutron #2" page from the tutorial to understand the whole configuration, as these assume #1 and #2 have been completed (#1 walks through how to setup the support services). The tutorials are for VXLAN, but are modifiable to be VLAN. In particular; [ml2_type_vxlan] vni_ranges = 1:1000 becomes: [ml2_type_vlan] network_vlan_ranges = physnet1:1:1000 For you, I believe that last line would be: network_vlan_ranges = physnet1:684:684 What I can't help you with is how this interacts with PackStack. Thank you, Dominic L. Hilsbos, MBA Vice President – Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com From: Felipe Mogollon [mailto:fmogollon@vicomtech.org] Sent: Wednesday, February 2, 2022 12:44 AM To: Dominic Hilsbos Subject: Re: Openstack VLAN provider Network Do you mean to remove only ip address from VLAN's eth configuration or removing all VLAN's eth configuration? Thanks Felipe On Wed, Feb 2, 2022 at 12:21 AM <DHilsbos(a)performair.com> wrote: Felipe; I had significant problems with this as well, when I was first setting up our cluster. The first thing to recognize is that the network type is from the stand point of the host (more specifically from the network services host, and the neutron compute hosts), not the network itself. Your VLAN network is actually a physical network (from the standpoint of the host), because it is bound to a physical interface. If you want to actually use it as a vlan type; a) remove the IP address(es) from the interface(s) of the network and compute host(s), and b) properly configure ml2, or an equivalent plugin. Thank you, Dominic L. Hilsbos, MBA Vice President – Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com From: Felipe Mogollon [mailto:fmogollon@vicomtech.org] Sent: Tuesday, February 1, 2022 7:49 AM To: openstack-discuss Subject: Openstack VLAN provider Network I have deployed an OpenStack Victoria using packstack in a Centos 8 Stream machine. I have 3 NIC interfaces that are configured in the following way eno1 -> VLAN 684 10.15.0.0/16 eno2 -> local network 192.168.235.0/24 eno3 -> local network 192.168.15.0/24 VLAN and local networks are working fine outside Openstack. I have deployed Openstack using packstack and local networks work fine and I can deploy instances inside openstack that get floating ips from those ranges without problem and I can ping to them. The problem is with VLAN network, I can deploy instances and I get floating ips from VLAN network range but I can't ping them. My packstack answer file is https://pastebin.com/GEqspMWu I have created VLAN network using following commands: neutron net-create vlan_network --provider:network_type vlan --provider:physical_network vlan --router:external=True --shared --provider:segmentation_id=684 neutron subnet-create --name vlan_subnet --enable_dhcp=False --allocation-pool=start=10.15.11.103,end=10.15.11.113 --gateway=10.15.11.1 vlan_network 10.15.11.0/24 Any ideas? -- Juan Felipe Mogollón Rodríguez Researcher | Investigador fmogollon(a)vicomtech.org +[34] 943 30 92 30 Digital Media member of: La información que contiene este mensaje y sus adjuntos son confidenciales y están dirigidos exclusivamente a sus destinatarios. Si recibe este mensaje por error, se ruega nos lo comunique y proceda a su borrado. The information contained in this electronic message is intended only for the personal and confidential use of the recipients designated in the original message. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.

2 1

Openstack VLAN provider Network
by Felipe Mogollon 02 Feb '22

02 Feb '22

I have deployed an OpenStack Victoria using packstack in a Centos 8 Stream machine. I have 3 NIC interfaces that are configured in the following way eno1 -> VLAN 684 10.15.0.0/16 eno2 -> local network 192.168.235.0/24 eno3 -> local network 192.168.15.0/24 VLAN and local networks are working fine outside Openstack. I have deployed Openstack using packstack and local networks work fine and I can deploy instances inside openstack that get floating ips from those ranges without problem and I can ping to them. The problem is with VLAN network, I can deploy instances and I get floating ips from VLAN network range but I can't ping them. My packstack answer file is https://pastebin.com/GEqspMWu I have created VLAN network using following commands: neutron net-create vlan_network --provider:network_type vlan --provider:physical_network vlan --router:external=True --shared --provider:segmentation_id=684 neutron subnet-create --name vlan_subnet --enable_dhcp=False --allocation-pool=start=10.15.11.103,end=10.15.11.113 --gateway=10.15.11.1 vlan_network 10.15.11.0/24 Any ideas? -- <https://www.vicomtech.org> Juan Felipe Mogollón Rodríguez Researcher | Investigador fmogollon(a)vicomtech.org +[34] 943 30 92 30 Digital Media <https://www.linkedin.com/company/vicomtech> <https://www.youtube.com/user/VICOMTech> <https://twitter.com/@Vicomtech> member of: <https://graphicsvision.ai/> La información que contiene este mensaje y sus adjuntos son confidenciales y están dirigidos exclusivamente a sus destinatarios. Si recibe este mensaje por error, se ruega nos lo comunique y proceda a su borrado. The information contained in this electronic message is intended only for the personal and confidential use of the recipients designated in the original message. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.

3 4

[TripleO] Gate blocker - opstools repo
by Ronelle Landy 02 Feb '22

02 Feb '22

Hello All, We have an issue with tripleo-ci-centos-8-content-provider <https://zuul.opendev.org/t/openstack/build/b05d7482835f4b4d83180c29b12973b0> among other tests failing in check/gate due to missing 'centos-opstools' repo. Details are in: https://bugs.launchpad.net/tripleo/+bug/1959619. There are a few patch in flight to try address this issue: https://review.rdoproject.org/r/c/rdo-infra/ansible-role-dlrn/+/38673 - Use opstools packages from trunk.rdoproject.org in cs8 https://review.opendev.org/c/openstack/tripleo-quickstart/+/827111/ - Adds temporary rdoproject repo for collectd/opstools Centos-8 Please hold rechecks until we manage to merge the fixes. Thank you!

2 3

[Diversity] Diversity and Inclusion Meeting Reminder - New Day, Time and Location
by Amy Marrich 02 Feb '22

02 Feb '22

The Diversity & Inclusion WG invites members of all OIF projects to attend our next meeting Friday February 4th, at 15:00 UTC on https://meetpad.opendev.org/osf-diversity-and-inclusion. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (apotz)

1 0

[all][infra][qa][tripleo][openstack-ansible][rally][aodh][cinder][kolla][chef][sahara] CentOS 8 EOL and removal from CI label/image lists
by Clark Boylan 01 Feb '22

01 Feb '22

As noted last month the OpenDev [0] team intends on removing CentOS 8 images from our CI system now that the release has gone EOL. A number of you have already shifted over to CentOS 8 Stream in CI (thank you!), but there is still quite a bit remaining based on codesearch and some manual digging. The OpenDev team has begun the process of removing some of the supporting infrastructure and testing as well [1]. This list is probably not comprehensive but is a start. These projects will need to look at removing their CentOS 8 CI jobs (optionally replacing them with CentOS 8 Stream jobs): * devstack (victoria and older branches) * tripleo-validations * tripleo-upgrade * openstack-ansible * rally * aodh * cinderlib * kolla-ansible * openstack-chef * sahara * tenks * validations-common * validations-lib One thing to keep in mind is that stable branches may also be affected. We'd like to do this cleanup as gracefully as possible, but reality is that some projects are unlikely to completely remove their use of CentOS 8. I think that we can give it until the end of January before we force merge updates to remove the nodeset and label from our configs. At that point any Zuul configuration still using CentOS 8 will enter an error state and correcting it will be necessary to make updates to those Zuul configs. [0] https://lists.opendev.org/pipermail/service-announce/2021-December/000029.h… [1] https://review.opendev.org/q/topic:%22remove-centos-8%22+status:open

7 8

[requirements] The version of zeroconf in upper constraints no longer supports python3.6
by William Szumski 01 Feb '22

01 Feb '22

The zeroconf package seems to have dropped support for python3.6 since 0.38.0, see: https://github.com/jstasiak/python-zeroconf#0380. We currently have 0.38.1 in upper-constraints. My understanding was that the yoga release would still support python3.6. This is important for RHEL8 based distributions that only ship python3.6. Do we need to constrain zeroconf to a version <=0.37.0?

7 6

[infra] Issue with the new pip
by Radosław Piliszek 01 Feb '22

01 Feb '22

Hi! It seems that the new pip is breaking on infra's package indices. Several jobs crash with: """ ValueError: HTML doctype missing or incorrect. Expected <!DOCTYPE html>. If you believe this error to be incorrect, try passing the command line option --use-deprecated=html5lib and please leave a comment on the pip issue at https://github.com/pypa/pip/issues/10825. [0m [31m """ Example from kolla: https://zuul.opendev.org/t/openstack/build/e1bab19dd7c1487e93afeb67284a695e Example from manila: https://zuul.opendev.org/t/openstack/build/984ed9f10f0845ceba59b573e25bbb87 -yoctozepto

4 6

[TripleO] Meeting Cancelled for February 1
by James Slagle 01 Feb '22

01 Feb '22

Hello TripleO'ers, with no items on the agenda for today's meeting, let's go ahead and cancel it. Please reach out on IRC if you need prioritized reviews. Thanks. -- -- James Slagle --

1 0

[magnum] dropping mesos code
by Mohammed Naser 01 Feb '22

01 Feb '22

Hi there, Does it make sense for us to drop the Mesos driver code from the code base? I don't know of anyone that actually uses it and I believe it's likely not been tested for years. Mohammed -- Mohammed Naser VEXXHOST, Inc.

4 5

[nova][placement] Openstack only building one VM per machine in cluster, then runs out of resources
by Eugen Block 01 Feb '22

01 Feb '22

Hi all, I would like to follow up on a discussion from last year [1] since the issue is still present. In a fresh Victoria deployment we faced the same issue and my colleague tracked it down to a reoccuring issue within MariaDB [2]. Quoting from his response to a different thread [3]: ---snip--- MariaDB is version 10.6.5. When running placement API in debug mode, its log reveals a message like "Over capacity for VCPU on resource provider . Needed: 1, Used: 4118, Capacity: 768.0" but checking the entries in the placement db / allocations table shows that "4118" is the sum of all resources for the resource provided, not only for the CPU class. The problem results from errors in the DBMS handling the "outer join" with a subquery while retrieving the currently allocated resources. ---snip--- We found a workaround for this environment, but I wanted to bring some more attention to this, hoping that this will be fixed in MariaDB. Regards, Eugen [1] https://lists.openstack.org/pipermail/openstack-discuss/2021-July/023430.ht… [2] https://jira.mariadb.org/browse/MDEV-25714 [3] https://serverfault.com/questions/1064579/openstack-only-building-one-vm-pe…

2 1

[ironic] Deprecate/Remove PowerPC prep partition support?
by Julia Kreger 31 Jan '22

31 Jan '22

Greetings folks, I've been curious if anyone sees a reason to keep PowerPC PReP partition support in Ironic? A few things to consider: * This is/was to support partition images. * We generally shy away from partition images at this point. We recommend whole disk images. * PowerPC.... And I don't think many (any?) operators will be doing power deployments of Z* and beyond OpenStack once it is released. * This is not tested in CI, because Power hardware... Thoughts? Feelings? Concerns? -Julia

1 0

[all][tc] Technical Committee next weekly meeting on Feb 3rd at 1500 UTC
by Ghanshyam Mann 31 Jan '22

31 Jan '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Feb 3rd at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Feb 2nd, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 0

[job] What is the best list for posting an OpenStack job opening?
by Chris DiLorenzo 31 Jan '22

31 Jan '22

Hello, My company has an open position for an OpenStack engineer. We haven't gotten a lot of traction or the candidates we do get lack the OpenStack experience we're looking for. Is it appropriate to post here? Thanks Chris

3 2

[watcher][core] Resignation from Watcher core
by info＠dantalion.nl 31 Jan '22

31 Jan '22

Dear all, Unfortunately I have had increasingly little available free time to spent on the Watcher project over the years. Combined with loss of access to a test environment to debug an actual Watcher deployment for which it has become apparent it will not be reinstated. These combined events inhibit me from effectively making and reviewing patches. As of such I feel it is only right to resign as Watcher core reviewer. I will remove my roles from opendev and launchpad where appropriate as well as remove myself as reviewer from any pending patches. Kind regards & stay safe, Corne (Dantali0n)

1 0

[neutron] Bug Deputy Report January 24 - 30
by Nurmatov Mamatisa 31 Jan '22

31 Jan '22

Hi, I was bug deputy last week. Below is the week summary. I would like to highlight critical bug that affects CI and unassigned #1955008 '[functional] Failure of "test_floatingip_mac_bindings"' Also let me ask OVN team to help with triage OVN related bugs (end of list below). Details: Critical --------- - https://bugs.launchpad.net/neutron/+bug/1955008 - [functional] Failure of "test_floatingip_mac_bindings" - Confirmed - Unassigned! Note: Reported in December but was new occurrences - https://bugs.launchpad.net/neutron/+bug/1959196 - New Secure RBAC policies broke devstack-enforce-scope job - Confirmed - Assigned to Slawek Kaplonski High ---- - https://bugs.launchpad.net/neutron/+bug/1959028 - [OVN][Octavia] Fix the functional CI jobs - Fix Released: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826323 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959176 - neutron fullstack/functional jobs TIMED_OUT randomly - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/1959151 - Don't set HA ports down while L3 agent restart - In progress: https://review.opendev.org/c/openstack/neutron/+/826545 - Assigned to Krzysztof Tomaszewski Medium ------ - https://bugs.launchpad.net/neutron/+bug/1959125 - OVN mech driver failing to check the L2/L3 connectivity - In progress: https://review.opendev.org/c/openstack/neutron/+/826502 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959331 - Router's external gateway isn't properly updated when new subnet is added - In progress: https://review.opendev.org/c/openstack/neutron/+/826828 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959332 - With new secure RBAC external gateway ports can't be visible in the API - Confirmed - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959333 - Error 500 after request with Invalid Scope - In progress: https://review.opendev.org/c/openstack/neutron/+/826872 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959184 - [tempest] Test "test_list_policy_filter_by_name" failing - Fix released: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/826827 - Assigned to yatin - https://bugs.launchpad.net/neutron/+bug/1958964 - Fully Populated Load Balancer creation with OVN provider leaves pools as PENDING_CREATE - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826257 - Assigned to Fernando Royo Undecided --------- - https://bugs.launchpad.net/neutron/+bug/1959098 - [ovn] metadata route missing on the guest - New - Unassigned - https://bugs.launchpad.net/neutron/+bug/1958961 - [ovn-octavia-provider] lb create failing with with ValueError: invalid literal for int() with base 10: '24 2001:db8::131/64' - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826896 - Assigned to Slawek Kaplonski Thanks, Mamatisa --- Advanced Software Technology Lab Huawei, Moscow

2 1

[neutron] CI meeting 1.02.2022 cancelled
by Slawek Kaplonski 31 Jan '22

31 Jan '22

Hi, Due to overlapping internal meetings tomorrow I have to cancel this week Neutron CI meeting. Next week I will be on PTO but meeting (8.02) will be chair by ralonsoh - thx for that. I will be back on the CI meetings in two weeks - 15.02. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Re: Can neutron-fwaas project be revived?
by Heng Zhou (周恒)-浪潮数据 31 Jan '22

31 Jan '22

Hi Lajos， I understand that the process is to retire neutron-fwaas first, and then create a new project in the X namespace. If want to retire the project, do we need to wait until the stable version(Victoria) of the project is no longer maintained(Extended Maintenance estimated 2022-04-27)? 发件人: Lajos Katona [mailto:katonalala@gmail.com] 发送时间: 2022年1月18日 0:15 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com> 抄送: miguel(a)mlavalle.com; openstack-discuss(a)lists.openstack.org; Heng Zhou (周恒)-浪潮数据 <zhouhenglc(a)inspur.com> 主题: Re: Can neutron-fwaas project be revived? Hi, Neutron team discussed this question on the Drivers meeting, see the logs: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.… The agreement is to move neutron-fwaas to x/ namespace, and revive it as x/neutron-fwaas. Best regards Lajos Katona (lajoskatona) Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > ezt írta (időpont: 2022. jan. 6., Cs, 2:30): Hi，Miguel， Ok，let’s meet at January 14th. Best regards 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2022年1月6日 9:12 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, Unfortunately, this coming January 7th several members of the drivers team will be off on holiday. We won't have a quorum to discuss your proposal. I hope that January 14th works for you and your team. Best regards Miguel On Fri, Dec 24, 2021 at 10:18 AM Miguel Lavalle <miguel(a)mlavalle.com <mailto:miguel@mlavalle.com> > wrote: Hi Qin, I have added this topic to the drivers meeting agenda (see on demand agenda close to the bottom): https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Cheers On Thu, Dec 23, 2021 at 7:42 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, Thank you for your suggestion. My colleague HengZhou will submit relevant documents as soon as possible in accordance with the official neutron rules. Yes，we will attend the neutron drivers meeting on January 7th. Merry Christmas! Best wish for you! 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2021年12月24日 0:43 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, In preparation for your meeting with the drivers team, I suggest we follow as a starting point the Neutron Stadium Governance rules and processes as outlined in the official documentation: https://docs.openstack.org/neutron/latest/contributor/stadium/governance.ht…. In the past, we have re-incorporated projects to the Stadium, like for example in the case of neutron-vpnaas. This document in the Neutron specs repo summarizes how we assessed the readiness of vpnaas for the stadium: https://specs.openstack.org/openstack/neutron-specs/specs/stadium/queens/ne… (https://review.opendev.org/c/openstack/neutron-specs/+/506012) I suggest you start a similar document for fwaas in the folder for the current cycle: https://specs.openstack.org/openstack/neutron-specs/specs/yoga/index.html. As soon as you can, please push it to gerrit, so we can start reviewing it. Did I understand correctly that you will attend the drivers meeting on January 7th? Best regards Miguel On Wed, Dec 22, 2021 at 8:09 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, I am glad to hear this news. How about our discussion on January 7th, this Friday is not convenient, what do I need to prepare before the discussion, do I need to submit rfe or other descriptions? 发件人: Miguel Lavalle [mailto: <mailto:miguel@mlavalle.com> miguel(a)mlavalle.com] 发送时间: 2021年12月23日 0:20 收件人: Dazhong Qin (秦海中)-云数据中心集团 < <mailto:qinhaizhong01@inspur.com> qinhaizhong01(a)inspur.com> 抄送: <mailto:openstack-discuss@lists.openstack.org> openstack-discuss(a)lists.openstack.org 主题: Re: Can neutron-fwaas project be revived? Hi Qin, I think that in principle the community will be delighted if you and your team can reactivate the project and maintain it. Probably the best next step is for you to attend the next Neutron drivers meeting (https://wiki.openstack.org/wiki/Meetings/NeutronDrivers) so we can discuss the specifics of your proposal. This meeting takes place on Fridays at 1400 UTC over IRC in oftc.net <http://oftc.net> , channel #openstack-neutron. Due to the end of year festivities in much of Europe and America, the next meeting will take place until January 7th. Is that a good next step for you? If yes, I'll add this topic to the meeting's agenda. Best regards On Tue, Dec 21, 2021 at 10:29 AM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi： The firewall project is a necessary function when the project is delivered. The lack of firewall function after switching OVN is not acceptable to customers. We intend to maintain this project and develop the fwaas driver based on ovn. Whether the neutron-fwaas project can be reactivate? What should I do ?

5 9

[all][tc] What's happening in Technical Committee: summary 28th Jan, 21: Reading: 5 min
by Ghanshyam Mann 29 Jan '22

29 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-27-15.00.log.html * Next week's meeting is on 3rd Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 2nd Feb. 2. What we completed this week: ========================= * "FIPS compatibility and compliance" community-wide goal proposal is merged[2] * Renamed Skyline repo to openstack/ namespace[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * 3 open reviews for ongoing activities[5]. Renaming all `master` branches on all repos to `main` --------------------------------------------------------------- lourot brought this topic and we discussed if we want to do that. Key point here is how much effort it will take to do for all the existing repo in term of make it working in CI/integration testing tooling/other scripts or not. And we should do it for new repo only. All these are unknown as of now. As first step, lourot will try the project-config importing of dummy project with 'main' branch from GitHub. Based on that, we will discuss it further. Z release cycle name ------------------------- Name nomination is closed, election for proposed names are in-progress. Follow the ML thread for updates[6]. Z release cycle Technical Election --------------------------------------- Election schedule is under review [7], please review and add your feedback. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- Dan started the skip level upgrade in grenade and made its working for stable/wallaby to master[10]. TC is planning to meet and discuss the release cadence on 3rd Feb 16 UTC. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [12] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://governance.openstack.org/tc/goals/proposed/fips.html [3] https://review.opendev.org/c/openstack/governance/+/826243 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [10] https://review.opendev.org/c/openstack/grenade/+/826101 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] https://review.opendev.org/c/openstack/governance/+/798540 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0