September 2022 - openstack-discuss

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

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

22 Jul '23

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

8 30

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 30 Dec '22

30 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

[ovn][neutron] RE: OVN BGP Agent query
by Ihtisham ul Haq 19 Oct '22

19 Oct '22

Hi Luis and Daniel, Please see inline response. > From: Daniel Alvarez Sanchez <dalvarez(a)redhat.com> > Sent: 29 September 2022 11:37 > Subject: Re: OVN BGP Agent query > > Hi Ihtisham and Luis, > > On Thu, Sep 29, 2022 at 7:42 AM Luis Tomas Bolivar <ltomasbo(a)redhat.com> wrote: > > Some comments and questions inline > > > > On Tue, Sep 27, 2022 at 1:39 PM Ihtisham ul haq <ihtisham.uh(a)hotmail.com> wrote: > > > Hi Luis, > > > > > > Thanks for your work on the OVN BGP Agent. We are planning > > > to use it in our OVN deployment, but have a question regarding it. > > > > Great to hear! Can you share a bit more info about this environment? like > > openstack version, target workload, etc. We plan to use this with Yoga version. Our workload consist of enterprise users with VMs running on Openstack and connected to their enterprise network via transfer network(to which the customer neutron router is attached to). And we also have public workload but with the ovn-bgp we only want to we want to advertise the former. > > > > > The way our current setup with ML2/OVS works is that our customer VM IP routes > > > are announced via the router IP(of the that customer) to the leaf switch instead of > > > the IP of the host where the neutron BGP agent runs. And then even if the > > > router fails over, the IP of the router stays the same and thus the BGP route > > > doesn't need to be updated. > > > > Is this with Neutron Dynamic Routing? When you say Router IP, do you mean the virtual neutron router and its IP associated with the provider network? What type of IPs are you announcing with BGP? IPs on provider network or on tenant networks (or both)? Yes, that's with Neutron DR agent, and I meant virtual neutron router with IP from the provider network. We announce IPs of our tenant network via the virtual routers external address. > > If the router fails over, the route needs to be updated, doesn't it? Same IP, but exposed in the new location of the router? Correct. > The route to the tenant network doesn't change, ie. > 192.168.0.0 via 172.24.4.100 (this route remains the same regardless of where 172.24.4.100 is). > If there's L2 in the 172.24.4.0 network, the new location of 172.24.4.100 will be learnt via GARP announcement. In our case, this won't happen as we don't have L2 so we expose directly connected routes to overcome this "limitation". Right, in our case we have a stretched L2 transfer network(mentioned above) to which our gateway nodes and customer routers are connected to, so we can advertise the IPs from the tenant network via the virtual router external IP and thus the location of the router isn't relevant in case of failover as its address will be relearned. > In the case of Neutron Dynamic Routing, there's no assumption that everything is L3 so GARPs are needed to learn the new location. > > > > We see that the routes are announced by the ovn-bgp-agent via the host IP(GTW) in our > > > switch peers. If that's the case then how do you make sure that during failover > > > of a router, the BGP routes gets updated with the new host IP(where the router > > > failed over to)? > > > > The local FRR running at each node is in charge of exposing the IPs. For the IPs on the provider network, the traffic is directly exposed where the VMs are, without having to go through the virtual router, so a router failover won't change the route. > > In the case of VMs on tenant networks, the traffic is exposed on the node where the virtual router gateway port is associated (I suppose this is what you refer to with router IP). In the case of a failover the agent is in charge of making FRR to withdraw the exposed routes on the old node, and re-advertise them on the new router IP location > > > > > Can we accomplish the same route advertisement as our ML2/OVS setup, using the ovn-bgp-agent? > > I think this is technically possible, and perhaps you want to contribute that functionality or even help integrating the agent as a driver of Neutron Dynamic Routing? Sounds good, our plan currently is to add this to the ovn-bgp-agent, so we can announce our tenant routes via virtual routers external address on a stretched L2 network, to make it work with our use case. -- Ihtisham ul Haq Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>.

3 5

Re: How do I disable replication in swift
by Alvaro Soto 13 Oct '22

13 Oct '22

question: Do you want to delete replicas of old objects? o just disable it for future objects until you get more disk/nodes? for the second did you try to stop the object replicator service? On Fri, Sep 23, 2022 at 9:04 AM Paladox <thomasmulhall410(a)yahoo.com> wrote: > Thanks! But that doesn’t tell you how to disable as the value must be one > or higher? Unless it’s not 1+1 (or what ever you set as the replica value). > > On Thursday, 22 September 2022 at 19:58:41 BST, Alvaro Soto < > alsotoes(a)gmail.com> wrote: > > > Check changing the replica counts > > > https://docs.openstack.org/swift/xena/admin/objectstorage-ringbuilder.html#… > > --- > Alvaro Soto. > > Note: My work hours may not be your work hours. Please do not feel the > need to respond during a time that is not convenient for you. > ---------------------------------------------------------- > Great people talk about ideas, > ordinary people talk about things, > small people talk... about other people. > > On Thu, Sep 22, 2022, 6:54 AM Paladox <thomasmulhall410(a)yahoo.com> wrote: > > Hello, I would like Swift to only have 1 file not any copies of it, how do > I disable replication as you must set the value to 1 when you create the > rings? > > (We don’t have the disk space to have replication / copies of the files) > > -- Alvaro Soto *Note: My work hours may not be your work hours. Please do not feel the need to respond during a time that is not convenient for you.* ---------------------------------------------------------- Great people talk about ideas, ordinary people talk about things, small people talk... about other people.

3 7

[qa][ptg] Virtual PTG Planning
by Martin Kopec 11 Oct '22

11 Oct '22

Hello everyone, here is [1] our etherpad for Antelope PTG. Please, add your topics there if there is anything you would like to discuss / propose ... You can also vote for time slots of our sessions so that they fit your schedule at [2]. We will go with 3 maybe 4 one hour slots, depending on the number of topics. [1] https://etherpad.opendev.org/p/qa-antelope-ptg [2] https://framadate.org/dC2AEBTq8b5rAkvv Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 2

[ptl][tc][ops][ptg] Operator + Developers interaction (operator-hours) slots in 2023.1 Antelope PTG
by Ghanshyam Mann 11 Oct '22

11 Oct '22

Hello Everyone/PTL, As you know, one of the challenges we are facing nowadays is less interaction/feedback from operators. To solve that, OpenStack TC has been discussing it in various forum/places (Board, TC meetings). One of the ideas that came from those discussions was to bring operator and developer together in events like summit, PTG etc. On that idea, we are trying to invite more operators (especially form ops meetup attendees) in next virtual PTG. Idea is to have operators join the project PTG slots. To make it easy for operators and less conflict among projects, TC has booked a few slots as 'operator hours' in different time/day. Currently those are booked as 'operator-hour-placeholder'[1]. Project can convert/reserve them to their project operator-hour, for example 'operator-hour-nova'. How project can reserve/book these 'operator hour' (Action item for projects PTL/PTG planner): ----------------------------------------------------------------------------------------------------------------- 1. Request Kendal or Fungi (in #openinfra-events IRC channel) to register the new track 'operator-hour-<your project name>' for example, 'operator-hour-nova' 2. Once track is registered, pick one of the available 'operator-hour-placeholder' slot and book it with newly registered track 'operator-hour-<your project name>'. For example #operator-hour-nova book essex-WedB1 * Idea to book these slots as 'operator-hour-<your project name>' is to give operators a easy way to find and join. Otherwise it will be difficult for them to find such slot/time from etherpads. We request every projects to book at least one 'operator hours' slot for operators to join your PTG slot. Ping me in #openstack-tc or #openinfra-events IRC channel for any query. [1] https://ptg.opendev.org/ptg.html -gmann

1 1

[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

[nova][placement] add your PTG topics before Oct-06 please !
by Sylvain Bauza 06 Oct '22

06 Oct '22

Hi folks, as I said in the nova meeting, I'd like to create an agenda for our PTG topics. Given the PTG is in 3 weeks, please provide your topics you'd like to discuss at the PTG in [1] so I could look at them and try to provide an agenda for them. Eventually, I'd love to have most of the topics by Oct 6th as I said in the title so the agenda would be on the Friday Oct 7th. Also, if you can't be in the Nova PTG sessions for all the PTG schedule (between Tues and Fri for Nova), just add in the topic when you would like to be around. Thanks, -Sylvain [1] https://etherpad.opendev.org/p/nova-antelope-ptg

1 1

[Swift][Ussuri] Erasure Coding Quarantines
by Reid Guyett 05 Oct '22

05 Oct '22

Hello, I'm not sure if it is related, but I am testing reimaging a node from Ubuntu 18.04 to 20.04 (Cloud Archive Ussuri 2.25.1 to Focal Repo Ussuri 2.25.2) in a 3-node cluster. I have a lot of servers to upgrade, and the environments will be mixed for a while, so I have left this mixed for a week. Now the 18.04 servers are starting to accumulate quarantined EC objects. The 20.04 server has log messages indicating that it is unable to get enough responses from the reconstructor. The 18.04 servers have a couple EC messages. "...liberasurecode[30807]: Invalid fragment header information!" followed by "...object-server: Quarantined object /srv/node/d9/objects-4/10321/b2e/50a3dce515aafc6f222824ec5c7dfb2e/1664002866.33100#8#d.data: Invalid EC metadata at offset 0x0 Is there any thing you can think of that would cause this issue? My steps to reproduce: 1. Create a container in an EC policy 2. Upload object to EC container 3. Wait a bit of time (It looks like the object-server is quarantining but not sure on the trigger) 4. Try to download the file and it will give a 504 Looking at python3-swift dependencies and the package versions I thought may affect this: 20.04 libjerasure2 = 2.0.0+2017.04.10.git.de1739cc84-1 python3-pyeclib = 1.6.0-6build1 python3-xattr = 0.9.6-1.1 18.04 libjerasure2 = 2.0.0+2017.04.10.git.de1739cc84-1 python3-pyeclib = 1.3.1-1ubuntu3 python3-xattr = 0.9.2-0ubuntu1 Thanks! Reid Important Notice: This email is intended to be received only by persons entitled to receive the confidential and legally privileged information it presumptively contains, and this notice constitutes identification as such. Any reading, disclosure, copying, distribution or use of this information by or to someone who is not the intended recipient, is prohibited. If you received this email in error, please notify us immediately at legal(a)kaseya.com, and then delete it. To opt-out of receiving emails Please click here<https://info.kaseya.com/email-subscription-center.html>. The term 'this e-mail' includes any and all attachments.

3 6

[kolla-ansible] How to recover from unfinished upgrade
by wodel youchi 05 Oct '22

05 Oct '22

Hi, I am testing the upgrade from xena to yoga and I made a mistake in globals.yml, I forgot to specify the correct name of gnocchi ceph pool, so my deployment went wrong. I interrupted the deployment Ctrl+C I corrected the mistake, then I restarted the upgrade and it got stuck somewhere else, but I couldn't find where, I interrupted then restarted the deployment again and it got stuck at the same place. My questions : - Is there a way to rollback the upgrade in case of a problem, then start over? - What is the best way to restart a broken upgrade process? Regards.

2 2

[TripleO] TripleO Antelope PTG Topics
by Rabi Mishra 05 Oct '22

05 Oct '22

Hi All, Please add your session proposals to this etherpad[1]. We'll reserve time allocation based on proposed topics and work out a schedule in the coming weeks. [1] https://etherpad.opendev.org/p/tripleo-antelope-topics -- Regards, Rabi Mishra

2 4

[neutron] PTG topics and scheduling
by Rodolfo Alonso Hernandez 03 Oct '22

03 Oct '22

Hello all: Based on the schedule polls results, I've booked the Neutron meetings from Tuesday to Thursday in Mitaka channel [1], from 13UTC to 16UTC. Of course, if that is not enough, we can always use Friday to continue any pending conversation. The operator hour (actually 2), will be on Friday (pending for reservation), from 13UTC to 15UTC. Please continue adding any topic you want to discuss in the Neutron etherpad [2]. There is a specific section for the Nova-Neutron cross-team meeting. If you have any doubt or question, do not hesitate to let me know (IRC: ralonsoh, mail: ralonsoh(a)redhat.com) You can also ping any core reviewer in #openstack-neutron channel. See you in a few weeks! [1]https://ptg.opendev.org/ptg.html [2]https://etherpad.opendev.org/p/neutron-antelope-ptg

3 3

[all][tc] What's happening in Technical Committee: summary 2022 Sept 30: Reading: 5 min
by Ghanshyam Mann 01 Oct '22

01 Oct '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 29. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-29-15.00.log.html * Next TC weekly meeting will be a video call on Oct 6 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Oct 5. 2. What we completed this week: ========================= * Goal proposal of 'Migrating CI/CD testing from Ubuntu 20.04 to 22.04' is merged [2] * 2023.1 cycle leaderless projects: PTL appointment done for below projects: ** Adjutant[3] ** Keystone[4] ** Masakari[5] ** OpenStack_Charms[6] ** Sahara[7 ** Senlin[8] ** Swift[9] ** Venus[10] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[11], Five are completed and other items are in-progress. Open Reviews ----------------- * Five open reviews for ongoing activities[12]. Dedicating Zed release to Ilya Etingof -------------------------------------------- As you might know, there is sad news of Ilya Etingof (Ironic contributor) passed away on Aug 10[13] and we will be dedicating the Zed release to Ilya[14] New community-wide goal "Migration CI/CD to Ubuntu 22.04" -------------------------------------------------------------------------------------- The goal proposal is merged[15]. Dmitriy will propose this goal to be selected for 2023.1 cycle. 2023.1 cycle Leaderless projects & TC Chair ---------------------------------------------------- * PTL appointments for 8 projects are done. Zun project PTL appointment is under review[16]. * TC Chair: TC members are in the progress to select the chair for the next term. 2023.1 cycle TC PTG planning ------------------------------------ * JayF sent the ICS invite of TC PTG slots on ML[17] * Etherpads to add the topics: ** https://etherpad.opendev.org/p/tc-2023-1-ptg ** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 * I sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[18] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[19]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- We discussed the Zuul config error for zuul 'queue' syntex[20]. Also added it in the zuul config error etherpad[21 ]. Requesting projects have zuul config errors in their jobs to look into those and fix them asap. As most of the errors occur while project renaming/retiring, I am adding a separate step about it in the project rename/retiring process[22]. Project updates ------------------- * None. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[23]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [24] 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/+/858690 [3] https://review.opendev.org/c/openstack/governance/+/858967 [4] https://review.opendev.org/c/openstack/governance/+/858969 [5] https://review.opendev.org/c/openstack/governance/+/858974 [6] https://review.opendev.org/c/openstack/governance/+/858973 [7] https://review.opendev.org/c/openstack/governance/+/858975 [8] https://review.opendev.org/c/openstack/governance/+/858976 [9] https://review.opendev.org/c/openstack/governance/+/858978 [10] https://review.opendev.org/c/openstack/governance/+/858979 [11] https://etherpad.opendev.org/p/tc-zed-tracker [12] https://review.opendev.org/q/projects:openstack/governance+status:open [13] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030062.… [14] https://review.opendev.org/c/openstack/governance/+/859464 [15] https://review.opendev.org/c/openstack/governance/+/858690 [16] https://review.opendev.org/c/openstack/governance/+/858980 [17] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0306… [18] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [19] https://review.opendev.org/c/openstack/governance/+/836888 [20] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0305… [21] https://etherpad.opendev.org/p/zuul-config-error-openstack [22] https://review.opendev.org/c/openstack/project-team-guide/+/859886 [23] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [24] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[Diversity] Diversity and Inclusion WG meeting reminder
by Amy Marrich 01 Oct '22

01 Oct '22

The D&I WG will be meeting Monday at 15:00 UTC. The meeting will be held on video at https://meetpad.opendev.org/osf-diversity-and-inclusion and the agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. Thanks, Amy (spotz)

1 0

[release] Release countdown for week R+0, Oct 3 - 7
by Előd Illés 30 Sep '22

30 Sep '22

Development Focus ----------------- We will be releasing the coordinated OpenStack Zed release next week, on October 5th, 2022. Thanks to everyone involved in the Zed cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the virtual PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.openstack.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 5th, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

TLS error when cloning https://opendev.org/openstack/devstack
by Neil Jerram 30 Sep '22

30 Sep '22

Anyone else seeing this? neil@glaurung:~/tt$ git clone https://opendev.org/openstack/devstack Cloning into 'devstack'... remote: Enumerating objects: 28589, done. remote: Counting objects: 100% (28589/28589), done. remote: Compressing objects: 100% (9638/9638), done. error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet. fatal: early EOF fatal: fetch-pack: invalid index-pack output Best wishes, Neil -- Neil Jerram Principal Software Engineer Tigera neil(a)tigera.io | @neiljerram <http://twitter.com/neiljerram> Follow Tigera: Blog <https://blog.tigera.io/> | Twitter <https://twitter.com/tigeraio> | LinkedIn <https://www.linkedin.com/company/tigera/> Security and observability for containers, Kubernetes, and cloud <https://tigera.io/>

5 14

Oracle Linux 6 VM volume performance
by Quang Long 30 Sep '22

30 Sep '22

Hi Openstack-users, I am having a problem with I/O performance on VM running Oracle Linux 6, I/O throughput on VM Oracle Linux 6 is much lower than VM using another OS (Ubuntu, CentOS). - VM Oracle Linux 6: throughput 40 MBps https://prnt.sc/buKscX_qEtcF - Other VM: throughput 113 MBps https://prnt.sc/IRhBUPrGgLOy - Test tool: dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync; rm -f test My Enviroment: - Openstack: Ussuri - Ceph: Octopus 15.2.8 - Compute: CentOS8_x86_64, kernel: 4.18.0-240.15.1.el8_3.x86_64 - KVM: qemu-kvm-5.2.0-16.el8.x86_64 - VM Oracle linux6: kernel-uek-4.1.12-124.42.3.el6uek.x86_64 I think because the kernel of Oracle Linux 6 is too old, maybe an older KVM version could support it, and now KVM does not optimize for this OS. Could you guy can help me with this? -- *Lê Quang Long* 0942.533.683 | 0977.116.502

2 2

Oracle Linux 6 VM disk performance
by Quang Long 30 Sep '22

30 Sep '22

Hi Openstack-users, I am having a problem with I/O performance on VM running Oracle Linux 6, I/O throughput on VM Oracle Linux 6 is much lower than VM using another OS (Ubuntu, CentOS). - VM Oracle Linux 6: throughput 40 MBps https://prnt.sc/buKscX_qEtcF - Other VM: throughput 113 MBps https://prnt.sc/IRhBUPrGgLOy - Test tool: dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync; rm -f test My Enviroment: - Openstack: Ussuri - Ceph: Octopus 15.2.8 - Compute: CentOS8_x86_64, kernel: 4.18.0-240.15.1.el8_3.x86_64 - KVM: qemu-kvm-5.2.0-16.el8.x86_64 - VM Oracle linux6: kernel-uek-4.1.12-124.42.3.el6uek.x86_64 I think because the kernel of Oracle Linux 6 is too old, maybe an older KVM version could support it, and now KVM does not optimize for this OS. Could you guy can help me with this? -- *Lê Quang Long* 0942.533.683 | 0977.116.502

1 0

Live Migration Issues
by Alexander Dibbo - STFC UKRI 30 Sep '22

30 Sep '22

Hi All, I'm having a few issues with live migration at the moment. This is an openstack train deployed with rdo packages. 1. when migrating some VMs the migration succeeds but the VM doesn't move and the following error can be found in the nova logs with nothing that seems to correspond in the neutron logs: 2022-09-30 11:04:04.069 716669 INFO nova.compute.manager [-] [instance: c10d1d9e-2baf-4ab5-ba3a-2f60f521aea6] Took 76.49 seconds for pre_live_migration on destination host hv548.nubes.rl. ac.uk. 2022-09-30 11:04:04.720 716669 ERROR nova.virt.libvirt.driver [-] [instance: c10d1d9e-2baf-4ab5-ba3a-2f60f521aea6] Live Migration failure: 'fa:ca:ad:1f:71:41' 2. When migrating some VMs the migration is marked as complete and the VM is moved from the source to the destination hypervisor but nova keeps the migrating state and doesn't update the host or the node fields. The following error is found in nova with no corresponding error that I can find in neutron. The config is the same across all hypervisors. 2022-09-13 10:37:23.709 12387 ERROR nova.network.neutronv2.api [req-ee51a8b4-911c-4f92-860b-9d6a7a24c786 27be800439c244c1bd742ff056cf700c 4de86830e89b4a46b590536571b6ccd4 - 38372510d9bb4ac7916178b062d387de 38372510d9bb4ac7916178b062d387de] Neutron client was not able to generate a valid admin token, please verify Neutron admin credential located in nova.conf: neutronclient.common.exceptions.Unauthorized: 401-{'error': {'message': 'The request you have made requires authentication.', 'code': 401, 'title': 'Unauthorized'}} 2022-09-13 10:37:23.845 12387 ERROR oslo_messaging.rpc.server [req-ee51a8b4-911c-4f92-860b-9d6a7a24c786 27be800439c244c1bd742ff056cf700c 4de86830e89b4a46b590536571b6ccd4 - 38372510d9bb4ac7916178b062d387de 38372510d9bb4ac7916178b062d387de] Exception during message handling: nova.exception.NeutronAdminCredentialConfigurationInvalid: Networking client is experiencing an unauthorized exception. Regards Alexander Dibbo - Cloud Architect / Cloud Operations Group Leader For STFC Cloud Documentation visit https://stfc-cloud-docs.readthedocs.io<https://stfc-cloud-docs.readthedocs.io/> To raise a support ticket with the cloud team please email cloud-support(a)stfc.ac.uk<mailto:cloud-support@stfc.ac.uk> To receive notifications about the service please subscribe to our mailing list at: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STFC-CLOUD To receive fast notifications or to discuss usage of the cloud please join our Slack: https://stfc-cloud.slack.com/ This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.

1 0

[all] Skip level upgrades (SLURP) grenade job
by Slawek Kaplonski 30 Sep '22

30 Sep '22

Hi, As You may know there some time ago TC merged resolution about release cadence adjustment [1]. According to that resolution starting from 2023.1 (Antelope) will be first "SLURP" release. That means that upgrade directly from 2023.1 to 2024.1 ("C") needs to be supported so projects will need to run "skip-level" grenade job [2]. To start that effort and see how it works currently and what needs to be done/fixed by teams we (TC) would like to ask teams to add such job to CI in the current (2023.1) cycle already. That job will test upgrade from Yoga to master (2023.1). You can refer to the Manila job [3] and do something similar in Your project. If that job will cause some problems, You can make it non-voting temporary and work on fix it but we highly recommend to have this job voting already. If You would have any questions, please reach out to us here or on the #openstack-tc IRC channel. [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad… [2] https://github.com/openstack/grenade/blob/b1cd7a1866ee7d17392bd9896db6060d4… [3] https://review.opendev.org/c/openstack/manila/+/859875 -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Image Encryption] No meeting on Monday
by Josephine Seifert 30 Sep '22

30 Sep '22

Hi, Monday the 3. of October is a national holiday. So there will not be a meeting for the Image Encryption pop up team. cheers, Luzi

1 0

[ironic] Stable & Bugfix branch maintenance and retirement
by Jay Faulkner 30 Sep '22

30 Sep '22

Hi folks, I'm letting you all know it's my intention to, very soon, perform the following actions on all Ironic projects: 1) Perform a release for any maintained stable and bugfix branches (EM stable branches excluded by policy) 2) Retire all stable branches for releases prior to stable/train (For Ironic; this is queens, rocky, and stein -- I have not enumerated them yet for other projects). If you either have code you'd like to ensure gets in the stable release or want to step up and volunteer to maintain the older branches -- including backporting existing bugfixes that did not make it back that far and maintaining CI -- please let me know within the next couple of days. Thanks, Jay Faulkner OpenStack Ironic PTL OpenStack TC member

