Re: [openstack-dev] [Neutron] BGP support
On 30 March 2016 at 17:07, Abhishek Raut wrote: > I think what Gary is talking about is BGP and the Border Gateway API > spec[1] in L2 GW repo. > [1] https://review.openstack.org/#/c/270786/ > Spec [1] has nothing to do with BGP (the routing protocol) last time I checked (note to self: I should go and have another look). We should probably consider clarify the confusion that stems from the use of the word 'Border' in spec [1]. A. > > —Abhishek Raut > > From: "Tidwell, Ryan" > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Wednesday, March 30, 2016 at 4:52 PM > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Neutron] BGP support > > Gary, > > > > I’m not sure I understand the relationship you’re drawing between BGP and > L2 GW, could you elaborate? The BGP code that landed in Mitaka is mostly > geared toward the use case where you want to directly route your tenant > networks without any NAT (ie no floating IP’s, no SNAT). Neutron peers > with upstream routers and announces prefixes that tenants allocate > dynamically. We have talked about how we could build on what was merged in > Mitaka to support L3 VPN in the future, but to my knowledge no concrete > plan has emerged as of yet. > > > > -Ryan > > > > *From:* Gary Kotton [mailto:gkot...@vmware.com ] > *Sent:* Sunday, March 27, 2016 11:36 PM > *To:* OpenStack List > *Subject:* [openstack-dev] [Neutron] BGP support > > > > Hi, > > In the M cycle BGP support was added in tree. I have seen specs in the L2 > GW project for this support too. Are we planning to consolidate the > efforts? Will the BGP code be moved from the Neutron git to the L2-GW > project? Will a new project be created? > > Sorry, a little in the dark here and it would be nice if someone could > please provide some clarity here. It would be a pity that there were > competing efforts and my take would be that the Neutron code would be the > single source of truth (until we decide otherwise). > > I think that the L2-GW project would be a very good place for that service > code to reside. It can also have MPLS etc. support. So it may be a natural > fit. > > Thanks > > Gary > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] BGP support
I think what Gary is talking about is BGP and the Border Gateway API spec[1] in L2 GW repo. [1] https://review.openstack.org/#/c/270786/ -Abhishek Raut From: "Tidwell, Ryan" mailto:ryan.tidw...@hpe.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, March 30, 2016 at 4:52 PM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron] BGP support Gary, I'm not sure I understand the relationship you're drawing between BGP and L2 GW, could you elaborate? The BGP code that landed in Mitaka is mostly geared toward the use case where you want to directly route your tenant networks without any NAT (ie no floating IP's, no SNAT). Neutron peers with upstream routers and announces prefixes that tenants allocate dynamically. We have talked about how we could build on what was merged in Mitaka to support L3 VPN in the future, but to my knowledge no concrete plan has emerged as of yet. -Ryan From: Gary Kotton [mailto:gkot...@vmware.com] Sent: Sunday, March 27, 2016 11:36 PM To: OpenStack List Subject: [openstack-dev] [Neutron] BGP support Hi, In the M cycle BGP support was added in tree. I have seen specs in the L2 GW project for this support too. Are we planning to consolidate the efforts? Will the BGP code be moved from the Neutron git to the L2-GW project? Will a new project be created? Sorry, a little in the dark here and it would be nice if someone could please provide some clarity here. It would be a pity that there were competing efforts and my take would be that the Neutron code would be the single source of truth (until we decide otherwise). I think that the L2-GW project would be a very good place for that service code to reside. It can also have MPLS etc. support. So it may be a natural fit. Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] BGP support
Gary, I’m not sure I understand the relationship you’re drawing between BGP and L2 GW, could you elaborate? The BGP code that landed in Mitaka is mostly geared toward the use case where you want to directly route your tenant networks without any NAT (ie no floating IP’s, no SNAT). Neutron peers with upstream routers and announces prefixes that tenants allocate dynamically. We have talked about how we could build on what was merged in Mitaka to support L3 VPN in the future, but to my knowledge no concrete plan has emerged as of yet. -Ryan From: Gary Kotton [mailto:gkot...@vmware.com] Sent: Sunday, March 27, 2016 11:36 PM To: OpenStack List Subject: [openstack-dev] [Neutron] BGP support Hi, In the M cycle BGP support was added in tree. I have seen specs in the L2 GW project for this support too. Are we planning to consolidate the efforts? Will the BGP code be moved from the Neutron git to the L2-GW project? Will a new project be created? Sorry, a little in the dark here and it would be nice if someone could please provide some clarity here. It would be a pity that there were competing efforts and my take would be that the Neutron code would be the single source of truth (until we decide otherwise). I think that the L2-GW project would be a very good place for that service code to reside. It can also have MPLS etc. support. So it may be a natural fit. Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] BGP support
Hi, Thanks for the clarification. I still feel like there may be some overlap here. Thanks Gary From: Irena Berezovsky mailto:irenab@gmail.com>> Date: Monday, March 28, 2016 at 11:16 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>>, Gary Kotton mailto:gkot...@vmware.com>> Subject: Re: [openstack-dev] [Neutron] BGP support Hi Gary, The new L2GW spec is [1] comes to enable inter-cloud connection to stretch the network between the local and the remote clouds using tunnels between border VTEP devices. VTEP can be populated manually with remote MAC (optionally) IP entries. BGP support is a bit orthogonal or may I say complementary. [1] https://review.openstack.org/#/c/270786/ On Mon, Mar 28, 2016 at 9:36 AM, Gary Kotton mailto:gkot...@vmware.com>> wrote: Hi, In the M cycle BGP support was added in tree. I have seen specs in the L2 GW project for this support too. Are we planning to consolidate the efforts? Will the BGP code be moved from the Neutron git to the L2-GW project? Will a new project be created? Sorry, a little in the dark here and it would be nice if someone could please provide some clarity here. It would be a pity that there were competing efforts and my take would be that the Neutron code would be the single source of truth (until we decide otherwise). I think that the L2-GW project would be a very good place for that service code to reside. It can also have MPLS etc. support. So it may be a natural fit. Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] BGP support
Hi Gary, The new L2GW spec is [1] comes to enable inter-cloud connection to stretch the network between the local and the remote clouds using tunnels between border VTEP devices. VTEP can be populated manually with remote MAC (optionally) IP entries. BGP support is a bit orthogonal or may I say complementary. [1] https://review.openstack.org/#/c/270786/ On Mon, Mar 28, 2016 at 9:36 AM, Gary Kotton wrote: > Hi, > In the M cycle BGP support was added in tree. I have seen specs in the L2 > GW project for this support too. Are we planning to consolidate the > efforts? Will the BGP code be moved from the Neutron git to the L2-GW > project? Will a new project be created? > Sorry, a little in the dark here and it would be nice if someone could > please provide some clarity here. It would be a pity that there were > competing efforts and my take would be that the Neutron code would be the > single source of truth (until we decide otherwise). > I think that the L2-GW project would be a very good place for that service > code to reside. It can also have MPLS etc. support. So it may be a natural > fit. > Thanks > Gary > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] BGP support
Hi Gary, Could you please provide the spec details.. Thanks Vikram On Mon, Mar 28, 2016 at 1:27 PM, Gary Kotton wrote: > Thanks for the pointers. Any reason why this is not part of the L2 gateway > effort? I think that could be a natural place for this. The project name > may be a bit misleading, but at the end of the day the Neutron tenant will > have network connectivity irrespective if a neutron network is realized in > a number of different places that are connected either via MPLS or BGP or > any other protocol. > I think that creating another project is just fragmenting things even more > … > > From: Hirofumi Ichihara > Reply-To: OpenStack List > Date: Monday, March 28, 2016 at 10:50 AM > To: OpenStack List > Subject: Re: [openstack-dev] [Neutron] BGP support > > Hi Gary, > > You can look at the discussion in here[1, 2] > > [1]: https://bugs.launchpad.net/neutron/+bug/1560003 > [2]: https://review.openstack.org/#/c/268726 > > Thanks, > Hirofumi > > On 2016/03/28 15:36, Gary Kotton wrote: > > Hi, > In the M cycle BGP support was added in tree. I have seen specs in the L2 > GW project for this support too. Are we planning to consolidate the > efforts? Will the BGP code be moved from the Neutron git to the L2-GW > project? Will a new project be created? > Sorry, a little in the dark here and it would be nice if someone could > please provide some clarity here. It would be a pity that there were > competing efforts and my take would be that the Neutron code would be the > single source of truth (until we decide otherwise). > I think that the L2-GW project would be a very good place for that service > code to reside. It can also have MPLS etc. support. So it may be a natural > fit. > Thanks > Gary > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] BGP support
Thanks for the pointers. Any reason why this is not part of the L2 gateway effort? I think that could be a natural place for this. The project name may be a bit misleading, but at the end of the day the Neutron tenant will have network connectivity irrespective if a neutron network is realized in a number of different places that are connected either via MPLS or BGP or any other protocol. I think that creating another project is just fragmenting things even more … From: Hirofumi Ichihara mailto:ichihara.hirof...@lab.ntt.co.jp>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Monday, March 28, 2016 at 10:50 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron] BGP support Hi Gary, You can look at the discussion in here[1, 2] [1]: https://bugs.launchpad.net/neutron/+bug/1560003 [2]: https://review.openstack.org/#/c/268726 Thanks, Hirofumi On 2016/03/28 15:36, Gary Kotton wrote: Hi, In the M cycle BGP support was added in tree. I have seen specs in the L2 GW project for this support too. Are we planning to consolidate the efforts? Will the BGP code be moved from the Neutron git to the L2-GW project? Will a new project be created? Sorry, a little in the dark here and it would be nice if someone could please provide some clarity here. It would be a pity that there were competing efforts and my take would be that the Neutron code would be the single source of truth (until we decide otherwise). I think that the L2-GW project would be a very good place for that service code to reside. It can also have MPLS etc. support. So it may be a natural fit. Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] BGP support
Hi Gary, You can look at the discussion in here[1, 2] [1]: https://bugs.launchpad.net/neutron/+bug/1560003 [2]: https://review.openstack.org/#/c/268726 Thanks, Hirofumi On 2016/03/28 15:36, Gary Kotton wrote: Hi, In the M cycle BGP support was added in tree. I have seen specs in the L2 GW project for this support too. Are we planning to consolidate the efforts? Will the BGP code be moved from the Neutron git to the L2-GW project? Will a new project be created? Sorry, a little in the dark here and it would be nice if someone could please provide some clarity here. It would be a pity that there were competing efforts and my take would be that the Neutron code would be the single source of truth (until we decide otherwise). I think that the L2-GW project would be a very good place for that service code to reside. It can also have MPLS etc. support. So it may be a natural fit. Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] BGP support
Hi, In the M cycle BGP support was added in tree. I have seen specs in the L2 GW project for this support too. Are we planning to consolidate the efforts? Will the BGP code be moved from the Neutron git to the L2-GW project? Will a new project be created? Sorry, a little in the dark here and it would be nice if someone could please provide some clarity here. It would be a pity that there were competing efforts and my take would be that the Neutron code would be the single source of truth (until we decide otherwise). I think that the L2-GW project would be a very good place for that service code to reside. It can also have MPLS etc. support. So it may be a natural fit. Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev