September 2024 - openstack-discuss

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-0)
by Goutham Pacha Ravi 30 Sep '24

30 Sep '24

Hello Stackers, After 26 weeks of effort across the community, we're finally at the release week for the 2024.2 release [1], codenamed 'Dalmatian'. I'll cue "Who Let the Dogs Out" for 2024-10-02 and toast the successful delivery of the 30th release of OpenStack with all of you. Congratulations, and thank you for your contributions in making this yet another on-time release. Please tune into the OpenInfra Live episode at 1400 UTC on 2024-10-03 [2], where you'll hear from a few Project Team Leads about the new and exciting things included in this release. Over the past week, the OpenStack TC assisted the release team in tagging a few deliverables, and on its behalf, I'd like to commend the release team for pulling out all the stops to ensure yet another on-time release. It takes a village, as Jeremy Stanley (fungi) noted on IRC — the happy, buzzing Stackerton village. We also merged some governance changes in the meantime. Notably, we adopted a community goal to move all existing Ubuntu testing to the latest LTS [3], and we retired several charms repositories after their consolidation into the Sunbeam-charms project [4]. I am pleased to welcome Dmitriy Rabotyagov (noonedeadpunk) as the Vice Chair for the TC, and I thank the outgoing Vice Chair, Dr. Jens Harbott (frickler), for his contributions during the 2024.2 release cycle. Next week, as we step into the 2025.1 ("Epoxy") release cycle formally [5], we'll switch into PTG and planning mode and chart out the remaining release priorities early. === Weekly Meeting === The Technical Committee's weekly meeting was held over IRC on 2024-09-24 [6]. We began the meeting by welcoming new members and thanking outgoing ones. We appointed a TC Chair (me) and a Vice Chair (noonedeadpunk) for the 2025.1 release cycle. We then worked through several 2024.2 release issues. We were presented with a peculiar, but familiar problem involving release deliverables that couldn't proceed without help from project maintainers who were unavailable during the release crunch. The release team prepares release candidate patches a week before the RC1 deadline and encourages project maintainers to vote on them. They also submit changes to the respective repositories to verify the state of the CI system to prevent releasing broken code. However, when a project team doesn't respond, there's a risk to the coordinated release. We brainstormed strategies to deal with the current conundrum. Thanks to noonedeadpunk and the attentiveness of project maintainers in Zun and Barbican, we were able to fix broken CI jobs and tag release candidates for some projects. However, we couldn't determine the state of "kuryr-kubernetes" and "kuryr-tempest-plugin." These projects, flagged earlier as unmaintained, are expected to be retired soon, so there are no releases from these projects in the 2024.2 release stream. If you depend on these projects, please let us know. We are looking for maintainers who can commit to reviving the CI and furthering these projects. The next OpenStack TC meeting is on 2024-10-01 at 1800 UTC. This meeting will be held simultaneously via video and IRC. Please find the agenda and other meeting details in our meeting wiki [7]. I hope you'll be able to join us. Remember, you can always edit the agenda and propose new topics! === Governance Proposals === ==== Merged ==== - Retire all single charm repositories | https://review.opendev.org/c/openstack/governance/+/903490 - Select community-wide goal: migrate CI/CD jobs to Ubuntu Noble | https://review.opendev.org/c/openstack/governance/+/929703 - Add 2025.1 TC chair and vice-chair | https://review.opendev.org/c/openstack/governance/+/930376 - Add chair nomination folder for 2025.1 | https://review.opendev.org/c/openstack/governance/+/929970 - Add GouthamR nomination for 2025.1 TC chair | https://review.opendev.org/c/openstack/governance/+/929971 ==== Open for Review ==== - Appoint Tim Burke as PTL for Swift | https://review.opendev.org/c/openstack/governance/+/928881 - Add Axel Vanzaghi as PTL for Mistral | https://review.opendev.org/c/openstack/governance/+/927962 - Mark kuryr-kubernetes and kuryr-tempest-plugin as Inactive | https://review.opendev.org/c/openstack/governance/+/929698 - Retire kuryr-kubernetes and kuryr-tempest-plugin | https://review.opendev.org/c/openstack/governance/+/922507 === Upcoming Events === - 2024-10-02: OpenInfra Live - Introducing OpenStack Dalmatian 2024.2 [2] - 2024-10-08: OpenInfra Monthly Board Meeting: https://board.openinfra.dev/ - 2024-10-15: OpenInfra Days NA, Indianapolis: https://ittraining.iu.edu/explore-topics/titles/oid-iu/ - 2024-10-21: OpenInfra Project Teams Gathering https://openinfra.dev/ptg/ === How to Contact the TC === You can reach the TC in several ways: 1. Email: send an email with the tag [tc] on this mailing list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel. 3. Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1800 UTC [7]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2024.2 "Dalmatian" Release Schedule: https://releases.openstack.org/dalmatian/schedule.html [2] Introducing OpenStack Dalmatian 2024.2: https://openinfra.dev/live/ [3] Goal: migrate CI/CD jobs to Ubuntu Noble: https://review.opendev.org/c/openstack/governance/+/929703 [4] Retire all single charm repositories: https://review.opendev.org/c/openstack/governance/+/903490 [5] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [6] TC Meeting IRC Log, 2024-09-24: https://meetings.opendev.org/meetings/tc/2024/tc.2024-09-24-17.59.log.html [7] TC Meeting Agenda, 2024-10-01: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

