December 2022 - openstack-discuss

[ironic][release] Bugfix branch status and cleanup w/r/t zuul-config-errors
by Jay Faulkner 08 Dec '22

08 Dec '22

Hey all, I've been looking into the various zuul config errors showing up for Ironic-program branches. Almost all of our old bugfix branches are in the list. Additionally, not properly retiring the bugfix branches leads to an ever-growing list of branches which makes it a lot more difficult, for contributors and operators alike, to tell which ones are currently supported. I've put together a document describing the situation as it is now, and my proposal: https://etherpad.opendev.org/p/IronicBugfixBranchCleanup Essentially, I think we need to: - identify bugfix branches to cleanup (I've done this in the above etherpad, but some of the ) - clean them up (the next step) - update Ironic policy to set a regular cadence for when to retire bugfix branches, and encode the process for doing so This means there are two overall questions to answer in this email: 1) Mechanically, what's the process for doing this? I don't believe the existing release tooling will be useful for this, but I'm not 100% sure. I've pulled (in the above etherpad and a local spreadsheet) the last SHA for each branch; so we should be able to EOL these branches similarly to how we EOL stable branches; except manually instead of with tooling. Who is going to do this work? (I'd prefer releases team continue to hold the keys to do this; but I understand if you don't want to take on this manual work). 2) What's the pattern for Ironic to adopt regarding these branches? We just need to write down the expected lifecycle and enforce it -- so we prevent being this deep into "branch debt" in the future. What do folks think? - Jay Faulkner

4 6

[ironic][stable] Cleanup of clerical issues in ironic-stable-maint group
by Jay Faulkner 08 Dec '22

08 Dec '22

Hey all, I was looking over Ironic ACLs in Gerrit today, and I discovered the ironic-stable-maint group which is set to include ironic-core and stable-maint-core (as expected) -- but I also discovered a member in this list who is no longer a core reviewer, or active contributor to Ironic (Jim Rollenhagen). Lucky for us, Jim is a nice guy and we all trust him, and this access hasn't been used. In order to prevent this from happening in the future, I've removed all individual members from the ironic-stable-maint group and left it inheriting from ironic-core. The effective difference is just that Jim has been removed. tl;dr: The effective ironic-stable-maint core group has been dropped by one; Jim Rollenhagen was mistakenly left in the list. Thanks, Jay Faulkner

1 0

[Manila] S-RBAC Hack-a-thon
by Liron Kuchlani 07 Dec '22

07 Dec '22

Hi everyone, We are planning a Hack-a-thon for secure RBAC between Wed 12/07 to Thur 12/08 with Fri 12/09 as needed for code reviews. The session will take place between 15:00 UTC and 15:30 UTC. Join meeting: https://bluejeans.com/8520212381 Please find below helpful references and links, Openstack S-RBAC docs [0] Manila-tempest-plugin S-RBAC tests [1] S-RBAC collab review [2] Manila Secure RBAC Antelope PTG etherpad [3] Openstack Shared File Systems API documentation [4] S-RBAC code reviews [5] S-RBAC Kanban [6] [0] https://docs.openstack.org/patrole/latest/rbac-overview.html [1] https://github.com/openstack/manila-tempest-plugin/tree/master/manila_tempe… [2] https://etherpad.opendev.org/p/Manila-S-RBAC-collaborative-review [3] https://etherpad.opendev.org/p/antelope-ptg-manila-srbac [4] https://docs.openstack.org/api-ref/shared-file-system [5] https://review.opendev.org/q/topic:secure-rbac+project:openstack/manila-tem… [6] https://tree.taiga.io/project/silvacarloss-manila-tempest-plugin-rbac/kanban Hope you can all join us, -- Thanks, Liron

1 1

[largescale-sig] Next meeting: Dec 7, 15utc
by Thierry Carrez 07 Dec '22

07 Dec '22

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

1 1

