Update documentation structure.

This patch is used to update documentation structure.

Change-Id: I50d4ef4256ccfc57a0434123e7532a50000582cf
Co-Authored by:Srinivas <srinivas.atmakuri@tcs.com>
Co-Authored by:RajithaY<rajithax.yerrumsetty@intel.com>
Co-Authored by:shravani paladugula <shravanix.paladugula@intel.com>
Co-Authored by:Navya Bathula <navyax.bathula@intel.com>
Signed-off-by: Gundarapu Kalyan Reddy <reddyx.gundarapu@intel.com>
(cherry picked from commit f1f3cc27f23bdde81c37d8142d4288d811bd5e45)

14 files changed, 1785 insertions, 0 deletions

diff --git a/docs/release/scenarios/.kvmfornfv.scenarios.description.rst.swp b/docs/release/scenarios/.kvmfornfv.scenarios.description.rst.swp
new file mode 100644
index 000000000..b6ef17624
--- /dev/null
+++ b/docs/release/scenarios/.kvmfornfv.scenarios.description.rst.swp
diff --git a/docs/release/scenarios/abstract.rst b/docs/release/scenarios/abstract.rst
new file mode 100644
index 000000000..dcdd62fa9
--- /dev/null
+++ b/docs/release/scenarios/abstract.rst
@@ -0,0 +1,42 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+*****************
+Scenario Abstract
+*****************
+This chapter includes detailed explanation of various sceanrios files deployed as part
+of kvm4nfv D-Release.
+
+Release Features
+----------------
+
++------------------------------------------+------------------+-----------------+
+| **Scenario Name**                        | **Colorado**     | **Danube**      |
+|                                          |                  |                 |
++==========================================+==================+=================+
+| - os-nosdn-kvm-ha                        |     ``Y``        |     ``Y``       |
++------------------------------------------+------------------+-----------------+
+| - os-nosdn-kvm_nfv_ovs_dpdk-noha         |                  |     ``Y``       |
++------------------------------------------+------------------+-----------------+
+| - os-nosdn-kvm_nfv_ovs_dpdk-ha           |                  |     ``Y``       |
++------------------------------------------+------------------+-----------------+
+| - os-nosdn-kvm_nfv_ovs_dpdk_bar-noha     |                  |     ``Y``       |
++------------------------------------------+------------------+-----------------+
+| - os-nosdn-kvm_nfv_ovs_dpdk_bar-ha       |                  |     ``Y``       |
++------------------------------------------+------------------+-----------------+
+
+D- Release Scenario's overview
+-------------------------------
+
++------------------------------------------+-----------------------+---------------------+------------------+----------+----------+
+| **Scenario Name**                        | **No of Controllers** | **No of Computes**  | **Plugin Names** | **DPDK** | **OVS**  |
+|                                          |                       |                     |                  |          |          |
++==========================================+=======================+=====================+==================+==========+==========+
+| - ``os-nosdn-kvm_nfv_ovs_dpdk-noha``     |     1                 |     3               |    KVM           |    Y     |    Y     |
++------------------------------------------+-----------------------+---------------------+------------------+----------+----------+
+| - ``os-nosdn-kvm_nfv_ovs_dpdk-ha``       |     3                 |     2               |    KVM           |    Y     |    Y     |
++------------------------------------------+-----------------------+---------------------+------------------+----------+----------+
+| - ``os-nosdn-kvm_nfv_ovs_dpdk_bar-noha`` |     1                 |     3               |    KVM & BAR     |    Y     |    Y     |
++------------------------------------------+-----------------------+---------------------+------------------+----------+----------+
+| - ``os-nosdn-kvm_nfv_ovs_dpdk_bar-ha``   |     3                 |     2               |    KVM & BAR     |    Y     |    Y     |
++------------------------------------------+-----------------------+---------------------+------------------+----------+----------+
diff --git a/docs/release/scenarios/index.rst b/docs/release/scenarios/index.rst
new file mode 100644
index 000000000..f1f93c31a
--- /dev/null
+++ b/docs/release/scenarios/index.rst
@@ -0,0 +1,60 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _kvmfornfv-scenarios:
+
+*********************************
+Scenario Overview and Description
+*********************************
+
+.. toctree::
+   :caption: Scenario Overview and Description
+   :numbered:
+   :maxdepth: 4
+
+   ./abstract.rst
+   ./kvmfornfv.scenarios.description.rst
+
+*******************************************************
+os-nosdn-kvm_nfv_ovs_dpdk-noha Overview and Description
+*******************************************************
+
+.. toctree::
+   :caption: os-nosdn-kvm_nfv_ovs_dpdk-noha
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst
+
+*****************************************************
+os-nosdn-kvm_nfv_ovs_dpdk-ha Overview and Description
+*****************************************************
+
+.. toctree::
+   :caption: os-nosdn-kvm_nfv_ovs_dpdk-ha
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst
+
+***********************************************************
+os-nosdn-kvm_nfv_ovs_dpdk_bar-noha Overview and Description
+***********************************************************
+
+.. toctree::
+   :caption: os-nosdn-kvm_nfv_ovs_dpdk_bar-noha
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst
+
+*********************************************************
+os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Overview and Description
+*********************************************************
+
+.. toctree::
+   :caption: os-nosdn-kvm_nfv_ovs_dpdk_bar-ha
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst
diff --git a/docs/release/scenarios/kvmfornfv.scenarios.description.rst b/docs/release/scenarios/kvmfornfv.scenarios.description.rst
new file mode 100644
index 000000000..5a5328666
--- /dev/null
+++ b/docs/release/scenarios/kvmfornfv.scenarios.description.rst
@@ -0,0 +1,493 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _scenario-guide:
+
+============================
+KVM4NFV Scenario-Description
+============================
+
+Abstract
+--------
+
+This document describes the procedure to deploy/test KVM4NFV scenarios in a nested virtualization
+environment. This has been verified with os-nosdn-kvm-ha, os-nosdn-kvm-noha,os-nosdn-kvm_ovs_dpdk-ha,
+os-nosdn-kvm_ovs_dpdk-noha and os-nosdn-kvm_ovs_dpdk_bar-ha test scenarios.
+
+Version Features
+----------------
+
++-----------------------------+---------------------------------------------+
+|                             |                                             |
+|      **Release**            |               **Features**                  |
+|                             |                                             |
++=============================+=============================================+
+|                             | - Scenario Testing feature was not part of  |
+|       Colorado              |   the Colorado release of KVM4NFV           |
+|                             |                                             |
++-----------------------------+---------------------------------------------+
+|                             | - High Availability/No-High Availability    |
+|                             |   deployment configuration of KVM4NFV       |
+|                             |   software suite                            |
+|        Danube               | - Multi-node setup with 3 controller and    |
+|                             |   2 compute nodes are deployed for HA       |
+|                             | - Multi-node setup with 1 controller and    |
+|                             |   3 compute nodes are deployed for NO-HA    |
+|                             | - Scenarios os-nosdn-kvm_ovs_dpdk-ha,       |
+|                             |   os-nosdn-kvm_ovs_dpdk_bar-ha,             |
+|                             |   os-nosdn-kvm_ovs_dpdk-noha,               |
+|                             |   os-nosdn-kvm_ovs_dpdk_bar-noha            |
+|                             |   are supported                             |
++-----------------------------+---------------------------------------------+
+
+
+Introduction
+------------
+The purpose of os-nosdn-kvm_ovs_dpdk-ha,os-nosdn-kvm_ovs_dpdk_bar-ha and
+os-nosdn-kvm_ovs_dpdk-noha,os-nosdn-kvm_ovs_dpdk_bar-noha scenarios testing is to
+test the High Availability/No-High Availability deployment and configuration of
+OPNFV software suite with OpenStack and without SDN software.
+
+This OPNFV software suite includes OPNFV KVM4NFV latest software packages
+for Linux Kernel and QEMU patches for achieving low latency and also OPNFV Barometer for traffic,
+performance and platform monitoring.
+
+High Availability feature is achieved by deploying OpenStack
+multi-node setup with 1 Fuel-Master,3 controllers and 2 computes nodes.
+
+No-High Availability feature is achieved by deploying OpenStack
+multi-node setup with 1 Fuel-Master,1 controllers and 3 computes nodes.
+
+KVM4NFV packages will be installed on compute nodes as part of deployment.
+The scenario testcase deploys a multi-node setup by using OPNFV Fuel deployer.
+
+System pre-requisites
+---------------------
+
+- RAM - Minimum 16GB
+- HARD DISK - Minimum 500GB
+- Linux OS installed and running
+- Nested Virtualization enabled, which can be checked by,
+
+.. code:: bash
+
+        $ cat /sys/module/kvm_intel/parameters/nested
+          Y
+
+        $ cat /proc/cpuinfo | grep vmx
+
+*Note:*
+If Nested virtualization is disabled, enable it by,
+
+.. code:: bash
+
+     For Ubuntu:
+     $ modeprobe kvm_intel
+     $ echo Y > /sys/module/kvm_intel/parameters/nested
+     $ sudo reboot
+
+     For RHEL:
+     $ cat << EOF > /etc/modprobe.d/kvm_intel.conf
+       options kvm-intel nested=1
+       options kvm-intel enable_shadow_vmcs=1
+       options kvm-intel enable_apicv=1
+       options kvm-intel ept=1
+       EOF
+     $ cat << EOF > /etc/sysctl.d/98-rp-filter.conf
+       net.ipv4.conf.default.rp_filter = 0
+       net.ipv4.conf.all.rp_filter = 0
+       EOF
+     $ sudo reboot
+
+Environment Setup
+-----------------
+
+**Configuring Proxy**
+~~~~~~~~~~~~~~~~~~~~~
+
+For **Ubuntu**.,
+Create an apt.conf file in /etc/apt if it doesn't exist. Used to set proxy for apt-get if working behind a proxy server.
+
+.. code:: bash
+
+   Acquire::http::proxy "http://<username>:<password>@<proxy>:<port>/";
+   Acquire::https::proxy "https://<username>:<password>@<proxy>:<port>/";
+   Acquire::ftp::proxy "ftp://<username>:<password>@<proxy>:<port>/";
+   Acquire::socks::proxy "socks://<username>:<password>@<proxy>:<port>/";
+
+For **CentOS**.,
+Edit /etc/yum.conf to work behind a proxy server by adding the below line.
+
+.. code:: bash
+
+   $ echo "proxy=http://<username>:<password>@<proxy>:<port>/" >> /etc/yum.conf
+
+**Network Time Protocol (NTP) setup and configuration**
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Install ntp by:
+
+.. code:: bash
+
+    $ sudo apt-get update
+    $ sudo apt-get install -y ntp
+
+Insert the following two lines after  “server ntp.ubuntu.com” line and before “ # Access control configuration; see `link`_ for” line in /etc/ntp.conf file:
+
+.. _link: /usr/share/doc/ntp-doc/html/accopt.html
+
+.. code:: bash
+
+   server 127.127.1.0
+   fudge 127.127.1.0 stratum 10
+
+Restart the ntp server to apply the changes
+
+.. code:: bash
+
+    $ sudo service ntp restart
+
+Scenario Testing
+----------------
+
+There are three ways of performing scenario testing,
+    - 1 Fuel
+    - 2 OPNFV-Playground
+    - 3 Jenkins Project
+
+Fuel
+~~~~
+
+**1 Clone the fuel repo :**
+
+.. code:: bash
+
+   $ git clone https://gerrit.opnfv.org/gerrit/fuel.git
+
+**2 Checkout to the specific version of the branch to deploy by:**
+
+The default branch is master, to use a stable release-version use the below.,
+
+.. code:: bash
+    To check the current branch
+    $ git branch
+
+    To check out a specific branch
+    $ git checkout stable/Colorado
+
+**3  Building the Fuel iso :**
+
+.. code:: bash
+
+              $ cd ~/fuel/ci/
+              $ ./build.sh -h
+
+Provide the necessary options that are required to build an iso.
+Create a ``customized iso`` as per the deployment needs.
+
+.. code:: bash
+
+              $ cd ~/fuel/build/
+              $ make
+
+(OR) Other way is to download the latest stable fuel iso from `here`_.
+
+.. _here: http://artifacts.opnfv.org/fuel.html
+
+.. code:: bash
+
+   http://artifacts.opnfv.org/fuel.html
+
+**4 Creating a new deployment scenario**
+
+``(i). Naming the scenario file``
+
+Include the new deployment scenario yaml file in ~/fuel/deploy/scenario/. The file name should adhere to the following format:
+
+.. code:: bash
+
+    <ha | no-ha>_<SDN Controller>_<feature-1>_..._<feature-n>.yaml
+
+``(ii). Meta data``
+
+The deployment configuration file should contain configuration metadata as stated below:
+
+.. code:: bash
+
+              deployment-scenario-metadata:
+                      title:
+                      version:
+                      created:
+
+``(iii). “stack-extentions” Module``
+
+To include fuel plugins in the deployment configuration file, use the “stack-extentions” key:
+
+.. code:: bash
+
+             Example:
+                     stack-extensions:
+                        - module: fuel-plugin-collectd-ceilometer
+                          module-config-name: fuel-barometer
+                          module-config-version: 1.0.0
+                          module-config-override:
+                          #module-config overrides
+
+**Note:**
+The “module-config-name” and “module-config-version” should be same as the name of plugin configuration file.
+
+The “module-config-override” is used to configure the plugin by overrriding the corresponding keys in
+the plugin config yaml file present in ~/fuel/deploy/config/plugins/.
+
+``(iv).  “dea-override-config” Module``
+
+To configure the HA/No-HA mode, network segmentation types and role to node assignments, use the “dea-override-config” key.
+
+.. code:: bash
+
+        Example:
+        dea-override-config:
+               environment:
+                   mode: ha
+                   net_segment_type: tun
+               nodes:
+               - id: 1
+                  interfaces: interfaces_1
+                  role: mongo,controller,opendaylight
+               - id: 2
+                 interfaces: interfaces_1
+                 role: mongo,controller
+               - id: 3
+                  interfaces: interfaces_1
+                  role: mongo,controller
+               - id: 4
+                  interfaces: interfaces_1
+                  role: ceph-osd,compute
+               - id: 5
+                  interfaces: interfaces_1
+                  role: ceph-osd,compute
+        settings:
+            editable:
+                storage:
+                     ephemeral_ceph:
+                              description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes).
+                              label: Ceph RBD for ephemeral volumes (Nova)
+                              type: checkbox
+                              value: true
+                              weight: 75
+                     images_ceph:
+                              description: Configures Glance to use the Ceph RBD backend to store images.If enabled, this option will prevent Swift from installing.
+                              label: Ceph RBD for images (Glance)
+                              restrictions:
+                              - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
+                              type: checkbox
+                              value: true
+                              weight: 30
+
+Under the “dea-override-config” should provide atleast {environment:{mode:'value},{net_segment_type:'value'}
+and {nodes:1,2,...} and can also enable additional stack features such ceph,heat which overrides
+corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
+
+``(v). “dha-override-config”  Module``
+
+In order to configure the pod dha definition, use the “dha-override-config” key.
+This is an optional key present at the ending of the scenario file.
+
+``(vi). Mapping to short scenario name``
+
+The scenario.yaml file is used to map the short names of scenario's to the one or more deployment scenario configuration yaml files.
+The short scenario names should follow the scheme below:
+
+.. code:: bash
+
+               [os]-[controller]-[feature]-[mode]-[option]
+
+        [os]: mandatory
+        possible value: os
+
+Please note that this field is needed in order to select parent jobs to list and do blocking relations between them.
+
+.. code:: bash
+
+
+    [controller]: mandatory
+    example values: nosdn, ocl, odl, onos
+
+    [mode]: mandatory
+    possible values: ha, noha
+
+    [option]: optional
+
+Used for the scenarios those do not fit into naming scheme.
+Optional field in the short scenario name should not be included if there is no optional scenario.
+
+.. code:: bash
+
+            Example:
+                1. os-nosdn-kvm-noha
+                2. os-nosdn-kvm_ovs_dpdk_bar-ha
+
+
+Example of how short scenario names are mapped to configuration yaml files:
+
+.. code:: bash
+
+                  os-nosdn-kvm_ovs_dpdk-ha:
+                      configfile: ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
+
+Note:
+
+- ( - )  used for separator of fields. [os-nosdn-kvm_ovs_dpdk-ha]
+
+- ( _ ) used to separate the values belong to the same field. [os-nosdn-kvm_ovs_bar-ha].
+
+**5 Deploying the scenario**
+
+Command to deploy the os-nosdn-kvm_ovs_dpdk-ha scenario:
+
+.. code:: bash
+
+        $ cd ~/fuel/ci/
+        $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso
+
+where,
+    ``-b`` is used to specify the configuration directory
+
+    ``-f`` is used to re-deploy on the existing deployment
+
+    ``-i`` is used to specify the image downloaded from artifacts.
+
+    ``-l`` is used to specify the lab name
+
+    ``-p`` is used to specify POD name
+
+    ``-s`` is used to specify the scenario file
+
+**Note:**
+
+.. code:: bash
+
+           Check $ sudo ./deploy.sh -h for further information.
+
+
+OPNFV-Playground
+~~~~~~~~~~~~~~~~
+
+Install OPNFV-playground (the tool chain to deploy/test CI scenarios in fuel@opnfv, ):
+
+.. code:: bash
+
+    $ cd ~
+    $ git clone https://github.com/jonasbjurel/OPNFV-Playground.git
+    $ cd OPNFV-Playground/ci_fuel_opnfv/
+
+- Follow the README.rst in this ~/OPNFV-Playground/ci_fuel_opnfv sub-holder to complete all necessary installation and setup.
+- Section “RUNNING THE PIPELINE” in README.rst explain how to use this ci_pipeline to deploy/test CI test scenarios, you can also use
+
+.. code:: bash
+
+    ./ci_pipeline.sh --help  ##to learn more options.
+
+
+
+``1 Downgrade paramiko package from 2.x.x to 1.10.0``
+
+The paramiko package 2.x.x doesn’t work with OPNFV-playground  tool chain now, Jira ticket FUEL - 188 has been raised for the same.
+
+Check paramiko package version by following below steps in your system:
+
+.. code:: bash
+
+   $ python
+   Python 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for more information.
+
+   >>> import paramiko
+   >>> print paramiko.__version__
+   >>> exit()
+
+You will get the current paramiko package version, if it is 2.x.x, uninstall this version by
+
+.. code:: bash
+
+    $  sudo pip uninstall paramiko
+
+Ubuntu 14.04 LTS has python-paramiko package (1.10.0), install it by
+
+.. code:: bash
+
+    $ sudo apt-get install python-paramiko
+
+
+Verify it by following:
+
+.. code:: bash
+
+   $ python
+   >>> import paramiko
+   >>> print paramiko.__version__
+   >>> exit()
+
+
+``2  Clone the fuel@opnfv``
+
+Check out the specific version of specific branch of fuel@opnfv
+
+.. code:: bash
+
+   $ cd ~
+   $ git clone https://gerrit.opnfv.org/gerrit/fuel.git
+   $ cd fuel
+   By default it will be master branch, in-order to deploy on the Colorado/Danube branch, do:
+   $ git checkout stable/Danube
+
+
+``3 Creating the scenario``
+
+Implement the scenario file as described in 3.1.4
+
+``4 Deploying the scenario``
+
+You can use the following command to deploy/test os-nosdn kvm_ovs_dpdk-(no)ha and os-nosdn-kvm_ovs_dpdk_bar-(no)ha scenario
+
+.. code:: bash
+
+   $ cd ~/OPNFV-Playground/ci_fuel_opnfv/
+
+For os-nosdn-kvm_ovs_dpdk-ha :
+
+.. code:: bash
+
+   $ ./ci_pipeline.sh -r ~/fuel -i /root/fuel.iso -B -n intel-sc -s os-nosdn-kvm_ovs_dpdk-ha
+
+For os-nosdn-kvm_ovs_dpdk_bar-ha:
+
+.. code:: bash
+
+   $ ./ci_pipeline.sh -r ~/fuel -i /root/fuel.iso -B -n intel-sc -s os-nosdn-kvm_ovs_dpdk_bar-ha
+
+The “ci_pipeline.sh” first clones the local fuel repo, then deploys the
+os-nosdn-kvm_ovs_dpdk-ha/os-nosdn-kvm_ovs_dpdk_bar-ha scenario from the given ISO, and run Functest
+and Yarstick test.  The log of the deployment/test (ci.log)  can be found in
+~/OPNFV-Playground/ci_fuel_opnfv/artifact/master/YYYY-MM-DD—HH.mm, where YYYY-MM-DD—HH.mm is the
+date/time you start the “ci_pipeline.sh”.
+
+Note:
+
+.. code:: bash
+
+   Check $ ./ci_pipeline.sh -h for further information.
+
+
+Jenkins Project
+~~~~~~~~~~~~~~~
+
+os-nosdn-kvm_ovs_dpdk-(no)ha and os-nosdn-kvm_ovs_dpdk_bar-(no)ha scenario can be executed from the jenkins project :
+
+    ``HA scenarios:``
+        1.  "fuel-os-nosdn-kvm_ovs_dpdk-ha-baremetal-daily-master" (os-nosdn-kvm_ovs_dpdk-ha)
+        2.  "fuel-os-nosdn-kvm_ovs_dpdk_bar-ha-baremetal-daily-master" (os-nosdn-kvm_ovs_dpdk_bar-ha)
+
+    ``NOHA scenarios:``
+       1.  "fuel-os-nosdn-kvm_ovs_dpdk-noha-virtual-daily-master" (os-nosdn-kvm_ovs_dpdk-noha)
+       2.  "fuel-os-nosdn-kvm_ovs_dpdk_bar-noha-virtual-daily-master" (os-nosdn-kvm_ovs_dpdk_bar-noha)
diff --git a/docs/release/scenarios/os-nosdn-kvm-ha/index.rst b/docs/release/scenarios/os-nosdn-kvm-ha/index.rst
new file mode 100755
index 000000000..ab82d96b8
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm-ha/index.rst
@@ -0,0 +1,14 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _kvmfornfv-os-nosdn-kvm-ha:
+
+****************************************
+os-nosdn-kvm-ha Overview and Description
+****************************************
+
+.. toctree::
+   :numbered:
+   :maxdepth: 3
+
+   os-nosdn-kvm-ha.description.rst
diff --git a/docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst b/docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst
new file mode 100644
index 000000000..f64f26ffc
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst
@@ -0,0 +1,133 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+
+.. http://creativecommons.org/licenses/by/4.0
+
+============================
+os-nosdn-kvm-ha Description
+============================
+
+Introduction
+-------------
+
+.. In this section explain the purpose of the scenario and the
+   types of capabilities provided
+
+The purpose of os-nosdn-kvm-ha scenario testing is to test the
+High Availability deployment and configuration of OPNFV software suite
+with OpenStack and without SDN software. This OPNFV software suite
+includes OPNFV KVM4NFV latest software packages for Linux Kernel and
+QEMU patches for achieving low latency. High Availability feature is achieved
+by deploying OpenStack multi-node setup with 3 controllers and 2 computes nodes
+
+KVM4NFV packages will be installed on compute nodes as part of deployment.
+This scenario testcase deployment is happening on multi-node by using
+OPNFV Fuel deployer.
+
+Scenario Components and Composition
+-----------------------------------
+.. In this section describe the unique components that make up the scenario,
+.. 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 deploys the High Availability OPNFV Cloud based on the
+configurations provided in ha_nfv-kvm_heat_ceilometer_scenario.yaml.
+This yaml file contains following configurations and is passed as an
+argument to deploy.py script
+
+* ``scenario.yaml:`` This configuration file defines translation between a
+  short deployment scenario name(os-nosdn-kvm-ha) and an actual deployment
+  scenario configuration file(ha_nfv-kvm_heat_ceilometer_scenario.yaml)
+
+* ``deployment-scenario-metadata:`` Contains the configuration metadata like
+  title,version,created,comment.
+
+* ``stack-extensions:`` Stack extentions are opnfv added value features in form
+  of a fuel-plugin.Plugins listed in stack extensions are enabled and
+  configured.
+
+* ``dea-override-config:`` Used to configure the HA mode,network segmentation
+  types and role to node assignments.These configurations overrides
+  corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
+  These keys are used to deploy multiple nodes(3 controllers,2 computes)
+  as mention below.
+
+  * **Node 1**: This node has MongoDB and Controller roles. The controller
+    node runs the Identity service, Image Service, management portions of
+    Compute and Networking, Networking plug-in and the dashboard. The
+    Telemetry service which was designed to support billing systems for
+    OpenStack cloud resources uses a NoSQL database to store information.
+    The database typically runs on the controller node.
+
+  * **Node 2**: This node has Controller and Ceph-osd roles. Ceph is a
+    massively scalable, open source, distributed storage system. It is
+    comprised of an object store, block store and a POSIX-compliant distributed
+    file system. Enabling Ceph,  configures Nova to store ephemeral volumes in
+    RBD, configures Glance to use the Ceph RBD backend to store images,
+    configures Cinder to store volumes in Ceph RBD images and configures the
+    default number of object replicas in Ceph.
+
+  * **Node 3**: This node has Controller role in order to achieve high
+    availability.
+
+  * **Node 4**: This node has Compute role. The compute node runs the
+    hypervisor portion of Compute that operates tenant virtual machines
+    or instances. By default, Compute uses KVM as the hypervisor.
+
+  * **Node 5**: This node has compute role.
+
+* ``dha-override-config:`` Provides information about the VM definition and
+  Network config for virtual deployment.These configurations overrides
+  the pod dha definition and points to the controller,compute and
+  fuel definition files.
+
+* os-nosdn-kvm-ha scenario is successful when all the 5 Nodes are accessible,
+  up and running
+
+Scenario Usage Overview
+-----------------------
+.. Provide a brief overview on how to use the scenario and the features available to the
+.. user.  This should be an "introduction" to the userguide document, and explicitly link to it,
+.. where the specifics of the features are covered including examples and API's
+
+* The high availability feature can be acheived by executing deploy.py with
+  ha_nfv-kvm_heat_ceilometer_scenario.yaml as an argument.
+* Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
+  Environment:
+
+  -Example:
+
+.. code:: bash
+
+  sudo python deploy.py -iso ~/ISO/opnfv.iso -dea ~/CONF/hardware/dea.yaml -dha ~/CONF/hardware/dha.yaml -s /mnt/images -b pxebr -log ~/Deployment-888.log.tar.gz
+
+* Install Fuel Master and deploy OPNFV Cloud from scratch on Virtual
+  Environment:
+
+  -Example:
+
+.. code:: bash
+
+  sudo python deploy.py -iso ~/ISO/opnfv.iso -dea ~/CONF/virtual/dea.yaml -dha ~/CONF/virtual/dha.yaml -s /mnt/images -log ~/Deployment-888.log.tar.gz
+
+* os-nosdn-kvm-ha scenario can be executed from the jenkins project
+  "fuel-os-nosdn-kvm-ha-baremetal-daily-master"
+* This scenario provides the High Availability feature by deploying
+  3 controller,2 compute nodes and checking if all the 5 nodes
+  are accessible(IP,up & running).
+* Test Scenario is passed if deployment is successful and all 5 nodes have
+  accessibility (IP , up & running).
+* Observed that scenario is not running any testcase on top of deployment.
+
+Known Limitations, Issues and Workarounds
+-----------------------------------------
+.. Explain any known limitations here.
+
+* Test scenario os-nosdn-kvm-ha result is not stable. After node reboot
+  triggered by kvm plugin, sometimes puppet agent (mcollective) is not
+  responding with in the given time.
+
+References
+----------
+
+For more information on the OPNFV Danube release, please visit
+http://www.opnfv.org/danube
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/index.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/index.rst
new file mode 100755
index 000000000..ddb6071c8
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/index.rst
@@ -0,0 +1,14 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk-ha:
+
+*****************************************************
+os-nosdn-kvm_nfv_ovs_dpdk-ha Overview and Description
+*****************************************************
+
+.. toctree::
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst
new file mode 100644
index 000000000..a96130cad
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst
@@ -0,0 +1,247 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+
+.. http://creativecommons.org/licenses/by/4.0
+
+=========================================
+os-nosdn-kvm_nfv_ovs_dpdk-ha Description
+=========================================
+
+Introduction
+------------
+
+.. In this section explain the purpose of the scenario and the
+   types of capabilities provided
+
+The purpose of os-nosdn-kvm_ovs_dpdk-ha scenario testing is to test the
+High Availability deployment and configuration of OPNFV software suite
+with OpenStack and without SDN software. This OPNFV software suite
+includes OPNFV KVM4NFV latest software packages for Linux Kernel and
+QEMU patches for achieving low latency. High Availability feature is achieved
+by deploying OpenStack multi-node setup with 3 controllers and 2 computes nodes.
+
+KVM4NFV packages will be installed on compute nodes as part of deployment.
+This scenario testcase deployment is happening on multi-node by using OPNFV Fuel deployer.
+
+Scenario Components and Composition
+-----------------------------------
+.. In this section describe the unique components that make up the scenario,
+.. 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 deploys the High Availability OPNFV Cloud based on the
+configurations provided in ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml.
+This yaml file contains following configurations and is passed as an
+argument to deploy.py script
+
+* ``scenario.yaml:`` This configuration file defines translation between a
+  short deployment scenario name(os-nosdn-kvm_ovs_dpdk-ha) and an actual deployment
+  scenario configuration file(ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml)
+
+* ``deployment-scenario-metadata:`` Contains the configuration metadata like
+  title,version,created,comment.
+
+.. code:: bash
+
+   deployment-scenario-metadata:
+      title: NFV KVM and OVS-DPDK HA deployment
+      version: 0.0.1
+      created: Dec 20 2016
+      comment: NFV KVM and OVS-DPDK
+
+* ``stack-extensions:`` Stack extentions are opnfv added value features in form
+  of a fuel-plugin.Plugins listed in stack extensions are enabled and
+  configured. os-nosdn-kvm_ovs_dpdk-ha scenario currently uses KVM-1.0.0 plugin.
+
+.. code:: bash
+
+   stack-extensions:
+      - module: fuel-plugin-kvm
+        module-config-name: fuel-nfvkvm
+        module-config-version: 1.0.0
+        module-config-override:
+          # Module config overrides
+
+* ``dea-override-config:`` Used to configure the HA mode,network segmentation
+  types and role to node assignments.These configurations overrides
+  corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
+  These keys are used to deploy multiple nodes(``3 controllers,2 computes``)
+  as mention below.
+
+  * **Node 1**:
+     - This node has MongoDB and Controller roles
+     - The controller node runs the Identity service, Image Service, management portions of
+       Compute and Networking, Networking plug-in and the dashboard
+     - Uses VLAN as an interface
+
+  * **Node 2**:
+     - This node has Ceph-osd and Controller roles
+     - The controller node runs the Identity service, Image Service, management portions of
+       Compute and Networking, Networking plug-in and the dashboard
+     - Ceph is a massively scalable, open source, distributed storage system
+     - Uses VLAN as an interface
+
+  * **Node 3**:
+     - This node has Controller role in order to achieve high availability.
+     - Uses VLAN as an interface
+
+  * **Node 4**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  * **Node 5**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  The below is the ``dea-override-config`` of the ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml file.
+
+.. code:: bash
+
+   dea-override-config:
+     fuel:
+       FEATURE_GROUPS:
+       - experimental
+     nodes:
+     - id: 1
+       interfaces: interfaces_1
+       role: controller
+     - id: 2
+       interfaces: interfaces_1
+       role: mongo,controller
+     - id: 3
+       interfaces: interfaces_1
+       role: ceph-osd,controller
+     - id: 4
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+     - id: 5
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+
+     attributes_1:
+       hugepages:
+         dpdk:
+           value: 1024
+         nova:
+           value:
+             '2048': 1024
+
+     settings:
+       editable:
+         storage:
+           ephemeral_ceph:
+             description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes).
+             label: Ceph RBD for ephemeral volumes (Nova)
+             type: checkbox
+             value: true
+             weight: 75
+           images_ceph:
+             description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing.
+             label: Ceph RBD for images (Glance)
+             restrictions:
+             - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
+             type: checkbox
+             value: true
+             weight: 30
+
+* ``dha-override-config:`` Provides information about the VM definition and
+  Network config for virtual deployment.These configurations overrides
+  the pod dha definition and points to the controller,compute and
+  fuel definition files.
+
+  The below is the ``dha-override-config`` of the ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml file.
+
+.. code:: bash
+
+   dha-override-config:
+     nodes:
+     - id: 1
+       libvirtName: controller1
+       libvirtTemplate: templates/virtual_environment/vms/controller.xml
+     - id: 2
+       libvirtName: controller2
+       libvirtTemplate: templates/virtual_environment/vms/controller.xml
+     - id: 3
+       libvirtName: controller3
+       libvirtTemplate: templates/virtual_environment/vms/controller.xml
+     - id: 4
+       libvirtName: compute1
+       libvirtTemplate: templates/virtual_environment/vms/compute.xml
+     - id: 5
+       libvirtName: compute2
+       libvirtTemplate: templates/virtual_environment/vms/compute.xml
+     - id: 6
+       libvirtName: fuel-master
+       libvirtTemplate: templates/virtual_environment/vms/fuel.xml
+       isFuel: yes
+       username: root
+       password: r00tme
+
+
+* os-nosdn-kvm_ovs_dpdk-ha scenario is successful when all the 5 Nodes are accessible,
+  up and running.
+
+**Note:**
+
+* In os-nosdn-kvm_ovs_dpdk-ha scenario, OVS is installed on the compute nodes with DPDK configured
+
+* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
+
+* Hugepages are only configured for compute nodes
+
+* This results in faster communication and data transfer among the compute nodes
+
+Scenario Usage Overview
+-----------------------
+.. Provide a brief overview on how to use the scenario and the features available to the
+.. user.  This should be an "introduction" to the userguide document, and explicitly link to it,
+.. where the specifics of the features are covered including examples and API's
+
+* The high availability feature can be acheived by executing deploy.py with
+  ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml as an argument.
+* Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
+  Environment:
+
+
+Command to deploy the os-nosdn-kvm_ovs_dpdk-ha scenario:
+
+.. code:: bash
+
+        $ cd ~/fuel/ci/
+        $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso
+
+where,
+    -b is used to specify the configuration directory
+
+    -i is used to specify the image downloaded from artifacts.
+
+**Note:**
+
+.. code:: bash
+
+          Check $ sudo ./deploy.sh -h for further information.
+
+* os-nosdn-kvm_ovs_dpdk-ha scenario can be executed from the jenkins project
+  "fuel-os-nosdn-kvm_ovs_dpdk-ha-baremetal-daily-master"
+* This scenario provides the High Availability feature by deploying
+  3 controller,2 compute nodes and checking if all the 5 nodes
+  are accessible(IP,up & running).
+* Test Scenario is passed if deployment is successful and all 5 nodes have
+  accessibility (IP , up & running).
+
+Known Limitations, Issues and Workarounds
+-----------------------------------------
+.. Explain any known limitations here.
+
+* Test scenario os-nosdn-kvm_ovs_dpdk-ha result is not stable.
+
+References
+----------
+
+For more information on the OPNFV Danube release, please visit
+http://www.opnfv.org/Danube
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/index.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/index.rst
new file mode 100755
index 000000000..742ddb1ee
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/index.rst
@@ -0,0 +1,14 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk-noha:
+
+*******************************************************
+os-nosdn-kvm_nfv_ovs_dpdk-noha Overview and Description
+*******************************************************
+
+.. toctree::
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst
new file mode 100644
index 000000000..a7778d963
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst
@@ -0,0 +1,239 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+
+.. http://creativecommons.org/licenses/by/4.0
+
+==========================================
+os-nosdn-kvm_nfv_ovs_dpdk-noha Description
+==========================================
+
+Introduction
+------------
+
+.. In this section explain the purpose of the scenario and the
+   types of capabilities provided
+
+The purpose of os-nosdn-kvm_ovs_dpdk-noha scenario testing is to test the No
+High Availability deployment and configuration of OPNFV software suite
+with OpenStack and without SDN software. This OPNFV software suite
+includes OPNFV KVM4NFV latest software packages for Linux Kernel and
+QEMU patches for achieving low latency. No High Availability feature is achieved
+by deploying OpenStack multi-node setup with 1 controller and 3 computes nodes.
+
+KVM4NFV packages will be installed on compute nodes as part of deployment.
+This scenario testcase deployment is happening on multi-node by using OPNFV Fuel deployer.
+
+Scenario Components and Composition
+------------------------------------
+.. In this section describe the unique components that make up the scenario,
+.. 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 deploys the No High Availability OPNFV Cloud based on the
+configurations provided in no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml.
+This yaml file contains following configurations and is passed as an
+argument to deploy.py script
+
+* ``scenario.yaml:`` This configuration file defines translation between a
+  short deployment scenario name(os-nosdn-kvm_ovs_dpdk-noha) and an actual deployment
+  scenario configuration file(no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml)
+
+* ``deployment-scenario-metadata:`` Contains the configuration metadata like
+  title,version,created,comment.
+
+.. code:: bash
+
+   deployment-scenario-metadata:
+      title: NFV KVM and OVS-DPDK NOHA deployment
+      version: 0.0.1
+      created: Dec 20 2016
+      comment: NFV KVM and OVS-DPDK
+
+* ``stack-extensions:`` Stack extentions are opnfv added value features in form
+  of a fuel-plugin.Plugins listed in stack extensions are enabled and
+  configured. os-nosdn-kvm_ovs_dpdk-noha scenario currently uses KVM-1.0.0 plugin.
+
+.. code:: bash
+
+   stack-extensions:
+      - module: fuel-plugin-kvm
+        module-config-name: fuel-nfvkvm
+        module-config-version: 1.0.0
+        module-config-override:
+          # Module config overrides
+
+* ``dea-override-config:`` Used to configure the NO-HA mode,network segmentation
+  types and role to node assignments.These configurations overrides
+  corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
+  These keys are used to deploy multiple nodes(``1 controller,3 computes``)
+  as mention below.
+
+  * **Node 1**:
+     - This node has MongoDB and Controller roles
+     - The controller node runs the Identity service, Image Service, management portions of
+       Compute and Networking, Networking plug-in and the dashboard
+     - Uses VLAN as an interface
+
+  * **Node 2**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  * **Node 3**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  * **Node 4**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  The below is the ``dea-override-config`` of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml file.
+
+.. code:: bash
+
+   dea-override-config:
+     fuel:
+       FEATURE_GROUPS:
+       - experimental
+     environment:
+       net_segment_type: vlan
+     nodes:
+     - id: 1
+       interfaces: interfaces_vlan
+       role: mongo,controller
+     - id: 2
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+     - id: 3
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+     - id: 4
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+
+     attributes_1:
+       hugepages:
+         dpdk:
+           value: 1024
+         nova:
+           value:
+             '2048': 1024
+
+     network:
+       networking_parameters:
+         segmentation_type: vlan
+       networks:
+       - cidr: null
+         gateway: null
+         ip_ranges: []
+         meta:
+           configurable: false
+           map_priority: 2
+           name: private
+           neutron_vlan_range: true
+           notation: null
+           render_addr_mask: null
+           render_type: null
+           seg_type: vlan
+           use_gateway: false
+           vlan_start: null
+         name: private
+         vlan_start: null
+
+     settings:
+       editable:
+         storage:
+           ephemeral_ceph:
+             description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes).
+             label: Ceph RBD for ephemeral volumes (Nova)
+             type: checkbox
+             value: true
+             weight: 75
+           images_ceph:
+             description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing.
+             label: Ceph RBD for images (Glance)
+             restrictions:
+             - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
+             type: checkbox
+             value: true
+             weight: 30
+
+* ``dha-override-config:`` Provides information about the VM definition and
+  Network config for virtual deployment.These configurations overrides
+  the pod dha definition and points to the controller,compute and
+  fuel definition files. The no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
+  has no dha-config changes i.e., default configuration is used.
+
+* os-nosdn-kvm_ovs_dpdk-noha scenario is successful when all the 4 Nodes are accessible,
+  up and running.
+
+
+
+**Note:**
+
+* In os-nosdn-kvm_ovs_dpdk-noha scenario, OVS is installed on the compute nodes with DPDK configured
+
+* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
+
+* Hugepages are only configured for compute nodes
+
+* This results in faster communication and data transfer among the compute nodes
+
+
+Scenario Usage Overview
+-----------------------
+
+.. Provide a brief overview on how to use the scenario and the features available to the
+.. user.  This should be an "introduction" to the userguide document, and explicitly link to it,
+.. where the specifics of the features are covered including examples and API's
+
+* The high availability feature is disabled and deploymet is done by deploy.py with
+  noha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml as an argument.
+* Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
+  Environment:
+
+
+Command to deploy the os-nosdn-kvm_ovs_dpdk-noha scenario:
+
+.. code:: bash
+
+        $ cd ~/fuel/ci/
+        $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso
+
+where,
+    -b is used to specify the configuration directory
+
+    -i is used to specify the image downloaded from artifacts.
+
+**Note:**
+
+.. code:: bash
+
+         Check $ sudo ./deploy.sh -h for further information.
+
+* os-nosdn-kvm_ovs_dpdk-noha scenario can be executed from the jenkins project
+  "fuel-os-nosdn-kvm_ovs_dpdk-noha-baremetal-daily-master"
+* This scenario provides the No High Availability feature by deploying
+  1 controller,3 compute nodes and checking if all the 4 nodes
+  are accessible(IP,up & running).
+* Test Scenario is passed if deployment is successful and all 4 nodes have
+  accessibility (IP , up & running).
+
+Known Limitations, Issues and Workarounds
+-----------------------------------------
+.. Explain any known limitations here.
+
+* Test scenario os-nosdn-kvm_ovs_dpdk-noha result is not stable.
+
+References
+----------
+
+For more information on the OPNFV Danube release, please visit
+http://www.opnfv.org/Danube
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/index.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/index.rst
new file mode 100755
index 000000000..a8192edcc
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/index.rst
@@ -0,0 +1,14 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk_bar-ha:
+
+*********************************************************
+os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Overview and Description
+*********************************************************
+
+.. toctree::
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst
new file mode 100644
index 000000000..0ab20514a
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst
@@ -0,0 +1,257 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+
+.. http://creativecommons.org/licenses/by/4.0
+
+============================================
+os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Description
+============================================
+
+Introduction
+------------
+
+.. In this section explain the purpose of the scenario and the
+   types of capabilities provided
+
+The purpose of os-nosdn-kvm_ovs_dpdk_bar-ha scenario testing is to test the
+High Availability deployment and configuration of OPNFV software suite
+with OpenStack and without SDN software. This OPNFV software suite
+includes OPNFV KVM4NFV latest software packages for Linux Kernel and
+QEMU patches for achieving low latency. High Availability feature is achieved
+by deploying OpenStack multi-node setup with 3 controllers and 2 computes nodes.
+
+OPNFV Barometer packages is used for traffic,performance and platform monitoring.
+KVM4NFV packages will be installed on compute nodes as part of deployment.
+This scenario testcase deployment is happening on multi-node by using OPNFV Fuel deployer.
+
+Scenario Components and Composition
+-----------------------------------
+.. In this section describe the unique components that make up the scenario,
+.. 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 deploys the High Availability OPNFV Cloud based on the
+configurations provided in ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml.
+This yaml file contains following configurations and is passed as an
+argument to deploy.py script
+
+* ``scenario.yaml:`` This configuration file defines translation between a
+  short deployment scenario name(os-nosdn-kvm_ovs_dpdk_bar-ha) and an actual deployment
+  scenario configuration file(ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml)
+
+* ``deployment-scenario-metadata:`` Contains the configuration metadata like
+  title,version,created,comment.
+
+.. code:: bash
+
+   deployment-scenario-metadata:
+      title: NFV KVM and OVS-DPDK HA deployment
+      version: 0.0.1
+      created: Dec 20 2016
+      comment: NFV KVM and OVS-DPDK
+
+* ``stack-extensions:`` Stack extentions are opnfv added value features in form
+  of a fuel-plugin.Plugins listed in stack extensions are enabled and
+  configured. os-nosdn-kvm_ovs_dpdk_bar-ha scenario currently uses KVM-1.0.0 plugin and barometer plugin.
+
+.. code:: bash
+
+  stack-extensions:
+     - module: fuel-plugin-kvm
+       module-config-name: fuel-nfvkvm
+       module-config-version: 1.0.0
+       module-config-override:
+        # Module config overrides
+     - module: fuel-plugin-collectd-ceilometer
+       module-config-name: fuel-barometer
+       module-config-version: 1.0.0
+       module-config-override:
+         # Module config overrides
+
+
+* ``dea-override-config:`` Used to configure the HA mode,network segmentation
+  types and role to node assignments.These configurations overrides
+  corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
+  These keys are used to deploy multiple nodes(``3 controllers,2 computes``)
+  as mention below.
+
+  * **Node 1**:
+     - This node has MongoDB and Controller roles
+     - The controller node runs the Identity service, Image Service, management portions of
+       Compute and Networking, Networking plug-in and the dashboard
+     - Uses VLAN as an interface
+
+  * **Node 2**:
+     - This node has Ceph-osd and Controller roles
+     - The controller node runs the Identity service, Image Service, management portions of
+       Compute and Networking, Networking plug-in and the dashboard
+     - Ceph is a massively scalable, open source, distributed storage system
+     - Uses VLAN as an interface
+
+  * **Node 3**:
+     - This node has Controller role in order to achieve high availability.
+     - Uses VLAN as an interface
+
+  * **Node 4**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  * **Node 5**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  The below is the ``dea-override-config`` of the ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.
+
+.. code:: bash
+
+   dea-override-config:
+     fuel:
+       FEATURE_GROUPS:
+       - experimental
+     nodes:
+     - id: 1
+       interfaces: interfaces_1
+       role: controller
+     - id: 2
+       interfaces: interfaces_1
+       role: mongo,controller
+     - id: 3
+       interfaces: interfaces_1
+       role: ceph-osd,controller
+     - id: 4
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+     - id: 5
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+
+     attributes_1:
+       hugepages:
+         dpdk:
+           value: 1024
+         nova:
+           value:
+             '2048': 1024
+
+     settings:
+       editable:
+         storage:
+           ephemeral_ceph:
+             description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes).
+             label: Ceph RBD for ephemeral volumes (Nova)
+             type: checkbox
+             value: true
+             weight: 75
+           images_ceph:
+             description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing.
+             label: Ceph RBD for images (Glance)
+             restrictions:
+             - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
+             type: checkbox
+             value: true
+             weight: 30
+
+* ``dha-override-config:`` Provides information about the VM definition and
+  Network config for virtual deployment.These configurations overrides
+  the pod dha definition and points to the controller,compute and
+  fuel definition files.
+
+  The below is the ``dha-override-config`` of the ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.
+
+.. code:: bash
+
+   dha-override-config:
+     nodes:
+     - id: 1
+       libvirtName: controller1
+       libvirtTemplate: templates/virtual_environment/vms/controller.xml
+     - id: 2
+       libvirtName: controller2
+       libvirtTemplate: templates/virtual_environment/vms/controller.xml
+     - id: 3
+       libvirtName: controller3
+       libvirtTemplate: templates/virtual_environment/vms/controller.xml
+     - id: 4
+       libvirtName: compute1
+       libvirtTemplate: templates/virtual_environment/vms/compute.xml
+     - id: 5
+       libvirtName: compute2
+       libvirtTemplate: templates/virtual_environment/vms/compute.xml
+     - id: 6
+       libvirtName: fuel-master
+       libvirtTemplate: templates/virtual_environment/vms/fuel.xml
+       isFuel: yes
+       username: root
+       password: r00tme
+
+
+* os-nosdn-kvm_ovs_dpdk_bar-ha scenario is successful when all the 5 Nodes are accessible, up and running.
+
+
+**Note:**
+
+* In os-nosdn-kvm_ovs_dpdk_bar-ha scenario, OVS is installed on the compute nodes with DPDK configured
+
+* Baraometer plugin is also implemented along with KVM plugin
+
+* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
+
+* Hugepages are only configured for compute nodes
+
+* This results in faster communication and data transfer among the compute nodes
+
+
+Scenario Usage Overview
+------------------------
+.. Provide a brief overview on how to use the scenario and the features available to the
+.. user.  This should be an "introduction" to the userguide document, and explicitly link to it,
+.. where the specifics of the features are covered including examples and API's
+
+* The high availability feature can be acheived by executing deploy.py with
+  ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml as an argument.
+* Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
+  Environment:
+
+
+Command to deploy the os-nosdn-kvm_ovs_dpdk_bar-ha scenario:
+
+.. code:: bash
+
+        $ cd ~/fuel/ci/
+        $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso
+
+where,
+    -b is used to specify the configuration directory
+
+    -i is used to specify the image downloaded from artifacts.
+
+**Note:**
+
+.. code:: bash
+
+         Check $ sudo ./deploy.sh -h for further information.
+
+* os-nosdn-kvm_ovs_dpdk_bar-ha scenario can be executed from the jenkins project
+  "fuel-os-nosdn-kvm_ovs_dpdk_bar-ha-baremetal-daily-master"
+* This scenario provides the High Availability feature by deploying
+  3 controller,2 compute nodes and checking if all the 5 nodes
+  are accessible(IP,up & running).
+* Test Scenario is passed if deployment is successful and all 5 nodes have
+  accessibility (IP , up & running).
+
+Known Limitations, Issues and Workarounds
+-----------------------------------------
+.. Explain any known limitations here.
+
+* Test scenario os-nosdn-kvm_ovs_dpdk_bar-ha result is not stable.
+
+References
+----------
+
+For more information on the OPNFV Danube release, please visit
+http://www.opnfv.org/Danube
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/index.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/index.rst
new file mode 100755
index 000000000..3a07e98c9
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/index.rst
@@ -0,0 +1,14 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk_bar-noha:
+
+***********************************************************
+os-nosdn-kvm_nfv_ovs_dpdk_bar-noha Overview and Description
+***********************************************************
+
+.. toctree::
+   :numbered:
+   :maxdepth: 3
+
+   ./os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst
diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst
new file mode 100644
index 000000000..47a7f1034
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst
@@ -0,0 +1,244 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+
+.. http://creativecommons.org/licenses/by/4.0
+
+============================================
+os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Description
+============================================
+
+Introduction
+-------------
+
+.. In this section explain the purpose of the scenario and the
+   types of capabilities provided
+
+The purpose of os-nosdn-kvm_ovs_dpdk_bar-noha scenario testing is to test the
+No High Availability deployment and configuration of OPNFV software suite
+with OpenStack and without SDN software. This OPNFV software suite
+includes OPNFV KVM4NFV latest software packages for Linux Kernel and
+QEMU patches for achieving low latency.No High Availability feature is achieved
+by deploying OpenStack multi-node setup with 1 controller and 3 computes nodes.
+
+OPNFV Barometer packages is used for traffic,performance and platform monitoring.
+KVM4NFV packages will be installed on compute nodes as part of deployment.
+This scenario testcase deployment is happening on multi-node by using OPNFV Fuel deployer.
+
+Scenario Components and Composition
+------------------------------------
+.. In this section describe the unique components that make up the scenario,
+.. 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 deploys the No High Availability OPNFV Cloud based on the
+configurations provided in no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml.
+This yaml file contains following configurations and is passed as an
+argument to deploy.py script
+
+* ``scenario.yaml:`` This configuration file defines translation between a
+  short deployment scenario name(os-nosdn-kvm_ovs_dpdk_bar-noha) and an actual deployment
+  scenario configuration file(no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml)
+
+* ``deployment-scenario-metadata:`` Contains the configuration metadata like
+  title,version,created,comment.
+
+.. code:: bash
+
+   deployment-scenario-metadata:
+      title: NFV KVM and OVS-DPDK HA deployment
+      version: 0.0.1
+      created: Dec 20 2016
+      comment: NFV KVM and OVS-DPDK
+
+* ``stack-extensions:`` Stack extentions are opnfv added value features in form
+  of a fuel-plugin.Plugins listed in stack extensions are enabled and
+  configured. os-nosdn-kvm_ovs_dpdk_bar-noha scenario currently uses KVM-1.0.0 plugin and barometer-1.0.0 plugin.
+
+.. code:: bash
+
+  stack-extensions:
+     - module: fuel-plugin-kvm
+       module-config-name: fuel-nfvkvm
+       module-config-version: 1.0.0
+       module-config-override:
+        # Module config overrides
+     - module: fuel-plugin-collectd-ceilometer
+       module-config-name: fuel-barometer
+       module-config-version: 1.0.0
+       module-config-override:
+         # Module config overrides
+
+* ``dea-override-config:`` Used to configure the HA mode,network segmentation
+  types and role to node assignments.These configurations overrides
+  corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
+  These keys are used to deploy multiple nodes(``1 controller,3 computes``)
+  as mention below.
+
+  * **Node 1**:
+     - This node has MongoDB and Controller roles
+     - The controller node runs the Identity service, Image Service, management portions of
+       Compute and Networking, Networking plug-in and the dashboard
+     - Uses VLAN as an interface
+
+  * **Node 2**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  * **Node 3**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  * **Node 4**:
+     - This node has compute and Ceph-osd roles
+     - Ceph is a massively scalable, open source, distributed storage system
+     - By default, Compute uses KVM as the hypervisor
+     - Uses DPDK as an interface
+
+  The below is the ``dea-override-config`` of the no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.
+
+.. code:: bash
+
+   dea-override-config:
+     fuel:
+       FEATURE_GROUPS:
+       - experimental
+     environment:
+       net_segment_type: vlan
+     nodes:
+     - id: 1
+       interfaces: interfaces_vlan
+       role: mongo,controller
+     - id: 2
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+     - id: 3
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+     - id: 4
+       interfaces: interfaces_dpdk
+       role: ceph-osd,compute
+       attributes: attributes_1
+
+     attributes_1:
+       hugepages:
+         dpdk:
+           value: 1024
+         nova:
+           value:
+             '2048': 1024
+
+     network:
+       networking_parameters:
+         segmentation_type: vlan
+       networks:
+       - cidr: null
+         gateway: null
+         ip_ranges: []
+         meta:
+           configurable: false
+           map_priority: 2
+           name: private
+           neutron_vlan_range: true
+           notation: null
+           render_addr_mask: null
+           render_type: null
+           seg_type: vlan
+           use_gateway: false
+           vlan_start: null
+         name: private
+         vlan_start: null
+
+     settings:
+       editable:
+         storage:
+           ephemeral_ceph:
+             description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes).
+             label: Ceph RBD for ephemeral volumes (Nova)
+             type: checkbox
+             value: true
+             weight: 75
+           images_ceph:
+             description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing.
+             label: Ceph RBD for images (Glance)
+             restrictions:
+             - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
+             type: checkbox
+             value: true
+             weight: 30
+
+* ``dha-override-config:`` Provides information about the VM definition and
+  Network config for virtual deployment.These configurations overrides
+  the pod dha definition and points to the controller,compute and
+  fuel definition files. The noha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml has no dha-config changes i.e., default    configuration is used.
+
+* os-nosdn-kvm_ovs_dpdk_bar-noha scenario is successful when all the 4 Nodes are accessible,
+  up and running.
+
+
+
+**Note:**
+
+* In os-nosdn-kvm_ovs_dpdk_bar-noha scenario, OVS is installed on the compute nodes with DPDK configured
+
+* Baraometer plugin is also implemented along with KVM plugin.
+
+* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
+
+* Hugepages are only configured for compute nodes
+
+* This results in faster communication and data transfer among the compute nodes
+
+Scenario Usage Overview
+-----------------------
+.. Provide a brief overview on how to use the scenario and the features available to the
+.. user.  This should be an "introduction" to the userguide document, and explicitly link to it,
+.. where the specifics of the features are covered including examples and API's
+
+* The high availability feature is disabled and deploymet is done by deploy.py with
+  noha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml as an argument.
+* Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
+  Environment:
+
+
+Command to deploy the os-nosdn-kvm_ovs_dpdk_bar-noha scenario:
+
+.. code:: bash
+
+        $ cd ~/fuel/ci/
+        $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso
+
+where,
+    -b is used to specify the configuration directory
+
+    -i is used to specify the image downloaded from artifacts.
+
+Note:
+
+.. code:: bash
+
+          Check $ sudo ./deploy.sh -h for further information.
+
+* os-nosdn-kvm_ovs_dpdk_bar-noha scenario can be executed from the jenkins project
+  "fuel-os-nosdn-kvm_ovs_dpdk_bar-noha-baremetal-daily-master"
+* This scenario provides the No High Availability feature by deploying
+  1 controller,3 compute nodes and checking if all the 4 nodes
+  are accessible(IP,up & running).
+* Test Scenario is passed if deployment is successful and all 4 nodes have
+  accessibility (IP , up & running).
+
+Known Limitations, Issues and Workarounds
+-----------------------------------------
+.. Explain any known limitations here.
+
+* Test scenario os-nosdn-kvm_ovs_dpdk_bar-noha result is not stable.
+
+References
+----------
+
+For more information on the OPNFV Danube release, please visit
+http://www.opnfv.org/Danube