We use the similar lab infrastructure recommended by OPNFV project. 

ONAP Lab Specification

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, E2E use case integration testing, Community demo, or interoperation testing with 3rd part productions. Each lab can have 1~4 PODs depending on test cases.

The lab specification section provides information for recommended hardware and network configuration.

Overview

A ONAP lab compliant test-bed provides:

• One CentOS 7 jump server on which the installer runs

• More then one POD should be delivered depends on the usage scenarios.

• A configured network topology allowing for LOM(Lights-out Management), Admin, Public, Private, and/or Storage Networks if needed.

• Remote access through VPN or other approach provided by individual labs

• Security through a firewall

Hardware

Servers 

Network Hardware

• TOR Switch

• Router

• others

Networking

Open

Remote Management

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. 

As an example, taking the above large pod as requirement, we can build a hypothetical pod with servers listed in the following table: