June 2025 - openstack-discuss - lists.openstack.org

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-17)
by Goutham Pacha Ravi 03 Jun '25

03 Jun '25

Hello Stackers, We're 17 weeks away from the release date for OpenStack 2025.2 "Flamingo" [1]. All projects following the cycle-trailing release model [2] will release their 2025.1 Epoxy deliverables by 2025-06-05, i.e., Thursday this week. The OpenStack Technical Committee is close to merging a resolution to require "Developer Certificate of Origin" [3] sign-offs from committers starting 2025-07-01. This will affect committers across the community. We request that you review what the DCO signifies [4] and how OpenStack governance plans to enforce it [3], and be prepared for the change. You can add "Signed-off-by" in your commit messages today. Project maintainers are requested to encourage this sign off, and spread the word to contributors via review comments and project team meetings. When Git is properly configured with your username and email, commit with the "-s" option to include the sign-off line in the commit message. In the past week, the TC didn't merge any new governance proposals; however, several, including the proposal to transition from the CLA to the DCO, are under review. === Weekly Meeting === Last week's meeting of the OpenStack Technical Committee occurred on 2025-05-27 on OFTC's #openstack-tc channel [5]. We covered a range of topics, including DCO implementation, the OpenInfra User Survey, and gate health. The primary focus was on the transition from CLA (Contributor License Agreement) to DCO. Many tooling changes are under review to facilitate this transition. Discussions also clarified that all new patches after July 1st will require a DCO sign-off, and existing patches can be rebased and signed off in Gerrit. There was a brief discussion about potentially abandoning patches in merge-conflict without a sign-off after July 1st, but the consensus was to instead add a comment to inform contributors about the need for the DCO with the updated patchset. The 2025 OpenInfra User Survey is currently live and will close in August [6]. Foundation staff will collate responses and share them with project leads/liaisons and the OpenStack TC in September. The TC reviewed the existing questions and decided not to make changes to avoid confusing the summarization of responses. There was also an update regarding the 2024 user survey, with clarification that anonymized raw data will be shared with PTLs and the TC, and that an NDA may be required for access. The next meeting of the OpenStack TC is on 2025-06-03. This meeting will be hosted simultaneously over video and IRC. You're welcome to join through any platform that you prefer. The agenda and call details are posted to the meeting's wiki page [7]. I hope that you'll be able to join us. === Governance Proposals === ==== Merged ==== - Fix outdated info on the tc-guide | https://review.opendev.org/c/openstack/governance/+/950446 ==== Open for review ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - [resolution] Replace CLA with DCO for all contributions | https://review.opendev.org/c/openstack/governance/+/950463 - Clarify actions when no elections are required | https://review.opendev.org/c/openstack/governance/+/949431 - Add nova-contrib repository | https://review.opendev.org/c/openstack/governance/+/951569 === Upcoming Events === - 2025-06-03: 15 ans d'OpenStack - OpenInfra UG, Paris: https://www.meetup.com/openstack-france/events/307492285 - 2025-06-05: OpenStack 15 ans! - OpenInfra UG, Rennes: https://www.meetup.com/openstack-rennes/events/306903998 - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-trailing": https://releases.openstack.org/reference/release_models.html#cycle-trailing [3] TC resolution to replace CLA with DCO for all contributions: https://review.opendev.org/c/openstack/governance/+/950463 [4] Developer Certificate of Origin: https://developercertificate.org/ [5] TC Meeting IRC Log 2025-05-27: https://meetings.opendev.org/meetings/tc/2025/tc.2025-05-27-17.00.html [6] Take the 2025 OpenStack User Survey: https://www.openstack.org/user-survey/survey-2025/ [7] TC Meeting Agenda, 2025-06-03: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ops][largescale-sig][scientific-sig] Ops Radio Hour on May 30, 2025
by Ildiko Vancsa 02 Jun '25

02 Jun '25

Hi OpenStack Community, I'm reaching out to you to draw your attention to a new online gathering called Ops Radio Hour. The call series is a casual setting for operators, engineers, and contributors to come together, share knowledge, and collaborate on the complexities of managing and deploying OpenStack environments. The first meeting is scheduled to May 30, 2025 at 1400UTC [1]. The call will happen on Meetpad, and you can find the agenda on the etherpad[2] created for the series. See You there! Best Regards, Ildikó [1] https://wiki.openstack.org/wiki/Operations/Meetups#2025_Ops_Radio_Hour_Seri… [2] https://etherpad.opendev.org/p/openstack_ops_radiohour

2 4

[nova][horizon] VNC console policy
by Eugen Block 02 Jun '25

02 Jun '25

