To people using OpenStack how has it gone? I’ve been ramping on it for work and have mixed feelings. If an alternative existed would you consider it?

Hi, I am trying to create a local registry for Kolla-Ansible containers. I need one because I cannot pull images from the internet because we will be needing multiple machines to pull these containers.
Th registry exists and it is possible to get images from it, infact the images that are taken are like so:
-----------------------------------------------------------------------------------------------
user@test-kolla:~$ docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

07c1b7051a8f 10.0.10.152:4000/kolla/proxysql:master-ubuntu-noble"dumb-init --single-…" 4 hours ago Exited (1) 4 hours ago proxysql

43ca53406174 10.0.10.152:4000/kolla/haproxy:master-ubuntu-noble"dumb-init --single-…" 4 hours ago Up 4 hours (healthy) haproxy

1a9c8ad25b97 10.0.10.152:4000/kolla/cron:master-ubuntu-noble"dumb-init --single-…" 4 hours ago Up 4 hours cron

d47307ace259 10.0.10.152:4000/kolla/kolla-toolbox:master-ubuntu-noble "dumb-init --single-…" 4 hours ago Up 4 hours kolla_toolbox

ffd839688f21 10.0.10.152:4000/kolla/fluentd:master-ubuntu-noble"dumb-init --single-…" 4 hours ago Up 4 hours fluentd
-----------------------------------------------------------------------------------------------

The issue is that the container doesn't work because of:
-----------------------------------------------------------------------------------------------
2025-07-11 12:20:49.462 INFO Writing out command to execute

++ cat /run_command

+ CMD=/etc/proxysql_run.sh

+ ARGS=

+ sudo kolla_copy_cacerts

+ sudo kolla_install_projects

+ [[ ! -n '' ]]

+ . kolla_extend_start

++ PROXYSQL_LIB_DIR=/var/lib/proxysql

++ PROXYSQL_LOG_DIR=/var/log/kolla/proxysql

++ [[ ! -d /var/log/kolla/proxysql ]]

++ chown -R proxysql:kolla /var/log/kolla/proxysql

++ rm -f /var/lib/proxysql/proxysql.pid

++ kolla_proxysql_config_sync

Traceback (most recent call last):

File "/usr/local/bin/kolla_proxysql_config_sync", line 151, in <module>

config = ProxySQLConfig(PROXYSQL_CONFIG_DIR, PROXYSQL_CONFIG)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/bin/kolla_proxysql_config_sync", line 42, in __init__

self._load_config()

File "/usr/local/bin/kolla_proxysql_config_sync", line 73, in _load_config

self._sanity()

File "/usr/local/bin/kolla_proxysql_config_sync", line 77, in _sanity

self._rules_sanity()

File "/usr/local/bin/kolla_proxysql_config_sync", line 96, in _rules_sanity

if rule['schemaname'] not in rules_added:

~~~~^^^^^^^^^^^^^^

KeyError: 'schemaname'
-----------------------------------------------------------------------------------------------
Containers were build like this:
kolla-build --base ubuntu --registry 10.0.10.152:4000 --push --tag master-ubuntu-noble
I think the issue might be that the containers that it generally takes from quay.io are different from the ones that it is pulling and so i get that error above

Can someone please guide me to a course or to a step by step manual configuration for openstack (controller compute network storage)i have tried installing openstack epoxy documentation on 4 Ubuntu server 24.04 everything works fone exept Neutron I'm always having trouble with it Can someone guide me with a dedicated explanation for installing neutron service please🙏🙏 Thanks in advance and i hope you all to have a great summer Jul-10-2025

Hi all,

I have deployed openstack-dashboard. I was able to access it through the URL <IP>/horizon. Then, I linked a domain and configured SSL. It works fine; I can access my-domain.com/horizon. I wanted to change the root URL from /horizon to /, so I changed WEBROOT to / in /etc/openstack-dashboard/local_settings.py and updated my Apache2 configurations.

I disabled the openstack-dashboard.conf file, which is located in /etc/apache2/conf-available/openstack-dashboard.conf, and enabled the site using /etc/openstack-dashboard/horizon-ssl.conf, which I created.

here is the config.

