- openstack-discuss - lists.openstack.org

[all][tc][ptl][ptg] TC Discussions at the PTG - Sign Up and Suggest Topics
by Goutham Pacha Ravi 01 Oct '24

01 Oct '24

Hello Stackers, I'd like to highlight the Technical Committee's PTG planning etherpad [1], where we're organizing our discussions for the upcoming PTG. Over the next week, I aim to finalize time slots and prioritize discussion topics. Since TC discussions are cross-project, we'll do our best to avoid scheduling conflicts with project team meetings. To help with this, I encourage all interested parties to sign up or vote on the topics listed in the etherpad. Feel free to add any additional topics you'd like to discuss as well. Thank you! Best regards, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://etherpad.opendev.org/p/oct2024-ptg-os-tc

1 0

[all] [security] [ptls] Please review core security teams
by Jay Faulkner 01 Oct '24

01 Oct '24

Hi all, I'm writing on behalf of the Vulnerability Management Team (VMT). We often use the ${project}-coresec teams to determine who is best to help triage initial issues. These groups do not appear to be universally up to date. If you are in charge of a repo managed by the VMT ( https://security.openstack.org/repos-overseen.html#repositories-overseen ) please ensure the associated launchpad ${project}-coresec group has active, trusted members of your community -- or otherwise reach out to the VMT in #openstack-security to arrange other contacts if needed. For example, https://launchpad.net/~ironic-coresec/+members contains four longtime Ironic cores and former PTLs. (I'll note: I likely need to audit the equivalent group for Ironic-adjacent repos, and will do that after hitting send). This is extremely important! If we can't get an issue triaged and dealt with in time, it gets opened to the public. If there's any questions, feel free to respond here or reach out in #openstack-security on OFTC. Thanks, Jay Faulkner

1 0

[ironic] Postgres CI job broken
by Julia Kreger 01 Oct '24

01 Oct '24

Greetings folks, We had a little bit of a discussion on this subject in #openstack-ironic IRC earlier today[0], but the tl;dr is it appears the postgres integration CI job Ironic has had as a "canary" of support is now failing. This time it appears to be rooted in keystone[1]. Like our prior times of raising awareness, we're sending this email to the mailing list. Given the overall deprecation of postgres support many years ago, and the decline in postgres CI jobs in OpenStack, we believe it is time for us to remove this CI job. That being said, if someone wants such support to be fixed and rejuvenated, please consider this email your call to action. Thanks, -Julia [0]: https://meetings.opendev.org/irclogs/%23openstack-ironic/%23openstack-ironi… [1]: https://7d12977942ed9fbb75e4-56d2480851ef91de1634aa83a3abd804.ssl.cf1.rackc…

2 1

[Kolla-Ansible] [Ironic] Node Deploy Failed with MissingAuthPlugin
by Ali Hussain 01 Oct '24

01 Oct '24

Hi Kolla and Ironic folks, While playing with stable/kolla release to fix the No VIF found error. Looks like adding Readers role to ironic user fixed it. But run into Missing Auth plugin [2] issue while image is being deployed to ironic node. Openstack endpoint list command [1] shows the correct IP of the controller. My question is: 1. Kolla-Ansible needs explicite Ironic keystone configuration in Ironic.conf? Following this link <https://docs.openstack.org/kolla-ansible/yoga/reference/bare-metal/ironic-g…> which does not seems to need any keystone configurations. This issue is observed when 1. --boot-interface redfish-virtual-media 2. --deploy-interface ramdisk 3. --driver-info deploy_iso= 4. -instance-info kernel & ramdisk 2. My passwords.yaml has 1. ironic_database_password: 2. ironic_inspector_database_password: 3. ironic_inspector_keystone_password: 4. ironic_keystone_password: Any suggestions please. Thank you. Ali [1] openstack endpoint list | grep ironic | <ID> | <Region> | ironic-inspector | baremetal-introspection | True | internal | http://<IP>:5050 | | <ID> | <Region> | ironic | baremetal | True | public | http://<IP>:6385 | | <ID> | <Region> | ironic-inspector | baremetal-introspection | True | public | http://<IP>:5050 | | <ID> | <Region> | ironic | baremetal | True | internal | http://<IP>:6385 [2] *Error: *Detected change in error condition on node Node1. Deploy step deploy.deploy failed with MissingAuthPlugin: An auth plugin is required to determine endpoint URL.. An unhandled exception was encountered while aborting. More information may be found in the log file.

2 6

Automating Network VLAN Reconfiguration Post-Bare Metal Provisioning with OpenStack Ironic
by Hajasolo 01 Oct '24

01 Oct '24

Hello OpenStack Community, I am currently working with OpenStack Ironic for provisioning bare metal servers and facing a specific challenge related to network security and automation. I would appreciate any insights or experiences you could share! We use Ironic to provision bare metal servers, which involves utilizing a management VLAN during the PXE boot and initial OS installation process. Post-provisioning, the server’s management interface remains accessible, posing a security risk as it can potentially access the management network. I need to ensure that once a server is provisioned and handed over to a user, it cannot access the management VLAN until it is deprovisioned. 1. How can we automate the process of removing the management VLAN from the server’s network interface post-provisioning to prevent unauthorized access to the management network? 2. Upon server deprovisioning, how can we automatically re-enable the management VLAN to allow for server re-provisioning? 3. Are there any built-in OpenStack tools or common practices within the Ironic or larger OpenStack community to handle such scenarios? Our goal is to maintain a high level of automation and self-service capability in our OpenStack environment while ensuring rigorous network security standards. Solutions that integrate seamlessly with OpenStack’s existing architecture would be ideal. Thank you for your time and help! Best regards, Haja, Joel

2 1

[largescale-sig] Next meeting: September 18, 9utc
by Thierry Carrez 01 Oct '24

01 Oct '24

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=20240918T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

3 3

[Glance] Weekly Meeting Cancelled (OCT 3)
by Pranali Deore 30 Sep '24

30 Sep '24

Hi All, As discussed during last week's meeting[1], the meeting for 3rd OCT has been cancelled. See you all next week!! [1]: https://meetings.opendev.org/irclogs/%23openstack-meeting/%23openstack-meet… Thanks, Pranali

1 0

[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