December 2022 - openstack-discuss

[Magnum] Technology and Ubuntu Driver.
by Nguyễn Hữu Khôi 11 Dec '22

11 Dec '22

Hello guys, Can you tell me which tools Magnum used to build the k8s cluster. I do a lot of research but I still have not figured it out. And one more thing, Why it does not support Ubuntu Distro? Thank you. Nguyen Huu Khoi

3 5

Re: [cinder] Problem with restoring purestorage volume backup
by Ришат Азизов 10 Dec '22

10 Dec '22

Hello, Thanks. We use cinder 18.2.0-1 Wallaby. Can we use this patch? Or does it need to be improved? сб, 10 дек. 2022 г. в 17:54, Ришат Азизов <rishat.azizov(a)gmail.com>: > Hello, > > Thanks. We use cinder 18.2.0-1 Wallaby. Can we use this patch? Or does it > need to be improved? > > ср, 26 окт. 2022 г. в 23:12, Sofia Enriquez <senrique(a)redhat.com>: > >> Hello, >> This is a major bug in Cinder that has been reported. Please check >> https://launchpad.net/bugs/1895035. >> The bug has a fix proposed to master to haven't merged yet [2]. >> I'll mention it again in next week's Cinder meeting. >> Regards, >> Sofia >> [2] https://review.opendev.org/c/openstack/cinder/+/750782 >> >> On Wed, Oct 26, 2022 at 9:45 AM Ришат Азизов <rishat.azizov(a)gmail.com> >> wrote: >> >>> Hello! >>> >>> We have a problem with cinder-backup with cephbackup driver and volume >>> on purestorage. When backing up purestorage volume with cinder-backup with >>> cephbackup driver it creates in ceph pool and everything is ok. But >>> when we try to restore the backup, it is not restored with an error >>> "rbd.ImageNotFound" in the screenshot attached to this email. This happens >>> because the original image is not in rbd, it is in purestorage. It is >>> not clear why the cinder is trying to look for a disk in the ceph. Could >>> you please help with this? >>> >>> Thanks. Regards. >>> >> >> >> -- >> >> 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> >> >>

2 1

openstack 504 error
by fereshteh loghmani 10 Dec '22

10 Dec '22

hello i use Kolla ansible multi-region. in one of my regions that is not keystone and hypervisor on it. some times I receive the error Gateway Timeout. how could i solve this problem? thanks is advance. Gateway Timeout The gateway did not receive a timely response from the upstream server or application.

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Dec 09: Reading: 5 min
by Ghanshyam Mann 10 Dec '22

10 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Dec 7. Most of the meeting discussions are summarized in this email. Meeting recording and summary logs are available @ https://www.youtube.com/watch?v=JQYzoJV35Xw @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-07-16.00.log.html * Next TC weekly meeting will be on Dec 14 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Dec 13. 2. What we completed this week: ========================= * Technical Election changes: extending the period for nomination and voting to two weeks You might have observed in elections that a lot of candidates miss the nomination deadline. To improve the situation, TC discussed it in the election retrospective in PTG and decided to extend the nomination and the voting period to two weeks. This has been updated in the TC charter[2]. This change will be applicable from the next (2023.2 cycles) technical elections. Another update to the next elections is that ianychoi and tonyb will be serving as election officials[3]. Thanks to both to volunteer for it. * Added Adjutant to inactive project list[4] Dale Smith (current PTL) is in sync with this and already started working on the pending things to mark it Active. For example, he fixed the gate[5]. * Added the infinidat-tools subordinate charm to OpenStack charms[6] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[7]. Open Reviews ----------------- * Two open reviews for ongoing activities[8]. Change in Inactive project timeline ----------------------------------------- While proposing the Adjutant project in the Inactive list, the release team pointed out that we should have the final list of deliverables to release by milestone 2 instead of the final release time. This is a valid point and TC is reflecting the same in Inactive project timeline where TC will take the final decision on inactive projects to move back to active again and consider for release by milestone 2. The change in TC documentation is up for review[9] Mistral release and more maintainers ------------------------------------------- The release team identified the Mistral needs more work to be considered for release and proposing to mark Mistral release deprecated [10]. The good thing is that there are more volunteers from OVHcloud to help maintain it[11]. TC will monitor the situation and decide on the Mistral release before milestone 2. Renovate translation SIG i18 ---------------------------------- * Brian on behalf of TC presented it in the Board meeting on Dec 6th and the budget for the Weblate tool license seems ok but we still need an engineer to do the translation migration and maintenance. Here is the proposal discussed in the Board meeting[12] Project updates ------------------- * None 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://review.opendev.org/c/openstack/governance/+/865367 [3] https://governance.openstack.org/election/#election-officials [4] https://review.opendev.org/c/openstack/governance/+/849153 [5] https://review.opendev.org/c/openstack/adjutant/+/866823 [6] https://review.opendev.org/c/openstack/governance/+/864067 [7] https://etherpad.opendev.org/p/tc-2023.1-tracker [8] https://review.opendev.org/q/projects:openstack/governance+status:open [9] https://review.opendev.org/c/openstack/governance/+/867062 [10] https://review.opendev.org/c/openstack/governance/+/866562 [11] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03142… [12] https://docs.google.com/document/d/1PwGASync8blZoFOlqaIe3xwJkOc1iByHKVbGDTb… [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-14, Dec 12 - 16
by Elõd Illés 10 Dec '22

