summaryrefslogtreecommitdiffstats
path: root/docs/requirements/use_cases/l3vpn_ecmp.rst
diff options
context:
space:
mode:
authorGeorg Kunz <georg.kunz@ericsson.com>2016-05-30 20:17:26 +0200
committerGerrit Code Review <gerrit@172.30.200.206>2016-06-04 18:51:24 +0000
commitb75641db76831ea60b136f5c9c9970046c0174fb (patch)
treeaf0a680bca34d4009222202f876d56ce53185540 /docs/requirements/use_cases/l3vpn_ecmp.rst
parente0622306f573d086ab53c34532578e798fcbade4 (diff)
Intial text on analysis of L3VPN ECMP use case
Change-Id: I5ae30328ec55130d3d654b0cc358de681971592f Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
Diffstat (limited to 'docs/requirements/use_cases/l3vpn_ecmp.rst')
-rw-r--r--docs/requirements/use_cases/l3vpn_ecmp.rst39
1 files changed, 35 insertions, 4 deletions
diff --git a/docs/requirements/use_cases/l3vpn_ecmp.rst b/docs/requirements/use_cases/l3vpn_ecmp.rst
index c218179..c115a7a 100644
--- a/docs/requirements/use_cases/l3vpn_ecmp.rst
+++ b/docs/requirements/use_cases/l3vpn_ecmp.rst
@@ -32,26 +32,57 @@ can be load split from either WAN GW or another VM like G5.
Derrived Requirements
~~~~~~~~~~~~~~~~~~~~~
- - TBD
Northbound API / Workflow
+++++++++++++++++++++++++
- TBD
+
Data model objects
++++++++++++++++++
- TBD
+
Orchestration
+++++++++++++
- TBD
+
Dependencies on compute services
++++++++++++++++++++++++++++++++
- TBD
-Potential implementation
-++++++++++++++++++++++++
- - TBD
+Current implementation
+~~~~~~~~~~~~~~~~~~~~~~
+
+Support for creating and managing L3VPNs is in general available in OpenStack
+Neutron by means of the BGPVPN project [BGPVPN]_. However, the BGPVPN API does
+not yet support ECMP, but this feature is on the project roadmap. Hence, it is
+currently not possible to configure the networking use case as described above.
+
+
+
+Gaps in the current solution
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Given the use case description and the currently available implementation in
+OpenStack provided by BGPVPN project, we identify the following gaps:
+
+* [L3VPN-ECMP-GAP1] ECMP is current not yet supported by the BGPVPN API. The
+ Development of this feature is on the roadmap of the project, however.
+ TODO: add timeline and planned API
+
+* [L3VPN-ECMP-GAP2] It is not possible to assign the same IP to multiple Neutron
+ ports within the same Neutron subnet. This is due to the fundamental
+ requirement of avoiding IP collisions within the L2 domain which is a Neutron
+ network. A potential workaround is to create two subnets with the same IP ranges
+ and associate both with the same BGP VPN.
+
+
+
+Conclusion
+~~~~~~~~~~
+
+TBD