June 2023 - openstack-discuss - lists.openstack.org

[kolla-ansible][zun] Deleting container through api
by James Leong 24 Jun '23

24 Jun '23

Hi all, I am currently playing around with the Zun component. I have deployed the yoga version of OpenStack using kolla-ansible. Is there an api to delete a container based on the ID without any user context? Best, Jame

1 0

Next minimum libvirt / QEMU versions for "C" release (2024)
by Kashyap Chamarthy 24 Jun '23

24 Jun '23

Hi, folks! The last time we incremented versions for libvirt and QEMU was for "Wallaby" release[1]. It'Although we advertized NEXT_MIN_{LIBVIRT,QEMU} versions to be libvirt 7, 0, 0 and QEMU 5.2.0, we actually didn't bump. So, for "Bobcat", we'll bump the MIN libvirt and QEMU versions to: MIN_LIBVIRT_VERSION = (7, 0, 0) MIN_QEMU_VERSION = (5, 2, 0) For the upcoming "C" release (2024), we annouce the NEXT_MIN_{LIBVIRT,QEMU} to be the following: NEXT_MIN_LIBVIRT_VERSION = (8, 0, 0) NEXT_MIN_QEMU_VERSION = (6, 2, 0) Hope that sounds fine. If anyone has concerns or further comments, please raise them on this thread or add 'em in the patch below: https://review.opendev.org/c/openstack/nova/+/886825 Pick next min libvirt / QEMU versions for "C" (2024) release Rationale --------- We picked the above NEXT_MIN version based on Ubuntu "Jammy" (22.04). It is the lowest common denominotor among Debian 11 ("Bullseye"), Ubuntu 22.04 ("Jammy"), and CentOS 9 Stream. - Ubuntu 22.04 (Jammy): - libvirt-daemon: 8.0.0-1ubuntu7.5 - qemu-system-x86: 6.2+dfsg-2ubuntu6.11 - Debian 11 (Bullseye): - libvirt: 7.0.0-3+deb11u2 - qemu: 5.2+dfsg-11+deb11u2 - CentOS Stream 9: - libvirt-daemon-kvm-9.3.0-2.el9.x86_64.rpm - qemu-kvm-8.0.0-4.el9.x86_64.rpm [1] https://opendev.org/openstack/nova/commit/95724bbaef6 -- libvirt: Bump MIN_{LIBVIRT,QEMU}_VERSION and NEXT_MIN_{LIBVIRT,QEMU}_VERSION, 2020-09-28) -- /kashyap

4 4

[kolla] does cinder volumes works on ceph rbd pools erasure coded?
by garcetto 24 Jun '23

24 Jun '23

good evening, trying to make it working, (ubuntu 22, kolla all-in-one, external ceph wirh both rdb replica AND erasure code pools). with replica cinder-volumes works. no way with ec pools? cephx and access already check all ok... any idea? is it supported? thank you

1 0

[kolla] User Forum Vancouver
by Michał Nasiadka 24 Jun '23

24 Jun '23

Hello Koalas, Thank you for attending User Forum on Vancouver 2023 Summit. We’ve had a fruitful conversation around Kolla-Ansible performance and additional actions that can be taken to improve day 2 operations and stability of production environments. Link to etherpad: https://etherpad.opendev.org/p/YVR23-kolla-user-forum See you next time - and I once again encourage everybody to attend Kolla Weekly Meetings [1] or write messages to the Mailing List. [1]: https://meetings.opendev.org/#Kolla_Team_Meeting Michal

1 0

[Glance] Weekly Meeting Cancelled
by Pranali Deore 23 Jun '23

23 Jun '23

Hello, Glance weekly meeting for next week, Thursday 29th June, has been cancelled and instead we are going to have review party on 28th June. Kindly please refer the meeting etherpad[1] for more details, [1]: https://etherpad.opendev.org/p/glance-team-meeting-agenda Thanks and regards, ~Pranali

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 23 Jun '23

23 Jun '23

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

1 0

[kolla] help working config cinder and cinder-backup on different nfs servers and exports
by garcetto 23 Jun '23

23 Jun '23

good morning, i am having trouble understanding how to config different nfs shares on different nfs servers, one for cinder and ANOTHER one for use for cinder-backup, this is my files: (already check both nfs export are reachable and works fine in rw inside openstack) (kolla latest version on ubuntu 22 hosts, all-in-one-deploy) [globals.yaml] ... enable_cinder: "yes" enable_cinder_backend_nfs: "yes" enable_cinder_backup: "yes" cinder_backup_driver: "nfs" cinder_backup_share: "192.168.100.100:/exports/backup" cinder_backup_mount_options_nfs: "vers=3" [config/nfs_shares] 192.168.100.100:/exports/backup 192.168.200.200:/exports/volumes thank you.

1 0

DRaaS question
by KK CHN 23 Jun '23

23 Jun '23

List, Looking for solutions using OpenStack Similar to 1. VMWare VCDR( VMware Cloud Disaster Recovery) as a Pilot Light DR Solution hassle free Failover and Failback. 2. AWS Cloud Replication Agent( Cloud Endurance ) Operational DR solution in Cloud ( Both 1 and 2 have capabilities of acting as an Operational DR in Cloud and serving both from AWS demonstrated as a PoC ). Any solution/directives to achieve a similar to better solution using OpenStack techniques and components? Please enlighten with your ideas. Thank you Krishane.

7 9

[all][ops][rbac] RBAC discussion summary from Vancouver summit
by Ghanshyam Mann 23 Jun '23

23 Jun '23

Hello Everyone, Most of you know we had the RBAC discussion at the Vancouver summit on Tuesday. - https://etherpad.opendev.org/p/rbac-operator-feedback-vancouver2023 This forum session started providing the current progress for RBAC work which you can find in Etherpad - https://etherpad.opendev.org/p/rbac-operator-feedback-vancouver2023#L46 After the progress updates, we started the feedback from operators. I am writing the summary and feel free to add anything I missed to capture here: Admin Access: =========== * Keep current Admin (legacy admin means admin in any project) untouched. * There is a need for second-level support along with the current admin, and this can be done with the project manager * Public Cloud use case: ---------------------------- ** Currently defined RBAC goal does not solve the public cloud use case of having a domain admin manage the specific domain's user/project/role. ** If the domain admin can assign an admin role to any user under their domain, then that user gets admin access across all the projects on the service side (even projects are in different domains as the service side does not have domain boundaries) ** We do not have any better solution for now, but one idea is to have the Domain manager allow managing the user/project/ role in their domain except 'Admin' role assignment. Current legacy admin (admin across all domains) can handle the 'Admin' role assignment. I mean, domain manager behaves as domain-level admin and legacy admin as a global admin. Feel free to write other solutions if you have? Member Access: ============ * Project Member is a good fix and useful to enforce 'member' roles actually Reader Access: ============ * Project Reader is one of the most useful roles in this change. * There is an ask for a global reader, which was nothing but a system reader in past. This can be useful for performing the audit of the complete cloud. One idea is to do this with a special role _role in Keystone. I will write the spec for it, and we can talk about it there. -gmann

2 2

[ironic] Summit PTG Summary
by Jay Faulkner 23 Jun '23

23 Jun '23

Hey all, As indicated before the summit, the Ironic PTG was dedicated to in-person collaboration, hacking, and design chats but were not intended for any final decision making due to not all of our community being present. Full, contemporaneous notes taken are at https://etherpad.opendev.org/p/ironic-openinfra-2023 -- this is meant to be a high level summary. For the summit, there were several extremely well-attended Ironic talks. Thank you to all of those who gave talks! In addition, I, and other members of the Ironic community, were able to connect with many people using Ironic quietly in production with a large amount of success. As always, the Ironic community strongly encourages people with success stories to loudly communicate about them :D. Ironic did have a single forum session, where we met with several operators, answering questions and in some places providing solutions to people struggling with a problem. The full notes from the session, primarily consisting of a census of Ironic installs, are accessible from the above linked etherpad. As for the PTG sessions, there were a few topics. These are extremely rough outlines of what was discussed; but again, no specific decisions were made. - networking-generic-switch -- Several contributors, including Baptise Jonglez and John Garbutt, discussed options for scaling NGS further up in the future, including enhancing it to support other protocols, such as VXLAN. Some of these discussions have already moved to the list; and I encourage folks to engage with Baptise to make our network tooling scale even more. - Future of Ironic -- We spoke for a while about the Ironic vision document created in Rocky, targeting approximately now: https://docs.openstack.org/ironic/latest/contributor/vision.html -- we've accomplished many of the items on the list, but what's next? -- Possibilities brainstormed included: --- Enhanced network interfaces that use SDN or DPU orchestration to configure baremetal networks --- more distinct support for composible hardware --- expanding Ironic standalone use cases --- getting more directly connected with communities like Metal3 integrating into Ironic --- scaling down Ironic into a tool useful at smaller scale (that a tool like cobbler has a strong hold on today) --- terraform driver designed to call Ironic directly -- I think we should update the vision document with some of these ideas so we can use it as a measuring stick in 5-6 years, like we were able to use the Rocky vision document this time. Finally, we closed up the summit with an Ironic dinner, with 16 attendees from various companies, use cases, and backgrounds with one thing in common: we all need bare metal servers :). If you're wondering who the faces of Ironic are, here are some of us https://twitter.com/jayofdoom/status/1669531671937384449 :). I'll say, on a personal note, it was extremely nice to get to see many of my old and new friends in the OpenInfra community face to face for the first time in years. The absence of those unable to travel was felt deeply as well, and I hope we'll be able to reconnect in person in the future. Thanks, Jay Faulkner Ironic PTL

