...

Depending of which openstack-installation you have been given access to, one of the following web-interfaces should be used:

• https://stack.it.ntnu.no/ (For OpenStack in Trondheim)
• https://skyhigh.iik.ntnu.no/ (For OpenStack in Gjøvik)

The SkyHiGh environment allows you to create a virtual infrastructure by your designs. This infrastructure can consist of:

• Virtual networks
• Virtual routers
• Virtual Servers

This article explains the prosess of how the initial setup of a small and simple architecture is performed trough the webinterface.

Webinterface login and navigation

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 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).

Top menus

If your user have access to more than one project, the current project can be switched using a menu in the top of the webinterface.

Left-hand menus:

To the left there is a menu which lets you administer specific parts of the infrastructure:

• Project:
  • API Access: API information
  • Compute: Virtual machine administration
    • Overview: This is the first page seen when logging in to the webinterface. Here a short summary of your project status is given.
    • Instances: This view is to administer virtual machines. Here it is possible to create new virtual machines, and administer existing machines.
    • Images: This view is to administer the images of which a virtual machine can boot from. It will always contain a wide selection of linux images (Debian, Fedora, Ubuntu, CentOS etc.) and some Windows images, and it is possible to upload your own images if the image you want is not present.
    • Key Pairs: SSH key-pairs which allows you to log into your virtual machines
  • Volumes: Volume administration
    • Volumes: This view is to administer cinder volumes, which are block-devices/persistent-storage (disks) which can be attached to virtual machines.
    • Backups:
    • Snapshots:
    • Consistency Groups:
    • Consistency Group Snapshots
  • Network: Network administration
    • Network Topology: A graphical representation of your infrastructure.
    • Networks: Your virtual networks.
    • Routers: Your virtual routers, routing
    • Security groups: The firewall protecting your virtual machines
    • Floating IPs: IP-Adresses which enables you to connect to machines from external networks.
  • Orchestration: Openstack-heat, an automation engine to roll out virtual infrastructure based on scripts.
• Identity: Lets you display information of your own affiliation to SkyHiGh.
  
  • Projects: This view is to show you which projects your user is a member of.

Creating an initial network topology

Before a virtual machine can be created, at least one network needs to be present for the machine to be present on. Creating this network, and a router to give the network external access, is described in this part.

Create a network

To create a network, you first have to navigate to "Network -> Networks" in the left hand menu, and clicking the button "create network". The dialog appearing have three sections.

...

• Allocation pools: It is possible to limit which ranges of adresses in the subnet are used to address the virtual machines. The default is to use the whole pool; which should be fine in most cases.
• DNS Name Servers: If custom DNS Servers should be used for this subnet, their adresses should be listed here.
• Host Routes: If static routes (except for the regular default-route) should be injected to the hosts, they should be listed here.

Create a router to give the network external access

The network just created is currently isolated from the rest of the world. To give this network access to other networks, and the internet, we need to create a router. Navigate to "Network -> Routers" in the left menu, and click the "Create Router" button. Give the router a name, and select which external network this router should be connected to. This articles has an overview of the various external networks available.

...

A look at the Network Topology graph should display something like so:

Configuring access parametres

The default settings does not allow much access to the resources inside skyhigh. To allow access to the virtual machines we are going to create we need to preform two steps:

1. Allow incoming SSH traffic trough our skyhigh firewall
2. Create a SSH keypair, where the public key will be injected into linux virtual machines when these are created.

Open up the firewall

It is possible to create multiple firewalls in Openstack, so that they can be tailored to each and every application. For now we are just going to modify the default firewall to allow incoming SSH traffic. Click the "Manage Rules" button.

...

It is also useful to be able to ping your virtual machines. To allow this another rule needs to be added allowing ICMP traffic:

Create SSH Keypair

Openstack can create a keypair for you, but it also allows you to inject the public part of a keypair you already created.

If you are a Windows user, and are planning to use PuTTY as your SSH client - please advise this page

Create a new keypair

To have openstack create a keypair for you, click the "Create Key Pair" button.

...

Openstack does not store the private key, so if it is lost at a later point in time you would need to create a new key.

Inject an existing public-key

Particulary linux users often have ssh-keypairs already. In their case they can upload the public part of their key to openstack, allowing openstack to inject this key to new virtual machine. The default location for such public keys are "~/.ssh/id_rsa.pub". The content of this file can be pasted in the dialog box appearing when the "Import Key Pair" button is clicked:

Creating a virtual machine

At this point everything needed to create a virtual server is available (if you follow this guide...). To create the virtual server navigate to "Compute -> Instances" and click the "Launch Instance" button:

...

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:

...