1 0

[neutron] Drivers meeting agenda -30.09.2022.
by Lajos Katona 29 Sep '22

29 Sep '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFE to discuss: * [RFE] Expose Open vSwitch other_config column in the API (#link https://bugs.launchpad.net/neutron/+bug/1990842 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[kolla][centos][rdo] NOTICE: OVS version mismatch between Wallaby and later
by Radosław Piliszek 29 Sep '22

29 Sep '22

Dears, This is a notice to users of OVS with Kolla with CentOS-Stream-8-based images or RDO directly. It seems that RDO Wallaby currently installs OVS 2.17 while later ones install OVS 2.15. The problem is that currently: *** Upgrades from Wallaby to Xena will cause OVS to misbehave and lose all network connectivity until host reboot. *** This is because downgrades of running OVS are not supported. We are investigating this issue, please stay tuned to this topic. The solution we believe to be the correct one now is to bump OVS to 2.17 also in later branches of RDO. Kind regards, Radek -yoctozepto

1 1

[Glance] Weekly Meeting Cancelled
by Pranali Deore 29 Sep '22

29 Sep '22

Hello, This week's upstream meeting is cancelled, since there is nothing on agenda for today. Thanks & Regards, Pranali Deore

1 0

[kolla][ssl] Deploy third-party SSL for HAProxy
by Satish Patel 29 Sep '22

29 Sep '22

Folks, I have GoDaddy SSL cert and trying to deploy with kolla but little big confused with this doc https://docs.openstack.org/kolla-ansible/latest/admin/tls.html I have a single interface for internal/external vip and try following config to deploy SSL/TLS for haproxy and other services. --- openstack_release: "wallaby" kolla_internal_vip_address: "10.73.0.180" kolla_external_vip_address: "{{ kolla_internal_vip_address }}" network_interface: "eth0" neutron_external_interface: "eth1" # TLS kolla_enable_tls_internal: "yes" kolla_certificates_dir: "/etc/kolla/certificates" kolla_internal_fqdn_cert: "{{ kolla_certificates_dir }}/my_company_cert.pem" When i run "kolla-ansible -i multinode certificates" command it deploy something but then i found it generated certificate itself (self-sign) in /etc/kolla/cacertificates directory and override my third-party cert When I tried in the browser https://foobar.com it didn't connect to 443 port that means it did not enable SSL. Am I missing something here?

2 8

(no subject)
by fereshteh loghmani 29 Sep '22

29 Sep '22

in kolla ansible (release: victoria) when i run command: " kolla-ansible -i ./multinode bootstrap-servers --limit compute1 " i receive this error: TASK [baremetal : Enable docker apt repository] * fatal: [R5DG1.cpaas.ir]: FAILED! => {"changed": false, "msg": "apt cache update failed"} could you please help me how could i fix this? ( my compute1 has the ubuntu20 )

2 1

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

29 Sep '22

Hello Everyone, Below is the agenda for Tomorrow's TC meeting scheduled 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 ** 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' *** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… * 2023.1 cycle Technical Election & Leaderless projects ** Leaderless projects *** https://etherpad.opendev.org/p/2023.1-leaderless ** TC Chair election * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[cinder][outreachy] Internship proposal 💻
by Sofia Enriquez 29 Sep '22

29 Sep '22

Hello Argonauts, As discussed in Cinder Meeting two weeks ago[1], I've created the internship proposal Etherpad[2]. Please, feel free to add comments and in particular, if you have any suggestions on the benefits please add them. The deadline is this Friday. Thanks in advance, Cheers, Sofi [1] https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-09-21-14.00.l… [2] https://etherpad.opendev.org/p/outreachy-cinder-dec-2022-to-march-2023 -- 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

[kolla-ansible] Error while upgrading from xena to yoga
by wodel youchi 28 Sep '22

28 Sep '22

Hi, I am trying to upgrade from xena to yoga. I have created a test environment that resembles the production one using VMs. The deployment consists of 03 controllers and 03 compute/storage nodes. I am using Rokcy 8 as my base OS and I am using another VM as a deployer with a local registry. I followed the documentation here : https://docs.openstack.org/kolla-ansible/yoga/user/operating-kolla.html The precheks went well, but when deploying I got the following error : fatal: [ctrl02]: FAILED! => {"changed": true, "msg": "'Traceback (most > recent call last):\\n > File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line > 268, in _raise_for_status\\n > response.raise_for_status()\\n File > \"/usr/local/lib/python3.6/site-packages/requests/models.py\", line 960, > in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\n > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: > http+docker://localhost/v1.41/images/create?tag=yoga& > fromImage=10.50.0.252%3A4000%2Fopenstack.kolla%2Fcentos-source-rabbitmq\\n\\nDuring > handling of the above exception, > another exception occurred:\\n\\nTraceback (most recent call last):\\n > File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", > line 381, > in main\\n File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", > > line 660, in recreate_or_restart_container\\n self.pull_image()\\n > File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", > > line 451, in pull_image\\n repository=image, tag=tag, stream=True\\n > File \ > "/usr/local/lib/python3.6/site-packages/docker/api/image.py\", line 430, > in pull\\n self._raise_for_status(response)\\n > File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line > 270, in _raise_for_status\\n > raise create_api_error_from_http_exception(e)\\n File > \"/usr/local/lib/python3.6/site-packages/docker/errors.py\", > line 31, in create_api_error_from_http_exception\\n raise cls(e, > response=response, explanation=explanation)\\n > docker.errors.NotFound: 404 Client Error for > http+docker://localhost/v1.41/images/create?tag=yoga > &fromImage=10.50.0.252%3A4000%2Fopenstack.kolla%2Fcentos-source-rabbitmq: > Not Found > *(\"manifest for > 10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq:yoga > <http://10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq:yoga> not > found: manifest unknown: manifest unknown\")\\n'"}* > [deployer@deployer yoga]$ sudo docker images | grep yoga | grep rabbit quay.io/openstack.kolla/centos-source-rabbitmq yoga 4ea3207bfef3 33 hours ago 920MB 10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq yoga 4ea3207bfef3 33 hours ago 920MB Any ideas? Regards.

2 2

[release][requirements][oslo][nova] How to fix a bug and release the fix in oslo.concurrency 4.5.x series
by Balazs Gibizer 28 Sep '22

28 Sep '22

Hi, So we have a bug[1] that was fixed in oslo.concurrency on master[2] and released as 5.0.1 and Zed is released with 5.0.1. The issue is present in stable/yoga as well. There we have oslo.concurrency upper constraint pinned to 4.5.0 [3]. 1) How can I backport [2] to the 4.5.x series of oslo.concurrency to release 4.5.2 with the fix? I don't see a branch that I could use for this. 2) If #1) is solved and 4.5.2 is released can I propose an upper constraint bump on stable/yoga from 4.5.0 to 4.5.2? 3) If #1) and #2) is done. Can I propose a minimum requirement bump in nova's requirements.txt from >= 4.5.0 to >= 4.5.2 on stable/yoga? Cheers, gibi [1] https://bugs.launchpad.net/nova/+bug/1988311 [2] https://review.opendev.org/c/openstack/oslo.concurrency/+/855714 [3] https://github.com/openstack/requirements/blob/e64217c9f9316675f57e14ff559b…

4 5

[cinder] Bug Report 09-28-2022
by Sofia Enriquez 28 Sep '22

28 Sep '22

This is a bug report from 09-21-2022 to 09-28-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1990053 "Cinder NFS backend with image-volume cache creates volumes with the wrong size." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1990846 "NetApp FC: Not filterings WWPNs correctly in multiple HA pair deployments." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1990946 "Dell PowerFlex: Size shown for a volume doesn't match powerflex backend allocation." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1991068 "Duplicate config option barbican in tempest plugins cinder and barbican." Unassigned. - https://bugs.launchpad.net/os-brick/+bug/1939390 "Missing dependency: lsscsi." Unassigned. Incomplete - https://bugs.launchpad.net/os-brick/+bug/1990825 "Should wait for all devices to appear?." Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Regarding Magnum configuration on Xena Openstack
by Adivya Singh 27 Sep '22

27 Sep '22

Hi Team, Can we have standard inputs to put and test to implement Containerization in Xena Openstack installed using ansible Regards Adivya Singh

2 3

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

27 Sep '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: 28th September, 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

Unable to create access rules 'state:error' | Wallaby | Tripelo | NetApp
by Swogat Pradhan 27 Sep '22

27 Sep '22

