This epic will encompass the work to be done within the ONAP External Community Sandbox. This sandbox will be used for ONAP projects being developed by ONAP community members.

The sandbox will be generally composed of two main environments:

• A replicated copy of a full ONAP instance (latest release) as it is deployed using the OOM approach in the Integration Team’s TLAB ETE Platform Testing. This instance is to be upgraded every one/two weeks to deploy the latest ONAP release available. Therefore, this instance can/should be shared by multiple parties for purposes that do not directly modify the ONAP instance’s state, such as the scenarios below:
  • Deploying/Testing VNFs/PNFs against one or more ONAP components
  • Test demos/use case scenarios
  • Demonstrate current ONAP capabilities (Portal Apps, how ONAP GUIs work, how ONAP API calls are used/work, etc.)

• A flexible Kubernetes Cluster (shared by multiple parties as well) to:
  • Quickly deploy single/multiple ONAP components for different scenarios
  • Idea is to have a stable Kubernetes cluster with flexible deployment options to rapidly test/tear-down ONAP component instances for quick testing/debugging scenarios

A TLAB toolchain will also form part of this environment to support an automated set of jenkins jobs to trigger re-deployment of the ONAP instance on a weekly basis.