February 2025 - openstack-discuss

[cinder] Support for Portworx
by Waines, Greg 16 Feb '25

16 Feb '25

Does anyone know how to use a https://portworx.com/ kubernetes-based storage solution as the storage backend for Cinder ? There is a Pure Storage driver listed in https://docs.openstack.org/cinder/latest/configuration/block-storage/volume… . https://docs.openstack.org/cinder/latest/configuration/block-storage/driver… BUT I do NOT believe this is the correct driver for interfacing with an https://portworx.com/ storage cluster. AND Neither the portworx documentation site ( https://docs.portworx.com/ ) nor the portworx github ( https://github.com/portworx ) have any information about integration with Cinder or OpenStack. ( ... although I believe it used to ... ) any info would be appreciated, Greg.

2 2

[tc][all][monasca ] Retiring the Monasca project
by Ghanshyam Mann 16 Feb '25

16 Feb '25

Hello everyone, As you might know, the Monasca project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Monasca retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

6 17

[kolla-ansible]how to set ovn_cms_opts in non gateway chassis
by Satish Patel 15 Feb '25

15 Feb '25

Folks, I have 3 controller nodes and they are gateway nodes also but now I want to add 2 more compute nodes who will have the following flag to handle external port traffic to reply to DHCP for sriov nodes. $ ovs-vsctl set open_vswitch . external_ids:ovn-cms-options="enable-chassis-as-extport-host" How and where do I tell kolla-ansible to put the above option for those 2 new compute nodes so options will survive re-deployment.

2 2

[ironic][nova] deploying VMware ESXi
by Doug Goldstein 15 Feb '25

15 Feb '25

Hello all, I’ve got a need to boot bare metal machines with VMware ESXi. ESXi 7 and newer is resistant to an image that can be reused like other OS images are used from Nova. As I mentioned it’s a bare metal machine so I’m working with Ironic but ultimately looking to drive this via Nova (through the Ironic hypervisor backend). Coming up empty in my Google-fu for an example of someone doing this so I figured I’d crowd source asking the ML. Right now I’m able to get an ISO of a system and it’s using VMware’s “weasel” installer which appears to be a fork/related to Anaconda and using Kickstart. Ironic supports an Anaconda deploy mechanism but the files are different and so it won’t just work out of the box (there is no stage2 but instead like 80 individual files) so my plan is to make a “weasel” deploy mechanism for Ironic. But just wanted to see if someone had any better approaches or ideas before I plod forward. Thanks. — Doug

1 0

[release] Release countdown for week R-6, Feb 17 - 21
by Elõd Illés 14 Feb '25

14 Feb '25

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on February 20th, 2025. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2025.1 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (February 27th, 2025) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 27th, 2025. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2025.1 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2025.1 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2025.1 Epoxy will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 20th, 2025 (R-6 week) Client library freeze: February 27th, 2025 (R-5 week) Epoxy-3 milestone: February 27th, 2025 (R-5 week) Cycle Highlights Due: March 6th, 2025 (R-4 week) 2025.1 Epoxy final release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0

[charms][elections][ptl] PTL non-candidacy
by James Page 14 Feb '25

14 Feb '25

Hi OpenStack Charmers Due to some changes in my focus I won't be standing as PTL for the OpenStack Charms project for the upcoming cycle. Thanks James

1 0

[neutron] Drivers meeting agenda for Friday, February 14th
by Brian Haley 14 Feb '25

14 Feb '25

Hello Neutrinos: Sorry for the late notice but this is the agenda for tomorrow's drivers meeting: * Router PUT behavior discussion: - https://review.opendev.org/c/openstack/neutron/+/941511 - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/941545 Not an RFE, but something Rodolfo wanted to talk about based on a recent bug. See you then, -Brian

2 1

[Neutron] Router external GW info policies bug
by Rodolfo Alonso Hernandez 14 Feb '25

14 Feb '25

Hello all: Yesterday I opened a bug because of an issue in the router's external GW info policies: https://bugs.launchpad.net/neutron/+bug/2098109. At the end of the day I found that the issue is more complicated than the trivial fixes I proposed. NOTE: I've reverted two backports of a patch that was not merged in master branch. I've also -W the patches proposed. I would like you to read https://bugs.launchpad.net/neutron/+bug/2098109/comments/11, that describes the current issue. Today I'm going to propose several patches to fix that problem, first in n-lib to fix the definitions and then in Neutron, to implement the needed policies for these new actions and their sub-attributes. Please don't hesitate to ping me in IRC for more info. @Brian Haley <haleyb.dev(a)gmail.com> I don't think it will be needed to add this topic to the drivers meeting. I think I've better described it in the bug comment and we can continue any discussion offline. So I think we can remove the section you added; it will be better to "digest" this info reading the bug and commenting async in IRC. Regards.

1 0

[nova] How to gain approval for a new feature on unavailable hardware
by taketani.ryo＠fujitsu.com 14 Feb '25

14 Feb '25

To Whom It May Concern, We are considering to propose and develop a new feature on OpenStack Nova for building Arm Confidential Computing Architecture (Arm CCA)-encrypted instances. I have some questions for doing it. * While specification of Arm CCA is already open(https://developer.arm.com/documentation/den0125/0300/Overview), No Arm CCA-enabled hardware is currently available to our knowledge. Therefore, we plan to conduct testing in an internal environment. * Would a proposal for a feature utilizing publicly unavailable hardware be acceptable to OpenStack? Alternatively, in this case, what steps or preparations are required for approval? * Should the blueprint and specification be submitted simultaneously? * The specification is currently incomplete. Building Arm CCA instances requires libvirt APIs, similar to AMD SEV instances(https://blueprints.launchpad.net/nova/+spec/amd-sev-libvirt-suppo…, but specification of these are not yet determined publicly. We are considering submitting the blueprint first to inform the community of our ongoing development efforts. Regards

3 6

#eventlet-removal Meeting canceled - Feb 18
by Herve Beraud 13 Feb '25

13 Feb '25

Hey folks, The coming meeting (Feb 18) is canceled. The next meeting will be on March 04. For more details about meetings: - https://etherpad.opendev.org/p/epoxy-eventlet-tracking - https://wiki.openstack.org/wiki/Eventlet-removal#Recurring_Events Thanks for your attention. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0