February 2023 - openstack-discuss

ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat.| Openstack tripleo wallaby version
by Swogat Pradhan 24 Dec '24

24 Dec '24

Hi, I am currently trying to deploy openstack wallaby using tripleo arch. I created the network jinja templates, ran the following commands also: #openstack overcloud network provision --stack overcloud --output networks-deployed-environment.yaml custom_network_data.yaml # openstack overcloud network vip provision --stack overcloud --output vip-deployed-environment.yaml custom_vip_data.yaml # openstack overcloud node provision --stack overcloud --overcloud-ssh-key /home/stack/sshkey/id_rsa overcloud-baremetal-deploy.yaml and used the environment files in the openstack overcloud deploy command: (undercloud) [stack@hkg2director ~]$ cat deploy.sh #!/bin/bash THT=/usr/share/openstack-tripleo-heat-templates/ CNF=/home/stack/ openstack overcloud deploy --templates $THT \ -r $CNF/templates/roles_data.yaml \ -n $CNF/workplace/custom_network_data.yaml \ -e ~/containers-prepare-parameter.yaml \ -e $CNF/templates/node-info.yaml \ -e $CNF/templates/scheduler-hints.yaml \ -e $CNF/workplace/networks-deployed-environment.yaml \ -e $CNF/workplace/vip-deployed-environment.yaml \ -e $CNF/workplace/overcloud-baremetal-deployed.yaml \ -e $CNF/workplace/custom-net-bond-with-vlans.yaml Now when i run the ./deploy.sh script i encounter an error stating: ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command.: tripleoclient.exceptions.InvalidConfiguration: Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command. 2022-04-19 13:47:16.582 735924 INFO osc_lib.shell [-] END return value: 1 Can someone tell me where the mistake is? With regards, Swogat Pradhan

4 4

Kolla Ansible on Ubuntu 20.04 - cloud-init & other network issues
by Tobias McNulty 10 Oct '24

10 Oct '24

Hi, I'm attempting to use Kolla Ansible 14.6.0 to deploy OpenStack Yoga on a small 3-node Ubuntu 20.04 cluster. The nodes have 128 GB RAM each, dual Xeon processors, and dual 10G Intel NICs. The NICs are connected to access ports on a 10G switch with separate VLANs for the local and external networks. All the playbooks run cleanly, but cloud-init is failing in the Ubuntu 20.04 and 22.04 VMs I attempt to boot. The VM images are unmodified from https://cloud-images.ubuntu.com/, and cloud-init works fine if I mount a second volume with user-data. The error is a timeout attempting to reach 169.254.169.254. This occurs both when booting a VM in an internal routed network and directly in an external network. I tried various neutron plugin agents (ovn, linuxbridge, and openvswitch both with and without firewall_driver = openvswitch <https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro…>) first with a clean install of the entire OS each time, all with the same result. Running tcpdump looking for 169.254.169.254 shows nothing. As a possible clue, the virtual NICs are unable to pass any traffic (e.g., to reach an external DHCP server) unless I completely disable port security on the interface (even if the associated security group is wide open). But disabling port security does not fix cloud-init (not to mention I don't really want to disable port security). Are there any additional requirements related to deploying OpenStack with Kolla on Ubuntu 20.04? This is a fairly vanilla configuration using the multinode inventory as a starting point. I tried to follow the Quick Start <https://docs.openstack.org/kolla-ansible/yoga/user/quickstart.html> as closely as possible; the only material difference I see is that I'm using the same 3 nodes for control + compute. I am using MAAS so it's easy to get a clean OS install on all three nodes ahead of each attempt. I plan to try again with the standard (non-HWE) kernel just in case, but otherwise I am running out of ideas. In case of any additional clues, here are my globals.yml and inventory file, along with the playbook I'm using to configure the network, images, VMs, etc., after bootstrapping the cluster: https://gist.github.com/tobiasmcnulty/7dbbdbc67abc08cbb013bf5983852ed6 Thank you in advance for any advice! Cheers, Tobias

5 9

Live migration fails
by Szabo, Istvan (Agoda) 07 Aug '24

07 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

[ptl][tc] OpenStack packages PyPi additional external maintainers audit & cleanup
by Ghanshyam Mann 17 May '24

17 May '24

Hi PTLs, As you might know or have seen for your project package on PyPi, OpenStack deliverables on PyPi have additional maintainers, For example, https://pypi.org/project/murano/, https://pypi.org/project/glance/ We should keep only 'openstackci' as a maintainer in PyPi so that releases of OpenStack deliverables can be managed in a single place. Otherwise, we might face the two sets of maintainers' places and packages might get released in PyPi by additional maintainers without the OpenStack project team knowing about it. One such case is in Horizon repo 'xstatic-font-awesome' where a new maintainer is added by an existing additional maintainer and this package was released without the Horizon team knowing about the changes and release. - https://github.com/openstack/xstatic-font-awesome/pull/2 To avoid the 'xstatic-font-awesome' case for other packages, TC discussed it in their weekly meetings[1] and agreed to audit all the OpenStack packages and then clean up the additional maintainers in PyPi (keep only 'openstackci' as maintainers). To help in this task, TC requests project PTL to perform the audit for their project's repo and add comments in the below etherpad. - https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup Thanks to knikolla to automate the listing of the OpenStack packages with additional maintainers in PyPi which you can find the result in output.txt at the bottom of this link. I have added the project list of who needs to check their repo in etherpad. - https://gist.github.com/knikolla/7303a65a5ddaa2be553fc6e54619a7a1 Please complete the audit for your project before March 15 so that TC can discuss the next step in vPTG. [1] https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html#… -gmann

18 27

[Watcher] How use Watcher to scheduler Openstack resource without cpu_usage
by Nguyễn Hữu Khôi 06 Mar '24

06 Mar '24

Hello guys. I want to use watcher to scheduler openstack resources but some openstack versions are missing cpu_usage metric. How do we use Watcher without it? Thank you. Nguyen Huu Khoi

3 5

[designate] Proposal to deprecate the agent framework and agent based backends
by Michael Johnson 09 Jan '24

09 Jan '24

TLDR: The Designate team would like to deprecate the backend agent framework and the agent based backends due to lack of development and design issues with the current implementation. The following backends would be deprecated: Bind9 (Agent), Denominator, Microsoft DNS (Agent), Djbdns (Agent), Gdnsd (Agent), and Knot2 (Agent). Designate includes many backend DNS server drivers[1], many of which are "native" (also known as xfr type backends) backend implementations. In addition to the "native" backends, Designate has an agent backend[2] that supports other backends via an agent process. To quote the agent backend documentation[2]: This backend uses an extension[3] of the DNS protocol itself to send management requests to the remote agent processes, where the requests will be actioned. The rpc traffic between designate and the agent is both unauthenticated and unencrypted. Do not run this traffic over unsecured networks. Here are the reasons we are proposing to deprecate the agent framework now: 1. The agent protocol used by Designate is using an "unassigned"[4][5] DNS opcode (14) that is causing problems with the dnspython library >= 2.3.0 which is now validating the opcode when building DNS messages. It is a bad practice to use "unassigned" values as they may be officially assigned at any time, likely with an incompatible message format. 2. The agent backends are not tested in the OpenStack jobs[1]. 3. Many of the agent backends have been marked as "Experimental" since 2016 with no additional contributions beyond general repository code maintenance. 4. The protocol between the Designate worker process and the agent process is unauthenticated and unencrypted. 5. We do not know of a development resource to rewrite the agent framework protocol to address issue #1 and #4 above. 6. The introduction of catalog zones[6] may eliminate the need for some of the agent based backend drivers. By marking the agent framework and agent based backends "deprecated" in the Antelope cycle, we would remove the code no earlier than the "C" release of OpenStack (per the OpenStack deprecation policy[7]). In the meantime, issue #1 has been worked around by overriding the dnspython opcode validation[7] as needed in the Designate code (similar to a monkey patch). This is not a sustainable long term solution. The following backend agent based drivers would be marked "deprecated" in addition to the agent framework itself: Bind9 (Agent) Denominator Microsoft DNS (Agent) Djbdns (Agent) Gdnsd (Agent) Knot2 (Agent) We plan to propose patches for the deprecation over the next week, but will not merge them until at least January 24th to allow time for comment from the community. If you have concerns about this deprecation plan or are interested in rewriting the agent framework protocol to address the above issues, please reply to this announcement. Michael [1] https://docs.openstack.org/designate/latest/admin/support-matrix.html [2] https://docs.openstack.org/designate/latest/admin/backends/agent.html [3] https://github.com/openstack/designate/blob/master/designate/backend/privat… [4] https://www.rfc-editor.org/rfc/rfc6895.html#section-2.2 [5] https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-pa… [6] https://www.ietf.org/archive/id/draft-ietf-dnsop-dns-catalog-zones-08.txt [7] https://docs.openstack.org/project-team-guide/deprecation.html [8] https://review.opendev.org/c/openstack/designate/+/870678

3 13

[openstack-ansible] Recommended branch for a production environment?
by Roger Rivera 05 Sep '23

05 Sep '23

Hello, We have deployed Openstack-Ansible in a test environment and we were wondering what the recommended repository branch is to deploy in a production environment that will be integrated with a separate Ceph cluster. 1. We are thinking about pinning to the stable/zed. Is that recommended over the master branch? 2. Are bugs ironed out on both master and stable/zed with the same cadence? 3. Additionally, is Debian 11 a better alternative than Ubuntu 22 for target hosts? We noticed Ubuntu 22.04 support was added recently, whereas Debian 11 has been supported for quite some time now which leads us to believe its stability/integration could be more mature at this point? Any suggestions will be appreciated. Thank you, -- *Roger *

3 7

[puppet] Proposing core team clean up
by Takashi Kajinami 23 Aug '23

23 Aug '23

Hello, I went through the current core reviewers and found out that the current list includes some people no longer working in the OpenStack community. I'd like to propose removing the following persons from the core reviewer team as we haven't seen these people making any activity in the community recently. * Pradeep Kilambi - puppet-aodh, puppet-ceilometer, puppet-gnocchi, puppet-panko * Richard Megginson - puppet-keystone * Denis Egorenko - puppet-murano * Serg Melikyan - puppet-murano * Sergey Kolekonov - puppet-neutron * David Moreau Simard - puppet-openstack-integration * Yu xingchao - all modules Also, I confirmed that Wes Hayutin is no longer working for OpenStack and he agreed to retire from the core reviewer position. Thus I'll remove him as well. I'll be open for any feedback for one week to hear any thoughts/feedback about this removal. I'd like to take this moment to thank all people for their past work. We always welcome them back if they resume their work in this project. Thank you, Takashi KAJINAMI

3 4

[cloudkitty] question to the scope_key in cloudkitty
by Noah Elias Feldt 28 Jul '23

28 Jul '23

Hello! I am currently trying to get CloudKitty to work with the Prometheus Collector and PyScripts. I noticed that the scope_key for Prometheus can only be changed once in the global configuration file. This was a problem for me because we need different scope_keys for different metrics. Many of the metrics still need the scope key "tenant_id" and some others "project_id". I have found in the documentation of CloudKitty no way to change this for each metric, so I have internally changed something in the source code and added the function to set the scope_key for each metric individually. I just wanted to ask if you would be interested if I submit the small change upstream? Thank you. Regards Noah Feldt

3 3

[cinder] cinder-backup volume stuck in creating
by Satish Patel 27 Jul '23

27 Jul '23

Folks, I have configured nova and cinder with ceph storage. VMs running on ceph storage but now when i am trying to create a backup of cinder volume its getting stuck on creating and doing nothing. Logs also do not give any indication of bad. My cinder.conf [DEFAULT] enabled_backends = rbd-1 backup_driver = cinder.backup.drivers.ceph.CephBackupDriver backup_ceph_conf = /etc/ceph/ceph.conf backup_ceph_user = cinder-backup backup_ceph_chunk_size = 134217728 backup_ceph_pool = backups backup_ceph_stripe_unit = 0 backup_ceph_stripe_count = 0 restore_discard_excess_bytes = true osapi_volume_listen = 10.73.0.181 osapi_volume_listen_port = 8776 Output of "openstack volume service list" showing cinder-backup service is up but when i create a backup it's getting stuck in this stage and no activity. I am not seeing anything getting transferred to the ceph backups pool also. Any clue? or method to debug? # openstack volume backup list --all +--------------------------------------+------+-------------+----------+------+ | ID | Name | Description | Status | Size | +--------------------------------------+------+-------------+----------+------+ | bc844d55-8c5a-4bd3-b0e9-7c4c780c95ad | foo1 | | creating | 20 | +--------------------------------------+------+-------------+----------+------+

5 7

Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 22 Jul '23

22 Jul '23

Hello Kai, Great to hear that you’re interested! I’m currently just testing this as a POC directly in devstack so there is real-world testing (not should it yet I think, needs more development first). Best regards Tobias > On 30 Aug 2022, at 18:32, Kai Bojens <kb(a)kbojens.de> wrote: > > Am 29.08.22 um 15:46 schrieb Tobias Urdin: > >> If anybody, or any company, out there would be interested in collaborating in a project to bring this support and maintain it feel free to >> reach out. I’m hoping somebody will bite but atleast I’ve put it out there for all of you. > > Hi, > I am very much interested to take a closer look at your work and maybe contribute to it. Although I'm working with OpenStack for my employer at the moment, I'd do this in my spare time as I'm not sure that I can convince him to add another staging system with a full OpenStack installation just for developing a RabbitMQ replacement. That's not on our agenda as we are mostly users and not developers of OpenStack. > > As I'm pretty new to the messaging topic and had just heard of NATS and your idea, I'll first would have to dive into NATS and then I would take a closer look at your code and maybe try to create some documentation or tests. So, I can't promise anything but as I said I'm very interested in your approach as I also see the massive load from RabbitMQ. > > This brings me to the most important question: Where do you run and test your code? > > Greetings, > Kai

8 30

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

Kubernetes Conformance 1.24 + 1.25
by Kendall Nelson 05 Jun '23

05 Jun '23

