path: root/docs/release/scenarios/os-odl-sfc_fdio-noha/scenario.description.rst
diff options
Diffstat (limited to 'docs/release/scenarios/os-odl-sfc_fdio-noha/scenario.description.rst')
1 files changed, 3 insertions, 60 deletions
diff --git a/docs/release/scenarios/os-odl-sfc_fdio-noha/scenario.description.rst b/docs/release/scenarios/os-odl-sfc_fdio-noha/scenario.description.rst
index 6ef8c4ba..b9d965a3 100644
--- a/docs/release/scenarios/os-odl-sfc_fdio-noha/scenario.description.rst
+++ b/docs/release/scenarios/os-odl-sfc_fdio-noha/scenario.description.rst
@@ -6,10 +6,9 @@ Introduction
.. In this section explain the purpose of the scenario and the types of capabilities provided
-The os-odl-sfc_fdio-noha is intended to be used to install the OPNFV SFC project in a standard
-OPNFV Non-High Availability mode. The OPNFV SFC project integrates the OpenDaylight SFC
-project into the OPNFV environment. The OPNFV SFC Euphrates release uses the OpenDaylight
-Nitrogen SR1 release.
+The os-odl-sfc_fdio-ha is intended to be used to install the OPNFV SFC project in a standard
+OPNFV High Availability mode. The OPNFV SFC project integrates the OpenDaylight SFC project
+into the OPNFV environment. The OPNFV SFC Fraser release uses the OpenDaylight Oxygen SR1 release.
Scenario components and composition
@@ -17,49 +16,9 @@ Scenario components and composition
.. what each component provides and why it has been included in order
.. to communicate to the user the capabilities available in this scenario.
-This scenario installs everything needed to use the SFC OpenDaylight project in an OPNFV
-environment. Since this scenario is Non-High Availability, then only one controller and
-one compute node will be deployed. The classifier used in this scenario is implemented
-by the Netvirt OpenDaylight project.
-Following is a detailed list of what is included with this scenario:
OpenDaylight features installed
-The OpenDaylight SDN controller is installed in the controller node.
-The following are the SFC features that get installed:
-- odl-sfc-model
-- odl-sfc-provider
-- odl-sfc-provider-rest
-- odl-sfc-ovs
-- odl-sfc-openflow-renderer
-The following are the Netvirt features that get installed:
-- odl-netvirt-openstack
-- odl-sfc-genius
-- odl-neutron-service
-- odl-neutron-northbound-api
-- odl-neutron-spi
-- odl-neutron-transcriber
-- odl-ovsdb-southbound-impl-api
-- odl-ovsdb-southbound-impl-impl
-- odl-ovsdb-library
-By simply installing the odl-netvirt-sfc feature, all the dependant features
-will automatically be installed.
-The VNF Manager
-In order to create a VM for each Service Function, a VNF Manager is needed. The OPNFV
-SFC project currently uses the Tacker OpenStack project as a VNF Manager. Tacker is
-installed on the controller node and manages VNF life cycle, and coordinates VM creation
-with the OpenDaylight SFC project.
Scenario usage overview
.. Provide a brief overview on how to use the scenario and the features available to the
@@ -76,26 +35,10 @@ Limitations, Issues and Workarounds
.. faults or bugs. If the system design only provide some expected functionality then provide
.. some insight at this point.
-The *client* virtual machine needs to be located in a compute node where at least
-one of the service functions (SFs) is placed. This is due to a limitation in OpenDaylight,
-Nitrogen, which only installs the traffic classifier in the compute nodes where the SFs are.
Specific version of FD.IO
-For more information about SFC, please visit:
-For more information on the OPNFV Euphrates release, please visit: