diff options
author | Georg Kunz <georg.kunz@ericsson.com> | 2016-07-19 14:26:16 +0200 |
---|---|---|
committer | Georg Kunz <georg.kunz@ericsson.com> | 2016-07-22 09:25:25 +0200 |
commit | a973062e984d73b04f71790af4ed1fa05172ec71 (patch) | |
tree | 9317bb92fd8b90b5c7d9a5ebf11106bba908fdcb /docs/requirements/use_cases/l3vpn_any_to_any.rst | |
parent | 183ec869bfc403db64b422280b4a6339e070f7d1 (diff) |
Working on comments and document cleanup
Commenting out some of my previous comments so that they are not
part of the final document but remain in the source code. Added
conclusion to L3VPN use cases.
Change-Id: I1f51cbce1fb496d05d005cfd440cc16a52eab0d8
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
Diffstat (limited to 'docs/requirements/use_cases/l3vpn_any_to_any.rst')
-rw-r--r-- | docs/requirements/use_cases/l3vpn_any_to_any.rst | 35 |
1 files changed, 11 insertions, 24 deletions
diff --git a/docs/requirements/use_cases/l3vpn_any_to_any.rst b/docs/requirements/use_cases/l3vpn_any_to_any.rst index b11a381..574eac6 100644 --- a/docs/requirements/use_cases/l3vpn_any_to_any.rst +++ b/docs/requirements/use_cases/l3vpn_any_to_any.rst @@ -55,13 +55,13 @@ subnet 10.1.1.0/24. -Derrived Requirements +Derived Requirements ~~~~~~~~~~~~~~~~~~~~~ Northbound API / Workflow +++++++++++++++++++++++++ -[**Georg: this section needs to be made more readable**] +.. **Georg: this section needs to be made more readable** An example of the desired workflow is as follows: @@ -87,21 +87,6 @@ An example of the desired workflow is as follows: -Data model objects -++++++++++++++++++ - - TBD - - -Orchestration -+++++++++++++ - - TBD - - -Dependencies on compute services -++++++++++++++++++++++++++++++++ - - TBD - - Current implementation ~~~~~~~~~~~~~~~~~~~~~~ @@ -181,16 +166,18 @@ Comments: * The ports are associated indirectly to the VPN through their networks. -* The BGPVPN backend takes care of distributing the /32 routes to the OVR instances - and assigning appropriate RD values. +* The BGPVPN backend takes care of distributing the /32 routes to the vForwarder + instances and assigning appropriate RD values. Gaps in the current solution ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -There are no gaps in the currently available solution which prevent realizing -this particular use case. -[**Georg: there are no gaps in terms of functionality provided by the BGPVPN -project. However, a better analysis of the multi-backend support in Neutron is -needed**] +In terms of the functionality provided by the BGPVPN project, there are no gaps +preventing this particular use case from a L3VPN perspective. + +However, in order to support the multi-vendor aspects of this use case, a better +support for integrating multiple backends is needed (see previous use case). + + |