Deployment

okadm, Kolla Ansible, OpenStack-Helm

One binary: no venv, no SSH inventory, no chart repository; everything is embedded except the images.

Tool, target and data plane

	Kolla Ansible	OpenStack-Helm	okadm
Tool	Python and Ansible: venv, install-deps, Galaxy collection	Helm charts, helm osh plugin; kubectl and helm required	One Go binary: client-go and Helm SDK built in, embedded charts
Target	Linux hosts over SSH, all-in-one or multinode inventory	Existing Kubernetes cluster; creating it is out of scope	Existing Kubernetes cluster, or a kind cluster created for a lab
Hosts	bootstrap-servers: packages, Docker, firewall, SELinux, AppArmor, NTP	deploy-env Ansible role for a lab, not idempotent	Nothing to prepare: okadm plan checks and prints the command
Data plane	libvirt and OVS agents in containers on the hosts	libvirt and openvswitch DaemonSets, Ceph to deploy	KubeVirt, OVN and CSI: Kubernetes building blocks

Configure and operate: the scope

	Kolla Ansible	OpenStack-Helm	okadm
Data	MariaDB, RabbitMQ, Memcached, HAProxy in Kolla containers	One Helm release per brick: mariadb, rabbitmq, memcached	Operators; instances, databases, accounts and vhosts created by okadm
Configuration	globals.yml: 326 options; Ansible inventory	Values overrides per chart and per feature set	--mode lab or production, --domain, -f values
Secrets	passwords.yml: 106 secrets generated by kolla-genpwd	In the chart values	Generated in Kubernetes Secrets, per component
Life cycle	26 subcommands: deploy, reconfigure, upgrade, mariadb-recovery…	helm upgrade --install, chart by chart, in the right order	plan, install, upgrade, status, access, uninstall; idempotent

Kolla Ansible (stable/2026.2) and OpenStack-Helm (master of 2026-11-03): facts taken from their upstream repositories for the presentation, outside the workspace.