...
When accessing the webinterface, you are presented with a login-page. The domain dropdown should be set to "NTNU accounts", and the "User Name" and "Password" fields should be populated with your NTNU username (only the username, no @stud.ntnu.no @ntnu.no etc.) and password.
Dashboard
After a successful login (which is possible only if your user has access to at least one SkyHiGh project), you are presented with a dashboard. This dashboard displays your current resource usage and your current quota limits. The top of the interface shows your current project name (right above the pointer in the image).
...
First is the network-pane, which requires you to give the new network a name (do not change the other defaults):
The MTU field has a sane default, do not fill in a value here if you don't know what you are doing.
Then the network needs at least one subnet; and the first subnet is created in the "subnet" pane. Give it a name, choose "Enter Network Address manually", and select an IP range. It is not necessary to fill in anything for Gateway IP, it has a sane default (the first usable address in your selected subnet). See this article to see which addresses to select.
...
Next you would need to select what your machine should boot from, and where it should store its files.There are a wide range of pre-made images available, containing a wide range of operating systems. To use one of these, select "Image" as the boot source.
It is Usually we recommended to not create a new volume but rather use the disk provided to the machine when a flavor is selected, as the disk associated with the flavor is not counted towards your storage-quota. Selecting yes when creating an image will create downtime during patch window since the vm can't be live migrated during stack upgrade. If a new volume is created, its size will be result in the disk-size being taken from your storage qouta.
It is possible to search in the list of images. In this case it is searched for a debian an ubuntu image, and "Debian 8.7.0Ubuntu 20.04 LTS (Focal Fossa) amd64" is selected.
After an image is selected, it is time to select how powerful machine is needed. The amount of CPU and RAM are limited by your projects quotas, so it is wise to use some moderation when selecting your machine size. It is possible to increase the size later; not decrease...
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
#cloud-config
ssh_authorized_keys:
- <paste public key here>
|
After pressing "Launch Instance" the openstack plattform should need a couple of seconds before your machine is running. You can see your machine in the "Instance" list.
Assigning a floating IP to the instance
Your freshly made machine lives on your own private network, created by you, and is thus currently unreachable from the rest of the world. To enable outside access to the machine you would need to assign a floating IP address to it. This is done using the Action menu:
If this is the first time you use a floating IP, there are probably no IP allocated to your project. To allocate an IP to your project you could use the small "+" button:
Select which network to allocate the floating IP from (what networks are available can be seen here). It should be the same network that were sellected when the router were created.
When an IP is allocated, it can be Associated to a certain VM:
At the end the "Instance" list should display both the internal and the floating IP.
How to actually access your virtual machine is described in this page.