- openstack-discuss - lists.openstack.org

[neutron] Bug deputy report for week of June 2nd
by Brian Haley 10 Jun '25

10 Jun '25

Hi, I was the Neutron bug deputy last week. Below is a short summary about the reported bugs. -Brian Critical bugs ------------- * None High bugs --------- * https://bugs.launchpad.net/neutron/+bug/2112314 - [OVN] Missing call to update the 'neutron:ovn-bridge' in the OVN agent "metadata" extension - https://review.opendev.org/c/openstack/neutron/+/951512 * https://bugs.launchpad.net/neutron/+bug/2112569 - [ml2/ovn] Neutron sending network-vif-plugged event to nova on port down - https://review.opendev.org/c/openstack/neutron/+/951863 * https://bugs.launchpad.net/neutron/+bug/2112648 - [OVS Firewall] Remote-group member flows not restored after port rebind with same IP/MAC during migration to OVS - Patch included in bug - Need to reproduce Medium ------ * https://bugs.launchpad.net/neutron/+bug/2112453 - subnet create with subnet-pool and --gateway none creates gateway ip - Confirmed, needs owner * https://bugs.launchpad.net/neutron/+bug/2112492 - neutron-metadata-agent shows XXX (dead) status despite being functional in Neutron 26.0.0 - I could not confirm, asked for more info * https://bugs.launchpad.net/neutron/+bug/2112620 - [neutron-tempest-plugin] Test ``test_vlan_transparent_allowed_address_pairs`` failing - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/952177 - Is more work necessary? Low --- * None Wishlist -------- * https://bugs.launchpad.net/neutron/+bug/2112313 - [OVN] Deprecate OVN metadata agent in favor of OVN agent (with metadata extension) - Rodolfo took ownership * https://bugs.launchpad.net/neutron/+bug/2112446 - [RFE] Internal DNS resolution with OVS Agent - Will add to future driver's agenda

1 0

[CINDER] Dependent reviews need to be merged
by Harsh Ailani 10 Jun '25

10 Jun '25

Hello core reviewers, The following reviews are very important in the upcoming cinder release for IBM SVf Cinder Driver : 925450: [IBM SVf driver] Adding support for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/925450 926844: [IBM SVf Driver] Added support for volumegroup-snapshot for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/926844 916722: [IBM SVf Driver] Added support for restorefromsnapshot CLI for volumegroups | https://review.opendev.org/c/openstack/cinder/+/916722 938771: [IBM SVf Driver] Added support of clone operation for volumegroup | https://review.opendev.org/c/openstack/cinder/+/938771 929906: Doc: Documentation updates for ibm-svf-volumegroup feature. | https://review.opendev.org/c/openstack/cinder/+/929906 They are dependent on each other and our upcoming features are all dependent on these reviews. Zuul has passed on these and our internal customer reviews are also completed. Requesting you to please review them and help us merge them in the upcoming release. Thanks and Regards, Harsh

2 1

October 2025 PTG Team Signup Kickoff
by Kendall Nelson 09 Jun '25

09 Jun '25

Hello Everyone! The next OpenInfra PTG[1] will take place October 27-31, 2025 and registration for the event is now open[2]! To sign your team up, you must complete the survey[3] by September 14th at 19:00 UTC. If your team is not interested in participating, there is no need to fill out the survey. The contact information (email and preferably also IRC nickname) in the form will be used to share important details with moderators about team signup and further logistics. To ensure you receive all communications please double check and submit *ACCURATE* information! If you are not on IRC, please get on the OFTC network[4] and join #openinfra-events as much of the coordination for the event will be done in the #openinfra-events channel. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out to ptg(a)openinfra.org! Information about signing up for time slots will be sent to moderators after the team signup deadline. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.org/ptg/ [2] PTG Registration: http://ptg.openinfra.org/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2025_ptg_survey [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

[all] Submit Your OpenInfra Summit Talk This Week!
by Jeremy Stanley 09 Jun '25

09 Jun '25

