diff options
Diffstat (limited to 'docs/release/installation')
| -rw-r--r-- | docs/release/installation/abstract.rst | 6 | ||||
| -rw-r--r-- | docs/release/installation/baremetal.rst | 2 | ||||
| -rw-r--r-- | docs/release/installation/introduction.rst | 2 | ||||
| -rw-r--r-- | docs/release/installation/requirements.rst | 2 | ||||
| -rw-r--r-- | docs/release/installation/upstream.rst | 4 |
5 files changed, 8 insertions, 8 deletions
diff --git a/docs/release/installation/abstract.rst b/docs/release/installation/abstract.rst index 2d55c154..ab78691a 100644 --- a/docs/release/installation/abstract.rst +++ b/docs/release/installation/abstract.rst @@ -1,16 +1,16 @@ Abstract ======== -This document describes how to install the Gambia release of OPNFV when +This document describes how to install the Hunter release of OPNFV when using Apex as a deployment tool covering it's limitations, dependencies and required system resources. License ======= -Gambia release of OPNFV when using Apex as a deployment tool Docs +Hunter release of OPNFV when using Apex as a deployment tool Docs (c) by Tim Rozet (Red Hat) -Gambia release of OPNFV when using Apex as a deployment tool Docs +Hunter release of OPNFV when using Apex as a deployment tool Docs are licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>. diff --git a/docs/release/installation/baremetal.rst b/docs/release/installation/baremetal.rst index efea0f86..03657f04 100644 --- a/docs/release/installation/baremetal.rst +++ b/docs/release/installation/baremetal.rst @@ -90,7 +90,7 @@ Install Bare Metal Jump Host ``sudo yum install https://repos.fedorapeople.org/repos/openstack/openstack-queens/rdo-release-queens-1.noarch.rpm`` ``sudo yum install epel-release`` - ``sudo curl -o /etc/yum.repos.d/opnfv-apex.repo http://artifacts.opnfv.org/apex/gambia/opnfv-apex.repo`` + ``sudo curl -o /etc/yum.repos.d/opnfv-apex.repo http://artifacts.opnfv.org/apex/hunter/opnfv-apex.repo`` The RDO Project release repository is needed to install OpenVSwitch, which is a dependency of opnfv-apex. If you do not have external connectivity to diff --git a/docs/release/installation/introduction.rst b/docs/release/installation/introduction.rst index 706e2265..a2e13774 100644 --- a/docs/release/installation/introduction.rst +++ b/docs/release/installation/introduction.rst @@ -1,7 +1,7 @@ Introduction ============ -This document describes the steps to install an OPNFV Gambia reference +This document describes the steps to install an OPNFV Hunter reference platform using the Apex installer. The audience is assumed to have a good background in networking diff --git a/docs/release/installation/requirements.rst b/docs/release/installation/requirements.rst index 239db197..3da39967 100644 --- a/docs/release/installation/requirements.rst +++ b/docs/release/installation/requirements.rst @@ -15,7 +15,7 @@ The Jump Host requirements are outlined below: 4. minimum 1 networks and maximum 5 networks, multiple NIC and/or VLAN combinations are supported. This is virtualized for a VM deployment. -5. The Gambia Apex RPM and its dependencies. +5. The Hunter Apex RPM and its dependencies. 6. 16 GB of RAM for a bare metal deployment, 64 GB of RAM for a Virtual Deployment. diff --git a/docs/release/installation/upstream.rst b/docs/release/installation/upstream.rst index f18c4b11..59aa57c3 100644 --- a/docs/release/installation/upstream.rst +++ b/docs/release/installation/upstream.rst @@ -36,9 +36,9 @@ in order to download and prepare the cached artifacts. Scenarios and Deploy Settings for Upstream Deployments ------------------------------------------------------ -The deploy settings and scenarios included with the Gambia release of Apex will +The deploy settings and scenarios included with the Hunter release of Apex will be supported as deemed by the `OPNFV Scenarios in Apex`_ section of this guide. -Each of these scenarios has been tested by Apex over the Gambia release, and +Each of these scenarios has been tested by Apex over the Hunter release, and using those deploy settings will control which upstream artifacts are pulled at deploy time. By specifying different versions of OpenStack, ODL, or other components in the deploy settings, different upstream artifacts may be downloaded |