...
The lab specification section provides information on for recommended hardware and network requirementsconfiguration
Hardware
A lab compliant test-bed pod provides:
- One CentOS 7 jump server on which the installer runs
- You may select a A variety of deployment toolchains to deploy from the jump server.
- Minimal 5-8 compute / controller nodes depends on the use case
- A configured network topology allowing for LOM, Admin, Public, Private, and Storage Networks
- Remote access through VPN
Servers
CPU:
- Intel Xeon E5-2600v2 2658v3 Series or newer
Firmware:
- BIOS/EFI compatible for x86-family servers
...
- Disks: 2 x 1TB HDD + 1 x 100GB SSD (or greater capacity)
- The first HDD should be used for OS & additional software/tool installation
- The second HDD is configured for CEPH object storage
- The SSD should be used as the CEPH journal
- Virtual ISO boot capabilities or a separate PXE boot server (DHCP/tftp or Cobbler)
Memory:
- 188G 256GB RAM Minimum
Power Supply
Single power supply acceptable (redundant power not required/nice to have)is acceptable
Networking
Network Hardware
- 24 or 48 Port TOR Switch
- NICs - Combination of 1GE and 10GE based on network topology options (per server can be on-board or use PCI-e)
- Connectivity for each data/control network is through a separate NIC. This simplifies Switch Management however requires more NICs on the server and also more switch ports
- BMC (Baseboard Management Controller) for lights-out mangement network using IPMI (Intelligent Platform Management Interface)
...
- Option I: 4x1G Control, 2x10G Data, 48 Port Switch
- 1 x 1G for lights-out IPMI Management
- 1 x 1G for Admin/PXE boot
- 1 x 1G for control-plane connectivity
- 1 x 1G for storage
- 2 x 10G for data network (redundancy, NIC bonding, High bandwidth testing)
- Option II: 1x1G Control, 2x 10G Data, 24 Port Switch
- Connectivity to networks is through VLANs on the Control NIC
- Data NIC used for VNF traffic and storage traffic segmented through VLANs
- Option III: 2x1G Control, 2x10G Data, 2x10G Storage, 24 Port Switch
- Data NIC used for VNF traffic
- Storage NIC used for control plane and Storage segmented through VLANs (separate host traffic from VNF)
- 1 x 1G for lights-out IPMI mangement
- 1 x 1G for Admin/PXE boot
- 2 x 10G for control-plane connectivity/storage
- 2 x 10G for data network
...
- Subnet, VLANs (may be constrained by existing lab setups or rules)
- IPs
- Types of NW - lights-outIPMI, public, private, admin, storage
- May be special NW requirements for performance related projects
- Default gateways
Remote Management
...
A Pod Example for VoLTE use case:
| Hostname | CPU | Memory | Storage | ipmiIPMI | Admin/PXE | Private | Public | Storage | 40GbE10GbE: NIC#, IP, MAC, VLAN, IP, Network | 10GbE: NIC#, IP, MAC, VLAN, Network | jumpserver | Network | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| jumpserver | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 188G256G | 1.7T2T | Mac 88:cf:98:db:ad:fb IP 172.30.8.64root/Onap12#$ username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | p1p1:Mac:88:cf:98:e9:9a:bd,VLAN 31, p1p2:Mac:88:cf:98:e9:9a:be,VLAN 31, | p4p1:Mac:88:cf:98:61:66:e2, IP:192.168.30.2 p4p2:Mac:88:cf:98:61:66:e3,p4p1: MAC,IP p4p2: MAC,IP | ||||
| Host1 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 188G256G | 1.7T2T | Mac 88:cf:98:db:ad:db IP172.30.8.10 root/Onap12#$ | eth0:Mac:88:cf:98:e9:9a:99,VLAN 31, eth3:Mac:88:cf:98:e9:9a:9a,VLAN 31, | eth1:Mac:88:cf:98:83:31:d7 IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac:88:cf:98:83:31:d8,,IP | |||
| Host2 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 188G256G | 1.7T2T | Mac 88:cf:98:db:ad:0b IP 172.30.8.11 root/Onap12#$ | eth0:Mac:88:cf:98:e9:9a:c3,VLAN 31, eth3:Mac:88:cf:98:e9:9a:c4,VLAN 31, | eth1:Mac:88:cf:98:61:67:0a, IP eth2:Mac:88:cf:98:61:66:0b IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac,IP | |||
| Host3 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 188G256G | 1.7T2T | Mac 88:cf:98:db:ad:dd IP 172.30.8.12 root/Onap12#$ | eth0:Mac:88:cf:98:e9:9a:b3,VLAN 31, eth3:Mac:88:cf:98:e9:9a:b4,VLAN 31, | eth1:Mac:88:cf:98:61:66:d8, IP eth2:Mac:88:cf:98:61:66:d9 | Host4 | IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac,IP | |
| Host4 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 188G256G | 1.7T2T | Mac 88:cf:98:db:b1:d7 IP 172.30.8.13 root/Onap12#$ | eth0:Mac:88:cf:98:e9:9a:9b,VLAN 31, eth3:Mac:88:cf:98:e9:9a:9c,VLAN 31, | eth1:Mac:88:cf:98:83:30:b3, IP peth2:Mac:88:cf:98:83:30:b4, | Host5 IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac,IP | ||
| Host5 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 256G | 2T | Mac IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac,IP | |||||
| Host6 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 256G | 2T | Mac IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac,IP | |||||
| Host7 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 256G | 2T | Mac IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac,IP | |||||
| Host8 | Intel(R) Xeon(R) CPU E5-2658A V3 @ 2.20GHz | 188G | 1.7T | Mac 88:cf:98:db:ad:39 IP 172.30.8.14 root/Onap12#$ | eth0:Mac:88:cf:98:e9:9a:af,VLAN 31, eth3:Mac:88:cf:98:e9:9a:b0,VLAN 31, | eth1:Mac:88:cf:98:61:66:da | 256G | 2T | Mac IP username/passwd | Port Mac IP | Port Mac IP | Port Mac IP | Port Mac IP | eth1:Mac,IP eth2:Mac:88:cf:98:61:66:db,IP |
The network diagram for the above pod:
...
| Code Block |
|---|
IPMI/Lights+out management Admin Private Public Storage
PXE
vlan 300
172.30.8.64/26 192.168.1.0/24 +
+ + 192.168.0.0/24| |
| | + + |
| | | 172.30.10.0/24 |
| +-----------------+ | | + |
| | | enp6 | | | |
+--------+ Jumpserver | 192.168.1.66 | | | |
| | CentOS 7 +-----------------------------+ | | |
| | | | | | |
| | | enp7 | | | |
| | | 192.168.0.66 | | | |
| | user/pass +---------------------------------------+ | |
| | | | | | |
| | | enp8 | | | |
| | | 172.30.10.72 | | | |
| | +-------------------------------------------------+ |
| | | | | | |
| | | enp9 | | | |
| | | | | | |
| | +----------------------------------------------------------+
| | | | | | |
| +-----------------+ | | | |
| | | | |
| | | | |
| | | | |
| +----------------+ | | | |
| | 1 | | | | |
+-------+ +--------------+-+ | | | |
| | | 2 | | | | |
| | | +--------------+-+ | | | |
| | | | 3 | | | | |
| | | | +--------------+-+ | | | |
| | | | | ... 4 | | | | |
| +-+ | | +--------------+-+ | | | |
| | | | | 58 +-----------------------+ | | |
| +-+ | | nodes for | | | | |
| | | | deploying +---------------------------------+ | |
| +-+ | ONAP | | | | |
| | | +-------------------------------------------+ |
| +-+ | | | | |
| | +----------------------------------------------------+
| +----------------+ | | | |
| | | | |
| | | | |
| + + + +
|
...