- openstack-discuss - lists.openstack.org

[cinder][nova][os-brick] Guidance on cross-project driver contribution
by Alokedip Choudhuri 08 Feb '26

08 Feb '26

Hello Everyone, We are working on contributing a new Cinder driver for *Infoscale*. This implementation requires coordinated changes across three projects to support the full attachment lifecycle: 1. *Cinder:* The core driver implementation. 2. *os-brick:* The connector APIs have been implemented there 3. *Nova:* New driver implementation to support the required operations like, "attach, detach, extend" for the volumes provisioned through the InfoScale Backend. We have already registered blueprints for this work: - *Cinder Blueprint:* https://blueprints.launchpad.net/cinder/+spec/infoscale-cinder-driver - *Nova Blueprint:* https://blueprints.launchpad.net/nova/+spec/infoscale-nova-driver Since this is a cross-project effort, I would appreciate guidance on the preferred workflow for submitting patches across multiple repositories to ensure a smooth integration. Looking forward to your feedback and suggestions. Thanks & Regards Alokedip

3 2

[keystone] Questions about federation mapping rules for academic research
by Sait, Abubakur Abdulgader S 07 Feb '26

07 Feb '26

Hello Keystone community, I am a PhD student researching privacy in federated identity systems. My work focuses on OpenStack Keystone federation, specifically how mapping rules process attributes from external Identity Providers. I would appreciate any insights from operators or developers about real-world federation deployments. My questions are: About mapping rules: 1. How many mapping rules do you typically have per federated IdP? 2. How often do these rules change after initial deployment? 3. Do you commonly use regex conditions, or mostly exact match conditions like any_one_of and not_any_of? About attributes: 4. How many attributes do you typically receive from federated IdPs? 5. For multi-valued attributes, how many values does a typical user have? About privacy: 6. Do you have privacy requirements affecting federated attributes? Any response would help my research. I am happy to share findings with the community when completed. Thank you for your time. Best regards, Abubakur Sait PhD Student, Wright State University, Dayton, OH, USA

1 0

[all][election] Check your voting eligibility for the OpenStack PTL & TC elections
by Goutham Pacha Ravi 06 Feb '26

06 Feb '26

Hello Stackers, Election season is here, and we want to ensure every voice that helps build OpenStack is heard. I would like you to take a moment to verify your "Active Contributor" [1] and OpenInfra Foundation membership status so you don't miss your chance to vote. To receive a ballot for the OpenStack TC elections, you must be a contributor to OpenStack repositories _and_ hold the status of "OIF Individual Member." To receive a ballot for a PTL election, you must have contributed to any of a project team's repositories _and_ hold the status of "OIF Individual Member." Check your membership level: ======================== Log in to your profile at https://openinfra.org/a/profile. Even if you’ve been a member for years, the OpenInfra Foundation (OIF) has a policy that automatically downgrades memberships to "OIF Community Member" if you haven't voted in recent Governing Board elections [2]. Upon logging in, if you see that you are an "OIF Community Member," you can restore your "OIF Individual Member" status on that profile page. Get recognized as an "Active Contributor": ================================ While our policy traditionally focuses on contributors to OpenStack's git repositories, we know that impactful work happens far beyond just code and documentation. We definitely value the "intangible" work that keeps this community running. If you haven’t contributed code or documentation to a repository during the 2025.2–2026.1 timeframe (March 14, 2025 – February 18, 2026), you can still vote! Please reach out to the PTL or DPL liaison of the project team you’ve supported and request to be added as an "Extra AC" (Extra Active Contributor) today [3]. The deadline to do this is February 13, 2026. If you run into issues or have questions about your eligibility, the TC would be happy to help. Simply reply to this thread, or chime in on OFTC's #openstack-tc IRC channel. Thanks, Goutham Pacha Ravi (gouthamr) [1] "Active Contributor": https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-se… [2] OIF membership page: https://openinfra.org/join/individual/ [3] Extra AC deadline: https://releases.openstack.org/gazpacho/schedule.html#g-extra-acs

5 6

[release] Release countdown for week R-7
by Thierry Carrez 06 Feb '26

06 Feb '26

