April 2025 - openstack-discuss - lists.openstack.org

[kolla-ansible][rabbitmq] Change to quorum queue
by Winicius Allan 29 Apr '25

29 Apr '25

Hi community o/ I've got a little confused about the procedure[1] to change the type of queues to quorum queues. The documentation says that it is needed to stop the services that use Rabbit, but in some tasks in `genconfig` step, some APIs must be up, for example, in[2]. I think the documentation is not too clear, or I just missed something. So, I need to stop services and turn on the APIs? Will it affect the procedure of changing the queue type from classic to quorum? Another question is: when upgrading from Antelope to Caracal, is this procedure mandatory? [1] https://docs.openstack.org/kolla-ansible/latest/reference/message-queues/ra… [2] https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/octavi…

2 2

[neutron] Bug Deputy Report Apr 21 - Apr 27
by Yatin Karel 29 Apr '25

29 Apr '25

Hi Neutrinos, Below is the bug deputy report for last week:- High ==== - https://bugs.launchpad.net/neutron/+bug/2109592 - [master][periodic] oslo master jobs broken with ImportError: cannot import name 'format_inspector' from 'oslo_utils.imageutils' Unassigned - https://bugs.launchpad.net/neutron/+bug/2109591 - master periodic job running with centos 9-stream broken with py39 constraint drop https://review.opendev.org/c/openstack/requirements/+/948285 Unassigned - https://bugs.launchpad.net/neutron/+bug/2109456 - AttributeError occurs when querying ports immediately after starting neutron-server Assigned to Gwangseok Jeon - https://bugs.launchpad.net/neutron/+bug/2107925 - [ovn] neutron_pg_drop deleted when using network log Assigned to Elvira García Ruiz - https://bugs.launchpad.net/neutron/+bug/2109326 - test_release_for_ipv6_lease_no_dhcp_release6 unit tests fails randomly Assigned to Yatin Karel Medium ====== - https://bugs.launchpad.net/neutron/+bug/2109354 - Incorrect behavior when filtering networks by provider:network_type with a limit parameter Unassigned Wishlist ======== - https://bugs.launchpad.net/neutron/+bug/2108952 - [RFE][ml2][ovs] distributed DHCP extends supports for DPU baremetal Unassigned Incomplete ========= - https://bugs.launchpad.net/neutron/+bug/2108985 - [BGP DVR] Incorrect /32 Fixed IP Route Advertisement Logic Asked for more input -- Thanks and Regards Yatin Karel

1 1

[tacker] Skip next IRC meeting
by Yasufumi Ogawa 29 Apr '25

29 Apr '25

Hi team, Due to holidays in Japan this week, I would like to skip today's IRC meeting. Thanks, Yasufumi

1 0

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

28 Apr '25

