November 2023 - openstack-discuss

[tc] Next Technical Committee Meeting Nov 28 1800 UTC
by Jay Faulkner 27 Nov '23

27 Nov '23

Hi all, The next weekly meeting of the Technical Committee is tomorrow, November 28, at 1800 UTC. It will be held in #openstack-tc in OFTC. Agenda - Roll call - Follow up on tracked action items: https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-07-18.00.html - Rosmaita to propose amendment to unmaintained branch resolution allowing a single review group - Rosmaita to email mailing list about progress implementing unmaintained branch resolution - Gate health check - Leaderless projects (gmann) - Implementation of Unmaintained branch statuses - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - Upgrade issue between tooz and cinder - https://review.opendev.org/c/openstack/requirements/+/901131 - https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… - Declare projects inactive for lack of ...? - Working py311 unit tests - Support for sqla2 - Broken CI since 2023.2 release - Do we want/need to look at specific deliverables or only whole projects? - Open Discussion and Reviews Thanks, Jay Faulkner TC Chair

1 0

[all] North Dakota State University Student Opportunity
by Kendall Nelson 27 Nov '23

27 Nov '23

Hello All! I was contacted by a professor at North Dakota State University wondering if there were projects in OpenStack that students could work on over the course of the coming semester (Jan -May). The students will be nearing the end of their Bachelors degree (this course being one of the final requirements to graduate) so should be relatively knowledgeable and adept and picking up the technologies required if they aren't already versed in them. If you have an idea for a project that you would want to work with a group of students on, please let me know ASAP. I will get you connected with the professor. Project descriptions are due to the professor by December 1st so we only have a couple weeks to get them together. Anyone interested? -Kendall Nelson Senior Upstream Developer Advocate OpenInfra Foundation

1 2

Is "nova-manage db online_data_migrations" cumulative across versions?
by Michel Jouvin 27 Nov '23

27 Nov '23

Hi, We realized that after a Stein -> Train upgrade of our cloud, we forgot to run "nova-manage db online_data_migrations" and did the Train -> Ussuri upgrade. We have not seen any bad side effect but where wondering if the online_data_migrations was cumulative across versions and if running it under Ussuri fixed potential changes related to Stein -> Train upgrade that we forgot to fix right after the Train upgrade. If not, are there things to do to cleanup the situation? Cheers, Michel

2 1

[neutron] Bug Deputy Report Nov 20-26
by Oleg Bondarev 27 Nov '23

27 Nov '23

Hello Neutron Team, Easy week, as usual for me :P 1 bug is undecided, more info requested, others are on track or fixed. Critical ----- - https://bugs.launchpad.net/neutron/+bug/2043959 - Unit test jobs with neutron-lib master(3.9.0) failing - Fix released: https://review.opendev.org/c/openstack/neutron/+/901430 - Fixed by yatinkarel High ----- - https://bugs.launchpad.net/neutron/+bug/2044272 - Inconsistent IGMP configuration across drivers - In progress: https://review.opendev.org/c/openstack/neutron/+/901753 - assigned to lucasagomes Medium ----- - https://bugs.launchpad.net/neutron/+bug/2044171 - External shared networks may not be seen by other projects - Invalid, not relevant for master ( https://review.opendev.org/c/openstack/neutron-lib/+/901565 closed) - handled by libosvar - https://bugs.launchpad.net/neutron/+bug/2044484 - Enabling DHCP after setting the subnet's 'enable_dhcp' to false does not recreate the metadata namespace - In progress https://review.opendev.org/c/openstack/neutron/+/901812 - assigned to huanghailun Undecided ----- - https://bugs.launchpad.net/neutron/+bug/2044215 - dns: Keyword is replaced by project_name instead of project_id - Incomplete, more info requested Thanks, Oleg

1 0

[cinder][kolla][OpenstackAnsible] 2023.2 Bobcat cycle-trailing release deadline
by Elõd Illés 27 Nov '23

27 Nov '23