Hi *, I'm a bit confused regarding the policy requirements to grant a user access to the vnc console via horizon dashboard. Since we have 10 years of history in our cloud, I tried to remove legacy stuff, e.g. old policy files and try with the defaults to see what we're missing. I recently upgraded this cloud to Caracal. It seems like currently, only a user with the admin role has access. Searching for some hints, I found the deprecated policies in (everything is commented): /usr/share/openstack-dashboard/openstack_dashboard/conf/nova_policy.yaml And then the defaults here: /usr/share/openstack-dashboard/openstack_dashboard/conf/default_policies/nova.yaml In the code I found two checks for "os_compute_api:os-consoles:show": class ConsoleTab(policy.PolicyTargetMixin, tabs.Tab): name = _("Console") slug = "console" template_name = "project/instances/_detail_console.html" preload = False policy_rules = (("compute", "os_compute_api:os-consoles:show"),) class InstanceDetailTabs(policy.PolicyTargetMixin, tabs.DetailTabsGroup): slug = "instance_details" tabs = (OverviewTab, InterfacesTab, LogTab, ConsoleTab, AuditTab) sticky = True policy_rules = (("compute", "os_compute_api:os-consoles:show"),) from /usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/instances/tabs.py. But I don't find any policy like that in the defaults. So I'm wondering what the current recommendation would be. Should I add only "os_compute_api:os-consoles:show" to /usr/share/openstack-dashboard/openstack_dashboard/conf/default_policies/nova.yaml? I'm not sure if that would override the other defaults (because of one entry only) or if this would be an additional policy (haven't been playing with those for some time now). Could anyone point me to the best approach? Thanks! Eugen

1 0

[Neutron] Bug deputy - summary from week of May 26th
by Sławek Kapłoński 02 Jun '25

02 Jun '25

Hi, I was bug deputy last week and here is short summary: ### Critical None ### High None ### Medium - https://bugs.launchpad.net/neutron/+bug/2111660 - OVN_AGENT_NEUTRON_SB_CFG_KEY doesn't set when Neutron OVN Agent starts - I marked it as Medium but I don't really have env to confirm it currently, - https://bugs.launchpad.net/neutron/+bug/2111908 - [FT] ``test_subport_delete`` fails - fix proposed already by Rodolfo, - https://bugs.launchpad.net/neutron/+bug/2112110 - [ovn-octavia-provider] LoadBalancer member not coming back after disable-enable - fix already proposed by Fernando, ### Low - https://bugs.launchpad.net/neutron/+bug/2112123 - Functional: privsep helper command exited non-zero test_trunk_creation_with_no_subports - opened by Lajos to track failiure with some functional test, ### RFE - https://bugs.launchpad.net/neutron/+bug/2111899 - [RFE] Use stateless NAT rules for FIPs - proposed by Rodolfo - https://bugs.launchpad.net/neutron/+bug/2111891 - IPv6 Subnet-Router anycast address inappropriately used for gateway_ip when specifying --subnet-range - unassigned, - https://bugs.launchpad.net/neutron/+bug/2112297 - [RFE] Support Policy Based Routing for LRs in Neutron OVN driver ### To triage - https://bugs.launchpad.net/openstack-helm/+bug/2112130 - No port found in network None with IP address 169.254.169.254 - Brian already started looking into this, it seems for me that it is more OpenStack Helm issue rather than Neutron so I added Helm project to it too. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[telemetry] Nominate Jaromír Wysoglad to Telemetry Core
by Juan Larriba 02 Jun '25

02 Jun '25

Hi, One of the things I wanted to do when becoming PTL of telemetry was to revive the interest in the community as I sensed that telemetry had been left a little bit behind from the rest of the projects. Since then, there has been a lot of movement: new Ceilometer features were added and even new projects (aethos, a prometheus-keystone proxy and grian-ui, a new metric displaying dashboard for Horizon) which has showed that the interest in gathering and displaying better and more scalable metrics is only growing. In these circumstances, the very small core contributor team needs to grow to keep up with all the influx of new features coming from the amazing community and I cannot think of anyone better than Jaromír Wysoglad to fulfill that role. Jaromír has been involved in the telemetry upstream community for years, tirelessly working to, among other things, make the whole telemetry suite to be compatible with Prometheus storage. He has implemented Prometheus compatibility with aodh, python-observabilityclient and many other things, including maintaining and improving the telemetry tempest test suite. Recently he created and is writing from scratch aetos, the new openstack-prometheus compatibility layer. I can't see a better contributor to the core group. If I don't hear any objections for one week, I'll add Jaromír to the group. Best Regards, Juan Larriba

3 3