Single-node guided
This tutorial shows how to install OpenStack (based on project Sunbeam). It will deploy an OpenStack 2024.1 (Caracal) cloud.
Requirements
You will need a single machine whose requirements are:
- physical or virtual machine running Ubuntu 24.04 LTS
- a multi-core amd64 processor (ideally with 4+ cores)
- a minimum of 16 GiB of free memory
- 50 GiB of SSD storage available on the root disk
- two network interfaces
- primary: for access to the OpenStack control plane
- secondary: for remote access to cloud VMs
Caution: Any change in IP address of the local host will be detrimental to the deployment. A virtual host will generally have a more stable address.
Important: For environments constrained by a proxy server, the target machine must first be configured accordingly. See section Configure for the proxy at the OS level on the Manage a proxied environment page before proceeding.
Control plane networking
The network associated with the primary network interface requires a range of approximately ten IP addresses that will be used for API service endpoints.
For the purposes of this tutorial, the following configuration is in place:
| Network component | Value |
|---|---|
| CIDR | 172.16.1.0/24 |
| Gateway | 172.16.1.1 |
| Address range | 172.16.1.201-172.16.1.220 |
| Interface name on machine | eno1 |
External networking
The network associated with the secondary network interface requires a range of IP addresses that will be sufficient for allocating floating IP addresses to VMs. This will, in turn, allow them to be contacted by remote hosts.
For the purposes of this tutorial, the following configuration is in place:
| Network component | Value |
|---|---|
| CIDR | 172.16.2.0/24 |
| Gateway | 172.16.2.1 |
| Address range | 172.16.2.2-172.16.2.254 |
| Interface name on machine | eno2 |
Deploy the cloud
The cloud deployment process consists of several stages: installing a snap, preparing the cloud node machine, bootstrapping the cloud, and finally configuring the cloud.
Note: During the deployment process you will be asked to input information in order to configure your new cloud. These questions are explained in more detail on the Interactive configuration prompts page in the reference section.
Install the openstack snap
Begin by installing the openstack snap:
sudo snap install openstack --channel 2024.1/beta
Caution: It is highly recommended to use the --channel 2024.1/beta switch which includes all the latest bug fixes and updates before the next stable release coming in Q4 2024.
Prepare the machine
Sunbeam can generate a script to ensure that the machine has all of the required dependencies installed and is configured correctly for use in OpenStack - you can review this script using:
sunbeam prepare-node-script
or the script can be directly executed in this way:
sunbeam prepare-node-script | bash -x && newgrp snap_daemon
The script will ensure some software requirements are satisfied on the host. In particular, it will:
- install
openssh-serverif it is not found - configure passwordless sudo for all commands for the current user (
NOPASSWD:ALL)
Bootstrap the cloud
Deploy the OpenStack cloud using the cluster bootstrap command:
sunbeam cluster bootstrap
On snap channel 2024.1/beta, you will first be prompted whether or not to enable network proxy usage. If ‘Yes’, several sub-questions will be asked.
Use proxy to access external network resources? [y/n] (y):
http_proxy ():
https_proxy ():
no_proxy ():
Note that proxy settings can also be supplied by using a manifest (see Deployment manifest).
When prompted, enter the CIDR and the address range for the control plane networking. Here we use the values given earlier:
Management network (172.16.1.0/24):
OpenStack APIs IP ranges (172.16.1.201-172.16.1.240): 172.16.1.201-172.16.1.220
Configure the cloud
Now configure the deployed cloud using the configure command:
sunbeam configure --openrc demo-openrc
The --openrc option specifies a regular user (non-admin) cloud init file (demo-openrc here).
A series of questions will now be asked. Below is a sample output of an entire interactive session. The values in square brackets, when present, provide acceptable values. A value in parentheses is the default value. Here we use the values given earlier:
Local or remote access to VMs [local/remote] (local): remote
External network (172.16.2.0/24):
External network’s gateway (172.16.2.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********):
Project network (192.168.0.0/24):
Enable ping and SSH access to instances? [y/n] (y):
External network’s allocation range (172.16.2.2-172.16.2.254):
External network’s type [flat/vlan] (flat):
Writing openrc to demo-openrc ... done
External network’s interface [eno1/eno2] (eno1): eno2
Any remote hosts intending to connect to VMs on this node (remote access in first question) must have connectivity with the interface selected for external traffic (last question above).
Launch a VM
Verify the cloud by launching a VM called ‘test’ based on the ‘ubuntu’ image (Ubuntu 22.04 LTS). The launch command is used:
sunbeam launch ubuntu --name test
Sample output:
Launching an OpenStack instance ...
Access instance with `ssh -i /home/ubuntu/.config/openstack/sunbeam [email protected]`
Connect to the VM over SSH. Because remote VM access has been enabled, you will need the private SSH key given in the above output from the launching node. Copy it to the connecting host. Note that the VM will not be ready instantaneously; waiting time is mostly determined by the cloud’s available resources.
Related how-tos
Now that OpenStack is set up, be sure to check out the following howto guides: