From a973062e984d73b04f71790af4ed1fa05172ec71 Mon Sep 17 00:00:00 2001 From: Georg Kunz Date: Tue, 19 Jul 2016 14:26:16 +0200 Subject: 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 --- docs/requirements/use_cases/l3vpn.rst | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) (limited to 'docs/requirements/use_cases/l3vpn.rst') diff --git a/docs/requirements/use_cases/l3vpn.rst b/docs/requirements/use_cases/l3vpn.rst index b1ee030..c2da424 100644 --- a/docs/requirements/use_cases/l3vpn.rst +++ b/docs/requirements/use_cases/l3vpn.rst @@ -14,5 +14,16 @@ L3VPN Use Cases Conclusion ---------- -[**Georg: add conclusion here, covering the identified gaps of the three use -cases above**] +Based on the gap analyses of the three specific L3VPN use cases we conclude that +there are gaps in both the functionality provided by the BGPVPN project as well +as the support for multiple backends in Neutron. + +Some of the identified gaps [L3VPN-ECMP-GAP1, L3VPN-ECMP-GAP2, L3VPN-HS-GAP3] +in the BGPVPN project are merely missing functionality which can be integrated +in the existing OpenStack networking architecture. + +Other gaps, such as the inability to explicitly disable the layer 2 semantics of +Neutron networks [L3VPN-HS-GAP1] or the tight integration of ports and networks +[L3VPN-HS-GAP2] hinder a clean integration of the needed functionality. In order +to close these gaps, fundamental changes in Neutron or alternative approaches +need to be investigated. -- cgit 1.2.3-korg