[openstack-dev] Change in openstack/neutron-specs[master]: BGP dynamic routing

A, Keshava keshava.a at hp.com
Wed Jun 25 17:51:27 UTC 2014


Hi,



[cid:image004.png at 01CF90CC.29214C90]

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  &regards,

Keshava



-----Original Message-----
From: Jaume Devesa (Code Review) [mailto:review at 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 <nextone92 at yahoo.com<mailto:nextone92 at yahoo.com>>

Gerrit-Reviewer: Anthony Veiga <anthony_veiga at cable.comcast.com<mailto:anthony_veiga at cable.comcast.com>>

Gerrit-Reviewer: Artem Dmytrenko <nextone92 at yahoo.com<mailto:nextone92 at yahoo.com>>

Gerrit-Reviewer: Carl Baldwin <carl.baldwin at hp.com<mailto:carl.baldwin at hp.com>>

Gerrit-Reviewer: Itsuro Oda <oda at valinux.co.jp<mailto:oda at valinux.co.jp>>

Gerrit-Reviewer: Jaume Devesa <devvesa at gmail.com<mailto:devvesa at gmail.com>>

Gerrit-Reviewer: Jenkins

Gerrit-Reviewer: Nachi Ueno <nachi at ntti3.com<mailto:nachi at ntti3.com>>

Gerrit-Reviewer: Pedro Marques <pedro.r.marques at gmail.com<mailto:pedro.r.marques at gmail.com>>

Gerrit-Reviewer: Sean M. Collins <sean_collins2 at cable.comcast.com<mailto:sean_collins2 at cable.comcast.com>>

Gerrit-Reviewer: YAMAMOTO Takashi <yamamoto at valinux.co.jp<mailto:yamamoto at valinux.co.jp>>

Gerrit-Reviewer: fumihiko kakuma <kakuma at valinux.co.jp<mailto:kakuma at valinux.co.jp>>

Gerrit-Reviewer: keshava <keshava.a at hp.com<mailto:keshava.a at hp.com>>

Gerrit-Reviewer: mark mcclain <mmcclain at yahoo-inc.com<mailto:mmcclain at yahoo-inc.com>>

Gerrit-HasComments: Yes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140625/147edb8e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oledata.mso
Type: application/octet-stream
Size: 12320 bytes
Desc: oledata.mso
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140625/147edb8e/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.emz
Type: application/octet-stream
Size: 17885 bytes
Desc: image003.emz
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140625/147edb8e/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 17909 bytes
Desc: image004.png
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140625/147edb8e/attachment-0001.png>


More information about the OpenStack-dev mailing list