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)" <dannc...@cisco.com<mailto:dannc...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<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>" <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
