Allow a guest VM to deposit routes in its own VRF via BGP protocol

Registered by OpenContrail Admin on 2015-09-29

This feature requires guest VM to be able to connect to control node and advertise routes into the VRF.

Detail:

vRouter Agent will be modified to accept BGP connections from the VMs and proxy them to the Control node

vRouter Agent will always choose one of the active Control nodes that it is using as XMPP servers
The proxy feature will be enabled based on the following configuration:

Configuration API:
Model is similar to Junos. 2 BGP Router objects are configured under the virtual network (RI). One object represents the Control node and the other object represents the VNF
A connection between these 2 objects represents peering and peering families can be configured as properties on this connection.

Configuration Model for the VNFs:
From the VNF point of view, it has a Inet-BGP peering configuration with the default gateway. The default gateway has to be the vRouter in this virtual network
There will be a configurable limit on the # of prefixes the VNF can send
2nd BGP session for HA can also be configured appropriately using one more BGP router object in the Contrail config and from the VNFs point of view peering session to the DNS IP address (reserved by Contrail)

CAVEATS & NOTES
BGP sessions must use IPv4 transport
VNF has to support RFC 2545 to carry IPv6 routes over IPv4 peer
Only inet and inet6 address family will be supported

Blueprint information

Status:
Complete
Approver:
Ashish Ranjan
Priority:
High
Drafter:
Ashish Ranjan
Direction:
Approved
Assignee:
Nischal Sheth
Definition:
Approved
Series goal:
Accepted for r3.0
Implementation:
Implemented
Milestone target:
milestone icon r3.0-fcs
Started by
Ashish Ranjan on 2016-03-01
Completed by
Ashish Ranjan on 2016-03-01

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.