3 3

[neutron] - OVN heartbead - short agent_down_time
by Roberto Bartzen Acosta 22 Jun '23

22 Jun '23

Hello Neutron folks, We discussed in the Operators feedback session about OVN heartbeat and the use of "infinity" values for large-scale deployments because we have a significant infrastructure impact when a short 'agent_down_time' is configured. The merged patch [1] limited the maximum delay to 10 seconds. I understand the requirement to use random values to avoid load spikes, but why does this fix limit the heartbeat to 10 seconds? What is the goal of the agent_down_time parameter in this case? How will it work for someone who has hundreds of compute nodes / metadata agents? Regards, Roberto [1] - https://review.opendev.org/c/openstack/neutron/+/883687 -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

3 5

[all] PyCharm/JetBrains licenses renewed
by Daniel Mellado 22 Jun '23

22 Jun '23

Hi all o/ This is just to inform you that the open source licenses for PyCharm/JetBrains have been renewed for 1 extra year until Aug 2024. Best! Daniel Mellado

1 0

Experience with VGPUs
by Oliver Weinmann 22 Jun '23

22 Jun '23

Dear All, we are planning to have a POC on VGPUs in our Openstack cluster. Therefore I have a few questions and generally wanted to ask how well VGPUs are supported in Openstack. The docs, in particular: https://docs.openstack.org/nova/zed/admin/virtual-gpu.html explain quite well the general implementation. But I am more interested in general experience with using VGPUs in Openstack. We currently have a small YOGA cluster, planning to upgrade to Zed soon, with a couple of compute nodes. Currently our users use consumer cards like RTX 3050/3060 on their laptops and the idea would be to provide VGPUs to these users. For this I would like to make a very small POC where we first equip one compute node with an Nvidia GPU. Gladly also a few tips on which card would be a good starting point are highly appreciated. I know this heavily depends on the server hardware but this is something I can figure out later. Also do we need additional software licenses to run this? I saw this very nice presentation from CERN on VGPUs: https://indico.cern.ch/event/776411/contributions/3345183/attachments/18516… In the table they are listing Quadro vDWS licenses. I assume we need these in order to use the cards? Also do we need something like Cyborg for this or is VGPU fully implemented in Nova? Best Regards, Oliver

17 36

[nova][tempest] Hold your rechecks
by Sylvain Bauza 22 Jun '23

22 Jun '23

As far as I can tell, all nova-live-migration job runs are getting a FAILURE [1] due to [2] so please hold your rechecks. Thanks to Rodolfo, we have a workaround for it https://review.opendev.org/c/openstack/tempest/+/886496* so please wait until this change is merged.* Tempest cores, it would be nice if you can look at the above change quickly :) Thanks, -Sylvain [1] https://zuul.openstack.org/builds?job_name=nova-live-migration&skip=0 [2] https://bugs.launchpad.net/nova/+bug/2024160

2 1

[keystone] Updates to core reviewers
by Nikolla, Kristi 22 Jun '23

22 Jun '23

Hi all, Some updates to the core reviewers in Keystone repos. Dave Wilde (d34dh0r53) has been Keystone PTL for the Antelope and Bobcat cycle and has done an amazing work. Dave is now a core reviewer in Keystone. Artem Goncharov (gtema) is the PTL of OpenStack SDK, he is willing to help out with the Keystoneauth library, that being a core part of the SDK and CLI. Thank you Artem, you are now a core reviewer of Keystoneauth. Lance Bragstad (lbragstad) has been inactive for a bit over a year now and I believe doesn't work on OpenStack anymore. Due to that I am removing as a core reviewer from Keystone. Lance has been a contributor to Keystone and OpenStack for a really really long time and was an essential part of the Keystone team, serving as its PTL too. Best, Kristi Nikolla

3 2

[ceilometer][cinder] How to properly set up Block Storage meters / cinder-volume-usage-audit
by Christian Rohmann 21 Jun '23

21 Jun '23

Hello OpenStack-Discuss, when setting up telemetry (ceilometer, gnocci, aodh) I followed the documentation at https://docs.openstack.org/ceilometer/latest/install/cinder/install-cinder-… to set up sending metrics for cinder to ceilomter. 1) The instruction to run cinder-volume-usage-audit as a timer / cron every 5 minutes > */5 * * * * /path/to/cinder-volume-usage-audit --send_actions has me confused. This would cause the usage data for the last full month, to be sent to the notifications queue every 5 minutes. There is no progress tracker or pointer limiting this to only sent data that has not yet been sent. Looking at how openstack-ansible configures this (https://github.com/openstack/openstack-ansible-os_cinder/blob/1af3003e163e0…) it seems they were aware that running this without bounds and every 5 minutes is wrong. I also opened a bug (https://bugs.launchpad.net/ceilometer/+bug/2024475) about this. 2) Extending on 1) I believe setting the > volume_usage_audit_period in the cinder configuration, to e.g. month or hour, will already set the interval for which the data is emitted. Then the important thing is to only run cinder-volume-usage-audit in the same frequency. 3) Looking at the "--send_actions" options, I am wondering if the "create/delete" actions for volumes, snapshosts and backups are not sent by cinder anyways and why they would need to be sent again in batch and by cinder-volume-usage-audit? I am referring to > [oslo_messaging_notifications] > driver = messagingv2 > being enabled. This might also be the reasoning behind this bug, https://bugs.launchpad.net/openstack-ansible/+bug/1968734, asking for this parameter to be behind a config switch to avoid duplicate actions to be sent. 4) Thinking about the whole setup more questions arise * What happens when I run this more than once in the same interval? What will ceilometer do with the (redundant) data? * I am also wondering how well this single piece of software scales and how this could be split up more? * Is there no way to implement a pointer to allow running this command more often and only send "new data"? Just like the timestamp up to which data was sent. * What about any locking / coordination to enable multiple instances? Regards Christian

1 0

[ceilometer][gnocchi][telemetry] (User) frontend or tool to create reports on telemetry data (GPU, RAM, disk, network, ...)
by Christian Rohmann 21 Jun '23

21 Jun '23

Hello OpenStack-Discuss, I was wondering if there are any simple frontends or similar solutions to provide ceilometer's telemetry data, such as CPU, RAM, volume throughput and IOPs, network throughput, ... to users? Something like a basic horizon dashboard? Or does anybody have written something using the API to create some nice graphs? I know there is Cloudkitty, but that looks more targeted towards doing rating and billing with this kind of data? Thanks and with regards Christian

3 2

HOT template help
by Antony P 21 Jun '23

21 Jun '23

Hi team, This is user data jenkins_password=$(sudo cat /var/lib/jenkins/secrets/initialAdminPassword) i want to pass this as output like Output: value: password How can i resolve this? *--Warm Regards* *Antony P* *Jr. DevOps Engineer* antony(a)edgebricks.com Mob No: +919498079898 www.edgebricks.com

1 0

Cinder Bug Report 2023-06-21
by Sofia Enriquez 21 Jun '23

21 Jun '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Wishlist* - Restore RBD Incremental Backup Fails When Using the --container Argument. <https://bugs.launchpad.net/cinder/+bug/2024484> - *Status*: Fix proposed to master. <https://review.opendev.org/c/openstack/cinder/+/788319> *Low* - Hitachi: wrong exception when deleted volume is busy. <https://bugs.launchpad.net/cinder/+bug/2024418> - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/885986>. 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

versioning hidden container accounting
by Geert Geurts 21 Jun '23

21 Jun '23

Hello I've implemented the newer type of versioning (x-versions-enabled: True) for a container. The documentation (https://docs.openstack.org/swift/latest/middleware.html#object-versioning) states that actual data is written to a hidden container. Now my question is would it be possible to set the account for the data of the current ("is_latest": true) objects to a different account? Would it be possible to set headers on the event that 'current' changes? Can I see/change the properties of this "hidden" container? Thanks allot for any help/pointers! Best regards, Geert

1 0

[ironic] [networking-generic-switch] NGS performance and moving to an agent-based design
by Baptiste Jonglez 21 Jun '23

21 Jun '23

Hello, We have been hitting performance issues with networking-generic-switch (NGS), the Neutron ML2 plugin that performs dynamic reconfiguration of physical switches, most notably used by Ironic. In our quest to improve NGS performance, we have designed and implemented an agent-based system for NGS, and we would now like to upstream it. Since this is a fairly big change, and some parts of the design such as HA are not completely clear yet, feel free to join the discussion on the RFE: https://bugs.launchpad.net/networking-generic-switch/+bug/2024385 Regards, Baptiste -- Baptiste Jonglez Research Engineer, Inria <https://www.inria.fr/> STACK team <https://stack-research-group.gitlabpages.inria.fr/web/>

2 1

[kolla] nova-compute image build failed with invalid signature
by Satish Patel 21 Jun '23

21 Jun '23

