openstack-discuss

openstack-discuss@lists.openstack.org

February 2026

  • 52 participants
  • 61 discussions

19 Feb '26
Hello All!Thank you to all those that were able to find the time to attend andparticipate in this week's meeting!For those that were not able to attend, here is the recording of today'smeeting so that you can catch up and stay engaged with these efforts:https://zoom.us/rec/share/a5cXdx6RsWRNuGt8uqyQEgrVDNnIbexDag8NaUEzhcuyiUmTh…*Now, as far as next steps go: *- Soon, Allison and I will send around some samples of stance text for thelanding page and we will *NEED* your feedback and opinions to make sure wehave everything covered.- If you have a use case that you think would be good to share, pleasestart working on those case studies ASAP! While we don't need them tolaunch the landing page (which is scheduled for March 20th-ish) the morecontent we have ready to go early on, the better!- If you are interested in helping with either of the other initialdeliverables ( the comparison sheet or the best practices doc), please addyour name to those sections of the etherpad<https://etherpad.opendev.org/p/Digital-Sovereignty-WG>. Also, if you haveadditional resources that would be helpful in crafting either deliverable,add them to the etherpad. Feel free to also get started throwing content ineither as well! They will be living documents in draft form for a while, sonothing has to be perfect. Focus on just getting content in and we willpolish things up later.When Allison and I send drafts of stances for review, we will also send outthe poll for selecting the next meeting time which is slated for the weekof March 9th, likely the 10th, 11th or 12th.Whew, that was a lot of information, but we have a lot of work to get doneas a group! I am so excited to see this effort through with you all; we area strong community and we are stronger together, so thank you for sharingyour expertise and time with the Digital Sovereignty Working Group.-- Kendall Nelson*Senior Upstream Developer Advocate*The OpenInfra Foundation <https://openinfra.dev/>
1 0
0 0
Nova Multi-Cell Live Migration Issues
by Tyler Wilson 19 Feb '26

19 Feb '26
Hello All,I'm trying to get a 2 cell setup going as a test environment and amrunning into some troubles. I seem to be able to start VM's just fine,however when I try live-migrations I am getting this error:2026-02-19 20:11:01.448 1 ERROR nova.conductor.manager [Nonereq-91d4c1c6-a69f-41d4-a3ca-c0890bde0af8 - - - - - -] Migration ofinstance 73123ed9-d112-4030-945c-96c75a016d55 to host compute1unexpectedly failed.: oslo_messaging.rpc.client.RemoteError: Remoteerror: RemoteError Remote error: CantStartEngineError Nosql_connection parameter is establishedI see this on the following service logsnova-conductor (superconductor role only)nova-apinova-computeWhat is odd is that I don't see any activity in the cell-conductorwhen this happens, even with debug enabled.Here are the configured connection strings I have in eachconductor/api/compute services:https://pastebin.com/raw/uuamtzskAre these the correct database connection strings for each service?I'm basing this off the multi-cell diagram in the docs.The fact that the cell-conductors aren't showing any activity whenthis happens is throwing me off. I feel like I'm missing somethinghere but I can't put my finger on it.Any help would be appreciated, thanks!
1 0
0 0
[all] POST_FAILURE in openstack-tox-py310
by Takashi Kajinami 19 Feb '26

