- openstack-discuss - lists.openstack.org

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

06 Jun '25

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

1 0

[CINDER] Abandon old patches
by Harsh Ailani 06 Jun '25

06 Jun '25

Hi reviewers, Some of my team members are no longer contributors and have left the company as well. I need to abandon a few active patches which they raised earlier. How do I abandon someone else's patches? Patches to be abandoned: 871257: [SVf] Adding support of clone operation for volumegroup | https://review.opendev.org/c/openstack/cinder/+/871257 880518: [SVf] Adding support of extend operation for volumegroup | https://review.opendev.org/c/openstack/cinder/+/880518 869999: Allow Volume Migration with additional extra specs to enter driver code | https://review.opendev.org/c/openstack/cinder/+/869999 Thanks and Regards, Harsh Ailani

2 2

[Neutron][operators] LinuxBridge to OVN Outreach
by Daniel Failing 05 Jun '25

05 Jun '25

Hi all, Following on the good session we had last time discussing migrating out of LinuxBridge between operators, it was proposed to meet again in June. To find a good time slot, please respond to the following survey: https://newdle.cern.ch/newdle/TtbH8Dbv For reference, the notes from last meeting: https://etherpad.opendev.org/p/neutron-lb-ovn-migration Best, Daniel Failing CERN Cloud Infrastructure

1 1

RE: Create image error
by berndbausch＠gmail.com 05 Jun '25

05 Jun '25

Violating limits imposed by the operator should lead to a useful error message rather than an HTTP 5xx error. In any case, there should have been a message in the Glance API log. Perhaps you are using a prerelease version of OpenStack? When you get Devstack from the Git, you may want to specify the version; otherwise, you obtain software that is currently under development. For example, the following gets you the first version released this year (Epoxy): git clone https://opendev.org/openstack/devstack -b stable/2025.1 ------------------------------------------------------------------------------------------------------------------- From: BEDDA Fadhel <fadhel.bedda(a)gmail.com> Sent: Saturday, May 31, 2025 6:00 PM To: berndbausch(a)gmail.com Subject: Re: Create image error Hello, I was able to work around the problem by disabling the limits in the file: /etc/glance/glance-api.conf False instead of True Thanks Le sam. 31 mai 2025 à 09:55, <mailto:berndbausch@gmail.com> a écrit : My guess is that the image service is down. To check its status: systemctl status devstack@g-api Also check the image service log: journalctl -e -u devstack@g-api ------------------------------------------------------------------------ From: BEDDA Fadhel <mailto:fadhel.bedda@gmail.com> Sent: Saturday, May 31, 2025 3:08 PM To: mailto:openstack-discuss@lists.openstack.org Subject: Create image error Hi everyone, I installed OpenStack (DevStack). At first, I was able to create three images (Ubuntu, Debian, and Windows) in addition to the Cirros image. When I tried to add another image, everything got stuck. I couldn't add any images, and I got the infamous error 550. HttpException: 502: Server Error for url:

2 1

October 2025 PTG Dates & Registration
by Kendall Nelson 04 Jun '25

04 Jun '25

Hello Everyone! The next PTG[1] will take place October 27-31, 2025! Registration is now open[2] and free for all to attend, as per usual. Shortly, I will send along the team sign up to collect groups interested in participating. -- Kendall Nelson *Senior Upstream Developer Advocate* OpenInfra Foundation <https://openinfra.org/> [1] https://openinfra.dev/ptg/ [2] https://ptg.openinfra.org/

1 0

[neutron][ops] pre-created port remains in use after instance is deleted
by Eugen Block 04 Jun '25

04 Jun '25

Hello again, this is version Caracal, recently upgraded from Antelope. We're currently facing an issue with pre-created ports. This used to work just fine for years, now we have to delete the port, recreate it and try again. For example, we launch an instance with a pre-created port, notice that something is wrong and delete the instance. Previously, we could just launch a new instance and use the same port-id, but now we get this error: # openstack server create --image <image> --flavor 1 --port d10298ea-6dd9-40af-af7e-507f4d83a8cf test-port4 Port d10298ea-6dd9-40af-af7e-507f4d83a8cf is still in use. (HTTP 409) (Request-ID: req-e6cef8b4-d8af-4312-852b-d44ec92cf27a) I noticed that the device_id was still pointing to the previous instance, so I tried a couple of things to clear the port state, but to no avail. I tried: - openstack port set --device None d10298ea-6dd9-40af-af7e-507f4d83a8cf - openstack port set --device "" d10298ea-6dd9-40af-af7e-507f4d83a8cf and a couple of more set commands. I also don't see any option for port creation to allow reusing a pre-created port. Am I missing something? Thanks! Eugen

3 7

[Octavia] - Loadbalancer appear offline but are running
by Karl Kloppenborg 04 Jun '25

04 Jun '25

