Yes, let's move discussion to bug report.
On Fri, Jun 23, 2017 at 5:01 AM, Margin Hu wrote:
> Hi kevin,
>
> [ovs]
> bridge_mappings = physnet1:br-ex,physnet2:provision,physnet3:provider
> ovsdb_connection = tcp:10.53.16.12:6640
> local_ip = 10.53.32.12
> you can check the attachement, and more
Hi kevin,
[ovs]
bridge_mappings = physnet1:br-ex,physnet2:provision,physnet3:provider
ovsdb_connection = tcp:10.53.16.12:6640
local_ip = 10.53.32.12
you can check the attachement, and more logs can be found at
https://bugs.launchpad.net/neutron/+bug/1697243
On 6/23 16:43, Kevin Benton wrote:
Can you provide your ml2_conf.ini values you are using?
On Thu, Jun 22, 2017 at 7:06 AM, Margin Hu wrote:
> thanks.
>
> I met an issue , I configured three ovs bridge ( br-ex, provision,
> provider) in ml2_conf.ini but after I reboot the node , found only 2
> bridges flow table is normal , the
thanks.
I met an issue , I configured three ovs bridge ( br-ex, provision,
provider) in ml2_conf.ini but after I reboot the node , found only 2
bridges flow table is normal , the other one bridge's flow table is empty.
the bridge sometimes is "provision" , sometimes is "provider" , which
p
Rules to allow aren't setup until the port is wired and it calls the
functions like this:
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L602-L606
On Wed, Jun 21, 2017 at 4:49 PM, Margin Hu wrote:
> Hi Guys,
>
> I have a questi
Hi Guys,
I have a question in setup_physical_bridges funtion of
neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py
# block all untranslated traffic between bridges
self.int_br.drop_port(in_port=int_ofport)
br.drop_port(in_port=phys_ofport)
[refer]