- openstack-discuss - lists.openstack.org

[tc][all] Technical Committee Weekly Summary -- May 5, 2023
by Nikolla, Kristi 08 May '23

08 May '23

Hi all, Here’s another edition of “What’s happening on the Technical Committee.” Meeting ======= The Technical Committee met on May 2, 2023 on the Zoom. A recording of the meeting can be found on Youtube at https://youtu.be/e-IUZ1ymi_A The next meeting will be held on May 9, 2023 at 18:00UTC. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Happenings ========== Adding Python 3.8 to PTI and expectation of Python support ---------------------------------------------------------- Based on the TC discussion during the last weekly meeting, the TC proposed a change adding Python 3.8 as a PTI requirement for libraries[0] and a proposal attempting to clarify which Python versions we should aim to support in general[1]. [0]. https://review.opendev.org/c/openstack/governance/+/882165 [1]. https://review.opendev.org/c/openstack/governance/+/882154 Changes ======= • Merged • Align release naming terminology (documentation-change) | https://review.opendev.org/c/openstack/governance/+/881706 • Appoint Jerry Zhou as Sahara PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881186 • Retire puppet-rally - Step 3: Retire Repository (project-update) | https://review.opendev.org/c/openstack/governance/+/880018 • New Open • Appoint Dmitriy Rabotyagov as Vitrage PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882139 • Appoint Hasan Acar as Monasca PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882374 • Add py38 as a PTI requirement for libraries (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882165 • Clarify expectations on keeping Python versions (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882154 • Abandoned • All Open • https://review.opendev.org/q/project:openstack/governance+status:open 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 an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.

1 0

[Nova] Clean up dead vms entries from DB
by Satish Patel 07 May '23

07 May '23

Folks, I have a small environment where controllers and computers run on the same nodes and yes that is a bad idea. But now what happened the machine got OOM out and crashed and stuck somewhere in Zombie stat. I have deleted all vms but it didn't work. Later I used the "virsh destroy" command to delete those vms and everything recovered but my openstack hypervisor state show" command still says you have 91 VMs hanging in DB. How do i clean up vms entered from nova DB which doesn't exist at all. I have tried the command "nova-manage db archive_deleted_rows" but it didn't help. How does nova sync DB with current stat? # openstack hypervisor stats show This command is deprecated. +----------------------+--------+ | Field | Value | +----------------------+--------+ | count | 3 | | current_workload | 11 | | disk_available_least | 15452 | | free_disk_gb | 48375 | | free_ram_mb | 192464 | | local_gb | 50286 | | local_gb_used | 1911 | | memory_mb | 386570 | | memory_mb_used | 194106 | | running_vms | 91 | | vcpus | 144 | | vcpus_used | 184 | +----------------------+--------+ Technically I have only single VM # openstack server list --all +--------------------------------------+---------+--------+---------------------------------+------------+----------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+---------+--------+---------------------------------+------------+----------+ | b33fd79d-2b90-41dd-a070-29f92ce205e7 | foo1 | ACTIVE | 1=100.100.75.22, 192.168.1.139 | ubuntu2204 | m1.small | +--------------------------------------+---------+--------+---------------------------------+------------+----------+

2 1

Re: openstack-discuss Digest, Vol 55, Issue 17
by BEDDA Fadhel 07 May '23

07 May '23