Hello Stackers, We're a couple of weeks away from milestone-1 of the 2025.2 ("Flamingo") release cycle [1]. A few project teams have added team-specific deadlines to the release schedule. If you're thinking about team-specific events, please propose a change to the "openstack/releases" repository with the details, e.g., like the Nova team is doing [2]. We're looking for volunteers to serve as election officials [3] for the next combined elections for the OpenStack Technical Committee and Project Team Leads. This election will be held between August and September 2025 and will allow us to elect 2026.1's project team leads across the community, alongside 4 TC members. If you're interested, please reach out to me off-list or chime in within the #openstack-election IRC channel on OFTC. In the last week, the TC approved the deprecation of "openstack-ansible-tests". The project team has been working hard to replace all their testing with molecule-based testing that will significantly improve CI jobs. The TC is working on a resolution to amend the Vulnerability Management Team's purview [4] and will follow that up by working with project teams to ensure a streamlined security process. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was held over IRC in OFTC's #openstack-tc channel on 2025-04-22 [5]. The meeting was well attended, and we discussed several action items from the Flamingo PTG that was held earlier this month. Some of these concerned the i18n SIG. We briefly discussed how one could obtain visitor statistics that might inform how the documentation websites were being accessed from around the world. We don't publish this information on any website, and we were not keen on involving proprietary, third-party tools to track and report this data. The "goaccess" data is published in Zuul with a short retention (~6 weeks) and may yet answer some questions. A word of warning was shared that the statistics may be influenced by bots and LLM crawlers of late. You may be aware that the SIG has been migrating translation infrastructure from Zanata to Weblate. We recalled the work that happened to set up a hosted Weblate service a few years ago and took action items to follow up offline to investigate changes that are now required. Finally, we intend to follow up on discussions that didn't find room at the PTG in future weekly meetings. The next weekly meeting of the OpenStack TC is today, 2025-04-29. It will be hosted over IRC in OFTC's #openstack-tc channel. This meeting is open to any community member to propose governance discussions. Please find the agenda on the meeting's wiki page [6]. I hope you'll be able to join us! === Governance Proposals === ==== Merged ==== - Fix gmaan's email address | https://review.opendev.org/c/openstack/governance/+/948342 - Deprecate openstack-ansible-tests repo | https://review.opendev.org/c/openstack/governance/+/947622 ==== Open for Review ==== - Updating Ghanshyam email/irc name | https://review.opendev.org/c/openstack/governance/+/948354 - [resolution] Extend scope of VMT to cover all project teams | https://review.opendev.org/c/openstack/governance/+/944817 - Add openstack/grian-ui | https://review.opendev.org/c/openstack/governance/+/948252 - Retire openstack-helm-infra repo | https://review.opendev.org/c/openstack/governance/+/947611 - Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 === Upcoming Events === - 2025-04-29: StackConf https://stackconf.eu/ - 2025-04-29: SCS Hackathon / OpenStack Birthday: https://events.sovereigncloudstack.org/hackathon5-2025/ - 2025-05-13: OpenInfra Board Meeting: https://board.openinfra.org/ - 2025-05-22: OpenInfra UG Meetup, Sweden: https://www.meetup.com/openinfra-user-group-sweden/events/306139678/ 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] Add Nova deadlines to the official schedule | https://review.opendev.org/c/openstack/releases/+/948077 [3] OpenStack election officials: https://governance.openstack.org/election/#election-officials [4] Extend scope of VMT to cover all project teams: https://review.opendev.org/c/openstack/governance/+/944817 [5] TC Meeting IRC Log 2025-04-22: https://meetings.opendev.org/meetings/tc/2025/tc.2025-04-22-17.01.log.html [6] TC Meeting Agenda, 2025-04-29: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Request to Join as GSoC 2025 Mentor for OpenStack
by anjali 28 Apr '25

28 Apr '25

Hi OpenInfra GSoC Team, I’m Anjali Dhanuka, currently working as MTS at Salesforce with backend and cloud engineering experience (JavaScript, AWS, distributed systems). I am very interested in joining OpenStack as a mentor for GSoC 2025. I have prior experience building scalable cloud systems and I am passionate about helping students grow their skills through real-world backend projects. I would love to assist in proposal reviews and mentoring one or more students this summer. Please let me know the next steps or any information you need from me. Looking forward to contributing to OpenInfra’s GSoC journey! Thanks and Regards, Anjali Dhanuka

1 0

[kolla-ansible][rabbitmq] RabbitMQ cluster creation took too long
by Nguyễn Hữu Khôi 28 Apr '25

28 Apr '25

Hello. I am deploying OpenStack 2025.1 with Kolla-Ansible 2025.1 (master branch) using the latest images. However, when I created a RabbitMQ(4.0.x) cluster with 3 nodes, it took too long—around 12 minutes(it stucked at DB: virgin node -> run peer discovery). I then changed the images to RabbitMQ version 3.13.7, and it worked well. My OS: Ubuntu 24.01 Nguyen Huu Khoi

