<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Hi Keshava,</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">
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.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">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: <a href="https://review.openstack.org/#/c/93329/">https://review.openstack.org/#/c/93329/</a> I think is so close to your proposal.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Regards,</div><div class="gmail_default" style="font-family:tahoma,sans-serif">jaume</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 25 June 2014 19:51, A, Keshava <span dir="ltr"><<a href="mailto:keshava.a@hp.com" target="_blank">keshava.a@hp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div>
<p>Hi,<u></u><u></u></p>
<p><u></u> <u></u></p>
<p><u></u><img width="463" height="482" src="cid:image004.png@01CF90CC.29214C90"><u></u><u></u><u></u></p>
<p>If BGP can export its private-IP to upstream they can be placed in the corresponding VRF table w.r.t that VPN.<u></u><u></u></p>
<p>In the below example Geographically separated Data-center hosts same Customers (Red, Blue Customer).<u></u><u></u></p>
<p>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.<u></u><u></u></p>
<p>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.<u></u><u></u></p>
<p>Based on the packet will be forwarded on respective VPN tunnel .<u></u><u></u></p>
<p><u></u> <u></u></p>
<p><b>So private-IP should be advertised by BGP from the cloud under that respective VRF (VPN).<u></u><u></u></b></p>
<p><u></u> <u></u></p>
<p>Thanks ®ards,<u></u><u></u></p>
<p>Keshava<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>-----Original Message-----<br>
From: Jaume Devesa (Code Review) [mailto:<a href="mailto:review@openstack.org" target="_blank">review@openstack.org</a>] <br>
Sent: Wednesday, June 25, 2014 3:06 PM<br>
To: Artem Dmytrenko<br>
Cc: Baldwin, Carl (OpenStack Neutron); mark mcclain; Sean M. Collins; Anthony Veiga; Pedro Marques; Nachi Ueno; YAMAMOTO Takashi; Itsuro Oda; fumihiko kakuma; A, Keshava<br>
Subject: Change in openstack/neutron-specs[master]: BGP dynamic routing</p>
<p><u></u> <u></u></p>
<p>Jaume Devesa has posted comments on this change.<u></u><u></u></p><div class="">
<p><u></u> <u></u></p>
<p>Change subject: BGP dynamic routing<u></u><u></u></p>
<p>......................................................................<u></u><u></u></p>
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
<p>Patch Set 8:<u></u><u></u></p>
<p><u></u> <u></u></p>
</div><p>(3 comments)<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Hi keshava,<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>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)<u></u><u></u></p><div class="">
<p><u></u> <u></u></p>
<p><a href="https://review.openstack.org/#/c/90833/8/specs/juno/bgp-dynamic-routing.rst" target="_blank"><span style="color:windowtext;text-decoration:none">https://review.openstack.org/#/c/90833/8/specs/juno/bgp-dynamic-routing.rst</span></a><u></u><u></u></p>
<p>File specs/juno/bgp-dynamic-routing.rst:<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Line 120: namespace in the compute node.<u></u><u></u></p>
<p>> Please make it clear: If DVR is turned-on BGP can be enabled or not ?
<u></u><u></u></p>
</div><p>BGP can be enabled. However, I think this paragraph crosses concepts that may confuse people. I will delete in the next patch.<u></u><u></u></p><div class="">
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
<p>Line 123: to an upstream router. It does not require learning routes from the upstream<u></u><u></u></p>
<p>> Is it possible how to block learning from upstream peer router ?<u></u><u></u></p>
</div><p>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 .<u></u><u></u></p><div class="">
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
<p>Line 159: Overview<u></u><u></u></p>
<p>> Is it possible to enabled BGP only on private IP address ?
<u></u><u></u></p>
</div><p>With the RoutingInstance entity, you put together:<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>1. Which peers you want to connect<u></u><u></u></p>
<p>2. Which networks are involved<u></u><u></u></p>
<p>3. Whether to enable/disable discovery AND advertise of routes.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Also, you will be able to add advertise routes manually.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>So theoretically, you will be able to advertise a private IP address, although I can not see the use case of this.<u></u><u></u></p><div class="">
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
<p>-- <u></u><u></u></p>
<p>To view, visit <a href="https://review.openstack.org/90833" target="_blank">
<span style="color:windowtext;text-decoration:none">https://review.openstack.org/90833</span></a><u></u><u></u></p>
<p>To unsubscribe, visit <a href="https://review.openstack.org/settings" target="_blank">
<span style="color:windowtext;text-decoration:none">https://review.openstack.org/settings</span></a><u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Gerrit-MessageType: comment<u></u><u></u></p>
<p>Gerrit-Change-Id: I41b66c1c3083d7c8205368353302fafdb7a110c8<u></u><u></u></p>
<p>Gerrit-PatchSet: 8<u></u><u></u></p>
<p>Gerrit-Project: openstack/neutron-specs<u></u><u></u></p>
<p>Gerrit-Branch: master<u></u><u></u></p>
<p>Gerrit-Owner: Artem Dmytrenko <<a href="mailto:nextone92@yahoo.com" target="_blank"><span style="color:windowtext;text-decoration:none">nextone92@yahoo.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Anthony Veiga <<a href="mailto:anthony_veiga@cable.comcast.com" target="_blank"><span style="color:windowtext;text-decoration:none">anthony_veiga@cable.comcast.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Artem Dmytrenko <<a href="mailto:nextone92@yahoo.com" target="_blank"><span style="color:windowtext;text-decoration:none">nextone92@yahoo.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Carl Baldwin <<a href="mailto:carl.baldwin@hp.com" target="_blank"><span style="color:windowtext;text-decoration:none">carl.baldwin@hp.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Itsuro Oda <<a href="mailto:oda@valinux.co.jp" target="_blank"><span style="color:windowtext;text-decoration:none">oda@valinux.co.jp</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Jaume Devesa <<a href="mailto:devvesa@gmail.com" target="_blank"><span style="color:windowtext;text-decoration:none">devvesa@gmail.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Jenkins<u></u><u></u></p>
<p>Gerrit-Reviewer: Nachi Ueno <<a href="mailto:nachi@ntti3.com" target="_blank"><span style="color:windowtext;text-decoration:none">nachi@ntti3.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Pedro Marques <<a href="mailto:pedro.r.marques@gmail.com" target="_blank"><span style="color:windowtext;text-decoration:none">pedro.r.marques@gmail.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: Sean M. Collins <<a href="mailto:sean_collins2@cable.comcast.com" target="_blank"><span style="color:windowtext;text-decoration:none">sean_collins2@cable.comcast.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: YAMAMOTO Takashi <<a href="mailto:yamamoto@valinux.co.jp" target="_blank"><span style="color:windowtext;text-decoration:none">yamamoto@valinux.co.jp</span></a>><u></u><u></u></p>
</div><p>Gerrit-Reviewer: fumihiko kakuma <<a href="mailto:kakuma@valinux.co.jp" target="_blank"><span style="color:windowtext;text-decoration:none">kakuma@valinux.co.jp</span></a>><u></u><u></u></p><div class="">
<p>Gerrit-Reviewer: keshava <<a href="mailto:keshava.a@hp.com" target="_blank"><span style="color:windowtext;text-decoration:none">keshava.a@hp.com</span></a>><u></u><u></u></p>
<p>Gerrit-Reviewer: mark mcclain <<a href="mailto:mmcclain@yahoo-inc.com" target="_blank"><span style="color:windowtext;text-decoration:none">mmcclain@yahoo-inc.com</span></a>><u></u><u></u></p>
</div><p>Gerrit-HasComments: Yes<u></u><u></u></p>
</div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><font face="tahoma, sans-serif">Jaume Devesa</font><div><font face="tahoma, sans-serif">Software Engineer at Midokura</font></div></div>
</div>