summaryrefslogtreecommitdiffstats
path: root/docs/installationprocedure/virtualinstall.rst
diff options
context:
space:
mode:
authorSofia Wallin <sofia.wallin@ericsson.com>2016-08-19 16:39:06 +0200
committerSofia Wallin <sofia.wallin@ericsson.com>2016-08-19 16:39:06 +0200
commit1e4742787c6c45b44f5e49de03ec8b1b1075c04e (patch)
treea58b62aaf2637676066e26517ecda0e1b07f6f23 /docs/installationprocedure/virtualinstall.rst
parent4862f3b57479d64c5408268cc2086b53e4e97b81 (diff)
Renamed install instructions folder according to docs directive
Change-Id: I8970be0bcbed501e43d6fb76af1278881274f69a Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
Diffstat (limited to 'docs/installationprocedure/virtualinstall.rst')
-rw-r--r--docs/installationprocedure/virtualinstall.rst69
1 files changed, 69 insertions, 0 deletions
diff --git a/docs/installationprocedure/virtualinstall.rst b/docs/installationprocedure/virtualinstall.rst
new file mode 100644
index 0000000..0197189
--- /dev/null
+++ b/docs/installationprocedure/virtualinstall.rst
@@ -0,0 +1,69 @@
+Installation High-Level Overview - Virtual Deployment
+=====================================================
+
+The VM nodes deployment operates almost the same way as the bare metal
+deployment with a few differences. ``opnfv-deploy`` still deploys an
+undercloud VM. In addition to the undercloud VM a collection of VMs
+(3 control nodes + 2 compute for an HA deployment or 1 control node and 1
+or more compute nodes for a non-HA Deployment) will be defined for the target
+OPNFV deployment. The part of the toolchain that executes IPMI power
+instructions calls into libvirt instead of the IPMI interfaces on baremetal
+servers to operate the power managment. These VMs are then provisioned with
+the same disk images and configuration that baremetal would be. To Triple-O
+these nodes look like they have just built and registered the same way as bare
+metal nodes, the main difference is the use of a libvirt driver for the power
+management. Finally, the default network_settings file will deploy without
+modification. Customizations are welcome but not needed if a generic set of
+network_settings are acceptable.
+
+Installation Guide - Virtual Deployment
+=======================================
+
+This section goes step-by-step on how to correctly install and provision the
+OPNFV target system to VM nodes.
+
+Install Jumphost
+----------------
+
+Follow the instructions in the `Install Bare Metal Jumphost`_ section.
+
+Running ``opnfv-deploy``
+------------------------
+
+You are now ready to deploy OPNFV!
+``opnfv-deploy`` has virtual deployment capability that includes all of
+the configuration nessesary to deploy OPNFV with no modifications.
+
+If no modifications are made to the included configurations the target
+environment will deploy with the following architecture:
+
+ - 1 undercloud VM
+
+ - The option of 3 control and 2 or more compute VMs (HA Deploy / default)
+ or 1 control and 1 or more compute VM (Non-HA deploy / pass -n)
+
+ - 1-5 networks: provisioning, private tenant networking, external, storage
+ and internal API. The API, storage and tenant networking networks can be
+ collapsed onto the provisioning network.
+
+Follow the steps below to execute:
+
+1. ``sudo opnfv-deploy -v [ --virtual-computes n ]
+ [ --virtual-cpus n ] [ --virtual-ram n ] [ --flat ]
+ -n network_settings.yaml -i inventory.yaml -d deploy_settings.yaml``
+
+2. It will take approximately 45 minutes to an hour to stand up undercloud,
+ define the target virtual machines, configure the deployment and execute
+ the deployment. You will notice different outputs in your shell.
+
+3. When the deployment is complete the IP for the undercloud and a url for the
+ OpenStack dashboard will be displayed
+
+Verifying the Setup - VMs
+-------------------------
+
+To verify the set you can follow the instructions in the `Verifying the Setup`_
+section.
+
+.. _`Install Bare Metal Jumphost`: baremetal.html
+.. _`Verifying the Setup`: verification.html