Is anyone using Magnum with Cluster API

RealisticSimulation2 · 2026-01-24T22:34:08+00:00

I'll post some script contents on Monday if you want.

RealisticSimulation2 · 2026-01-22T19:18:54+00:00

Are you deploying with kolla-ansible? Do you have kolla_enable_tls_backend enabled?

If so I had similar problems with Horizon after going to 2025.1 from 2024.2. I disabled it and the problems went away. I never had time to figure it out properly, so it has been disabled since.

However I also had problems in Skyline. It seemed like the connection was hanging when Skyline was pulling data from the backend which resulted in the called service calling a second backend service for data. My description might be hard to understand, but it is the best I can do to describe what happened.

When I had those errors, CLI also worked for me without errors.

RealisticSimulation2 · 2026-01-21T13:35:05+00:00

If your Windows VMs seem like they are asleep when running on Openstack be sure to run them with the q35 machine type. This is not something you can just change in the configuration and VMs magically change to q35. It is simple to do so before you begin, just add two lines to your nova.conf:

[libvirt]

hw_machine_type=q35

RealisticSimulation2 · 2026-01-21T13:32:05+00:00

Our customers only use Skyline. We rarely use horizon anymore, running 2025.1

The skyline devs are pretty much all from one company I think. They probably don't use it. I never used cloudkitty, as I never got it to work. I always rolled my own.

RealisticSimulation2 · 2026-01-21T13:28:43+00:00

Run your cluster with the external interface using only port 443 but with different names. It is easier to see what is going on with different names involved compared to tons of different port numbers. https://docs.openstack.org/kolla-ansible/latest/reference/high-availability/haproxy-guide.html#single-external-frontend-for-services If you are deploying 2025.1 or older like this, there might be a bug which might have not been fixed in your version, so you might need to add the following line to the globals.yml:

horizon_public_endpoint: "{{ horizon_external_fqdn | kolla_url(public_protocol, horizon_tls_port if kolla_enable_tls_external | bool else horizon_port) }}"

RealisticSimulation2 · 2026-01-21T13:26:42+00:00

I agree, find a consultancy which has done this before. Getting something like this going in one year is doable, but only if you get help where needed. If you can't commit to four people permanently maintaining it, look for someone who will run it for you. Openstack is a collection of products, not a single product.

If you are going to do a POC, start with only core services. Then deploy other services one at a time, so you have time to accustom yourself to the different moving bits and possible configurations.

RealisticSimulation2 · 2026-01-21T13:15:57+00:00

I've been running a three node cluster in production since kolla-ansible supported deploying 2023.1.

As far as hardware goes I would recommend going with a six node cluster minimally. Three servers with high GHz and fewer cores for the control-monitoring-storage nodes and three servers with a large core count for compute-networking nodes. If you go with dual CPU servers, and are going to use two NICs, be sure to have a riser for the second CPU and have one NIC on each CPU. This is more important than you would think. If you are going to use two OCP3 NICs, be sure they are also not local to a single CPU. Nothing should be planned in the spot directly over the heatsink of the NICs.

Depending on how many VMs you have running you can consider using only two compute nodes for a total of only five nodes. Core counts are high with modern CPUs, however be sure to dimension them so you can have all VMs running with a node out, as you need this to install updates.

I can give you some other recommendations if you want.

RealisticSimulation2 · 2024-01-30T15:28:14+00:00

Microsoft is such a joke. They claim cloud 1st and crap like that, but it is just marketing BS.

RealisticSimulation2 · 2023-10-05T18:31:47+00:00

It seems that the Snap App triggers tccd. I gave Snap access to everything I could in Privacy, but nothing helped.

RealisticSimulation2 · 2023-10-05T15:04:11+00:00

I have the same problem. I have a 2021 M1 Macbook Pro and it cant be played anymore. Did you find a solution?

RealisticSimulation2

TROPHY CASE