November 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 23 Dec '24

23 Dec '24

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

4 4

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

10 Oct '24

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

5 9

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

06 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 23 Aug '23

23 Aug '23

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

3 4

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

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

01 Jun '23

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

3 5

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

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

24 Feb '23

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

3 5

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

08 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

The CFP for the OpenInfra Summit 2023 is open!
by Erin Disney 25 Dec '22

25 Dec '22

Hi Everyone! The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is NOW LIVE [1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. The CFP closes January 10, 2023, at 11:59 p.m. PT We are also now accepting submissions for Forum sessions [3]! What should you submit to the forum vs. the traditional CFP? For the Forum, submit discussion-oriented sessions, including challenges around different software components, working group progress or best practices to tackle common issues. Looking for other resources? Registration [4], sponsorships [5], travel support [6] and visa requests [7] are also all open! Find all the information on the OpenInfra Summit 2023 in one place [8]! Cheers, Erin [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations <https://cfp.openinfra.dev/app/vancouver-2023/19/presentationshttps://cfp.op…> [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/> [3] https://cfp.openinfra.dev/app/vancouver-2023/20/ <https://cfp.openinfra.dev/app/vancouver-2023/20/> [4] http://openinfra.dev/summit/registration <http://openinfra.dev/summit/registration> [5] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/> [6] https://openinfrafoundation.formstack.com/forms/openinfra_tsp <https://openinfrafoundation.formstack.com/forms/openinfra_tsp> [7] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 <https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023> [8] https://openinfra.dev/summit/vancouver-2023 <https://openinfra.dev/summit/vancouver-2023>

2 1

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

16 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

[manila][release] Proposing to EOL Stein
by Carlos Silva 14 Dec '22

14 Dec '22

Hello! Recently in a weekly meeting we chatted about EOLing stable/stein and all the attendants were found to be in favor of this [0]. As the procedures go [1], we need to make it formal through a post in this mailing list, and see if there are objections. In case of concerns or objections, please reach out through email or the #openstack-manila IRC channel. This will impact all branched manila repositories (manila, python-manilaclient and manila-ui). If there aren't objections or strong concerns, I will be proposing the patches to EOL stable/stein within one week. [0] https://meetings.opendev.org/meetings/manila/2022/manila.2022-11-03-15.00.l… [1] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l… Thanks, carloss

1 1

[cinder] volume_attachement entries are not getting deleted from DB
by Hemant Sonawane 13 Dec '22

13 Dec '22

Hello I am using wallaby release openstack and having issues with cinder volumes as once I try to delete, resize or unshelve the shelved vms the volume_attachement entries do not get deleted in cinder db and therefore the above mentioned operations fail every time. I have to delete these volume_attachement entries manually then it works. Is there any way to fix this issue ? nova-compute logs: cinderclient.exceptions.ClientException: Unable to update attachment.(Invalid volume: duplicate connectors detected on volume Help will be really appreciated Thanks ! -- Thanks and Regards, Hemant Sonawane

3 6

[neutron][devstack][qa] Dropping lib/neutron module
by Slawek Kaplonski 12 Dec '22

12 Dec '22

Hi, As You maybe know (or not as this was very long time ago) there are 2 modules to deploy Neutron in devstack: * old one called lib/neutron-legacy * new one called lib/neutron The problem is that new module lib/neutron was really never finished and used widely and still everyone is using (and should use) old one lib/neutron-legacy. We discussed that few times during PTGs and we finally decided to drop "new" module lib/neutron and have then rename old "lib/neutron-legacy" to be "lib/neutron" again. Decision was made because old module works fine and do its job, and as there is nobody who would like to finish really new module. Also having 2 modules from which "legacy" one is the only one which really works can be confusing and we want to avoid that confusion. So I proposed patches [1] and [2] to drop this unfinished module. I also proposed DNM patches for Neutron [3] and Tempest [4] to test that all jobs will work fine. But if You are maybe relaying on the Neutron modules from Devstack, please propose some test patch in Your project too and check if everything works fine for You. In patch [2] I didn't really removed "lib/neutron-legacy" yet because there are some projects which are sourcing that file in their devstack module. As [1] and [2] will be merged I will be proposing patches to change that for those projects but any help with that is welcome :) [1] https://review.opendev.org/c/openstack/devstack/+/865014 [2] https://review.opendev.org/c/openstack/devstack/+/865015 [3] https://review.opendev.org/c/openstack/neutron/+/865822 [4] https://review.opendev.org/c/openstack/tempest/+/865821 -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

[ironic][release] Bugfix branch status and cleanup w/r/t zuul-config-errors
by Jay Faulkner 07 Dec '22

07 Dec '22

Hey all, I've been looking into the various zuul config errors showing up for Ironic-program branches. Almost all of our old bugfix branches are in the list. Additionally, not properly retiring the bugfix branches leads to an ever-growing list of branches which makes it a lot more difficult, for contributors and operators alike, to tell which ones are currently supported. I've put together a document describing the situation as it is now, and my proposal: https://etherpad.opendev.org/p/IronicBugfixBranchCleanup Essentially, I think we need to: - identify bugfix branches to cleanup (I've done this in the above etherpad, but some of the ) - clean them up (the next step) - update Ironic policy to set a regular cadence for when to retire bugfix branches, and encode the process for doing so This means there are two overall questions to answer in this email: 1) Mechanically, what's the process for doing this? I don't believe the existing release tooling will be useful for this, but I'm not 100% sure. I've pulled (in the above etherpad and a local spreadsheet) the last SHA for each branch; so we should be able to EOL these branches similarly to how we EOL stable branches; except manually instead of with tooling. Who is going to do this work? (I'd prefer releases team continue to hold the keys to do this; but I understand if you don't want to take on this manual work). 2) What's the pattern for Ironic to adopt regarding these branches? We just need to write down the expected lifecycle and enforce it -- so we prevent being this deep into "branch debt" in the future. What do folks think? - Jay Faulkner

4 6

[heat][release] Proposing to EOL Rocky and Stein
by Brendan Shephard 06 Dec '22

06 Dec '22

Hi, We were discussing some of the older branches we have and thought it was about time we start moving some of them to EOL. Initially, I would like to move Rocky and Stein to EOL and have done so here: https://review.opendev.org/c/openstack/releases/+/866135 We would also like to move Train to EOL as well, pending a few changes being merged. I wanted to reach out and ensure there is no objections here to any of these branches being EOL’d. Feel free to voice any concerns, otherwise I will move forward with that next week. Cheers, Brendan Shephard Senior Software Engineer Red Hat Australia

2 1

[nova][placement][tempest] Hold your rechecks
by Sylvain Bauza 05 Dec '22

05 Dec '22

Sorry folks, that's kind of an email I hate writing but let's be honest : our gate is busted. Until we figure out a correct path for resolution, I hereby ask you to *NOT* recheck in order to not spill our precious CI resources for tests that are certain to fail. Long story story, there are currently two problems : #1 https://launchpad.net/bugs/1940425 nova-ovs-hybrid-plug and nova-next jobs 100% fail due to a port remaining in down state. #2 https://bugs.launchpad.net/nova/+bug/1960346 nova-lvm job 100% fails due to a volume detach failure probably due to QEMU #1 is currently investigated by the Neutron team meanwhile a patch [1] has been proposed against Zuul to skip the failing tests. Unfortunately, this patch [1] is unable to merge due to #2. #2 has a Tempest patch that's being worked on [2] but the current state of this patch is WIP. We somehow need to have an agreement on the way forward during this afternoon (UTC) to identify whether we can reasonably progress on [2] or skip the failing tests on nova-lvm. Again, sorry about the bad news and I'll keep you informed. -Sylvain [1] https://review.opendev.org/c/openstack/nova/+/865658/ [2] https://review.opendev.org/c/openstack/tempest/+/842240

2 5

[Magnum] ls /etc/cni/net.d/ is emty
by Nguyễn Hữu Khôi 30 Nov '22

30 Nov '22

Hello guys. I use Magnum on Xena and I custom k8s cluster by labels. But My cluster is not ready and there is nothing in /etc/cni/net.d/ and my cluster said: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized And this is my labels kube_tag=v1.21.8-rancher1,container_runtime=containerd,containerd_version=1.6.10,containerd_tarball_sha256=507f47716d7b932e58aa1dc7e2b3f2b8779ee9a2988aa46ad58e09e2e47063d8,calico_tag=v3.21.2,hyperkube_prefix= docker.io/rancher/ Note: I use Fedora Core OS 31 for images. Thank you. Nguyen Huu Khoi

2 3

[kolla-ansible][Yoga][Magnum] How to delete a cluster containing errors
by wodel youchi 30 Nov '22

30 Nov '22

Hi, I have a magnum cluster stack which contains errors in its constituents, some of the VMs (minions) that belong to that cluster do longer exist. When I try to delete the stack it fails, and I get DELETE aborted (Task delete from ResourceGroup "kube_minions" [fddb3056-9b00-4665-b0d6-c3d3f176814b] Stack "testcluter01-puf45b6dxmrn" [d10af7f2-6ecd-442b-b1f9-140b79e58d13] Timed out) Is there a way to force the deletion to proceed even with those errors? Regards.

3 6

[cinder] Bug report from 11-23-2022 to 11-30-2022
by Sofia Enriquez 30 Nov '22

30 Nov '22

No meeting today due to Antelope Midcycle-1 (R-18). This is a bug report from 11-23-2022 to 11-30-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1998083 "volume_attachement entries are not getting deleted from DB." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1997980 "rbd: 'error updating features for image' when enabling multi-attach." Fix proposed to master. Low - https://bugs.launchpad.net/cinder/+bug/1997876 "Ceph backup: Improve error message when creating an incremental backup of a non-RBD volume." Unassigned. Cheers, Sofia -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[cinder] 2023.1 R-16 virtual mid cycle on 30th November (today)
by Rajat Dhasmana 30 Nov '22

30 Nov '22

Hello Argonauts, The first 2023.1 (Antelope) mid cycle R-16 will be held on 30th November (today) with the following details: Date: 30th November 2022 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 Etherpad: https://etherpad.opendev.org/p/cinder-antelope-midcycles Thanks and regards Rajat Dhasmana

1 0

[neutron][releases] Proposing to EOL Train networking-ovn
by Rodolfo Alonso Hernandez 30 Nov '22

30 Nov '22

Hello: The transition of this branch to EM was done 1,5 years ago [1]. During this time the maintenance of Train networking-ovn has continued. However, due to the lack of time and personal resources, we can't properly maintain it. That leads to problems like [1]. The ML2/OVN driver was successfully merged in the Neutron repository in Ussury. We continue the development and improvement of this ML2 mechanism driver. A patch to mark this branch as EOL will be pushed in two weeks. If you have any inconvenience, please let me know in this mail chain or in IRC (ralonsoh, #openstack-neutron channel). You can also contact any Neutron core reviewer in the IRC channel. Regards. [1]https://review.opendev.org/c/openstack/releases/+/790760 [2]https://bugs.launchpad.net/neutron/+bug/1997262

1 0

Re: Unable to access Internet from an instance and accessing instance using floating-point IPs from external network
by Eugen Block 30 Nov '22

30 Nov '22

So you did modify the default security-group, ports 8000 and 8080 are not open by default. Anyway, can you please clarify what doesn't work exactly? Does the instance have an IP in the public network but the router is not pingeable (but that is not necessarily an issue) and you can't access it via which protocols? Does SSH work? Is the access blocked by a http_proxy? Zitat von vincent lee <vincentlee676(a)gmail.com>: > To add on to my previous email, I have attached an image of my security > group as shown below. > > Best regards, > Vincent > > On Tue, Nov 22, 2022 at 3:58 AM Eugen Block <eblock(a)nde.ag> wrote: > >> Just one more thing to check, did you edit the security-group rules to >> allow access to the outside world? >> >> Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >> >> > it should be missing a default route most of the time. >> > or check IP tables on router namespace the DNAT and SNAT are working >> > properly >> > >> > >> > >> > On Tue, Nov 22, 2022 at 9:40 AM Tobias McNulty <tobias(a)caktusgroup.com> >> > wrote: >> > >> >> On Mon, Nov 21, 2022 at 7:39 PM vincent lee <vincentlee676(a)gmail.com> >> >> wrote: >> >> >> >>> After reviewing the post you shared, I believe that we have the correct >> >>> subnet. Besides, we did not modify anything related to the cloud-init >> for >> >>> openstack. >> >>> >> >> >> >> I didn't either. But I found it's a good test of the network! If you are >> >> using an image that doesn't rely on it you might not notice (but I >> >> would not recommend that). >> >> >> >> >> >>> After launching the instances, we are able to ping between the >> instances >> >>> of the same subnet. However, we are not able to receive any internet >> >>> connection within those instances. From the instance, we are able to >> ping >> >>> the router IP addresses 10.42.0.56 and 10.0.0.1. >> >>> >> >> >> >> To make sure I understand: >> >> - 10.42.0.56 is the IP of the router external to OpenStack that provides >> >> internet access >> >> - This router is tested and working for devices outside of OpenStack >> >> - OpenStack compute instances can ping this router >> >> - OpenStack compute instances cannot reach the internet >> >> >> >> If that is correct, it does not sound like an OpenStack issue >> necessarily, >> >> but perhaps a missing default route on your compute instances. I would >> >> check that DHCP is enabled on the internal subnet and that it's >> providing >> >> everything necessary for an internet connection to the instances. >> >> >> >> Tobias >> >> >> >> >> >> >> >> >> >> >> > > -- > thanks you. > vincentleezihong > 2garnet > form2

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Nov 30 at 1600 UTC
by Ghanshyam Mann 29 Nov '22

29 Nov '22

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

1 1

[Kolla-ansible][Neutron] VMs not getting public IPs if attached directly to public subnet
by wodel youchi 29 Nov '22

29 Nov '22

Hi, We have an HCI deployment with 3 controllers and 9 compute/storage nodes. Two of the controllers have the role of neutron server. The platform uses two bonded interfaces : bond1 : is used for : *neutron_external_interface* bond0 : with many vlans on top of it to segregate the rest of the networks : - bond0 : vlan natif used for nodes deployment (dhcp, tftp, pxeboot) - bond0.10 : vlan 10 ceph public - bond0.20 : vlan 20 ceph cluster - bond0.30 : vlan 30 API - bond0.40 : vlan 40 tunnel * - bond0.50 : vlan 50 Public network, here are the public IPs of the 03 controllers, the public horizon VIP interface is created here.* In our configuration we have *"enable_neutron_provider_networks = yes"*, which means that an instance can have a public IP directly without using a virtual-router + NAT. But it does not work. If we create and instance with a private network, then we attach to it a floating IP, the VM is reachable from the Internet, but if we attach the VM directly to the public network, it does not get an IP address from the public pool, we think it's a dhcp problem but we could not find the source, we think it's the *Vlan part.* The controllers are in Vlan 50, if we create a virtual-router it gets its public IP without any problem. But if we are not mistaken, if an instance is plugged directly into the public network, it uses bond1 to send its dhcp requests, but since this interface is not in vlan 50, the requests don't get to the controllers, is this right? If yes, is there a solution? can we use bond1.50 as an interface for kolla's *neutron_external_interface * instead? Regards.

3 3

[OVB - openstack-virtual-baremetal] - Douglas Viroel and Chandan Kumar as core
by Harald Jensas 29 Nov '22

29 Nov '22

Hi, After discussions with Douglas, Chandan and Ronelle Landy I would like to suggest adding Douglas and Chandan to the OVB core team. The repository have very little activity, i.e there is not a lot of review history to base the decision on. I did work with both individuals when onboarding new clouds to run TripleO CI jobs utilizing OVB, they have a good understanding of how the thing works. If there are no objections, I will add them to them as core reviewers next week. Regards, Harald

3 3

[openstack-ansible] Designate: role seems trying to update DNS server pools before syncing database
by Taltavull Jean-François 29 Nov '22

29 Nov '22

Hello, During the first run, the playbook 'os-designate-install.yml' fails and the 'designate-manage pool update' command produces the log line below: 'Nov 25 11:50:06 pp3controller1a-designate-container-53d945bb designate-manage[2287]: 2022-11-25 11:50:06.518 2287 CRITICAL designate [designate-manage - - - - -] Unhandled error: oslo_messaging.rpc.client.RemoteError: Remote error: ProgrammingError (pymysql.err.ProgrammingError) (1146, "Table 'designate.pools' doesn't exist")' Looking at the 'os_designate' role code shows that the handler ` Perform Designate pools update` is flushed before tables are created in the 'designate' database. O.S.: Ubuntu 20.04 OpenStack release: Wallaby OSA tag: 23.2.0 Regards, Jean-Francois

2 4

[neutron] neutron-db-manage multiple heads
by Eugen Block 29 Nov '22

29 Nov '22

Hi *, I'd like to ask you for advice on how to clean up my neutron db. At some point (which I don't know exactly, probably train) my neutron database got inconsistent, apparently one of the upgrades did not go as planned. The interesting thing is that the database still works, I just upgraded from ussuri to victoria where that issue popped up again during 'neutron-db-manage upgrade --expand', I'll add the information at the end of this email. Apparently, I have multiple heads, and one of them is from train, it seems as if I never ran --contract (or it failed and I didn't notice). Just some additional information what I did with this database: this cloud started out as a test environment with a single control node and then became a production environment. About two and a half years ago we decided to reinstall this cloud with version ussuri and import the databases. I had a virtual machine in which I upgraded the database dump from production to the latest versions at that time. That all worked quite well, I only didn't notice that something was missing. Now that I finished the U --> V upgrade I want to fix this inconsistency, I just have no idea how to do it. As I'm not sure how all the neutron-db-manage commands work exactly I'd like to ask for some guidance. For example, could the "stamp" command possibly help? Or how else can I get rid of the train head and/or how to get the train revision to "contract" so I can finish the upgrade and contract the victoria revision? I can paste the whole neutron-db history if necessary (neutron-db-manage history), please let me know what information would be required to get to the bottom of this. Any help is greatly appreciated! Thanks! Eugen ---snip--- controller01:~ # neutron-db-manage upgrade --expand [...] alembic.script.revision.MultipleHeads: Multiple heads are present for given argument 'expand@head'; 633d74ebbc4b, I38991de2b4 controller01:~ # neutron-db-manage current --verbose Running current for neutron ... INFO [alembic.runtime.migration] Context impl MySQLImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. Current revision(s) for mysql+pymysql://neutron:XXXXX@controller.fqdn/neutron: Rev: bebe95aae4d4 (head) Parent: b5344a66e818 Branch names: contract Path: /usr/lib/python3.6/site-packages/neutron/db/migration/alembic_migrations/versions/ussuri/contract/bebe95aae4d4_.py Rev: 633d74ebbc4b (head) Parent: 6c9eb0469914 Branch names: expand Path: /usr/lib/python3.6/site-packages/neutron/db/migration/alembic_migrations/versions/train/expand/633d74ebbc4b_.py Rev: I38991de2b4 (head) Parent: 49d8622c5221 Branch names: expand Path: /usr/lib/python3.6/site-packages/neutron/db/migration/alembic_migrations/versions/victoria/expand/I38991de2b4_source_and_destination_ip_prefix_neutron_metering_rule.py OK ---snip---

2 10

Re: Unable to access Internet from an instance and accessing instance using floating-point IPs from external network
by Tobias McNulty 28 Nov '22

28 Nov '22

On Mon, Nov 21, 2022 at 7:39 PM vincent lee <vincentlee676(a)gmail.com> wrote: > After reviewing the post you shared, I believe that we have the correct > subnet. Besides, we did not modify anything related to the cloud-init for > openstack. > I didn't either. But I found it's a good test of the network! If you are using an image that doesn't rely on it you might not notice (but I would not recommend that). > After launching the instances, we are able to ping between the instances > of the same subnet. However, we are not able to receive any internet > connection within those instances. From the instance, we are able to ping > the router IP addresses 10.42.0.56 and 10.0.0.1. > To make sure I understand: - 10.42.0.56 is the IP of the router external to OpenStack that provides internet access - This router is tested and working for devices outside of OpenStack - OpenStack compute instances can ping this router - OpenStack compute instances cannot reach the internet If that is correct, it does not sound like an OpenStack issue necessarily, but perhaps a missing default route on your compute instances. I would check that DHCP is enabled on the internal subnet and that it's providing everything necessary for an internet connection to the instances. Tobias

4 3

[all] Cargo Culted Tox install_command overrides
by Clark Boylan 28 Nov '22

28 Nov '22

A subset of tempest jobs recently began to exhibit some interesting behavior. The tox installation was finding the global pip installation instead of pip in the tox virtualenv which led to an attempt to install packages globally which failed. Eventually, I discovered the reason this happened was that virtualenv created a broken venv installation for tox, but this was made far more confusing by two tox settings in tempest's tox.ini: install_command and allowlist_externals. Tempest had overridden install_command to ` pip install {opts} {packages}` and set allowlist_externals to `*`. This allowed tox to find and use global pip without complaint. Tempest has since cleaned these up with this change [0], which should result in nicer error messages in the future if we have similar problems. I have noticed that many projects have cargo culted this configuration, particularly for install_command [1]. The default install_command for tox is `python -m pip install {opts} {packages}` [2]. This is almost equivalent to our overrides except that it uses pip as a module. This is important in this case because we don't install python2 regularly which means there is no `python` command except for in the created virtualenv where `python` == `python3`. The resulting behavior difference here would have been helpful to have when debugging the underlying issue in tempest. All that to say, I would suggest that those who have install_command set similarly to tempest remove this unnecessary configuration. Separately, setting allowlist_externals to `*` allows all global commands to run without complaint or an indication they are being used. Far fewer projects have this problem though [3]. Those that do should consider updating their config to explicitly list the commands they actually need from outside the virtualenv. Neither of these changes is critical, but I wanted people to be aware of this as we seem to have copied it all over the place. [0] https://review.opendev.org/c/openstack/tempest/+/865314 [1] https://codesearch.opendev.org/?q=install_command&i=nope&literal=nope&files… [2] https://tox.wiki/en/latest/config.html#conf-install_command [3] https://codesearch.opendev.org/?q=allowlist_externals%20%3D%20%5C*&i=nope&l…

1 0

[oslo] New driver for oslo.messaging
by 王坤田 28 Nov '22

28 Nov '22

Hello: I want to develop a new driver for oslo.messaging to use rocketmq in openstack environment. I wonder if the community need this new driver？ Best Regards！

4 3

[neutron] Bug deputy report, Nov. 21. - Nov. 27.
by Lajos Katona 28 Nov '22

28 Nov '22

Hi Neutron Team I was the bug deputy in neutron last week, please check my summary. Needs attention ================= * networking-ovn-dsvm-functional-py27 job killed on timeout in stable/train branch (https://bugs.launchpad.net/neutron/+bug/1997262) *Stable only* * [ovn-octavia-provider] Octavia LB stuck in PENDING_UPDATE after creation (https://bugs.launchpad.net/neutron/+bug/1997567 ) *HIGH* * neutron_lib.exceptions.InvalidInput: Invalid input for operation: Segmentation ID should be lower or equal to 4095 ( https://bugs.launchpad.net/neutron/+bug/1997955 ) *Incomplete* * related doc bug: Manual install & Configuration in Neutron incorrect vni_ranges leads to error (https://bugs.launchpad.net/neutron/+bug/1998085 ) *LOW* * Prevent initializing "ovn-router" service if OVN mech driver is not called (https://bugs.launchpad.net/neutron/+bug/1997970 ) *MEDIUM* * [fullstack] Error in "test_logging" ( https://bugs.launchpad.net/neutron/+bug/1997965 ) *High* In Progress ================= * [ovn-octavia-provider] HM not working for FIPs ( https://bugs.launchpad.net/neutron/+bug/1997418 ) * Neutron server doesn't wait for port DHCP provisioning while VM creation ( https://bugs.launchpad.net/neutron/+bug/1997492 ): https://review.opendev.org/c/openstack/neutron/+/865470 * "convert_to_sanitized_mac_address" shoudl accept netaddr.EUI type values ( https://bugs.launchpad.net/neutron/+bug/1997680 ): https://review.opendev.org/c/openstack/neutron-lib/+/865517 * after restart of a ovn-controller the agent is still down ( https://bugs.launchpad.net/neutron/+bug/1997982 ): https://review.opendev.org/c/openstack/neutron/+/865697 Already merged ================ * [DHCP] Error in "call_driver" method ( https://bugs.launchpad.net/neutron/+bug/1997964) https://review.opendev.org/c/openstack/neutron/+/840421

1 0

Does openstack have an official automatic evacuation instance scheme
by 韩光宇 28 Nov '22

28 Nov '22

Hi all, I would like to ask whether the openstack community has an official automatic evacuation instance scheme？ I have a openstack cluster, and all of glance, nova and cinder has used ceph. So I have a basic of instance HA. I want to imply automatic evacuation instance, but I'm a newer in this. Does the community have any related projects or recommended open source solutions? Any help is greatly appreciated! Thanks! Han

2 1

[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

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

25 Nov '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ *This week's meeting was cancelled. * Next TC weekly meeting will be on Nov 30 Wed at 16:00 UTC. Feel free to add the topic to the agenda[1] by Nov 29. 2. What we completed this week: ========================= * Nothing specific this week. 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[2]. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. Technical Election changes (Extending Nomination and voting period) ---------------------------------------------------------------------------------- As discussed in TC PTG sessions, TC is extending the technical election (PTL as well as the TC election) nomination and voting period from 1 week to 2 weeks. The TC charter change[4] is up for review and the changes will be effective from the 2023.2 cycle technical elections. Renovate translation SIG i18 ---------------------------------- * As the next step, Brian is working on the weblate funding proposal and it will be discussed with the Foundation staff and Board members in Dec 6th board meeting. Adjutant situation (project is not active) ----------------------------------------------- The adjutant project is not active. The last changes merged was on Oct 26, 2021 (more than 1 year back), Gate is broken also. During July this year, TC was marking this project as inactive[5] but Dale smith volunteered as PTL to maintain it. But there is no improvement in the situation yet. TC will be discussing it in the next TC meeting and decide the next step. Project updates ------------------- * Add Skyline repository for OpenStack-Ansible[6] * Add the cinder-infinidat charm to Openstack charms[7] * Add the infinidat-tools subordinate charm to OpenStack charms[8] * Add the manila-infinidat charm to Openstack charms[9] 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[10]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [11] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/865367 [5] https://review.opendev.org/c/openstack/governance/+/849153 [6] https://review.opendev.org/c/openstack/governance/+/863166 [7] https://review.opendev.org/c/openstack/governance/+/863958 [8] https://review.opendev.org/c/openstack/governance/+/864067 [9] https://review.opendev.org/c/openstack/governance/+/864068 [10] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [11] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][stable][ptl] Propose to EOL Queens series
by Elõd Illés 25 Nov '22

25 Nov '22

Hi, As more and more teams decide about moving their Queens branches to End of Life, it looks like the time has come to transition the complete Queens stable release for every project. The reasons behind this are the following things: - gates are mostly broken - minimal number of bugfix backports are pushed to these branches - gate job definitions are still using the old, legacy zuul syntax - gate jobs are based on Ubuntu Xenial, which is also beyond its public maintenance window date and hard to maintain - lack of reviews / reviewers on this branch Based on the above, if no objection comes from teams, then I'll start the process of EOL'ing Queens stable series. Please let the community know what you think, or indicate if any of the projects' stable/queens branch should be kept open in Extended Maintenance. Thanks, Előd Illés irc: elodilles @ #openstack-stable / #openstack-release

1 1

[openstackclient] Consistency between OSC commands >>> consistency with legacy clients
by Stephen Finucane 25 Nov '22

25 Nov '22

👋 tl;dr: $subject I reviewed a patch against openstackclient (OSC) today [1] and left a rather lengthy comment that I thought worthy of bringing up to a wider audience. The patch itself doesn't matter so much as what is was trying to achieve, namely modifying an existing OSC command to better match the structure of the equivalent legacy client command. The review provides more detail than I do here but the tl;dr: is that this is a big no-no and OSC will and must maintain consistency between OSC commands over consistency with legacy clients. As I noted in the review, consistency is one of the biggest advantages of OSC over the legacy clients: if you know the name of the resource type you wish to work with, you can pretty accurately guess the command and its structure. This is a thing that operators have consistently said they love about OSC and its one of the key reasons we're trying to get every command to provide full current API implementations in OSC (and SDK). Now I get that the way some of these consistent commands have been implemented has been the cause of contention in the past. I don't imagine it remains any less contentious today. However, these patterns are well-understood, well-known patterns that have for the most part worked just fine for close to a decade now. The kind of patterns I'm thinking about include: * The command to create a new resource should always take the format '<resource> create <human-readable identifer> * The command to modify some property of a resource should always take the format '<resource> set --property=value <name-or-identifier>' * The command to list, fetch or delete resources should always take the format '<resource> list', '<resource> get <name-or-identifier>', and '<resource> delete <name-or-identifier>', respectively. * Boolean options should always take the form of flags with an alternate negative option like '--flag' and '--no-flag', rather than '-- flag=<true|false>' * And a couple of other things that we tend to highlight in reviews. We want to preserve this behavior, lest OSC lose this huge USP and devolve into a muddle mess of different ideas and various individuals'/teams' preferences. I'm more than happy to discuss and debate this stuff with anyone who's interested and we'll continue reviewing each patch on its merit and providing exceptions to these rules where they make sense, but it will remain an ongoing goal and it's something we'd like people to consider when working on OSC itself or any of its plugins. I will now get off my pedestal/ivory tower 🗼 Thanks! Stephen PS: I'm talking here about the command themselves, not their implementations. We do somethings extra in OSC that are user helpful, like allowing users to identify resources by their name in addition to by their UUIDs. We also currently do things that no so user helpful, like crashing and burning if the name lookups fail (I'm thinking about the various Glance-related commands that error out if a project name/ID is passed to a command and the user can't look up that project). These are things we're more than willing to fix and will happily accept patches for :) [1] https://review.opendev.org/c/openstack/python-openstackclient/+/865377

6 13

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 25 Nov '22

25 Nov '22

Hello Neutrinos: Due to the lack of agenda and quorum this week, the Neutron drivers meeting is cancelled today. Have a nice weekend and see you next week!

1 0

[tacker] Tacker's Legacy API deprecation
by Ayumu Ueha (Fujitsu) 24 Nov '22

24 Nov '22

Hi Tacker users, Tacker team is going to mark the Tacker's Legacy APIs [1] (excluding VIM feature) to "deprecated" in Antelope cycle. Please see etherpad [2] about list of target APIs. We follow deprecation guideline [3] of OpenStack, and need to know how many users use Tacker's Legacy API. Please let me know if anyone still uses the Legacy API that will be marked "deprecated" via Rest-API or CLI(python-tackerclient) or GUI(tacker-horizon). If no one is using it, we will obsolete it in C cycle as planned. Thanks. [1] https://docs.openstack.org/api-ref/nfv-orchestration/v1/legacy.html [2] https://etherpad.opendev.org/p/tacker-legacy-deprecation [3] https://docs.openstack.org/project-team-guide/deprecation.html#guidelines Best Regards, Ueha

1 0

[neutron] networking-midonet mantainers
by Rodolfo Alonso Hernandez 24 Nov '22

24 Nov '22

Hello Neutrinos: We have recently found some zuul errors related to networking-midonet. In order to fix them, we have pushed [1]. However, the CI status of this project is not in good shape. This mail is a kind request for maintainers of this project. We need to ensure that the stable branches are still accepting patches and the CI jobs are passing. Thank you in advance. [1] https://review.opendev.org/q/project:openstack%252Fnetworking-midonet+statu…

2 1

[Openstack-Magnum] Health Check without Floating IP
by Nguyễn Hữu Khôi 24 Nov '22

24 Nov '22

Hello guys. I have used Magnum to setup k8s cluster and I dont use floating ip then my cluster show as below: [image: image.png] I used provider network only. Could you tell me if there is any way to have a health check? And Is there any way to setup k8s multi master without loadbalancer? Many thanks Nguyen Huu Khoi

1 0

[swift] Periodically crashes of proxy-server
by Ришат Азизов 24 Nov '22

24 Nov '22

Hello! Periodically we get "UNCAUGHT EXCEPTION#012Traceback" errors on swift-proxy, log attached to this email. After that the swift-proxy process crashes, clients get 502 errors. Could you please help with this? Swift version - yoga 2.29.1. Thank you. Regards.

1 1

[CloudKitty] use of Monasca
by Rafael Weingärtner 24 Nov '22

24 Nov '22

Hello guys, As discussed in the PTG [1], in October, we wanted to check with the community if there are people using CloudKitty with Monasca. This discussion was brought up during the PTG that Kolla-ansible is deprecating support to Monasca, and we wanted to check if others are using CloudKitty with Monasca. This integration is not being actively tested and maintained; therefore, we are considering the issue of a deprecation notice and further removal of the integration. What do you guys think? Are there people using CloudKitty with Monasca? [1] https://etherpad.opendev.org/p/oct2022-ptg-cloudkitty -- Rafael Weingärtner

1 1

“Can not allocate kernel buffer” when I use officail ubuntu image to create instance
by 韩光宇 23 Nov '22

23 Nov '22

Hi, all I download ubuntu focal-server-cloudimg-amd64.img from officail website[1]. And when I use it to creae instance, I can access the grub interface in horizon vnc. But if I choose "Ubuntu", I get: error: cannot allocate kernel buffer. error: you need to load the kernel first. Can I get some advice on how I should use it properly to create instances [1] https://cloud-images.ubuntu.com/focal/20221121/focal-server-cloudimg-amd64.…

1 1

[manila] Weekly meeting cancelled (Nov 24th 2022)
by Carlos Silva 23 Nov '22

23 Nov '22

Hello, Zorillas! Since there are some holidays in the US in the next few days, and some of our usual crowd will be offline, we are cancelling tomorrow's weekly meeting. The next Manila weekly meeting will be on December 1st. If you would like to chat about something urgent, please ping me on IRC. Sorry for the late notice. Thanks, carloss

1 0

[largescale-sig] Next meeting: Nov 23, 15utc
by Thierry Carrez 23 Nov '22

23 Nov '22

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

1 1

[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

Bug report from 11-16-2022 to 11-23-2022
by Sofia Enriquez 23 Nov '22

23 Nov '22

This is a bug report from 11-16-2022 to 11-23-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1997088 "Implement TODOs from change 94dfad99c2b." Assigned to Sofia Enriquez. 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

(Openstack-nova or neutron error) in Canonical Openstack
by Adivya Singh 23 Nov '22

23 Nov '22

hi, What could be the reason for this error? Any guesses Went to status ERROR due to "Message: Build of instance 29ff9e37-e619-4406-adb8-200eec3aa1c7 aborted: Failed to allocate the network(s), not rescheduling., Code: 500" I am planning to restart libvirt services on compute node, may be Start the Nova services in compute node, neutron ovs services in compute node Maybe change the parameter in the plugin for the neutron time parameter from 10 sec to 60 sec. Any guesses, what more can I do more?

4 3

[neutron][tap-as-a-service][release] Deletion old branches of taas
by Lajos Katona 22 Nov '22

22 Nov '22

Hi, Tap-as-a-service is a Neutron stadium project, and recently we decided it is time to EOL old branches of it as we did for other stadium projects (see for example [1]). The branches which we would like to delete are: - stable/ocata - stable/pike - stable/queens - stable/rocky - stable/stein If you would like to keep these branches please answer back to this mail. As tap-as-a-service was moved in and out of stadium projects, it has no yaml files in releases repo before zed, I would like to ask the help of the release team to delete and tag these branches. I list here the hashes to have everything here as reference: - stable/ocata: 23536669c161be786185ecb6fb8831458476f74b - stable/pike: 0c974fe28b31453ab02eb597b4242f059b274c95 - stable/queens: 33f3e6d0432241e2846288291f1a8229c95b1425 - stable/rocky: 0eae0a540d16192c583232b8dfc574f233e60199 - stable/stein: 951390c12655f296460a3210c221da47f9cb5a3b [1]: https://review.opendev.org/c/openstack/releases/+/846188 Best wishes Lajos (lajoskatona)

1 0

ISO file as user-data
by Srinivasan T 22 Nov '22

22 Nov '22

Hi Team, I'm trying to understand if it is possible to pass an ISO file as user-data or config-drive while creating an instance. Ex., *openstack server create --image <my image> --flavor <my flavor> --user-data /path/to/myiso.iso --network <my network> --config-drive true <instance name>* Basically we need to mount & get the files in our ISO that is passed to the VM instance for initial configuration. When trying the above OpenStack CLI command with ISO as user-data, below error is thrown (where as plain text file works), *'utf8' codec can't decode byte 0xbb in position 32848: invalid start byte* Regards, Srini

1 0

[keystone] Weekly Meeting Cancelled
by Dave Wilde 22 Nov '22

22 Nov '22

Sorry for the late notice, but the weekly meeting is cancelled this week as I’m AFK for the U.S. holiday. Please let me know if you need anything and have a wonderful holiday if you’re celebrating. /Dave Sent from my iPad

1 0

Problem in freezer deploymentnt
by K Santhosh 22 Nov '22

22 Nov '22

Hai , I am Santhosh, I do facing a problem with freezer deploymentnt After the deployment of freezer . The freezer_scheduler container is continuously restarting in kolla openstack can you help me out with this freezer_scheduler container

2 1

Strange situation regarding Availability Zones
by Lennart van Gijtenbeek | Routz 22 Nov '22

22 Nov '22

3 3

[neutron] CI meeting 22.11 cancelled
by Slawek Kaplonski 22 Nov '22

22 Nov '22

Hi, I don't feel well today and I will not be able to chair neutron CI meeting. See You on the meeting next week. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Re: [neutron-dynamic-routing] BGPspeaker LOOP
by Roberto Bartzen Acosta 22 Nov '22

22 Nov '22

Thanks Sean. I believe that the os-ken driver is not coded to honor this premise because the below function can learn new paths from peer update messages. https://opendev.org/openstack/os-ken/src/branch/master/os_ken/services/prot… Em qua., 16 de nov. de 2022 às 09:14, Sean Mooney <smooney(a)redhat.com> escreveu: > On Wed, 2022-11-16 at 09:05 -0300, Roberto Bartzen Acosta wrote: > > Sorry for the mistake, I meant, the bgpspeaker should only "*advertise*!" > > and not "learn" the AS_PATHs via BGP. > yes that used to be the scope of that project to advertise only and not > learn > so i would geuss either that has change recently and they broke backward > compaitbly > or they have refactord it to use an external bgp speaker like frr and it > learns by default > > i dont really see anything here > https://github.com/openstack/neutron-dynamic-routing/commits/master > im not really familar with the internals of the project but i dont see any > code to learn routs form > > > https://github.com/openstack/neutron-dynamic-routing/blob/master/neutron_dy… > > it just has code for advertizing and withdrawing routes. > > > > > > > Em qua., 16 de nov. de 2022 às 08:57, Sean Mooney <smooney(a)redhat.com> > > escreveu: > > > > > On Wed, 2022-11-16 at 08:43 -0300, Roberto Bartzen Acosta wrote: > > > > Hey folks, > > > > > > > > Please, I have a question here, the bgpspeaker should only "learn" > and > > > not > > > > "advertise" the AS_PATHs via BGP, right? > > > > > > its been a while since i looked at it but in the past it did not > supprot > > > learning at all > > > > > > it just advertised the routes for the neutron netowrks > > > > > > > > > > > In my tests, I can see that it is learning routes from BGP neighbors. > > > This > > > > behavior can cause an AS_PATH loop because the bgpspeaker learns > back its > > > > own advertised routes, and I see a message like this in the logs: > > > > > > > > 2022-11-11 19:45:41.967 7220 ERROR bgpspeaker.peer [-] AS_PATH on > UPDATE > > > > message has loops. Ignoring this message: > > > > > > > > BGPUpdate(len=91,nlri=[],path_attributes=[BGPPathAttributeMpReachNLRI(afi=2,flags=144,length=46,next_hop='2001:db7:1::1',nlri=[IP6AddrPrefix(addr='2001:db9:1234::',length=64)],safi=1,type=14), > > > > BGPPathAttributeOrigin(flags=64,length=1,type=1,value=0), > > > > BGPPathAttributeAsPath(flags=80,length=10,type=2,value=[[65001, > > > > > > > > 65000]])],total_path_attribute_len=68,type=2,withdrawn_routes=[],withdrawn_routes_len=0) > > > > > > > > This can be fixed by suppressing the neighbor route advertisement > (using > > > > route-map export), but have I misunderstood how > neutron-dymanic-routing > > > > works or do we have a possible bug here? > > > > > > > > Regards > > > > > > > > > > > > > > -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

2 3

[barbican][release] Transition Queens, Rocky & Stein to EOL
by Grzegorz Grasza 22 Nov '22

22 Nov '22

Hi all, The barbican team no longer plans to maintain branches older than Train. The patch to mark these branches as EOL is in review [1], but according to the steps to achieve this [2], we need first to announce it. Please send your feedback by leaving a comment on the patch. I will unblock it next week. / Greg [1] https://review.opendev.org/c/openstack/releases/+/862515 [2] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l…

1 0

[all][openstack-dev][ptls] Migrating devstack jobs to Jammy (Ubuntu LTS 22.04)
by Dmitriy Rabotyagov 21 Nov '22

21 Nov '22

Hi everyone, According to a 2023.1 community-wide goal [1], base-jobs including but not limited to devstack-minimal, devstack, devstack-ipv6, devstack-multinode, tox, will be switched from Ubuntu Focal (20.04) to Jammy (22.04). That will also bring python 3.10 as a default python interpreter for these jobs. Migration will affect most of the projects, so to make it smooth, we will split the process into the following steps: 1. Patches for switching base jobs to Jammy will be proposed and marked as WIP (Work In Progress). It will allow projects to check if their code is compatible without breaking gates. These patches are ready and you can check them out here [2] 2. All projects should ensure that the code is compatible and merge changes if required. To properly track and test these changes you should: * Create a DNM patch that will contain in its commit message: "Depends-On: https://review.opendev.org/c/openstack/tempest/+/861110" to consume new nodesets. You can check the sample patch for Nova below [3] * In case of any job failure due to Ubuntu 22.04 or Python 3.10, land requires changes to support this new distribution * If you have overridden nodeset for your project jobs, ensure that you also have jobs against Ubuntu 22.04 and these jobs set to voting. * Set topic to all related changes to "migrate-to-jammy" * Please use etherpad [4] for tracking patches, bug reports, current status, or any other activity related to this topic 3. On R-18, which is the first 2023.1 milestone that will happen on the 18th of November 2022, base-jobs patches mentioned in step 1 will be merged. Please ensure you have verified compatibility for your projects and landed the required changes if any were needed before this date otherwise, they might fail. Please, do not hesitate to raise any questions or concerns. [1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubunt… [2] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/861116 https://review.opendev.org/c/openstack/tempest/+/861110 https://review.opendev.org/c/openstack/devstack/+/860795 [3] https://review.opendev.org/c/openstack/nova/+/861111 [4] https://etherpad.opendev.org/p/migrate-to-jammy

2 2

[neutron] metadata IPv6
by Roberto Bartzen Acosta 21 Nov '22

21 Nov '22

Hey folks, Can you confirm if the metadata should work in an ipv6-only environment? As I understand from this discussion on LP:1460177 <https://bugs.launchpad.net/neutron/+bug/1460177> and the fork of the discussion in many opendev reviews #315604 <https://review.opendev.org/c/openstack/neutron-specs/+/315604>, #738205 <https://review.opendev.org/c/openstack/neutron-lib/+/738205> #745705 <https://review.opendev.org/c/openstack/neutron/+/745705>, ..., it seems like it should work. However, this comment in the openstack doc [1] has me questioning if it really works. *"There are no provisions for an IPv6-based metadata service similar to what is provided for IPv4. In the case of dual-stacked guests though it is always possible to use the IPv4 metadata service instead. IPv6-only guests will have to use another method for metadata injection such as using a configuration drive, which is described in the Nova documentation on config-drive <https://docs.openstack.org/nova/latest/user/config-drive.html>."* Is anyone using metadata in an ipv6-only Openstack setup? Regards, Roberto [1] https://docs.openstack.org/neutron/latest/admin/config-ipv6.html#configurin… -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

5 8

Unable to access Internet from an instance and accessing instance using floating-point IPs from external network
by vincent lee 21 Nov '22

21 Nov '22

Hi all, I have an OpenStack deployment using kolla-ansible <https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html> with the Yoga version. Our network setup is provided in the attachment ( *network.jpg*). The configuration file (*globals.yml)* and inventory ( *multinode*) are also attached to this email. After the deployment steps, I try to run the script *init-runonce* to create the images and the networks by modifying the external network parameters according to our network setup. I am successful in launching instances from the horizon dashboard. However, the instances were not able to connect to the Internet. I have tried attaching the floating point IPs to the instance, where the IPs are successfully allocated from the range I have specified in the* init-runonce* script. When I launched the instance and tried to ping the external network, it failed. It will be very helpful if anyone can advise me to resolve this issue. I am currently using Ubuntu 20.04.05 LTS version on the controller and compute nodes. Best regards, Vincent

2 1

In Need of Reviewer for Proposal
by Juan Pablo Suazo 21 Nov '22

21 Nov '22

Hello All, I'm in need of a reviewer to take a look at my kolla-ansible proposal, which consists of the modification of a couple of cinder tasks to support placing multiple ceph conf files in a cinder/ceph/ directory to make integrating multiple volume services easier. I have already received insight from another reviewer ( radoslaw.piliszek(a)gmail.com) and made changes to comply with conventions and fix bugs. I couldn't tend to this proposal for a while, and in that time my reviewer has stopped reviewing patches altogether so I'm unable to get the approval for merging. All Zuul tasks are currently successful and the change has been tested locally to ensure it works correctly, so the review should be pretty straight forward. Best wishes, *Juan Pablo Suazo* Cloud Developer Trainee jsuazo(a)whitestack.com

2 2

[TripleO] Intermittent gate failure - centos-9-content-provider jobs
by Ronelle Landy 21 Nov '22

21 Nov '22

Hello All, We are investigating an intermittent check/gate failure on content provider jobs related to DNS and mirror access/resolution: tripleo-ci-centos-9-content-provider <https://zuul.opendev.org/t/openstack/build/8a3afc815e8743568acf3906c92ee203> and the -zed and -wallaby versions. Details are in the related Launchpad bug: https://bugs.launchpad.net/tripleo/+bug/1997202. We will update the list as we know more. Thanks, TripleO CI Team.

1 0

[neutron] Bug deputy report (week starting on Nov-14-2022)
by Bernard Cafarelli 21 Nov '22

21 Nov '22

Hey neutrinos, last bug deputy rotation of the year started: https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy and I was deputy last week, here are the reported bugs. Overall all bugs have patches or at least assignees Critical * [neutron-lib] Stable py3x jobs failing - https://bugs.launchpad.net/neutron/+bug/1996776 Patch and backports by ralonsoh merged - https://review.opendev.org/q/I3a4a27ec4672f8ea8848d7c04651730dae6f40ff * [CI] "test_live_migration_with_trunk" failing - https://bugs.launchpad.net/neutron/+bug/1997025 Caused by recent os-vif bump, workaround suggested by ralonsoh to block this newer version - https://review.opendev.org/c/openstack/neutron/+/865026 High * With new RBAC enabled (enforce_scope and enforce_new_defaults): 'router:external' field is missing in network list response - https://bugs.launchpad.net/neutron/+bug/1996836 Assigned to slaweq, fixed with https://review.opendev.org/c/openstack/neutron/+/865032 Also a related neutron-lib patch merged https://review.opendev.org/c/openstack/neutron-lib/+/864809 * With new RBAC enabled (enforce_scope and enforce_new_defaults): some security groups aren't visible for admin user - https://bugs.launchpad.net/neutron/+bug/1997089 Also assigned to slaweq, patch in progress https://review.opendev.org/c/openstack/neutron/+/865040 * Metadata service broken after minor neutron update when OVN 21.09+ is used - https://bugs.launchpad.net/neutron/+bug/1997092 Fix by ihrachys merged, backports in progress - https://review.opendev.org/c/openstack/neutron/+/864777 Medium * Unit test failure with Python 3.11 - https://bugs.launchpad.net/neutron/+bug/1996527 Fix by haleyb merged - https://review.opendev.org/c/openstack/neutron/+/864448 * OVN metadata randomly stops working - https://bugs.launchpad.net/neutron/+bug/1996594 Happening with xena and OVS 2.16, otherwiseguy investigating (may be caused by OVS version too low for RAFT) * QoS rules policies do not work for "owners" - https://bugs.launchpad.net/neutron/+bug/1996606 Assigned to ralonsoh * [OVN] support update fixed_ips of metadata port - https://bugs.launchpad.net/neutron/+bug/1996677 Patch in progress by huanghailun - https://review.opendev.org/c/openstack/neutron/+/864715 * Add support for DHCP option 119 (domain-search) for IPv4 in ML2/OVN - https://bugs.launchpad.net/neutron/+bug/1996759 Fix by lucasagomes merged - https://review.opendev.org/c/openstack/neutron/+/864740 * [OVN] Enabling and disabling networking log objects doesn't work as expected - https://bugs.launchpad.net/neutron/+bug/1996780 Patch in progress by elvira - https://review.opendev.org/c/openstack/neutron/+/864152 * [ovn-octavia-provider] HM created at fully populated loadbalancer stuck in PENDING_CREATE - https://bugs.launchpad.net/neutron/+bug/1997094 Assigned to froyo * ML2 When OVN mech driver is enabled dhcp extension is disabled - https://bugs.launchpad.net/neutron/+bug/1997185 When OVN is enabled with another driver (linuxbridge here), DHCP extension is disabled. Fix suggested by author to mark extension as supported in OVN - https://review.opendev.org/c/openstack/neutron/+/865081 Low * Replace the Linux Bridge references with Open vSwitch in the installation manuals - https://bugs.launchpad.net/neutron/+bug/1996772 Discussed in team meeting, this part of the doc is quite outdated Patch by ralonsoh merged - https://review.opendev.org/c/openstack/neutron/+/864748 * Install and configure controller node in Neutron - https://bugs.launchpad.net/neutron/+bug/1996889 Doc fix on domain names case, patch by haleyb - https://review.opendev.org/c/openstack/neutron/+/864921 RFE * add address scope to OVN Southbound/Northbound - https://bugs.launchpad.net/neutron/+bug/1996741 Enhancement to use ovn-bgp-agent with non-SNATed tenant networks Patch in review: https://review.opendev.org/c/openstack/neutron/+/861719 Opinion * The virtual network is broken on the node after neutron-openvswitch-agent is restarted if RPC requests return an error for a while - https://bugs.launchpad.net/neutron/+bug/1996788 ralonsoh++ jumped in on that one, issue on OVS agent start when RPC fails. Not much we can do here probably, but left as opinion for potential further discussion Incomplete * [OpenStack-OVN] Poor network performance - https://bugs.launchpad.net/neutron/+bug/1996593 Reported much lower performance with security groups enabled between ML2/OVS and ML2/OVN, more details asked on deployment setup -- Bernard Cafarelli

1 0

Kolla Ansible Image add python package.
by Nguyễn Hữu Khôi 20 Nov '22

20 Nov '22

Hello guys. I read https://docs.openstack.org/kolla/latest/admin/image-building.html but I would like to know how to install python packages for all images at building time. I would be very glad if I can get some guides. Nguyen Huu Khoi

1 0

OpenStack: Can't create instances using KVM on host.
by Seyed Amir Hossein Ahmadi 19 Nov '22

19 Nov '22

I have a Dockerize installation from Devstack all-in-one. The goal for me is to connect to the host's KVM and create instances there. Nova was configured as follows for this purpose. *# /etc/nova/nova.conf# /etc/nova/nova-cpu.conf# [libvirt]# connection_uri = qemu+ssh://root@172.10.1.1/system <http://root@172.10.1.1/system>* When I try to build the instance, I get the following error. *# Build of instance cdd6f8b4-6dcf-4a43-b96a-fb6166b20235 aborted: Failed to allocate the network(s), not rescheduling.* ovs-vsctl commands cause the error. What is the problem? Does this need to be done differently?

1 0

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

18 Nov '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * * We had this week's meeting on Nov 16. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html * Next week (Nov 23) TC weekly meeting is canceled[1]. 2. What we completed this week: ========================= * Defined process for the TC chair nomination & election[2] * Updated the 2023.1 cycle testing runtime[3] * Documented the upgrade patch testing in PTI[4] * Added zookeeper role under OpenStack-Ansible governance[5] * TC stopped using Storybooard. We were not using it for many cycles but TC officially decided [6] to clear all story and close the governance repo in Storyboard[7]. We will not use any other task tracking tool, etherpad or tracking things in meetings are working fine. 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[8]. Open Reviews ----------------- * Four open reviews for ongoing activities[9]. OpenInfra Board + OpenStack Syncup Call -------------------------------------------------- We continued the syncup call with Board members on Nov 16[10]. We discussed two topic in this call 1. "Less Diversity" and 2. i18 SIG. Most of the discussion was around first topic. There were multiple ideads were shared and discussed including: - Spreading and encouraging the contribution to wider audiance including large deployement, users, company manager. - Making contribution process more easy for part time contributorts. operators etc by helping them in testing requirement, process, half-baked patches to merge. - Reachout out to platinum members company and company executives to know the reason for not contributing in community and explain/encourage them to contribution. There was no concrete action or step to improve the Diversity but we all togehther need to put effort in all direction to improve it slowly. i18 SIG proposal by Brian about Weblate funding which is ~1500 Euro/year and this sounds reasonable to do from foundation but Brian need to write the foaml proposal to foundation before Board meeting on Dec 6th so that it can be discussed there is needed. Thanks Brian for working and following up on this. The next syncup call will be on Feb 2022-02-08 at 20:00 UTC. If anyone is interested, feel free to join it. Renovate translation SIG i18 ---------------------------------- * We discussed it in Board syncup call and Brian will take it forward to put the Weblate funding formal proposal to foundation. TC Video meeting discussion ---------------------------------- Based on the feedback JayF has abandoned the resolution patch[11]. Thanks JayF for proposal and discussion. Project updates ------------------- * Add Skyline repository for OpenStack-Ansible[12] * Add the cinder-infinidat charm to Openstack charms[13] * Add the infinidat-tools subordinate charm to OpenStack charms[14] * Add the manila-infinidat charm to Openstack charms[15] 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:00 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. See you all next week in PTG! [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://governance.openstack.org/tc/reference/tc-chair-elections.html [3] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03122… [4] https://governance.openstack.org/tc/reference/project-testing-interface.htm… [5] https://review.opendev.org/c/openstack/governance/+/863161 [6] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html#… [7] https://review.opendev.org/c/openstack/project-config/+/864771 [8] https://etherpad.opendev.org/p/tc-2023.1-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://etherpad.opendev.org/p/2022-11-board-openstack-sync [11] https://review.opendev.org/c/openstack/governance/+/863685 [12] https://review.opendev.org/c/openstack/governance/+/863166 [13] https://review.opendev.org/c/openstack/governance/+/863958 [14] https://review.opendev.org/c/openstack/governance/+/864067 [15] https://review.opendev.org/c/openstack/governance/+/864068 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Call for Participation: Sovereign Cloud DevRoom at FOSDEM 2023
by Felix Kronlage-Dammers 18 Nov '22

18 Nov '22

# FOSDEM 2023 In Person – Sovereign Cloud DevRoom Call for Participation! The twenty-third edition of FOSDEM takes place Saturday 4th and Sunday 5th February 2023 in Brussels, Belgium. For the first time there will be a DevRoom that focuses on the subject of Sovereign Cloud and its practical aspect for digital sovereignty. ## Key dates tl;dr: - Conference dates 4-5 February, 2023 In person - Sovereign Cloud DevRoom date: Saturday 4th February - Submission deadline: Friday December 9th, 2022 - 23:59 UTC. - Announcement of selected talks: Thursday 15th December - You must be available in person to present your talk ## About the Sovereign Cloud DevRoom ### Overview The Sovereign Cloud DevRoom is for discussing topics and issues of user privacy and sovereignty and the intersection with the needs of infrastructure providers in the cloud computing era. A few topic examples to illustrate (a longer list is below): - Can all operations be open, or may there be a need for a two+ tier openess (country specific laws or company secrets)? - How can privacy relevant data be anonymized instead of being deleted, without losing the useful information? - Open Operations is more than just sharing runbooks, how is knowledge shared and fostered best across organizations? - Navigating our personal data lakes -- we're going to need better tools that are easier to use by more people for managing and curating encrypted data lakes - The role of machine learning in conducting data science on anonymized information - Countering the risks of integrated platforms These are just a few example suggestions, we welcome proposals on any aspects around these topic. More topic ideas and details on how to submit proposals is below. ### Discussing the Sovereign Cloud The recent EU focus on digital sovereignity has brought fresh attention and innovation to a problem area many of us have been interested in and working on for a long time. This DevRoom focuses on a practical aspect of digital sovereignty: how it affects user-oriented and potentially privacy-containing infrastructure in the cloud computing era. This aspect is the _sovereign cloud_, the intersection of digital sovereignty and a modern cloud-centric way to create and sustain infrastructure, operations, and development to address the needs of users (which may be other cloud services or actual, real people.) With the rise of the Confidential Computing Consortium (https://confidentialcomputing.io/) some people feel we are beginning to achieve "sovereign enough" where it comes to the balance of the needs of the individual and the needs of tech companies et al. But there are just as many other voices calling attention to potential problems and unfulfillable needs of staying on that path. Looking at the entire landscape of the problem, it's clear that Confidential Computing also aligns with usage on a sovereign cloud. It is a tool to ensure the least amount of provider trust, and it is still a good idea until we've moved new processor architectures into the mainstream that are less impacted by predictive execution vulnerabilities. So while it is not perfect, making it harder for an attacker is always a good idea where feasible. In looking for other paths to fill more needs, we naturally come to the intersection of Free/Open where interests from different backgrounds pursuing different goals suddenly find themselves working together in a common direction. Two of those groups are part of the organizing committee for this devroom: As a way of addressing the holistic needs and supporting a truly balanced digital sovereignty, organizations such as the overeign Cloud Stack (https://scs.community/) have come together to provide a complete technology solution, standards as well as reference implementations, that can be proven and recognized by everyone as a truly sovereign cloud. In this area where the requirements of a sovereign cloud are being met is another intersection from the ecosytem of Free and Open Source software development. The idea of Open Operations is essential to projects such as Operate First that provide a developer-friendly post-CI/CD platform for running, testing, and proving Open Source services. Longer list of topic ideas - this is not an exclusive list, feel free to submit further ideas: - Can all operations be open, or may there be a need for a two+ tier openess (country specific laws or company secrets)? - How can privacy relevant data be anonymized instead of being deleted, without losing the useful information? - Discussion: How open can software be called, if it relies on closed operations and closed infrastructure? - Do we need to refine the definition of upstream in the idea of Open Operations? - Is hybrid accelerating Open Operations or can it be a slow-downer/ separator? Or the solution to possible privacy issues? - Interoperability, transparency, and independence are the go to goals, what can be accepted on our way until we are there? - Open Operations is more than just sharing runbooks, how is knowledge shared and fostered best across organizations? - Share experiences and stories on creating environments of psychological safety so that failures indeed make us experts - Building communities of practice across organizations - Navigating our personal data lakes -- we're going to need better tools that are easier to use by more people for managing and curating encrypted data lakes - The role of machine learning in conducting data science on anonymized information - Countering the risks of integrated platforms Again, these are just suggestions. We welcome proposals on any aspects around these topic. Format and lengths of submissions: - Long (40 minutes, including Q&A) - Short (20 minutes, including Q&A) - Lightning (5 minutes, no Q&A) Aside from Presentation also Meetings/Discussions are welcome for topics where a BoF-style (Birds of Feather) session is appropriate. HOW TO SUBMIT A TALK - Head to the FOSDEM 2023 Pentabarf <https://penta.fosdem.org/submission/FOSDEM23> website. - If you already have a Pentabarf account, please don’t create a new one. - If you forgot your password, reset it. - Otherwise, follow the instructions to create an account. - Once logged in, select “New Event” and click on “Show All” in the top right corner to display the full form. Your submission must include the following information: - First and last name / Nickname (optional)/ Image - Email address - Mobile phone number (this is a very hard requirement as there will be no other reliable form of emergency communication on the day) - Title and subtitle of your talk (please be descriptive, as titles will be listed with ~500 from other projects) - Track: Select “Sovereign Cloud DevRoom” as the track - Event type: - Lightning Talk OR - Meeting or Discussion OR - Presentation - Persons: Add yourself as the speaker with your bio - Description: Abstract (required)/ Full Description (optional) - Links to related websites / blogs etc. - Beyond giving us the above, let us know if there’s anything else you’d like to share as part of your submission – Twitter handle, GitHub activity history – whatever works for you. We especially welcome videos of you speaking elsewhere, or even just a list of talks you have done previously. First time speakers are, of course, welcome! - For issues with Pentabarf, please contact cloud-devroom-manager(a)fosdem.org. Feel free to send a notification of your submission to that email. If you need to get in touch with the organisers or program committee of the Sovereign Cloud DevRoom, email us at cloud-devroom-manager(a)fosdem.org FOSDEM website <https://fosdem.org/2023/> / FOSDEM code of conduct <https://fosdem.org/2023/practical/conduct/>

1 0

[all][tc] Canceling next week TC meetings
by Ghanshyam Mann 18 Nov '22

18 Nov '22

Hello Everyone, As many of us will not be available due to thanks giving, we are cancelling the next week's (Nov 23) TC meeting. -gmann

1 0

[Glance] No weekly meeting next week
by Pranali Deore 18 Nov '22

18 Nov '22

Hello, I will be on PTO from Tuesday, 22nd Nov to Friday, 25th Nov, so I won't be available for the weekly meeting next week. If anyone has anything important to be discussed feel free to add in the meeting agenda etherpad[1] and it would be nice if someone from the glance team volunteers to chair the meeting based on the agenda. [1]: https://etherpad.opendev.org/p/glance-team-meeting-agenda#L70 Thanks, Pranali

1 0

[release] Release countdown for week R-17, Nov 21 - 25
by Herve Beraud 18 Nov '22

18 Nov '22

Development Focus ----------------- We are now past the Antelope-1 milestone. Teams should now be focused on feature development and completion of release cycle goals [0]. [0] https://governance.openstack.org/tc/goals/selected/ General Information ------------------- Our next milestone in this development cycle will be Antelope-2, on January 5, 2023. This milestone is when we freeze the list of deliverables that will be included in the 2023.1 final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/antelope directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- Antelope-2 Milestone: January 5, 2023 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

Host node monitoring
by KK CHN 18 Nov '22

18 Nov '22

List, A general question: Can nagios core be used for HCI nodes and other nodes which are installed with Type1 hypervisors ? ( Eg: ESXi hypervisor doesn't have an OS to install the nagios on to it.. as it a bare metal hypervisor . ) How do people monitor these base machines with configurable alerts/notifications to email, and mobile phones of people who manage ?' Krish

2 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 18 Nov '22

18 Nov '22

Hello Neutrinos: Due to the lack of agenda, today's drivers meeting is cancelled. Have a nice weekend!

1 0

[kolla-ansible][Yoga] Install with self-signed certificate
by wodel youchi 18 Nov '22

18 Nov '22

Hi, To deploy Openstack with a self-signed certificate, the documentation says to generate the certificates using kolla-ansible certificates, to configure the support of TLS in globals.yml and to deploy. I am facing a problem, my old certificate has expired, I want to use a self-signed certificate. I backported my servers to an older date, then generated a self-signed certificate using kolla, but the deploy/reconfigure won't work, they say : self._sslobj.do_handshake()\n File \"/usr/lib64/python3.6/ssl.py\", line 648, in do_handshakeself._sslobj.do_handshake()\nssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED certificate verify failed PS : in my globals.yml i have : *kolla_verify_tls_backend: "yes"* Regards.

2 11

[tc][policy] RBAC (policy-popup team) meeting time
by Ghanshyam Mann 17 Nov '22

17 Nov '22

Hello Everyone, I am starting the RBAC (policy-pop up) bi-weekly meeting on alternate Tuesday (starting Nov 22) at 17:00 UTC on #openstack-meeting IRC channel. Details: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… ICS File: https://meetings.opendev.org/#Secure_Default_Policies_Popup-Team_Meeting -gmann

1 0

[all][tc] 2023.1 cycle updated testing runtime (recommended Upgrade Path testing)
by Ghanshyam Mann 17 Nov '22

17 Nov '22

Hello Everyone, You might have seen the TC discussion[1] in PTG for the best possible testing for smooth upgrade. When there is a distro version change in testing runtime, then we need to test both the old and the new distro versions (for the cycle when we are bumping the distro version). We have documented the recommended upgrade path testing in PTI also[2], refer to that for details. In 2023.1 cycle, we are moving from Ubuntu Focal (20.04) to Jammy (22.04)[3] and as per the upgrade path testing we should test the Focal (20.04) also. TC has merged these updates in the 2023.1 cycle testing runtime document[4] which are basically: 1. Testing Ubuntu Focal (20.04) in a single job (one job is enough to test the old version) in project gate. For example, neutron did[5]. This can be a new job or one of the existing jobs. 2. Python minimum version to test is python 3.8 (default version in Ubuntu Focal). We will be testing python 3.8 and python 3.10 unit/functional jobs. Unit test job template change has been merged[6] which will automatically start running py38 unit test job and functional jobs can be modified (if needed) by project side. [1] https://etherpad.opendev.org/p/tc-2023-1-ptg#L422 [2] https://governance.openstack.org/tc/reference/project-testing-interface.htm… [3] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubunt… [4] https://review.opendev.org/c/openstack/governance/+/860599 [5] https://review.opendev.org/c/openstack/neutron/+/862492 [6] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/864464 -gmann

1 0

[openstack-ansible] Designate: rndc config file not generated
by Taltavull Jean-François 17 Nov '22

17 Nov '22

Hello, I'm deploying Designate on OpenStack Wallaby/Ubuntu 20.04 with DNS servers located outside the OpenStack platform. After running 'os-designate-install.yml' playbook, 'bind9-utils' package is correctly installed but I can't find rndc config file anywhere inside the lxc container. This prevents rndc from running well and communicating with the DNS servers. Any idea ? Regards, Jean-Francois

3 4

[Kolla][kolla-ansible][HAProxy] Splitting the load balancer into internal and external?
by Mariusz Karpiarz 17 Nov '22

17 Nov '22

All, Was the idea of moving internal components deployed by kolla-ansible (like the MySQL database) to a load balancer separate to the one used by user-facing APIs discussed anywhere? This feels like a good option to have for security but, as far as I'm aware, it's not supported by kolla-ansible. It should be possible to use existing Kolla HAProxy images, but mount config files from subdirectories of `/etc/kolla/haproxy/` for each container. I suspect the main hurtle here would be rewriting the user interface of kolla-ansible to account for the split whilst maintaining backward compatibility... Mariusz Karpiarz

3 4

Re:
by K Santhosh 17 Nov '22

17 Nov '22

can any one help me out with this freezer_scheduler container On Wed, Nov 16, 2022 at 6:00 PM K Santhosh <sandcruz666(a)gmail.com> wrote: > /var/log/kolla/freezer_scheduler.log > and > logs from container > > <https://mail.google.com/mail/u/0?ui=2&ik=849caec82f&attid=0.1&permmsgid=msg…> > > On Tue, Nov 15, 2022 at 4:18 PM Michal Arbet <michal.arbet(a)ultimum.io> > wrote: > >> What about logs from container ? >> What about log in /var/log/kolla..... >> >> >> Michal Arbet >> Openstack Engineer >> >> Ultimum Technologies a.s. >> Na Poříčí 1047/26, 11000 Praha 1 >> Czech Republic >> >> +420 604 228 897 >> michal.arbet(a)ultimum.io >> *https://ultimum.io <https://ultimum.io/>* >> >> LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | >> Twitter <https://twitter.com/ultimumtech> | Facebook >> <https://www.facebook.com/ultimumtechnologies/timeline> >> >> >> út 15. 11. 2022 v 6:18 odesílatel K Santhosh <sandcruz666(a)gmail.com> >> napsal: >> >>> Hai , >>> I am Santhosh, >>> I do facing a problem with freezer deploymentnt >>> After the deployment of freezer . The freezer_scheduler >>> container is continuously restarting in kolla openstack >>> can you help me out with this freezer_scheduler container >>> >>

1 0

[kolla-ansible]Reset Configuration
by Franck VEDEL 16 Nov '22

16 Nov '22

Hello, yesterday I sent a desperate message about the functioning of my Openstack (kolla-ansible, yoga, centos8Stream). The situation is incomprehensible. For some accounts in some projects, everything works (creation of networks, subnets, dhcp configuration, instances, everything works). For other accounts, everything works except having an IP address per dhcp on a subnet. The servers have restarted following a power outage. I managed to put everything back together except those DHCP issues. As I can start from an empty configuration, how to reset everything ... for example with a command: kolla-ansible -i multinode ____________ Or how to fix my configuration. It seems very complicated to me. I would like some opinions if possible. Thanks in advance Franck

3 10

[CloudKitty][os-api-ref][openstack-dev] v1 API docs
by Mariusz Karpiarz 16 Nov '22

16 Nov '22

All, CloudKitty docs for v1 APIs (https://docs.openstack.org/cloudkitty/latest/api-reference/v1/v1.html) appear to be generated from the source code instead of using `os-api-ref` (https://opendev.org/openstack/os-api-ref) like in case of v2 docs. I want to move both v1 and v2 API docs to a separate `api-ref/source` directory in the root of the repository, where we will only be using "os_api_ref" and "openstackdocstheme" Sphinx extensions, so we need to decide what to do with v1 docs. I started rewriting v1 docs to the format supported by `os-api-ref` but they don't quite translate well to the new format, mainly because of different ways results are presented (Python objects vs JSONs). How much do we care about proper v1 API docs and would it be worth for someone (likely me) to write them again from scratch? There is also the option for carrying over the old extensions (they are all listed here: https://opendev.org/openstack/cloudkitty/src/branch/stable/zed/doc/source/c…) but I'm not sure all of them are still supported by the system building https://docs.openstack.org/api/ and this is a good opportunity to clean this list up. :) Please let me know if you have any ideas. Mariusz

2 1

[puppet] Configure openid with Keycloak IdP in Keystone
by Fernandez Rodriguez Daniel 16 Nov '22

16 Nov '22

Hello, this is a bit of a long shot but maybe some of you succesfully configured Openstack to use Keycloak as an Identity Provider so we can use Single Sign-On on Horizon. To install and configure OpenStack Keystone I am using 'stable/xena' version of the https://github.com/openstack/puppet-keystone . Likewise for Horizon. So far so good. I would like to enable openid in Keystone so I can have Single Sign-On via Horizon. I am pretty much following the official docs: https://docs.openstack.org/keystone/latest/admin/federation/configure_feder… with the help of the puppet module. To do it I included the class: include ::keystone::federation::openidc And configured some hiera variables: keystone::federation::openidc::keystone_url: "https://openstackdev.loadbalancer:5000" keystone::federation::openidc::methods: 'password,token,oauth1,mapped,openid' keystone::federation::openidc::idp_name: 'keycloak' keystone::federation::openidc::openidc_provider_metadata_url: 'https://keycloak_server/auth/realms/BBP/.well-known/openid-configuration' keystone::federation::openidc::openidc_client_id: 'a_keycloak_client' keystone::federation::openidc::openidc_client_secret: <redacted> keystone::federation::openidc::openidc_crypto_passphrase: <redacted> keystone::federation::openidc::remote_id_attribute: 'HTTP_OIDC_ISS' And this is the resulting relevant configuration in /etc/httpd/conf.d/10-keystone_wsgi.conf [...] OIDCClaimPrefix "OIDC-" OIDCResponseType "id_token" OIDCScope "openid email profile" OIDCProviderMetadataURL "https://keycloak_server/auth/realms/BBP/.well-known/openid-configuration" OIDCClientID "a_keycloak_client" OIDCClientSecret <redacted> OIDCCryptoPassphrase <redacted> # The following directives are necessary to support websso from Horizon # (Per https://docs.openstack.org/keystone/pike/advanced-topics/federation/websso.…) OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/identity_provi…" OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid" <LocationMatch "/v3/auth/OS-FEDERATION/websso/openid"> AuthType "openid-connect" Require valid-user </LocationMatch> <LocationMatch "/v3/auth/OS-FEDERATION/identity_providers/keycloak/protocols/openid/websso"> AuthType "openid-connect" Require valid-user </LocationMatch> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ But unfortunately this does not work. First of all, the OIDCRedirectURI the module set points to a valid URL with content. So I manually changed them by: OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/identity_provi…" OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid/…" After changing that now I get redirected to the Keycloak login page and I am able to enter my username and pass, after the login is done I get redirected to: https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid?…<https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid?…>openstackdev.loadbalancer<https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid?…>/dashboard/auth/websso/ and it shows the following error: error code 404 message "Could not find Identity Provider: https://keycloak_server/auth/realms/BBP<https://bbpauth.epfl.ch/auth/realms/BBP>." title "Not Found" And in: /var/log/keystone/keystone.log {"message": "Could not find Identity Provider: https://keycloak_server/auth/realms/BBP.", "asctime": "2022-11-16 16:24:56", "name": "keystone.server.flask.application", "msg": "Could not find Identity Provider: https://keycloak_server/auth/realms/BBP.", "args": [], "levelname": "WARNING", "levelno": 30, "pathname": "/usr/lib/python3.6/site-packages/keystone/server/flask/application.py", "filename": "application.py", "module": "application", "lineno": 87, "funcname": "_handle_keystone_exception", "created": 1668612296.6284614, "msecs": 628.4613609313965, "relative_created": 32117.148637771606, "thread": 140579135473408, "thread_name": "Dummy-1", "process_name": "MainProcess", "process": 3051629, "traceback": null, "hostname": "bbpcb030.bbp.epfl.ch", "error_summary": "keystone.exception.IdentityProviderNotFound: Could not find Identity Provider: https://keycloak_server/auth/realms/BBP.", "context": {"user_name": null, "project_name": null, "domain_name": null, "user_domain_name": null, "project_domain_name": null, "user": null, "tenant": null, "system_scope": null, "project": null, "domain": null, "user_domain": null, "project_domain": null, "is_admin": false, "read_only": false, "show_deleted": false, "auth_token": null, "request_id": "req-5187f72d-cb4b-470f-9635-6c05565707eb", "global_request_id": null, "resource_uuid": null, "roles": [], "user_identity": "- - - - -", "is_admin_project": true}, "extra": {"project": null, "version": "unknown"}} And this is how I configured the identity provider, mapping and federation protocol. # openstack identity provider show keycloak +-------------------+-----------------------------------------+ | Field | Value | +-------------------+-----------------------------------------+ | authorization_ttl | None | | description | None | | domain_id | 96a75a2b29b5411497a9971c14a2167c | | enabled | True | | id | keycloak | | remote_ids | https://keycloak_server/auth/realms/BBP | +-------------------+-----------------------------------------+ # openstack mapping show openid_mapping +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+ | id | openid_mapping | | rules | [{'local': [{'user': {'name': '{0}'}, 'group': {'domain': {'name': 'Default'}, 'name': 'federated_users'}}], 'remote': [{'type': 'OIDC-preferred_username'}]}] | +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+ # openstack federation protocol show --identity-provider keycloak openid +---------+----------------+ | Field | Value | +---------+----------------+ | id | openid | | mapping | openid_mapping | +---------+----------------+ Can someone please give me a hand with this? Thank you very much, Daniel.

1 0

[kolla-ansible][Yoga] Deployment stuck
by wodel youchi 16 Nov '22

16 Nov '22

Hi, I am trying to deploy a new platform using kolla-ansible Yoga and I am trying to upgrade another platform from Xena to yoga. On both platforms the prechecks went well, but when I start the process of deployment for the first and upgrade for the second, the process gets stuck. I tried to tail -f /var/log/kolla/*/*.log but I can't get hold of the cause. In the first platform, some services get deployed, and at some point the script gets stuck, several times in the modprobe phase. In the second platform, the upgrade gets stuck on : Escalation succeeded [204/1859] <20.3.0.28> (0, b'\n{"path": "/etc/kolla/cron", "changed": false, "diff": {"before": {"path": "/etc/kolla/cro n"}, "after": {"path": "/etc/kolla/cron"}}, "uid": 0, "gid": 0, "owner": "root", "group": "root", "mode": "07 70", "state": "directory", "secontext": "unconfined_u:object_r:etc_t:s0", "size": 70, "invocation": {"module_ args": {"path": "/etc/kolla/cron", "owner": "root", "group": "root", "mode": "0770", "recurse": false, "force ": false, "follow": true, "modification_time_format": "%Y%m%d%H%M.%S", "access_time_format": "%Y%m%d%H%M.%S", "unsafe_writes": false, "state": "directory", "_original_basename": null, "_diff_peek": null, "src": null, " modification_time": null, "access_time": null, "seuser": null, "serole": null, "selevel": null, "setype": nul l, "attributes": null}}}\n', b'') ok: [20.3.0.28] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True , 'image': '20.3.0.34:4000/openstack.kolla/centos-source-cron:yoga', 'environment': {'DUMMY_ENVIRONMENT': 'ko lla_useless_env', 'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_f iles/:ro', '/etc/localtime:/etc/localtime:ro', '', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) => { "ansible_loop_var": "item", "changed": false, "diff": { "after": { "path": "/etc/kolla/cron" }, "before": { "path": "/etc/kolla/cron" } }, "gid": 0, "group": "root", How to start debugging the situation. Regards.

1 5

[neutron-dynamic-routing] BGPspeaker LOOP
by Roberto Bartzen Acosta 16 Nov '22

16 Nov '22

Hey folks, Please, I have a question here, the bgpspeaker should only "learn" and not "advertise" the AS_PATHs via BGP, right? In my tests, I can see that it is learning routes from BGP neighbors. This behavior can cause an AS_PATH loop because the bgpspeaker learns back its own advertised routes, and I see a message like this in the logs: 2022-11-11 19:45:41.967 7220 ERROR bgpspeaker.peer [-] AS_PATH on UPDATE message has loops. Ignoring this message: BGPUpdate(len=91,nlri=[],path_attributes=[BGPPathAttributeMpReachNLRI(afi=2,flags=144,length=46,next_hop='2001:db7:1::1',nlri=[IP6AddrPrefix(addr='2001:db9:1234::',length=64)],safi=1,type=14), BGPPathAttributeOrigin(flags=64,length=1,type=1,value=0), BGPPathAttributeAsPath(flags=80,length=10,type=2,value=[[65001, 65000]])],total_path_attribute_len=68,type=2,withdrawn_routes=[],withdrawn_routes_len=0) This can be fixed by suppressing the neighbor route advertisement (using route-map export), but have I misunderstood how neutron-dymanic-routing works or do we have a possible bug here? Regards -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

2 2

[cinder] Bug report from 11-08-2022 to 11-16-2022
by Sofia Enriquez 16 Nov '22

16 Nov '22

This is a bug report from 11-08-2022 to 11-16-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinderlib/+bug/1996738 "Cinderlib Gate broken in Zed." Unassigned. Invalid - https://bugs.launchpad.net/cinder/+bug/1990257 "[OpenStack Yoga] Creating a VM fails when stopping only one rabbitmq." Moved to Nova. 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

Issue installing OpenStack in CentOS VMs - cannot launch instances
by André Ferreira 16 Nov '22

16 Nov '22

Hello, I'm trying to setup an openstack cluster by following the instructions on https://docs.openstack.org/install-guide/openstack-services.html#minimal-de… I'm using two CentOS8 VMs: - VM1: controller node - VM2: compute node After installing all the minimum services, I've tried to create a server instance but it's failing. >From the logs, looks like that nova is not able to find a compute node to launch the instance: 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager [req-c1aa668e-73db-4799-baa4-d782ec5986e9 e6529a38880d4efcb55308277aeabb88 6a857bb3fb7f47849ff5a11d97968344 - default default] Failed to schedule i host was found. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 241, in inner return func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/nova/scheduler/manager.py", line 209, in select_destinations raise exception.NoValidHost(reason="") nova.exception.NoValidHost: No valid host was found. 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager Traceback (most recent call last): 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 1549, in schedule_and_build_instances 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager instance_uuids, return_alternates=True) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 910, in _schedule_instances 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager return_alternates=return_alternates) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager instance_uuids, return_objects, return_alternates) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager return cctxt.call(ctxt, 'select_destinations', **msg_args) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/client.py", line 192, in call 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager retry=self.retry, transport_options=self.transport_options) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/transport.py", line 128, in _send 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager transport_options=transport_options) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 691, in send 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager transport_options=transport_options) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 681, in _send 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager raise result 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager nova.exception_Remote.NoValidHost_Remote: No valid host was found. 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager Traceback (most recent call last): 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 241, in inner 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager return func(*args, **kwargs) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/scheduler/manager.py", line 209, in select_destinations 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager raise exception.NoValidHost(reason="") 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager nova.exception.NoValidHost: No valid host was found >From nova-scheduler: 2022-11-15 16:54:11.797 3978 INFO nova.scheduler.manager [req-c1aa668e-73db-4799-baa4-d782ec5986e9 e6529a38880d4efcb55308277aeabb88 6a857bb3fb7f47849ff5a11d97968344 - default default] Got no allocation can cient resources or a temporary occurrence as compute nodes start up. 2022-11-15 16:54:23.160 3978 DEBUG oslo_service.periodic_task [req-d477e747-537b-48b2-8913-ef84447d5a21 - - - - -] Running periodic task SchedulerManager._discover_hosts_in_cells run_periodic_tasks /usr/li 2022-11-15 16:54:23.169 3978 DEBUG oslo_concurrency.lockutils [req-4dbefd76-0b81-47d9-b6cf-382f43e3505e - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" acquired by "nova.context.set_target_cell.<loc .000s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:390 2022-11-15 16:54:23.170 3978 DEBUG oslo_concurrency.lockutils [req-4dbefd76-0b81-47d9-b6cf-382f43e3505e - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" "released" by "nova.context.set_target_cell.<l .001s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:405 2022-11-15 16:54:59.097 3977 DEBUG oslo_service.periodic_task [req-bb4ca11b-2089-414c-b8d5-6c45aa58c1bf - - - - -] Running periodic task SchedulerManager._discover_hosts_in_cells run_periodic_tasks /usr/li 2022-11-15 16:54:59.112 3977 DEBUG oslo_concurrency.lockutils [req-cf62a2b4-6721-4f98-a97d-7b51e58a34b3 - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" acquired by "nova.context.set_target_cell.<loc .000s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:390 2022-11-15 16:54:59.113 3977 DEBUG oslo_concurrency.lockutils [req-cf62a2b4-6721-4f98-a97d-7b51e58a34b3 - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" "released" by "nova.context.set_target_cell.<l .001s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:405 The problem is that the compute node is not placed on the cell. The list of hypervisors is also empty. I've searched online but I don't find a way to fix this. (admin-rc) [andrefe@controller0 ~]$ openstack compute service list +--------------------------------------+----------------+------------------------+----------+---------+-------+----------------------------+ | ID | Binary | Host | Zone | Status | State | Updated At | +--------------------------------------+----------------+------------------------+----------+---------+-------+----------------------------+ | fa781cbb-732c-43db-8c9f-4c31bd73bbd2 | nova-scheduler | controller0.os.lab.com | internal | enabled | up | 2022-11-15T15:59:40.000000 | | 106e9574-5ae3-45e2-a7c2-09ce3624a1d6 | nova-conductor | controller0.os.lab.com | internal | enabled | up | 2022-11-15T15:59:40.000000 | | 28072820-609a-4066-abc8-affea51c3600 | nova-compute | compute0.os.lab.com | nova | enabled | up | 2022-11-15T15:59:41.000000 | +--------------------------------------+----------------+------------------------+----------+---------+-------+----------------------------+ [root@controller0 ~]# /bin/sh -c "nova-manage cell_v2 list_cells" nova +-------+--------------------------------------+-------------------------------------------+--------------------------------------------------+----------+ | Name | UUID | Transport URL | Database Connection | Disabled | +-------+--------------------------------------+-------------------------------------------+--------------------------------------------------+----------+ | cell0 | 00000000-0000-0000-0000-000000000000 | none:/ | mysql+pymysql://nova:****@controller0/nova_cell0 | False | | cell1 | 79648906-0ea8-4672-8c5f-73d5998a7b73 | rabbit://openstack:****@controller0:5672/ | mysql+pymysql://nova:****@controller0/nova | False | +-------+--------------------------------------+-------------------------------------------+--------------------------------------------------+----------+ [root@controller0 ~]# /bin/sh -c "nova-manage cell_v2 list_hosts" +-----------+--------------------------------------+---------------------+ | Cell Name | Cell UUID | Hostname | +-----------+--------------------------------------+---------------------+ | cell1 | 79648906-0ea8-4672-8c5f-73d5998a7b73 | compute0.os.lab.com | +-----------+--------------------------------------+---------------------+ [root@controller0 ~]# /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova Found 2 cell mappings. Skipping cell0 since it does not contain hosts. Getting computes from cell 'cell1': 79648906-0ea8-4672-8c5f-73d5998a7b73 Found 0 unmapped computes in cell: 79648906-0ea8-4672-8c5f-73d5998a7b73 (admin-rc) [andrefe@controller0 ~]$ nova hypervisor-list +----+---------------------+-------+--------+ | ID | Hypervisor hostname | State | Status | +----+---------------------+-------+--------+ +----+---------------------+-------+--------+ Any idea on how I can fix this and add the compute to the cell? Thanks.

2 1

[all][tc] Technical Committee next weekly meeting on 2022 Nov 16 at 1600 UTC
by Ghanshyam Mann 15 Nov '22

15 Nov '22

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

1 1

[mistral][keystone] Updating credentials and trusts
by Arnaud Morin 15 Nov '22

15 Nov '22

Hey team, Mistral is using keystone "trusts" in order to perform action on behalf of another customer. If I understand correctly the trust mechanism in keystone, it's related to a specific user_id. Imagine I want to update the user (and password) of the mistral service (mistral-api), then the user ID may change, so the trust will be broken. Is there any way to update the user of mistral-api without breaking the trusts? One answer is to not change the user, but only the password. But doing so will break my service for a moment (while I update the passwords in both services - keystone and mistral). Is there any other option? Regards, Arnaud - OVHcloud.

1 0

[tripleo] gate blocker /tripleo/+bug/1996482 - please hold rechecks
by Marios Andreou 15 Nov '22

15 Nov '22

Hi folks, per $subject we have a gate blocker at https://bugs.launchpad.net/tripleo/+bug/1996482 Please avoid recheck if you are hitting this issue - it fails during undercloud/standalone install and looks like: ERROR! Unexpected Exception, this is probably a bug: 'Task' object has no attribute '_valid_attrs' Fix is coming with https://review.opendev.org/c/openstack/tripleo-ansible/+/864392 thanks to Takashi for chasing that today regards, marios

1 1

EMC SAN with Openstack ansible
by Derek O keeffe 15 Nov '22

15 Nov '22

Hi all, I've been chatting on the IRC channel and I've gotten some feedback that I need to read up on regarding overrides, but just in case I'm about to reinvent the wheel (try at least) has anyone set up cinder volumes on an EMC SAN using OSA? and if so could yo give me some advice, examples, pointers, etc... We had it set up manually on an old cluster but are unsure how to do it through OSA (starting to look at it today based on the advice we got) This explains how to do it manually https://www.delltechnologies.com/asset/en-us/products/storage/industry-mark… Any info would be great and hugely appreciated. Should we figure it out before then we will drop the config here for others that may be interested. Regards,Derek

2 1

(no subject)
by K Santhosh 15 Nov '22

15 Nov '22

Hai , I am Santhosh, I do facing a problem with freezer deploymentnt After the deployment of freezer . The freezer_scheduler container is continuously restarting in kolla openstack can you help me out with this freezer_scheduler container

2 1

how to remove image with still used volumes
by Christoph Anton Mitterer 15 Nov '22

15 Nov '22

Hey. I have instances with a volume that were once created from some image. Now the volume's OS was upgraded over time to the respective current releases, while the image is long obsolete and just uses up space. Is there a way to remove those images? It seems normal commands don't allow me, as long as there are volumes which were created from them. Thanks, Chris.

5 12

Unable to snapshot instances on backend storage
by Derek O keeffe 15 Nov '22

15 Nov '22

Hi all, When we create an instance and leave the "Create new volume" option as no then we can manage the instance with no issues (migrate, snapshot, etc..) These instances are saved locally on the compute nodes. When we create an instance and select "Create new volume" yes the instance is spun up fine on our backend storage with no obvious issues (reachable with ping & ssh. shutdown, restart, networking, etc.. all fine) however, when we try to snapshot it or migrate it it fails. We can however take volume snapshots of volumes that we have created and are stored on the same shared backend. Has anyone came across this or maybe a pointer as to what they may think is causing it? It sounds to us as if nova try's to create a snapshot of the VM but thinks it's a volume maybe? Any help greatly appreciated. Regards,Derek

2 2

[tc] Fwd: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Nov 16, 2022 20:00 - 21:00 (UTC)
by Jeremy Stanley 14 Nov '22

14 Nov '22

Just a reminder that a few months ago we arranged a November meeting time between the OpenStack community and the OpenInfra Board of Directors, Wednesday 2022-11-16 at 20:00 UTC. Julia has graciously supplied a conference call connection for the hour. I've also added the connection info to the pad we've been using for planning this call: https://etherpad.opendev.org/p/2022-11-board-openstack-sync -- Jeremy Stanley ----- Forwarded message from juliaashleykreger(a)gmail.com ----- Date: Mon, 14 Nov 2022 18:10:42 +0000 Subject: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Nov 16, 2022 2pm - 3pm (CST) (jeremy(a)openinfra.dev) OpenInfra Board sync with OpenStack TC Wednesday Nov 16, 2022 ⋅ 2pm – 3pm Central Time - Chicago Location https://us02web.zoom.us/j/84584540710?pwd=aVdpaytPcG01NW9VWVZERDNtZURaZz09 https://www.google.com/url?q=https%3A%2F%2Fus02web.zoom.us%2Fj%2F8458454071… Greetings Directors & All, During the last meeting between the Board and the OpenStack TC, we determined we would attempt to meet on the 16th of November to have another general open discussion between the two groups. Mailing list posts were made, but a calendar invite was not sent out directly to the attendees. This is that invite. Please use the attached meeting link for call. -Julia ----- End forwarded message -----

1 0

Need information
by Gk Gk 14 Nov '22

14 Nov '22

Hi All, At the core of nova-api, I am trying to trace the function which executes the SQL query for listing all the instances for a user. I want to know where in the code this query is executed. I have traced it till this point in the code: ---- if self.cells: results = context.scatter_gather_cells(ctx, self.cells, context.CELL_TIMEOUT, query_wrapper, do_query) --- in the file " https://github.com/openstack/nova/blob/c97507dfcd57cce9d76670d3b0d48538900c… " But where in the above file, is the SQL query executed ? Please help me Thanks Kumar

2 1

RDO Zed Released
by Amy Marrich 14 Nov '22

14 Nov '22

The RDO community is pleased to announce the general availability of the RDO build for OpenStack Zed for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Zed is the 26th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. As with the Upstream release, this release of RDO is dedicated to Ilya Etingof who was an upstream and RDO contributor. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-zed/ The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/zed/highlights.html *TripleO in the RDO Zed release:* Since the Xena development cycle, TripleO follows the Independent release model ( https://specs.openstack.org/openstack/tripleo-specs/specs/xena/tripleo-inde… ). For the Zed cycle, TripleO project will maintain and validate stable Zed branches. As for the rest of packages, RDO will update and publish the releases created during the maintenance cycle. *Contributors* During the Zed cycle, we saw the following new RDO contributors: - Miguel Garcia Cruces - Michael Johnson - René Ribaud - Paras Babbar - Maurício Harley - Jesse Pretorius - Francesco Pantano - Carlos Eduardo - Arun KV Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all *57* contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: - Adriano Vieira Petrich - Alan Bishop - Alan Pevec - Alfredo Moralejo Alonso - Amol Kahat - Amy Marrich - Ananya Banerjee - Arun KV - Arx Cruz - Bhagyashri Shewale - Carlos Eduardo - Chandan Kumar - Cédric Jeanneret - Daniel Pawlik - Dariusz Smigiel - Douglas Viroel - Emma Foley - Eric Harney - Fabien Boucher - Francesco Pantano - Gregory Thiemonge - Jakob Meng - Jesse Pretorius - Jiří Podivín - Joel Capitao - Jon Schlueter - Julia Kreger - Karolina Kula - Leif Madsen - Lon Hohberger - Luigi Toscano - Marios Andreou - Martin Kopec - Mathieu Bultel - Matthias Runge - Maurício Harley - Michael Johnson - Miguel Garcia Cruces - Nate Johnston - Nicolas Hicher - Paras Babbar - Pooja Jadhav - Rabi Mishra - Rafael Castillo - René Ribaud/780 - Riccardo Pittau - Ronelle Landy - Sagi Shnaidman - Sandeep Yadav - Sean Mooney - Shreshtha Joshi - Slawomir Kaplonski - Steve Baker - Takashi Kajinami - Tobias Urdin - Tristan De Cacqueray - Yatin Karel *The Next Release Cycle* At the end of one release, focus shifts immediately to the next release i.e Antelope. *Get Started* To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. *Get Help* The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS and TripleO IRC channels (#centos, #centos-devel in Libera.Chat network, and #tripleo on OFTC), however we have a more focused audience within the RDO venues. *Get Involved* To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[neutron] Bug deputy Nov 7 to Nov 13
by Rodolfo Alonso Hernandez 14 Nov '22

14 Nov '22

Hello Neutrinos: This is the bug list from the past week: High: * https://bugs.launchpad.net/neutron/+bug/1996150: Neutron fails to create network with enforced scopes and new RBAC policies. Assigned: Slawek. * https://bugs.launchpad.net/neutron/+bug/1996129: With new RBAC enabled: Tempest test failing on NetworkNotFound. Duplicate of 1996150. Medium: * https://bugs.launchpad.net/neutron/+bug/1995972: L3 router is doing schedule_routers when adding/removing external gateway. Unassigned. * https://bugs.launchpad.net/neutron/+bug/1995974: [OVN] Router "router_extra_attributes" register is not created. Patch: https://review.opendev.org/c/openstack/neutron/+/864051 * https://bugs.launchpad.net/neutron/+bug/1996180: [OVN] "standard_attr" register missing during inconsistency check. Assigned: Rodolfo. Low: * https://bugs.launchpad.net/neutron/+bug/1996241: Manual install & Configuration in Neutron. Low hanging fruit. * https://bugs.launchpad.net/neutron/+bug/1996421: 'openstack port list' should display ports only from current project. Not sure this is a legit bug, commented in the bug and the patch. Invalid/opinion/incomplete/duplicated: * https://bugs.launchpad.net/neutron/+bug/1995872: A stuck INACTIVE port binding causes wrong l2pop fdb entries to be sent. Duplicated of https://bugs.launchpad.net/neutron/+bug/1979072. * https://bugs.launchpad.net/neutron/+bug/1996199: router external gateway assigning unsupported IPv6. Justification: https://bugs.launchpad.net/neutron/+bug/1996199/comments/1. Regards.

1 0