June 2025 - openstack-discuss - lists.openstack.org

[neutron] Bug deputy report for week 25 of 2025 (June 16th)
by Miguel Lavalle 23 Jun '25

23 Jun '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/2114732 grenade-skip-level-always job fails with: Security Group None cannot perform precommit_delete due to Callback. No owner https://bugs.launchpad.net/neutron/+bug/2115026 test_direct_route_for_address_scope and test_fip_connection_for_address_scope Functional test randomly fails. Assignee Yatin Karel. Proposed fix https://review.opendev.org/c/openstack/neutron/+/952958 Medium ---------- https://bugs.launchpad.net/neutron/+bug/2114819 "tag" plugin is not case sensitive. Assignee Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/952819 https://bugs.launchpad.net/neutron/+bug/2114919 dhcp_ready_on_ports() + fwaas might fail due to open transaction. Assignee Sebastian Lohff. Proposed fix https://review.opendev.org/c/openstack/neutron-fwaas/+/952852 merged https://bugs.launchpad.net/neutron/+bug/2115053 conntrack flow created for stateless SG rule. No owner Low ----- https://bugs.launchpad.net/neutron/+bug/2114832 [FT] ``test_agent_show_real_heartbeat_timestamp`` should check the timestamp in UTC timezone. Assignee Rodolfo Alonso. https://bugs.launchpad.net/neutron/+bug/2114909 [FT] Random errors in ``test_create_bridges`` . Assignee Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/952828 merged

1 0

Inquiry on Integrating Ansible with Vendor-Specific Cinder Driver Code
by Sumit Gupta 21 Jun '25

21 Jun '25

Hello Moderators, We maintain a substantial body of open-source Ansible code (certified by Red Hat as a collection) for IBM Storage Virtualize, which we believe could directly benefit the Cinder driver roadmap. I’d like to understand whether it is technically and architecturally acceptable to invoke Ansible scripts from within a vendor-specific Cinder driver. Specifically: * Are there any guidelines or constraints on integrating external automation tools (like Ansible) within a Cinder driver implementation? * Is there any official documentation on the acceptance of such cross-language or framework integrations (e.g., calling Ansible from Python)? Your guidance would be greatly appreciated to ensure any contributions align with community standards and best practices. Thank you! Sumit K Gupta sumit.gupta16(a)ibm.com Senior Storage Leader, IBM

2 1

[eventlet-removal]When to drop eventlet support
by Balazs Gibizer 19 Jun '25

19 Jun '25

Hi Stackers! I would like to sync about the planned timeline of dropping eventlet support from OpenStack / Oslo. Nova definitely needs at least the full 2026.1 cycle to have a chance to transform the nova-compute service. But this plan already feels stretched based on the progress in the current cycle. So being conservative means we need the 2026.2 cycle as a buffer. Nova would like to keep a release where we support both eventlet and threading in parallel. So that operators can do the switching from eventlet to threading outside of the upgrade procedure. (This was an explicit request from them during the PTG). So 2026.2 could be that version where nova fully supports both concurrency mode, while eventlet can be marked deprecated. Then the 2027.1 release could be the first release dropping eventlet. However we need to align with the SLURP upgrade as well. 2026.1 is a SLURP. But in that release Nova might not be ready to have all services running in threading mode. So the 2026.1 - 2027.1 SLURP upgrade would force the operators to change the concurrency mode during the upgrade itself. I see two ways forward: * A) We say that operators who want to do the concurrency mode change outside of an upgrade could not skip the 2026.2 release, i.e. they cannot do SLURP directly from 2026.1. to 2027.1. * B) We keep supporting the eventlet mode in the 2027.1 release as well and only dropping support in 2028.1. What do you think? Cheers gibi

10 22

[Cinder] SystemReader & all_tenants filter issue
by skryhin＠godaddy.com 19 Jun '25

19 Jun '25

Hey Cinder team, We're running into a problem where our SystemReader role can't use the all_tenants filter when listing Cinder volumes (e.g., via `openstack volume list --all-projects`). The filter is getting stripped at the API layer here<https://github.com/openstack/cinder/blob/stable/2024.1/cinder/volume/api.py…>. This is a blocker for auditability and integrating with third-party CMDB systems, as granting full admin access for these tools isn't a secure option. We’ve seen similar functionality handled in other services like Nova (e.g., `os_compute_api:servers:index:get_all_tenants` for SystemReader), as well as in Keystone and Neutron via policy tuning. Is there a particular reason this pattern hasn’t been implemented yet in Cinder? And would it make sense to consider making this configurable via the `volume:get_all_tenants_filter` policy rule? Appreciate any insights! Best regards, Serhii K.