1 0

Nova placement
by engineer2024 30 Sep '24

30 Sep '24

Is there a way to get back the correct used resources allocation data, in case of loosing the db ? Does placement update the allocation details after restarting the compute nodes to get the latest resources usage for that node ? Thanks elinux

2 2

[neutron] Proposing Ihar Hrachyshka as neutron stable core reviewer
by Brian Haley 30 Sep '24

30 Sep '24

Hello Neutrinos, I would like to nominate Ihar Hrachyshka for Neutron stable core reviewer (again). Ihar previously led the neutron stable core reviewer team a number of years ago, and I think he'd be a great re-addition to the team. Please vote with a +1/-1. Thanks, -Brian, Neutron PTL

6 6

[kolla] Proposing Matt Crees for Kayobe core
by William Szumski 30 Sep '24

30 Sep '24

Greetings Kayobians, I would like to propose Matt Crees as a core reviewer for Kayobe. With Mark Goddard stepping back from Kayobe maintenance duties, we have a slot to fill in the core team. In my opinion, Matt Crees is the strongest candidate for the position, having provided numerous reviews and contributions over the past few cycles. Please register any objections to this decision before the kolla meeting on 25th of September, otherwise I will proceed with making formal arrangements to get him added. Thanks Will Szumski will(a)stackhpc.com

6 6

[neutron] Bug Deputy report Sep 23 - 29th
by Oleg Bondarev 30 Sep '24

30 Sep '24

Hello Team, Nothing critical this week, 3 High bugs need assignees, 1 RFE to review by Drivers team. Full report for the week of Sep 23 is below: High: - https://bugs.launchpad.net/neutron/+bug/2081868 - LoggingDBApiTestCase.test_get_logs_bound_sg fails - Confirmed - unassigned - https://bugs.launchpad.net/neutron/+bug/2081870 - TestProcessMonitor.test_respawn_handler failed - Confirmed - unassigned - https://bugs.launchpad.net/neutron/+bug/2081871 - TestHAL3Agent.test_ha_router failed - Confirmed - unassigned - https://bugs.launchpad.net/neutron/+bug/2081945 - [postgresql] AttributeError: 'NoneType' object has no attribute 'id' - In progress: https://review.opendev.org/c/openstack/neutron/+/930408 - assigned to Rodolfo Alonso Medium: - https://bugs.launchpad.net/neutron/+bug/2082066 - Logging not supported in unmaintained branches - In progress: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/930546 - assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2082070 - [unmaintained] Errors in the "neutron-tempest-plugin-scenario-ovn" job - In progress: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/930548 - assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2082344 - [unmaintained] ``NetworkWritableMtuTest`` test don't work in ML2/OVN - In progress: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/930594 - assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2082880 - [ovn-octavia-provider] config registration hit DuplicateOptError - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/930670 - assigned to Rico Lin Low: - https://bugs.launchpad.net/neutron/+bug/2082883 - neutron-tempest-plugin: KeyError caused by missing 'previous' ref Edit - Confirmed - unassigned RFEs: - https://bugs.launchpad.net/ironic/+bug/2081847 - [RFE] Implement a new DHCP backend for Ironic and Neutron Edit - New - unassigned Thanks, Oleg

