Getting Started

Start a project and create the first server

Read our Tutorial on how to create your first OpenStack project and server here!

Openstack CLI


Just install the official OpenStackClient from PyPi:

pip install python-openstackclient python-barbicanclient python-cinderclient python-designateclient python-glanceclient python-heatclient python-neutronclient python-novaclient python-octaviaclient python-magnumclient python-heatclient gnocchiclient

Requires: Python >=3.8

Load the OpenStack Environment File

Now you can source the environment file. After entering the password you can send requests to the OpenStack-CLI.
If you have access to multiple projects you will be asked to choose one of the available projects before you can continue with the CLI commands.

$ source
$ openstack server list

The OpenStack Environment File also has the ability to make project switching easier for you. 
Just source the environment file again and you will be asked if you would like to switch the project.

$ source
Access token is still present. Please choose one of the following options:
1) switch project   2) re-authenticate  3) exit
Enter a number: 1
Selected option: switch project

Please select one of your OpenStack projects.

1) 18-openstack-c4dae  2) 29-openstack-a46f4
Enter a number: 2
Selected project: 29-openstack-a46f4

If you would like to only list your available projects, you can just execute the following command:

$ openstack federation project list

Have a look at the Cheat-Sheet to find commonly used CLI commands or have a look into the official OpenStackClient Docs.

Horizon dashboard

The horizon dashboard is the official Web UI for OpenStack. You will find almost anything you need to control your OpenStack cloud there.


You can log in to the horizon dashboard at with your NWS-ID. Please ask your administrator for the appropriate rights.

S1 and S2 Flavor stacks: Differences between our two VM categories

If you want to start a VM in our OpenStack, you have the choice between two VM categories: S1 and S2. 

These differ, apart from hard disk size and compute power (CPU and RAM), mainly in two points: in the IOPS and the bandwidth.


This standard unit of measurement indicates how many input and output commands can be executed per second.
The S1- flavors can process 1000 IOPS in normal operation. For a period of 60 seconds, even a peak of 2000 IOPS can be processed before it is then throttled back to the normal value.
The S2 flavors can process twice the amount of commands - i.e. 2000 IOPS - in normal operation. They can even be turned up to 4000 IOPS for 60 seconds in peak. After that, they are also turned back down to normal. 


The second difference concerns the network connection. The S1 and S2 categories differ not only in IOPS, but also in the available bandwidth. The larger the bandwidth, the more data can be transferred simultaneously within a time window.
In the S1 flavor, 1 Gbit per second can be transferred as standard. This corresponds to a data volume of 125,000 KB per second. In peak operation, the amount can double to 250,000 KB/s or 2 Gbit/s for a period of 1 minute.
With the S2 Flavor, 2 Gbit/s are available in normal operation. In peak it is even 4 Gbit/s or 500,000 KB/s. 

Who uses what?

For all those who have a memory and network-intensive load, it is therefore advisable to fall back on an S2 VM. Examples would be video streams, backup servers (which load a lot of data) or databases. Also AI machines, where large amounts of data need to be processed, should run on s2 flavors.
Here you can find the overview, which helps you to compare all possible flavors in terms of price and conditions.