Are you working on something exciting with OpenStack? This is your last chance to share it with the global OpenInfra community at the OpenInfra Summit Europe in Paris[0]! The CFP[1] closes this Friday, June 13, and the Summit organizers are especially looking for talks related to OpenStack. Whether you're operating production deployments, contributing upstream, or building new tools, this is the place to share your story. Sponsoring the Summit[2]? If you'd like to be part of the schedule launch marketing happening at the end of June, this Friday is also the deadline to confirm your sponsorship. Don’t miss the chance to highlight your work and connect with the global open source community. [0] My beloved French colleagues would want me to clarify that this is actually "Paris-Saclay" (but it's still very close to Paris!) [1] Sponsorship: https://summit2025.openinfra.org/sponsor [2] CFP: https://summit2025.openinfra.org/cfp -- Jeremy Stanley

1 0

[tacker] Proposal for changing IRC timeslot
by Yasufumi Ogawa 09 Jun '25

09 Jun '25

Hi tacker team, For some members joined our team recently, it's not convenient to attend the IRC meeting since they have another regular meeting at the same time. So I'd like to propose to change the meeting time from Tuesday 8:00 UTC to Monday 8:00 UTC. Let me know if you guys are not convenient, or we'll change the time from next week (16th June). Thanks, Yasufumi

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-16)
by Goutham Pacha Ravi 09 Jun '25

09 Jun '25

Hello Stackers, We're 16 weeks away from the date earmarked for the coordinated 2025.2 "Flamingo" release of OpenStack [1]. OpenStack project teams are wrapping up design specifications and gearing up to land feature changes. In the past week, the OpenInfra Foundation officially joined the Linux Foundation [2]. This is a significant move for OpenStack and other projects under the OIF. I join you in hoping that this means greater acceleration for OpenStack and broader avenues to collaborate with other open source projects under the Linux Foundation. In the same week, the OpenStack Technical Committee also passed a few important resolutions. The primary one was to adopt the "Developer Certificate of Origin" [3] for contributor sign-offs beginning July 1, 2025. What does this mean for you? This means that any new patch uploaded to the OpenStack review system (https://review.opendev.org) on or after July 1, 2025, will require a "Signed-off-by" line in the commit message. Doing so indicates that you are submitting this code in adherence to the DCO, which replaces the Contributor License Agreement that we have long required. Adding a DCO sign-off can be done by using "git commit -s" when your username and email are properly configured in your Git environment. The TC encourages PTLs, project liaisons, and all maintainers to help other contributors become familiar with this change and assist anyone who may be confused by the new requirement. If you have any questions, please join us in #openstack-dev or #openstack-tc on OFTC, or ask away on this mailing list. Alongside this significant change, the TC also clarified the actions that the Election Officials will take when there is no need for an election [4]. The next elections for Project Team Leads and a portion of the OpenStack Technical Committee will occur between Aug 27, 2025, and Sep 17, 2025. The official nomination window opens at 23:45 UTC on Aug 06, 2025. However, you're welcome to submit your nomination at any time before this date. Doing so may be helpful if you plan to be away during the nomination window. OpenDev Infrastructure Administrators have now enabled all registered users to add or edit hashtags on the code review system [5]. Some project teams have long found this useful for linking related changes—hashtags in Gerrit are more versatile than topics. I hope you'll find this helpful! === Weekly Meeting === On Jun 3, 2025, the OpenStack Technical Committee held its weekly meeting as both a video conference [6] and over IRC in OFTC's #openstack-tc channel [7]. The meeting was well attended and primarily focused on the DCO (Developer Certificate of Origin) implementation, contributor experience challenges, and other open governance proposals. A key decision was to separate translation-related concerns from the main DCO implementation. The i18n SIG has been migrating from Zanata to Weblate and will explore how the DCO can be prominently enforced via Weblate. The discussion then moved on to the findings from the maintainer and contributor surveys for the Epoxy release cycle. The survey results [8] indicated that 73% of maintainers reported difficulty getting review attention, while 68% of non-maintainer contributors faced challenges in having their reviews completed. TC members brainstormed potential reasons, and some key concerns identified include: - Inconsistent review prioritization across projects - Poor visibility into project-specific review processes - Heavy reliance on Etherpads for tracking priorities - Underutilization of review priority labels in projects that have enabled them A couple of minor action items were identified for the TC and project maintainers. Project maintainers are expected to audit their CONTRIBUTING.rst files and clearly indicate how contributors can get their changes reviewed and merged. The TC also plans to enforce more structured cross-project discussions at the October PTG. As a tangential concern, we supported the idea of hosting an ops meetup at the upcoming OpenInfra Summit in Paris-Saclay [9]. The next meeting of the OpenStack TC is today, 2025-06-09, at 17:00 UTC. This meeting will be held over IRC in the #openstack-tc channel on OFTC. Please find the agenda on the meeting's wiki page [10]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Replace CLA with DCO for all contributions | https://review.opendev.org/c/openstack/governance/+/950463 - Add nova-contrib repository | https://review.opendev.org/c/openstack/governance/+/951569 - Clarify actions when no elections are required | https://review.opendev.org/c/openstack/governance/+/949431 ==== Open for review ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-06-13: CFP Closes for the OpenInfra Summit EU: https://summit2025.openinfra.org/cfp/ - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 - 2025-07-19: OpenInfra Days Indonesia: https://2025.openinfra.id/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] OIF joins Linux Foundation: https://openinfra.org/blog/openinfra-joins-linux-foundation [3] DCO enforcement from July 1, 2025: https://governance.openstack.org/tc/resolutions/20250520-replace-the-cla-wi… [4] Election amendment: https://review.opendev.org/c/openstack/governance/+/949431 [5] Hashtags on review.opendev.org: https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/… [6] TC Meeting Video Recording, 2025-06-03: https://youtu.be/y0BwG8TadVk [7] TC Meeting IRC Log 2025-06-03: https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-03-17.00.html [8] Contributor and Maintainer Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [9] OpenInfra Summit 2025: https://summit2025.openinfra.org/ [10] TC Meeting Agenda, 2025-06-10: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 1

