Color Guide
ONLY Completed items should be green.
COMPLETED
PROGRESSING >= 90%
PROGRESSING <90%
# | Use CaseFunctional Requirement Nonfunctional Requirement | Test Cases | Lab | IntegrationTest Lead | Status | Details | Doc status | CI integration* | Components involved | Comments |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Model Driven Control Loop Design | (vDNS is part of scale out use case below #10) | Intel / Windriver | https://onap.readthedocs.io/en/elalto/submodules/integration.git/docs/docs_vfw.html#docs-vfw minor updates | ? | SDC Dmaap SDNC SO AAI Policy ... | ||||
| 2 | Use Case: Residential Broadband vCPE (Approved) | vCPE Integration Test Case | Intel / Windriver | |||||||
| 3 | vCPE with TOSCA | vCPE(tosca) with HPA - Integration test cases | Intel / Windriver | |||||||
| 4 | 5G - Realtime PM and High Volume Stream Data Collection | 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Cases | Intel / Windriver | https://onap.readthedocs.io/en/elalto/submodules/integration.git/docs/docs_5g_rtpm.html#docs-realtime-pm | Partially integrate Tests are already automated on http://onapci.org/jenkins/ | |||||
| 5 | 5G - PNF PnP | 5G - PNF PnP - Integration Test Cases | Intel / Windriver | https://docs.onap.org/en/elalto/submodules/integration.git/docs/docs_5g_pnf_pnp.html#docs-5g-pnf-pnp minor updates | Already in CI gate | |||||
| 6 | 5G - Bulk PM | 5G - Bulk PM - Test Status | Intel / Windriver SB-02 | |||||||
| 7 | 5G - Configuration with NETCONF | 5G - PNF Configuration via Netconf - Test Status | Intel/ Windriver | Minor updates | Yes | |||||
| 8 | 5G - Preonboarding/Onboarding - Test Status | Intel / Windriver | PNF Preonboarding (VNF SDK): PNF Onboarding (SDC): | |||||||
| 9 | 5G - OOF SON: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt | Integration Test | OWL / Windriver | Reshmasree c | minor updates | ? | ||||
| 10 | Scale Out | Scale Out - Integration Test Cases and Status | Intel / Windriver | minor updates | APPC VID DCAE SO Policy ... | Some new platform capabilities have been developed in SO and CDS. If they can’t be used for some reason, we’ll fall back to using the current process. | ||||
| 11 | CCVPN | CCVPN Integration Test Cases | CMCC | |||||||
| 12 | HPA vFW/vDNS | vFW/vDNS HPA Testing(Test Plan 1 inHPA & Cloud Agnostic Intent - R3 Test Plan) | Intel / Windriver | |||||||
| 13 | Change Management - Flexible Designer & Orchestrator | Steps: 1) Designing custom workflows with Workflow Designer 2) Distributing custom workflows to SO 3) Deploying the custom workflow in SO 4) Sending workflow metadata to VID 5) Triggering custom workflow execution from VID 6) Executing custom workflows in SO | Intel / Windriver | |||||||
| 14 | Steps: 1) Instantiation of vFWDT 2) Configuration of OOF Policies for vFWDT 3) Execution of OSDF/HAS requests for data collection 4) Configuration of VNF profiles in CDT 5) Configuration of Ansible Server 6) Execution of TD workflow | Intel / Windriver | El Alto doc good: https://docs.onap.org/en/elalto/submodules/integration.git/docs/docs_vFWDT.html#docs-vfw-traffic but major updates needed (as the use cases evolved) | No Not sure if full automation will be possible – depends on automation of APPC/CDT part. | Use case will be renamed and include upgrade | |||||
| 15 | Change Management - 5G PNG Software Upgrade | Change Management - 5G PNF Software Upgrade Integration Test Status | Intel / Windriver | |||||||
| 16 | Change Management - Schedule Optimization | Intel / Windriver | ||||||||
| 17 | BBS Broadband Service Use Case (Dublin) | BBS Use Case Tracking (Dublin Release)#Testing | BBS Swisscom Lab | frankfurt is a maintenance release | No, planned for future releases | we need to find a solution to emulate 3rd party controllers first. Our use case relies on physical equipment and external controllers and we can only test it in the Swisscom lab at the moment. We may have a second lab with the required equipment in UNH-IOL, but it is not confirmed yet. | ||||
| 18 | VSP Compliance Check within SDC (Dublin) - Phase 1 | VSP Compliance Check within SDC - Integration Test Plan | Vodafone | wiki only? | No | |||||
| 19 | K8S based Cloud Region Support - vFW Use case | Deploy vFW Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud | intel / Windriver | |||||||
| 20 | K8S based Cloud Region Support - EdgeXFoundry Use case | Deploy EdgeXFoundry Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud | Intel/ Windriver | |||||||
| 24 | ETSI Alignment SO plugin to support SOL003 to connect to an external VNFM | |||||||||
| 27 | Component/memory optimization: Ongoing Assessment | |||||||||
| 29 | S3P- Geo-Redundancy | |||||||||
| 30 | SOL 004 (VNF Package Security) | 5G - Preonboarding/Onboarding - Test Status | Ericsson, Intel / Windriver | |||||||
| 31 | xNF communication security enhancements. | xNF communication security enhancements - Tests Description and Status | ||||||||
| 32 | Locale/Internationalization language support | |||||||||
| 33 | ||||||||||
| 34 | HPA vIPsec | vIPsec HPA testing | Intel / Windriver | |||||||
| 35 | Health Checks for PODS | Percentage coverage of Health Checks for Running PODS | Integration | |||||||
| 36 | New Installation Tests in 4 labs | Intel/Windriver | ||||||||
| Orange (Rocky) | Morgan Richomme | |||||||||
| Ericsson Lab (Rocky) | ||||||||||
| DT | ||||||||||
| Robot Keyword Testing | ||||||||||
| init_robot | ||||||||||
| init | ||||||||||
| health | ||||||||||
| eteHelm-k8.sh | ||||||||||
| healthdist | ||||||||||
| instantiateVFWCL | ||||||||||
| vfwclosedloop <png_ip> | ||||||||||
| instantiateVFWDT | ||||||||||
| distributeVCPEResCust | ||||||||||
| sdc-dcae-d | ||||||||||
| vcpe.py | ||||||||||
| postinstall | ||||||||||
| 72 Hour Stability Run | onboard/instantiate | |||||||||
| closedloop | ||||||||||
HTTP Certificate Expiry Test (verify_cert.sh) | clamp 3/2020 dmaap 3/2020 | |||||||||
DCAEGEN2-1539 - Getting issue details... STATUS
*: CI integration: the goal is to introduce the use case in CI daily chains for Frankfurt. Ths table could be completed with a CI dashboard where the use cases will be run every day.
As it should be runnable in any lab, some constraints need to be considered:
- no proprietary VNFs
- use cases must be self-content , third party equiments may not be present in all labs.
- infrastructure setup/teardown shall be clear: the use case must be runnable from a clean ONAP installation. These resources must be cleaned at the end of the test ,
- results shall be pushed to a common DB. It is recommended ot use xtesting to run the tests (robotframework, python, bash, unit test drivers)