Good morning, I set up openstack, on an Ubuntu 22.04 VM. Installation went well: I created an account and a project, as well as all the steps for creating an Ubuntu 18 instance. But when launching the instance, I only have error messages. My question: Is there someone who can help me and provide me with a procedure complete and tested. With my sincere thanks Le sam. 6 mai 2023 à 10:21, <openstack-discuss-request(a)lists.openstack.org> a écrit : > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. [Nova] Clean up dead vms entries from DB (Satish Patel) > 2. [OPENSTACK][rabbitmq] using quorum queues (Nguy?n H?u Kh?i) > 3. Re: openstack-discuss Digest, Vol 55, Issue 16 (BEDDA Fadhel) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 May 2023 15:14:18 -0400 > From: Satish Patel <satish.txt(a)gmail.com> > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: [Nova] Clean up dead vms entries from DB > Message-ID: > <CAPgF-fqVSj3YKx7cYSF3gzAbL54veXM= > S18K5-sX6XMCbjTWKA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Folks, > > I have a small environment where controllers and computers run on the same > nodes and yes that is a bad idea. But now what happened the machine got OOM > out and crashed and stuck somewhere in Zombie stat. I have deleted all vms > but it didn't work. Later I used the "virsh destroy" command to delete > those vms and everything recovered but my openstack hypervisor state show" > command still says you have 91 VMs hanging in DB. > > How do i clean up vms entered from nova DB which doesn't exist at all. > > I have tried the command "nova-manage db archive_deleted_rows" but it > didn't help. How does nova sync DB with current stat? > > # openstack hypervisor stats show > This command is deprecated. > +----------------------+--------+ > | Field | Value | > +----------------------+--------+ > | count | 3 | > | current_workload | 11 | > | disk_available_least | 15452 | > | free_disk_gb | 48375 | > | free_ram_mb | 192464 | > | local_gb | 50286 | > | local_gb_used | 1911 | > | memory_mb | 386570 | > | memory_mb_used | 194106 | > | running_vms | 91 | > | vcpus | 144 | > | vcpus_used | 184 | > +----------------------+--------+ > > > Technically I have only single VM > > # openstack server list --all > > +--------------------------------------+---------+--------+---------------------------------+------------+----------+ > | ID | Name | Status | Networks > | Image | Flavor | > > +--------------------------------------+---------+--------+---------------------------------+------------+----------+ > | b33fd79d-2b90-41dd-a070-29f92ce205e7 | foo1 | ACTIVE | 1=100.100.75.22, > 192.168.1.139 | ubuntu2204 | m1.small | > > +--------------------------------------+---------+--------+---------------------------------+------------+----------+ >

2 1

Re: openstack-discuss Digest, Vol 55, Issue 16
by BEDDA Fadhel 06 May '23

06 May '23

Bonjour, J’ai mis en place openstack, sur une VM Ubuntu 22.04. L’installation s’est bien passé: J’ai créé un compte et un projet, ainsi que toute les étapes pour la création d’une instance Ubuntu 18. Mais lors de lancement de l’instance, je n’ai que des messages d’erreur. Ma question: Est ce qu’il y’a quelqu’un qui peut m’aider et me fournir une procédure complète et testée. Avec mes vifs remerciements Le ven. 5 mai 2023 à 20:09, <openstack-discuss-request(a)lists.openstack.org> a écrit : > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. [release] Release countdown for week R-21, May 08-12 (El?d Ill?s) > 2. Re: Kubernetes Conformance 1.24 + 1.25 (Guilherme Steinm?ller) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 May 2023 14:30:58 +0000 > From: El?d Ill?s <elod.illes(a)est.tech> > To: "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: [release] Release countdown for week R-21, May 08-12 > Message-ID: > < > VI1P18901MB07511B14C9655567C4A5EC88FF729(a)VI1P18901MB0751.EURP189.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="utf-8" > > Development Focus > ----------------- > > The Bobcat-1 milestone is next week, on May 11th, 2023! Project team > plans for the 2023.2 Bobcat cycle should now be solidified. > > General Information > ------------------- > > Libraries need to be released at least once per milestone period. Next > week, the release team will propose releases for any library which had > changes but has not been otherwise released since the 2023.1 Antelope > release. > PTLs or release liaisons, please watch for these and give a +1 to > acknowledge them. If there is some reason to hold off on a release, let > us know that as well, by posting a -1. If we do not hear anything at all > by the end of the week, we will assume things are OK to proceed. > > NB: If one of your libraries is still releasing 0.x versions, start > thinking about when it will be appropriate to do a 1.0 version. The > version number does signal the state, real or perceived, of the library, > so we strongly encourage going to a full major version once things are > in a good and usable state. > > Upcoming Deadlines & Dates > -------------------------- > > Bobcat-1 milestone: May 11th, 2023 > OpenInfra Summit Vancouver (including PTG): June 13-15, 2023 > Final 2023.2 Bobcat release: October 4th, 2023 > > > El?d Ill?s > irc: elodilles @ #openstack-release >

1 0

[release] Release countdown for week R-21, May 08-12
by Elõd Illés 05 May '23

05 May '23

