Multiple external networks with a single L3 agent

In the old days (so, like, last year), Neutron supported a single external network per L3 agent. You would run something like this...

$ neutron net-create external --router:external=true

...and neutron would map this to the bridge defined in external_network_bridge in /etc/neutron/l3_agent.ini. If you wanted to support …

read more

Video: Configuring OpenStack's external bridge on a single-interface system

I've just put a video on Youtube that looks at the steps required to set up the external bridge (br-ex) on a single-interface system:

read more

Open vSwitch and persistent MAC addresses

Normally I like to post solutions, but today's post is about a vexing problem to which I have not been able to find a solution.

This started as a simple attempt to set up external connectivity on an all-in-one Icehouse install deployed on an OpenStack instance. I wanted to add eth0 to br-ex in order to model a typical method for providing external connectivity, but I ran into a very odd problem: the system would boot and work fine for a few seconds, but would then promptly lose network connectivity.

read more

Solved: Open vSwitch and persistent MAC addresses

In my previous post I discussed a problem I was having setting a persistent MAC address on an OVS bridge device. It looks like the short answer is, "don't use ip link set ..." for this purpose.

You can set the bridge MAC address via ovs-vsctl like this:

ovs-vsctl set bridge …
read more

Fedora and OVS Bridge Interfaces

I run OpenStack on my laptop, and I've been chasing down a pernicious problem with OVS bridge interfaces under both F19 and F20. My OpenStack environment relies on an OVS bridge device named br-ex for external connectivity and for making services available to OpenStack instances, but after rebooting, br-ex was …

read more