Ask Your Question
0

Network Neutron - how to configure Openstack itself are VMs

asked 2015-05-14 09:21:58 -0500

cykchee2 gravatar image

Hi All,

I'm following the installation guide for OpenStack at: http://docs.openstack.org/icehouse/in...

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

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2015-05-14 11:28:33 -0500

updated 2015-05-16 01:27:52 -0500

I have done similar setup with F21 KVM Hypervisor VMs as Controller,Network,Compute Nodes.
Attempt to use management network as external for 3 node config caused crash on Network Node for me. Solution was to create three Libvirt subnets :-

# cat openstackvms.xml
<network>
   <name>openstackvms</name>
   <uuid>d0e9964a-f91a-40c0-b769-a609aee41bf2</uuid>
   <forward mode='nat'>
     <nat>
       <port start='1024' end='65535'/>
     </nat>
   </forward>
   <bridge name='virbr1' stp='on' delay='0' />
   <mac address='52:54:00:60:f8:6d'/>
   <ip address='192.169.142.1' netmask='255.255.255.0'>
     <dhcp>
       <range start='192.169.142.2' end='192.169.142.254' />
     </dhcp>
   </ip>
 </network>

[root@junoJVC01 ~]# cat public.xml
<network>
   <name>public</name>
   <uuid>d0e9965b-f92c-40c1-b749-b609aed42cf2</uuid>
   <forward mode='nat'>
     <nat>
       <port start='1024' end='65535'/>
     </nat>
   </forward>
   <bridge name='virbr2' stp='on' delay='0' />
   <mac address='52:54:00:60:f8:6d'/>
   <ip address='172.24.4.225' netmask='255.255.255.240'>
     <dhcp>
       <range start='172.24.4.226' end='172.24.4.238' />
     </dhcp>
   </ip>
 </network>

[root@junoJVC01 ~]# cat vteps.xml
<network>
   <name>vteps</name>
   <uuid>d0e9965b-f92c-40c1-b749-b609aed42cf2</uuid>
   <forward mode='nat'>
     <nat>
       <port start='1024' end='65535'/>
     </nat>
   </forward>
   <bridge name='virbr3' stp='on' delay='0' />
   <mac address='52:54:00:60:f8:6d'/>
   <ip address='10.0.0.1' netmask='255.255.255.0'>
     <dhcp>
       <range start='10.0.0.1' end='10.0.0.254' />
     </dhcp>
   </ip>
 </network>

1. First Libvirt subnet "openstackvms" serves as management network. All 3 VM are attached to this subnet
2. Second Libvirt subnet "public" serves for simulation external network Network Node attached to public,latter on "eth2" interface (belongs to "public") is supposed to be converted into OVS port of br-ex on Network Node. This Libvirt subnet via libvirt's bridge virbr2 172.24.4.25 provides VMs running on Compute Node access to Internet due to match to external network created by packstack installation 172.24.4.224/28
3.Third Libvirt subnet "vteps" serves for VTEPs endpoint simulation. Network and Compute Node VMs are attached to this subnet.Details here http://bderzhavets.blogspot.com/2015/...
image description

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-05-14 09:21:58 -0500

Seen: 1,439 times

Last updated: May 16 '15