Add Static/Dynamic Routes to a L3 BGPVPN

Registered by Jan Scheurich

This blueprint addresses the need to advertise more than just fixed IPs of a Port as routes in a L3 BGPVPN, in particular "static" routes.

An example of a static route use is : advertise that "1.2.3.0/24 is behind Port <UUID>" as a route in BGPVPN foo.

See etherpad for other "non static" examples.

Blueprint information

Status:
Complete
Approver:
Mathieu Rohon
Priority:
Medium
Drafter:
Jan Scheurich
Direction:
Approved
Assignee:
Thomas Morin
Definition:
Superseded
Series goal:
Accepted for pike
Implementation:
Not started
Milestone target:
milestone icon 5.0.0
Completed by
Thomas Morin

Related branches

Sprints

Whiteboard

Was initially discussed in https://etherpad.openstack.org/p/bgpvpn_static_routes
Then in https://etherpad.openstack.org/p/bgpvpn_advanced_features

Now in https://etherpad.openstack.org/p/bgpvpn_port_routes

API Specification: https://review.openstack.org/#/c/467277

Moving the blueprint to "Approved", the discussion is pursued in the API spec proposal.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.