summaryrefslogtreecommitdiffstats
path: root/docs/installation-instructions/introduction.rst
diff options
context:
space:
mode:
authorTim Rozet <trozet@redhat.com>2016-04-08 18:56:27 +0000
committerGerrit Code Review <gerrit@172.30.200.206>2016-04-08 18:56:27 +0000
commit1b33d33b234cf64833516cd45099c0766a4ab2fd (patch)
tree9aebebd42e0ac38aba09eeb225d920be9760c8b1 /docs/installation-instructions/introduction.rst
parent2b66c3113aa34829621e140b66fbfb25dbf086cf (diff)
parenta49f39bda754e493553cd4c8fb8459893db60c7b (diff)
Merge "Documentation updates for Colorado"
Diffstat (limited to 'docs/installation-instructions/introduction.rst')
-rw-r--r--docs/installation-instructions/introduction.rst24
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/installation-instructions/introduction.rst b/docs/installation-instructions/introduction.rst
index 25452614..3d5d1bc4 100644
--- a/docs/installation-instructions/introduction.rst
+++ b/docs/installation-instructions/introduction.rst
@@ -1,7 +1,7 @@
Introduction
============
-This document describes the steps to install an OPNFV Bramaputra reference
+This document describes the steps to install an OPNFV Colorado reference
platform, as defined by the Genesis Project using the Apex installer.
The audience is assumed to have a good background in networking
@@ -10,31 +10,31 @@ and Linux administration.
Preface
=======
-Apex uses the RDO Manager Open Source project as a server provisioning tool.
-RDO Manager is the RDO Project implimentation of OpenStack's Triple-O project.
-The Triple-O image based life cycle installation tool provisions an OPNFV
-Target System (3 controllers, n number of compute nodes) with OPNFV specific
-configuration provided by the Apex deployment tool chain.
+Apex uses Triple-O from the RDO Project OpenStack distribution as a
+provisioning tool. The Triple-O image based life cycle installation
+tool provisions an OPNFV Target System (3 controllers, n number of
+compute nodes) with OPNFV specific configuration provided by the Apex
+deployment tool chain.
The Apex deployment artifacts contain the necessary tools to deploy and
configure an OPNFV target system using the Apex deployment toolchain.
These artifacts offer the choice of using the Apex bootable ISO
-(``opnfv-apex-bramaputra.iso``) to both install CentOS 7 and the
-nessesary materials to deploy or the Apex RPM (``opnfv-apex.rpm``)
+(``opnfv-apex-colorado.iso``) to both install CentOS 7 and the
+necessary materials to deploy or the Apex RPMs (``opnfv-apex*.rpm``)
which expects installation to a CentOS 7 libvirt enabled host. The RPM
-contains a collection of configuration file, prebuilt disk images,
+contains a collection of configuration files, prebuilt disk images,
and the automatic deployment script (``opnfv-deploy``).
An OPNFV install requires a "Jumphost" in order to operate. The bootable
ISO will allow you to install a customized CentOS 7 release to the Jumphost,
which includes the required packages needed to run ``opnfv-deploy``.
If you already have a Jumphost with CentOS 7 installed, you may choose to
-skip the ISO step and simply install the (``opnfv-apex.rpm``) RPM. The RPM
-is the same RPM included in the ISO and includes all the necessary disk
+skip the ISO step and simply install the (``opnfv-apex*.rpm``) RPMs. The RPMs
+are the same RPMs included in the ISO and include all the necessary disk
images and configuration files to execute an OPNFV deployment. Either method
will prepare a host to the same ready state for OPNFV deployment.
-``opnfv-deploy`` instantiates an RDO Manager Undercloud VM server using libvirt
+``opnfv-deploy`` instantiates a Triple-O Undercloud VM server using libvirt
as its provider. This VM is then configured and used to provision the
OPNFV target deployment (3 controllers, n compute nodes). These nodes can
be either virtual or bare metal. This guide contains instructions for