1 0

The Placement API endpoint was not found
by mitku.bade＠mitm-tech.com 19 Jun '25

19 Jun '25

I was trying to setup a three node (controller, compute, and neutron)openstack environment manually using ubuntu 22.04 and the openstack caracal 2024.1 release. Every instance that I have created went into cell0 ,while I expect it to went into cell1 .Plus, the cells and the hots mapping are correctly configured and are working without error .But, I face an error which related to the Placement API endpoint. Running nova-status upgrade check returns the Placement API with Failure , while the other checks such as cellV2 are successful. Also running the nova-scheduler log returns The placement API endpoint was not found :keystoneauth1.exceptions.catalog.endpointnotfound:couldnot find the requested endpoint in service catalog. I validated the [placement],[keystone_Authtoken],[DEFAULT]],[database] settings, the endpoint,service,role of placement to be correct .It has been many days .Any one to stretch his/her support on this ?

2 2

[manila] No weekly meeting tomorrow Jun 18
by Carlos Silva 19 Jun '25

19 Jun '25

Hello, Tomorrow is a holiday for some people in the US and in Brazil, and that impacts on the attendance of the meeting, so let's cancel the meeting. Please ping me on email or in #openstack-manila in case you'd like to bring up something. Thank you, carloss

1 1

VMware Migration Guide - It’s LIVE!
by Kendall Nelson 18 Jun '25

18 Jun '25

Hello Everyone, Over the last few months, the VMware Working Group has been hard at work crafting a more in depth, detailed follow up to the initial VMware Migration Whitepaper. The goal of this follow up effort is to do a deeper dive into what migration away from VMware to OpenStack could look like, the considerations, the benefits, the key pieces that OpenStack offers to meet the needs of the workloads being migrated, etc. I am pleased to announce the VMware Migration Guide <https://www.openstack.org/vmware-migration-to-openstack/vmware-to-openstack…> ! Please feel free to share this document with the larger industry, future or present customers, and anyone else looking to learn more about what it means to migrate from VMware to OpenStack. We, the working group, really hope that this resource will provide all of the answers to common questions (and more!) about the migration process and help sustain this huge resurgence of OpenStack. Additionally, we’ll be putting together a series of Superuser posts on case studies around VMware migration. If you or your company have not already submitted one, now is the time! You can send them to kendall(a)openinfra.dev! Thank you to the VMware Working Group for all of the hard work, expertise, and knowledge shared to put together this HUGE achievement. -- Kendall Nelson *Senior Upstream Developer Advocate* The OpenInfra Foundation <https://openinfra.dev/>

1 0

[cinder] Unexpected Ceph RBD snapshot retention behavior when deleting image-based volumes
by Rocha Lobo, Vinicius 18 Jun '25

18 Jun '25

Hi, OpenStack Community. I'm part of the StarlingX Community and our starlingx-openstack distribution is currently delivering the 2024.1 (Caracal) release. We are facing an issue when using Cinder with the Ceph RBD backend: volumes created from Glance images leave behind protected snapshots and *.deleted volumes in the cinder-volumes pool after deletion, and these remnants are not being cleaned up automatically, even though I’ve enabled deferred deletion and garbage collection. So, I'm writing this email to explain our current issue and get feedback on this new Launchpad [1] I’m creating for Cinder. Environment: * OpenStack version: 2024.1 (Caracal) * Ceph version: Reef * Cinder configuration (via Helm override): conf: cinder: backend_defaults: rbd_flatten_volume_from_snapshot: True enable_deferred_deletion: True deferred_deletion_purge_interval: 10 ceph: image_volume_cache_enabled: False Issue description: 1) Create volume(s) from an image: * openstack volume create --image <image_id> --size 100 volume-test 2) Cinder creates a protected snapshot of the source image and then clones from it (as expected due to Ceph’s requirement for protected snapshots when cloning). 3) Delete the volume(s) via OpenStack CLI: * openstack volume delete volume-test After the deletion the corresponding RBD image and its snapshot are not cleaned up: * rbd -p cinder-volumes ls -l NAME SIZE PARENT FMT PROT LOCK <uuid>.deleted 100 GiB 2 <uuid>.deleted@<clone_snap>.clone_snap 1 GiB 2 yes... Even with the garbage collection features enabled (enable_deferred_deletion, rbd_flatten_volume_from_snapshot, and deferred_deletion_purge_interval), these protected snapshots and deleted volumes persist indefinitely, unless I clean them manually: * rbd snap unprotect <volume>.deleted@<snapshot> -p cinder-volumes * rbd snap rm <volume>.deleted@<snapshot> -p cinder-volumes * rbd rm <volume>.deleted -p cinder-volumes Here’s the logs that cinder pod shows while trying to delete the volume each 10 seconds: 2025-05-28 19:44:48.079 8 INFO cinder.volume.drivers.rbd [-] Purging trash for backend 'ceph-store' 2025-05-28 19:44:58.076 8 INFO cinder.volume.drivers.rbd [-] Purging trash for backend 'ceph-store' 2025-05-28 19:45:08.081 8 INFO cinder.volume.drivers.rbd [-] Purging trash for backend 'ceph-store' Questions: * Is this behavior expected in Cinder/CEPH integrations? * Shouldn't Cinder unprotect/delete the snapshot when the last volume, depending on how it is removed? Any insights or best practices would be greatly appreciated. Thanks in advance, Vinicius Lobo StarlingX contributor [1] https://bugs.launchpad.net/cinder/+bug/2114853

