diff options
authorFrank Brockners <>2016-08-12 04:04:39 -0700
committerFrank Brockners <>2016-08-12 04:04:39 -0700
commit69388bf1f5ac51852443ed01ee64a22aea072c7e (patch)
parent76aa192240e7a959ee6e9d422b2cba02fd83f517 (diff)
Editorial updates to os-odl_l3-fdio-noha docs
Evolved section headers to match OPNFV template. Added motivation for the scenario. Added references section. Change-Id: Id174e910d24fcc465577f7e7d796b87d94be5bdd Signed-off-by: Frank Brockners <>
1 files changed, 51 insertions, 9 deletions
diff --git a/docs/scenarios/os-odl_l3-fdio-noha/scenario.description.rst b/docs/scenarios/os-odl_l3-fdio-noha/scenario.description.rst
index cc95fd9..bf32eb6 100755
--- a/docs/scenarios/os-odl_l3-fdio-noha/scenario.description.rst
+++ b/docs/scenarios/os-odl_l3-fdio-noha/scenario.description.rst
@@ -13,14 +13,44 @@ FastDataStacks OPNFV project. The main components of the
- APEX (TripleO) installer (please also see APEX installer documentation)
- Openstack (in non-HA configuration)
- - OpenDaylight controller controlling layer 2 and layer 3 networking
+ - OpenDaylight controller (non-clustered)
+ controlling layer 2 and layer 3 networking
- virtual forwarder for tenant networking
-Scenario Overview
+NFV and virtualized high performance applications, such as video processing,
+require a "fast data stack" solution that provides both carrier grade
+forwarding performance, scalability and open extensibility, along with
+functionality for realizing application policies and controlling a complex
+network topology.
+A solution stack is only as good as its foundation. Key foundational assets for
+NFV infrastructure are
+ * The virtual forwarder: The virtual forwarder needs to be a feature rich,
+ high performance, highly scale virtual switch-router. It needs to leverage
+ hardware accelerators when available and run in user space.
+ In addition, it should be modular and easily extensible.
+ * Forwarder diversity: A solution stack should support a variety of
+ forwarders, hardware forwarders (physical switches and routers)
+ as well as software forwarders. This way virtual and physical
+ forwarding domains can be seamlessly glued together.
+ * Policy driven connectivity: Connectivity should respect and
+ reflect different business
+In order to meet the desired qualities of an NFV infrastructure, the
+following components were chosen for the "Openstack - OpenDaylight
+ -" scenario:
+ * Vector Packet Processor (VPP) - a highly scalable,
+ high performance, extensible virtual forwarder
+ * OpenDaylight Controller - an extensible controller platform which
+ offers the ability to separate business logic from networking
+ constructs, supports a diverse set of network devices
+ (virtual and physical) via the "group based policy (GBP)"
+ component, and can be clustered to achieve a highly available
+ deployment.
The "Openstack - OpenDaylight -" scenario provides the capability to
realize a set of use-cases relevant to the deployment of NFV nodes instantiated
@@ -75,8 +105,8 @@ Main features of the "apex-os-odl_l3-fdio-noha" scenario:
floating IP addresses (i.e. NAT) are implemented by the forwarder
* Manual and automatic (via DHCP) addressing on tenant networks
-Software components of the scenario
+Scenario components and composition
The apex-os-odl_l3-fdio-noha scenario combines components from three key open
source projects: OpenStack, OpenDaylight, and Fast Data ( The key
@@ -217,5 +247,17 @@ File "deploy_settings.yaml": Choose Opendaylight as controller with version
vpn: false
vpp: true
-Notes and known issues
+Limitations, Issues and Workarounds
+There are no known issues.
+ * FastDataStacks OPNFV project wiki:
+ * Fast Data (
+ * Vector Packet Processor (VPP):
+ * OpenDaylight Controller:
+ * OPNFV Colorado release - more information: