- openstack-discuss - lists.openstack.org

[cinder]Need some help for merging the bug fixing commits
by hao wang 18 Mar '25

18 Mar '25

Hi, guys It is possible that get your help reviewing and merging those two bug-fixing commits? They have been there for a long time and have discussed for many rounds. If there are no further concerns, could we merge it in the new cycle? Thanks a lot. [1]https://review.opendev.org/c/openstack/cinder/+/740146 [2]https://review.opendev.org/c/openstack/cinder/+/734415 Regards, Hao Wang -- Best Wishes To You!

1 0

[administrivia] Recent change in moderation for new subscribers
by Jeremy Stanley 18 Mar '25

18 Mar '25

Due to a spate of spammers subscribing to openstack-discuss over the last several days in order to send off-topic messages to the list, I've altered the default behavior for posts from new subscribers. For now, if someone subscribes, their initial post to the list will be held for moderation in order for our moderators to make sure it's a legitimate post, before setting their subscription to bypass moderation for any subsequent posts they make. Note that this only affects new subscriptions as of now, anyone who has already subscribed to the list before now should see no change in how things work for them. As for the spam to the list for the past few days, I've blocked those subscribers from sending any new messages and deleted their off-topic posts from the public archive. Please let me know if you have any questions. -- Jeremy Stanley

1 0

[nova][cinder][glance] Support for rbd namespaces
by Eugen Block 18 Mar '25

18 Mar '25

Hi, I've been searching and testing for a while, but I haven't found anything helpful yet. Someone in the Ceph community brought up the question about rbd namespaces for nova, cinder and glance. It would make sense to use only one pool for those services with regards to PG numbers. Having multiple pools means to manage their pg_num individually, and scaling can be limited due to the max number of PGs per OSD. Having only one pool would make that easier. I mean, we've been using a single pool for those three services from the beginning, but without a permission segregation. Is there anything on the road map to support rbd namespaces? Or has there been something and it was decided not to go down that road? I'd appreciate any insights! Thanks! Eugen

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-2)
by Goutham Pacha Ravi 17 Mar '25

17 Mar '25

Hello Stackers, We're two weeks away from the release date for the 2025.1 ("Epoxy") coordinated release [1]. OpenStack project teams worked with the release team to make the first release candidate (RC) available for wider testing. Over the next couple of weeks, any release-critical bugs may require revised RCs. Now's a good time to review release highlights [2] that project teams have added to reflect major changes made during this release. Development focus has shifted to the next release, 2025.2 "Flamingo" [3]. Last week was eventful. The OpenInfra Foundation board unanimously approved resolutions that further its move to become a sub-foundation of the Linux Foundation [4]. For many of you who are members of the foundation, you will have an opportunity to ratify the board's decisions through a vote next month. In the past week, the OpenStack Technical Committee didn't merge any new governance updates; however, several are open for community review. === Weekly Meeting === The TC's weekly meeting in OFTC's #openstack-tc channel on 2025-03-11 was well attended [5]. We were joined by several attendees of the OpenInfra Days North America event to discuss key takeaways and gather action items for the TC. There was broad acknowledgment that many presentations and discussions at the event revolved around Running AI workloads on OpenStack and aiding the migration of enterprises that are transitioning to OpenStack from existing commercial/proprietary solutions We expressed interest in participating in working group discussions at the upcoming PTG on both these topics. Additionally, we revisited community pain points that were brainstormed at the event. Two notable issues were: - The need for an official presence on communication platforms beyond OFTC/IRC - The lack of sufficient engagement from operators on the openstack-discuss mailing list No immediate actions were taken on these issues during the meeting, but both topics generated significant discussion. We expect to gather input from the wider community during the upcoming PTG. The next OpenStack TC meeting is today, 2025-03-18, at 1800 UTC on OFTC's #openstack-tc channel. Please find the agenda on the meeting’s wiki page [6]. I hope you'll be able to join us. I'd encourage the community to bring any topics of interest to this meeting. The synchronous attention of the TC and the lively discussions that follow are a great way to demonstrate our commitment to OpenStack’s "Open Community" values. === Governance Proposals === ==== Open for Review ==== - [resolution] Extend scope of VMT to cover all project teams | https://review.opendev.org/c/openstack/governance/+/944817 - Add separate freezer-api deliverable | https://review.opendev.org/c/openstack/governance/+/944781 - Fix links to chair responsibilities in TC Guide | https://review.opendev.org/c/openstack/governance/+/944802 - Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === 2025-04-01 – 2025-04-04: KubeCon+CloudNativeCon EU: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/ 2025-04-02: OpenStack 2025.1 ("Epoxy") Release 2025-04-08: OpenInfra Board Meeting: https://board.openinfra.org/ 2025-04-07 – 2025-04-12: OpenInfra PTG === How to Contact the TC === You can reach the TC in several ways: - Email: Send an email with the [tc] tag on this mailing list. - IRC: Ping us using the tc-members keyword in the #openstack-tc IRC channel on OFTC. - Weekly Meetings: The Technical Committee meets every Tuesday at 1800 UTC [6]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] 2025.1 "Epoxy" Release Highlights: https://releases.openstack.org/epoxy/highlights.html [3] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [4] OIF Board March '25 Meeting Recap: https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/th… [5] TC Meeting IRC Log 2025-03-11: https://meetings.opendev.org/meetings/tc/2025/tc.2025-03-11-18.00.log.html [6] TC Meeting Agenda, 2025-03-18: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ovs] [neutron] Egress traffic is not reaching table 71
by yardalgedal＠gmail.com 17 Mar '25

17 Mar '25

Hi, all! We are experimenting with bluefield-2 and neutron-openvswith-agent on it and have a big problem – all our egress traffic (from stateless point of view) are not leaving the bluefield. Symptoms are the next: the baremetal to which bluefield-2 is connected successfully responds on ping, but does not return any response for TCP traffic and can not send anything from inside. We have some security group with fully allowed egress rules. +--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ | ID | IP Protocol | Ethertype | IP Range | Port Range | Direction | Remote Security Group | Remote Address Group | +--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ | 14604165-e0c1-4bce-ae21-d20bf4165fa2 | None | IPv6 | ::/0 | | ingress | None | None | | 16f3f44f-1c9a-48f1-bcd0-7ff8df0cd30a | None | IPv4 | 0.0.0.0/0 | | ingress | None | None | | c7054cde-72ce-4dc8-a4e0-361df199204e | None | IPv6 | ::/0 | | egress | None | None | | d8bc8f82-f181-443d-a0ca-67cbae78b47f | None | IPv4 | 0.0.0.0/0 | | egress | None | None | +--------------------------------------+-------------+-----------+-----------+------------+-----------+-----------------------+----------------------+ and port to which it is assigned has port_security_enabled: True (if we are disabling port security, there is no problem anymore, it is actual only for enabled port security) we have disabled DVR and VxLAN tunnel here, we have native openvswitch firewall also [agent] tunnel_types = l2_population = true arp_responder = true extensions = qos baremetal_smartnic = True [securitygroup] firewall_driver = openvswitch [ovs] bridge_mappings = br-ex:br-int datapath_type = system ovsdb_connection = tcp:127.0.0.1:6640 #local_ip = tunnel_bridge = of_inactivity_probe = 60 ovsdb_timeout = 60 when we're sending some traffic, all flows in table 71 (BASE_EGRESS_TABLE) has n_packets = 0, so they are not reaching it. in table 60 (TRANSIENT_TABLE), which should send traffic to the table 71, on flow which should do it we can see n_packets=0 as well cookie=0x6cc97f12f173f538, duration=2086.129s, table=60, n_packets=0, n_bytes=0, priority=100,in_port=pf0hpf actions=load:0x2b->NXM_NX_REG5[],load:0x1->NXM_NX_REG6[],resubmit(,71) at the same time, the counter for NORMAL flow is growing, so packets are probably going to here (not sure cookie=0x6cc97f12f173f538, duration=2126.547s, table=60, n_packets=139340, n_bytes=6817502, priority=3 actions=NORMAL on trace we can see that the packet was directly sent to port 1 instead of going via the table ovs-appctl ofproto/trace br-int 'dl_src=a0:88:c2:eb:15:4e,dl_dst=00:1c:73:00:57:ff,ip,nw_dst=DST_IP,nw_src=SRC_IP,in_port=43,nw_ttl=64,nw_proto=6,tp_dst=80' Flow: tcp,in_port=43,vlan_tci=0x0000,dl_src=a0:88:c2:eb:15:4e,dl_dst=00:1c:73:00:57:ff,nw_src=SRC_IP,nw_dst=DST_IP,nw_tos=0,nw_ecn=0,nw_ttl=64,nw_frag=no,tp_src=0,tp_dst=80,tcp_flags=0 bridge("br-int") ---------------- 0. priority 0, cookie 0x699a137a0a73d6a8 NORMAL -> forwarding to learned port bridge("br-int") ---------------- 0. in_port=5,dl_vlan=1, priority 4, cookie 0x699a137a0a73d6a8 set_field:4297->vlan_vid NORMAL -> forwarding to learned port Final flow: unchanged Megaflow: recirc_id=0,eth,ip,in_port=43,dl_src=a0:88:c2:eb:15:4e,dl_dst=00:1c:73:00:57:ff,nw_frag=no Datapath actions: push_vlan(vid=201,pcp=0),1 any ideas why it happens or any proposals for future debugging? Thank you in advance!

1 0

