r/openstack

My company wants to sell openstack solution and for that we are planning to set up lab so we can test its capablities with 2 Server 128 GB RAM each and 64 cores each is it possible with 2 Server because we will also we using vm made using openstack for our other projects is it safe and I will be using kolla ansible for deployment.

Hello everyone,

I am looking to implement an automated workflow where a newly attached OpenStack Cinder volume is automatically formatted and mounted inside the instance.

Currently, I have a working proof-of-concept using udev rules triggering a systemd service with a bash script. However, this is static. I would like the ability to specify the desired filesystem type (e.g., ext4, xfs, btrfs) at the time of volume creation or attachment.

My questions are:

1. Is there a way to pass custom metadata from a Cinder volume to the guest OS during attachment so a script can read it?
2. Are there better "OpenStack-native" ways to handle volume provisioning and formatting beyond custom bash scripting?
3. Does anyone have experience using cloud-init or ConfigDrive to handle this securely?

Any advice on architecture or existing tools would be greatly appreciated!

I put together a small OpenTofu repo for AWS/OpenStack VM and networking workflows.

Would appreciate honest feedback on the overall flow and repo structure. If people find it useful and it gets a bit of interest, I’ll continue improving it.

Repo: https://github.com/Dionise/tofu-provider-fabric

Hi everyone

I’m starting an academic project on centralized logging for OpenStack using Kolla-Ansible, and later I’ll try to feed the logs into an anomaly detection model.

I already found some sample logs and I was advised to use two VMs (8 GB for deployment(kolla ansible) and 16 GB for controller(services)), but I only have about 20 GB RAM available in total.

Since I only need a demo setup (installation + a simple attack simulation like brute force on an instance), I’m wondering if I can reduce the RAM for both VMs. What would be a realistic minimal setup that still works?

Also, I’m struggling to find up-to-date documentation for installing OpenStack with Kolla-Ansible. If anyone has good resources or tips, I’d really appreciate it.

Hey all, I'm trying to deploy a small open stack deployment on my home lab so I can learn about ironic. I have 3 controllers and 4 compute nodes, older think system minis for the former and some older intel NUCs for the latter all running ubuntu noble 24.04.

I can run the bootstrap and prechecks targets fine but when I go to deploy Mariadb doesn't work it says that kolla-toolbox isn't working, when I look on the hosts its not being pulled even on the pull target then when I go to deploy it again (even after a destroy) I get something to the effect of "database already present" If I do a manual pull (i.e. docker pull kolla-toolbox) on each of the hosts then it does get past that point but then fails to actually connect the database together.

So my question is what in the world am I doing wrong and why doesn't kolla pull this important part of the deployment and do you have any tips on making this work and any documentation / guides the open stack docs are...lacking. below is my globals.yml and inventory. Thanks in advance folks.

kolla_install_type: "binary"

openstack_release: "2025.1"

kolla_insternal_vip_address: "10.0.0.50"

enable_haproxy: "yes"

enable_keepalived: "yes"

keepalived_virtual_router_id: "51"

enable_neutron_provider_networks: "yes"

enable_ironic: "yes"

enable_glance: "yes"

enable_keystone: "yes"

enable_nova: "yes"

enable_neutron: "yes"

enable_cinder: "no"

enable_horizon: "yes"

ironic_cleaning_network: "public1"

ironic_dnsmasq_dhcp_ranges:

- range: "10.20.30.100,10.20.30.150"

routers: "10.20.30.1"

dns_servers: "10.20.30.1"

ntp_servers: "10.20.30.1"

ironic_dnsmasq_bootfile: "pxelinux.0"

[control]

cp1 ansible_host=10.0.0.1 network_interface=eno1

cp2 ansible_host=10.0.0.2 network_interface=eno1

cp3 ansible_host=10.0.0.3 network_interface=eno1

[network]

cp1

cp2

cp3

[loadbalancer]

cp1

cp2

cp3

[compute]

cn1 ansible_host=10.0.0.4 network_interface=eno1

cn2 ansible_host=10.0.0.5 network_interface=enp0s25

cn3 ansible_host=10.0.0.6 network_interface=enp0s25

cn4 ansible_host=10.0.0.7 network_interface=enp0s25

[monitoring]

cp1

cp2

cp3

[storage]

cp1

cp2

cp3

[deployment]

localhost ansible_connection=local

[baremetal:children]

control

network

compute

[bifrost]

[nova-api:children]

control

[nova-scheduler:children]

control

[nova-super-conductor:children]

control

[nova-conductor:children]

control

[nova-novncproxy:children]

