<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>thanks. <br>
</p>
<p>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. <br>
</p>
<p>the bridge sometimes is "provision" , sometimes is "provider" ,
which possibilities is there for this issue.? <br>
</p>
[root@cloud]# ovs-ofctl show provision<br>
OFPT_FEATURES_REPLY (xid=0x2): dpid:0000248a075541e8<br>
n_tables:254, n_buffers:256<br>
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS
ARP_MATCH_IP<br>
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan
mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src
mod_tp_dst<br>
1(bond0): addr:24:8a:07:55:41:e8<br>
config: 0<br>
state: 0<br>
speed: 0 Mbps now, 0 Mbps max<br>
2(phy-provision): addr:2e:7c:ba:fe:91:72<br>
config: 0<br>
state: 0<br>
speed: 0 Mbps now, 0 Mbps max<br>
LOCAL(provision): addr:24:8a:07:55:41:e8<br>
config: 0<br>
state: 0<br>
speed: 0 Mbps now, 0 Mbps max<br>
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0<br>
[root@cloud]# ovs-ofctl dump-flows provision<br>
NXST_FLOW reply (xid=0x4):<br>
<br>
[root@cloud]# ip r<br>
default via 192.168.60.247 dev br-ex<br>
10.53.16.0/24 dev vlan16 proto kernel scope link src 10.53.16.11<br>
10.53.17.0/24 dev provider proto kernel scope link src
10.53.17.11<br>
10.53.22.0/24 dev vlan22 proto kernel scope link src 10.53.22.111<br>
10.53.32.0/24 dev vlan32 proto kernel scope link src 10.53.32.11<br>
10.53.33.0/24 dev provision proto kernel scope link src
10.53.33.11<br>
10.53.128.0/24 dev docker0 proto kernel scope link src
10.53.128.1<br>
169.254.0.0/16 dev vlan16 scope link metric 1012<br>
169.254.0.0/16 dev vlan22 scope link metric 1014<br>
169.254.0.0/16 dev vlan32 scope link metric 1015<br>
169.254.0.0/16 dev br-ex scope link metric 1032<br>
169.254.0.0/16 dev provision scope link metric 1033<br>
169.254.0.0/16 dev provider scope link metric 1034<br>
192.168.60.0/24 dev br-ex proto kernel scope link src
192.168.60.111<br>
<br>
what' the root cause ? <br>
<br>
rpm -qa | grep openvswitch<br>
openvswitch-2.6.1-4.1.git20161206.el7.x86_64<br>
python-openvswitch-2.6.1-4.1.git20161206.el7.noarch<br>
openstack-neutron-openvswitch-10.0.1-1.el7.noarch<br>
<br>
<br>
<div class="moz-cite-prefix">On 6/22 9:53, Kevin Benton wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAO_F6JMYrPUThwRgQDPc6tvT=b=j03rdm=ng6VMdcDazuEVygQ@mail.gmail.com">
<div dir="ltr">
<div>Rules to allow aren't setup until the port is wired and it
calls the functions like this:</div>
<a
href="https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L602-L606"
moz-do-not-send="true">https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L602-L606</a><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jun 21, 2017 at 4:49 PM, Margin
Hu <span dir="ltr"><<a href="mailto:today.good@163.com"
target="_blank" moz-do-not-send="true">today.good@163.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Guys,<br>
<br>
I have a question in setup_physical_bridges funtion of
neutron/plugins/ml2/drivers/op<wbr>envswitch/agent/ovs_neutron_ag<wbr>ent.py<br>
<br>
# block all untranslated traffic between bridges<br>
self.int_br.drop_port(in_port=<wbr>int_ofport)<br>
br.drop_port(in_port=phys_ofpo<wbr>rt)<br>
<br>
[refer](<a
href="https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1159"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/ope<wbr>nstack/neutron/blob/master/neu<wbr>tron/plugins/ml2/drivers/openv<wbr>switch/agent/ovs_neutron_agent<wbr>.py#L1159</a>)<br>
<br>
when permit traffic between bridges ? when modify flow
table of ovs bridge?<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank" moz-do-not-send="true">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>