From ba9d9f4ba4fb3458598d3769f38f6b2906b314d5 Mon Sep 17 00:00:00 2001 From: Georg Kunz Date: Fri, 22 Jul 2016 18:12:48 +0200 Subject: Added conclusion on Neutron network semantics to summary This conclusion is based on input from Ian Wells. Change-Id: If050df74141ee8ec47c306e690576562f4c932b7 Signed-off-by: Georg Kunz --- docs/requirements/summary.rst | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'docs/requirements') diff --git a/docs/requirements/summary.rst b/docs/requirements/summary.rst index 3736072..2761a48 100644 --- a/docs/requirements/summary.rst +++ b/docs/requirements/summary.rst @@ -29,6 +29,14 @@ Based on the gap analyses, we draw the following conclusions: networking on-demand in order to accelerate time-to-market and achieve business agility for innovations in NFV networking business. +* Neutron networks are implicitly, because of their reliance on subnets, L2 + domains. L2 network overlays are the only way to implement Neutron networks + because of their semantics. However, L2 networks are inefficient ways to + implement cloud networking, and while this is not necessarily a problem for + enterprise use cases with moderate traffic it can add expense to the + infrastructure of NFV cases where networking is heavily used and efficient use + of capacity is key. + * In NFV environment it should be possible to execute network administrator tasks without OpenStack administrator rights. -- cgit 1.2.3-korg