Moving documentation content into new template

JIRA: DOCS-103, DOCS-134, SDNVPN-40

Moving documentation content into new feature description and user guide template.

Change-Id: I2c1549b44ef43e28961f1a0d2885adc0dd161910
Signed-off-by: Tim Irnich <tim.irnich@ericsson.com>

1 files changed, 0 insertions, 72 deletions

diff --git a/docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst b/docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst
deleted file mode 100644
index 649b5a4..0000000
--- a/docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst
+++ /dev/null
@@ -1,72 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International
-.. License. .. http://creativecommons.org/licenses/by/4.0 ..
-.. (c) Christopher Price (Ericsson AB), Nikolas Hermanns (Ericsson AB) and other
-
-Fuel installation and scenario deployment
-================================================
-
-This section describes the installation of the os-odl_l2-bgpvpn-ha or
-os-odl_l2-bgpvpn-noha OPNFV reference platform stack across a server cluster.
-
-Scenario Preparation
---------------------
-dea.yaml and dha.yaml need to be copied and changed according to the lap/host
-where you deploy.
-Copy the full lab config from:
-::
-
- cp <path-to-opnfv-fuel-repo>/deploy/config/labs/devel-pipeline/elx \
-    <path-to-opnfv-fuel-repo>/deploy/config/labs/devel-pipeline/<your-lab-name>
-
-Add at the bottom of dha.yaml.
-::
-
- disks:
-   fuel: 100G
-   controller: 100G
-   compute: 100G
-
- define_vms:
-   controller:
-     vcpu:
-       value: 4
-     memory:
-       attribute_equlas:
-         unit: KiB
-       value: 16388608
-     currentMemory:
-       attribute_equlas:
-         unit: KiB
-       value: 16388608
-
-Check if dea.yaml contains all your needed changes.
-
-Installation procedures
------------------------
-
-We describe several alternative procedures in the following.
-Go to
-::
-
- cd <opnfv-fuel-repo>/ci
-
-Full automatic virtual deployment High Availablity Mode
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-::
-
- sudo bash ./deploy.sh -b file://<path-to-opnfv-fuel-repo>/config/ -l devel-pipeline -p <your-lab-name> -s os-odl_l2-bgpvpn-ha -i file://<path-to-fuel-iso>
-
-Full automatic virtual deployment NO High Availablity Mode
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-::
-
- sudo bash ./deploy.sh -b file://<path-to-opnfv-fuel-repo>/config/ -l devel-pipeline -p <your-lab-name> -s os-odl_l2-bgpvpn-noha -i file://<path-to-fuel-iso>
-
-Automatic Fuel installation and manual scenario deployment
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-::
-
- sudo bash ./deploy.sh -b file://<path-to-opnfv-fuel-repo>/config/ -l devel-pipeline -p <your-lab-name> -s os-odl_l2-bgpvpn-ha -i file://<path-to-fuel-iso> -e
-
-With -e option the installer does not launch environment deployment, so
-a user can do some modification before the scenario is really deployed. Another interesting option is the -f option which deploys the scenario  on existing Fuel.