Hi, When i am trying to create access rule for manila share, the rules are created in error state. Here is the manila share log: 2022-09-23 19:03:58.557 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status 2022-09-23 19:04:01.720 26 INFO manila.share.manager [req-3d66c534-a782-414b-a0a7-2bdd57f57b8f - - - - -] Updating share status 2022-09-23 19:04:58.554 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server [req-5f035b4a-7dc8-4e61-bbd5-d38d4b81a00d c1905e3c5a374924980e851840e7f028 5d922243077045c48fe4b075e386551b - - -] Exception during message handling: manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 216, in wrapped 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/utils.py", line 568, in wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3965, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server_id=share_server_id) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3981, in update_access_for_instances 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 302, in update_access_rules 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 341, in _update_access_rules 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 409, in _update_rules_through_share_driver 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/drv_single_svm.py", line 104, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server delete_rules, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py", line 2347, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server helper.update_access(share, share_name, access_rules) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 36, in wrapped_func 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return source_func(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 391, in inner 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 34, in source_func 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 115, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server auth_methods = self._get_auth_methods() 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 222, in _get_auth_methods 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server kerberos_enabled = self._client.is_kerberos_enabled() 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_cmode.py", line 1896, in is_kerberos_enabled 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = self.send_request('kerberos-config-get', api_args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_base.py", line 90, in send_request 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server use_zapi=use_zapi) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 710, in invoke_successfully 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server na_element, api_args=api_args, enable_tunneling=enable_tunneling) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 380, in invoke_successfully 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server raise NaApiError(code, msg) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist Please suggest how to mitigate this issue. With regards, Swogat Pradhan

2 2

[tacker] Critical bug report and backport the fix
by Yuta Kazato 27 Sep '22

27 Sep '22

Hi tacker team, As you know, new bug report #1990793 [1] related to K8s resource name and v2 API is submitted by Masaki. The bug will appear if K8s resource name contains `-`. I think this is a critical issue because users often set resource names that contain `-`. Fortunately, the fix patch [2] has already been submitted. I suggest that we should backport the fix patch to the stable/zed branch before Zed release. What do you think? [1] https://bugs.launchpad.net/tacker/+bug/1990793 [2] https://review.opendev.org/c/openstack/tacker/+/859206 Yuta -- Yuta Kazato (風戸雄太) NTT Network Innovation Center. tel: +81-422-59-6754 mail: yuta.kazato.nw(a)hco.ntt.co.jp

3 2

Create the TripleO container images using the command in Xena
by Suranga Prabhath 27 Sep '22

27 Sep '22

Hi All, I.m going to install OpenStack Xena on CentOS 8.5. I'm following the TripleO in RDO Xena Release. I followed the RDO guide & enable the required packages. Package installation is successful, but the pulling of the triple container imagers using the command was unsuccessful. Here is the command I use. openstack tripleo container image build --base ubi8 --debug --distro centos \ --namespace tripleoxena --prefix openstack --tag cloudsig-xena \ --push --registry 172.22.1.10::8787 \ --volume /etc/yum.repos.d:/etc/distro.repos.d:z --volume /etc/pki/rpm-gpg:/etc/pki/rpm-gpg:z --volume /etc/dnf/vars:/etc/dnf/vars:z \ --work-dir ~/workdir After executing the above command error was received & I attach it to this mail. Please provide me with a solution for this. -- Thanks & Regards, *Suranga Prabhath,* System Administrator hSenid Software International *Sri Lanka* *M* : +94 00 000 0000 *P* : +94 11 268 3751 *F* : +94 11 268 3951 *Singapore* *M* : +65 00 000 000 *P* : +65 65 332 140 *F* : +65 62 910 023 <http://www.hsenid.com/> <http://www.hsenidmobile.com/> <https://www.facebook.com/hSenid.Software.International/> <https://twitter.com/hsenid_biz> <https://www.linkedin.com/company/hsenid-business-solutions> <https://www.youtube.com/user/hsenidbiz> *www.hSenid.com* <http://www.hsenid.com/> <https://www.google.com/url?q=http://www.hsenidmobile.com/&source=gmail-html…> *Disclaimer*: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. The content and opinions contained in this email are not necessarily those of hSenid Mobile Solutions. If you have received this email in error please contact the sender.

1 0

[kolla-ansible][Yoga] What are the benefits to run libvirt daemon on host rather on a container?
by wodel youchi 27 Sep '22

27 Sep '22

Hi, What are the benefits to run libvirt daemon directly on the host rather than on a container? In Yoga's release note, it is said : "Currently this is only supported for fresh deployments without an existing nova_libvirt container" But Also it it is said : "Adds a kolla-ansible nova-libvirt-cleanup command, which may be used to clean up the nova_libvirt container. This may be useful if switching to a host libvirt daemon". Is switching supported? I am in ther verge of upgrading from Xena to Yoga and I ma wondering about this. - What is the gain to use libvirt daemon? - Could the switch be done after the upgrade to Yoga? Regards.

2 1

[kolla-ansible] question about network nodes number
by wodel youchi 27 Sep '22

27 Sep '22

Hi, Is it a good idea to configure more than 02 network nodes? Regards.

2 1

[ptls][zed] OpenInfra Live: OpenStack Zed
by Allison Price 26 Sep '22

26 Sep '22

Hi everyone, As we get closer to the OpenStack release, I wanted to reach out to see if any PTLs were interested in providing their Zed cycle highlights in an OpenInfra Live[1] episode on Thursday, October 6 at 1400 UTC. Ideally, we would get 4-6 projects represented. Previous examples of OpenStack release episodes can be found here[2] and here[3]. Please let me know if you’re interested and I can provide next steps. If you would like to provide a project update but that time doesn’t work for you, please share a recording with me and I can get it added to the project navigator. Thanks, Allison [1] https://openinfra.dev/live/ <https://openinfra.dev/live/> [2] https://www.youtube.com/watch?v=hwPfjvshxOM <https://www.youtube.com/watch?v=hwPfjvshxOM> [3] https://www.youtube.com/watch?v=aqilhEmkEBw <https://www.youtube.com/watch?v=aqilhEmkEBw>

1 1

[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

[neutron] bug deputy report of week 2022-09-19
by Bence Romsics 26 Sep '22

26 Sep '22

Hi All, Here comes last week's deputy report (we had only a handful of reports): Unassigned: * https://bugs.launchpad.net/neutron/+bug/1990229 [OVN] Stop using external_ids from SB Chassis table Edit Medium: * https://bugs.launchpad.net/neutron/+bug/1990129 [ovn-octavia-provider] Avoid LB in ERROR status on delete due to LR/LS not found proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/857716 Low: * https://bugs.launchpad.net/neutron/+bug/1990285 Help for `network create --external` is incorrect Edit proposed fix: https://review.opendev.org/c/openstack/python-openstackclient/+/858708 Incomplete: * https://bugs.launchpad.net/neutron/+bug/1990561 Network filtering by provider attributes has a race condition with network removal Cheers, Bence

1 0

Re: RE : RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
by mhazan＠mandint.org 26 Sep '22

26 Sep '22

no joy with the accept_ra fiddling, the image are all ubuntu or debian cloud-init ready and are working on all in one node but not dedicated compute node, it's as if the dhcpv6 packet (before address is allocated to interface) are not passing between the control node and the dedicated compute node. Le 2022-09-20 10:53, Michael Hazan a écrit : > Thanks for the suggestion, i will look into the accept_ra setting. However, the very same image that boot on the « old » all in one node are getting ipv6 and ipv4 without issue. The network interfaces are configured similarly on all nodes. > > Michael > > DE : Neil Jerram > ENVOYÉ LE :mardi, 20 septembre 2022 10:47 > À : Michael Hazan > CC : Lajos Katona; openstack-discuss(a)lists.openstack.org > OBJET :Re: RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6 > > They may be outdated now, but I wonder if any of the steps described at https://projectcalico.docs.tigera.io/networking/openstack/ipv6 would help you? In particular, given that you have no route, perhaps you need the accept_ra config. > > Best wishes, > > Neil > > On Tue, Sep 20, 2022 at 9:12 AM Michael Hazan <mhazan(a)mandint.org> wrote: > >> Hello, >> >> The 3 nodes are running Ubuntu 20.04 and using libvirt. The instance are Ubuntu or debian based. The openstack virtual network is configured with both a v4 and a v6 dhcp pool. The instance should be getting both v4 and v6 (on the same interface) but the instance that are hosted on the compute node only get v4. If i run the dhclient -6 -r the instance actually get it's ipv6 but it's wrongly configured with a /128 (instead of 64) and no route. >> >> Michael >> >> DE : Lajos Katona >> ENVOYÉ LE :mardi, 20 septembre 2022 09:39 >> À : mhazan(a)mandint.org >> CC : openstack-discuss(a)lists.openstack.org >> OBJET :Re: [neutron][nova][ipv6]instance on compute node not getting dhcpv6 >> >> Hi, >> >> Do you have some more details of your environment, which backend you use? OVS? >> >> Your VMs have both IPv4 and v6 addresses and you mean that they got IPv4 as expected? >> >> Lajos >> >> <mhazan(a)mandint.org> ezt írta (időpont: 2022. szept. 19., H, 16:19): >> >> Hello all, >> >> i manage a small openstack cluster installed via Ubuntu package, it has >> been upgraded since the day of Newton and currently running Victoria. it >> started as a single node with the basic services installed, later a >> dedicated storage node and compute node were added. after upgrading to >> victoria, any instance that boot on the dedicated compute node start up >> but fails to get it's global ipv6 via stateful dhcp6, only >> linklocal(fe80) ip is shown by the instance. The ipv6 is created in >> openstack, the dhcpv4 works and there are no issue if the instance boot >> on the "old" all in one node. i can manually allocate (by editing the >> instance network config file) the ipv6 config and it works. any pointer >> as to what could cause this issue ? >> >> BR, Michael

1 1

[magnum][heat][requirements][release] Potential blocker for release with python-magnumclient 4.0.0
by Tony Breeds 26 Sep '22

26 Sep '22

Hello all, In [1] baymodel code was removed, although it still seems to be listed in the API-ref. Story [2] states it's been deprecated for a long time, but a quick check failed to see this documented anywhere. Heat still supports baymodel and the removal is causing failures. Blocking the use of python-magnumclient 4.0.0[3] inzed, even though the 4.0.0 release is clearly meant for zed. I can see a couple of paths forward. 0. Remove the documentation in the api-ref for baymodels 1. Remove the support in heat for baymodels (I think the newer clusters API can be used instead?) 2. Revert the change in magnumclient and re-release etc etc 3. Keep 4.0.0 for the Antelope release, and reset the stable/zed branch python-magnumclient to fd0cb1e (before the removal of baymodels) Obviously option 1 looks like the least disruptive change, but potentially causes a problem for heat depending on the published state of baymodel support [1] https://review.opendev.org/c/openstack/python-magnumclient/+/803629 [2] https://storyboard.openstack.org/#!/story/2009104 [3] https://review.opendev.org/c/openstack/requirements/+/858089 -- Yours Tony.

3 4

[openstack-helm] OpenStack-Helm PTG
by Gage Hugo 26 Sep '22

26 Sep '22

Hey team, The next PTG is coming up (Oct 17-21). I've booked a slot for project discussions on Tue Oct 18th @ 1500 UTC Please sign up to the etherpad if you wish to propose any topics: https://etherpad.opendev.org/p/oct2022-ptg-openstack-helm See you there!

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Sept 23: Reading: 5 min
by Ghanshyam Mann 24 Sep '22

24 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 22. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-22-15.00.log.html * Next TC weekly meeting will be on Sept 29 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 28. 2. What we completed this week: ========================= * Antelope Elections[2]. Thanks to all the leaders who step up for the role. Also thanks to the election official. * Updated node.js version to 18 in 2023.1 testing runtime[3] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[4], Five are completed and other items are in-progress. Open Reviews ----------------- * Thirteen open reviews for ongoing activities[5]. New community-wide goal proposal "Migration CI/CD to Ubuntu 22.04" -------------------------------------------------------------------------------------- As we decided to migrate the CI/CD testing from Ubuntu 20.04 to 22.04 in 2023.1 cycle, we need to define this task as a community-wide goal. This work requires more testing than changes which are covered in base jobs. The goal proposal is under review[6]. Thanks, Dmitriy to compose and volunteer to drive this goal. 2023.1 cycle Leaderless projects & TC Chair ---------------------------------------------------- * We had 9 projects that missed the PTL nomination but the good news is that we found the leaders for all 9 projects now[7]. TC is discussing their appointment on gerrit reviews. * TC Chair: we have two nominations for the TC Chair[8][9] which is really a good thing having multiple people stepping up for the role. We will keep nomination open until Tuesday (27 Sept) if anyone else also would like to add a nomination. On Tuesday, we can start the CIVS poll among TC members to select the chair for next term. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * TC decided to meet at the below slots [10]: ** Monday 15:00 - 17:00 UTC (2 hours) for TC+leaders interaction discussion. ** Thursday 15:00 - 19:00 UTC (4 hours) ** Friday 15:00 - 19:00 UTC (4 hours) * Etherpads: ** https://etherpad.opendev.org/p/tc-2023-1-ptg ** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 * I sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[11] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[12]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[13]14]. Project updates ------------------- * None. 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[15]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [16] 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/+/858539 [3] https://review.opendev.org/c/openstack/governance/+/856927 [4] https://etherpad.opendev.org/p/tc-zed-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance/+/858690 [7] https://etherpad.opendev.org/p/2023.1-leaderless [8] https://review.opendev.org/c/openstack/governance/+/858947 [9] https://review.opendev.org/c/openstack/governance/+/858957 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0305… [11] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [12] https://review.opendev.org/c/openstack/governance/+/836888 [13] https://etherpad.opendev.org/p/zuul-config-error-openstack [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [15] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [16] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[manila] Antelope PTG planning
by Carlos Silva 24 Sep '22

24 Sep '22

Greetings, Zorillas and interested stackers! At this point, I bet you already know that the PTG is coming. It goes from 17th to 21st of October 2022, and if you have not registered yet, there is still time! [1] We have already booked the slots for our discussions, please add it to your agenda: 17th: 16:00 UTC to 17:00 UTC (Monday) 19th: 14:00 UTC to 17:00 UTC (Wednesday) 20th: 14:00 UTC to 17:00 UTC (Thursday) 21st: 13:00 UTC to 17:00 UTC (Friday) Please add the topics you would like to bring up to our planning etherpad [2]. Looking forward to meeting you there! [1] https://openinfra.dev/ptg/ [2] https://etherpad.opendev.org/p/antelope-ptg-manila-planning - carloss

1 0

[release] Release countdown for week R-1, Sep 26 - 30
by Előd Illés 23 Sep '22

23 Sep '22

Development Focus ----------------- We are on the final mile of the Zed development cycle! Remember that the Zed final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. September 29th, 2022 is the deadline for final Zed release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on October 5th, 2022. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the 2023.1 Antelope development cycle, including discussing Forum and PTG sessions content, in preparation of Virtual PTG @ October 17-21, 2022. Actions ------- Watch for any translation patches coming through on the stable/zed branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/zed branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release ! Upcoming Deadlines & Dates -------------------------- Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

[kolla] Antelope PTG
by Michał Nasiadka 23 Sep '22

23 Sep '22

Greetings Koalas, As you most probably know the OpenStack Antelope PTG is coming soon (17-21th Oct 2022). I’ve booked the usual slots (Mon-Wed) for Kolla project group (Kolla, Kolla-Ansible, Kayobe) with Wed being primary a slot for Kayobe. For operator-focus - the Kolla projects Operator Hour is booked for Tue, 16-17 UTC. Please sign up to the ether pad https://etherpad.opendev.org/p/kolla-antelope-ptg <https://etherpad.opendev.org/p/kolla-antelope-ptg> and propose topics. See you on the PTG! Best regards, Michal Nasiadka

1 0

[nova][ironic][ptg] Improved ironic<>nova driver interactions session
by Jay Faulkner 23 Sep '22

23 Sep '22

Hello Nova folks, At the Ironic PTG planning meeting this morning, discussion of improving Nova and Ironic driver interactions; and specifically this spec: https://review.opendev.org/c/openstack/nova-specs/+/842015/ came up. It's important for our teams to come together and reach consensus as to how to fix this. According to the latest OpenStack user survey ( https://www.openstack.org/analytics/) over 20% of Nova deployments utilize the Ironic driver. However, in my years operating Ironic for multiple different organizations, the Nova<>Ironic driver interface has repeatedly been the source of most operational pain. We should work together to prioritize saving these operators from downtime and bad failure semantics. I'd love for Ironic and Nova to schedule a session together to talk about this and try to find a solution. We owe it to our users to no longer shy away from this hard technical problem and fix things. What's the best way for us to get this time scheduled? Someone can feel free to reach out to me on IRC (JayF), or reply here and I'm sure we can work it out. Thanks in Advance, Jay Faulkner G-Research Open Source Software lab OpenStack Ironic PTL OpenStack Technical Committee member

2 1

Swift not recognizing mounted drives
by Andrew Boring 23 Sep '22

23 Sep '22

Hi all. I have a new Openstack Swift install, currently a single node with 12 disks running CentOS 8 Stream and Openstack Yoga / RDO release with Keystone Auth. Disks are formatted with xfs and mounted at /srv/node/sd[a-l] as described in the Install docs, but no Swift services reccognize it. SELinux is set to permissive mode. Log sample: Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sda is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdb is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdc is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdd is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sde is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdf is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdg is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdh is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdi is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdj is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdk is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdl is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Beginning replication run Sep 22 11:29:01 [hostname] account-replicator[182475]: Replication run OVER Sep 22 11:29:01 [hostname] account-replicator[182475]: Attempted to replicate 0 dbs in 0.00344 seconds (0.00000/s) Sep 22 11:29:01 [hostname] account-replicator[182475]: Removed 0 dbs Sep 22 11:29:01 [hostname] account-replicator[182475]: 0 successes, 144 failures Sep 22 11:29:01 [hostname] account-replicator[182475]: diff:0 diff_capped:0 empty:0 hashmatch:0 no_change:0 remote_merge:0 rsync:0 ts_repl:0 Container and Object processes show the same issue. And yet...devices are mounted: [root@swift]# mount | grep srv /dev/sdb on /srv/node/sdb type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdc on /srv/node/sdc type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdd on /srv/node/sdd type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sde on /srv/node/sde type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdf on /srv/node/sdf type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdg on /srv/node/sdg type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdh on /srv/node/sdh type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdi on /srv/node/sdi type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdj on /srv/node/sdj type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdk on /srv/node/sdk type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdl on /srv/node/sdl type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sda on /srv/node/sda type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) And the rings are built: [root@swift]# swift-ring-builder /etc/swift/account.builder /etc/swift/account.builder, build version 13, id 415987b4753847e9924147119872d547 2048 partitions, 3.000000 replicas, 1 regions, 1 zones, 12 devices, 0.00 balance, 0.00 dispersion The minimum number of hours before a partition can be reassigned is 1 (0:16:41 remaining) The overload factor is 0.00% (0.000000) Ring file /etc/swift/account.ring.gz is up-to-date Devices: id region zone ip address:port replication ip:port name weight partitions balance flags meta 0 1 1 172.16.2.2:6202 172.16.2.2:6202 sda 100.00 512 0.00 1 1 1 172.16.2.2:6202 172.16.2.2:6202 sdb 100.00 512 0.00 2 1 1 172.16.2.2:6202 172.16.2.2:6202 sdc 100.00 512 0.00 3 1 1 172.16.2.2:6202 172.16.2.2:6202 sdd 100.00 512 0.00 4 1 1 172.16.2.2:6202 172.16.2.2:6202 sde 100.00 512 0.00 5 1 1 172.16.2.2:6202 172.16.2.2:6202 sdf 100.00 512 0.00 6 1 1 172.16.2.2:6202 172.16.2.2:6202 sdg 100.00 512 0.00 7 1 1 172.16.2.2:6202 172.16.2.2:6202 sdh 100.00 512 0.00 8 1 1 172.16.2.2:6202 172.16.2.2:6202 sdi 100.00 512 0.00 9 1 1 172.16.2.2:6202 172.16.2.2:6202 sdj 100.00 512 0.00 10 1 1 172.16.2.2:6202 172.16.2.2:6202 sdk 100.00 512 0.00 11 1 1 172.16.2.2:6202 172.16.2.2:6202 sdl 100.00 512 0.00 Bash certainly thinks they are actually mounted and writable: [root@swift ~]# ls -l /srv/node/sda total 0 [root@swift ~]# touch /srv/node/sda/file [root@swift ~]# ls /srv/node/sda file [root@swift ~]# umount /dev/sda [root@swift ~]# ls /srv/node/sda [root@swift ~]# mount /srv/node/sda/ [root@swift ~]# ls /srv/node/sda file [root@swift ~]# rm /srv/node/sda/file rm: remove regular empty file '/srv/node/sda/file'? y And Swift is configured to look at /srv/node for the devices: [root@swift ~]# grep devices /etc/swift/*.conf /etc/swift/account-server.conf:devices = /srv/node /etc/swift/container-server.conf:devices = /srv/node /etc/swift/object-server.conf:devices = /srv/node Running "swift info" shows the expected configuration output, but "swift stat" throws this error: [root@controller ~]# swift stat Account HEAD failed: https:/[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8 403 Forbidden Failed Transaction ID: tx9128250987cb4e07ad55d-00632c8d05 and the logs show account-server throwing "507 ERROR Insufficient Storage" before 503, and then returning a 403. [root@swift ~]# journalctl -b | grep tx9128250987cb4e07ad55d-00632c8d05 Sep 22 12:27:49 [hostname] account-server[182505]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdc/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0004 "-" 182505 - Sep 22 12:27:49 [hostname] proxy-server[182464]: ERROR Insufficient Storage 172.16.2.2:6202/sdc (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:49 [hostname] account-server[182515]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdj/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0004 "-" 182515 - Sep 22 12:27:49 [hostname] proxy-server[182464]: ERROR Insufficient Storage 172.16.2.2:6202/sdj (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:49 [hostname] account-server[182514]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdh/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0011 "-" 182514 - Sep 22 12:27:49 [hostname] proxy-server[182464]: ERROR Insufficient Storage 172.16.2.2:6202/sdh (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:49 [hostname] account-server[182506]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdl/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0011 "-" 182506 - Sep 22 12:27:49 [hostname] account-server[182504]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdf/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0010 "-" 182504 - Sep 22 12:27:49 [hostname] account-server[182504]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdi/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0002 "-" 182504 - Sep 22 12:27:49 [hostname] proxy-server[182464]: Handoff requested (4) (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] account-server[182512]: 172.16.2.2 - - [22/Sep/2022:16:27:50 +0000] "HEAD /sda/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0011 "-" 182512 - Sep 22 12:27:50 [hostname] proxy-server[182464]: Handoff requested (5) (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] account-server[182494]: 172.16.2.2 - - [22/Sep/2022:16:27:50 +0000] "HEAD /sde/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0010 "-" 182494 - Sep 22 12:27:50 [hostname] proxy-server[182464]: Handoff requested (6) (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] account-server[182506]: 172.16.2.2 - - [22/Sep/2022:16:27:50 +0000] "HEAD /sdk/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0003 "-" 182506 - Sep 22 12:27:50 [hostname] proxy-server[182464]: Account HEAD returning 503 for [507, 507, 507] (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] proxy-server[182464]: - - 22/Sep/2022/16/27/50 HEAD /v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8%3Fformat%3Djson HTTP/1.0 503 - Swift - - - - tx9128250987cb4e07ad55d-00632c8d05 - 0.0337 RL - 1663864069.976659298 1663864070.010398626 - Sep 22 12:27:51 [hostname] proxy-server[182464]: [IP] 172.16.2.2 22/Sep/2022/16/27/51 HEAD /v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8%3Fformat%3Djson HTTP/1.0 403 - python-swiftclient-3.13.1 gAAAAABjLI0FH9MP... - - - tx9128250987cb4e07ad55d-00632c8d05 - 1.4298 - - 1663864069.970289707 1663864071.400121450 - No data is being written to the disks by Swift: [root@swift ~]# ls -lR /srv/node /srv/node: total 0 drwxr-xr-x. 2 swift swift 6 Sep 22 11:13 sda drwxr-xr-x. 2 swift swift 6 Sep 22 11:07 sdb drwxr-xr-x. 2 swift swift 6 Sep 22 11:07 sdc ... /srv/node/sda: total 0 /srv/node/sdb: total 0 /srv/node/sdc: total 0 ... What am I missing here?

2 5

[dev][security-sig] Revisiting tarfile, or "What's old is new again"
by Jeremy Stanley 23 Sep '22

23 Sep '22

The tarfile module from Python's standard library is in the news this week, with people publicly exploiting the very long-standing CVE-2007-4559[0] (yes, you read that correctly, *2007*). Some old-timers in the community might remember this from such popular hits as OSSA-2011-001: Path traversal issues registering malicious images using EC2 API[1], our very first OpenStack Security Advisory! This revived interest in unsafe use of tarfile methods will undoubtedly have lots of people scanning OpenStack's Git repos looking for potentially exploitable calls. Indeed, some of our own community members are already auditing the collective codebase to make sure new vulnerabilities haven't sneaked in over the 11 years since this first came up for us, but more help is always welcome. I encourage anyone using tarfile in their projects to double-check you're doing so safely[2]. If you rely bandit to check your source code, be advised that the most recent 1.7.4 release doesn't catch this but you can install its main branch[3] instead which does include a check for it, at least until they tag a new release (which I have a feeling they'll do quite soon given the recent furor around this topic). On a related note, I want to take this opportunity to remind everyone that OpenStack has a Security Special Interest Group (SIG), which meets monthly[4] on IRC, and members will also be in attendance at the upcoming virtual PTG[5] in case anyone is interested in discussing this or similar subject matter. Our PTG slot is currently booked for 15:00 UTC Wednesday (2022-10-19), though we can adjust or book an additional hour at another time if this conflicts with any tracks people also need to join, just let me know. [0] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4559 [1] https://security.openstack.org/ossa/OSSA-2011-001.html [2] https://docs.python.org/3/library/tarfile.html#tarfile.TarFile.extractall [3] https://github.com/pycqa/bandit [4] https://meetings.opendev.org/#OpenStack_Security_SIG_meeting [5] https://ptg.opendev.org/ptg.html -- Jeremy Stanley

2 1

[ironic][ptg] Last call for topics
by Jay Faulkner 22 Sep '22

22 Sep '22

This morning, a group of Ironic cores met and mapped out a rough schedule for our PTG sessions. Please review the etherpad here: https://etherpad.opendev.org/p/ironic-antelope-ptg for more details on the outcome of that. We did want to give one last chance for anyone who has not yet had a chance to add their topic to do so before the plans are finalized. Please add any additional topics to the etherpad, and preferably, also respond to this email or let us know in #openstack-ironic on IRC. Thanks, Jay Faulkner G-Research Open Source Software lab OpenStack Ironic PTL OpenStack Technical Committee member

1 0

How do I disable replication in swift
by Paladox 22 Sep '22

22 Sep '22

Hello, I would like Swift to only have 1 file not any copies of it, how do I disable replication as you must set the value to 1 when you create the rings? (We don’t have the disk space to have replication / copies of the files)

2 2

[neutron] Drivers meeting - Friday 22.09.2022 - cancelled
by Lajos Katona 22 Sep '22

22 Sep '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

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

Floating IP attached to octavia not working | tripleo wallaby | centos | OVN DVR
by Swogat Pradhan 22 Sep '22

22 Sep '22

Hi, I've deployed Octavia + OVN + DVR and floating IPs assigned to Octavia VIPs are not reachable. Other floating IPs tied to nova instances are working fine. The octavia vip is reachable and working fine from inside on the private network, however the Floating IP is not reachable at all. I found a similar issue in bugzilla but the bug is closed now and i do not have any solution. https://bugzilla.redhat.com/show_bug.cgi?id=1608951 Please help me get a solution for this issue. With regards, Swogat pradhan

3 3

[ansible-os-modules] Antelope PTG in October | Ansible OpenStack Collection
by Jakob Meng 22 Sep '22

22 Sep '22

Hi everyone, we have scheduled our Antelope's vPTG session for the Ansible OpenStack Collection [1] at the same time and place as in April: at 13:00 - 15:00 UTC on Thursday October 20, 2022 in Essex room. Topics will be our migration progress to openstacksdk's first major release, new features, notable changes and open todos. Do not hesitate to add any questions and topics you want to address in our PTG session to etherpad [2]. Looking forward to meet you ☺️ [1] https://opendev.org/openstack/ansible-collections-openstack [2] https://etherpad.opendev.org/p/oct2022-ptg-os-ansible-modules Thanks, Ananya, Arx, Rafael, Sagi and Jakob

1 0

[openstack][quuens][cinder] consistency groups bug ?
by Ignazio Cassano 22 Sep '22

22 Sep '22

Hi everyone, in my openstack installation, for performance reasons, I use a cinder type to address different storage virtual machines on the same device. Balancing takes place via the scheduler. Below is an example of my configuration in cinder.conf: https://paste.openstack.org/show/b0hCTsdniLhinoQiVT7A/ As you can see nfsgold1 to nfsgold8 are all part of the volume type nfsgold. Unfortunately if I create a consistency group with volume type nfsgold, it can only contain volumes on the same backend, even though they are of the same type. For example, if in my consistency group there is a volume on nfsgold1 and I add a volume present on nfsgold8 I get the following: https://paste.openstack.org/show/b4XnUeGDF5wYlCBLTcuc/ Any help, please ? Ignazio

2 3

cloud Stack Testing
by KK CHN 22 Sep '22

22 Sep '22

List, We have deployed Openstack wallaby using kolla-ansible openstack installation . The setup is up and running with default configurations all-in-one node ... Reference: https://docs.openstack.org/project-deploy-guide/kolla-ansible/wallaby/quick… 1. We need to test this cloud stack for Compute, Network, and storage able to scale across multiple local and remote zones. What other components/configurations needed to be configured /built for this purpose? What are the testing parameters to check the above setup scale across multiple local and remote zones? or what methods/procedures need to be performed for this testing ? 2. for Successful deployment of enterprise applications having enough scaling and availability requirements in each IaaS, SaaS & PaaS category may further help in evaluating this setup across these categories. Is there any such kind of benchmarking tools or sample application/s to test the capacity to kindly share the name/details of such application/s to deploy as PoC? Any help/hints much appreciated. Thanks in advance, Krish

2 1

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

22 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 * Zed cycle tracker checks ** 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' *** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… * 2023.1 cycle Technical Election & Leaderless projects ** https://governance.openstack.org/election/ ** https://etherpad.opendev.org/p/2023.1-leaderless ** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304… * Meeting time check ** We have new TC members. Let's check if the current meeting time is ok for everyone. * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[all][elections][tc][ptl] Antelope: Technical Committee & PTL Election Conclusion & Results
by Ian Y. Choi 22 Sep '22

22 Sep '22

Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Technical Committee (TC) & Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability thank you to all those who make this process possible. 1. Please join me in congratulating the 4 newly elected members of the TC: Dan Smith (dansmith)Ghanshyam Mann (gmann)Jay Faulkner (JayF)Dmitriy Rabotyagov (noonedeadpunk) Full results:https://civs1.civs.us/cgi-bin/results.pl?id=E_41d42603087bcf58 2. For the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Barbican : Grzegorz Grasza (xek)* Blazar : Pierre Riteau (priteau)* Cinder : Rajat Dhasmana ()* Cloudkitty : Rafael Weingartner ()* Cyborg : alex song ()* Designate : Michael Johnson (johnsom)* Ec2 Api : Andrey Pavlov (andrey-mp)* Freezer : ge cong ()* Glance : Pranali Deore (pdeore)* Heat : Brendan Shephard ()* Horizon : Vishal Manchanda (vishalmanchanda)* Ironic : Jay Faulkner (JayF)* Kolla : Michal Nasiadka (mnasiadka)* Kuryr : Roman Dobosz (gryf)* Magnum : Jake Yip (jakeyip)* Manila : Carlos Silva (carloss)* Monasca : Martin Chacon Piza (chaconpiza)* Murano : Rong Zhu (zhurong)* Neutron : Rodolfo Alonso Hernandez ()* Nova : Sylvain Bauza (bauzas)* Octavia : Gregory Thiemonge (gthiemonge)* Openstack Chef : Lance Albertson (Ramereth)* OpenStack Helm : Gage Hugo (gagehugo)* OpenStackAnsible : Dmitriy Rabotyagov (noonedeadpunk)* OpenStackSDK : Artem Goncharov (gtema)* Puppet OpenStack : Takashi Kajinami (tkajinam)* Quality Assurance : Martin Kopec (kopecmartin)* Rally : Andrey Kurilin (andreykurilin)* Skyline : Wenxiang Wu (wu_wenxiang)* Solum : Rong Zhu (zhurong)* Storlets : Takashi Kajinami (tkajinam)* Tacker : Yasufumi Ogawa (yasufum)* Telemetry : Matthias Runge (mrunge)* Tripleo : Rabi Mishra (ramishra)* Trove : wu chunyang (wuchunyang)* Vitrage : Eyal Bar-Ilan ()* Watcher : chen ke ()* Winstackers : Lucian Petrut ()* Zaqar : Hao Wang () PTL Election:* Ironic: https://civs1.civs.us/cgi-bin/results.pl?id=E_c7d81a19f30c67f0 Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Ian Y. Choi, on behalf of the OpenStack Technical Election Officials

4 4

OpenStack PTG, Neutron schedule
by Rodolfo Alonso Hernandez 22 Sep '22

22 Sep '22

Hello Neutrinos: This is the poll to vote for the Neutron schedule during the next OpenStack PTG. The goal is to have at least 3 hours per day, from Monday to Thursday. The second poll is to decide the operator hour for Neutron [2], according to [3]. I'll keep the polls open until next Monday 26 Sep. Then I'll reserve the room in [3]. Thank you for participating. [1]https://doodle.com/meeting/participate/id/dwmlAVra [2]https://doodle.com/meeting/participate/id/eZVRoxge [3]https://ptg.opendev.org/ptg.html

1 0

[cinder] Bug Report 09-21-2022
by Sofia Enriquez 21 Sep '22

21 Sep '22

This is a bug report from 09-14-2022 to 09-21-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1989514 "NFS volume snapshot does not update volume attachment format to qcow2." Fix proposed to master. Low - https://bugs.launchpad.net/cinder/+bug/1989730 "Dell PowerMax - Optimized SL should be assigned when retyping a volume to a default volume type." Fixed proposed to master. - https://bugs.launchpad.net/cinder/+bug/1990136 " Dell PowerFlex: Failed to attach a volume when using self-signed Certificates." Fixed proposed to master. - https://bugs.launchpad.net/cinder/+bug/1990134 "Tatlin driver does not set project id for temp volumes." Fixed proposed to master. -- 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

[ironic] Looking for downstream users of bugfix/* branches
by Jay Faulkner 21 Sep '22

21 Sep '22

Hey all, Ironic releases intermediate bugfix releases during the cycle. These are consumed by some packagers and standalone users of Ironic. Today, using Ironic as an example, we have 4 active bugfix branches: - bugfix/21.0 and bugfix/20.2 are between yoga and zed - bugfix/19.0 is between xena and yoga - bugfix/18.1 is between wallaby and xena We are considering cleaning up some of the older bugfix branches, to reduce stable maintenance load -- but we would like to poll you all first: Is anyone consuming these releases downstream? If so, which ones and why? This will be useful input to whatever action we decide to take! Thanks, Jay Faulkner

2 1

[ironic] Proposing Harald Jensas to metalsmith-core
by Iury Gregory 21 Sep '22

21 Sep '22

Hello ironic-cores and metalsmith-cores, I would like to propose Harald Jensas for metalsmith-core. During the Zed Cycle he had a lot of reviews for the project [1], in yoga he contributed a lot to the project [2]. Looking at all the releases in stackalytics he is #6 in commits [3] and reviews [4]. Please vote with +1/-1 (till Sep 25) [1] https://www.stackalytics.io/?release=zed&module=opendev.org/openstack/metal… [2] https://www.stackalytics.io/?release=yoga&module=opendev.org/openstack/meta… [3] https://www.stackalytics.io/?release=all&module=opendev.org/openstack/metal… [4] https://www.stackalytics.io/?release=all&module=opendev.org/openstack/metal… -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL Yoga and Zed Cycle* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

5 4

[tacker][ptg] Virtual PTG Planning
by Yasufumi Ogawa 21 Sep '22

21 Sep '22

Hi Tacker team, I've updated the etherpad for our antelope PTG [1] as I mentioned in the previous IRC meeting. Please add your topics if you have any suggestions for the next release. [1] https://etherpad.opendev.org/p/tacker-antelope-ptg Cheers, Yasufumi

1 0

[keystone] Changing user password_hash directly in database
by 박경원 21 Sep '22

21 Sep '22

1 0

CFP Open - Ubuntu Summit 2022
by T. Nichole Williams 21 Sep '22

21 Sep '22

Greetings everyone, Your friendly neighborhood Kata Community Manager checking in to let you all know that the call for presentations[2] is now open for Ubuntu Summit 2022[1]. The event will be held from November 7-9, 2022 in Prague, Czech Republic. The Ubuntu Summit (FKA the Ubuntu Developer Summit) will include a series of talks, workshops, panels and Q&A covering a broad range of topics to appeal not only to developers, but anyone involved in open source. The event is organized into the following tracks: • Ubuntu Desktop • Community • Data Science & Data Platforms • Application Ecosystem • Infrastructure Though in-person attendance is preferred, there is a virtual option for those unable to travel. CFP will close September 30, 2002, so if you have a presentation (or workshop) on OpenStack ready to go, please send it in! Regards, T. Nichole Williams Technical Community Manager | Kata Containers Twitter: OGtrilliams GitHub: OGtrilliams IRC: PagliaccisCloud [1] https://events.canonical.com/event/2/ [2] https://events.canonical.com/event/2/abstracts/

1 0

[tripleo] Gate blocker NODE_FAILURES when running tripleo-ci-centos-9-scenario010-standalone
by Amol Kahat 20 Sep '22

20 Sep '22

Hello All, Description of problem: NODE_FAILURE when running tripleo-ci-centos-9-scenario010-standalone job. We have been seeing this failure[1] since 09/17. Logs are not present so it's hard to say what is the root cause of this issue. This job uses nodeset: single-centos-9-node-nested-virt - so assumption is that it's the nest-virt nodeset [1] https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-scenario010-… Thanks, -- *Amol Kahat* Software Engineer *Red Hat India Pvt. Ltd. Pune, India.* akahat(a)redhat.com B764 E6F8 F4C1 A1AF 816C 6840 FDD3 BA6C 832D 7715

3 2

Query about networking-onos for newer OpenStack releases
by Aditya Sathish 20 Sep '22

20 Sep '22

Hello! I am trying to integrate an SDN controller with our lab's OpenStack network. Currently, we have already deployed a version of ONOS to serve our needs and I have been following the SONA project which uses the networking-onos ML2 plugin with OpenStack. However, it seems that the networking-onos project has been retired since the Train release. Is there any way I can get ONOS to work with OpenStack Yoga? If not, what is the go-to way to integrate an SDN controller with OpenFlow support with Neutron?? Any help will be much appreciated. Regards, Aditya.

2 1

[ironic] Check PTG topics
by Iury Gregory 20 Sep '22

20 Sep '22

Hello ironicers, The Antelope PTG is in a a few weeks, we had the idea to check the PTG topics (so we can group some before setting the final schedule) Please vote in the doodle [1] for a time where we can discuss a bit o/ Feel free to add topics to our etherpad! [2] Thanks! [1] https://doodle.com/meeting/participate/id/dBL8ZZXa [2] https://etherpad.opendev.org/p/ironic-antelope-ptg -- *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 2

Re: RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
by Neil Jerram 20 Sep '22

20 Sep '22

They may be outdated now, but I wonder if any of the steps described at https://projectcalico.docs.tigera.io/networking/openstack/ipv6 would help you? In particular, given that you have no route, perhaps you need the accept_ra config. Best wishes, Neil On Tue, Sep 20, 2022 at 9:12 AM Michael Hazan <mhazan(a)mandint.org> wrote: > Hello, > > The 3 nodes are running Ubuntu 20.04 and using libvirt. The instance are > Ubuntu or debian based. The openstack virtual network is configured with > both a v4 and a v6 dhcp pool. The instance should be getting both v4 and v6 > (on the same interface) but the instance that are hosted on the compute > node only get v4. If i run the dhclient -6 -r the instance actually get > it’s ipv6 but it’s wrongly configured with a /128 (instead of 64) and no > route. > > > > Michael > > > > *De : *Lajos Katona <katonalala(a)gmail.com> > *Envoyé le :*mardi, 20 septembre 2022 09:39 > *À : *mhazan(a)mandint.org > *Cc : *openstack-discuss(a)lists.openstack.org > *Objet :*Re: [neutron][nova][ipv6]instance on compute node not getting > dhcpv6 > > > > Hi, > > Do you have some more details of your environment, which backend you use? > OVS? > > Your VMs have both IPv4 and v6 addresses and you mean that they got IPv4 > as expected? > > > > Lajos > > > > <mhazan(a)mandint.org> ezt írta (időpont: 2022. szept. 19., H, 16:19): > > Hello all, > > i manage a small openstack cluster installed via Ubuntu package, it has > been upgraded since the day of Newton and currently running Victoria. it > started as a single node with the basic services installed, later a > dedicated storage node and compute node were added. after upgrading to > victoria, any instance that boot on the dedicated compute node start up > but fails to get it's global ipv6 via stateful dhcp6, only > linklocal(fe80) ip is shown by the instance. The ipv6 is created in > openstack, the dhcpv4 works and there are no issue if the instance boot > on the "old" all in one node. i can manually allocate (by editing the > instance network config file) the ipv6 config and it works. any pointer > as to what could cause this issue ? > > BR, Michael > > >

2 1

[kuryr] Antelope PTG topics
by Maysa De Macedo Souza 20 Sep '22

20 Sep '22

Hello, The Antelope PTG is a few weeks away and if you have any topics to discuss in the Kuryr session, feel free to include it in the etherpad[1]. Cheers, Maysa Macedo. [1] https://etherpad.opendev.org/p/kuryr-antelope-ptg

1 0

[neutron][nova][ipv6]instance on compute node not getting dhcpv6
by mhazan＠mandint.org 20 Sep '22

20 Sep '22

Hello all, i manage a small openstack cluster installed via Ubuntu package, it has been upgraded since the day of Newton and currently running Victoria. it started as a single node with the basic services installed, later a dedicated storage node and compute node were added. after upgrading to victoria, any instance that boot on the dedicated compute node start up but fails to get it's global ipv6 via stateful dhcp6, only linklocal(fe80) ip is shown by the instance. The ipv6 is created in openstack, the dhcpv4 works and there are no issue if the instance boot on the "old" all in one node. i can manually allocate (by editing the instance network config file) the ipv6 config and it works. any pointer as to what could cause this issue ? BR, Michael

3 2

[neutron] dhcp/dnsmasq issue after upgrade to queens
by Benedikt Trefzer 19 Sep '22

19 Sep '22

Hello out there I'm stuck with neutron not starting any dnsmasq processes after upgrading neutron to the queens release (yes I know this is an elderly version ;)) Details: I see errors from neutron-dhcp-agent (on the dhcp host and on the controller node for the neutron-rpc-server): ValueError: Unrecognized attribute(s) 'binding:host_id' But I'm pretty sure this is a followup of the directory /var/lib/neutron/dhcp ($state_path) beeing almost empty (only empty directories named by the networks beeing there, which are rebuild by the neutron-dhcp-agent if deleted). I'm further do not see any ports in the DB for dhcp. Which eventually explains why the state files for dnsmasq are missing. So now I'm stuck: - Which agent/daemon should create the ports for the dnsmasq process ? The installation should launch two dhcp processes on two router nodes (HA setup). Which is also correctly shown using neutron dhcp-agent-list-hosting-net which shows two dhcp-agents up and running ! Any hints how to solve are appreciated ! Greetings Benedikt

1 0

[CloudKitty] Virtual PTG October 2022
by Rafael Weingärtner 19 Sep '22

19 Sep '22

Hello everyone, As you probably heard our next PTG will be held virtually in October. We've marked October 17, at 14:00-16:00 UTC [1]. We already have a CloudKitty meeting organized for this day. Therefore, it seems the most practical choice. However, if you guys would like some other dates and/or time, just let me know. The room we selected is called "Essex". 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://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/oct2022-ptg-cloudkitty -- Rafael Weingärtner

1 0

[neutron] bug deputy report September 12th to 18th
by Miguel Lavalle 19 Sep '22

19 Sep '22

Hi, Here's this week's bugs deputy report: Requires follow up ============== High ==== https://bugs.launchpad.net/neutron/+bug/1989480 [OVN] Neutron server floods logs with hash ring messages on startup. Assigned to Lucas Gomes. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/857463 Medium ====== https://bugs.launchpad.net/neutron/+bug/1989460 [ovn-octavia-provider] HealthMonitor event received on port deleted. Assigned to Fernando Royo. Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/857365 https://bugs.launchpad.net/neutron/+bug/1989979 Unexpected number of DHCP interfaces for metadata proxy. Assigned to MIguel Lavalle (mlavalle) RFE === Incomplete ======== https://bugs.launchpad.net/neutron/+bug/1989986 changing dns_domain on the charm does not propagate to ovn

1 0

Container not appearing
by Lee, Vincent Z 17 Sep '22

17 Sep '22

Hi all, I am facing issues with making containers to appear on my gui. I have managed to run a container, however, it is not showing it on horizon dashboard. [cid:3761763c-eed0-4912-af5f-4a4e91d7da1f] When I tried to create a container, it will be successfully [cid:067852ef-34b3-40c5-a590-757a192eb556] [cid:56d30ba1-c65b-4dfa-ab91-41e872332e29] Best, Vincent

2 1

[all][tc] What's happening in Technical Committee: summary 2022 Sept 16: Reading: 5 min
by Ghanshyam Mann 17 Sep '22

17 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 15. Most of the meeting discussions are summarized in this email. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-15-15.00.log.html * Next TC weekly meeting will be on Sept 22 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 21. 2. What we completed this week: ========================= * Switched release management to distributed leadership [2] * Retired panko projects [3] * Add Keystone OpenID Connect charm to OpenStack charms [4] * 2023.1 cycle testing runtime: 2023.1 cycle testing runtime is defined and merged [5], As feedback by the Horizon team, I am updating Node.JS version also to 18.0[6]. As discussed in last cycle PTG, we are moving to the python version testing template to unversioned name[7] and will control/update the new stable branch and cycle changes in central place in openstack-zuul-jobs repo. With that we do not need to update the each project repo on every release by release bot patches. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[8], four are completed and others items are in-progress. Open Reviews ----------------- * Two open reviews for ongoing activities[9]. 2023.1 cycle Technical Election (TC + PTL) -------------------------------------------------- We will have election voting for TC and Ironic project. The voting is open until Sept 19. Please follow the election official emails for actions/things to do. We had 9 projects missed the PTL nomination but good news is that we found the leaders for all the 9 projects now[10]. As next step, TC will be discussing the PTL appointment. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[10], * I have created the TC PTG etherpad to collect the topic[11]. * I sent email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[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. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14]15]. Project updates ------------------- * None. 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 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/+/855276 [3] https://review.opendev.org/c/openstack/governance/+/850005 [4] https://review.opendev.org/c/openstack/governance/+/857493 [5] https://review.opendev.org/c/openstack/governance/+/854375 [6] https://review.opendev.org/c/openstack/governance/+/856927 [7] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/856903 [8] https://etherpad.opendev.org/p/tc-zed-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://etherpad.opendev.org/p/2023.1-leaderless [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://etherpad.opendev.org/p/tc-2023-1-ptg [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-2, Sep 19 - 23
by Előd Illés 16 Sep '22

16 Sep '22

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Zed deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/zed branch creation for all deliverables that have not branched yet, using the latest available Zed release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/zed branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/zed branch before releasing out of the stable/zed branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2023.1 Antelope development, though the focus should still be on finishing up Zed until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Zed release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Zed version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

[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

[kolla] [train] Horizon port security group management fails
by Albert Braden 16 Sep '22

16 Sep '22

We're running kolla train and we're seeing an apparent bug when we try to add or remove security groups on a port. We see error "Failed to update port <ID>". It works fine in CLI; we only see this in Horizon. Is this a known bug, or are we doing something wrong?

6 19

[requirements][adjutant][magnum][sahara][venus][relmgmt] Requirements Freeze Exception requests
by Előd Illés 16 Sep '22

16 Sep '22

Hi, I would like to ask for a Requirements Freeze Exception for the following deliverables (as their former releases were done from broken gates, thus needed some extra fix): python-adjutantclient 0.11.0 [1] python-magnumclient 4.0.0 [2] python-saharaclient 4.0.2 [3] python-venusclient 1.0.1 [4] [1] https://review.opendev.org/c/openstack/releases/+/857736 [2] https://review.opendev.org/c/openstack/releases/+/856853 [3] https://review.opendev.org/c/openstack/releases/+/856858 [4] https://review.opendev.org/c/openstack/releases/+/856381 Előd irc: elodilles

2 1

[neutron] Drivers meeting - Friday 15.09.2022 - cancelled
by Lajos Katona 16 Sep '22

16 Sep '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[all][ptl][release] Zed release critical issue with oslo.db 12.1.0
by Előd Illés 15 Sep '22

15 Sep '22

Hi, With the latest oslo.db 12.1.0 release it seems multiple repositories are broken (see the corresponding requirements patch [1] for details, and probably there are more, that are not tested within requirements repository). The patch that introduces the break [2] "is necessary for oslo.db and openstack applications in general to be able to run on SQLAlchemy 2.0" according to patch author. Since we are after the 3rd milestone of Zed, we have very limited time to figure out what to do. The 2 options are: 1) fix every broken repository to work with oslo.db 12.1.0 as far as we know this is quite impossible as for some repositories the already existing fixes took almost a cycle to be implemented and there are still undiscovered bugs around this. (we don't know if this is really true, or probably there are cases where it's easy to fix) 2) revert the breaking change [2] and do another release in oslo.db now without it (and add it back after Zed release & release oslo.db with it as soon as possible in Antelope cycle) as far as we understand this does not cause any issue for those who already adapted to oslo.db 12.1.0, so this should not be painful Based on the above Release team is opting toward the 2nd option. Please let us know your opinion! [1] https://review.opendev.org/c/openstack/requirements/+/855153/ [2] https://review.opendev.org/c/openstack/oslo.db/+/804775 Thanks, Előd

8 18

[all][elections][ptl][tc] Reminder to opt-in to CIVS polling
by Jay Bryant 15 Sep '22

15 Sep '22

All, Apologies for the additional e-mail in your in-box, but wanted to make sure that everyone saw the reminder to opt-in to voting with CIVS. ACTION IS REQUIRED to receive the voting ballot from CIVS: you must opt-in to receiving email communications from CIVS. More information and the form to do so can be found at https://civs1.civs.us/cgi-bin/opt_in.pl Polling will start TODAY and this operation needs to be completed before then. Happy Voting! - Jay Bryant (jungleboyj)

1 1

[cinder] Festival of XS reviews
by Rajat Dhasmana 15 Sep '22

15 Sep '22

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

1 0

[blazar][FFE] Improvements to ExternalServiceFilter
by Pierre Riteau 15 Sep '22

15 Sep '22

Hello, We have merged a new Blazar usage enforcement filter late into the cycle, but have since received a change from Radosław Piliszek (yoctozepto) improving it [1]. It is important for us to get this merged for Zed, as it changes the name of new configuration options. Not merging it now would require us to deprecate the newly added configuration options in Antelope. I am planning to grant an FFE for it just before issuing RC1. Cheers, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/blazar/+/856527

1 0

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

15 Sep '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 ** 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' *** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… * 2023.1 cycle Technical Election & Leaderless projects ** https://governance.openstack.org/election/ ** https://etherpad.opendev.org/p/2023.1-leaderless ** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304… * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[tacker] Recent FT errors
by Yasufumi Ogawa 15 Sep '22

15 Sep '22

Hi tacker team, We've several unexpected failures on functional tests since last week or so. It might be because of new tests introduced in the recent some updates, and some lackness of resources on zuul tests we usually meet the same situation at the end of release possibly. Thanks to ueha to propose a patch [1] as a remedy for the issue, but it doesn't work for now unfortunately. For plan B, we can make the new tests non-voting for a while because it's not related to all reamined patches being reviewed now actually. We can revert it and focus on to fix the problem after RC1 is released. What do you think? [1] https://review.opendev.org/c/openstack/tacker/+/857551 Yasufumi

2 5

TC Election Double Ballots
by Amy Marrich 15 Sep '22

15 Sep '22

Hi everyone, As some of you have reported you have received 2 emails for the election. This was a result of our uploading the lists twice to make sure everyone who had to opt-in were included. Sorry for any confusion, Amy and the rest of the Election Officials

1 0

cpu metric not getting created for resource instance
by Swogat Pradhan 15 Sep '22

15 Sep '22

Hi, I am trying out the heat autoscalling and i am facing an issue where the instance created doesn't have cpu metric (enabled in ceilometer polling.yaml file) (overcloud) [stack@hkg2director ~]$ gnocchi resource show 130a0dfd-4e43-4373-ad0c-b5ffd4fcca95 +-----------------------+---------------------------------------------------------------------+ | Field | Value | +-----------------------+---------------------------------------------------------------------+ | created_by_project_id | 7c9659572662449da4906cc77b33f21b | | created_by_user_id | 4cb066d9701440dea941c5157186d06d | | creator | 4cb066d9701440dea941c5157186d06d:7c9659572662449da4906cc77b33f21b | | ended_at | None | | id | 130a0dfd-4e43-4373-ad0c-b5ffd4fcca95 | | metrics | compute.instance.booting.time: c0f77048-a85d-48a3-92cd-cdca50b341e8 | | | disk.ephemeral.size: 46d77e5d-aba1-4b93-92eb-3a97f9512a3c | | | disk.root.size: 3f60cb9f-9c06-4ccc-b47d-d2ca899fe5ea | | | memory: 97f796ed-c26c-4625-8670-64cf004a7b26 | | | vcpus: 513908f9-1bba-429e-8106-3bf933f04a76 | | original_resource_id | 130a0dfd-4e43-4373-ad0c-b5ffd4fcca95 | | project_id | 5d922243077045c48fe4b075e386551b | | revision_end | None | | revision_start | 2022-09-14T13:00:53.216445+00:00 | | started_at | 2022-09-14T12:57:21.846635+00:00 | | type | instance | | user_id | c1905e3c5a374924980e851840e7f028 | +-----------------------+---------------------------------------------------------------------+ For other instances also i do not see any cpu metric. Now the issue is as cpu metric is not getting created the alarm is not getting any data from the VM in terms of cpu usage and my autoscaling feature is failing. Please suggest how to fix this issue. With regards, Swogat Pradhan

2 3

[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

[largescale-sig] Next meeting: Sept 14th, 15utc
by Thierry Carrez 14 Sep '22

14 Sep '22

Hi everyone, The Large Scale SIG 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=20220914T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[cinder] Bug Report 09-14-2022
by Sofia Enriquez 14 Sep '22

14 Sep '22

This is a bug report from 09-07-2022 to 09-14-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1989271 " revert_snapshot_will_destory_attachment_with_lvm_backend." Fix proposed to master but Zuul voted -1. - https://bugs.launchpad.net/cinder/+bug/1989281 "IPV6 with lightos driver won't work." Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/1988942 "Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1989280 "Wrong assertion methods in unit tests." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1989280 "Wrong assertion methods in unit tests." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1989176 "Hitachi driver: no message for resource lock." Fix proposed to master. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

RE: Re: [openstack yova][nova-spiceproxy] Spice proxy behind SSL termination: protocol mismatch error in horizon web UI
by 박경원 14 Sep '22

14 Sep '22

1 0

[vitrage] RCA not showing on dashboard
by Carlos Rodríguez 14 Sep '22

14 Sep '22

Hi, I hope find very well, We are using vitrage-dashboard, but right we are presenting problems displaying the RCA alarm graph. [image: vitrageerror.png] When clicking RCA button in any alarm, the graph is not displayed and the following error is shown in inspector: Error: layers[node.rank] is undefined Downgrading to vitrage-dashboard stable/train seems to solve the issue. For the latest releases, the issue is solved when the following commit is reverted: d181623f22 Replace embedded static files with XStatic-* It seems that there is some problem with the XStatic libraries. Tested in Chrome, Firefox, Edge. Openstack release: Victoria Are you working to solve this problem? Or do you have any solution to display the graph. Thanks for your time, kind regards.

1 0

Outreachy 2022 - 2023?
by Sofia Enriquez 14 Sep '22

14 Sep '22

Hello, I'd like to propose myself as a mentor for this Outreachy round. However, I haven't seen any email on the mailing list announcing that OpenStack is joining this round. Please let me know if Openstack is going to sponsor the next rounds. Thanks in advance, Best, 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>

3 3

[neutron] bug deputy report (week of Sep 5)
by Akihiro Motoki 13 Sep '22

13 Sep '22

Hi, I was a bug deputy last week. It was a quiet week and only two new bugs are unassigned. ## Unassigned * https://bugs.launchpad.net/neutron/+bug/1988793 OVN as a Provider Driver for Octavia in ovn-octavia-provider This is a request to add a limitation corresponding to bug 1901936 (manual failure over is not supported) to the document. Hopefully ovn-octavia-driver folks can update the limitations section in the doc. * Neutron 20.2 Unknown Chassis Issue https://bugs.launchpad.net/neutron/+bug/1989155 ralonso suggested to file a bug on this to OVN upstream. It seems an issue in OVN core and perhaps we can mark it as invalid in neutron. ## In Progress * https://bugs.launchpad.net/neutron/+bug/1989391 [OVN] Allowed Address Pairs which is netmask doesn't work Thanks, Akihiro Motoki (amotoki)

1 0

Openstack.io is down
by Elvira Garcia Ruiz 13 Sep '22

13 Sep '22

Hi everyone! I noticed that stackalytics.io has been down for several days now. As far as I know this was widely used by the community, although it is not part of OpenInfra as a project. I'm not sure who was maintaining this, but I just wanted to make them aware of the problem, and also thank them for keeping it up and running. Kind regards! Elvira García (irc:elvira)

5 5

[openstack yova][nova-spiceproxy] Spice proxy behind SSL termination: protocol mismatch error in horizon web UI
by 박경원 13 Sep '22

13 Sep '22

2 1

[tripleo] puppetlabs-apache: soon a just a bad memory?
by Cédric Jeanneret 13 Sep '22

13 Sep '22

Hello Community! TLDR; puppetlabs-apache broke us so many times, I'm proposing a way to get rid of it, using plain ansible. Some work is needed, but it's "easy", and will allow us to keep a hand on the whole configuration code. Longer version: You probably saw mails about issues with puppetlabs-apache releases breaking the CI (and, by extension, TripleO). Over and over and over again. Well, good news: this may be just a bad memory - though it will require some work :). I've been working on a couple of ansible roles[1] in order to just get the needed pieces we really need in TripleO: file generation. Once we get those 2 roles in, we'll be able to switch, service by service, away from puppet management for apache/httpd. There's already an on-going example[2] with ironic. Of course, as you can see, there's some work to do, even on the puppet side. But it's not really complicated, and can be done quickly. I'll do my best to move things, but be prepared to get pings from time to time if help is needed. I can't do all by myself, can I? ;) And if anyone wants to jump in and work on the transition, please do, and don't hesitate to reach to me, either by mail, or on #tripleo - I go there as Tengu. Cheers, C. [1] https://review.opendev.org/c/openstack/tripleo-ansible/+/853481 [2] https://review.opendev.org/q/topic:standalone%252Fapache -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[tripleo] Switching to nftables - it's coming soon!
by Cédric Jeanneret 13 Sep '22

13 Sep '22

Hello there, TLDR; we're about to switch to nftables[1], there are some changes described in the up-to-date doc. Reason is: faster, more modern interface, close to no possibility to get locked out of the system. Also, once it's switched, please use `nft list ruleset' instead of `iptables -L'. [1] https://review.opendev.org/c/openstack/tripleo-heat-templates/+/852808 Longer version: I've been working a good amount of time in order to get rid of the current tripleo_iptables custom action. On of the reasons here was the fact we could get locked out the overcloud if, for any reason, a network reset happens in ansible during the application of the rules. For the records, tripleo_iptables is calling the native "iptables" module from ansible, just doing a batching of the ruleset in an attempt to apply everything faster. It has some weird things, such as reversing the rule order before applying them using the "insert" action, meaning it will lock everything first, then open one by one the accesses. Knowing "ssh" is like 003 rule, you can imagine how things can go wrong. So, I took the opportunity to make some changes. While doing so, I saw `iptables' was just a compatibility wrapper for nftables - basically, `iptables' is a symlink to `iptables-nft', so I also took the opportunity to bypass it, and go straight for `nft'. Doing so, I created a new tripleo_nftables role in tripleo-ansible project; it's "just" creating files based on templates, then validates the whole lot of files, and applies all the rules in one single transaction. Compared to tripleo_iptables, it's really more robust, while being faster, and less prone to lock out and other unwanted things. The current state is: we're close, really close to switch things up. We're missing 2 patches in the CI to make the infra properly supported, and then, there's "the" switch itself. What will change: almost nothing: the way we create rules in tripleo-heat-templates and the different parameters therein doesn't change at all; the thing that will really change is the way to list the rules: instead of calling `iptables -vnL' or the like, you'll need to call `nft list ruleset'. Now, in order to make things easier, the doc is already up-to-date: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… As you will see, there will be some differences in the actual layout: all of the tripleo rules will be in dedicated chains, prefixed by TRIPLEO_ - for instance, TRIPLEO_INPUT, TRIPLEO_OUTPUT, TRIPLEO_FORWARD, and so on. This allows to get a cleaner layout, cleaner way to filter the output and, really important thing, to ensure we're cleaning dangling rules - the TRIPLEO_* chains will be flushed before the ruleset are added. All in one single transaction. Some more information/content: tripleo_nftables role: https://opendev.org/openstack/tripleo-ansible/src/branch/master/tripleo_ans… Doc: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… Debug files available in the CI: log of dropped packets: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… nftables configuration dump: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… nftables configuration: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… All of that can help understanding the potential issues you may encounter. As a side note, we've been testing the whole thing for about a month now, correcting issues, updating the doc and making sure at least all of the current CI jobs (yes: ALL) are green without any weird behavior. A doc has been created in order to list the current state, with what we've seen, what we've done: https://hackmd.io/F0W2gYw_SiaiWkowjFU9cw?view#NFTABLES-testing-results Brace yourself, the change is coming :). But it should be transparent ;). -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 13 Sep '22

13 Sep '22

Hi all, Tomorrow we will have our bi-weekly meeting at 0800 UTC in #openstack-operators. Notes from previous meeting can be found here [0]. Please go in prior to the meeting and vote for for the naming conventions suggested, which you believe are the most important or if you think some of them should not be considered at all. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0

[ptl][tc][election][adjutant][barbican][OpenStackSDK][OpenStack_Charms][sahara][swift][venus] Leaderless project for 2023.1 cycle
by Ghanshyam Mann 13 Sep '22

13 Sep '22

Hello, As you know, 2023.1 cycle election nomination is ended and we end up with 11 leaderless projects. List is in the etherpad: https://etherpad.opendev.org/p/2023.1-leaderless Out of 11, we have found 4 projects leaders but 7 (in the subject list) projects still need some leaders to volunteer: 1. Adjutant 2. Barbican 3. OpenStackSDK 3. OpenStack_Charms 4. Sahara 5. Swift 6. Venus Please reply here or ping us in #openstack-tc channel if you would like to lead these projects. -gmann

2 4

[cinder][stable] cinder-stable-core additions
by Rajat Dhasmana 13 Sep '22

13 Sep '22

Hi All, After discussing with the current members of the cinder stable core team, I've decided to add the following members to the cinder stable core team. 1) Walter Boring - (Currently cinder core) 2) Sofia Enriquez - (Currently cinder core) Sofia and Walt have been long term contributors in the Cinder project and I'm happy to have them as part of the stable core team. I will proceed with making changes to the stable core team[1]. [1] https://review.opendev.org/admin/groups/1b3ca2faf07b15efff426901a387eb7c914… Thanks and Regards Rajat Dhasmana

1 0

[all][elections][ptl][tc] Conbined PTL/TC antelope cycle Election Voting Kickoff
by Ian Y. Choi 13 Sep '22

13 Sep '22

Polls for PTL and TC elections are now open and will remain open for you to cast your vote until Sep 19, 2022 23:45 UTC. We are selecting 4 TC members, and are having PTL elections for Ironic. Please rank all candidates in your order of preference. You are eligible to vote in the TC election if you are a Foundation individual member[0] that also has committed to any official project team's deliverable repositories[1] over the Sep 17, 2021 00:00 UTC - Sep 07, 2022 00:00 UTC timeframe (Yoga to Zed) or if you are in the list of extra-atcs[2] for any official project team. You are eligible to vote in a PTL election if you are a Foundation individual member[0] and had a commit in one of that team's deliverable repositories[1] over the Sep 17, 2021 00:00 UTC - Sep 07, 2022 00:00 UTC timeframe (Yoga to Zed) or if you are in that team's list of extra-atcs[2]. If you are eligible to vote in an election, you should find your email with a link to the Condorcet page to cast your vote in the inbox of your Gerrit preferred email[3]. What to do if you don't see the email and have a commit in at least one of the projects having an election: * check the trash or spam folders of your gerrit Preferred Email address, in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the project's deliverable repos[0] and email the election officials [4] * requires opt-in to CIVS polling to receive email communications from the voting system [5]. If we can confirm that you are entitled to vote, we will add you to the voters list for the appropriate election. Our democratic process is important to the health of OpenStack, please exercise your right to vote! Candidate statements/platforms can be found linked to Candidate names on this page: https://governance.openstack.org/election/ Happy voting, /Ian, as one of OpenStack Election Officials [0] https://www.openstack.org/community/members/ [1] The list of the repositories eligible for electoral status: https://opendev.org/openstack/governance/src/tag/oct-2022-elections/referen… [2] Look for the extra-atcs element in [1] [3] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [4] https://governance.openstack.org/election/#election-officials [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304…

1 0

[baremetal-sig][ironic] Future of baremetal-sig
by Jay Faulkner 13 Sep '22

13 Sep '22

Stackers, An item came up in the Ironic meeting today regarding the future of the baremetal sig. Essentially, Arne was doing great work sourcing talks for it, but now he's going to be unable to continue hosting it and proactively sourcing talks. (A seriously big thanks is owed to Arne for doing a great job on this!) This led us to wonder if BM SIG in its current form remains sustainable. Some options we can consider include: - Keep the BM SIG as-is, cancel it months where there's not a talk available. - Change the BM SIG meetings to more of a meetup style for operators to talk about Ironic - Something else entirely we haven't thought about yet. What do you all think? - Jay Faulkner

1 0

OpenInfra Summit Vancouver 2023 Track Chair Nominations Now Open
by Helena Spease 13 Sep '22

13 Sep '22

Hey everyone! Track Chair nominations <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>> for the 2023 OpenInfra Summit in Vancouver (June 13-15, 2023) are now open! Track Chairs for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2023 Summit Tracks: 5G/NFV & Edge AI/Machine Learning/HPC CI/CD Container Infrastructure Getting Started Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Hands On Workshops Full track descriptions are available here <https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/>>. If you’re interested in nominating yourself or someone else to be a member of the Summit Track Chairs for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>>. Nominations will close on October 28th, 2022. Track Chairs selections will occur before we close the Call for Presentations (CFP) so that the Chairs can host office hours to consult on submissions, and help promote the event. CFP will be opening in November, registration <https://openinfrasummit2023.eventbrite.com/ <https://openinfrasummit2023.eventbrite.com/>> and sponsorship <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/>> information are already available. Please email speakersupport(a)openinfra.dev <mailto:speakersupport@openinfra.dev> with any questions or feedback. Cheers, Helena Spease

1 0

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

12 Sep '22

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

1 0

[tc][ptl][election][masakari] I volunteer to become Masakari PTL again
by Radosław Piliszek 12 Sep '22

12 Sep '22

As in the topic - I saw Masakari did not receive a candidate and I don't want to see this project disappear so I volunteer to be the PTL. I don't have any major plans regarding Masakari except for keeping it afloat and working where it works already. Cheers, Radek -yoctozepto

2 1

[horizon][QA][release] Cycle With Intermediary without recent deliverables
by Előd Illés 12 Sep '22

12 Sep '22

Hi, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest Zed release available on release week. The following deliverables have done a Zed release, but it was not refreshed in the last two months: horizon tempest You should consider making a new one very soon, so that we don't use an outdated version for the final release. Előd Illés irc: elodilles

3 2

[neutron] [ovn] Distributed routing ingress traffic flow
by Roman Pomazanov 12 Sep '22

12 Sep '22

1 0

[monasca][kolla-ansible] Help for a monasca newbie to get metrics for instances needed
by Christian Stelter 12 Sep '22

12 Sep '22

Hi! I'm trying to explore monasca, but I'm bit lost in how to get metrics from a project/tenant collected. I'm using kolla-ansible in my test setup running ubuntu-source images. Ubuntu release is Yoga. Monasca seems to be up and running. I can see the default metrics with a appropriate user in the monasca_control_plane project. cpu.* disk.* io.* load.* mem.* monasca.* net.* ntp.* And I find measurements in the influxdb, but only metrics/measurements for the openstack hypervisor nodes yet. What I'm missing after searching the existing documentation is how I can enable a plugin as for libvirt for example or whatever the recommendation for monitoring the instances is. As I have found the plugins directory on the hypervisors under /etc/kolla/monasca-agent-collector/plugins I thought putting a config file like in the documentation [1] for the libvirt plugin and restart the monasca-agent-collector would be sufficient. But all I got was an error message: 2022-09-11 12:22:26,412 | ERROR | collector | monasca_agent.common.util(util.py:529) | Unable to import check module libvirt.py from checks_d Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/util.py", line 520, in load_check_directory check_module = load_module('checksd_%s' % check_name, check) File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/util.py", line 470, in load_module module_spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 848, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/../collector/checks_d/libvirt.py", line 20, in <module> import libvirt ModuleNotFoundError: No module named 'libvirt' As it seems the plugin system dependencies like libvirt-dev are missing. So I assume I have to rebuild the container myself and/or open an issue on opendev.org. Or is there another way to get metrics for instances? Next question: even if I had a running libvirt plugin. What has to be done to enable another user in a normal tenant project to use these metrics? Just add the monasca-read-only-user to user(s) which shall be enabled to manage alarm definitions, alarms and notifications? Will the tenant then see or at least use the metrics for his (and only his) project? I found a lot of high level documentation, (base) installation instructions, hints for developers on how to extend monasca, but nothing beyond the initial setup for monasca newbies like me. I queried the all-knowing, all-seeing trash heap, mailing lists, and the YT academy already. May be I just missed something. So hints are welcome! BTW. Is the kolla-ansible part of monasca still in active maintenance and development? I stumpled upon the same error as in [2] and I'm getting an HTTP 500 error when trying to open the monitoring overview and is still unassigned. Thanks in advance! Kind regards, Christian Stelter [1] https://github.com/openstack/monasca-agent/blob/master/docs/Libvirt.md#conf… [2] https://bugs.launchpad.net/kolla-ansible/+bug/1967278

2 2

[First Contact][SIG][PTG] Planning October 2022
by Kendall Nelson 12 Sep '22

12 Sep '22

Hello Party People, I started putting together the etherpad[1] for planning our time at the PTG! Add your topics and your name if you plan on attending :) If the time I selected doesn't work for folks, we can book other time (instead or in addition to), I just know historically we have been a mix of Americas/ APAC and so this time block should work for folks. Also, gentle reminder to register if you haven't already - it is free afterall [2]. -Kendall Nelson (diablo_rojo) [1] https://etherpad.opendev.org/p/oct2022-ptg-first-contact [2] https://openinfra-ptg.eventbrite.com/

1 0

[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

[designate] zone sharing between projects and how to create classless PTR
by Tomáš Bredár 11 Sep '22

11 Sep '22

Hi Folks, I have a few questions: 1. Is there a possibility to share DNS zones between tenants? I've found this [1] patchset, but it's not merged yet. 2. Is there a way to create a classless reverse zone? According to [2], it should work. Creating a zone is ok: openstack zone create --email tomas.bredar(a)gmail.com \ --ttl 3600 --description "in-addr.arpa. zone for reverse lookups for e-devel subnet 10.254.226.0/26" \ 0-26.226.254.10.in-addr.arpa. But when I try to add a recordset, I get an error: openstack recordset create --record testvm.bredytest.abc.com. --type PTR --ttl 600 0-26.226.254.10.in-addr.arpa. 1.226.254.10.in-addr.arpa. RecordSet is not contained within it's parent zone I'm using OpenStack Wallaby If this won't work, I'm considering using the neutron integration with external DNS. Thanks for your help Tomas [1] https://review.opendev.org/c/openstack/designate/+/726334 [2] https://docs.openstack.org/designate/latest/user/manage-ptr-records.html

3 4

[manila] Bugsquash postponed by one week
by Carlos Silva 10 Sep '22

10 Sep '22

Hello, Zorillas! I'm sending this email to inform you that the bugsquash we planned for this week will be postponed by one week. We currently have some FFEs and we could use the change owners and reviewers energy to get those changes moving forward. We hope to have the FFE changes merged by the end of this week, so next week we could use some focus time on the bugsquash. Regards, carloss

1 1

[release] Release countdown for week R-3, Sep 12 - 16
by Előd Illés 09 Sep '22

09 Sep '22

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

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Sept 9
by Slawek Kaplonski 09 Sep '22

09 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 08. Most of the meeting discussions are summarized in this email. Meeting logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-08-15.00.log.html * Next TC weekly meeting will be on Sept 15 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 14. 2. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], four are completed and others items are in-progress. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. 2023.1 cycle Technical Election (TC + PTL) ------------------------------------------------------------- Nomination period is now over. We are currently in the campaign time. Please remember that there is an action required if You want to receive ballot from CIVS. Please check [4] for more details. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [5]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[6], * gmann created the TC PTG etherpad to collect the topic[7]. * gmann sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[8]. 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. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[10][11]. Project updates ------------------- * Switch release management to distributed leadership[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 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://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304… [5] https://review.opendev.org/c/openstack/governance/+/854375 [6] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [7] https://etherpad.opendev.org/p/tc-2023-1-ptg [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [12] https://review.opendev.org/c/openstack/governance/+/855276 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Drivers meeting agenda - 9.09.2022.
by Lajos Katona 09 Sep '22

09 Sep '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFE to discuss: [RFE] OVN support for vnic type virtio-forwarder (#link https://bugs.launchpad.net/neutron/+bug/1988542 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[rabbitmq][kolla-ansible] How to enable rabbitmq plugin via configuration file?
by A Tom 09 Sep '22

09 Sep '22

Hi, I’m trying to enable rabbitmq_tracing plugin in my kolla-ansible. In „typical” installation you have to enable plugin via rabbitmq-plugins enable and (in case of this particular plugin) add directory,username and password to rabbitmq.conf. These changes (adding username,password and directory) are obvious, but how do I enable particular plugin by kolla-ansible configuration file? Should I put something in globals.yaml? Best regards Adam Tomas

1 0

[baremetal-sig][ironic] No meeting in September
by Iury Gregory 09 Sep '22

09 Sep '22

Hello everyone, This email is just to let you know that we won't have any presentation/meeting for the Baremetal-sig this month. -- *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

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations End
by Amy Marrich 08 Sep '22

08 Sep '22

Please note we are in the process of adding a standalone TC Campaigning period before opening the TC election for voting. This will allow the candidates to answer any questions and also people to opt-in to the CIVS system before we start the voting process. Pending a patch being added and merged we are looking at starting the voting early to mid next week. Thanks, Amy +++++++++++++++++++++++++++++++++++++++++++++++++++ The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 11 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Adjutant, Barbican, Keystone, Masakari, OpenStackSDK, OpenStack_Charms, Sahara, Senlin, Swift, Venus, Zun -- TC Election Details -- There are 1 projects that will have elections: Ironic. Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Sep 07, 2022 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#antelope-ptl-candidates [1] https://governance.openstack.org/election/#antelope-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

2 1

Retirement process openstack/training-labs
by gaspard varennes 08 Sep '22

08 Sep '22

Hello, I found on https://lists.openstack.org/pipermail/openstack-discuss/2021-October/025586… an email saying "If you are using it for your training please reply to this email pr ping us on #openstack-tc IRC OFTC channel otherwise we will start the retirement process." We (a digital school in France) are still using your training labs, so we write you this email. But we think the retirement process is already done because last commit of the repo https://opendev.org/openstack/training-labs.git is almost empty. I presume (but I'm not sure because I'm not a tech guy) that we still can use the previous version of the repo https://opendev.org/openstack/training-labs/src/commit/2585b12b879bae4c3fe4… to train on the labs, am I right? Thank you very much for your time and consideration. Gaspard VARENNES Pedagogical Engineer Content Excellency Department Epitech LILLE 5/9 rue du palais Rihour 59000 LILLE 06 69 33 83 30

2 1

[neutron] [openvswich-agent] Driver for security groups
by ETP 08 Sep '22

08 Sep '22

Hi, what is the recommended openvswich agent driver for security groups? Two options on my table are now OVS native firewall driver vs. OVSHybridIptablesFirewall driver Br, - Eki -

3 2

[elections][Keystone] PTL Candidacy for Antelope
by Dave Wilde 07 Sep '22

07 Sep '22

Hello all, I would like to let you know that I will be running for the PTL of the Keystone project for the Antelope cycle. I have been working closely with the current PTL and core reviewers on our initiatives to improve the speed at which we review code submissions and get things merged. I would like to continue focusing on this and continue to build momentum. I look forward to contributing back to the community and Keystone in general and would like to thank Douglas Mendizábal for his work and leadership. Thank you, -- /Dave

1 0

Join the OpenStack Community in Vancouver for the OpenInfra Summit!
by Helena Spease 07 Sep '22

07 Sep '22

Hi Everyone, Registration and sponsorships for the OpenInfra Summit Vancouver [1] are now open! This is your chance to collaborate directly with the people building and running OpenStack. Mark your calendars for June 13-15, 2023 and register early [2] to save your seat! Find information on sponsorships[3], the Summit travel support program[4], visa requirements[5], and track chair nominations[6]. Stay tuned for November when the Call for Presentations opens! Cheers, Helena [1] https://openinfra.dev/summit/vancouver-2023 [2] https://openinfrasummit2023.eventbrite.com/ [3] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp [5] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 [6] https://openinfrafoundation.formstack.com/forms/trackchairnominations2023

1 0

Designate Installation in Openstack
by Adivya Singh 07 Sep '22

07 Sep '22

Hi Team, Any idea, what user variables we need to create in user_variables, for it to pick in Openstack Configuration using ansible. Regards Adivya Singh

2 1

[elections][tc] I'm running for TC
by Jay Faulkner 07 Sep '22

07 Sep '22

Hello, I wanted to announce I'm running for TC in the upcoming election. Please take a look at my candidate statement if you want some insight into my motivations and how I'd approach the position: https://opendev.org/openstack/election/raw/branch/master/candidates/antelop… . If you have any questions for me, feel free to ask them here. Thanks, Jay Faulkner

1 0

[oslo][tooz] Feature Freeze exception request
by Alan Bishop 07 Sep '22

07 Sep '22

I'd like to request an exception for https://review.opendev.org/c/openstack/releases/+/856128. <https://review.opendev.org/710539> This patch proposes a new tooz release for the purpose of picking up [1], which fixes a bug [2] (it's not a feature, per se) that otherwise prevents tooz's etcd3gw driver from working with recent versions of etcd. The issue was initially observed back in 2020 [3]. [1] https://review.opendev.org/c/openstack/tooz/+/827492 [2] https://bugs.launchpad.net/python-tooz/+bug/1983668 [3] https://github.com/dims/etcd3-gateway/issues/41#issuecomment-673558108 Thank you for your consideration, Alan Bishop (abishop)

2 1

[election][Glance] PTL Candidacy for Antelope
by Pranali Deore 07 Sep '22

07 Sep '22

Hello everyone, I would like to let you know that I will be PTL of Glance project for the Antelope cycle. I have been working closely with the previous PTL, Abhishek, since last cycle and I am hoping to contribute back to the community as a PTL while following his excellent example. The following will be my goals for Antelope cycle: 1. Bridge gap between python-glanceclient and openstackclient The CLI support for all glance APIS is already there in GlanceClient and the similar CLI support we need to have in OpenstackClient for the missing Glance APIs in this upcoming cycle. 2. Default Glance to configure multiple stores Glance has deprecated single stores configuration since Stein cycle and will remove the support of the same in the upcoming cycle. 3. Secure RBAC In Xena we have managed to move all policy checks to API layer and implemented project scope of metadef APIs. As per the revised community goal, in zed cycle we have made all policy rules set scope_types=['project'] for all project resources that have already implemented scope. Now we need to have manager role support once it's fully implemented in Keystone. 4. Community priorities Whatever community goals put forward by TC, as a PTL of Glance project will want to adopt these as a priority for the Antelope cycle. 5. Other As we are very short team at this moment, I would like to put some efforts in attracting some contributors, help them to understand how Glance functions and encourage them to contribute for Glance. Looking at how Abhishek, Erno and Brian have steadied the ship, I know it's a big task and with their help I will do my best not to fail the expectations. Thank you for consideration, Pranali Deore (pdeore)

4 3

[cinder] Bug Report - 08-31-2022 - 09-07-2022
by Sofia Enriquez 07 Sep '22

07 Sep '22

This is a bug report from 08-31-2022 to 09-07-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1988317 "Remove IET iSCSI target." Unassigned. Wishlist - https://bugs.launchpad.net/cinder/+bug/1988803 "With image-volume cache enabled backend, volume creation for a smaller volume than image-volume cache has the same size of the image-volume cache." 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

[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][Requirements] PTL candidacy
by Matthew Thode 07 Sep '22

07 Sep '22

I would like to announce my candidacy for PTL of the Requirements project. The project was recently updated to allow multiple PTLs this cycle and I imagine tony will be my better half. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible. 3. Fix some automation of generate contstraints (pkg-resources being added and setuptools being dropped) 4. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. 5. introduce better python version range support into constraints. An image with all the python versions we want is likely needed. I look forward to continue working with you in this cycle, as your PTL or not. Thanks for your time, -- Matthew Thode

3 5

[election][Ironic] PTL Candidacy
by Jay Faulkner 07 Sep '22

07 Sep '22

Hi all, I wanted to let you know I'm running for PTL of Ironic for the Antelope cycle. You can read my candidate statement[1] for full information, but feel free to ask me any questions you'd like here if you have them. Thanks, Jay Faulkner [1] - https://governance.openstack.org/election/#antelope-ptl-candidates

1 0

[horizon] instance filtering dropdown default
by John Ratliff 07 Sep '22

07 Sep '22

When I load certain pages in horizon, like the compute instances page, the default filter is "Instance ID". How can I change the default to "Instance Name" instead? Thanks. --John Ratliff

1 0

Horizon
by Atharva Dhanwate 07 Sep '22

07 Sep '22

4 3

[neutron] Bug deputy report for week of August 29th
by Brian Haley 06 Sep '22

06 Sep '22

Hi, I was Neutron bug deputy last week. Below is a short summary about the reported bugs. BTW, you don't have to wait for me to be deputy to file all your bugs :) -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1988026 - Neutron should not create security group with project==None - Talked to Security Response Team and they decided to add a tracker to it since the quota system doesn't seem to limit how many random default security groups one can create. - https://review.opendev.org/c/openstack/neutron/+/855580 High bugs --------- * https://bugs.launchpad.net/neutron/+bug/1988037 - Neutron does not find an existing route - https://review.opendev.org/c/openstack/neutron/+/854986 * https://bugs.launchpad.net/neutron/+bug/1988296 - neutron-lib pep8 CI failing with pylint==2.15.0 - https://review.opendev.org/c/openstack/neutron-lib/+/855061 Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1988069 - neutron-dhcp-agent fails when small tenant network mtu is set - Could not reproduce issue reported with MTU as 70 for network, only saw that instances could not do DHCP with it so small. Looks like a potential kernel bug since this works on later versions. * https://bugs.launchpad.net/neutron/+bug/1988199 - https://review.opendev.org/c/openstack/neutron/+/855257 * https://bugs.launchpad.net/neutron/+bug/1988220 - large unused dependency ncclient + paramiko in os-ken - Assigned to Rodolfo since he made change to remove nose https://review.opendev.org/c/openstack/os-ken/+/850631 - closed (won't-fix) as ncclient is required for os-ken, just wasn't explicitly called-out in requirements. * https://bugs.launchpad.net/neutron/+bug/1988549 - Trunk status is down after a live-migration - Arnau Verdaguer took ownership Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1988298 - [neutron-lib] "registry.has_resource_extenders" is the same as "resource_extend.has_resource_extenders" - Needs owner * https://bugs.launchpad.net/neutron/+bug/1586731 - restart neutron ovs agent will leave the fanout queue behind - Old bug re-opened - Partial patch posted, asked commenter to submit to master Misc bugs --------- * https://bugs.launchpad.net/neutron/+bug/1988281 - neutron dhcp agent state not consistent with real status - After a restart, the agent status is UP even though it is still doing a full-sync operation, is there a way to signify this status? See bug for further discussion. * https://bugs.launchpad.net/neutron/+bug/1988382 - L3 agent(agent_mode=dvr_snat) restart, fip namespace removed rfp-port, resulting in fip not connecting - Failure is seen in code from 2019, asked submitter to try tip of stable/victoria and reproduce since there have been fixed in this area since then. Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1988077 - Noisy neutron-openvswitch-agent service - There are some deployments that wanted more logging which is why the agent is more verbose. Will have to have a further discussion to see if there is a way to address concern of log being noisy, besides using more aggressive log rotation as suggested. * https://bugs.launchpad.net/neutron/+bug/1988188 - Create an automated tool to retrieve the needed OVS version depending on the OVN one - Suggested by Rodolfo to help improve gate dependencies. * https://bugs.launchpad.net/neutron/+bug/1988542 - [RFE] OVN support for vnic type virtio-forwarder - Will need to add to Drivers meeting agenda

1 0

Two containers fail
by Derek O keeffe 06 Sep '22

06 Sep '22

Hi, I recently successfully installed OSA and I am now trying to install it again from scratch with all the configuration changes I needed in place. Unfortunately this time around it is failing on setup_hosts.yml here: TASK [lxc_container_create : Create container (dir)] ******************************************************************ok: [infra1_memcached_container-b92f4db7 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_rabbit_mq_container-d286a482 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_utility_container-05f756fc -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_galera_container-5beef059 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_aodh_container-639f5ad8 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_neutron_server_container-f67e972d -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_horizon_container-dfeaa0dc -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_placement_container-350e4ede -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_heat_api_container-82cbd764 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_nova_api_container-b30c38d1 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_repo_container-f16e50a9 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_ceilometer_central_container-910a888f -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_keystone_container-32dcd68b -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_gnocchi_container-30ccb451 -> infra1(CONTROLLER_IP_ADDRESS)]fatal: [infra1_cinder_api_container-840a18bb -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_cinder_api_container-840a18bb ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_cinder_api_container-840a18bb", "state": "stopped"}, "msg": "The container [ infra1_cinder_api_container-840a18bb ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1}fatal: [infra1_glance_container-b50e16a6 -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_glance_container-b50e16a6 ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_glance_container-b50e16a6", "state": "stopped"}, "msg": "The container [ infra1_glance_container-b50e16a6 ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1} I don't understand how 14 containers are fine (can be attached to and commands run through lxc-attach) and 2 containers are failing. I have a deploy host, controller and two computes all with a fresh install of Ubuntu 20.04. The bootstrap_ansible script ran fine on the deploy host and the setup_hosts playbook ran through fully as after the above it skipped cinder and glance containers every where else. Can anybody please point me in the direction of getting more info or a possible cause. Thanks in advance.

2 2

[Octavia][release] Requesting exception for python-octaviaclient
by Gregory Thiemonge 06 Sep '22

06 Sep '22

Hi Folks, I am requesting a Feature Freeze Exception for the release of python-octaviaclient for Zed. One patch [0] was merged at the end of last week in python-octaviaclient (we were waiting for the related feature to get merged in the octavia repo) and a new release (3.1.0) was proposed for Zed in the release repo [1], but it wasn't merged in time. We would like to get the approval for this new release so we could base the stable/zed branch on this new tag (we would need to update [2]). Thanks, Gregory [0] https://review.opendev.org/c/openstack/python-octaviaclient/+/664473 [1] https://review.opendev.org/c/openstack/releases/+/855675 [2] https://review.opendev.org/c/openstack/releases/+/855912

2 1

[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

[nova]How to confirm whether a arm64 node supports hardware acceleration for virtual machines
by 韩光宇 06 Sep '22

06 Sep '22

Hello, I see `egrep -c '(vmx|svm)' /proc/cpuinfo` in nova install documentation[1]. It can be used to confirm whether a node supports hardware acceleration for virtual machines on x86 architecture. But it is not applicable in the ARM architecture. Do we have an officially recommended method to confirm in ARM architecture? Thanks, Han Guangyu [1]https://docs.openstack.org/nova/latest/install/compute-install-rdo.html#f…

3 2

[oslo][relmgmt][taskflow][nova] fasteners.ReaderWriterLock and oslo.concurrency's fair lock is broken if used in eventlet
by Balazs Gibizer 06 Sep '22

06 Sep '22

Hi, It is hard to properly figure out which OpenStack project is affected exactly. But I want to give a heads up. If the following is true for your project then you are affected: * using eventlet and * using oslo.concurrency fair internal lock (external lock or non fair locks are not affected) or using fasteners.ReaderWriterLock directly. I know that nova is affected and based on code search taskflow is affected at least. The oslo.concurrency's fair lock uses fasteners.ReaderWriterLock[1]. The fasteners.ReaderWriterLock relies on threading.current_thread to identify a thread and decide if a thread already has a lock and therefore can reenter the lock. However in an eventlet monkey patched environment, a thread that is created with eventlet.spawn_n() or the patched threading.Thread() the threading.current_thread call does not return an eventlet unique ID. This causes that the lock can be reentered from multiple eventlets at the same time. We have 4 ways forward: 0) Fix eventlet. There is an open issue in eventlet[3] for this open since October 2021. Based on the ticket this direction does not seems to feasible. 1) Sean recently opened an issue[4] on fasteners to restore a previously existing workaround that could fix our issues. If an new fasteners lib is released with the workaround[5] then at least oslo.concurrency requirements needs to be bumped and a new oslo release is pushed. 2) If the fasteners' maintainer does not accept [4][5] in time then I have an oslo.concurrency patch[6] that implements a workaround in oslo. This also requires a new olso.concurrency release. Also this means that projects that are using fasteners.ReaderWriterLock directly need to re-implement the fix locally. 3) If all odds fails I have a nova only patch[7] that implements the workaround locally in nova. Note that this issue is present in stable/yoga and on master. On stable/xena we uses fasteners < 0.15.0 which is not affected. Cheers, gibi [1] https://github.com/openstack/oslo.concurrency/blob/052b2f23572900601b0f4138… [2] https://bugs.launchpad.net/oslo.concurrency/+bug/1988311 [3] https://github.com/eventlet/eventlet/issues/731 [4] https://github.com/harlowja/fasteners/issues/96 [5] https://github.com/harlowja/fasteners/pull/97 [6] https://review.opendev.org/q/topic:bug/1988311+project:openstack/oslo.concu… [7] https://review.opendev.org/q/topic:bug/1988311+project:openstack/nova

2 2

[ops][largescale-sig] rabbitmq and the durability of reply_ queues
by Felix Hüttner 06 Sep '22

06 Sep '22

Hi everyone, the largescale-sig currently recommends the following rabbitmq policy [1]: '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. If I found the history of this setting correctly, it resulted from this mailinglist thread [2] which came to the conclusion: > * use durable-queue and replication for long-running queues/exchanges > * use non-durable-queue without replication for short (fanout, reply_) queues However I am unsure if reply_ queues are actually shorted lived than the "long-running" ones. If we take the example of the cinder-scheduler we have the following queues: * cinder-scheduler: Tied to the lifetime of the whole cinder-scheduler cluster; currently durable + replicated * cinder-scheduler.myhostname: Tied to the lifetime of the cinder-scheduler service, but not removed when the service stops; currently durable + replicated * cinder-scheduler_fanout_somerandomid: Tied to the lifetime of the cinder-scheduler service, but removed when the service stops; currently neither durable nor replicated * reply_somerandomid: Tied to the lifetime of the cinder-scheduler service, but removed when the service stops; currently neither durable nor replicated If I read got all of the above correctly then reply_ and fanout queues are actually not shorter lived than the normal queue to send requests to that service. The only difference is that we remove them when the service itself stops. Therefor I want to propose the question if we should not also make these queues durable and replicated. Thank you [1]: https://docs.openstack.org/large-scale/other/rabbitmq.html#pattern [2]: https://lists.openstack.org/pipermail/openstack-discuss/2020-August/016562.… -- Felix Huettner Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>.

2 2

[puppet] Gate blocker: enabling neutron-ovn-metadata-agent consistently fails in CentOS Stream 9
by Takashi Kajinami 06 Sep '22

06 Sep '22

Hello, Currently we are facing a problem with integration jobs with ml2+ovn in CentOS Stream 9 ( puppet-openstack-integration-7-scenario00[35]-tempest-centos-9-stream ) and these jobs are consistently failing. Details can be found in https://launchpad.net/bugs/1988552 . I've already reported the issue to RDO and CentOS Stream to get their help while I'm also implementing a temporary workaround. https://review.opendev.org/c/openstack/puppet-openstack-integration/+/855617 Please avoid rechecking/approving patches until these jobs are fixed. Thank you, Takashi

1 1

Re: Secret getPayload() openstack4j
by Srinivasan T 06 Sep '22

06 Sep '22

Hi, Does anyone have any idea on this? >From the REST API documentation, it seems GET /v1/secret/{uuid} may not fetch the payload and we need to use a different endpoint GET /v1/secret/{uuid}/payload . Is there any equivalent Java API (openstack4j) for this? Regards, Srini On Mon, Sep 5, 2022 at 11:08 PM Srinivasan T <tsrini.alr(a)gmail.com> wrote: > Thanks Artem for the response. > > I face the same issue when using the below version as well (snippet from > pom.xml), > > <modelVersion>4.0.0</modelVersion> > <artifactId>openstack4j-core</artifactId> > <name>OpenStack4j Core</name> > <description>OpenStack Java API</description> > <url>http://github.com/openstack4j/openstack4j/</url> > > Regards, > Srini > > On Mon, Sep 5, 2022 at 9:48 PM Artem Goncharov <artem.goncharov(a)gmail.com> > wrote: > >> Hi, >> >> The library is not an official OpenStack delivery. I guess nobody here >> would be able to give you proper suggestion. Moreover it does not look like >> being actively maintained. >> >> Regards, >> Artem >> >> On 5. Sep 2022, at 18:03, Srinivasan T <tsrini.alr(a)gmail.com> wrote: >> >> Hi, >> >> I'm unable to get the secret's payload from openstack4j, it always >> returns null. >> >> Secret secret = os.barbican().secrets().get("19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60"); >> secret.getPayload(); //Always returns null >> >> The same works when using the OpenStack CLI, >> >> openstack secret get --payload_content_type 'application/octet-stream' --file secret-payload http://x.x.x.x:9311/v1/secrets/19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60 >> >> I'm using the below OpenStack4j version, >> >> Bundle-Name: OpenStack4j Core >> >> Bundle-Version: 3.6.0 >> >> OpenStack is in Queens version. >> >> Let me know if someone can help on this. >> Regards, >> Srini >> >> >>

1 0

Kolla-ansible all-in-one and Hyper Converged solution
by KK CHN 06 Sep '22

06 Sep '22

Hi, [1 ] I am aiming for a prototype of HCI on a DELL ( R650 2 CPU and 40 cores . 2.4 TB) server machine. The Operating System choice is Debian 10. [2] Right now I am successful in Kolla-ansible all-in-one installation of Wallaby/stable on a Debian 10 Virtual machine with the default configs enabled as in the documentation " https://docs.openstack.org/project-deploy-guide/kolla-ansible/wallaby/uicks… " in Virtualenv setup. Able to get the horizon dashboard with the default services enabled and created and tested the cirros VM launching .. working fine. [3 ] I have to repeat the same all-in-one deployment on the physical machine as in [1] with the default configs and then convert it as an HCI node. What all features do I need to configure / enable in all-in-on / globals.yml to convert this box as a working HCI node ? Any hints / directives for the essential configurations needed for this server box to convert it as an HCI node are most welcome. kindly shed some light on this and any reference documents/URLs to do this ? Thank you, Krish

5 5

Microstack - VM networking & installation probs
by Tim Kahlke 06 Sep '22

06 Sep '22

Hi, I tried to install microstack 245 via Canonical and am running into the “old” VM-can’t-connect-external-network problem. OS: Ubuntu 20.04 Microstack v245 Install seems to have worked ok using sudo snap install microstack --beta. However, journalctl -xe shows ovsdb-server[83528]: ovs|26322|socket_util|ERR|6642:0.0.0.0: bind: Address already in use But not sure if that’s related or not. Network setup is the default, i.e., external 10.20.20.0/24 and internal 192.168.1.0/24. From the host machine I can ping the VMs and vice versa, but I can’t get past the host from the VM. I tried to apply some of the solutions I found on the web, so far without success. This one seems to work for people but my microstack doesn’t seem to have the ovs-vsctl command anywhere. Any suggestions would be much appreciated. Tim

2 1

[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

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Last Days - FINAL REMINDER
by Amy Marrich 06 Sep '22

06 Sep '22

This is your last reminder for the election, I know the US , CA, and a few other countries are on holiday today. Please also read Jeremy's early email about the TC seats and governance. Thank, 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 : 2 days, 4:16:33 Nominations progress : 84.44% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 35 ( 67.31%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 17 (Adjutant Barbican Keystone Masakari Mistral OpenStackSDK OpenStack_Charms Openstack_Chef Oslo Release_Management Requirements Sahara Senlin Skyline Swift Venus Zun) =================================================== Stats gathered @ 2022-09-05 19:28:27 UTC This means that with approximately 2 days left, 17 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

[neutron] Team meeting on Sept. 6 cancelled
by Lajos Katona 06 Sep '22

06 Sep '22

Hi, Sorry for late mail, but tomorrow I can't drive the team meeting, so I have to cancel it. I will be otherwise available tomorrow (except around the meeting time), so you can reach me on neutron channel for example. Lajos Katona (lajoskatona)

1 0

Error During installation devstack ModuleNotFoundError: No module named 'neutron'
by mahdi n 06 Sep '22

06 Sep '22

I was installing DevStack on Ubuntu 20.04 when I encountered this error It says that the Neutron module was not found while neutron is installed ++lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > /usr/local/bin/python3.8 -c 'from neutron.common.ovn import extensions ;\ > > print(",".join(extensions.ML2_SUPPORTED_API_EXTENSIONS)) > ' > Traceback (most recent call last): > > File "<string>", line 1, in <module> > > ModuleNotFoundError: No module named 'neutron' > > +lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > >

3 2

[all][election][tc] TC election at risk of single-employer majority
by Jeremy Stanley 06 Sep '22

06 Sep '22

The extended nomination period for the upcoming TC election closes in just over two days. We need to elect people to fill 4 of the 9 seats on the TC during this round. We currently have just enough candidates to fill the open seats, but in so doing we would end up with a majority of the TC members employed by the same company. Appendix 4 of the bylaws of the Open Infrastructure Foundation, the Technical Committee Member Policy[*], states: > In the event of a Technical Committee election that would result > in half or more of the members of the Technical Committee being > Affiliated, the Board of Directors may defer the effective date of > office of the newly elected Technical Committee members who are > Affiliated for a period not to exceed thirty (30) days after a > resolution by the Board of Directors approving such deferral. The > Board of Directors must pass such resolution within thirty (30) > days of the notice of election results from the Technical > Committee. During such period of deferral, the Technical Committee > and the Board of Directors shall work to resolve the issue by > agreement among themselves, such as by a resignation of one or > more Technical Committee members or having the Individual Member > with the next highest number of votes become a member of the > Technical Committee. If the Technical Committee and the Board of > Directors are not able to agree on a resolution within such thirty > (30) day period, the Board of Directors may require another > election for such positions. In order to avoid this outcome, we need additional nominees with a variety of affiliations immediately. If you've considered running for a seat on the OpenStack TC before, now is definitely the time. Please see earlier announcements[**] from the election officials for details on how to submit your nomination. Thanks! [*] https://openinfra.dev/legal/openstack-technical-committee-member-policy [**] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030094.… https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… -- Jeremy Stanley

1 0

Secret getPayload() openstack4j
by Srinivasan T 05 Sep '22

05 Sep '22

Hi, I'm unable to get the secret's payload from openstack4j, it always returns null. Secret secret = os.barbican().secrets().get("19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60"); secret.getPayload(); //Always returns null The same works when using the OpenStack CLI, openstack secret get --payload_content_type 'application/octet-stream' --file secret-payload http://x.x.x.x:9311/v1/secrets/19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60 I'm using the below OpenStack4j version, Bundle-Name: OpenStack4j Core Bundle-Version: 3.6.0 OpenStack is in Queens version. Let me know if someone can help on this. Regards, Srini

2 1

[adjutant][magnum][mistral][sahara][watcher][zaqar][tc] broken gate for deliverables
by Előd Illés 05 Sep '22

05 Sep '22

Hi, Now that we have passed Zed-3 milestone, Release team starts to check the health of deliverables via their gate healthiness. The 1st round of checks showed that the following deliverables seem to have blocked gates: python-adjutantclient [1] python-magnumclient [2] python-mistralclient [3] python-saharaclient [4] python-watcherclient [5] python-zaqarclient [6] We are asking the teams to fix their gates and propose a release after it is fixed as soon as possible, otherwise these deliverables might not be part of the official Zed release. [1] https://review.opendev.org/c/openstack/python-adjutantclient/+/855763 [2] https://review.opendev.org/c/openstack/python-magnumclient/+/855778 [3] https://review.opendev.org/c/openstack/python-mistralclient/+/855781 [4] https://review.opendev.org/c/openstack/python-zaqarclient/+/855796 [5] https://review.opendev.org/c/openstack/python-watcherclient/+/855795 [6] https://review.opendev.org/c/openstack/python-saharaclient/+/855787 Thanks, Előd Illés irc: elodilles

2 1

http proxy support
by Oliver Weinmann 03 Sep '22

03 Sep '22

Hi, I was wondering if there is a way to set a http proxy in kolla-ansible during deployment / update etc. Today I wanted to pull new containers and this saturates our internet connection. What we usually do is have machine that massively download stuff from the internet use a squid proxy that throttles their bandwidth. I found the following feature request: https://bugs.launchpad.net/kolla-ansible/+bug/1829586 And it seems some work had been done, but I can't seem to find any info if the change really made it into production: https://review.opendev.org/c/openstack/kolla-ansible/+/692006/ Any help or hints are highly appreciated. Cheers, Oliver

2 4

[all][tc] What's happening in Technical Committee: summary 2022 Sept 2: Reading: 5 min
by Ghanshyam Mann 03 Sep '22

03 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 01. Most of the meeting discussions are summarized in this email. Meeting full recording is available @ https://www.youtube.com/watch?v=WDfOx1m-wog and summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-01-15.01.log.html * Next TC weekly meeting will be on Sept 08 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 07. 2. What we completed this week: ========================= * Appointed Dale Smith as Adjutant PTL for Zed cycle[2] * Switched requirements to distributed leadership [3] * Added Exception for the combined 2023.1(Antelope) elections [4] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[5], four are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[6]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- By considering the holiday weeks, we decided to extend the nomination by a week[7]. The new deadline for nomination is Sept 7 [8]. We request you not to delay your nomination for PTL or TC. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [9]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[10], * I have created the TC PTG etherpad to collect the topic[11]. * I sent email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[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. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14]15]. Project updates ------------------- * Switch release management to distributed leadership[16] 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[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 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/+/849606 [3] https://review.opendev.org/c/openstack/governance/+/854685 [4] https://review.opendev.org/c/openstack/governance/+/854624 [5] https://etherpad.opendev.org/p/tc-zed-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… [8] https://governance.openstack.org/election/ [9] https://review.opendev.org/c/openstack/governance/+/854375 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://etherpad.opendev.org/p/tc-2023-1-ptg [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] https://review.opendev.org/c/openstack/governance/+/855276 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

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

02 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

[tripleo] gate blocker tripleo-ci-centos-9-content-provider
by Chandan Kumar 02 Sep '22

02 Sep '22

Hello tripleo, Please hold your recheck on master tripleo branch, we have a gate blocker for tripleo-ci-centos-9-content-provider. https://bugs.launchpad.net/tripleo/+bug/1988514 The team is currently working on fixing it. With Regards, Chandan Kumar

2 1

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

02 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

[release] Release countdown for week R-4, Sep 05 - 09
by Előd Illés 02 Sep '22

02 Sep '22

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

1 0

Kolla-ansible Openstack : Queries on Metering and Rating Module
by KK CHN 02 Sep '22

02 Sep '22

I have installed all-in-one using Kolla-ansible wallaby on a Virtual Machine (Debian 10) By default configurations up and running are able to create VMs .. with the default Cirros image. I want the Metering and Billing modules for a deployment scenario. So I used this setup as a PILOT and use ceilometer with cloudkitty and gnocchi.. I have enabled ( correct me If I am wrong or missing any other directives for metering and rating other than this if required => enable_ceilometer : "yes" enable_cloudkitty : "yes" enable_gnocchi : "yes" , enable_horizon_cloudkitty : "{{ enable_cloudkitty |bool }}" cloudkitty_collector_backend: "gnocchi" in /etc/kolla/globals.yml Then re deployed the all in one $ ( (venvopenstack) cloud@wallaby:~$ kolla-ansible -i ./all-in-one bootstrap-servers , (venvopenstack) cloud@Xena:~$ kolla-ansible -i ./all-in-one prechecks, (venvopenstack) cloud@Xena:~$ kolla-ansible -i ./all-in-one deploy ) .. All went well up and able to access horizon dashboard. How to view the metrics and ratings :: I am able to get Admin => Rating tab Enabled the three Rating Modules there. (Hashmap, noop, pyscripts) .. Rating Summary : I am getting as below All CloudTotal 0 LL <http://10.184.48.94/admin/rating_summary/ALL> Cloud Total <http://10.184.48.94/admin/rating_summary/ALL> 0 Hashmap and pyscrips tab nothing to view , its empty. How can I use this Rating module and how to get useful values there ? Or is there any other configurations I have to make to get a better metering and billing utility using these tools. Kindly share your tips and expertise with these tools. What / where to refer to get a nice Rating/metering configurations using these tools.( Or do I need to enable / configure more directives or resources ??) I have not seen a highly populated Rating Module interface in Horizon so it should be. Any reference images and configurations are most welcome. Thank you, Krish

3 5

[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

Unable to change the app-name / programname for barbican-api service
by Rohit Singh 02 Sep '22

02 Sep '22

Hi guys, I am facing issues with barbican-api logging with syslog. I have configured rsyslog for barbican service and want to write the logs on remote host based on %programname properties, But I observed that the barbican-api app-name is not set ,so by default it's logging into loadwsgi.py.log . Is there any way to set the app-name for barbican-api service ? Regards Rohit Singh Mob : +91- 88824 68891

1 0

Unable to change the app-name / programname for barbican-api service
by Rohit Kumar Singh 02 Sep '22

02 Sep '22

Hi guys, I am facing issues with barbican-api logging with syslog. I have configured rsyslog for barbican service and want to write the logs on remote host based on %programname properties, but i observed barbican-api app-name is not set ,so by default it's logging into loadwsgi.py.log . I s there any way to set the app-name for barbican-api service ?

1 0

[all][elections][tc] TC Election Non-Candidacy ...
by Jay Bryant 02 Sep '22

02 Sep '22

All, I wanted to take a moment to let everyone know that I am not going to be running for the TC, this time around. The last two years on the TC have been a great experience and I am grateful for the trust the community put in me. At this point, however, I think it is best to let others who may want to join the TC have the opportunity to do so. Again, thank you for this opportunity to support the community over the last couple of years! Sincerely, Jay Bryant (jungleboyj)

3 2

[manila] Feature freeze exceptions
by Carlos Silva 02 Sep '22

02 Sep '22

Hello, Zorillas and interested stackers! During today's Manila weekly meeting we went over the status of our open changes that are eligible for feature freeze. Some candidates for the deadline were successfully merged over the course of this week, but there are also a few other changes that are receiving feedback from reviewers. Those changes will need some extra time to get in. We are in a shortage of reviewers to take care of all of the changes at once, and we are extending the deadline by one week. The changes yet to be merged and receiving the feature freeze exception are: *Metadata for share snapshots [1]* During the Yoga cycle, Manila metadata APIs were changed to be more generic and be able to accommodate metadata for other resources. For Zed, we planned to have metadatas being added to the snapshot resources. This change has received some reviews and seems to be quite close to being merged. During the tests, the manipulation of metadata for share snapshots seems to work just fine, and we are only getting some final tweaks to the implementation. *Refactor the Ceph NFS driver to use Cephadm NFS [2]* This is a driver-only change and it does not impact the Manila core itself. It is important for people consuming the Ceph drivers, and does not impact the current driver implementation. *Support share transfer between project [3]* This change is currently under review and is a good addition to the Manila core. Due to the shortage of reviewers, we only got more people looking at the change and testing the functionality late in the cycle. The three changes aforementioned should be merged by next Thursday (08 september 2022). [1] https://review.opendev.org/c/openstack/manila/+/825008 [2] https://review.opendev.org/c/openstack/manila/+/848987 [3] https://review.opendev.org/c/openstack/manila/+/843832 In case you have questions or concerns, please let me know. Thank you, carloss

1 0

[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

[neutron] Drivers meeting - Friday 02.09.2022 - cancelled
by Lajos Katona 01 Sep '22

01 Sep '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[cinder] experiences with S3 cinder-backup driver // client-side encryption feature
by Christian Rohmann 01 Sep '22

01 Sep '22

Hello openstack-discuss and cinder-backup users! There is an S3 driver available for cinder-backup since the Wallaby release already, see https://docs.openstack.org/releasenotes/cinder/wallaby.html#relnotes-18-0-0…. 1) I was wondering if anybody already used that on a somewhat larger scale and what you experiences are about performance, stability and compatibility? 2) What object storage implementation or external service were / are you using? 3) While there are options like "backup_s3_sse_customer_algorithm" and "backup_s3_sse_customer_key" make use of server-side-encryption (SSE), there seems to be no way to encrypt the data before actually sending it to the remote S3 (read: client-side encryption). Since the boto3 Python SDK by AWS is used, which does not actually implement CSE, like other language SDKs do (see my issue: https://github.com/boto/boto3/issues/3395) it seems obvious why that is not a totally low-hanging fruit. But there are ways to add this, check out the references to e.g. https://github.com/StephenSorriaux/s3-encryption in the mentioned boto3 issue. Encrypting data before sending it off to a potentially externally operated service seems like a nice feature. Even a single encryption key would then protect that data from having to trust a 3rd party. I know encrypted cinder volumes would also work, but they are not as commonly used. * Is CSE something that others would also like to see for the S3 driver? * Cinder devs, would this maybe be worth a spec for the next cycle? Regards Christian

1 0

[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