Carl,
I have added the + community in this List.
Please find my thoughts how it may/can evolve later once BGP is introduced.
Data center will host multi-Tennant with overlapping address amount tenants
with private IP address.
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.
Since there is overlapping , these “ private-IP needs to be injected with
corresponding VPN into BGP respective vrf-table”
We may have multiple options
1. Learn these IP dynamically by each BGP inject this IP to Gate way BGP.
2. Inject all the VM ip to Gateway router by Controller.
==> OpenStack Controller to add the private Prefix ?
==> Or ODL controller to add ?
When VM moves dynamically to different subnet/Rack: : adding
by controller and then advertising this new prefix may be too late ?
Let me know the opinions.
Thank & regards,
Keshava
-----Original Message-----
From: Carl Baldwin (Code Review) [mailto:rev...@openstack.org]
Sent: Friday, June 27, 2014 9:51 AM
To: Artem Dmytrenko; Jaume Devesa
Cc: 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
Carl Baldwin has posted comments on this change.
Change subject: BGP dynamic routing
......................................................................
Patch Set 8: Code-Review-1
(3 comments)
Still concerned about the first diagram. Ping me tomorrow if you want.
https://review.openstack.org/#/c/90833/8/specs/juno/bgp-dynamic-routing.rst
File specs/juno/bgp-dynamic-routing.rst:
Line 29: Allow Neutron to dynamically announce to from external uplink
nit: maybe insert "and/or" here between to and from.
Line 50: gateway_router[color = red];
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.
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.
Line 93: uplink_router1;
This diagram is more like what I was thinking. Here, it might make sense for
openstack to speak with the uplinks.
--
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<mailto:nexton...@yahoo.com>>
Gerrit-Reviewer: Anthony Veiga
<anthony_ve...@cable.comcast.com<mailto:anthony_ve...@cable.comcast.com>>
Gerrit-Reviewer: Artem Dmytrenko
<nexton...@yahoo.com<mailto:nexton...@yahoo.com>>
Gerrit-Reviewer: Carl Baldwin <carl.bald...@hp.com<mailto:carl.bald...@hp.com>>
Gerrit-Reviewer: Itsuro Oda <o...@valinux.co.jp<mailto:o...@valinux.co.jp>>
Gerrit-Reviewer: Jaume Devesa <devv...@gmail.com<mailto:devv...@gmail.com>>
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: Nachi Ueno <na...@ntti3.com<mailto:na...@ntti3.com>>
Gerrit-Reviewer: Pedro Marques
<pedro.r.marq...@gmail.com<mailto:pedro.r.marq...@gmail.com>>
Gerrit-Reviewer: Sean M. Collins
<sean_colli...@cable.comcast.com<mailto:sean_colli...@cable.comcast.com>>
Gerrit-Reviewer: YAMAMOTO Takashi
<yamam...@valinux.co.jp<mailto:yamam...@valinux.co.jp>>
Gerrit-Reviewer: fumihiko kakuma
<kak...@valinux.co.jp<mailto:kak...@valinux.co.jp>>
Gerrit-Reviewer: keshava <keshav...@hp.com<mailto:keshav...@hp.com>>
Gerrit-Reviewer: mark mcclain
<mmccl...@yahoo-inc.com<mailto:mmccl...@yahoo-inc.com>>
Gerrit-HasComments: Yes
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