Api routes
by engineer2024 08 Jun '25

08 Jun '25

In openstack, is there a feature to list all the available routes for the rest api servers, instead of checking and referring the documentation? Thanks elinux

1 0

[designate] Support for quorum queues
by Thomas Goirand 06 Jun '25

06 Jun '25

Hi, When setting-up Designate with quorum queues, when designate-central starts, I get: Queue.declare: (406) PRECONDITION_FAILED - invalid property 'non-durable' for queue 'central' in vhost '/' Does Designate support quorum queues? If so, how com it's trying to set 'non-durable', which doesn't exist as attribute, at least with RabbitMQ 4.0.5? Cheers, Thomas Goirand (zigo)

6 6

[release] Release countdown for week R-16
by Thierry Carrez 06 Jun '25

06 Jun '25

Development Focus ----------------- The Flamingo-2 milestone will happen in next month, on July 3rd, 2025. 2025.2 Flamingo-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/flamingo/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/flami… You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/flamingo/schedule.html#f-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Flamingo-2 Milestone: July 3rd, 2025 -- Thierry Carrez (ttx)

1 0

Networking design for two external networks
by Andrei RADU 06 Jun '25

06 Jun '25

Hello guys, This is obviously a noob question but here goes: We want to link our openstack cloud with the rest of the network with two separate external physical routers, for redundancy. These will also be the BGP peers declared in openstack for advertising internal routes. We could do VRRP and have a shared IP between the two external routers but I understand that if we make a bgp adjacency with a VIP between the two external routers, when this will move from one router to the other in case of failure, there will be a period of outage on the BGP. So in order to avoid that, in openstack we were thinking to have two external provider network vlans, one for each external router, which will handle connectivity with the exterior. What would be the best network design to link the tenant networks to these two networks in a HA mode? Where would be best place to do the “smart” routing to direct the traffic one way or the other. Or is there a more elegant solution? Thank you and sorry if the question is too basic or too general, hopefully if someone used this design can share their experience. All the best, Andrei <a href="https://www.linkedin.com/company/the-pictet-group" target="_blank"></a> <a href="https://www.instagram.com/pictetgroup/" target="_blank"></a> <a href="https://twitter.com/PictetGroup" target="_blank"></a> This message is not intended for persons who are citizens of, domiciled or resident in, or entities registered in a country or jurisdiction in which its distribution, publication, provision or use would violate current laws and regulations. The content of this message is confidential and may be read and/or used only by the recipient of this message. For information about personal data protection, please refer to the Pictet Group’s Privacy Notice available at www.pictet.com/privacynotice. If you have received this e-mail message in error, please destroy it and delete it from your computer. The Pictet Group may not be held liable for the use, transmission or treatment of the content of this message. The recipient of this message remains solely liable for any form of reproduction, copying, disclosure, modification and/or publication of the content. No liability whatsoever will be incurred by the Pictet Group. The recipient of this message agrees to comply with the applicable laws and regulations in the jurisdictions where they use the information contained herein.<br>

1 0