10 Dec '22

Development Focus ----------------- The Antelope-2 milestone will happen next month, on January 5th, 2023. 2023.1 Antelope-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/antelope/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. (Note: cycle-with-rc release model does not suit for every project) At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/antel… You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/antelope/schedule.html#a-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Antelope-2 Milestone: January 5th, 2023 Final 2023.1 Antelope release: March 22nd, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[gate][stable][qa] Hold recheck: Devstack based job using tox4 are broken (especially greande, stable jobs)
by Ghanshyam Mann 10 Dec '22

10 Dec '22

Hi All, As you might know, the devstack-based job fails on the tempest command with the below error: Error- venv: failed with tempest is not allowed, use allowlist_externals to allow it It is failing where jobs are using the tox4 (in grenade job or stable branch job or some master branch job like focal job using tox4[1]). This is another issue of mix match of tox version in stable and master jobs which we are discussing in a separate thread[2]. On tempest command or allowlist_externals failure, we are testing one fix for that but please hold recheck until it gets fixed or any workaround is merged - https://review.opendev.org/q/Ifc8fc6cd7aebda147043a52d6baf99a2bacc009c I have opened a bug also to track it https://bugs.launchpad.net/devstack/+bug/1999183 [1] https://zuul.opendev.org/t/openstack/build/aaad7312f68246c0979e1a43cfe96c3b… [2] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03144… -gmann

1 1

[sahara][sahara-cores] Combined patch that recovers CI tests
by Dmitriy Rabotyagov 09 Dec '22

09 Dec '22

Hi sahara cores, As you might know Sahara has been broken for quite some time now due to multiple reasons, and didn't have passing tests for Zed release at all. I have come up with a patch [1] that fixes major issues, including: * Zuul Queus definition * Adapting new jsonschema version * Replacing usage of iteritems with six As a result Zuul is happy, all tempest and tox tests are passing it the moment. It would be great if you could review these changes and land other important patches to unblock other contributors in the project and prevent it from falling under "inactive" projects list. [1] https://review.opendev.org/c/openstack/sahara/+/864728

1 0

[neutron] Drivers meeting cancelled
by Rodolfo Alonso Hernandez 09 Dec '22

09 Dec '22

Hello Neutrinos: Due to the lack of agenda, today's meeting is cancelled. If you want to add any topic to this meeting, please check [1] and use the "on demand agenda" section. Regards. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

the zun cmd "python3 setup.py install" error(s)
by 无数的星球 09 Dec '22

09 Dec '22

system:ubuntu:20.04 useDocumentation:https://docs.openstack.org/zun/zed/install/controller-inst… root@controller:/var/lib/zun/zun# python3 setup.py install ERROR:root:Error parsing Traceback (most recent call last):   File "/usr/lib/python3/dist-packages/pbr/core.py", line 96, in pbr     attrs = util.cfg_to_args(path, dist.script_args)   File "/usr/lib/python3/dist-packages/pbr/util.py", line 271, in cfg_to_args     pbr.hooks.setup_hook(config)   File "/usr/lib/python3/dist-packages/pbr/hooks/__init__.py", line 25, in setup_hook     metadata_config.run()   File "/usr/lib/python3/dist-packages/pbr/hooks/base.py", line 27, in run     self.hook()   File "/usr/lib/python3/dist-packages/pbr/hooks/metadata.py", line 25, in hook     self.config['version'] = packaging.get_version(   File "/usr/lib/python3/dist-packages/pbr/packaging.py", line 874, in get_version     raise Exception("Versioning for this project requires either an sdist" Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name zun was given, but was not able to be found. error in setup command: Error parsing /var/lib/zun/zun/setup.cfg: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name zun was given, but was not able to be found. root@controller:/var/lib/zun/zun# cryed: pip3 install --upgrade distribute pip3 install --upgrade tensorflow_gpu

3 2

Issue resizing volumes attached to running volume backed instances
by Jérôme BECOT 09 Dec '22

09 Dec '22

