<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Hi Zhi Chang,</div><div>Maybe you should add a config option in [ovs] section: bridge_mappings = public:br-ex, physnet1:br-physnet1 to handle the provider network 'physnet1'.</div><div><br></div><div>Thanks,</div><div>shihanzhang</div><div style="position:relative;zoom:1"></div><div id="divNeteaseMailCard"></div><br>At 2016-11-01 11:56:33, "zhi" <changzhi1990@gmail.com> wrote:<br> <blockquote id="isReplyContent" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><div dir="ltr">hi shihanzhang.<div><br></div><div>Below is configuration in ml2_conf.ini. Please review it. :)</div><div><br></div><div><div>stack@devstack:~/neutron/neutron$ cat /etc/neutron/plugins/ml2/ml2_conf.ini |grep -v "#"|grep -v ^$</div><div>[DEFAULT]</div><div>[ml2]</div><div>tenant_network_types = vxlan</div><div>extension_drivers = port_security</div><div>mechanism_drivers = openvswitch,linuxbridge</div><div>tenant_network_types = vxlan</div><div>[ml2_type_flat]</div><div>flat_networks = public,public,</div><div>[ml2_type_geneve]</div><div>vni_ranges = 1:1000</div><div>[ml2_type_gre]</div><div>tunnel_id_ranges = 1:1000</div><div>[ml2_type_vlan]</div><div>network_vlan_ranges = physnet1,physnet2</div><div>[ml2_type_vxlan]</div><div>vni_ranges = 1:1000</div><div>[securitygroup]</div><div>firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver</div><div>[agent]</div><div>tunnel_types = vxlan</div><div>root_helper_daemon = sudo /usr/local/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf</div><div>root_helper = sudo /usr/local/bin/neutron-rootwrap /etc/neutron/rootwrap.conf</div><div>[ovs]</div><div>datapath_type = system</div><div>bridge_mappings = public:br-ex</div><div>tunnel_bridge = br-tun</div><div>local_ip = 192.168.10.20</div></div><div><br></div><div><br></div><div><br></div><div>Thanks</div><div>Zhi Chang</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-11-01 9:15 GMT+08:00 shihanzhang <span dir="ltr"><<a href="mailto:ayshihanzhang@126.com" target="_blank">ayshihanzhang@126.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">hi Zhi chang,<br><div>Could you provide your ml2_conf.ini for ovs agent, I guess the reason is that your ovs-agent on host devstack can't handle the related segment id.</div><br><div style="zoom:1"></div><div id="m_3678170977224185101divNeteaseMailCard"></div><div>Thanks,</div><div>shihanzhang</div><div><div class="h5"><div><br></div>ÔÚ 2016-10-31 18:43:36£¬"zhi" <<a href="mailto:changzhi1990@gmail.com" target="_blank">changzhi1990@gmail.com</a>> дµÀ£º<br> <blockquote id="m_3678170977224185101isReplyContent" style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><div dir="ltr">Hi, all.<div><br></div><div>Recently, I watch the OpenStack Summit video named ' Scaling Up OpenStack Networking with Routed Networks '. Carl and Miguel made this topic. I learned a lot of your topic. Thanks. </div><div><br></div><div>But I have some questions about the demo in the topic. </div><div><br></div><div>I do some steps according to the topic. </div><div><br></div><div>First, creating two networks like this:</div><div><br></div><div><div>neutron net-create multinet --shared --segments type=dict list=true provider:physical_network=<wbr></wbr>physnet1,provider:<wbr></wbr>segmentation_id=2016,provider:<wbr></wbr>network_type=vlan provider:physical_network=<wbr></wbr>physnet2,provider:<wbr></wbr>segmentation_id=2016,provider:<wbr></wbr>network_type=vlan</div></div><div><br></div><div><br></div><div>Second, I get two segments after creating this network. I get these segments by using " openstack network segment list ". </div><div><br></div><div>Third, I create two subnets by these segments by using this command " </div><div><br></div><div><div>neutron subnet-create --ip_version 4 --name multi-segment1-subnet [net-id] <a href="http://10.1.0.0/24" target="_blank">10.1.0.0/24</a> --segment_id [segment-id]</div><div>neutron subnet-create --ip_version 4 --name multi-segment2-subnet [net-id] <a href="http://10.1.1.0/24" target="_blank">10.1.1.0/24</a> --segment_id [segment-id]</div></div><div> "</div><div><br></div><div>At last, I want to create a port with host_id. My local environment contains two compute nodes, one is named "devstack" and the other is "devstack2". So I use this command " neutron port-create --binding:host_id=devstack [net-id] ". </div><div><br></div><div>Exception happens in neutron server. The exception says "</div><div><br></div><div>Host devstack is not connected to any segments on routed provider network [net-id]. It should be connected to one." I can not get this exact point about this exception. </div><div><br></div><div>Why does the "routed network" have relationship with host? </div><div><br></div><div>How they work together between "host info (compute node ?)" and "routed network"?</div><div><br></div><div>What should I do if I want to get rid of this exception?</div><div><br></div><div><br></div><div>Hope for your reply. Especially Carl and Miguel. ;-)</div><div><br></div><div><br></div><div><br></div><div>Many Thanks</div><div>Zhi Chang</div></div>
</blockquote></div></div></div><br><br><span title="neteasefooter"><p> </p></span><br>______________________________<wbr></wbr>______________________________<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">OpenStack-dev-request@lists.<wbr></wbr>openstack.org?subject:<wbr></wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr></wbr>cgi-bin/mailman/listinfo/<wbr></wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br><span title="neteasefooter"><p> </p></span>