Hello All! First of all, I want to say a huge thanks to Guilherme Steinmuller for all his help ensuring that OpenStack Magnum remains Kubernetes Certified [1]! We are certified for v1.24! However, in digging into the set of conformance tests this round, it appears that we will not be able to get 1.25 certified with the current Magnum. This means that in May when we have to re-cert (every 3 months they reach an EOL because that's k8s release cadence) we will not be able to maintain this which is the other part of why I wanted to write this email - to raise awareness and ask for help digging into what needs to happen to make sure we can retain this. Tangentially related, Guilherme has posted a patch with documentation for how to run the conformance tests for yourself and it could use some reviews [2]. And one last thing, I have begun conversation with the opendev folks about what it might take to setup jobs to run the conformance tests periodically so that we don't have to manually run them when it's time to recert. I am planning on submitting a forum topic for this for those interested :) Long live LOKI! - Kendall Nelson [1] https://github.com/cncf/k8s-conformance/pull/2446 [2] https://review.opendev.org/c/openstack/magnum/+/849156

5 10

[ironic][stable] Proposing EOL of ironic project branches older than Wallaby
by Jay Faulkner 02 Jun '23

02 Jun '23

Hi all, Ironic has a large amount of stable branches still in EM. We need to take action to ensure those branches are either retired or have CI repaired to the point of being usable. Specifically, I'm looking at these branches across all Ironic projects: - stable/queens - stable/rocky - stable/stein - stable/train - stable/ussuri - stable/victoria In lieu of any volunteers to maintain the CI, my recommendation for all the branches listed above is that they be marked EOL. If someone wants to volunteer to maintain CI for those branches, they can propose one of the below paths be taken instead: 1 - Someone volunteers to maintain these branches, and also report the status of CI of these older branches periodically on the Ironic whiteboard and in Ironic meetings. If you feel strongly that one of these branches needs to continue to be in service; volunteering in this way is how to save them. 2 - We seriously reduce CI. Basically removing all tempest tests to ensure that CI remains reliable and able to merge emergency or security fixes when needed. In some cases; this still requires CI fixes as some older inspector branches are failing *installing packages* in unit tests. I would still like, in this case, that someone volunteers to ensure the minimalist CI remains happy. My intention is to let this message serve as notice and a waiting period; and if I've not heard any response here or in Monday's Ironic meeting (in 6 days), I will begin taking action on retiring these branches. This is simply a start; other branches (including bugfix branches) are also in bad shape in CI, but getting these retired will significantly reduce the surface area of projects and branches to evaluate. I know it's painful to drop support for these branches; but we've provided good EM support for these branches for a long time and by pruning them away, we'll be able to save time to dedicate to other items. Thanks, Jay Faulkner

3 5

[magnum] Propose deprecation of Docker Swarm, CoreOS, fedora-ironic
by Jake Yip 28 Apr '23

28 Apr '23

Hi, Due to limited resources, Magnum team has decided to put most effort into supporting the most popular use case - Kubernetes on Fedora CoreOS. In light of that, we are seeking maintainers for the less well maintained drivers / COE - Docker Swarm, CoreOS and fedora-ironic drivers. The reasons are as follows: - Docker Swarm - It uses Fedora Atomic which has been EOL [1] - CoreOS - It is EOL [2] - fedora-ironic - Not tested, unsure if it is still working If anyone wants to take up maintenance of any of the above, we will be glad. Please let us know either through the ML or at the Magnum meetings. If there are no suitable maintainers, we will start the deprecation of these before end of Antelope. Regards, Jake [1]: https://projectatomic.io/blog/2019/11/fedora-atomic-host-nearing-eol/ [2]: https://www.redhat.com/en/technologies/cloud-computing/openshift/what-was-c… -- Jake Yip Magnum Team

2 3

Re: [all][stable][ptl] Propose to EOL Rocky series
by Elõd Illés 17 Apr '23

17 Apr '23

Hi, thanks for all the feedbacks from teams so far! @Zigo: Extended Maintenance process was created just for the same situation: to give space to interested parties to cooperate and keep things maintained even when stable releases are over their 'supported' lifetime. So it's good to see that there is interest in it! Unfortunately, with very old branches we've reached the state where gates can't be maintained and without a functional gate it's not safe to merge patches (yes, even security fixes) and they are just using resources (CI & maintainers' time). When gate is broken in such extent, then i think the community have to accept that it is not possible to merge patches confidently and needs to EOL that release. (Yes, it means that some vendors still have to do it for their own sake, testing it by their own, etc). Keeping things open in such state gives the false signal to vendors that 'it is maintained' however this is done without fully testing the changes. Another aspect is that code cannot be cleaned up until those old branches are still present (CI jobs, project configurations, etc) which gives pain for developers. So, however some vendors would appreciate probably to keep things open forever, for the community this is not beneficial and doable I think. Seeing that teams want to EOL their old branches is a proof that this is needed (unfortunately). Thanks, Előd Illés irc: elodilles @ #openstack-stable / #openstack-release ________________________________ From: Thomas Goirand <thomas(a)goirand.fr> Sent: Saturday, January 28, 2023 2:25 PM Cc: openstack-discuss(a)lists.openstack.org <openstack-discuss(a)lists.openstack.org> Subject: Re: [all][stable][ptl] Propose to EOL Rocky series Hi, I understand the gate is broken, however, Rocky is in Debian LTS, and I would like to keep the possibility to merge patches, even with the gate tests disabled. CVE-2022-47951 is an example why this is important... Thomas Goirand (zigo) On Jan 28, 2023 11:54, Radosław Piliszek <radoslaw.piliszek(a)gmail.com> wrote: > > Masakari is happy to EOL Rocky too. > > Radek > -yoctozepto > > On Fri, 27 Jan 2023 at 20:59, Jay Faulkner <jay(a)gr-oss.io> wrote: > > > > Thanks for doing all this cleanup work Elod. Ironic is OK with retirements of these shared resources up to Train. > > > > - > > Jay Faulkner > > > > On Fri, Jan 27, 2023 at 10:12 AM Elõd Illés <elod.illes(a)est.tech> wrote: > >> > >> Hi, > >> > >> Similarly like the Queens branch EOL proposal [1] I would like to propose > >> to transition every project's stable/rocky to End of Life: > >> > >> - gates are mostly broken > >> - minimal number of activity can be seen on this branch > >> - some core projects already transitioned their stable/rocky to EOL > >> recently (like ironic, neutron, nova) > >> - gate job definitions are still using the old, legacy zuul syntax > >> - gate jobs are based on Ubuntu Xenial, which is also beyond its public > >> maintenance window date and hard to maintain > >> > >> Based on the above, if there won't be any project who wants to keep open > >> their stable/rocky, then I'll start the process of EOL'ing Rocky stable > >> series as a whole. If anyone has any objection then please respond to > >> this mail. > >> > >> Thanks, > >> > >> Előd Illés > >> irc: elodilles @ #openstack-stable / #openstack-release > >> > >> [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-October/031030… > >> >

3 4

DCN compute service goes down when a instance is scheduled to launch | wallaby | tripleo
by Swogat Pradhan 28 Mar '23

28 Mar '23

Hi, I currently have 3 compute nodes on edge site1 where i am trying to launch vm's. When the VM is in spawning state the node goes down (openstack compute service list), the node comes backup when i restart the nova compute service but then the launch of the vm fails. nova-compute.log 2023-02-26 08:15:51.808 7 INFO nova.compute.manager [req-bc0f5f2e-53fc-4dae-b1da-82f1f972d617 - - - - -] Running instance usage audit for host dcn01-hci-0.bdxworld.com from 2023-02-26 07:00:00 to 2023-02-26 08:00:00. 0 instances. 2023-02-26 08:49:52.813 7 INFO nova.compute.claims [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Claim successful on node dcn01-hci-0.bdxworld.com 2023-02-26 08:49:54.225 7 INFO nova.virt.libvirt.driver [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Ignoring supplied device name: /dev/vda. Libvirt can't honour user-supplied dev names 2023-02-26 08:49:54.398 7 INFO nova.virt.block_device [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Booting with volume c4bd7885-5973-4860-bbe6-7a2f726baeee at /dev/vda 2023-02-26 08:49:55.216 7 WARNING nova.cache_utils [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Cache enabled with backend dogpile.cache.null. 2023-02-26 08:49:55.283 7 INFO oslo.privsep.daemon [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Running privsep helper: ['sudo', 'nova-rootwrap', '/etc/nova/rootwrap.conf', 'privsep-helper', '--config-file', '/etc/nova/nova.conf', '--config-file', '/etc/nova/nova-compute.conf', '--privsep_context', 'os_brick.privileged.default', '--privsep_sock_path', '/tmp/tmpin40tah6/privsep.sock'] 2023-02-26 08:49:55.791 7 INFO oslo.privsep.daemon [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Spawned new privsep daemon via rootwrap 2023-02-26 08:49:55.717 2647 INFO oslo.privsep.daemon [-] privsep daemon starting 2023-02-26 08:49:55.722 2647 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2023-02-26 08:49:55.726 2647 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_SYS_ADMIN/CAP_SYS_ADMIN/none 2023-02-26 08:49:55.726 2647 INFO oslo.privsep.daemon [-] privsep daemon running as pid 2647 2023-02-26 08:49:55.956 7 WARNING os_brick.initiator.connectors.nvmeof [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Process execution error in _get_host_uuid: Unexpected error while running command. Command: blkid overlay -s UUID -o value Exit code: 2 Stdout: '' Stderr: '': oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2023-02-26 08:49:58.247 7 INFO nova.virt.libvirt.driver [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Creating image Is there a way to solve this issue? With regards, Swogat Pradhan

5 40

[all][ptg] Pre-PTG discussion: New Keystone Middleware Feature Supporting OAuth2.0 with External Authorization Service
by Hiromu Asahina 27 Mar '23

27 Mar '23

Hello Everyone, Recently, Tacker and Keystone have been working together on a new Keystone Middleware that can work with external authentication services, such as Keycloak. The code has already been submitted [1], but we want to make this middleware a generic plugin that works with as many OpenStack services as possible. To that end, we would like to hear from other projects with similar use cases (especially Ironic and Barbican, which run as standalone services). We will make a time slot to discuss this topic at the next vPTG. Please contact me if you are interested and available to participate. [1] https://review.opendev.org/c/openstack/keystonemiddleware/+/868734 -- Hiromu Asahina

4 11

[TripleO] Last maintained release of TripleO is Wallaby
by James Slagle 24 Mar '23

24 Mar '23

The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment. The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust. TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan. -- -- James Slagle --

6 21

[Openstack] Lack of Balance solution such as Watcher.
by Nguyễn Hữu Khôi 16 Mar '23

16 Mar '23

I am building a private cloud.Everything is ok. But I cannot find a way to balance vm when It have heavy load which cause impact other vm on the compute node. I found solutions such as Watcher and Leveller. But they need to be done manually. Watcher is not good because It need cpu metric such as cpu load in Ceilometer which is removed so we cannot use it. Leveller is good, but It is obsolete. Nguyen Huu Khoi

4 7

live resize
by Parsa Aminian 15 Mar '23

15 Mar '23

hello on openstack with ceph backend is it possible to live resize instances ? I want to change flavor without any down time .

5 6

[security][ironic] Ironic + the VMT
by Jay Faulkner 10 Mar '23

10 Mar '23

Hey all, A recent topic at Ironic meetings the last couple of weeks have been around vulnerability management. Ironic has not been using the OpenStack VMT traditionally; for reasons that AFAICT are lost to time. Is there any reason Ironic should not be vulnerability-managed? Is the security team willing to have us? The only potential complication is that Ironic may receive reports for vendor libraries used by Ironic but not maintained by Ironic -- I was hoping there might already be some historical precedent for how we handle those; it can't be that unique to Ironic. What do folks think? Thanks, Jay Faulkner Ironic PTL TC Member

2 2

[openstack-dev][PCI passthrough] How to use PCI passthrough feature correctly? And is this BUG in update_devices_from_hypervisor_resources?
by Simon Jones 10 Mar '23

10 Mar '23

Hi all, I'm working on openstack Yoga's PCI passthrough feature, follow this link: https://docs.openstack.org/nova/latest/admin/pci-passthrough.html I configure exactly as the link said, but when I create server use this command, I found ERROR: ``` openstack server create --flavor cirros-os-dpu-test-1 --image cirros \ --nic net-id=066c8dc2-c98b-4fb8-a541-8b367e8f6e69 \ --security-group default --key-name mykey provider-instance | fault | {'code': 500, 'created': '2023-02-23T06:13:43Z', 'message': 'No valid host was found. There are not enough hosts available.', 'details': 'Traceback (most recent call last):\n File "/usr/lib/python3/dist-packages/nova/conductor/manager.py", line 1548, in schedule_and_build_instances\n host_lists = self._schedule_instances(context, request_specs[0],\n File "/usr/lib/python3/dist-packages/nova/conductor/manager.py", line 908, in _schedule_instances\n host_lists = self.query_client.select_destinations(\n File "/usr/lib/python3/dist-packages/nova/scheduler/client/query.py", line 41, in select_destinations\n return self.scheduler_rpcapi.select_destinations(context, spec_obj,\n File "/usr/lib/python3/dist-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations\n return cctxt.call(ctxt, \'select_destinations\', **msg_args)\n File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/client.py", line 189, in call\n result = self.transport._send(\n File "/usr/lib/python3/dist-packages/oslo_messaging/transport.py", line 123, in _send\n return self._driver.send(target, ctxt, message,\n File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 689, in send\n return self._send(target, ctxt, message, wait_for_reply, timeout,\n File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 681, in _send\n raise result\nnova.exception_Remote.NoValidHost_Remote: No valid host was found. There are not enough hosts available.\nTraceback (most recent call last):\n\n File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 241, in inner\n return func(*args, **kwargs)\n\n File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 223, in select_destinations\n selections = self._select_destinations(\n\n File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 250, in _select_destinations\n selections = self._schedule(\n\n File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 416, in _schedule\n self._ensure_sufficient_hosts(\n\n File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 455, in _ensure_sufficient_hosts\n raise exception.NoValidHost(reason=reason)\n\nnova.exception.NoValidHost: No valid host was found. There are not enough hosts available.\n\n'} | // this is what I configured: gyw@c1:~$ openstack flavor show cirros-os-dpu-test-1 +----------------------------+------------------------------+ | Field | Value | +----------------------------+------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | access_project_ids | None | | description | None | | disk | 1 | | id | 0 | | name | cirros-os-dpu-test-1 | | os-flavor-access:is_public | True | | properties | pci_passthrough:alias='a1:1' | | ram | 64 | | rxtx_factor | 1.0 | | swap | | | vcpus | 1 | +----------------------------+------------------------------+ // in controller node /etc/nova/nova.conf [filter_scheduler] enabled_filters = PciPassthroughFilter available_filters = nova.scheduler.filters.all_filters [pci] passthrough_whitelist = {"vendor_id": "15b3", "product_id": "101e", "physical_network": null, "remote_managed": "true"} alias = { "vendor_id":"15b3", "product_id":"101e", "device_type":"type-VF", "name":"a1" } // in compute node /etc/nova/nova.conf [pci] passthrough_whitelist = {"vendor_id": "15b3", "product_id": "101e", "physical_network": null, "remote_managed": "true"} alias = { "vendor_id":"15b3", "product_id":"101e", "device_type":"type-VF", "name":"a1" } ``` The detail ERROR I found is: - The reason why "There are not enough hosts available" is, nova-scheduler's log shows "There are 0 hosts available but 1 instances requested to build", which means no hosts support PCI passthough feature. This is nova-schduler's log ``` 2023-02-28 06:11:58.329 1942637 DEBUG nova.scheduler.manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Starting to schedule for instances: ['8ddfbe2c-f929-4b62-8b73-67902df8fb60'] select_destinations /usr/lib/python3/dist-packages/nova/scheduler/manager.py:141 2023-02-28 06:11:58.330 1942637 DEBUG nova.scheduler.request_filter [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] compute_status_filter request filter added forbidden trait COMPUTE_STATUS_DISABLED compute_status_filter /usr/lib/python3/dist-packages/nova/scheduler/request_filter.py:254 2023-02-28 06:11:58.330 1942637 DEBUG nova.scheduler.request_filter [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Request filter 'compute_status_filter' took 0.0 seconds wrapper /usr/lib/python3/dist-packages/nova/scheduler/request_filter.py:46 2023-02-28 06:11:58.331 1942637 DEBUG nova.scheduler.request_filter [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Request filter 'accelerators_filter' took 0.0 seconds wrapper /usr/lib/python3/dist-packages/nova/scheduler/request_filter.py:46 2023-02-28 06:11:58.332 1942637 DEBUG nova.scheduler.request_filter [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Request filter 'remote_managed_ports_filter' took 0.0 seconds wrapper /usr/lib/python3/dist-packages/nova/scheduler/request_filter.py:46 2023-02-28 06:11:58.485 1942637 DEBUG oslo_concurrency.lockutils [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Lock "567eb2f1-7173-4eee-b9e7-66932ed70fea" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:386 2023-02-28 06:11:58.488 1942637 DEBUG oslo_concurrency.lockutils [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Lock "567eb2f1-7173-4eee-b9e7-66932ed70fea" "released" by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: held 0.003s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:400 2023-02-28 06:11:58.494 1942637 DEBUG oslo_db.sqlalchemy.engines [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] MySQL server mode set to STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION _check_effective_sql_mode /usr/lib/python3/dist-packages/oslo_db/sqlalchemy/engines.py:314 2023-02-28 06:11:58.520 1942637 INFO nova.scheduler.host_manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Host mapping not found for host c1c2. Not tracking instance info for this host. 2023-02-28 06:11:58.520 1942637 DEBUG oslo_concurrency.lockutils [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Lock "('c1c2', 'c1c2')" acquired by "nova.scheduler.host_manager.HostState.update.<locals>._locked_update" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:386 2023-02-28 06:11:58.521 1942637 DEBUG nova.scheduler.host_manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Update host state from compute node: ComputeNode(cpu_allocation_ratio=16.0,cpu_info='{"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["sse4.2", "mds-no", "stibp", "pdpe1gb", "xsaveopt", "ht", "intel-pt", "mtrr", "abm", "tm", "lm", "umip", "mca", "pku", "ds_cpl", "rdrand", "adx", "rdseed", "lahf_lm", "xgetbv1", "nx", "invpcid", "rdtscp", "tsc", "xsavec", "pcid", "arch-capabilities", "pclmuldq", "spec-ctrl", "fsgsbase", "avx2", "md-clear", "vmx", "syscall", "mmx", "ds", "ssse3", "avx", "dtes64", "fxsr", "msr", "acpi", "vpclmulqdq", "smap", "erms", "pge", "cmov", "sha-ni", "fsrm", "x2apic", "xsaves", "cx8", "pse", "pse36", "clflushopt", "vaes", "pni", "ssbd", "movdiri", "movbe", "clwb", "xtpr", "de", "invtsc", "fpu", "tsc-deadline", "pae", "clflush", "ibrs-all", "waitpkg", "sse", "sse2", "bmi1", "3dnowprefetch", "cx16", "popcnt", "rdctl-no", "fma", "tsc_adjust", "xsave", "ss", "skip-l1dfl-vmentry", "sse4.1", "rdpid", "monitor", "vme", "tm2", "pat", "pschange-mc-no", "movdir64b", "gfni", "mce", "smep", "sep", "apic", "arat", "f16c", "bmi2", "aes", "pbe", "est", "pdcm"]}',created_at=2023-02-14T03:19:40Z,current_workload=0,deleted=False,deleted_at=None,disk_allocation_ratio=1.0,disk_available_least=415,free_disk_gb=456,free_ram_mb=31378,host='c1c2',host_ip=192.168.28.21,hypervisor_hostname='c1c2',hypervisor_type='QEMU',hypervisor_version=4002001,id=8,local_gb=456,local_gb_used=0,mapped=0,memory_mb=31890,memory_mb_used=512,metrics='[]',numa_topology='{" nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{" nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163962, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["cpuset", "memory_usage", "cpu_usage", "id", "pinned_cpus", "pcpuset", "socket", "network_metadata", "siblings", "mempages", "memory"]}]}, "nova_object.changes": ["cells"]}',pci_device_pools=PciDevicePoolList,ram_allocation_ratio=1.5,running_vms=0,service_id=None,stats={failed_builds='0'},supported_hv_specs=[HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec],updated_at=2023-02-28T06:01:33Z,uuid=c360cc82-f0fd-4662-bccd-e1f02b27af51,vcpus=12,vcpus_used=0) _locked_update /usr/lib/python3/dist-packages/nova/scheduler/host_manager.py:167 2023-02-28 06:11:58.524 1942637 DEBUG nova.scheduler.host_manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Update host state with aggregates: [] _locked_update /usr/lib/python3/dist-packages/nova/scheduler/host_manager.py:170 2023-02-28 06:11:58.524 1942637 DEBUG nova.scheduler.host_manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Update host state with service dict: {'id': 17, 'uuid': '6d0921a6-427d-4a82-a7d2-41dfa003125a', 'host': 'c1c2', 'binary': 'nova-compute', 'topic': 'compute', 'report_count': 121959, 'disabled': False, 'disabled_reason': None, 'last_seen_up': datetime.datetime(2023, 2, 28, 6, 11, 49, tzinfo=datetime.timezone.utc), 'forced_down': False, 'version': 61, 'created_at': datetime.datetime(2023, 2, 14, 3, 19, 40, tzinfo=datetime.timezone.utc), 'updated_at': datetime.datetime(2023, 2, 28, 6, 11, 49, tzinfo=datetime.timezone.utc), 'deleted_at': None, 'deleted': False} _locked_update /usr/lib/python3/dist-packages/nova/scheduler/host_manager.py:173 2023-02-28 06:11:58.524 1942637 DEBUG nova.scheduler.host_manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Update host state with instances: [] _locked_update /usr/lib/python3/dist-packages/nova/scheduler/host_manager.py:176 2023-02-28 06:11:58.525 1942637 DEBUG oslo_concurrency.lockutils [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Lock "('c1c2', 'c1c2')" "released" by "nova.scheduler.host_manager.HostState.update.<locals>._locked_update" :: held 0.004s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:400 2023-02-28 06:11:58.525 1942637 DEBUG nova.filters [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Starting with 1 host(s) get_filtered_objects /usr/lib/python3/dist-packages/nova/filters.py:70 2023-02-28 06:11:58.526 1942637 DEBUG nova.pci.stats [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] ---- before ---- _filter_pools /usr/lib/python3/dist-packages/nova/pci/stats.py:542 2023-02-28 06:11:58.526 1942637 DEBUG nova.pci.stats [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] [] _filter_pools /usr/lib/python3/dist-packages/nova/pci/stats.py:543 2023-02-28 06:11:58.526 1942637 DEBUG nova.pci.stats [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] ---- after ---- _filter_pools /usr/lib/python3/dist-packages/nova/pci/stats.py:545 2023-02-28 06:11:58.527 1942637 DEBUG nova.pci.stats [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] [] _filter_pools /usr/lib/python3/dist-packages/nova/pci/stats.py:546 2023-02-28 06:11:58.527 1942637 DEBUG nova.pci.stats [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Not enough PCI devices left to satisfy request _filter_pools /usr/lib/python3/dist-packages/nova/pci/stats.py:556 2023-02-28 06:11:58.527 1942637 DEBUG nova.scheduler.filters.pci_passthrough_filter [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] (c1c2, c1c2) ram: 31378MB disk: 424960MB io_ops: 0 instances: 0 doesn't have the required PCI devices (InstancePCIRequests(instance_uuid=<?>,requests=[InstancePCIRequest])) host_passes /usr/lib/python3/dist-packages/nova/scheduler/filters/pci_passthrough_filter.py:52 2023-02-28 06:11:58.528 1942637 INFO nova.filters [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Filter PciPassthroughFilter returned 0 hosts 2023-02-28 06:11:58.528 1942637 DEBUG nova.filters [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Filtering removed all hosts for the request with instance ID '8ddfbe2c-f929-4b62-8b73-67902df8fb60'. Filter results: [('PciPassthroughFilter', None)] get_filtered_objects /usr/lib/python3/dist-packages/nova/filters.py:114 2023-02-28 06:11:58.528 1942637 INFO nova.filters [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Filtering removed all hosts for the request with instance ID '8ddfbe2c-f929-4b62-8b73-67902df8fb60'. Filter results: ['PciPassthroughFilter: (start: 1, end: 0)'] 2023-02-28 06:11:58.529 1942637 DEBUG nova.scheduler.manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] Filtered [] _get_sorted_hosts /usr/lib/python3/dist-packages/nova/scheduler/manager.py:610 2023-02-28 06:11:58.529 1942637 DEBUG nova.scheduler.manager [req-13b1baee-e02d-40fc-926d-d497e70ca0dc ff627ad39ed94479b9c5033bc462cf78 512866f9994f4ad8916d8539a7cdeec9 - default default] There are 0 hosts available but 1 instances requested to build. _ensure_sufficient_hosts /usr/lib/python3/dist-packages/nova/scheduler/manager.py:450 ``` Then I search database, I found PCI configure of compute node is not upload: ``` gyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 PCI_DEVICE No inventory of class PCI_DEVICE for c360cc82-f0fd-4662-bccd-e1f02b27af51 (HTTP 404) gyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 PCI_DEVICE No inventory of class PCI_DEVICE for c360cc82-f0fd-4662-bccd-e1f02b27af51 (HTTP 404) gyw@c1:~$ openstack resource class show PCI_DEVICE +-------+------------+ | Field | Value | +-------+------------+ | name | PCI_DEVICE | +-------+------------+ gyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 MEMORY_MB +------------------+-------+ | Field | Value | +------------------+-------+ | allocation_ratio | 1.5 | | min_unit | 1 | | max_unit | 31890 | | reserved | 512 | | step_size | 1 | | total | 31890 | | used | 0 | +------------------+-------+ 这个 31890 能跟上面compute node resource tracker上报的日志对上。 gyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 VCPU 、^Cgyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 VCPU +------------------+-------+ | Field | Value | +------------------+-------+ | allocation_ratio | 16.0 | | min_unit | 1 | | max_unit | 12 | | reserved | 0 | | step_size | 1 | | total | 12 | | used | 0 | +------------------+-------+ gyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 SRIOV_NET_VF No inventory of class SRIOV_NET_VF for c360cc82-f0fd-4662-bccd-e1f02b27af51 (HTTP 404) gyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 DISK_GB +------------------+-------+ | Field | Value | +------------------+-------+ | allocation_ratio | 1.0 | | min_unit | 1 | | max_unit | 456 | | reserved | 0 | | step_size | 1 | | total | 456 | | used | 0 | +------------------+-------+ gyw@c1:~$ openstack resource provider inventory show c360cc82-f0fd-4662-bccd-e1f02b27af51 IPV4_ADDRESS No inventory of class IPV4_ADDRESS for c360cc82-f0fd-4662-bccd-e1f02b27af51 (HTTP 404) MariaDB [nova]> select * from compute_nodes; +---------------------+---------------------+---------------------+----+------------+-------+-----------+----------+------------+----------------+---------------+-----------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------+-------------+--------------+------------------+-------------+---------------------+---------+---------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------+-----------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+----------------------+----------------------+--------------------------------------+-----------------------+--------+ | created_at | updated_at | deleted_at | id | service_id | vcpus | memory_mb | local_gb | vcpus_used | memory_mb_used | local_gb_used | hypervisor_type | hypervisor_version | cpu_info | disk_available_least | free_ram_mb | free_disk_gb | current_workload | running_vms | hypervisor_hostname | deleted | host_ip | supported_instances | pci_stats | metrics | extra_resources | stats | numa_topology | host | ram_allocation_ratio | cpu_allocation_ratio | uuid | disk_allocation_ratio | mapped | +---------------------+---------------------+---------------------+----+------------+-------+-----------+----------+------------+----------------+---------------+-----------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------+-------------+--------------+------------------+-------------+---------------------+---------+---------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------+-----------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+----------------------+----------------------+--------------------------------------+-----------------------+--------+ | 2023-01-04 01:55:44 | 2023-01-04 03:02:28 | 2023-02-13 08:34:08 | 1 | NULL | 4 | 3931 | 60 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 4, "cores": 1, "threads": 1}, "features": ["pat", "cmov", "ibrs-all", "pge", "sse4.2", "sse", "mmx", "ibrs", "avx2", "syscall", "fpu", "mtrr", "xsaves", "mce", "invpcid", "tsc_adjust", "ssbd", "pku", "ibpb", "xsave", "xsaveopt", "pae", "lm", "pdcm", "bmi1", "avx512vnni", "stibp", "x2apic", "avx512dq", "pcid", "nx", "bmi2", "erms", "3dnowprefetch", "de", "avx512bw", "arch-capabilities", "pni", "fma", "rdctl-no", "sse4.1", "rdseed", "arat", "avx512vl", "avx512f", "pclmuldq", "msr", "fxsr", "sse2", "amd-stibp", "hypervisor", "tsx-ctrl", "clflushopt", "cx16", "clwb", "xgetbv1", "xsavec", "adx", "rdtscp", "mds-no", "cx8", "aes", "tsc-deadline", "pse36", "fsgsbase", "umip", "spec-ctrl", "lahf_lm", "md-clear", "avx512cd", "amd-ssbd", "vmx", "apic", "f16c", "pse", "tsc", "movbe", "smep", "ss", "pschange-mc-no", "ssse3", "popcnt", "avx", "vme", "smap", "pdpe1gb", "mca", "skip-l1dfl-vmentry", "abm", "sep", "clflush", "rdrand"]} | 49 | 3419 | 60 | 0 | 0 | gyw | 1 | 192.168.2.99 | [["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"]] | {"nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3], "pcpuset": [0, 1, 2, 3], "memory": 3931, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0], [1], [2], [3]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 1006396, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "reserved", "size_kb", "total"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "reserved", "size_kb", "total"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "reserved", "size_kb", "total"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": null}, "nova_object.changes": ["cpuset", "pinned_cpus", "mempages", "network_metadata", "cpu_usage", "pcpuset", "memory", "id", "socket", "siblings", "memory_usage"]}]}, "nova_object.changes": ["cells"]} | gyw | 1.5 | 16 | b1bf35bd-a9ad-4f0c-9033-776a5c6d1c9b | 1 | 1 | | 2023-01-04 03:12:17 | 2023-01-31 06:36:36 | 2023-02-23 08:50:29 | 2 | NULL | 4 | 3931 | 60 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 4, "cores": 1, "threads": 1}, "features": ["pclmuldq", "fsgsbase", "f16c", "fxsr", "ibpb", "adx", "movbe", "aes", "x2apic", "abm", "mtrr", "arat", "sse4.2", "bmi1", "stibp", "sse4.1", "pae", "vme", "msr", "skip-l1dfl-vmentry", "fma", "pcid", "avx2", "de", "ibrs-all", "ssse3", "apic", "umip", "xsavec", "3dnowprefetch", "amd-ssbd", "sse", "nx", "fpu", "pse", "smap", "smep", "lahf_lm", "pni", "spec-ctrl", "xsave", "xsaves", "rdtscp", "vmx", "avx512f", "cmov", "invpcid", "hypervisor", "erms", "rdctl-no", "cx16", "cx8", "tsc", "pge", "pdcm", "rdrand", "avx", "amd-stibp", "avx512vl", "xsaveopt", "mds-no", "popcnt", "clflushopt", "sse2", "xgetbv1", "rdseed", "pdpe1gb", "pschange-mc-no", "clwb", "avx512vnni", "mca", "tsx-ctrl", "tsc_adjust", "syscall", "pse36", "mmx", "avx512cd", "avx512bw", "pku", "tsc-deadline", "arch-capabilities", "avx512dq", "ssbd", "clflush", "mce", "ss", "pat", "bmi2", "lm", "ibrs", "sep", "md-clear"]} | 49 | 3419 | 60 | 0 | 0 | c1c1 | 2 | 192.168.2.99 | [["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"]] | {"nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3], "pcpuset": [0, 1, 2, 3], "memory": 3931, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0], [1], [2], [3]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 1006393, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "total", "size_kb", "reserved"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "total", "size_kb", "reserved"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "total", "size_kb", "reserved"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["tunneled", "physnets"]}, "socket": null}, "nova_object.changes": ["memory_usage", "socket", "cpuset", "siblings", "id", "mempages", "pinned_cpus", "memory", "pcpuset", "network_metadata", "cpu_usage"]}]}, "nova_object.changes": ["cells"]} | c1c1 | 1.5 | 16 | 1eac1c8d-d96a-4eeb-9868-5a341a80c6df | 1 | 0 | | 2023-02-07 08:25:27 | 2023-02-07 08:25:27 | 2023-02-13 08:34:22 | 3 | NULL | 12 | 31890 | 456 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["sha-ni", "intel-pt", "pat", "monitor", "movbe", "nx", "msr", "avx2", "md-clear", "popcnt", "rdseed", "pse36", "mds-no", "ds", "sse", "fsrm", "rdctl-no", "pse", "dtes64", "ds_cpl", "xgetbv1", "lahf_lm", "smep", "waitpkg", "smap", "fsgsbase", "sep", "tsc_adjust", "cmov", "ibrs-all", "mtrr", "cx16", "f16c", "arch-capabilities", "pclmuldq", "clflush", "erms", "umip", "xsaves", "xsavec", "ssse3", "acpi", "tsc", "movdir64b", "vpclmulqdq", "skip-l1dfl-vmentry", "xsave", "arat", "mmx", "rdpid", "sse2", "ssbd", "pdpe1gb", "spec-ctrl", "adx", "pcid", "de", "pku", "est", "pae", "tsc-deadline", "pdcm", "clwb", "vme", "rdtscp", "fxsr", "3dnowprefetch", "invpcid", "x2apic", "tm", "lm", "fma", "bmi1", "sse4.1", "abm", "xsaveopt", "pschange-mc-no", "syscall", "clflushopt", "pbe", "avx", "cx8", "vmx", "gfni", "fpu", "mce", "tm2", "movdiri", "invtsc", "apic", "bmi2", "mca", "pge", "rdrand", "xtpr", "sse4.2", "stibp", "ht", "ss", "pni", "vaes", "aes"]} | 416 | 31378 | 456 | 0 | 0 | c-MS-7D42 | 3 | 192.168.2.99 | [["alpha", "qemu", "hvm"], ["armv7l", "qemu", "hvm"], ["aarch64", "qemu", "hvm"], ["cris", "qemu", "hvm"], ["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["lm32", "qemu", "hvm"], ["m68k", "qemu", "hvm"], ["microblaze", "qemu", "hvm"], ["microblazeel", "qemu", "hvm"], ["mips", "qemu", "hvm"], ["mipsel", "qemu", "hvm"], ["mips64", "qemu", "hvm"], ["mips64el", "qemu", "hvm"], ["ppc", "qemu", "hvm"], ["ppc64", "qemu", "hvm"], ["ppc64le", "qemu", "hvm"], ["s390x", "qemu", "hvm"], ["sh4", "qemu", "hvm"], ["sh4eb", "qemu", "hvm"], ["sparc", "qemu", "hvm"], ["sparc64", "qemu", "hvm"], ["unicore32", "qemu", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"], ["xtensa", "qemu", "hvm"], ["xtensaeb", "qemu", "hvm"]] | {" nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163866, "used": 0, "reserved": 0}, "nova_object.changes": ["total", "reserved", "used", "size_kb"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["total", "reserved", "used", "size_kb"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["total", "reserved", "used", "size_kb"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["network_metadata", "cpuset", "mempages", "id", "socket", "cpu_usage", "memory", "pinned_cpus", "pcpuset", "siblings", "memory_usage"]}]}, "nova_object.changes": ["cells"]} | c-MS-7D42 | 1.5 | 16 | f115a1c2-fda3-42c6-945a-8b54fef40daf | 1 | 0 | | 2023-02-07 09:53:12 | 2023-02-13 08:38:04 | 2023-02-13 08:39:33 | 4 | NULL | 12 | 31890 | 456 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["rdctl-no", "acpi", "umip", "invpcid", "bmi1", "clflushopt", "pclmuldq", "movdir64b", "ssbd", "apic", "rdpid", "ht", "fsrm", "pni", "pse", "xsaves", "cx16", "nx", "f16c", "arat", "popcnt", "mtrr", "vpclmulqdq", "intel-pt", "spec-ctrl", "syscall", "3dnowprefetch", "ds", "mce", "bmi2", "tm2", "md-clear", "fpu", "monitor", "pae", "erms", "dtes64", "tsc", "fsgsbase", "xgetbv1", "est", "mds-no", "tm", "x2apic", "xsavec", "cx8", "stibp", "clflush", "ssse3", "pge", "movdiri", "pdpe1gb", "vaes", "gfni", "mmx", "clwb", "waitpkg", "xsaveopt", "pse36", "aes", "pschange-mc-no", "sse2", "abm", "ss", "pcid", "sep", "rdseed", "mca", "skip-l1dfl-vmentry", "pat", "smap", "sse", "lahf_lm", "avx", "cmov", "sse4.1", "sse4.2", "ibrs-all", "smep", "vme", "tsc_adjust", "arch-capabilities", "fma", "movbe", "adx", "avx2", "xtpr", "pku", "pbe", "rdrand", "tsc-deadline", "pdcm", "ds_cpl", "de", "invtsc", "xsave", "msr", "fxsr", "lm", "vmx", "sha-ni", "rdtscp"]} | 416 | 31378 | 456 | 0 | 0 | c-MS-7D42 | 4 | 192.168.28.21 | [["alpha", "qemu", "hvm"], ["armv7l", "qemu", "hvm"], ["aarch64", "qemu", "hvm"], ["cris", "qemu", "hvm"], ["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["lm32", "qemu", "hvm"], ["m68k", "qemu", "hvm"], ["microblaze", "qemu", "hvm"], ["microblazeel", "qemu", "hvm"], ["mips", "qemu", "hvm"], ["mipsel", "qemu", "hvm"], ["mips64", "qemu", "hvm"], ["mips64el", "qemu", "hvm"], ["ppc", "qemu", "hvm"], ["ppc64", "qemu", "hvm"], ["ppc64le", "qemu", "hvm"], ["s390x", "qemu", "hvm"], ["sh4", "qemu", "hvm"], ["sh4eb", "qemu", "hvm"], ["sparc", "qemu", "hvm"], ["sparc64", "qemu", "hvm"], ["unicore32", "qemu", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"], ["xtensa", "qemu", "hvm"], ["xtensaeb", "qemu", "hvm"]] | {" nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163866, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "total", "used", "reserved"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "total", "used", "reserved"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "total", "used", "reserved"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["siblings", "cpuset", "mempages", "socket", "pcpuset", "memory", "memory_usage", "id", "network_metadata", "cpu_usage", "pinned_cpus"]}]}, "nova_object.changes": ["cells"]} | c1c2 | 1.5 | 16 | 10ea8254-ad84-4db9-9acd-5c783cb8600e | 1 | 0 | | 2023-02-13 08:41:21 | 2023-02-13 08:41:22 | 2023-02-13 09:56:50 | 5 | NULL | 12 | 31890 | 456 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["bmi2", "ht", "pae", "pku", "monitor", "avx2", "sha-ni", "acpi", "ssbd", "syscall", "mca", "mmx", "mds-no", "erms", "fsrm", "arat", "xsaves", "movbe", "movdir64b", "fpu", "clflush", "nx", "mce", "pse", "cx8", "aes", "avx", "xsavec", "invpcid", "est", "xgetbv1", "fxsr", "rdrand", "vaes", "cmov", "intel-pt", "smep", "dtes64", "f16c", "adx", "sse2", "stibp", "rdseed", "xsave", "skip-l1dfl-vmentry", "sse4.1", "rdpid", "ds", "umip", "pni", "rdctl-no", "clwb", "md-clear", "pschange-mc-no", "msr", "popcnt", "sse4.2", "pge", "tm2", "pat", "xtpr", "fma", "gfni", "sep", "ibrs-all", "tsc", "ds_cpl", "tm", "clflushopt", "pcid", "de", "rdtscp", "vme", "cx16", "lahf_lm", "ss", "pdcm", "x2apic", "pbe", "movdiri", "tsc-deadline", "invtsc", "apic", "fsgsbase", "mtrr", "vpclmulqdq", "ssse3", "3dnowprefetch", "abm", "xsaveopt", "tsc_adjust", "pse36", "pclmuldq", "bmi1", "smap", "arch-capabilities", "lm", "vmx", "sse", "pdpe1gb", "spec-ctrl", "waitpkg"]} | 416 | 31378 | 456 | 0 | 0 | c-MS-7D42 | 5 | 192.168.28.21 | [["alpha", "qemu", "hvm"], ["armv7l", "qemu", "hvm"], ["aarch64", "qemu", "hvm"], ["cris", "qemu", "hvm"], ["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["lm32", "qemu", "hvm"], ["m68k", "qemu", "hvm"], ["microblaze", "qemu", "hvm"], ["microblazeel", "qemu", "hvm"], ["mips", "qemu", "hvm"], ["mipsel", "qemu", "hvm"], ["mips64", "qemu", "hvm"], ["mips64el", "qemu", "hvm"], ["ppc", "qemu", "hvm"], ["ppc64", "qemu", "hvm"], ["ppc64le", "qemu", "hvm"], ["s390x", "qemu", "hvm"], ["sh4", "qemu", "hvm"], ["sh4eb", "qemu", "hvm"], ["sparc", "qemu", "hvm"], ["sparc64", "qemu", "hvm"], ["unicore32", "qemu", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"], ["xtensa", "qemu", "hvm"], ["xtensaeb", "qemu", "hvm"]] | {"nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163866, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "size_kb", "total", "reserved"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "size_kb", "total", "reserved"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["used", "size_kb", "total", "reserved"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["tunneled", "physnets"]}, "socket": 0}, "nova_object.changes": ["pinned_cpus", "cpuset", "memory_usage", "id", "cpu_usage", "network_metadata", "siblings", "mempages", "socket", "memory", "pcpuset"]}]}, "nova_object.changes": ["cells"]} | c1c2 | 1.5 | 16 | 8efa100f-ab14-45fd-8c39-644b49772883 | 1 | 0 | | 2023-02-13 09:57:30 | 2023-02-13 09:57:31 | 2023-02-13 13:52:57 | 6 | NULL | 12 | 31890 | 456 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["rdpid", "intel-pt", "fxsr", "pclmuldq", "xsaveopt", "pae", "xsave", "movdiri", "syscall", "ibrs-all", "mmx", "tsc_adjust", "abm", "ssbd", "sse", "mce", "clwb", "vmx", "dtes64", "ssse3", "fsrm", "est", "bmi1", "mtrr", "avx2", "pse36", "pat", "gfni", "mds-no", "clflushopt", "cmov", "fma", "sep", "mca", "ss", "umip", "popcnt", "skip-l1dfl-vmentry", "ht", "sha-ni", "pdcm", "pdpe1gb", "rdrand", "pge", "lahf_lm", "aes", "xsavec", "pni", "smep", "md-clear", "waitpkg", "tm", "xgetbv1", "stibp", "apic", "vaes", "fpu", "ds_cpl", "ds", "sse4.2", "3dnowprefetch", "smap", "x2apic", "vpclmulqdq", "acpi", "avx", "de", "pbe", "sse2", "xsaves", "monitor", "clflush", "tm2", "pschange-mc-no", "bmi2", "movbe", "pku", "pcid", "xtpr", "erms", "movdir64b", "cx8", "nx", "rdctl-no", "invpcid", "spec-ctrl", "tsc", "adx", "invtsc", "f16c", "rdtscp", "vme", "pse", "lm", "cx16", "fsgsbase", "rdseed", "msr", "sse4.1", "arch-capabilities", "arat", "tsc-deadline"]} | 416 | 31378 | 456 | 0 | 0 | c-MS-7D42 | 6 | 192.168.28.21 | [["alpha", "qemu", "hvm"], ["armv7l", "qemu", "hvm"], ["aarch64", "qemu", "hvm"], ["cris", "qemu", "hvm"], ["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["lm32", "qemu", "hvm"], ["m68k", "qemu", "hvm"], ["microblaze", "qemu", "hvm"], ["microblazeel", "qemu", "hvm"], ["mips", "qemu", "hvm"], ["mipsel", "qemu", "hvm"], ["mips64", "qemu", "hvm"], ["mips64el", "qemu", "hvm"], ["ppc", "qemu", "hvm"], ["ppc64", "qemu", "hvm"], ["ppc64le", "qemu", "hvm"], ["s390x", "qemu", "hvm"], ["sh4", "qemu", "hvm"], ["sh4eb", "qemu", "hvm"], ["sparc", "qemu", "hvm"], ["sparc64", "qemu", "hvm"], ["unicore32", "qemu", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"], ["xtensa", "qemu", "hvm"], ["xtensaeb", "qemu", "hvm"]] | {" nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163866, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "total", "reserved"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "total", "reserved"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "total", "reserved"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["memory_usage", "id", "mempages", "pinned_cpus", "network_metadata", "pcpuset", "cpuset", "siblings", "socket", "cpu_usage", "memory"]}]}, "nova_object.changes": ["cells"]} | c1c2 | 1.5 | 16 | 8f5b58c5-d5d7-452c-9ec7-cff24baf6c94 | 1 | 0 | | 2023-02-14 01:35:43 | 2023-02-14 01:35:43 | 2023-02-14 03:16:51 | 7 | NULL | 12 | 31890 | 456 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["pcid", "pse36", "movdir64b", "apic", "nx", "vpclmulqdq", "mtrr", "popcnt", "pdcm", "fsgsbase", "lahf_lm", "sse2", "pae", "aes", "movdiri", "xsaves", "erms", "invtsc", "waitpkg", "pbe", "ht", "pni", "avx2", "rdpid", "fxsr", "tm2", "pku", "x2apic", "fma", "pge", "rdseed", "pdpe1gb", "mmx", "sse4.1", "sha-ni", "xtpr", "tsc_adjust", "cx16", "xsave", "cx8", "mce", "md-clear", "gfni", "clwb", "msr", "abm", "f16c", "ss", "xsaveopt", "ds_cpl", "pse", "syscall", "cmov", "3dnowprefetch", "ssse3", "pclmuldq", "arch-capabilities", "ibrs-all", "arat", "ds", "pat", "invpcid", "vaes", "xsavec", "mds-no", "tm", "smep", "acpi", "fsrm", "movbe", "fpu", "sse4.2", "umip", "rdtscp", "tsc-deadline", "skip-l1dfl-vmentry", "est", "rdctl-no", "clflush", "spec-ctrl", "tsc", "lm", "avx", "vmx", "clflushopt", "rdrand", "dtes64", "smap", "ssbd", "sse", "xgetbv1", "stibp", "mca", "adx", "vme", "bmi1", "pschange-mc-no", "intel-pt", "de", "monitor", "bmi2", "sep"]} | 416 | 31378 | 456 | 0 | 0 | c-MS-7D42 | 7 | 192.168.28.21 | [["alpha", "qemu", "hvm"], ["armv7l", "qemu", "hvm"], ["aarch64", "qemu", "hvm"], ["cris", "qemu", "hvm"], ["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["lm32", "qemu", "hvm"], ["m68k", "qemu", "hvm"], ["microblaze", "qemu", "hvm"], ["microblazeel", "qemu", "hvm"], ["mips", "qemu", "hvm"], ["mipsel", "qemu", "hvm"], ["mips64", "qemu", "hvm"], ["mips64el", "qemu", "hvm"], ["ppc", "qemu", "hvm"], ["ppc64", "qemu", "hvm"], ["ppc64le", "qemu", "hvm"], ["s390x", "qemu", "hvm"], ["sh4", "qemu", "hvm"], ["sh4eb", "qemu", "hvm"], ["sparc", "qemu", "hvm"], ["sparc64", "qemu", "hvm"], ["unicore32", "qemu", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"], ["xtensa", "qemu", "hvm"], ["xtensaeb", "qemu", "hvm"]] | {"nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163866, "used": 0, "reserved": 0}, "nova_object.changes": ["reserved", "total", "used", "size_kb"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["reserved", "total", "used", "size_kb"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["reserved", "total", "used", "size_kb"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["tunneled", "physnets"]}, "socket": 0}, "nova_object.changes": ["pcpuset", "mempages", "socket", "cpu_usage", "memory_usage", "siblings", "memory", "pinned_cpus", "network_metadata", "cpuset", "id"]}]}, "nova_object.changes": ["cells"]} | c1c2 | 1.5 | 16 | 9f81894d-028d-4bb0-ada0-116159b13ed8 | 1 | 0 | | 2023-02-14 03:19:40 | 2023-02-28 07:30:14 | NULL | 8 | NULL | 12 | 31890 | 456 | 0 | 512 | 0 | QEMU | 4002001 | {"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["ds_cpl", "vpclmulqdq", "pbe", "lahf_lm", "clflush", "xsaveopt", "bmi2", "clwb", "skip-l1dfl-vmentry", "de", "cmov", "pku", "acpi", "xsavec", "3dnowprefetch", "mmx", "mtrr", "vmx", "movbe", "ssse3", "adx", "syscall", "spec-ctrl", "abm", "umip", "fxsr", "pge", "vme", "xsave", "rdctl-no", "rdrand", "sse", "cx8", "gfni", "dtes64", "invpcid", "md-clear", "fsrm", "fma", "arat", "rdtscp", "tsc", "sse4.1", "xsaves", "est", "tm", "ibrs-all", "stibp", "fsgsbase", "cx16", "arch-capabilities", "ssbd", "pse", "avx", "pse36", "pdpe1gb", "tm2", "nx", "pdcm", "sse4.2", "erms", "sep", "aes", "mca", "invtsc", "bmi1", "rdseed", "ss", "ht", "x2apic", "movdir64b", "rdpid", "lm", "tsc-deadline", "msr", "mce", "smep", "avx2", "sse2", "pschange-mc-no", "intel-pt", "tsc_adjust", "ds", "monitor", "popcnt", "f16c", "pae", "movdiri", "xgetbv1", "pcid", "pni", "pclmuldq", "xtpr", "apic", "mds-no", "sha-ni", "smap", "vaes", "waitpkg", "pat", "fpu", "clflushopt"]} | 415 | 31378 | 456 | 0 | 0 | c1c2 | 0 | 192.168.28.21 | [["alpha", "qemu", "hvm"], ["armv7l", "qemu", "hvm"], ["aarch64", "qemu", "hvm"], ["cris", "qemu", "hvm"], ["i686", "qemu", "hvm"], ["i686", "kvm", "hvm"], ["lm32", "qemu", "hvm"], ["m68k", "qemu", "hvm"], ["microblaze", "qemu", "hvm"], ["microblazeel", "qemu", "hvm"], ["mips", "qemu", "hvm"], ["mipsel", "qemu", "hvm"], ["mips64", "qemu", "hvm"], ["mips64el", "qemu", "hvm"], ["ppc", "qemu", "hvm"], ["ppc64", "qemu", "hvm"], ["ppc64le", "qemu", "hvm"], ["s390x", "qemu", "hvm"], ["sh4", "qemu", "hvm"], ["sh4eb", "qemu", "hvm"], ["sparc", "qemu", "hvm"], ["sparc64", "qemu", "hvm"], ["unicore32", "qemu", "hvm"], ["x86_64", "qemu", "hvm"], ["x86_64", "kvm", "hvm"], ["xtensa", "qemu", "hvm"], ["xtensaeb", "qemu", "hvm"]] | {"nova_object.name": "PciDevicePoolList", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"objects": []}, "nova_object.changes": ["objects"]} | [] | NULL | {"failed_builds": "0"} | {"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163962, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "reserved", "total", "used"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "reserved", "total", "used"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "reserved", "total", "used"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["tunneled", "physnets"]}, "socket": 0}, "nova_object.changes": ["cpu_usage", "siblings", "id", "pcpuset", "cpuset", "network_metadata", "memory", "pinned_cpus", "memory_usage", "socket", "mempages"]}]}, "nova_object.changes": ["cells"]} | c1c2 | 1.5 | 16 | c360cc82-f0fd-4662-bccd-e1f02b27af51 | 1 | 0 | +---------------------+---------------------+---------------------+----+------------+-------+-----------+----------+------------+----------------+---------------+-----------------+--------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------+-------------+--------------+------------------+-------------+---------------------+---------+---------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------+-----------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+----------------------+----------------------+--------------------------------------+-----------------------+--------+ 8 rows in set (0.001 sec) ``` Then I search code, I found these infomation is upload in compute node's nova-compute, in the init process in nova/compute/resource_tracker.py:_init_compute_node Then I add some debug log, I found in _init_compute_node, there are PCI configure which read from /etc/nova/nova.conf, but in _setup_pci_tracker pop these infomation, this is code: ``` def _setup_pci_tracker(self, context, compute_node, resources): if not self.pci_tracker: LOG.debug("_setup_pci_tracker 11111") LOG.debug(resources) # 2023-02-28 14:01:33.782 443293 DEBUG nova.compute.resource_tracker [req-52743217-f0b6-4525-b9fd-371246b6c929 - - - - -] _setup_pci_tracker 11111 _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:772 # 2023-02-28 14:01:33.782 443293 DEBUG nova.compute.resource_tracker [req-52743217-f0b6-4525-b9fd-371246b6c929 - - - - -] {'supported_instances': [('alpha', 'qemu', 'hvm'), ('armv7l', 'qemu', 'hvm'), ('aarch64', 'qemu', 'hvm'), ('cris', 'qemu', 'hvm'), ('i686', 'qemu', 'hvm'), ('i686', 'kvm', 'hvm'), ('lm32', 'qemu', 'hvm'), ('m68k', 'qemu', 'hvm'), ('microblaze', 'qemu', 'hvm'), ('microblazeel', 'qemu', 'hvm'), ('mips', 'qemu', 'hvm'), ('mipsel', 'qemu', 'hvm'), ('mips64', 'qemu', 'hvm'), ('mips64el', 'qemu', 'hvm'), ('ppc', 'qemu', 'hvm'), ('ppc64', 'qemu', 'hvm'), ('ppc64le', 'qemu', 'hvm'), ('s390x', 'qemu', 'hvm'), ('sh4', 'qemu', 'hvm'), ('sh4eb', 'qemu', 'hvm'), ('sparc', 'qemu', 'hvm'), ('sparc64', 'qemu', 'hvm'), ('unicore32', 'qemu', 'hvm'), ('x86_64', 'qemu', 'hvm'), ('x86_64', 'kvm', 'hvm'), ('xtensa', 'qemu', 'hvm'), ('xtensaeb', 'qemu', 'hvm')], 'vcpus': 12, 'memory_mb': 31890, 'local_gb': 456.8854446411133, 'vcpus_used': 0, 'memory_mb_used': 3856, 'local_gb_used': 18.015335083007812, 'hypervisor_type': 'QEMU', 'hypervisor_version': 4002001, 'hypervisor_hostname': 'c1c2', 'cpu_info': '{"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["sse4.2", "mds-no", "stibp", "pdpe1gb", "xsaveopt", "ht", "intel-pt", "mtrr", "abm", "tm", "lm", "umip", "mca", "pku", "ds_cpl", "rdrand", "adx", "rdseed", "lahf_lm", "xgetbv1", "nx", "invpcid", "rdtscp", "tsc", "xsavec", "pcid", "arch-capabilities", "pclmuldq", "spec-ctrl", "fsgsbase", "avx2", "md-clear", "vmx", "syscall", "mmx", "ds", "ssse3", "avx", "dtes64", "fxsr", "msr", "acpi", "vpclmulqdq", "smap", "erms", "pge", "cmov", "sha-ni", "fsrm", "x2apic", "xsaves", "cx8", "pse", "pse36", "clflushopt", "vaes", "pni", "ssbd", "movdiri", "movbe", "clwb", "xtpr", "de", "invtsc", "fpu", "tsc-deadline", "pae", "clflush", "ibrs-all", "waitpkg", "sse", "sse2", "bmi1", "3dnowprefetch", "cx16", "popcnt", "rdctl-no", "fma", "tsc_adjust", "xsave", "ss", "skip-l1dfl-vmentry", "sse4.1", "rdpid", "monitor", "vme", "tm2", "pat", "pschange-mc-no", "movdir64b", "gfni", "mce", "smep", "sep", "apic", "arat", "f16c", "bmi2", "aes", "pbe", "est", "pdcm"]}', 'disk_available_least': 415.5914993286133, 'pci_passthrough_devices': '[{"dev_id": "pci_0000_02_00_0", "address": "0000:02:00.0", "product_id": "a809", "vendor_id": "144d", "numa_node": 0, "label": "label_144d_a809", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_01_00_5", "address": "0000:01:00.5", "product_id": "101e", "vendor_id": "15b3", "numa_node": null, "label": "label_15b3_101e", "dev_type": "type-VF", "parent_addr": "0000:01:00.0", "parent_ifname": "enp1s0f0np0", "capabilities": {"network": ["rx", "tx", "sg", "tso", "gso", "gro", "rxvlan", "txvlan", "rxhash", "rdma", "txudptnl"]}}, {"dev_id": "pci_0000_00_1c_0", "address": "0000:00:1c.0", "product_id": "7ab8", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7ab8", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_08_0", "address": "0000:00:08.0", "product_id": "464f", "vendor_id": "8086", "numa_node": null, "label": "label_8086_464f", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_1f_4", "address": "0000:00:1f.4", "product_id": "7aa3", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7aa3", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_01_00_3", "address": "0000:01:00.3", "product_id": "101e", "vendor_id": "15b3", "numa_node": null, "label": "label_15b3_101e", "dev_type": "type-VF", "parent_addr": "0000:01:00.0", "parent_ifname": "enp1s0f0np0", "capabilities": {"network": ["rx", "tx", "sg", "tso", "gso", "gro", "rxvlan", "txvlan", "rxhash", "rdma", "txudptnl"]}}, {"dev_id": "pci_0000_00_06_0", "address": "0000:00:06.0", "product_id": "464d", "vendor_id": "8086", "numa_node": null, "label": "label_8086_464d", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_17_0", "address": "0000:00:17.0", "product_id": "7ae2", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7ae2", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_1f_5", "address": "0000:00:1f.5", "product_id": "7aa4", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7aa4", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_01_00_6", "address": "0000:01:00.6", "product_id": "101e", "vendor_id": "15b3", "numa_node": null, "label": "label_15b3_101e", "dev_type": "type-VF", "parent_addr": "0000:01:00.0", "parent_ifname": "enp1s0f0np0", "capabilities": {"network": ["rx", "tx", "sg", "tso", "gso", "gro", "rxvlan", "txvlan", "rxhash", "rdma", "txudptnl"]}}, {"dev_id": "pci_0000_00_1f_0", "address": "0000:00:1f.0", "product_id": "7a86", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7a86", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_02_0", "address": "0000:00:02.0", "product_id": "4692", "vendor_id": "8086", "numa_node": null, "label": "label_8086_4692", "dev_type": "type-PF"}, {"dev_id": "pci_0000_00_16_0", "address": "0000:00:16.0", "product_id": "7ae8", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7ae8", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_1c_1", "address": "0000:00:1c.1", "product_id": "7ab9", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7ab9", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_1c_3", "address": "0000:00:1c.3", "product_id": "7abb", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7abb", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_04_00_0", "address": "0000:04:00.0", "product_id": "8125", "vendor_id": "10ec", "numa_node": null, "label": "label_10ec_8125", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_00_0", "address": "0000:00:00.0", "product_id": "4650", "vendor_id": "8086", "numa_node": null, "label": "label_8086_4650", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_01_0", "address": "0000:00:01.0", "product_id": "460d", "vendor_id": "8086", "numa_node": null, "label": "label_8086_460d", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_01_00_0", "address": "0000:01:00.0", "product_id": "a2d6", "vendor_id": "15b3", "numa_node": null, "label": "label_15b3_a2d6", "dev_type": "type-PF", "mac_address": "08:c0:eb:8e:bd:f4"}, {"dev_id": "pci_0000_01_00_2", "address": "0000:01:00.2", "product_id": "c2d3", "vendor_id": "15b3", "numa_node": null, "label": "label_15b3_c2d3", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_14_2", "address": "0000:00:14.2", "product_id": "7aa7", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7aa7", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_14_3", "address": "0000:00:14.3", "product_id": "7af0", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7af0", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_00_1f_3", "address": "0000:00:1f.3", "product_id": "7ad0", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7ad0", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_01_00_4", "address": "0000:01:00.4", "product_id": "101e", "vendor_id": "15b3", "numa_node": null, "label": "label_15b3_101e", "dev_type": "type-VF", "parent_addr": "0000:01:00.0", "parent_ifname": "enp1s0f0np0", "capabilities": {"network": ["rx", "tx", "sg", "tso", "gso", "gro", "rxvlan", "txvlan", "rxhash", "rdma", "txudptnl"]}}, {"dev_id": "pci_0000_05_00_0", "address": "0000:05:00.0", "product_id": "0612", "vendor_id": "1b21", "numa_node": null, "label": "label_1b21_0612", "dev_type": "type-PCI"}, {"dev_id": "pci_0000_01_00_1", "address": "0000:01:00.1", "product_id": "a2d6", "vendor_id": "15b3", "numa_node": null, "label": "label_15b3_a2d6", "dev_type": "type-PF", "mac_address": "08:c0:eb:8e:bd:f5"}, {"dev_id": "pci_0000_00_14_0", "address": "0000:00:14.0", "product_id": "7ae0", "vendor_id": "8086", "numa_node": null, "label": "label_8086_7ae0", "dev_type": "type-PCI"}]', 'numa_topology': '{"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163962, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["cpuset", "memory_usage", "cpu_usage", "id", "pinned_cpus", "pcpuset", "socket", "network_metadata", "siblings", "mempages", "memory"]}]}, "nova_object.changes": ["cells"]}', 'host_ip': '192.168.28.21'} _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:773 self.pci_tracker = pci_manager.PciDevTracker(context, compute_node) if 'pci_passthrough_devices' in resources: dev_json = resources.pop('pci_passthrough_devices') self.pci_tracker.update_devices_from_hypervisor_resources( dev_json) LOG.debug("_setup_pci_tracker 22222") LOG.debug(resources) # 2023-02-28 14:01:33.798 443293 DEBUG nova.compute.resource_tracker [req-52743217-f0b6-4525-b9fd-371246b6c929 - - - - -] _setup_pci_tracker 22222 _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:781 # 2023-02-28 14:01:33.799 443293 DEBUG nova.compute.resource_tracker [req-52743217-f0b6-4525-b9fd-371246b6c929 - - - - -] {'supported_instances': [('alpha', 'qemu', 'hvm'), ('armv7l', 'qemu', 'hvm'), ('aarch64', 'qemu', 'hvm'), ('cris', 'qemu', 'hvm'), ('i686', 'qemu', 'hvm'), ('i686', 'kvm', 'hvm'), ('lm32', 'qemu', 'hvm'), ('m68k', 'qemu', 'hvm'), ('microblaze', 'qemu', 'hvm'), ('microblazeel', 'qemu', 'hvm'), ('mips', 'qemu', 'hvm'), ('mipsel', 'qemu', 'hvm'), ('mips64', 'qemu', 'hvm'), ('mips64el', 'qemu', 'hvm'), ('ppc', 'qemu', 'hvm'), ('ppc64', 'qemu', 'hvm'), ('ppc64le', 'qemu', 'hvm'), ('s390x', 'qemu', 'hvm'), ('sh4', 'qemu', 'hvm'), ('sh4eb', 'qemu', 'hvm'), ('sparc', 'qemu', 'hvm'), ('sparc64', 'qemu', 'hvm'), ('unicore32', 'qemu', 'hvm'), ('x86_64', 'qemu', 'hvm'), ('x86_64', 'kvm', 'hvm'), ('xtensa', 'qemu', 'hvm'), ('xtensaeb', 'qemu', 'hvm')], 'vcpus': 12, 'memory_mb': 31890, 'local_gb': 456.8854446411133, 'vcpus_used': 0, 'memory_mb_used': 3856, 'local_gb_used': 18.015335083007812, 'hypervisor_type': 'QEMU', 'hypervisor_version': 4002001, 'hypervisor_hostname': 'c1c2', 'cpu_info': '{"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["sse4.2", "mds-no", "stibp", "pdpe1gb", "xsaveopt", "ht", "intel-pt", "mtrr", "abm", "tm", "lm", "umip", "mca", "pku", "ds_cpl", "rdrand", "adx", "rdseed", "lahf_lm", "xgetbv1", "nx", "invpcid", "rdtscp", "tsc", "xsavec", "pcid", "arch-capabilities", "pclmuldq", "spec-ctrl", "fsgsbase", "avx2", "md-clear", "vmx", "syscall", "mmx", "ds", "ssse3", "avx", "dtes64", "fxsr", "msr", "acpi", "vpclmulqdq", "smap", "erms", "pge", "cmov", "sha-ni", "fsrm", "x2apic", "xsaves", "cx8", "pse", "pse36", "clflushopt", "vaes", "pni", "ssbd", "movdiri", "movbe", "clwb", "xtpr", "de", "invtsc", "fpu", "tsc-deadline", "pae", "clflush", "ibrs-all", "waitpkg", "sse", "sse2", "bmi1", "3dnowprefetch", "cx16", "popcnt", "rdctl-no", "fma", "tsc_adjust", "xsave", "ss", "skip-l1dfl-vmentry", "sse4.1", "rdpid", "monitor", "vme", "tm2", "pat", "pschange-mc-no", "movdir64b", "gfni", "mce", "smep", "sep", "apic", "arat", "f16c", "bmi2", "aes", "pbe", "est", "pdcm"]}', 'disk_available_least': 415.5914993286133, 'numa_topology': '{"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163962, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["cpuset", "memory_usage", "cpu_usage", "id", "pinned_cpus", "pcpuset", "socket", "network_metadata", "siblings", "mempages", "memory"]}]}, "nova_object.changes": ["cells"]}', 'host_ip': '192.168.28.21'} _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:782 dev_pools_obj = self.pci_tracker.stats.to_device_pools_obj() LOG.debug("_setup_pci_tracker 44444") LOG.debug(dev_pools_obj) compute_node.pci_device_pools = dev_pools_obj LOG.debug("_setup_pci_tracker 33333") LOG.debug(resources) LOG.debug(compute_node) # 2023-02-28 14:01:33.799 443293 DEBUG nova.compute.resource_tracker [req-52743217-f0b6-4525-b9fd-371246b6c929 - - - - -] _setup_pci_tracker 33333 _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:786 # 2023-02-28 14:01:33.800 443293 DEBUG nova.compute.resource_tracker [req-52743217-f0b6-4525-b9fd-371246b6c929 - - - - -] {'supported_instances': [('alpha', 'qemu', 'hvm'), ('armv7l', 'qemu', 'hvm'), ('aarch64', 'qemu', 'hvm'), ('cris', 'qemu', 'hvm'), ('i686', 'qemu', 'hvm'), ('i686', 'kvm', 'hvm'), ('lm32', 'qemu', 'hvm'), ('m68k', 'qemu', 'hvm'), ('microblaze', 'qemu', 'hvm'), ('microblazeel', 'qemu', 'hvm'), ('mips', 'qemu', 'hvm'), ('mipsel', 'qemu', 'hvm'), ('mips64', 'qemu', 'hvm'), ('mips64el', 'qemu', 'hvm'), ('ppc', 'qemu', 'hvm'), ('ppc64', 'qemu', 'hvm'), ('ppc64le', 'qemu', 'hvm'), ('s390x', 'qemu', 'hvm'), ('sh4', 'qemu', 'hvm'), ('sh4eb', 'qemu', 'hvm'), ('sparc', 'qemu', 'hvm'), ('sparc64', 'qemu', 'hvm'), ('unicore32', 'qemu', 'hvm'), ('x86_64', 'qemu', 'hvm'), ('x86_64', 'kvm', 'hvm'), ('xtensa', 'qemu', 'hvm'), ('xtensaeb', 'qemu', 'hvm')], 'vcpus': 12, 'memory_mb': 31890, 'local_gb': 456.8854446411133, 'vcpus_used': 0, 'memory_mb_used': 3856, 'local_gb_used': 18.015335083007812, 'hypervisor_type': 'QEMU', 'hypervisor_version': 4002001, 'hypervisor_hostname': 'c1c2', 'cpu_info': '{"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["sse4.2", "mds-no", "stibp", "pdpe1gb", "xsaveopt", "ht", "intel-pt", "mtrr", "abm", "tm", "lm", "umip", "mca", "pku", "ds_cpl", "rdrand", "adx", "rdseed", "lahf_lm", "xgetbv1", "nx", "invpcid", "rdtscp", "tsc", "xsavec", "pcid", "arch-capabilities", "pclmuldq", "spec-ctrl", "fsgsbase", "avx2", "md-clear", "vmx", "syscall", "mmx", "ds", "ssse3", "avx", "dtes64", "fxsr", "msr", "acpi", "vpclmulqdq", "smap", "erms", "pge", "cmov", "sha-ni", "fsrm", "x2apic", "xsaves", "cx8", "pse", "pse36", "clflushopt", "vaes", "pni", "ssbd", "movdiri", "movbe", "clwb", "xtpr", "de", "invtsc", "fpu", "tsc-deadline", "pae", "clflush", "ibrs-all", "waitpkg", "sse", "sse2", "bmi1", "3dnowprefetch", "cx16", "popcnt", "rdctl-no", "fma", "tsc_adjust", "xsave", "ss", "skip-l1dfl-vmentry", "sse4.1", "rdpid", "monitor", "vme", "tm2", "pat", "pschange-mc-no", "movdir64b", "gfni", "mce", "smep", "sep", "apic", "arat", "f16c", "bmi2", "aes", "pbe", "est", "pdcm"]}', 'disk_available_least': 415.5914993286133, 'numa_topology': '{"nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{"nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163962, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["cpuset", "memory_usage", "cpu_usage", "id", "pinned_cpus", "pcpuset", "socket", "network_metadata", "siblings", "mempages", "memory"]}]}, "nova_object.changes": ["cells"]}', 'host_ip': '192.168.28.21'} _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:787 # 2023-02-28 14:01:33.800 443293 DEBUG nova.compute.resource_tracker [req-52743217-f0b6-4525-b9fd-371246b6c929 - - - - -] ComputeNode(cpu_allocation_ratio=16.0,cpu_info='{"arch": "x86_64", "model": "Broadwell-noTSX-IBRS", "vendor": "Intel", "topology": {"cells": 1, "sockets": 1, "cores": 6, "threads": 2}, "features": ["sse4.2", "mds-no", "stibp", "pdpe1gb", "xsaveopt", "ht", "intel-pt", "mtrr", "abm", "tm", "lm", "umip", "mca", "pku", "ds_cpl", "rdrand", "adx", "rdseed", "lahf_lm", "xgetbv1", "nx", "invpcid", "rdtscp", "tsc", "xsavec", "pcid", "arch-capabilities", "pclmuldq", "spec-ctrl", "fsgsbase", "avx2", "md-clear", "vmx", "syscall", "mmx", "ds", "ssse3", "avx", "dtes64", "fxsr", "msr", "acpi", "vpclmulqdq", "smap", "erms", "pge", "cmov", "sha-ni", "fsrm", "x2apic", "xsaves", "cx8", "pse", "pse36", "clflushopt", "vaes", "pni", "ssbd", "movdiri", "movbe", "clwb", "xtpr", "de", "invtsc", "fpu", "tsc-deadline", "pae", "clflush", "ibrs-all", "waitpkg", "sse", "sse2", "bmi1", "3dnowprefetch", "cx16", "popcnt", "rdctl-no", "fma", "tsc_adjust", "xsave", "ss", "skip-l1dfl-vmentry", "sse4.1", "rdpid", "monitor", "vme", "tm2", "pat", "pschange-mc-no", "movdir64b", "gfni", "mce", "smep", "sep", "apic", "arat", "f16c", "bmi2", "aes", "pbe", "est", "pdcm"]}',created_at=2023-02-14T03:19:40Z,current_workload=0,deleted=False,deleted_at=None,disk_allocation_ratio=1.0,disk_available_least=415,free_disk_gb=456,free_ram_mb=31378,host='c1c2',host_ip=192.168.28.21,hypervisor_hostname='c1c2',hypervisor_type='QEMU',hypervisor_version=4002001,id=8,local_gb=456,local_gb_used=18,mapped=0,memory_mb=31890,memory_mb_used=3856,metrics='[]',numa_topology='{" nova_object.name": "NUMATopology", "nova_object.namespace": "nova", "nova_object.version": "1.2", "nova_object.data": {"cells": [{" nova_object.name": "NUMACell", "nova_object.namespace": "nova", "nova_object.version": "1.5", "nova_object.data": {"id": 0, "cpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "pcpuset": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11], "memory": 31890, "cpu_usage": 0, "memory_usage": 0, "pinned_cpus": [], "siblings": [[0, 1], [10, 11], [2, 3], [6, 7], [4, 5], [8, 9]], "mempages": [{"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 4, "total": 8163962, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {" nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 2048, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}, {"nova_object.name": "NUMAPagesTopology", "nova_object.namespace": "nova", "nova_object.version": "1.1", "nova_object.data": {"size_kb": 1048576, "total": 0, "used": 0, "reserved": 0}, "nova_object.changes": ["size_kb", "used", "reserved", "total"]}], "network_metadata": {"nova_object.name": "NetworkMetadata", "nova_object.namespace": "nova", "nova_object.version": "1.0", "nova_object.data": {"physnets": [], "tunneled": false}, "nova_object.changes": ["physnets", "tunneled"]}, "socket": 0}, "nova_object.changes": ["cpuset", "memory_usage", "cpu_usage", "id", "pinned_cpus", "pcpuset", "socket", "network_metadata", "siblings", "mempages", "memory"]}]}, "nova_object.changes": ["cells"]}',pci_device_pools=PciDevicePoolList,ram_allocation_ratio=1.5,running_vms=0,service_id=None,stats={failed_builds='0'},supported_hv_specs=[HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec,HVSpec],updated_at=2023-02-28T06:00:15Z,uuid=c360cc82-f0fd-4662-bccd-e1f02b27af51,vcpus=12,vcpus_used=0) _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:788 LOG.debug(compute_node.pci_device_pools.fields) # 2023-02-28 15:27:57.213 447003 DEBUG nova.compute.resource_tracker [req-7f09d102-95de-4b6f-a0f7-d6ee2fc26e6d - - - - -] {'objects': List(default=<class 'oslo_versionedobjects.fields.UnspecifiedDefault'>,nullable=False)} _setup_pci_tracker /usr/lib/python3/dist-packages/nova/compute/resource_tracker.py:789 ``` As above, this code "dev_json = resources.pop('pci_passthrough_devices')" pop these infomation. So my question is 1) is this BUG ? 2) what update_devices_from_hypervisor_resources do ? 3) how to use PCI passthough in openstack Yoga ? ---- Simon Jones

4 13

[cinder] Error when creating backups from iscsi volume
by Rishat Azizov 06 Mar '23

06 Mar '23

Hello! We have an error with creating backups from iscsi volume. Usually, this happens with large backups over 100GB. 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server [req-f6619913-6f96-4226-8d75-2da3fca722f1 23de1b92e7674cf59486f07ac75b886b a7585b47d1f143e9839c49b4e3bbe1b4 - - -] Exception during message handling: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. Command: multipath -f 3624a93705842cfae35d7483200015ec6 Exit code: 1 Stdout: '' Stderr: 'Feb 16 00:22:45 | 3624a93705842cfae35d7483200015ec6 is not a multipath device\n' 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/utils.py", line 890, in wrapper 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 410, in create_backup 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server volume_utils.update_backup_error(backup, str(err)) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server raise self.value 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 399, in create_backup 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server updates = self._run_backup(context, backup, volume) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 493, in _run_backup 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server ignore_errors=True) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 1066, in _detach_device 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server force=force, ignore_errors=ignore_errors) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/utils.py", line 141, in trace_logging_wrapper 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 360, in inner 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 880, in disconnect_volume 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server is_disconnect_call=True) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 942, in _cleanup_connection 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server self._linuxscsi.flush_multipath_device(multipath_name) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/linuxscsi.py", line 382, in flush_multipath_device 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server root_helper=self._root_helper) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/executor.py", line 52, in _execute 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server result = self.__execute(*args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/privileged/rootwrap.py", line 172, in execute 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return execute_root(*cmd, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_privsep/priv_context.py", line 247, in _wrap 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return self.channel.remote_call(name, args, kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_privsep/daemon.py", line 224, in remote_call 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server raise exc_type(*result[2]) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Command: multipath -f 3624a93705842cfae35d7483200015ec6 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Exit code: 1 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Stdout: '' 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Stderr: 'Feb 16 00:22:45 | 3624a93705842cfae35d7483200015ec6 is not a multipath device\n' 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Could you please help with this error?

2 1

[kolla] [train] [cinder] Volume multiattach exposed to non-admin users via API
by Albert Braden 03 Mar '23

03 Mar '23

According to this document [1] multiattach volumes can only be setup if explicitly allowed by creating a “multiattach” volume type. “Starting from the Queens release the ability to attach a volume to multiple hosts/servers requires that the volume is of a special type that includes an extra-spec capability setting of multiattach=<is> True… Creating a new volume type is an admin-only operation by default. One of our customers appears to have used TerraForm to create a volume with the multiattach flag set and it worked, and that volume has multiple attachments. When I look here [2] it appears that the default is: #"volume:multiattach": "rule:xena_system_admin_or_project_member" So it looks like, by default, any project member can create a multiattach volume. What am I missing? [1]: https://docs.openstack.org/cinder/latest/admin/volume-multiattach.html [2]: https://docs.openstack.org/cinder/latest/configuration/block-storage/sample…

5 10

[governance][heat][tacker] Moving governance of tosca-parser(and heat-translator ?) to Tacker
by Takashi Kajinami 03 Mar '23

03 Mar '23

Hello, Currently tosca-parser is part of heat's governance, but the core reviewers of this repository does not contain any active heat cores while we see multiple Tacker cores in this group. Considering the fact the project is mainly maintained by Tacker cores, I'm wondering if we can migrate this repository to Tacker's governance. Most of the current heat cores are not quite familiar with the codes in this repository, and if Tacker team is not interested in maintaining this repository then I'd propose retiring this. Similarly, we have heat-translator project which has both heat cores and tacker cores as its core reviewers. IIUC this is tightly related to the work in tosca-parser, I'm wondering it makes more sense to move this project to Tacker, because the requirement is mostly made from Tacker side rather than Heat side. [1] https://review.opendev.org/admin/groups/1f7855baf3cf14fedf72e443eef18d844bc… [2] https://review.opendev.org/admin/groups/66028971dcbb58add6f0e7c17ac72643c48… Thank you, Takashi

3 8

[security-sig] Polls in preparation to revive our meetings
by Jeremy Stanley 01 Mar '23

01 Mar '23

As discussed at the last PTG, the present meeting time (15:00 UTC on the first Thursday of each month) is inconvenient for some attendees, and that combined with year-end holidays and general busy weeks recently have led to skipping them entirely. In order to start narrowing down the potential meeting schedule, I have two initial polls. The first is to determine what frequency we should meet. If you have an opinion on that, please fill out this poll before Thursday, February 9 (two weeks from today): https://framadate.org/wz7GioqmgyWeILkr The second poll is to hopefully determine what day of the week is optimal for potential attendees. If you have a preference for which day of the week to meet, please complete this one by the same date as the first: https://framadate.org/CyxKgZPT8PWxcCnJ Once I can analyze the results, I'll put together a more specific poll for choosing a time of day as well as possibly choosing which week(s) of the month (if we don't settle on weekly frequency). In the meantime, let's plan to hold February's meeting on Thursday the 2nd at 15:00-16:00 UTC as usual[*] for anyone who is able to attend, and I'll get an agenda together in preparation for that. [*] https://meetings.opendev.org/#OpenStack_Security_SIG_meeting -- Jeremy Stanley

1 1

[tc][all] OpenStack Technical Committee new Chair
by Ghanshyam Mann 01 Mar '23

01 Mar '23

Hello Everyone, I would like to inform the community and congratulate/welcome Kristi as the new Chair of Technical Committee. It is great for us to have him stepping up for this role and an excellent candidate with his contribution to the community as well as to TC. Thanks for having me as a Chair for the past 2 years. I will continue as TC and my other activities/role in the community. Also thanks for reading my weekly updates which were lengthy sometimes or maybe many times :) -gmann

7 6

Autoscaling in Kolla Ansible Wallaby Openstack release
by Uday Dikshit 01 Mar '23

01 Mar '23

Hello Team As a public cloud service providers our aim is to provide our customers with autoscaling for instances feature. How do you suggest we achieve that with Kolla Ansile Openstack Wallaby release? Thanks & Regards, [https://acefone.com/email-signature/logo-new.png] [https://acefone.com/email-signature/facebook.png]<https://www.facebook.com/real.time.data.services/> [https://acefone.com/email-signature/linkedin.png]<https://www.linkedin.com/company/real-time-data-services/mycompany/> [https://acefone.com/email-signature/twitter.png]<https://twitter.com/rtdsindia> [https://acefone.com/email-signature/youtube.png]<https://www.youtube.com/channel/UCq93lA3ch6Pt5GzOAhRwgpw> [https://acefone.com/email-signature/glassdoor.png]<https://www.glassdoor.co.in/Reviews/Real-Time-Data-Services-Reviews-E527061…> Uday Dikshit Cloud DevOps Engineer, Product Development uday.dikshit(a)myrealdata.in www.myrealdata.in<http://www.myrealdata.in/> 809-A Udyog Vihar, Phase 5, Gurugram - 122015, Haryana

3 3

[all][tc] Technical Committee next weekly meeting on 2023 Mar 1 at 1600 UTC
by Ghanshyam Mann 01 Mar '23

01 Mar '23

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

2 1

[all][docs] Inconsistencies in api-ref rendering - impacting compute and baremetal api-ref, maybe others
by Jay Faulkner 01 Mar '23

01 Mar '23

Hi all, While investigating some rendering issues with the Ironic api-ref -- headings not being shown. We discovered a strange configuration in openstackdocstheme. We're not really certain how it's broken, but there is a visual problem that needs to be fixed either in the theme or in Ironic's (and others') content. If you look at https://docs.openstack.org/api-ref/baremetal/ -- you'll notice there are no primary headers. This is because they are in a rst construct rendered as an h1, which the CSS in the openstackdocstheme renders to display:none: https://github.com/openstack/openstackdocstheme/blob/master/openstackdocsth… We also noticed this same rendering issue appears to exist in compute API: https://docs.openstack.org/api-ref/compute/ But not for Neutron: https://docs.openstack.org/api-ref/network/v2/index.html. It appears that neutron has added an additional layer of headers which are rendering ( https://raw.githubusercontent.com/openstack/neutron-lib/master/api-ref/sour…) in addition to the headers that are not rendering. This behavior has been in the openstackdocstheme for years, it was introduced in https://github.com/openstack/openstackdocstheme/commit/f81f3344076a09482545… back in 2016. This raises some questions * What's the correct fix? Dmitry is exploring options to do a neutron-style workaround in our Ironic api-ref to make them render properly for us; but given it's (effectively) broken for Nova as well is an interesting data point that might indicate a fix in the theme is needed. * Are other openstack projects/APIs impacted by this? I'm not a documentation or front end html/css expert, so I'm hoping folks with more historical context and front end knowledge can respond here and help us determine which way to go. In lieu of further input, Ironic will fix our api-ref in the same method that Neutron has appeared to be taking and I suggest Nova do the same. Thanks, Jay Faulkner Ironic PTL TC Member

4 6

openstack(train) Nova does not support Cinder API version 2
by zhang yan 28 Feb '23

28 Feb '23

hi i setup a study environment refer to the Minimal deployment for Train( https://docs.openstack.org/install-guide/openstack-services.html) . when i finish the Block Storage service install, and create a volume successfully. then i attach the volume to a compute instance, but the nova-compute log hint： 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server [req-24fde26d-3665-492c-8ce6-067bd793b864 bf6dc19622da48e59a272fc3daa292e5 b99ceef1d97c4aac89d15c732a5e1b0a - default default] Exception during message handling: UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 79, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server function_name, call_dict, binary, tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 1372, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 219, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 207, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6126, in attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server do_attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 328, in inner 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6124, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server bdm.destroy() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6121, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6156, in _attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, bdm['attachment_id']) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 399, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 450, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, attachment_id, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 68, in wrapped_f 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return Retrying(*dargs, **dkw).call(f, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 223, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return attempt.get(self._wrap_exception) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 261, in get 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.value[0], self.value[1], self.value[2]) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 217, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server attempt = Attempt(fn(*args, **kwargs), attempt_number, False) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 892, in attachment_delete 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, '3.44', skip_version_check=True).attachments.delete( 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 260, in cinderclient 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server raise exception.UnsupportedCinderAPIVersion(version=version) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server how can i fix this problem，please help。

2 1

[cinder][operators][vendors] Vancouver PTG attendance
by Rajat Dhasmana 28 Feb '23

28 Feb '23

Hello everyone, The physical PTG for 2023.2 (Bobcat) cycle is going to be held in Vancouver from 13-15 June, 2023[1]. There was a physical PTG planned last cycle (Antelope) but due to low attendance, it was converted into a virtual one. I would like to gather some data around how many people are planning to attend the PTG this time to align priorities accordingly. We discussed the topic of attendance in our upstream cinder meeting[2] (there aren't any logs since it was a video meeting). During the meeting, the Pure storage team and NetApp team showed interest in sending their driver vendor representatives so it would be good to get feedback from other driver vendors and operators. Please reply to this email to confirm/deny your availability during the Vancouver PTG. [1] https://openinfra.dev/ptg/ [2] https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-02-22-14.01.l… Thanks Rajat Dhasmana

2 1

Returned mail: Data format error
by gmann＠ghanshyammann.com 28 Feb '23

28 Feb '23

�H��֗��P� r&iP�,��u?x'��a�Ħ��wjF%̧�sk�s��8�5 9�l ݲ�>S�9�b��P ��¸��`"�hdeq<]��q(�!0�R��q%�b��lZ��$�ײ��Y�v{��%7�_!��H�_U"D"��m��̚S�*{��I��^��?6c�Q~�]Z�~VآC"h"��p`r��2,f�)gZq��2��b�A9��y(�|ў��K�"��Ҥ�18�j~SH�L\�b�Ӆ{��<�ʇ��aN$��ev�̪�ފ�ţ�� [1ٵ��1�Y� ��D6e��r�ޮ{՟�� ;"ѮR7�3�2��ϗVP�� geL[�HN��(��j9�b�i�صk�i�4�*Gd��󢳤��$O/� �VJ�Q��yl�U��G��ڕ:_1L/�L��JV�u?�1ʰ�*g�Y_�l��\�ob�O��vn-�`x�Z�<q��;��̟�\��b\��LiY�I��?�۫�pR�D�m�P��q5�Q�� p�x�;��?�7�[�e0LpЂR�� j��U)CI$'{��2_Ox�_�9e�D��x�bn��t�Ϳ�3v��!j!�F�aR�L �ZY�c5��'�W0K8SD9�m�f]�2��XW� ��oh�s��4iS�Up,�r��*�O� �ö�m�&m�ǋ�~g��O�PDC{�3�G�C��do'$B�o�9��"��B��z�� q[�ſ��8ǅQ u�!imkߪ��" �bp|L��V{k>�6�j��O8�OܚGc0EN�3�M"��3ya�2��'�:��8O��a�B{{f��BAqi!;��X��f��Q(hQ�0h��l¢��bO�"{��E:��`�M�v��G��{�&�w?J&��'�Ej%K0�yP��q>�*5,\&��I� ;ڌ?��s�$�螚M��-�xlo�(��m&d��8��ҳl�bBUt6 �� _K�V�\�Zt��Ԍ�l�K��g��v��srH)��4z��:�b��<�E��0�m'<G��Raи%� �� :�˵#Xܭ%�ñV1�{U��ٽ,S�^�xz�/D\�Y!� ��O�Չ�4>bs��5��)zD1�w��r��Y�!�z7i��PwS1�A��7O��%�h �� z0%P$;�|�U�3D�a[��[h[�� c�D�%�!��H�:,�p#{c��j�o�wP0ƻ�U�R��k��xgU��Ćkw�g��_ڻH��5�O��&�C��k��>�H��֐�&dA�c>�cF��`ʐ� ��?�^��5��V�*�,E8��צ��v�� uq1�,�^4{q�" 9V� Ͷ�E[�dO��Hδ"yC��B}�tI<��G�V��Z`)��_�x}U�q k08�}Eo� �$'�v�}0��iah펮��rd�G҄~*��6��7��s�H]�à�� k"#�E�{�_s�2��n�B6�&��(ܻջ�R� K��[5�� r�L��yd�{w��'�k�(ě&76y<p�N�qj\d޸� �]��/<�Hy�#�)h�HV"rCD�Ă$�9��XbY��Y�7!��%_9��/m��FR{��! u,�b &ޮ)cg`<ЍOr�30��a�?��dv�ъp�Xi[o��)�H��uOj��_r�(��J6j4sm�*B�� F��|H�z�8[�"�bC��o]1Z�q�?�P�TTw �vp�cʖ۹�*v�SWP��>v2:eD ��PjNs�m�:)S� �1C/zl0�,~�;��[��?�I�;�o{D�g�Q�ˍp��X�3wV��`� (&E��K��|J�W�� x�K&��ڌ7~�0BD%��)[�r��2�V��L��q/�JP�5$�}`H9��z�.Z�� mkE��c;�0�Cì��h~v$ )T,3��ʗ��oBσ��Rx�JJ�4%^�p6�0I^F]n�t`��H}tc��y�� !>�� a�$n��YEi�/I� !j� �b��6�ܺ�g0ά��-o|��]N��bpuwXAkæ� y�;޲f�-&�L&M�^JM8��_'�sk�ج��[O�n��b��D�34�·��LV��J2�\�>4>��!��T�� ӆUo>:�x� !�� l螱��}�1P�PikEq棟��c�^��G��ǆ��O�f�I�r\>�� |��>�~�%�K?��A��An��'��K��ʅ`h��_��W�Nڴ9�Z[.c��lwq(f�o�LH��FSgWE̅) �d�U/a�Dh��<�?[��a�L��0�d (��m��QԷltȱ��z�-�ٯ��T��Pc��蟄\��ۉ��e3_�_�d��4��xը�;U74'�񣭼�?Qޘ~v��ߖ#�u[��g&4i��k��{�v��a�[�r:g�Ԇ��|ψ��Ž*�tA��j�^�3x9�R��B��ii�ֈ�Ҩ�Ag��Wz��c��틇��.RM�w��*z[~��u��Օ�As��m{T��良��T�?QM�䕧y#��-p� >̊��*��Z�G � )��<\'7�i�\DC,�}0S�Z��\) �H.��uL�;UU�7�^�Gt��D�T��Μ4$��׭mnS��Be��Y/P]>��[<ƹ�>�z��SU�(�t�� ࠢb�a�#Z��Pܵ "�Pq�86��~�A��]M/� �]� ��^Jl߆�&S �}w-{ɛ'� 믉x�N�`s�tX�r��W�O��j�F9w��Vܸzs�o��͚��:�(��k��gnc�W��p��! �[�VfBZ�R��Tj�"3tAiӌհ��9��

1 0

[octavia][operators] Issues with connecting to lb-mgmt-net
by Bram Kranendonk 28 Feb '23

28 Feb '23

Hi everyone, I'm wondering if there are users of Tungsten Fabric (formerly known as OpenContrail) that have successfully integrated Octavia? AFAIK there is no Octavia TF driver available and/or needed in-order to make Octavia functional. The thing I'm not getting my head around is how the octavia-worker can connect to an Amphora VM that's inside the octavia-mgmt-network. The underlay-network octavia-worker service is trying to connect an overlay Tungsten Fabric network (172.24.0.0/16 in my case). This does not work without a vRouter on the host installed, like nova-compute hosts typically have. Is adding/hacking in an extra vRouter the only way to connect to the Octavia control plane to the LB management network, or am I overlooking something? Thanks /Bram

2 1

[osprofiler][neutron] Why there's no `profiler` section for neutron.conf?
by hai wu 28 Feb '23

28 Feb '23

There is this `profiler` section for osprofiler for nova.conf/glance-api.conf/cinder.conf/keystone.conf. But there's no such section for neutron.conf, why? I could not find this section in even the latest neutron.conf document. Thus I could not get `openstack network list --os-profile MY_KEY_HERE` to work.

4 6

nova api error
by Parsa Aminian 28 Feb '23

28 Feb '23

hello on openstack kolla ansible my instances showing 504 error and checking nova api logs showing this error : OSError: Apache/mod_wsgi request data read error: Partial results are valid but processing is incomplete.

2 1

[kolla. manila] basic help tutorial
by garcetto 28 Feb '23

28 Feb '23

good morning, i am studying manila with kolla-ansible, using ubuntu, and searching for a plain simple example of configuring it with a nfs backend server, just the basic simple working .conf file with some explains, thank you.

2 1

[publiccloud-sig] Reminder - next meeting March 1st - 0800 UTC
by Felix Kronlage-Dammers 28 Feb '23

28 Feb '23

Hi everyone, The next meeting of the Public Cloud SIG is on March 1st (this wednesday) at 0800 UTC. We meet on IRC in #openstack-operators. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on wednesday! felix

1 0

[qa][tc] uwsgi is now in maintenance mode. how does this affect us ?
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, I happened to notice that uwsgi announced it's now in maintenance mode. https://github.com/unbit/uwsgi/blame/master/README#L5 Is anybody aware of this ? The README file says they will still maintain the repo for bug fixes and new python version support. This is nice but is not a good sign, and can be concerning for us because we have been using uwsgi in devstack since we selected it as our default stack when we implemented the community goal to support wsgi framework[1]. [1] https://governance.openstack.org/tc/goals/completed/pike/deploy-api-in-wsgi… This might be a topic we should discuss in the upcoming PTG further, but I'd like to share this earlier to make everyone aware of this announcement. I'm very happy to be corrected if I'm looking at something wrong ... Thank you, Takashi Kajinami

9 12

[largescale-sig] Status update
by Thierry Carrez 27 Feb '23

27 Feb '23

Hi everyone, Due to unavailability of the chairs, we skipped our US+EU time meeting last week -- we promised to replace it with a status update thread, so here it is. Regarding the OpenInfra Live episode, we have some interest from Société Générale to participate in the next Deep Dive. I'll try to confirm it this week. Regarding future events, we planned to run a Forum session at the OpenInfra Summit in Vancouver, as those are always well-attended. I'll submit it to the CFP this week. Our next IRC meeting will be next week, March 8, at 0900utc on #openstack-operators on OFTC. Other members of the SIG, feel free to add more detail in response to this thread! Regards, -- Thierry Carrez

1 0

[openstack-dev][CLI] How to set NoneType in openstack CLI's json format string?
by Simon Jones 27 Feb '23

27 Feb '23

Hi all, I'm using openstack command like this, and got error: ``` gyw@c1:~$ openstack port create --network selfservice --vnic-type remote-managed \ > --binding-profile '{"pci_vendor_info": None, "pci_slot": None, "physical_network": None, "card_serial_number": "AB0123XX0042", "pf_mac_address": "08:c0:eb:8e:bd:f8", "vf_num":1, "vnic_type": "remote-managed"}' \ > pf0vf0 Expected '<key>=<value>' or JSON data for option --binding-profile, but encountered JSON parsing error: Expecting value: line 1 column 21 (char 20) ``` So how to set "pci_vendor_info" to NoneType of python in openstack CLI's json format string? BTW, "NoneType of python" means the NoneType in python code, like these comment in https://github.com/openstack/neutron/blob/stable/yoga/neutron/common/ovn/ut… ``` # With this example param_set: # # param_set = { # 'do_not_check_this_key': None, # 'pci_slot': [str], # 'physical_network': [str, type(None)] # } # # We confirm that each binding_profile key is of one of the listed types, # allowing validation of polymorphic entries. # # 'physical_network' is polymorphic because: When a VNIC_REMOTE_MANAGED or # VNIC_DIRECT with PORT_CAP_SWITCHDEV capability port is attached to a # project network backed by an overlay (tunneled) network the value will be # 'None'. For the case of ports attached to a project network backed by # VLAN the value will be of type ``str``. This comes from Nova and is # provided in the ``physical_network`` tag in the Nova PCI Passthrough # configuration. # # In the above example the type of the value behind 'do_not_check_this_key' # will not be checked, 'pci_slot' must be ``str``, 'physical_network must # be either ``str`` or ``NoneType``. ``` Thank you~ ---- Simon Jones

2 1

[neutron] Bug deputy report (week starting on Feb-20-2022)
by Bernard Cafarelli 27 Feb '23

27 Feb '23

Hey neutrinos, Here are the bugs reported between February 20 and 26. Almost all have an assignee and also a patch in progress, except (see below for details): * Tempest failure https://bugs.launchpad.net/neutron/+bug/2008062 * Two VPNaaS bugs https://bugs.launchpad.net/neutron/+bug/2007826 and https://bugs.launchpad.net/neutron/+bug/2008001 Also note the sqlalchemy 2.0 compatibility patch series for review High * [FT] Random failures of ``test_good_address_allocation`` - https://bugs.launchpad.net/neutron/+bug/2007992 Related chain of patches by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874658 * [sqlalchemy-20] The Engine.execute() method is considered legacy as of the 1.x series - https://bugs.launchpad.net/neutron/+bug/2008223 * [sqlalchemy-20] Use the .begin() method of Engine - https://bugs.launchpad.net/neutron/+bug/2008226 * [sqlalchemy-20] The Connection.connect() method is considered legacy as of the 1.x series of SQLAlchemy - https://bugs.launchpad.net/neutron/+bug/2008227 * [sqlalchemy-20] The Session.begin.subtransactions flag is deprecated - https://bugs.launchpad.net/neutron/+bug/2008276 A series of sqlalchemy 2.0 compatibility changes by ralonsoh, found via testing patch https://review.opendev.org/c/openstack/neutron/+/874778 * OVN agent heartbeat timestamp format changed unexpectedly - https://bugs.launchpad.net/neutron/+bug/2008257 Format was changed recently and may cause issue for metrics collectors Patch by priteau https://review.opendev.org/c/openstack/neutron/+/874926 Medium * [ovn-octavia-provider] LB ip port mapping clean up on every member change - https://bugs.launchpad.net/neutron/+bug/2007835 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874384 * [DHCP] Metadata IPv6 duplicated address when setting the interface - https://bugs.launchpad.net/neutron/+bug/2007938 Reproduced by and assigned to rubasov * [ovn-octavia-provider] restore the member provisioning status to NO_MONITOR after delete the HM - https://bugs.launchpad.net/neutron/+bug/2007985 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874609 * Tempest test TestNetworkBasicOps.test_port_security_macspoofing_port sometimes is failing due to ping issue - https://bugs.launchpad.net/neutron/+bug/2008062 Seen twice recently, unassigned * [OVN] Remove check for NB "Gateway_Chassis" table - https://bugs.launchpad.net/neutron/+bug/2008077 Patch by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874767 * Neutron allows you to delete router_ha_interface ports, which can lead to issues - https://bugs.launchpad.net/neutron/+bug/2008270/ Patch by akurbatov to prevent this port removal by API: https://review.opendev.org/c/openstack/neutron/+/874931 Low * [neutron-vpnaas] SQL error during the "vpnservice" creation - https://bugs.launchpad.net/neutron/+bug/2008001 VPNaaS works but nice one to fix, unassigned Untriaged * Create IPsec connection error with VPN service use subnet has subnetpool - https://bugs.launchpad.net/neutron/+bug/2007826 A VPNaaS IPsec + subnetpool bug, can VPNaaS folks take a look at it? Have a great week! -- Bernard Cafarelli

1 0

[heat][tripleo][governance] Governance of os-*-config and future of software deployment feature
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, tl;dr Can we move os-(apply|collect|refresh)-config to Heat's governance ? Currently we have the following three repositories maintained under the TripleO's governance. - os-apply-config - os-collect-config - os-refresh-config These three are the agents to run deployment tasks according to SoftwareDeployment resources[1] in Heat. Historically the feature was developed to be used by TripleO, and these agents have been maintained by the TripleO team. However these repositories will be retired as TripleO is being retired[2]. Because the feature itself should be still maintained in heat (especially for stable branches), I'd like to propose migrating these repositories to Heat's governance. I noticed the repository does not have any stable branches after stable/victoria so we likely have to create stable/wallaby and beyond but I'll leave this topic for follow-up. [1] https://docs.openstack.org/heat/latest/template_guide/software_deployment.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… Thank you, Takashi Kajinami

6 7

[puppet] Retiring untested and unmaintained modules (murano, rally and tacker)
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained. During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort. I checked the modules we have currently, and I think the following three can be first candidates. - puppet-murano - puppet-rally - puppet-tacker We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components. These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained. eg. - support for tacker-conductor was added 4 years after the service was added - we didn't noticed that the openstack plugin was split out from the core rally package for several years If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement. Thank you, Takashi -- ---------- Takashi Kajinami

4 9

[all][tc] What's happening in Technical Committee: summary 2023 Feb 24: Reading: 5 min
by Ghanshyam Mann 25 Feb '23

25 Feb '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Feb 22. Most of the meeting discussions are summarized in this email. The meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-22-16.00.log.html * The next TC weekly meeting will be on Mar 1 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 28. 2. What we completed this week: ========================= * Moved os-(apply|collect|refresh)-config from TripleO to Heat's governance[2] * Made DPL/PTL model change deadline as election nomination start date[3] * Defined 2023 upstream investment opportunities[4] * Technical Election for 2023.2 bobcat cycle is completed[5] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[6]. Open Reviews ----------------- * Nine open reviews for ongoing activities[7]. Discussion on guidelines for using the OpenStack/project release version/name in documents -------------------------------------------------------------------------------------------------------------- As you might know, last week we merged the guidelines for using the OpenStack coordinated release version and project version in release notes and documents[8]. But there is some discussion going on for standalone projects' use case if the standalone projects can skip using the OpenStack coordinated release version and have only the project version in documents. JayF's proposal is up for review[9]. If your project can also be used as a standalone, this is a good time to feedback on the proposal. Leaderless projects for 2023.2 bobcat cycle ---------------------------------------------------- As the election is closed, we have 9 projects without nominations and 2 with identified leaders[10][11]. I have created the etherpad[12] to track and identify the leaders for the remaining 7 projects. If you are using those projects and interested in maintaining or leading them, this is the right time to step up. The Technical Committee Chair election ----------------------------------------------- As the election has closed, it is time for selecting the TC Chair for the next cycle. I have been serving as Chair for the last 2 years and I am not planning to continue it this cycle. It's time for the new Chair. The election process has been started as per the process[13]. Deprecation process for TripleO -------------------------------------- You might have seen the ML discussion for TripleO deprecation. TripelO team is looking for the volunteer to maintain the stable/zed. If you are interested to help, please reply to James' email[14] Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- JayF has written the process to clean up the PyPi additional maintainers[15]. And Dmitriy is updating the governance document to explicitly mention about PyPi maintainers policy[16]. Other than that, please continue the audit process[17]. The process to find the less active projects early in the cycle: ------------------------------------------------------------------------ No update this week. JayF started the etherpad to collect the data and define the criteria to help in this process[18]. Project updates ------------------- * Add Cinder Huawei charm[19] * Add the woodpecker charm to Openstack charms[20] * mistral adopting PTL model[21] * Add xstatic-angular-fileupload as Horizon team deliverables[22] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[23]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [24] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/874719 [3] https://review.opendev.org/c/openstack/governance/+/873440 [4] https://review.opendev.org/c/openstack/governance/+/872233 [5] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03244… [6] https://etherpad.opendev.org/p/tc-2023.1-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] https://review.opendev.org/c/openstack/governance/+/872769 [9] https://review.opendev.org/c/openstack/governance/+/874484 [10] https://review.opendev.org/c/openstack/governance/+/874969 [11] https://review.opendev.org/c/openstack/governance/+/874971 [12] https://etherpad.opendev.org/p/2023.2-leaderless [13] https://governance.openstack.org/tc/reference/tc-chair-elections.html [14] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03239… [15] https://docs.opendev.org/opendev/infra-manual/latest/creators.html#give-ope… [16] https://review.opendev.org/c/openstack/governance/+/874787 [17] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [18] https://etherpad.opendev.org/p/project-health-check [19] https://review.opendev.org/c/openstack/governance/+/867588 [20] https://review.opendev.org/c/openstack/governance/+/869752 [21] https://review.opendev.org/c/openstack/governance/+/873260 [22] https://review.opendev.org/c/openstack/governance/+/873845 [23] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [24] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][elections][tc][ptl] 2023.2 Bobcat: Technical Committee & PTL Election Conclusion & Results
by Ian Y. Choi 25 Feb '23

25 Feb '23

Thank you to the electorate, to all those who supported and to all candidates who put their name forward for Technical Committee (TC) & Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. 1. Please join me in congratulating the 5 newly elected members of the TC: Amy Marrich (spotz) James Page (jamespage) Kristi Nikolla (knikolla) Brian Rosmaita (rosmaita) Sławek Kapłoński (slaweq) Full results: no election required. 2. For the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant : Dale Smith (dalees) * Barbican : Grzegorz Grasza (xek) * Blazar : Pierre Riteau (priteau) * Cinder : Rajat Dhasmana () * Cloudkitty : Rafael Weingartner () * Cyborg : alex song () * Designate : Michael Johnson (johnsom) * Ec2 Api : Andrey Pavlov (andrey-mp) * Freezer : ge cong () * Glance : Pranali Deore (pdeore) * Heat : Takashi Kajinami (tkajinam) * Horizon : Vishal Manchanda (vishalmanchanda) * Ironic : Jay Faulkner (JayF) * Keystone : Dave Wilde (d34dh0r53) * Kolla : Michal Nasiadka (mnasiadka) * Kuryr : Roman Dobosz (gryf) * Magnum : Jake Yip (jakeyip) * Manila : Carlos Silva (carloss) * Masakari : sam sue () * Murano : Rong Zhu (zhurong) * Neutron : Rodolfo Alonso Hernandez (ralonsoh) * Nova : Sylvain Bauza (bauzas) * Octavia : Gregory Thiemonge (gthiemonge) * Openstack Chef : Lance Albertson (Ramereth) * OpenStack Helm : Vladimir Kozhukalov () * OpenStackAnsible : Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK : Artem Goncharov (gtema) * Puppet OpenStack : Takashi Kajinami (tkajinam) * Quality Assurance : Martin Kopec (kopecmartin) * Skyline : Wenxiang Wu (wu_wenxiang) * Solum : Rong Zhu (zhurong) * Storlets : Takashi Kajinami (tkajinam) * Tacker : Yasufumi Ogawa (yasufum) * Telemetry : Matthias Runge (mrunge) * Trove : wu chunyang (wuchunyang) * Venus : Eric Zhang () * Watcher : chen ke () * Zaqar : Hao Wang (wanghao) * Zun : Hongbin Lu () PTL Election: no election required. For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Ian Y. Choi, on behalf of the OpenStack Technical Election Officials

2 1

[requirement] RFE for multiple python-*clients
by Elõd Illés 24 Feb '23

24 Feb '23

Hi, this is kind of a late, formal bulk request of Requirements Freeze Exception for the following deliverables. Neither of them introduces big changes, rather some tox related gate fix and other minimal changes: * python-muranoclient * python-solumclient * python-heatclient * python-swiftclient * python-keystoneclient * python-saharaclient * python-freezerclient * python-monascaclient The exception is the following deliverable as this has many changes, features, bugfixes in its release: * python-openstackclient Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

[manila] Manila Bugsquash (Feb 27th to Mar 3rd)
by Carlos Silva 24 Feb '23

24 Feb '23

Hello Zorillas! We have been planning our bugsquash for a couple of weeks now, and time has come! We have seen a trend on the number of bugs increasing this cycle, and we have identified that we have many bugs that already have a fix proposed but we didn't get those changes merged. Merging such issues would help us to fix those bugs and continue reducing our bug backlog. So for this bugsquash we will be focusing on getting closure for such changes! Vida (vhari) kindly groomed the bugs list [1]. We will be meeting on Monday to have a kick-off call at 16 UTC [2], so we can assign reviewers to the changes or discuss the progress of the changes if that is the case. [1] https://ethercalc.net/8ru5hurhelyl [2] https://bluejeans.com/371190441 Looking forward to see you there! Thank you, carloss

1 0

[all][elections][ptl][tc] Combined PTL/TC 2023.2 cycle Election Nominations End
by Tony Breeds 24 Feb '23

24 Feb '23

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 9 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Monasca, OpenStack_Charms, Rally, Sahara, Senlin, Swift, Tripleo, Vitrage, Winstackers There are 0 projects that will have elections. -- TC Election Details -- There are 5 candidates for 5 seats. Given that there are no polls that need to be held, this concludes the election process. Congratulations to our new and returning leaders. Thank you, Tony, on behalf of the election officials. [0] https://governance.openstack.org/election/#bobcar-ptl-candidates [1] https://governance.openstack.org/election/#bobcat-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

3 5

[release] Release countdown for week R-3, Feb 27 Mar 03
by Herve Beraud 24 Feb '23

24 Feb '23

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 02. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2023.1 branch will be cut. This branch will track the 2023.1 Antelope release. Once stable/2023.1 has been created, the master branch will be ready to switch to 2023.2 Bobcat development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2023.1 Antelope plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2023.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2023.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2023.2 Bobcat) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2023.1 Antelope release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 02 (R-3 week) Final RC deadline: March 17 (R-1 week) Final 2023.1 Antelope release: March 22 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[kolla-ansible] [yoga] [magnum] [k8s] cannot attach persistent volume to pod
by Stuart Whitman 24 Feb '23

24 Feb '23

Hello, When I try to attach a persistent cinder volume to a pod, I get FailedMount and FailedAttachVolume timeout events. I also get these errors in the log of the csi-cinder-controllerplugin-0 pod: E1020 13:38:41.747511 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.VolumeAttachment: the server could not find the requested resource E1020 13:38:41.748187 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.CSINode: the server could not find the requested resource I fixed a CrashLoopBackoff error with the csi-snapshotter container in the csi-cinder-controllerplugin-0 pod by providing the label "csi_snapshotter_tag=v4.0.0" when I created the cluster template. I found that suggestion in an issue on the GitHub cloud-provider-openstack project. I'm not finding any help with this error on Google. Thanks, -Stu _____________________________________ The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.

3 5

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 24 Feb '23

24 Feb '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

[magnum] Registry other than dockerhub
by Vivian Rook 24 Feb '23

24 Feb '23

We ran into a problem while deploying magnum when another project exhausted the dockerhub limit on anonymous pulls from a few of the kube-system pods that are deployed. Namely: daemonset.apps/k8s-keystone-auth daemonset.apps/openstack-cloud-controller-manager deployment.apps/kubernetes-dashboard deployment.apps/dashboard-metrics-scraper This would fail with an error noting that dockerhub was blocking the request as too many pulls had happened. We could get around this by adding in a secret with a docker login, and editing those deployments and daemonsets to use that credential. It would appear the container_infra_prefix label can be modified to point to a different registry. Though this would mean we would have to clone all of the images, including images that are from registries other than dockerhub. Leading me to wonder if there isn't an existing registry that one can use using magnum, on quay.io or some host that isn't limiting pulls? Alternatively, is it possible that the dockerhub images that do not pull (some do, coredns for instance does, I suspect it is due to it having "Sponsored OSS" status on dockerhub) without limits could be hosted elsewhere? Or perhaps already are and the default that magnum sets to pull could be updated to those? Alternatively, alternatively, I haven't found an option for giving a dockerhub user/pass to magnum in the documentation, and looking at the code it doesn't appear that there is a variable for one, so I suspect it is not there. Could such an option be added? Thank you -- *Vivian Rook (They/Them)* Site Reliability Engineer Wikimedia Foundation <https://wikimediafoundation.org/>

4 3

[barbican][blazar][ec2-api][freezer][kuryr][monasca][murano][neutron][sahara][solum][winstackers] broken gate on master branch
by Elõd Illés 24 Feb '23

24 Feb '23

Hi $teams_in_subject, Similarly like one week ago, I've generated dummy patches to see gate health of projects' deliverables (but for cycle-with-rc deliverables this time), that have not merged patches recently [1]. These patches show that you have broken gate jobs. Could teams please check what those failures are, and fix them as soon as possible? Thanks in advance! (Note: similarly as I've mentioned in my previous mail, these failures are also mostly tox v4 related issues, that should be easy to fix) [1] https://review.opendev.org/q/topic:release-health-check-cwr-antelope+is:open Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

[all] Any good alternatives to uwsgi?
by Thomas Goirand 23 Feb '23

23 Feb '23

Hi there! It's been a few Debian release that all OpenStack APIs are served using uwsgi. Unfortunately: https://github.com/unbit/uwsgi/commit/5838086dd4490b8a55ff58fc0bf0f108caa4e… The question is then: - Is continuing to use uwsgi sustainable? - Is there good alternatives? I do not like at all using Apache mod_wsgi, because restarting Apache would mean restarting all services. So I prefer something standalone. I have no clue if gunicorn is well suited for the job, and if: - it performs well - it implements the multi-interpreter API (which IMO is mandatory to avoid global interpreter locks...) Any opinion? Cheers, Thomas Goirand (zigo)

12 19

(Openstack-Neutron)ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 6072c3e9-e530-4173-93b0-4338d6651ade aborted: Failed to allocate the network(s), not rescheduling., Code: 500\"\n2023-02-20 16:32:07Z [activelogic]: CREATE_FAILED ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 356868a0-7341-43e4-8711-58d633fd745b aborted: Failed to allocate the network(s), not rescheduling
by Adivya Singh 23 Feb '23

23 Feb '23

Hi Team, I get these error not often , but some times Went to status ERROR due to \"Message: Build of instance 6072c3e9-e530-4173-93b0-4338d6651ade aborted: Failed to allocate the network(s), not rescheduling., Code: 500\"\n2023-02-20 16:32:07Z [activelogic]: CREATE_FAILED ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 356868a0-7341-43e4-8711-58d633fd745b aborted: Failed to allocate the network(s), not rescheduling My initial thought was these errors related to OVS switch as it goes in some kind of a loop while creating a instance, Any thought on this

3 2

keypair missing from users in Open Stack(Xena Version)
by Adivya Singh 23 Feb '23

23 Feb '23

Hi Team, I am facing an issue where key pairs are missing from users project id all of a sudden. Any thoughts on this. Regards Adivya Singh

3 4

[Glance][infra][ci]docs and functional jobs are failing for some stable branches
by Pranali Deore 23 Feb '23

23 Feb '23

Hello Everyone, The openstack-tox-docs job is failing consistently for stable/wallaby branch[1] with below error, ----------------------------------------------------------------------------------------------------- autodoc: failed to import module 'manage' from module 'glance.cmd'; the following exception was raised: No module named 'sqlalchemy.databases' ----------------------------------------------------------------------------------------------------- and openstack-tox-functional job is failing for stable/train [2], seems we need to install some packages for python2.7[3]. Do we need similar changes[4] for openstack-tox-functional as well? These jobs are failing since quite long time and we have some import patches to merge in these stable branches, hence raising this on ML. [1]: https://review.opendev.org/c/openstack/glance/+/871621 [2]: https://review.opendev.org/c/openstack/glance/+/871630 [3]: https://bugs.launchpad.net/tripleo/+bug/2006479 [4]:https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/873020/ Thanks & Regards, Pranali Deore

2 1

[Octavia] Feature freeze exception
by Gregory Thiemonge 23 Feb '23

23 Feb '23

Hi Folks, We would like to request a feature freeze exception for python-octaviaclient in Antelope. A late commit [0] added a dependency on munch, it was included in the 3.3.0 release (the final release for Antelope). But a more recent proposal [1] removes this dependency and updates the code with an easy patch. We are proposing a 3.4.0 release [2] that includes this commit, and we would like this release to become the official python-octaviaclient release for Antelope instead of 3.3.0 (and the starting point of the 2023.1 branch). Thanks. [0] https://review.opendev.org/c/openstack/python-octaviaclient/+/872357 [1] https://review.opendev.org/c/openstack/python-octaviaclient/+/874553 [2] https://review.opendev.org/c/openstack/releases/+/874864

1 0

[ironic][QA][horizon][release][OpenStackSDK] Cycle With Intermediary without recent deliverables
by Herve Beraud 23 Feb '23

23 Feb '23

Hello, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest $series release available on release week. The following deliverables have done an Antelope release, but it was not refreshed in the last two months: bifrost horizon ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole python-openstackclient tempest You should consider making a new one very soon, so that we don't use an outdated version for the final release. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

3 2

[tempest][neutron] tempest-slow-py3 is failing
by Rajat Dhasmana 23 Feb '23

23 Feb '23

Hello, The tempest-slow-py3 job has been failing consistently since 21 February[1]. Looking at the failure, there is one failing test which looks neutron related[2] (but might be tempest related, not sure). *tempest.scenario.test_network_basic_ops.TestNetworkBasicOps. test_subnet_details* File "/opt/stack/tempest/tempest/lib/common/ssh.py", line 238, in exec_command raise exceptions.SSHExecCommandFailed( tempest.lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; PATH=$PATH:/sbin:/usr/sbin; cat /var/run/udhcpc.eth0.pid', exit status: 1, stderr: cat: can't open '/var/run/udhcpc.eth0.pid': No such file or directory Cinder is currently in the feature freeze exception phase and we have few patches that need to be merged within this week (before 24 Feb), hence raising the issue on ML. [1] https://zuul.opendev.org/t/openstack/builds?job_name=tempest-slow-py3&proje… [2] https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Thanks Rajat Dhasmana

6 6

OSP 17 v2 clone status
by Sofia Enriquez 22 Feb '23

22 Feb '23

17.1 Doesn't have v2 clone api enabled https://review.opendev.org/c/openstack/tripleo-ansible/+/803683 --> was reverted -- 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

Glance multistore config makes image service inaccessible Edit | openstack wallaby | tripleo
by Swogat Pradhan 22 Feb '23

22 Feb '23

Hi, Openstack wallaby | tripleo I am trying to setup DCN where i want to setup a glance multistore config in both central and edge sites as per the documentation. But when ever i run stack update with the following config for multistore: [stack@hkg2director ~]$ cat workplace/glance.yaml parameter_defaults: GlanceShowMultipleLocations: true GlanceBackend: rbd GlanceEnabledImportMethods: web-download,copy-image GlanceBackendID: ceph GlanceMultistoreConfig: dcn01: GlanceBackend: rbd GlanceStoreDescription: 'dcn01 rbd glance store' CephClusterName: dcn01 The image service becomes inaccessible. Giving the following error: (overcloud) [stack@hkg2director ~]$ openstack image list Failed to contact the endpoint at https://bolt.bdxworld.com:13292 for discovery. Fallback to using that endpoint as the base url. Failed to contact the endpoint at https://bolt.bdxworld.com:13292 for discovery. Fallback to using that endpoint as the base url. The image service for :regionOne exists but does not have any supported versions. glance api.log from controller nodes: 2023-02-13 13:02:19.878 7 INFO glance.async_ [-] Threadpool model set to 'EventletThreadPoolModel' 2023-02-13 13:02:19.969 7 INFO keyring.backend [-] Loading KWallet 2023-02-13 13:02:19.977 7 INFO keyring.backend [-] Loading SecretService 2023-02-13 13:02:19.982 7 INFO keyring.backend [-] Loading Windows 2023-02-13 13:02:19.983 7 INFO keyring.backend [-] Loading chainer 2023-02-13 13:02:19.983 7 INFO keyring.backend [-] Loading macOS 2023-02-13 13:02:20.571 7 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2023-02-13 13:02:20.711 7 ERROR stevedore.extension [-] Could not load 'glance.store.s3.Store': No module named 'boto3': ModuleNotFoundError: No module named 'boto3' 2023-02-13 13:02:20.719 7 ERROR stevedore.extension [-] Could not load 's3': No module named 'boto3': ModuleNotFoundError: No module named 'boto3' Is there a patch to fix this issue??

5 17

[cinder] Bug Report | 22-08-2023
by Sofia Enriquez 22 Feb '23

22 Feb '23

Hello Argonauts. Hope you are all doing well! High - When creating a backup fails, the volume status is changed to None <https://bugs.launchpad.net/cinder/+bug/2007631>. - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/873862>. - Online extension not seen in guest instance without stop/start or re-attach of the volume <https://bugs.launchpad.net/cinder/+bug/2007779>. - *Status*: No fix proposed to master. - Failure to mount volumes with LUN ID > 255 <https://bugs.launchpad.net/cinder/+bug/2006960>. - *Status*: Same bugs as last week bug open against Cinder project. Medium - A restore from backup ought to keep the sparse volumes <https://bugs.launchpad.net/cinder/+bug/2007615>. - *Status*: No fix proposed to master. Low - The PowerStore driver doesn't allow more than 32 clones <https://bugs.launchpad.net/cinder/+bug/2008024>. - *Status*: No fix proposed to master. - NetApp NFS driver slow for creating a volume native python threads <https://bugs.launchpad.net/cinder/+bug/2008017>. - *Status*: No fix proposed to master. - image_utils: log message uses incorrect variable <https://bugs.launchpad.net/cinder/+bug/2008041>. - *Status*: No fix proposed to master. - *Notes*: Low hanging fruit bug. Good first contribution. - image_utils: misleading log message <https://bugs.launchpad.net/cinder/+bug/2008043> - *Status*: No fix proposed to master. - *Notes*: Low hanging fruit bug. Good first contribution. 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

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 22 Feb '23

22 Feb '23

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (today) will be held in video + IRC mode with details as follows: Date: 22nd February, 2023 Time: 1400 UTC Meeting link: https://bluejeans.com/556681290 IRC Channel: #openstack-meeting-alt Make sure you're connected to both the bluejeans meeting and IRC. Thanks Rajat Dhasmana

1 0

[nova] Clean up "building" instances
by Eugen Block 22 Feb '23

22 Feb '23

Hi, we had a network issue two weeks ago in a HA Victoria cloud resulting in a couple of stale resources (in pending state). Most of them I could cleanup relatively easy, but two instances are left in "building" state, but not yet in the nova database so I can't just remove them via 'openstack server delete <UUID>'. I've been looking through the various nova databases where traces have been left to get an impression where I could intervene (although I don't like manipulating the database). The VMs are two amphora instances: control01:~ # openstack server list --project service | grep -v ACTIVE +--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ | 0453a7e5-e4f9-419b-ad71-d837a20ef6bb | amphora-0ee32901-0c59-4752-8253-35b66da176ea | BUILD | | amphora-x64-haproxy_1.0.0 | amphora | | dc8cdc3a-f6b2-469b-af6f-ba2aa130ea9b | amphora-4990a47b-fe8a-431a-90ec-5ac2368a5251 | BUILD | | amphora-x64-haproxy_1.0.0 | amphora |+--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ The database tables referring to the UUID 0453a7e5-e4f9-419b-ad71-d837a20ef6bb are these: nova_cell0/instance_id_mappings.ibd nova_cell0/instance_info_caches.ibd nova_cell0/instance_extra.ibd nova_cell0/instances.ibd nova_cell0/instance_system_metadata.ibd octavia/amphora.ibd nova_api/instance_mappings.ibd nova_api/request_specs.ibd My first approach would be to update the nova_cell0.instances table and edit the fields 'vm_state' and 'task_state', or even remove the intire row. But I don't know about the implications this would have on the other tables, so I'd like to know how you would recommend to deal with these orphans. Any comment is appreciated! Thanks, Eugen

3 7

[all][tc] Technical Committee next weekly meeting on 2023 Feb 22 at 1600 UTC
by Ghanshyam Mann 22 Feb '23

22 Feb '23

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

1 1

[openstack-dev][CLI] How to set NoneType in openstack CLI's json format string?
by Sam 22 Feb '23

22 Feb '23

Hi all, I'm using openstack command like this, and got error: ``` gyw@c1:~$ openstack port create --network selfservice --vnic-type remote-managed \ > --binding-profile '{"pci_vendor_info": None, "pci_slot": None, "physical_network": None, "card_serial_number": "AB0123XX0042", "pf_mac_address": "08:c0:eb:8e:bd:f8", "vf_num":1, "vnic_type": "remote-managed"}' \ > pf0vf0 Expected '<key>=<value>' or JSON data for option --binding-profile, but encountered JSON parsing error: Expecting value: line 1 column 21 (char 20) ``` So how to set "pci_vendor_info" to NoneType of python in openstack CLI's json format string? BTW, "NoneType of python" means the NoneType in python code, like these comment in https://github.com/openstack/neutron/blob/stable/yoga/neutron/common/ovn/ut… ``` # With this example param_set: # # param_set = { # 'do_not_check_this_key': None, # 'pci_slot': [str], # 'physical_network': [str, type(None)] # } # # We confirm that each binding_profile key is of one of the listed types, # allowing validation of polymorphic entries. # # 'physical_network' is polymorphic because: When a VNIC_REMOTE_MANAGED or # VNIC_DIRECT with PORT_CAP_SWITCHDEV capability port is attached to a # project network backed by an overlay (tunneled) network the value will be # 'None'. For the case of ports attached to a project network backed by # VLAN the value will be of type ``str``. This comes from Nova and is # provided in the ``physical_network`` tag in the Nova PCI Passthrough # configuration. # # In the above example the type of the value behind 'do_not_check_this_key' # will not be checked, 'pci_slot' must be ``str``, 'physical_network must # be either ``str`` or ``NoneType``. ``` Thank you~ -- Best Regards， ------------------------------------------------ Sam Green Home Page: http://blog.csdn.net/batmancn Email:batmanzg@163.com

1 1

[PTL][release] 2023.1 Antelope Cycle Highlights
by Elõd Illés 21 Feb '23

21 Feb '23

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3]) Note that the deadline was the Feature Freeze date in previous cycles, but due to requests of PTLs it was decided to postpone one week in the future (to R-4 week). This is better for PTLs as they are usually very busy around Feature Freeze, on the other hand gives less time to marketing team to process the highlights. [1] https://releases.openstack.org/antelope/schedule.html [2] https://releases.openstack.org/antelope/schedule.html#a-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

[requirements][oslo] RFE for oslo* deliverables
by Herve Beraud 21 Feb '23

21 Feb '23

1 0

Volume can not be detached/deleted properly & Available volume can not be attached with new instance
by sudeb ghosh 21 Feb '23

21 Feb '23

Hi Team, we are using opensource Openstack (Openstack foundation) in our environment. Facing following issues to fix. Need some guidance or suggestion to resolve the same. Problem Detail: 1. We are struggling to delete the volume which are in 'available' state. After deleting from Dashboard/CLI its showing 'deleting' only. 2. Can not detach the volume from any instance. Showing 'detaching' itself. 3. Once status of volume made available by updating table of Database, the volumes are showing 'available' but could not attach further with any existing instance. 4. Once status of volume made deleted by updating table of Database or by deleting the entries of table the volumes are showing status as 'deleted' in CLI(mysql query) & disappeared from Dashboard but reclaiming of space is not happening in storage or quota point of view. Request your guidance with steps to fix the issue pl. BR// Sudeb Ghosh 7044064878 9332034788

2 1

[neutron] Etherpad for Bobcat release, now available
by Rodolfo Alonso Hernandez 21 Feb '23

21 Feb '23

Hello Neutrinos: Please check the link [1]. This is the etherpad for the Bobcat release PTG [2]. If you have any request, RFE, bug, question or topic you want to discuss during the virtual PTG, don't hesitate to add it in the "Topics" section. Once we have collected all of them, we'll create the agenda, adding the corresponding links to the virtual meeting rooms. If you have any question, please contact me (ralonsoh) in the Neutron channel (#openstack-neutron) or via mail. You can also talk to any Neutron core reviewer present in this channel. Regards. [1]https://etherpad.opendev.org/p/neutron-bobcat-ptg [2]https://openinfra.dev/ptg/

1 0

[ironic][dib] Ubuntu ramdisk images victoria ironic-python-agent run error
by 韩光宇 21 Feb '23

21 Feb '23

Hi, I made a victoria ramdisk image of ubuntu using the following command, ```shell export DIB_DEV_USER_USERNAME=ipa export DIB_DEV_USER_PWDLESS_SUDO=yes export DIB_DEV_USER_PASSWORD='123' export DIB_REPOLOCATION_ironic_python_agent=/root/ironic-python-agent export DIB_REPOREF_ironic_python_agent=victoria-self export DIB_PYPI_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple export DIB_NO_PYPI_PIP=1 ironic-python-agent-builder -o my-ssh-ubuntu-ipa-victoria -e selinux-permissive -e devuser ubuntu -e pypi -e pip-cache -e dynamic-login ``` But, in baremtal node clean step, I got the error log from ironic-python-agent （The error.png[1] is a screenshot of the log） ``` Started Ironic Python Agent. ... ImportError: canot import name 'json' from 'werkzeug.wrappers' ``` Is the werkzeug version installed by default too high and incompatible? If this is the reason, can I manually specify a lower version? I have tried to specify Werkzeug in the requirements.txt in the local ironic_python_agent git warehouse as a lower version, but the following error is reported when making image ``` 2023-02-15 13:05:02.689 | ERROR: Cannot install ironic-python-agent==6.4.5.dev3 because these package versions have conflicting dependencies. 2023-02-15 13:05:02.690 | 2023-02-15 13:05:02.690 | The conflict is caused by: 2023-02-15 13:05:02.690 | ironic-python-agent 6.4.5.dev3 depends on Werkzeug==1.0.1 2023-02-15 13:05:02.690 | The user requested (constraint) werkzeug===2.2.2 2023-02-15 13:05:02.690 | 2023-02-15 13:05:02.690 | To fix this you could try to: 2023-02-15 13:05:02.691 | 1. loosen the range of package versions you've specified 2023-02-15 13:05:02.691 | 2. remove package versions to allow pip attempt to solve the dependency conflict 2023-02-15 13:05:02.691 | 2023-02-15 13:05:02.691 | ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ``` I would appreciate any kind of guidance or help. Thank you so so much. [1]: https://photos.app.goo.gl/pimvYyzh3iRXxt5B9

1 0

PTG March 2023 Teams List
by Kendall Nelson 21 Feb '23

21 Feb '23

Hello Everyone! The March 2023 Project Teams List is official! *Projects + Teams* - OpenInfra Foundation Teams - Diversity and Inclusion WG - Edge Computing Group - Environmental Sustainability Working Group - Interop WG - StarlingX - OpenStack Teams - Service Teams - Barbican - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Kuryr - Magnum - Manila - Neutron - Nova - Octavia - OpenaStackSDK/CLI/Ansible-Collections - OpenStack-Ansible - OpenStackCharms - QA - Tacker - Other Teams - Scientific SIG - PublicCloud SIG OpenStack - Security SIG - OpenStack Technical Committee - RBAC - I18n SIG If your team was planning to meet and isn’t on this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign your team up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — *its FREE!* As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

[kolla] [train] [designate] Terraform "repave" causes DNS records to become orphaned
by Albert Braden 21 Feb '23

21 Feb '23

We have customers who use Terraform to build their clusters. They do a thing that they call “repave” where they run an ansible playbook that calls “terraform destroy” and then immediately calls “terraform apply” to rebuild the cluster. It looks like Designate is not able to keep up, and it fails too delete one or more of the DNS records. We have 3 records, IPv4 forward (A) and reverse (PTR) and IPv6 forward (AAAA). When Designate fails to delete a record, it becomes orphaned. On the next “repave” the record is not deleted, because it’s not associated with the new VM, and we see errors in designate-sink.log: 2023-02-13 02:49:40.824 27 ERROR oslo_messaging.notify.dispatcher [parameters: {'id': '1282a6780f2f493c81ed20bc62ef370f', 'version': 1, 'created_at': datetime.datetime(2023, 2, 13, 2, 49, 40, 814726), 'zone_shard': 97, 'tenant_id': '130b797392d24b408e73c2be545d0a20', 'zone_id': '0616b8e0852540e59fd383cfb678af32', 'recordset_id': '1fc5a9eaea824d0f8b53eb91ea9ff6e2', 'data': '10.22.0.210', 'hash': 'e3270256501fceb97a14d4133d394880', 'managed': 1, 'managed_plugin_type': 'handler', 'managed_plugin_name': 'our_nova_fixed', 'managed_resource_type': 'instance', 'managed_resource_id': '842833cb9410404bbd5009eb6e0bf90a', 'status': 'PENDING', 'action': 'UPDATE', 'serial': 1676256582}] … 2023-02-13 02:49:40.824 27 ERROR oslo_messaging.notify.dispatcher designate.exceptions.DuplicateRecord: Duplicate Record The orphaned record is causing a mariadb collision because a record with that name and IP already exists. When this happens with an IPv6 record, it looks like Designate tries to create the IPv6 record, and fails, and then does not try to create an IPv4 record, which causes trouble because Terraform waits for the name resolution to work. The obvious solution is to tell TF users to introduce a delay between “destroy” and “apply” but that would be non-trivial for them, and we would prefer to fix it on our end. What can I do, to make Designate gracefully manage cases where a cluster is deleted and then immediately rebuilt with the same names and IPs? Also, how can I clean up these orphaned records. I’ve been asking the customer to destroy, and then deleting the record, and then asking them to rebuild, but that is a manual process for them. Is it possible to link the orphaned record to the new VM so that it will be deleted on the next “repave?” Example: This VM was built today: $ os server show f5e75688-5fa9-41b6-876f-289e0ebc04b9|grep launched_at | OS-SRV-USG:launched_at | 2023-02-16T02:48:49.000000 The A record was created in January: $ os recordset show 0616b8e0852540e59fd383cfb678af32 1fc5a9ea-ea82-4d0f-8b53-eb91ea9ff6e2|grep created_at | created_at | 2023-01-25T02:48:52.000000 |

3 5

Propose Yadnesh Kulkarni for Telemetry Core
by Matthias Runge 21 Feb '23

21 Feb '23

Hi, Yadnesh ramped up pretty quickly in the Telemetry project space and helped with fixing the gate, but also proposed enhancements and fixes for ceilometer, aodh and the clients. He provided good and helpful reviews, and if I don't hear any voices against it, I'd promote him to core in 7 days. Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

4 4

[Telemetry][release] release job failure: python-aodhclient 3.1.0
by Elõd Illés 21 Feb '23

21 Feb '23

Hi Telemetry team, we have a release job failure [1], as it seems pypi did not accept the upload of the release [2]. This is probably beccause of a recently added new line in setup.cfg [3]. Can you please try to fix the issue so that we could propose a new release. [1] https://lists.openstack.org/pipermail/release-job-failures/2023-February/00… [2] https://zuul.opendev.org/t/openstack/build/8b0957e7b8af45f99d8412851542492a [3] https://opendev.org/openstack/python-aodhclient/src/branch/master/setup.cfg… Thanks in advance, Előd Illés irc: elodilles @ #openstack-release

4 3

[ironic] This topic describes how to deploy images for the ironic service
by 任亮 20 Feb '23

20 Feb '23

Hi The.kernel and.initramfs images contained in ramdisk are used to use bare metal services. The open source address provides centos ramdisk mirroring.  https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/ https://tarballs.opendev.org/openstack/ironic-python-agent-builder/dib/file… I want to build our own ramdisk mirror, and I would like to ask whether there is a way to manually make ramdisk mirror. If so, how to add the ironic python agent service to it? Or use the ironic-python-agent-builder tool to support other system construction methods. 发自我的企业微信

4 4

[ironic][release] Dmitry no longer release liason
by Jay Faulkner 20 Feb '23

20 Feb '23

Hey all, Dmitry has gotten busier as our secret agent in the CNCF working on Metal3.io -- we're lightening his load on this side by dropping him as a release liaison for Ironic at his request. Riccardo and Iury will remain as release liaisons for Ironic. This email is being sent for transparency purposes. We'll obviously welcome Dmitry to rejoin as a liaison when and if his time allows. Thanks for the help keeping on top of releases the last few years! -Jay Faulkner

1 0

*[cinder] Request for Feature Freeze Exception*
by 河合敦史 / KAWAI，ATSUSHI 20 Feb '23

20 Feb '23

Hi Team, I'd like to request FFE for following patch: *Hitachi: support data deduplication and compression* Patch: https://review.opendev.org/c/openstack/cinder/+/850831 Status: Fix merge conflict and add unit test Why missed the deadline is merge conflict when it occurred at the deadline day. I'll upload this patch, which is rebased and fixed unresolved review comment, by Feb 21st. This feature is useful for capacity saving, and is isolated to the Hitachi driver module, and have no impact on the Cinder database, REST/RPC and APIs. Best regards, Atsushi Kawai

2 1

[neutron] Bug Deputy Report February 13 - 19
by Yatin Karel 20 Feb '23

20 Feb '23

Hello Neutron Team !! Please find bug report from February 13th to 19th, Undecided bugs needs further triage:- *Critical:-* - https://bugs.launchpad.net/neutron/+bug/2007152 - Race condition in DHCP agent cause deletion of the dhcp port as stale port Assigned to slawek - https://bugs.launchpad.net/neutron/+bug/2007254 - [UT] "test_create_ndp_proxy_with_duplicated" fail Fixed with https://review.opendev.org/q/I2fcad691df4a7ae112e1d55fefe662016430aa5b Aassigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2007166 - [tempest] CI job "neutron-ovn-tempest-ipv6-only-ovs-release" unstable, most of the times because of "test_hotplug_nic" Fix proposed https://review.opendev.org/c/openstack/neutron/+/874112 Assigned to yatin - https://bugs.launchpad.net/neutron/+bug/2007565 - [tempest] "test_network_basic_ops" failing randomly Fix proposed https://review.opendev.org/c/openstack/neutron/+/874112 Assigned to ralonsoh *High:-* - https://bugs.launchpad.net/neutron/+bug/2007357 - Grenade jobs failing due to failed ping to the test instance Unassigned - https://bugs.launchpad.net/neutron/+bug/2007553 - [DHCP] TypeError: disable() got an unexpected keyword argument 'network_id' Fix proposed https://review.opendev.org/c/openstack/neutron/+/874073 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2007353 - Functional test neutron.tests.functional.services.ovn_l3.test_plugin.TestRouter.test_gateway_chassis_rebalance fails intermittently Unassigned *Medium:-* - https://bugs.launchpad.net/neutron/+bug/2007327 - Don't send rpc messages about security groups Fix proposed https://review.opendev.org/c/openstack/neutron/+/873850 Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1934666 - IPv6 not set on VMs when using DVR HA + SLAAC/SLAAC (or DHCPv6 stateless) Reopened based on discussion on https://review.opendev.org/c/openstack/neutron/+/869741 *Low:-* - https://bugs.launchpad.net/neutron/+bug/2007414 - [RBAC] "RULE_ADMIN_OR_NET_OWNER_OR_ADVSVC" rule not used any more (Neutron and n-lib) Unassigned *Undecided:-* - https://bugs.launchpad.net/neutron/+bug/2007167 - OVN DHCP replies source from subnet gateway IP Possible Invalid from Neutron perspective, discussion Ongoing - https://bugs.launchpad.net/nova/+bug/2006467 - tempest ssh timeout due to udhcpc fails in the cirros guest Need to root cause it, discussion Ongoing - https://bugs.launchpad.net/neutron/+bug/2007674 - Neutron creates too many connections to rabbitmq Requested more info Thanks and Regards Yatin Karel

1 0

[cinder] Feature freeze in effect
by Rajat Dhasmana 20 Feb '23

20 Feb '23

Hello Argonauts, We are past the feature freeze deadline i.e. 17 Feb, 2023[1]. If you have a feature which you would like to get it into the 2023.1 (Antelope) release, please request a feature freeze exception on the OpenStack discuss mailing list with the following subject: *[cinder] Request for Feature Freeze Exception* Include the patch details, reason for missing the feature freeze deadline and current status in the email. The feature freeze exception will be granted for 1 week i.e. till 24th Feb, 2023 and no features will be accepted after that. Following are the targeted features and their current status: *Hitachi: support data deduplication and compression* Patch: https://review.opendev.org/c/openstack/cinder/+/850831 Status: Fix merge conflict and add unit test *Add iSCSI export support to the StorPool driver* Patch: https://review.opendev.org/c/openstack/cinder/+/847536 Status: Has multiple negative votes with feedback that needs to be addressed *[SVf] Adding support of clone operation for volumegroup* Patch: https://review.opendev.org/c/openstack/cinder/+/871257 Status: Has negative votes with feedback that needs to be addressed *LVM NVMe Target* Topic: https://review.opendev.org/q/topic:lvm-nvmet-shared Status: Need confirmation that the patches are in a reviewable state [1] https://releases.openstack.org/antelope/schedule.html#a-ff Thanks Rajat Dhasmana

2 2

[oslo][OpenStackSDK][heat][keystone][Telemetry][ironic][freezer][senlin][monasca][murano][vitrage][solum][magnum][winstackers][blazar] broken gate on master branch
by Elõd Illés 20 Feb '23

20 Feb '23

Hi $teams_in_subject, I've generated dummy patches to see gate health (to projects' for cycle-with-intermediary deliverables, that have not merged any patches in this year yet) and the patches shows that you have broken CI jobs on your gate. Could the teams please check what the issue / issues are and fix as soon as possible? Thanks in advance! (Note: most of the failures have probably been introduced with tox version 4 release and should be straightforward to fix) Thanks, Előd Illés irc: elodilles @ #openstack-release

4 4

Can't access terminal on website
by vincent lee 20 Feb '23

20 Feb '23

Hi all, I have deployed OpenStack on my system (all with Ubuntu 20.04 Desktop versions) using kolla-ansible deployment. I am able to launch containers and open the terminal (console of containers) in the web-browser from the horizon dashboard. However, when I installed an OpenStack on my system using *Ubuntu 20.04 Server* version using kolla-ansible deployment, all containers were running, but I was not able to access the terminal in the web-browser on the horizon dashboard for the running container. I am getting an error message "*Firefox can't establish a connection to the server at wss://...*" All my OpenStack is deployed using the Python virtual environment. I have been following the exact steps in deploying OpenStack from "https://docs.openstack.org/kolla-ansible/yoga/user/quickstart.html." My current OpenStack version is yoga. Apart from that, I would like to ask if there is any specific path I can make modifications on my OpenStack. Every time when I deployed a fresh OpenStack on my system and tried to make some modifications, the path might not take any effect on the horizon dashboard. Sometimes, modifying the library in /var/lib/kolla/venv/lib/python3.8/site-packages/openstack_dashboard and restarting horizon updates the modification. Sometimes, it might be in /horizon-source/.../openstack_dashboard/. Thank you, Vincent

1 0

[kolla-ansible] Upgrade roadmap
by Nguyễn Hữu Khôi 19 Feb '23

19 Feb '23

Hello guys. I have questions: - Can we upgrade version skipping such as Wallaby to Zed OR Wallaby >> Xena >> Yoga >> Zed? - Is there any way to upgrade Openstack to a new version without host upgrade? Imaging that We have 1000 nodes as a Train version then we need to upgrade to Zed, it is too hard, - Is there any plan to upgrade Xena(Ubuntu 20.04) to Zed(20.04). Thank you. Regards Nguyen Huu Khoi

2 7

Issue on Volume Attach/Detach/Delete in openstack
by sudeb ghosh 19 Feb '23

19 Feb '23

Hi Team, we are using opensource Openstack (Openstack foundation) in our environment. Facing following issues to fix. Need some guidance or suggestion to resolve the same. Problem Detail: 1. We are struggling to delete the volume which are in 'available' state. After deleting from Dashboard/CLI its showing 'deleting' only. 2. Can not detach the volume from any instance. Showing 'detaching' itself. 3. Once status of volume made available by updating table of Database, the volumes are showing 'available' but could not attach further with any existing instance. 4. Once status of volume made deleted by updating table of Database or by deleting the entries of table the volumes are showing status as 'deleted' in CLI(mysql query) & disappeared from Dashboard but reclaiming of space is not happening in storage or quota point of view. Request your guidance with steps to fix the issue pl. BR// Sudeb Ghosh 7044064878 9332034788

2 1

[cinder]Improve Cinder backup
by Nguyễn Hữu Khôi 19 Feb '23

19 Feb '23

Hello guys. I want to show Cinder backup pool stats such as size, I search google but there is no cli to achieve this task. One more thing, we also need a progress bar when backup volume. It is a useful feature for users who want to track their backup tasks. Thank you. Regards Nguyen Huu Khoi

1 0

[all][tc] What's happening in Technical Committee: summary 2023 Feb 17: Reading: 5 min
by Ghanshyam Mann 18 Feb '23

18 Feb '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Feb 15. Most of the meeting discussions are summarized in this email. The meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-15-16.00.log.html * The next TC weekly meeting will be on Feb 22 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 21. 2. What we completed this week: ========================= * Guidelines for using the OpenStack/project release version/name in 1. releasenotes 2. Documentation[2] * Retire repo from the Governance repo - Retire xstatic-font-awesome[3] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[4]. Open Reviews ----------------- * Seven open reviews for ongoing activities[5]. Deprecation process for TripleO -------------------------------------- You might have seen the ML discussion for TripleO deprecation[6]. TripelO release model is a little different where they do have stable branches till stable/wallaby and after that, it was an independent release. But in the independent release model also, stable/zed branch was cut. With the TripleO deprecation, the team can maintain only till stable/wallaby. This makes the situation a little difficult where we do not have the best possible way to deprecate/retire stable/zed. TC discussed it but could not find any suitable options other than maintaining the stable/zed also. James will be checking this option with TripleO team and updating the ML thread. Election updates -------------------- Technical election nomination for the next cycle has been closed[7]. Even though there is no poll required in PTL as well as in TC elections, the TC campaigning is going on[8] where you can ask question to the TC candidates. Defining 2023 upstream investment opportunities ------------------------------------------------------------ Every calendar year, TC defines the upstream investment opportunities where we need help and the organization can help. I have pushed the patch[9] to define the 2023 calendar year, which is continuing last year's opportunities. Please let TC know if any of the areas/projects you think need help and should be added to this list. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The audit process is going on and a few projects have been completed [10]. There is a discussion also going on in ML[11]. JayF is working on an email template which can be used to communicate to additional developers to transfer the ownership to 'openstackci' account and remove them from the maintainer's list. The process to find the less active projects early in the cycle: ------------------------------------------------------------------------ No update this week. JayF started the etherpad to collect the data and define the criteria to help in this process[12]. Project updates ------------------- * Add Cinder Huawei charm[13] * Add the woodpecker charm to Openstack charms[14] * Retire xstatic-font-awesome[15] * mistral adopting PTL model[16] * Add xstatic-angular-fileupload as Horizon team deliverables[17] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/872769 [3] https://review.opendev.org/c/openstack/governance/+/872837 [4] https://etherpad.opendev.org/p/tc-2023.1-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… [7] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03224… [8] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03224… [9] https://review.opendev.org/c/openstack/governance/+/872233 [10] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [11] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [12] https://etherpad.opendev.org/p/project-health-check [13] https://review.opendev.org/c/openstack/governance/+/867588 [14] https://review.opendev.org/c/openstack/governance/+/869752 [15] https://review.opendev.org/c/openstack/governance/+/872837 [16] https://review.opendev.org/c/openstack/governance/+/873260 [17] https://review.opendev.org/c/openstack/governance/+/873845 [18] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Ceph outage cause filesystem error on VM
by Satish Patel 18 Feb '23

18 Feb '23

Folks, I am running a small 3 node compute/controller with 3 node ceph storage in my lab. Yesterday, because of a power outage all my nodes went down. After reboot of all nodes ceph seems to show good health and no error (in ceph -s). When I started using the existing VM I noticed the following errors. Seems like data loss. This is a lab machine and has zero activity on vms but still loses data and the file system corrupt. Is this normal ? I am not using eraser coding, does that help in this matter? blk_update_request: I/O error, dev sda, sector 233000 op 0x1: (WRITE) flags 0x800 phys_seg 8 prio class 0

5 14

Fedora 37 image for Openstack Magnum
by sri ramu 18 Feb '23

18 Feb '23

Hi Team, I am testing the Openstack magnum ussuri version. However, to launch a magnum K8s cluster I am using Fedora32 as the backend image . As everyone is aware this fedora32 image has no support. So I have planned to deploy with fedora37 but their Heat agent was not running properly. Need your help to run the heat agent in fedora37. Regards, Sriramu Desing

2 1

[manila] Feature freeze exceptions
by Carlos Silva 17 Feb '23

17 Feb '23

Hello, Zorillas and interested stackers! As discussed in yesterday's Manila weekly meeting, some features we are targeting for Antelope will need some extra time to be merged due to a shortage of reviewers we had in the cycle. These changes have been under review and we believe they are close to being merged. The changes we will need more time to merge are: *Metadata for share network subnets:* Reviews ongoing [1]. Change was proposed in time during the cycle, has received a couple of reviews and authors have been responsive. There is also a small third party driver modification being proposed alongside [2]. Both seem close to being merged. Client change did not make it to the release and will be merged earlier in the next cycle. *NetApp ONTAP REST API transition:* NetApp contributors are pursuing an implementation that will allow them to transition from ZAPI to REST [3]. This is a huge change as they need to rewrite things to be compatible with their ONTAP REST API. The changes have been proposed in time, authors have been providing test results and reviewers have been providing feedback. We had a collaborative review earlier this week where they walked us through the changes [4]. We are extending the feature freeze deadline until next Thursday (Feb 23rd) for these changes. [1] https://review.opendev.org/c/openstack/manila/+/869707/ [2] https://review.opendev.org/c/openstack/manila/+/869708/ [3] https://etherpad.opendev.org/p/collab-review-manila-netapp-rest-api [4] https://www.youtube.com/watch?v=zCOm_g7HGWU Regards, carloss

1 0

[keystone] Feature freeze exceptions
by Hiromu Asahina 17 Feb '23

17 Feb '23

Hi All, As discussed in the reviewathon today, due to the shortage of review bandwidth, we are planning to extend the feature freeze for the changes related to mTLS OAuth2.0. Current feature freeze date (for keystone): 17 February 2023 New feature freeze date (for keystone): 24 February 2023 Kindly let me know if there are any objections to the above proposal else the changes related to topic:bp/support-oauth2-mtls [1] are eligible for the feature freeze exception of 1 week. [1] https://review.opendev.org/q/topic:bp%252Fsupport-oauth2-mtls Thanks, Hiromu Asahina

1 0

[release] Release countdown for week R-4, Feb 20-24
by Elõd Illés 17 Feb '23

17 Feb '23

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the 2023.1 Antelope deliverables can be proposed, well ahead of the final 2023.1 Antelope release date. General Information ------------------- We are still finishing up processing a few release requests, but the 2023.1 Antelope release requirements are now frozen. If new library releases are needed to fix release-critical bugs in 2023.1 Antelope, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in 2023.1 Antelope that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By March 2nd, 2023 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/2023.1 branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for 2023.1 Antelope changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed 2023.1 Antelope cycle-highlights yet, then you are encouraged to do so as deadline is February 23rd, 2023. A separate email will be sent early next week. Upcoming Deadlines & Dates -------------------------- Cycle Highlights Due: February 23rd, 2023 (R-4 week) RC1 deadline: March 2nd, 2023 (R-3 week) Final RC deadline: March 16th, 2023 (R-1 week) Final 2023.1 Antelope release: March 22nd, 2023 2023.2 Bobcat Virtual PTG: March 27-31, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[elections][Cinder] PTL Candidacy for 2023.2 (Bobcat)
by Rajat Dhasmana 17 Feb '23

17 Feb '23

Hi All, I would like to nominate myself to be Cinder PTL during the 2023.2 (Bobcat) cycle. I have been serving as the PTL for the last two cycles i.e. Zed and 2023.1 (Antelope) and there were a lot of key areas which we were able to improve as follows: ** Review bandwidth and quality:* Cinder's policy of "Do reviews to get reviews" has helped improve the review bandwidth and we have seen more participation and activity in code reviews. We have also added efficient review guidelines[1] to help new contributors onboard to the review process quickly and help them do quality reviews. ** cinderclient to openstackclient migration:* We are working towards reducing the parity between cinderclient and openstackclient and the effort can be tracked with this topic[2]. Currently we have proposed all the commands that were missing in openstackclient. ** Third party CI to report on os-brick changes: *The third party vendor CI's used to report only on cinder gate and not on os-brick gate which means their driver wasn't tested with the connector and they could only see issues when the os-brick release happens. Unfortunately, the driver merge deadline is milestone-2 and os-brick (non-client library) release is 1 week before feature freeze so it doesn't give enough time for driver maintainers to fix the issues. Reporting the CI on os-brick gate helps identify issues earlier and fix them timely. ** Security Vulnerabilities:* We went through the open security issues in Zed and triaged their priority and importance. A new security issue was reported in 2023.1 regarding VMDK file format for which a CVE has been filed, CVE-2022-47951 [3]. We have addressed the issue and releases were done for the actively maintained stable branches i.e. Zed[1], Yoga[2] and Xena[3]. Apart from that, we were able to handle deadlines better by managing and prioritizing work based on the milestones. Following are the plans for the 2023.2 cycle: * our first target will be to move away from adding additional commands to cinderclient and only rely on openstackclient for the CLI interface. Also we will explore openstacksdk to add support for cinder commands so we can break the dependency on the python bindings that exist in cinderclient. * Another thing to address is adding the service role after the keystone implements it[7]. * Third party drivers are the core of cinder that allows cinder to what the end users desire i.e. to interface between users and storage backends. We will focus to improve the experience of driver vendors to implement new drivers by improving our driver documentation and test stability by doing a 3rd party CI compliance check. We have been making progress in this area but more efforts are required that we will target for the next cycle. Finally will try to continue all the good things we have started that keeps the project healthy and active and also address new gaps discovered along the way. [1] https://docs.openstack.org/cinder/latest/contributor/gerrit.html#efficient-… [2] https://review.opendev.org/q/topic:add-missing-cinderclient-commands [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-47951 [4] https://pypi.org/project/cinder/21.1.0 [5] https://pypi.org/project/cinder/20.1.0 [6] https://pypi.org/project/cinder/19.2.0 [7] https://review.opendev.org/c/openstack/keystone/+/863420 - Rajat Dhasmana

2 1

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

17 Feb '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

Answer questions about 'OpenInfra Live - VGPU Management by OpenStack Nova and Cyborg'
by Alex Song (宋文平) 17 Feb '23

17 Feb '23

Hi everyone, The Episode of VGPU Management by OpenStack Nova and Cyborg has completed. Below is the answer of questions: Q:Does Cyborg do the MIG configuration or is that done manually outside OpenStack? A: We can configure MIG by cyborg-api, we list the MIG split combinations on the page for user to set. Cyborg-agent only need configure the driver of nvidia_mig_driver. In the driver, we automatic discover the vgpu_types and PCI addresses and set default vgpu_types. Q:Do l get it right that we need at least Ussuri on the hosts for Nova ? A: Yeah, from Ussuri we complete the interaction with Nova and Cyborg. If you use old Nova version, you can cherry pick the Cyborg part code. Q:does cyborg also help with SRIOV netork with MIG and passthrough hosts? A: Firstly, Cyborg has supported manage SmartNIC SRIOV network. Secondly, MIG and vGPU only support passthrough hosts in OpenStack nowadays, GPUDirect need RDMA communication. Thanks, Alex

1 0

[election][keystone] PTL candidacy for 2023.2 (Bobcat)
by Dave Wilde 16 Feb '23

16 Feb '23

Hello, I would like to nominate myself to be Keystone PTL for the 2023.2 (Bobcat) cycle. This will be my second cycle serving as PTL and I am looking forward to continuing the progress that we're making in Keystone. Some of the highlights of the last cycle that I would like to continue and build upon are: *Reviewathons*: We have been holding weekly reviewathons that I feel have been quite successful. We meet on Fridays (ping me if you'd like an invite) in an informal hour long GMeet room and either go down the list of pending reviews or if there is a specific topic/feature we might focus on that. The reviewathons have helped in significantly reducing our backlog of easily merged, maintenance type patches and have given us a very good opportunity to discuss in detail a very complicated feature. I would like to continue the reviewathons and extend an invitation to anyone who would like to join. *Weekly Meetings*: The weekly meetings are happening regularly and are fostering good discussion and information sharing. The weekly meetings are currently scheduled for Tuesdays at 15:00 UTC but I am always open to changing the day and time if it will garner more participation. *Bug Cleanup*: Keystone proper has over two hundred bugs and the other Identity projects probably contribute another one hundred, this is too many. I have been slowly going through and trying to close out old and irrelevant bugs as well as triage those that need fixing (my apologies for the emails about bugs that are years old :). I would like to continue this work and get our bug backlog into a manageable state. I've enjoyed my first cycle as PTL and with your continued support am looking forward to another cycle. Thanks for your consideration. /Dave

2 1

[cinder] festival of feature reviews 17th February 2023
by Rajat Dhasmana 16 Feb '23

16 Feb '23

Hello Argonauts, We will be having our monthly festival of reviews tomorrow i.e. 17th February (Friday) from 1400-1600 UTC. This time we are planning to review features instead of XS patches since we have feature freeze this week. Following are some additional details: Date: 17th February, 2023 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! Thanks Rajat Dhasmana

1 0

[horizon][kolla] xstatic libraries and setuptools 67.3.1
by Michał Nasiadka 16 Feb '23

16 Feb '23

Hello, Recently setuptools 67.3.1 has been released, and it broke Kolla Horizon container builds. It seems that xstatic libraries rely on setuptools importing pkg_resources during build, which does not work in latest setuptools [1]. I raised a horizon bug #2007574 (https://bugs.launchpad.net/horizon/+bug/2007574) Raising awareness on the ML, because maybe that affects more projects than only Horizon. We’ve pinned to 67.2.0 in Kolla for now (in master and stable/zed, because earlier branches have a pin from u-c) [1]: https://github.com/pypa/setuptools/issues/3824 Michal Nasiadka

1 0