Networks

First thing, all instances in Openstack have access to the external network (internet) by default.  Giving the external network (internet) access to your instances is where the complexity lies.

 

Choose between two types of access:

 

Self Service

• As its name suggests, this network requires the least amount of admin involvement for provisioning.  Useful for quick deployments. By itself, your instance will have access to the internet but will not be accessible from the outside. The only way to access will be through the console.
• The only way to gain access from the outside is with a floating IP.
  • (gui) Create and Attach Floating IP
  • (cmd) Create and Attach Floating IP

 

Provider

• The provider network relies on an external network from openstack.
  • • Openstack controls only two facts about the interface:
      1. The MAC of the interface
      2. The security groups of the interface
  • This requires the admin to provision a mac address and ip to a DHCP server
    • So if you do not have access to the DHCP server on the subnet the provider is on you won’t be able to get the instance online automatically.
    • However, if you have console access, you can get to the instance once its booted, log into the console and configure the network interface with the static ip of the provider port.  You’ll need to know the IP, subnet and gateway along with the DNS addresses since DHCP won’t be there to provide it.
  • The network requires significant involvement from the admin and thus needs to be planned ahead of time in order to be efficient in any deployment.

Admin:

• (gui) Create a Provider Port
• (cmd) Create a Provider Port

 

How can I tell the difference between a Self Service and Provider Network?

 

Usually,  you can tell by the name of the network in Openstack

 

Self Service:

Anything that “ends” with a “-net” is a self service network

Provider:

Anything that starts with “Vlan”  or “VLAN” is a provider network.

If you have any questions about which is a provider or which is a self service just ask!

 

GT:

Self Service:

If your instance only uses the self service there is not much you have to deal with on the GT side.

However, if you have to attach a floating ip to it,

• you will need to work with GT  DNS (gtipam.dns.gatech.edu) or your local DNS to associate the floating ip with a DNS record.
• Will also need to work with GT Firewall (fw.noc.gatech.edu) to clear access ports as well as work with security groups in openstack.

Provider:

You will need to work with DNS and Firewalls as if you are on a self service network with a floating ip already attached.