summaryrefslogtreecommitdiffstats
path: root/docs/installation-instructions/virtualinstall.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/installation-instructions/virtualinstall.rst')
-rw-r--r--docs/installation-instructions/virtualinstall.rst57
1 files changed, 31 insertions, 26 deletions
diff --git a/docs/installation-instructions/virtualinstall.rst b/docs/installation-instructions/virtualinstall.rst
index c2ee66d8..01971893 100644
--- a/docs/installation-instructions/virtualinstall.rst
+++ b/docs/installation-instructions/virtualinstall.rst
@@ -2,24 +2,25 @@ 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 compute node 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.
+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.
+This section goes step-by-step on how to correctly install and provision the
+OPNFV target system to VM nodes.
Install Jumphost
----------------
@@ -33,32 +34,36 @@ 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:
+If no modifications are made to the included configurations the target
+environment will deploy with the following architecture:
- - 1 Undercloud VM
+ - 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)
- - 2-4 networks: provisioning / internal API, storage, private tenant networking
- and the external network. The storage and tenant networking networks
- can be collapsed onto the provisioning network.
+ - 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 [ --flat ] -n network_settings.yaml -i inventory.yaml -d deploy_settings.yaml``
+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.
+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 you will see "Overcloud Deployed"
+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.
+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