Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Network Neutron - how to configure Openstack itself are VMs

Hi All,

I'm following the installation guide for OpenStack at: http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron_initial-external-network.html

I follow the instructions architecture to have: - Three-node architecture with OpenStack Networking (neutron)

i) Controller Node (controller)
   eth0: 10.0.0.11/24  Management
ii) Network Node (network)
   eth0: 10.0.0.21/24  Management
   eth1: 10.0.1.21/24  Instance Tunnels
   eth2: Unnumbered  External
iii) Compute Node (compute1)
   eth0: 10.0.0.31/24  Management
   eth1: 10.0.1.31/24  Instance Tunnels

One Twist: My controller, network and compute1 nodes are ALL VM themselves. Using VirtualBox as the host on my laptop, my controller/network/compute1 are 3 Linux centos6.4 VMs, connected via Host Only configuration. Hence in addition to the above, i have

Network:  192.168.82.216 
Controller: 192.168.82.217
Compute1:  192.168.82.218

In the documentation, it says:

For example, using 203.0.113.0/24 with floating IP address range 203.0.113.101 to 203.0.113.200:

$ neutron subnet-create ext-net --name ext-subnet --allocation-pool start=203.0.113.101,end=203.0.113.200 --disable-dhcp --gateway 203.0.113.1 203.0.113.0/24

Does that mean in my case, instead of 203.0.113.1 203.0.113.0/24; I would instead have something like: 192.168.82.1 192.168.82.0/24 and maybe a range of 192.168.82.210 to 192.168.82.220?

Basically, instead of 203.0.113.X being the external network, is my external network 192.168.82.X?


In addition to this, my three nodes are also Bridges to my real laptop machine

Network:  192.168.1.19
Controller: 192.168.1.103
Compute1:  192.168.1.101

I suppose I can switch off this VirtualBox bridged interface, so that the 192.168.1.X would not interfere with the OpenStack subnet which is also 192.168.1.X

Thanks