May 2023 - openstack-discuss - lists.openstack.org

[all][tc][release] Hold the Python3.8 dropping
by Ghanshyam Mann 09 May '23

09 May '23

Hello Everyone, As you know the gate is breaking due to Python3.8 drop[1][2], which we discussed in the TC channel and meeting[3]. TC is preparing the guidelines on not dropping Python3.8 in 2023.2 pti. Meanwhile, governance guidelines are prepared, this email is a heads-up to hold the dropping of Python3.8 from your project/repo. Do not bump the min py version in setup.cfg (do not bump version in python_requires ). @Release team, It will be helpful if you can check/hold the release of any project/lib dropping the Python3.8. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033450.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033454.h… [3] https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#… -gmann

1 1

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

09 May '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, May 9, 2023 at 1800 UTC on #openstack-tc on OFTC IRC Please propose items to the agenda 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

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 08 May '23

08 May '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we review the Foundation-wide diversity survey questions for release at Summit. Thanks, Amy (spotz)

1 0

Fwd: (Openstack-Cinder) Error
by Adivya Singh 08 May '23

08 May '23

HI, Can you please guide me, There is this error which i am getting "fatal: [t1w_cinder_volumes_container-29d71abf]: FAILED! => {"msg": "The conditional check 'cinder_backend_lvm_inuse | bool' failed. The error was: error while evaluating conditional (cinder_backend_lvm_inuse | bool): {{ (cinder_backends|default(\"\")|to_json).find(\"cinder.volume.drivers.lvm.LVMVolumeDriver\") != -1 }}: {'lvm': {'iscsi_ip_address': '{{ 172.29.244.50 }}', 'volume_backend_name': 'LVM_iSCSI', 'volume_driver': 'cinder.volume.drivers.lvm.LVMVolumeDriver', 'volume_group': 'cloud'}}: float object has no element 244\n\nThe error appears to be in '/opt/openstack-ansible/playbooks/common-playbooks/cinder.yml': line 67, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Configure container (cinder-volume) when lvm is in-use\n ^ here\n"} I understand this error to some extent, but want to confirm with you if any body have seen similiar kind of error storage_hosts: s1w: ip: 172.29.236.50 container_vars: #cinder_storage_availability_zone: nova #cinder_default_availability_zone: nova cinder_backends: lvm: volume_backend_name: LVM_iSCSI volume_driver: cinder.volume.drivers.lvm.LVMDriver volume_group: cloud-volume iscsi_ip_address: "{{ cinder_storage_address }}" limit_container_types: cinder_volume Regards Adivya Singh

1 0

[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