19 Feb '26
I feel like this week is one of the most exciting week we have had recently :-PWe started seeing consistent POST_FAILURE in openstack-tox-py310 (and other jobs using py310).https://github.com/testing-cabal/testtools/issues/569The issue was caused by testtools and was fixed in testools 2.8.4, but we likely need torebuild the image used in CI to pull the fixed version.Please avoid mass recheck or merging any new changes now before you check the CI statuscarefully.Thank you,Takashi-- Takashi Kajinamiirc: tkajinamgithub:https://github.com/kajinamitlaunchpad:https://launchpad.net/~kajinamit
2 3
0 0
Hello Neutrinos:I am going to cancel tomorrow's Drivers meeting as there are no topics on the agenda. Just a reminder that our open spec list is at [0].Have a nice weekend!-Brian[0]https://review.opendev.org/q/status:open+project:openstack/neutron-specs
1 0
0 0
Hi all,I am currently experiencing issues while setting up a basic ironicdeployment. My environment consists of a controller running Ubuntu 24.04and a baremetal host with IPMI support but no operating system installed. Iam using kolla-ansible for the Flamingo version OpenStack deployment, andall configuration is being managed through the globals.yml file. One of thecontroller’s network interfaces is configured to provide DHCP and isconnected to a physical switch. I have attached an image (Figure 1)illustrating the physical layout of my setup.My controller had the following configuration:{ Two interface (eth0 and eth1) eth0: 10.42.0.1 with netmask 24 eth1: No IP assignment }My compute had the following configuration:{ 5 interfaces (eth0, eth1, eth2, eth3, IPMI) eth1: No IP assignment and is connected to switch (MAC:6F:F1:34:E9:01:29) IPMI: 10.42.0.100 connected to switch}In my globals.yml file, I have the following configuration:{ openstack_release: "2025.2" # Flamingo kolla_internal_vip_address: "10.42.0.1" docker_configure_for_zun: true containerd_configure_for_zun: true containerd_grpc_gid: 42463 enable_openstack_core: true enable_haproxy: false enable_cinder: false enable_etcd: true enable_fluentd: true enable_ironic: true enable_kuryr: true enable_magnum: true enable_zun: true ironic_dnsmasq_dhcp_ranges: - range: "10.42.0.5,10.42.0.200" ironic_dnsmasq_boot_file: "pxelinux.0" ironic_cleaning_network: "public1" ironic_dnsmasq_default_gateway: "10.42.0.1" ironic_inspector_kernel_cmdline_extras: ['ipa-lldp-timeout=90.0','ipa-collect-lldp=1']}After completing the deployment, I verified that all the required servicesare running as docker containers. Immediately afterward, I executed thenecessary command to generate the admin credentials, which allows me to usethe OpenStack client.1. $pip install python-openstackclient -chttps://releases.openstack.org/constraints/upper/master2. $kolla-ansible post-deploy3. $/path/to/venv/share/kolla-ansible/init-runonceAfter running the command, the following baseline was created.1. Two network (public1 and demo-net), where public is a flat network2. cirros image file3. flavorsAfter that, I uploaded a working kernel, initramfs, and ISO image toOpenStack. I verified that these images were functioning correctly bysuccessfully launching an instance. Next, during the node enrollmentprocess, I ran the following command to enroll my baremetal node.1. $openstack flavor create --ram 32768 --vcpu 16 --disk 120 baremetal2. $openstack flavor set --property resources:CUSTOM_IRONIC=1 baremetal3. $openstack flavor set --property resources:VCPU=0 baremetal4. $openstack flavor set --property resources:MEMORY_MB=0 baremetal5. $openstack flavor set --property resources:DISK_GB=0 baremetal6. $openstack baremetal node create --driver ipmi --deploy-interface direct--driver-info ipmi_username=<IPMI_usernmae> --driver-infoipmi_password=<IPMI_password> --driver-info ipmi_address=10.42.0.100--driver-info deploy_kernel=<kernel uploaded> --driver-infodeploy_ramdisk=<initramfs uploaded> --property local_gb=20 --resource-classbaremetal --name My_nodeAfter enrolling the node as described above, and since I do not have anironic Inspector setup, I manually created a port for the enrolled nodeusing the MAC address 6F:F1:34:E9:01:29, which corresponds to the LANinterface. At this point, I am unsure how to proceed with booting thedesired image onto the bare-metal host. I would greatly appreciate anyguidance on the next steps required to deploy the image to the machine.Best,Vincent
1 0
0 0

19 Feb '26
Hi everyone,First of all, apologies for the lack of regular updates over the past fewmonths. I haven’t managed to find the time and energy recently, but I’mtrying to get back to a more regular rhythm.For the next meeting, I’d like us to explicitly reserve 10 to 15 minutesfor bug scrubbing and avoid skipping it. To make this possible, I’ll adjustthe agenda accordingly so that this time is clearly allocated.For those volunteering for bug scrubbing: if you have questions aboutspecific bugs, please try to prepare them in advance and, if possible, addthem to the agenda document under the Bug Scrubbing section. This shouldhelp us make that time more efficient and focused upfront.Thanks everyone, and see you at the meeting.Cheers,René
1 0
0 0

18 Feb '26
Developers, The TC Election Campaigning Period has now started[1]. During the nextcouple days, you are all encouraged to ask the candidates questions abouttheir platforms[2], opinions on OpenStack, community governance, and anythingelse that will help you to better determine how you will vote. This is thetime to raise any issues you wish the future TC to consider, and to evaluatethe opinions of the nominees prior to their election.Candidates, Each of you has posted a platform[2], and announced your nomination tothe developers. From this point, you are encouraged to ask each otherquestions about the posted platforms, and begin discussion of any pointsthat you feel are particularly important during the next cycle. While youare not yet TC members, your voices and opinions about the issues raised inyour platforms and questions raised by the wider community will help ensurethat the future TC has the widest possible input on the matters of communityconcern, and the electorate has the best information to determine the idealTC composition to address these and other issues that may arise.[1]https://governance.openstack.org/election/[2]https://opendev.org/openstack/election/src/branch/master/candidates/2026.2/…
1 0
0 0
The PTL and TC Nomination period is now over. The official candidate listsfor PTLs [0] and TC seats [1] are available on the election website.-- PTL Election Details --There are 8 projects without candidates, so according to thisresolution[2], the TC will have to decide how the followingprojects will proceed: Adjutant, Masakari, Mistral, Oslo,Requirements, Skyline, Venus, VitrageThere are 2 projects that will have elections: Barbican, Horizon.-- TC Election Details --The official candidate list is available on the election website[1].Now begins the campaigning period where candidates and electoratemay debate their statements.Polling will start Feb 25, 2026 23:45 UTC.Thank you,[0]https://governance.openstack.org/election/#ptl-candidates[1]https://governance.openstack.org/election/#tc-candidates[2]https://governance.openstack.org/resolutions/20141128-elections-process-for…
1 0
0 0
Hi all,I would like to announce my candidacy for Watcher PTL for the 2026.2(Hibiscus) cycle.I started contributing to OpenStack during the Stein cycle in Manilaproject where I still assist with patch reviews, depending on the demand.Starting at 2025.1 release, I have been a Watcher contributor andmaintainer, working with other contributors to revive the project andtackle many of the existing technical debts. In 2025.2 I started theeffort to remove Eventlet from Watcher and in 2026.1, working as tact-sig,have been refactoring our CI, including our stable branches, to properlytest patches in both check and gate pipelines.For the 2026.2 cycle, these are some of the priorities that I plan tofocus on:Testing and CI/CD Coverage Improvements:* Support the implementation of new integration test in Watcher Dashboard* Expand test coverage for features, datasources, and/or integrations that remain untested in CI (e.g.: Audit Scope feature)* Start the effort on adding functional tests to Watcher* Continue improvements to check/gate pipelines for master and stablebranchesScalability and Availability:* Support for osprofiler in Watcher to enable performance analysis at scale* Performance analysis in Action Plan parallelizationOpenStack SDK Migration:* Support the migration effort started in 2026.1 to modernize the remaining integrationsEventlet Removal:* Make native threads the default thread mode in 2026.2* Address performance gaps when running with native threading* Prepare for Eventlet deprecation in 2027.1Thank you for your consideration.Douglas ViroelIRC: dviroel
1 0
0 0

18 Feb '26
Hello Argonauts,This is a reminder that the twice-monthly Cinder Festival of Reviews will be held at the end of this week on Friday 20 February.who: Everyone!what: The Cinder Festival of Reviewswhen: Friday 20 February 2026 from 1400-1600 UTCwhere: videoconf info on the etherpadetherpad:https://etherpad.opendev.org/p/cinder-festival-of-reviewsThis recurring meeting, that happens on the first and third Friday of each month, can be placed on your calendar by using this handy ICS file:https://meetings.opendev.org/calendars/cinder-festival-of-reviews.icsSee you there!
1 0
0 0