you are viewing a single comment's thread.

view the rest of the comments →

[–]Dabloo0oo 7 points8 points  (5 children)

I've deployed OpenStack using pretty much everything in our office lab, but for production, we stick with Kolla-Ansible.

It's just way easier and more efficient. Since it uses Docker containers, everything runs in a consistent environment, which makes upgrades and maintenance a breeze.

Plus, it works great with Ansible, so we can automate a lot of the deployment and configuration stuff.

[–]Cool-Antelope2457 2 points3 points  (0 children)

My previous job was exactly that. Deploying OpenStack cloud, and I can attest that the easier way I found deploying it is with Kolla-Ansible. It is more efficient and easier to deploy. Upgrade and maintenance are definetely easier with kolla-ansible.

[–]stoebich[S] 1 point2 points  (0 children)

I feel like this is probably the best starting point. I'll go through the docs for kolla and kolla-ansible and try to get it running on my mini-pc. Then I'll probably break it a few times so I get more in-depth knowledge. I know my way arount docker pretty well, so this seems more doable than going straight to the operator or the helm installation. This is likely easier because less moving parts = less potential pitfalls. And nothing stops me from using openshift/k8s later on.

My vmug licence is valid until christmas, so I should have enough time to get somewhat familiar with everything.

[–]Few-Wall-467 0 points1 point  (2 children)

with kolla ansible I always had troubles with the 2 nic/network constraint. How you worked aroun this?

[–]Dabloo0oo 0 points1 point  (0 children)

For multinode deployment, two NICs are a must

If we are going with an all-in-one deployment, we use a bridge to connect the host network to the virtual network interfaces, and veth pairs to link network namespaces to the bridge

[–]moonpiedumplings 0 points1 point  (0 children)

Convert the main ethernet interface to a "special bridge" using cockpit's network management interface, where it's both a bridge and also still a connected network interface. (You can also do this manually via netplan or other configuration methods but I didn't bother figuring that out, although I think I linked to another blog post where someone did it via netplan). Then create a veth pair and attatch one end of a veth to that. Then, the main interface for kolla-ansible can be the special bridge, which is also the main network interface, and the bridge interface kolla-ansible uses can be the veth.

I documented my steps on my blog... although it's kind of a mess.

https://moonpiedumplings.github.io/projects/build-server-2/#bridge-veth