2 1

[all][tc][cyborg] Call for cyborg project maintainers
by Ghanshyam Maan 18 Jun '25

18 Jun '25

Hello Everyone, Cyborg project is lacking the active maintenance. The gate is broken, no response on the fix[1]. Two weeks ago, Sean raised the conern to ML[2] but there is no response from current core. We discussed it in TC meeting (last week[3] and today[4]) and as per foundation staff reachout, the next step is to call for new maintainers. If anyone using or interested to maintain it then this is right time to step up. Also, I would like existing maintainers (first of all, thanks for maintaining it till now) to give more insight about project status and their bandwidth which can help new maintainers to onboard. As per TC process to check project status, I have proposed to mark cyborg as inactive[5], feel free to provide your opinion here or in gerrit. If we do not hear back and mark project Inactive, there will be no cyborg project deliverables release in this cycle. [1] https://review.opendev.org/c/openstack/cyborg/+/949772 [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-10-17.00.log.html#… [4] https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-17-17.00.log.html#… [5] https://review.opendev.org/c/openstack/governance/+/952798 -gmaan

1 0

Nova bug report #2114855
by Vicentini Fracarolli, Joao 18 Jun '25

18 Jun '25

Hello OpenStack Community, I'm part of the StarlingX Community and our starlingx-openstack distribution is currently delivering the 2024.1 (Caracal) release. We were exploring the openstack-client "server rebuild" feature [1], and we might have found a bug. So, I'm writing this email to explain our current issue and get feedback on this new Launchpad we are creating for the Nova component https://bugs.launchpad.net/nova/+bug/2114855 [2]. It happened in the following scenario: * Create a VM with some small disk flavor and a small image. For example, using a flavor of 1 GB with the Cirros image (~ 21 MB of disk size). * Try to rebuild the VM using a new image. Example: the ubuntu-jammy qcow image. When the steps above are executed with an image with a disk size greater than the flavor size, the Nova API returns an error and the VM is not rebuilt: Flavor's disk is too small for requested image. Flavor disk is 1073741824 bytes, image is 1283063808 bytes. (HTTP 400) (Request-ID: req-7db974bb-15f3-425f-b97b-98b789b7e10f) But when we use an image with a disk size smaller than the flavor disk size, but with a virtual size bigger than the flavor disk size, Nova will try to rebuild the VM and fail: the VM state will be ERROR. It looks like the Nova API is accepting such rebuild requests, but when Nova Compute checks for virtual size, it fails. Is that expected behavior? Shouldn't the Nova API reject the request with an explicit warning telling the user to resize the VM before trying to rebuild? Thank you very much [1] https://docs.openstack.org/python-openstackclient/latest/cli/command-object… [2]https://bugs.launchpad.net/nova/+bug/2114855 Bug #2114855 “VM rebuild starts even if image virtual size is gr...” : Bugs : OpenStack Compute (nova)<https://bugs.launchpad.net/nova/+bug/2114855> Description =========== Openstackclient + Nova API accept to rebuild server with virtual size greater than the specified flavor’s disk size. Steps to Reproduce ================== 1 - Create a server specifying a flavor with small disk size (example: 1 GB) and an image small enough to fit. openstack flavor create --ram 512 --disk 1 --vcpus 1 tiny openstack server create –flavor tiny –image cirros vm-test 2 - Try to rebuild the server using a larger image but that still fits. It’s v... bugs.launchpad.net

