Re: [openstack-dev] [devstack] Question about the "OVS_PHYSICAL_BRIDGE" attribute defined in localrc

[Andreas Scheuring]

I'm not sure about the exact reason, but this is what I think: 

It's intended behavior, as adding an interface to a bridge is a
disruptive task. Here an example.

You want to add your eth0 interface that has an ip address assigned to
your bridge br-p1p1. You could do this with ovs-vsctl add-port br-p1p1
eth0. This causes your eth0 to become a slave of the bridge --> you
cannot use the eth0 device for communication anymore. So your host won't
be reachable over the network anymore! To solve this you have to take
away the ip configuration of your eth interface and put this config on
your br-p1p1. E.g ifconfig eth0 0; ifconfig br-p1p1 1.2.3.4/24
Now your host should be reachable again.

If eth0 is your only interface, I guess there's a big risk, that you
lock out yourself if this would be part of devstack.

Hope that helps


-- 
Andreas 
(irc: scheuran)


On Wed, 2014-10-15 at 14:28 +, Danny Choi (dannchoi) wrote:
> Hi,
> 
> 
> When I have "OVS_PHYSICAL_BRIDGE=br-p1p1” defined in localrc, devstack
> creates the OVS bridge "br-p1p1".
> 
> 
> localadmin@qa4:~/devstack$ sudo ovs-vsctl show
> 
> 5f845d2e-9647-47f2-b92d-139f6faaf39e
> 
> Bridge "br-p1p1" <
> 
> Port "phy-br-p1p1"
> 
> Interface "phy-br-p1p1"
> 
> type: patch
> 
> options: {peer="int-br-p1p1"}
> 
> Port "br-p1p1"
> 
> Interface "br-p1p1"
> 
> type: internal
> 
> 
> However, no physical port is added to it.  I have to manually do it.
> 
> 
> localadmin@qa4:~/devstack$ sudo ovs-vsctl add-port br-p1p1 p1p1
> 
> localadmin@qa4:~/devstack$ sudo ovs-vsctl show
> 
> 5f845d2e-9647-47f2-b92d-139f6faaf39e
> 
>Bridge "br-p1p1"
> 
>Port "phy-br-p1p1"
> 
>Interface "phy-br-p1p1"
> 
>type: patch
> 
>options: {peer="int-br-p1p1"}
> 
>Port "br-p1p1"
> 
>Interface "br-p1p1"
> 
>type: internal
> 
>Port “p1p1” <
> 
> Interface “p1p1"
> 
> 
> 
> Is this expected behavior?
> 
> 
> Thanks,
> 
> Danny
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [devstack] Question about the "OVS_PHYSICAL_BRIDGE" attribute defined in localrc

[Paddu Krishnan (padkrish)]

The agent code only sets up the patch/veth ports between the physical bridge 
and the integration bridge. I believe the physical port has to be manually 
added.

Thanks,
Paddu

From: "Danny Choi (dannchoi)" mailto:dannc...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, October 14, 2014 8:51 AM
To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [devstack] Question about the "OVS_PHYSICAL_BRIDGE" 
attribute defined in localrc

Hi,

When I have "OVS_PHYSICAL_BRIDGE=br-p1p1” defined in localrc, devstack creates 
the OVS bridge "br-p1p1".

localadmin@qa4:~/devstack$ sudo ovs-vsctl show
5f845d2e-9647-47f2-b92d-139f6faaf39e
Bridge "br-p1p1" <
Port "phy-br-p1p1"
Interface "phy-br-p1p1"
type: patch
options: {peer="int-br-p1p1"}
Port "br-p1p1"
Interface "br-p1p1"
type: internal

However, no physical port is added to it.  I have to manually do it.

localadmin@qa4:~/devstack$ sudo ovs-vsctl add-port br-p1p1 p1p1
localadmin@qa4:~/devstack$ sudo ovs-vsctl show
5f845d2e-9647-47f2-b92d-139f6faaf39e
Bridge "br-p1p1"
Port "phy-br-p1p1"
Interface "phy-br-p1p1"
type: patch
options: {peer="int-br-p1p1"}
Port "br-p1p1"
Interface "br-p1p1"
type: internal
Port “p1p1” <
Interface “p1p1"


Is this expected behavior?

Thanks,
Danny
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev