diff options
author | 2016-08-19 16:39:06 +0200 | |
---|---|---|
committer | 2016-08-19 16:39:06 +0200 | |
commit | 1e4742787c6c45b44f5e49de03ec8b1b1075c04e (patch) | |
tree | a58b62aaf2637676066e26517ecda0e1b07f6f23 /docs/installation-instructions/requirements.rst | |
parent | 4862f3b57479d64c5408268cc2086b53e4e97b81 (diff) |
Renamed install instructions folder according to docs directive
Change-Id: I8970be0bcbed501e43d6fb76af1278881274f69a
Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
Diffstat (limited to 'docs/installation-instructions/requirements.rst')
-rw-r--r-- | docs/installation-instructions/requirements.rst | 79 |
1 files changed, 0 insertions, 79 deletions
diff --git a/docs/installation-instructions/requirements.rst b/docs/installation-instructions/requirements.rst deleted file mode 100644 index d54d584b..00000000 --- a/docs/installation-instructions/requirements.rst +++ /dev/null @@ -1,79 +0,0 @@ -Setup Requirements -================== - -Jumphost Requirements ---------------------- - -The Jumphost requirements are outlined below: - -1. CentOS 7 (from ISO or self-installed). - -2. Root access. - -3. libvirt virtualization support. - -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. - -Network Requirements --------------------- - -Network requirements include: - -1. No DHCP or TFTP server running on networks used by OPNFV. - -2. 1-5 separate networks with connectivity between Jumphost and nodes. - - - Control Plane (Provisioning) - - - Private Tenant-Networking Network* - - - External Network - - - Storage Network* - - - Internal API Network* (required for IPv6 \*\*) - -3. Lights out OOB network access from Jumphost with IPMI node enabled - (bare metal deployment only). - -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.* -\*\* *Internal API network, by default, is collapsed with provisioning in IPv4 - deployments, this is not possible with the current lack of PXE boot - support and therefore the API network is required to be its own - network in an IPv6 deployment.* - -Bare Metal Node Requirements ----------------------------- - -Bare metal nodes require: - -1. IPMI enabled on OOB interface for power control. - -2. BIOS boot priority should be PXE first then local hard disk. - -3. BIOS PXE interface should include Control Plane network mentioned above. - -Execution Requirements (Bare Metal Only) ----------------------------------------- - -In order to execute a deployment, one must gather the following information: - -1. IPMI IP addresses for the nodes. - -2. IPMI login information for the nodes (user/pass). - -3. MAC address of Control Plane / Provisioning interfaces of the overcloud - nodes. |