February 2026 - openstack-discuss

[manila] Removal of the "manila" CLI
by Carlos Silva 03 Feb '26

03 Feb '26

Hello everyone, Following up on our deprecation of the manila shell client, we are officially announcing its removal in the 2026.1 Gazpacho release [1]. The legacy manila shell was first deprecated in the OpenStack Zed release. Since then, we have achieved full feature parity with our OpenStackClient (OSC) plugin. Moving forward, Manila will exclusively support the "openstack share" command set. No new features have been added to the legacy "manila" client since its deprecation, and it did not support recent API microversions. The manila executable will no longer be installed or supported. All management and provisioning tasks must be performed using the openstack CLI (e.g., openstack share create instead of manila create). If you are still using the "manila" command in your automation, CI/CD pipelines, or daily workflows, please migrate to the openstack CLI immediately. We appreciate your cooperation as we move toward a more maintainable OpenStack CLI experience. Regards, carloss [1] https://review.opendev.org/q/topic:%22bp/openstack-client-support%22+(statu…

1 0

[manila] Removal of the long deprecated "v1" API
by Carlos Silva 03 Feb '26

03 Feb '26

Hello everyone, After being deprecated for nearly a decade, the Manila V1 API is officially being removed from the codebase [1]. This effort will be completed in the 2026.1 Gazpacho release. Since the introduction of the Microversioned V2 API, V1 has been deprecated. However, to reduce technical debt and streamline our maintenance efforts, we are finally decommissioning it. In the Gazpacho release, the /v1 endpoint will cease to exist. While we sunset this API, please note that the /v2 API at micro-version 2.0 is identical to the /v1 API. Action Required: If you have legacy scripts or integrations still pointing to the V1 endpoint (which we do not expect at this point), please update them to use the V2 API immediately. [1] https://review.opendev.org/q/hashtag:%22remove-manila-api-v1%22+(status:ope… Regards, carloss

1 0

[neutron] Bug Deputy Report Jan 26 - Feb 01
by Yatin Karel 03 Feb '26

03 Feb '26

Hi Neutrinos, Below is the bug deputy report for last week:- Critical ====== - https://bugs.launchpad.net/neutron/+bug/2139271 - [FT] Failing test ``test_gateway_chassis_balanced_scheduling_multiple_gw_networks`` Fixed by Rodolfo High ==== - https://bugs.launchpad.net/neutron/+bug/2139143 - [OVN] ``_sync_ha_chassis_group`` fails if the current HCG has more than ``MAX_CHASSIS_IN_HA_GROUP`` HA_Chassis registers Assigned to Rodolfo Medium ====== - https://bugs.launchpad.net/neutron/+bug/2139586 - [whitebox-neutron-tempest-plugin] Metadata tests should be execute with OVN agent too Assigned to Rodolfo - https://bugs.launchpad.net/neutron/+bug/2139063 - Ensure no RPC clients are instantiated if ``rpc_workers=0`` Assigned to Rodolfo - https://bugs.launchpad.net/neutron/+bug/2139581 - Updating router state fails due to NoneType error Assigned to William Tripp Low === - https://bugs.launchpad.net/neutron/+bug/2139416 [doc] Document what changes are needed when changing supported Python version Unassigned Incomplete - https://bugs.launchpad.net/neutron/+bug/2139583 - neutron-openvswitch-agent native driver: Permanent flow loss after OVS restart due to unhandled 'unknown dpid' during rpc_loop Looks valid but requested more details -- Thanks and Regards Yatin Karel

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2026.1/R-8)
by Goutham Pacha Ravi 02 Feb '26

02 Feb '26

