OpenStack with All-in-One via Packstack - No bridge mapping

Latest response

I am testing RHOS 4.0 and used a basic all-in-one scenario with an interactive packstack setup. Everything went great except that packstack did not actually set the: CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:eth1 line up inside of OVS. I had to manually make the mapping happen via: ovs-vsctl add-port br-ex eth1

Once I added the port mapping by hand all of my instances could get out.

There were no errors reported during the packstack run.

My packstack file is attached.

I don't see anything in the documentation stating that packstack/puppet won't add the OVS port setup. Is this a known issue?

Thanks,
Shannon

Attachments

SM
Log in to join the conversation

Responses

rhn-support-jdexter's picture Red Hat Active Contributor 130 points
16 March 2014 1:58 AM

Shannon,
This issue has come up in the past a few times.
There is actually a parameter in the packstack answer file that addresses adding the external bridge to an all-in-one installation.

# Whether to configure the ovs external bridge in an all-in-one
# deployment
CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE=n

This added feature is mentioned in the Technical notes in section 3.3.
A more detailed method of adding the OVS bridge is described in the Installation and configuration Guide

SM Community Member 25 points
20 March 2014 6:37 AM

Thanks Jeff. I am traveling out of the country right now but when I get back I will give this a try. Makes total sense. Sorry I missed that in the docs.

rhn-support-jdexter's picture Red Hat Active Contributor 130 points
22 March 2014 2:48 AM

Shannon, not a problem, its down at the bottom of the answer file. I missed it the first 20 or 30 times I did a packstack install.
If you want to set up the br-ex external bridge after the install, you can also look at this solution Red Hat instances unable to reach external network after packstack install

SM Community Member 25 points
4 April 2014 4:33 PM

Just a follow-up Jeff. This worked great using the CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE=y option.

SM Community Member 25 points
5 April 2014 3:24 PM

Actually, on a fresh rebuild this is not working. I set this: CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE=y but it does not set the port correctly for eth1:
Bridge br-ex
Port phy-br-ex
Interface phy-br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: "1.11.0"

I have to manually add it for it to work.

David Powles's picture Red Hat 25369 points
7 April 2014 6:42 AM

Thanks for letting us know, Shannon. Is this working with the manual update, or do you need further help?

SM Community Member 25 points
16 April 2014 5:40 PM

Dave, sorry for the delay. I am at the RH Summit and behind on email notifications. So I have narrowed it down a bit. When I set the CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE=y value it looks like it does part of the job. I have not had a chance to look at your puppetry on this but the ifcfg-eth1 file (the one identified in the answer file that is used for external access) is not getting fully setup correctly for OVS. The install is setting up the ifcfg-br-ex file but the ifcfg-eth1 file is not getting touched at all.

When I manually update the ifcfg-eth1 file to include the below, it all works great.
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.