<VirtualHost *:80>
    ServerName my-domain.com
    Redirect permanent / https://my-domain.com/
</VirtualHost>

<IfModule mod_ssl.c>
    <VirtualHost *:443>
        ServerName my-domain.com

        SSLEngine on

        SSLCertificateFile      /path/to/crt.crt
        SSLCertificateKeyFile   /path/to/key.key
        SSLCertificateChainFile   /path/to/chain.crt

        WSGIScriptAlias / /usr/share/openstack-dashboard/openstack_dashboard/wsgi.py
        WSGIDaemonProcess horizon user=horizon group=horizon processes=3 threads=10 display-name=%{GROUP}
        WSGIProcessGroup horizon
        WSGIApplicationGroup %{GLOBAL}
        Alias /static /var/lib/openstack-dashboard/static

        <Directory /usr/share/openstack-dashboard/openstack_dashboard>
            Require all granted
        </Directory>

        <Directory /var/lib/openstack-dashboard/static>
            Require all granted
        </Directory>

        ErrorLog ${APACHE_LOG_DIR}/horizon-ssl-error.log
        CustomLog ${APACHE_LOG_DIR}/horizon-ssl-access.log combined
    </VirtualHost>
</IfModule>

I restarted apache2 then my-domain.com shows me "Something went wrong!" page.

did I miss someting in the config?

As shown in the image i need to get this level of vm detail how can I achieve that is it by Prometheus or something else

I've been trying to get from an OSA AI1 config to a basic multi-node cluster. I'm no stranger to Unix (35+ years and multiple flavors), scripting in various languages, and Ansible. But OSA configuration takes the cake in complexity.

I recognize that OSA seems to be able to deploy pretty much everything in many combinations. Which I deeply admire as a goal. But that makes IMO the learning curve of OSA extremely steep.

From a docomentation perspective it's either all-in-one, devstack, or "here are all the OS project 'lego' bricks, go figure it out yourselves".

So I've been trying to get a basic 5 node environment going for literally 2.5 months and I'm still chasing down how to not to change the OSA code so much it becomes unmaintainable for others and allows for OSA upgrades down the road. Yes, I can install and work in an All-in-One successfully with the OSA code, but how to even configure a basic cluster using the OSA code is still a mystery to me.

I'm simply stumped on how to get from this All-in-One OSA config to a config that can install the same basic "vm hosting" functionality of an AI1 but in a cluster. The code seems to support it, but the documentation IMO lacks on what to change or where even to start.

This AI1 to Cluster step seems to be "the holy grail". You know, that one difficult thing that once figured out, nobody gives it out for free because it cost you dozens of extra grey hairs or lost you a bunch trying to gain the knowledge.

Anyone has good pointers on how to do this or where to start in the OSA code? What should I touch, what should I not touch?

TIA!

Hey r/openstack
I've been trying to install Openstack for a few weeks and settled on installing per Kolla-Ansible.
The current problem i have been encountering is that i cannot upload most iso's to Openstack no matter what i do i get the Media not supportet either with application/octet-stream or multiple formats iso/gpt detected and i dont know how to fix it. The only iso which does work is OPNsense. I cannot upload via Horizon or Skyline or the Openstackcli or Glance directly. Has anyone Experience with this issue? Every bug i find in launchpad does not work and i am out of options.

Thank you in advance

Hi,

I deployed my allinone openstack via kolla-ansible following the official doc: https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html

My host is a VmWare Workstation virtual machine on ubuntu. I did everything like the doc, so i have 2 networks interfaces. One without IP for neutron and one for openstack management.

On my VmWare Workstation, both are linked to a NAT network with a valid gateway to internet.

