diff options
author | Dan Radez <dradez@redhat.com> | 2016-01-19 14:36:31 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@172.30.200.206> | 2016-01-19 14:36:31 +0000 |
commit | bd2faa0275917ef18606f781f462d33387d2532a (patch) | |
tree | 05d840945479cd77595839ed20951f68294a5557 /docs/installation-instructions/architecture.rst | |
parent | 668e52b657e134d27dbd03b473dc927daa58dda6 (diff) | |
parent | f479b77c4f7c0d11196e3902bb7e60ff8e34a1fe (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. |