From f479b77c4f7c0d11196e3902bb7e60ff8e34a1fe Mon Sep 17 00:00:00 2001 From: ChristopherPrice Date: Tue, 12 Jan 2016 03:01:18 +0100 Subject: Restructured the installation-instruction file into indexed sub files Created a section based structure for the installation-instruction. It should show on the html artifact as a structured web page. We may want to move some sections to other directories to incorporate them into the release configguide. Left that for step 2... Change-Id: I4e2b4f398cbb0f4203166af68520ce4ecd82a328 Signed-off-by: ChristopherPrice --- docs/installation-instructions/requirements.rst | 66 +++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 docs/installation-instructions/requirements.rst (limited to 'docs/installation-instructions/requirements.rst') diff --git a/docs/installation-instructions/requirements.rst b/docs/installation-instructions/requirements.rst new file mode 100644 index 00000000..46dca2a0 --- /dev/null +++ b/docs/installation-instructions/requirements.rst @@ -0,0 +1,66 @@ +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 2 networks and maximum 6 networks, multiple NIC and/or VLAN combinations are supported. + This is virtualized for a VM deployment. + +5. The Bramaputra Apex RPM. + +6. 16 GB of RAM for a bare metal deployment, 56 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. 2-6 separate networks with connectivity between Jumphost and nodes. + + - Control Plane Network (Provisioning) + + - Private / Internal Network* + + - External Network + + - Storage Network* + +3. Lights out OOB network access from Jumphost with IPMI node enabled (bare metal deployment only). + +4. Admin or public network has Internet access, meaning a gateway and DNS availability. + +| `*` *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 +---------------------------- + +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. -- cgit 1.2.3-korg