February 2024 - 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

[octavia] Purging ERROR'ed amphora and load balancers stuck in transitional states
by Paul Browne 11 Apr '25

11 Apr '25

Hello Octavia users, For a while I've been trying to find a systematic way to remove Octavia LBs+Amphora that have become stuck in ERROR or transitional PENDING_* states ; $ openstack loadbalancer amphora list -f value | grep ERROR a2323f14-3aaa-418a-8249-111aaa9c21fe 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe ERROR MASTER 10.8.0.242 192.168.3.247 e5b236ba-e7ee-4ed7-9f58-57ce7a408489 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe ERROR BACKUP 10.8.0.190 192.168.3.247 6b556f28-93c9-49dd-b6ee-4379288e7957 d5e402fe-2c4b-49af-a700-532cb408cee5 ERROR MASTER 10.8.0.39 192.168.3.126 c669db5d-8686-4d5c-9e95-e02030b34301 d5e402fe-2c4b-49af-a700-532cb408cee5 ERROR BACKUP 10.8.0.174 192.168.3.126 $ openstack loadbalancer list -f value | grep -vi active 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe k8s-clusterapi-cluster-default-ci-6386871107-kube-upgrade-kubeapi 3a06571936a0424bb40bc5c672c4ccb1 192.168.3.247 PENDING_UPDATE amphora d5e402fe-2c4b-49af-a700-532cb408cee5 k8s-clusterapi-cluster-default-ci-6386871107-latest-kubeapi 3a06571936a0424bb40bc5c672c4ccb1 192.168.3.126 PENDING_DELETE amphora These resources are marked immutable and so cannot be failed over or deleted; $ openstack loadbalancer amphora failover a2323f14-3aaa-418a-8249-111aaa9c21fe Load Balancer 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe is immutable and cannot be updated. (HTTP 409) (Request-ID: req-6e66c4e8-c3d3-4549-a03c-367017c8c8b3) $ openstack loadbalancer failover 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe Invalid state PENDING_UPDATE of loadbalancer resource 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe (HTTP 409) (Request-ID: req-84b44212-e7a8-4101-a16f-18c774c0577e) The backing Nova instances for these Amphora do seem to exist and be in good working order. Is there any API way to purge these out of Octavia's service state, or would (very careful) DB hackery be required here? Many thanks, Paul Browne ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk<mailto:pfb29@cam.ac.uk> Tel: 0044-1223-746548 *******************

4 6

[glance][ops] proposal to remove the glance-scrubber
by Brian Rosmaita 19 Jan '25

19 Jan '25

Hello Glance users, The Glance project team wants to determine whether anyone is using the glance-scrubber utility [0]. If not, we are thinking of deprecating it this cycle to be removed in the appropriate future cycle. If you have not previously heard of the glance-scrubber, that's most likely because it's only useful for particular deployment configurations of which yours is not one. See the doc [0] for details if you are curious. Our suspicion is that the glance-scrubber may have outlived its usefulness for modern OpenStack configurations. (The last time I remember it being discussed at a PTG was during the snowstorm in Dublin, which I believe was the Rocky development cycle). On the other hand, the team also has some ideas for improving the scrubber, but there's no point doing that if it's not actually being used in the first place. So if removal of the glance-scrubber would negatively affect you, please respond to this email so we can get some data points. Thanks! [0] https://docs.openstack.org/glance/latest/cli/glancescrubber.html

2 2

[cinder][kubernetes] pvc stuck in reserved state
by Eugen Block 10 Jan '25

10 Jan '25

Hi, we have a couple of k8s clusters in our openstack environment (Victoria) and are facing some problems when pods get moved to different worker nodes. The PVCs get stuck in "reserved" state, and they only get attached after resetting the volumes to "available" state. First I thought it was due to the missing multiattach volume type which seems to work fine in our customer's cluster. I also found the "duplicate connector" error messages in the nova-compute.log: > Unable to update attachment.(Invalid volume: duplicate connectors > detected on volume But after adding the multiattach volume type and retyping the affected volumes, the PVCs still get stuck in "reserved" state while I don't see any error messages on the hypervisors anymore. So it seems that something has changed/improved, but now I don't have a trace where to look next. Could this be a cinder-csi driver issue or something? Our cinder backend is ceph (Pacific). Not sure which information could help so please ask for anything I can provide. Any pointers are highly appreciated! Thanks! Eugen

1 2

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] [openeuler] CI jobs status
by Michał Nasiadka 26 Nov '24

26 Nov '24

Hello Koalas, OpenEuler jobs in master (to be Antelope) are failing for a long time. If no one is interested in maintaining OpenEuler support in Kolla-Ansible - I will propose dropping it’s support on Wednesday Kolla meeting. Best regards, Michal

4 3

[horizon][ceph] object storage container storage policy missing
by Satish Patel 24 Nov '24

24 Nov '24

Folks, Openstack Release: Zed Recently I have integrated ceph RGW service with openstack/keystone and testing with command line tool "openstack container create foo1" and it works but when I go to Horizon UI I am seeing it doesn't have storage policy dropdown list and because of that I am not able to create container or upload file from Horizon GUI https://ibb.co/KhYW6Rd It works with commands like but not horizon. $ openstack container create foo1 +---------------------------------------+-----------+------------------------------------------------+ | account | container | x-trans-id | +---------------------------------------+-----------+------------------------------------------------+ | AUTH_d4d82849885e4126aef402c408ad2c5c | foo1 | tx00000c057454841b13497-0065b558b4-42ff2eb-ahm | +---------------------------------------+-----------+------------------------------------------------+ $ openstack container list +------+ | Name | +------+ | foo1 | +------+

2 2

[nova][libvirtd] internal error: unable to execute QEMU command 'query-named-block-nodes'
by Satish Patel 22 Oct '24

22 Oct '24

Folks, I have a ceph cluster and recently I configured rbd-mirror to replicate all data to remove ceph cluster for disaster recovery. Yesterday for POC we did a hard cutover on ceph and point openstack to the new cluster. All other vms came back up fine but 2 vms stuck in this error state in libvirt logs 2024-01-31 22:44:37.591+0000: 474597: error : qemuMonitorJSONCheckErrorFull:399 : internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied If it's a wider issue than it should impact all the vms but why only two VM stuck and not starting and libvirt giving me this error in logs nova-compute logs also showing same error 2024-01-31 22:44:40.925 7 INFO nova.compute.manager [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] [instance: 2de0f880-77c7-4d2c-9e01-898c57ad3693] Successfully reverted task state from powering-on on failure for instance. 2024-01-31 22:44:40.944 7 ERROR oslo_messaging.rpc.server [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] Exception during message handling: libvirt.libvirtError: internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied

3 8

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

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

16 May '24

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

18 27

[kolla-ansible] support for FWaaS/LBaaS?
by garcetto 15 May '24

15 May '24

good morning, does kolla support fwaas or lbaas? thank you

3 4

[all][packaging][release][qa] pep-517 and pip 23
by smooney＠redhat.com 06 May '24

06 May '24

hi folks, TL;DR ----- this is a long email so the tl;dr is we should add pyproject.toml ``` [build-system] requires = ["pbr>=5.7.0", "setuptools>=36.6.0", "wheel"] build-backend = "pbr.build" ``` to all openstack projects to supprot pip 23.1+ Long version ------------ As some of you may know the ptg happend last week an done of hte topic raised there was a know limitation in devstack where GLOBAL_VENV=True does not work on centos/fedora derived distros. while i generally dont use centos/fedora derived distros for my daily work i have been using devstack for over 10 years at this point so when im told it broken i ocationlly will go fix it. In this case the issue is not with devstack (it often isnt) and is actully in our collective reliance on a deprecated functionality and how we package openstack today. Back story, for better or worse when openstack was created the landscape of python packaging was significantly different then it is today. To help corodinate our dependcies the openstack comunity went all in on requirements.txt and developed upper-constraits to manage our requirements and developed PBR (python build Reasonableness). both of those approches have served us well and likely will continue to do so for some time. Since then pyproject.toml has started to gain popularity and pep-517 (A build-system independent format for source trees) has been adotpted but so far openstack as a comunity has not embraced those changes. (although pbr already supprot pep-517 :) ). Until now this has not been a problem however with recent release of pip things are now breaking. Problem Context: - openstack does not provide pyporject.toml files - openstack project configure setuptools to use pbr via setup.py - setuptools support generating scripts form entry points(console_scripts) which we use for project binaries( nova- compute, neutron-server, ...) - openstack api services use a pbr extension know as wsgi_scripts which adds a similar functionality for generating wsgi application mains file - devstack due to coming changes in distro to block "sudo pip install" now installs openstack in a single by default on debian distros. on centos/fedora distros it currently almost functional (but not). - devstack installs in editable mode because that is how most developers use devstack for developemnt What changed: - pip 20.2 deprecated support for falling back to calling setup.py when pyproject.toml is not present - https://pip.pypa.io/en/stable/news/#v20-2 - https://github.com/pypa/pip/issues/8368 - at this point when pyproject.yaml is not called pip calls setup.py install [-e] <path to repo or package name> - setup.py invokes pbr to generate wsgi_scripts and other files - in pip 23.1 the fallback was removed https://pip.pypa.io/en/stable/news/#v23-1 - pip now builds a temp local wheel instead of calling setup.py install when pyproject.toml is not found - in editable mode (-e) the default way the wheel is built does not invoke pbr properly to generate the wsgi files - as a result the wsgi files are not installed to the venv bin dir and this causes devstack to fail to start keystone (or any other wsgi api) The fix, there are a few ways to approch this: - clamp pip (https://review.opendev.org/c/openstack/devstack/+/898845) this is a terible idea and it breaks debian - clamping pip below 23.1 works on centos for now however OVS on debian already requires pep 517 for installing - as such when that version of ovs (or other projects start enforcing that) hits centos it will break - add a minimal pyproject.toml to all openstack project - example for keystone https://review.opendev.org/c/openstack/keystone/+/899519 - this example jsut adds the minium pyproject.toml to enable pbr to be used as the build system - it does not remove supprot for setup.py but it will not be used by default going forward whit new version of pip - all config is still in setup.cfg - add pyproject.toml support but remove setup.py support https://review.opendev.org/c/opendev/bindep/+/816741 - this goes one step futrue and actuly nulls out setup.py - we could take this approach if we want to but its not required. The reason for this email is to get agreement on how to support pip 23.1+ My proposal would be to add pyproject.toml with the minimal config required to enable pip 23.2 but not drop the setup.py support in this cycle. i would suggest that we can deprecate installing via setup.py in caracal if that is desirable but not make that change until the next slurp to give time to projects and packages to catch up. if there are no objections to that i would like to ask what is the preferd way to create and submit the patches for the minimal pyproject.toml ``` [build-system] requires = ["pbr>=5.7.0", "setuptools>=36.6.0", "wheel"] build-backend = "pbr.build" ``` i can propose patches to the main project deployed by devstack by default. i.e. nova/neutron ectra but it might be better if someone form the core teams of each project could take on that task and chasing the reviews. if someone has a script to generate a patch for a set of repos that just add the above pyporject.toml then we can use that to keep a consistent topic/commit message across all patches. my proposal for testing this is two fold. in ci we can test the patches are functional by using a DNM patch to devstack to force enable the gloal venv on centos and depend on the set of patches, i will modify https://review.opendev.org/c/openstack/devstack/+/898845 to do that locally we can test that the patch is functional by doing the following substituting keystone for the relevant project. ``` git clone https://opendev.org/openstack/keystone cd keystone python3 -m venv .venv . .venv/bin/activate python3 -m pip install -U pip python3 -m pip install -e . ls .venv/bin/keystone* ``` the ls will not contain the wsgi script with the addition of the pyproject.toml it should. on debian sid i can reproduce the same issue the problem we are seeing on centos 9 now will start impacting other distos eventually so its good to fix this now. if i start proposing this to glance/nova/neutron/cinder/swift/horizon/placement (to get a default devstack working) can i get cores to review? can cores form each project nominate peopel to review or volenteer to do this work. i have created https://etherpad.opendev.org/p/pep-517-and-pip-23 to track this work i have some other work that i think we can do in parallel like addign pyporject.toml support to the pti requirements if we go this way but that i think we can discuss on a governacne patch to updated it. anyway this is a lot to digest so feedback is welcome. if someone else would like to drive this that is also welcome (i.e. tc/release team) regards sean.

10 27

[all][tc] Modernize Python Stack
by Niklas Schwarz 10 Apr '24

10 Apr '24

