Cloud Services

Cloud Services based on OpenStack

Getting Started

Getting Started

Start a project and create the first server

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

Getting Started

Openstack CLI

Installation

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 nws-id-openstack-rc.sh
...
$ 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 nws-id-openstack-rc.sh
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.

Getting Started

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.

image.png

You can log in to the horizon dashboard at https://cloud.netways.de with your NWS-ID. Please ask your administrator for the appropriate rights.


Administrative Tasks

Administrative Tasks

Backups and Snapshots

Take a look at the Backup and Snapshot Tutorial to find out how to backup your servers and volumes.

Administrative Tasks

Load Balancers

The following guides only cover the basic mandatory settings. If you would like to read more about some advanced load balancer setups and settings, please refer to our Advanced Topics section or the official Basic Load Balancing Cookbook of OpenStack.

Configuration via the OpenStack Dashboard

"Load Balancers" can be found as a subsection of the submenu "Network" in the menu on the left.

Bildschirm­foto 2022-12-20 um 11.15.58.png

To create a load balancer just click on the button "+ Create Load Balancer". A window will open on that page which will help you to walk through the initial configuration.
On the first page you can fill in some basic details like name and description. It is not necessary but recommended to set a name. However it is mandatory to choose a subnet.
On a plain new OpenStack project you will find your main subnet by looking for a subnet which has the same name as your OpenStack project but with a "-subnet" extension. 
To read more about the meaning of the advanced fields, you can click on the question mark on the right side of the window.

Bildschirm­foto 2022-12-20 um 11.22.09.png

Click on the "Next" button to continue. 

On the following page you will be asked to fill in the listener details. You don't have to set a name. But make sure to choose a protocol and to set a port number. The listener defines the frontend listening port of the load balancer. Let's say you would like to deploy a load balancer for some web servers. Then you would choose HTTP or TCP as protocol and set the port to 80 or 443. 

Bildschirm­foto 2022-12-20 um 11.35.39.png

By default the "Connection Limit" is set to "-1" which means, that no limit is enforced. However we discovered that setting no limit here can cause problems

After clicking on "Next", you will be able to choose a load balancing algorithm - for default setups we recommend setting it to "ROUND_ROBIN.

Bildschirm­foto 2022-12-20 um 11.53.32.png

In the following section "Pool Members" you will be asked to assign members to the pool. The members resemble the VMs you would like to forward incoming requests to. 
Additionally you will have to set the port number where the application or web server is listening on inside of the corresponding VM.  
You can also set a weight - members with a higher weight will receive a higher amount of requests than members with lower weight.

Bildschirm­foto 2022-12-20 um 11.59.11.png

The last section will let you define a health monitor for the pool and its members. Depending on your application or web server make sure to choose an appropriate protocol type. Additionally you can set some timeouts and delay parameter according to which the health monitor will execute the health checks against the pool members.
Reminder: you can click on the question mark on the right side of the window to read more about these parameters.

Bildschirm­foto 2022-12-20 um 12.10.47.png

Now that you have filled in all the mandatory fields, you are good to go and therefore you can click on the orange button "Create Load Balancer". 
It will take a while until the load balancer and all its dependent resources have been deployed. 

As a final optional action you can associate a floating IP with your load balancer. Doing so will let you expose your load balancer to the public internet. Be aware that everyone on the internet would be able to access your application or web site running on your VMs if you assign a floating IP.
To associate a floating IP, click on the dropdown menu of your load balancer and choose "Associate Floating IP".

Bildschirm­foto 2022-12-20 um 12.22.01.png

Depending on if you already have floating IPs allocated to your OpenStack project, you can either choose a existing floating IP or allocate a new one from the window that opens up next. 
If you choose to allocate a new floating IP from a pool, make sure to select the public-network.