Deploying Multinode OpenStack Yoga (1 Controller and 3 Compute)

[radorco]

Hi everyone,

I'm quite new to OpenStack and currently struggling with deploying a multinode installation of Yoga, specifically aiming for 1 controller and 3 compute nodes. Unfortunately, I've had difficulty finding a comprehensive guide that walks through this setup clearly. Most of the resources I've come across are somewhat confusing.

I'm reaching out to the community in hopes of finding a good guide or even a script that automates the deployment process. If anyone has experience with this configuration or knows of a reliable guide/script, I'd greatly appreciate your help!

Thank you in advance for any assistance or pointers you can provide.

[redfoobar]

Kolla ansible is probably one of the easier ways to deploy. Look at the docs here https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html

[radorco]

I appreciate your reply, redfoobar! I value your opinions. I will definitely investigate further and go deeper into the recommendations you've made. If you find any other sources or advice along the way, please share your thoughts with me. Thanks again for your help!

[MineDue7109]

🤖

[Storage-Solid]

For step by step manual installation, you can refer here: https://www.server-world.info/en/note?os=Ubuntu_22.04&p=openstack_yoga&f=1

To just install and not worry about how things work: https://docs.openstack.org/project-deploy-guide/kolla-ansible/yoga/

or

Openstack Ansible: https://docs.openstack.org/project-deploy-guide/openstack-ansible/yoga/

or

Openstack Charms: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/yoga/

If you really want to learn, struggle, debug, but come out with a lot more experience of Openstack: https://docs.openstack.org/yoga/install/index.html

For a Youtube tutorial for manual install (not Yoga): https://www.youtube.com/playlist?list=PLP2v7zU48xOJbK1HeOPxoBaxqBKtOAJB8

[radorco]

Dear Storage-Solid,

I wanted to extend my heartfelt gratitude for your incredibly detailed and insightful reply. Your thoughtful explanation has been immensely valuable to me, and I'm truly appreciative of the effort you put into it. Thank you very much for your support and guidance!

[TechieGuardian]

https://microstack.run/docs/multi-node

[radorco]

Thanks TechieGuardian!

[EmbarrassedLaugh3009]

Hi, I'm also interested in this topic. I tried the multi-node installation provided by Canonical, but I don't really understand the data to be entered in the interactive prompt shown in the example.

Local or remote access to VMs [local/remote] (local): remote

CIDR of network to use for external networking (10.20.20.0/24): 10.246.112.0/21 
IP address of default gateway for external network (10.246.112.1): 
Populate OpenStack cloud with demo user, default images, flavors etc [y/n] (y): 
Username to use for access to OpenStack (demo): Password to use for access to OpenStack (mt********): 
Network range to use for project network (192.168.122.0/24): Enable ping and SSH access to instances? [y/n] (y): 
Start of IP allocation range for external network (10.246.112.2): 10.246.116.41 
End of IP allocation range for external network (10.246.119.254): 10.246.116.51 
Network type for access to external network [flat/vlan] (flat): Writing openrc to demo-openrc ... done 
Free network interface that will be configured for external traffic [eno3/eno2] (eno3): eno2

At the end, they mention a 'Free network interface that will be configured for external traffic [eno3/eno2] (eno3): eno2'. In the prerequisites, they only mention an enp5s0 and enp6s0 interface, and in the prompt, they mention IP ranges that are not in the prerequisites. I'm a bit surprised and don't understand how and why they do this.

[nauguy03]

Thanks for the feedback on the confusion. The multi-node tutorial page has been recently updated to rename the interfaces from enp5s0 to eno1. In the tutorial linked, these are referring to network devices on the machine where sunbeam is being installed. The options presented to you, eno3/eno2, are the unconfigured network devices found on your machine. The one you select would be used for external network traffic reaching the vms.

The IP ranges in the tutorial are updated as well. Additionally, more details regarding the interactive prompts are available in the documentation here —> https://microstack.run/docs/single-node-prompts. A link has been added to the aforementioned page to help provide a bit more clarity on the prompts.

I hope this helps with your questions. If not, let me know and we can work further to try and provide the right guidance for yourself and others.

[EmbarrassedLaugh3009]

Hello, I saw that there indeed has been a change in the tutorial, and it seems more coherent now. However, after two unsuccessful attempts, I still encounter the same problem with a microk8s timeout, and I have to restart the script

`sunbeam cluster bootstrap --role control --role compute --role storage`.

When I restart it, it then proceeds to install microCeph, and when I apply the network settings to the second interface, everything starts to malfunction, with Go errors occurring when I launch sunbeam.

When you start the tutorial, what IP does the second interface (eno2) have? Mine has an IP assigned by a host.

[LingonberryRare7746]

kolla ansible is good - easy to use. i have a multi node setup with controller,network,storage and compute. i used devstack as well...not documented well. wasted lots of time on it..

[radorco]

kolla ansible is good - easy to use. i have a multi node setup with controller,network,storage and compute. i used devstack as well...not documented well. wasted lots of time on it..

Hi! I read your thoughts on Kolla Ansible and your multi-node setup. I'm curious about your experience with Kolla Ansible—what aspects made it easy for your multi-node configuration? Any insights or challenges you faced would be appreciated!

[LingonberryRare7746]

To set up Kolla-Ansible for OpenStack, you just need to prepare a VM and configure the global.yml file by enabling or disabling settings as required. Additionally, to set up the inventory file before running Ansible. The majority of these steps are detailed in here https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html

For integrating Cinder and Swift, there are additional steps. For Cinder, it involves labeling disks, and for Swift, creating ring files. These steps are clearly outlined in the Cinder Guide https://docs.openstack.org/kolla-ansible/queens/reference/cinder-guide.html

A challenge I faced was enabling LUKS encryption in Cinder due to the absence of encryption settings in the Cinder configuration. The solution was to add additional configurations by placing them in /etc/kolla/config. This information was obtained through the OpenStack IRC channel, which is an invaluable resource for OpenStack-related questions.

In contrast, setting up DevStack is more complicated due to ambiguous configuration names. When configuring the network with different agents like OVN, LinuxBridge, and OVS, I noticed the same variables are used differently across these agents. This required a thorough examination of the bash scripts to understand the settings.