Add and update apex sdn and ovs scenarios to Danube 1.0

[ovsnfv.git] / docs / release / scenarios / os-nosdn-ovs-noha / scenario.description.rst

diff --git a/docs/release/scenarios/os-nosdn-ovs-noha/scenario.description.rst b/docs/release/scenarios/os-nosdn-ovs-noha/scenario.description.rst
index 3027a7e..91504f1 100644 (file)
--- a/docs/release/scenarios/os-nosdn-ovs-noha/scenario.description.rst
+++ b/docs/release/scenarios/os-nosdn-ovs-noha/scenario.description.rst
@@ -37,7 +37,7 @@ servers:
 
   * 1 Jumphost hosting the APEX installer - running the Undercloud
   * 1 Controlhost, which runs the Overcloud and Openstack services
 
   * 1 Jumphost hosting the APEX installer - running the Undercloud
   * 1 Controlhost, which runs the Overcloud and Openstack services

-  * 1 or more Computehosts
+  * 1 or more computehosts or nodes

 
 .. image:: ovs4nfv.png
 
 
 .. image:: ovs4nfv.png
 


@@ -45,7 +45,7 @@ Tenant networking leverages Open vSwitch accelerated with a fast user space data
 as DPDK.
 Open VSwitch (OVS) with the Linux kernel module data path is used for all other
 connectivity, such as connectivity to public networking "the
 as DPDK.
 Open VSwitch (OVS) with the Linux kernel module data path is used for all other
 connectivity, such as connectivity to public networking "the

-Internet" (i.e. br-ext) is performed via non-accelerated OVS.
+Internet" (i.e. br-ex) is performed via non-accelerated OVS.

 
 Features of the scenario
 ------------------------
 
 Features of the scenario
 ------------------------


@@ -66,34 +66,22 @@ with DPDK user space accelerated capability.
 Scenario Configuration
 ======================
 
 Scenario Configuration
 ======================
 

-To enable the "apex-os-nosdn-ovs-noha" scenario check the appropriate settings
-in the APEX configuration files. Those are typically found in /etc/opnfv-apex.
-
-File "deploy_settings.yaml" choose false for sdn controller::
-
-  global_params:
-    ha_enabled: false
-
-  deploy_options:
-    sdn_controller: false
-    sdn_l3: false
-    tacker: false
-    congress: false
-    sfc: false
-    vpn: false
+Simply deploy this scenario by using the os-ovs-nosdn-noha.yaml deploy
+settings file.

 
 Validated deployment environments
 =================================
 
 The "os-odl_l2-ovs-noha" scenario has been deployed and tested
 on the following sets of hardware:
 
 Validated deployment environments
 =================================
 
 The "os-odl_l2-ovs-noha" scenario has been deployed and tested
 on the following sets of hardware:

- * TBD
+ * Validated on virtual deployments only.
+ * Not yet validated on the UCS hardware.

 
 
 Limitations, Issues and Workarounds
 ===================================
 
 
 
 Limitations, Issues and Workarounds
 ===================================
 

-There are no known issues.
+* _APEX-415 br-phy dpdk interfaces are not brought up by os-net-config

 
 References
 ==========
 
 References
 ==========


@@ -102,4 +90,4 @@ References
   * OVS for NFV OPNFV project wiki: https://wiki.opnfv.org/display/ovsnfv
   * Open vSwitch: http://openvswitch.org/
   * DPDK: http://dpdk.org
   * OVS for NFV OPNFV project wiki: https://wiki.opnfv.org/display/ovsnfv
   * Open vSwitch: http://openvswitch.org/
   * DPDK: http://dpdk.org

-  * OPNFV Colorado release - more information: http://www.opnfv.org/colorado
+  * OPNFV Danube release - more information: http://www.opnfv.org/colorado