Hello Stackers, We're 8 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. Next week is the feature freeze for OpenStack's Common Library projects ("oslo"), and this includes python-openstackclient and python-openstacksdk for this release. It's also the deadline for PTLs and DPL liaisons to propose additional names as contributors to OpenStack [2]. Please take this opportunity to credit folks who have been contributing to project maintenance without having any merged changes via Gerrit. Recording these individuals' contributions as "Active Contributors" acknowledges their effort and allows them to vote in the upcoming elections. Speaking of elections, the nomination period for TC and PTL elections begins this week. If you intend to contest these elections, please do submit your candidacy [3]. In the past week, the OpenStack Technical Committee began updating projects that followed the "Distributed Leadership" model during the 2026.1 "Gazpacho" release cycle. The release management team has opted to govern itself using the distributed leadership model and has retained the liaisons. The Watcher project has decided to move to the PTL model, and its PTL will be elected in the upcoming elections. We're awaiting decisions from the Ironic, Requirements, Freezer, and Oslo projects. Please review the open governance patches to help these teams make appropriate governance decisions. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was hosted on January 27th, 2026 in OFTC's #openstack-tc IRC channel [4]. We focused our attention toward the 2026.2 Election cycle, which is fast approaching. Nominations open on February 4 and run through February 18 [5]; since our election officials are spread a bit thin this time, several TC members who aren't seeking re-election stepped up to help attest nomination patches. We’ve decided to retarget the MariaDB/MySQL Character Set community goal. While it’s a vital piece of technical debt to address, we’re looking to define and commit to this in the 2026.2 cycle to ensure the rollout is realistic and implementable across the projects. We had a robust discussion regarding updating the Technical Vision [6] and how it intersects with the Foundation’s "Next Level in 2026" initiatives [7]. The goal here isn't just to produce a static document, but to use the vision as a tool to refocus the "What is OpenStack?" question, helping us stay consistent as we also define how to evolve the vision. We also touched upon the retirement of some inactive projects in the 2026.2 "Hibiscus" cycle [8]. We hope to make practical decisions in the interest of conserving the community's energy and focusing on paying down technical debt such as eventlet removal. The next meeting of the OpenStack TC is on Tuesday, February 3rd, 2026. It'll be at 1700 UTC in OFTC's #openstack-tc channel. Please find the agenda on the meeting's wiki [9]. This week we're looking to discuss improvements to the User Survey, revival of Cyborg, and begin planning our presence at the PTG in April. I hope you're able to participate. === Governance Proposals === ==== Merged ==== - Remove rbd-iscsi-client from release management | https://review.opendev.org/c/openstack/governance/+/972316 - Remove barbican-ui from release management | https://review.opendev.org/c/openstack/governance/+/972315 - Update mission statement for kolla project | https://review.opendev.org/c/openstack/governance/+/974421 - Reset the DPL model for watcher project | https://review.opendev.org/c/openstack/governance/+/974926 ==== Open For Review ==== - Move FIPS Compliance goal back to proposed | https://review.opendev.org/c/openstack/governance/+/969145 - Reset the DPL model for Oslo project | https://review.opendev.org/c/openstack/governance/+/974929 - Reset the DPL model for Freezer project | https://review.opendev.org/c/openstack/governance/+/974931 - Reset the DPL model for requirements project | https://review.opendev.org/c/openstack/governance/+/974927 - Reset the DPL model for Ironic project | https://review.opendev.org/c/openstack/governance/+/974930 - Revert "Revive os_monasca" | https://review.opendev.org/c/openstack/governance/+/974775 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] Nominate "Extra ACs": https://releases.openstack.org/gazpacho/schedule.html#extra-ac-freeze [3] Be a candidate this election: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] TC Meeting IRC Log, Jan 27 2026: https://meetings.opendev.org/meetings/tc/2026/tc.2026-01-27-17.00.html [5] 2026.2 Elections: https://governance.openstack.org/election/ [6] Vision for OpenStack Clouds: https://governance.openstack.org/tc/reference/technical-vision.html [7] "Next Level in 2026": https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] Inactive Projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [9] TC Meeting Agenda, Feb 03 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Digital Sovereignty WG Kickoff Summary + Recording + Next Steps
by Kendall Nelson 01 Feb '26

01 Feb '26

Hello Everyone! Thank you to those that were able to attend our first meeting of the Digital Sovereignty Working Group! We had excellent representation from many different countries and organizations. Lots of good perspective and ideas were shared and I am eager to get started! As promised, here is the recording for those that were not able to attend: https://zoom.us/rec/share/QLyhngha_pgXEc2736oPEdDGWz_UI8IZLbHbJGyDWLv7nt4es… And here is the etherpad where we took notes, but will also continue to use going forward for meeting agendas and general working group coordination: https://etherpad.opendev.org/p/Digital-Sovereignty-WG If you watch the recording, please feel free to add your name to the attendees list in the etherpad, just make an additional note that you watched the recording. Everyone is encouraged to add to the notes and content in the etherpad whether they attended the meeting live or watched the recording. The goal is to capture as much participation as possible. Digital sovereignty is a very important topic with an ever developing list of accompanying legislation and we need everyone's perspective! Now, while there wasn't much in the way of immediate todo's, the one request that I have is that folks fill out this poll so that we can select a meeting time <https://beta.framadate.org/polls/5f355daf8e4329e1cd52> for the next one (during the first week of February). Responses to this poll are allowed until January 28th. -Kendall

1 2

[nova] gate fix for broken nova-alt-configurations
by Ghanshyam Maan 01 Feb '26

01 Feb '26

Hi All, WIth the recent change in tempest, nova-alt-configurations is broken for the rbac policy access. I proposed the fix, please avoid recheck until fix is merged - https://review.opendev.org/c/openstack/tempest/+/975356 - gmaan

1 0