...
# | 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 Azure |
| Distribtion
Instantiation
Control Loop
| 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 |
| https://jira.onap.org/browse/SDNC-1017 | https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vCPE.html | Yes | intention to contribute to usecase automation and providing fixes for any future issues/provide new functionalities in scripts as well as improve CI gating. As for the usecase architecture itself or integration lab deployments status reporting please ask Brian. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3 | vCPE with TOSCA | vCPE(tosca) with HPA - Integration test cases | CMCC / Intel |
| https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vCPE%20with%20Tosca%20VNF.html minor updates | Yes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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/latest/submodules/integration.git/docs/docs_5g_rtpm.html#docs-realtime-pm | Yes | DCAE | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 5 | 5G - PNF PnP
| 5G - PNF PnP - Integration Test Cases | Intel / Windriver |
| https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_5g_pnf_pnp.html#docs-5g-pnf-pnp minor updates | Already in CI gate | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 6 | 5G - Bulk PM "Data Plane" | 5G - Bulk PM - Test Status | Ericsson Lab |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 |
| Use case: https://docs.onap.org/en/dublin/submodules/integration.git/docs/docs_5G_oof_pci.html SON-Handler MS (DCAE): https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/services/son-handler/index.html Updates for Frankfurt submitted (INT-1466 and DCAEGEN2-2104) | Stretch goal, will be re-visited end of March | DCAE (SON-Handler MS), Policy, SDN-C, OOF | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 10 | E2E Network Slicing | Test Status | Windriver/CMCC |
| Use case documentation submitted (INT-1468). | Stretch goal, may not be possible within Frankfurt time frame | UUI, EXT-API, SO, OOF (Test only: SDC, A&AI, Poilcy) | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 11 | Scale Out | Scale Out - Integration Test Cases and Status | Intel / Windriver | Testing Status (Frankfurt Scaling)
| 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 12 | CCVPN-E LINE over OTN NNI | CCVPN Integration Test Cases | Huawei |
| https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_CCVPN.html#docs-ccvpn updates will be based on Frankfurt scope | SDNC AAI OOF UUI | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 12.1 | CCVPN - MDONS | MDONS Integration Test Case | Fujitsu/Orange |
| https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_CCVPN.html#docs-ccvpn updates will be based on Frankfurt scope | SO - C A&AI - C SDN-C - C UUI - C CCSDK-C SDC - TO ExtAPI - TO | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 | HPA vFW/vDNS | vFW/vDNS HPA Testing(Test Plan 1 inHPA & Cloud Agnostic Intent - R3 Test Plan) | Intel / Windriver |
| https://onap.readthedocs.io/en/elalto/submodules/integration.git/docs/docs_vfwHPA.html#docs-vfw-hpa | SO SDC VID OOF Policy SDNC AAI | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 | 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 |
| 1) Designing custom workflows with Workflow Designer – 100% 2) Distributing custom workflows to SO – Was 100% in Dublin Issues arose with SDC Distribution in El Alto and remain unresolved – 80% working now. However, SO does work properly with manual WF distribution and workaround notes are posted on the wiki 3) Deploying the custom workflow in SO – 100% 4) Sending workflow metadata to VID – 100% 5) Triggering custom workflow execution from VID – 100% 6) Executing custom workflows in SO – Execution mechanism 100%, Building Blocks – 60% (Had many issues with test environment & APPC blocking testing from Nov-Jan) 7) Pause for Manual Task – 100% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 15 | Change Management Frankfurt Extensions
| 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 the workflow | Intel / Windriver |
| El Alto doc good: https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vFWDT.html#docs-vfw-traffic but major updates needed (as the use cases evolved) Documentation change is in progress https://gerrit.onap.org/r/c/integration/+/102853 | No Not sure if full automation will be possible – depends on automation of APPC/CDT part. | Use case will be renamed and include upgrade | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 16 | PNF Software Upgrade
| Steps: 1) Execute custom PNF SW Upgrade WF from SO 2) SO send conventional LCM API to SDNC/CCSDK 3) Controller send ansible commands to AS 4) AS contact EM with ansible | Huawei |
| Documentation containing new scenarios will be upadted in R6.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 17 | Change Management - Schedule Optimization | Intel / Windriver |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 18 | BBS Broadband Service Use Case (Frankfurt) | BBS Integration Test Cases (Frankfurt) | BBS Swisscom Lab |
| Frankfurt is a maintenance release for BBS use case BBS Use Case Tracking (Frankfurt Release) Integration testing not started in BBS Swisscom Lab | Frankfurt doc: https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_BBS.html | 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 19 | VSP Compliance and Validation Check within SDC (Frankfurt) - Phase 2 | VSP Compliance Check within SDC - Integration Test Plan | Vodafone |
| https://onap-sdc.readthedocs.io/en/latest/consumedapis.html https://onap-doc.readthedocs.io/projects/onap-sdc/en/latest/externaltesting.html | No | SDC VTP | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 20 | K8S based Cloud Region Support - vFW Use case | Deploy vFW Helm Chart using Multicloud K8s Plugin in Kubernetes Cl
| intel / Windriver |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 | K8S based Cloud Region Support - EdgeXFoundry Use case | Deploy EdgeXFoundry Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud | Intel/ Windriver |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 | ORAN A1 Adapter Implemented in ONAP (SDNR) | A1 Adapter Test Cases | Intel/Windriver |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 23 | PNF Software Upgrade using direct Netconf/Yang interface with PNF | PNF software upgrade in R6 Frankfurt#-654105238 | Intel |
| Documentation needs to be updated with new use cases in Frankfurt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 24 | Enable PNF software version at onboarding | PNF software upgrade in R6 Frankfurt#-1811172036 | Ericsson Lab | André Schmid |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 25 | K8s CDS Support (vFW_CDS_CNF)
| TO BE DEFINED | Currently testing in internal lab. Tests in official integration lab not started yet. |
| https://gerrit.onap.org/r/#/c/integration/+/101900/4 - in review | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 26 | ETSI Alignment SO plugin to support SOL003 to connect to an external VNFM |
CSIT for ETSI package management is being tested We plan to complete the CSIT by RC0 completion
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 | Component/memory optimization: Ongoing Assessment | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 29 | S3P- Geo-Redundancy | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 | SOL 004 (VNF Package Security) | 5G - Preonboarding/Onboarding - Test Status | Ericsson, Intel / Windriver | Status of this item is embedded into & equal to status of “5G - Preonboarding/Onboarding - Test Status” | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 31 | xNF communication security enhancements. | xNF communication security enhancements - Tests Description and Status | Yes | DCAE | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 37 | PNF Software Upgrade
| PNF software upgrade in R6 Frankfurt | Huawei |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 38 | 5G - 5G NRM Network Resource Model (Configuration Mgmt) | 5G Network Resource Model (NRM) Configuration in R6 Frankfurt | Huawei |
| New documentation to be created, as it is a new use case for Frankfurt
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 39 | TOSCA Compliant Policy types | Pairwise Testing | Intel / Windriver |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 40 | Policy Update Notifications | Pairwise Testing | Intel / Windriver |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 41 | CLAMP Deployment of Policies to PDP Groups | Pairwise Testing | Intel / Windriver |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 42 | Integration of CDS as an Actor | TBD | Intel / Windriver |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 42 | Component Upgrades to the new Policy Lifecycle API | Pairwise Testing | Intel / Windriver |
|
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 43 | Configuration with NETCONF in Frankfurt/R6
| Detailed Steps carried out for performing E2E Testcases can be found at : E2E Integration Testing for NETCONF over TLS Configuration- Test Case | Ajay Deep Singh |
|
| Yes | AAF-Certservice SDNC Netconf-Pnp-Simulator | Currently Blocked on below issues:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 44 | E2E Automation vLB w/CDS Use Case (Frankfurt) NOTE: SO is using Config Assign & Config Deploy building blocks. SO Marco Instantiation using Controller Execution Building Block [new for Frankfurt] for vLB Instantiation will be a separate test case.[row below] | Steps: Design Time 1) CBA Package onboarding CDS 2) SDC VSP, VF, Service Creation and onbaording for vLB. Run Time: 1) SO send Marcro requst to SDNC GR-API 2) SDNC GR-API send request to CDS, Netbox, Naming for instantiation resource auto resolution 3) SO sends request to CDS for Config Assign. 4) SO sends request to Openstack for vLB Instantiation 5) SO send request to CDS for ConfigDeploy | Intel / Windriver |
| CDS, SDNC, SO, Policy, Naming MS, Netbox | SO issue with heat stack creation. Jira is open.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 45 | Steps: | Telstra |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
...