control

[nova-ssh:children]

control

[nova-metadata:children]

control

[nova-compute-ironic:children]

control

[nova-serialproxy:children]

control

[nova-spicehtml5proxy:children]

control

[nova-serialproxy:children]

control

[neutron-ovn-agent]

cp1

[neutron-dhcp-agent:children]

control

[neutron-l3-agent:children]

control

[ironic-neutron-agent:children]

control

[neutron-metadata-agent:children]

control

[neutron-ovn-metadata-agent:children]

control

[neutron-metering-agent:children]

control

[neutron-bgp-dragent:children]

control

[neutron-infoblox-ipam-agent:children]

control

[manila-share:children]

control

[mariadb:children]

control

[memcached]

cp1

[horizon]

cp1

[cinder-volume:children]

control

[cinder-volumes:children]

control

[cinder-backup:children]

control

[neutron-server]

cp1

[glance-api:children]

control

[heat-api:children]

control

[heat-api-cfn:children]

control

[ironic-api:children]

control

[keystone]

cp1

[placement-api]

cp1

[rabbitmq:children]

control

[rabbitmq]

cp1

[ironic-conductor:children]

control

[ironic-inspector:children]

control

[ironic-tftp:children]

control

[ironic-http:children]

control

[heat-engine]

cp1

[cinder-scheduler]

cp1

[cinder-api]

cp1

I’ve been trying to deploy Octavia using Kolla-Ansible, but running into consistent issues.

The Amphora image gets created successfully, but after that the Octavia management components are unable to monitor the Amphora health. It seems like the health manager isn’t able to reach the Amphora instances.

So far I’ve checked:

• Amphora image creation
• Octavia services are running
• But health monitoring / heartbeat is failing

I suspect it might be something related to:

• Management network configuration
• Security groups / ports (UDP 5555?)
• Controller ↔ Amphora connectivity

Has anyone successfully deployed Octavia with Kolla-Ansible in a production or lab setup?

Would really appreciate if you could share:

• Key configs you had to tweak
• Common pitfalls
• Networking setup (management network, provider network, etc.)

Thanks in advance

I have tunnel network, internal, public network, provider network ( floating ip ) and running multi region cluster. But while i was deploying octavia in test cluster. I could not bring the loadbalancer

I’m currently having a OpenStack platform deployed, it will have several tenants running on the platform.

I’m currently figuring out how to deploy public IP to the hosts. The current approach seems to span the essentially a L2 segment to a routed next hop anycast gateway on the upstream nexus switches. There is no firewall between the hosts and the nexus switches.

Now that to me sounds pretty horrific, having to span a /23 range of public IPs with each network node having an IP on that subnet. I can’t see how we would provision discreet subnets for customers and every customer would be on same giant broadcast domain. This seems so.. 2010.

I would have thought the network nodes running on each of the compute hypervisors could build a BGP neighbourship with each of the leaf switches allowing us to announce new ranges on demand from the host. Apparently BGP isn’t supported, which, frankly sounds either incorrect or… well.. dear me.

Does anyone have any thoughts or direction of investigating for me to follow?

Thank you in advance.

I'm having an issue getting a working Manila deployment on a three node cluster. All three nodes running control, network, compute, storage. kolla-ansible 2025.1. OVS & DVR

manila.conf

[DEFAULT]
enabled_share_backends = generic


[generic]
share_driver = manila.share.drivers.generic.GenericShareDriver
interface_driver = manila.network.linux.interface.OVSInterfaceDriver
driver_handles_share_servers = true
service_instance_password = password
service_instance_user = manila
service_image_name = manila-service
share_backend_name = GENERIC

The first issue is that kolla-ansible is creating multiple Manila service networks on deployment https://bugs.launchpad.net/kolla-ansible/+bug/2138767 So I end up with two or three service networks.

After I delete the extra service networks and ports, restart all Manila services on all nodes. I'm able to create a share ONLY if the driver decides the create the share VM on the same node of the active Manila service. ie. If share server is at ostack1@generic, the service cannot reach the share VM unless it picks ostack1 to create the share VM.

The only way I've been able to make it work consistently is creating a vlan on the physical switch, add new interfaces to all three nodes with the vlan tag, add a provider network to Openstack. Then configure Manila to use that network with admin_network_id & admin_subnet_id.

Has anyone deployed DHSS on multinode without using provider vlans for service network?

https://bugs.launchpad.net/kolla-ansible/+bug/2139425

Does anyone have this issue ?

We tried also prometheus-cadvisor 0.56.2 and our

Storage Driver: overlay2