August 2022 - openstack-discuss - lists.openstack.org

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 1

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

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

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

24 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

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

[charms] Team Delegation proposal
by Chris MacNaughton 09 Feb '23

09 Feb '23

Hello All, <tl;dr> I would like to propose some new ACLs in Gerrit for the openstack-charms project: - openstack-core-charms - ceph-charms - network-charms - stable-maintenance </tl;dr> With an increasing focus split among the openstack-charmers team, I'm observing that people are focused on more specific subsets of the charms, and would like to propose that new ACLs are created to allow us to recognize that officially. I've chosen the breakdown above as it aligns neatly with where the focus lines are at this point, letting developers work on their specific focus areas. This proposal would not reduce permissions for anybody who is currently a core on the openstack-charms project and, in fact, future subteam core members could aspire to full openstack-charmers core as well. Ideally, this approach will let us escalate developers to "core" developers for the subteam(s) where they have demonstrated the expertise we expect in a core-charmer. It also allows a more gradual escalation to being a core in the openstack-charms project, making it a progression rather than a single destination. As a related addition, I'm appending to this proposal the creation of a stable-maintenance ACL which would allow members to manage backports without a full core-charmer grant. --- Chris MacNaughton

5 7

[cinder][drivers] third-party CI for os-brick changes
by Brian Rosmaita 04 Jan '23

04 Jan '23

To all third-party CI maintainers, As you are aware, cinder third-party CI systems are required to run on all cinder changes. However, the os-brick library used in cinder CI testing is the latest appropriate *released* version of os-brick. Thus, it is possible for changes to be happening in os-brick development that might impact the functionality of your driver. If you aren't testing os-brick changes, you won't find out about these until *after* the next os-brick release, which is bad news all around. Therefore, at last week's cinder midcycle [0], the cinder project team agreed to require that cinder third-party CI systems run on all os-brick changes in addition to all cinder changes. This is a nice-to-have for the current (Zed) development cycle, but will be required in order for a driver to be considered 'supported' in the 2023.1 (Antelope) release [1]. If you have comments or concerns about this policy, please reply on the list to this email or put an item on the agenda [2] for the cinder weekly meeting. [0] https://etherpad.opendev.org/p/cinder-zed-midcycles [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_changes… [2] https://etherpad.opendev.org/p/cinder-zed-meetings

2 1

Glance api deployed only on a single controller on multi-controller deployment [kolla]
by A Monster 31 Dec '22

31 Dec '22

I've deployed openstack xena using kolla ansible on a centos 8 stream cluster, using two controller nodes, however I found out after the deployment that glance api is not available in one node, I tried redeploying but I got the same behavior, although the deployment finished without displaying any error. Thank you. Regards

4 4

[all][TC] Bare rechecks stats week of 25.07
by Slawek Kaplonski 17 Dec '22

17 Dec '22

Hi, Here are fresh data about bare rechecks. +--------------------+---------------+--------------+-------------------+ | Team | Bare rechecks | All Rechecks | Bare rechecks [%] | +--------------------+---------------+--------------+-------------------+ | requirements | 2 | 2 | 100.0 | | keystone | 1 | 1 | 100.0 | | OpenStackSDK | 3 | 3 | 100.0 | | tacker | 3 | 3 | 100.0 | | freezer | 1 | 1 | 100.0 | | rally | 1 | 1 | 100.0 | | OpenStack-Helm | 14 | 15 | 93.33 | | cinder | 6 | 7 | 85.71 | | kolla | 20 | 25 | 80.0 | | neutron | 4 | 5 | 80.0 | | Puppet OpenStack | 10 | 13 | 76.92 | | OpenStack Charms | 3 | 6 | 50.0 | | nova | 11 | 22 | 50.0 | | tripleo | 8 | 19 | 42.11 | | ironic | 1 | 3 | 33.33 | | Quality Assurance | 1 | 3 | 33.33 | | octavia | 0 | 1 | 0.0 | | OpenStackAnsible | 0 | 1 | 0.0 | | designate | 0 | 1 | 0.0 | | Release Management | 0 | 1 | 0.0 | | horizon | 0 | 1 | 0.0 | +--------------------+---------------+--------------+-------------------+ Those data should be more accurate as my script now counts only comments from last 7 days, not all comments from patches updated in last 7 days. Reminder: "bare rechecks" are recheck comments without any reason given. If You need to do recheck for patch due to failed job(s), please first check such failed job and try to identify what was the issue there. Maybe there is already opened bug for that or maybe You can open new one and add it as explanation in the recheck comment. Or maybe it was some infra issue, in such case short explanation in the comment would also be enough. -- Slawek Kaplonski Principal Software Engineer Red Hat

6 10

[neutron] Switching the ML2 driver in-place from linuxbridge to OVN for an existing Cloud
by Christian Rohmann 26 Nov '22

26 Nov '22