Folks, Just wanted to check with folks if I did anything wrong here. Building 2023.1 image of nova-compute and encounter errors. root@docker-reg:/opt/kolla/etc/kolla# kolla-build --registry docker-reg:4000 --config-file kolla-build.conf --debug --cache --threads 1 --skip-existing --push --format none nova-compute INFO:kolla.common.utils:Using engine: docker INFO:kolla.common.utils:Found the container image folder at /usr/local/share/kolla/docker INFO:kolla.common.utils:Added image nova-compute-ironic to queue INFO:kolla.common.utils:Added image nova-compute to queue INFO:kolla.common.utils:Attempt number: 1 to run task: BuildTask(nova-compute-ironic) DEBUG:kolla.common.utils.nova-compute-ironic:Processing INFO:kolla.common.utils.nova-compute-ironic:Building started at 2023-06-20 17:36:33.771585 DEBUG:kolla.common.utils.nova-compute-ironic:Turned 0 plugins into plugins archive DEBUG:kolla.common.utils.nova-compute-ironic:Turned 0 additions into additions archive INFO:kolla.common.utils.nova-compute-ironic:Step 1/4 : FROM docker-reg:4000/kolla/nova-base:2023.1 INFO:kolla.common.utils.nova-compute-ironic: ---> 0ebe71c922b4 INFO:kolla.common.utils.nova-compute-ironic:Step 2/4 : LABEL maintainer="Kolla Project (https://launchpad.net/kolla)" name="nova-compute-ironic" build-date="20230620" INFO:kolla.common.utils.nova-compute-ironic: ---> Using cache INFO:kolla.common.utils.nova-compute-ironic: ---> 5209e0cc6403 INFO:kolla.common.utils.nova-compute-ironic:Step 3/4 : RUN apt-get --error-on=any update && apt-get -y install --no-install-recommends genisoimage nvme-cli && apt-get clean && rm -rf /var/lib/apt/lists/* INFO:kolla.common.utils.nova-compute-ironic: ---> Running in 196bc3715e45 INFO:kolla.common.utils.nova-compute-ironic:Get:1 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope InRelease [5,463 B] INFO:kolla.common.utils.nova-compute-ironic:Get:2 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB] INFO:kolla.common.utils.nova-compute-ironic:Err:1 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope InRelease INFO:kolla.common.utils.nova-compute-ironic: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:Get:3 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [3,463 B] INFO:kolla.common.utils.nova-compute-ironic:Get:6 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB] INFO:kolla.common.utils.nova-compute-ironic:Err:2 http://archive.ubuntu.com/ubuntu jammy-backports InRelease INFO:kolla.common.utils.nova-compute-ironic: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:Get:5 https://mirror.dal.nexril.net/ubuntu jammy-updates InRelease [119 kB] INFO:kolla.common.utils.nova-compute-ironic:Err:6 http://archive.ubuntu.com/ubuntu jammy-security InRelease INFO:kolla.common.utils.nova-compute-ironic: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:Get:4 http://ftp.usf.edu/pub/ubuntu jammy InRelease [270 kB] INFO:kolla.common.utils.nova-compute-ironic:Err:5 https://mirror.dal.nexril.net/ubuntu jammy-updates InRelease INFO:kolla.common.utils.nova-compute-ironic: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:Err:4 http://ftp.usf.edu/pub/ubuntu jammy InRelease INFO:kolla.common.utils.nova-compute-ironic: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:Reading package lists... INFO:kolla.common.utils.nova-compute-ironic:W: GPG error: http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope InRelease: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:E: The repository 'http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope InRelease' is not signed. INFO:kolla.common.utils.nova-compute-ironic:W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed. INFO:kolla.common.utils.nova-compute-ironic:W: GPG error: http://archive.ubuntu.com/ubuntu jammy-security InRelease: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:E: The repository 'mirror://mirrors.ubuntu.com/mirrors.txt jammy-security InRelease' is not signed. INFO:kolla.common.utils.nova-compute-ironic:W: GPG error: https://mirror.dal.nexril.net/ubuntu jammy-updates InRelease: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:E: The repository 'mirror://mirrors.ubuntu.com/mirrors.txt jammy-updates InRelease' is not signed. INFO:kolla.common.utils.nova-compute-ironic:W: GPG error: http://ftp.usf.edu/pub/ubuntu jammy InRelease: At least one invalid signature was encountered. INFO:kolla.common.utils.nova-compute-ironic:E: The repository 'mirror://mirrors.ubuntu.com/mirrors.txt jammy InRelease' is not signed. INFO:kolla.common.utils.nova-compute-ironic: INFO:kolla.common.utils.nova-compute-ironic:Removing intermediate container 196bc3715e45 ERROR:kolla.common.utils.nova-compute-ironic:Error'd with the following message ERROR:kolla.common.utils.nova-compute-ironic:The command '/bin/sh -c apt-get --error-on=any update && apt-get -y install --no-install-recommends genisoimage nvme-cli && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100 INFO:kolla.common.utils:Attempt number: 2 to run task: BuildTask(nova-compute-ironic) DEBUG:kolla.common.utils.nova-compute-ironic:Processing Full trace - https://paste.opendev.org/show/b3IYgcUXsvg0kxVpEaLM/

2 2

[neutron][ptg] PTG summary
by Rodolfo Alonso Hernandez 21 Jun '23

21 Jun '23

Hello all: Thank you for joining us during the Forum session and the PTG slots. It was very productive and we were able to check the pulse of OpenStack and Neutron in particular. This time both the Forum session and the PTG were attended mainly by operators and users; the number of developers was reduced and this is something we need to improve. A healthy community is nourished by the active participation of their members, not only pushing new code but reviewing and helping fixing the new bugs. === Forum session === That was a good surprise for me to find so many people in the room. I wasn't expecting that after checking the etherpad link provided before the meeting. During this short session, focused on issues/pain points of Neutron, we could find out that: * The ML2/OVN backend is increasing its adoption rate. * Most users have deployments between Wallaby and Antelope. * Hardware offload is increasing its demand due to the network BW increasing requirements. * BGP/eVPN is deployed in most of the environments. >From this session I would highlight some lessons learned for next events: * If the Forum session time slot is reduced (30 mins), the attendant interventions should be limited to 2-3 minutes, enough to describe the issue. Any further discussion should be taken in the PTG sessions. * Request attendance "checkin" in the etherpad, to be prepared for the event. * Request people to add their questions in the etherpad in advance. === PTG === We didn't have technical sessions but many questions about issues and possible bugs. These are the most relevant ones: *** OVN L3 scheduler issue *** This issue has been reproduced in an environment with more than 5 chassis with gateway ports. The router GW ports are assigned to the GW chassis using a manual scheduler implemented in Neutron (the default one is ``OVNGatewayLeastLoadedScheduler``). If one of the chassis is stopped, the GW ports should be re-assigned to the other GW chassis. This is happening but all ports fall under the same one; this re-scheduling should share the ports among the other active chassis. * Action item: I'll open a LP bug and investigate this issue. *** Size of the OVN SB "HA_Chassis_Group" table *** The OVN SB "HA_Chassis_Group" increases its size indefinitely with each operation creating a router and assigning a new external gateway (external network). This table never decreases, * Action item: I'll open a LP bug, investigate this issue and if this is a core OVN issue, report it. *** Live migration with ML2/OVN *** This is a common topic and not only for ML2/OVN. The migration time has many factors (memory size, applications running, network BW, etc) that could slow down the migration time and trigger a communication gap during this process. * Action item: to create better documentation, both in Nova and Neutron, about the migration process, what has been done to improve it (for example, the OVN multiple port binding) and what factors will affect the migration. *** ML2/OVN IPv6 DVR *** This spec was approved during the last cycle [1]. The implementation [2] is under review. * Action item: to review the patch (for Neutron reviewers) * Action item: to implement the necessary tempest tests (for the feature developers) *** BGP with ML2/OVS, exposing address blocks *** This user has successfully deployed Neutron with ML2/OVS and n-d-r. This user is currently making public a certain set of FIPs. However, for other VMs without FIPs, the goal is to make the router GW port IP address public, using the address blocks functionality; this is not working according to the user. * Action item: (for this user) to create a LP bug describing the architecture of the deployment, the configuration used and the API commands used to reproduce this issue. *** Metadata service (any backend) *** Neutron is in charge of deploying the Metadata service on the compute nodes. Each time the metadata HTTP server is called, it requests from the Neutron API the instance and tenant ID [3]. This method implies a RPC call. In "busy" compute nodes, where the VMs are created and destroyed very fast, this RPC communication is a bottleneck. * Action item: open a LP bug to implement the same ``CacheBackedPluginApi`` used in the OVS agent. This RPC cached class creates a set of subscriptions to the needed resources ("ports" in this case). The Neutron API will send the port updated info and cached locally; that makes unnecessary the RPC request if the resources are stored locally. *** ML2/OVN + Ironic nodes *** This user has deployed ML2/OVN with Ironic nodes, and is using ovn-bgp-agent with the eVPN driver to make public the private ports (IP and MACs) to the Ironic node ports. More information in [4]. *** BGP acceleration in ML2/OVN *** Many questions related to this topic, both with DPDK and HW offload. I would refer (once the link is available) to the talk "Enabling multi-cluster connectivity using dynamic routing via BGP in Openstack" given by Christophe Fontaine during this PTG. You'll find it very interesting how this new implementation moves all the packet processing to the OVS datapath (removing any Linux Bridge / iptables processing). The example provided in the talk refers to the use of DPDK. I hope this PTG was interesting for you! Don't hesitate to use the usual channels that are the mailing list and IRC. Remember we have the weekly Neutron meeting every Tuesday at 1400UTC. Regards. [1] https://specs.openstack.org/openstack/neutron-specs/specs/2023.1/ovn-ipv6-d… [2]https://review.opendev.org/c/openstack/neutron/+/867513 [3] https://github.com/openstack/neutron/blob/cbb89fdb1414a1b3a8e8b3a9a4154ef62… [4]https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/

