February 2025 - openstack-discuss

[neutron] Drivers meeting canceled Friday, February 7th
by Brian Haley 07 Feb '25

07 Feb '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as there is no agenda. 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

Having troubles with Mistral.
by Alvin Starr 06 Feb '25

06 Feb '25

I am trying to use Mistral to create a VM and I cannot seem to find the appropriate parameters. Here is part of my workflow. tasks: create_instance: action: nova.servers_create input: name: <% $.vm_name %> image: <% $.image %> flavor: <% $.flavor %> nics: - net-id: <% $.network %> key_name: <% $.keypair %> disk_config: AUTO availability_zone: nova meta: status: "pending" # Initial metadata value publish: instance_id: <% task(create_instance).result.id %> on-success: - get_vm_details I seem to keep getting a no suitable hypervisor found error. I have checked and i am sure I am not running into any resource constraints. any help or pointers would be greatly appreciated. -- Alvin Starr || land: (647)478-6285 Netvel Inc. || home: (905)513-7688 alvin(a)netvel.net ||

2 2

[nova][elections][ptl] Leaving my seat
by Sylvain Bauza 06 Feb '25

06 Feb '25

Hey Nova-ers That's a bit bittersweet but after running as a Nova PTL for 7 cycles, I preferred to leave this seat as I no longer have a lot of time for this. I'll continue to be around and I'll help our next PTL for sure :-) Thanks and see you at the PTG anyway :-) -Sylvain

2 1

[deployment] Is there a ranked list of automated deployment technologies (based on production usage)?
by Jordan Olin (OLINSolutions) 06 Feb '25

06 Feb '25

Hello, I’m trying to narrow my deployment focus on the most commonly used OpenStack automated deployment technologies/approaches. Does a ranked list or previous recent survey exist of currently available deployment automation solutions? If not, what is the correct approach for me to take to collect something like this? Thank you, Jordan. =========================== Jordan Olin, TOGAF EA President and Chief Solutioneer OLINSolutions, Inc. e: jordan(a)olinsolutions.com p: +1 508-982-4872 w: olinsolutions.com This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. This communication may contain material protected by government legislation. If you are not the intended recipient or the person responsible for delivering this email to the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email and then delete the email from your computer.

2 1

[openstack-ansible] Relocate ceph-mons to new hosts and decouple Ceph from openstack-ansible
by Jan Marquardt 06 Feb '25

06 Feb '25

Hi, We run a cluster with ~15 compute hosts and ~25 Ceph nodes. Everything was initially deployed with openstack-ansible. For some reasons we would like to decouple Ceph from openstack-ansbile and therefore move the ceph-mon containers to dedicated hosts. - Moving the containers seems straightforward, but how do we tell openstack-ansible that the containers are gone and that it can’t use the ip addresses anymore for other purposes? - How do we tell openstack-ansible which keyrings it has to deploy on compute hosts? Any recommendations? Has anyone done this before? Can you think of anything else that should be considered? Thanks in advance and best regards Jan

2 1

[Neutron] [FeatureRequest] Port AllowedIPs Subnet-Pool extension
by Justin Lamp 06 Feb '25

06 Feb '25

Hey there, I'd like to propose a feature to allow subnets to be added to Neutron ports and be allocated from a subnet-pool. We would have a couple of use cases for this. Please correct me if I am wrong, but right now we do not have a method to route a subnet to a VM without adding many fixed-ips from the subnet the VM is residing in. This is highly undesirable for us as our use case would be with Kubernetes. We'd like to be able to allocate a IPv6 subnet for every Kubernetes Node, so that every pod can get a fully routed v6 address without resorting to NAT. While searching the mailing list for IPv6 in general I found another person having a similar inquiry. In his case he wanted a subnet to use for his VPN-VM. This is also something we want to address and provide to our customers at some point. This is why I would like to propose that AllowedIP subnets can be created based on subnet pools, making it possible to route them externally. This will also make it possible for something like the OVN-BGP-Agent to expose them via BGP. Does anybody have any thoughts on this? Best regards, Justin -- Justin Lamp Systems Engineer NETWAYS Managed Services GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk, Sebastian Saemann | AG Nuernberg HRB25207 https://www.netways.de | justin.lamp(a)netways.de ** stackconf 2025 - April | Munich - https://stackconf.eu ** ** OSMC 2025 - November | Nuremberg - https://osmc.de ** ** NETWAYS Web Services - https://nws.netways.de ** ** NETWAYS Trainings - https://netways.de/trainings **

