We use the similar lab infrastructure recommended by OPNFV project.
...
- Option I: 4x1G Control, 2x10G Data, 48 Port Switch
- 1 x 1G for 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)
- Option III: 2x1G Control, 1x10G Data(redundancy nice to have), 1x10G Control or Storage(if needed, redundancy nice to have), 48 Port Switch
- Data NIC used for VNF traffic
- 1 x 1G for IPMI mangement
- 1 x 1G for Admin/PXE boot
- 1 x 10G for control-plane connectivity/storage(if needed, control plane and storage segmented through VLANs)
- 1 x 10G for data network
...
- Out-of-band management for power on/off/reset and bare-metal provisioning
- Access to server is through a lights-out-management tool and/or a serial console
- Refer to applicable light-out management information from server manufacturer, such as ...
POD
In the following table, we define 3 types of Pod based on the resource usage assumption and each POD recommended configuration is described in the following. Please note in lab and real deployment scenarios, resource can be over subscribed depending on workload. Also we assume that ONAP platform will be deployed in a separate pod from VNFs.
...