T-LAB Test Lab

This wiki page is used to maintain the latest information on what is currently being tested in T-LAB.

Compared to the Windriver Lab, T-LAB will touch upon multiple versions of ONAP depending on what the specific use case or requirements are, but will mostly work with the latest releases of ONAP components.

This lab will configure and instantiate different ONAP instances, deploying them in multiple manners such as:

HEAT-based approach: Template at https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/ONAP/onap_openstack.yaml;h=242d0dd2087053d1b8d7b3a692720f0951ef1ceb;hb=refs/heads/master & ENV file at https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/ONAP/onap_openstack.env;h=189dfd27838c752d89c999b33470cac96f0171b4;hb=refs/heads/master
OOM-based approach: There are two ways that are currently being devised
- Rancher-based approach: Uses a HEAT template which contains scripts that automate the instantiation of a Rancher/Multi-Node K8S deployment of a complete ONAP instance (Template at https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=deployment/heat/onap-oom/onap-oom.yaml;h=9cf44e41c5a5b11167af95b7d4968c821f85774f;hb=HEAD)
- TOSCA-based approach using Cloudify

General notes

The main idea of T-LAB is to be able to share as many resources as possible across use cases / scenarios. Nonetheless, there are some cases where T-LAB is hosting ONAP release testing (i.e. SB00/SB04 testing happening in an ONAP instance on T-LAB)
ONAP developers have root access to the VMs. SSH access requires a private key. Please contact the Integration Team to get your private key.