2 1

[nova] multiple pci types with same address
by Arnaud Morin 17 Jun '25

17 Jun '25

Hello nova team, Quick question regarding support for multiple types (see [1]) with the same address: {vendor_id: "10de", product_id: "233b", "address": "00000000:03:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:04:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:44:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:45:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:83:00.0", "resource_class": "CUSTOM_H200_B"} {vendor_id: "10de", product_id: "233b", "address": "00000000:84:00.0", "resource_class": "CUSTOM_H200_B"} {vendor_id: "10de", product_id: "233b", "address": "00000000:C3:00.0", "resource_class": "CUSTOM_H200_B"} {vendor_id: "10de", product_id: "233b", "address": "00000000:C4:00.0", "resource_class": "CUSTOM_H200_B"} This works fine, I was able to define multiple aliases: {name: "h200a", device_type:"type-PF", resource_class: "CUSTOM_H200_A"} {name: "h200b", device_type:"type-PF", resource_class: "CUSTOM_H200_B"} I did that to create two blocks of 4 resources (A or B). But now, I need to create a flavor to boot instances with these devices. I want to have only one flavor that can use either A or B: For now I created a flavor with: pci_passthrough:alias='h200a:4' And was forced to create a second flavor with h200b:4. Is there any way to achieve a single flavor with both: Something like this? pci_passthrough:alias='h200a:4|h200b:4' I can't figure that out for now, is it possible? [1] https://docs.openstack.org/nova/latest/admin/pci-passthrough.html#support-f…

2 1

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

17 Jun '25

Hello Stackers, We're fifteen weeks away from the coordinated 2025.2 "Flamingo" release of OpenStack [1]. Milestone-2 is in a couple of weeks. This milestone is observed by several project teams for bug targeting. From the point of view of OpenStack's governance, this milestone serves as a point where we vet project deliverables to be included in the coordinated release. Releases are not tagged for deliverables from project teams that are deemed "inactive" [2]. In OpenStack, a project team is considered "inactive" when it no longer has regular contributor engagement or ongoing development. This often reflects that the problem the project once addressed is now being solved more effectively by another solution—either within or outside OpenStack. Inactivity isn't a failure, but rather a natural sign of how technology needs evolve over time. Any community member can propose a change to mark a project team inactive prior to Milestone-2. Doing so will prevent shipping broken or unmaintained code. In the past week, the OpenStack Technical Committee did not make any new governance changes. The team's focus has been on the implementation of the DCO by our deadline of 2025-07-01. I'd like to gently remind you that beyond July 1st, changes without a "Signed-off-by" line in the commit message cannot be uploaded to Gerrit. If you have a project team meeting before this date, please let folks know about this change. === Weekly Meeting === The last weekly meeting of the TC was held over IRC on OFTC's #openstack-tc channel on Tuesday, 2025-06-10 [3]. The main focus of the meeting was tracking all the changes necessary for enforcing the Developer Certificate of Origin in lieu of the ICLA beginning on 2025-07-01 [4]. We noted changes to various infrastructure pieces, and while we're hoping for a smooth transition, we do anticipate some hiccups. We are hoping for the community's patience and cooperation as we iron out the kinks. Further, concerns were raised about the Cyborg project's apparent inactivity. The last change merged into Cyborg was over two months ago, and a critical CI fix remains open, lacking review attention. Efforts to engage the team via the mailing list have not yielded any response, and there is no recent activity on IRC or Gerrit. While it's known that the Cyborg team has historically preferred WeChat/Weixin for communication, relying on unofficial channels or Foundation staff for outreach isn’t sustainable. The TC agreed that it’s important to determine whether the project is defunct or simply in need of new leadership, and to encourage maintainers to monitor and respond through community channels. Additionally, a self-report from the Vitrage team indicated that Tempest tests are currently failing due to a lack of contributor time this cycle. With the M-2 milestone deadline approaching on July 3rd, we emphasized the importance of project teams providing accurate and timely updates to the release team. The next meeting of the OpenStack TC is today, 2025-06-17. It'll be held over IRC in OFTC's #openstack-tc channel at 1700 UTC. Please find the agenda on the meeting's wiki page [5]. I hope you'll be able to join us. === Governance Proposals === ==== Open for review ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-07-03: OpenStack's 15th Birthday, Colombia User Group: https://www.meetup.com/colombia-openinfra-user-group/events/308383244 - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 - 2025-07-19: OpenInfra Days, Indonesia: https://2025.openinfra.id/ === 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. - Meeting: Join us at our weekly meeting. The Technical Committee meets every week on Tuesdays at 1700 UTC [4]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] Inactive projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [3] TC Meeting IRC Log 2025-06-10: https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-10-17.00.html [4] Replace ICLA with DCO: https://governance.openstack.org/tc/resolutions/20250520-replace-the-cla-wi… [5] TC Meeting Agenda, 2025-06-17: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[neutron] bug deputy report for week of 2025-06-09
by Bence Romsics 16 Jun '25

