Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I have it working... almost.

I ended up re-installing everything on my OpenStack host, including the host OS (CentOS 6.5 - basic server installation). After installing CentOS, I set up eth0 as static & the default route. For reference, here is my eth0 config:

DEVICE=eth0
HWADDR=E4:1F:13:1F:46:C4
TYPE=Ethernet
UUID=39fb6462-d33b-4700-ad0c-304945de92b8
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=192.168.1.12
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.168.1.1
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"

I left eth1 as disabled for now.

As seen in thisguide provided by c0nsaw I set SELINUX=permissive. This was different from my previous setup where I had left SELINUX=enforcing.

Then I ran the RDO installation as per the linked post (and many others just like it) using the havana-release repo and packstack --allinone --provision-all-in-one-ovs-bridge=n. This will bind all the various OpenStack components to either my loopback or eth0 network interface according to PackStack.

After Packstack did it's thing, I configured my br-ex and eth1 interfaces as follows:

/etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
HWADDR=E4:1F:13:1F:46:C6
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes
NM_CONTROLLED=no
IPV6INIT=no

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.10.10.100
NETMASK=255.255.255.0
DNS1=10.10.10.1
ONBOOT=yes

Restart the network service and loged into Horizon from 192.168.1.12 as admin and deleted all the existing networking components from the demo and admin tenants. After clearing out all the existing demo networking, I created a whole new set of virtual networking resources using the following commands from my host's CLI:

 . keystonerc_admin
neutron net-create public --router:external=True
neutron subnet-create public 10.10.10.0/24 --name public_subnet --enable_dhcp=False --allocation-pool start=10.10.10.101,end=10.10.10.199 --gateway=10.10.10.1
neutron router-create router1
neutron router-gateway-set router1 public

For the tenant private network and sub-network, I set up through horizon. Added some inbound rules to the default security group, started a test instance, assigned a floating IP and I was able to ping out and in.

I did not set up any policy based routing.

The only issue remaining is that all ports off the public network show their status as DOWN even though I am able to pass traffic between my physical network to/from my virtual network. Open-VSwitch shows all the corresponding virtual interfaces correctly.

I've seen some references to a 'bug' in openstack that causes this behavior. I'll have to conduct a little more research before I claim that this is the reason.

However, for now my instances are online and available!