Development Focus ----------------- The Bobcat-1 milestone is next week, on May 11th, 2023! Project team plans for the 2023.2 Bobcat cycle should now be solidified. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the 2023.1 Antelope release. PTLs or release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Bobcat-1 milestone: May 11th, 2023 OpenInfra Summit Vancouver (including PTG): June 13-15, 2023 Final 2023.2 Bobcat release: October 4th, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron] Drivers meeting cancelled today
by Rodolfo Alonso Hernandez 05 May '23

05 May '23

Hello Neutrinos: Due to the lack of agenda [1], today's drivers meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[dev][ceilometer] Add custom uptime metric to Ceilometer
by Angel Santana 04 May '23

04 May '23

Guys, I deployed Ceilometer into my OpenStack deployment using the Juju charm. I’m trying to add a custom metric that records the uptime of instances every hour. I’m totally lost on how to archive this or if it’s possible. Any help would be appreciate. So far I tried playing around with the meters.yaml and polling.yaml to see if I could pull it off with no luck. Is this possible? how should I do it? Thanks in advance. Regards, Ángel

3 2

Certbot auto renew
by Derek O keeffe 04 May '23

04 May '23

Hi all, We're having a problem with renewing letsencrypt certs via certbot in an external Neutron network where a security group is locking down HTTP+HTTPS access to select IP ranges. As far as we know the IP address for the Certbot ACME challenge server is always changing and therefore a static security group can't be set up to allow in traffic from that server. We have experimented with using UFW rules instead thinking we may be able to write a script to open port 80 periodically to allow the ACME challenge through, then close it back up, but it hasn't worked as we'd hoped either (either all traffic is blocked or the security group immediately takes precedence). Is there any way to programmatically enable + disable a security group as needed using something like OpenstackSDK to achieve the same thing? Thanks in advance. Regards,Derek

3 3

[openstack-ansible] Proposing Neil Hanlon for core reviewer
by Dmitriy Rabotyagov 04 May '23

04 May '23

Hi everyone, I'm pleased to propose Neil Hanlon as OpenStack-Ansible Core Reviewer. Neil has helped us a lot lately with maintenance of RHEL-like distros - both CentOS Stream and Rocky Linux, and basically has brought in support for the last one. Neil is present at meetings and always is responsive in IRC. At the same time they were providing useful reviews lately [1] If there are no objections, I will add Neil to the team on 25th of April 2023. Until then, please feel free to provide your feedback/opinions on the matter. [1] https://www.stackalytics.io/report/contribution?module=openstackansible-gro…

6 7

[openstack-helm] Nominate Karl Kloppenborg for openstack-helm-core
by Vladimir Kozhukalov 04 May '23

04 May '23

Dear Openstack-helmers, I would like to suggest Karl Kloppenborg as a member of the core review team. He's been actively doing code review recently and also contributed as a developer. He has been using Openstack-Helm for a few years now, so his experience as a user is also to our advantage. I hope for your support. -- Best regards, Kozhukalov Vladimir

2 2

[all][tc][vitrage] Final call for Vitrage project maintainers
by Ghanshyam Mann 03 May '23

03 May '23

Hello Everyone, You might have noticed that the Vitrage project is leaderless in this cycle[1]. Eyal, who was the previous PTL and the only maintainer of this project for more than two years[2], will not be able to continue in this project[3]. We thank and appreciate all previous maintainers' work on this project. This is the final call for maintainers. If anyone is using or interested in this project, this is the right time to step up and let us know in this email or IRC(OFTC) #openstack-tc channel. If there is no response by the end of April 2023, we will discuss the retirement of this project. [1] https://etherpad.opendev.org/p/2023.2-leaderless [2] https://www.stackalytics.io/?module=vitrage-group&release=wallaby [3] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033333.h… -gmann

2 2

OpenInfra Live - May 4, 2023 at 9 a.m. CT / 14:00 UTC
by Kristin Barrientos 03 May '23

03 May '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenInfra Foundation Staff. Episode: May the OpenInfra Force Be With You: Preview of the OpenInfra Summit! Join us for an insightful and informative discussion as we give you the inside scoop on what’s in store at the OpenInfra Summit, Vancouver, happening, June 13-15! Don’t miss your chance to learn how you can get involved! Speakers: Wes Wilson, Allison Price, Jimmy McArthur, Kendall Nelson Date and time: May 4, 2023, at 9 a.m. CT. (14:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/live/g_nTOpLGftw?feature=share LinkedIn: https://www.linkedin.com/events/7056677974057648128/comments/ WeChat: recording will be posted on OpenStack WeChat after the live stream Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[dev][infra][qa][tact-sig] Future of Fedora and CentOS Stream Test Images
by Jeremy Stanley 03 May '23

