The section provides information for hardware and network configuration. ONAP Open Labs are collections of dedicated hardware, generally partitioned into pods with servers. Pods can be used for different testings like development, CI/CD, ONAP platform testing, or E2E testing. The minimal requirements for each pod are defined in the following.
A lab compliant pod provides:
In the following table, we define 3 types of pod based on the resource usage assumption. 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.
Type of Pod | Compute Nodes | Number of Control Nodes Vanilla OpenStack / Titanium Cloud | |||
Total Memory(GB) | Total VCPU | Total Storage | Number of Compute Nodes | ||
Large | 600GB | 120 | 4TB | >=2 | 3 / 2 |
Medium | 200GB | 80 | 2TB | >=2 | 3 / 2 |
Small | 40GB | 24 | 1TB | >=1 | 1 / can support AIO (all in one) i.e. one node for controller, compute, and storage functions. |
In addition, you may need a provisioning server to help install and access a server pod.
A recommended node (server) configuration is as following:
Network Hardware
Basic requirements
Firewall rules accommodate
Internet access
Internet available for some software online installation and update
ONAP itself will need a medium sized server pod.
Use Cases | VNFs | Deployment Topology | Server Pod Number | Network Hardware | Software |
---|---|---|---|---|---|
Development or vFW/vDNS demo apps | Open sourced vFW/vDNS | 1 (Small) | TOR | Cloud OS | |
vCPE | vCPE | 2 (Medium) | WAN/SPTN Router (2) DC Gateway (2) TOR (n) ThinCPE (1) | Cloud OS (for Edge and Core) WAN/SPTN Controller DC Controller Specific VNFM & EMS | |
VoLTE | vIMS/vEPC | 2 (Large) | WAN/SPTN Router (2) DC Gateway (2) TOR (n) Wireless Access Point (2) VoLTE Terminal Devices (2) | Cloud OS (for Edge and Core) WAN/SPTN Controller DC Controller Specific VNFM & EMS |