..
 This work is licensed under a Creative Commons Attribution 3.0 Unported
 License.

 http://creativecommons.org/licenses/by/3.0/legalcode

Specification notes
===================

Database design
---------------

The implementation will rely on three tables:

* one for BGPVPN objects

* one to define the 1-n relation ship between a BGPVPN and a set of Networks

* one to define the 1-n relation ship between a BGPVPN and a set of Routers


The information stored in these tables will reflect what is exposed on the
API, with an exception for route_targets:

* this list will not be present in the database

* on an API request to create or modify a BGPVPN: the route_targets
  parameter will be merged with import_rts, without duplicates, before storing
  in import_rts ; and the same will be done for export_rts

* on an API request to show a BGPVPN:

  * route_targets will be synthesized to include RTs present in both
    export_rts and import_rts

  * import_targets will contain only RTs not in common with export_rts

  * export_targets will contain only RTs not in common with import_rts



..
 This work is licensed under a Creative Commons Attribution 3.0 Unported
 License.

 http://creativecommons.org/licenses/by/3.0/legalcode

Specification notes
===================

Database design
---------------

The implementation will rely on three tables:

* one for BGPVPN objects

* one to define the n-n relation ship between BGPVPNs and Networks

* one to define the n-n relation ship between BGPVPNs and Routers


The information stored in these tables will reflect what is exposed on the
API.



Update the spec : remove RTs consolidation part
Update the spec : remove RTs consolidation part

RTs consolidation specified in the spec is currently not implemented.
This consolidation will have to be done at the driver level,
not at the plugin level.

Change-Id: I3b3cbbf0846f8caadb4e7ce105bd33eac460dfe9
Closes-bug: 1478998