03 May '23

tl;dr is that the OpenDev Collaboratory is looking at potentially scaling back on Fedora-based test platform support. Several options are presented in this service-discuss post: https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/t… If you have an opinion on using Fedora in our CI jobs, please follow up to the discussion there. -- Jeremy Stanley

1 0

[largescale-sig] Next meeting: May 3, 8utc
by Thierry Carrez 03 May '23

03 May '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 8UTC, our EU+APAC-friendly time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230503T08 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

Getting 403 from keystone as admin user.
by Andy Speagle 03 May '23

03 May '23

We're getting strange 403's from keystone on the CLI when trying to list users, groups, and role assignments. Running keystone 17.0.1 on ussuri. I've looked through our policy.json... can't find anything strange. Has anyone seen this behavior? Any ideas what can be done? Thanks.

2 1

Cinder Bug Report 2023-05-03
by Sofia Enriquez 03 May '23

03 May '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Low* - Infinidat driver should use the pool's compression setting when creating volumes. <https://bugs.launchpad.net/cinder/+bug/2017815> - *Status: *Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/881188>. - Cinder retype fails with "no host supplied" for SolidFire driver. <https://bugs.launchpad.net/cinder/+bug/2018001> - *Status*: Unassigned. *Incomplete* - When cinder-backup and nova-compute at the same node,backup restore will delete multipath. <https://bugs.launchpad.net/cinder/+bug/2017952> - *Status*: Waiting for reported reply. 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

[OpenvSwitch][Neutron] native flow based firewall Vs LinuxBridge Iptables firewall
by Satish Patel 02 May '23

02 May '23

Folks, As we know, openvswitch uses a linuxbridge based firewall to implement security-groups on openstack. It works great but it has so many packet hops. It also makes troubleshooting a little complicated. OpenvSwitch does support native firewall features in flows, Does it mature enough to implement in production and replace it with LinuxBridge based IPtables firewall? ~S

3 3

[tc] Reminder: 2023-05-10 OpenInfra Board Sync
by Jeremy Stanley 02 May '23

02 May '23

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2023-05-board-openstack-sync As previously announced[*], we're planning to hold the next call at 20:00 UTC on Wednesday, May 10. A link to the conference bridge will be added to the pad prior to that time. [*] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033244.h… -- Jeremy Stanley

1 0

[horizon][nova][masakari] Instances created with "Any AZ" problem
by Nguyễn Hữu Khôi 02 May '23

02 May '23

Hello guys. I playing with Nova AZ and Masakari https://docs.openstack.org/nova/latest/admin/availability-zones.html Masakari will move server by nova scheduler. Openstack Docs describe that: If the server was not created in a specific zone then it is free to be moved to other zones, i.e. the AvailabilityZoneFilter <https://docs.openstack.org/nova/latest/admin/scheduling.html#availabilityzo…> is a no-op. I see that everyone usually creates instances with "Any Availability Zone" on Horzion and also we don't specify AZ when creating instances by cli. By this way, when we use Masakari or we miragrated instances( or evacuate) so our instance will be moved to other zones. Can we attach AZ to server create requests API based on Any Availability Zone to limit instances moved to other zones? Thank you. Regards Nguyen Huu Khoi

5 20

[kolla-ansible][all][nova][zed][latest] USB passthrough / Hot-plug / Cold-plug
by Modyngs 02 May '23

02 May '23

090c090cFolks, A USB device (not necessarily a mass/Flash drive) needs to be connected to one of the VMs (an openstack instance). Openstack installed with kolla-ansible{Latest version/ Also tested on Zed} ALL IN ONE Deployments on ubuntu server 22.04 ( Core i9 12900K). I found the [nova-libvirt] container which contains *virsh *and is able to edit it or use custom config for VMs. I've gone through lots of the docs, to name a few: https://libvirt.org/formatdomain.html https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://wiki.openstack.org/wiki/Nova/proposal_about_usb_passthrough https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-libvirt-config… https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://docs.nxp.com/bundle/GUID-487B2E69-BB19-42CB-AC38-7EF18C0FE3AE/page/… but none of them worked for me!! To reproduce: *Cold-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *%Turn the Desired VM off* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running - instance-0000000a shut off *# virsh edit instance-0000000a* Add the changes [1][2][3][4],... ( many efforts have been done but few samples of them are) [1]: under <devices> added <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [2]:under <devices> added <controller type='usb' index='0'/> <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [3]: under <devices> added <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [4]: under <devices> added <controller type='usb' model='nec-xhci' index='0'/> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [5]: <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='usb' bus='1' port='2'/> <controller type='usb' index='0'/> </hostdev> *%Start the VM* *expected behavior:* when login to the VM, lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *OR *virsh dumpxml instance-0000000a > instance-0000000a.xml and then change the configs as above and then virsh attach-device instance-0000000a --file /path/to/updated-instance-0000000a.xml --config *Hot-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running 20 instance-0000000a running *#nano USB.xml* *%add changes explained in *[1][2][3][4],... *$ virsh attach-device instance-0000000a /path/to/USB.xml/file* *expected behavior:* lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *Can you please guide me through this? Any recommendation would be much appreciated!Any custom changes comes to your mind ( Reply it) would be solution for this problem /;* Thanks Best regards

2 1

[cinder][kolla][OpenstackAnsible] 2023.1 Antelope Cycle-Trailing Release Deadline
by Elõd Illés 02 May '23

02 May '23

Hello teams with trailing projects, The 2023.1 Antelope cycle-trailing release deadline is in ~1 months [1], and all projects following the cycle-trailing release model must release their 2023.1 Antelope deliverables by June 1st, 2023. The following trailing projects haven't been released yet for 2023.1 Antelope (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/bobcat/schedule.html#b-cycle-trail Thanks, Előd irc: elodilles @ #openstack-release

1 0

[openstack-helm] Cancelling monthly meetings
by Vladimir Kozhukalov 02 May '23

02 May '23

Dear Openstack-helmers, I would like to announce that we are going to stop having monthly IRC meetings due to the lack of interest. There are two major concerns: 1) It is usually not a good idea to wait few weeks for the next meeting to happen if you have something to discuss 2) If only few people are attending the meeting then it is anyway not enough to have a strong community consensus and to make any important decisions We discussed this a couple months ago in the IRC meeting and now it is time to do the next step and to cancel it. So, if you have something to discuss please feel free to start the discussion directly in the #openstack-helm Slack chat (Slack is our preferable way of communication). Today's meeting (May/02/2023) is also canceled. -- Best regards, Kozhukalov Vladimir

1 0

[tripleo] hold rechecks content provider gate blocker - CentOS-9 stream mirrors
by Ronelle Landy 02 May '23

02 May '23

Hello All, We have a check/gate blocker impacting all CentOS-9 jobs. Details are in: https://bugs.launchpad.net/tripleo/+bug/2018265 - CentOS-9 stream mirrors are returning Status code: 404. Per https://review.opendev.org/868392 - the Rackspace mirrors are being used to sync CentOS-9 repos - so possibly there is a lag/roll back there. We will post out once there is a fix/workaround or if the situation gets unblocked dueto an update. Thank you.

1 1

Offline Openstack Release:Train Deployment
by Vineet Thakur 01 May '23

01 May '23

Greetings openstack community members, It's regarding the deployment of openstack release: train on CentoOS 7.9 environment by using openstack-ansible tool. (Offline environment) We are facing challenges to download the packages, some package links are not accessible or somewhere PIP packages are not available as per the constraint requirement list. See: https://artifacts.ci.centos.org/sig-cloudinstance/centos-7-191001/x86-64/ce… For pip packages: https://opendev.org/openstack/requirements/raw/0cfc2ef6318b639bb4287fa051ea… During installation we are facing a lot of errors, and not sure what would be the best approach in such scenarios where packages are not available or need to be downloaded from random sites. We are in the mid of a mega deployment and appreciate it if you can guide us through. Awaiting your response, thank you. Kind Regards, Vineet Thakur

3 3

[tc] Technical Committee next weekly meeting on May 2, 2023
by Nikolla, Kristi 01 May '23

01 May '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held tomorrow (May 2) at 1800 UTC on Zoom. Items can be proposed by editing the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting At the end of today I will send out an email with the finalized agenda. Thank you, Kristi Nikolla

1 1