November 2023 - openstack-discuss

[magnum] Weekly Meeting Cancelled - 29 Nov 2023
by Jake Yip 29 Nov '23

29 Nov '23

Hi all, Apologies for cancelling this week's meeting due to a clash. If you have a discussion topic, please add them to the agenda, and we will get to them next week. Regard, Jake

1 0

A questionnaire for unmaintained package users
by smoncaff＠gmail.com 29 Nov '23

29 Nov '23

1 0

Re: [Heat][requirements] Possible feature backport to stable branches
by Martin Magr 28 Nov '23

28 Nov '23

On Mon, Nov 13, 2023 at 4:50 PM Martin Magr <mmagr(a)redhat.com> wrote: > Adding more folks from requirements core to CC. > And also correct mailing list. I'm sorry for the noise. > > On Mon, Nov 13, 2023 at 4:32 PM Martin Magr <mmagr(a)redhat.com> wrote: > >> Greetings, >> >> we have introduced new feature to Aodh [1][2] (which introduced new >> dependency [3]) and Heat [4] recently. >> The changes to both projects are relatively small, it just added >> new respective resources and did not change >> existing logic. Also the new dependency is providing functionality to >> those new resources. >> >> We are building our product on stable/antelope and so ideal state for us >> would be to have those changes >> included in this branch also on upstream side. I'm aware that Heat >> follows stable branch policy and it's written >> in requirements documentation, that new dependency cannot be added in >> stable ranches, but before we are >> going to start building workarounds on this I'd like to ask if there is >> any chance of getting exception >> (given the fact that changes are pretty safe) on backporting the Heat >> patch down to stable/antelope >> and(or at least) including the new dependency in stable/antelope. >> >> Thanks for answer in advance, >> Martin >> >> [1] https://review.opendev.org/c/openstack/aodh/+/890529 >> [2] https://review.opendev.org/c/openstack/python-aodhclient/+/893319 >> [3] https://review.opendev.org/c/openstack/requirements/+/891291 >> [4] https://review.opendev.org/c/openstack/heat/+/893673 >> >> -- >> Martin Mágr >> Principal Software Engineer - Service Telemetry Framework >> Red Hat Czech >> > > -- Martin

5 6

[largescale-sig] Next meeting: Nov. 29, at 16UTC
by Kristin Barrientos 27 Nov '23

27 Nov '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 16UTC. Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[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