Networks created within the openstack platforms are not routed trough through NTNU, and it is thus in theory it is not important exactly what which subnet is selected. It might however present be a problem if your virtual machine needs to contact external resources and you have provision your virtual machines within the same address range selected overlaps with address ranges used that is currently being use elsewhere, in case your virtual machines would like to contact external resources with the same addresses as its local causing your local address range to overlap with the address range of another network. Because of this, it is normal to create network within the RFC1918 rangescommon practice to use the address ranges specified in the RFC1918 (a.k.a IPv4 Private Address Space):
- 10.0.0.0/8
- 172.16.0.0/12
- 192.168.0.0/16
- tl;dr - use a subnet from this range to avoid any weird issues → 192.168.N.0/24 where N is a number from 0 and 255.
RFC1918 within NTNU
NTNU are is however using quite a few the following subnets within the RFC1918 range, and these subnets should thus therefore their use should be avoided:
10.0.0.0/8 - Large pieces of this range is already in use; and this block is likely to be used in new subnets within NTNU as well.
ItThe general purpose floatin-IP's assigned in openstack is also from this range, and it can thus involve a bit of confusion if both the vm's IP and the floating-ip looks the same. It is thus recommended not to
notuse this block at all
.172.16.0.0/16 - Used as floating-IP's in skyhigh.hig.
no; free in other clouds- 172.17.0.0/16 - Used within NTNU in Gjøvik, and is thus not recommended used in openstack networks.192.168.0.0 - Partly used in NTNU Ålesund (subnets listed below). The rest is free.
- 192.168.10.0/24
- 192.168.30.0/24
- 192.168.50.0/24
- 192.168.90.0/24
- 192.168.110.0/24
- 192.168.114.0/24
- 192.168.201.0/24
- 192.168.212.0/24
- 192.168.221.0/24
- 192.168.222.0/24
- 192.168.223.0/24 192.168.224.0/24