January 2025 - openstack-discuss - lists.openstack.org

openstack-discuss-owner mailbox
by Albert Braden 28 Jan '25

28 Jan '25

Is anyone manning the openstack-discuss-owner mailbox? I've been writing to that address about the recent glitch that deleted my list subscription and account (and according to the error message, hundreds of others), but I'm not getting a response.

2 3

[publiccloud-sig] Public Cloud SIG Meeting this week
by Felix Kronlage-Dammers 28 Jan '25

28 Jan '25

Hi everyone, This upcoming Wednesday (January 29th) the next meeting of the publiccloud-sig is going to happen or at least would happen: However I’ll not be around tomorrow to facilitate and I did not get any feedback from anyone else on it. Usually we would be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig - so give it a shot ;) See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG felix -- Felix Kronlage-Dammers Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[nova] Performance Issues with OpenStack Server List on os-compute-api-version 2.96
by 黒羽正徳 [Kuroha Masanori] 28 Jan '25

28 Jan '25

Hello, We have recently encountered a situation where the response time for the openstack server list command is significantly slower when specifying os-compute-api-version 2.96 for certain projects. In comparison with version 2.95, some projects experience a response time that is 2-3 times longer, while other projects show little to no difference. We understand that in version 2.96, there was a change to obtain the availability zone from the request_spec [1]. However, upon checking the instance records in request_spec for the projects, we have not identified any differences that would account for this slow response behavior. Additionally, we have observed that when certain ERROR VM is present, the response time for the server list can become considerably slower for specific projects. In one case, we resolved the slow response issue by deleting instances that did not have corresponding fault records in the database. However, the exact reason why this action resolved the issue remains unclear. If anyone has more detailed information or potential solutions regarding these issues, or if you have encountered similar situations, we would greatly appreciate your insights. [1] https://git.linecorp.com/Flava-IaaS/nova/commit/c98c8d84eec6e65f1b67ae1ab82… Best regards, Masanori Kuroha

1 1

[largescale-sig] Next meeting: January 15, 9utc
by Thierry Carrez 27 Jan '25

27 Jan '25

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250115T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

3 3

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-9)
by Goutham Pacha Ravi 27 Jan '25

27 Jan '25

