8. Setup Requirements¶
8.1. Jumphost Requirements¶
The Jumphost requirements are outlined below:
- CentOS 7 (from ISO or self-installed).
- Root access.
- libvirt virtualization support.
- minimum 1 networks and maximum 5 networks, multiple NIC and/or VLAN combinations are supported. This is virtualized for a VM deployment.
- The Colorado Apex RPMs and their dependencies.
- 16 GB of RAM for a bare metal deployment, 64 GB of RAM for a VM deployment.
8.2. Network Requirements¶
Network requirements include:
- No DHCP or TFTP server running on networks used by OPNFV.
- 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 **)
- Lights out OOB network access from Jumphost with IPMI node enabled (bare metal deployment only).
- 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.*
8.3. Bare Metal Node Requirements¶
Bare metal nodes require:
- IPMI enabled on OOB interface for power control.
- BIOS boot priority should be PXE first then local hard disk.
- BIOS PXE interface should include Control Plane network mentioned above.
8.4. Execution Requirements (Bare Metal Only)¶
In order to execute a deployment, one must gather the following information:
- IPMI IP addresses for the nodes.
- IPMI login information for the nodes (user/pass).
- MAC address of Control Plane / Provisioning interfaces of the overcloud nodes.