16 Jun '25

Hi Team, We only had a handful of new bug reports last week: High: * https://bugs.launchpad.net/neutron/+bug/2113861 [FT] Test ``test_initialize_network_segment_range_support_parallel_execution`` randomly failing already unblocked on master, backport in progress: https://review.opendev.org/q/topic:bug/2113861 Medium: * https://bugs.launchpad.net/neutron/+bug/2114176 [L3] L3 agent ``ProcessMonitor`` is not correctly registering the new processes fix merged: https://review.opendev.org/c/openstack/neutron/+/952450 Low: * https://bugs.launchpad.net/neutron/+bug/2114190 [whitebox-neutron-tempest-plugin] ``test_only_dropped_traffic_logged`` test failing with the WSGI Neutron API migration fix merged: https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/951264 [BTW: Maybe this project would be in a better place under the openstack namespace?] RFE: * https://bugs.launchpad.net/neutron/+bug/2114451 [RFE] ports should contain a reference to the segment_id they are bound to Related to https://bugs.launchpad.net/neutron/+bug/2105855. Probably a good idea to discuss on the drivers meeting. Cheers, Bence

1 0

[nova] Is It Possible to Attach a Cinder Volume as device='lun' ?
by Janaka Wickramasinghe 16 Jun '25

16 Jun '25

Hi, I'm running an OpenStack setup with Fibre Channel (FC) storage using Cinder volumes. I'm currently trying to configure a Windows Failover Cluster in guest VMs and have encountered an issue. Windows is querying the SCSI device for the Device Identification VPD (Page 0x83). The LUN is attached as a SCSI device using a virtio-scsi controller. In the domain XML (via libvirt), I see that the disk is defined as <disk type='block' device='disk'> also has a <serial>cinder-vol-uuid</serial> When Page 0x83 is queried, it returns the serial value (i.e., the cinder-vol-uuid), which Windows fails to recognize or accept. However, if I modify the XML to use: <disk type='block' device='lun'> and remove the <serial> tag, the guest is able to retrieve the expected information (I had to stop the compute service and restart the libvirt domain). Unfortunately, any changes made directly to the domain XML do not persist. Is there a supported way to specify device='lun' instead of device='disk' for volumes attached ? Any guidance would be greatly appreciated. Thank you With Best regards, Janaka

3 3

Re: [Octavia] - Loadbalancer appear offline but are running
by Wells, Aaron 14 Jun '25

14 Jun '25

Hi Karl, We ran into and fixed this issue on our installation by making sure that the UDP heartbeat packets on port 5555 were reaching the controllers. Thanks. Aaron -- Aaron Wells wellsaar(a)iu.edu DevOps Engineer Jetstream 2 https://kb.iu.edu/d/bfde

2 1

[neutron] Neutron BGP integration upstream sync
by Jakub Libosvar 13 Jun '25

13 Jun '25

Hi all, as per the previous suggestions I created the doodle [1] to pick the right time when we could meet. Finding a good timeslot is challenging as I noticed interest from all around the globe (US, EU, Australia). Please vote for which slot fits you best and if anyone has better suggestions, please let me know and let’s discuss. Thanks! Jakub [1] https://doodle.com/group-poll/participate/aK9Nkknd/vote

1 1

[horizon] Cancel weekly meeting on 2025-06-18
by Tatiana Ovchinnikova 13 Jun '25

13 Jun '25

Hello team, I am cancelling the upcoming weekly meeting since most of the members are on PTO. See you all in two weeks, June 25th! With kind regards, Tatiana

1 0

[nova][eventlet-removal]Weekly sync video call
by Balazs Gibizer 13 Jun '25

13 Jun '25