Hello, I have just ran over the mailing listing post OpenStack 2024.2 testing runtime by Ganshyam Mann [1] on dropping support for python3.8 for the upcoming Openstack 2024.2 release. This post and some small contributions to some openstack components have lead me to write this post. What I would like to suggest to modernize the Python-Stack used for OpenStack. Such a modernization includes: - A current python version - A modern and up to date static code analysis - Introduce type annotations Let me explain what I mean: A current python version: The current supported Python versions are Python 3.8 to Python 3.11 [2]. As of writing, OpenStack Yoga was just moved to unmaintained. To install this release, e.g. on an Ubuntu Jammy operating system the packages are included in the Ubuntu-Packages. The default Python version on an Ubuntu 22.04 operating system is Python3.10. And looking at the support of the Python versions [3] Python 3.8 to 3.10 only receive security updates but the end is near for Python 3.8 to be out of support. The policy defined which Python version should be used for testing [4] will result that Python 3.8 is still used for the OpenStack 2024.1 release [5]. And this will also result in required support for Python3.8 in the upcoming releases of OpenStack. I my opinion the policy should be reworked and the OpenStack releases should be more aggressive on dropping support for older Python versions. Modern features of the language cannot be otherwise be used, therefor improvements in speed, security and general toolchain/ecosystem cannot be fully leveraged. By defining the lower bound of the Python Version we are limiting ourself to this version but we might also reduce the features we can use because of deprecations of the newer versions . A modern and up to date static code analysis: Currently flake8 and pylint are used both of which are modern analysis tools. But their configuration is in my opinion not up to date. Lets have a look at the configuration of the neutron-lib [6]. As seen a lot of rules are disabled by the configuration and are needed at the current moment at the state of the project. In addition some rules need to be adjusted such as the line length (80 characters is a very aggressive limit and on most modern displays a line length of 100 to 120 can fit without any problems, personal opinion). The adjustment of the static code analysis besides opinionated rules will lead me to my third point to modernize the Python stack used Introduce type annotations Python type annotations are well supported in the current Python versions and through the typing package additional types are added. The introduction of type annotations will improve the developer experience. This is also motivated by the Python foundation in pep-484 [7]. Because of the type annotation all modern IDEs can provide (more precise) type hints. The type hints can and in in my experience will reduce the introduction of bugs (accessing members or calling methods, no logical bugs) and will shorten the time to develop a new feature or fix a logical bug and do not run in runtime exceptions. The datatypes passed to a method are clear and we do not need to dig down a rabbithole to find out what is passed to a method. The name of a variable does not always tell the truth. As an example I want to look at a patch [8] for the neutron-vpnaas component. Christian Rohmann and I worked on this patch for the component together (this has also lead me to write this email) to improve the reconciling for VPNaaS. It took as along time to find out that a RouterInformation object is passed in to a method instead of a router but the variable was named router. We both agreed on that in the first place the naming of the variable was wrong but type annotations would have saved us a good amount of time. This does not mean that the naming is not important and that type annotations will save the world, the context which includes the name of variables is important and type annotations will add additional information to the context. And I have just touched the surface on what is possible with the introduction of type annotations, thinking of automatic document generation, test generation, even code generation,... As a reference to my point modernizing the static analysis this can then also include the introduction of mypy to check the types used. Of course such a change cannot be done in one big commit and needs time but I suggest to start adding type annotations and improve the overall code quality of the OpenStack services, starting with the oslo packages as they are used by mostly all OpenStack components. Of course such changes cannot be done for such a huge project in one day. It took a long time to remove support for Python 2. So I do not expect such changes to happen immediately. But it would be nice to have a discussion about it and maybe create a road map and adjust some policy on supported Python versions and create new policies how to write Python code and what additional tools should be used. I can also understand if not everything is possible but the last two points need to be addressed in my opinion. These changes will lead overall to better code quality but most important the introduction to the big code base will be easier for new developers and reviewers will also have a better time. Best regards Niklas [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://docs.openstack.org/tempest/latest/supported_version.html [3] https://devguide.python.org/versions/ [4] https://governance.openstack.org/tc/resolutions/20181024-python-update-proc… [5] https://governance.openstack.org/tc/reference/runtimes/2024.1.html [6] https://github.com/openstack/neutron-lib/blob/master/.pylintrc [7] https://peps.python.org/pep-0484/#rationale-and-goals [8] https://review.opendev.org/c/openstack/neutron-vpnaas/+/875745

15 27

Accessing virsh in openstack wallaby | tripleo
by Swogat Pradhan 24 Mar '24

24 Mar '24

Hi, Can someone please tell me how can i access the virsh utility on the compute node on openstack wallaby? Previously we used nova_libvirt but in wallaby there are multiple containers and i am unable to use virsh utility to edit my domain.xml file. List of containers: [root@dcn01-hci-2 ~]# podman ps | grep nova 10d981158842 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtlogd_wrapper e91667516afc 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtsecretd a4b07fe0e833 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtnodedevd d7e1db393e9c 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtstoraged 5308a171793e 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtqemud f490a6249ba1 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 6 weeks ago nova_virtproxyd ab0441e56957 172.25.201.68:8787/tripleomaster/openstack-nova-compute:current-tripleo kolla_start 2 months ago Up 2 months ago (healthy) nova_migration_target f35fbba5b690 172.25.201.68:8787/tripleomaster/openstack-nova-compute:current-tripleo kolla_start 2 months ago Up 6 weeks ago (unhealthy) nova_compute 82bc01993106 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo /usr/sbin/virtlog... 2 months ago Up 2 months ago Can someone please suggest how I can i edit an instance xml file in this setup? With regards, Swogat Pradhan

2 5

[swift] Can I use oslo.log / oslo.config in swift? Can we make Swift behave like the rest of OpenStack?
by Thomas Goirand 20 Mar '24

20 Mar '24

Hi, Because we had some issues with a bad rebalance in production (we didn't loose any data, but some drives went full...), I attempted to implement the Swift mitigation to prevent disk full scenarios. I found that what upstream recommends [1] is a script that's written in Python 2, and that wouldn't work at all: it's not only very old, it's also a very partial implementation. So I wrote this: https://review.opendev.org/c/openstack/swift/+/907523 But then, I was told (thanks for the review!) that I shouldn't be using oslo.config and/or oslo.log, as other parts of Swift don't do that. I do understand that the rest of Swift is like this, and therefore, the review comment is probably right. However... Back in the days, I would have understood why things would have been written that way: the Oslo libs were young, and not available everywhere, and it was kind of a good idea not to use them. But now, fast forward in 2024, I found that Swift behaving differently from the rest of OpenStack is more a problem than a feature. It's also very frustrating to use the old way with the config_parser, which can't auto-generate the config file and so on. So I am wondering: - is it still the case, that I shouldn't use oslo.config / oslo.log when adding a patch in Swift? - can we revisit this, and convert swift to oslo.config generated config files, and PBR shell-script entry points instead of binary simply dropped into the toplevel bin folder? Can we make swift smarter and behave like the rest of OpenStack? :) Cheers, Thomas Goirand (zigo) [1] https://docs.openstack.org/swift/latest/admin_guide.html#preventing-disk-fu…

2 2

Use Openstack SDK for Swift
by Albert Braden 19 Mar '24

19 Mar '24

I'm writing a script that will use admin credentials to check user projects for containers. I'm already doing something similar for non-swift accounts, doing things like: cloud.network.networks(project_id=projectid): I read here about the Object SDK: https://docs.openstack.org/openstacksdk/latest/user/guides/object_store.html And I tried this: cloud.object_store.containers(project_id=projectid): But I get an error: Invalid query params: project_id I read the Object SDK document here and it doesn't seem to say anything about how to specify a project: https://docs.openstack.org/openstacksdk/latest/user/proxies/object_store.ht… But when I read the Swift API document, I see that I can use "/v1/{account}/{container}", so I'm guessing that there must be a way to do it via the SDK. https://docs.openstack.org/api-ref/object-store/#show-container-details-and… Is it possible to specify the project in an Object SDK call, or do I need to use the old python API for this?

2 2

[Freezer] Is Freezer dead?
by pi3.14＠tuta.io 18 Mar '24

18 Mar '24

Hi folks, is Freezer still supported? I don't see any real development going on with it. Is it recommended to use in a production Cloud environment? Are there other free and open source alternatives to Freezer? Thanks Roby

8 19

[swift] Increase part power on account/container ring
by Thiago De Moraes Teixeira 13 Mar '24

13 Mar '24

Morning, Here we have a cluster with Accounts/Containers ring with part power 8 and our Objects ring with part power 20 (builted later). Now we want to migrate the 'old' Accounts/Containers ring to a new one, with higher part power, like 20. Is there a better way to do this? I'm doing some crazy tests with SAIO and multiples storage nodes, based in build a new ring with part power 20 and just swap the old files (account/container.ring.gz) with the new ones and let the replicators do their jobs, moving *.db files to their new home partition. Until today these tests worked fine, but I don't know how to do it on a large scale, with some terabytes of data. Just wondering about some ways to do that :) And before/after this change, is there any command in swift that i can audit this entire process, ensuring that cluster data remains the same? Thanks! -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

3 8

[neutron][horizon] disable permission to release floating ip for non-admin users
by Satish Patel 08 Mar '24

08 Mar '24

Folks, I want to disable permission or the horizon button or whatever best way to not allow end users to "Release floating IP" because I want them to stick with assigned IP and not releasing them because of some regulatory process. Not sure what is the best way to have this level of control. I found neutron policy delete_floatingip: but is this the correct way to implement this policy? OR Does Horizon have some level of ACL to remove buttons or disable it? Looking for advice or clues. Thanks!

3 2

[heat][monasca][sahara][senlin] Features dependent on inactive projects
by Takashi Kajinami 08 Mar '24

08 Mar '24

Hello, As you know, some of the OpenStack projects were marked inactive during this cycle. There are still on-going discussions but from my view these are very likely excluded from the upcoming 2024.1 release and it's unclear yet if any of these projects will be kept. Currently heat provides features integrated with some of the inactive projects (Monasca, Sahara and Senlin), and we have to decide how we deal with these features[1]. The main concern is that we can't maintain the features for the inactive projects, and IMO we should retire these features if these inactive projects are abandoned or are no longer maintained in the consistent way with the other active projects. Based on the current situation, I'd propose the following steps for upcoming cycles. - Deprecate the features dependent on inactive projects in 2023.2 release - Note that we have to remove these features directly during this cycle in case any problems related to these project block the upcoming heat release. - Remove these features in 2024.1 release unless we are sure that these projects are kept maintained as active projects in the openstack namespace, with following the global release cycle. Please let me know if you have any concern about the proposed plan. If I hear no objections then I'll propose patches for deprecation. Thank you, Takashi Kajinami irc: tkajinam [1] I've submitted a series of patches to remove these features and these would give a clear view about the features affected. https://review.opendev.org/q/topic:%22inactive-project-removal%22+project:o…

3 6

[neutron] Is the vxlan(overlay) network a Provider network or a self-service network
by 韩光宇 08 Mar '24

08 Mar '24

Hi, In neutron install doc[1], I got the concept of Provider network and Self-service network. And I got that: - Provider network bridges virtual networks to physical networks and relies on physical network infrastructure for layer-3 (routing) services - Self-service network routes virtual networks to physical networks using Network Address Translation (NAT) So I understand: Flat/Vlan network are Provide network and vxlan/gre network are Self-service network. But, in openstack cmd, I found that all network types are classified as provider network types. ``` openstack network create --help ... --provider-network-type <provider-network-type> The physical mechanism by which the virtual network is implemented. For example: flat, geneve, gre, local, vlan, vxlan. ``` I am confused, why do vxlan and gre appear in the **provider network type**? According to the installation doc[1], overlay networks should not all be self-service networks Or is the provider network in cmd not the same as the provider network in the installation document, the provider network here is only different from the tenant network? Can someone help me distinguish between these concepts, or suggest questions that I can read: why vxlan is provider network I will appreciate for any help. Best wishes, Han Guangyu [1] https://docs.openstack.org/neutron/latest/install/controller-install-obs.ht…

2 1

[cinder][glance][nova][telemetry][monasca][oslo][vmware] Can we deprecate(and remove) VMWare support ?
by Takashi Kajinami 07 Mar '24

07 Mar '24

Hi all, As you might know, some of the OpenStack projects currently support usage of VMWare component. However recently the VMware virt driver in nova was marked experimental in 2023.2 release [1] and it has been discussed that the driver will be removed in 2023.2 release[2], after deprecation is backported to 2023.1. (Please someone from nova team correct me if I'm wrong) So my current question is; Does it make sense to deprecate all of the features to support VMWare component ? My understanding is that these features were added to be used along with VMWare virt driver in nova, but once the virt driver is removed this use case is voided. I'll list up the features within the discussion scope below. nova: VMWare virt driver (this is already experimental by [1]) cinder: VMware Storage Driver (vmdk) glance: VMWare Datastore (I proposed deprecating this in [3][4]) ceilometer: VMWare virt driver (this was deprecated by [5]) os-brick: VmdkConnector monasca-agent: vcenter collector (*1) oslo.vmware: the whole project NOTE: These features are found based on dependency on oslo.vmware but there can be a few not listed here. Outside of OpenStack's governance, there are two projects dependent on oslo.vmware, networking-vsphere and vmware-nsx but both of these look inactive. Because of SLURP, we have to complete deprecation during in 2024.1 release so that we can drop the feature right after 2024.1. If we fail then we have to maintain these features until 2025.1 (the features already deprecated can be removed earlier, though). So I'd like to get feedback and decision before deadline for 2024.1 Thank you, Takashi (*1) Monasca is now inactive so I doubt anyone would work on this topic before it is retired. [1] https://review.opendev.org/c/openstack/nova/+/863911 [2] https://review.opendev.org/c/openstack/nova/+/897017 [3] https://review.opendev.org/c/openstack/glance_store/+/893696 [4] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] https://review.opendev.org/c/openstack/ceilometer/+/894540

6 21

[kolla][cinder][nfs] NFS backend error for volumes
by Satish Patel 06 Mar '24

06 Mar '24

Folks, I am configuring NFS for the cinder backend but somehow it doesn't go well. I am running kolla-ansible with the 2023.1 release. cinder.conf [DEFAULT] enabled_backends = volumes-ssd,volumes-nfs [volumes-nfs] volume_driver = cinder.volume.drivers.nfs.NfsDriver volume_backend_name = volumes-nfs nfs_shares_config = /etc/cinder/nfs_shares nfs_snapshot_support = True nas_secure_file_permissions = False nas_secure_file_operations = False Inside the cinder_volume docker container I can see it mounts NFS automatically and directory permissions is also cinder:cinder also I am able to write on NFS share also so it's not a permission issue also. $ docker exec -it cinder_volume mount | grep nfs 192.168.18.245:/volume1/NFS on /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.18.245,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=192.168.18.245) But service is still showing down. | cinder-volume | os-ctrl2@volumes-nfs | nova | enabled | down | 2024-02-28T04:13:11.000000 | In logs I am seeing these 3 lines but then no activity in logs even after restarting the container so that is very strange. 2024-02-28 04:13:12.995 153 ERROR os_brick.remotefs.remotefs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] Failed to mount 192.168.18.245:/volume1/NFS, reason: mount.nfs: Protocol not supported : oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file permissions mode will be 666 (allowing other/world read & write access). This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NFS configuration. 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file operations will be run as root: allowing root level access at the storage backend. This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NAS configuration. Has anyone configured NFS and noticed any behavior?

3 12

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

06 Mar '24

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

3 5

[tc][murano] Removing Murano from 2024.1 release
by Jay Faulkner 05 Mar '24

05 Mar '24

Hi all, After discussion in the TC meeting today about lots of gathered evidence that Murano is inactive and plagued by serious bugs, I have proposed a resolution to remove Murano from the release. This is roughly equivalent to marking it inactive; however we can only use inactive status to remove things from the release before milestone-2. At this point, the TC is too late discovering the bad state of Murano to use inactivity to prevent its release. Therefore, I have proposed a special-case resolution[0] reflecting general consensus in the TC meeting that Murano should not be released. I wanted to inform the community of this resolution, and advise anyone who may be considering deployment of Murano to be aware of its current inactive state. Additionally, if you believe our evaluation of the situation is wrong, feel free to let your voice be heard in Gerrit. Thanks, Jay Faulkner OpenStack TC Chair 0: https://review.opendev.org/c/openstack/governance/+/910434

1 1

[diskimage-builder] bootable ISO image for baremetal
by Ettore Simone 05 Mar '24

05 Mar '24

Hi! I know it is not one of the most wonderful options for DIB, but in some circumstances I used ISO image in a USB stick for some old and unmaintained hardware. I used to fix by hand every time the "iso" element to complete the task, due to an old reference to a deprecated variable (DIB_IMAGE_ROOT_FS_UUID, now DIB_BOOT_LABEL). I proposed a very small fix and I hope it could be merged in the future: https://review.opendev.org/c/openstack/diskimage-builder/+/905556 Thank you for all your great work. Cheers, Ettore

4 6

[magnum][nova] AZ or Host aggregates not working as expected
by Satish Patel 04 Mar '24

04 Mar '24

2 13

Need Help to setup Bumblebee VDI project
by Artemio Mendoza 01 Mar '24

01 Mar '24

