[openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

zhi changzhi1990 at gmail.com
Tue Nov 1 06:31:35 UTC 2016


Hi, shihanzhang.

Thanks for your advice. Now I can created ports successfully by your
advice.



Thanks
Zhi Chang


2016-11-01 12:50 GMT+08:00 shihanzhang <ayshihanzhang at 126.com>:

> Hi Zhi Chang,
> Maybe you should add a config option in [ovs] section: bridge_mappings =
> public:br-ex, physnet1:br-physnet1 to handle the provider network
> 'physnet1'.
>
> Thanks,
> shihanzhang
>
> At 2016-11-01 11:56:33, "zhi" <changzhi1990 at gmail.com> wrote:
>
> hi shihanzhang.
>
> Below is configuration in ml2_conf.ini. Please review it. :)
>
> stack at devstack:~/neutron/neutron$ cat /etc/neutron/plugins/ml2/ml2_conf.ini
> |grep -v "#"|grep -v ^$
> [DEFAULT]
> [ml2]
> tenant_network_types = vxlan
> extension_drivers = port_security
> mechanism_drivers = openvswitch,linuxbridge
> tenant_network_types = vxlan
> [ml2_type_flat]
> flat_networks = public,public,
> [ml2_type_geneve]
> vni_ranges = 1:1000
> [ml2_type_gre]
> tunnel_id_ranges = 1:1000
> [ml2_type_vlan]
> network_vlan_ranges = physnet1,physnet2
> [ml2_type_vxlan]
> vni_ranges = 1:1000
> [securitygroup]
> firewall_driver = neutron.agent.linux.iptables_firewall.
> OVSHybridIptablesFirewallDriver
> [agent]
> tunnel_types = vxlan
> root_helper_daemon = sudo /usr/local/bin/neutron-rootwrap-daemon
> /etc/neutron/rootwrap.conf
> root_helper = sudo /usr/local/bin/neutron-rootwrap
> /etc/neutron/rootwrap.conf
> [ovs]
> datapath_type = system
> bridge_mappings = public:br-ex
> tunnel_bridge = br-tun
> local_ip = 192.168.10.20
>
>
>
> Thanks
> Zhi Chang
>
> 2016-11-01 9:15 GMT+08:00 shihanzhang <ayshihanzhang at 126.com>:
>
>> hi Zhi chang,
>> 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.
>>
>> Thanks,
>> shihanzhang
>>
>> 在 2016-10-31 18:43:36,"zhi" <changzhi1990 at gmail.com> 写道:
>>
>> Hi, all.
>>
>> 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.
>>
>> But I have some questions about the demo in the topic.
>>
>> I do some steps according to the topic.
>>
>> First, creating two networks like this:
>>
>> neutron net-create multinet --shared --segments type=dict list=true
>> provider:physical_network=physnet1,provider:segmentation_id=
>> 2016,provider:network_type=vlan     provider:physical_network=phys
>> net2,provider:segmentation_id=2016,provider:network_type=vlan
>>
>>
>> Second, I get two segments after creating this network. I get these
>> segments by using " openstack network segment list ".
>>
>> Third, I create two subnets by these segments by using this command "
>>
>> neutron subnet-create --ip_version 4 --name multi-segment1-subnet
>> [net-id] 10.1.0.0/24 --segment_id [segment-id]
>> neutron subnet-create --ip_version 4 --name multi-segment2-subnet
>> [net-id] 10.1.1.0/24 --segment_id [segment-id]
>>  "
>>
>> 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] ".
>>
>> Exception happens in neutron server. The exception says "
>>
>> 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.
>>
>> Why does the "routed network" have relationship with host?
>>
>> How they work together between "host info (compute node ?)" and "routed
>> network"?
>>
>> What should I do if I want to get rid of this exception?
>>
>>
>> Hope for your reply. Especially Carl and Miguel. ;-)
>>
>>
>>
>> Many Thanks
>> Zhi Chang
>>
>>
>>
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161101/d20c1c2b/attachment.html>


More information about the OpenStack-dev mailing list