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

...

• Project:
  • 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.
    • Volumes: This view is to administer cinder volumes, which are bloc-devices/persistent-storage (disks) which can be attached to virtual 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.
    • Access & Security: This view administers multiple access-related settings:
      • Security groups: The firewall protecting your virtual machines
      • Key Pairs: SSH key-pairs which allows you to log into your virtual machines
      • Floating IPs: IP-Adresses which enables you to connect to machines from external networks.
      • API Access: API information
  • Network: Network administration
    • Network Topology: A graphical representation of your infrastructure.
    • Networks: Your virtual networks.
    • Routers: Your virtual routers, routing
  • 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.

First is the network-pane, which requires you to give the new network a name:

Image Added

Then the network needs at least one subnet; and the first subnet is created in the "subnet" pane. Give it a name, and select an IP range. It is recommended to use some RFC1918 adresses, which includes these network blocks:

• 10.0.0.0/8
• 172.16.0.0/12
• 192.168.0.0/16

In this example the network "10.14.1.0/24" is selected.

Image Added

The final part of the network configuration dialog is to define additional DHCP parameters for any hosts placed in this network.

...

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

Image Added

Create a router to give the network external access