Sunday, October 2, 2016
Saturday, October 1, 2016
Mirantis Fuel - deploy OpenStack
Using Mirantis 7.0 from https://www.mirantis.com/software/mirantis-openstack/releases/ - use the iso image to boot a virtual server under VirtualBox.
Mirantis can then deploy OpenStack to two other virtual servers. Once the 2 "slave" servers are deployed, you can log on to the OpenStack console (Horizon) and create virtual servers, virtual networks (switches), virtual routers, import images of other cloud servers; for example from http://cloud-images.ubuntu.com/.
After deploying, I ran 'ifconfig -a' on all three systems, and grouped where the IP addresses appeared to be on the same subnet. Note Horizon 172.16.0.3 is not a physical interface, it's a virtual IP on the compute node (slave1).
After deploying some instances of virtual networks and servers, here is how the virtual parts align with the physical parts:
Observe that the 172.160.0.x address that is the "associated IP" for the internal virtual server (associated / mapped to the virtual server in 192.168.111.x), is in the same routing domain and IP address subnet as they physical 172.16.0.1 address of the Fuel server, the application virtual IP accessing Horizon at 172.16.0.3, and now the IP you will use to access the virtual server created by OpenStack.
Mirantis can then deploy OpenStack to two other virtual servers. Once the 2 "slave" servers are deployed, you can log on to the OpenStack console (Horizon) and create virtual servers, virtual networks (switches), virtual routers, import images of other cloud servers; for example from http://cloud-images.ubuntu.com/.
After deploying, I ran 'ifconfig -a' on all three systems, and grouped where the IP addresses appeared to be on the same subnet. Note Horizon 172.16.0.3 is not a physical interface, it's a virtual IP on the compute node (slave1).
After deploying some instances of virtual networks and servers, here is how the virtual parts align with the physical parts:
Observe that the 172.160.0.x address that is the "associated IP" for the internal virtual server (associated / mapped to the virtual server in 192.168.111.x), is in the same routing domain and IP address subnet as they physical 172.16.0.1 address of the Fuel server, the application virtual IP accessing Horizon at 172.16.0.3, and now the IP you will use to access the virtual server created by OpenStack.