Hello, I'm trying to set up the Bumblebee (https://github.com/NeCTAR-RC/bumblebee) project on my local computer to test. So I installed docker and tried setup by following the readme. But I'm really new in OpenStack (only tried to run OpenStack through devstack) so I would appreciate it if I could have a very detailed guide. So please share any idea, online video link, or guide document. anything is good to me. Looking forward to hearing from you. Thanks, Artemio Mendoza

3 4

[TC][openapi] Request for new projects under the OpenStack hat
by gtema 01 Mar '24

01 Mar '24

Hi TC representatives, Some time ago I was communicating about my POC on generating OpenAPI schemas from the source code of services. I continued working on that and have now few projects (that I was developing on GitHub to make life easier) that I would like to bring under the OpenStack hood (and place them under the SDK team). I have also figured out that Nova is now reviewing spec on starting using supporting this (thanks Stephen) and Neutron folks expressed also interest. === codegenerator https://gtema.github.io/openstack-codegenerator/ This project is responsible for generation of the OpenAPI specs and generate other (currently user-facing) code ouf of them === openstack-openapi https://gtema.github.io/openstack-openapi/ This repo hosts rendered specs and provides analogue to the os-api-ref Sphinx extension that renders them into the html (what you see under the link is a mix of Swagger and os-api-ref style). I was not really effectively working on that rendering lately, the repo right now is more or less a storage for the specs themselves with a first sketch of sphinx extension of rendering and basic OpenAPI flavoring doc. === openstack-rs https://gtema.github.io/openstack/ This is a Rust monorepo project with few items: - SDK for OpenStack out of the rendered OpenAPI specs - experimental CLI following very different approach compared to the python- openstackclient. It is compiled into single binary (what helps those not willing to pull whole python with all deps and the insanity we experience lately or those who build docker containers with only OSC inside to bypass the mentioned hell) and purely auto-generated from the specs - [future] openstack-tui (similar to k9s for Kubernetes) Here it is all really oriented only on the user facing tooling. I am very convinced in this project and will continue working on it independent on the outcome. Any objections/ideas/comments? Should I just go and create 3 project-config changes pending the approval? ====== Since I am on this topic anyway I would also like to address another related question. While working for OpenTelekomCloud we developed HashiVault plugin for managing OpenStack credentials as secrets (I had a talk on that in Vancouver). We tried to bring this to OpenDev but were unsure under which namespace. Pretty shortly a Hashi license issue started circling around and after few back and forth iterations we were not sure what to do with that project at all. Anyway the plugin itself is Apache-2 and working. It should be possible to also use it with OpenBAO (as a fork of Vault), but it was not tested so far. I am now not with Telekom anymore, but people there are still willing to contribute it under the OpenStack. Do you have any opinions on that? Is there interest in getting this under the OpenDev and if yes then which namespace (openstack or X)? ======= Thanks, Artem

4 5

[all][ptls][release] Action needed to move forward Unmaintained branch policy
by Jay Faulkner 01 Mar '24

01 Mar '24

Hi all, If you are a PTL of a project, a release liason, or a person generally interested in older OpenStack branches, please make sure you take a look at the topic here: https://review.opendev.org/q/topic:%22vwx-unmaintained%22 and vote appropriately on projects you care about. More information can be found in the commit message for the patches themselves. A lot of folks have done work behind the scenes to enable this transition; please help us by doing your part and getting these reviews done in a timely manner is one way we can show gratitude to the releases team and others who have worked to make this transition possible. Thanks, Jay Faulkner OpenStack TC Chair

2 1

[blazar] Proposing Mark Powers and Matt Crees as core reviewers
by Pierre Riteau 29 Feb '24

29 Feb '24

Hello, I would like to nominate two new core reviewers for the Blazar project: - Mark Powers from University of Chicago - Matt Crees from StackHPC Mark Powers has been operating Blazar for several years for the Chameleon project (https://www.chameleoncloud.org) and maintains a fork of Blazar with many changes for this environment. The most useful changes are gradually being contributed upstream. Matt Crees has contributed several useful features to Blazar in the past few releases and helps to maintain the code. The Blazar project will benefit from their expertise and I trust their input as reviewers. Best wishes, Pierre Riteau (priteau)

1 1

[all] Gate issues and memory pressure; can you help?
by Jay Faulkner 29 Feb '24

29 Feb '24

Hi all, As some of you are aware, keeping the OpenStack CI system operating is a massive amount of work, and it's a team effort. Along those lines, we continue to have issues with CI, and memory pressure is a common thread. Recently at a TC meeting[0] we discussed how the gate is using more ram -- now in the form of swap. One additional concern is that this memory usage increase may be reflective of what our users are experiencing -- bugs that we need to fix for the sake of our users. A specific target of concern is oslo.privsep[1], but generally a need for an audit of memory usages of OpenStack services would be of significant value to the community. If you're interested in taking on this work, please reach out here, on the mailing list, or in any relevant #openstack-* channel, such as #openstack-tc. In any event, don't wait for permission! Take action and see if you can make things better, even a little bit. Thanks, Jay Faulkner OpenStack TC Chair 0: https://meetings.opendev.org/meetings/tc/2024/tc.2024-02-20-18.00.log.html 1: https://opendev.org/openstack/oslo.privsep

1 0

[cinder] FFE request for [NetApp] LUN space allocation support in 2024.1
by Borra, Jayaanand 29 Feb '24

29 Feb '24

Hello All, I would like to request FFE in the 2024.1 Caracal cycle for the below patch https://review.opendev.org/c/openstack/cinder/+/893106 Reason for FFE: Addressing review comments Thank you! Jayaanand.

3 2

Openstack Networking queries
by KK CHN 29 Feb '24

29 Feb '24

List, My kolla-ansible OpenStack installation all-in-one on Virtual Machine( Ubuntu 22.04, ) This base VM has three vNICs 1. ens192 with ip 10.170.16.128 from my organization's LAN with internet connectivity 2. ens224 is configured manually with a 10.220.0.51 IP ( from a VLAN for internal testing without internet) 3. ens160 This interface is made up without any IPs ( I don't know why this has to be up without any IP address, but kolla-ansible all-in-one installation document specifies one interface like this required ) Can I do the kolla-ansible deployment with the above 2 vNICs only ( ens192 and ens 224 ?) But ens192 I cannot have without IP addresses as it is my organizational LAN. Other clients in the office use this Segment for daily work . I don't have control on 10.170.16.0/24 but only on10.170.16.128 ip Any serious issues there by using only ens192 and ens224 alone in this case ? ( I can use ens224 ( 10.220.0.0/24 segment as floating IPs as it is in my control as a VLAN) But How can I connect the internet and external world communication to this vLAN 10.220.0.0/24 from 10.170.16.128 IP which has the internet. (to use these vLAN IPs as floating point IPs ) my tenant network can be ( all VMs can be on 10.0.0.0/24) How to provide the internet to this vLAN 10.220.0.0/24 from the available internet connected IP ens192 (10.170.16.128 with internet) I have only control on this IP but not on 10.170.16.0/24 network as it is not under my control. Can I use the following config for bootstrapping and deploying kolla-ansible all-in-one *Correct me what I am missing or what wrong I am doing in this setup ??* (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes config_strategy: "COPY_ALWAYS" kolla_base_distro: "ubuntu" openstack_release: "2023.1" kolla_internal_vip_address: "10.220.0.24" kolla_external_vip_address: "{{ kolla_internal_vip_address }}" kolla_container_engine: docker network_interface: "ens224" neutron_external_interface: "ens160" neutron_plugin_agent: "openvswitch" nova_compute_virt_type: "qemu" (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$

2 1

*[glance] Request for Feature Freeze Exception*
by Abhishek Kekane 29 Feb '24

29 Feb '24

Hi Team, I would like to request FFE for "Using centralized database for cache operations" feature. Patches: https://review.opendev.org/q/topic:%22centralized-cache-db%22 Status: Base functionality is merged Pending: - Devstack patch for defaulting cache_driver to centralized_db - https://review.opendev.org/c/openstack/devstack/+/907110 - Tempest tests for caching images on remote node - https://review.opendev.org/c/openstack/tempest/+/901525 - Grenade patch to change cache-driver to centralized_db on upgrade - https://review.opendev.org/c/openstack/grenade/+/901678 - New tempest job to test centralized db - https://review.opendev.org/c/openstack/glance/+/901429 - New Grenade job to test upgrade scenario - https://review.opendev.org/c/openstack/glance/+/901649 - Make centralized_db driver default in glance - https://review.opendev.org/c/openstack/glance/+/907111 Why miss the deadline: Some useful restructuring during milestone 3 This feature is useful as we just need a single database which reduces the need of maintaining sqlite3 database and also can enhance caching operations by introducing new APIs in future. Kindly consider this feature for the current cycle and assist with reviews and suggestions. Thank you, Abhishek Kekane

3 2

[nova] dry-run migration api
by Pavlo Shchelokovskyy 29 Feb '24

29 Feb '24

Hi all, Recently I've been looking into various load optimizations tooling for OpenStack (like Watcher), and noticed a lacking feature that could make such tooling much more robust and useful. The optimization tooling usually collects some metric about compute hosts and instances that nova may be totally unaware of (e.g. power consumption of a compute node in Watts), and then tries to reshuffle the instances between hypervisors to optimize said metric in some sense. The problem is, the tool has no idea beforehand if nova will actually allow moving this given instance to this given hypervisor. I am talking about resource consumption, resource provider traits, image and aggregate metadata matching, numa placement, server group affinities etc. To know all this for sure, the optimization tool would have to duplicate most of the nova scheduler and good part of placement inside of itself - which is not feasible. This is why AFAIU in Watcher all available strategies mention that they expect "any VM to be migrateable to any hypervisor", which is far from many if not most real life deployments. What I suggest is adding a new API to nova to effectively have a 'migration dry run' - it should return the list of target hosts a given instance may be migrated to, accounting for all the knowledge nova has about the instance and the hypervisors. The list can be already sorted by nova weighers to signal the preferred choice from nova side. AFAIU such a new API would not require any drastic changes in Nova - the most of the code is already there, used during migrations, only that at the last step, instead of choosing the best compute and actually initiating the migration process, the result of filtering and weighing will be returned to the caller in some form. Would there be interest in such an API? If yes, I could start writing and proposing a spec. Best regards, -- Dr. Pavlo Shchelokovskyy Principal Software Engineer Mirantis Inc www.mirantis.com

3 2

Re: Enabling external connectivity to VMs
by Eugen Block 29 Feb '24

29 Feb '24

Please don't drop the list from your response. I'm not very familiar with kolla, but if you're able to ping the instance via floating IP it seems okayish. Maybe you need to set neutron_external_interface to ens192 instead? Someone with more kolla experience will probably correct me here, so don't rely on my response. Zitat von KK CHN <kkchn.in(a)gmail.com>: > Hi Eugen, > > I have followed the > https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro… > > But mistakenly I have configured ens160 as neurton_external_interface: > "ens160" as the docs says an interface without IP address needed so I > create a vNIC ens160 without IP and used this without knowing What I am > doing..!!!! > > The issue is tenant VMs don't get Internet. also tenant VMs cant ping > base VM(Ubuntu 22.04 IP 10.220.0.51, or 10.176.16.128 .. ) totally > confused. > > > Could you help me to understand what I am doing wrong here ? > Greetings > Krish. > > *For more info what I have done so far : * Please refer to > the following... > > In the Base VM, I created 3 vNICs. > > 1. ens192 with my Org's dhcp LAN IP 10.176.16.128 which has the internet. > 2. ens224 with 10.220.0.51 IP which is a VLAN IP of (10.220.0.0/24) which > is created for testing purposes internally by N/W guy. This doesn't have > the internet.. > > 3. ens160 up active without IP address. ( Wrongly I specified this as the > e neutron_external_interface in globals.yml) > > > > *I have deployed the openstack..Everything up and running .. * > I am able to create Routers, Network and subnets and able to create > instances(all VMs spawning with 10.0.0.0/24 IPs) > > I created the networks(external with subnet 10.220.0.0/24 with > start=10.220.0.30 to end=10.220.0.50) and internal Network(with subnet > named demo-net 10.0.0.0/24 for tenants) > > I am able to associate the VMs with 10.0.0.0/24 IPs to Floating IPs from > 10.220.0.0/24 > > and from my Base(host) VM(Ubuntu22.04 with ens224 10.220.0.51) I am able > to ping the 10.0.0.28 tenant VM IP through the associated floating IPs as > > $ ip netns ( On base (host) VM) dsplays the router > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ ip netns > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 (id: 1) > > qdhcp-c29f26ac-3594-4c40-bf20-f2d5ba7d6eea (id: 0) > > > $(kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ sudo ip netns exec > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 ping 10.0.0.28 ( the VM > tenant IP address) > PING 10.0.0.28 (10.0.0.28) 56(84) bytes of data. > 64 bytes from 10.0.0.28: icmp_seq=1 ttl=64 time=0.972 ms > > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ sudo ip netns exec > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 ping 10.220.0.44 ( the > Floating IP associated to 10.0.0.28 VM) > PING 10.220.0.44 (10.220.0.44) 56(84) bytes of data. > 64 bytes from 10.220.0.44: icmp_seq=1 ttl=64 time=0.840 ms > 64 bytes from 10.220.0.44: icmp_seq=2 ttl=64 time=0.599 ms > > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ sudo ip netns exec > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 ping 10.220.0.33 ( The router > IP through which connects floating ip 10.220.0.44 and then to tenant VM ip > 10.0.0.28 ) > > PING 10.220.0.33 (10.220.0.33) 56(84) bytes of data. > 64 bytes from 10.220.0.33: icmp_seq=1 ttl=64 time=0.038 ms > > *Hence it works somehow. * But ens224 10.220.0.51 doesn't have > internet on the base VM. But only ens192->10.170.16.128 IP has.. > > How can I provide the internet connectivity of ens192 to ens224 Is this > possible or Am I doing some dump here.? What is the other way / best way > to do this .. > I am beginning my journey with OpensStack but stuck here without much > progress.. > > > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml > --- > workaround_ansible_issue_8743: yes > config_strategy: "COPY_ALWAYS" > kolla_base_distro: "ubuntu" > openstack_release: "2023.1" > kolla_internal_vip_address: "10.220.0.24" > kolla_external_vip_address: "{{ kolla_internal_vip_address }}" > kolla_container_engine: docker > network_interface: "ens224" > neutron_external_interface: "ens160" > neutron_plugin_agent: "openvswitch" > nova_compute_virt_type: "qemu" > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ > > > The following screenshot shown the tenant VM console(tty) where I am able > to ping floating IP(10.220.0.44 and its router ip 10.220.0.33 ) but > neither 10.220.0.51 the base VM ens224 IP nor ens192 10.17.16.128 > > > [image: image.png] > > > > krish > > On Tue, Feb 27, 2024 at 11:09 PM Eugen Block <eblock(a)nde.ag> wrote: > >> Hi, >> >> Check out this page: >> >> >> https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro… >> >> You need some sort of external network to provide connectivity for >> instances. >> >> Zitat von KK CHN <kkchn.in(a)gmail.com>: >> >> > List, >> > >> > I am a bit confused with the OpenStack Networking configuration for >> > Created virtual machines on a (Kolla-ansible all-in-one on an Ubuntu >> > 22.04 VM ) openstack installation. >> > >> > I am able to create virtual machines through the dashboard as well as >> CLI. >> > I have used the default network/cirros images created from init-runonce >> > script. >> > >> > But Real time, how can I configure these new VMs to communicate with Base >> > VM or external world by ping, ssh or make internet connection etc. >> > >> > Base VM is Ubuntu22.04 - with IPs ens192=>10.170.16.128(with Internet), >> > second interface => ens224 => 10.220.0.51 and ens160 up and running >> > without IP address for neutron_external_interface: >> > >> > All the VMs which I created getting IP addresses in series (10.0.0.X). >> > >> > But How to allocate Internet and make external world communication to >> and >> > from these VMs ? >> > >> > >> > Any hints/directions towards this much appreciated. >> > >> > Greetings, >> > Krish >> > >> > >> > If required more inputs here follows the additional information. >> > >> > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] >> /etc/kolla/globals.yml >> > --- >> > workaround_ansible_issue_8743: yes >> > config_strategy: "COPY_ALWAYS" >> > kolla_base_distro: "ubuntu" >> > openstack_release: "2023.1" >> > kolla_internal_vip_address: "10.220.0.24" >> > kolla_external_vip_address: "{{ kolla_internal_vip_address }}" >> > kolla_container_engine: docker >> > network_interface: "ens224" >> > neutron_external_interface: "ens160" >> > neutron_plugin_agent: "openvswitch" >> > nova_compute_virt_type: "qemu" >> > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ >> > >> > >> > >> > Additional inputs: >> > >> > There are 3 virtual interfaces on the base Ubuntu22.04 Virtual Machine. >> > ens192->10.170.16.128 with internet, ens224->10.220.0.51 , ens160 up >> > without IP >> > >> > 1. First Interface contain IP address from My organizations DHCP lease >> from >> > LAN(10.16.16.0) Which has Internet connectivity. >> > ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP >> group >> > default qlen 1000 link/ether 00:0c:29:33:18:3c brd ff:ff:ff:ff:ff:ff >> > altname enp11s0 >> > inet 10.170.16.128/23 brd 10.170.17.255 scope global dynamic >> noprefixroute >> > ens192 >> > valid_lft 786963sec preferred_lft 786963sec >> > inet6 fe80::cd1a:bc6c:b129:f91f/64 scope link noprefixroute >> > valid_lft forever preferred_lft forever3 >> > >> > >> > 2. Interface I have 10.220.0.51 >> > >> > ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP >> group >> > default qlen 1000 >> > link/ether 00:0c:29:33:18:46 brd ff:ff:ff:ff:ff:ff >> > altname enp19s0 >> > inet 10.220.0.51/24 brd 10.220.0.255 scope global noprefixroute >> ens224 >> > valid_lft forever preferred_lft forever >> > inet 10.220.0.24/32 scope global ens224 >> > valid_lft forever preferred_lft forever >> > inet6 fe80::a8b6:f094:c47:8282/64 scope link noprefixroute >> > valid_lft forever preferred_lft forever >> > >> > 3. ens160 without any IP address which is up and running configured for >> > Kolla neutron_external_interface: "ens160" >> > >> > ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master >> > ovs-system state UP group default qlen 1000 >> > link/ether 00:0c:29:33:18:32 brd ff:ff:ff:ff:ff:ff >> > altname enp3s0 >> > >> > >> > >> > 1. What networks need to be created additionally ? >> > 2. Bridges and bonds required here or not ? >> > >> > 3. To enable these New VMs to talk to external world( ssh, ping, internet >> > connection to all these VMs ) what all the steps need to be performed or >> I >> > left out ? >> >> >> >>

