Migrate docs to the new Danube dir structure.

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

diff --git a/docs/scenarios/os-nosdn-ovs/scenario.description.rst b/docs/scenarios/os-nosdn-ovs/scenario.description.rst
deleted file mode 100644 (file)
index 04d88a1..0000000
--- a/docs/scenarios/os-nosdn-ovs/scenario.description.rst
+++ /dev/null
@@ -1,48 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) Intel Corporation
-
-Introduction
-============
-For Fuel this scenario installs the latest DPDK-enabled Open vSwitch component,
-version - 2.5.90 based on DPDK 16.07.
-
-For Apex this scenario installs the latest DPDK-enabled Open vSwitch component,
-version - 2.5.90 based on DPDK 16.04.
-
-Scenario components and composition
-===================================
-This scenario is currently able to be installed using the Fuel and Apex installers.
-For details on how to install the ovsnfv scenarion using these installer tools
-please refer to the installation instructions at:
-  * Fuel installation instruction: http://artifacts.opnfv.org/fuel/colorado/2.0/docs/installation-instruction/index.html
-  * Apex installation instruction: http://artifacts.opnfv.org/apex/colorado/2.0/docs/installation-instruction/index.html
-
-.. Above links need to be updated with the eventual release URL's.  This will need to be done closer to the
-.. release date once the project and docs team have a solution ready and the final version of the installation
-.. documents are done.
-
-Scenario usage overview
-=======================
-After installation use of the scenario requires no further action by the user.
-Traffic on the private network will automatically be processed by the upgraded
-DPDK datapath.
-
-Limitations, Issues and Workarounds
-===================================
-The same limitations that apply to using Fuel DPDK-enabled interfaces also apply
-when using this scenario. Including:
-
-* Fuel9 OVS-DPDK support works only for VLAN segmentation.
-* Only interfaces running the private network (and no other network) can be
-  supported so each node needs a separate interface dedicated to the private network.
-* The nodes with dpdk enabled interfaces will need to have hugepages
-  configured and some cores reserved for dpdk.
-
-
-References
-==========
-
-For more information on the OPNFV Colorado release, please visit
-http://www.opnfv.org/colorado
-