3 6

Help Needed: Configuring OpenStack Glance with VMware
by Anupam Panta 20 Jun '23

20 Jun '23

Dear OpenStack Community, I hope this email finds you well. I am reaching out to seek assistance and guidance regarding the configuration of OpenStack integration with VMware. I have encountered some difficulties while trying to configure Glance, and I would greatly appreciate any help or insights you can provide. Here is a brief overview of the issue I am facing: * Configuration Challenge: I am currently working on integrating OpenStack with VMware as the backend infrastructure for image storage and management. * Specific Problem: While configuring Glance, I am stuck with an error message stating "Store for identifier vmware not found". * Configuration Attempts: I have reviewed the relevant documentation and followed the recommended steps, tried changing parameters to configure the VMware store backend in Glance. However, despite my efforts, the error persists. I kindly request your guidance and expertise to help me troubleshoot and resolve this issue. Any advice, best practices, or configuration examples related to Glance integration with VMware would be highly appreciated. To provide you with more context, here are some relevant details of my environment: I am using kolla installation for openstack deployment. My global.yml file consists of: ``` #### GLANCE CONFIG glance_backend_vmware: "yes" glance_backend_insecure: "yes" #### VMWARE CONFIG vmware_vcenter_host_ip: <my-vcenter-ip-address> vmware_vcenter_host_username: <my-vcenter-admin-username> vmware_vcenter_host_password: <my-vcenter-admin-password> vmware_datastore_name: glance-datastore vmware_vcenter_name: <my-vcenter-domain-name> vmware_vcenter_cluster_name: "openstack" vmware_vcenter_datacenter_name: <my-vcenter-datacenter-name> vmware_vcenter_insecure: "True" ``` After running reconfigure command, my glance-api container stuck in restart loop, with error message "Store for identifier vmware not found". I also tried changing parameters in glance-api.conf file, specific parameters `default_backend= vsphere`, `stores= file, http, swift, vmware`. Your assistance will not only help me but also contribute to the collective knowledge of the community. Thank you in advance for your time and support. I look forward to your valuable insights and suggestions. Regards, Anupam Panta | LinkedIn<http://www.linkedin.com/in/anupam-panta> System Engineer anupam.panta(a)f1soft.com 9802079915 Movers & Shakes Tower, Pulchowk, Nepal [cid:78d40d57-4926-472e-bbe6-ea05244f879f] <https://f1soft.com/> Disclaimer This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, followed by deleting this e-mail and destroying any copies thereof Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal unless consented by the sender. F1soft International Private Limited or its employees are not responsible for any auto-generated spurious messages that you may receive from F1soft email addresses.

2 1

[cinder] in-use volume retype error "Expecting to find domain in project"
by Eugen Block 20 Jun '23

20 Jun '23

Hi, while trying to reproduce the issue mentioned in [1] I stumbled upon [2], I commented there but because of the "wishlist" importance I don't expect too much attention. I have a production cloud with Victoria where I see the same issue as described in [2], trying to retype an in-use volume results in a stack trace in cinder: 2023-06-20 12:45:52.900 1085571 ERROR oslo_messaging.rpc.server keystoneauth1.exceptions.http.BadRequest: Expecting to find domain in project. The server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400) (Request-ID: req-6b412e96-a735-4b94-a5e6-8252dd949297) I have also a test cloud installed the same way as the production cloud with V and upgraded to Wallaby where this stack trace does not occur, retyping an in-use volume just works there. I tried the described workaround in [1] and added a [nova] section to the cinder.conf, and that worked. There is no such section in the W cloud. I checked the Wallaby release notes and the only thing related to retype with ceph as backend is [3]. Could that make the difference here? One difference between V and W I noticed was that in V I see two volumes with the same name (but a different UUID, of course) during the retype process while in W I see only one volume at all times. So I assume that W handles the retype differently and it doesn't require a nova section. I'd appreciate any comment. Thanks, Eugen [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-June/034160.ht… [2] https://bugs.launchpad.net/cinder/+bug/1941062 [3] https://bugs.launchpad.net/cinder/+bug/1886543

1 0

OpenStack (cinder) volumes retyping on Ceph back-end
by Andrea Martra 20 Jun '23

20 Jun '23