1 1

[nova] Did something change about interface detach/attach from Yoga to Caracal?
by Nell Jerram 28 Apr '25

28 Apr '25

I'm not sure why it was originally written, but I have an ancient system test that: - creates a VM attached to one network - finds the VM's port and calls interface_detach for it - checks that the VM is now unpingable - calls interface_attach with the relevant network_id - hard reboots the VM - checks that the VM is now pingable again. With Yoga, the test passes, and at the end of the test the VM has one NIC, eth0, with an IP address. With Caracal, the test also passes, but at the end of the test the VM has two NICs: - eth0 with no IP address - eth1 with an IP address. Diffing the Nova code, it looks like interface_detach and interface_attach might actually have been no-ops in Yoga - although possibly only for a "vdpa" vnic-type, and I'm unsure whether that vnic-type would be relevant to my test setup. Any ideas about this? Many thanks - Nell

2 3

[openstack-ansible] lxc-container upgrade from ubuntu 18 to ubuntu 20 for USSURI
by Danish Khan 28 Apr '25

28 Apr '25

Dear Team, I am trying to upgrade lxc-container from ubuntu 18 to ubuntu 20 and I doing it by destroying and recreating lxc-containers. I have successfully upgraded cinder, glance, heat, horizon,memcached, neutron, nova and placement containers. But now I am unable to create galera, utility containers. I am getting below error for both: failed: [host5_galera_container-ac20] (item={'url': ' http://repo.vexxhost.net/mariadb/key.gpg'}) => {"ansible_loop_var": "key", "attempts": 5, "changed": false, "key": {"url": " http://repo.vexxhost.net/mariadb/key.gpg"}, "msg": "Failed to download key at http://repo.vexxhost.net/mariadb/key.gpg: HTTP Error 404: Not Found"} And it seems the URL http://repo.vexxhost.net/mariadb/key.gpg doesn't exist now. Do we have any workaround for this? Regards, Danish

2 5

[neutron] Today's CI meeting cancelled
by Yatin Karel 28 Apr '25

28 Apr '25

Hello Neotron Team !! I will not be around today so cancelling CI meeting. Sorry for the last minute change. -- Thanks and Regards Yatin Karel

1 0

[neutron][ptg] 2025.2 Flamingo PTG summary
by Brian Haley 24 Apr '25

24 Apr '25