Hi, The Nova core team agreed to have a weekly high bandwidth sync meeting about the ongoing Eventlet removal work. Here are the details: [public]Nova Eventlet removal sync Every Wednesday: 14:30-15:00 UTC (16:30 – 17:00 CEST) Video call link: https://meet.google.com/bcy-uqoz-hje Cheers, gibi

2 1

[neutron] Drivers meeting agenda for Friday, June 13th
by Brian Haley 13 Jun '25

13 Jun '25

Hello Neutrinos: We have one item on the agenda for tomorrow's drivers meeting. Please add anything else to the wiki [0] to discuss if I missed something. * [RFE] Internal DNS resolution with OVS Agent - https://bugs.launchpad.net/neutron/+bug/2112446 See you tomorrow, -Brian [0] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[designate] It only syncs at reboot
by Alexander Luedtke 12 Jun '25

12 Jun '25

Hello Everyone, I have a strange problem, I wanted the designate services as hidden master, everything works fine, expect that the designate server does only sync with the master DNS server if I do a reboot of the host where the designate docker is on, or I have to restart the designate docker. Has anyone an idea how to fix that ? best regards Alex

2 1

[horizon] Changing the Term “Instance” to “Server” for improved clarity and consistency
by Dmitriy Chubinidze 11 Jun '25

11 Jun '25

Propose changing the term "Instance" to "Server" ( "Instances" to "Servers") in the platform’s user interface. This update will be aiming to improve clarity for users, align with industry terminology, and create a more intuitive experience. "Server" is a more commonly understood term than "Instance", especially for users who are not deeply familiar with cloud computing. Major platforms like AWS and Azure often use "Server" in their UI, even when referring to virtual instances. Adopting this term will make OpenStack easier to use and understand. This change will affect only the visual elements — such as UI labels, menus, and documentation. The underlying code, APIs, and data structures using the term instance will remain unchanged. This ensures there is no impact on functionality or development processes. We are open to feedback and discussion on this proposal.

7 8

Re: Api routes
by Bernd Bausch 11 Jun '25

11 Jun '25

I took the liberty to add the OpenStack mailing list on CC. As far as I know, the list of a service's APIs is not advertised to users, except in the documentation. An operator with access to the cloud controllers can list all endpoints of a service by generating a policy file, for example oslopolicy-sample-generator --namespace nova This will create a YAML file that contains a paragraph similar to the following per endpoint, which describes the authorization policy of this endpoint: # Delete a server # DELETE /servers/{server_id} # Intended scope(s): project #"os_compute_api:servers:delete": "rule:project_member_or_admin" This example is from https://docs.openstack.org/nova/2025.1/configuration/sample-policy.html. You need to run the oslopolicy command on a controller that contains the service's (in this case, Nova's) code. ________________________________________ From: engineer2024 <engineerlinux2024(a)gmail.com> Sent: Tuesday, June 10, 2025 10:55 PM To: Bernd Bausch <berndbausch(a)gmail.com> Subject: Re: Api routes This is not what I need. I need a way, sya, for nova api services, how many api routes or urls it supports. like, /servers , /servers/detail/ /os-aggregates etc On Tue, Jun 10, 2025 at 1:41 PM Bernd Bausch <berndbausch(a)gmail.com> wrote: These commands list API endpoints in your cloud: openstack endpoint list openstack catalog list ________________________________________ From: engineer2024 <engineerlinux2024(a)gmail.com> Sent: Monday, June 9, 2025 2:59 PM To: openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Api routes In openstack, is there a feature to list all the available routes for the rest api servers, instead of checking and referring the documentation? Thanks elinux

1 0

nova.conf : can [pci]alias be multivalued ?
by Michel Jouvin 10 Jun '25

10 Jun '25

Hi, We need to support several GPU models in our Nova configuration. This normally requires to add multiple `alias` entries (lines) in the [pci] section of nova.conf. Unfortunately for us, it complicates a lot the generation of nova.conf by our system configuration management tool (where the section is represented by a dict/hash, meaning that there is only 1 possible entry for 'alias'). Before trying to hack our tool, we were wondering if there is a way to put the different values as a list for a single 'alias' line and what should be the separator or syntax ? I was not able to identify a generic description of the syntax for multivalued parameters, if there is a generic rule. I already found this limitation (but we could live with it) for Keystone [federation]trusted_dashboard for example... Thanks in advance for any hint. Best regards, Michel

4 6

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

10 Jun '25

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

1 0

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

10 Jun '25

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

2 1