Hi Octavia Team. We’ve been recently running Octavia in our lab and despite load balancers creating and running correctly, status of them always reports offline, see attached screenshot.[cid:47E71115-B565-4330-8878-4E74F1BD57AF] Does anyone have any clues towards this? All the housekeeping and other processes seem to be working fine… Does anyone maybe have more information on how this telemetry is reported? Maybe that might send me down the correct rabbit hole. Thanks, Karl. Karl Kloppenborg Chief Technology Officer m: +61 437 239 565 resetdata.com<https://resetdata.com/> [cid:reset_69557fc2-1d63-4932-b5fd-93bd4f39ca7b.png] ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting For more information on the phasing of these requirements for business please visit; https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…<https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…> This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to contact(a)resetdata.com.au<mailto:contact@resetdata.com.au>

1 0

[neutron] Approach to a spec for OVN BGP integration (RFE 2111276)
by Frode Nordahl 04 Jun '25

04 Jun '25

Hello, Jakub, Thank you for filing the RFE for Neutron support for OVN native support for route exchange, which includes BGP. We appear to have a common goal of making use of this with OpenStack, and we have time set aside this cycle to work towards this goal. Communication through IRC and e-mail often has limited bandwidth, and I wonder if you would be interested in participating in a A/V sync on some cadence to get us off the ground with the initial spec work. We have good experience with how the core OVN A/V sync is organized and we could do something similar for this. WDYT? -- Frode Nordahl

6 9

[cinder]How do I configure Cinder to recognize free space in the data pool when using a Ceph Erasure Coded Pool?
by Yuta Kambe (Fujitsu) 03 Jun '25

03 Jun '25

Hi everyone, I'm using a Ceph Erasure Coded pool as the backend for OpenStack Cinder. I've created a replicated pool (volumes_meta) for metadata and an erasure-coded pool (volumes_data) for data, following the documentation here: https://docs.ceph.com/en/latest/rados/operations/erasure-code/ When I set rbd_pool to volumes_meta in cinder.conf, I receive an "Insufficient free virtual space" error, even though volumes_data has ample free space. This is because Cinder is calculating free space based on the metadata pool. When rbd_pool is set to volumes_data, Cinder correctly calculates free space based on the data pool. However, I then encounter an "RBD operation not supported" error during volume creation. I need Cinder to recognize the free space available in volumes_data while avoiding the "RBD operation not supported" error. I'm unsure how to configure this correctly and would appreciate any advice. The following is supplemental information. cinder.conf is: [ceph] volume_driver = cinder.volume.drivers.rbd.RBDDriver volume_backend_name = ceph rbd_pool = volumes_meta rbd_ceph_conf = /etc/ceph/ceph.conf rbd_flatten_volume_from_snapshot = false rbd_max_clone_depth = 5 rbd_store_chunk_size = 4 rados_connect_timeout = -1 rbd_user = cinder rbd_secret_uuid = <uuid> For example, if the pool usage is as follows, Cinder gets 1.6TiB as the pool free space: $ ceph df --- POOLS --- POOL ID PGS STORED OBJECTS USED %USED MAX AVAIL volumes_meta 4 32 40 KiB 24 189 KiB 0 1.6 TiB volumes_data 7 32 61 GiB 15.67k 92 GiB 2.80 2.1 TiB $ cinder get-pools --detail +-----------------------------+-----------------------------------------------------------------------------------+ | Property | Value | +-----------------------------+-----------------------------------------------------------------------------------+ | allocated_capacity_gb | 523 | | backend_state | up | | driver_version | 1.3.0 | | filter_function | None | | free_capacity_gb | 1592.07 <-★free capacity of volumes_meta | | goodness_function | None | | location_info | ceph:/etc/ceph/ceph.conf:<uuid>:cinder:volumes_meta | | max_over_subscription_ratio | 20.0 | | multiattach | True | | name | <hostname>@ceph#ceph | | qos_support | True | | replication_enabled | False | | reserved_percentage | 0 | | storage_protocol | ceph | | thin_provisioning_support | True | | timestamp | 2025-05-29T07:44:17.903149 | | total_capacity_gb | 1592.07 | | vendor_name | Open Source | | volume_backend_name | ceph | +-----------------------------+-----------------------------------------------------------------------------------+ OpenStack and Ceph versions are: $ ceph -v ceph version 17.2.8 (f817ceb7f187defb1d021d6328fa833eb8e943b3) quincy (stable) $ dnf list --installed | grep openstack-cinder openstack-cinder.noarch 1:21.3.2-1.el9s @centos-openstack-zed

4 4

[kolla] Weekly meeting 04/06/2025 cancelled
by Michał Nasiadka 03 Jun '25

03 Jun '25

Hello Koalas, Due to clashes with other meetings from my side and majority of core reviewers - I’m cancelling the meeting tomorrow. See you next week Michal

1 0