Hi keshava,

> Hi,
>
>
>
> 1.       From where the MPLS traffic will be initiated ?

In this design, MPLS traffic will be initiated from a network node,
where the qrouter is located. However, we though of alternative design
where MPLS traffic is initiated on the compute node, directly from a
VM plugged in an exported IPVPN network. In this case, /32 would be
advertised, and the bgpspeaker would be hosted on each compute node.
see here :

https://docs.google.com/drawings/d/1bMXiOwHsbKS89xfE0vQMtu7D9H3XV8Cvkmcoz6rzDOE/edit?usp=sharing

>
> 2.       How it will be mapped ?

in the proposed design, the mapping in br-mpls will be done on
destinantion network received in bgp, and on the "in_port", to
distinguish trafic from each qrouter. in br-mpls, there would be one
internal port per qrouter.

Regards

Mathieu

>
>
>
> Regards,
>
> Keshava
>
> From: Damon Wang [mailto:damon.dev...@gmail.com]
> Sent: Friday, October 17, 2014 12:42 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] BGPVPN implementation discussions
>
>
>
> Good news, +1
>
>
>
> 2014-10-17 0:48 GMT+08:00 Mathieu Rohon <mathieu.ro...@gmail.com>:
>
> Hi all,
>
> as discussed during today's l3-meeting, we keep on working on BGPVPN
> service plugin implementation [1].
> MPLS encapsulation is now supported in OVS [2], so we would like to
> summit a design to leverage OVS capabilities. A first design proposal,
> based on l3agent, can be found here :
>
> https://docs.google.com/drawings/d/1NN4tDgnZlBRr8ZUf5-6zzUcnDOUkWSnSiPm8LuuAkoQ/edit
>
> this solution is based on bagpipe [3], and its capacity to manipulate
> OVS, based on advertised and learned routes.
>
> [1]https://blueprints.launchpad.net/neutron/+spec/neutron-bgp-vpn
> [2]https://raw.githubusercontent.com/openvswitch/ovs/master/FAQ
> [3]https://github.com/Orange-OpenSource/bagpipe-bgp
>
>
> Thanks
>
> Mathieu
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to