Hello teams with trailing projects, The 2023.2 Bobcat cycle-trailing release deadline is in ~1 months [1], and all projects following the cycle-trailing release model must release their 2023.2 Bobcat deliverables by December 7th, 2023. The following trailing projects haven't been released yet for 2023.2 Bobcat (aside the release candidates versions if exists). Cinder team's deliverables: - cinderlib OSA team's deliverables: - openstack-ansible-roles - openstack-ansible Kolla team's deliverables: - kayobe - kolla - kolla-ansible - ansible-collection-kolla This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/caracal/schedule.html#c-cycle-trail Thanks, Előd irc: elodilles @ #openstack-release

1 1

[release][puppet] Can we retire old stable branches ?
by Takashi Kajinami 27 Nov '23

27 Nov '23

Hi release team, The puppet-ceph repository in Puppet OpenStack project currently follows the independent release model. This is because the module is more aligned with Ceph releases rather than OpenStack release. In the past, we created a stable branches per Ceph stable release and we currently have the following three stable branches. - stable/jewel - stable/mimic - stable/luminous However we no longer use these branches because the old stable branches (eg train) using these old releases are already EOL. So I'm wondering if someone from the release team can create -eol tag from the latest commits and remove these branches. Ideally we may be able to create a release from the latest commits, but I doublt we can merge any patches cleanly to these ancient branches so I tend to just add -eol tag instead, assuming no one may need releases for these old contents. Thank you, Takashi Kajinami

2 1

[all] [taskflow] asyncore is removed in Python 3.12
by Corey Bryant 27 Nov '23

27 Nov '23

Hi All, As noted in the following bug, taskflow uses asyncore, which is removed in Python 3.12. tasklfow needs to be switched to asyncio as a result. Does anyone happen to be working on this? https://bugs.launchpad.net/ubuntu/+source/python-taskflow/+bug/2024588 Thanks, Corey

5 7

[publiccloud-sig] Reminder - next meeting November 29th - 0800 UTC
by Felix Kronlage-Dammers 27 Nov '23

27 Nov '23

Hi everyone, since we’re switching to even weeks with the publiccloud-sig meeting (as also announced last week[1] in my summary), I’m happy to share the reminder for this weeks meeting :) This Wednesday the next meeting of the public cloud sig is going to happen. We meet on IRC in #openstack-operators at 0800 UTC. See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG felix [1] <url: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…> -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[tripleo] stepping down from TripleO core
by Takashi Kajinami 27 Nov '23

27 Nov '23

Hello, As you might know or notice, I recently joined a different company, and my focus has been changed. I'm still involved in the OpenStack community but I may no longer be involved in TripleO. To clarify my status I've removed myself from TripleO core. # Please be aware that I'm removing myself from release liason, # someone from the core team might want to replace me, though # I don't think there may be multiple releases created in the future. I'd like to thank all members in the team (current members and ex-menmbers) for your great collaboration and work in the project. Thank you, Takashi Kajinami

3 2

[puppet] Proposing EOL of stable/wallaby and xena
by Takashi Kajinami 24 Nov '23

24 Nov '23

Hello, Some of you may know this but currently CentOS 8 Stream integration jobs in stable branches are all broken. I've looked into some of these failures but tasks randomly get stuck which eventually caused timeout and I've not yet found any potential cause. While we may be able to spend some time to dig into the problem, I'm wondering if anyone still requires wallaby and xena which support CentOS 8 Stream. Most of the backports submitted to these old branches were for TripleO,but I've seen some patches indicating TripleO wallaby is being retired so I doubt anyone still need keeping these branches open for backports. Please let me know if you have any concern about the proposed EOL and are interested in fixing these jobs. The stable/yoga branch has already passed the EM phase, so is another candidate for EOL but my intention is to keep it for now and re-consider its EOL early next year. We may have to make all CentOS 8 jobs non-voting, though. (We have CentOS 9 jobs in this branch). Thank you, Takashi Kajinami

2 2