Controller node openstack LXC containers clashing on IP subnets
by Sarah Thompson 17 Mar '25

17 Mar '25

Hi all, I've got much further now, and am now tracking down networking issues. I'm pretty sure everything is now installing, but I'm seeing a systematic issue. My test network that I'm running the openstack instances on is 10.0.1.x -- the VMs all have fixed IP addresses, can talk to each other, etc, nothing weird going on. haproxy is installing and running, but throwing 503 errors. Digging into this, it seems that there are some issues with the network configs of at least some of the LXC containers. The one I'm seeing that's preventing Ansible from completing the infrastructure setup is the repo server container. If I attach to the container, the keepalive comes back correctly. Externally to the container, the HTTP connection is rejected. Looking into the reasons, it looks like there are 3 networks visible from inside the container: ens18: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.1.38 netmask 255.255.255.0 broadcast 10.0.1.255 inet6 fe80::216:3eff:feab:ab45 prefixlen 64 scopeid 0x20<link> ether 00:16:3e:ab:ab:45 txqueuelen 1000 (Ethernet) RX packets 96 bytes 6952 (6.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16 bytes 1236 (1.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.3.113 netmask 255.255.255.0 broadcast 10.0.3.255 inet6 fe80::216:3eff:fe45:64d6 prefixlen 64 scopeid 0x20<link> ether 00:16:3e:45:64:d6 txqueuelen 1000 (Ethernet) RX packets 351 bytes 425285 (425.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 263 bytes 19114 (19.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2939 bytes 208134 (208.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2939 bytes 208134 (208.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The 10.0.1.38 address seems to be the problem. I think this is an internally routed subnet, not the actual physical subnet (note the lack of a gateway address, and 10.0.1.38 is definitely not being allocated via the DCHP server). Looking at some other containers, I'm seeing 10.0.2.x and 10.0.3.x there, so obviously this is being allocated on the fly either by lxc or the container(s). TL;DR: The internal 10.0.1.x is clashing with the physical 10.0.1.x network, which is almost certainly why the keepalive is failing. Does anyone have any idea how to fix the configuration to use some other CIDR block for this? I'd like to avoid the extreme pain of remapping my physical network (this is a way more complicated problem than a few test nodes unfortunotely!) Thank you in advance, Sarah Thompson -- [s]

3 4

PCI alias rtx is not defined
by Felipe Mogollon 17 Mar '25

17 Mar '25

Dear all, I am suffering a problem in my OpenStack servers. I have a 3 server configuration: - controller + compute - 2 x compute nodes The controller node has an Nvidia L4 configured in vGPU mode. One of the compute nodes has another Nvidia L4 in vGPU mode. Both servers are running fine, and I can deploy instances with vGPU capabilities. The problem comes with my 2nd compute node; that node has a Nvidia RTX4000 that can only work in passthrough mode. , I am pretty sure that in past times I managed to deploy this compute node with an Nvidia RTX 4000 in passthrough mode as a compute node of another OpenStack server configuration, but nowadays I am not able to use that GPU in passthrough mode and I don't know why: - I have configured IOMMU in compute node - I have configured nova.conf with pci alias and whitelist in compute node - I have configured nova.conf with pci alias and enabled filters in controller node - I have created a flavor and set up pci_passthrough:rtx:1 to it's configuration As far as I know, those are the steps to configure a GPU passthrough in a compute node in a Openstack multi-node configuration... But when I try to deploy a new instance I am always getting a "PCI alias rtx is not defined (HTTP 400)" error. Any ideas about what could be the problem? Is there any incompatibility with vGPU and passthrough working modes? Thanks in advance. Felipe -- [image: Vicomtech] <https://www.vicomtech.org> Industry Division Juan Felipe Mogollón Rodríguez Senior Researcher Digital Media and Communications fmogollon(a)vicomtech.org +(34) 943 30 92 30 The information contained in this electronic message is intended only for the personal and confidential use of the recipients. If you have received this e-mail by mistake, please, notify us and delete it. Avoid printing this message if it is not strictly necessary.

1 0

Routed provider networks
by Alvin Starr 17 Mar '25

17 Mar '25

I have a couple of small flat networks that I am using for a POC project. I am trying to use the routed provider networks features to create a single public net. I delete the old networks and try to install the following network and it looks like it works in that I see the 2 subnets as part of the single public-net. The trouble is that I cannot create a router with an interface in the public-net. Is there anything special that I need to do to create a router on the public-net? I changed the addresses so the subnets are likely wrong. I am installing with openstack-ansible using stable/2023.2 onto Centos-Stream. # Create the parent network with first physical segment PUBNET_ID=$(openstack network create --share \ --provider-physical-network pub204 \ --provider-network-type flat \ --external \ public-net \ -f value -c id ) FIRST_SEG=$(openstack network segment list --network ${PUBNET_ID} -f value -c ID) openstack network segment set --name segment-pub204 ${FIRST_SEG} # Add second physical segment to the network openstack network segment create \ --physical-network pub203 \ --network-type flat \ --network public-net \ segment-pub203 # Create subnet for pub203 segment openstack subnet create --network public-net \ --network-segment segment-pub203 \ --ip-version 4 \ --subnet-range 1.2.50.192/28 \ --allocation-pool start=1.2.50.196,end=1.2.50.206 \ --gateway 1.2.50.193 \ --dhcp \ public-subnet203 # Create subnet for pub204 segment openstack subnet create --network public-net \ --ip-version 4 \ --network-segment segment-pub204 \ --subnet-range 1.2.48.128/29 \ --allocation-pool start=1.2.48.132,end=1.2.48.134 \ --gateway 1.2.48.129 \ --dhcp \ public-subnet204 -- Alvin Starr || land: (647)478-6285 Netvel Inc. || home: (905)513-7688 alvin(a)netvel.net ||

1 0

[openstack-ansible]Playbooks failing after upgrading lxc containers from ubuntu18 to ubuntu20 due to python version mismatch.
by Danish Khan 17 Mar '25

17 Mar '25

Dear All, We are upgrading one of our openstack cluster from ussuri to wallaby and for this we are first upgrading OS of lxc container from ubuntu to 18 to 20(hosts OS is also upgraded to 20). We are destroying LXC containers(which don't form quorum like nova,neutron,heat,cinder,horizon) of one infra node and then creating it again. The new containers are getting created with Ubuntu 20 as the host OS is 20. Playbook for cinder, nova neutron were completed successfully for new containers of ubuntu 20. But Playbook is failing for heat, placement and memcached due to python version mismatch: fatal: [host5_heat_api_container-25f90e52]: FAILED! => {"attempts": 5, "changed": false, "cmd": ["/openstack/venvs/heat-21.2.5/bin/pip3", "install", "-U", "--constraint", "/openstack/venvs/heat-21.2.5/global-constraints.txt", "--constraint", "/openstack/venvs/heat-21.2.5/constraints.txt", "--pre", "--log", "/var/log/python_venv_build.log", "cryptography", "keystonemiddleware", "openstack-heat", "osprofiler", "pymemcache", "PyMySQL", "python-ceilometerclient", "python-glanceclient", "python-heatclient", "python-keystoneclient", "python-memcached", "python-neutronclient", "python-novaclient", "python-openstackclient", "python-swiftclient", "python-troveclient", "systemd-python"], "msg": "stdout: Ignoring python-saharaclient: markers 'python_version == \"2.7\"' don't match your environment\nIgnoring python-saharaclient: markers 'python_version == \"3.6\"' don't match your environment\nIgnoring python-saharaclient: markers 'python_version == \"3.7\"' don't match your environment\nIgnoring oslo.limit: markers 'python_version == \"2.7\"' don't match your environment\nIgnoring oslo.limit: markers 'python_version == \"3.6\"' don't match your environment\nIgnoring oslo.limit: markers 'python_version == \"3.7\"' don't match your environment\nIgnoring sphinxcontrib-actdiag: markers 'python_version == \"2.7\"' don't match your environment\nIgnoring sphinxcontrib-actdiag: markers 'python_version == \"3.6\"' don't match your environment\nIgnoring sphinxcontrib-actdiag: markers 'python_version == \"3.7\"' don't match your environment\nIgnoring os-api-ref: markers 'python_version == \"2.7\"' don't match your environment\nIgnoring os-api-ref: markers 'python_version == \"3.6\"' don't match your environment\nIgnoring os-api-ref: markers 'python_version == \"3.7\"' don't match your environment\nIgnoring oslo.concurrency: markers 'python_version == \"2.7\"' don't match your environment\nIgnoring oslo.concurrency: markers 'python_version == \"3.6\"' don't match your environment\nIgnoring oslo.concurrency: markers 'python_version == \"3.7\"' don't match your environment\nIgnoring osprofiler: markers 'python_version == \"2.7\"' don't match your environment\nIgnoring osprofiler: markers 'python_version == \"3.6\"' don't match your environment\nIgnoring osprofiler: markers 'python_version == \"3.7\"' don't match your environment\nIgnoring os-resource-classes: markers 'python_version == \"2.7\"' don't match your environment\nIgnoring os-resource-classes: markers 'python_version == \"3.6\"' don't match your environment\nIgnoring os-resource-classes: markers I understand that 2.7 version is depricated but where should make changes to fix it? https://docs.openstack.org/releasenotes/python-heatclient/ussuri.html I tried updating few variable to fix python version like: /etc/ansible/roles/os_heat/defaults/main.yml #heat_venv_python_executable: "{{ openstack_venv_python_executable | default('python3') }}" updated it from python2 to python 3 Tried few more variables but that didn't work. Any idea how we can fix this version mismatch issue ? Regards, Danish

2 1

[Devstack] Trying to setup development environment on VM
by Ishan Shanware (ishanwar) 16 Mar '25

16 Mar '25

Hello Everyone, I am currently trying to setup in all-in-one development environment for OpenStack on a Debian VM. The VM has 16 GB RAM and 4 CPUs. However, I face an error while trying to run FORCE=yes ./stack.sh. I get an error that keystone does not start. This causes the entire process to fail. Requesting assistance in solving this issue. I am following the this guide: https://docs.openstack.org/devstack/latest/guides/single-machine.html PFA the error log and error message on the terminal. [Call Trace] ./stack.sh:1126:start_keystone /opt/stack/devstack/lib/keystone:549:die [ERROR] /opt/stack/devstack/lib/keystone:549 keystone did not start Error on exit World dumping... see /opt/stack/logs/worlddump-2024-11-18-150808.txt for details ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Thanks in advance, Ishan

3 5

[neutron] Bug deputy report for week 11 of 2025
by Miguel Lavalle 16 Mar '25

16 Mar '25

I was the Neutron bug deputy last week. Following is a brief summary of the reported bugs: High bugs -------------- https://bugs.launchpad.net/neutron/+bug/2101839 [fullstack] Random errors during the execution of ``wait_until_true``. Assignee Rodolfo Alonso. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/943942 https://bugs.launchpad.net/neutron/+bug/2101857 ``neutron-tempest-plugin-ovn-ubuntu-jammy`` job unstable. No owner. Jobs neutron-tempest-plugin-*-ubuntu-jammy`` were made no voting: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/944119 Medium bugs ------------------ https://bugs.launchpad.net/neutron/+bug/2101840 ovs jobs randomly failing with guest vms not getting ip from dhcp. Assignee Lajos Katona https://bugs.launchpad.net/neutron/+bug/2101998 [OVN][Placement] Deleting a configured resource provider does not remove the Placement entry. Assignee Rodolfo Alonso. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/944053 https://bugs.launchpad.net/neutron/+bug/2102083 ``SingletonDecorator`` class to allow destroying instances. Assignee Rodolfo Alonso. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/944099 https://bugs.launchpad.net/neutron/+bug/2101871 Use of revision_number for router update on 2023.2 Bobcat cause error 500. Waiting for reproducer info from submitter Low bugs ------------- https://bugs.launchpad.net/neutron/+bug/2102095 [OVN][Placement] Change the message level when a Placement exception happens. Assignee Rodolfo Alonso. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/944101 RFEs ----- https://bugs.launchpad.net/neutron/+bug/2102090 [RFE][OVN][Placement] With Neutron API WSGI module, the initial chassis configuration is not executed. https://bugs.launchpad.net/neutron/+bug/2102165 [RFE] Forbid usage of certain IP addresses in subnet pools https://bugs.launchpad.net/neutron/+bug/2102184 [RFE] Project-Specific QoS Controls for Granular Resource Management Incomplete --------------- https://bugs.launchpad.net/neutron/+bug/2102044 Nova-API problem - cannot list instances anymore

1 0

[ci][all] Migrating doc job back to ubuntu jammy
by Takashi Kajinami 16 Mar '25

16 Mar '25

Hi, I noticed that doc job in taskflow repo was broken recently. Example: https://review.opendev.org/c/openstack/taskflow/+/944495?tab=change-view-ta… Digging into the failure, it seems the failure is caused by api doc build, trying to parse a module importing asyncore, because asyncore is no longer available in Python 3.12. IIUC Doc job was recently migrated from Ubuntu Jammy to Ubuntu Noble, which means that the default python version was bumped to 3.12. We are aware of the deprecation/removal of asyncore and already deprecated the implementation in taskflow. However deprecation was merged during 2024.2 cycle so we can't remove it until 2025.2 cycle to follow SLURP policy. There might be a way to drop the asyncore-related implementations from docs to unblock the doc job, I'm not sure if that is the right approach given the fact the implementation is deprecated but is still valid in older python versions. Thus, I wonder if we can keep running doc job in Jammy for 2025.1, which still supports Ubuntu Jammy, and then migrate the job again during 2025.2 . An alternative approach is to remove the asyncore implementation during this cycle, breaking SLURP policy, but I'm not sure if this can be the preferred option. Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 4

Deploiment in 2025
by Albert Shih 16 Mar '25

16 Mar '25

Hi everyone Long time ago I deploy a openstack mostly manually, then I integrated in our deployment tool (puppet). Now I need to re-install everything. I'm searching the «best» method to do that. My deployment would be on bare-metal, I don't need/want a deployment of CEPH (I already have my ceph cluster). Just need the cinder to use the ceph. The main focus is the easy way to upgrade. I don't have a lot of hardware so I can afford to have a «test» cluster for upgrading. I'm thinking of kolla, what do you think ? I see they are now openstack-helm project, which If I understand correctly use a k8s to manage the deployment of openstack. Is that correct ? With those tools is they are any limitation about the result ? Or can I got the most the main features of openstack ? What would you recommend ? Regards. -- Albert SHIH 🦫 🐸 Observatoire de Paris France Heure locale/Local time: mer. 05 mars 2025 17:13:54 CET

8 16

[all][tc][ptl][qa] Migrating upstream CI/CD jobs to Ubuntu Noble (24.04)
by Ghanshyam Mann 14 Mar '25

14 Mar '25

Hello Everyone, As per the 2025.2 cycle testing runtime, we need to run upstream CI/CD jobs on Ubuntu Noble (24.04) [1]. For better tracking and speeding up this work, it is the community-wide goal for this cycle[2]. This is the etherpad which has the migration plan and will be used for the tracking: - https://etherpad.opendev.org/p/migrate-to-noble I have prepared the change(WIP) for base jobs migration on Noble (openstack tox jobs, devstack, and tempest) which will migrate most of the projects jobs. Tempest change[3] include dependency on openstack tox, devstack base jobs changes so testing project gate using the the tempest change will test the complete set. Refer to the etherpad for the complete migration plan/steps. * Deadline: Nov 29th 2024 (R18) is the deadline to test/fix the projects jobs and to merge the base jobs running on Noble (openstck tox, devstack, and tempest). [1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html [2] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubunt… [3] https://review.opendev.org/c/openstack/tempest/+/932156 -gmann

2 9

[release] Release countdown for week R-2
by Thierry Carrez 14 Mar '25

14 Mar '25

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the 2025.1 Epoxy deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/2025.1 branch creation for all deliverables that have not branched yet, using the latest available 2025.1 Epoxy release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2025.1 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2025.1 branch before releasing out of the stable/2025.1 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2025.2 Flamingo development, though the focus should still be on finishing up 2025.1 Epoxy until the final release. Opening up the new development cycle is also a good opportunity to teams to revise their zuul jobs and used nodesets and clean up all unnecessary ones. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2025.1 Epoxy release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2025.1 Epoxy version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: March 28th, 2025 (R-1 week) Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting canceled Friday, March 14th
by Brian Haley 13 Mar '25

13 Mar '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as there is currently nothing listed in the agenda and we should be focusing on getting last-minute changes for RC1 merged. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

weighing compute nodes by real memory available when filtering
by Jiatong Shen 13 Mar '25

13 Mar '25

Hello Experts, I would like to ask if there is an available implementation to achieve filtering or weighing compute nodes by the real memory usage. From my observation, nova filters the compute-nodes by computing the summation of all instances' flavor ram and reserved ram. But since reserved ram is only an empirical value, sometimes compute nodes could potentially use more ram. Making things even worse is the ram allocation ratio could be more than 1. So I would like to know if there is an available implementation such that when the real memory available (from procfs) is low, the compute-node could be given a smaller weight or simply filtered out. Thank you. -- Best Regards, Jiatong Shen

2 2

Building a test cluster with openstack ansible
by Sarah Thompson 13 Mar '25

13 Mar '25

Hi all, I've been experimenting with openstack through a devstack instance, but I need to start looking at a more realistic deployment architecture. I have a 5 node Proxmox cluster available, so I've created 6 VMs, one to serve as a deployment host for Ansible etc, one as a controller node, and four compute nodes. These are all currently set up with Ubuntu 22 LTS and configured with 128GB of disk, 20GB of RAM and 12 cores. I've verified that Ansible works, LXC works correctly, etc. I'm getting a failure when I'm running openstack-ansible openstack.osa.setup_infrastructure Specifically I get errors like: PLAY [Gather repo facts] ******************************************************************************************************* TASK [Gathering Facts] ********************************************************************************************************* [WARNING]: Unhandled error in Python interpreter discovery for host openstack-controller-repo-container-e44299d5: unexpected output from Python interpreter discovery fatal: [openstack-controller-repo-container-e44299d5]: FAILED! => ansible_facts: {} changed: false failed_modules: ansible.legacy.setup: ansible_facts: discovered_interpreter_python: /usr/bin/python3 failed: true module_stderr: |- lxc-attach: openstack-controller-repo-container-e44299d5: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid lxc-attach: openstack-controller-repo-container-e44299d5: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context module_stdout: '' msg: |- MODULE FAILURE See stdout/stderr for the exact error rc: 1 warnings: - Platform unknown on host openstack-controller-repo-container-e44299d5 is using the discovered Python interpreter at /usr/bin/python3, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.17/reference_appendices/interpreter… for more information. msg: |- The following modules failed to execute: ansible.legacy.setup Inspecting the openstack-controller node manually with lxc-ls, there are no containers present. (I have manually created one and tested it successfully, so it's definitely not something weird with not being able to create/run containers). Thank you in advance for your insights. :-) Sarah PS: When I have this working, next step is to put this on bare metal in a colo, assuming I can get it working.

3 8

[infra][tc][trove] Freeing the reddwarf project on PyPI
by Jeremy Stanley 12 Mar '25

12 Mar '25

I've received a request from a representative of The Computational Democracy Project (pol.is) who have a project named red-dwarf and would like to release software to PyPI under that name. For those of you who have been around long enough to remember, the Trove project was called Red Dwarf during incubation, but was renamed roughly 12 years ago owing to trademark concerns. The https://pypi.org/p/reddwarf project was reserved but no release files were uploaded to it. I don't expect our community has any reason to continue holding onto that name as I don't see that we would ever actually use it, but I'm posting this for the sake of transparency. Does anyone object to letting go of the reddwarf project on PyPI so that it can be reused by another open source community effort? -- Jeremy Stanley

2 3

[kolla] [nova] API flags ignored in Wallaby
by Albert Braden 12 Mar '25

12 Mar '25

After rebuilding our Train clusters on Wallaby we are seeing some API issues. It appears that flags that work in Train are still documented in Wallaby, but are ignored. Do we have something setup wrong, or are we encountering bugs? The first thing is the “locked” list: Train: openstack server list --all-projects --locked --os-compute-api-version 2.73 <empty list because nothing is locked> openstack server list --all-projects --unlocked --os-compute-api-version 2.73 <list of every VM in the cluster> Wallaby (locked flag is ignored): openstack server list --all-projects --locked --os-compute-api-version 2.73 <list of every VM in the cluster> openstack server list --all-projects --unlocked --os-compute-api-version 2.73 <list of every VM in the cluster> The second problem is the hypervisor list. We can’t get “long” output in Wallaby: Train: openstack hypervisor list --long | ID | Hypervisor Hostname | Hypervisor Type | Host IP | State | vCPUs Used | vCPUs | Memory MB Used | Memory MB | Wallaby (long flag is ignored): openstack hypervisor list --long | ID | Hypervisor Hostname | Hypervisor Type | Host IP | State |

6 14

[keystone] Keystone tries to get project by selecting user_id
by İzzettin Erdem 12 Mar '25

12 Mar '25

Hi, I faced to an odd issue; while migrating some servers, keystone threw an exception and migration aborted - Could not find project: 6008439893ca4d80ab933cf3b0b5fef0 When I checked, a project with this ID does not exist, but the key point is it's not a project ID, it's an ID of a user. I googled this problem but couldn't find more information except this [1] <https://bugs.launchpad.net/keystone/+bug/2062247>. PS: _ mysql logs were fine, didn't see weird queries _ keystone works fine _ openstack version kolla-ansible/train Do you have any ideas? Thanks, İzzettin

2 1

[all] Important discussion about the OpenInfra Foundation's future
by Jeremy Stanley 12 Mar '25

12 Mar '25

The OpenInfra Foundation's board of directors is considering a significant organizational change, and your feedback is critical to assist them in their decision. Please read this announcement on the foundation mailing list: https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/th… You can follow up publicly on that list with any questions or input you have for the board and staff, or in one of the public feedback conference calls mentioned there, as well as privately to Jonathan Bryce or myself if you prefer to give feedback in confidence. Thanks as always for your interest in the future of our community! -- Jeremy Stanley -- Jeremy Stanley

4 11

[ovn][neutron] ha_chassis make priority permanent
by Satish Patel 12 Mar '25

12 Mar '25

Folks, I am dealing with a very strange DHCP issue because of the priority of ha_chassis. I have the following ha_chassis group and I want os-chn-gen-comp-001 and os-chn-gen-comp-002 to always service DHCP for sriov interface. I have used following command to give them high priority $ ovn-nbctl --no-leader-only set ha_chassis 97077f76-46ae-4e15-9502-24fdb4ad0214 priority=32767 $ ovn-nbctl --no-leader-only set ha_chassis 97077f76-46ae-4e15-9502-24fdb4ad0214 priority=32767 But suddenly today something happened and all priority got reset causing small outage and cause all sriov VM started looking IP address. Solution was I have again set high priority again by hand to fix it.. How do I make priority permanently so it will never reset again. $ (ovn-nb-db)[root@os-chn-ctrl01 /]# ovn-nbctl --no-leader-only list HA_Chassis 784ec6e9-9af8-45c6-86e0-75ae7ccf9278 7fa04343-4471-4707-b5e9-23bd7f29ca6e 97077f76-46ae-4e15-9502-24fdb4ad0214 c75de7ab-b346-4aa5-886b-31b0fd12401e dd6ce2d4-9746-4429-862a-e78750bb4909 _uuid : 784ec6e9-9af8-45c6-86e0-75ae7ccf9278 chassis_name : os-chn-ctrl03 external_ids : {} priority : 32764 _uuid : 7fa04343-4471-4707-b5e9-23bd7f29ca6e chassis_name : os-chn-gen-comp-001 external_ids : {} priority : 32766 _uuid : 97077f76-46ae-4e15-9502-24fdb4ad0214 chassis_name : os-chn-gen-comp-002 external_ids : {} priority : 32767 _uuid : c75de7ab-b346-4aa5-886b-31b0fd12401e chassis_name : os-chn-ctrl01 external_ids : {} priority : 32765 _uuid : dd6ce2d4-9746-4429-862a-e78750bb4909 chassis_name : os-chn-ctrl02 external_ids : {} priority : 32763

1 1

Confidential VM and TDX support in upstream Openstack
by Ildiko Vancsa 11 Mar '25

11 Mar '25

Hi, I'm reaching out about a topic that came up in the Kata Containers / Confidential Containers communities related to a feature in Kata that is called remote hypervisor and also referred to as peer pods. Kata provides an API that allows users to implement a function to run Kata Containers pods in a remote location, which can include a different host machine or cloud environment. The Cloud API Adaptor in the Confidential Containers project is an implementation of the Kata remote hypervisor interface: https://github.com/confidential-containers/cloud-api-adaptor It recently came up to add support for OpenStack to be a cloud option to run Kata remote VMs in. In order to implement that, OpenStack would need to support the creation of Confidential VMs (CVM) along with things like TDX. I looked around and found 3rd-party implementation to add TDX support to Nova, but the repo has been archived: https://github.com/intel/secured-cloud-management-stack/blob/main/scm3.0/no… Does anyone know if the CVM support along with supporting Intel TDX or related technologies have been added to OpenStack already? Or if there's anyone in the community planning for adding these in the future? Thanks and Best Regards, Ildikó

4 4

[publiccloud-sig] Next meeting of Public Cloud SIG upcoming - March 12th at 0800 UTC
by Felix Kronlage-Dammers 11 Mar '25

11 Mar '25

Hi everyone, This upcoming Wednesday (March 12th) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG We've had a few new faces in the SIG lately which is awesome. Onboarding is easy - just come by and join the discussion :) cheers felix -- Felix Kronlage-Dammers Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

about using sriov-agent
by Jiatong Shen 11 Mar '25

11 Mar '25

Hello Experts, I am learning using SR-IOV to enable faster network access. I do not have a smartNIC so I am only talking about regular VF device passthrough. Right now, I configure Nova and use regular device passthrough flavor to create an instance. It works but since the PF device is a trunk network port, I have to configure sub interface manually in the guest. I find that I can only use neutron to configure SR-IOV VF devices (bandwidth, spoofcheck etc.). I am not trying it yet but I would like to ask if I use SR-IOV through neutron, does neutron's sriovagent will configure vlan id automatically such that I do not need to configure it inside the guest? if answer is yes, could you show me the related code? Thank you for your help. -- Best Regards, Jiatong Shen

4 8

[tempest] dynamically defined tests
by jerome.defavereau＠uclouvain.be 11 Mar '25

11 Mar '25

Hi, I'm currently trying to use tempest to run a simple series of tests on each of my hypervisors. I would like to have a separate test for each hypervisor instead of a single test for all. For that I need to dynamically define tests. I wrote a simple plugin to run the tests and then I use "sertattr" in a loop to define one "test_" method per hypervisor. The plugin is listed properly, as well as the tests, but when I run them using a regexp or the full test path I get "The test run didn't actually run any tests". I was able to run them using: "python -m unittest discover -s ./multi_hypervisor_tempest_plugin" but tempest run fails. Would anyone have wisdom to share ? Thanks !

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-3)
by Goutham Pacha Ravi 10 Mar '25

10 Mar '25

Hello Stackers, We're three weeks away from the coordinated 2025.1 "Epoxy" release [1]. The release will be published on 2025-04-02. This week, we're expecting to publish release candidates for all project deliverables that follow the "cycle-with-rc" release model [2]. In the past week, the OpenStack TC appointed project team leaders for Barbican (Mauricio Harley/mharley), Masakari (Suzhengwei/suzhengwei), and Zaqar (Hao Wang/wanghao) project teams. There's a pending appointment to the OpenStack Charms project [3] that we'll wrap up this week. The Oslo team re-nominated DPL liaisons, and the TC is going through the process of naming its chair and vice-chair for its current term. The community convened alongside Southern California Linux Expo (SCaLE) 2025 for an OpenInfra Days North America event. The event was well attended and featured close to 40 sessions spread across two days. You can watch most of the recorded proceedings as they were streamed live on both days [4][5][6]. We also celebrated OpenStack's 15th birthday with cake! If you missed this one, please check out upcoming birthday celebrations organized by different local user groups around the world [7]. === Weekly Meeting === The OpenStack Technical Committee (TC) held its weekly meeting primarily via video call [8], with action items and minutes documented in IRC [9]. The agenda covered past action items, PTL election results, leaderless projects, and a discussion on the format of TC meetings. A number of new Project Team Leads who will take charge of several OpenStack project teams next week are not core reviewers of the deliverables their teams manage. The general consensus was that a PTL does not have to be a core reviewer, as long as they collaborate effectively with the cores. PTLs should focus on driving consensus rather than making unilateral decisions—whether technical or otherwise. The TC trusts that if no one else nominates or objects, a lone PTL nominee has the support of the team. I personally believe that new and relatively new contributors can bring energy to the PTL role by being inquisitive and enthusiastic. I hope that the core team nurtures these qualities to integrate them into the fold sooner rather than later. The TC discussed why certain project teams that were deemed "leaderless" at the end of this past election consistently require appointments. We're learning from volunteers who have stepped up to lead each of these teams whether they would suggest any changes to the election process. Finally, we spent some time discussing whether the TC's monthly video meetings were useful and what the downsides were. We'll revisit this topic at the upcoming Project Teams Gathering with a wider audience. The next meeting of the OpenStack Technical Committee is today, 2025-03-11. Please find the agenda on the meeting's wiki page [10]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== Add suzhengwei as PTL for Masakari | https://review.opendev.org/c/openstack/governance/+/943226 Appoint Hao Wang as PTL for OpenStack Zaqar | https://review.opendev.org/c/openstack/governance/+/943338 Switch back Oslo to DPL model | https://review.opendev.org/c/openstack/governance/+/942793 Appoint Mauricio Harley as PTL for Barbican | https://review.opendev.org/c/openstack/governance/+/942907 Add gouthamr's nomination for 2025.2 TC chair | https://review.opendev.org/c/openstack/governance/+/943204 Add TC chair nomination folder for 2025.2 | https://review.opendev.org/c/openstack/governance/+/943203 ==== Open for Review ==== Appoint Felipe Reyes as PTL for OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/943254 Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === 2025-03-11: OpenInfra Board Meeting: https://board.openinfra.org/ 2025-04-02: OpenStack 2025.1 ("Epoxy") Release 2025-04-07 - 2025-04-12: OpenInfra PTG Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] cycle-with-rc release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] Appoint Felipe Reyes as PTL for OpenStack Charms: https://review.opendev.org/c/openstack/governance/+/943254 [4] OpenInfraDays @ SCaLE 2025, Thursday Stream 1: https://www.youtube.com/watch?v=W9OmGdtJAAE [5] OpenInfraDays @ SCaLE 2025, Thursday Stream 2: https://www.youtube.com/watch?v=prIwZshr55U [6] OpenInfraDays @ SCaLE 2025, Friday: https://www.youtube.com/watch?v=Fv0Bdw6pBlk [7] Celebrating 15 years of OpenStack: https://www.openstack.org/blog/celebrating-15-years-of-openstack/ [8] TC Meeting Video Recording, 2025-03-04: https://youtu.be/NMDrz1N6ogo [9] TC Meeting IRC Log 2025-03-04: https://meetings.opendev.org/meetings/tc/2025/tc.2025-03-04-18.00.log.html [10] TC Meeting Agenda, 2025-03-11: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

openstack ansible lxc containers
by engineer2024 10 Mar '25

10 Mar '25

Using the lxc-container-create playbook, how to. create a container with a specific name and specific release ? openstack-ansible lxc-containers-create.yml -e "container_name=testing" -e "lxc_container_distribution=ubuntu" -e "lxc_container_release=jammy" --limit 'test' is throwing an error. it is trying to attach to the 'testing' container when it does not exist in the first place. I want the playbook to create one with that name ? So, what's the workaround ? --- module_stderr": "lxc-attach: testing: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid\nlxc-attach: testing: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", ----

2 1

[telemetry] Nominate Juan Larriba to Telemetry core
by Takashi Kajinami 10 Mar '25

10 Mar '25

Hi, As some of you may know, current telemetry core team is quite small due to some cores shifting their focus recently. (As far as I see Matthius and I are the cores around the community recently). On the other hand we have seen revived interest in adding new features to telemetry services. To make sure these effort may receive appropriate feedback, I'd like to nominate Juan as a new Telemetry project core. He has been contributing the project for some time, and I've recently seen his consistent presence to review patches. In addition he volunteered to be a Telemetry PTL for the next cycle with his continued interest to keep the project active. If I don't hear any objections for one week, I'll add Juan to the group. Also, I'd like to take this chance to mention that we are really happy to see anyone who is interested in helping the project and appreciate any help to review proposed changes or maintain the project (so that we can invite them to the core group as well). Thank you, Takashi Kajinami -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 4

[neutron] bug deputy report for 2025w10
by Bence Romsics 10 Mar '25

10 Mar '25

Hi Neutron Team! Last week we had the following new bug reports: Gate failures: * https://bugs.launchpad.net/neutron/+bug/2100776 test_securitygroup(ovs-openflow) fullstack test random failure with Time out exception unassigned * https://bugs.launchpad.net/neutron/+bug/2101165 Random failure in test_established_tcp_session_after_re_attachinging_sg unassigned * https://bugs.launchpad.net/neutron/+bug/2101166 Random failure in dvr ovs grenade jobs to ping vm post upgrade unassigned * https://bugs.launchpad.net/neutron/+bug/2100806 Intermittent test_batch_notifier failure fix proposed: https://review.opendev.org/c/openstack/neutron/+/943212 High: * https://bugs.launchpad.net/neutron/+bug/2101150 User who is not owner of the SG can create/delete rules in the shared SG assigned to Slawek * https://bugs.launchpad.net/neutron/+bug/2101063 [OVN] min-bw QoS policy cannot be defined alone, exception raised fix proposed: https://review.opendev.org/c/openstack/neutron/+/943664 Medium: * https://bugs.launchpad.net/neutron/+bug/2101140 [OVN] Make LSP up/down events processing resilient to IDL disconnections fix proposed: https://review.opendev.org/c/openstack/neutron/+/943404 * https://bugs.launchpad.net/neutron/+bug/2101162 [OVN] Use HA_Chassis_Group for tunnelled gateway network LRPs WIP fix: https://review.opendev.org/c/openstack/neutron/+/938134 * https://bugs.launchpad.net/neutron/+bug/2100938 Assign HA_Chassis_Group to all LRPs for tunnelled gateway assigned to Rodolfo Eventlet removal: * https://bugs.launchpad.net/neutron/+bug/2101076 [eventlet-removal] Remove the usage of eventlet in the MacVTap agent unassigned RFEs: * https://bugs.launchpad.net/neutron/+bug/2100770 [RFE] Make alembic_migration scripts in neutron idempotent * https://bugs.launchpad.net/neutron/+bug/2073254 nova-compute optional wait for vif-plugged in ovn usecase Further triage needed: * https://bugs.launchpad.net/neutron/+bug/2101077 neutron-bgp-agent dies with debug log + json Info requested from reporter on reproduction method * https://bugs.launchpad.net/neutron/+bug/2100752 Severe Packet Loss During Live Migration Due to Premature Route Advertisement in Neutron BGP Dynamic Routing Edit Lajos promised to triage this Cheers, Bence

1 0

using compute_monitors option for nova
by Jiatong Shen 07 Mar '25

07 Mar '25

Hello Experts, I hope this email finds you well. I am researching the "compute_monitors" option for nova and would like to find out what it can do. By some googling I find that by enabling this option, the compute_nodes table will store extra metrics and reflect the vcpu usage on the compute node. My question is is it possible to also save memory usage? Besides, is this option still supported in the long term? Thank you very much for the help. -- Best Regards, Jiatong Shen https://docs.openstack.org/ocata/config-reference/compute/config-options.ht…

2 2

[dev][ptl][release] Cycle highlights reminder (2025.1/Epoxy)
by Jeremy Stanley 07 Mar '25

07 Mar '25

Just a reminder in case anyone missed it: we've officially reached the deadline for merging 2025.1/Epoxy release highlights, but if anyone has something they want to mention then now is the time to write, push and approve it! The OpenInfra marketing machine is getting ready to digest what they find at https://releases.openstack.org/epoxy/highlights.html and put together a press release and package for news outlets. They're interested in whatever you're excited to include, but especially anything related to AI, digital sovereignty, security, or VMware feature parity. Please get your remaining highlights in ASAP!!! -- Jeremy Stanley

1 0

[horizon] Propose Jan Jašek to Horizon core
by Tatiana Ovchinnikova 07 Mar '25

07 Mar '25

Hello team, As it was discussed at our weekly meeting, I would like to add Jan Jašek to the OpenStack Horizon core team. Jan has been contributing to the Horizon project since 2022, and his impact is tremendous. His improvement and maintenance of Horizon test jobs made them significantly more stable, and Jan's reviews are always fast and valuable. Thank you Jan! Regards, Tatiana

1 0

[release] Release countdown for week R-3
by Thierry Carrez 07 Mar '25

07 Mar '25

Development Focus ----------------- The Release Candidate (RC) deadline is next Friday, March 14th, 2025. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2025.1 branch will be cut. This branch will track the 2025.1 Epoxy release. Once stable/2025.1 has been created, the master branch will be ready to switch to 2025.2 Flamingo development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2025.1 Epoxy plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2025.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2025.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be Flamingo development) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2025.1 Epoxy release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 14th, 2025 (R-3 week) Final RC deadline: March 28th, 2025 (R-1 week) Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 -- Thierry Carrez (ttx)

1 0

[openstack-helm] Inquiry: OpenStack-Helm Deployment in Production Environments
by Thamanna Farhath 07 Mar '25

07 Mar '25

Hello OpenStack Community, I hope this email finds you well. I am currently exploring OpenStack-Helm for deploying OpenStack and would like to understand its adoption in live production environments. Specifically, I am interested in knowing if any cloud providers have successfully deployed and are operating OpenStack using OpenStack-Helm in production. If there are any case studies, references, or experiences shared by operators who have implemented this deployment method, I would greatly appreciate any insights or guidance. Looking forward to your valuable input. Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

4 5

SRIOV on 2024.1 caracal
by Manohar Kundapura (makundap) 07 Mar '25

07 Mar '25

Hi Everyone, I have the 2024.1 Caracal multi node setup working. Now I am trying to enable SRIOV on this setup by following the below link, https://docs.openstack.org/neutron/2024.1/admin/config-sriov.html Observing the below issue while running the “neutron-sriov-agent” service on compute node and it is restarting on every 2 seconds. Kindly let me know if I need to enable any configs specific to “neutron-sriov-agent” service. # tail -f /var/log/neutron/neutron-sriov-agent.log 2025-03-06 15:02:42.968 9311 INFO neutron.common.config [-] Logging enabled! 2025-03-06 15:02:42.969 9311 INFO neutron.common.config [-] /usr/bin/neutron-sriov-nic-agent version 24.0.0 2025-03-06 15:02:42.969 9311 DEBUG neutron.common.config [-] command line: /usr/bin/neutron-sriov-nic-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/plugins/ml2/sriov_agent.ini --log-file=/var/log/neutron/neutron-sriov-agent.log setup_logging /usr/lib/python3/dist-packages/neutron/common/config.py:123 2025-03-06 15:02:42.970 9311 DEBUG neutron.agent.common.utils [-] Std library socket module is patched by eventlet. Requesting std library socket module from eventlet. __init__ /usr/lib/python3/dist-packages/neutron/agent/common/utils.py:91 2025-03-06 15:02:42.971 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Physical Devices mappings: {'vf_inside': ['enp216s0f0'], 'vf_outside': ['enp216s0f1']} 2025-03-06 15:02:42.971 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Exclude Devices: {} 2025-03-06 15:02:42.972 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider bandwidths: {} 2025-03-06 15:02:42.972 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider inventory defaults: {'allocation_ratio': 1.0, 'min_unit': 1, 'step_size': 1, 'reserved': 0} 2025-03-06 15:02:42.972 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider hypervisors: {'enp216s0f1': 'u36c01p06-ostest-cmp2.openstack.local', 'enp216s0f0': 'u36c01p06-ostest-cmp2.openstack.local'} 2025-03-06 15:02:42.973 9311 DEBUG neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [-] Number of VFs configured on device enp216s0f0: 8 get_numvfs /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/eswitch_manager.py:134 2025-03-06 15:02:42.973 9311 DEBUG neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [-] Number of VFs configured on device enp216s0f1: 8 get_numvfs /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/eswitch_manager.py:134 2025-03-06 15:02:42.976 9311 DEBUG neutron.agent.securitygroups_rpc [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Init firewall settings (driver=noop) init_firewall /usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py:124 2025-03-06 15:02:42.976 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] RPC agent_id: nic-switch-agent.u36c01p06-ostest-cmp2 2025-03-06 15:02:42.981 9311 INFO neutron.agent.agent_extensions_manager [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Loaded agent extensions: [] 2025-03-06 15:02:43.037 9311 WARNING oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true': amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.038 9311 INFO oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] [7d2d8221-cd72-4203-b717-46c9d4fac7a9] Retrying to declare the exchange (q-agent-notifier-port-update_fanout) as non durable 2025-03-06 15:02:43.041 9311 ERROR oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Failed to declare consumer for topic 'q-agent-notifier-port-update': Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true': amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.046 9311 ERROR oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Unable to connect to AMQP server on 10.10.4.19:5671 after inf tries: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true': amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 CRITICAL neutron [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Unhandled error: oslo_messaging.exceptions.MessageDeliveryFailure: Unable to connect to AMQP server on 10.10.4.19:5671 after inf tries: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron Traceback (most recent call last): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 421, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self.queue.declare() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 605, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self._create_exchange(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 612, in _create_exchange 2025-03-06 15:02:43.047 9311 ERROR neutron self.exchange.declare(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 180, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron return (channel or self.channel).exchange_declare( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 612, in exchange_declare 2025-03-06 15:02:43.047 9311 ERROR neutron self.send_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 66, in send_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.wait(wait, returns_tuple=returns_tuple) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 86, in wait 2025-03-06 15:02:43.047 9311 ERROR neutron self.connection.drain_events(timeout=timeout) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 522, in drain_events 2025-03-06 15:02:43.047 9311 ERROR neutron while not self.blocking_read(timeout): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 528, in blocking_read 2025-03-06 15:02:43.047 9311 ERROR neutron return self.on_inbound_frame(frame) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/method_framing.py", line 53, in on_frame 2025-03-06 15:02:43.047 9311 ERROR neutron callback(channel, method_sig, buf, None) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 534, in on_inbound_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.channels[channel_id].dispatch_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 143, in dispatch_method 2025-03-06 15:02:43.047 9311 ERROR neutron listener(*args) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 281, in _on_close 2025-03-06 15:02:43.047 9311 ERROR neutron raise error_for_code( 2025-03-06 15:02:43.047 9311 ERROR neutron amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron During handling of the above exception, another exception occurred: 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron Traceback (most recent call last): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1036, in ensure 2025-03-06 15:02:43.047 9311 ERROR neutron ret, channel = autoretry_method() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/connection.py", line 524, in _ensured 2025-03-06 15:02:43.047 9311 ERROR neutron return fun(*args, **kwargs) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/connection.py", line 600, in __call__ 2025-03-06 15:02:43.047 9311 ERROR neutron return fun(*args, channel=channels[0], **kwargs), channels[0] 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1025, in execute_method 2025-03-06 15:02:43.047 9311 ERROR neutron method() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1262, in _declare_consumer 2025-03-06 15:02:43.047 9311 ERROR neutron consumer.declare(self) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 431, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self._declare_fallback(err, conn, consumer_arguments) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 396, in _declare_fallback 2025-03-06 15:02:43.047 9311 ERROR neutron self.queue.declare() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 605, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self._create_exchange(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 612, in _create_exchange 2025-03-06 15:02:43.047 9311 ERROR neutron self.exchange.declare(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 180, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron return (channel or self.channel).exchange_declare( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 612, in exchange_declare 2025-03-06 15:02:43.047 9311 ERROR neutron self.send_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 66, in send_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.wait(wait, returns_tuple=returns_tuple) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 86, in wait 2025-03-06 15:02:43.047 9311 ERROR neutron self.connection.drain_events(timeout=timeout) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 522, in drain_events 2025-03-06 15:02:43.047 9311 ERROR neutron while not self.blocking_read(timeout): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 528, in blocking_read 2025-03-06 15:02:43.047 9311 ERROR neutron return self.on_inbound_frame(frame) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/method_framing.py", line 53, in on_frame 2025-03-06 15:02:43.047 9311 ERROR neutron callback(channel, method_sig, buf, None) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 534, in on_inbound_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.channels[channel_id].dispatch_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 143, in dispatch_method 2025-03-06 15:02:43.047 9311 ERROR neutron listener(*args) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 281, in _on_close 2025-03-06 15:02:43.047 9311 ERROR neutron raise error_for_code( 2025-03-06 15:02:43.047 9311 ERROR neutron amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron During handling of the above exception, another exception occurred: 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron Traceback (most recent call last): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/bin/neutron-sriov-nic-agent", line 10, in <module> 2025-03-06 15:02:43.047 9311 ERROR neutron sys.exit(main()) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/cmd/eventlet/plugins/sriov_nic_neutron_agent.py", line 27, in main 2025-03-06 15:02:43.047 9311 ERROR neutron agent_main.main() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py", line 568, in main 2025-03-06 15:02:43.047 9311 ERROR neutron agent = SriovNicSwitchAgent(device_mappings, 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py", line 181, in __init__ 2025-03-06 15:02:43.047 9311 ERROR neutron self.connection.consume_in_threads() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/rpc.py", line 345, in consume_in_threads 2025-03-06 15:02:43.047 9311 ERROR neutron server.start() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 267, in wrapper 2025-03-06 15:02:43.047 9311 ERROR neutron states[state].run_once(lambda: fn(self, *args, **kwargs), 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 188, in run_once 2025-03-06 15:02:43.047 9311 ERROR neutron post_fn = fn() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 267, in <lambda> 2025-03-06 15:02:43.047 9311 ERROR neutron states[state].run_once(lambda: fn(self, *args, **kwargs), 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 413, in start 2025-03-06 15:02:43.047 9311 ERROR neutron self.listener = self._create_listener() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 150, in _create_listener 2025-03-06 15:02:43.047 9311 ERROR neutron return self.transport._listen(self._target, 1, None) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/transport.py", line 142, in _listen 2025-03-06 15:02:43.047 9311 ERROR neutron return self._driver.listen(target, batch_size, 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 709, in listen 2025-03-06 15:02:43.047 9311 ERROR neutron conn.declare_fanout_consumer(target.topic, listener) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1398, in declare_fanout_consumer 2025-03-06 15:02:43.047 9311 ERROR neutron self.declare_consumer(consumer) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1273, in declare_consumer 2025-03-06 15:02:43.047 9311 ERROR neutron return self.ensure(_declare_consumer, 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1058, in ensure 2025-03-06 15:02:43.047 9311 ERROR neutron raise exceptions.MessageDeliveryFailure(msg) 2025-03-06 15:02:43.047 9311 ERROR neutron oslo_messaging.exceptions.MessageDeliveryFailure: Unable to connect to AMQP server on 10.10.4.19:5671 after inf tries: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron Thanks, Manohar

3 2

[neutron] Drivers meeting canceled Friday, March 7th
by Brian Haley 06 Mar '25

06 Mar '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as discussed at this week's team meeting, since we are past feature freeze and should be focusing on getting in-flight things merged and bug fixes. Just a reminder there are still open specs that need review, list is at [0]. And just a reminder I am offline until next Tuesday. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

Assistance Required: OpenStack Helm Deployment (Version 2023.1) Compatibility Issues
by Thamanna Farhath 05 Mar '25

05 Mar '25

Hello OpenStack Community, I hope you are doing well. I am currently deploying OpenStack on top of a Kubernetes cluster using OpenStack Helm and aiming to install the 2023.1 (Antelope) version. However, I am facing difficulties in installing this specific version via Helm charts. Despite my attempts, I have not been able to successfully deploy the required OpenStack services for this release. Additionally, I am ensuring that the dependent services, such as RabbitMQ, align with the compatibility requirements of OpenStack 2023.1. As per the OpenStack documentation, RabbitMQ 3.11 is the recommended version, but I encountered issues while deploying it. Instead, I found that RabbitMQ 3.12 works without any issues. I would like to know: Is there a way to install OpenStack 2023.1 properly using Helm charts, or should I consider using a newer OpenStack version? Will using RabbitMQ 3.12 instead of 3.11 cause any potential issues with OpenStack services, or is it safe to proceed with this version? Are there any known workarounds or recommendations for deploying OpenStack 2023.1 using Helm? I would appreciate any guidance, best practices, or documentation references that could help resolve these challenges. Looking forward to your valuable insights. Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

4 6

[nova][libvirt][qemu] Internal error: process exited while connecting to monitor
by Roby G 04 Mar '25

04 Mar '25

Hello everyone, After upgrading to Antelope i´m getting following errors when creating new volume-backed instance. Volumes are stored in a ceph pool. - nova: 27.4.0 - libvirt: 8.0.0 - qemu: 6.2.0 - Operating system: Ubuntu 22.04 ``` ERROR nova.virt.libvirt.driver [instance: f8fa30f3-3dc8-43bd-bc29-8ed23b15b1f2] Failed to start libvirt guest: libvirt.libvirtError: internal error: process exited while connecting to monitor: 2025-03-04T15:15:34.416946Z qemu-system-x86_64: -blockdev {"driver":"rbd","pool":"cinder","image":"volume-6dfe3084-ef9d-4107-8b69-b0036fefbed0","server":[{"host":"1.2.3.4","port":"1234"},{"host":"1.2.3.5","port":"1234"},{"host":"1.2.3.6","port":"1234"}],"user":"cinder","auth-client-required":["cephx","none"],"key-secret":"libvirt-1-storage-auth-secret0","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}: error connecting: Permission denied libvirtd[50229]: internal error: process exited while connecting to monitor: 2025-03-04T15:15:34.416946Z qemu-system-x86_64: -blockdev {"driver":"rbd","pool":"cinder","image":"volume-6dfe3084-ef9d-4107-8b69-b0036fefbed0","server":[{"host":"1.2.3.4","port":"1234"},{"host":"1.2.3.5","port":"1234"},{"host":"1.2.3.6","port":"1234"}],"user":"cinder","auth-client-required":["cephx","none"],"key-secret":"libvirt-1-storage-auth-secret0","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}: error connecting: Permission denied libvirtd[50229]: internal error: qemu unexpectedly closed the monitor: 2025-03-04T15:15:34.416946Z qemu-system-x86_64: -blockdev {"driver":"rbd","pool":"cinder","image":"volume-6dfe3084-ef9d-4107-8b69-b0036fefbed0","server":[{"host":"1.2.3.4","port":"1234"},{"host":"1.2.3.5","port":"1234"},{"host":"1.2.3.6","port":"1234"}],"user":"cinder","auth-client-required":["cephx","none"],"key-secret":"libvirt-1-storage-auth-secret0","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}: error connecting: Permission denied os-cmt7 libvirtd[50229]: Unable to read from monitor: Connection reset by peer ``` Any fixes/tips? From The compute node accessing the ceph pool using `rbd` client, there are no permission errors. Are this errors related to qemu monitor?

1 0

PTG April 2025 Teams List
by Kendall Nelson 04 Mar '25

04 Mar '25

Hello Everyone! The list of teams participating in the upcoming virtual PTG (April 7-11, 2025) is now official! Projects + Teams - OpenInfra Foundation Teams - - OpenInfra Diversity and Inclusion Working Group - Kata Containers - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Heat - Horizon - Ironic - Keystone - Kolla - Manila - Neutron - Nova - Octavia - OpenStack-Ansible - OpenStack SDK/CLI - Sunbeam - Swift - Tacker - Watcher - Other OpenStack Teams - Eventlet Removal - i18n SIG - OpenStack for AI Working Group - OpenStack Security SIG - OpenStack Technical Committee - Public Cloud SIG - VMware Migration Working Group - StarlingX - Adjacent Open Source Communities - - OceanBase If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once it is configured for the teams that are signed up to attend the event. Etherpads for agenda planning and note taking will be automatically generated as a part of that configuration. Otherwise, please don't forget to register[2] — it's FREE! Also, it does help us with event coordination and communication, so please take a moment to register. As usual, feel free to let me know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://opendev.org/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg.openinfra.org/

1 0

[neutron] LXB Removal and OVN migration
by Ricardo Cano 04 Mar '25

04 Mar '25

Hello openstack-discuss, With the removal of the linuxbridge mechanism driver, has anyone successfully completed an in-place migrationfrom LinuxBridge to OVN? I did come across this https://www.jimmdenton.com/migrating-lxb-to-ovn/ and that looks good as a one-shoit while biting the bullet and taking a full outage. However, I was wondering if it was possible to run lxb and ovn side-by-side and cut them over, say one network at a time. This particular deployment was stood up using openstack-ansible back in the rocky days (now running antelope) and it appears that openstack ansible's default was lxb up until Zed. Any suggestions or recommendations on the best path forward? Also, will the dynamic routing agent work with ovn?

7 8

Contributing to Openstack [Looking for Mentorship]
by jb03229422＠student.ku.edu.np 04 Mar '25

04 Mar '25

Dear Mentors, I have good experience in building openstack in multiple environments bare-metal, kolla-ansible and helm project for minimal deployment to good HA clusters. Now, I'm looking to get into code level and contribute to open-infra foundation. I'm not a someone beginner to coding, I have done programming in a good amount and hold a knowledge of paradigm and principles. Here's my github: https://github.com/jamesii-b I'm looking for mentor who can guide me what to do as a Contribution.. Even deploying first openstack is overwhelming on its own, Coding is more. Please have me. Trust me, I'll have utmost respect to your time and energy and get most of it. Knowledge I have: HPC, Openstack Deployment, Network & System, Parallel Programming, Python, Rust.

2 1

[tacker] Today's weekly meeting
by Yasufumi Ogawa 03 Mar '25

03 Mar '25

Hi tacker team, I might not be able to join today's meeting due to something urgent come up. Let me join the today's discussion by adding my comment on the etherpad later. Thanks, Yasufumi

1 0

[neutron] Bug deputy report for week of February 24th
by Brian Haley 03 Mar '25

03 Mar '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/2100001 - [FT] Random errors in ``test_server.TestPluginWorker.test_start`` - https://review.opendev.org/c/openstack/neutron/+/942798 * https://bugs.launchpad.net/neutron/+bug/2100261 - [FT] Consistent errors in ``neutron-functional-with-pyroute2-master`` CI job - https://github.com/svinota/pyroute2/issues/1181 might be related - Rodolfo took ownership * https://bugs.launchpad.net/neutron/+bug/2100270 - [whitebox-neutron-tempest-plugin] Missing method ``configure_vlan_transparent`` imported from neutron-tempest-plugin - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/942776 * https://bugs.launchpad.net/neutron/+bug/2099981 - [ovn] Adding an IPv6 subnet to public network breaks all FIPs - Still trying to reproduce * https://bugs.launchpad.net/neutron/+bug/2099982 - [ovn] Removal of IPv6 subnet from the public network is not reflected in LRs - Might be related to above OVN bug 2099981 * https://bugs.launchpad.net/neutron/+bug/2100294 - [ovn] Changing gateway for IPv6 subnet updates wrong routes family - Might be related to above OVN bug 2099982 Medium ------ * https://bugs.launchpad.net/neutron/+bug/2099911 - Castellan as config source fails with "greenlet.error: cannot switch to a different thread" - https://review.opendev.org/c/openstack/neutron/+/942622 - But don't think that might be necessary with us removing eventlet * https://bugs.launchpad.net/neutron/+bug/2100505 - Neutron OVN external ports creation change HA chassis group master - FT reproducer patch confirms issue - Needs owner Low --- * https://bugs.launchpad.net/neutron/+bug/2100479 - Segments plugin: Not updating used IP addresses - https://review.opendev.org/c/openstack/neutron/+/935990 might fix? Wishlist -------- * https://bugs.launchpad.net/neutron/+bug/2099896 - [eventlet-removal] Remove the usage of eventlet in the Metadata agent - Needs owner * https://bugs.launchpad.net/neutron/+bug/2100268 - cleanup os-ken from the CLI part - Needs owner * https://bugs.launchpad.net/neutron/+bug/2100585 - [metadata] Unify metadata code - Eventlet follow-up

1 0

[manila] March 6th weekly meeting cancelled
by Carlos Silva 03 Mar '25

03 Mar '25

Hello zorillas, As a big part of our audience will not be able to join this week's weekly meeting, we are cancelling it. In case you have something to bring up, please ping on IRC. We will resume our upstream weekly meetings on March 13th. Thank you, carloss

1 0

Installation guide: service_user_token clarification
by Eugen Block 03 Mar '25

03 Mar '25

Hi *, to me it's still a bit unclear, what exactly is required to properly set up service user tokens. The Yoga release notes point to the nova configuration guide [0], which only briefly describes the concept. But looking at the latest installation guide [1], there's also only a very short section with a link to the config page. But there's no mention of a service role that has to be created. If this is the default since Yoga, shouldn't the installation guides cover the entire process, including creating all necessary roles or the [keystone_authtoken] section that should probably contain "service_token_roles = service"? I currently find it quite confusing. Thanks! Eugen [0] https://docs.openstack.org/nova/latest/admin/configuration/service-user-tok… [1] https://docs.openstack.org/nova/2024.2/install/controller-install-ubuntu.ht…

1 0

[release][PTLs] Reminder to 2025.1 Epoxy Cycle highlights
by Elõd Illés 03 Mar '25

03 Mar '25

Hi, This is a gentle reminder that this week is the week when 2025.1 Epoxy's Cycle highlights should be finalized (now that the Feature Freeze deadline has passed) so that they can be included in release marketing preparations. Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

Problems with Cinder and iSCSI
by Alexander Luedtke 02 Mar '25

02 Mar '25

Hello Everyone, I have a really strange problem with iSCSI, Cinder, Kolla setup. 1. What I want to do: I did setup with kolla 1 Controller, 4 Compute nodes and 2 storage nodes (iSCSI, Cinder, LVM). Kolla Deploying works fine, all Machines can find all others. 2. Problem: happens when I try to create an instance * Im creating an new instance what fails because the cinder volume couldn't be "mounted" on the compute node * What I checked then: o storage2 (the 2. cinder iscsi storage node) is available (by ping ) from the compute node o Port 3260 on storage2 is not reachable from compute node o so checking storage2 + the volume was created on LVM (checked with lvs) + Port 3260 is not available local too + it looks like that cinder creates an iSCSI target and deletes it after some seconds ... no reason shown (I activated debug mode in Kolla in the hope to see more but no ...) Did anyone have some similar behavior or can give me a hint where else to look ? Thanks a lot for your help ! best Alex Logfile of the storage2 node /var/log/kolla/cinder/cinder-volume.log: the following lines came 5-6 times and then nothing more. 2025-03-03 08:17:02.625 42 DEBUG cinder.volume.drivers.lvm [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Updating volume stats _update_volume_stats /var/lib/kolla/venv/lib/python3.12/site-packages/cinder/volume/drivers/lvm.py:227 2025-03-03 08:17:02.626 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C vgs --noheadings --unit=g -o name,size,free,lv_count,uuid --separator : --nosuffix cinder-volumes execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:03.057 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C vgs --noheadings --unit=g -o name,size,free,lv_count,uuid --separator : --nosuffix cinder-vo lumes" returned: 0 in 0.432s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:03.059 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly ci nder-volumes execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:03.483 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly cinder-volumes" returne d: 0 in 0.425s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:03.485 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o size,data_percent --separator : --nosuffix /dev/cinder-volumes/cinder-volumes-pool execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:03.899 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o size,data_percent --separator : --nosuffix /dev/cinder-volumes/ cinder-volumes-pool" returned: 0 in 0.414s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:03.900 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly ci nder-volumes execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:04.319 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly cinder-volumes" returne d: 0 in 0.418s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:04.320 42 DEBUG cinder.manager [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Notifying Schedulers of capabilities ... _publish_service_capabilities /var/lib/kolla/venv/lib/python3.12/site-packages/cinder/manager.py:202 2025-03-03 08:18:02.626 42 DEBUG oslo_service.periodic_task [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running periodic task VolumeManager.publish_service_capabilities run_periodic_tasks /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_service/periodic_task. py:210

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-4)
by Goutham Pacha Ravi 02 Mar '25

02 Mar '25

Hello Stackers, Last week, we passed milestone-3 of the 2025.1 "Epoxy" release cycle [1]. With this, we're at the tail end of this release cycle. Next week, we'll be tagging release candidates across the board for all project deliverables following the "cycle-with-rc" release model. By the end of this week, Project Team Leads and liaisons are expected to submit release cycle highlights, capturing important updates that operators and users can expect from each project in the Epoxy release. In the past week, election officials finalized the results of the PTL and TC elections for the next release cycle: 2025.2 "Flamingo" [2][3]. Please join me in congratulating these individuals. I'm especially excited to see a long lineup of first-time PTLs: Matt Crees (mattcrees) leading Blazar, Omer Schwartz (oschwart) leading Designate, Cyril Roelandt (croelandt) leading Glance, Artem Goncharov (gtema) leading Keystone, Dale Smith (dalees) leading Magnum, René Ribaud (uggla) leading Nova, Juan Larriba leading Telemetry, and Jiasirui leading Venus. The community is grateful to past PTLs, many of whom have mentored these new leaders. Additionally, Michal Nasiadka (mnasiadka) has joined the OpenStack TC, replacing Slawek Kaplonski (slaweq), who has served on the TC since the Zed cycle. Thank you for your service, and congratulations! I'd also like to thank Slawek and Ian Y Choi (ianychoi) for their service as the election officials. Later this week, the North American section of the OpenInfra Community will gather in Pasadena, CA, alongside SCALE 2025 [4]. I invite you to join community leaders at the OpenInfra Leadership meet-and-greet event if you're attending. Helena Spease (hspease) tells me there'll be cake to celebrate OpenStack's 15th birthday! [5] === Weekly Meeting === The OpenStack TC met on 2025-02-25 over IRC [6]. The election results were discussed, and we paid special attention to "leaderless" project teams—i.e., teams where no PTL nominations were accepted before the deadline: Oslo, Barbican, Masakari, OpenStack Charms, and Zaqar. Of these, the Oslo team decided to continue following a Distributed Project Leadership model, while the remaining teams are pending PTL appointments. The TC is in discussions with potential candidates. We also shared the TC's PTG Planning Etherpad [7] during the meeting. The TC and the community are encouraged to add topics to this etherpad. The next meeting of the OpenStack TC will be held simultaneously on video (Zoom) and IRC (#openstack-tc on OFTC) tomorrow, 2025-03-04. Please find the agenda for this meeting on the meeting wiki [8]. I hope you'll be able to join us. Remember that you can propose topics for the weekly TC meetings by editing this wiki page. Please leave your IRC nick next to the topic proposed so we can call on you during the meeting. === Governance Proposals === ==== Merged ==== Add TC/PTL results from 2025.2 election | https://review.opendev.org/c/openstack/governance/+/942507 Add Extra-ACs to the tech committee repos | https://review.opendev.org/c/openstack/governance/+/942296 ==== Open for Review ==== Appoint Mauricio Harley as PTL for Barbican | https://review.opendev.org/c/openstack/governance/+/942907 Switch back Oslo to DPL model | https://review.opendev.org/c/openstack/governance/+/942793 Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === - 2025-03-06: SCALE 2025 + OpenInfra Days NA (Link) - 2025-03-11: OpenInfra Board Meeting (Link) - 2025-04-02: OpenStack 2025.1 ("Epoxy") Release - 2025-04-07 - 2025-04-11: OpenInfra PTG === How to Contact the TC === You can reach the TC in several ways: - Email: Send an email with the tag [tc] on this mailing list. - IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. - Meetings: Join us at our weekly meeting. The Technical Committee meets every Tuesday at 1800 UTC [8]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] 2025.2 TC Election Results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] 2025.2 PTL Election Results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [4] OpenInfraDays @ SCALE 2025: https://www.socallinuxexpo.org/scale/22x/events/open-infra-days [5] Celebrating 15 years of OpenStack: https://www.openstack.org/blog/celebrating-15-years-of-openstack/ [6] TC Meeting IRC Log 2025-02-25: https://meetings.opendev.org/meetings/tc/2025/tc.2025-02-25-18.00.log.html [7] TC 2025.2 PTG Planning Etherpad: https://etherpad.opendev.org/p/apr2025-ptg-os-tc [8] TC Meeting Agenda, 2025-03-04: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0