[Horizon] How to enforce particular language on login
by A Tom 07 Dec '22

07 Dec '22

Hi everyone, I have a question regarding languages in Horizon - is there any way to enforce different language for different users - I mean without user interaction. Like user account is created and since then the default language for the user is set. Can it be done via Horizon API/config? Or maybe as Domain/Project properties? And second question - what about two different Horizons to one openstack? I mean every resorces are the same, but first Horizon has FQDN X-company.YY and is branded with X-company logo, and the other one has FQDN Y-company.ZZ and is branded wit Y-company logo - is such setup possible/right? OR maybe also two domains should be used? Best regards Adam Tomas

1 0

[cinder] Bug Report from 12-07-2022
by Sofia Enriquez 07 Dec '22

07 Dec '22

This is a bug report from 11-30-2022 to 12-07-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025028 "[Debian] python-cinderclient: (autopkgtest) needs update for python3.11: conflicting subparser: another-fake-action." - https://bugs.launchpad.net/cinder/+bug/1998083 "volume_attachement entries are not getting deleted from DB." Unassigned. Marked as duplicate - https://bugs.launchpad.net/cinder/+bug/1998369 "[NFS] Creating an encrypted volume from an image overwrites the volume file with a broken symlink." Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[mistral] Mistral maintenance and PTL
by Axel Vanzaghi 07 Dec '22

07 Dec '22

Hello everyone, Let me introduce myself, Axel Vanzaghi, first used OpenStack in 2015 and got back to it when I joined OVHCloud as SRE. Here at OVHCloud, we make an intensive use of Mistral in our internals processes, so we don't want to see it going deprecated [1] or abandonned. We decided to take action to maintain it, first by proposing someone to be the PTL for Mistral [2]. I proposed myself for this role. Yet, my experience with Mistral is only being an user of it, I worked on some of our workflow. However, I really liked what we could do with the tool so I'm willing to learn more and contribute on this project as I will be able to have time for it. Our first goal is to maintain the project alive, but new features will still be welcomed. Regards, Axel Vanzaghi [1] https://review.opendev.org/c/openstack/governance/+/866562 [2] https://lists.openstack.org/pipermail/openstack-discuss/2021-February/02015…

1 0

[neutron] Issue during the EOL of Queens, Rocky and Stein branches
by Rodolfo Alonso Hernandez 07 Dec '22

07 Dec '22

Hello all: In [1], the Neutron team transitioned all projects to EOL. However, because of a loose patch merged after the branch freeze, the automated tools can't finish the EOL task. Yesterday, during the Neutron team meeting [3], the attendants agreed to skip this last patch (that changes one line in the documentation) and comment on the affected stable release patches. This mail is to confirm that and to ask the QA team to manually perform this action. We'll be more careful in the future. Regards. [1]https://review.opendev.org/c/openstack/releases/+/862937 [2]https://review.opendev.org/q/Ie8dd684a7b79b0a322b1f2d17fffb4d58cfe94fc [3] https://meetings.opendev.org/meetings/networking/2022/networking.2022-12-06…

1 0

[heat][release] Proposing to EOL Rocky and Stein
by Brendan Shephard 07 Dec '22

07 Dec '22

Hi, We were discussing some of the older branches we have and thought it was about time we start moving some of them to EOL. Initially, I would like to move Rocky and Stein to EOL and have done so here: https://review.opendev.org/c/openstack/releases/+/866135 We would also like to move Train to EOL as well, pending a few changes being merged. I wanted to reach out and ensure there is no objections here to any of these branches being EOL’d. Feel free to voice any concerns, otherwise I will move forward with that next week. Cheers, Brendan Shephard Senior Software Engineer Red Hat Australia

2 1

[all][tc] Technical Committee next weekly meeting on 2022 Dec 7 at 1600 UTC
by Ghanshyam Mann 07 Dec '22

07 Dec '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Dec 7, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Dec 6 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1