Hello, I configured different back-end storage on OpenStack (Yoga release) and using Ceph (ceph version 17.2.4) with different pools (volumes, cloud-basic, shared-hosting-os, shared-hosting-homes,...) for RBD application. I created different volume types towards each of the backends and everything works perfectly. If I perform a "change volume type" from OpenStack on volumes attached to the VMs the system successfully migrates the volume from the source pool to the destination pool and at the end of the process the volume is visible in the new pool and is removed from the old pool. The problem encountered is that when reconfiguring the VM, to specify the new pool associated with the volumes (performed through a resize of the VM, I haven't found any other method to change the information on the nova/cinder db automatically. I also did some tests shut-off of the VM and modification of the xml through virsh edit and startup the VM) the volume presented to the VM is exactly the version and content on the retype date of the volume itself. All data written and modified after the retype is lost. The VM after the retype continues to work perfectly in RW but the "new" volume created in the new pool is not used to write data and consequently when the VM is shut down all the changes are lost. Do you have any idea how to carry out a check and possibly how to proceed in order not to lose the data of the vm of which I have retyped the volume? The data is written somewhere (the IO is still going to the old pool/image although they already have been removed) because the VMs work perfectly. Thank you -- Andrea Martra +39 393 9048451

1 0

[kolla] rabbitmq failed to build image using 2023.1 release
by Satish Patel 20 Jun '23

20 Jun '23

Folks, Do you know how to solve this? I am using release 2023.1 of kolla to build images using ubuntu 22.04 root@docker-reg:/opt/kolla/etc/kolla# kolla-build --registry docker-reg:4000 --config-file kolla-build.conf --debug --threads 1 --skip-existing --push --cache --format none rabbitmq INFO:kolla.common.utils:Using engine: docker INFO:kolla.common.utils:Found the container image folder at /usr/local/share/kolla/docker INFO:kolla.common.utils:Added image rabbitmq to queue INFO:kolla.common.utils:Attempt number: 1 to run task: BuildTask(rabbitmq) DEBUG:kolla.common.utils.rabbitmq:Processing INFO:kolla.common.utils.rabbitmq:Building started at 2023-06-11 02:25:44.208880 DEBUG:kolla.common.utils.rabbitmq:Turned 0 plugins into plugins archive DEBUG:kolla.common.utils.rabbitmq:Turned 0 additions into additions archive INFO:kolla.common.utils.rabbitmq:Step 1/11 : FROM docker-reg:4000/kolla/base:2023.1 INFO:kolla.common.utils.rabbitmq: ---> 4551f4af8ddf INFO:kolla.common.utils.rabbitmq:Step 2/11 : LABEL maintainer="Kolla Project (https://launchpad.net/kolla)" name="rabbitmq" build-date="20230611" INFO:kolla.common.utils.rabbitmq: ---> Using cache INFO:kolla.common.utils.rabbitmq: ---> 6c2ef10499f7 INFO:kolla.common.utils.rabbitmq:Step 3/11 : RUN usermod --append --home /var/lib/rabbitmq --groups kolla rabbitmq && mkdir -p /var/lib/rabbitmq && chown -R 42439:42439 /var/lib/rabbitmq INFO:kolla.common.utils.rabbitmq: ---> Using cache INFO:kolla.common.utils.rabbitmq: ---> 29ef8940f40b INFO:kolla.common.utils.rabbitmq:Step 4/11 : RUN echo 'Uris: https://ppa.launchpadcontent.net/rabbitmq/rabbitmq-erlang/ubuntu' >/etc/apt/sources.list.d/erlang.sources && echo 'Components: main' >>/etc/apt/sources.list.d/erlang.sources && echo 'Types: deb' >>/etc/apt/sources.list.d/erlang.sources && echo 'Suites: jammy' >>/etc/apt/sources.list.d/erlang.sources && echo 'Signed-By: /etc/kolla/apt-keys/erlang-ppa.gpg' >>/etc/apt/sources.list.d/erlang.sources && echo 'Uris: https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu' >/etc/apt/sources.list.d/rabbitmq.sources && echo 'Components: main' >>/etc/apt/sources.list.d/rabbitmq.sources && echo 'Types: deb' >>/etc/apt/sources.list.d/rabbitmq.sources && echo 'Suites: jammy' >>/etc/apt/sources.list.d/rabbitmq.sources && echo 'Signed-By: /etc/kolla/apt-keys/rabbitmq.gpg' >>/etc/apt/sources.list.d/rabbitmq.sources INFO:kolla.common.utils.rabbitmq: ---> Using cache INFO:kolla.common.utils.rabbitmq: ---> 6d92a7342a90 INFO:kolla.common.utils.rabbitmq:Step 5/11 : RUN apt-get --error-on=any update && apt-get -y install --no-install-recommends logrotate rabbitmq-server && apt-get clean && rm -rf /var/lib/apt/lists/* INFO:kolla.common.utils.rabbitmq: ---> Running in 0deab7961445 INFO:kolla.common.utils.rabbitmq:Get:1 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope InRelease [5,463 B] INFO:kolla.common.utils.rabbitmq:Get:2 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB] INFO:kolla.common.utils.rabbitmq:Get:3 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [3,447 B] INFO:kolla.common.utils.rabbitmq:Get:7 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope/main amd64 Packages [126 kB] INFO:kolla.common.utils.rabbitmq:Get:8 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy InRelease [5,152 B] INFO:kolla.common.utils.rabbitmq:Get:9 https://ppa.launchpadcontent.net/rabbitmq/rabbitmq-erlang/ubuntu jammy InRelease [18.1 kB] INFO:kolla.common.utils.rabbitmq:Get:5 http://mirror.siena.edu/ubuntu jammy-updates InRelease [119 kB] INFO:kolla.common.utils.rabbitmq:Get:10 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages [9,044 B] INFO:kolla.common.utils.rabbitmq:Get:6 http://ftp.usf.edu/pub/ubuntu jammy-security InRelease [110 kB] INFO:kolla.common.utils.rabbitmq:Get:11 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [27.0 kB] INFO:kolla.common.utils.rabbitmq:Get:4 https://archive.linux.duke.edu/ubuntu jammy InRelease [270 kB] INFO:kolla.common.utils.rabbitmq:Get:12 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [49.4 kB] INFO:kolla.common.utils.rabbitmq:Get:14 http://ubuntu.osuosl.org/ubuntu jammy-updates/main amd64 Packages [857 kB] INFO:kolla.common.utils.rabbitmq:Get:17 https://ppa.launchpadcontent.net/rabbitmq/rabbitmq-erlang/ubuntu jammy/main amd64 Packages [8,167 B] INFO:kolla.common.utils.rabbitmq:Get:16 http://pubmirrors.dal.corespace.com/ubuntu jammy-security/universe amd64 Packages [928 kB] INFO:kolla.common.utils.rabbitmq:Get:15 https://atl.mirrors.clouvider.net/ubuntu jammy-security/main amd64 Packages [575 kB] INFO:kolla.common.utils.rabbitmq:Get:19 http://www.club.cc.cmu.edu/pub/ubuntu jammy/main amd64 Packages [1,792 kB] INFO:kolla.common.utils.rabbitmq:Get:18 http://mirror.team-cymru.com/ubuntu jammy/universe amd64 Packages [17.5 MB] INFO:kolla.common.utils.rabbitmq:Get:13 http://mirrors.syringanetworks.net/ubuntu-archive jammy-updates/universe amd64 Packages [1,176 kB] INFO:kolla.common.utils.rabbitmq:Fetched 23.7 MB in 6s (4,091 kB/s) INFO:kolla.common.utils.rabbitmq:Reading package lists... INFO:kolla.common.utils.rabbitmq:Reading package lists... INFO:kolla.common.utils.rabbitmq:Building dependency tree... INFO:kolla.common.utils.rabbitmq:Reading state information... INFO:kolla.common.utils.rabbitmq:Some packages could not be installed. This may mean that you have INFO:kolla.common.utils.rabbitmq:requested an impossible situation or if you are using the unstable INFO:kolla.common.utils.rabbitmq:distribution that some required packages have not yet been created INFO:kolla.common.utils.rabbitmq:or been moved out of Incoming. INFO:kolla.common.utils.rabbitmq:The following information may help to resolve the situation: INFO:kolla.common.utils.rabbitmq:The following packages have unmet dependencies: INFO:kolla.common.utils.rabbitmq: rabbitmq-server : Depends: erlang-base (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: erlang-base-hipe (< 1:26.0) but it is not installable or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-crypto (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-eldap (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-inets (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-mnesia (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-os-mon (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-parsetools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-public-key (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-runtime-tools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-ssl (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-syntax-tools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-tools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq: Depends: erlang-xmerl (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or INFO:kolla.common.utils.rabbitmq: esl-erlang (< 1:26.0) but it is not installable INFO:kolla.common.utils.rabbitmq:E: Unable to correct problems, you have held broken packages. INFO:kolla.common.utils.rabbitmq:

3 8

[tc] Technical Committee next weekly meeting on June 20, 2023
by Nikolla, Kristi 20 Jun '23

20 Jun '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, June 20, 2023 at 1800 UTC on #openstack-tc on OFTC IRC. Please find below the agenda for the meeting: * Roll call * Follow up on past action items * Open Infra Summit retrospective * Gate health check * Open Discussion and Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open More information can be found and items proposed at the following link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Thank you, Kristi Nikolla

1 0

[puppet] Summary of discussions at PTG Vancouver June 2023
by Takashi Kajinami 20 Jun '23

20 Jun '23

Hello, Thank you all for joining our PTG session ! It was really nice to meet some of the team members in person. The etherpad for the discussion can be found in the link below, but I'll share a summary of our discussions in this email. In case you have any questions/concerns then feel free to let me know. https://etherpad.opendev.org/p/vancouver-june2023-puppet-openstack - Status update - We share the status of each person. - Unfortunately all of the members attending the discussion have limited resources especially for development - *Agreement:* we focus on priorities and de-prioritize items which does not cause immediate problems/breackages - *Agreement: *we ensure we finish the prioritized items in a specific release to keep our maintenance simple - Puppet 8 support - We added unit/lint tests with Puppet 8 for early testing, but adding integration tests is currently blocked by some ruby dependencies not yet available for Ruby 3.1 which is required by Puppet 8. - All of the operating system versions do not provide Ruby 3.1 now - Puppet 7 EOL is not yet declared - *Agreement*: We leave this as non-priority for now and re-work on it once Ruby 3.1 is globally available - Adaptation to puppetlab-stdlib 9.0.0 - Some deprecated items were removed. We adapted our modules but are still waiting for update in the dependent modules - validate_legacy was deprecated and causes large warning no*w* - Functions from stdlib should be now namespace-d to avoid warnings after bump is done - *Agreement:* We prioritize replacing validate_legacy by typed parameters - *Agreement*: We pin stdlib to an older version for now but attempt to bump it early - Module modernizations - Typed parameters - Replacing validate_legacy needs to be prioritized now to adapt to puppetlab-stdlib 9.0.0 - Implementing type validations for openstack config options require further discussions. Handling of os_service_defualt would be the main topic we have to sort - We prefer consistent implementations for all openstack service modules, while we can attempt some changes early in a few "independent" modules such as extras, vswitch, qdr - *Agreement: *We de-prioritize implementing validations for config options - *Agreement: *We ensure implementations is distributed to all modules consistently in a single release - Hieradata - This is "modern" design pattern, and it's ideal to replace legacy params class by it - However we don't have urgent requirement to complete this work - We have to create the common structure for hieradata files maintained in each repositories - Some concerns have been raised mainly how we can pick up some values once this change is made - *Agreement: *We de-prioritize this work for now - *Agreement: *We can start with the flat files (pattern 1 in https://etherpad.opendev.org/p/puppet-hieradata-structure ) - *Agreement: *tkajinam will submit a few examples and we review how this impact the existing usage - *Agreement: *Similarly to typed parameters, we should coordinate this work to make the change consistently - Making distro/version specific logic selectable by parameters - This work is tightly related to the hieradata work - *Agreement: *We basically leave this work until the above hieradata work is completed, and de-prioritize this. - Branch retirements - We have multiple branches open now and aim to reduce number of branches - Red Hat is interested in keeping train open until 2023Q3 (tentative) and wallaby for some times for donwstream - Others do not have requirement to maintain old releases in EM status - *Agreement: *We aim to retire train/ussuri/branch after 2023Q3. Retiring further branches is subject to future discussions Thank you, Takashi Kajinami

2 1

[nova] Summary of discussions at Vancouver June 2023 (PTG + Forum meet&greet)
by Sylvain Bauza 20 Jun '23

20 Jun '23

Thanks folks that were joining our PTG but also our meet&greet forum session ! IT was again a productive week for us, as we were able to discuss with a lot of operators during around 4 hours (3.30' for the PTG and 30 mins for the forum session) Below you'll find the summary of all the topics we discussed during those hours but you can also look at the etherpads directly : * Nova meet&greet https://etherpad.opendev.org/p/nova-vancouver2023-meet-and-greet * Nova PTG sessions https://etherpad.opendev.org/p/vancouver-june2023-nova While there were unfortunately very few Nova maintainers and developers in both rooms, we've seen a packed room for the meet&greet and then at every hour of the PTG, we got at least one operator wanting to discuss with us. Can't tell how much I love this, hopefully we'll continue to discuss it between us afterwards. Now, let me tell you the summary : === Short survey at the meet&greet === * most of the operators (~21) in the meet&greet were either running Train or Yoga. Some of them were already running 2023.1 Antelope. Wow. * all of them were running libvirt but one running ironic driver. * using virtual GPUs/mdevs and setting flavors to define CPU usage were the two most in-use features (the next one is SR-IOV) * accordingly, the most needed missing quotas are for PCI devices, obviously. === Pain points at the meet&greet === * Availability zones : Basically, some operators use massively AZs and they want to get off some AZ (even if the instance is pinned) for maintenance reasons. We continued to discuss this usecase at the PTG (see below) * Update of userdata : we said this was coming with a proposed spec * Filtering flavors by a resource : this would require a nova spec * Hard affinity problems : we continued to discuss this at the PTG (see below) * Ceph backend for Nova compute and need for local ephemeral storage (case of GPUs) : this should be discussed in a spec * attach/detach issues with BDMs : we said this is a known issue, some bug report has to be filled for proper triaging * state of CVEs and the fact that old releases are still impacted : this is known and relates to the state of Extended Maintenance releases, which was addressed by another Forum session. === The PTG === * Affinity/Anti-affinity migration problems if hard policy : we explained the consensus we had at the Bobcat vPTG and a Bloomberg operator kindly volunteered to capture this agreement in a backlog spec (tl,dr: allow operators to violate the policy and let the servergroup API show the violation). More to come hopefully soon. * Exposing metrics : Some operator explained how the current use of Prometheus exporter is super slow since it's using the Nova APIs for gathering usage metrics. We proposed him to look into using Placement APIs for such case, he'll test and eventually come back to us if the existing Placement APIs aren't viable for him. * memfd-backed memory backing per instance : there are multiple concerns that need to be addressed in a spec. For example, we need to ensure the flavor extraspec is driver-agnostic, we need to care about the defaults and the potential upgrade concerns (like changing from anonymous to memfd) and how to interact with the existing hugepages feature in Nova. * using virtio9p instead of virtiofs for Manila shares : we discussed it intensively to eventually come up to the conclusion this wasn't worth the effort to implement it. Let's revisit this decision by the next PTG if no progress has been made on virtiofs migration feature gaps. * Manila/Nova cross-project PTG discussion on Manila share support : we discussed on the next Manila features (lock API and use of service roles). We agreed on the mandatory Nova configuration for service roles as a requirement for Manila shares usage. We also agreed on Manila storing the instance UUID as the semaphore for the lock API. FWIW, there was a packed table with 7 operators (all public clouds) *REALLY* interested in this feature [1]. That's it for Nova-related bits at Vancouver but other topics were worth being discussed. You can find the list of all discussed Forum sessions here : https://wiki.openstack.org/wiki/Forum/Vanvouver2023 I've found particular interest in the ExtendedMaintainance potential abandon discussion, OSC and SDK sessions, live-migration usecases and problems and a couple of others. I'd urge you to glance at all etherpads' contents. [1] https://photos.app.goo.gl/t1tSyk67GG6TRRW59 HTH, -Sylvain

1 0

[neutron] Bug deputy report (June-12 - June-18)
by Lajos Katona 19 Jun '23

19 Jun '23

Hey Neutrinos, I was the bug deputy last week, so I send the summary from last week. GATE ISSUES: these seems to be related to OVN version bump and https://review.opendev.org/c/openstack/neutron/+/883681: * Gate: Fuctional test_virtual_port_host_update failes recently (#link https://bugs.launchpad.net/neutron/+bug/2023634 ) ** *Unassigned* * [trunk ports] subport doesn't reach status ACTIVE (#link https://bugs.launchpad.net/neutron/+bug/2024160 ) ** *Unassigned* HIGH * n-d-r: Peering failing on mixed IPv4 + IPv6 updates (#link https://bugs.launchpad.net/neutron/+bug/2023632 ) ** Dr. Jens Harbott * [OVN] Hash Ring nodes removed when "periodic worker" is killed (#link https://bugs.launchpad.net/neutron/+bug/2024205 ) ** Lucas Alvares Gomes * Adding a static route to router returns internal server error (#link https://bugs.launchpad.net/neutron/+bug/2024251 ) ** *Unassigned* MEDIUM * [sqlalchemy-20] Remove redundant indexes of some tables (#link https://bugs.launchpad.net/neutron/+bug/2024044 ) ** Rodolfo Alonso * OVN: Removal of chassis results in unbalanced distribution of LRPs (#link https://bugs.launchpad.net/neutron/+bug/2023993 ) ** *Unassigned* * create_subnet policy allows users to create subnet in the shared networks (#link https://bugs.launchpad.net/neutron/+bug/2023679 ) ** Slawek Kaplonski Lajos Katona (lajoskatona)

1 0

[heat] Heat discussions at PTG Vancouver June 2023
by Takashi Kajinami 19 Jun '23

19 Jun '23

Hello, Thank you all who attended the PTG discussions last week at Vancouver. We were small but it was nice to meet/see you in person and discuss how we can improve our projects I'll share a summary of the PTG discussions and also a few more topics related to our projects, which were discussed during Forum sessions. Please let me know if you have any questions or concerns. PTG sessions: - We exchanged information about how we use heat downstream. Jonathan and Alan from Georgia Cyber Center explained their quite interesting usage to launch an lab environment for their end users. - There are still a number of resource properties not yet supported by Heat but we want to prioritize implementations according to actual needs. We suggested creating a storyboard story in case any user finds out any missing properties to cover their use case. - Jonathan shared a very nice demo about their visualizer of heat stacks[1], which gives more meaningful visualization based on resource types. We agreed this can replace the current implementation in heat dashboard. We agreed that we'll explore if we can integrate this and deprecate the current implementation. [1] https://gitlab.com/gacybercenter/open/openstack-top-graph Forum sessions: - In SRBAC sessions status of individual projects were shared. Heat is lagging behind now and we have to focus on completing step 1(removing system scope). - In TC/Community Leaders communication, we agreed we are setting a timeline to bump sqlalchemy to 2.0 (followup would be sent separately). We removed usage of sqlalchemy-migrate as the first step to adapt sqlalchemy 2.0 but we still need some work for full adoption. We first need to add some testing as was done in Neutron already. Thank you, Takashi Kajinami

1 0

[nova] update_resources_interval parameter
by Arnaud Morin 19 Jun '23

19 Jun '23

Hey team, I'd like to understand the stakes behing the update_resources_interval parameter ([1]) We decided on our side to increase this value from 60sec to 600sec (see [2]). What I understand is that is will "delay" the update of metrics on nova side. I mostly think that these metrics are used by filter scheduler to select the best host when scheduling. Is there anything else it can affect? Cheers, Arnaud. [1] https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.up… [2] https://review.opendev.org/c/openstack/large-scale/+/886166

3 3

[kolla-ansible][zun] Deleting container within code without authentication
by James Leong 19 Jun '23

19 Jun '23

Hi all, I am currently playing around with the Zun component. I have deployed the yoga version of OpenStack using kolla-ansible. Is there a way to delete a container in the code base by giving the container id? It seems like without the proper context or authentication information, I will not be able to remove the container when calling the delete function in zun/api/controllers/v1/containers.py since the compute_api will not work. Would it be possible to create fake admin info within the code to enforce the container to be deleted? Apart from that, how can I create a compute API object from scratch? Best, Jame

1 0

[tripleo] Gate blocker - CentOS 9 jobs
by Ronelle Landy 17 Jun '23

17 Jun '23

Hello All, There is currently a failure on CentOS 9 jobs that is impacting check/gate and periodic jobs - causing Tempest jobs to fail. The details of the issue are in: https://bugs.launchpad.net/tripleo/+bug/2023764. A workaround is being tested. We will update this thread when the gate is unblocked. Thank you, CI Team

1 1

[kolla] User forum Etherpad link
by Michał Nasiadka 17 Jun '23

17 Jun '23

Hello Koalas, Thank you for attending the Kolla User forum on the Vancouver summit. You can check out the etherpad [1] for notes. [1]: https://etherpad.opendev.org/p/YVR23-kolla-user-forum Michal

1 0

[all][db] Lots of redundant DB indices ?
by Christian Rohmann 16 Jun '23

16 Jun '23

Helolo openstack-discuss! I recently saw lots of warnings the like of: "/usr/lib/python3/dist-packages/pymysql/cursors.py:170: Warning: (1831, 'Duplicate index `uniq_instances0uuid`. This is deprecated and will be disallowed in a future release') result = self._query(query)" This originated from MySQL error 1831 (see [1]). I then raised a few bugs and also did some changes in regards to the duplicate indices I noticed: * Placement https://storyboard.openstack.org/#!/story/2010251 <https://storyboard.openstack.org/#!/story/2010251> / https://review.opendev.org/c/openstack/placement/+/856770 <https://review.opendev.org/c/openstack/placement/+/856770> * Keystone - https://bugs.launchpad.net/keystone/+bug/1988297 <https://bugs.launchpad.net/keystone/+bug/1988297> / https://review.opendev.org/c/openstack/keystone/+/885463 <https://review.opendev.org/c/openstack/keystone/+/885463> * Neutron - https://bugs.launchpad.net/neutron/+bug/1988421 <https://bugs.launchpad.net/neutron/+bug/1988421> / https://review.opendev.org/c/openstack/neutron/+/885456 <https://review.opendev.org/c/openstack/neutron/+/885456> * Nova - https://review.opendev.org/c/openstack/nova/+/856757 <https://review.opendev.org/c/openstack/nova/+/856757> But running Percona's pt-duplicate-key-checker ([2]) there are quite a few more redundant indices reported: > ALTER TABLE `cinder`.`driver_initiator_data` DROP INDEX > `ix_driver_initiator_data_initiator`; ALTER TABLE > `cinder`.`quota_usages` DROP INDEX `ix_quota_usages_project_id`; ALTER > TABLE `cinder`.`quota_usages` DROP INDEX > `quota_usage_project_resource_idx`; ALTER TABLE `designate`.`records` > DROP FOREIGN KEY `records_ibfk_2`; ALTER TABLE > `designate`.`recordsets` DROP INDEX `rrset_zoneid`; ALTER TABLE > `designate`.`recordsets` DROP INDEX `rrset_type`; ALTER TABLE > `glance`.`image_members` DROP INDEX `ix_image_members_image_id`; ALTER > TABLE `glance`.`image_members` DROP INDEX > `ix_image_members_image_id_member`; ALTER TABLE > `glance`.`image_properties` DROP INDEX `ix_image_properties_image_id`; > ALTER TABLE `glance`.`image_tags` DROP INDEX `ix_image_tags_image_id`; > ALTER TABLE `keystone`.`access_rule` DROP INDEX `external_id`; ALTER > TABLE `keystone`.`access_rule` DROP INDEX `user_id`; ALTER TABLE > `keystone`.`project_tag` DROP INDEX `project_id`; ALTER TABLE > `keystone`.`token` DROP INDEX `ix_token_expires`; ALTER TABLE > `mysql`.`transaction_registry` DROP INDEX `commit_timestamp`, ADD > INDEX `commit_timestamp` (`commit_timestamp`); ALTER TABLE > `neutron`.`addressgrouprbacs` DROP INDEX > `ix_addressgrouprbacs_target_project`; ALTER TABLE > `neutron`.`addressscoperbacs` DROP INDEX > `ix_addressscoperbacs_target_project`; ALTER TABLE > `neutron`.`floatingipdnses` DROP INDEX > `ix_floatingipdnses_floatingip_id`; ALTER TABLE > `neutron`.`networkdnsdomains` DROP INDEX > `ix_networkdnsdomains_network_id`; ALTER TABLE > `neutron`.`networkrbacs` DROP INDEX `ix_networkrbacs_target_project`; > ALTER TABLE `neutron`.`ovn_hash_ring` DROP INDEX > `ix_ovn_hash_ring_node_uuid`; ALTER TABLE > `neutron`.`ovn_revision_numbers` DROP INDEX > `ix_ovn_revision_numbers_resource_uuid`; ALTER TABLE > `neutron`.`portdataplanestatuses` DROP INDEX > `ix_portdataplanestatuses_port_id`; ALTER TABLE `neutron`.`portdnses` > DROP INDEX `ix_portdnses_port_id`; ALTER TABLE `neutron`.`ports` DROP > INDEX `ix_ports_network_id_mac_address`; ALTER TABLE > `neutron`.`portuplinkstatuspropagation` DROP INDEX > `ix_portuplinkstatuspropagation_port_id`; ALTER TABLE > `neutron`.`qos_minimum_bandwidth_rules` DROP INDEX > `ix_qos_minimum_bandwidth_rules_qos_policy_id`; ALTER TABLE > `neutron`.`qos_minimum_packet_rate_rules` DROP INDEX > `ix_qos_minimum_packet_rate_rules_qos_policy_id`; ALTER TABLE > `neutron`.`qos_packet_rate_limit_rules` DROP INDEX > `ix_qos_packet_rate_limit_rules_qos_policy_id`; ALTER TABLE > `neutron`.`qos_policies_default` DROP INDEX > `ix_qos_policies_default_project_id`; ALTER TABLE > `neutron`.`qospolicyrbacs` DROP INDEX > `ix_qospolicyrbacs_target_project`; ALTER TABLE `neutron`.`quotas` > DROP INDEX `ix_quotas_project_id`; ALTER TABLE `neutron`.`quotausages` > DROP INDEX `ix_quotausages_project_id`; ALTER TABLE > `neutron`.`securitygrouprbacs` DROP INDEX > `ix_securitygrouprbacs_target_project`; ALTER TABLE > `neutron`.`segmenthostmappings` DROP INDEX > `ix_segmenthostmappings_segment_id`; ALTER TABLE > `neutron`.`subnet_dns_publish_fixed_ips` DROP INDEX > `ix_subnet_dns_publish_fixed_ips_subnet_id`; ALTER TABLE > `neutron`.`subnetpoolrbacs` DROP INDEX > `ix_subnetpoolrbacs_target_project`; ALTER TABLE `nova`.`agent_builds` > DROP INDEX `agent_builds_hypervisor_os_arch_idx`; ALTER TABLE > `nova`.`block_device_mapping` DROP INDEX > `block_device_mapping_instance_uuid_idx`; ALTER TABLE > `nova`.`console_auth_tokens` DROP INDEX > `console_auth_tokens_token_hash_idx`; ALTER TABLE `nova`.`fixed_ips` > DROP INDEX `address`; ALTER TABLE `nova`.`fixed_ips` DROP INDEX > `network_id`; ALTER TABLE `nova`.`instance_actions` DROP INDEX > `instance_uuid_idx`; ALTER TABLE `nova`.`instance_type_extra_specs` > DROP INDEX `instance_type_extra_specs_instance_type_id_key_idx`; ALTER > TABLE `nova`.`instance_type_projects` DROP INDEX `instance_type_id`; > ALTER TABLE `nova`.`instances` DROP INDEX `uniq_instances0uuid`; ALTER > TABLE `nova`.`instances` DROP INDEX `instances_project_id_idx`; ALTER > TABLE `nova`.`inventories` DROP INDEX > `inventories_resource_provider_id_idx`; ALTER TABLE > `nova`.`inventories` DROP INDEX > `inventories_resource_provider_resource_class_idx`; ALTER TABLE > `nova`.`networks` DROP INDEX `networks_vlan_deleted_idx`; ALTER TABLE > `nova`.`resource_providers` DROP INDEX `resource_providers_name_idx`; > ALTER TABLE `nova`.`resource_providers` DROP INDEX > `resource_providers_uuid_idx`; ALTER TABLE `nova_api`.`build_requests` > DROP INDEX `build_requests_instance_uuid_idx`; ALTER TABLE > `nova_api`.`cell_mappings` DROP INDEX `uuid_idx`; ALTER TABLE > `nova_api`.`flavor_extra_specs` DROP INDEX > `flavor_extra_specs_flavor_id_key_idx`; ALTER TABLE > `nova_api`.`host_mappings` DROP INDEX `host_idx`; ALTER TABLE > `nova_api`.`instance_mappings` DROP INDEX `instance_uuid_idx`; ALTER > TABLE `nova_api`.`inventories` DROP INDEX > `inventories_resource_provider_id_idx`; ALTER TABLE > `nova_api`.`inventories` DROP INDEX > `inventories_resource_provider_resource_class_idx`; ALTER TABLE > `nova_api`.`placement_aggregates` DROP INDEX > `ix_placement_aggregates_uuid`; ALTER TABLE > `nova_api`.`project_user_quotas` DROP INDEX > `project_user_quotas_user_id_idx`; ALTER TABLE > `nova_api`.`request_specs` DROP INDEX > `request_spec_instance_uuid_idx`; ALTER TABLE > `nova_api`.`resource_providers` DROP INDEX > `resource_providers_name_idx`; ALTER TABLE > `nova_api`.`resource_providers` DROP INDEX > `resource_providers_uuid_idx`; ALTER TABLE `nova_cell0`.`agent_builds` > DROP INDEX `agent_builds_hypervisor_os_arch_idx`; ALTER TABLE > `nova_cell0`.`block_device_mapping` DROP INDEX > `block_device_mapping_instance_uuid_idx`; ALTER TABLE > `nova_cell0`.`console_auth_tokens` DROP INDEX > `console_auth_tokens_token_hash_idx`; ALTER TABLE > `nova_cell0`.`fixed_ips` DROP INDEX `address`; ALTER TABLE > `nova_cell0`.`fixed_ips` DROP INDEX `network_id`; ALTER TABLE > `nova_cell0`.`instance_actions` DROP INDEX `instance_uuid_idx`; ALTER > TABLE `nova_cell0`.`instance_type_extra_specs` DROP INDEX > `instance_type_extra_specs_instance_type_id_key_idx`; ALTER TABLE > `nova_cell0`.`instance_type_projects` DROP INDEX `instance_type_id`; > ALTER TABLE `nova_cell0`.`instances` DROP INDEX `uniq_instances0uuid`; > ALTER TABLE `nova_cell0`.`instances` DROP INDEX > `instances_project_id_idx`; ALTER TABLE `nova_cell0`.`inventories` > DROP INDEX `inventories_resource_provider_id_idx`; ALTER TABLE > `nova_cell0`.`inventories` DROP INDEX > `inventories_resource_provider_resource_class_idx`; ALTER TABLE > `nova_cell0`.`networks` DROP INDEX `networks_vlan_deleted_idx`; ALTER > TABLE `nova_cell0`.`resource_providers` DROP INDEX > `resource_providers_name_idx`; ALTER TABLE > `nova_cell0`.`resource_providers` DROP INDEX > `resource_providers_uuid_idx`; ALTER TABLE `placement`.`inventories` > DROP INDEX `inventories_resource_provider_id_idx`; ALTER TABLE > `placement`.`inventories` DROP INDEX > `inventories_resource_provider_resource_class_idx`; ALTER TABLE > `placement`.`placement_aggregates` DROP INDEX > `ix_placement_aggregates_uuid`; ALTER TABLE > `placement`.`resource_providers` DROP INDEX > `resource_providers_name_idx`; ALTER TABLE > `placement`.`resource_providers` DROP INDEX > `resource_providers_uuid_idx`; > # > ######################################################################## > # Summary of indexes # > ######################################################################## > # Size Duplicate Indexes 35810 # Total Duplicate Indexes 84 # Total > Indexes 1792 (When adding more services (Telemetry, ...) there are even more indices reported.) Does it make sense to address this more broadly maybe? Especially with all the changes happening for SQLAlchemy 2.x currently? Regards Christian [1] https://mariadb.com/kb/en/mariadb-error-codes/ [2] https://docs.percona.com/percona-toolkit/pt-duplicate-key-checker.html

2 2

[kolla-ansible][zun][cinder] Restricting the amount of disk when creating containers
by James Leong 16 Jun '23

16 Jun '23

Hi all, I am using the yoga version of OpenStack with the deployment tool of kolla-ansible. How would I create a container on the horizon dashboard with a specific disk size? Every time when I create a container, I get the below error. "Your host does not support the disk quota feature." Is it essential to have a cinder (Volume set up)? I have not enabled Cinder in my use case. If so, would it be possible to provide some information regardless of how I can enable Cinder on OpenStack? In the past month, I attempted to enable Cinder, but it never worked on my site. Thanks for your help, James

2 1

[ptg][tacker] Tacker PTG schedule
by Yasufumi Ogawa 16 Jun '23

16 Jun '23

Hi team, We are going to have our PTG session on this Thursday 15:00-17:50 UTC at room 10. We also have setup webex so that you can join from remote. See tacker's etherpad for the link of the remote session. https://etherpad.opendev.org/p/vancouver-june2023-tacker Thanks, Yasufumi

2 1

[neutron][ptg] Neutron PTG sessions
by Rodolfo Alonso Hernandez 16 Jun '23

16 Jun '23

Hello Neutrinos: Just a heads-up: we are in table 15 in the ballroom. You are welcome to join us to ask any question, make any suggestion or just for a cup of coffee. See you!

1 0

missing erlang-base_25.3.2.2-1rmq1ppa1~ubuntu22.04.1_amd64.deb
by Michal Arbet 15 Jun '23

15 Jun '23

Hello, We are installing rabbitmq-server from https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/debian and erlang from your ppa repository *ppa:rabbitmq/rabbitmq-erlang*. We have erlang pinned as below Package: erlang* Pin: version 1:25.* Pin-Priority: 1000 Problem is that you removed erlang-base_25* and there is only erlang-base_26.0.1-1rmq1ppa1~ubuntu22.04.1_arm64.deb Please, is there any reason why you removed erlang-base_25* for other ubuntu versions ? Because I can see 25* version for ubuntu 18.04 only Please, can u help us and upload erlang 25* also for other ubuntu versions ? Thank you very much Log below : ()[root@builder /]# apt update;apt install rabbitmq-server Get:1 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB] Get:2 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope InRelease [5,463 B] Get:3 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [228 B] Get:7 https://ppa.launchpadcontent.net/rabbitmq/rabbitmq-erlang/ubuntu jammy InRelease [18.1 kB] Get:8 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy InRelease [5,152 B] Get:4 http://ftp.cvut.cz/ubuntu jammy InRelease [270 kB] Get:9 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/antelope/main amd64 Packages [126 kB] Get:5 http://ucho.ignum.cz/ubuntu jammy-updates InRelease [119 kB] Get:6 https://mirror.it4i.cz/ubuntu jammy-security InRelease [110 kB] Get:10 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [49.4 kB] Get:11 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [27.0 kB] Get:12 https://ppa.launchpadcontent.net/rabbitmq/rabbitmq-erlang/ubuntu jammy/main amd64 Packages [8,167 B] Get:13 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages [9,044 B] Get:14 http://ftp.cvut.cz/ubuntu jammy-updates/universe amd64 Packages [1,178 kB] Get:15 https://mirror.it4i.cz/ubuntu jammy-updates/main amd64 Packages [861 kB] Get:16 https://cz.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB] Get:18 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages [579 kB] Get:19 https://mirror.it4i.cz/ubuntu jammy-security/universe amd64 Packages [928 kB] Get:17 https://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1,792 kB] Fetched 23.7 MB in 4s (6,499 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: rabbitmq-server : Depends: erlang-base (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or erlang-base-hipe (< 1:26.0) but it is not installable or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-crypto (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-eldap (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-inets (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-mnesia (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-os-mon (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-parsetools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-public-key (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-runtime-tools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-ssl (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-syntax-tools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-tools (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable Depends: erlang-xmerl (< 1:26.0) but 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 is to be installed or esl-erlang (< 1:26.0) but it is not installable E: Unable to correct problems, you have held broken packages. ()[root@builder /]# apt-cache policy rabbitmq-server ^[[Arabbitmq-server: Installed: (none) Candidate: 3.11.16-1 Version table: 3.12.0-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.18-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.17-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.16-1 1000 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.15-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.14-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.13-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.12-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.11-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.10-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.9-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.8-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.7-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.6-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.5-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.4-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.3-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.2-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.1-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.11.0-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.24-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.23-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.22-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.21-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.20-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.19-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.18-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.17-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.16-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.14-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.13-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.12-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.11-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.10-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.9-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.8-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.7-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.6-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.5-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.4-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.2-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.1-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.10.0-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.9.29-1 500 500 https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu jammy/main amd64 Packages 3.9.13-1ubuntu0.22.04.1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt jammy-updates/main amd64 Packages 3.9.13-1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt jammy/main amd64 Packages ()[root@builder /]# apt-cache policy erlang-base erlang-base: Installed: (none) Candidate: 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 Version table: 1:26.0.1-1rmq1ppa1~ubuntu22.04.1 500 500 https://ppa.launchpadcontent.net/rabbitmq/rabbitmq-erlang/ubuntu jammy/main amd64 Packages 1:24.2.1+dfsg-1ubuntu0.1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt jammy-updates/main amd64 Packages 500 mirror://mirrors.ubuntu.com/mirrors.txt jammy-security/main amd64 Packages 1:24.2.1+dfsg-1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt jammy/main amd64 Packages Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

4 15

[nova] [keystone] Default logrotate configuration for apache2
by hai wu 15 Jun '23

15 Jun '23

It seems the default logrotate configuration for apache2 log files from vanilla OS installation is to do the following daily: postrotate if invoke-rc.d apache2 status > /dev/null 2>&1; then \ invoke-rc.d apache2 reload > /dev/null 2>&1; \ fi; endscript Sometimes I noticed that not all log entries would show up for the same day after apache2 got reloaded. Also it seems redhat openstack switched its logrotate config to use copytruncate instead of reloading apache2 iirc. Is there some known issues with reloading apache2 daily for logrotate config? Sometimes there are keystone 503 errors, and I am wondering if that's related to the logrotate default config to reload apache2 daily..

2 1

[neutron][ptg] PTG sessions
by Rodolfo Alonso Hernandez 15 Jun '23

15 Jun '23

Hello Neutrinos: Thank you for your attendance to the meeting session yesterday and today to our PTG sessions in the ballroom. This mail is just a heads-up to remind you that we'll be in the ballroom tomorrow at 9:00AM too. You'll be welcome! If you have any questions and you think it will be helpful first to describe them "on paper", please use the Neutron etherpad: https://etherpad.opendev.org/p/vancouver-june2023-neutron. See you!

1 0

[ironic] ARM Support in CI: Call for vendors / contributors / interested parties
by Jay Faulkner 15 Jun '23

15 Jun '23

Hi stackers, Ironic has published an experimental Ironic Python Agent image for ARM64 ( https://tarballs.opendev.org/openstack/ironic-python-agent-builder/dib/file…) and discussed promoting this image to supported via CI testing. However, we have a problem: there are no Ironic developers with easy access to ARM hardware at the moment, and no Ironic developers with free time to commit to improving our support of ARM hardware. So we're putting out a call for help: - If you're a hardware vendor and want your ARM hardware supported? Please come talk to the Ironic community about setting up third-party-CI. - Are you an operator or contributor from a company invested in ARM bare metal? Please come join the Ironic community to help us build this support. Thanks, Jay Faulkner Ironic PTL

6 11

[scientific-sig] PTG session today, 11:00 PT
by Stig Telfer 15 Jun '23

15 Jun '23

Hi all - We have a Scientific SIG session today at the PTG, co-located at the Open Infra Summit. The session starts 11:00 at table 6 in the ground floor auditorium. Everyone is welcome. Cheers, Stig

1 0

[OSA] Multiple Deployment Hosts
by Murilo Morais 14 Jun '23

14 Jun '23

Good morning everybody! Is it possible to use another Host as Deployment Host? For example, if a problem occurs in the "primary" Deployment Host, use a second backup to perform some kind of intervention/change. Thanks in advance!

3 3

[cinder-backup] incremental backup on nfs and ceph
by garcetto 14 Jun '23

14 Jun '23

good morning, i was trying cinder-backup to backup cinder volumes from nfs backend and ceph rbd backend. both my test show that i can do incremental cinder-backup, but i dont get how technically the cinder-backup could "understand" the new incremental blocks from previous backup? maybe on ceph it leverages ceph-diff? but on nfs backend, how it knows changed blocks? thank you

2 1

Cinder Bug Report 2023-06-14
by Sofia Enriquez 14 Jun '23

14 Jun '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Low* - HPE 3par: Minor error occurs during retype of volume. <https://bugs.launchpad.net/cinder/+bug/2023253> - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/885440>. *Wishlist* - Prevent co-locating charms that may be conflicting with each other <https://bugs.launchpad.net/cinder/+bug/2022057>. - *Status*: I've removed cinder on the projects affected because the problem only affects Charms. 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

Community attendance - OpenInfra Summit Vancouver
by Roberto Bartzen Acosta 14 Jun '23

14 Jun '23

Hello, Will anyone from the Brazilian community attend the OpenInfra in Vancouver? I would like to meet other members from Brazil and discuss the challenges and possibilities of using OpenStack in Brazilian infrastructures. You can ping me on IRC too (racosta). Kind regards, Roberto -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

3 6

[storlets] Proposal to make Train/Ussuri/Victoria EOL
by Takashi Kajinami 14 Jun '23

14 Jun '23

Hello, Currently we have multiple stable branches open but we haven't seen any backport proposed so far. To reduce number of branches we have to maintain, I'd like to propose retiring old stable branches(train, ussuri and victoria). In case you have any concerns, please let me know. Thank you, Takashi Kajinami

1 1