Hi all, Thanks for all that attended the meetings, we had a good turnout for Neutron, the Nova/Cinder cross-project and the eventlet removal discussions that were important to the team. For complete notes see the etherpad [0] but a summary is below. And please comment if you feel I missed anything. Thank you, -Brian ### Epoxy retrospective ### Like any other PTG, it started with a retrospective of the past cycle, with the highlights and improvement points. Good: - Eventlet removal is going well. Even the transition period (for the Neutron API with ML2/OVN) finished with good results. - Permanent "open doors" status to welcome newcomers. Our meetings (team meeting, drivers meeting) are a good forum for them. - Removed experimental code (Linuxbridge, IPv6 PD). - Migration from ML2/Linux Bridge to ML2/OVN discussions have started in Operators community (https://etherpad.opendev.org/p/neutron-lb-ovn-migration) Bad: - The loss of 2 important core developers. - No new specs merged in Epoxy cycle. ### Gate Stability ### Team has been very good at addressing gate issues quickly, and meets on a regular basis. We have noticed a few issues related to eventlet changes and are reverting them until we can address them. ### Spring cleanup / Code base modernization ### At the beginning of every cycle, we always try and cleanup the code base, for example, removing deprecated and dead code, doc updates, job consolidation. We have made progress on those already. - During Epoxy, several changes were made to match the expected output of pyupgrade/autopep8 for py39+. We will make a similar change in Flamingo for py310+ as that is now the lower bounds (haleyb). - It was also discussed to include "ruff" to our checklist (mlavalle). - Now that the OVN agent is in place and the default in gate, it was discussed about removing the OVN metadata agent as it is unnecessary to have both. - CI job reduction: move the ML2/OVS iptables-hybrid jobs to periodic (and experimental) and determine if iptables-hybrid driver can be moved to experimental config space. - TODOs: spend some time addressing the current TODO notes in the code, fixing what is proposed, already started. - Remove the unneeded OVN maintenance tasks, according to the comments in the methods. - Will make sure beginning/end of cycle docs are up-to-date on things like CI jobs, etc. (haleyb) ### Eventlet removal ### The "oslo.service" library will implement two backends (eventlet or threading), that will allow us to test both implementations during the removal. It could be useful to have temporary CI jobs, using both implementations. The testing CI (unit test, functional and fullstack) should start the migration during this cycle, but only once the Neutron service code is migrated. Please see [1] and [2] for more information and meetings notes from the eventlet-specific agenda. ### Migration to SDK (neutronclient removal) ### Etherpad link: https://etherpad.opendev.org/p/python-neutronclient_deprecation During the last cycle a number of Horizon patches merged (thanks Lajos!). Heat patches are still under review (and not attended). Nova patch is WIP: https://review.opendev.org/c/openstack/nova/+/928022 Neutron team will add deprecation warnings in the neutronclient code as there are still a number of places in both in and out-of tree code that is using the neutronclient. The fullstack tests will migrate to SDK during this cycle. ### Migrate the OVN L3 scheduler to use HA_Chassis_Group ### Link: https://bugs.launchpad.net/neutron/+bug/2092271 As recommended by the OVN core team, the usage of ``Gateway_Chassis`` to bind a ``Logical_Router_Port`` is deprecated. Instead of this, ``HA_Chassis_Group`` should be used. This bug tracks this effort that should be done during the next cycle. ### An OVN L3 router tool ### Link: https://bugs.launchpad.net/neutron/+bug/2103521 The goal of this tool is: - To be able to list the current GW LRP assignment, according to the ``HA_Chassis_Group``. It will show the GW chassis assignation level (according to the priority) and the number of routers per chassis. - To be able to reschedule the current assignments. In case of unbalance (chassis deletion, router deletion), this tool will allow to reschedule the GW chassis across the existing LRPs. This is something that is useful to cloud operators that currently must manually try and re-balance LRPs. Status: Approved ### Alembic idempotency ### Link: https://bugs.launchpad.net/neutron/+bug/2100770 This request comes from an issue seen in RHOSO18 with a DB migration back port. It is not possible to change the cycle milestones (last DB migrations of each cycle), thus the D/S migrations (in U/S are forbidden) are done before these milestones. The problem happens when a user, that is already in the last DB migration step, needs to re-execute the DB migration tool to receive the new back ported migration. That will fail because it is not possible to execute a DB migration script twice. This proposal includes: - Implementing a new test class that checks any new DB migration in order to ensure it works, as we found issues recently. - Enforce any new DB migration (code developers and reviewers) to be idempotent. - This would be supported on all existing migrations as well, not just from today forward. - Provide a usage guide on the alembic methods if necessary Status: Approved ### Stop DB drop migrations, with field drop exceptions ### Link: https://bugs.launchpad.net/neutron/+bug/2104160 In a DB migration, developers should add a TODO note to drop anything not used in the next SLURP release. That will prevent the case described in the bug, where a user executed the "expand" phase migration code with the old Neutron API code (as specified by the upgrade guide), resulting in an error due to a missing DB column, which was dropped by a DB migration script. The initial output of this bug is a new policy in the development guide. ### Create a restricted default policy for undefined API calls ### Link: https://bugs.launchpad.net/neutron/+bug/2098737 The goal of this RFE is to define a default restrictive rule for every non-defined policy in the Neutron API, as "oslo.policy" allows us to create a "default" policy that will be used in case the API call is not defined. The "default" Neutron policy is RULE_ADMIN_OR_OWNER, we propose to change this to RULE_ADMIN_ONLY. Any new API not defined in the policies would be executable only by the admin user. This change cannot be done now, due to the high number of missing API rules not defined that are using the default rule, see https://review.opendev.org/c/openstack/neutron/+/945687 - but this rule migration should be a background tasks for any team member that will improve the quality of the RBAC system in Neutron. Status: Approved ### Nova/Cinder cross-project ### We discussed two topics at the Nova/Cinder cross-project meeting. Project-Specific QoS Controls for Granular Resource Management. Driven by Bloomberg. Link: https://bugs.launchpad.net/neutron/+bug/2102184 Despite many questions still existing about the implementation, the Neutron team agreed to accept a spec describing it. The Neutron team agreed to have a per-project QoS policy that will affect to a non-defined set of resources (ports, networks, routers, FIPs). Bloomberg agreed to work on this later this cycle. For live-migration with OVN, Nova currently has a vif-plugged event timer to work-around any missed (or not sent) notifications. Link: https://bugs.launchpad.net/nova/+bug/2073254 The code for the multiple binding is in core OVN (23.09) and Neutron. Nova team will propose a patch to remove the condition in Nova and wait for the vif-plugged event when using the ML2/OVN backend as the condition should not happen any more. Patch link: https://review.opendev.org/c/openstack/nova/+/946950 ### Service role permissions ### The Octavia allowed address pair driver requires new service role permissions. Link: https://bugs.launchpad.net/neutron/+bug/2105502 Three patches proposed: - Add new default policy for device_id field on ports: https://review.opendev.org/c/openstack/neutron/+/861169 - Allow service role to create/update port device_id: https://review.opendev.org/c/openstack/neutron/+/947003 - Allow service role more RBAC access for Octavia: https://review.opendev.org/c/openstack/neutron/+/945329 ### L3/DHCP thread pool resizing ### Link: https://review.opendev.org/c/openstack/neutron/+/938411 This proposal is related to the eventlet removal topic. There is no direct replacement for ``eventlet.GreenPool``. The resizable mechanism does not provide a resource improvement in speed or memory and there is no kernel library that provides this functionality. The default and static maximum number of threads will be 32 (the current maximum). ### VXLAN physical networks ### Link: https://bugs.launchpad.net/neutron/+bug/2105855 The goal is to be able to schedule a VXLAN port depending on the physical mappings as the VTEP interfaces in each compute node could be connected to different physical networks. This would help improve the "networking-generic-switch" back end as it could use this new information. An alternative to this could be to implement a new type driver: l2vni, used for tunneled drivers (VXLAN) with a physical back end. A spec is required to study this proposal further. ### vlan_transparent ### Link: https://bugs.launchpad.net/neutron/+bug/2092174 Proposal to deprecate and remove the vlan_transparent config option. By default, the loaded drivers will determine if the functionality is supported or not. Status: Approved ### OVN "Add-Only" Sync Mode ### Link: https://bugs.launchpad.net/neutron/+bug/2099818 Proposal to add a new OVN sync mode option that will only add things to the OVN database and never remove from either OVN or Neutron. There were a few worries, as turning-off delete might just make things more out of sync, and not address any issues being seen in ovn-controller or ovn-northd. It was also pointed out that we did spend some time over past cycles tagging neutron-owned objects in OVN explicitly, and there might just be some additional edge cases we need to fix. This might address the issue where other objects change unexpectedly. Need to discuss further at future Drivers meeting as submitter did not attend. ### RFE discussions ### On-demand topic to discuss any in-progress or proposed RFE changes, please see etherpad for more information. [0] https://etherpad.opendev.org/p/apr2025-ptg-neutron [1] https://etherpad.opendev.org/p/neutron-eventlet-deprecation [2] https://etherpad.opendev.org/p/apr2025-ptg-eventlet

1 0