1 0

[oslo][release][requirement] FFE request for oslo.context
by Takashi Kajinami 29 Feb '24

29 Feb '24

Hello, I'd like to request an exception to merge a change[1] to oslo.context and create a new stable/2024.1 release. This change is required to fix the problem which is current blocking us from bumping oslo.messaging to the final 2024.2 release version (14.7.0)[2]. The change is small and has quite limited impact. I've tested the modification locally and confirmed it fixes the heat unit tests. [1] https://review.opendev.org/c/openstack/oslo.context/+/910153 [2] https://review.opendev.org/c/openstack/requirements/+/909906 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 4

[magnum] Dropping default Cluster API driver
by Mohammed Naser 28 Feb '24

28 Feb '24

Hi everyone, It seems that based on a recent post that I saw on the Twitter-sphere[1], it seems that the Magnum team has decided to move forward with setting a default driver for the Cluster API. I don't agree with this. Unfortunately, we don't have much recordings of our PTG conversations, and since the notes on the PTG are pretty light[2], I don't see any details of that. I don't see why we should be merging a native Cluster API driver and not allowing the operators and deployment tools decide which one they want to support. Personally, I think that the Helm driver should be built in a separate repository and then installed by the user as a Python package once they understand what are the backends and their options, as opposed to shipping one out of the box with far less features. We already have successful users which are using our implementation in production that have also posted blogs and shared their experience, we'd be doing them a disservice by now announcing a 'native' built-in driver. Can the decision be changed so that there is no built-in driver, and you must decide to install one yourself? Also, I would be really happy to hear feedback from users of the driver for their comments here. Thanks, Mohmamed [1]: https://www.stackhpc.com/magnum-clusterapi.html [2]: https://etherpad.opendev.org/p/r.5b94a5a9dbf4e3bf8202b5e57cb93770

19 34

[ptl][election][trove] PTL candidacy for 2024.2
by chunyang wu 28 Feb '24

28 Feb '24

Hello everyone: I would like to announce my candidacy for PTL of the Trove project for the 2024.2 cycle. For the Dalmatian cycle, i'd like to focus on the following: * review the coming patches * Add more tempest tests * Add CI tests for the latest datastore(mysql, mariadb, postgresql) version * improve docs thanks wu.chunyang

2 2

[all][elections][tc] TC Election Campaigning Kickoff
by Ian Y. Choi 28 Feb '24

28 Feb '24

