Open Stack

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 +0000, Danny Choi (dannchoi) wrote:
> Hi,
> 
> 
> When I have "OVS_PHYSICAL_BRIDGE=br-p1p1” defined in localrc, devstack
> creates the OVS bridge "br-p1p1".
> 
> 
> localadmin at 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 at qa4:~/devstack$ sudo ovs-vsctl add-port br-p1p1 p1p1
> 
> localadmin at 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 at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev