Skip to content

Quick-start

All-in-one

The easiest way to get started with Atmosphere is to deploy the all-in-one installation. This will install an entire stack of Atmosphere, with Ceph and all the OpenStack services inside a single machine.

Info

The all-in-one installation is not for production use, it's perfect for testing and development.

Warning

The all-in-one will fully take-over the machine by making system-level changes. It's recommended to run it inside a virtual machine or a physical machine that can be dedicated to this purpose.

In order to get started, you'll need a Ubuntu 22.04 system with the following minimum system requirements:

  • Cores: 8 threads / vCPUs
  • Memory: 32GB

If you're looking to run Kubernetes clusters, you'll need more memory for the workloads, it following minimum is recommended (but more memory is always better!):

  • Cores: 16 threads / vCPUs
  • Memory: 64GB

Info

If you're running this inside a virtual machine, it is extremely important that the virtual machines supported nested virtualization, otherwise the performance of the VMs will be un-usable.

You can use the following commands to deploy the all-in-one environment:

# Install dependencies
sudo apt-get update
sudo apt-get install git python3-pip
sudo pip install poetry

# Clone the repository
git clone https://github.com/vexxhost/atmosphere.git

# Deploy AIO
cd atmosphere
sudo poetry install --with dev
sudo poetry run molecule converge -s aio

Once the deployment is done, you can either use the CLI to interact with the OpenStack environment, or you can access the Horizon dashboard.

For the CLI, you can source /root/openrc and then use the openstack CLI. For example, if you want to list the networks, you can run the following command:

source /root/openrc
openstack network list

For the Horizon dashboard, you can find the URL to access it by running the following command:

kubectl -n openstack get ingress/dashboard -ojsonpath='{.spec.rules[0].host}'

You can find the credentials to login to the dashboard reading the /root/openrc file. You can use the following variables to match the credentials:

  • Username: OS_USERNAME
  • Password: OS_PASSWORD
  • Domain: OS_USER_DOMAIN_NAME