diff options
Diffstat (limited to 'docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst')
| -rw-r--r-- | docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst | 79 |
1 files changed, 52 insertions, 27 deletions
diff --git a/docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst b/docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst index ecb4e52..649b5a4 100644 --- a/docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst +++ b/docs/installationprocedure/os-odl_l2-bgpvpn/installation.rst @@ -1,47 +1,72 @@ .. 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) and others +.. (c) Christopher Price (Ericsson AB), Nikolas Hermanns (Ericsson AB) and other -Fuel server installation and scenario deployment +Fuel installation and scenario deployment ================================================ -.. Let's figure out how to structure this to highlight both virtual and -.. bare metal deployments. I need some help from the scenrio owners to get -.. that right. - -This section describes the installation of the OPNFV installation -server (jumphost) as well as the deployment of the os-odl_l2-bgpvpn-ha or +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. -Preparation ------------ +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. +:: -clone fuel repo -download opnfv iso -create dea.yaml and dha.yaml based on existing examples from FUel repo + 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 jumphost installation and deployment -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Full automatic virtual deployment High Availablity Mode +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +:: -call deploy.sh with scenario string + 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> -Automatic Fuel server installation and manual scenario deployment -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Full automatic virtual deployment NO High Availablity Mode +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +:: -call deploy.sh with -e option to only install FUel server i.e. no platform deployment -Log into Fuel web GUI and configure scenario options, including activation of SDN VPN feature -PXE boot compute nodes from Fuel server -Trigger deployment through web GUI + 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> -Update Fuel server settings without re-installation -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Automatic Fuel installation and manual scenario deployment +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +:: -In case of having to change the jumphost settings without having the reinstall the -whole jumphost, it is possible to call deploy-sh with the -f option, which will only -update the settings without reinstalling the host, saving a lot of time. + 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. |