diff options
author | Dan Radez <dradez@redhat.com> | 2016-08-10 15:53:36 -0400 |
---|---|---|
committer | Dan Radez <dradez@redhat.com> | 2016-08-11 14:26:41 -0400 |
commit | c3643b857be79ebdfd2340118ccd8288bb80cb23 (patch) | |
tree | 7b6459805865ae75369dcc15dcbf8710e41b8746 /docs/installation-instructions/requirements.rst | |
parent | 1900c3825ef9163b721cda7c117c18a42aa84fb9 (diff) |
Initial pass through the docs for Colorado Release
- doc8 compatibility
- wraped lines at 79 chars
- updated basic information
- have not added any new feature information
JIRA: DOCS-114
Change-Id: I6fad44315ce9211305399d2d220d0fe80365454a
Signed-off-by: Dan Radez <dradez@redhat.com>
Diffstat (limited to 'docs/installation-instructions/requirements.rst')
-rw-r--r-- | docs/installation-instructions/requirements.rst | 31 |
1 files changed, 20 insertions, 11 deletions
diff --git a/docs/installation-instructions/requirements.rst b/docs/installation-instructions/requirements.rst index af03aac8..bf0a5f3d 100644 --- a/docs/installation-instructions/requirements.rst +++ b/docs/installation-instructions/requirements.rst @@ -12,12 +12,13 @@ The Jumphost requirements are outlined below: 3. libvirt virtualization support. -4. minimum 2 networks and maximum 6 networks, multiple NIC and/or VLAN combinations are supported. - This is virtualized for a VM deployment. +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 Colorado Apex RPMs and their dependencies. -6. 16 GB of RAM for a bare metal deployment, 64 GB of RAM for a VM deployment. +6. 16 GB of RAM for a bare metal deployment, 64 GB of RAM for a VM + deployment. Network Requirements -------------------- @@ -26,22 +27,29 @@ Network requirements include: 1. No DHCP or TFTP server running on networks used by OPNFV. -2. 2-6 separate networks with connectivity between Jumphost and nodes. +2. 1-5 separate networks with connectivity between Jumphost and nodes. - - Control Plane (Provisioning) / Private (API) Network + - Control Plane (Provisioning) - - Internal (Tenant Networking) Network + - Private Tenant-Networking Network* - External Network - Storage Network* -3. Lights out OOB network access from Jumphost with IPMI node enabled (bare metal deployment only). + - Internal API Network* -4. Admin or public network has Internet access, meaning a gateway and DNS availability. +3. Lights out OOB network access from Jumphost with IPMI node enabled + (bare metal deployment only). -| `*` *These networks can be combined with each other or all combined on the Control Plane network.* -| `*` *Non-External networks will be consolidated to the Control Plane network if not specifically configured.* +4. External network is a routable network from outside the cloud, + deployment. The External network is where public internet access would + reside if available. + +\* *These networks can be combined with each other or all combined on the + Control Plane network.* +\* *Non-External networks will be consolidated to the Control Plane network + if not specifically configured.* Bare Metal Node Requirements ---------------------------- @@ -63,4 +71,5 @@ In order to execute a deployment, one must gather the following information: 2. IPMI login information for the nodes (user/pass). -3. MAC address of Control Plane / Provisioning interfaces of the overcloud nodes. +3. MAC address of Control Plane / Provisioning interfaces of the overcloud + nodes. |