...
- 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.
Integration
Testing activity: Hosts infrastructure support VMs like apt and docker caches
Owner: Gary Wu
Integration-Jenkins
Testing activity: This tenant is used for ONAP daily builds for OOM-based deployment of the Beijing release: https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/
Owner: Gary Wu
Integration-SB-00
Testing activity: OOM Pairwise Testing
Owner: Helen Chen Brian Freeman
Integration-SB-01
Testing activity: HEAT deployment for OOF HPA testing
Owner: Helen Chen Marcus Williams Alexander Vul
Integration-SB-02
Testing activity: 72 hour stability testing of HEAT Beijing installation
Owner: Gary Wu
Integration-SB-03
Testing activity: VoLTE use case on OOM
Owner: Yang Xu
Integration-SB-04
Testing activity: 72 hour stability testing of OOM Beijing installation
Owner: Helen Chen
Integration-SB-05
Testing activity: VoLTE Use Case Testing on HEAT
Owner: Yang Xu
Integration-SB-06
Testing activity: Beijing OOM-Based Pairwise Testing
Owner: Mike Elliott
Integration-SB-07
Testing activity: HEAT Pairwise Testing
Owner: Gary Wu Marco Platania Brian Freeman
Integration-SB-Stable
Testing activity: This tenant is used for ONAP daily builds for heat-based deployment of the Beijing release: https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-heat-deploy/
Owner: Gary Wu
ONAP-vCPE
Testing activity: Testing vCPE
Owner: Kang Xi, Brian Freeman, Helen Chen
CLI
Testing activity: CLI overall testing
- Access to T-LAB is defined by the specific type of access being looked for. Access to the T-LAB dashboard is limited unless there is a clear reason as to why such access is needed.
- The main mode to communicate with the T-LAB community is through http://onap-integration.eastus.cloudapp.azure.com:3000/channel/tlab-testing
Current T-LAB Tenants
ETE-OOM-Test
Testing activity: ETE ONAP Deployment Test using OOM/K8S approach, runs periodically for consistent deployment testing
ETE-HEAT-Test
Testing activity: ETE ONAP Deployment Test using HEAT approach, runs periodically for consistent deployment testing
ETE-Integration
Testing activity: Hosts infrastructure support VMs like apt and docker caches
EXTONAP_DEV
Testing activity: Deploy / Test multiple ONAP use cases with a single ONAP instance triggered by Jenkins
EXTONAP_K8S
Testing activity: Deploy / Test multiple ONAP use cases with a multi-node ONAP instance. This is mainly used to run scenarios outside of Integration Team's Resiliency / ONAP release testing
R-Control_Plane
Testing activity: Deploy / Test multiple ONAP use cases with a multi-node ONAP instance. This is mainly used to run scenarios that are part of Integration Team's Resiliency / ONAP release testingOwner: user-67d6f