Tenant Networking

In our Instance Creation doc to keep things simple we attach our instances directly to the King's network and use Security Groups to allow access via SSH. For more complex architectures that involve traffic between multiple VMs within an OpenStack project we recommend configuring an internal "tenant" network.

Navigating the "Network" section of the OpenStack UI yields the following sections.

Network Topology

Gives a graphical overview of the whole network in the project and provides shortcuts to most objects.

Networks

An internal network can be created for VMs to be associated with. Open the dialogue to create a network and:

1. Leave the default settings and add a unique network name.
2. Select 'Subnet', add a unique subnet name and network address. The hint suggests
   192.168.0.0/24 which will provide 254 usable addresses (although one will be taken for the
   gateway address).
3. Additional subnet details can be added although it is not necessary for most uses.

For VMs that need to be connected to from outside the project (e.g. via SSH, HTTP/S or VDI) a floating IP on the external network will also need to be associated in addition to any internal network interfaces.

Routers

To allow VMs with only internal network interfaces to communicate with external services one must configure a router.

1. Create a router with a unique name attached to the external network
2. Select the router by clicking on its name
3. Select the 'Interfaces' tab and add an interface
4. Choose the internal subnet you want the router to connect to