Neutron Extension for BGP Based VPN

Registered by Nachi Ueno on 2013-03-27

This BP implements partial RFC4364 BGP/MPLS IP Virtual Private Networks (VPNs) support for interconnecting existing network and OpenStack cloud, or inter connection of OpenStack Cloud.

Blueprint information

Status:
Complete
Approver:
Mark McClain
Priority:
Undefined
Drafter:
Nachi Ueno
Direction:
Needs approval
Assignee:
Nachi Ueno
Definition:
Superseded
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Armando Migliaccio on 2015-10-13

Related branches

Sprints

Whiteboard

I have some questions about the use case 2. The BGP is carrying the routes of the virtual network. For interacting with external site, you have to exchange routing information with the external site so BGP makes sense. In use case 2, all regions are on the same administrator domain. the routes are known already so virtual router can be configured automatically. There should be no need to exchange routing information.

<-- This sounds like there is no need for iBGP. (Nachi)

(carl_baldwin, 2014-03-10): Is the neutron virtual router playing the role of a CE in these use cases? Is it a BGP peer to some PE and the route_target/import_target/export_target are exchanged between CE and PE as described in the last paragraph of section 4.3.1 of the RFC? That is the way I see it. Please correct me if I'm wrong.

(carl_baldwin, 2014-03-10): Also, is it assumed that this neutron router's gateway interface is connected to a private external network representing the "attachment circuit" connecting the CE and PE as described in section 3.1 of the RFC? Let me know if I'm way off here. If I am, I could use some more detailed topology diagrams to help me understand.

<-- This is a kind of implementation detail. The API express only how to connect l3vpn and existing network. (Nachi)

(?)

Work Items