Developers, The TC Election Campaigning Period has now started[1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms[2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform[2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. [1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/2024.2/…

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Nominations End
by Ian Y. Choi 28 Feb '24

28 Feb '24

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 11 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Ec2_Api, Freezer, Kuryr, Murano, OpenStack_Charms, Sahara, Senlin, Skyline, Solum, Trove, Watcher There are 0 projects that will have elections: . -- TC Election Details -- The official candidate list is available on the election website[1]. Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Mar 06, 2024 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#2024.2-ptl-candidates [1] https://governance.openstack.org/election/#2024.2-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

Ansible performance
by Gk Gk 28 Feb '24

28 Feb '24

Hi, Is there any way to speedup the playbooks execution of openstack ansible ? Can we remove gather facts for any tasks without affecting the installation ?

5 4

Ansible variables
by Gk Gk 28 Feb '24

28 Feb '24

Hi, We have an OSA setup. During a service playbook, for example, say rabbitmq, which task or play is responsible for creating it's haproxy configuration ? I mean, where is the code in openstack ansible to say to gather the values from user_variables file for that particular service or gather it from conf.d ? For instance, for rabbitmq service, where is the code which says to get the rabbitmq management port for the backend to be 15671 ? I mean where is the source code for pulling it from user_variables file and also which variable from it ?

3 2

[ptl][election][barbican] PTL Candidacy for 2024.2
by Grzegorz Grasza 28 Feb '24

28 Feb '24

Hello, I would like to propose my candidacy for Barbican PTL in the 2024.2 cycle. I've been the PTL since Antelope and I would like to continue to contribute in this role. As in the past cycles, I will continue to focus on Barbican maintenance and stability. Thanks you for your consideration, Grzegorz Grasza (xek)

1 0

[election][cloudkitty] PTL candidacy for the 2024.2 release cycle
by Rafael Weingärtner 28 Feb '24

28 Feb '24

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the 2024.2 release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/910519 -- Rafael Weingärtner

1 0

[ptl][election][keystone] PTL Candidacy for 2024.2
by Dave Wilde 28 Feb '24

28 Feb '24

Hello, I would like to continue my tenure as PTL of Keystone. Over the past cycle we have made some great progress especially around the cadence in getting patches reviewed and merged. I would like to focus this next cycle on seeing that [1] is implemented as well as some much needed backlog cleanup. I would also, finally, like to get a "known-issues" section added to the documentation as well as ensuring that our documentation is up to date. Thanks for your time and support and I'm looking forward to another great cycle. [1]: https://specs.openstack.org/openstack/keystone-specs/specs/keystone/2024.1/… /Dave

1 0

TC Candidacy
by Amy Marrich 28 Feb '24

28 Feb '24

I am declaring my candidacy for the Technical Committee. I currently serve on the TC and have contributed to multiple projects over the years within OpenStack as well as being an operator which I feel gives me a well rounded view of what makes OpenStack and how the pieces should work together and what the users need. I feel I represent all members of the community from the small private clouds to the teams running large public clouds. I also feel my experiences helping with OpenStack Upstream Institute, OpenStack OPS Meetup team, the OpenStack mentoring program, and the Git and Gerrit workshops help me to connect with contributors from those just starting out to those who have been here from the beginning. My main goal for rejoining the TC is to take my experiences with Operators and making sure they have a voice within the our decisions so that we can better meet the needs of our users. Thanks, Amy Marrich (spotz)

1 0

[ptl][election][kuryr] PTL non-candidacy for 2024.2
by Roman Dobosz 28 Feb '24

28 Feb '24

Hello, I'm not going to run for PTL of Kuryr for Dalmation. I encourage Kuryr contributors to run for PTL and will offer any assistance needed for whoever is elected. Thanks, Roman Dobosz (gryf)

1 0

[election][tc] Candidacy for the TC
by James Page 28 Feb '24

28 Feb '24

Hi All, I'd like to announce my candidacy for the Technical Committee. For those of you who do not know me, I've been involved with OpenStack from the very early days of the project. I've attended many OpenStack summits and Project Teams Gatherings over the years and have been privileged to help the project grow from its small beginnings to the established cloud platform that it has now become. I was the main driver behind migration of the OpenStack Charms to its current home as an official OpenStack project which I then led for many cycles as PTL and I remain an active core developer on this project. I'm the current PTL of Sunbeam which was accepted into OpenStack last year as a new incubating project, providing a reboot of the charmed approach to deploying OpenStack utilising the many new projects that have appeared since we started the OpenStack Charms project back in 2011. I also work as part of the team responsible for the packaging and distribution of OpenStack as part of Ubuntu. I have been a member of the TC for the last year providing a voice from a deployment tooling and distribution perspective. I would like the opportunity to continue in this role providing what I believe is a valuable perspective to the technical governance of the OpenStack project. In particular I think we need to address some of the challenges around the general health of wider ecosystem dependencies of OpenStack to ensure that we move forward onto a stable base benefiting operators, distributors and developers. Thank you for taking the time to consider my candidacy for this role. Regards James Page (irc:jamespage)

1 0

[puppet][murano] Retiring puppet-murano
by Takashi Kajinami 27 Feb '24

27 Feb '24

Hello, As you may know, TC decided to exclude Murano from 2024.1 release because of its health status[1]. Based on this fact, and also another fact that puppet-murano has had no real development activities for long, I'd propose retiring puppet-murano now. It may be too late to make release deliverable decision. However our puppet modules are tightly coupled with openstack release cycles and we can't assure compatibility between our modules and inactive components, which are no longer aligned with the consistent release cycle. Please let me know if you have any concerns. Thank you, Takashi [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[ptl][election][sunbeam] PTL candidacy for 2024.2
by Hemanth N 27 Feb '24

27 Feb '24

Hello OpenStack Community, I am nominating myself for the Sunbeam PTL position during the 2024.2 cycle. I am a core team member of the Sunbeam project from the incubation stage and contributed to most of the charms that are part of the sunbeam project. In the last cycle we focussed on moving the 20+ charm repo's to a mono repo which helped reduce the codebase and easy maintenance of all the sunbeam charms. In the 2024.2 cycle, my priorities will be * Adding new features or charms and filling gaps to enable charms to be production ready * Stabilise the existing charms or libraries * Bug smashing * CI stability Thank you for your support. Best Regards, Hemanth Nakkina (hemanth, hemanth.nakkina(a)canonical.com)

1 0

Tim Burke candidacy for Swift PTL
by Tim Burke 27 Feb '24

27 Feb '24

I'm pleased to announce my candidacy for Swift PTL for the Dalmation cycle. As usual, we have a great many projects currently in flight: - Supporting Python 3.12 - Adding more fine-grained metrics, while keeping it configurable to not break existing metrics pipelines nor overwhelm them - Improving S3 compatibility, enabling a broader community of tools to work out of the box - More operator tooling for expiring objects - Better process management for WSGI servers - Backend ratelimiting to improve per-node load shedding I'm excited to see how each of these will move forward over the next cycle. Tim Burke

2 1

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Nominations Last Days
by Ian Y. Choi 27 Feb '24

27 Feb '24

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 28, 2024 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2024-02-14 23:45:00 UTC Nominations end @ 2024-02-28 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 23:49:45 Nominations progress : 92.91% --------------------------------------------------- Projects[1] : 47 Projects with candidates : 30 ( 63.83%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 17 (Barbican Cloudkitty Ec2_Api Freezer Glance Keystone Kuryr Magnum Murano OpenStackAnsible OpenStack_Charms Sahara Senlin Skyline Solum Trove Watcher) --------------------------------------------------- TC Candidates : 7 (5 Required) =================================================== Stats gathered @ 2024-02-27 23:55:15 UTC This means that with approximately 2 days left, 17 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[ptl][election][cinder] PTL candidacy for 2024.2
by Jon Bernard 27 Feb '24

27 Feb '24

Hi All, I would like to announce my candidacy for PTL of the Cinder project for the 2024.2 cycle. I think Rajat has done an excellent job serving the project and I would like to carry existing efforts forward while continuing to focus maintaining a healthy and productive community around the Cinder project. I've been contributing to the Cinder project in varying capacity for close to 10 years. I've worked on migration and replication at the driver layer, mentored new contributors from the outreachy project, and provided bug fixes and reviews wherever possible. I'm a core reviewer and also a stable core. I have served as the release liaison for the last 2 cycles and run a weekly bug squashing meeting to help maintain our launchpad backog. We continue to face review bandwidth pressure. Emphasis should be placed on encouraging contributors to do code reviews and to recognize the efforts of those currently participating. There are several potential core reviewers and I feel that empowering the community is one way to increase engagement and the quality of our releases. 3rd party CI continues to be crucial resource for evaluating driver-specific changes. Maintaining good 3rd party CI for the drivers supported in Cinder by providing clear documentation and requirements will be a focus. Additionally, we have room for improvement in our backup and restore use case. My goal is to improve the entire backup/restore situation so that it can be leveraged by users in production environments. Our customers are using 3rd party backup products to backup workloads and volumes and I think this is one are where improvements here can directly benefit users. In summary, I would like to continue the efforts made by Rajat and continue to focus the areas most in need of attention for the 2024.2 cycle. I will do my best to make a positive contribution to both the technical and community aspects of Cinder during my time as PTL. Thank you for your consideration. -- Jon Bernard (jbernard)

1 0

Enabling external connectivity to VMs
by KK CHN 27 Feb '24

27 Feb '24

List, I am a bit confused with the OpenStack Networking configuration for Created virtual machines on a (Kolla-ansible all-in-one on an Ubuntu 22.04 VM ) openstack installation. I am able to create virtual machines through the dashboard as well as CLI. I have used the default network/cirros images created from init-runonce script. But Real time, how can I configure these new VMs to communicate with Base VM or external world by ping, ssh or make internet connection etc. Base VM is Ubuntu22.04 - with IPs ens192=>10.170.16.128(with Internet), second interface => ens224 => 10.220.0.51 and ens160 up and running without IP address for neutron_external_interface: All the VMs which I created getting IP addresses in series (10.0.0.X). But How to allocate Internet and make external world communication to and from these VMs ? Any hints/directions towards this much appreciated. Greetings, Krish If required more inputs here follows the additional information. (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes config_strategy: "COPY_ALWAYS" kolla_base_distro: "ubuntu" openstack_release: "2023.1" kolla_internal_vip_address: "10.220.0.24" kolla_external_vip_address: "{{ kolla_internal_vip_address }}" kolla_container_engine: docker network_interface: "ens224" neutron_external_interface: "ens160" neutron_plugin_agent: "openvswitch" nova_compute_virt_type: "qemu" (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ Additional inputs: There are 3 virtual interfaces on the base Ubuntu22.04 Virtual Machine. ens192->10.170.16.128 with internet, ens224->10.220.0.51 , ens160 up without IP 1. First Interface contain IP address from My organizations DHCP lease from LAN(10.16.16.0) Which has Internet connectivity. ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0c:29:33:18:3c brd ff:ff:ff:ff:ff:ff altname enp11s0 inet 10.170.16.128/23 brd 10.170.17.255 scope global dynamic noprefixroute ens192 valid_lft 786963sec preferred_lft 786963sec inet6 fe80::cd1a:bc6c:b129:f91f/64 scope link noprefixroute valid_lft forever preferred_lft forever3 2. Interface I have 10.220.0.51 ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0c:29:33:18:46 brd ff:ff:ff:ff:ff:ff altname enp19s0 inet 10.220.0.51/24 brd 10.220.0.255 scope global noprefixroute ens224 valid_lft forever preferred_lft forever inet 10.220.0.24/32 scope global ens224 valid_lft forever preferred_lft forever inet6 fe80::a8b6:f094:c47:8282/64 scope link noprefixroute valid_lft forever preferred_lft forever 3. ens160 without any IP address which is up and running configured for Kolla neutron_external_interface: "ens160" ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:0c:29:33:18:32 brd ff:ff:ff:ff:ff:ff altname enp3s0 1. What networks need to be created additionally ? 2. Bridges and bonds required here or not ? 3. To enable these New VMs to talk to external world( ssh, ping, internet connection to all these VMs ) what all the steps need to be performed or I left out ?

2 1

Re: Use Openstack SDK for Swift
by gtema 27 Feb '24

27 Feb '24

> I didn't see a response to this email so I am re-sending. That's interesting because I responded. My Email client decided by default to respond to a single person dropping discuss, but response to you went out. Anyway, reposting my answer On Thursday, 22 February 2024 12:11:31 CET you wrote: > Hey > > this is a tricky thing explained by a single auth concept: in OpenStack when > you connect to the cloud as a regular user you request certain scope which > normally grants you access to the single domain or the project. Moreover > with this authorization you get list of endpoints you can communicate with > and for Swift this is a project bound endpoint that look somehow like > https:// swift.example.com/v1/AUTH_<project_id>. But the "AUTH_" part may > be actually different since it is part of the swift config. If you are an > admin the situation is a bit different > > In summary that means that you want to do something in the way the API was > not designed for. > > Solutions: > > generally first question you must address is the authorization: is your user > able to access containers of different projects or not. If not you have no > chance and you need to establish new connection with another credentials > When the answer is "yes" you have some options: > > - switch your authorization using > https://opendev.org/openstack/openstacksdk/ > src/branch/master/openstack/cloud/openstackcloud.py#L123. That gives you > new session for a different project that you can use in scope of a certain > project > > - use you single session for pure API calls. This has a disadvantage that > you have raw API communication and need to do lot of tricky things yourself > ``` > conn.get("../AUTH_<another_project_id>/") > ``` > > Unfortunately there is nothing else what could help you, but even with > alternative API wrappers you have the same issue. > > Hope this helps, > Artem > > On Tuesday, 20 February 2024 21:59:19 CET Albert Braden wrote: > > I'm writing a script that will use admin credentials to check user > > projects > > for containers. I'm already doing something similar for non-swift > > accounts, > > doing things like: > > > > cloud.network.networks(project_id=projectid): > > > > I read here about the Object SDK: > > > > https://docs.openstack.org/openstacksdk/latest/user/guides/object_store.ht > > ml > > > > And I tried this: > > > > cloud.object_store.containers(project_id=projectid): > > > > But I get an error: > > > > Invalid query params: project_id > > > > I read the Object SDK document here and it doesn't seem to say anything > > about how to specify a project: > > > > https://docs.openstack.org/openstacksdk/latest/user/proxies/object_store.h > > tm l > > > > But when I read the Swift API document, I see that I can use > > "/v1/{account}/{container}", so I'm guessing that there must be a way to > > do > > it via the SDK. > > > > https://docs.openstack.org/api-ref/object-store/#show-container-details-an > > d-> list-objects > > > > Is it possible to specify the project in an Object SDK call, or do I need > > to use the old python API for this?

2 1

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

27 Feb '24

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (tomorrow) will be held in video + IRC mode with the following details: Date: 28th February, 2024 Time: 1400 UTC Meeting link: https://meet.google.com/xqc-ekpa-dao IRC Channel: #openstack-meeting-alt Make sure you're connected to both the gmeet meeting and IRC. Thanks Rajat Dhasmana

1 0

[Kolla][Ironic] Ironic inspector ignore BareMetal node mac address
by Jayesh5.Chaudhari＠ril.com 27 Feb '24

27 Feb '24

Hi All, I have implemented ironic in my kolla ansible yoga cloud. When I am adding new BareMetal node, it's getting added successfully. But the ironic inspector put the ignore label in the data directory in front of its mac address. I tried to remove it manually, but inspector immediately reverted it. Please help me, how I can proceed from here? Thanks, Jayesh "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."

2 1

Reg Snapshot
by Rohit Sansiya 27 Feb '24

27 Feb '24

Hii all, I am trying to upload a volume to an image but it has uploading as a snapshot but I want to upload my snapshot to an image "type". how to do that help me asap through cmd or openstack dashboard please help Your message is ready to be sent with the following file or link attachments: Rohit Sansiya https://sites.google.com/view/rpgcloud/research-india Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

2 1

[tc][elections] Candidacy for the TC
by gtema 27 Feb '24

27 Feb '24

Hi All, I'd like to announce my candidacy for the Technical Committee. I have never applied for a TC seat so far and decided to do it this time. My relations with OpenStack started not terribly long ago, on the other side 6 years are also not less in my eyes. During that time I became PTL for OpenStackSDK/CLI (and to some extend OpenStack Ansible Modules). I think many of you have noticed my strong push to improve the user experience of OpenStack users. For that I took the PTL role over all those mentioned projects which are focused primarily on the users. You may have noticed my push on introduction of the OpenAPI to the whole OpenStack with the intention to serve those who work with OpenStack. What I currently observe is that there are a lot of representatives and voices from maintainers and operators in TC, but since combining of the TC and User Committee focus end users voice slowly disappeared. That is why I decided to apply for Technical Committee to ensure this aspect is not forgotten. Some of you know me as a "maker" and not as a "talker", so this position is not going to be trivial for me, but I believe it is necessary to have engineers and architects in the politics otherwise laws are just serving wrong targets. My stand point is that policies should not hinder the progress, but instead we should make policies that serve ourselves to be efficient and successful. OpenStack is not existing to keep maintainers happy, but because someone (operators and users) needs it. So let us focus on that. Thank you for considering my candidacy, Regards, Artem (irc: gtema)

1 0

[ironic] Control Power using PoE?
by Kai Jellinghaus 26 Feb '24

26 Feb '24

Hello, I'm looking into using ironic to control a bunch of low-power compute. I'm wondering whether it'd be possible, or even the right approach, to control power states via the PoE switch. This would only allow completely cutting off power, and I'm not sure that's the right kind of control for ironic. I'd combine this with PXE/iPXE, but the way I understand ironic that shouldn't make a difference. Has anyone worked with PoE? Is that even a reasonable approach? Kind Regards, Kai Jellinghaus

1 0

[ptl][election][horizon] PTL candidacy for 2024.2
by Tatiana Ovchinnikova 26 Feb '24

26 Feb '24

Hi all, I would like to announce my candidacy for PTL of the Horizon project for the 2024.2 (Dalmatian) cycle. During the Caracal cycle we did a great job on integration tests improvement, feature implementation, bug fixing, and have completed migration from Django 3.2 to Django 4.2. For the Dalmatian cycle, I would like to focus on the following: * Continue working with feature gap, * Switch from current integration tests to new pytest-based selenium tests, * Switch to OpenSDK * Triage more bugs * Involve more contributors into the community. Thank you for your consideration. Tatiana Ovchinnikova (tmazur)

1 0

[ptl][election][neutron] PTL candidacy for 2024.2
by Brian Haley 26 Feb '24

26 Feb '24

Hello Openstack Community, I am writing to submit my candidacy for the Neutron PTL position during the 2024.2 cycle, continuing in my role from the 2024.1 cycle. A lot of my priorities as PTL are the same as the 2024.1 cycle: * Always make sure the stable branches are consumable downstream. With the introduction of unmaintained branches, the community has extended the lifecycle in a new direction. As a member of the downstream community that relies on these branches, I will continue to dedicate part of my time to reviewing backports and keeping them maintained. * Continue pursuing CI stability. * Keep working on ongoing specs. We did a good job of getting some of the larger specs done this cycle, but there are still a few in our review pipeline. I would set a goal to get these completed next cycle if they fail to make 2024.1: ** Active-active L3 Gateway with Multihoming (LP #2002687) ** Multiple back-end support for L3 routers in ML2/OVN (LP #2020823) * Reduce the bug backlog. Over the past cycle we were able to keep our bug backlog constant through the continued great work of a lot of contributors. Having a reduction, either through verification or bug fixes, would be one of my goals. * Making sure we are good stewards of gate resources. * Always welcome new contributors. Thanks for your support. -Brian Haley (haleyb, haleyb.dev(a)gmail.com)

1 0

[tc] Next Technical Committee meeting Feb 27
by Jay Faulkner 26 Feb '24

26 Feb '24

Hi all, The next TC meeting will be February 27 at 1800 UTC in #openstack-tc on OFTC. The proposed agenda is below. Agenda - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - Testing runtime for 2024.2 release (gmann) - https://review.opendev.org/c/openstack/governance/+/908862 - Murano inactivity and Caracal release - Should https://review.opendev.org/c/openstack/governance/+/908859/ be landed with/without the release removal change? - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - Open Discussion and Reviews Thanks, Jay Faulkner OpenStack TC Chair

1 0

[kolla][octavia][ovs] networking issue with dhcp-agent namespace
by Satish Patel 26 Feb '24

26 Feb '24

Folks, All my deployment is running on OVN and things are working great with octavia and its special lb-mgmt-net working. Recently I am deploying a new cloud using the OVS network plugin and found dhcp-agent namespace not pinging because I have a similar IP address configured on the host interface. My LBaaS nic /etc/netplan/00-network.yml ... ... # OS1_LBAAS bond0.15: id: 15 link: bond0 dhcp4: false dhcp6: false mtu: 1500 addresses: [ 192.168.32.201/24 ] Controller node interface # ifconfig bond0.15 bond0.15: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.32.201 netmask 255.255.255.0 broadcast 192.168.32.255 inet6 fe80::b489:8ff:fe61:2298 prefixlen 64 scopeid 0x20<link> ether b6:89:08:61:22:98 txqueuelen 1000 (Ethernet) RX packets 1074073 bytes 54067608 (54.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1594 bytes 78172 (78.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 octavia DHCP agent namespace (lb-mgmt-net) # ip netns exec qdhcp-1008bdd3-372a-44af-8fd3-00fb99b8e489 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 13: tape6186f5a-40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:c7:bf:2d brd ff:ff:ff:ff:ff:ff inet 192.168.32.10/24 brd 192.168.32.255 scope global tape6186f5a-40 valid_lft forever preferred_lft forever inet 169.254.169.254/32 brd 169.254.169.254 scope global tape6186f5a-40 valid_lft forever preferred_lft forever My global.yml ################### # Octavia options ################### enable_octavia: "yes" octavia_network_interface: "bond0.15" octavia_amp_flavor: name: "amphora" is_public: no vcpus: 2 ram: 2048 disk: 5 octavia_amp_network: name: lb-mgmt-net provider_network_type: vlan provider_segmentation_id: 15 provider_physical_network: physnet1 external: false shared: false subnet: name: lb-mgmt-subnet cidr: "192.168.32.0/24" allocation_pool_start: "192.168.32.10" allocation_pool_end: "192.168.32.100" no_gateway_ip: yes enable_dhcp: yes When I ping from namespace to controller machine LBaaS interface I am not able to ping # ip netns exec qdhcp-1008bdd3-372a-44af-8fd3-00fb99b8e489 ping 192.168.32.201 PING 192.168.32.201 (192.168.32.201) 56(84) bytes of data. ^C --- 192.168.32.201 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2039ms Seems like standard linux arp/kernel issue. How does it work? In OVN there is no namespace so everything works fine but in OVS because of namespace it doesn't work.

1 0

[ptl][election][manila] PTL candidacy for 2024.2
by Carlos Silva 26 Feb '24

26 Feb '24

Hello, I would like to announce my candidacy for the role of Manila PTL during the 2024.2 cycle. I have been serving as PTL to this amazing community for 4 cycles, and I would like to continue serving as PTL. With the brilliant work of the Zorillas, we managed to make great progress on several community wide efforts, and deliver good quality features and fixes that will for sure enhance the usability and stability of the features. For the next cycle, I would like to focus on: * Working with the contributors to harden the security of our code base by ensuring we have proper testing on CI, and working on security related tech debt such as the rootwrap migration to privsep. * Engaging contributors to assist in the completion of the integration of Manila with OpenStack SDK and Barbican. * Working on the stability of our CI jobs and getting more test scenarios implemented in all Manila repositories. * Continue increasing the number of active reviewers through mentoring and creating more community engagement opportunities, such as: promoting hackatons, bug squashes and collaborative review sessions. Thank you for your consideration! Carlos da Silva IRC: carloss

1 0

[ptl][election][tacker] Yasufumi Ogawa candidancy for Tacker PTL
by Yasufumi Ogawa 26 Feb '24

26 Feb '24

Hi, I'd like to nominate myself for Tacker PTL for 2024.2 cycle. I've contributed to Tacker as a PTL since victoria release. In caracal cycle, we've improved Tacker for the 5G usecases including radio-access network and core network. We also contributed to O-RAN SC to provide Tacker as Service Management and Orchestration (SMO) which is a key feature of resource management in O-RAN architecture as a collaboration activity of OpenStack and O-RAN SC. In the next cycle, we'll continue to improve Tacker for container management required for vRAN usecases in addition to the features developed in caracal, such as advanced monitoring for large amount of vRAN apps, the latest container networking for performance or descriptor for container. Regards, Yasufumi (yasufum)

1 0

Re: [TC][openapi] Request for new projects under the OpenStack hat
by gtema 26 Feb '24

26 Feb '24

Reposting Sean's response with my answers > > > > > what i really dont wnat to see is going forward an api change to nova > > > woudl > > > also requrie the oepnapi schema be updated by submiting a patch to a > > > speratre repo. > > > so im fine with haveing schemas in the nova repo but im not ok with > > > having a https://opendev.org/openstack/openstack-openapi/ repo > > > > Please do not mix jsonschemas in services and the resulting OpenAPI spec > > file. > if we crate an openapi spec file i woudl like to use that for api validation > in the serveircies and i would like to ensure that the two never get out of > sync which is why i want to have the OpenAPI spec file be part of the > project. From your comments further down in the message I see where you are heading. From all the tooling and docs around OpenAPI you can see there are 2 different use cases of OpenAPI spec: 1. generation of the spec from current sources giving you freedom to use whichever underlying technology you want (Stephen's nova-spec change is also explicitly going this way) 2. using spec in the sources in the runtime a) query parameters + body validation b) request routing Those are actually very contradicting with each other. We need to align what exactly we are talking about and what is the scope of the change Your direction feels like (2.) about having devs to write a standalone spec and letting service consume it to implement the API in runtime (2b). This requires that either all services switch to single framework or we implement OpenStack-flavoured OpenAPI support into all of the currently used frameworks (or of course we again stuck with services doing absolutely different things) My proposal (1.) is to have spec generated supporting current zoo of frameworks used by services for request routing without devs needing to deal with OpenAPI directly. That requires us to ensure current jsonschemas and docstrings in the code are complete. Currently I see a tendency in other opensource projects that the bigger projects tend to go for 1. (with Kubernetes and GitHub being examples here) while smaller ones tend to choose 2. This can be explained by the additional complexity you get with maintaining manually the spec for huge services (my current compute OpenAPI spec is 46511 lines of code). Last, but not least, is the evolution of the OpenAPI standard itself forcing you to rewrite the spec time to time. This approach does not let you to consume openapi to route requests while it still allows you to have a test suite that would validate your service behaves like the spec describes. If we are on that level of discussion I really would like to see TC to get more actively into the discussion and we all agree and commit on a single way. > > > Anyway, I was thinking about such approach also. Issue, but not really > > critical for me, is that having schemas in various repos will make it > > harder for the user to actually grep them, unless we build a single page > > with links to all specs. > > > > In addition to that with the spec generated by a different tool we are > > going to have some workflow issue: schema is an artifact of a build and > > need to be hosted somewhere permanently. > > yep we can host it in the project docs sight. > besided the rendered api_ref. > we can also commit it to the git repo is if we want to. > i feel like not maing it the output of a build process also has advantages. > > > You would be having problem in having an API > > > > affecting change which during merge generates spec and this spec being > > submitted into the repo as well. > > i was not proposing having any generations of the schema and instead > modfiying them by hand when we are modifying the api to ensure the two > correalate and capture the intent of the api change. Ok, but this is exactly what I am proposing - generate spec from source code of services My analysis of the source code of services showed that there are much more things and bugs exposed then devs know/expect/want. Maintaining OpenAPI per hand is something people have problem with and is very error-prone with respect to OpenStack API nuances. > > Forcing devs to manually invoke the generator and include the spec into > > the > > change is definitely a very strong no-go for me, this will be a disaster. > > Pushing rendered specs to some artifacts server is necessary. > > well having external schema files is also a stong no-go form me but im > trying not to draw red lines and find a way forward. > > there are three thing i want to prevent. > i never want to have an external schema definition result in a client > rejecting a api call that should have been valid for a given cloud. > i don't want to maintain two diffent vallidation schmea for the apis (one in > the proeject and a second external) finally i dont want to have to do a > seperate release of a lib just to udpate the schema to be able to merge a > new api microversion or the reverses to require an update an external repo > after every api microversion. > > if we have the openapi sechma defs in nova we should not need to update the > openstack sdk when we have an api uidate and woudl only need to update > openstack client to use that new api. Agreed, as said - I am ok with not keeping the rendered spec part of different repository and wasn't under any means proposing to have a "lib" like repo with releases and so on. 3rd party "doc" repo can be used to link specs of different services together. One more time clarifying since I still feel we are not in sync about one technical aspect: jsonschemas of request bodies are and must be in the service repository, service router is exposing list of supported routes/methods with corresponding body jsonschemas. OpenAPI spec combines information about those exposed routes with their corresponding bodies and descriptions and applies standard on how to document microversions and actions (your router just shows that there is /"servers/{server_id}/action" url while you need to further define all the different actions and microversions). > > > In any case what is required is to have a sphinx-extension that allows us > > to generate docs for the schema and this repo is primarily is exactly > > about that (I have no issue renaming it to better indicate that fact). > > Just as a matter of temporary demonstration it also hosts the rendered > > specs. > > > > > > # My "ideal" workflow would look like that: > > > > - service developer creates change like above that changes the API > > so in my expected workflow the openapi spec file would be a file in the repo > that is updated and review as part of the normal review process > > > - Zuul job generates OpenAPI spec for the service respecting the change > > and > > publishes it together with job artifacts (just like docs right now) > > > > - Once a change is merged the OpenAPI spec artifact is published as a > > deliverable (just like doc job publishes built docs). Maybe the api-ref > > job > > can be modified to publish openapi spec and rendered HTML together > > i also think we should have a job to publish the spec file too but im not > sure we need to have any generation step outside of what we already do for > the api ref. > > - [from here absolutely speculatively] > > > > - another job kicks in and automatically proposes changes to projects that > > consume this OpenAPI spec (like a change toward the SDK is automatically > > opened that applies corresponding change) > > this gets a little dicey in terms of licensing as we currently have a policy > in openstack that all patches must be authored by a human who has signed > the icla with the exception of the depency bump patches so we would have to > make sure that any such patches dont fall foul of the guidance that > maintainer should not merge patches form AI bots > > in general any generated code not submitted by a human is problematic form a > copyright point of view and icla point of veiw which is partly why i woudl > prefer the spec update to be in the orginal patch to the project not > autogenerated via a job. This is not AI generated code. It is similar to a tooling that RM is using to open bunch changes to the projects (only difference is who triggers it: a human or Zuul as a result of another job). Here it is about rendering pre-defined templates with new values and automatically proposing that as a change. We control both the templates and the values. I really do not understand a point of discussion like in example when a job completely under your control is doing periodic check of new available dependencies versions following your update strategy and proposing an update once all tests are green. But I definitely do not want to move the discussion into the different aspect. It is not about that. Anyway, I hope we can address this aspect by adapting our policies where required or stop being productive in a fear of laws. > > > - dependent project developers review this automatic change and > > merge/modify it as necessary > > > > > > === openstack-rs > > > > https://gtema.github.io/openstack/ > > > > > > > > This is a Rust monorepo project with few items: > > > > - SDK for OpenStack out of the rendered OpenAPI specs > > > > - experimental CLI following very different approach compared to the > > > > python- openstackclient. It is compiled into single binary (what helps > > > > those not willing to pull whole python with all deps and the insanity > > > > we > > > > experience lately or those who build docker containers with only OSC > > > > inside to bypass the mentioned hell) and purely auto-generated from > > > > the > > > > specs > > > > - [future] openstack-tui (similar to k9s for Kubernetes) > > > > > > i was actully playing with rust and pyo3 to try and generate rust data > > > types form the jsonscheam defintion of novas oslo versioend objects > > > https://github.com/SeanMooney/nova-oxide thats mainly to paly with rust > > > and > > > rust<>python interaction in partarlary. > > > > > > i was toying with the idea of writing a deamon that coudl comuncitate > > > with > > > nova comonets over the rpc bus effectivly a rust implemetiaon of a > > > nova-comptue agent as way to learn rust. basically nova-comput ewould > > > need > > > effectivly a rewrite to remove our use of eventlet anyway so i was > > > toying > > > with the idea of if we are rewriting should we rewtien in something > > > other > > > then python. > > > > > > have you considerd using something like pyo3 to provide python binding > > > around a rust inmpelmation of the sdk to support both lanageues form a > > > singel codeabse. https://pyo3.rs/v0.20.3/ > > > > Yes, it is clearly possible and I am poking with idea of integrating > > generated code into the openstacksdk (at least in some parts like auth > > caching). > > > > I really think of having a new openstacksdk2 that is either also generated > > from specs or is under the hood uses the rust sdk. > > Changing the current OpenStackSDK would require huge breaking changes, so > > this is not in the scope right now. > > i think if we were to add rust to the supproted langugaes for openstack > projects then creating an openstack-sdk-rs project would make sense however > rust is not an appvoed lanague for use in offial project go, javascript adn > python are so for this to proceed in the openstack namespace you would need > to formally request rust be added via > https://github.com/openstack/governance/blob/master/reference/new-language-r > equirements.rst > > and we woudl have to defien a new rust pti likely targeting the rust stable > release. https://github.com/openstack/governance/tree/master/reference/pti Ouch, I completely missed when "Go" was added into that list. Right, and thus mentioning it here. At least now I see you are also thinking about usage of Rust so at least there are now 2 person and this can be triggered. If Rust is not accepted then my project will not be official OpenStack delivery. The real question is who wins in that case. > > > > > Here it is all really oriented only on the user facing tooling. I am > > > > very > > > > convinced in this project and will continue working on it independent > > > > on > > > > the outcome. > > > > > > > > Any objections/ideas/comments? > > > > > > yep see above. > > > mainly just decopleing the schmas form the implemation. > > > if we keep the schemas with the python code in the same repo or in a lib > > > repo provded by each service project > > > > I do not get the point here really. > > > > - Ideally every service is extending schemas already present in the code > > and adds descriptions directly into the code. > > - from schemas in the service code we are able to generate OpenAPI > > - the OpenAPI spec can be used to render API docs of the service > > - OpenAPI specs can be used to generate client facing (and possibly also > > server bindings) tooling (sdk, cli, etc) > > ideally from my point of view we would remove our custom jsonschma > validation and replace it with an openapi spec file then use something like > https://github.com/python-openapi/openapi-core?utm_source=openapi-tools&utm_ > medium=website&utm_campaign=data-validators to load the spec file form disk > and use it ot add server side request validation. i would really like the > nova api to be able to do somethign like > ``` > from openapi_core import OpenAPI > openapi = OpenAPI.from_file_path('openapi.json') > try: > result = openapi.unmarshal_request(request) > handel_request(request) > excpet ValidationError: > ... > ``` > > the current json schema validation we have is a custom intergartion and im > inclidned to consider it techdebt and look to replace it with a better > supported, purpose built project that we dont have to maintain long term... This is an absolutely valid approach (as also pointed above), but in my eyes would require much more work and will not work for all OpenStack services together without enforcement of OpenStack flavor of OpenAPI (same as you can't enforce all services to use same wsgi framework as of now or to follow the accepted API guidelines). As described my proposal is about going a less offensive way and allows us have "auto-documented" code what could be standardized across services while keeping the service's freedom to use whichever technology it prefers. That does not block any service from implementing service relying on the spec, but puts certain requirements on the form of the spec. N.B: what really surprises and disappoints me is general lack of any reaction in this thread as well as all previous attempts. Is it so unimportant ? Is it a fear of debate or just understanding that this is going to be another heated discussion without consensus? Is it something too big to do and thus let us not even start doing that? Is the community "died out" short in front of elections? Is it just waiting for somebody to break the "governance/policies/rules" wall we built between each other? Or am I the only one who thinks to see this issue? But that would not match to what others tell me directly. P.S. I re-read my message and assume some may feel offended by the tone. It is not really intended, so sorry in advance. Regards, Artem

1 0

[ptl][election] Sylvain Bauza candidacy for Nova 2024.1 PTL
by Sylvain Bauza 26 Feb '24

26 Feb '24

Hey Nova and Placement folks, Yet again, I'm asking you to put myself on the Nova and Placement PTL seat. I was awaiting to see whether new candidates were wanting to nominate themselves for that seat but now I am convinced to run again for this position. Challenges are still upfront. Our gate is still coughing every single day and despite the excellent work that a very few awesome people did on stabilizing and which helped improving the situation (kudos to those who will recognize themselves), we are still urging to fix the most common patterns. As a PTL, I'll ensure to keep the energy to chase those issues and identify them so as a team we can fight them. Another concern to me is the reviewing pace. While we're continuing to deliver solid reviews on feature proposals and patches, our team isn't much evolving and we need fresh blood. In order to be able to deliver things, we need to ensure that we properly recognize those who dedicate a portion of their daytime to help others by providing valuable feedback (and I stress on the fact that this feedback *has to* be valuable in order to by worthy). As a PTL, I'll continue to encourage people to express their thoughts and concerns into Gerrit comments so that we are able to count on. The last challenge I have to mention here is the release cadence. Now that we are about to deliver 2023.1 (Caracal), it will be time to remember ourselves that 2023.2 (Dalmatian) will be a skippable release for operators and we need to carefully think about the implications of such things. I'll just finish on a last word. While I really appreciated acting as a PTL for the last 5 cycles, I'd be more than happy if someone would like to step up next cycle (E) so I could offer some mentoring for a smooth transition. Thanks, -Sylvain

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Nominations Kickoff
by Ian Y. Choi 26 Feb '24

26 Feb '24

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 28, 2024 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2024.2/<Project_Name or "TC">/<email_address> (for example, "candidates/2024.2/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2023.2 to 2024.1 timeframe, Mar 03, 2023 00:00 UTC - Feb 28, 2024 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Mar 06, 2024 23:45 UTC through to Mar 20, 2024 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the 2023.2 to 2024.1 timeframe, Mar 03, 2023 00:00 UTC - Feb 28, 2024 00:00 UTC, as well as any Extra ACs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the 2023.2 to 2024.1 timeframe, Mar 03, 2023 00:00 UTC - Feb 28, 2024 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ACs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ACs. Please find below the timeline: PTL + TC nomination starts @ Feb 14, 2024 23:45 UTC PTL + TC nomination ends @ Feb 28, 2024 23:45 UTC TC campaigning starts @ Feb 28, 2024 23:45 UTC TC campaigning ends @ Mar 06, 2024 23:45 UTC PTL + TC elections start @ Mar 06, 2024 23:45 UTC PTL + TC elections end @ Mar 20, 2024 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2024-02-28 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 1

Re: [TC][openapi] Request for new projects under the OpenStack hat
by gtema 26 Feb '24

26 Feb '24

Ups, used wrong button and replied to Sean only, reposting my replies here directly > Hey, > > thanks for feedback > > see comments inline > > > > === openstack-openapi > > > https://gtema.github.io/openstack-openapi/ > > > > > > This repo hosts rendered specs and provides analogue to the os-api-ref > > > Sphinx extension that renders them into the html (what you see under the > > > link is a mix of Swagger and os-api-ref style). I was not really > > > effectively working on that rendering lately, the repo right now is more > > > or less a storage for the specs themselves with a first sketch of sphinx > > > extension of rendering and basic OpenAPI flavoring doc. > > > > i personally object to haveing a offical repo to define the open api > > scemas > > for offial projcet that scope of the relevent repo. > > > > i.e. i do not agree that we shoudl have openapi defintion for the nova api > > ourside of the nova repo or a repo that is not a deliverable of the > > comptue > > project. > > > > stephen has proposed a spec to add openapi support to nova directly > > https://review.opendev.org/c/openstack/nova-specs/+/909448 > > I was referring to that spec in the header of my email > > > what i really dont wnat to see is going forward an api change to nova > > woudl > > also requrie the oepnapi schema be updated by submiting a patch to a > > speratre repo. > > so im fine with haveing schemas in the nova repo but im not ok with having > > a https://opendev.org/openstack/openstack-openapi/ repo > > Please do not mix jsonschemas in services and the resulting OpenAPI spec > file. > > Anyway, I was thinking about such approach also. Issue, but not really > critical for me, is that having schemas in various repos will make it harder > for the user to actually grep them, unless we build a single page with > links to all specs. > > In addition to that with the spec generated by a different tool we are going > to have some workflow issue: schema is an artifact of a build and need to > be hosted somewhere permanently. You would be having problem in having an > API affecting change which during merge generates spec and this spec being > submitted into the repo as well. > Forcing devs to manually invoke the generator and include the spec into the > change is definitely a very strong no-go for me, this will be a disaster. > Pushing rendered specs to some artifacts server is necessary. > > In any case what is required is to have a sphinx-extension that allows us to > generate docs for the schema and this repo is primarily is exactly about > that (I have no issue renaming it to better indicate that fact). Just as a > matter of temporary demonstration it also hosts the rendered specs. > > > # My "ideal" workflow would look like that: > > - service developer creates change like above that changes the API > > - Zuul job generates OpenAPI spec for the service respecting the change and > publishes it together with job artifacts (just like docs right now) > > - Once a change is merged the OpenAPI spec artifact is published as a > deliverable (just like doc job publishes built docs). Maybe the api-ref job > can be modified to publish openapi spec and rendered HTML together > > - [from here absolutely speculatively] > > - another job kicks in and automatically proposes changes to projects that > consume this OpenAPI spec (like a change toward the SDK is automatically > opened that applies corresponding change) > > - dependent project developers review this automatic change and merge/modify > it as necessary > > > > === openstack-rs > > > https://gtema.github.io/openstack/ > > > > > > This is a Rust monorepo project with few items: > > > - SDK for OpenStack out of the rendered OpenAPI specs > > > - experimental CLI following very different approach compared to the > > > > > > python- openstackclient. It is compiled into single binary (what helps > > > those not willing to pull whole python with all deps and the insanity we > > > experience lately or those who build docker containers with only OSC > > > inside to bypass the mentioned hell) and purely auto-generated from the > > > specs > > > > > > - [future] openstack-tui (similar to k9s for Kubernetes) > > > > i was actully playing with rust and pyo3 to try and generate rust data > > types form the jsonscheam defintion of novas oslo versioend objects > > https://github.com/SeanMooney/nova-oxide thats mainly to paly with rust > > and > > rust<>python interaction in partarlary. > > > > i was toying with the idea of writing a deamon that coudl comuncitate with > > nova comonets over the rpc bus effectivly a rust implemetiaon of a > > nova-comptue agent as way to learn rust. basically nova-comput ewould need > > effectivly a rewrite to remove our use of eventlet anyway so i was toying > > with the idea of if we are rewriting should we rewtien in something other > > then python. > > > > have you considerd using something like pyo3 to provide python binding > > around a rust inmpelmation of the sdk to support both lanageues form a > > singel codeabse. https://pyo3.rs/v0.20.3/ > > Yes, it is clearly possible and I am poking with idea of integrating > generated code into the openstacksdk (at least in some parts like auth > caching). > > I really think of having a new openstacksdk2 that is either also generated > from specs or is under the hood uses the rust sdk. > Changing the current OpenStackSDK would require huge breaking changes, so > this is not in the scope right now. > > > > Here it is all really oriented only on the user facing tooling. I am > > > very > > > convinced in this project and will continue working on it independent on > > > the outcome. > > > > > > Any objections/ideas/comments? > > > > yep see above. > > mainly just decopleing the schmas form the implemation. > > if we keep the schemas with the python code in the same repo or in a lib > > repo provded by each service project > > I do not get the point here really. > > - Ideally every service is extending schemas already present in the code and > adds descriptions directly into the code. > - from schemas in the service code we are able to generate OpenAPI > - the OpenAPI spec can be used to render API docs of the service > - OpenAPI specs can be used to generate client facing (and possibly also > server bindings) tooling (sdk, cli, etc)

1 0

[neutron] Bug Deputy Report February 19 - 25
by Lucas Alvares Gomes 26 Feb '24

26 Feb '24

Hi, This is the Neutron bug report from February 19th to 25th. Only a few bugs this week. High: * https://bugs.launchpad.net/neutron/+bug/2054435 - "Testing errors when using new netaddr library" Unassigned Medium: * https://bugs.launchpad.net/neutron/+bug/2054324 - "Iptables rule wrong if created a rule with protocol 4" Assigned to: Brian Haley Needs further triage: * https://bugs.launchpad.net/neutron/+bug/2008238 - "SRIOV port binding_profile attributes for OVS hardware offload are stripped on instance deletion or port detachment" Unassigned Note re #2008238 <https://bugs.launchpad.net/neutron/+bug/2008238>, this bug is old and was originally assigned and fixed in Nova, reading the comments I see that Rodolfo has added Neutron to it with the following message: "Adding Neutron to this bug. A port extension could be needed to avoid writing in the port port_binding register when creating a port. That will avoid the Neutron policy restriction, that only allows to write on this field to service role." It seems like an enhancement on our side to avoid writing to the port's port_binding field directly. Perhaps this needs further triage or even a LP of its own. Cheers, Lucas

1 0

[elections][tc] Candidacy for the TC for 2024.2
by Sławek Kapłoński 26 Feb '24

26 Feb '24

Hi Stackers, I have been a member of the TC for the last 2 years and I would like to keep doing that for the next year. I have been an OpenStack contributor for many years now and have contributed to many different projects with primary focus on the OpenStack Neutron. As a member of the Technical Committee I am focusing on the day to day job to keep OpenStack projects in the healthy state and to make contributors' lives easier. I was helping to improve gate stability by e.g. monitoring rechecks made by contributors of the projects. I am also monitoring the overall state of the official OpenStack projects and helping less active ones to find new contributors and keep them running. I want to use my experience as a TC member and continue working in the TC in those areas for the next year. Thank you for considering my candidacy for the Technical Committee. -- Slawek Kaplonski (slaweq) Principal Software Engineer Red Hat

1 0

[openstack][skyline] Some works with skyline
by Nguyễn Hữu Khôi 25 Feb '24

25 Feb '24

Hello guys. I am working on Skyline. I can integrate my monitor tab on it. I will try to do something about it. If it works properly, I can contribute. It is a very nice project. I hope it will grow and grow in the future. Thanks Skyline Team. [image: image.png] Nguyen Huu Khoi

3 7

OpenStack on Production Servers : Few Queries
by KK CHN 24 Feb '24

24 Feb '24

List, I am going ahead to adopt OpensStack for our Live deployment sites which all are running previously on proprietary HCI solutions. *Few queries.* 1. Which base Operating System need to be selected for production? ( prefer OpenSource community Operating Systems.) Is Debian a good choice? If so, which version ? Or any other suggestions? 2. What backend / SDS needs to be configured for a crash resistant FaultTolerant cluster. In case of a node / Disks failure which can withstand the workload and most preferably avoid data loss in the worst case scenario. 3. Heard about Ceph. How its a best choice for a 24x7 mission critical cluster? kindly advise. If so, what configuration architecture needs to be considered ? 3. My luxury is only at an On Prem Server Cluster comprising a minimum 3 to max 4 Nodes. ( possible DELL 650 or 750 series OR HPE servers ) . 4. As my cluster resources are limited to 3 to 4 server nodes / site ( 2 X32C 64 Threads, Intel Xeon Gold processors, with min 512 GB Ram , 4 x3.94TB SSD or 8 x1.92TB in each node) Is it reliable/advisable to set Controllers, Compute and Storage all together in these three or four nodes? Which is the best possible deployment options I can have with these 3/4 nodes. Kindly shed some light . 5. Any other points need to be considered while this must be a reliable infrastructure for running a mission critical 24x7 operation. 6. Which mode of installation I can choose, the Kolla-ansible multinode is advisable for a production deployment ? ( I am familiar with the kolla-ansible all-in-one installation ) OR ther a better deployment method for production sites ? ) Kindly shed some light and your valuable suggestions . Any hints most welcome. Thank you, Krish

2 1

[kolla][magnum] Creating Magnum trustee user role
by Satish Patel 23 Feb '24

23 Feb '24

Folks, I am deploying magnum using openstack release 2023.1 but getting this error. But I have a similar deployment running in another datacenter which didn't give any error. What could be the problem? TASK [magnum : Creating Magnum trustee user] **************************************************************************************** ok: [os-eng-ctrl-01] TASK [magnum : Creating Magnum trustee user role] *********************************************************************************** fatal: [os-eng-ctrl-01]: FAILED! => {"action": "os_user_role", "changed": false, "extra_data": {"data": null, "details": "None", "response": "None"}, "msg": "Must specify either a user or a group"}

4 6

[release] Release countdown for week R-5
by Thierry Carrez 23 Feb '24

23 Feb '24

General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 29th, 2024. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2024.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 29th, 2024 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also a good time for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Caracal-3 milestone (feature freeze): February 29th, 2024 (R-5 week) Cycle Highlights Due: March 7th, 2024 (R-4 week) RC1 deadline: March 14, 2024 (R-3 week) Final RC deadline: March 28, 2024 (R-1 week) 2024.1 Caracal final release: April 3rd, 2024 Dalmatian PTG: April 8-12, 2024 -- Thierry Carrez (ttx)

1 0

[openstack-ansible][live migration/migration of Paused VM] Need to migrate Paused VM on different host.
by Danish Khan 23 Feb '24

23 Feb '24

Hello Team, Is it possible to live migrate or migrate VM which is in paused state? I have few VMs which are in paused state which I need to migrate to a different host. Regards, Danish Khan

2 1

[neutron][ovs] br-tun bridge setup
by Jaime Ibar 23 Feb '24

23 Feb '24

Hi all, I'm setting up neutron and ovs and I can't make br-tun work and pick up the ip address configured in openvswitch_agent.ini file. If I tcpdump br-tun tcpdump -l -n -i br-tun 'port 4789' I don't see any traffic getting through however(it goes through the physical interface) if I spin up a vm, it reaches the internet, I can ping it from another machine after allocating a floating ip but can't ssh into it. Can anyone please share the /etc/network/interfaces file configuration for br-tun? Should the br-tun ip address be configured on the bridge or in the physical interface the bridge is attached to? Should the vxlan traffic go through br-tun bridge? Thanks Jaime -- salu2 Jaime

3 5

PTG April 2024 Teams List
by Kendall Nelson 23 Feb '24

23 Feb '24

Hello Everyone! The April 2024 Project Teams List is official! Projects + Teams - OpenInfra Foundation Teams - - Diversity & Inclusion Working Group - OpenInfra Edge Computing Group - Kata Containers - OpenDev - StarlingX - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Magnum - Manila - Neutron - Nova - Octavia - OpenStackAnsible - OpenStack-Helm - OpenStackSDK/CLI - Quality Assurance - Release Management - Tacker - Other OpenStack Teams - - OpenStack Security SIG - OpenStack Technical Committee - PublicCloud SIG - RBAC - VDI If your team was planning to meet and isn’t on this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon, I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — it's FREE! As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://ptg2024.openinfra.dev/ <http://ptg2023.openinfra.dev/>

1 1

[election][ptl][sunbeam] non-candidacy for Sunbeam
by James Page 23 Feb '24

23 Feb '24

Hi All I'm not going to stand for PTL of the Sunbeam project for the upcoming cycle in order to allow others in the core dev team to stand for this position. Cheers James

1 0

[all][diversity] Final call for mentors and projects for the May 2024 Outreachy round
by Dmitry Tantsur 22 Feb '24

22 Feb '24

Hi folks, Sorry for the late heads-up. We don't currently have any projects submitted for OpenStack this cycle. If you have a project and would like to contribute to make the world a better place, please submit at https://www.outreachy.org/communities/cfp/openstack/ until tomorrow, Feb 23rd, 4pm UTC. Don't hesitate to reach out with any questions! Dmitry

1 0

[antelope][kolla-ansible][magnum]Multidomain problem
by Franck VEDEL 22 Feb '24

22 Feb '24

Hello I'm coming back to you with a new problem, which has already been submitted. I thought it worked with Antelope but maybe not. I have a kolla-ansible installation, antelope, on Ubuntu22.04, multinode. everything works as I want. If I leave only one domain (Default), I add heat and magnum. This works (with /etc/kolla/config/magnum.conf and cluster_user_trust = True). I add a second domain (users from an Active Directory). And there, adding magnum no longer works. When I do a "kolla-ansible reconfigure.....), I get the error: "action": "os_user_role", "changed": false OK, a search gives me this link: https://github.com/ansible/ansible/issues/57099 But I'm in the antelope version. Is this problem still relevant? How can we solve it? Thanks for your advices. Franck.

1 0

kolla-ansible all in one reconfigure fails
by KK CHN 22 Feb '24

22 Feb '24

I have a kolla-ansible all-in-one openstack installation working on a Virtual Machine (Ubuntu22.04 on a ESXi 7.0 host) Reference: https://kifarunix.com/create-and-upload-custom-linux-image-into-openstack/?… All went well and able to get the horizon dashboard and default Cirros image and demo networks up and running. Able to create instances using the default image. To create cloud OS images from the ISO files , I have done additionally the following iinstallation in the same Ubuntu22.04 VM . STEP 1. *$ sudo apt install -y qemu-kvm virt-manager libvirt-daemon-system virtinst libvirt-clients bridge-utils* $ sudo systemctl enable --now libvirtd $ sudo systemctl start libvirtd Everything went well. I am able to get virt-manager up and running and able to create the Cloud Image from an Ubuntu22.04 Server ISO. Then I uploaded this cloud image to the All-IN-ONE kolla-ansible openstack horizon dashboard, the image creation was successful. 2. But when I tried to create an instance by using this image through the horizon dashboard the instance dialog doesn't show any availability zone (nova). I am sure before doing the step 1 I am able to create Linux instances using the default Cirros image multiple times and the instances up and running successfully with the default availability zone "nova" ( I mean kolla-ansible all-in-one openstack installation was working fine before doing the step 1). But now there is no availability zones showing in horizon for creating new instances. Availability Zone There are no Availability Zones. I checked in CLI also $ openstack hypervisor list //it also shows ( down) availability zones also down 3. So I decided to reconfigure the $ kolla-ansible -i all-in-one reconfigure step, but the step fails with the following. RUNNING HANDLER [nova-cell : Restart nova-ssh container] *********************** changed: [localhost] RUNNING HANDLER [nova-cell : Restart nova-libvirt container] ******************* changed: [localhost] RUNNING HANDLER [nova-cell : Checking libvirt container is ready] ************** FAILED - RETRYING: [localhost]: Checking libvirt container is ready (10 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (9 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (8 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (7 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (6 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (5 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (4 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (3 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (2 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (2 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (1 retries left). fatal: [localhost]: FAILED! => {"attempts": 10, "changed": true, "cmd": "set -o pipefail && docker exec -i nova_libvirt ls /run/libvirtd.pid\n", "delta": "0:00:00.016249", "end": "2024-02-21 16:21:22.750454", "msg": "non-zero return code", "rc": 1, "start": "2024-02-21 16:21:22.734205", "stderr": "Error response from daemon: container 46d139a236f57e41cfcf3121b3879ea01eae774d771415c5418b003c839f3257 is not running", "stderr_lines": ["Error response from daemon: container 46d139a236f57e41cfcf3121b3879ea01eae774d771415c5418b003c839f3257 is not running"], "stdout": "", "stdout_lines": []} Each time I do reconfigure, the reconfiguration fails by reaching the step RUNNING HANDLER [nova-cell : Restart nova-libvirt container] ******************* changed: [localhost] 4. Why it fails, what the root cause of it, I suspect due to step 1 all the errors happened . 4. How can I recover the all-in-one openstack installation back and be able to create instances and images as earlier? Only option is to fresh deploy the kolla-ansible -i all-in-one ? Then all the current VM and images will all be lost ? ( If it in production what the method is to recover ?? OR will loss all data in production by running deployment again ? ) Greetings, Krish

1 1

[manila] Collab Review discussion for Snapshot/Replication based backups for NetApp shares and Generic solution for human readable export locations
by Saravanan Manickam 21 Feb '24

21 Feb '24

Hello Zorillas and other interested stackers, We'll have collab review discussion on a couple of features the NetApp team is building in Caracal release. * Snapshot/Replication based backups for NetApp shares (Gireesh Awasthi) * Generic solution for human readable export locations and relevant implementation for NetApp and LVM drivers (Jayaanand Borra) Date: 22nd February 2024 Time: 1400 UTC https://etherpad.opendev.org/p/ptg-backup-manila https://etherpad.opendev.org/p/manila-share-backup <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fetherpad.…> https://etherpad.opendev.org/p/caracal-ptg-manila-human-readable-export-loc… Zoom: https://netapp.zoom.com/j/96908608436?pwd=aCtNSngxMWVTVlV6Ykx6OW85UDZndz09 Thanks, Saravanan

1 0

[largescale-sig] Next meeting: February 21, 16utc
by Thierry Carrez 21 Feb '24

21 Feb '24

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

1 1

Cinder Bug Report 2024-02-21
by Jon Bernard 21 Feb '24

21 Feb '24

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - IBM SVf : Enable support for force detach of a volume <https://bugs.launchpad.net/cinder/+bug/2054317> - Status: New Thanks, -- Jon

1 0

[keystone] Weekly meeting canceled 21-Feb-24
by Dave Wilde 21 Feb '24

21 Feb '24

Hi folks, Due to a family emergency I’m not able to host the keystone weekly meeting this week and so I am canceling it. Please reach out via email if you need anything from me as my ability to access IRC is limited right now. Thanks! /Dave

1 0

Openstack ansible service variables
by Gk Gk 21 Feb '24

21 Feb '24

Hi, We have an OSA setup. I see that common-playbooks/haproxy-service-config.yml has the following: --- - hosts: "{{ service_group }}" gather_facts: false run_once: true tasks: - name: "Temporarily copy haproxy_service_configs value from {{ service_group }} to haproxy_all" add_host: name: "{{ item }}" haproxy_service_configs: "{{ hostvars[inventory_hostname][service_variable] }}" with_items: "{{ groups['haproxy_all'] }}" How does the openstack ansible collect haproxy configuration for a specific service as in this case for repo service ? Where is this defined in the code ? How does it even generate specific haproxy variables for each service ? How does it specifically know what haproxy variables to collect ?

2 1

Haproxy and rabbitmq
by Gk Gk 21 Feb '24

21 Feb '24

Hi, We have the latest version of openstack setup. The rabbitmq backend health check is getting successful even though the curl to its ssl url is failing as shown below: ---- backend rabbitmq_mgmt-back mode http balance leastconn stick-table type ipv6 size 256k expire 10s store http_err_rate(10s) http-request track-sc0 src http-request deny deny_status 429 if { sc_http_err_rate(0) gt 20 } !{ src 192.168.0.0/16 } !{ src 172.16.0.0/12 } !{ src 10.0.0.0/8 } option forwardfor option httpchk HEAD / HTTP/1.0\r\nUser-agent:\ osa-haproxy-healthcheck server rabbit_mq_container-527affef <ip>:15671 check port 15671 inter 12000 rise 3 fall 3 ssl check-ssl verify none server rabbit_mq_container-68b39094 <IP>:15671 check port 15671 inter 12000 rise 3 fall 3 ssl check-ssl verify none server rabbit_mq_container-83661288 <IP>:15671 check port 15671 inter 12000 rise 3 fall 3 ssl check-ssl verify none ------ But the ssl curl to its ip and port 15671 is failing: 1234567 curl -vvv 172.21.152.187:15671 * Trying 172.21.152.187:15671... * TCP_NODELAY set * connect to 172.21.152.187 port 15671 failed: Connection refused * Failed to connect to 172.21.152.187 port 15671: Connection refused * Closing connection 0 curl: (7) Failed to connect to 172.21.152.187 port 15671: Connection refused How then, the haproxy is still able to detect it as green and status ok in the haproxy stats page ?

3 6

How to enable VT in VM(Ubuntu22.04): Nested Virtualization.
by KK CHN 21 Feb '24

21 Feb '24

I am running an ubuntu VM (instance 22.04) on Esxi 7.0 virtualized platform. I am trying to create Linux cloud images on this ubuntu VM by installing virt-manager .. Reference: https://kifarunix.com/create-and-upload-custom-linux-image-into-openstack/?… But on my VM when I execute grep -iE 'vmx|svm' /proc/cpuinfo Returns 0 //means not CPU virtualization enabled ? modprobe: FATAL: Module l not found in directory /lib/modules/5.15.0-25-generic root@ubuntu-VM:/home/ubuntu# lscpu |grep Virtualization Virtualization type: full root@ubuntu-VM:/home/ubuntu# root@ubuntu-VM:/home/ubuntu# grep -iE 'vmx|svm' /proc/cpuinfo root@ubuntu-VM:/home/ubuntu# grep -c '(vmx|svm)' /proc/cpuinfo 0 root@ubuntu-VM:/home/ubuntu# grep -iE 'vmx|svm' /proc/cpuinfo root@ubuntu-VM:/home/ubuntu# root@ubuntu-VM:/home/ubuntu# How can I enable the virtualization support on this VM ?? What to do for Nested Virtualization support in this Virtual Machine ? Any hints welcome. Thank you Krish

4 5

neutron zed security group not applied on node
by Ionuț Bîru 21 Feb '24

21 Feb '24

Hi guys, I have an issue with neutron not applying on host the rules updates or when a new ip is added on the port. I'm using kolla-ansible to deploy Openstack with openvswitch and the only way I got it working is to switch in globals.yml neutron_legacy_iptables: 'yes' or to 'no' depending on what value I had it before for that host. [securitygroup] firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver I checked with: iptables -nL | grep ip When doesn't work nothing is returned. Switching to neutron_legacy_iptables yes or to, then checked again with the same command and I have output. I don't see any errors in logs. Ubuntu 20.04 on host with linux-hwe kernel 5.15.0-79-generic Do you guys have any ideas on how to fix that ? --- Ionuț Bîru - Hosterion

1 0

[tc][murano] Status of the murano project
by Takashi Kajinami 20 Feb '24

20 Feb '24

Hello, As I brought in another thread about yaql library maintenance[1], It seems murano project is not active now, based on the following points. * The changes merged during recent two years but all of these are gate fix * Its CI is currently broken and no one is trying to fix it * I tried reaching the current PTL by email or gerrit review but didn't get any feedback even after waiting for a few weeks I'm wondering if murano project should be added to the inactive projects, or at least its project health and plan needs to be reviewed by TC, before we include this to Caracal deliverables. # Though it might be too later to drop the deliverables now Thank you Takashi Kajinami irc: tkajinam [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…

4 15

[tc][powervmstacker-sig] Status of the PowerVMStacker SIG
by Takashi Kajinami 20 Feb '24

20 Feb '24

Hello, # I'm adding TC tag because this is a governance topic I happened to notice that none of the repositories[1] owned by the PowerVMStacker sig have not been updated for ~5 years. May I know the current status of this SIG ? The SIG list page[2] says this SIG is active but I don't think it's true now based on the update in these repos. If no one is actually working in the SIG then I'd suggest that we retire the SIG and its repositories. Note: It seems these repositories still have old stable branches(ocata, pike) and we may need some help from the release team with retirement of these branches. Thank you, Takashi Kajinami irc: tkajinam [1] https://opendev.org/openstack/ceilometer-powervm https://opendev.org/openstack/nova-powervm https://opendev.org/openstack/networking-powervm [2] https://governance.openstack.org/sigs/

2 3

Re: [Cinder] PTL non-candidacy
by Rajat Dhasmana 20 Feb '24

20 Feb '24

Thanks everyone! Good to know I was able to do justice to the PTL role and I will continue to be an active contributor in the Cinder project. On Mon, Feb 19, 2024 at 10:31 AM Tilay, Raghavendra < raghavendra-uddhav.tilay(a)hpe.com> wrote: > Thanks Rajat for all the help & guidance. > > > > *From:* Rajat Dhasmana <rdhasman(a)redhat.com> > *Sent:* Friday, February 16, 2024 9:51 PM > *To:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > *Subject:* [Cinder] PTL non-candidacy > > > > Hello everyone, > > > > I'm sending this email out to let everyone know that I will not be running > for PTL for the Cinder project during the 2024.2 (Dalmatian) cycle. > > I started my PTL journey with the Zed cycle and it's been a great > experience leading the Cinder project for 4 cycles. > > > > I think it is time for someone else to step up and bring their insights > into the PTL tasks since I believe a new perspective will surely benefit > > the project. > > > > I would like to thank the Cinder team for their support, without which, it > would have been a very hard task to accomplish. > > Last but not the least, Brian and Jay (former Cinder PTLs) helped out a > lot to run things smoothly and in making complex decisions so a special > > thanks for all their help and support. > > > > Thanks > > Rajat Dhasmana >

1 0

Re: [neutron] qrouter namespace missing in controllers - opensack ussuri
by Sławek Kapłoński 20 Feb '24

20 Feb '24

Hi, Please don't drop openstack-discuss ML from the thread. Dnia piątek, 16 lutego 2024 04:39:05 CET keshav bareja pisze: > Hi > > I can see below status in the neutron command: > > [image: image] > > and qrouter namespace is missing in controller nodes for most of the > projects. > so instances are not accessible. > I tried to check errors in l3-agent but no major indication. tried > restarting all neutron services in all the 3 controllers but no success. > Also tried turning ha-mode disabled/enable but it seems qrouter namespace > is not getting generated. > All this issue started after reboot of one of the control nodes. > > How can I trigger the creation of qrouter namespace or any other > suggestions? Is it only qrouter namespace missing? Are snat-<router_id> namespaces for example created fine or also missing? Regarding triggering it manually You can't really do that in other way than restarting L3 agent on the node. But I guess there may be something in logs if the namespaces aren't created fine. Please enable debug logs in L3 agent, restart it and then share its logs with us. > > Regards > Keshav Bareja > > On Thu, Feb 15, 2024 at 9:19 PM keshav bareja <keshav.bareja(a)gmail.com> > wrote: > > > Hi > > > > We have DVR ha-mode activated , router for each project and showing as > > qrouter-() on each of the controller. > > > > For some project router , there is no qrouter-(router-id) in any of the > > controller node. > > > > Regards > > Keshav > > > > > > Sent from my iPhone > > > > > On 15 Feb 2024, at 8:27 PM, Sławek Kapłoński <skaplons(a)redhat.com> > > wrote: > > > > > > Hi, > > > > > > Dnia czwartek, 15 lutego 2024 18:37:01 CET keshav bareja pisze: > > >> Hi Team > > >> > > >> We are experiencing an issue of reachability in some of the projects, > > >> instances in the project are not reachable. It is a project specific > > issue. > > >> I tried to check router details and could observe . > > >> For the project having issues, I checked the router and could see that > > the > > >> qrouter namespace is not present in the command "ip netns" in any of the > > >> controllers. > > >> > > >> Problem started after a reboot of one controller. > > >> > > >> Do any one has faced a similar issue and any suggestions to recover > > this? > > >> > > >> Regards > > >> Keshav Bareja > > >> > > > > > > Any errors in the L3 agent logs on controllers? Are those DVR or > > centralized routers? > > > > > > -- > > > Slawek Kaplonski > > > Principal Software Engineer > > > Red Hat > > > -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

Red Cinder-volume detaching error
by Rohit Sansiya 20 Feb '24

20 Feb '24

Hello all, please help me i m unable to detach volume with the help of gui. i checked logs also no error it shows. [image: image.png] Your message is ready to be sent with the following file or link attachments: Rohit Sansiya https://sites.google.com/view/rpgcloud/research-india Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

2 1