diff options
author | ChristopherPrice <christopher.price@ericsson.com> | 2016-07-26 12:05:00 +0200 |
---|---|---|
committer | ChristopherPrice <christopher.price@ericsson.com> | 2016-07-26 12:05:00 +0200 |
commit | 6da365c5898a3a20638dc18b21cb1c307b61f711 (patch) | |
tree | d84fb56594670c1b16646e4055c259710ccb2c8a /docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst | |
parent | 7d6d582ffc69597ef82e7eed7c34e27f71b4889e (diff) |
Updating the scenario installation template based on comments.
Commets from https://gerrit.opnfv.org/gerrit/#/c/16837 adressed.
Change-Id: I83a58c5ec6088805a8670bc7801351d33c6e5fa8
Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
Diffstat (limited to 'docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst')
-rw-r--r-- | docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst b/docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst index c546a35f3..450c8bf5e 100644 --- a/docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst +++ b/docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst @@ -7,14 +7,14 @@ Preparation .. Not all of these options are relevant for all scenario's. I advise following the .. instructions applicable to the deploy tool used in the scenario. -Before starting the installation of the <template> scenario some preparation must -be done. You may choose to install the <template> scenario using an ISO image, or +Before starting the installation of the <scenario> scenario some preparation must +be done. You may choose to install the <scenario> scenario using an ISO image, or executing the installation from a prepared jumphost. Preparing your jumphost to install by script -------------------------------------------- -To deploy the <template> scenario from a script you will need to prepare the jumphost +To deploy the <scenario> scenario from a script you will need to prepare the jumphost with a compatible operating system. Prepare your jumphost running CentOS 7 with libvirt running on it. You may then install the RDO Release RPM: @@ -27,13 +27,13 @@ the OpenVSwitch RPM from the RDO Project repositories and install it with the op Preparing your jumphost using an ISO image ------------------------------------------ -An alternative to preparing your own jumphost id to use a <template> ISO image as a boot image. +An alternative to preparing your own jumphost id to use a <scenario> ISO image as a boot image. Download or build the ISO image according to the following instructions. Retrieving the ISO image ^^^^^^^^^^^^^^^^^^^^^^^^ -If you choose to install the <template> scenario from an ISO image you must first +If you choose to install the <scenario> scenario from an ISO image you must first retrieve the <template-containing>.iso image of the Colorado release. This can be found can be found at <hyperlink required>. @@ -41,12 +41,12 @@ Building the ISO image ^^^^^^^^^^^^^^^^^^^^^^ Alternatively, you may choose to build the Fuel .iso from source by cloning the -opnfv/fuel git repository. To retrieve the repository for the Brahmaputra release use the following command: +opnfv/fuel git repository. To retrieve the repository for the Colorado release use the following command: $ git clone https://gerrit.opnfv.org/gerrit/fuel -Check-out the Brahmaputra release tag to set the HEAD to the -baseline required to replicate the Brahmaputra release: +Check-out the Colorado release tag to set the HEAD to the +baseline required to replicate the Colorado release: $ git checkout colorado.1.0 @@ -59,7 +59,7 @@ For more information on how to build, please see *Reference: 14* Booting from the ISO image ^^^^^^^^^^^^^^^^^^^^^^^^^^ -Mount the <template> ISO file/media as a boot device on the jump host server. If all your hardware +Mount the <scenario> ISO file/media as a boot device on the jump host server. If all your hardware preparation is complete at this time you should reboot the jumphost to establish the deployment server. |