Hello Openstack, We have Ussuri deployed on a few clouds, and they're all plugged to PureStorage Arrays. We allow users to only use volumes for their servers. It means that each server disk is a LUN attached over ISCSI (with multipath) on the compute node hosting the server. Everything works quite fine, but we have a weird issue when extending volumes attached to running instances. The guests notice the new disk size .. of the last extent. Say I have a server with a 10gb disk. I add 5gb. On the guest, still 10gb. I add another 5gb, and on the guest I get 15, and so on. I've turned the debug mode on and I could see no error in the log. Looking closer at the log I could catch the culprit: 2022-12-08 17:35:13.998 46195 DEBUG os_brick.initiator.linuxscsi [] Starting size: *76235669504* 2022-12-08 17:35:14.028 46195 DEBUG os_brick.initiator.linuxscsi [] volume size after scsi device rescan *80530636800* extend_volume 2022-12-08 17:35:14.035 46195 DEBUG os_brick.initiator.linuxscsi [] Volume device info = {'device': '/dev/disk/by-path/ip-1...1:3260-iscsi-iqn.2010-06.com.purestorage:flasharray.x-lun-10', 'host': '5', 'channel': '0', 'id': '0', 'lun': '10'} extend_volume 2022-12-08 17:35:14.348 46195 INFO os_brick.initiator.linuxscsi [] Find Multipath device file for volume WWN 3624... 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] Checking to see if /dev/disk/by-id/dm-uuid-mpath-3624.. exists yet. wait_for_path 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] /dev/disk/by-id/dm-uuid-mpath-3624... has shown up. wait_for_path 2022-12-08 17:35:14.382 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *current size 76235669504* 2022-12-08 17:35:14.412 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *new size 76235669504* 2022-12-08 17:35:14.413 46195 DEBUG oslo_concurrency.lockutils [] Lock "extend_volume" released by "os_brick.initiator.connectors.iscsi.ISCSIConnector.extend_volume" :: held 2.062s inner 2022-12-08 17:35:14.459 46195 DEBUG os_brick.initiator.connectors.iscsi [] <== extend_volume: return (2217ms) *76235669504* trace_logging_wrapper 2022-12-08 17:35:14.461 46195 DEBUG nova.virt.libvirt.volume.iscsi [] Extend iSCSI Volume /dev/dm-28; new_size=*76235669504* extend_volume 2022-12-08 17:35:14.462 46195 DEBUG nova.virt.libvirt.driver [] Resizing target device /dev/dm-28 to *76235669504* _resize_attached_volume The logs clearly shows that the rescan confirm the new size but when interrogating multipath, it does not. But requesting multipath few seconds after on the command line shows the new size as well. It explains the behaviour. I'm running Ubuntu 18.04 with multipath 0.7.4-2ubuntu3.2. The os-brick code for multipath is far more basic than the one in master branch. Maybe the multipath version installed is too recent for os-brick. Thanks for the help Jerome

1 0

(PXE FAILURE)using dnsmasq
by Adivya Singh 08 Dec '22

08 Dec '22

Hi Team. i m trying to setup PXE using dnsmasq, it fails on "Address listen on port 53" but i don't see any IP address listen on this port This IP 10.128.244.2 in the interface IP of the Infrastructure server where PXE is ported named as eno2 my dnsmasq.conf looks like this, All other setting are as per PXE configuration a default file under pxelinux.cfg and a installer in default, and a user-data file under the /var/www/html no-resolv interface=eno2 listen-address=10.128.244.2 dhcp-range=10.128.244.102,10.128.244.110,6h dhcp-boot=pxelinux/pxelinux.0 enable-tftp tftp-root=/var/lib/tftpboot Anyone having any idea on this error Regards Adivya Singh

2 1

[IRC Client] [Setup in Macbook] Best Practice to follow
by Rajesh Gunasekaran 08 Dec '22

08 Dec '22

Hello Team, I am really struggling with setting up the OpenStack IRC client in my new macbook pro! I made the switch from Windows to MAC recently. Could someone please advise what is the best practice I should follow to stay connected with #openstack community channels! in IRC while using mac -- Thanks, Rajesh

3 3

[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 08 Dec '22

08 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 08 Dec '22

08 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

[openstack-ansible] Meetings on December 27 and January 3 cancelled
by Dmitriy Rabotyagov 07 Dec '22

07 Dec '22

Hi folks, During today's meeting we have agreed on cancelling our regular weekly meetings on December 27 2022 and January 3 2022. We still have meetings on December 13 and December 20 before this small break.

1 0

[openstack-ansible] CI is broken - hold on rechecks
by Dmitriy Rabotyagov 07 Dec '22

07 Dec '22

Hi folks, After merging [1] all our CI tests seem broken until we merge [2], so please hold on all your rechecks. With that being said, we need to focus on landing 862924 or merge temporary workaround to the integrated repo to define neutron_ml2_drivers_type and neutron_plugin_base for other checks to pass without [2]. [1] https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/865961 [2] https://review.opendev.org/c/openstack/openstack-ansible/+/862924

1 1

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 06 Dec '22

06 Dec '22

Hi everyone, Tomorrow it's time again for our bi-weekly meeting, 0800 UTC in #openstack-operators. Etherpad can be found here [0]. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0