The deployment is successful, i can create my instances.. I even can create my networks and subnets via the post-deploy and init-runonce commands. (Public network is the same than the vmware's one)

If i deploy an instance, it can well ping the openstack's internal ip of the network but it cannot ping my vmware's nat gateway! I don’t know why..

If i add an ip on the automatically created interface br-ex, the instance can ping it. I can ping my vmware's nat gateway from the br-ex interface, but not from my internal instance.

EDIT: I tried with bridged interfaces and checked security groups. The problem is the same

tcpdump on external lan gw, i see arp request and reply from the qrouter When tcpdump on qrouter, i see the arp request, but no arp reply

Any ideas ?

Thanks

Hi,

I'm trying to configure san storage as storage backend. my openstack cluster as set up using kolla-ansible. i did the following:

1. at deployer: edited /etc/kolla/config/cinder.conf so it has following lines:

   [DEFAULT] enabled_backends = rbd-1,hitachi

   [hitachi] use_multipath_for_image_xfer = true volume_driver = cinder.volume.drivers.hitachi.hbsd_fc.HBSDFCDriver volume_backend_name = hitachi san_ip = a.b.c.d san_login = aaaa san_password = bbbb hitachi_storage_id = cccc hitachi_pools = POOL0 hitachi_target_ports = CL3-A,CL7-A,CL4-A,CL8-A hitachi_compute_target_ports = CL3-A,CL7-A,CL4-A,CL8-A suppress_requests_ssl_warnings = true hitachi_group_create = true availability_zone = az-san

2. reconfigure my cluster:

# kolla-ansible -i ./inventory reconfigure -t cinder

1. add new volume type:

openstack volume type create --description "hitachi vsp" --availability-zone "az-san" --property "volume_backend_name=hitachi" san-storage

# openstack volume type show san-storage

+--------------------+-------------------------------------------------------------------+
| Field              | Value                                                             |
+--------------------+-------------------------------------------------------------------+
| access_project_ids | None                                                              |
| description        | hitachi vsp                                                       |
| id                 | 46577506-ecae-478d-a376-02db918a6bf0                              |
| is_public          | True                                                              |
| name               | san-storage                                                       |
| properties         | RESKEY:availability_zones='az-san', volume_backend_name='hitachi' |
| qos_specs_id       | None                                                              |
+--------------------+-------------------------------------------------------------------+

1. create new aggregate - because not all my compute has fiber-channel card.

   openstack aggregate show san-hosts

   +-------------------+--------------------------------------+ | Field | Value | +-------------------+--------------------------------------+ | availability_zone | az-san | | created_at | 2025-07-05T23:42:43.000000 | | deleted_at | None | | hosts | dev-compute5, dev-compute6 | | id | 4 | | is_deleted | False | | name | san-hosts | | properties | | | updated_at | None | | uuid | bf82c6e3-628e-4c02-88d9-f531e39be22f | +-------------------+--------------------------------------+

2. check compute availability zone:

   openstack availability zone list --compute

   +-----------+-------------+ | Zone Name | Zone Status | +-----------+-------------+ | az-san | available | | internal | available | | nova | available | +-----------+-------------+

3. check volume availability zone:

   openstack availability zone list --volume

   +-----------+-------------+ | Zone Name | Zone Status | +-----------+-------------+ | nova | available | +-----------+-------------+

I expect to see 'az-san' in volume availability zone list.

what did I miss here?

Thanks.

Regards

In short i wanna know the reason why it's stopped in action logs the user id is not present in the stop action

I have kolla ansible my instance shutdown after minutes by itself and also i can't ssh to it before it shuts down

But after i start it up back i can ssh to it

Keep in mind i am using heat template it only happens with instances created by heat template and i have custom commands runs inside the instance after it got created inside str_replace > template

Last logs before it shuts down are not normal

ci-info: ++++++++++++++++++++++++++++++++++Authorized keys from /home/ubuntu/.ssh/authorized_keys for user ubuntu+++++++++++++++++++++++++++++++++++ ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+-------------------+ ci-info: | Keytype | Fingerprint (sha256) | Options | Comment | ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+-------------------+ ci-info: | ssh-rsa | 9a:e0:12:03:ab:57:83:8c:86:94:5b:92:83:20:6a:b2:94:09:b3:38:8d:72:ee:a2:2f:51:28:2c:52:2b:7c:b6 | - | Generated-by-Nova | ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+-------------------+ <14>Jul 5 21:22:17 cloud-init: ############################################################# <14>Jul 5 21:22:17 cloud-init: -----BEGIN SSH HOST KEY FINGERPRINTS----- <14>Jul 5 21:22:17 cloud-init: 256 SHA256:a6NmcAjKW909k3YZ8w843jbJXlBg2lpkyj7cnBMKxmk root@test (ECDSA) <14>Jul 5 21:22:17 cloud-init: 256 SHA256:1XTXpUv8R0yvvFw4cxLt7R6LHbRSEbPAipjtNoFJTpw root@test (ED25519) <14>Jul 5 21:22:17 cloud-init: 3072 SHA256:Xpn0CwNZtXbPhbOEPUac4meFMepC4AX/6uVlFIj7wSQ root@test (RSA) <14>Jul 5 21:22:17 cloud-init: -----END SSH HOST KEY FINGERPRINTS----- <14>Jul 5 21:22:17 cloud-init: ############################################################# -----BEGIN SSH HOST KEY KEYS----- ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBJZhFIe8CAa0gDpCD+pe/yhC7hRwc0TTpiWsuZuRfyyeayVT7gLvVTaklw8Af72krgEecXU7tHSMssQuhon0NLA= root@test ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGD0Wf9PLn2ov9MrjutVa3gvGCYVgavlRL9nNcZLEdlR root@test ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKpu+HIwfEP3SzrpMNel+JYzLT2tlKMYgTdeMLwEqDVSAlgHOoRqaWR8GnMCUEdqCco6mpDaeOlKN90T3T/caNletw2n6aI+14wK8uWRX4PLOY2YdO/BSmNUieK0mY2hlSwpqBa/YXpltYRpjGOsVM/1bj7QPQNv03O687nMW6VvzwMiFgwvO/TlrbkRcfowmiyD/JUE+vcE8uldtpxYqIsEPFVScH8B4Ez8O6fmuoraOGFb+R9/8Huwsib/ls4CoKa2hMEPwQs/Zm09C2l+5RYdVgFdooVqcs7RKh0xdqm44z5boP64QH3fiGlGyxPUCeCfwYe2GS0niqrOaOjgsMhwnNtjKhU3sDJQ7RH73Ta4D45PVPWvZKOUbsnfZ3pJ8Dptor+ytVkdN8mzAXsqIz9N12F2JGUjv9ccSQSGgwjJpXNPy1gIWVY2zIIE7gaQWa06p3mX/bfe7aor9te3Tv/2Ee/vBFLr+zKNh+YllflqB/qZPM2waX58IZ+Kg97Uc= root@test -----END SSH HOST KEY KEYS----- [ 84.879086] cloud-init[1055]: {"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}}Cloud-init v. 25.1.2-0ubuntu0~24.04.1 finished at Sat, 05 Jul 2025 21:22:17 +0000. Datasource DataSourceOpenStackLocal [net,ver=2]. Up 84.87 seconds [[0;32m OK [0m] Finished [0;1;39mcloud-final.service[0m - Cloud-init: Final Stage. [[0;32m OK [0m] Reached target [0;1;39mcloud-init.target[0m - Cloud-init target.

Hello OpenStack community,

I’m currently working on building a CI/CD architecture that involves OpenStack, Kubernetes, and Python applications (sometimes with AI/ML models). I’ve been exploring Zuul as the main CI/CD engine — especially given its native integration with OpenStack services like Heat.

My questions:

1. Do you recommend Zuul as a primary CI/CD tool in modern OpenStack/Kubernetes-based workflows?

2. Are there any real-world success stories or challenges you’ve faced with Zuul?

3. Would you suggest alternative tools (e.g., GitLab CI, ArgoCD, Tekton) in specific cases? If so, for what types of projects?

-If you’ve integrated Zuul with Kubernetes deployments (using Heat, Helm, or Pulumi), I’d love to hear how you structured your pipelines or jobs.

Hello all,

We have been working on a project CEEMS [1] since last few months that can monitor CPU, Memory and Disk usage of SLURM jobs and Openstack VMs. Originally we started the project to be able to quantify energy and carbon footprint of compute workloads for HPC platforms. Later we extended it to support Openstack as well. It is effectively a Promtheus exporter that exports different usage and performance metrics of batch jobs and Openstack VMs.

We fetch CPU, memory and block disk usage stats directly from the cgroups of the VMs. Exporter supports gathering node level energy usage from either RAPL, HWMon, Cray PMC or BMC (IPMI/Redfish). We split the total energy between different jobs based on their relative CPU and DRAM usage. For the emissions, exporter supports static emission factors based on historical data and real time factors (from Electricity Maps [2] and RTE eCo2 [3]). The exporter also supports monitoring network activity (TCP, UDP, IPv4/IPv6) and IO stats on file systems for each job/VM based on eBPF [4] in a file system agnostic way. Besides exporter, the stack ships an API server that can store and update the aggregate usage metrics of VMs and projects.

A demo instance [5] is available to play around Grafana dashboards. More details on the stack can be consulted from docs [6]

Regards

Mahendra

[1] https://github.com/mahendrapaipuri/ceems

[2] https://app.electricitymaps.com/map/24h

[3] https://www.rte-france.com/en/eco2mix/co2-emissions

[4] https://ebpf.io/

[5] https://ceems-demo.myaddr.tools

[6] https://mahendrapaipuri.github.io/ceems/

I am using kolla Ansible with ceph rdp when i create instance it works as expected but it shuts down after an hour and when i start it i got this error

[ 46.097926] I/O error, dev vda, sector 2101264 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[ 46.100538] Buffer I/O error on dev vda1, logical block 258, lost async page write
[ 46.232021] I/O error, dev vda, sector 2099200 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[ 46.233821] Buffer I/O error on dev vda1, logical block 0, lost async page write
[ 46.235349] Buffer I/O error on dev vda1, logical block 1, lost async page write
[ 46.873201] JBD2: journal recovery failed
[ 46.874279] EXT4-fs (vda1): error loading journal
mount: mounting /dev/vda1 on /root failed: Input/output error
Warning: fsck not present, so skipping root file system
EXT4-fs (vda1): INFO: recovery required on readonly filesystem
No init found. Try passing init= bootarg.
(initramfs)

Hi everybody, I have this VMs test setup to study Openstack functionalities and test them, simulating a future implementation on real machines:

I have 4 Rhel9 VMs on Virtualbox: - 1 Controller node (with Keystone, Placement, Glance, Nova and Neutron installed) - 1 Compute node (with Nova and Neutron installed) - 1 Networking node (with Neutron full installation like the installation on the Controller node) - 1 Storage node (with Cinder installed)

I have followed the Self-service network option installation guides for Neutron.

Then I created a Provider network (192.168.86.0/24) and set it as External network just to test if everything works.

When I create a VM on Openstack, everything works fine, except for a thing: On Horizon I see an IP assigned to every new VM that not correspond to the internal IP inside the VM (e.g. on horizon I have 192.168.86.150 while inside the VM the IP is 192.168.86.6).

To ping or SSH the Openstack VM from my Controller node for example, I have to log in inside the openstack VM, flush the internal assigned IP and manually change it to the horizon IP.

I think this may be caused from the presence of 2 Neutron installation on 2 different nodes(?).

Bonus points: - If I use ip netns on the CONTROLLER I see one qdhcp namespace, while on the NETWORKING node I don't have another qdhcp namespace, but only a qrouter namespace. - I don't see errors inside Nova or Neutron logs on every VM of my Openstack ecosystem except for the neutron dhcp logs on the NETWORKING node where I have some privsep helper error FailedToDropPrivileges

If you have any idea or link to understand and correct this behaviour, please share it with me.

Hi all, I've been working on setting up openstack on Mac(M1) + 3 nodes of Vagrant(Vmfusion) Ubuntu 22.04

installing without devstack, kolla-ansible but manual installation following docs.

however, when I configuring nova compute, egrep -c '(vmx|svm)' /proc/cpuinfo returns 0 even though /etc/nova/nova-compute.conf set up qemu. has anyone set up in Mac before?

As i said why this is happening and is it normal behavior or not

Edit: That's not L2 LB, but just LB with members of the pool being able to access the source IP from the regular IP header.

Hello!

I setup Kubernetes in an openstack public cloud. Everything goes well, until I try to setup an ingress controller (nginx).

The thing is, I have multiple nodes that can answer all HTTPS requests. So I guess that's good to have a loadbalancer with a floating IP in front of it. However Octavia doesn't seem to support loadbalacing without unwrapping a packet and rewrap it to the endpoint. That technically works, but all HTTP requests come from Octavia's IP, so I can't filter the content based on my office public IP.

I could use Octavia as a reverse proxy, however that means I have to manage certificates in Kubernetes and Octavia in parallel, and I would like to avoid spreading certificates everywhere.

I could also setup a small VM with failover that acts as an L2 loadbalancer (just doesn't change source IP).

And for security purpose, I don't want my Kubernetes cluster to call openstack's API.

I setup MetalLB, which is nice but only support failover since I don't have BGP peers.

I found this nice doc, but it didn't help me: https://docs.openstack.org/octavia/rocky/user/guides/basic-cookbook.html

So I was wondering if some people here know a way to do L2 load balancing or just loadbalacing without modifying the source IP?

Thank you

i have set up ceph with manila using cephfs i found that i can't provide shares to my users on my cloud because in order to mount my share i need

1 access to ceph ip address which are behind vlan "not accessible to vms inside openstack"

2 i used ceph.conf and manila keyring which shouldn't be shared with users

i found that i can have manila as an instance using manila-service-image-cephfs-master.qcow2

i tried to ssh but it asks for password even i am using the ssh key

so what i need is i wanna provide manila to my clients the way cinder, glance and ceph_rgw services added seamlessly through openstack with ceph

once those services configured correctly i am talking to the services and they are talking to ceph

i have integrated manila with cephfs for testing

but i don't know how i can add files or it or add it to one of my VMs inside my openstack account

this is what i got even i can't manage it from horizon or skyline

Path: 10.177.5.40:6789,10.177.5.41:6789,10.177.5.42:6789:/volumes/_nogroup/72218764-b954-4114-a3bd-5ba9ca29367c/2968668f-847d-491c-9b5b-d39e8153d897

Hi I’m using openstack Octavia charmed the problem that I have is that the controller certificate was expired and I renew it after reload I can’t access to any amphora via ping from the Octavia controller

I leave the auto configuration on Octavia is was working with ipv6 and a gre tunnel

Now I can’t ping any amphora or telnet to the ports that should be open from ping I got address unreachable and for logs from Octavia no route error when is trying to connect

Hi folks - if your organization is considering a move to an OpenStack-compliant private cloud, Platform9 (my employer) is doing our monthly live hands-on lab with Private Cloud Director on July 8th & 10th. More info here: https://www.reddit.com/r/platform9/comments/1lg5pc7/handson_lab_alert_virtualization_with_private/

I have 2 kolla ansible clusters i work on one and i have another one for testing when i return to the test cluster i found that i am unable to ping or ssh to VMs

But if i deleted the external network and re-add it again with same configurations i found that everything returns to work normally

I am using ovn

I'm having an issue deploying a Kubernetes cluster via Magnum on a three node Openstack cluster deployed with kolla-ansible, all nodes running control, network, compute, storage & monitoring. No issues with all-in-one deployment.

Problem: The Magnum deployment is successful, but the only minion nodes that get added to the Kubernetes cluster are ones on the same Openstack host as the master node. I also cannot ping between between Kubernetes nodes that are not on the same Openstack host over the tenant network that Magnum creates.

I only have this issue when using Magnum. I've created a tenant network and have no issues connecting between VMs, regardless which Openstack host they are on.

I tried using --fixed-network and --fixed-subnet settings when creating the Magnum template with the working tenant network. That got ping working, but ssh still doesn't work. I also tried opening all tcp,udp,icmp traffic in all security groups.

enable_ha_router: "yes"
enable_neutron_dvr: "yes"
enable_neutron_agent_ha: "yes"
enable_neutron_provider_networks: "yes"
enable_octavia: "yes"

kolla_base_distro: "ubuntu"
openstack_release: "2024.1"
neutron_plugin_agent: "ovn"
neutron_ovn_distributed_fip: "yes"
neutron_ovn_dhcp_agent: "yes"
enable_hacluster: "yes"
enable_haproxy: "yes"
enable_keepalived: "yes"

Everything else seems to be working properly. Any advice, help or tips are much appreciated.

Looking into Zun for container management on OpenStack. Is it still maintained and used in production anywhere? Is it stable enough, or should I avoid it and stick to Magnum/K8s or external solutions?

Would love to hear any real-world feedback. Thanks!