...
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.
...
- 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
- Server groups: Advanced functionality, where you can create server groups for your VMs, with different scheduling policies. I.e making sure that instances is spread across different physical hosts.
- 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:
- Container Infra: Container cluster administration
- Clusters: Start page for managing container clusters (i.e kubernetes)
- Cluster Templates: Templates for container cluster creation
- 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
- Load balancers: Manage virtual load balancers
- 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.
- Object Store: Object storage administration
- Containers: Your containers for object storage
- 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.
...
First is the network-pane, which requires you to give the new network a name (do not change the other defaults):
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.
In this example the subnet "10192.14168.110.0/24" is used.
The final part of the network configuration dialog is to define additional DHCP parameters for any hosts placed in this network. DO NOT UNTICK THE "ENABLE DHCP" BOX! The defaults (shown in the picture) is sufficient, but the following can be defined if wanted:
- 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. The blank default will use NTNUs nameservers (129.241.0.200 and 129.241.0.201).
- 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, leave the "Enable Admin State" ticked, and select which external network this router should be connected to. This articles has an overview of the various external networks available.
When the router is created, click on its name to start configuring it. We need to add an interface to the router, so click the "Add Interface" button.
Select the desired subnet from the "Subnet" list, and submit the form. Note that the IP address is optional. That means it has a sane default (the first addressable IP in the selected subnet).
A look at the Network Topology graph should display something like so:
Configuring access parametres
...