3 2

[tc][election] TC election Non-Candidacy
by Sławek Kapłoński 06 Feb '25

06 Feb '25

Hi, It's been 3 years for me already to be part of the OpenStack Technical Committee and as my 3rd cadence is getting to the end now, I just want to let You all know that I am not going to candidate again. This was a pleasure and great experience for me to be part of the TC for such a long time and I am really grateful that I was elected to serve in that role. But now I think it is time to give this place back to someone new who will bring fresh ideas to the TC. I will still be around and happy to help if needed of course. -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

Reviews for IBM SVf Cinder Driver
by Harsh Ailani 06 Feb '25

06 Feb '25

Hello community and core reviewers, We are from the IBM Team to develop the IBM SVf Cinder Driver for our community and on-prem customers. Till 2022 we were contributing and participating actively in the community development and review processes but due to internal organisational changes we were unable to participate in the community. Also, our CI/CD pipeline was disrupted for over a year which caused the major delay in our contribution. However, now the team is back on track along with the CI/CD pipeline and we have some huge line items that we need to upstream so that all our OpenStack customers could use those features with IBM Storages. Currently we have the following patches active which need your reviews so that they can be merged and be useable for the customers: Volume-group feature support patches: 1. [IBM SVf driver] Adding support for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/925450 2. [IBM SVf Driver] Added support for volumegroup-snapshot for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/926844 3. [IBM SVf Driver] Added support for restorefromsnapshot CLI for volumegroups | https://review.opendev.org/c/openstack/cinder/+/916722 4. [IBM SVf Driver] Added support of clone operation for volumegroup | https://review.opendev.org/c/openstack/cinder/+/938771 5. Doc: Documentation updates for ibm-svf-volumegroup feature. | https://review.opendev.org/c/openstack/cinder/+/929906 Our team is relatively new (except myself) and we are starting the process of reviewing other contributor’s patches as well. Requesting the core reviewers to please help use review these patches and get the merged in the community as we have more storage features in development pipeline which has dependencies on volume-group feature. Thanks and Regards, Harsh Ailani Openstack Developer - Flashsystem IBM

1 0

[all][elections][ptl][tc] Combined PTL/TC 2025.2 cycle Election Nominations Kickoff
by Slawomir Kaplonski 06 Feb '25

06 Feb '25

Hi, Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 19, 2025 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2025.2/<Project_Name or "TC">/<email_address> (for example, "candidates/2025.2/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2024.2 to 2025.1 timeframe, Mar 15, 2024 00:00 UTC - Feb 19, 2025 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Feb 26, 2025 23:45 UTC through to Mar 19, 2025 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the 2024.2 to 2025.1 timeframe, Mar 15, 2024 00:00 UTC - Feb 19, 2025 00:00 UTC, as well as any Extra ACs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the 2024.2 to 2025.1 timeframe, Mar 15, 2024 00:00 UTC - Feb 19, 2025 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ACs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ACs. Please find below the timeline: PTL + TC nomination starts @ Feb 05, 2025 23:45 UTC PTL + TC nomination ends @ Feb 19, 2025 23:45 UTC TC campaigning starts @ Feb 19, 2025 23:45 UTC TC campaigning ends @ Feb 26, 2025 23:45 UTC PTL + TC elections start @ Feb 26, 2025 23:45 UTC PTL + TC elections end @ Mar 19, 2025 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2025-02-19 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -- Best regards Slawek Kaplonski skaplons(a)redhat.com

1 0

[freezer] Moving project bug tracker to launchpad
by Dmitriy Rabotyagov 06 Feb '25

06 Feb '25

Hey there, In order to simplify and align with most OpenStack projects on bug tracker I aim to move Freezer from different Storyboard [1] projects back to unified Launchpad [2] tracker. However, historically the OpenStack Administrators [3] group was not added as Freezer project administrator/owner on Launchpad, which means that no current maintainer of the project has the necessary rights to manage the mentioned Launchpad project. I've added all current Launchpad admins for Freezer project to CC of this email, to either of you to add "openstack-admins" [3] to the Freezer Drivers [4] team, so that OpenStack Infra team could assist with further recovering/managing access to the Launchpad project. That will be very nice if some of you could spend couple of minutes on making this change and help us avoid cumbersome process of recovering access to the project Thanks in advance! [1] https://storyboard.openstack.org/#!/project/list?q=freezer [2] https://launchpad.net/freezer [3] https://launchpad.net/~openstack-admins [4] https://launchpad.net/~freezer-drivers

4 3