<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div> </div>
<div>Carl,</div>
<div>I have added the + community in this List.</div>
<div> </div>
<div>Please find my thoughts how it may/can evolve later once BGP is introduced.</div>
<div>Data center will host multi-Tennant with overlapping address amount tenants with private IP address.</div>
<div>When these Data centers are geographically separated, and connected over Service provider network they will continue to communicate to each other over there Private IP address only.</div>
<div>Since there is overlapping , these “ private-IP needs to be injected with corresponding VPN into BGP respective vrf-table”</div>
<div>We may have multiple options</div>
<ol style="margin:0;padding-left:54pt;">
<li>Learn these IP dynamically by each BGP inject this IP to Gate way BGP.</li><li>Inject all the VM ip to Gateway router by Controller.</li></ol>
<ul style="margin:0;padding-left:72pt;">
<li>OpenStack Controller to add the private Prefix ? </li><li>Or ODL controller to add ? </li></ul>
<div> When VM moves dynamically to different subnet/Rack: : adding by controller and then advertising this new prefix may be too late ?</div>
<div style="padding-left:54pt;"> </div>
<div>Let me know the opinions.</div>
<div> </div>
<div><img src="cid:EDC9266EC0D2E64D94EF049FDB25AF06@Compaq.com"> </div>
<div> </div>
<div> </div>
<div> </div>
<div>Thank & regards,</div>
<div>Keshava</div>
<div> </div>
<div> </div>
<div> </div>
<div>-----Original Message-----<br>
From: Carl Baldwin (Code Review) [<a href="mailto:review@openstack.org">mailto:review@openstack.org</a>]
<br>
Sent: Friday, June 27, 2014 9:51 AM<br>
To: Artem Dmytrenko; Jaume Devesa<br>
Cc: 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</div>
<div> </div>
<div>Carl Baldwin has posted comments on this change.</div>
<div> </div>
<div>Change subject: BGP dynamic routing</div>
<div>......................................................................</div>
<div> </div>
<div> </div>
<div>Patch Set 8: Code-Review-1</div>
<div> </div>
<div>(3 comments)</div>
<div> </div>
<div>Still concerned about the first diagram. Ping me tomorrow if you want.</div>
<div> </div>
<div><a href="https://review.openstack.org/#/c/90833/8/specs/juno/bgp-dynamic-routing.rst">https://review.openstack.org/#/c/90833/8/specs/juno/bgp-dynamic-routing.rst</a></div>
<div>File specs/juno/bgp-dynamic-routing.rst:</div>
<div> </div>
<div>Line 29: Allow Neutron to dynamically announce to from external uplink</div>
<div>nit: maybe insert "and/or" here between to and from.</div>
<div> </div>
<div> </div>
<div>Line 50: gateway_router[color = red];</div>
<div>In this topology, the red router is still the single router between the Openstack network and the uplinks. So, there are not multiples paths. I think openstack would have to peer with the gateway and then the gateway would have to peer with the uplinks
because it is the next hop for both uplinks.</div>
<div> </div>
<div>The red gateway router needs to be configured with the neutron networks anyway so why would it need to learn them from openstack through BGP? Why wouldn't the gateway router simply peer with the uplinks and announce what it knows? I don't see a need
for BGP in openstack with this diagram.</div>
<div> </div>
<div> </div>
<div>Line 93: uplink_router1;</div>
<div>This diagram is more like what I was thinking. Here, it might make sense for openstack to speak with the uplinks.</div>
<div> </div>
<div> </div>
<div>-- </div>
<div>To view, visit <a href="https://review.openstack.org/90833">https://review.openstack.org/90833</a></div>
<div>To unsubscribe, visit <a href="https://review.openstack.org/settings">https://review.openstack.org/settings</a></div>
<div> </div>
<div>Gerrit-MessageType: comment</div>
<div>Gerrit-Change-Id: I41b66c1c3083d7c8205368353302fafdb7a110c8</div>
<div>Gerrit-PatchSet: 8</div>
<div>Gerrit-Project: openstack/neutron-specs</div>
<div>Gerrit-Branch: master</div>
<div>Gerrit-Owner: Artem Dmytrenko <<a href="mailto:nextone92@yahoo.com">nextone92@yahoo.com</a>></div>
<div>Gerrit-Reviewer: Anthony Veiga <<a href="mailto:anthony_veiga@cable.comcast.com">anthony_veiga@cable.comcast.com</a>></div>
<div>Gerrit-Reviewer: Artem Dmytrenko <<a href="mailto:nextone92@yahoo.com">nextone92@yahoo.com</a>></div>
<div>Gerrit-Reviewer: Carl Baldwin <<a href="mailto:carl.baldwin@hp.com">carl.baldwin@hp.com</a>></div>
<div>Gerrit-Reviewer: Itsuro Oda <<a href="mailto:oda@valinux.co.jp">oda@valinux.co.jp</a>></div>
<div>Gerrit-Reviewer: Jaume Devesa <<a href="mailto:devvesa@gmail.com">devvesa@gmail.com</a>></div>
<div>Gerrit-Reviewer: Jenkins</div>
<div>Gerrit-Reviewer: Nachi Ueno <<a href="mailto:nachi@ntti3.com">nachi@ntti3.com</a>></div>
<div>Gerrit-Reviewer: Pedro Marques <<a href="mailto:pedro.r.marques@gmail.com">pedro.r.marques@gmail.com</a>></div>
<div>Gerrit-Reviewer: Sean M. Collins <<a href="mailto:sean_collins2@cable.comcast.com">sean_collins2@cable.comcast.com</a>></div>
<div>Gerrit-Reviewer: YAMAMOTO Takashi <<a href="mailto:yamamoto@valinux.co.jp">yamamoto@valinux.co.jp</a>></div>
<div>Gerrit-Reviewer: fumihiko kakuma <<a href="mailto:kakuma@valinux.co.jp">kakuma@valinux.co.jp</a>></div>
<div>Gerrit-Reviewer: keshava <<a href="mailto:keshava.a@hp.com">keshava.a@hp.com</a>></div>
<div>Gerrit-Reviewer: mark mcclain <<a href="mailto:mmcclain@yahoo-inc.com">mmcclain@yahoo-inc.com</a>></div>
<div>Gerrit-HasComments: Yes</div>
<div> </div>
</span></font>
</body>
</html>