1 0

[kolla] [kolla-ansible]
by dariusz.bursztynowski＠pw.edu.pl 30 Sep '24

30 Sep '24

Hello, Are there plans for kolla-ansible to support Ubuntu 24.04 / ARM64 (to have LTS support for Raspberry Pi 5)? Best regards, Dariusz Bursztynowski

4 3

[Openstack] [Keystone] [Shibboleth] Assistance with Configuring Multiple IdPs in DevStack with Shibboleth Integration
by Abubakur Sait 29 Sep '24

29 Sep '24

Hi all, I have installed DevStack (release 2023.2) on Ubuntu 22.04 and integrated Shibboleth (the federation solution) with it. Everything works fine for a single IdP. However, I am looking to expand the setup to support multiple IdPs. I have read the Keystone documentation, but it doesn’t seem to cover this specific case. In my current setup, I have DevStack and Shibboleth integrated for a single IdP. I have read the shib-sp documentation as well. It mentions the need for a Discovery Service (DS) if we intend to use multiple IdPs which will be handled by the shib-SP software. This is the issue I am facing right now. Please see the following comments to get my point. Here’s the scenario I have so far: 1. A user accesses Horizon (Service Provider -- SP) at: http://192.168.4.103/dashboard/auth/login/?next=/dashboard/. 2. A drop-down list allows the user to choose the authentication method. The user selects the SAML IdP method. 3. The user is redirected to the IdP’s page where they authenticate. 4. The user is redirected back to the SP and successfully accesses the system. 5. The issue I’m facing is how to configure multiple IdPs so that users can choose from them at step (2). I understand that we can add a list of IdPs in the ~/horizon/openstack_dashboard/local/local_settings.py file to display in Horizon, but this doesn’t fully resolve the issue since the Shibboleth SP application itself doesn’t seem to handle multiple IdPs. Shibboleth SP typically expects a DS for multiple IdPs, but given that we already have a dropdown list in Horizon, do we still need the DS in this case? If not, how can we proceed with adding multiple IdPs in the system? Any guidance or advice would be greatly appreciated. Thank you for your help! Best regards, Bakur Sait

1 0

[octavia] Lose of some jobs by worker
by Payne Max 28 Sep '24

28 Sep '24

Hi, OpenStack community, I’ve faced a problem when some of our jobs can get lost by a worker, for example from the screenshot, SIGTERM was called in several seconds after receiving a job by a worker. [cid:image001.png@01DB1013.D648A630] Then there were no new log messages related to this job. Then our client complained that LB stucked in PENDING_UPDATE for several days and we started investigation. Our MySQL (persistent storage) is clean, but in our Redis, I can see several jobs without TTL and I think they are related to the «lost» jobs. [cid:image002.png@01DB1014.1DFF1BD0] Is it an ok situation? Can it be related to the https://github.com/openstack/octavia/blob/master/octavia/common/base_taskfl… Let’s discuss it!

4 6

kolla-ansible support for Ubuntu 2024.04/ARM64 ?
by dariusz.bursztynowski＠pw.edu.pl 28 Sep '24

28 Sep '24

Hello, Are there plans for kolla-ansible to support Ubuntu 24.04 / ARM64 (e.g., to have LTS support for Raspberry Pi 5)? Best regards, Dariusz Bursztynowski

1 0

[openstack]Problem with launching instances from VMDK
by Nguyễn Hữu Khôi 27 Sep '24

27 Sep '24

Hello I am trying create instance from vmdk but I have this error: The image format was claimed to be 'vmdk' but the image data appears to be in a different format. My cloud is Openstack 2023.1. This happened when We applied patches for CVE-2024-40767. Nguyen Huu Khoi

3 4