diff options
author | Tim Rozet <trozet@redhat.com> | 2016-01-20 16:46:18 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@172.30.200.206> | 2016-01-20 16:46:19 +0000 |
commit | 09188ece3e74e48f0cd3b0be346bfc455700ac33 (patch) | |
tree | 669aee3f3e3f2cec9bfbde681f2434368eaa361c /docs/installation-instructions/architecture.rst | |
parent | df14e77ab9d9f082b75c644db189ce30a89ed891 (diff) | |
parent | 129983418ead2f1352fa1998d4b74d19b40c484d (diff) |
Merge "Restructured the installation-instruction file into indexed sub files"
Diffstat (limited to 'docs/installation-instructions/architecture.rst')
-rw-r--r-- | docs/installation-instructions/architecture.rst | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/installation-instructions/architecture.rst b/docs/installation-instructions/architecture.rst new file mode 100644 index 00000000..33b96bd0 --- /dev/null +++ b/docs/installation-instructions/architecture.rst @@ -0,0 +1,24 @@ +Triple-O Deployment Architecture +================================ + +Apex is based on RDO Manager which is the RDO Project's implementation of +the OpenStack Triple-O project. It is important to understand the basics +of a Triple-O deployment to help make decisions that will assist in +successfully deploying OPNFV. + +Triple-O stands for OpenStack On OpenStack. This means that OpenStack +will be used to install OpenStack. The target OPNFV deployment is an +OpenStack cloud with NFV features built-in that will be deployed by a +smaller all-in-one deployment of OpenStack. In this deployment +methodology there are two OpenStack installations. They are referred +to as the undercloud and the overcloud. The undercloud is used to +deploy the overcloud. + +The undercloud is the all-in-one installation of OpenStack that includes +baremetal provisioning. RDO Manager's deployment of the undercloud is +call Instack. Instack will be deployed as a virtual machine on a jumphost. +This VM is pre-built and distributed as part of the Apex RPM. + +The overcloud is OPNFV. Configuration will be passed into Instack and +Instack will use OpenStack's orchestration component call Heat to +execute a deployment will provision the target nodes to become OPNFV. |