Development Focus ----------------- We are entering the last weeks of the 2026.1 " Gazpacho" development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on February 12th. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 12th. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 19th). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 26th) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 26th. Any feature addition beyond that date should be discussed on the mailing list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 12th) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 26th) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (March 5th). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: February 12th, 2026 (R-7 week) Oslo feature freeze: February 12th, 2026 (R-7 week) Non-client library freeze: February 19th, 2026 (R-6 week) Client library freeze: February 26th, 2026 (R-5 week) Gazpacho-3 milestone: February 26th, 2026 (R-5 week) Cycle highlights deadline: March 5th, 2026 (R-4 week) Hibiscus (virtual) PTG: April 20-24, 2026 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting canceled Friday, February 6th
by Brian Haley 05 Feb '26

05 Feb '26

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics and I will be out. 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

[kolla][cinder] strange behavior with 2 storage nodes
by Alexander Luedtke 05 Feb '26

05 Feb '26

Hello Everyone, I have an strange behavior here on an cinder installation deployed with Kolla: The Setup: - 1 Controller node - some compute nodes - 2 Storage nodes (storage0, storage2) - later it should be 3. both with NFS Setup what is working. both storage nodes are shown on Skyline. The Problem: 1. in Skyline both storage nodes are shown but both are shown with the same size of one of both. 2. When I created a Volume then it was created on the other host as shown (in DB, skyline and so on) Anyone an idea what I can do to correct this problems ? Thanks a lot for your help ! Alexander -- Alexander Luedtke Systemadministrator Technische Universität München TUM School of Computation, Information and Technology Chair of IT Security Garching Boltzmannstr. 3 Room 01.08.036 85748 Garching b. Muenchen Tel. +49 89 289 18039 www.sec.in.tum.de

1 1

[policy] Updating RBAC (policy-popup team) meeting time
by Ghanshyam Maan 04 Feb '26

04 Feb '26

Hello Everyone, I have a conflict at the current time, so I am rescheduling the RBAC meeting to an hour later. Monday, Monthly 17:00 UTC. -> Monday, Monthly 18:00 UTC. I will update the wiki and the ICS file. Details: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… ICS File: https://meetings.opendev.org/#Secure_Default_Policies_Popup-Team_Meeting -gmann

1 0

[cinder] festival of reviews friday 2026-02-06
by Brian Rosmaita 04 Feb '26

04 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 6 February. who: Everyone! what: The Cinder Festival of Reviews when: Friday 6 February 2026 from 1400-1600 UTC where: videoconf info on the etherpad etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews This 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.ics See you there!

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Nominations Kickoff
by Ian Y. Choi 04 Feb '26

04 Feb '26

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 18, 2026 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/2026.2/<Project_Name or "TC">/<email_address> (for example, "candidates/2026.2/TC/stacker(a)example.org"). The name of the file should match an email address for your current Foundation Individual Membership. Take this opportunity to ensure that your Open Infrastructure Foundation member profile contains current information: https://openinfra.org/a/profile Any Open Infrastructure 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 Open Infrastructure Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 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 25, 2026 23:45 UTC through to Mar 18, 2026 23:45 UTC. The electorate for the TC election are the Open Infrastructure Foundation Individual Members who have a code contribution to one of the official teams over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC, as well as any Extra ACs who are acknowledged by the TC. The electorate for a PTL election are the Open Infrastructure Foundation Individual Members who have a code contribution over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 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 04, 2026 23:45 UTC PTL + TC nomination ends @ Feb 18, 2026 23:45 UTC TC campaigning starts @ Feb 18, 2026 23:45 UTC TC campaigning ends @ Feb 25, 2026 23:45 UTC PTL + TC elections start @ Feb 25, 2026 23:45 UTC PTL + TC elections end @ Mar 18, 2026 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 2026-02-18 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 Foundation individual member profiles can be updated at https://review.opendev.org/#/settings/contact and https://openinfra.org/a/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

1 0

[nova][ci] nova-next job is failing 100%
by melanie witt 04 Feb '26

04 Feb '26

Hey all, Just a heads up that we currently have a 100% fail rate broken nova-next job due to the following bug: https://bugs.launchpad.net/cinder/+bug/2127196 Fixes on both the Cinder and Nova side are proposed: * https://review.opendev.org/c/openstack/cinder/+/975540 * https://review.opendev.org/c/openstack/nova/+/975542 Please hold your rechecks until at least one of these patches is merged. Cheers, -melwitt

1 1