Hi Keshava, I'm afraid that your use case is out of the scope of this bp. We have thought only to provide admin API to share external/provider network routes. Due IP ranges overlapping, share tenant networks won't be able with my approach.
However, I find that after BGP will be implemented, with a few changes (as let the user create RoutingInstance entities, add tenant_id field in that entity and use underlaying VPN technology), your use case would be feasible. Take a look at Nachi Ueno's spec: https://review.openstack.org/#/c/93329/ I think is so close to your proposal. Regards, jaume On 25 June 2014 19:51, A, Keshava <keshav...@hp.com> wrote: > Hi, > > > > If BGP can export its private-IP to upstream they can be placed in the > corresponding VRF table w.r.t that VPN. > > In the below example Geographically separated Data-center hosts same > Customers (Red, Blue Customer). > > If BGP from virtual Network exports its IP to upstream BGP VRF table (of > that VPN), then from there using carrier’s carrier mechanism , BGP will > carry respective VRF route entries to remote site BGP Routing table. > > During packet forwarding from remote-site , the remote router will look > into its corresponding VRF table entries to check where is the destination > for that IP. > > Based on the packet will be forwarded on respective VPN tunnel . > > > > *So private-IP should be advertised by BGP from the cloud under that > respective VRF (VPN).* > > > > Thanks ®ards, > > Keshava > > > > -----Original Message----- > From: Jaume Devesa (Code Review) [mailto:rev...@openstack.org] > Sent: Wednesday, June 25, 2014 3:06 PM > To: Artem Dmytrenko > Cc: Baldwin, Carl (OpenStack Neutron); mark mcclain; Sean M. Collins; > Anthony Veiga; Pedro Marques; Nachi Ueno; YAMAMOTO Takashi; Itsuro Oda; > fumihiko kakuma; A, Keshava > Subject: Change in openstack/neutron-specs[master]: BGP dynamic routing > > > > Jaume Devesa has posted comments on this change. > > > > Change subject: BGP dynamic routing > > ...................................................................... > > > > > > Patch Set 8: > > > > (3 comments) > > > > Hi keshava, > > > > I've tried to answer your questions, but I am not confident about your use > case. Can you explain me, please? Or ping me anytime at irc (my nickname is > devvesa) > > > > https://review.openstack.org/#/c/90833/8/specs/juno/bgp-dynamic-routing.rst > > File specs/juno/bgp-dynamic-routing.rst: > > > > Line 120: namespace in the compute node. > > > Please make it clear: If DVR is turned-on BGP can be enabled or not ? > > BGP can be enabled. However, I think this paragraph crosses concepts that > may confuse people. I will delete in the next patch. > > > > > > Line 123: to an upstream router. It does not require learning routes from > the upstream > > > Is it possible how to block learning from upstream peer router ? > > Yes, is absolutely configurable. If you see the RoutingInstance entity > down below, you will see that you can choose either you want to learn or > advertise the routes . > > > > > > Line 159: Overview > > > Is it possible to enabled BGP only on private IP address ? > > With the RoutingInstance entity, you put together: > > > > 1. Which peers you want to connect > > 2. Which networks are involved > > 3. Whether to enable/disable discovery AND advertise of routes. > > > > Also, you will be able to add advertise routes manually. > > > > So theoretically, you will be able to advertise a private IP address, > although I can not see the use case of this. > > > > > > -- > > To view, visit https://review.openstack.org/90833 > > To unsubscribe, visit https://review.openstack.org/settings > > > > Gerrit-MessageType: comment > > Gerrit-Change-Id: I41b66c1c3083d7c8205368353302fafdb7a110c8 > > Gerrit-PatchSet: 8 > > Gerrit-Project: openstack/neutron-specs > > Gerrit-Branch: master > > Gerrit-Owner: Artem Dmytrenko <nexton...@yahoo.com> > > Gerrit-Reviewer: Anthony Veiga <anthony_ve...@cable.comcast.com> > > Gerrit-Reviewer: Artem Dmytrenko <nexton...@yahoo.com> > > Gerrit-Reviewer: Carl Baldwin <carl.bald...@hp.com> > > Gerrit-Reviewer: Itsuro Oda <o...@valinux.co.jp> > > Gerrit-Reviewer: Jaume Devesa <devv...@gmail.com> > > Gerrit-Reviewer: Jenkins > > Gerrit-Reviewer: Nachi Ueno <na...@ntti3.com> > > Gerrit-Reviewer: Pedro Marques <pedro.r.marq...@gmail.com> > > Gerrit-Reviewer: Sean M. Collins <sean_colli...@cable.comcast.com> > > Gerrit-Reviewer: YAMAMOTO Takashi <yamam...@valinux.co.jp> > > Gerrit-Reviewer: fumihiko kakuma <kak...@valinux.co.jp> > > Gerrit-Reviewer: keshava <keshav...@hp.com> > > Gerrit-Reviewer: mark mcclain <mmccl...@yahoo-inc.com> > > Gerrit-HasComments: Yes > -- Jaume Devesa Software Engineer at Midokura
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