Hello Stackers, We're 9 weeks away from OpenStack's 2025.1 coordinated "Epoxy" release [1]. These weeks leading up to feature freeze (R-5/Feb 24-28) will be about "getting things done" for project teams. As Slawek Kaplonski (slaweq) wrote to you [2], we'll be kicking off combined elections for Project Team Leads for the 2025.2 "Flamingo" release cycle and five seats on the OpenStack Technical Committee next week. In light of this, please confirm your eligibility to vote in these elections by navigating to the CIVS website and entering your Gerrit email address: https://civs1.civs.us/cgi-bin/opt_in.pl In each of the past three elections, we've had roughly a fifth of eligible voters cast their votes. It would make a great difference to our community if we could improve this statistic with your cooperation! In the past week, the OpenStack Technical Committee approved a resolution to welcome the "Freezer" (Disaster-Recovery-as-a-Service) project back into the fold of "active" projects [3]. I'd like to extend a shout-out to Dmitriy Rabotyagov (noonedeadpunk) and Álvaro Soto (khyr0n) for their work to revive the project team. The team is looking to pursue the release of several project deliverables during this release. === Weekly Meeting === The TC weekly IRC meeting on 2025-01-21 [4] was well attended. We were in "getting things done" mode too, as much of the meeting followed up on action items from past meetings. We discussed getting more active review participation for changes to the "openstackdocstheme" repository by working with the Oslo team. We also deliberated on election nomination windows. We are in favor of early nominations from folks who are unable to self-nominate due to holidays or other personal reasons to be away from their computers during the nomination window. However, there were concerns expressed that the election officials may be burdened by the work necessary to shepherd such nominations. Early nominations would fail several CI checks, require re-checks, and potentially create some confusion. We'll attempt to watch this closely for the next election cycle and recalibrate. Our goal is to avoid leaderless projects due to holiday cycles during elections. The TC also discussed the next steps for the newly active Freezer project to release artifacts during the current release cycle. The next meeting of the OpenStack TC is today, 2025-01-28, at 1800 UTC in the #openstack-tc IRC channel on OFTC. Please find the meeting's agenda on the meeting wiki [5]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Retire Freezer DR | https://review.opendev.org/c/openstack/governance/+/938183 - Remove Freezer from inactive state | https://review.opendev.org/c/openstack/governance/+/938938 ==== Open for Review ==== - Retire qdrouterd role | https://review.opendev.org/c/openstack/governance/+/938193 - Reset the DPL model for Oslo project | https://review.opendev.org/c/openstack/governance/+/939485 - Reset the DPL model for Release project | https://review.opendev.org/c/openstack/governance/+/939486 - Add devstack-plugin-prometheus repo to Quality Assurance repos | https://review.opendev.org/c/openstack/governance/+/939953 - Reset the DPL model for Watcher project | https://review.opendev.org/c/openstack/governance/+/939488 - Add Watcher project update liaison | https://review.opendev.org/c/openstack/governance/+/940168 - Adopt DPL model for Watcher 2025.2 | https://review.opendev.org/c/openstack/governance/+/940167 - Define 2025 upstream investment opportunities | https://review.opendev.org/c/openstack/governance/+/939507 - Add resolution for late Freezer release | https://review.opendev.org/c/openstack/governance/+/939792 - Deprecate ironic-lib | https://review.opendev.org/c/openstack/governance/+/939278 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === - 2025-01-28: OpenInfra Board Monthly Meeting: https://board.openinfra.org/ - 2025-02-01: FOSDEM 2025 (https://fosdem.org/2025/) OpenStack's 15th Birthday Celebration - 2025-02-05: Nominations open for 2025.2 TC/PTL Elections: https://governance.openstack.org/election/ - 2025-02-28: 2025.1 ("Epoxy") Feature Freeze and release milestone 3 [1] - 2025-03-06: SCALE 2025 + OpenInfra Days NA (https://www.socallinuxexpo.org/scale/22x) Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] 2025.2 Election Kickoff: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] Remove Freezer from inactive state: https://review.opendev.org/c/openstack/governance/+/938938 [4] TC Meeting IRC Log 2025-01-21: https://meetings.opendev.org/meetings/tc/2025/tc.2025-01-21-18.00.log.html [5] TC Meeting Agenda, 2025-01-28: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[mistral] meetings during next PTG
by Arnaud Morin 27 Jan '25

27 Jan '25

Hey all, Next PTG will take place between April 7 to 10. Is there anyone willing to talk about mistral developement during this PTG? So far, mistral has not evolved that much, but maybe someone is having ideas about it? Also, there is this eventlet-removal topic that could be discussed. Let me know, Cheers, Arnaud.

1 0

[neutron] Bug Deputy Report Jan 20 - Jan 26
by Yatin Karel 27 Jan '25

27 Jan '25

Hi Neutrinos, Below is the bug deputy report for last week:- High ------ - https://bugs.launchpad.net/neutron/+bug/2095807 - OVN loadbalancer via FIP does not work for DVR + VLAN networks Unassigned OVN octavia provider, Asked Fernando to have a look as could be known one - https://bugs.launchpad.net/neutron/+bug/2095598 - test_async_process_respawns functional test failing in fips functional job Unassigned We thought it would get fixed with https://review.opendev.org/c/openstack/neutron/+/939627 but it's not, so have to be checked again - https://bugs.launchpad.net/neutron/+bug/2095595 - The neutron-dhcp-agent resync throttling mechanism doesn't work Assigned to Anton Kurbatov - https://bugs.launchpad.net/neutron/+bug/2095590 - [OVN] Neutron API stops refreshing the hash ring node Assigned to Rodolfo - https://bugs.launchpad.net/neutron/+bug/2095566 - [OVN] Router creation timeouts randomly Unassigned Rodolfo mentioned he has some fixes in flight to cover ovn wsgi related issue, so to confirm if this is also covered. Medium ---------- - https://bugs.launchpad.net/neutron/+bug/2095576 - [OVS] False ERROR log message every time when creating VM Unassigned - https://bugs.launchpad.net/neutron/+bug/2095322 - ADMIN_OR_NET_OWNER_{MEMBER|READER} rules don't work for subnets Unassigned Incomplete --------------- - https://bugs.launchpad.net/neutron/+bug/2096704 - [RFE] Allow rebalancing of OVN LRPs Asked for more context -- Thanks and Regards Yatin Karel

1 0

[all][elections][ptl][tc] Combined PTL/TC 2025.2 cycle Election Season
by Sławek Kapłoński 27 Jan '25

27 Jan '25

Hi, Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 05, 2025 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in these governance documents[1][2][3]. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. Similarly, there will only be a TC poll if there are more than 5 candidates stepping forward the available TC positions. All members of the community are encouraged to confirm their email address as described at: https://governance.openstack.org/election/#electorate There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you wish to discuss in private please email any of the election officials[4] so that we may address your concerns. Thank you, [1] https://governance.openstack.org/tc/reference/charter.html [2] https://governance.openstack.org/tc/reference/role-of-the-tc.html [3] https://docs.openstack.org/project-team-guide/ptl.html [4] https://governance.openstack.org/election/#election-officials -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[openstack-helm] Use Loci images by default
by Vladimir Kozhukalov 26 Jan '25

26 Jan '25

Hi, This is to announce multiple things: 1) OpenStack/Loci (a project for building OpenStack images) is currently equipped with periodic jobs that are run nightly. These jobs build images for 3 most recent OpenStack releases: - 2023.2 Bobcat - 2024.1 Caracal - 2024.2 Dalmatian Images are published to these two destinations: - docker.io/loci/* (which is known for its strict request rate limits) - quay.io/airshipit/* (which is much more tolerant to the number of requests) Images are tested before publishing with two basic deployment configurations: - compute-kit (Deploy minimal set of OpenStack components to run VMs) - cinder (Deploy Cinder with Ceph backend) 2) By default we are going to use Loci images published to the Quay registry [1]. All test jobs will be run with these images and this is also a recommendation for users to consume images from quay to mitigate possible rate limit issues. 3) OpenStack/OpenStack-Helm-Images project will build only non-OpenStack images. Primarily the motivation is to deduplicate the code base. Consequently, OpenStack images published nightly to docker.io/openstackhelm/* will not be updated after 2024.2. [1] https://review.opendev.org/c/openstack/openstack-helm/+/939426 -- Best regards, Kozhukalov Vladimir

2 2

Guidance Required for OVN-BGP-Agent Configuration with EVPN Mode
by AkashMadan Talebailkar 26 Jan '25

26 Jan '25

Dear Community, I hope this email finds you well. I came across this insightful discussion on the OpenStack forum regarding the OVN-BGP-Agent Discussio<https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030080.…>n. We are doing research on openstack capability and would greatly appreciate your guidance. We are utilizing the OVN mechanism driver along with the OVN-BGP-Agent<https://github.com/openstack/ovn-bgp-agent/tree/master> in EVPN mode. Our objective is to establish BGP-EVPN between our leaf switch and the OpenStack controller. The OVN-BGP-Agent should advertise the IP and MAC addresses of VMs to its BGP peers. Please find attached the following details for your reference: bgp-agent.conf Agent configuration OVN_DB configuration Result We installed the OVN-BGP-Agent and FRR on the controller. Below are the steps we followed: Network Setup: Created a tenant network (NET) with a subnet of 121.168.0.0/24. Created a provider network (EXNET) with a subnet of 192.27.5.0/24. Router Configuration: Set up a router (newrouter) with an external network (EXNET) and unchecked SNAT. Added the NET interface to the router. OVN Database Configuration: Configured the OVN Northbound DB (detailed in the attachment). VM Creation: Deployed a VM in NET with the VM's IP 121.168.0.202 PFA for the agent configuration and FRR configuration done once agent VM has been created. Despite following the steps above, the VM IP is not visible in FRR, PFA for the result. Consequently, we are unable to advertise its route via BGP-EVPN. We kindly request your guidance to identify any potential misconfigurations or missing steps. Thank you for your time and support. Best regards, Akash Talebailkar Palc Networks akashmadan.t(a)palcnetworks.com +91 9035376555

2 1