Hello openstack-discuss and neutron experts, I'd like to ask for your input and discussion on the idea of changing the ML2 driver for an existing cloud, read: changing a tire while still riding the bike. I actually like to find out if it's feasible to switch from the trusted Linuxbridge driver to the more modern SDN stack of OVN - in place. With all existing user networks, subnets, security groups and (running) instances in the database already. And while I know there a push of migrating from OVS to OVN and a clear migration path documented (https://docs.openstack.org/neutron/latest/ovn/migration.html) but they are much more similar in their data plane. And to get this out of the way: I am not asking to do be able to do this without downtime, interruptions, migrations or any active orchestration of the process. I just want to know all the possible options apart from setting up a new cloud and asking folks to migrate all of their things over... 1) Are the data models of the user managed resources abstract (enough) from the ML2 used? So would the composition of a router, a network, some subnets, a few security group and a few instances in a project just result in a different instantiation of packet handling components, but be otherwise transparent to the user? 2) What could be possible migration strategies? While it might be a little early to think about the actual migration steps. But just to consider more than a full cloud shutdown following a cold start with modified neutron config then using the OVN ML2. I know there is more than just the network and getting a virtual layer 2 network. There are DHCP, DNS and the metadata service and last but not least the gateway / router and the security groups. But if using VXLAN for OVN (as Linuxbridge uses currently) could the shift from one implementation to the other potentially be done node by node? Or project by project by changing the network agents over to nodes already running OVN? If not, is there any other hot cut-over approach that would avoid having to shutdown all the instances, but only cause them some network downtime (until the next DHCP renew or similar?) Has anybody ever done something similar or heard about this being done anywhere? Thanks for your time and input, Christian

3 5

[designate] How to avoid NXDOMAIN or stale data during cold start of a (new) machine
by Christian Rohmann 23 Nov '22

23 Nov '22

Hello openstack-discuss, I have a designate setup using bind9 as the user-serving DNS server. When starting a machine with either very old or no zones at all, NXDOMAIN or other actually stale data is sent out to clients as designate is not done doing an initial full sync / reconciliation. * What is the "proper" way to tackle this cold-start issue and to keep the bind from serving wrong data? ** Did I miss on any options to handle this startup case? * What is the usual runtime for an initial sync that you observe in case the backend DNS server has no zones at all anymore? Regards Christian

2 7

Zun connector for persistent shared files system Manila
by Vaibhav 13 Nov '22

13 Nov '22

Hi, I am using zun for running containers and managing them. I deployed cinder also persistent storage. and it is working fine. I want to mount my Manila shares to be mounted on containers managed by Zun. I can see a Fuxi project and driver for this but it is discontinued now. With Cinder only one container can use the storage volume at a time. If I want to have a shared file system to be mounted on multiple containers simultaneously, it is not possible with cinder. Is there any alternative to Fuxi. is there any other mechanism to use docker Volume support for NFS as shown in the link below? https://docs.docker.com/storage/volumes/ Please advise and give a suggestion. Regards, Vaibhav

2 4

[all][tc] 2023.1 Antelope TC-PTG Planning
by Ghanshyam Mann 20 Oct '22

20 Oct '22

Hello Everyone, As you already know that the 2023.1 cycle virtual PTG will be held between Oct 17th - 21[1]. I have started the preparation for the Technical Committee PTG sessions. Please do the following: 1. Fill the below poll as per your availability. - https://framadate.org/yi8LNQaph5wrirks 2. Add the topics you would like to discuss to the below etherpad. - https://etherpad.opendev.org/p/tc-2023-1-ptg NOTE: this is not limited to TC members only; I would like all community members to fill the doodle poll and, add the topics you would like or want TC members to discuss in PTG. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030041.… -gmann

2 4

[Ceilometer] Pollster cannot get RadosGW metrics when API endpoints are based on URL instead of port number
by Taltavull Jean-François 10 Oct '22

10 Oct '22

Hi All, In our OpenStack deployment, API endpoints are defined by using URLs instead of port numbers and HAProxy forwards requests to the right bakend after having ACLed the URL. In the case of our object-store service, based on RadosGW, the internal API endpoint is "https://<FQDN>/object-store/swift/v1/AUTH_<tenant_id>" When Ceilometer RadosGW pollster tries to connect to the RadosGW admin API with the object-store internal endpoint, the URL becomes https://<FQDN>/admin, as shown by HAProxy logs. This URL does not match any API endpoint from HAProxy point of view. The line of code that rewrites the URL is this one: https://opendev.org/openstack/ceilometer/src/branch/stable/wallaby/ceilomet… What would you think of adding a mechanism based on new Ceilometer configuration option(s) to control the URL rewriting ? Our deployment characteristics: - OpenStack release: Wallaby - Ceph and RadosGW version: 15.2.16 - deployment tool: OSA 23.2.1 and ceph-ansible Best regards, Jean-Francois

2 23

[ptg][edge]OpenStack at the Edge discussions
by Ildiko Vancsa 26 Sep '22

26 Sep '22

Hi, I’m reaching out to you in preparation to the upcoming PTG. The Edge Computing Group already started to prepare for the event and OpenStack came up during our conversations to have cross-project discussions with. The number of edge computing use cases in production is growing and OpenStack is a key infrastructure building block. Some edge related discussions regarding the project came up at previous PTGs and it would be great to continue and extend them. We covered areas in networking and looked into storage a little bit, and the question of finding a central place to store edge related documentation also came up. To identify new topics and follow up on ones we already started to discuss I added an OpenStack section to the Edge WG’s planning etherpad: https://etherpad.opendev.org/p/ecg-ptg-october-2022 If you are working on related features, have requirements or case studies to share, please add them to the above etherpad, so we can discuss them at the PTG and identify areas we can work together on to solve challenges and share information about exiting solutions. Please let me know if you have any questions or comments. Thanks, Ildikó

1 1

Cinder-volume active active setup
by Eugen Block 22 Sep '22

22 Sep '22

Hi, I didn't mean to hijack the other thread so I'll start a new one. There are some pages I found incl. Gorkas article [1], but I don't really understand yet how to configure it. We don't use any of the automated deployments (we created our own) like TripleO etc., is there any guide showing how to setup cinder-volume active/active? I see in my lab environment that python3-tooz is already installed on the control node, but how do I use it? Besides the "cluster" config option in the cinder.conf (is that defined when setting up the DLM?) what else is required? I also found this thread [2] pointing to the source code, but that doesn't really help me at this point. Any pointers to a how-to or deployment guide would be highly appreciated! Thanks, Eugen [1] https://gorka.eguileor.com/a-cinder-road-to-activeactive-ha/ [2] https://www.mail-archive.com/openstack@lists.openstack.org/msg18385.html

2 5

[all] Deprecated Zuul queue syntax
by Clark Boylan 16 Sep '22

16 Sep '22

Hello, Zuul deprecated declaring shared queues at a pipeline level with release 4.1.0 [0]. Zuul's current plan is to stop accepting this form of configuration with a future 7.0.0 release. More details on what needs to change can be found in Zuul's reminder notice on the Zuul mailing list [1]. I expect we have about a month before the v7 release which should give us plenty of time to fix this. If we don't fix this before the v7 release the expected fallout will be that these project branches will not have any pipelines defined, which means no Zuul jobs will run against that project branch until the configs are updated. I've marked this for everyone because 98 repositories are affected, and I'm not sure listing them all in the subject would be productive. Here is the list of affected repos: openstack/adjutant openstack/ansible-collection-kolla openstack/ansible-role-collect-logs openstack/ansible-role-tripleo-modify-image openstack/barbican openstack/barbican-tempest-plugin openstack/barbican-ui openstack/blazar openstack/blazar-tempest-plugin openstack/ceilometer openstack/cinderlib openstack/cloudkitty openstack/cloudkitty-tempest-plugin openstack/cyborg-tempest-plugin openstack/designate openstack/designate-dashboard openstack/designate-tempest-plugin openstack/devstack-gate openstack/ec2-api openstack/ec2api-tempest-plugin openstack/freezer openstack/freezer-tempest-plugin openstack/heat openstack/heat-dashboard openstack/heat-tempest-plugin openstack/horizon openstack/ironic openstack/ironic-inspector openstack/ironic-lib openstack/ironic-prometheus-exporter openstack/ironic-python-agent openstack/ironic-tempest-plugin openstack/kayobe openstack/kayobe-config openstack/kayobe-config-dev openstack/kolla openstack/kolla-ansible openstack/kuryr openstack/magnum openstack/magnum-tempest-plugin openstack/manila openstack/manila-tempest-plugin openstack/masakari openstack/masakari-monitors openstack/mistral openstack/mistral-tempest-plugin openstack/monasca-api openstack/monasca-common openstack/monasca-events-api openstack/monasca-log-api openstack/monasca-tempest-plugin openstack/murano openstack/murano-tempest-plugin openstack/networking-generic-switch openstack/octavia openstack/octavia-tempest-plugin openstack/openstack-chef openstack/os-net-config openstack/os-win openstack/oswin-tempest-plugin openstack/paunch openstack/project-config openstack/puppet-pacemaker openstack/puppet-tripleo openstack/python-designateclient openstack/python-ironicclient openstack/python-saharaclient openstack/python-tripleoclient openstack/python-troveclient openstack/sahara openstack/sahara-tests openstack/senlin openstack/senlin-tempest-plugin openstack/solum openstack/solum-tempest-plugin openstack/telemetry-tempest-plugin openstack/tenks openstack/tripleo-ci openstack/tripleo-ci-health-queries openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-quickstart openstack/tripleo-quickstart-extras openstack/tripleo-upgrade openstack/trove openstack/trove-tempest-plugin openstack/vitrage openstack/vitrage-tempest-plugin openstack/watcher openstack/watcher-tempest-plugin openstack/zaqar openstack/zaqar-tempest-plugin openstack/zun openstack/zun-tempest-plugin windmill/windmill windmill/windmill-backup x/neutron-classifier x/vmware-nsx I'll go ahead and push changes to windmill/* and x/* as those are leftovers from splitting things up into tenants and haven't ended up in their own tenants yet. But it would be great if OpenStack can work on cleaning up this deprecated syntax in the OpenStack repos. I've attached a file with a listing that includes more details for each repo (branches and specific config files) to make it easier for people to find where the old syntax is located so that it can be replaced with the new syntax. [0] https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-depre… [1] https://lists.zuul-ci.org/pipermail/zuul-discuss/2022-May/001801.html

2 2

[ironic] Ilya Etingof Passed Away
by Iury Gregory 15 Sep '22

15 Sep '22

With a heavy heart, I am sorry to announce that after a long struggle with an illness, Ilya Etingof (etingof on IRC) passed away on Wednesday, 10th August, 2022. He is survived by his mother and two daughters. Born in Russia, Ilya had moved to Czechia and in 2015 joined Red Hat. In 2017, Ilya started contributing to the Ironic project. He was the lead contributor to the Sushy project, Sushy Redfish emulator, an important contributor to Ironic and worked tirelessly to make hardware management reliable and consistent. His important contributions included boot management, out-of-band hardware inspection and virtual media boot. Outside of the OpenStack community, he has maintained Python packages with a particular focus on SNMP. For example: pysnmp, pysmi, pyasn1, softboxen and many others. Ilya was dedicated to helping younger and under-represented people. He used to run a virtualisation technologies course at the Masaryk University in Brno where he spoke about OpenStack and Kubernetes. He was also an active participant in the Outreachy program where he mentored those who contributed to Open Source projects. Goodbye Ilya from the Ironic community, may you rest in peace. -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 1

[all] GovStack community seeking for infrastructure expertise
by Lueck, Nico GIZ 11 Sep '22

11 Sep '22

Do you believe in the potential of digital public goods for positive impact? Ever wished for more digitally-enabled government services? GovStack [1] is a community-driven initiative on a mission to accelerate the digital transformation of government services in order to better serve citizens - and we want you to join us! We create and maintain an openly licenced blueprint for a modular architecture based on reusable building blocks [2]. Our various working groups work to define the (non-)functional and API specifications for building blocks, leveraging existing standards such as OpenStack. These specifications are then used for implementations in our partner countries across the world, to facilitate the delivery of foundational, life-enhancing services. Learn more about the call for contributions here [3]. We are specifically looking for experts with experience in infrastructure and security. The initiative is founded by the German Federal Ministry for Economic Cooperation and Development, Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ), the Ministry of Foreign Affairs of the Republic of Estonia, the International Telecommunication Union (ITU) and the Digital Impact Alliance. Thank you to the team of the Open Infrastructure Foundation for their support. Also, thank you to the whole community and please feel free to directly contact us. Nico (Lueck) <nico.lueck(a)giz.de> [1] https://www.govstack.global/ [2] https://govstack.gitbook.io/ [3] https://www.govstack.global/call-for-expression-of-interest/ ________________________________ Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ) GmbH; Sitz der Gesellschaft Bonn und Eschborn/Registered offices Bonn and Eschborn, Germany; Registergericht/Registered at Amtsgericht Bonn, Germany; Eintragungs-Nr./Registration no. HRB 18384 und/and Amtsgericht Frankfurt am Main, Germany; Eintragungs-Nr./Registration no. HRB 12394; USt-IdNr./VAT ID no. DE 113891176; Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Jochen Flasbarth; Vorstand/Management Board: Tanja Goenner (Vorstandssprecherin/Chair of the Management Board), Ingrid-Gabriela Hoven, Thorsten Schaefer-Guembel

3 2

[DIB][diskimage-builder] Rocky Linux image build method
by Pierre Riteau 07 Sep '22

07 Sep '22

Hello, I am curious about the choice of providing only a rocky-container element in DIB, which works differently to the centos element, which uses cloud images. It makes it hard to produce working images for VMs or bare metal, as various packages that would normally be installed are missing, such as cloud-utils-growpart or openssh-server. See the kickstarts for reference [1] [2]. It seems to also occasionally cause complex failures such as the one that rendered Rocky Linux 8 images unbootable last week [3]. I am guessing this wouldn't have happened had the build been from a cloud image. Would the DIB community be open to also have a rocky element using GenericCloud images, like centos? Thanks, Pierre Riteau (priteau) [1] https://git.rockylinux.org/rocky/kickstarts/-/blob/r8/Rocky-8-Container-Bas… [2] https://git.rockylinux.org/rocky/kickstarts/-/blob/r8/Rocky-8-GenericCloud.… [3] https://review.opendev.org/c/openstack/diskimage-builder/+/851687

6 6

[election][tripleo] PTL Candidacy for Antelope cycle
by Rabi Mishra 06 Sep '22

06 Sep '22

Hi All, I would like to nominate myself for Antelope cycle TripleO PTL. As some of you would know, I have been part of the OpenStack community for a long time and have been a core contributor for TripleO and Heat. I have also served as Heat PTL for Ocata cycle. James has done a great job as PTL for the last few cycles. I would like to take the opportunity to thank him for all his effort and we all would agree that he needs a well deserved break. I am looking forward to take the opportunity to help the community to achieve some of the already planned goals and in-progress workstreams like standalone roles, multi-rhel and other challenges that come along the way. Also, as before, our focus would continue to be on review prioritization, in progress work streams and collaboration on common priorities. Regards, Rabi Mishra

9 8

[manila] LVM shares are unmounted on reboot
by Vaibhav 06 Sep '22

06 Sep '22

Dear All, One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points. I use LVM Driver with DHSS=False. default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila [lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt After the reboot LVMs are there but they are mounted on their respective share location. Any way to solve this and this to be done automatically? Regards, Vaibhav

2 2

[tc][ptl] TC + Community Leaders interaction in 2023.1 Antelope Virtual PTG
by Ghanshyam Mann 03 Sep '22

03 Sep '22

Hello Everyone, We had successful TC+Community leaders interaction sessions in the last couple of PTG, and we will continue the same for 2023.1 cycle PTG also. I have created the poll to select the best suitable time. It will be for two hours (single or two sessions) either on Monday or Tuesday. Please add your preference in the below doodle poll (including TC members): - https://framadate.org/zsOqRxfVcmtjaPBC Also, I have created the below etherpad with the draft agenda, If you as PTL or project representatives or SIG Chair and would like to attend this session, please add your name: - https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 -gmann

1 1

[PTL][release] Zed Cycle Highlights
by Előd Illés 03 Sep '22

03 Sep '22

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].) [1]https://releases.openstack.org/zed/schedule.html [2]https://releases.openstack.org/zed/schedule.html#z-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles

4 6

[heat][elections] PTL Candidacy for Antelope Cycle
by Brendan Shephard 02 Sep '22

02 Sep '22

Hi all, I first wanted to thank Rico for his ongoing commitment to the project over the last cycles. He has provided lots of guidance and help to the Heat project for a long time and his contribution deserves recognition. I am proposing my candidacy for Heat PTL during the Antelope cycle. I have worked with the Heat project for several years both as a user and more recently over the last 2 years as a contributor. I see great potential in the project for our users and look forward to continuing work in order to support features and functionality of the project. Some of my objectives for the next few cycles are: Remove the dependencies on legacy python-*client libraries and instead shift to the openstacksdk client library. While the legacy libraries have served us well, they are starting to show their limitations and the delta in servicibilty will only increase as each project moves towards leveraging the openstacksdk. So this change, while quite extensive will ensure future compatibility with the other OpenStack project teams. Continue ensuring Heat supports the most up-to-date and recent features provided by each project. To ensure Heat is the default and best choice for our users, we need to ensure we are able to leverage the latest available features from the complimentary OpenStack projects. This is an ongoing challenge to stay up-to-date with the changes each cycle and work towards implementing them in Heat. Thank you all for you consideration, and I look forward to the next cycle and continuing to work with you all. Regards, Brendan

3 2

[all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 02 Sep '22

02 Sep '22

Hello everyone, Before continuing on, yes this kind of is a massive effort but it doesn’t have to be, it would be very cool to get a replacement for RabbitMQ as I’m probably not the only one not satisfied with it. I've proposed a very bare POC in [1] but it's long way from being finished, but atleast some basic devstack is passing. NATS [2] is a cloud-native scalable messaging system that supports the one-to-many and pub-sub methods that we can use to implement it as a oslo.messaging driver. This would make OpenStack easier to deploy in a highly available fashion, reduce outages related to RabbitMQ, free up memory and CPU usage by RabbitMQ (it’s insane when using clustering) and embrace a more cloud-native approach for our software that runs the cloud, alternatives is also welcome :) The POC has a lot of things that could be improved for example: • Do retries and acknowledgements in the library (since NATS does NOT persist messages like RabbitMQ could) • Handle reconnects or interruptions (for example resubscribe to topics etc) • Timeouts need to be implemented and handled • Investigate maximum message payload size • Find or maintain a NATS python library that doesn't use async like the official one does • Add a lot of testing • Cleanup everything noted as TODO in the POC code Now I couldn’t possibly pull this off myself without some collaboration with all of you, even though I’m very motivated to just dig in and do this for the rest of the year and migrate our test fleet there I unfortunately (like everyone else) is juggeling a lot of balls at the same time. 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. Best regards Tobias [1] https://review.opendev.org/c/openstack/oslo.messaging/+/848338 [2] https://nats.io

4 7

[ovn-bgp-agent][neutron] - expose_tenant_networks bug
by Satish Patel 01 Sep '22

01 Sep '22

Folks, I am setting up ovn-bgp-agent lab in "BGP mode" and i found everything working great except expose tenant network https://ltomasbo.wordpress.com/2021/02/04/ovn-bgp-agent-testing-setup/ Lab Summary: 1 controller node 3 compute node ovn-bgp-agent running on all compute node because i am using "enable_distributed_floating_ip=True" ovn-bgp-agent config: [DEFAULT] debug=False expose_tenant_networks=True driver=ovn_bgp_driver reconcile_interval=120 ovsdb_connection=unix:/var/run/openvswitch/db.sock I am not seeing my vm on tenant ip getting exposed but when i attach FIP which gets exposed in loopback address. here is the full trace of debug logs: https://paste.opendev.org/show/buHiJ90nFgC1JkQxZwVk/

2 9

help: set ironic inspect autodiscovery failed
by 陈薇 01 Sep '22

01 Sep '22

Hi All, I'm trying the ironic inspect autodiscovery but failed. What I did: Set the inspector.conf 1. [discovery] enroll_node_driver = ipmi [processing] permit_active_introspection = true processing_hooks = $default_processing_hooks,extra_hardware,lldp_basic Configure the python agent: inspection_callback_url: There's no node automatically added. I enter the host and read the log of python agent, no inspect related log. Could anybody give any advice about how to triage or setup correctly? Thanks & Regards, Wei

1 1

[election][openstack-ansible] PTL candidacy for Antelope cycle
by Dmitriy Rabotyagov 01 Sep '22

01 Sep '22

Hello. I want to self-nominate for the role of OpenStack-Ansible PTL for the Antelope release cycle. As always, my goal will be to constantly improve existing code, make deployments and further operations as reliable as possible. For the previous cycle we have reached some of previously defined goals, like adding a `service` role, finally implementing service_token_roles and support of CentOS 9 Stream, but there is still room for improvement for role testing. With the return of live events I will do my best to ensure project presence on them and get in touch with operators to gain feedback for project future improvement. -- Kind regards, Dmitriy Rabotyagov

2 1

[all][tc] Technical Committee next weekly meeting on 2022 Sept 1 at 1500 UTC
by Ghanshyam Mann 01 Sep '22

01 Sep '22

Hello Everyone, Below is the agenda for Tomorrow's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * Checks on Zed cycle tracker ** https://etherpad.opendev.org/p/tc-zed-tracker * 2023.1 cycle PTG Planning ** TC + Leaders interaction sessions *** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 ** TC PTG etherpad *** https://etherpad.opendev.org/p/tc-2023-1-ptg ** Schedule 'operator hours' as a separate slot in PTG(avoiding conflicts among other projects 'operator hours') *** https://twitter.com/osopsmeetup/status/1561708283492196353 *** https://doodle.com/meeting/participate/id/bD9kR2yd * 2023.1 cycle Technical Election ** https://governance.openstack.org/election/ * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[cinder] Extending Feature Freeze Deadline by 1 week
by Rajat Dhasmana 01 Sep '22

01 Sep '22

Hi All, As discussed in the cinder meeting today, due to the abundance of features proposed[1] and the shortage of review bandwidth, we are planning to extend the feature freeze by one week. Current feature freeze date (for cinder): 01 September 2022 New feature freeze date (for cinder): 08 September 2022 Kindly let me know if there are any objections to the above proposal else all the features proposed are eligible for the feature freeze exception of 1 week. [1] https://etherpad.opendev.org/p/cinder-zed-features Thanks and regards Rajat Dhasmana

1 0

[election][manila] PTL Candidacy for Antelope cycle
by Carlos Silva 01 Sep '22

01 Sep '22

Greetings, Zorillas and interested stackers, I would like to announce my candidacy to be the Manila PTL during the Antelope cycle. I have been the PTL for Manila since the Zed cycle, and have been contributing to OpenStack since the Stein release. It has been an awesome experience. Over the Zed cycle my focus was to continue mentoring and adding new core reviewers to the Manila repositories; Pursuing feature parity and complete support for manila in OSC (also increasing our functional tests coverage), tackling the tech debt; enhancing the documentation to help third party drivers to set up their CI systems; promoting events to gather the community members and getting bugs fixed and implementations moving faster. I am happy with the progress we made in those areas, but I still think there is room for improvement. During the Antelope cycle, I would like to focus on: - Continue our efforts to mentor contributors and increase the amount of active reviewers through engaging them in the community, teaching the OpenStack way and making it collaboratively as we did in the past cycles, promoting hackathons, bug squashes and collaborative review sessions. - Getting more features already available in the Manila core to Manila UI and get more attention to our changes to OpenStack SDK; - Continue pushing Manila to cover the tech debt areas we identified over the past cycles; - Enforcing maintainers to collaboratively cover the lack of documentation we have on third party CI setups for Manila, helping potential new vendors to quickly setup up their CI systems; Thank you for your consideration! Carlos da Silva IRC: carloss

3 2

[cinder] Antelope PTG Planning
by Rajat Dhasmana 01 Sep '22

01 Sep '22

Hi All, The virtual PTG for Antelope/2023.1 cycle will be held between 17-21 October 2022. The proposed schedule for cinder is as follows: Dates: Tuesday (18th October) to Friday (21st October) 2022 Time: 1300 to 1700 UTC Etherpad: https://etherpad.opendev.org/p/antelope-ptg-cinder-planning Please add topics to the etherpad as early as possible since that will help arrange the topics day wise in the actual PTG etherpad. Thanks and regards Rajat Dhasmana

1 0

[QA][ironic] cycle-with-intermediary deliverables without any release
by Előd Illés 01 Sep '22

01 Sep '22

Hi, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Zed cycle: [ironic*] bifrost ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch [Quality Assurance] patrole Those should be released ASAP, and in all cases before September 15th, so that we have a release to include in the final Zed release. (* actually, we DID discuss this already with Ironic release liaisons [1], so this is just a formal reminder for them) [1] https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-rele… Előd Illés irc: elodilles

1 0

[OVN] Error while creating a new instance due to port binding failure
by 박경원 01 Sep '22

01 Sep '22

1 0

[largescale-sig] Next meeting: August 31st, 15utc
by Thierry Carrez 31 Aug '22

31 Aug '22

Hi everyone, The Large Scale SIG is back from its extended vacation! We will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can check how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220831T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

Take the OpenStack User Survey! Deadline Today!
by Allison Price 31 Aug '22

31 Aug '22

Hi everyone, I wanted to remind you that today is the last day to complete your 2022 OpenStack User Survey. If you (or a customer) is operating an OpenStack environment, please take time to complete the deployment survey. If you have completed it before, you will just need to update your information, but your previous responses will auto-populate. Complete here: https://www.openstack.org/usersurvey <https://www.openstack.org/usersurvey> Please let me know if you have any issues. Cheers, Allison

1 0

[charms] Nominate Luciano Giudice for charms-ceph core
by Chris MacNaughton 31 Aug '22

31 Aug '22

Hello all, I'd like to propose Luciano as a new Ceph charms core team member. He has contributed quality changes over the last year, and has been providing quality reviews for the Ceph charms. patches: https://review.opendev.org/q/owner:luciano.logiudice%2540canonical.com reviews: https://review.opendev.org/q/reviewedby:luciano.logiudice%2540canonical.com I hope you will join me in supporting Luciano. Chris MacNaughton

4 3

[election][cloudkitty] PTL candidacy for Antelope
by Rafael Weingärtner 31 Aug '22

31 Aug '22

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the Antelope release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. -- Rafael Weingärtner

1 0

[cinder] Bug deputy report for week of 08-31-2022
by Sofia Enriquez 31 Aug '22

31 Aug '22

This is a bug report from 08-24-2022 to 08-31-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1987539 "DeprecationWarning: Flags not at the start of the expression." Fix proposed to master. Cheers, Sofia -- 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

[election][Octavia] PTL candidacy for Antelope cycle
by Gregory Thiemonge 31 Aug '22

31 Aug '22

Hi, I would like to announce my candidacy for Octavia PTL for the Antelope release. I have been PTL since the Xena cycle and I want to continue to contribute to this role. During the Antelope cycle we will focus on reviewing/merging some of the opened patches we still have in our backlog (we are a small team but we have been growing, we expect that we will be more efficient in merging patches). For the A cycle we also need to work on the migration to sqlalchemy 2, it will be a huge challenge for our team. Thanks for your consideration, Gregory Thiemonge (gthiemonge)

1 0

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Extended 7 days
by Amy Marrich 31 Aug '22

31 Aug '22

We have extended the nomination period 7 days and will overlap the TC campaigning period to accommodate the extension. Thank you everyone who has nominated themselves and for cutting down the list of leaderless projects to 24. Remember there are also 4 open seats for the TC this election cycle which the automated email does not include in this reminder. Thanks, Amy ---------------------------------------------------------------------------------------------- A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 07, 2022 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-08-24 23:45:00 UTC Nominations end @ 2022-09-07 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 7 days, 10:19:33 Nominations progress : 46.93% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 28 ( 53.85%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 24 (Adjutant Barbican Cloudkitty Keystone Masakari Mistral Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Openstack_Chef Oslo Quality_Assurance Rally Release_Management Requirements Sahara Senlin Skyline Swift Trove Venus Zaqar Zun) =================================================== Stats gathered @ 2022-08-31 13:25:27 UTC This means that with approximately 7 days left, 24 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[openstack-ansible] Converged compute ans ceph storage
by fv＠spots.edu 31 Aug '22

31 Aug '22

Hello everyone! Is it possible with OpenStack-Ansible to deploy converged nova compute and ceph storage on a single node? Thank you!

3 2

[openstack-ansible][ceph][yoga] wait for all osd to be up
by Father Vlasie 31 Aug '22

31 Aug '22

Hello everyone, I am running setup-infrastucture.yml. I have followed the ceph production example here: https://docs.openstack.org/openstack-ansible/latest/user/ceph/full-deploy.h… I have set things up so the compute and storage nodes are the same machine (hyperconverged). And the storage devices are devoid of any volumes or partitions. I see the following error: ------ FAILED - RETRYING: [compute3 -> infra1_ceph-mon_container-0d679d8d]: wait for all osd to be up (1 retries left). fatal: [compute3 -> infra1_ceph-mon_container-0d679d8d(192.168.3.145)]: FAILED! => {"attempts": 60, "changed": false, "cmd": ["ceph", "--cluster", "ceph", "osd", "stat", "-f", "json"], "delta": "0:00:00.223291", "end": "2022-08-22 19:36:29.473358", "msg": "", "rc": 0, "start": "2022-08-22 19:36:29.250067", "stderr": "", "stderr_lines": [], "stdout": "\n{\"epoch\":6,\"num_osds\":0,\"num_up_osds\":0,\"osd_up_since\":0,\"num_in_osds\":0,\"osd_in_since\":0,\"num_remapped_pgs\":0}", "stdout_lines": ["", "{\"epoch\":6,\"num_osds\":0,\"num_up_osds\":0,\"osd_up_since\":0,\"num_in_osds\":0,\"osd_in_since\":0,\"num_remapped_pgs\":0}”]} ------ I am not sure where to look to find more information. Any help would be much appreciated! Thank you, FV

2 2

[election][designate] PTL Candidacy for Antelope cycle
by Michael Johnson 31 Aug '22

31 Aug '22

Hello OpenStack community, I would like to announce my candidacy for PTL of Designate for the Antelope cycle. I would like to continue to support the Designate team for the Antelope release. As predicted, we have continued to focus on cleaning up technical debt and improving the test coverage. For a small team, we have accomplished a lot in the Zed release, though we could use more reviewers to help with the backlog of patches in need of review and comments. I expect the code cleanup will continue, but I hope we can also focus more on some of the proposed features that are in flight. Thank you for your support and your consideration for Antelope, Michael Johnson (johnsom)

1 0

[cinder] propose to EOL cinderlib train and ussuri
by Brian Rosmaita 31 Aug '22

31 Aug '22

At last week's cinder project midcycle [0], the team discussed recent fixes to keep the cinderlib CI functional in the oldest stable branches. At this point, stable/train is running the bare minimum of CI to keep the branch open, and stable/ussuri is running only one functional job in excess of the bare minimum. The only changes merged into either branch since each was tagged -em have been non-functional, so we believe that there is no demand for keeping the branches open. Thus, the following patches to EOL cinderlib train and ussuri have been posted: - https://review.opendev.org/c/openstack/releases/+/853534 - https://review.opendev.org/c/openstack/releases/+/853535 This email serves as notice of the intent of the cinder project to EOL the cinderlib train and ussuri branches. If you have comments or concerns, please reply to this email or leave a comment on the appropriate patch. [0] https://etherpad.opendev.org/p/cinder-zed-midcycles

1 1

[blazar][election] PTL candidacy for Antelope cycle
by Pierre Riteau 31 Aug '22

31 Aug '22

Hi, I would like to self-nominate for the role of PTL of Blazar for the Antelope release cycle. I have been PTL since the Stein cycle and I am willing to continue in this role. Though we had a quiet Zed cycle, we still have various improvements in the pipeline and I want to help the community deliver them to make Blazar more useful. Thank you for your support, Pierre Riteau (priteau)

1 0

[election][puppet] PTL Candidacy for Antelope cycle
by Takashi Kajinami 31 Aug '22

31 Aug '22

Hello, I'd like to announce my candidacy for the PTL role in Puppet OpenStack, to continue my PTL role for the Antelope cycle. Over the past two cycles, we've successfully improved feature coverage, platform coverage and simplicity of our modules. I'd like to list up a few items which would be our priorities during the next cycle. * Add Ubuntu 22.04 support This would be the next major change after we've completed implementation of CentOS 9 Stream support. We already adapted to Ruby 3 as part of C9S support so I'm not aware of any huge challenges at this moment. * Complete migration to Puppet 7 Currently our modules still support both Puppet 6 and 7. However once we complete migration to Ubuntu 22.04, we complete migration from Ruby 2.x to 3.x. As Puppet officially supports Ruby 3.x since 7.7, this means we no longer maintain test coverage with Puppet 6. It's time to consider again complete migration to Puppet 7. * Improve scenario/component coverage by CI During Zed cycle we added OVN and Octavia to the integration jobs. We'll review a few remaining modules like Manila and will continue extending the component coverage. * Review unmaintained/unused modules In Puppet OpenStack projects we maintain number of modules to support multiple OpenStack components. However, some modules have not been really active and attracted no interest. In the past few cycles we have retired several modules but I'd like to continue reviewing our modules to consider retiring inactive ones. * Keep each module up to date and simple It's always important that we add support for the new features/parameters timely so that users can leverage the new capability via our modules. Thank you for your consideration. Thank you, Takashi

3 2

[election][cinder] PTL Candidacy for Antelope
by Rajat Dhasmana 31 Aug '22

31 Aug '22

Hello everyone, I would like to announce my candidacy for PTL of the Cinder project for the Antelope cycle. I served as the PTL for Cinder during the Zed development cycle and targeted some of the areas which were lacking attention and worked on improving them like: 1. Review Quality Proposing the Efficient Review Guidelines[1] to help new contributors improve the quality of reviews. 2. Security Vulnerabilities Triaged the open security issues during the first mid cycle[2]. There are still areas which could be improved upon like 3rd Party Compliance checks and Cinder driver documentation which are good candidates of work items for the next development cycle and I look forward to actively work on them. Apart from that, there were deadlines which could have been better handled which I would like to incorporate in my planning skills so we get things merged in time and we won't have to extend deadlines frequently. Overall, I feel it was a good learning experience being PTL for the first time and I'm thankful for all the support I've had from the team, not to mention the advice and help from Brian while making critical decisions, and Hopefully I will take the learnings to be a better PTL this time. [1] https://docs.openstack.org/cinder/latest/contributor/gerrit.html#efficient-… [2] https://etherpad.opendev.org/p/cinder-zed-midcycles#L136 Rajat Dhasmana (whoami-rajat)

1 0

[election][Release_Management] Proposal to change to Distributed PTL model
by Előd Illés 31 Aug '22

31 Aug '22

Hi, This is my 2nd cycle (Yoga + Zed) as PTL of the Release Management team and this is the time when usually a PTL role is handed over. We had a discussion in our team and decided that now that OpenStack moves from Zed to Antelope and the cycles starts again from the beginning of the alphabet + the new naming is going to be introduced (2023.1 Antelope) this is a good time to change the leadership model of the team to a group leadership model (or DPTL; distributed project team leadership). @TC: so this mail is to inform the TC that we want to move to this direction & let us know if there is something we need to sort out for the model change. Thanks, Előd Illés irc: elodilles

2 1

PTG October 2022 Teams List
by Kendall Nelson 31 Aug '22

31 Aug '22

Hello Everyone! The October 2022 Project Teams List is official! Projects + Teams: - Computing Force Network (CFN) Working Group - Diversity& Inclusion Working Group - Environmental Sustainability Working Group - Kata Containers - Magma - OpenInfra Edge Computing Group - OpenStack Teams - - Ansible OpenStack Modules - Barbican - Blazar - Cinder - CloudKitty - Designate - First Contact SIG - Glance - Heat - Horizon - Interop WG - Ironic - Keystone - Kolla - Kuryr - Manila - Neutron - Nova/Placement - Octavia - OpenStack Charms - OpenStack Helm - OpenStack Operators - OpenStack SDK/CLI - OpenStack Security SIG - OpenStack Technical Committee - Openstack-Ansible - OpenStack-Helm - QA - Release Management - Swift - Tacker - Telemetry - TripleO - StarlingX If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign 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

[election][Neutron] PTL candidacy for Antelope cycle
by Rodolfo Alonso Hernandez 30 Aug '22

30 Aug '22

Hello all: I would like to announce my candidacy for the role of PTL of Neutron for the Antelope cycle. Let me introduce myself first. I started contributing to OpenStack in Liberty release (2015). I've contributed to several projects, mainly Neutron, neutron-lib, os-ken and os-vif, in addition to Nova and devstack. During the last two years I've been focused on the ML2/OVN integration, QoS and Placement related features and helping on the Neutron CI improvement and stabilization. For this new release, those are the main goals I would like to focus on: * Take care and focus on the approved and merged Neutron specs [1]. Those RFEs should be actively attended by the community, from the spec proposal to the code review. In order to increase the attention of the community on these new RFEs, new ways of tracking them should be proposed (a topic that should be discussed during the PTG). For example, having a core reviewer “godfather” for each RFE. * Continue with the improvement of CI stability. The job done during the last 2 or 3 releases has been impressive, probably the hardest and the most continued effort on the CI in the Neutron community ever. We *must* continue with this effort and the current processes to track the healthiness of the CI. * Start working on the smart NIC / hardware offload testing. The number of backends (ML2/OVS, ML2/OVN, ML2/SR-IOV) make non-viable to test any possible combination. But at least, depending on the available hardware, we would be able to test the stability of those backends with the newest hardware offload NICs. Note: that will imply an external CI support. * Work with users and operators, providing an active channel with them. The goal is to attract customers to be actively involved in the community, participating in the Neutron meetings (team meeting, CI meeting, drivers meeting) or even creating a specific meeting with them in order to capture new needs or issues. * Live migration improvement, specially in ML2/OVN. This feature is still being tested and has not proven to be very stable. There are several core OVN and Neutron efforts right now but we still need to make this feature stable enough to be delivered to customers. A part from those main goals, we should always keep an eye on: * The SQLAlchemy 2.0 migration and any possible issue detected. * The Neutron's stadium ecosystem alive and healthy: this is a permanent goal in any release. The Neutron ecosystem is wide and diverse and it is maintained with few resources. We should focus on those active projects and communities that support their respective repositories. * Still closing the ML2/OVS - ML2/OVN feature gap, that is smaller every cycle. Thank you in advance. Rodolfo Alonso Hernandez (ralonsoh, ralonsoh(a)redhat.com)

1 0

[TripleO] quay.io namespace local mirror using harbor. Quay.io do not list repos/images
by Ruslanas Gžibovskis 30 Aug '22

30 Aug '22

Hi all, I am trying to make a local repo/copy to be able to deploy OSP onsite behind firewall. I have found out from harbor, that Quay.io do not return repos/image anonymously also I have created account in quay.io with my RH account. Later reset quay.io password, so quay.io connection verify works. I can get it as a proxy, or exact image, but not full offline installation. Could you help/suggest any tool that could do a local repo? I have also tried foreman, but it only can sync repo in namespace, not whole namespace. Thank you for your advice and comments. -- Ruslanas Gžibovskis +370 6030 7030

2 1

[kolla] [nova] Rogue AggregateMultiTenancyIsolation filter
by Albert Braden 30 Aug '22

30 Aug '22

We're running kolla train, and we use the AggregateMultiTenancyIsolation for some aggregates by setting filter_tenant_id. Today customers reported build failures when they try to build VMs in a non-filtered region. I am able to duplicate the issue: os server create --image <image> --flavor medium --network private --availability-zone open alberttest1 | 5dd44105-2045-4d53-be43-5f521ddb420b | alberttest1 | ERROR | | <image> | medium | 2022-08-26 18:39:38.977 30 INFO nova.filters [req-342d065a-cd47-4edf-bc4b-3f84b34ab97c 25b53bdb96fb5f9f6e7331d7e03eee0a12c45746a9e8b978858b2140a5275a09 fdcf1553db504c8f82a2b54851a4c262 - 8793b235debf49e6aba6bd1e2bf65360 8793b235debf49e6aba6bd1e2bf65360] Filtering removed all hosts for the request with instance ID '5dd44105-2045-4d53-be43-5f521ddb420b'. Filter results: ['ComputeFilter: (start: 50, end: 50)', 'RetryFilter: (start: 50, end: 50)', 'AggregateNumInstancesFilter: (start: 50, end: 50)', 'AvailabilityZoneFilter: (start: 50, end: 6)', 'AggregateInstanceExtraSpecsFilter: (start: 6, end: 6)', 'ImagePropertiesFilter: (start: 6, end: 6)', 'ServerGroupAntiAffinityFilter: (start: 6, end: 6)', 'ServerGroupAffinityFilter: (start: 6, end: 6)', 'AggregateMultiTenancyIsolation: (start: 6, end: 0)'] Region "open" does not have any properties specified, so the AggregateMultiTenancyIsolation filter should not be active. qde3:admin]$ os aggregate show open|grep properties | properties | This is what we would see if it had the filter active: :qde3:admin]$ os aggregate show closed|grep properties | properties | filter_tenant_id='1c41e088b35f4b438023d081a6f70292,3e9727aaf03e4459a176c28dbdb3965e,f9b4b7dc8c614bb09d66657afc3b21cd,121a5da3dd0b489986908bee7eea61ae,d580ccc4b07e478a9efc2d71acf04cc1,107e14eeda01400988e58f5aac8b2772', closed='true' What could be causing this filter to remove hosts when we haven't set filter_tenant_id for that aggregate?

2 2

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

30 Aug '22

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (tomorrow) will be held in video + IRC mode with details as follows: Date: 31st August, 2022 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 since we do roll call and also discuss topics on IRC (if the author is more comfortable in written format). Thanks and regards Rajat Dhasmana

1 0

[election][nova][placement] Candidating for the Antelope cycle.
by Sylvain Bauza 30 Aug '22

30 Aug '22

Hi Nova and Placement folks, Yet again, I want to help our community for this cycle by working on papers. If you accept me for being Antelope Nova/Placement PTL, it would be my last cycle for it after already two of them (unless nobody runs for this). For the moment, we are not yet done with Zed but I'm happy to see that we have 13 open blueprints that are reviewed and where some of them are from contributors that aren't everyday Nova developers. That's the reason why I wanted to help those on-off contributors that have not a large time for upstream work and that's why we added a Gerrit review label value for them (saying "I want to review as a contributor"). We also tried a new way for discussing about open changes creating a new API microversion and even if it hadn't really needed, I think we could use this way next time if needed. So, what would I like for us to discuss during Antelope then ? Well, at least three points : - given Antelope will be the first 'tick' release, I want to make sure we won't have any issues in Nova or Placement for this cycle, and I also would like to prepare for the 'tock' release. - I would like to discuss with our community how to find some opportunities for new contributors that would like to work on Nova. - as we discussed with operators in the Berlin Summit, I would like to find a way for them to discuss with us and see how they could be in our community even if they're not developers. At least, I'd love to see some operators in our meetings and in our PTG sessions. Thanks, -Sylvain (again, not a leader but just a herder.)

1 0

[all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 30 Aug '22

30 Aug '22

Hello, Please note that the list provided was just from my own notes and I didn’t put much emphasis on making it complete or accurate. If you think back to the early days of OpenStack the pain was in OpenStack itself, today it’s a challenge instead to manage OpenStack scale and fit into the things we see, like moving OpenStack into containers (for example managed by Kubernetes). I would like OpenStack design to more embrace the distributed, cloud-native approach that Ceph and Kubernetes brings, and the resiliency of Ceph (and yes, I’m a major Ceph enthusiast) and there I’m seeing messaging and database as potential blockers to continue on that path. I’m not saying that’s the only thing, for example stuff like [1] _really_ matter in real world deployments so working on other OpenStack parts for resilience is also crucial. There is things I’m interested in that would impact the overall design, I can list some of them but I think it might be to broad of a subject for this thread. * Like brought up my Mohammed Naser before, I would like to investigate an effort for containers as an OpenStack deliverable for projects * Investigate cloud-native, highly available and resilient alternatives for messaging and database * Make OpenStack more resilient with above and [1] is a great example on what I mean I’ll respond to your questions with my views inline below. P.S The opionions stated here is my own personal opinions and should not be assumed to be the opinions of any other entity. Best regards Tobias [1] https://bugs.launchpad.net/neutron/+bug/1987780 Begin forwarded message: From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com<mailto:radoslaw.piliszek@gmail.com>> Subject: Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver Date: 29 August 2022 at 18:33:15 CEST To: Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>> Cc: openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> Hi Tobias, Good to see RMQ alternatives appearing. A couple of questions from me. On Mon, 29 Aug 2022 at 15:47, Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>> wrote: • Do retries and acknowledgements in the library (since NATS does NOT persist messages like RabbitMQ could) What do you mean? Is NATS only a router? (I have not used this technology yet.) It does not persist messages, if there is no backend to respond, the message will be dropped without any action hence why I want the RPC layer in oslo.messaging (that already does acknowledge calls in the driver) to notify client side that it’s being processed before client side waits for reply. • Find or maintain a NATS python library that doesn't use async like the official one does Why is async a bad thing? For messaging it's the right thing. This is actually just myself, I would love to just being able to use the official that is async based instead it’s just me that doesn’t understand how that would be implemented. https://github.com/nats-io/nats.py instead of the one in POC https://github.com/Gr1N/nats-python which has a lot of shortcomings and issues, my idea was just to investigate if was even possible to implement in a feasible way. Finally, have you considered just trying out ZeroMQ? Does not exist anymore. I mean, NATS is probably an overkill for OpenStack services since the majority of them stay static on the hosts they control (think nova-compute, neutron agents - and these are also the pain points that operators want to ease). I don’t think it it, or even if it is, why not use a better solution or stable approach than RabbitMQ? This is also the whole point, I don’t want OpenStack to become or be static, I want it to be more dynamic and cloud-native in it’s approach and support viable integrations that takes it there, we cannot live in the past forever, let’s envision and dream of the future as we want it! :) NATS seems to me to cater for a different use case. It actually caters to a lot of use cases. I might be wrong because I have read only the front page but that is the feeling I have. Cheers, Radek -yoctozepto Begin forwarded message: From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com<mailto:radoslaw.piliszek@gmail.com>> Subject: Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver Date: 29 August 2022 at 20:20:15 CEST To: Sean Mooney <smooney(a)redhat.com<mailto:smooney@redhat.com>> Cc: Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>>, openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> On Mon, 29 Aug 2022 at 20:03, Sean Mooney <smooney(a)redhat.com<mailto:smooney@redhat.com>> wrote: Finally, have you considered just trying out ZeroMQ? ZeroMQ used to be supported in the past but then it was remvoed if i understand correctly it only supprot notificaiton or RPC but not both i dont recall which but perhapse im miss rememebrign on that point. I believe it would be better suited for RPC than notifications, at least in the simplest form. As it’s advertised as scalable and performant I would argue that, why not use it for notifications as well? If anything according to your observations above it’s more suited for that than RPC, even though request-reply (that we can use for RPC) is a strong first-class implementation in NATS as well. I mean, NATS is probably an overkill for OpenStack services since the majority of them stay static on the hosts they control (think nova-compute, neutron agents - and these are also the pain points that operators want to ease). its not any more overkill then rabbitmq is True that. Probably. I agree with that, also if you think about it, how many issues related to stability, performance and outages is related to RabbitMQ? It’s quite a few if you ask me. Just the resource utilization and clustering in RabbitMQ makes me feel bad. It’s here that I mean that the cloud-native and scalable implementation would shine, you should be able to rely on it, if sometimes dies so what, things should just continue to work and that’s not my experience with RabbitMQ but it is my experience with Ceph because in the end the design really matters. i also dont know waht you mean when you say "majority of them stay static on the hosts they control" NATS is intended a s a cloud native horrizontally scaleable message bus. which is exactly what openstack need IMO. NATS seems to be tweaked for "come and go" situations which is an exception in the OpenStack world, not the rule (at least in my view). I mean, one normally expects to have a preset number of hypervisors and not them coming and going (which, I agree, is a nice vision, could be a proper NATS driver, with more awareness in the client projects I believe, would be an enabler for more dynamic clouds). It could, but it also doesn’t have to be that. Why not strive for more dynamic? I don’t think anybody would argue that more dynamic is a bad thing even if you were to have a more static approach to your cloud. Cheers, Radek -yoctozepto

2 2

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 30 Aug '22

30 Aug '22

Hi all, Tomorrow we will have our bi-weekly meeting at 0800 UTC in #openstack-operators. Agenda can be fond here [0]. Feel free to suggest topics to the agenda if you like. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0

RE: Openstack OVN (Open Virtual Network) HA deployment - running OVN in active/passive mode?
by 박경원 30 Aug '22

30 Aug '22

1 0

[infra][puppet] Old mirror contents in apt-puppetlabs
by Takashi Kajinami 30 Aug '22

30 Aug '22

Hello Infra team, I noticed the contents in the apt-puppetlabs directory in our CI mirror are old. The mirror repository provides puppet 6.23 while the upstream repository provides newer versions such as 6.28. Recently we bumped puppetlabs-mysql in our CI to 13.0.0 which requires puppet >= 6.24.0 and our Ubuntu jobs are failing now at a quite early stage because of the old puppet package. May someone please look into this ? I've checked mirror.iad3.inmotion.opendev.org and mirror.bhs1.ovh.opendev.org but it seems the contents in the directory have not been synced since July, 2021. Thank you, Takashi

2 3

Skyline apiserver can't connect to keystone and given error endpoint not found
by mahdi n 30 Aug '22

30 Aug '22

Skyline apiserver can't connect to keystone and given endpoint not found I install skyline api server and console But Apiserver get error : endpoint not found I attached pictures of this problem Please help me

1 1

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Last Days
by Amy Marrich 30 Aug '22

30 Aug '22

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 31, 2022 23:45 UTC. Should we find that many of the community members were off on vacation this date may get extended pushing the elections out. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-08-24 23:45:00 UTC Nominations end @ 2022-08-31 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 2 days, 5:50:21 Nominations progress : 67.95% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 5 ( 9.62%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 47 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Freezer Glance Heat Horizon Ironic Keystone Manila Masakari Mistral Monasca Murano Neutron Nova Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms OpenStack_Helm Openstack_Chef Oslo Puppet_OpenStack Quality_Assurance Rally Release_Management Requirements Sahara Senlin Skyline Solum Storlets Swift Tacker Telemetry Tripleo Trove Venus Vitrage Watcher Zaqar Zun) =================================================== Stats gathered @ 2022-08-29 17:54:39 UTC This means that with approximately 2 days left, 47 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[tacker][elections] PTL candidacy for Antelope cycle
by Yasufumi Ogawa 30 Aug '22

30 Aug '22

Hi, I'd like to propose my candidacy for Tacker PTL for Antelope cycle. I have contributed to Tacker as a PTL from Victoria for providing the latest features of ETSI-NVF standard features to enable operators to deploy their services. In the latest cycles, we have developed several supports for deploying CNFs, multi-version APIs for mixed environment of legacy and cutting edge-products provided by several vendors and more. We also have had several collaborative sessions with ETSI NFV for accelerating each activity of standardization and deployment of required features. In the next release, I would like to focus our target more on to develop features for reliability and avairability such as monitoring physical resources in addition to VMs and containers. Best regards, Yasufumi (yasufum)

1 0

[TripleO Wallaby] - Multi-attach Volume showing different files
by Lokendra Rathour 30 Aug '22

30 Aug '22

Hi Team, On TripleO Wallaby deployment, I have tried creating multi-attach type volume, which if I am attaching this volume to two VM, it is getting attached. After mounting the same in each VM, if I am creating the folders in one VM at the mount path, I am not seeing the same on the other VM at the mount path [image: image.png] Ideally if the backend volume is same and if I am understanding the idea correctly, then the content should be same in both the location, as the back is same. Checking at horizon I also see that Volume is showing attached to both the VMs. [image: image.png] Document followed to create this: https://docs.openstack.org/cinder/latest/admin/volume-multiattach.html Please advice -- ~ Lokendra skype: lokendrarathour

3 4

[Neutron] How to add Fake ML2 extension to Neutron?
by Igor Zhukov 30 Aug '22

30 Aug '22

Hi all! Sorry for a complete noob question but I can't figure it out 😿 So if I want to add Fake ML2 extension what should I do? I have neutron server installed and I have the file: https://github.com/openstack/neutron/blob/master/neutron/tests/unit/plugins… How to configure neutron server, where should I put the file, should I create another files? How can I test that it works?

2 7

[xena][placement] Xena placement upgrade leads to 500 on ubuntu focal
by CHANU ROMAIN 29 Aug '22

29 Aug '22

Hello, I just did upgrade my Placement to Xena on Ubuntu Focal (20.04). When I tried to start the process I got this error and all HTTP requests receive an HTTP 500 error: 2022-08-19 15:05:43.960573 2022-08-19 15:05:43.960 43 INFO placement.requestlog [req-f4c4d4f1-5d59-49d3-aa3e-1e8a09fe02fe 3ec54dee59424109913d4628ae8dac4c 19e62bc767484849a2763937883a256e - default default] 192.168.236.5 "GET /resource_providers/791c09ed-57f3- 4bfc-9278-4af6c5c137d8/allocations" status: 500 len: 244 microversion: 1.0\x1b[00m 2022-08-19 15:05:44.094951 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap [req-527dce52-c207-43ee-80f2-016a6f031cf5 3ec54dee59424109913d4628ae8dac4c 19e62bc767484849a2763937883a256e - default default] Placement API unexpected error: unsupported callable: TypeError: unsupported callable 2022-08-19 15:05:44.094973 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap Traceback (most recent call last): 2022-08-19 15:05:44.094977 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 1135, in getfullargspec 2022-08-19 15:05:44.094980 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap sig = _signature_from_callable(func, 2022-08-19 15:05:44.094998 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2233, in _signature_from_callable 2022-08-19 15:05:44.095001 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap sig = _signature_from_callable( 2022-08-19 15:05:44.095004 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2304, in _signature_from_callable 2022-08-19 15:05:44.095007 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _signature_from_function(sigcls, obj, 2022-08-19 15:05:44.095010 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2168, in _signature_from_function 2022-08-19 15:05:44.095013 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap parameters.append(Parameter(name, annotation=annotation, 2022-08-19 15:05:44.095015 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2491, in __init__ 2022-08-19 15:05:44.095018 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap self._kind = _ParameterKind(kind) 2022-08-19 15:05:44.095021 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap RecursionError: maximum recursion depth exceeded 2022-08-19 15:05:44.095024 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap 2022-08-19 15:05:44.095026 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap The above exception was the direct cause of the following exception: 2022-08-19 15:05:44.095029 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap 2022-08-19 15:05:44.095032 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap Traceback (most recent call last): 2022-08-19 15:05:44.095035 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/fault_wrap.py", line 39, in __call__ 2022-08-19 15:05:44.095038 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.application(environ, start_response) 2022-08-19 15:05:44.095040 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 129, in __call__ 2022-08-19 15:05:44.095043 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap resp = self.call_func(req, *args, **kw) 2022-08-19 15:05:44.095046 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 193, in call_func 2022-08-19 15:05:44.095049 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.func(req, *args, **kwargs) 2022-08-19 15:05:44.095052 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/microversion_parse/middleware.py", line 80, in __call__ 2022-08-19 15:05:44.095055 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap response = req.get_response(self.application) 2022-08-19 15:05:44.095057 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/request.py", line 1313, in send 2022-08-19 15:05:44.095060 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap status, headers, app_iter = self.call_application( 2022-08-19 15:05:44.095063 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/request.py", line 1278, in call_application 2022-08-19 15:05:44.095065 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap app_iter = application(self.environ, start_response) 2022-08-19 15:05:44.095068 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handler.py", line 215, in __call__ 2022-08-19 15:05:44.095071 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return dispatch(environ, start_response, self._map) 2022-08-19 15:05:44.095074 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handler.py", line 149, in dispatch 2022-08-19 15:05:44.095077 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return handler(environ, start_response) 2022-08-19 15:05:44.095083 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 129, in __call__ 2022-08-19 15:05:44.095086 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap resp = self.call_func(req, *args, **kw) 2022-08-19 15:05:44.095089 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/wsgi_wrapper.py", line 29, in call_func 2022-08-19 15:05:44.095092 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap super(PlacementWsgify, self).call_func(req, *args, **kwargs) 2022-08-19 15:05:44.095094 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 193, in call_func 2022-08-19 15:05:44.095097 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.func(req, *args, **kwargs) 2022-08-19 15:05:44.095100 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/util.py", line 64, in decorated_function 2022-08-19 15:05:44.095103 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return f(req) 2022-08-19 15:05:44.095106 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handlers/allocation.py", line 299, in list_for_resource_provider 2022-08-19 15:05:44.098861 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098864 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098867 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098870 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098873 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098876 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098893 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098896 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098899 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098905 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098907 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098910 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098913 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098916 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098919 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098922 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098925 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098928 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098930 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098933 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098936 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098939 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098941 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098944 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098947 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098950 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098952 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098955 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098958 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098960 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098963 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098966 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098968 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098971 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098974 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098977 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098980 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098982 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098985 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098991 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098993 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098996 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098999 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.099002 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.099004 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 75, in _check 2022-08-19 15:05:44.099007 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap argspec = inspect.getfullargspec(rule.__call__) 2022-08-19 15:05:44.099010 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 1144, in getfullargspec 2022-08-19 15:05:44.099013 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap raise TypeError('unsupported callable') from ex 2022-08-19 15:05:44.099016 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap TypeError: unsupported callable 2022-08-19 15:05:44.099018 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap \x1b[00m Placement-api is deployed in a container, so I got a fresh policy.yaml file. Did someone already face this? Do you have any idea how to fix this? Best regards, Romain

3 3

[Triple0] [Wallaby] External Ceph Integration getting failed
by Lokendra Rathour 29 Aug '22

29 Aug '22

Hi Team, I was trying to integrate External Ceph with Triple0 Wallaby, and at the end of deployment in step4 getting the below error: 2022-08-03 18:37:21,158 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.157962 | 525400fe-86b8-65d9-d100-0000000080d2 | TASK | Create containers from /var/lib/tripleo-config/container-startup-config/step_4 2022-08-03 18:37:21,239 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.238718 | 69e98219-f748-4af7-a6d0-f8f73680ce9b | INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/create.yml | overcloud-controller-2 2022-08-03 18:37:21,273 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.272340 | 525400fe-86b8-65d9-d100-0000000086d9 | TASK | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 2022-08-03 18:37:24,532 p=507732 u=stack n=ansible | 2022-08-03 18:37:24.530812 | | WARNING | ERROR: Can't run container nova_libvirt_init_secret stderr: 2022-08-03 18:37:24,533 p=507732 u=stack n=ansible | 2022-08-03 18:37:24.532811 | 525400fe-86b8-65d9-d100-0000000082ec | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 | overcloud-novacompute-0 | error={"changed": false, "msg": "Failed containers: nova_libvirt_init_secret"} 2022-08-03 18:37:44,282 p=507732 u *external-ceph.conf:* parameter_defaults: # Enable use of RBD backend in nova-compute NovaEnableRbdBackend: True # Enable use of RBD backend in cinder-volume CinderEnableRbdBackend: True # Backend to use for cinder-backup CinderBackupBackend: ceph # Backend to use for glance GlanceBackend: rbd # Name of the Ceph pool hosting Nova ephemeral images NovaRbdPoolName: vms # Name of the Ceph pool hosting Cinder volumes CinderRbdPoolName: volumes # Name of the Ceph pool hosting Cinder backups CinderBackupRbdPoolName: backups # Name of the Ceph pool hosting Glance images GlanceRbdPoolName: images # Name of the user to authenticate with the external Ceph cluster CephClientUserName: admin # The cluster FSID CephClusterFSID: 'ca3080-aaaa-4d1a-b1fd-4aaaa9a9ea4c' # The CephX user auth key CephClientKey: 'AQDgRjhiuLMnAxAAnYwgERERFy0lzH6ufSl70A==' # The list of Ceph monitors CephExternalMonHost: 'abcd:abcd:abcd::11,abcd:abcd:abcd::12,abcd:abcd:abcd::13' ~ Have tried checking and validating the ceph client details and they seem to be correct, further digging the container log I could see something like this : [root@overcloud-novacompute-0 containers]# tail -f nova_libvirt_init_secret.log tail: cannot open 'nova_libvirt_init_secret.log' for reading: No such file or directory tail: no files remaining [root@overcloud-novacompute-0 containers]# tail -f stdouts/nova_libvirt_init_secret.log 2022-08-04T11:48:47.689898197+05:30 stdout F ------------------------------------------------ 2022-08-04T11:48:47.690002011+05:30 stdout F Initializing virsh secrets for: ceph:admin 2022-08-04T11:48:47.690590594+05:30 stdout F Error: /etc/ceph/ceph.conf was not found 2022-08-04T11:48:47.690625088+05:30 stdout F Path to nova_libvirt_init_secret was ceph:admin 2022-08-04T16:20:29.643785538+05:30 stdout F ------------------------------------------------ 2022-08-04T16:20:29.643785538+05:30 stdout F Initializing virsh secrets for: ceph:admin 2022-08-04T16:20:29.644785532+05:30 stdout F Error: /etc/ceph/ceph.conf was not found 2022-08-04T16:20:29.644785532+05:30 stdout F Path to nova_libvirt_init_secret was ceph:admin ^C [root@overcloud-novacompute-0 containers]# tail -f stdouts/nova_compute_init_log.log -- ~ Lokendra skype: lokendrarathour

3 10

[nova] Changes for out-of-tree drivers
by Rajat Dhasmana 29 Aug '22

29 Aug '22

Hi, I'm working on a nova feature which adds support for rebuilding volume backed instances which modifies the arguments for 'rebuild' method. It adds a 'reimage_boot_volume' parameter which signifies if the user has requested a rebuild operation for a volume backed instance. Currently it is only implemented by the ironic driver in the in-tree drivers. If you're a maintainer of an out of tree driver then you will need to account for it. Thanks and regards Rajat Dhasmana

1 1

Lagging of vm
by Naveen j 29 Aug '22

29 Aug '22

Hi Team. When i create a vm, my vms are lagging so much when I run any application in ubuntu Regards Naveen j

2 2

Questions about High Availability setup
by 박경원 29 Aug '22

29 Aug '22

5 6

[requirement][all] Nose being removed from Debian and Ubuntu: let's remove it from our global requirements
by Thomas Goirand 29 Aug '22

29 Aug '22

Hi, It's no surprise for anyone that's been following it: Nose was deprecated years ago, and now, we're trying to remove it from Debian. Therefore, 49 bugs were filled against the Debian OpenStack package. It'd be nice if upstream OpenStack was also following this move, and removing nose from global-requirements. I'm not sure if it'd be a big deal if that wasn't the case, as I could use a different test runner in Debian, but I very much would prefer if it was the case. Probably Ubuntu will follow the same path, since Nose isn't in main (it's in Universe, meaning Debian maintained...). Your thoughts? Cheers, Thomas Goirand (zigo)

2 1

[neutron] Bug deputy report - week of 22 Aug
by Slawek Kaplonski 29 Aug '22

29 Aug '22

Hi, I was Neutron's bug deputy last week. Here is summary of what happend during this time: ## Critical https://bugs.launchpad.net/neutron/+bug/1987308 - [ovn-octavia-provider] ovn compilation is failing in "ovn-octavia-provider-tempest-master " job - assigned to Fernando, patch proposed https://review.opendev.org/c/openstack/ovn-octavia-provider/+/854008 ## High https://bugs.launchpad.net/neutron/+bug/1987530 - Duplicate external_ip in NAT table lead to loss of N/S connectivity - needs attention ## Medium https://bugs.launchpad.net/neutron/+bug/1987396 - masquerading behavior changed between queens and train - assigned to David Hill, patch proposed already: https://review.opendev.org/c/openstack/neutron/+/854041 https://bugs.launchpad.net/neutron/+bug/1987780 - Nova notifications with error response are not retried - assigned to Szymon Wróblewski https://bugs.launchpad.net/neutron/+bug/1987666 - Race condition when adding two subnet with same cidr to router - unassigned currently ## Low https://bugs.launchpad.net/neutron/+bug/1987281 - Create a method to add multiple IP addresses in one call - assigned to Rodolfo https://bugs.launchpad.net/neutron/+bug/1988026 - Neutron should not create security group with project==None - needs assignment, it seems like low hanging fruit bug to fix for me, ## Whishlist (RFEs) https://bugs.launchpad.net/neutron/+bug/1987378 - [RFE] Add DSCP mark 44 - assigned to Rodolfo, marked by him as an RFE but I don't really think we need to discuss and approve it in the drivers meeting. We discussed that during last drivers meeting and it's already triaged. ## Incomlete https://bugs.launchpad.net/neutron/+bug/1987377 - neutron-metadata-agent the memory usage is increasing, Lajos and Oleg already have some comments on that one, ## Needs attention https://bugs.launchpad.net/cloud-init/+bug/1899487 - cloud-init hard codes MTU configuration at initial deploy time - bug which was reported for cloud-init first but now after long discussion it's on Neutron and we need to check it, -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Openstack OVN (Open Virtual Network) HA deployment - running OVN in active/passive mode?
by 박경원 29 Aug '22

29 Aug '22

1 0

[neutron][elections] PTL non-candidacy for Antelope cycle
by Lajos Katona 29 Aug '22

29 Aug '22

Hi, It was a great pleasure and honor to be Neutron PTL for 2 cycles, thanks everybody for the help and support during this time (actually not just for these cycles but for all). It's not just smoke and ruins around networking after my PTLship, so after all I would say it was a success :-) My main focus was to keep the Neutron team as encouraging and inclusive as possible and work on cooperation with new contributor groups and even with other projects of whom we are consuming in Openstack. It is time to change and allow new ideas and energies to form Networking. I remain and I hope I can help the community in the next cycles also. Cheers Lajos Katona

10 9

Re: container and instances are not working on my dashboard
by test 29 Aug '22

29 Aug '22

1 0

containers ad instances are not working
by Lee, Vincent Z 29 Aug '22

29 Aug '22

[https://res.cdn.office.net/assets/mail/file-icon/png/txt_16x16.png]nova-com… 1.log<https://iowastate-my.sharepoint.com/:u:/g/personal/vincet_iastate_edu/EWerz…> Hi all, I am quite new to Openstack and faced some issues with creating instances and displaying created containers on my Openstack dashboard. I am currently working on multinode Openstack. I am hoping to get some helps and feedbacks about this. I will briefly go through the problems I encountered. When I created an instances on my dashboard, it directly went into error state. I have attached a screenshot as shown below. [cid:6d3cb41a-9176-4209-8e12-d669e05ecf5b] This is my list of hosts. [cid:11a45ab0-b7f8-4c79-a619-131d01121687] When I created a container using both cli and dashboard, two containers were running. However, when I tried to look into my dashboard, those containers were not shown. These are the created containers. [cid:1b05b862-8e1d-4833-a3e0-57b921fd6351] However, when i try to open my dashboard and look for them, they just don't appear on it. So I am not sure what is causing this. [cid:0eff5e44-5690-4590-9682-43410e2d52f1] The version of my Openstack deployment is 21.2.4. I deployed my Openstack using the master branch (latest). I have followed the guidelines provided online (https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html) which uses kolla-ansible. In my /var/log/kolla/zun/ directory, I have only a total of six different log files. [cid:4b28ae60-c42a-4cd4-a063-49431d8b5334] I have attached a sample of my globals.yml, multinode, zun-api and compute-api log file in this email. The below image is a sample of how I setup my openstack as shown below. [cid:8cc989cd-b334-4647-8084-048b499e229e] The below image is the reference of my local network. My controller [cid:6e322de9-216e-48c6-b0a2-7cd3f2465ba1] [cid:4695cd8c-a01c-45b5-9523-e9b9f95a9ebc] [cid:0426c49b-701d-4a9b-aadc-ea9353840f66] [cid:f1e89ed4-fc88-4679-bcb5-0150bef1fd7a] [cid:51c37875-f354-4f18-8a83-619ddb2c19d5] My compute host [cid:aad2498a-52f7-4f81-9c57-cdb49f52de4c] [cid:83c1a81e-342a-4ec0-9d94-c73753152087] Hope to hear from everyone soon. Best regards, Vincent

2 1

[nova] Could I boot instance from volume snapshot in cmd?
by 韩光宇 29 Aug '22

29 Aug '22

Hello, I want boot instance from volume snapshot in cmd, but I never found it in `openstack server create --help` and https://docs.openstack.org/nova/latest/user/launch-instances.html. Could I do it in cmd? I saw that this can be done on horizon Thanks, Han Guangyu

2 1

[heat] ERROR: You are not authorized to use stacks:global_index.
by Boxiang Zhu 28 Aug '22

28 Aug '22

Hi, I deployed the openstack with kolla-ansible. And the openstack_release of globals.yml is master. The version of openstackclient and heatclient is 5.8.0 and 3.0.0. I run command "source /etc/kolla/admin-openrc.sh" to export env of openstack. OS_PROJECT_DOMAIN_NAME=Default OS_USER_DOMAIN_NAME=Default OS_PROJECT_NAME=admin OS_TENANT_NAME=admin OS_USERNAME=admin OS_PASSWORD=xxxxxxxxx OS_AUTH_URL=http://192.168.100.10:5000 OS_INTERFACE=internal OS_ENDPOINT_TYPE=internalURL OS_MANILA_ENDPOINT_TYPE=internalURL OS_IDENTITY_API_VERSION=3 OS_REGION_NAME=RegionOne OS_AUTH_PLUGIN=password Then I try to list all stacks with command "openstack stack list --all-projects". But I got the error messages as followed: ERROR: You are not authorized to use stacks:global_index. I see the policy is "role:reader and system_scope:all". I think the user admin has role reader and also with system_scope:all. ❯ openstack role assignment list +----------------------------------+----------------------------------+-------+----------------------------------+----------------------------------+--------+-----------+ | Role | User | Group | Project | Domain | System | Inherited | +----------------------------------+----------------------------------+-------+----------------------------------+----------------------------------+--------+-----------+ | cd572da356fb4f7ca53c280802299eb0 | fccbdf34d33a407db1b53bed048d1187 | | 840500fb441a442fbcbca30d3a773b2c | | | False | | cd572da356fb4f7ca53c280802299eb0 | 70d3715e7e2246c08c901d0e96038443 | | | 0a6274ff7f994e8cb6f40e13b0d39ca2 | | False | | cd572da356fb4f7ca53c280802299eb0 | 5c100e870cbd4744af6e546fc9215a37 | | | | all | False | +----------------------------------+----------------------------------+-------+----------------------------------+----------------------------------+--------+-----------+ ❯ openstack user show admin +---------------------+----------------------------------+ | Field | Value | +---------------------+----------------------------------+ | domain_id | default | | enabled | True | | id | 5c100e870cbd4744af6e546fc9215a37 | | name | admin | | options | {} | | password_expires_at | None | +---------------------+----------------------------------+ How can I get all the stacks for all projects? Thanks, Best Regards, Boxiang Zhu

2 1

What is the Traffic Flow between Horizon and Swift?
by John van Ommen 28 Aug '22

28 Aug '22

When a user is using Horizon, and they're examining the contents of their containers in Swift, what does the traffic flow look like? I am unable to browse the contents of my Swift containers from Horizon. When I click on the contents of the container I get: "Unable to get the objects in the container" And when I click on the "Services" tab in Horizon, I get: "Unable to get Nova services list" and "Unable to get Cinder services list" John van Ommen

1 0

[Wallaby] Deployment getting failed Randomly
by Lokendra Rathour 27 Aug '22

27 Aug '22

Hi Team, we were trying to deploy OpenStack wallaby, and we see that 4 out of 5 runs deployment is getting failed for mentioned below reasons: *Error:* 2022-08-25 17:34:29.036371 | 5254004d-021e-d4db-067d-000000007b1a | TASK | Create identity internal endpoint 2022-08-25 17:34:31.176105 | 5254004d-021e-d4db-067d-000000007b1a | FATAL | Create identity internal endpoint | undercloud | error={"changed": false, "extra_data": {"data": null, "details": "The request you have made requires authentication.", "response": "{\"error\":{\"code\":401,\"message\":\"The request you have made requires authentication.\",\"title\":\"Unauthorized\"} }\n"}, "msg": "Failed to list services: Client Error for url: overcloud-public.myhsc.com <https://overcloud-public.myhsc.com:13000/v3/services> :13000/v3/services <https://overcloud-public.myhsc.com:13000/v3/services>, The request you have made requires authentication."} Debug logs: pending results.... The full traceback is: File "/tmp/ansible_openstack.cloud.endpoint_payload_qhlqb_qw/ansible_openstack.cloud.endpoint_payload.zip/ansible_collections/open stack/cloud/plugins/module_utils/openstack.py", line 407, in __call__ results = self.run() File "/tmp/ansible_openstack.cloud.endpoint_payload_qhlqb_qw/ansible_openstack.cloud.endpoint_payload.zip/ansible_collections/open stack/cloud/plugins/modules/endpoint.py", line 150, in run File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 537, in get_service return _utils._get_entity(self, 'service', name_or_id, filters) File "/usr/lib/python3.6/site-packages/openstack/cloud/_utils.py", line 197, in _get_entity entities = search(name_or_id, filters, **kwargs) File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 517, in search_services services = self.list_services() File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 501, in list_services error_message="Failed to list services") File "/usr/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 395, in get return self.request(url, 'GET', **kwargs) File "/usr/lib/python3.6/site-packages/openstack/proxy.py", line 668, in request return _json_response(response, error_message=error_message) File "/usr/lib/python3.6/site-packages/openstack/proxy.py", line 646, in _json_response exceptions.raise_from_response(response, error_message=error_message) File "/usr/lib/python3.6/site-packages/openstack/exceptions.py", line 238, in raise_from_response http_status=http_status, request_id=request_id 2022-08-25 19:38:03.201899 | 5254004d-021e-7578-cd65-000000007ad6 | FATAL | Create identity internal endpoint | undercloud | er ror={ "changed": false, "extra_data": { "data": null, "details": "The request you have made requires authentication.", "response": "{\"error\":{\"code\":401,\"message\":\"The request you have made requires authentication.\",\"title\":\"Unautho rized\"}}\n" }, "invocation": { "module_args": { "api_timeout": null, "auth": null, "auth_type": null, "availability_zone": null, "ca_cert": null, "client_cert": null, "client_key": null, "enabled": true, "endpoint_interface": "internal", "interface": "public", "region": "regionOne", "region_name": null, "service": "keystone", "state": "present", "timeout": 180, "url": "http://[fd00:fd00:fd00:2000::368]:5000", "validate_certs": null, "wait": true } }, "msg": "Failed to list services: Client Error for url: https://overcloud-public.myhsc.com:13000/v3/services, The request you have made requires authentication." } DeployCommand that was used: openstack overcloud deploy --templates \ -r /home/stack/templates/roles_data.yaml \ -n /home/stack/templates/custom_network_data.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ptp.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-dns.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/inject-trust-anchor-hiera.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/external-ceph.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/templates/overcloud-baremetal-deployed.yaml \ -e /home/stack/templates/networks-deployed-environment.yaml \ -e /home/stack/templates/vip-deployed-environment.yaml \ -e /home/stack/templates/environment.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /home/stack/templates/enable-tls.yaml \ -e /home/stack/templates/cloudname.yaml \ -e /home/stack/templates/my-additional-ceph-settings.yaml \ -e /home/stack/containers-prepare-parameter.yaml [Issue] we are seeing the deployment is working perfectly once and the same setting is not working perfectly in the second run. the failure rate is high. what can be the reasons behind this? *Note:* Before this, we were deploying with DNS and SSL and it was perfectly working fine in multiple reruns. But after SSL we have seen this random failure. -- ~ Lokendra skype: lokendrarathour

1 1

question about skyline apiserver and console
by mahdi n 27 Aug '22

27 Aug '22

Hello, I want to install ui skyline but I don't know how to install Does the first install the skyline api server next console? or only install skyline console ui? where must I set the keystone url ? skyline have not docs fir develop please help

3 3

[all][tc] What's happening in Technical Committee: summary 2022 Aug 26: Reading: 5 min
by Ghanshyam Mann 27 Aug '22

27 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 25. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-25-15.00.log.html * Next TC weekly meeting will be on Sept 1 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 31. 2. What we completed this week: ========================= * Retired openstack-helm-addons[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Six open reviews for ongoing activities[4]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- Nomination for the technical election (PTL and Technical Committee) are open now[5]. We are 1 week delay in election so as per TC charter we are adding this delay as exception[6]. Request you to add your nomination before Aug 31 and also ping anyone you know is interested in the PTL or TC position. Define 2023.1 cycle testing runtime ------------------------------------------- I have proposed the testing runtime for the 2023.1 cycle[7], please review and feedback if any. 2023.1 cycle TC PTG planning ------------------------------------ I have started the PTG planning for the TC sessions. * Similar to last coupe of PTG, we are planning "TC + Leader interaction" sessions[8], please vote your available day/time in poll[8]. * I have created the etherpad[10] to collect the TC slots topics and poll to select the TC slot timing[11]. * As you know, we are planning 'Operator Hours' in this PTG where developer and operator and meet for an hour to discuss/feedback. There is a poll to know if operator want to join developer PTG slot of interested to have their own space and let developer jump in there for discussion[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [14] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]16]. Project updates ------------------- * Switch requirements to distributed leadership[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 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/851859 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030094.… [6] https://review.opendev.org/c/openstack/governance/+/854624 [7] https://review.opendev.org/c/openstack/governance/+/854375 [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030108.… [9] https://framadate.org/zsOqRxfVcmtjaPBC [10] https://etherpad.opendev.org/p/tc-2023-1-ptg [11] https://framadate.org/yi8LNQaph5wrirks [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030114.… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://review.opendev.org/c/openstack/governance/+/849606 [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [17] https://review.opendev.org/c/openstack/governance/+/854685 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-5, Aug 29 - Sep 02
by Előd Illés 27 Aug '22

27 Aug '22

Development Focus ----------------- We are getting close to the end of the Zed cycle! Next week on September 1st, 2022 is the Zed-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2023.1 Antelope cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on September 1st, 2022. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/zed branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… September 1st, 2022 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Zed-3 milestone (feature freeze): September 1st, 2022 (R-5 week) RC1 deadline: September 15th, 2022 (R-3 week) Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[Nova] Can't Attach An Encrypted NFS (luksv1) Volume
by Sofia Enriquez 27 Aug '22

27 Aug '22

Hello Nova Team, eharney and I are working on NFS encrypted volume support [1] and [2]. I'm trying to attach an encrypted volume to a nova instance. However, this fails with "libvirt.libvirtError: internal error: unable to execute QEMU command 'blockdev-add': Image is not in qcow2 format" error. I'm using a Devstack environment (nova/cinder master branch). Last week I opened a bug report [3] and I'd like to raise some attention to it. I've proposed a WIP patch [4] with a possible solution that I'd like to get some feedback on or know if should follow a different approach. The problem is that is_luks() returns false for the NFS case, because NFS is using LUKS inside of qcow2 and not regular LUKS. Let me know what you think Thank you Sofia [1] https://review.opendev.org/c/openstack/cinder/+/597148 [2] https://review.opendev.org/c/openstack/cinder/+/749155 [3] https://bugs.launchpad.net/nova/+bug/1987311 [4] https://review.opendev.org/c/openstack/nova/+/854030 -- 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

[charms][elections] PTL candidacy for Antelope cycle
by Alex Kavanagh 26 Aug '22

26 Aug '22

Hi All I would like to put myself forward for another cycle for the Charms PTL for the Antelope cycle. I've been a contributor to OpenStack and Charms since 2016 and a core member since mid 2016. I've also been the PTL for the last 2 cycles. Why do I want to be PTL again? The team has again achieved a huge amount, testing and supporting the charms and packages across multiple Ubuntu LTS releases (bionic, focal and now, jammy) with Charms and OpenStack support back to queens. We've (almost) transitioned to the new Charmhub ( charmhub.io) and will continue to support Queens through to the upcoming Zed release, and onto Antelope. I'd like to continue to support the team as we march forward with the responsibilities of the PTL to smooth the processes. Thanks Alex (tinwood) -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

[Glance] PTL non-candidacy
by Abhishek Kekane 26 Aug '22

26 Aug '22

Hi all, I'm writing this email to let you know that I'm not going to run for Glance PTL for the Antelope dev cycle, I think it's time for some new ideas and new approaches so it's a good idea to hand over the hat of PTL to a new member of the team. I've been serving Glance PTL since Ussuri, tried my best to keep Glance stable, lots of changes have been made since then, my initial focus was to improve glance-tempest coverage which we managed to do in past cycles. I would like to thank all the members of the Glance team and others for supporting me during this period. My plan is to stick around, attend to my duties as a glance core contributor, and support my successor in whatever way I can to make for a smooth transition. Thank you once again! Cheers, Abhishek Kekane

4 3

[kuryr][elections] PTL candidacy for Antelope cycle
by Roman Dobosz 26 Aug '22

26 Aug '22

Hello, I would like to announce my candidacy to be the Kuryr PTL for the next Antelope cycle. I've been Kuryr contributor since the Ussuri release and became core reviewers member at the end of Victoria cycle. In the upcoming Antelope cycle, I'd like to focus on Kuryr stability and compatibility with upcoming Kubernetes release. Another thing which I'd like to move forward is to eliminate Kuryr services restarts. Thanks, Roman Dobosz (gryf)

1 0

[election][heat][ptl] PTL non-candidacy
by Rico Lin 26 Aug '22

26 Aug '22

Hi all, As the PTL election will soon start, I would like to share my statement on not planning to run another term of Heat PTL. And instead, I encourage anyone (core reviewer or not) who is interested to put their name on. I will definitely still stay around and help with reviews and patches. *Rico Lin*

2 1

Regarding Designate Installation in ansible Playbook
by Adivya Singh 26 Aug '22

26 Aug '22

hi Team, I have made under conf.d a designate. yml file, and rerunning the setup of Openstack-setuphost but still it is not installing a Designate Container in OpenStack. Is there any Reason for this, Something i am doing right Regards Adivya Singh

2 1

[OPS] Participation Poll for OPS Meetup at the PTG
by Amy Marrich 25 Aug '22

25 Aug '22

Hey all, Just putting this on the list for more visibility. On Monday we posted a poll from the OPS Meetup Twitter account for how Operators would prefer to interact with the Developers[0]. The poll closes on Monday but if you don't have twitter please reply here with your preference. We also have a poll for preferred times[1] Thanks, Amy 0 - https://twitter.com/osopsmeetup/status/1561708280455593984 1 - https://doodle.com/meeting/participate/id/bD9kR2yd

1 0

[neutron] Drivers meeting agenda - 26.08.2022.
by Lajos Katona 25 Aug '22

25 Aug '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFEs to discuss tomorrow: * [RFE] Add a port extension to set/define the switchdev capabilities (#link https://bugs.launchpad.net/neutron/+bug/1987093 ) * [RFE] Add DSCP mark 44 (#link https://bugs.launchpad.net/neutron/+bug/1987378 ) And we have a topic for the On Demand agenda: * (amorin): Add new novaplug mechanism driver ** https://bugs.launchpad.net/neutron/+bug/1986969 ** https://review.opendev.org/c/openstack/neutron/+/854553 [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

DCN and DVR in Openstack wallaby | tripleo
by Swogat Pradhan 25 Aug '22

25 Aug '22

Hi, I have a site1 and a site2. Site1 contains the controller nodes with some compute and storage and in site2 i have compute nodes maybe hci solution for it. site1 has a different network pool and site2 has a different network pool and these cannot be extended to one another. What I want to know is how I am going to configure network to be used by the compute nodes in site2. If i use DVR then i can just create a normal external network which will only be used for site2 and then the traffic doesn't have to go through the network node. Is it the right solution? And is DVR enabled by default or do I have to use the neutron-ovn-dvr.yaml template? And if i use DVR do i have to set the following parameter?: ComputeParameters: NeutronBridgeMappings: "" Is DCN with DVR the correct approach? With regards, Swogat Pradhan

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Aug 25 at 1500 UTC
by Ghanshyam Mann 25 Aug '22

25 Aug '22

Hello Everyone, Below is the agenda for Tomorrow's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** Schedule 'operator hours' as a separate slot in PTG(avoiding conflicts among other projects 'operator hours') * 2023.1 cycle Technical Election * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

container and instances are not working on my dashboard
by Lee, Vincent Z 25 Aug '22

25 Aug '22

Hi all, I am quite new to Openstack and faced some issues with creating instances and displaying created containers on my Openstack dashboard. I am currently working on multinode Openstack. I am hoping to get some helps and feedbacks about this. I will briefly go through the problems I encountered. When I created an instances on my dashboard, it directly went into error state. I have attached a screenshot as shown below. [cid:c1615736-e4b3-4100-99c0-dfb970ff365f] This is my list of hosts. [cid:8d2f9138-27fd-4cf5-95ca-0cd9038f723c] When I created a container using both cli and dashboard, two containers were running. However, when I tried to look into my dashboard, those containers were not shown. These are the created containers. [cid:61d517f2-c60a-4892-bf88-1a9e0d763b7f] However, when i try to open my dashboard and look for them, they just don't appear on it. So I am not sure what is causing this. [cid:fb9d0f7e-1afa-48c1-bc92-9c8054382b55] Hope to hear from everyone soon. Best regards, Vincent

3 2

[all][elections][ptl][tc] Combined PTL/TC Antelope cycle Election Nominations Kickoff
by Amy Marrich 25 Aug '22

25 Aug '22

Apologies all for the lack of notice to the start of the PTL/TC election season. Unfortunately we are starting late and we are attempting to get back on schedule. We will make sure we send out a reminder notice (or two) for nominations closing. Remember we can't do this without your nominations and folks being willing to lead the projects and the community ======================================================================== Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until Aug 31, 2022 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/antelope/<Project_Name or "TC">/<email_address> (for example, "candidates/antelope/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Sep 07, 2022 23:45 UTC through to Sep 14, 2022 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Aug 24, 2022 23:45 UTC PTL + TC nomination ends @ Aug 31, 2022 23:45 UTC TC campaigning starts @ Aug 31, 2022 23:45 UTC TC campaigning ends @ Sep 07, 2022 23:45 UTC PTL + TC elections start @ Sep 07, 2022 23:45 UTC PTL + TC elections end @ Sep 14, 2022 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2022-08-31 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 0

[TripleO] Derived Parameters going away
by John Fulton 25 Aug '22

25 Aug '22

It seems this feature was not widely adopted so the current maintainers would like to remove it. We have a proposed patch [1] to remove it from the main branch so it won't be in the TripleO release which accompanies Zed. It's presently in the release which accompanies Wallaby. Note that TripleO is using the independent release model [2]. What is the "Derived Parameters" feature? NFV and HCI overclouds require system tuning. There are formulas which output tuning parameters based on hardware. These parameters may then be provided as input to TripleO to deploy a tuned overcloud. There is an additional method of system tuning called “derived parameters” where TripleO uses inspected hardware data as input and automatically sets tuning parameters [3]. Removing this feature shouldn't block anyone since they can still deploy a tuned overcloud by providing standard parameters. There's also a docs patch [4] explaining how to migrate away from derived to standard parameters. John [1] https://review.opendev.org/q/topic:derive-parameters-cleanup [2] https://review.opendev.org/c/openstack/tripleo-specs/+/801512 [3] https://specs.openstack.org/openstack/tripleo-specs/specs/pike/tripleo-deri… [4] https://review.opendev.org/c/openstack/tripleo-docs/+/854443

1 0

OpenInfra Live - August 25 at 1400 UTC
by Allison Price 25 Aug '22

25 Aug '22

Hi everyone, This week’s OpenInfra Live episode is brought to you by members of the OpenStack community. Episode: Making VDI a first-class citizen in the OpenStack world Learn the importance of having a Virtual Desktop Infrastructure (VDI) with OpenStack. Get to know the VDI use cases. Discover which relevant features are already integrated and which are still missing. You’ll also have the opportunity to meet Bumblebee and enjoy the cute flying insect during a demo! Date and time: Thursday, August 25 at 1400 UTC (9am CT) You can watch us live on: YouTube: https://www.youtube.com/watch?v=juczRNlfg6c <https://www.youtube.com/watch?v=juczRNlfg6c> LinkedIn: https://www.linkedin.com/video/event/urn:li:ugcPost:6966050226767884289/ <https://www.linkedin.com/video/event/urn:li:ugcPost:6966050226767884289/> Facebook: https://www.facebook.com/104139126308032/posts/5359387687449790/ <https://www.facebook.com/104139126308032/posts/5359387687449790/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Manuel Bentele Andy Botting Radosław Piliszek Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. See you there! Allison

1 0

[neutron][ovn] Gauging community interest in supporting a masquerading forwarding DNS resolver for isolated tenant networks
by Miguel Lavalle 25 Aug '22

25 Aug '22

Hi, As described in this Launchpad bug https://bugs.launchpad.net/neutron/+bug/1902950, in contrast with ML2 / OVS, with ML2 / OVN there is not a masquerading forwarding DNS resolver available to instances on isolated tenant networks. The purpose of this message is to gather feedback from the community as to how much interest there is in providing this functionality under ML2 / OVN. If your organization has interest, please respond to this thread. Even better, register your interest on the topic in the etherpad for the upcoming Antelope PTG (https://etherpad.opendev.org/p/neutron-antelope-ptg) under the "Check of interest on closing ML2/OVN DNS gaps" topic. And of course, attend the conversation in October Best regards Miguel Lavalle

1 0

(no subject)
by ralonsoh＠redhat.com 24 Aug '22

24 Aug '22

The original message was received at Wed, 24 Aug 2022 22:48:10 +0900 from redhat.com [7.150.121.148] ----- The following addresses had permanent fatal errors ----- <openstack-discuss(a)lists.openstack.org>

1 0

High memory use with RabbitMQ on RHEL9 hosts
by Marcin Juszkiewicz 24 Aug '22

24 Aug '22

If you run RabbitMQ on RHEL9 family hosts (CentOS Stream 9, RockyLinux 9, AlmaLinux 9) and you see 1.6GB memory use then consider limiting amount of file descriptors: > EL9 (both CentOS Stream 9 and Rocky Linux 9) have 1073741816 while > CentOS Stream 8 has 1048576 - after lowering it's acceptable > memory usage. https://github.com/rabbitmq/erlang-rpm/discussions/104 for more

1 0

[cinder] Bug deputy report for week of 08-24-2022
by Sofia Enriquez 24 Aug '22

24 Aug '22

This is a bug report from 08-17-2022 to 08-24-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1982945 "[docs] Cannot start VM from disk with burst QoS." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1900406 "RBD support extends for in-use volume." Unassigned. Cheers, Sofia -- 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

[octavia] Help with fix barbican client in octavia when use trust-scoped token
by Ришат Азизов 24 Aug '22

24 Aug '22

Hello! I have error with terminated https loadbalancer, it described here: https://storyboard.openstack.org/#!/story/2007619 Could you please help with fix for barbican client? Thank you.

3 3

Re: ovn-bgp-agent installation issue
by Satish Patel 24 Aug '22

24 Aug '22

Hi Luis, /cc - openstack discuss mailing list Thank you so much for clearing my doubts. I have a counter question. BGP Mode: - In bgp mode where i should run ovn-bgp-agent ? Network node or Compute node? EVPN Mode: - In evpn mode where i should run ovn-bgp-agent? - In my lab i am using your heck "How to use it without BGPVPN" to create vni mapping, do you think because of that i am not seeing vni pushed out to FRR automatically? https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/ - In your demo link I can see you have bridge two different deployment clouds using the same VNI, In this scenario we need a router (or vrf) somewhere correct to bridge to different subnet IPs, correct? or is this L2 stretch? I am going to open a new thread to discuss issues related to expose_tenant_networks=True flag issue. On Tue, Aug 23, 2022 at 3:14 AM Luis Tomas Bolivar <ltomasbo(a)redhat.com> wrote: > Hi Satish! See inline > > On Mon, Aug 22, 2022 at 5:22 PM Satish Patel <satish.txt(a)gmail.com> wrote: > >> Hi Luis, >> >> Welcome back from your vacation, sorry i didn't know you are on vacation. >> Hope you had a wonderful time. >> >> How do i start conversion on opendev thread? is there a mailing list or >> are you saying open thread here - >> https://storyboard.openstack.org/#!/project/x/ovn-bgp-agent >> > > Actually, you did it right (sending it to openstack-discuss), but it seems > at some point we stop adding it on our replies... probably my fault due to > replying on the phone while on vacation. > > For the next issue we can open a different thread and I'll try not to drop > the openstack-discuss list! xD > > It would be great though if you can sent a follow up to the previous > thread with the final outcome (fixed by updating, or adding config X, ..), > so that community can see the project is alive, and other people facing > similar issues can try your solution/config. > >> I have an update for you, after upgrading the OVN/OVS version to the >> latest and that resolved lots of issues. As you mentioned earlier running >> the latest code is very important to get proper functionality. >> > > Awesome! Yeah, it is a new project, so functionality/fixes are being added > regularly, therefore using the latest version is the best approach. The > plan is to soon create a more stable version/release, once we have enough > testing coverage and main functionality covered > >> >> You are saying in BGP mode only FIP will get exposed but not the tenant >> VM ( What is this flag for expose_tenant_network=True ?) >> > > Main idea was: > - BGP mode for exposing VMs/LBs on provider networks, or with FIPs attached > - EVPN mode for tenant networks > > To give you some more context, we started with the BGP mode, and did the > expose_tenant_network to expose also tenant IPs. However, the BGP mode is > lacking an API to decide what to expose. So we moved to the EVPN mode (with > networking-bgpvpn as the API) to expose the tenant networks. > > That said, you are right, and the expose_tenant_network flag is intended > for the BGP mode, to expose all tenant networks (so you need to ensure no > overlapping CIDRs). And, if that is not working (it may be, as there is no > testing coverage for it), it is something we can definitely look at and > fix. So, feel free to open a new thread on openstack-discuss, or bug in > storyboard (whatever works for you better), and I'll try to fix asap. > > >> >> You are saying in EVPN mode only tenant VM ip will get exposed but not >> FIP but in this design what is the use of getting tenant VM exposed but you >> can't expose FIP then how does external people access VMs? ( I am totally >> confused in EVPN design and use case because your tenant VM is already >> talking to each other using geneve tunnel so why do we need EVPN/L2VPN to >> expose them?) >> > > EVPN mode is indeed only for tenant VMs (and loadbalancer). Idea for this > mode is to connect (N/S traffic, as you mention E/W is still using the > normal geneve path) tenant networks between different OpenStack clusters. > EVPN will create a vxlan tunnel connecting them. So, the vni/vxlan id > selected (with networking-bgpvpn) is the vxlan tunnel encap id being used > to connect both tenant networks. > > So, the idea behind the EVPN mode is not to make your VMs in a tenant > network publicly accessible, but being able to access them from a different > tenant network in a different cloud (it actually does not need to be an > OpenStack cloud, anything connected to the same vxlan id. Perhaps this is a > bit more clear in this demo: > https://ltomasbo.wordpress.com/2021/10/01/ovn-bgp-agent-interconnecting-kub… > > >> >> This is current status of my LAB >> >> ovn-bgp-agent in BGP Mode: >> I am successfully able to expose FIP and provider IPs (as you mentioned) >> but when i use expose_tenant_network=True in config then getting error and >> vm tenant ips not getting exposed to bgp so i am not sure what is the use >> case of that flag. >> > > Yep, most probably we broke something here due to lack of upstream testing > for this flag. I'll check asap and try to fix it > >> >> ovn-bgp-agent in EVPN Mode: >> In this mode everything is working and tenant vm also gets exposed but >> when I attach FIP to vm those FIP ip are not getting exposed in BGP (as you >> mentioned in your reply). >> > Yes, EVPN mode is not intended for FIPs or VMs on provider networks. Only > for tenants > > >> But i am seeing one bug here where vni config not getting inserted in FRR >> https://opendev.org/x/ovn-bgp-agent/src/branch/master/ovn_bgp_agent/drivers… >> >> >> Who will trigger that code and when will that code get triggered to >> configure FRR for vrf/vni ? >> > > This is being added by networking-bgpvpn. You can see some details about > the integration into my blogpost ( > https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/) > or in the upstream documentation: > https://opendev.org/x/ovn-bgp-agent/src/branch/master/doc/source/contributo… > > Note though, to make networking-bgpvpn to work with this integration, this > patch is needed (which btw I should include into the documentation): > https://review.opendev.org/c/openstack/networking-bgpvpn/+/803161 > > Cheers, > Luis > > >> >> >> >> >> >> On Mon, Aug 22, 2022 at 5:44 AM Luis Tomas Bolivar <ltomasbo(a)redhat.com> >> wrote: >> >>> Hi Satish, >>> >>> Sorry I was on vacation. Trying to get through my inbox. >>> >>> I'm not sure what is the current status, note there is a difference >>> between EVPN and BGP mode. BGP mode is for FIPs and VMs/LBs on the provider >>> network or with FIPs, while EVPN is for VMs on the tenant networks, without >>> FIPs. Right now you cannot mix them and need to choose either EVPN or BGP >>> mode. I'm planning to give it a try to make it multidriver, but I haven't >>> even started yet. >>> >>> BTW, as you did with the initial email, perhaps it is worth to have >>> conversations on the opendev thread, so that anyone else facing the same >>> issues can get some hints (or even provide feedback), that was one of the >>> main ideas about moving it in there. To be able to have better support. >>> >>> As for the questions: >>> # # on rack-2-host-1 >>> # when i created vm1 which endup on rack-2-host-1 but it doesn't expose >>> the vm ip address. Is that normal behavior? >>> >>> This should be exposed in the node with cr-lrp port, i.e., rack1-host2, >>> and it should be as simple as adding the IP to the lo-2001 dummy device >>> >>> # When I attach a floating ip to vm2 then why does my floating ip >>> address not get exposed in BGP? >>> This is what I mentioned before, you cannot merge BGP and EVPN mode. >>> >>> On Mon, Aug 8, 2022 at 1:41 PM Satish Patel <satish.txt(a)gmail.com> >>> wrote: >>> >>>> Hi Luis, >>>> >>>> Sorry for bugging. I’m almost there now. Do you have any thought of >>>> following question >>>> >>>> Sent from my iPhone >>>> >>>> On Aug 5, 2022, at 1:16 AM, Satish Patel <satish.txt(a)gmail.com> wrote: >>>> >>>> >>>> Good morning Luis, >>>> >>>> Quick question, I have following deployment as per your lab >>>> >>>> rack-1-host-1 (controller) >>>> rack-1-host-2 (compute1 - This is hosting cr-lrp ports, inshort router) >>>> rack-2-host-1 (compute2) >>>> >>>> I have created two vms >>>> >>>> vagrant@rack-1-host-1:~$ nova list >>>> nova CLI is deprecated and will be a removed in a future release >>>> >>>> +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ >>>> | ID | Name | Status | Task State | >>>> Power State | Networks | >>>> >>>> +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ >>>> | aecb4f10-c46f-4551-b112-44e4dc007e88 | vm1 | ACTIVE | - | >>>> Running | private-test=10.0.0.105 | >>>> | ceae14b9-70c2-4dbc-8071-0d64d9a0ca84 | vm2 | ACTIVE | - | >>>> Running | private-test=10.0.0.86, 172.16.1.200 | >>>> >>>> +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ >>>> >>>> # on rack-1-host-2 >>>> when i spun up vm2 which endup on rack-1-host-2 hence it created >>>> vrf-2001 on dummy lo-2001 interface and exposed vm2 ip address >>>> 10.0.0.86/32 >>>> >>>> 96: vrf-2001: <NOARP,MASTER,UP,LOWER_UP> mtu 65575 qdisc noqueue state >>>> UP group default qlen 1000 >>>> link/ether 22:cc:25:b3:7b:96 brd ff:ff:ff:ff:ff:ff >>>> 97: br-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>> master vrf-2001 state UP group default qlen 1000 >>>> link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff >>>> inet6 fe80::851:67ff:fe64:b2c3/64 scope link >>>> valid_lft forever preferred_lft forever >>>> 98: vxlan-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc >>>> noqueue master br-2001 state UNKNOWN group default qlen 1000 >>>> link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff >>>> inet6 fe80::8c3:23ff:fe7a:8f0c/64 scope link >>>> valid_lft forever preferred_lft forever >>>> 99: lo-2001: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>> master vrf-2001 state UNKNOWN group default qlen 1000 >>>> link/ether d6:60:da:91:2e:6d brd ff:ff:ff:ff:ff:ff >>>> inet 10.0.0.86/32 scope global lo-2001 >>>> valid_lft forever preferred_lft forever >>>> inet6 fe80::d460:daff:fe91:2e6d/64 scope link >>>> valid_lft forever preferred_lft forever >>>> >>>> >>>> # on rack-2-host-1 >>>> when i created vm1 which endup on rack-2-host-1 but it doesn't expose >>>> the vm ip address. Is that normal behavior? >>>> >>>> When I attach a floating ip to vm2 then why does my floating ip address >>>> not get exposed in BGP? >>>> >>>> Thank you in advance >>>> >>>> >>>> On Thu, Aug 4, 2022 at 2:30 PM Satish Patel <satish.txt(a)gmail.com> >>>> wrote: >>>> >>>>> Update: Good news, I found what was wrong. >>>>> >>>>> After adding AS it works. In your doc you only added VNI but look like >>>>> it is required to add BGP AS. Or may be your doc is little older and new >>>>> code required AS. >>>>> >>>>> vagrant@rack-1-host-1:~$ sudo ovn-nbctl set logical_switch_port >>>>> c32dcd90-7820-44bd-894f-416e44b36aa0 external_ids:"neutron_bgpvpn\:as"=64999 >>>>> vagrant@rack-1-host-1:~$ sudo ovn-nbctl set logical_switch_port >>>>> f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81 external_ids:"neutron_bgpvpn\:as"=64999 >>>>> >>>>> Now i can see it created VRF and exposed VM tenant ip in lo-2001 >>>>> >>>>> 73: vrf-2001: <NOARP,MASTER,UP,LOWER_UP> mtu 65575 qdisc noqueue state >>>>> UP group default qlen 1000 >>>>> link/ether b2:29:65:3b:ac:db brd ff:ff:ff:ff:ff:ff >>>>> 74: br-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>>> master vrf-2001 state UP group default qlen 1000 >>>>> link/ether d6:0d:61:2d:b7:29 brd ff:ff:ff:ff:ff:ff >>>>> inet6 fe80::6830:47ff:febc:b10b/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> 75: vxlan-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc >>>>> noqueue master br-2001 state UNKNOWN group default qlen 1000 >>>>> link/ether d6:0d:61:2d:b7:29 brd ff:ff:ff:ff:ff:ff >>>>> inet6 fe80::d40d:61ff:fe2d:b729/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> 76: lo-2001: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>>> master vrf-2001 state UNKNOWN group default qlen 1000 >>>>> link/ether fe:a1:a0:87:76:7c brd ff:ff:ff:ff:ff:ff >>>>> inet 10.0.0.83/32 scope global lo-2001 >>>>> valid_lft forever preferred_lft forever >>>>> inet6 fe80::fca1:a0ff:fe87:767c/64 scope link >>>>> >>>>> >>>>> I am continuing doing testing and seeing if I hit any other bug.. >>>>> >>>>> On Thu, Aug 4, 2022 at 11:58 AM Satish Patel <satish.txt(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Luis, >>>>>> >>>>>> I am following your doc, tell me if that doc is outdated or not >>>>>> https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/ >>>>>> >>>>>> I have upgraded pyroute2 to 0.7.2 but still getting the same error, >>>>>> if you look at carefully following logs you will see an agent saying I >>>>>> can't find VNI but it's there, i can see in ovn-nbctl list >>>>>> logical_switch_port. >>>>>> >>>>>> pyroute2 0.7.2 >>>>>> pyroute2.core 0.6.13 >>>>>> pyroute2.ethtool 0.6.13 >>>>>> pyroute2.ipdb 0.6.13 >>>>>> pyroute2.ipset 0.6.13 >>>>>> pyroute2.ndb 0.6.13 >>>>>> pyroute2.nftables 0.6.13 >>>>>> pyroute2.nslink 0.6.13 >>>>>> >>>>>> >>>>>> ovn-bgp-agent logs >>>>>> >>>>>> 2022-08-04 15:52:52.898 396714 DEBUG >>>>>> ovn_bgp_agent.drivers.openstack.utils.ovn [-] Either "neutron_bgpvpn:vni" >>>>>> or "neutron_bgpvpn:as" were not found or have an invalid value in the port >>>>>> f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81 external_ids {'neutron:cidrs': ' >>>>>> 172.16.1.132/24', 'neutron:device_id': >>>>>> '43b2c756-d92c-4fe5-b17b-32d5ab9b1f37', 'neutron:device_owner': >>>>>> 'network:router_gateway', 'neutron:network_name': >>>>>> 'neutron-0d82e6b0-bf9f-484d-85bd-0ba38aab508d', 'neutron:port_name': '', >>>>>> 'neutron:project_id': '', 'neutron:revision_number': '4', >>>>>> 'neutron:security_group_ids': '', 'neutron_bgpvpn:vni': '2001'} >>>>>> get_evpn_info >>>>>> /usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/utils/ovn.py:251 >>>>>> >>>>>> 2022-08-04 15:52:52.899 396714 DEBUG >>>>>> ovn_bgp_agent.drivers.openstack.ovn_evpn_driver [-] No EVPN information for >>>>>> CR-LRP Port with IPs ['172.16.1.132/24']. Not exposing it. >>>>>> _expose_ip >>>>>> /usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/ovn_evpn_driver.py:220 >>>>>> >>>>>> >>>>>> In OVN i can see vni number >>>>>> >>>>>> _uuid : 3473d0ce-1348-4423-a2dc-6d4df4c06f74 >>>>>> addresses : [router] >>>>>> dhcpv4_options : [] >>>>>> dhcpv6_options : [] >>>>>> dynamic_addresses : [] >>>>>> enabled : true >>>>>> external_ids : {"neutron:cidrs"="172.16.1.132/24", >>>>>> "neutron:device_id"="43b2c756-d92c-4fe5-b17b-32d5ab9b1f37", >>>>>> "neutron:device_owner"="network:router_gateway", >>>>>> "neutron:network_name"=neutron-0d82e6b0-bf9f-484d-85bd-0ba38aab508d, >>>>>> "neutron:port_name"="", "neutron:project_id"="", >>>>>> "neutron:revision_number"="4", "neutron:security_group_ids"="", >>>>>> "neutron_bgpvpn:vni"="2001"} >>>>>> ha_chassis_group : [] >>>>>> name : "f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81" >>>>>> options : {exclude-lb-vips-from-garp="true", >>>>>> nat-addresses=router, router-port=lrp-f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81} >>>>>> parent_name : [] >>>>>> port_security : [] >>>>>> tag : [] >>>>>> tag_request : [] >>>>>> type : router >>>>>> up : true >>>>>> >>>>>> >>>>>> On Thu, Aug 4, 2022 at 11:39 AM Satish Patel <satish.txt(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Luis, >>>>>>> >>>>>>> This is what I have installed on the compute and controller nodes. >>>>>>> >>>>>>> pyroute2 0.6.13 >>>>>>> pyroute2.core 0.6.13 >>>>>>> pyroute2.ethtool 0.6.13 >>>>>>> pyroute2.ipdb 0.6.13 >>>>>>> pyroute2.ipset 0.6.13 >>>>>>> pyroute2.ndb 0.6.13 >>>>>>> pyroute2.nftables 0.6.13 >>>>>>> pyroute2.nslink 0.6.13 >>>>>>> >>>>>>> On Wed, Aug 3, 2022 at 10:10 AM Luis Tomas Bolivar < >>>>>>> ltomasbo(a)redhat.com> wrote: >>>>>>> >>>>>>>> What version of pyroute2 are you using? Maybe it is related to some >>>>>>>> bug in there in an old version (I hit quite a few). You can try to upgrade >>>>>>>> that. Also, as it is on the resync, you can also disable that by setting a >>>>>>>> very long time in there. >>>>>>>> >>>>>>>> >>>>>>>> On Wednesday, August 3, 2022, Satish Patel <satish.txt(a)gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Any thoughts Luis. Thanks >>>>>>>>> >>>>>>>>> Sent from my iPhone >>>>>>>>> >>>>>>>>> On Jul 27, 2022, at 11:53 AM, Satish Patel <satish.txt(a)gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> Luis, >>>>>>>>> >>>>>>>>> If you look at this logs - >>>>>>>>> https://paste.opendev.org/show/buRbY415guvHFUtSapFK/ >>>>>>>>> >>>>>>>>> I am able to expose the tenant ip when I set "expose_tenant_networks=True" >>>>>>>>> in the ovn-bgp-agent.conf file. But interestingly it exposes ip for the >>>>>>>>> first time but when i delete vm and re-create new vm then its throws >>>>>>>>> following error which you can see full track in above link >>>>>>>>> >>>>>>>>> ERROR oslo_service.periodic_task [-] Error during BGPAgent.sync: KeyError: 'object does not exists' >>>>>>>>> >>>>>>>>> >>>>>>>>> I have just 1x controller and 1x compute machine at present. As >>>>>>>>> you said something is broken when setting up "expose_tenant_networks=True" >>>>>>>>> Let me know if you need more info or logs etc. i will continue to poke and >>>>>>>>> see if anything else I can find. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Jul 27, 2022 at 10:35 AM Luis Tomas Bolivar < >>>>>>>>> ltomasbo(a)redhat.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Satish,sorry for the delay in replies, I'm on vacations and >>>>>>>>>> have limited connectivity. >>>>>>>>>> >>>>>>>>>> See soon comments/replies inline >>>>>>>>>> >>>>>>>>>> On Wed, Jul 27, 2022 at 4:58 AM Satish Patel < >>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Luis, >>>>>>>>>>> >>>>>>>>>>> Just checking incase you missed my last email. If you are on >>>>>>>>>>> vacation then ignore it :) Thank you. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sat, Jul 23, 2022 at 12:27 AM Satish Patel < >>>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Luis, >>>>>>>>>>>> >>>>>>>>>>>> As you suggested, checkout 5 commits back to avoid the >>>>>>>>>>>> Load_Balancer issue that made good progress. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> Great to hear! >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> But now i am seeing very odd behavior where floating IP can get >>>>>>>>>>>> exposed to BGP but when i am trying to expose VM Tenant IP then I get a >>>>>>>>>>>> strange error. Here is the full logs output; >>>>>>>>>>>> https://paste.opendev.org/show/buRbY415guvHFUtSapFK/ >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> I was using the evpn mode for the tenant networks, so it has been >>>>>>>>>> a while since I tested the vm tenant ip with plain bgp. Perhaps we broke it >>>>>>>>>> with some of the new features/reshapes. >>>>>>>>>> >>>>>>>>>> Regarding the error, two things: >>>>>>>>>> - Do you have several hosts or just one? The VM IP should be >>>>>>>>>> exposed in the host holding the ovn cr-lrp port (ovn router gateway port >>>>>>>>>> connecting the router to the provider network). >>>>>>>>>> - The error there seems to be related to the re-sync task. I've >>>>>>>>>> hit some issues with pyroute2 in the past, please be sure to use a recent >>>>>>>>>> enough version (minimum supported is 0.6.4) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Jul 22, 2022 at 8:55 AM Satish Patel < >>>>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Luis, >>>>>>>>>>>>> >>>>>>>>>>>>> Thank you for reply, >>>>>>>>>>>>> >>>>>>>>>>>>> Let me tell you that your blog is wonderful. I have used your >>>>>>>>>>>>> method to install frr without any docker container. >>>>>>>>>>>>> >>>>>>>>>>>>> What is the workaround here? Can I tell ovn-bgp-agent to not >>>>>>>>>>>>> look for container of frr? >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> You just need to point where the frr socket is on the host. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> I have notice one more thing that it’s trying to run “copy >>>>>>>>>>>>> /tmp/blah running-config” but that command isn’t supported. >>>>>>>>>>>>> >>>>>>>>>>>>> I have tried to run copy command manually on vtysh shell to >>>>>>>>>>>>> see what options are available for copy command but there is only one >>>>>>>>>>>>> command available with copy which is “copy running-config startup-config” >>>>>>>>>>>>> do you think I have wrong version of frr running? I’m running 7.2. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> I think the minimum version I tried was either 7.4 or 7.5. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>> Please let me know if any workaround here. Thank you >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> No easy workaround for this, as it is relying on that way to >>>>>>>>>> reconfigure the frr.conf >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Luis >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> Sent from my iPhone >>>>>>>>>>>>> >>>>>>>>>>>>> On Jul 22, 2022, at 2:41 AM, Luis Tomas Bolivar < >>>>>>>>>>>>> ltomasbo(a)redhat.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Hi Satish, >>>>>>>>>>>>> >>>>>>>>>>>>> The one to use should be https://opendev.org/x/ovn-bgp-agent. >>>>>>>>>>>>> The one on my personal github repo was the initial PoC for it. But the >>>>>>>>>>>>> opendev one is the upstream effort to develop it, and is the one being >>>>>>>>>>>>> maintained/updated. >>>>>>>>>>>>> >>>>>>>>>>>>> Looking at your second logs, it seems you are missing FRR (and >>>>>>>>>>>>> its shell, vtysh) in the node. >>>>>>>>>>>>> >>>>>>>>>>>>> Actually, thinking about this: >>>>>>>>>>>>> "Unexpected error while running command. >>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config" >>>>>>>>>>>>> >>>>>>>>>>>>> The ovn-bgp-agent has been developed with "deploying on >>>>>>>>>>>>> containers" in mind, meaning it is assuming there is a frr container >>>>>>>>>>>>> running, and the container running the agent is trying to connect to the >>>>>>>>>>>>> same socket so that it can run the vtysh commands. Perhaps in your case the >>>>>>>>>>>>> frr socket is in a different location than /run/frr/ >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Jul 22, 2022 at 6:27 AM Satish Patel < >>>>>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Folks, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I am trying to create lab of of ovn-bgp-agent using this blog >>>>>>>>>>>>>> https://ltomasbo.wordpress.com/2021/02/04/ovn-bgp-agent-testing-setup/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> So far everything went well but I'm stuck at the bgp-agent >>>>>>>>>>>>>> installation and I encounter following error when running bgp-agent. >>>>>>>>>>>>>> Any suggestions? >>>>>>>>>>>>>> >>>>>>>>>>>>>> root@rack-1-host-2:/home/vagrant/bgp-agent# bgp-agent >>>>>>>>>>>>>> 2022-07-22 04:02:39.123 111551 INFO bgp_agent.config [-] >>>>>>>>>>>>>> Logging enabled! >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 CRITICAL bgp-agent [-] >>>>>>>>>>>>>> Unhandled error: AssertionError >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent Traceback >>>>>>>>>>>>>> (most recent call last): >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/bin/bgp-agent", line 10, in <module> >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> sys.exit(start()) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/agent.py", line 76, in >>>>>>>>>>>>>> start >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> bgp_agent_launcher = service.launch(config.CONF, BGPAgent()) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/agent.py", line 44, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> self.agent_driver = driver_api.AgentDriverBase.get_instance( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/driver_api.py", >>>>>>>>>>>>>> line 25, in get_instance >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> agent_driver = stevedore_driver.DriverManager( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/driver.py", line 54, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> super(DriverManager, self).__init__( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/named.py", line 78, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent extensions >>>>>>>>>>>>>> = self._load_plugins(invoke_on_load, >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/extension.py", line 221, >>>>>>>>>>>>>> in _load_plugins >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent ext = >>>>>>>>>>>>>> self._load_one_plugin(ep, >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/named.py", line 156, in >>>>>>>>>>>>>> _load_one_plugin >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent return >>>>>>>>>>>>>> super(NamedExtensionManager, self)._load_one_plugin( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/extension.py", line 257, >>>>>>>>>>>>>> in _load_one_plugin >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent obj = >>>>>>>>>>>>>> plugin(*invoke_args, **invoke_kwds) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/osp/ovn_bgp_driver.py", >>>>>>>>>>>>>> line 64, in __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> self._sb_idl = ovn.OvnSbIdl( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/osp/utils/ovn.py", >>>>>>>>>>>>>> line 62, in __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> super(OvnSbIdl, self).__init__( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/osp/utils/ovn.py", >>>>>>>>>>>>>> line 31, in __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> super(OvnIdl, self).__init__(remote, schema) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovs/db/idl.py", line 283, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent schema = >>>>>>>>>>>>>> schema_helper.get_idl_schema() >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovs/db/idl.py", line 2323, in >>>>>>>>>>>>>> get_idl_schema >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> self._keep_table_columns(schema, table, columns)) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovs/db/idl.py", line 2330, in >>>>>>>>>>>>>> _keep_table_columns >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent assert >>>>>>>>>>>>>> table_name in schema.tables >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent AssertionError >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> After googling I found one more agent at >>>>>>>>>>>>>> https://opendev.org/x/ovn-bgp-agent and its also throwing an >>>>>>>>>>>>>> error. Which agent should I be using? >>>>>>>>>>>>>> >>>>>>>>>>>>>> root@rack-1-host-2:~# ovn-bgp-agent >>>>>>>>>>>>>> 2022-07-22 04:04:36.780 111761 INFO ovn_bgp_agent.config [-] >>>>>>>>>>>>>> Logging enabled! >>>>>>>>>>>>>> 2022-07-22 04:04:37.247 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' stopped >>>>>>>>>>>>>> 2022-07-22 04:04:37.248 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' starting >>>>>>>>>>>>>> 2022-07-22 04:04:37.248 111761 INFO >>>>>>>>>>>>>> ovn_bgp_agent.drivers.openstack.utils.frr [-] Add VRF leak for VRF >>>>>>>>>>>>>> ovn-bgp-vrf on router bgp 64999 >>>>>>>>>>>>>> 2022-07-22 04:04:37.248 111761 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', >>>>>>>>>>>>>> 'ovn_bgp_agent.privileged.vtysh_cmd', '--privsep_sock_path', >>>>>>>>>>>>>> '/tmp/tmp4cie9eiz/privsep.sock'] >>>>>>>>>>>>>> 2022-07-22 04:04:37.687 111761 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> Spawned new privsep daemon via rootwrap >>>>>>>>>>>>>> 2022-07-22 04:04:37.598 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep daemon starting >>>>>>>>>>>>>> 2022-07-22 04:04:37.613 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep process running with uid/gid: 0/0 >>>>>>>>>>>>>> 2022-07-22 04:04:37.617 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep process running with capabilities (eff/prm/inh): >>>>>>>>>>>>>> CAP_NET_ADMIN|CAP_SYS_ADMIN/CAP_NET_ADMIN|CAP_SYS_ADMIN/none >>>>>>>>>>>>>> 2022-07-22 04:04:37.617 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep daemon running as pid 111769 >>>>>>>>>>>>>> 2022-07-22 04:04:37.987 111769 ERROR >>>>>>>>>>>>>> ovn_bgp_agent.privileged.vtysh [-] Unable to execute vtysh with >>>>>>>>>>>>>> ['/usr/bin/vtysh', '--vty_socket', '/run/frr/', '-c', 'copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config']. Exception: Unexpected error while >>>>>>>>>>>>>> running command. >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config\n' >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/privileged/vtysh.py", >>>>>>>>>>>>>> line 30, in run_vtysh_config >>>>>>>>>>>>>> return processutils.execute(*full_args) >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/oslo_concurrency/processutils.py", >>>>>>>>>>>>>> line 438, in execute >>>>>>>>>>>>>> raise ProcessExecutionError(exit_code=_returncode, >>>>>>>>>>>>>> oslo_concurrency.processutils.ProcessExecutionError: >>>>>>>>>>>>>> Unexpected error while running command. >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config\n' >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service [-] >>>>>>>>>>>>>> Error starting thread.: >>>>>>>>>>>>>> oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while >>>>>>>>>>>>>> running command. >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config\n' >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/oslo_service/service.py", line >>>>>>>>>>>>>> 806, in run_service >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> service.start() >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/agent.py", line >>>>>>>>>>>>>> 50, in start >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> self.agent_driver.start() >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/ovn_bgp_driver.py", >>>>>>>>>>>>>> line 73, in start >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> frr.vrf_leak(constants.OVN_BGP_VRF, CONF.bgp_AS, CONF.bgp_router_id) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/utils/frr.py", >>>>>>>>>>>>>> line 110, in vrf_leak >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> _run_vtysh_config_with_tempfile(vrf_config) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/utils/frr.py", >>>>>>>>>>>>>> line 93, in _run_vtysh_config_with_tempfile >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> ovn_bgp_agent.privileged.vtysh.run_vtysh_config(f.name) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/oslo_privsep/priv_context.py", >>>>>>>>>>>>>> line 271, in _wrap >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> return self.channel.remote_call(name, args, kwargs, >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/oslo_privsep/daemon.py", line >>>>>>>>>>>>>> 215, in remote_call >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> raise exc_type(*result[2]) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while >>>>>>>>>>>>>> running command. >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs running-config\n' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> 2022-07-22 04:04:37.993 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' stopping >>>>>>>>>>>>>> 2022-07-22 04:04:37.994 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' stopped >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> LUIS TOMÁS BOLÍVAR >>>>>>>>>>>>> Principal Software Engineer >>>>>>>>>>>>> Red Hat >>>>>>>>>>>>> Madrid, Spain >>>>>>>>>>>>> ltomasbo(a)redhat.com >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> LUIS TOMÁS BOLÍVAR >>>>>>>>>> Principal Software Engineer >>>>>>>>>> Red Hat >>>>>>>>>> Madrid, Spain >>>>>>>>>> ltomasbo(a)redhat.com >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> LUIS TOMÁS BOLÍVAR >>>>>>>> Principal Software Engineer >>>>>>>> Red Hat >>>>>>>> Madrid, Spain >>>>>>>> ltomasbo(a)redhat.com >>>>>>>> >>>>>>>> >>>>>>>> >>> >>> -- >>> LUIS TOMÁS BOLÍVAR >>> Principal Software Engineer >>> Red Hat >>> Madrid, Spain >>> ltomasbo(a)redhat.com >>> >>> >> > > -- > LUIS TOMÁS BOLÍVAR > Principal Software Engineer > Red Hat > Madrid, Spain > ltomasbo(a)redhat.com > >

2 1

[ironic][xena] problems updating redfish_password for existing node
by Wade Albright 24 Aug '22

24 Aug '22

Hi, I'm hitting a problem when trying to update the redfish_password for an existing node. I'm curious to know if anyone else has encountered this problem. I'm not sure if I'm just doing something wrong or if there is a bug. Or if the problem is unique to my setup. I have a node already added into ironic with all the driver details set, and things are working fine. I am able to run deployments. Now I need to change the redfish password on the host. So I update the password for redfish access on the host, then use an 'openstack baremetal node set <node> --driver-info redfish_password=<newpass>' command to set the new redfish_password. Once this has been done, deployment no longer works. I see redfish authentication errors in the logs and the operation fails. I waited a bit to see if there might just be a delay in updating the password, but after awhile it still didn't work. I restarted the conductor, and after that things work fine again. So it seems like the password is cached or something. Is there a way to force the password to update? I even tried removing the redfish credentials and re-adding them, but that didn't work either. Only a conductor restart seems to make the new password work. We are running Xena, using rpm installation on Oracle Linux 8.5. Thanks in advance for any help with this issue.

3 21

RE: [glance][cinder] Glance cinder backend or image cache ?
by Simon Dodsley 23 Aug '22

23 Aug '22

> Hello ! > > We're planning a new cluster without Ceph storage. > We will use an iSCSI pureStorage array for all storage except object > storage. > > PureStorage provide only a cinder driver. > So we will need to user boot on volume nova instances. > > My question is about glance. > PureStorage speak about Image Cache since Liberty: > https://support.purestorage.com/Solutions/OpenStack/z_Legacy_OpenStack_Refe… > > But I wonder if using the cinder backend of glance is a better, simpler, > transparent option ? The Image Cache you referenced is not specific to Pure. It is a common Cinder feature that many backend can leverage. You can use both the image cache and cinder as a glance store as well but they are redundant. It is best to pick one or the other. It depends on the images format you are using. For example if you are using QCOW2 as the format the glance cinder backend cannot optimize it, but the image cache can optimize. Simon

1 0

[TripleO] Adding Undercloud and overcloud container images to Foreman
by Ruslanas Gžibovskis 23 Aug '22

23 Aug '22

Hi all, Have anyone tried adding a container images registry from quay.io to the foreman installation? So far what I managed to achieve is - adding each image one by one, not a registry itself. I add it over Content > Products > (Added Product docker-registries) > Repositories > New Repository > Name > Type (select docker) > Upstream URL: quay.io > Upstream repository (tripleoussuri or tripleowallaby or any other) fails, it works only if I specify full image: tripleoussuri/centos-binary-heat-engine So my question, is there any way to copy whole repo using Foreman? Maybe I just go in incorrect place? Thanks. Regards -- Ruslanas Gžibovskis +370 6030 7030

1 0

[glance][cinder] Glance cinder backend or image cache ?
by Gilles Mocellin 23 Aug '22

23 Aug '22

Hello ! We're planning a new cluster without Ceph storage. We will use an iSCSI pureStorage array for all storage except object storage. PureStorage provide only a cinder driver. So we will need to user boot on volume nova instances. My question is about glance. PureStorage speak about Image Cache since Liberty: https://support.purestorage.com/Solutions/OpenStack/z_Legacy_OpenStack_Refe… But I wonder if using the cinder backend of glance is a better, simpler, transparent option ?

1 0

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 23 Aug '22

23 Aug '22

Hey team, Since there is nothing on the agenda for tomorrow's meeting, it has been cancelled. We will plan on meeting next week at the usual time.

1 0

[edge] OpenStack updates for an Akraino presentation
by Ildiko Vancsa 23 Aug '22

23 Aug '22

Hi OpenStack community, I’m reaching out to you as I would like to ask for a little help and pointers for a presentation I’m building about OpenStack. I was recently asked by the Akraino community to give a presentation about recently added features and enhancements and further updates in OpenStack. Akraino is a project that is primarily focused on edge computing use cases and building blocks of end-to-end edge infrastructures. To make my presentation relevant and most informative for them, I would like to highlight any recent development or ongoing work item that is, or can be, relevant for edge use cases. If there are features in your project that you think would be good to highlight or if your project team is working on relevant work items in the current release cycle, I would really appreciate if you could share pointers to any information about them! Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

1 0

[openstack-ansible] [yoga] utility_container failure
by Father Vlasie 23 Aug '22

23 Aug '22

Hello everyone, I have happily progressed to the second step of running the playbooks, namely "openstack-ansible setup-infrastructure.yml" Everything looks good except for just one error which is mystifying me: ---------------- TASK [Get list of repo packages] ********************************************************************************************************************************************************** fatal: [infra1_utility_container-5ec32cb5]: FAILED! => {"changed": false, "content": "", "elapsed": 30, "msg": "Status code was -1 and not [200]: Request failed: <urlopen error timed out>", "redirected": false, "status": -1, "url": "http://192.168.3.9:8181/constraints/upper_constraints_cached.txt"} ---------------- 192.168.3.9 is the IP listed in user_variables.yml under haproxy_keepalived_internal_vip_cidr Any help or pointers would be very much appreciated! Thank you, Father Vlasie

2 9

evacuate vm
by fereshteh loghmani 22 Aug '22

22 Aug '22

hello i use kolla ansiable with wallaby version. when i evacuate server some of my vm with centos OS have error about xfs and for solve this issue i change server to rescue mode and from rescue i use command xfs_repair -l and my server will be ok and boot successfully. could you help me about this issue that why some of my vm had xfs error ?

1 0

Kolla-ansible Xena installation Error
by KK CHN 22 Aug '22

22 Aug '22

I am following the documentation https://docs.openstack.org/project-deploy-guide/kolla-ansible/xena/quicksta… on VM with Debian 10 distro But I am getting the errors as follows . Here is my /etc/hosts whats wrong here ?? ############################################## (venv) cloud@Xena:~$ cat /etc/hosts 127.0.0.1 localhost #127.0.1.1 Xena #10.184.48.94 localhost Xena # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # BEGIN ANSIBLE GENERATED HOSTS 10.184.48.94 Xena # END ANSIBLE GENERATED HOSTS (venv) cloud@Xena:~$ ################################################### ERROR fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "sudo: a password is required\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} I am trying this installation on a Virtual Machine on Debian 10 OS. (venv) cloud@Xena:~$ kolla-ansible -i ./all-in-one bootstrap-servers Bootstrapping servers : ansible-playbook -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e kolla_action=bootstrap-servers /home/cloud/venv/share/kolla-ansible/ansible/kolla-host.yml --inventory ./all-in-one [WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details PLAY [Gather facts for all hosts] *************************************************************************************************************************************** TASK [Gather facts] ***************************************************************************************************************************************************** ok: [localhost] TASK [Group hosts to determine when using --limit] ********************************************************************************************************************** ok: [localhost] [WARNING]: Could not match supplied host pattern, ignoring: all_using_limit_True PLAY [Gather facts for all hosts (if using --limit)] ******************************************************************************************************************** skipping: no hosts matched PLAY [Apply role baremetal] ********************************************************************************************************************************************* TASK [baremetal : include_tasks] **************************************************************************************************************************************** included: /home/cloud/venv/share/kolla-ansible/ansible/roles/baremetal/tasks/bootstrap-servers.yml for localhost TASK [baremetal : Ensure localhost in /etc/hosts] *********************************************************************************************************************** fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "sudo: a password is required\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} PLAY RECAP ************************************************************************************************************************************************************** localhost : ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 Command failed ansible-playbook -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e kolla_action=bootstrap-servers /home/cloud/venv/share/kolla-ansible/ansible/kolla-host.yml --inventory ./all-in-one (venv) cloud@Xena:~$ Any hints welcome. Thank you all krish

2 1

Floating IP
by Venkat Reddy 22 Aug '22

22 Aug '22

Hi All Goodmorning, Please help me ,I have the requirement to assign floating IP automatically while creating an instance. Can please help me. -- Thanks & Regards, Venkat Reddy.S

4 4

docker.repo file
by Faezeh Salali 22 Aug '22

22 Aug '22

Hi on Kolla ansible victoria version in bootstrap command this error is displayed: failed to fetch key at https://download.docker.com/linux/rocky/gpg , error was: HTTP Error 404: Not Found my compute os is rocky Linux 8 and it seems there is some problem with the docker repo on compute and /etc/yum.repos.d/docker.repo directory. Please send me the link of the baseurl and gpgkey. Thank you.

4 3

[neutron] Bug deputy report for week of August 15
by Lajos Katona 22 Aug '22

22 Aug '22

Hi Neutron Team I was the bug deputy in neutron last week, please check my summary. Needs attention ================= * OVN Metadata set up very slow (https://bugs.launchpad.net/neutron/+bug/1987060) * [stable/stein][stable/rocky}[stable/queens] CI jobs failing (https://bugs.launchpad.net/neutron/+bug/1986682 ) For stein I pushed 2 patches, not sure if with minimal effort it can be fixed: * https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/853794 * https://review.opendev.org/c/openstack/neutron/+/853608 In Progress ================= * [ovn-octavia-provider] HealthMonitor affecting several LBs (https://bugs.launchpad.net/neutron/+bug/1986977 ) In Progress ( https://review.opendev.org/c/openstack/ovn-octavia-provider/+/853681) * ovn: db sync fails if all ips are allocated in the subnet and metadata port is missing an ip (https://bugs.launchpad.net/neutron/+bug/1987135) In Progress: https://review.opendev.org/c/openstack/neutron/+/853840 Documentation bug ================= * Manually assign --device and --device-owner to a port does NOT binds the port immediately (https://bugs.launchpad.net/neutron/+bug/1986969 ) RFE proposals ================= * [rfe][fwaas]support standard_attrs for firewall_group (https://bugs.launchpad.net/neutron/+bug/1986906 ) we already discussed and approved this RFE on Drivers meeting * [RFE] Add a port extension to set/define the switchdev capabilities (https://bugs.launchpad.net/neutron/+bug/1987093 )

1 0

[OVS] Can't access instances on a compute and after restarted ovs-vswitchd it's back to normal
by ginton 4k 22 Aug '22

22 Aug '22

*Bug Description* We are using openstack ussuri with openvswitch version 2.13.3 and ovn version 20.03.2. We are using ubuntu 18.04.5 LTS with kernel 4.15.0-122-generic. My question is sometimes and consistently all instances in one compute can't access and when hard reboot instance we got an error message: Unable to add port tapxxx to OVS bridge br-int. After restart ovs-vswitchd service all instances can be accessed.

1 0

[openstack-ansible] Reset Target Host
by Father Vlasie 21 Aug '22

21 Aug '22

Hello everyone, Is there a way to reset a target host with OpenStack-Ansible? What I mean is to remove all the changes that have been applied, say, to infra1 so that the scripts can be deployed afresh. (It seems that the only way to get back to square one is to do a OS reinstall…is that right?) I am trying to avoid a reinstall because I am deploying from a remote location. Thank you, Father Vlasie

2 1

Re: [octavia] Help with fix barbican client in octavia when use trust-scoped token
by Ришат Азизов 21 Aug '22

21 Aug '22

Hello, Dmitry, Thanks for answer, I think this issue with Barbican client inside Octavia, and it can be fixed in the same way as the problem with the neutron client was fixed by Ligxian Kong https://review.opendev.org/c/openstack/octavia/+/726042/ Or not?

1 0

[all] Proposed Antelope cycle schedule
by Előd Illés 20 Aug '22

20 Aug '22

Hi, As we are beyond Zed milestone 2 for more than 2 weeks now, it's time to start planning the next, Antelope cycle and its release schedule: Antelope schedule: https://review.opendev.org/c/openstack/releases/+/850753 (or see its generated page [1]) Feel free to review it and comment on the patch if there is something that should be considered for the schedule. [1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Thanks, Előd Illés irc: elodilles

3 3

[swift] Terraform has deprecated the Swift backend
by Andrew Ruthven 20 Aug '22

20 Aug '22

Hey, It has come to our attention that Terraform has recently added deprecation messages to a number of backends, including Swift[0], warning that these backends will be removed in a future version of Terraform. Unfortunately we don't have the bandwidth within Catalyst Cloud to pick this up, but I was hopeful that there'd be others on this list who share our concern. It looks as though Terraform has had the Swift backend marked as unmaintained since at least March 2020[1]. If there is another backend, or another method of managing Swift that isn't the S3 API then I'd be keen to hear about it. Kind regards, Andrew [0] https://github.com/hashicorp/terraform/commit/7941b2fbdc33a42a68b9b32af51e0… [1] https://github.com/hashicorp/terraform/commit/c434db158e631b0bfddb92e1dd342… -- Andrew Ruthven, Wellington, New Zealand andrew(a)etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |

4 4

Fwd: Virtual PTG October 2022 Team Signup Reminder - Last Call
by Kendall Nelson 20 Aug '22

20 Aug '22

Hello Everyone, This is your last call to sign up your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 17 to Friday, October 21st, 2022! NOTE: Since we are now hosting the PTG virtually, we will be holding the event all week (Monday - Friday) and will be using the ‘normal’ virtual schedule of 4 hour blocks of time covering hours for Americas/APAC, APAC/Europe+Africa, and Europe+Africa/Americas. If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 26th, 2022 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

[kolla-ansible] upgrade process when it involves OS and ceph major version
by wodel youchi 19 Aug '22

19 Aug '22

Hi, What are the steps of upgrading an openstack platform when the upgrade involves: - OS upgrade: how to perform the upgrade? What type of node to upgrade first? Controllers, network or compute? - Ceph storage when using HCI deployment? Just general steps. Regards

2 2

[release] Release countdown for week R-6, Aug 22 - 26
by Előd Illés 19 Aug '22

19 Aug '22

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on August 25th, 2022. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/zed branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (September 1st, 2022) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, September 1st, 2022. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/zed branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/zed branches are cut for a repo, the ability to approve any necessary backports into those branches for Zed will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 25th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Cycle Highlights Due: September 1st, 2022 (R-5 week) Zed final release: October 5th, 2022 Előd Illés irc: elodilles

1 0

[cinder] Festival of XS reviews
by Rajat Dhasmana 19 Aug '22

19 Aug '22

Hello Argonauts, We will be having our monthly festival of XS reviews today i.e. 19th August (Friday) from 1400-1600 UTC. Following are some additional details: Date: 19th August, 2022 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks and regards Rajat Dhasmana

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Aug 19
by Slawek Kaplonski 19 Aug '22

19 Aug '22

Hi, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 18. Most of the meeting discussions are summarized in this email. Meeting full logs are available at https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-18-15.00.log.html * Next TC weekly meeting will be on 25 Aug Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 3. 2. What we completed this week: ========================= 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], Two are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[3]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[4]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [5] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[6][7]. Project updates ------------------- * Retire openstack-help-addons [8] 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[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-zed-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/836888 [5] https://review.opendev.org/c/openstack/governance/+/849606 [6] https://etherpad.opendev.org/p/zuul-config-error-openstack [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [8] https://review.opendev.org/c/openstack/governance/+/851859 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[nova] Is the VMware NSX CI still being maintained?
by melanie witt 19 Aug '22

19 Aug '22

Hi all, I have noticed lately the VMware NSX CI does not seem to be running since March/April of this year based on casual gerrit search [1]. More recently, maybe starting in May, I have seen it post comments on reviews but they say: Build failed - ext-nova-zuul : NOT_REGISTERED Does anyone know whether this job is still being maintained and if it will be fixed? Thanks, -melwitt [1] https://review.opendev.org/q/reviewer:%2522VMware+NSX+CI%2522+project:opens…

1 0

Re: [all][tc] Technical Committee next weekly meeting on 2022 Aug 18 at 1500 UTC
by Ghanshyam Mann 18 Aug '22

18 Aug '22

Hello Everyone, Below is the agenda for Today's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** Encourage projects to schedule 'operator hours' as a separate slot in PTG(avoiding conflicts among other projects 'operator hours') * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[neutron] Drivers meeting agenda - 19.08.2022.
by Lajos Katona 18 Aug '22

18 Aug '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFEs to discuss tomorrow: [RFE] Add possibility to define default security group rules (#link https://bugs.launchpad.net/neutron/+bug/1983053 ) [rfe][fwaas]support standard_attrs for firewall_group (#link https://bugs.launchpad.net/neutron/+bug/1986906 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

Weird behaviour on a provider net
by Derek O keeffe 18 Aug '22

18 Aug '22

Hi all, We have an Openstack Victoria cluster deployed and a provider network (IPv4) created that worked fine for months. Lately we've noticed that about 30-40% of the VM's that are spun up using this network are inaccessible over ssh, Permission denied (publickey). Also, if you add a customisation script to create a password for the Ubuntu user that fails too. Initially we thought it was confined to one/two compute nodes but further testing this week shows that it can be any of the 6 compute nodes we have and always the original two that we identified as being the problem. If we create the VM's from the cli and send them to specific hosts everything works fine including the original two hosts that had issues. We're finding it hard to nail down the cause of this because it's not consistent behaviour so any tips on where to investigate would be welcome, we have a second provider net (IPv4 & IPv6) that works fine and have went through all the configs to see if there's any difference and all are identical over the hosts. Thanks in advance for any info. Regards,Derek

2 1

Which deployment Method for a production cloud ?
by KK CHN 18 Aug '22

18 Aug '22

List, I want to install Openstack Xena version on a DELL ( R650 2 CPU and 40 cores . 2.4 TB) server machine. Operating System preference is Debian 10. I want to deploy this for production use with Ceph OSDs. There are four methods described in the URL : Confused which to select. https://docs.openstack.org/xena/deploy/ 1. Using Charms deployment 2. Deploy openstack using Ansible in Docker containers 3. Openstack - Ansible Deployment guide. 4. Triple O deployment guide Which method do I have to follow a full fledged production deployment ? why ? Going ahead with Ansible and Docker is a best option or not ? Your kind guidance requested.. Thanks in advance, Krish ps:- Once Completed this installation I have to extend this as a High available(HA) Multi Node cloud. (multi node production cloud with 3 Controllers, 6 compute Nodes and 3 Storage nodes with Ceph OSD pools) . Request to consider this future scalability requirement while answering my query.

2 1

[openstack-ansible][wallaby] lxc-containers-create.yml fails when specifying a container group
by Taltavull Jean-François 18 Aug '22

18 Aug '22

Hello everyone, Whatever the container group, lxc-containers-create playbook fails when specifying the group with -l option. For example : $ sudo openstack-ansible lxc-containers-create.yml -l repo_container Fails with: TASK [lxc_container_create : Gather variables for each operating system] ******************************************************************************************************************************************************************************************************fatal: [p3controller1a_repo_container-b54c9eba]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1b_repo_container-1c7f8c1f]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1c_repo_container-1e73e8a7]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} Any similar experience ? Any idea ? Thank you, Jean-Francois

2 2

[Neutron][Octavia][ovn-octavia-provider] proposing Fernando Royo for ovn-octavia-provider core reviewer
by Lajos Katona 18 Aug '22

18 Aug '22

Hi I would like to propose Fernando Royo (froyo) as a core reviewer to the ovn-octavia-provider project. Fernando is very active in the project (see [1] and [2]). As ovn-octavia-provider is a link between Neutron and Octavia I ask both Neutron and Octavia cores to vote by answering to this thread, to have a final decision. Thanks for your consideration. [1]: https://review.opendev.org/q/owner:froyo%2540redhat.com [2]: https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Cheers Lajos

6 6

[cinder] Bug deputy report for week of 08-17-2022
by Sofia Enriquez 17 Aug '22

17 Aug '22

This is a bug report from 08-10-2022 to 08-17-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1985962 "Wrong volume_quota exception msg when extending volume_size." Fix proposed to master. Low - https://bugs.launchpad.net/cinder/+bug/1985065 "[Storwize] mkhost command failure". Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1986658 "NetApp driver is hitting the QoS policy limit due soft deletion." Fix proposed to master. Cheers, Sofia -- 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

[oslo][stable] Backport of the default value of the config option change
by Slawek Kaplonski 17 Aug '22

17 Aug '22

Hi, Some time ago oslo.messaging changed default value of the "heartbeat_in_pthread" config option to "True" [1]. As was noticed some time ago, this don't works well with nova-compute - see bug [2] for details. Recently we noticed in our downstream Red Hat OpenStack, that it's not only nova-compute which don't works well with it and can hangs. We saw the same issue in various neutron agent processes. And it seems that it can be the same for any non-wsgi service which is using rabbitmq to send heartbeats. So giving all of that, I just proposed change of the default value of that config option to be "False" again [3]. And my question is - would it be possible and acceptable to backport such change up to stable/wallaby (if and when it will be approved for master of course). IMO this could be useful for users as using this option set as "True" be default don't makes any sense for the non-wsgi applications really and may cause more bad then good things really. What are You opinions about it? [1] https://review.opendev.org/c/openstack/oslo.messaging/+/747395 [2] https://bugs.launchpad.net/oslo.messaging/+bug/1934937 [3] https://review.opendev.org/c/openstack/oslo.messaging/+/852251/ -- Slawek Kaplonski Principal Software Engineer Red Hat

13 14

[glance] Antelope PTG Planning
by Abhishek Kekane 17 Aug '22

17 Aug '22

Hi everyone, Virtual PTG for the Antelope cycle will be held between 17th - 21st October [1]. I've also created an etherpad [2] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] https://openinfra-ptg.eventbrite.com/ [2] https://etherpad.opendev.org/p/antelope-ptg-glance-planning Thanks, Abhishek Kekane

1 0

[kolla-ansible][octavia] need networking help
by Stuart Whitman 17 Aug '22

17 Aug '22

Hello, I enabled Octavia on a kolla-ansible installed Openstack cluster. When I try to launch a loadbalancer instance, the octavia-worker.log file reports: "WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance." I researched enough to know that the problem has to do with networking between the controller and the lb-mgmt-net network. I initially overlooked this in the kolla-ansible Octavia documentation: "If using a VLAN provider network, ensure that the traffic is also bridged to Open vSwitch on the controllers." But, I don't know how to do it. Help to create the necessary bridge would be greatly appreciated. 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.

4 6

[horizon][plugins] Horizon angular based plugins are broken after migrating to angularjs 1.8.2.2
by vishal manchanda 16 Aug '22

16 Aug '22

Hello everyone, Horizon team recently migrated XStatic-Angular 1.5.8.0->1.8.2.2 [1] and after that many horizon angular based plugins start failing [2]. We already fixed these issues in horizon [3]. So I guess we need to fix the similar thing in horizon plugins. Why did we migrated Angular 1.5.8.0->1.8.2.2? The angularjs version is updated 1.5.8.0->1.8.2.2 to include the CVE fixed in the latest version. Also, there is a security bug reported for the same [4]. I have also created an etherpad to track the progress for failed horizon plugins [5]. Action items for the horizon plugins team either fixed their plugins or review/merge the patch pushed by horizon team members on priority basis to fix the gate. The npm jobs are failing in below horizon plugins : • ironic-ui • octavia-dashboard • senlin-dashboard • designate-dashboard • vitrage-dashboard • murano-dashboard • zaqar-ui • zun-ui • magnum-ui In case of any queries, please feel free to reach out to Horizon channel #openstack-horizon. Thanks & Regards, Vishal Manchanda(irc: vishalmanchanda) [1] https://review.opendev.org/c/openstack/requirements/+/844099 [2] https://review.opendev.org/c/openstack/horizon/+/845733 [3] https://review.opendev.org/c/openstack/horizon/+/843346 [4] https://bugs.launchpad.net/horizon/+bug/1955556 [5] https://etherpad.opendev.org/p/Fix_Horizon_Plugins_With_Angularjs_v1.8.2.2

2 2

[neutron] CI meeting - agenda for 16.08.2022
by Slawek Kaplonski 16 Aug '22

16 Aug '22

Hi, Agenda for today's Neutron CI meeting is at [1]. This will be video meeting, which we will have on [2]. [1] https://etherpad.opendev.org/p/neutron-ci-meetings [2] https://meetpad.opendev.org/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Metering, billing software components for Openstack
by KK CHN 16 Aug '22

16 Aug '22

List, We are running our datacenter using the Ussuri version. Planning to upgrade to higher versions soon. 1. What are the metering, billing and metric solutions for ussuri and other latest openstack versions ? 2. The ceilometer and gnocchi is the way forward or ? People are using any latest tools for the best results pls share your thoughts. Any thoughts most welcome. Krish

3 3

[openstack-helm] No meeting tomorrow
by Gage Hugo 16 Aug '22

16 Aug '22

Hey team, Since there's nothing on the agenda for tomorrow's meeting, it has been cancelled. We will meet as scheduled next week. Thanks!

1 0

[neutron] Bug deputy report (week starting on Aug-8-2022)
by Bernard Cafarelli 16 Aug '22

16 Aug '22

Hello neutrinos, it is time again to start a new bug deputy rotation: https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy and my turn for last week's bugs A relatively quiet week (it is the holiday season in quite a few parts of the world!) with fixes already merged for most bugs. Two bugs to highlight though (and in need of some neutron eyes): a manila job failing with IPv6 VMs (1940324) and a live-migration issue (1986003) Critical * neutron-tempest-plugin failing on networking-bagpipe tests - https://bugs.launchpad.net/neutron/+bug/1986534 networking-bagpipe also needed update after neutron-lib constants rehoming, fix merged: https://review.opendev.org/c/openstack/networking-bagpipe/+/852867 High * [CI][Devstack] Failing to SSH to test VMs with IPv6 - https://bugs.launchpad.net/neutron/+bug/1940324 LVM job for manila fails on IPv6 hosts with socket.timeout: timed out, if CI/IPv6 gurus can take a look and help manila team Medium * neutron-dynamic-routing: Continuous warning because of missing context wrapper - https://bugs.launchpad.net/neutron/+bug/1984238 Previous fix missed one context wrapper, fix by tkajinam https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/852775 Low * Replace "click" with "cliff" - https://bugs.launchpad.net/neutron/+bug/1985049 Several patches in progress to update tools using click, see LP for details Original started as bug to add click to requirements - https://bugs.launchpad.net/neutron/+bug/1984109 * [OVN] Remove "FIPAddDeleteEvent" event - https://bugs.launchpad.net/neutron/+bug/1985096 Unassigned cleanup bug, workaround is not needed since OVN v20.03.0 * DeprecationWarning: Using the 'user' argument is deprecated in version '2.18' and will be removed in version '3.0', please use the 'user_id' argument instead - https://bugs.launchpad.net/neutron/+bug/1986418 Fix merged https://review.opendev.org/c/openstack/neutron/+/853050 * DeprecationWarning: invalid escape sequence \u - https://bugs.launchpad.net/neutron/+bug/1986421 Fix merged https://review.opendev.org/c/openstack/neutron/+/853051 * PkgResourcesDeprecationWarning: <MagicMock name='execute().split().__getitem__().__getitem__()' id='140417024565696'> is an invalid version and will not be supported in a future release - https://bugs.launchpad.net/neutron/+bug/1986428 Fix also merged: https://review.opendev.org/c/openstack/neutron/+/853053 Thanks Takashi Natsume for this series of deprecation fixes Untriaged * Exception in concurrent port binding activation - https://bugs.launchpad.net/neutron/+bug/1986003 Live migration issue that I did not have time to dig into - any takers? Have a nice week! -- Bernard Cafarelli

1 0

[Ansible] [Yoga] Infra LXC Cache Failure
by Father Vlasie 16 Aug '22

16 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6. I have 3 infra nodes all running the same software/hardware specifications but the 3rd one keeps giving me the following error. This occurs when running setup-hosts.yml ---------- TASK [lxc_hosts : Ensure that the LXC cache has been prepared] ******************************************************************************* FAILED - RETRYING: [infra3]: Ensure that the LXC cache has been prepared (120 retries left). FAILED - RETRYING: [infra3]: Ensure that the LXC cache has been prepared (119 retries left). fatal: [infra3]: FAILED! => {"ansible_job_id": "205392349782.93369", "attempts": 3, "changed": true, "cmd": "chroot /var/lib/machines/rocky-8-amd64 /opt/cache-prep-commands.sh > /var/log/lxc-cache-prep-commands.log 2>&1", "delta": "0:00:16.353232", "end": "2022-08-15 12:59:42.058169", "finished": 1, "msg": "non-zero return code", "rc": 1, "results_file": "/root/.ansible_async/205392349782.93369", "start": "2022-08-15 12:59:25.704937", "started": 1, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} ---------- Thank you very much for any help! Father Vlasie

1 1

[Octavia] Monitor through Listener Prometheus Protocol
by Vu Tuan Dat 15 Aug '22

15 Aug '22

HI, I installed Prometheus on controller nodes. However, My prometheus instance cannot connect to Listener Prometheus endpoint because it's binded to VIP only in network namespace. Anyone can help? Thanks in advanced, Dat

2 1

[Ansible] [Yoga] Set rsyslog not to containerise
by Father Vlasie 15 Aug '22

15 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6. I have a rsyslog host that is somewhat underpowered (RAM and CPU) and I thought it might help to run rsyslog without containerisation. I have searched but I have not been able to find an example of this.My guess is that I need to create a file in /etc/openstack_deploy/env.d What syntax and commands do I need? I have searched but I could not find any examples... Thank you very much! Father Vlasie

2 1

[ironic] Proposing Jacob Anders to sushy-core
by Iury Gregory 15 Aug '22

15 Aug '22

Hello ironic-cores and sushy-cores, I would like to propose Jacob Anders (janders irc) for sushy-core. He made great contributions to improve sushy to cover corner cases from different HW in the last releases, you can find some of his contributions in [1], please vote with +1/-1. [1] https://review.opendev.org/q/owner:janders%2540redhat.com+project:openstack… -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 2

[Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 13 Aug '22

13 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6 on my target hosts. The documentation here (https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/ta…) says " • Centos 8 Stream 64-bit * Derivitives: Rocky Linux” under the list of supported operation systems. Ansible does not seem to check for the existence of RHEL 8 systems. :( But when I run “openstack-ansible setup-hosts.yml” I get the error: TASK [Check for a supported Operating System] ***************************************************************************************** fatal: [infra1]: FAILED! => { "assertion": "(ansible_facts['distribution'] == 'Debian' and ansible_facts['distribution_release'] == 'bullseye') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'focal') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'jammy') or (ansible_facts['os_family'] == 'RedHat' and ansible_facts['distribution_major_version'] == '9')", "changed": false, "evaluated_to": false, "msg": "The only supported platforms for this release are Debian 11 (Bullseye), Ubuntu 20.04 LTS (Focal), Ubuntu 22.04 (Jammy) and CentOS 9 Stream.\n” What should I do? Thank you!

3 2

[all][tc] What's happening in Technical Committee: summary 2022 Aug 12: Reading: 5 min
by Ghanshyam Mann 13 Aug '22

13 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 11. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-11-15.00.log.html * Next TC weekly meeting will be on Aug 18 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 17. 2. What we completed this week: ========================= * None in this week. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Two open reviews for ongoing activities[4]. OpenStack TC + Board member meeting ------------------------------------------------ As you might know, OpenStack TC and Board member had a informal meeting on Aug 10[5][6], I am summarizing the discussion here. The Openstack TC has presented the 'OpenStack Updates' to Board meeting in berlin. One of the key part of the updates were 'OpenStack community Challenges' and we could not finish the discussion or brainstorm on these in berlin meeting. We decided to continue the discussion on those (Slide#21)[7]. In this call, we can only cover the first challenge only 'Less Interaction with Operators & Users'. There is no doubt that we are facing this issue at noticeable level (RBAC is good example where we lacked the operator/user feedback). A lot of things including ML, events are discussed on why it is happening and how to improve it. Having ops meetup as a separate event is something many members raised concern about and it will be good to merge these events into other community events like Summit, PTG etc. To try the first step towards that we can invite or welcome operators in Oct virtual PTG and give them a feeling on merging the events with developers event can be beneficial to both the group. On that, Dan suggested the idea of scheduling the 'Operatos Hours' per project in PTG and there we will keep the discussion on operator-centric and the format they want. We continued the discussion on this in TC weekly meeting where we had mixed suggestions on the 'Operator Hours' schedule, either to ask each project to schedule it in their room and operator join or other way around. Before deciding any format, we will be asking operators about their preference. We will continue the discussion on 'OpenStack community Challenges' in the next call which is schedule on 20:00 UTC on Wednesday, November 16[8]. If anyone is interested, feel free to join it. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- Not much update on this but we will be seeing the election schedule proposed soon. 2023.1 cycle TC PTG planning ------------------------------------ We discussed about how to best encourage/invite operators into the PTG (I wrote in the above section) and based on the operators feedback we will proceed next. We will continue the discussion in the next meeting also. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [10] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]12]. Project updates ------------------- * Retire openstack-helm-addons[13] 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/849997 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029886.… [6] https://etherpad.opendev.org/p/2022-08-board-openstack-sync [7] https://docs.google.com/presentation/d/1yCiZy_9A6hURXD0BRdr33OlK7Ugch5EgSvF… [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029968.… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] https://review.opendev.org/c/openstack/governance/+/849606 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [13] https://review.opendev.org/c/openstack/governance/+/849997 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Re: [Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 13 Aug '22

13 Aug '22

> On Aug 12, 2022, at 3:13 PM, openstack-discuss-request(a)lists.openstack.org wrote: > > Comparing https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play… <https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play…> to https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks… <https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks…> it appears that OpenStack Ansible has removed CentOS Stream/RHEL/Rocky 8 support on master, but the assertion allows it under Yoga. Based on the failure above you must be running master OSA? I would try running the Yoga branch instead. > > The master branch documentation likely needs to be updated as well. That worked perfectly, thank you! :)

1 0

[tc] November 2022 OpenInfra Board Sync
by Jeremy Stanley 13 Aug '22

13 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-11-board-openstack-sync At the conclusion of the August 10 discussion, we agreed to tentatively schedule the next call for 20:00 UTC on Wednesday, November 16, so I've attached a calendar file which can serve as a convenient schedule hold for this, in case anyone needs it. -- Jeremy Stanley

1 0

OpenStack User Survey
by Jimmy McArthur 12 Aug '22

12 Aug '22

Hi Everyone - Just a quick reminder to please take the OpenStack User Survey [1] This vitally important survey provides direct, anonymized feedback to our Project Teams to help them build better software. If you run a deployment, no matter the size, please take 30 min out of your day to take this survey! Thank you, Jimmy [1] https://openstack.org/user-survey/

1 0

[release] Release countdown for week R-7, Aug 15 - 19
by Előd Illés 12 Aug '22

12 Aug '22

Development Focus ----------------- We are entering the last weeks of the Zed development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on August 18th, 2022. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 25th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (September 1st, 2022) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, September 1st, 2022. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 15th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 29th, 2022) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (September 1st, 2022). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Extra-ATC freeze: August 18th, 2022 (R-7 week) Non-client library freeze: August 25th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[tripleo] gate blocker tripleo-ci-centos-9-undercloud-upgrade
by Marios Andreou 12 Aug '22

12 Aug '22

o/ tripleo please hold rechecks on master tripleo branch - we have a gate blocker for tripleo-ci-centos-9-undercloud-upgrade https://bugs.launchpad.net/tripleo/+bug/1984175 package/conflict/mirror issue not clear yet - grateful for pointers if you have them

5 10

About the meaning of compute nodes
by 정재철 11 Aug '22

11 Aug '22

If there are many nodes, is it possible to create a high-performance VM? (e.g. Can 2 1 core cpu nodes create 1 2 core cpu VM)

5 5

[tc] August 2022 OpenInfra Board Sync
by Jeremy Stanley 11 Aug '22

11 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-08-board-openstack-sync I've also created a Framadate poll has in order to identify a few preferred dates and times. Responses must be submitted by Friday, 2022-07-15, in order to provide the board members with time to pick from the available options. The poll can be found here: https://framadate.org/atdFRM8YeUtauSgC Feel free to reply here on the mailing list, or you can reach out to me directly by E-mail or as fungi in the #openstack-tc IRC channel, with any questions you may have. -- Jeremy Stanley

1 3

[kolla] Best way to restart controllers
by Yves Gd 11 Aug '22

11 Aug '22

Hi all, We are looking for the best way to process system upgrades on our controller nodes and especially the best way to restart them (we have 3 controllers nodes with routers ha). If we just restart them one by one (waiting long time between each), we have already seen rabbitmq cluster errors (needing a complete restart of rabbitmq). With a kolla stop, a restart and a kolla deploy, some docker containers are restarted on others nodes. The administration guides describes how to add or remove a node but not this simple case. How do you proceed securely? Thanks for all, Yves

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Aug 11 at 1500 UTC
by Ghanshyam Mann 11 Aug '22

11 Aug '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Aug 11, at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Aug 10 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[cinder] Bug deputy report for week of 08-10-2022
by Sofia Enriquez 10 Aug '22

10 Aug '22

This is a bug report from 08-03-2022 to 08-10-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1984169 "RBD pool stats are reported inaccurately." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1984000 "Infinidat Cinder driver consistency groups feature is broken." Fix proposed to master. Cheers, Sofia -- 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

[neutron][ovn] ovn-bgp-agent EVPN mode question
by Satish Patel 10 Aug '22

10 Aug '22

Folks, I am trying to set up the following lab and so far everything looks good and working but I have some doubts or questions to make sure it's really working as expected. Lab Ref: https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/ rack-1-host-1 (controller) rack-1-host-2 (compute1 - This is hosting cr-lrp ports, inshort router) rack-2-host-1 (compute2) I have created two vms vagrant@rack-1-host-1:~$ nova list nova CLI is deprecated and will be a removed in a future release +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ | aecb4f10-c46f-4551-b112-44e4dc007e88 | vm1 | ACTIVE | - | Running | private-test=10.0.0.105 | | ceae14b9-70c2-4dbc-8071-0d64d9a0ca84 | vm2 | ACTIVE | - | Running | private-test=10.0.0.86, 172.16.1.200 | +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ # on rack-1-host-2 when i spun up vm2 which endup on rack-1-host-2 hence it created vrf-2001 on dummy lo-2001 interface and exposed vm2 ip address 10.0.0.86/32 96: vrf-2001: <NOARP,MASTER,UP,LOWER_UP> mtu 65575 qdisc noqueue state UP group default qlen 1000 link/ether 22:cc:25:b3:7b:96 brd ff:ff:ff:ff:ff:ff 97: br-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vrf-2001 state UP group default qlen 1000 link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff inet6 fe80::851:67ff:fe64:b2c3/64 scope link valid_lft forever preferred_lft forever 98: vxlan-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-2001 state UNKNOWN group default qlen 1000 link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff inet6 fe80::8c3:23ff:fe7a:8f0c/64 scope link valid_lft forever preferred_lft forever 99: lo-2001: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue master vrf-2001 state UNKNOWN group default qlen 1000 link/ether d6:60:da:91:2e:6d brd ff:ff:ff:ff:ff:ff inet 10.0.0.86/32 scope global lo-2001 valid_lft forever preferred_lft forever inet6 fe80::d460:daff:fe91:2e6d/64 scope link valid_lft forever preferred_lft forever # on rack-2-host-1 when i created vm1 which endup on rack-2-host-1 but it doesn't expose the vm ip address. Is that normal behavior? When I attach a floating ip to vm2 then why does my floating ip address not get exposed in BGP? Thank you in advance

1 0

Openstack Graphical processors virtualisation
by KK CHN 10 Aug '22

10 Aug '22

1. Does Openstack support GPU virtualization ? We are running a cloud using ussuri with KVM hypervisors. Is creation of vGPUs possible? Does KVM support GPU virtualization or any limitations? 2. What are the supported GPU types? (GRID GPU or GPUs attached to physical blades ) 3. If it supports GPU attached to physical blades, will live migration of the VM be supported. Will OpenStack be able to identify the next host which has an attached GPU and perform live migration, in case of the Failure of One Blade with attached GPU with resident VM. 4. What are the virtualization options if vGPU options are not supported by a particular GPU model? Thanks in advance, Krish

4 4

[PTG] [ironic] Antelope PTG new Etherpad
by Iury Gregory 10 Aug '22

10 Aug '22

Hello everyone, We changed the etherpad link to track the topics we will discuss at the PTG, instead of https://etherpad.opendev.org/p/ironic-ptg-planing-Columbus-OH we will be using https://etherpad.opendev.org/p/ironic-antelope-ptg Feel free to add any topics =) -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

Need help on rabbitmq
by AJ_ sunny 10 Aug '22

10 Aug '22

Hi team I am using kolla-ansible based openstack infra and getting below error in logs seems frequent rabbitmq disconnections <0.5023.16> closing AMQP connection <0.5023.16> (10.80.0.13:40356 -> 10.80.0.13:5672 - mod_wsgi:19:d3196668-57e5-46dc-8b69-78d73b5873a0): missed heartbeats from client, timeout: 60s AMQP server on 10.80.0.13:5672 is unreachable: [Errno 104] Connection reset by peer. Trying again in 1 seconds.: ConnectionResetError: [Errno 104] Connection reset by peer Is this bug or any resolution for fixing this issue? Thanks Arihant Jain

4 4

[tacker] IRC meeting on Aug 16 cancelled
by Yasufumi Ogawa 10 Aug '22

10 Aug '22

Hi team, Since many of us are going to have a vacation next week, I'll cancel the meeting on Aug 16th. Thanks, Yasufumi

1 0

Correct way to add firewall rules in tripleo | Wallaby
by Swogat Pradhan 10 Aug '22

10 Aug '22

Hi, I am trying to add a rule for zabbix in my tripleo wallaby setup on top of centos 8 stream. i followed https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… but got the error message: [ERROR]: Failed, module return: {'msg': 'value of action must be one of: append, insert, got: accept', 'failed': True, 'invocation': {'module_args': {'state': 'present', 'action': 'accept', 'jump': 'ACCEPT', 'chain': 'INPUT', 'protocol': 'tcp', 'source': '172.25.161.50', 'ctstate': ['NEW'], 'ip_version': 'ipv4', 'comment': '301 allow zabbix ipv4', 'destination_port': '10050', 'table': 'filter', 'match': [], 'syn': 'ignore', 'flush': False}}, 'warnings': ["The value 10050 (type int) in a string field was converted to '10050' (type string). If this does not look like what you expect, quote the entire value to ensure it does not change."], '_ansible_parsed': True} [ERROR]: Failed, return data: {'stdout': None, 'stderr': None, 'msg': 'value of action must be one of: append, insert, got: accept', 'cmd': None, 'rc': 0, 'failed': True} 2022-07-21 01:27:33.335477 | 48d539a1-1679-1e80-25fd-000000005aa1 | TASK | Manage firewall rules 2022-07-21 01:27:33.351515 | 48d539a1-1679-1e80-25fd-000000005542 | FATAL | Manage firewall rules | overcloud-controller-0 | error={"changed": false, "cmd": null, "msg": "value of action must be one of: append, insert, got: accept", "rc": 0, "stderr": null, "stdout": null} When i tried the following link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15… <https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15…> my script is running fine but rules are not updated in iptables for zabbix. Can you please suggest a correct approach to open port 10050 in tripleo? With regards, Swogat Pradhan

2 1

Security vulnerabilities in Horizon dashboard | Openstack Wallaby | Tripleo | Openstack Horizon
by Swogat Pradhan 10 Aug '22

10 Aug '22

Hi, I am setting up an openstack wallaby cloud for a client using tripleo. After setting everything up the client ran a WEB scan and found some vulnerabilities (attached snapshot for reference). Can you please guide me on how to fix these vulnerabilities in the dashboard service? With regards, Swogat pradhan

2 3

[openstack-ansible] Meeting on August 16 is cancelled
by Dmitriy Rabotyagov 09 Aug '22

09 Aug '22

Hi everyone, Since several core participants won't be able to present at the meeting it was decided to cancel the Team meeting on 16th of August 2022.

1 0

[nova] Review guide for PCI tracking for Placement patches
by Balazs Gibizer 09 Aug '22

09 Aug '22

Hi Nova, The first batch of patches are up for review for the PCI tracking for Placement feature. These mostly covers two aspects of the spec[1]: 1) renaming [pci]passthrough_whitelist to [pci]device_spec 2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement This covers the first 4 sub chapters of Proposed Change chapter of the spec[1] up until "PCI alias configuration". I noted intentional deviations from the spec in the spec review [2] and I will push a follow up to the spec at some point fixing those. I tried to do it in small steps hence the long list of commits[3]: #2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement 5827d56310 Stop if tracking is disable after it was enabled before a4b5788858 Support [pci]device_spec reconfiguration 10642c787a Reject devname based device_spec config b0ad05fb69 Ignore PCI devs with physical_network tag f5a34ee441 Reject mixed VF rc and trait config c60b26014f Reject PCI dependent device config 5cf7325221 Extend device_spec with resource_class and traits eff0df6a98 Basics for PCI Placement reporting #1) renaming [pci]passthrough_whitelist to [pci]device_spec adfe34080a Rename whitelist in tests ea955a0c15 Rename exception.PciConfigInvalidWhitelist to PciConfigInvalidSpec 55770e4c14 Rename [pci]passthrough_whitelist to device_spec There is a side track branching out from "adfe34080a Rename whitelist in tests" to clean up the device spec handling[4]: 514500b5a4 Move __str__ to the PciAddressSpec base class 3a6198c8fb Fix type annotation of pci.Whitelist class f70adbb613 Remove unused PF checking from get_function_by_ifname b7eef53b1d Clean up mapping input to address spec types 93bbd67101 Poison /sys access via various calls in test 467ef91a86 Remove dead code from PhysicalPciAddress 233212d30f Fix PciAddressSpec descendants to call super.__init__ ad5bd46f46 Unparent PciDeviceSpec from PciAddressSpec cef0d2de4c Extra tests for remote managed dev spec 2fa2825afb Add more test coverage for devname base dev spec adfe34080a Rename whitelist in tests This is not a mandatory part of the feature but I think they improve the code in hand and even fixing some small bugs. I will continue with adding allocation healing for existing PCI allocations. Any feedback is highly appreciated. Cheers, gibi [1] https://specs.openstack.org/openstack/nova-specs/specs/zed/approved/pci-dev… [2] https://review.opendev.org/c/openstack/nova-specs/+/791047 [3] https://review.opendev.org/q/topic:bp/pci-device-tracking-in-placement [4] https://review.opendev.org/q/topic:bp/pci-device-spec-cleanup

1 2

[publiccloud-sig] A new start for Public Cloud SIG
by Tobias Rydberg 09 Aug '22

09 Aug '22

Hi everyone, In Berlin it became clear that there is a big interest in restarting the Public Cloud SIG. Thank you all for your contributions in that forum session [0] and the interest in participating in the work of this SIG. A lot of good ideas of what we should focus on was identified, with a clear focus of interoperability and standardization, to make the experience of using OpenStack as an end-user even better. Standardization of images and flavors - naming, metadata etc - being one of them, working closely with InterOp WG regarding the checks and governance of the OpenStack Powered Program another. The ultimate goal could be to reach a state where it is possible to start to federate between the public clouds, but for that to be possible on a more global scale we need to start with aligning the simple things. To kick this off, we will start with bi-weekly IRC meetings again, shape the goals kick of some work towards identified goals. Since we have an IRC channel (#openstck-publiccloud) my suggestion is that we will start there. Let's decide on suggestions for day and time for our bi-weekly meetings during the kick off meeting. Kick off meeting =========== When: Wednesday 10th of August at 1400 UTC Where: IRC in channel #openstack-publiccloud I created an etherpad for our first meeting [1], feel free to add items to the agenda or other suggestions on goals etc that you might have prior to the meeting. Hope to see at IRC in August! [0] https://etherpad.opendev.org/p/berlin-summit-future-public-cloud-sig [1] https://etherpad.opendev.org/p/publiccloud-sig-kickoff BR, Tobias Rydberg

2 2

[announcement] [debian] Debian Buster with OpenStack Rocky will receive LTS support
by Thomas Goirand 08 Aug '22

08 Aug '22

Hi! After some discussion with the folks taking care of the Debian LTS project, we decided that we will attempt to support OpenStack Rocky, running on Debian 10 (aka: Buster), for another 2 years, together with the rest of the distribution. In the past, we decided that we wouldn't do it, and that OpenStack would be part of the list of unsupported packages, because it was too difficult to maintain. However, it is my opinion that this has changed, because: - The codebase is evolving slower - I do have all the tooling to re-do a Rocky deployment if needed - There's a lot less CVE per year than it used to be (10 years ago, it was 1 every 2 weeks on average, now we have like 2 grave issue per year...). - I'm confident that if there's a grave issue, I'll be able to find help from the this wonderful community (it happened in the past...). Also, some sponsors of the Debian LTS project are actually running OpenStack Rocky on Debian. So it makes sense to help them. It is to be noted that I will not be the person doing the actual security backports, but I'll be there in case the person doing it needs help from me (for example, to do a deployment and manual regression testing). Hoping this will help OpenStack users running on Debian, Cheers, Thomas Goirand (zigo)

1 0

[all] Automatic update of Python jobs in Zuul project configuration
by Pierre Riteau 08 Aug '22

08 Aug '22

Hello, A patch submitted to python-blazarclient by yoctozepto [1] made me realise the automatic change of Python jobs from yoga to zed missed various repositories [2], mostly python clients. Is there a reason for this? Also, one can easily find projects which are using even older job templates (xena or earlier). Thanks, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/python-blazarclient/+/851903 [2] https://codesearch.openstack.org/?q=openstack-python3-yoga-jobs&i=nope&lite…

3 6

[kolla-ansible] why does not the bootstrap create the docker bridge?
by wodel youchi 08 Aug '22

08 Aug '22

Hi, The bootstrap installs docker but it does not create the docker bridge, why? Regards.

2 1

[Oslo] IRC meeting.
by Daniel Mats Niklas Bengtsson 08 Aug '22

08 Aug '22

Hi there, I'm sorry, I was on vacation and then I had personal problems. We are still in the summer period and I think there are still people on vacation, I suggest resuming meetings in September. What do you think?

1 0

[neutron] Bug Deputy Report August 01 - 07
by Elvira Garcia Ruiz 08 Aug '22

08 Aug '22

Hi, I was the bug deputy last week. Find the summary below: High: ------- - [ovn]router_interface port probability cannot be up https://bugs.launchpad.net/neutron/+bug/1983530 Fix: https://review.opendev.org/c/openstack/neutron/+/851997 - l2_pop does unnecessary db fetches for incompatible network types https://bugs.launchpad.net/neutron/+bug/1983558 Fix: https://review.opendev.org/c/openstack/neutron/+/852089 Medium: ----------- - [OVN] Old DNS servers are served by DHCP after dns_servers option is updated https://bugs.launchpad.net/neutron/+bug/1983270 Assigned to me Low: ------- - Neutron should clean up ACLs in OVN NB DB when a remote security group is deleted https://bugs.launchpad.net/neutron/+bug/1983600 Unassigned Kind regards! Elvira

1 0

[Cinder][NFS][Openstack-Ansible]
by Dave Hall 08 Aug '22

08 Aug '22

Hello, I seem to have gotten myself in a bit of a mess trying to set up Cinder with an NFS back-end. After working with Glance and NFS, I started on Cinder. I noticed immediately that there weren't any NFS mounts in the Cinder-API containers like there were in the Glance-API containers. Also that there were no NFS packages in the Cinder-API containers. In reading some Cinder documentation, I also got the impression that each Cinder host/container needs to have its own NFS store. Pawing through the playbooks and documentation I saw that unlike Glance, Cinder is split into two pieces - Cinder-API and Cinder-Volume. I found cinder-volume.yml.example in env.d, activated it, and created Cinder-Volume containers on my 3 infra hosts. I also created 3 separate NFS shares and changed the storage-hosts section of my openstack_user_config.yml accordingly. After this I found that while I was able to create volumes, the prep_volume part of launching an instance was failing. Digging in, I found: # openstack volume service list +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ | Binary | Host | Zone | Status | State | Updated At | +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ | cinder-volume | C6220-9@nfs_volume | nova | enabled | down | 2022-07-23T02:46:13.000000 | | cinder-volume | C6220-10@nfs_volume | nova | enabled | down | 2022-07-23T02:46:14.000000 | | cinder-volume | C6220-11@nfs_volume | nova | enabled | down | 2022-07-23T02:46:14.000000 | | cinder-scheduler | infra36-cinder-api-container-da8e100f | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-scheduler | infra38-cinder-api-container-27219f93 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-scheduler | infra37-cinder-api-container-ea7f847b | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | C6220-9@nfs_volume1 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | infra37-cinder-volumes-container-5b9635ad@nfs_volume | nova | enabled | down | 2022-08-04T18:32:53.000000 | | cinder-volume | infra36-cinder-volumes-container-77190057@nfs_volume1 | nova | enabled | down | 2022-08-06T13:03:03.000000 | | cinder-volume | infra38-cinder-volumes-container-a7bcfc9b@nfs_volume | nova | enabled | down | 2022-08-04T18:32:53.000000 | | cinder-volume | infra37-cinder-volumes-container-5b9635ad@nfs_volume2 | nova | enabled | down | 2022-08-06T13:03:05.000000 | | cinder-volume | C6220-10@nfs_volume2 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | C6220-11@nfs_volume3 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | infra38-cinder-volumes-container-a7bcfc9b@nfs_volume3 | nova | enabled | down | 2022-08-06T13:03:03.000000 | +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ Thinking I could save this, I used containers-lxc-destroy.yml to destroy my cinder-volumes containers and deactivated cinder-volume.yml.example. Then I ran setup-hosts.yml, which has restored the cinder-volumes containers even though is_metal: false has been removed. Clearly a stronger intervention will be required. I would like to fully get rid of the cinder-volumes containers and go back to an is_metal: true scenario. I also need to get rid of the unnumbered nfs_volume referenes, which I assume are in some cinder config file somewhere. Below is a clip from my openstack_user_config.yml: storage_hosts: infra36: ip: 172.29.236.36 container_vars: cinder_backends: nfs_volume1: volume_backend_name: NFS_VOLUME1 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume1 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME1" } infra37: ip: 172.29.236.37 container_vars: cinder_backends: nfs_volume2: volume_backend_name: NFS_VOLUME2 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume2 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME2" } infra38: ip: 172.29.236.38 container_vars: cinder_backends: nfs_volume3: volume_backend_name: NFS_VOLUME3 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume3 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME3" } Any advice would be greatly appreciated. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

4 8

Guide for Openstack installation with HA, OVN ?
by 박경원 07 Aug '22

07 Aug '22

3 2

[release] Release countdown for week R-8, Aug 08 - 12
by Előd Illés 06 Aug '22

06 Aug '22

General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle: Ironic: * bifrost * ironic-prometheus-exporter * ironic-python-agent-builder * ironic-ui * networking-baremetal * networking-generic-switch OpenStackSDK: * python-openstackclient Swift: * swift Since these deliverables are traditionally released after our warning, we did not propose to change the release model to cycle-with-rc for them this time. Please let us know if any of the above project is considering the release model change anyway and we propose those patches. Otherwise immediately release an intermediary release, or acknowledge that a release needs to be done before RC1! We also published a proposed release schedule for the upcoming Antelope cycle. Please check out the separate thread: https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029767.ht… Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 26th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Előd Illés irc: elodilles

1 0

[charms] General release of charmhub OpenStack xena/stable, ceph pacific/stable, OVN 21.09/stable tracks for Ubuntu 20.04 (focal) LTS
by Alex Kavanagh 06 Aug '22

06 Aug '22

Hi All The title may seem a bit odd because surely yoga is the current release, and zed is the current cycle? This is true, so a little explanation is in order. As the charm-guide [1] explains, in the previous cycle, the OpenStack, and supporting, charms moved from a single stable charm (for each component) that supported multiple releases, to a charm+track that targets a specific release [2]. The current release for the OpenStack charms is 'yoga' and thus there is a yoga/stable track. For a full explanation, please see [1]. Today, as part of our ongoing charmhub stable migration work this cycle, we have (re)released the 21.10 charms (that supported queens -> xena) as "xena" charms for OpenStack, "pacific" charms for Ceph, and "21.09" charms for OVN. The xena, pacific and 21.09-OVN channel charms have the same features as the existing 21.10 charms, include bug-fixes and relevant backports since the 21.10 charms were released, and have been re-tested and verified as a set prior to being released to the xena/stable channel. The full list of charms for a "Xena" OpenStack system, including ceph, OVN, mysql8, hacluster, rabbitmq-server, vault and others can be seen in the docs at [3]. The xena/pacific/21.09 charms have been designed to be upgradable from the 21.10 charms if you are running a xena OpenStack, but please consult the docs [4] about how to go about upgrading charms. The charms also are able to perform the OpenStack upgrade from wallaby -> xena, and again please consult the docs [5] for upgrading OpenStack. Our next stable maintenance release will be wallaby/pacific/20.12 (ovn), so please keep an eye out on the mailing lists. Thanks! [1] https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html [2] https://juju.is/docs/olm/deploy-a-charm-from-charmhub#heading--specify-a-ch… [3] https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html#c… [4] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… [5] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

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

06 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 4. Most of the topics I am summarizing in this email. This was a video call and recordings are available @https://www.youtube.com/watch?v=2CFrDKJsnEY * Next TC weekly meeting will be on Aug 11 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 10. 2. What we completed this week: ========================= * Added charmed k8s operators to OpenStack Charms[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- As we are in the R-9 week, its time to plan for the 2023.1 cycle election. As first step, we have volunteer to help executing this election. In TC meeting, Amy, Knikolla, and Slaweq volunteer to help and Ian might be available any ways. If you would like to get involved in the elections help, please let us know in #openstack-tc IRC channel. 2023.1 cycle TC PTG planning ------------------------------------ In TC meeting, we were gathering the data on who all will be traveling to in-person PTG or we should consider virtual PTG. But as you might have seen the announcement today, coming PTG will be 100% virtual[5]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[6]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [7] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[8][9]. Project updates ------------------- * Retire openstack-helm-addons[10] 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[11]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [12] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/849997 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029879.… [6] https://review.opendev.org/c/openstack/governance/+/836888 [7] https://review.opendev.org/c/openstack/governance/+/849606 [8] https://etherpad.opendev.org/p/zuul-config-error-openstack [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [10] https://review.opendev.org/c/openstack/governance/+/849997 [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Fwd: October PTG Update
by Kendall Nelson 06 Aug '22

06 Aug '22

Hello Everyone, I wanted to provide an update on the October Project Teams Gathering (PTG). After discussing with community members and prospective sponsors, we have made the decision to pivot the event to 100% virtual to be as inclusive as possible. I know that this is not the ideal outcome and there are a lot of factors contributing to this decision, but we think it’s the best decision for the global community at this time. We are continuing to receive feedback on the value and importance of in-person PTGs; we just need to wait for other factors to be less of an obstacle If you have already registered, you should have been contacted for a full refund. We are going to use the same week for a virtual PTG and it will be free to attend, just like the previous ones. The registration is already live [1]. If you have any questions or feedback on this decision, please let us know. We will continue to monitor feedback as we make plans for a 2023 PTG. Thank you, Kendall (diablo_rojo) [1] https://openinfra-ptg.eventbrite.com

1 0

[manila] Feature Proposal Freeze in effect
by Carlos Silva 05 Aug '22

05 Aug '22

Greetings, Zorillas and interested stackers! As we defined in the release schedule, this week is the Manila Feature Proposal Freeze [1]. It means that all featureful changes should be already proposed and substantially completed with unit, functional and integration tests by EOW. If you have not managed to submit your featureful changes to gerrit yet, and would like to request an exception, please let me know by responding to this email thread. In case your exception is granted, we can get you some extra time. [1] https://releases.openstack.org/zed/schedule.html#z-manila-fpfreeze Thank you! carloss

1 0

[openstack] how to speed up live migration?
by Ignazio Cassano 05 Aug '22

05 Aug '22

Hello All, I am looking for a solution to speed up live migration. Instances where ram is used heavily like java application servers, live migration take a long time (more than 20 minutes for 8GB ram instance) and converge mode is already set to True in nova.conf. I also tried with post_copy but it does not change. After the first live migration (very solow) if I try to migrate again it is very fast. I presume the first migration is slow because memory fragmentation when an instance is running on the same compute node for a long time. I am looking for a solution considering the on my computing node I can have a little ram overcommit. Any case I am increasing the number of compute nodes to reduce it. Thanks Ignazio

6 21

[tripleo] gate blocker - tripleo-ci-centos-9-content-provider-wallaby
by Ananya Banerjee 05 Aug '22

05 Aug '22

Hi, We have a failure in tripleo-ci-centos-9-content-provider-wallaby which is blocking the gate. We are reverting [1] to clear the gate. Related Bug : https://bugs.launchpad.net/tripleo/+bug/1983585 [1] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/multi-node-bridg… Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

2 1

Large files multipart upload fails - OpenStack Object Storage (swift)
by Komarov, Aleksandr 05 Aug '22

05 Aug '22

Hi to all! Please suggest how to fix the situation. When uploading files larger than 100GB, at the stage of multipart-manifest validation, we get 404 error for some segments that were previously uploaded successfully. As a result, the client receives a 400 response. Uploading a large file is not possible. Logs: Aug 1 13:18:30 swift01-object01 object-server: IP - - [01/Aug/2022:13:18:30 +0000] "PUT /mpathc/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/000 00032" 201 - "PUT http://domain-name/v1/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-se…" "tx30e82374b98845bab6883-0062e7d225" "proxy-server 8367" 128.7641 "-" 21577 0 Aug 1 13:18:30 swift01-object01 container-server: IP - - [01/Aug/2022:13:18:30 +0000] "PUT /mpathb/952/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/00 000032" 201 - "PUT http://domain-name/mpathe/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucke…" "tx30e82374b98845bab6883-0062 e7d225" "object-server 24710" 0.0005 "-" 13211 0 Aug 1 14:01:46 swift01-object01 object-server: IP - - [01/Aug/2022:14:01:46 +0000] "HEAD /mpathc/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/00000032" 404 - "HEAD http://domain-name/v1/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-se…" "txf09676de38964ca299b77-0062e7dcc8" "proxy-server 8367" 0.0003 "-" 21579 0 At the same time, some segments successfully found. With files less than 50GB everything is fine.

2 2

[neutron] CI meeting on Aug 9 cancelled
by Slawek Kaplonski 05 Aug '22

05 Aug '22

Hi, I will be on PTO next week and on last CI meeting we decided to cancel CI meeting on Tuesday 9th of August. Have a great week and see You on the meeting on August 16th. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

How do I deploy OpenStack open source cloud software on Red Hat Enterprise Linux 9.0?
by Turritopsis Dohrnii Teo En Ming 05 Aug '22

05 Aug '22

Subject: How do I deploy OpenStack open source cloud software on Red Hat Enterprise Linux 9.0? Good day from Singapore, How do I deploy OpenStack open source cloud software on Red Hat Enterprise Linux 9.0? I have just downloaded RHEL 9.0 ISO using RHEL Free Developer Subscription and installed it as a virtual machine inside Oracle VM VirtualBox. Windows 10 on my laptop is the host. Alternatively, can I deploy Red Hat OpenStack Platform in a Virtual Private Server (VPS)? I can make another order for a VPS just for this purpose. I already have 2 VPS servers just for deploying Virtualmin/Webmin web hosting control panel. If you can give me links to excellent and well-written guides and tutorials, it would be most useful. I want to try out open source software developed by NASA. Also, I have deployed Nextcloud previously. Now I want to try out OpenStack. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore 5 Aug 2022 Friday Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com

2 2

[glance] Error in store configuration. Adding images to store is disabled.
by Dave Hall 05 Aug '22

05 Aug '22

Hello, (Any help on this would be greatly appreciated. I've been chasing this for 2 weeks now...) I posted the other day that I had solved this issue, but now it's back. The primary glance-api error message is: Error in store configuration. Adding images to store is disabled. So why is my store disabled? Is there some command or config line that controls this? Shouldn't the store be enabled by default? The relevant stanza in my openstack-user-config.yml is image_hosts: # infra38: # ip: 172.29.236.38 # container_vars: # limit_container_types: glance # glance_remote_client: # - what: "172.29.244.27:/images" # where: "/var/lib/glance/images" # type: "nfs" # options: "_netdev,vers=3,proto=tcp,sec=sys" infra38: ip: 172.29.236.38 container_vars: glance_default_store: file glance_nfs_local_directory: "images" glance_nfs_client: - server: "172.29.244.27" remote_path: "/images" local_path: "/var/lib/glance/images" type: "nfs" options: "_netdev,vers=3,proto=tcp,sec=sys,noauto,user" config_overrides: "{}" The stanza that's commented out produced the same result. My user_variables.yaml does not have any lines pertaining to glance. Also, I've removed the stanzas for the other 2 infra hosts. The glance-api.conf file from the container is: [DEFAULT] # Disable stderr logging use_stderr = False debug = False use_journal = True fatal_deprecations = False bind_host = 172.29.238.205 bind_port = 9292 http_keepalive = True digest_algorithm = sha256 backlog = 4096 workers = 16 cinder_catalog_info = volumev3:cinderv3:internalURL enable_v2_api = True transport_url = rabbit:// glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.84:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.174:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.239.33:5671//glance?ssl=1&ssl_version=TLSv1_2&ssl_ca_file= scrub_time = 43200 image_cache_dir = /var/lib/glance/cache/ image_cache_stall_time = 86400 image_cache_max_size = 10737418240 # defaults to true if RBD is used as default store show_image_direct_url = False show_multiple_locations = True enabled_backends = file:file,http:http,cinder:cinder [task] task_executor = taskflow [database] connection = mysql+pymysql:// glance:e6dd6f2ca946c9e6f72bb864387a@172.29.236.36/glance?charset=utf8&ssl_verify_cert=true max_overflow = 50 max_pool_size = 5 pool_timeout = 30 connection_recycle_time = 600 [keystone_authtoken] insecure = False auth_type = password auth_url = http://172.29.236.36:5000/v3 www_authenticate_uri = http://172.29.236.36:5000 project_domain_id = default user_domain_id = default project_name = service username = glance password = c96a36e76208ee26851c78670d34dcaff1c870 region_name = RegionOne service_token_roles_required = False service_token_roles = service service_type = image memcached_servers = 172.29.239.168:11211,172.29.239.242:11211, 172.29.236.80:11211 token_cache_time = 300 # if your memcached server is shared, use these settings to avoid cache poisoning memcache_security_strategy = ENCRYPT memcache_secret_key = 0b65b4b99155a6430e923fc9c24d9674 [oslo_policy] policy_file = policy.yaml policy_default_rule = default policy_dirs = policy.d [oslo_messaging_notifications] topics = notifications driver = messagingv2 transport_url = rabbit:// glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.84:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.174:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.239.33:5671//glance?ssl=1&ssl_version=TLSv1_2&ssl_ca_file= [paste_deploy] flavor = keystone+cachemanagement [glance_store] default_backend = file [file] filesystem_store_datadir = /var/lib/glance/images/ [profiler] enabled = False [oslo_middleware] enable_proxy_headers_parsing = True [cors] allow_headers = origin,content-md5,x-image-meta-checksum,x-storage-token,accept-encoding,x-auth-token,x-identity-status,x-roles,x-service-catalog,x-user-id,x-tenant-id,x-openstack-request-id allow_methods = GET,POST,PUT,PATCH,DELETE allowed_origin = https://osa-portal.cs.binghamton.edu I'd be glad to run glance-api in the foreground with debug (in the container, or course), but it's not obvious from the .service file how to do that. I'd be glad to read source code, but a pointer or two would be handy. If NFS (or Hao's GPFS) just aren't supported anymore please tell me. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 2

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 05 Aug '22

05 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

[Glance] Weekly Meeting Cancelled
by Pranali Deore 04 Aug '22

04 Aug '22

Hello, Since most of the team members will not be around today, so cancelling today's glance weekly meeting. Thanks & Regards, Pranali

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Aug 4 at 1500 UTC
by Ghanshyam Mann 04 Aug '22

04 Aug '22

Hello Everyone, Below is the agenda for Today TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting == Agenda for Today's TC meeting == * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning * 2023.1 cycle Technical Election planning * RBAC feedback in ops meetup ** https://etherpad.opendev.org/p/rbac-zed-ptg#L171 ** https://review.opendev.org/c/openstack/governance/+/847418 * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

resize or migrate problem
by fereshteh loghmani 03 Aug '22

03 Aug '22

hello I use OpenStack and I create some VMs in different compute in one region. when I resize the VM. if the compute doesn't have enough space, automatically the vm will be migrated to another compute. but my problem is here that when it migrated, the _base file doesn't migrate and remains in the first compute that it doesn't have enough space. because of this, the VM appears with an error status in OpenStack. if I move the _base from first compute to final compute and reboot the server this problem has been solved. so i need to not transfer _base manually and if it migrated to another compute the disk and _base transfer with each other. could you please help me to solve this problem? thanks in advance

2 3

[cinder] Bug deputy report for week of 08-03-2022
by Sofia Enriquez 03 Aug '22

03 Aug '22

This is a bug report from 07-27-2022 to 08-03-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1983237 "Cannot retype volume of lvm to volume of fujitsu." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1983287 "Infinidat Cinder driver fails to backup attached volume." Fix proposed to master. Cheers, Sofia -- 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

[security-sig] Any interest in getting together at the PTG?
by Jeremy Stanley 03 Aug '22

03 Aug '22

I was going to bring this up during the monthly meeting, but since I'll be unavailable the next best solution is to raise it here... Are any of the Security SIG participants planning or at least hoping to be in Columbus for the PTG this October? And if so, is there any interest in carving out some spacetime in the schedule for security discussions? We still have another week to decide, but I'm happy to put in a request for us if anyone wants that. -- Jeremy Stanley

2 1

Reminder! PTG October 2022 Team Signup Deadline
by Kendall Nelson 03 Aug '22

03 Aug '22

Hello Everyone, Don't forget to sign your team up for the next Project Teams Gathering (PTG), which will be held in Columbus, OH from Monday, October 17 to Thursday, October 20th, 2022! If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 12th, 2022 at 7:00 UTC. Then make sure to register[2] for the PTG before prices go up on August 15th! Also, please book in the official hotel block for a discounted rate[3]. Booking in the PTG hotel block helps us keep costs low for all attendees, so please encourage your teams to book here. Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com [3] Hotel Block: https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT

1 0

[kolla][ops] Anyone using the collectd and/or telegraf?
by Radosław Piliszek 03 Aug '22

03 Aug '22

Hi Kolla-flavoured OpenStackers, Any of you using the collectd and/or telegraf with Kolla Ansible? The core team is looking to deprecate their support as it's not tested and collectd is now gone from Ubuntu Jammy. Please reply to this mail. Cheers, Radek -yoctozepto

2 2

[ceilometer][gnocchi][tacker] Internal Server Error in devstack for Zuul gate job
by ueha.ayumu＠fujitsu.com 03 Aug '22

03 Aug '22

Hi telemetry team, I’m Ueha from Tacker team, The Zuul gate job of Tacker failed with the following error. Do you know the solution? The gate job has failed, so we would appreciate it if you could deal it with high priority. Thanks! for reference, the same error occurring in the ceilometer patch. (https://review.opendev.org/c/openstack/ceilometer/+/851338 ‘s telemetry-dsvm-integration-centos-9s job) ------------------ ++ /opt/stack/ceilometer/devstack/plugin.sh:start_ceilometer:322 : /usr/local/bin/ceilometer-upgrade 2022-07-29 05:20:42.125 61523 DEBUG ceilometer.cmd.storage [-] Upgrading Gnocchi resource types upgrade /opt/stack/ceilometer/ceilometer/cmd/storage.py:42 2022-07-29 05:20:42.228 61523 CRITICAL ceilometer [-] Unhandled error: gnocchiclient.exceptions.ClientException: Internal Server Error (HTTP 500) 2022-07-29 05:20:42.228 61523 ERROR ceilometer Traceback (most recent call last): 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/usr/local/bin/ceilometer-upgrade", line 10, in <module> 2022-07-29 05:20:42.228 61523 ERROR ceilometer sys.exit(upgrade()) 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/opt/stack/ceilometer/ceilometer/cmd/storage.py", line 49, in upgrade 2022-07-29 05:20:42.228 61523 ERROR ceilometer tenacity.Retrying( ......... omit ......... 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/usr/local/lib/python3.8/dist-packages/gnocchiclient/client.py", line 52, in request 2022-07-29 05:20:42.228 61523 ERROR ceilometer raise exceptions.from_response(resp, method) 2022-07-29 05:20:42.228 61523 ERROR ceilometer gnocchiclient.exceptions.ClientException: Internal Server Error (HTTP 500) 2022-07-29 05:20:42.228 61523 ERROR ceilometer ------------------ Full log: https://zuul.opendev.org/t/openstack/build/71262e66ecf34827a8a3435657aa9b3f Best Regards, Ueha

4 4

[horizon][security-sig][tc] XStatic and JS dependencies
by Jeremy Stanley 02 Aug '22

02 Aug '22

We discussed this at the PTG, and sending out a recap has been on my to do list for a few months. Sorry about the delay! The tl;dr here is that OpenStack is effectively serving as the upstream distributor for (often vulnerable versions of) JavaScript software we didn't make, and downstream consumers like GNU/Linux distributions are then directly repackaging our copies of these things, and assuming we've taken care of any security vulnerabilities for them. In the early days, we needed a way to make it possible for Horizon to consume JavaScript libraries installed on systems, typically supplied by Linux distros via system level package management. XStatic was and still is a good framework for this, providing a means of bundling up metadata which can be adjusted in deployments to tie in local copies of JS libs so that Horizon can find them, and also allowing us to conveniently use the same sorts of mappings for upstream testing as well. The original idea was that we were shipping XStatic metadata packages, and distributions would take care of supplying the actual JS bits since that's not our specialty as a community. To make our own testing easier, we embedded copies of the actual JS within our XStatic packages, which is where all of this started going horribly wrong. The rationale at the time was that distro package maintainers would know to devendor (unbundle and replace) the JS inside our XStatic packages, substituting standard ones from their distribution. What has happened instead, likely due to a confluence of convenience and lack of clear communication on our part, is that the distros took the entirety of these XStatic packages and redistributed them, JS and all. Why is that bad? Well, our approach to Python dependencies is that we freeze the versions we use at the time of our coordinated release, on the assumption that distros backport any relevant security fixes for them. That's generally okay because we're not shipping those dependencies ourselves, someone else does and takes care of fixing and communicating vulnerabilities in them. For many of the XStatic packages Horizon relies on, however, distros are treating us as the upstream supplier of that software, including the JS bundled inside it. We don't (and really can't reliably) track security vulnerabilities in our dependencies, and JS is no exception in this regard. Unfortunately, when it comes to the outdated versions of JS libs we're redistributing inside those packages, many distros assume we are doing exactly that. Worse, it's not just the Linux distros, but even our own deployment projects following the same pattern. How can we address this? The first and fastest thing we should do is to start clearly communicating that we make no effort to track or fix vulnerabilities for JS inside our XStatic packages. Readme files in all of them should get a big disclaimer added, as visible as possible, that the included "convenience" copies of JS libs in them are not for production use and should be considered insecure, to be replaced at deployment time with actual upstream copies instead (this will be noticed not just when browsing our source code, but for any subsequent releases on PyPI too). Also update any places in our documentation where XStatic packages are mentioned to point this situation out. Ideally, we should reach out to distros and deployment projects we know are installing our copies of the embedded JS libs to make sure they're aware of this problem too. In the long term, we really need to gut the JS content from the source trees of our XStatic packages and make our test jobs use something like NPM or Yarn to fetch the relevant versions at deployment time, installing them into the expected locations pointed to by the XStatic metadata. This will make it more obvious that we're not taking responsibility for the security of those libraries, since we're no longer directly supplying them. I've only got the loosest understanding of how XStatic integration works, and not much familiarity with Horizon or its testing, so am relying on Horizon's contributors to weigh in on whether this course of action is sensible and, more importantly, achievable. -- Jeremy Stanley

1 1

[TripleO], Undercloud deployment is failing with with the NTP error
by Veronika Fisarova 02 Aug '22

02 Aug '22

Good day everyone, I was trying to deploy TripleO via tripleo-quickstart following this guide <https://docs.openstack.org/tripleo-quickstart/latest/getting-started.html#>. Working environment has satisfactory requirements following specifications in the guide. Python 3.6.8. is installed. The following deployment script was used: bash quickstart.sh --tags all -R wallaby -X --teardown all -v $VIRTHOST and the deployment is failing with the following error: 2022-08-02 13:05:13,693 p=21797 u=root n=ansible | 2022-08-02 13:05:13.692871 | 008acbda-7e58-575b-6e97-00000000078a | TASK | Ensure system is NTP time synced 2022-08-02 13:10:04,147 p=21797 u=root n=ansible | 2022-08-02 13:10:04.146932 | 008acbda-7e58-575b-6e97-00000000078a | FATAL | Ensure system is NTP time synced | undercloud | error={"changed": true, "cmd": ["chronyc", "waitsync", "30"], "delta": "0:04:50.254002", "end": "2022-08-02 13:10:04.121815", "msg": "non-zero return code", "rc": 1, "start": "2022-08-02 13:05:13.867813", "stderr": "", "stderr_lines": [], "stdout": "try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 2, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 3, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 4, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 5, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 6, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 7, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 8, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 9, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 10, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 11, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 12, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 13, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 14, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 15, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 16, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 17, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 18, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 19, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 20, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 21, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 22, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 23, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 24, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 25, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 26, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 27, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 28, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 29, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 30, refid: 00000000, correction: 0.000000000, skew: 0.000", "stdout_lines": ["try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 2, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 3, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 4, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 5, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 6, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 7, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 8, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 9, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 10, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 11, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 12, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 13, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 14, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 15, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 16, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 17, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 18, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 19, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 20, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 21, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 22, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 23, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 24, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 25, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 26, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 27, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 28, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 29, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 30, refid: 00000000, correction: 0.000000000, skew: 0.000"]} 2022-08-02 13:10:04,178 p=21797 u=root n=ansible | PLAY RECAP ********************************************************************* 2022-08-02 13:10:04,178 p=21797 u=root n=ansible | localhost : ok=1 changed=0 unreachable=0 failed=0 skipped=2 rescued=0 ignored=0 2022-08-02 13:10:04,179 p=21797 u=root n=ansible | undercloud : ok=209 changed=110 unreachable=0 failed=1 skipped=50 rescued=0 ignored=2 For more information, please see the copy of the partially deployed undercloud here <https://paste.opendev.org/show/bxKvk87Y8ZH1RdboQaa3/> and here <https://paste.opendev.org/show/banD6k2R1gReYvBjN8bx/>. As far as I know, I can SSH to the deployed undercloud, but I cannot ensure if the undercloud is working properly and how many functions are missing. If you would need any additional information, please email me or use the IRC nick: deydra Any help or suggestions appreciated. -- *Veronika Fisarova* Openstack Validation Framework - Intern Red Hat <http://www.redhat.com>

1 0

[security-sig] Cancelling our August meeting
by Jeremy Stanley 02 Aug '22

02 Aug '22

Apologies for the late notice, but I have travel for an appointment conflicting with our meeting and will be unable to chair it this month. If someone else wants to run the meeting please feel free, though we don't have any pressing agenda items so it's probably fine to skip. I'm also open to holding the meeting next week instead, if anybody is interested in rescheduling. Barring any ad hoc meetings in the interim, our next scheduled meeting is 15:00 UTC on Thursday, September 1. In the meantime, Security SIG folks can be found in the #openstack-security channel on OFTC or by prepending subjects to this ML with [security-sig] of course! -- Jeremy Stanley

1 0

Horizon dashboard query
by KK CHN 02 Aug '22

02 Aug '22

Hi everyone! I need a guide or advice or anything. I am administering a private cloud in openstack. As I am using the Horizon dashboard for the VM provisioning and administering activities. But the users are sending requests in mail and creating the VMs for them. can we make workflow automation for the request and approval and provisioning automatically in the Horizon dashboard on approval? Has anyone already done /have idea on these kinds of solutions for your openstack cloud ??. Is there some kind of documentation that could help me?. Any guidance much appreciated, where to start, what to refer and which tool/programming language best if I need to code from scratch. thanks in advance. Krish

5 6

[neutron] CI meeting agenda for 2.08.2022
by Slawek Kaplonski 02 Aug '22

02 Aug '22

Hi, It's just a reminder that today at 1500 UTC we will have our CI meeting. It will be on video this time [1]. Agenda is on etherpad [2]. [1] https://meetpad.opendev.org/neutron-ci-meetings [2] https://etherpad.opendev.org/p/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0