Page Comparison

Color Guide

ONLY Completed items should be green. 

...

Test results:

Test Status of Enhancement on PNF S/W Upgrade with EM with Ansible

David Perez Caparros

Swisscom lab is closed. 

Update (May 26): running BBS integration test cases in UNH-IOL. In progress

Frankfurt doc: https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_BBS.html 

No, planned for future releases

https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/VSP+Compliance+and+Validation+Check+within+SDC+%28Frankfurt%29+-+Phase+2#VSPComplianceandValidationCheckwithinSDC(Frankfurt)Phase2-VSPComplianceCheckwithinSDC-IntegrationTestPlan

https://onap-sdc.readthedocs.io/en/latest/consumedapis.html

https://onap-doc.readthedocs.io/projects/onap-sdc/en/latest/externaltesting.html

SDC

VTP

After above are fixed, a retest can be made to verify.

Calling this done based on testing done with fixes/workarounds of known issues.

1. Installation of KUD k8s environment
2. Configuration of k8s tenant in AAI
3. Configuration of kud/k8s region in multicloud
4. Configuration of kud/k8s region in SO
5. Modification of SO BPMN configuration
6. Onboarding of artifacts to SDC
7. Design and distribution of service in SDC
8. Instantiation of Service with SO

Updated 11.06

Updated 23.06 - completed

07.05: Currently usecase has been verified to work both in internal and windriver lab with workaround. Ongoing tests regarding verifying fixes provided under blocker jiras.

08.05: Removed blocker jiras that were tested for being corrected.

14.05: Updating fix brought under MSB-467 to fully cover issue, as previous patch was found incomplete

ETSI Alignment

SO plugin to support SOL003 to connect to an external VNFM and ETSI package management

1. SDC users onboards SOL004 VNF package to SDC
2. SDC users distributes SOL004 VNF package to ONAP SO
3. SO receives the SOL004 VNF packages from SDC
4. ONAP SO triggers ETSI Catalog Manager to store the original vendor SOL004 VNF package
5. ETSI Catalog Manager gets the SOL004 VNF package from SDC and stores it to its database
6. ETSI Catalog Manager sends a package notification to SOL003 Adapter
7. SOL004 Adapter forwards the notification to SVNFM (Simulator)
8. SVNFM queries SOL003 Adapter for the SOL004 VNF package
9. SOL003 Adapter queries ETSI Catalog Manager for the SOL004 VNF package 
10. ETSI Catalog Manager returns the SOL004 VNF package to the SOL003 Adapter 
11. SOL003 Adapter returns the SOL004 VNF package to the SVNFM

Merged with record 8

Tes Cases passed on RC0. Test status: xNF communication security enhancements - Tests Description and Status

Yes

CSIT's

PNF Software Upgrade

• PNF / PNF Software Upgrade with EM with Netconf

Test results:

Test Status of PNF S/W Upgrade with EM with Netconf/Yang interface

Policy - CDS integration test was successfully completed in SB01 lab for vFW use case.

CLAMP - Policy integration test was successfully completed in SB01 lab for vFW use case.

Policy Framework

CDS

A&AI

CLAMP

AAF-Certservice,  SDNC,

Netconf-Pnp-Simulator

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

Requires workaround or merge in order for use case to work out of the box in Frankfurt release. 

3rd Party Operational Domain Manager

Integration work will be part of OOF / SON / PCI Use Case.

will have the same integration status as that use case.

E2E Automation vLB w/CDS Use Case (Frankfurt)

SO Marco Instantiation using Controller Execution Building Block [new for Frankfurt] for vLB Instantiation.

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 ControllerExecutionBB with scope of vnf and action of config-assign.

4) SO sends request to Openstack for vLB Instantiation 

5) SO send request to CDS for ControllerExecutionBB with scope of vnf and action of config-deploy.

Requires workaround or merge in order for use case to work out of the box in Frankfurt release. 

CLOSED TICKETS:

• Naming MS Changes based on new policy api:  (Biju)
• https://gerrit.onap.org/r/c/oom/+/107423

• Naming MS Changes based on new policy api:  (Biju)
• https://gerrit.onap.org/r/c/oom/+/107425

• SO Patch: fixes for scale out:  (Janani)
• https://gerrit.onap.org/r/c/so/+/107752

vCPE Integration Test Case

During May 4 PTL meeting, Morgan Richomme reports that this issue may need to be de-scoped since there are no resources available for integration test.

Not restested as part of Frankfurt release

5G - PNF Configuration via Netconf - Test Status

Intel/

Windriver

https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_5G_Configuration_over_NETCONF.html#docs-5g-configuration-over-netconf

Minor updates

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

Not restested as part of Frankfurt release

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%

Not restested as part of Frankfurt release

Recommended for a GO

#1 Can you please provide your tests results?

#2 Any automated tests?

Recommended for a GO

#1 Can you please provide your tests results?

#2 Any automated tests?

Testing completed via POLICY/DCAE pairwise testing completed by RC0.

No automated tests.

Recommended for a GO

#1 Can you please provide your tests results?

#2 Any automated tests?

Testing completed via CLAMP/Policy pairwise testing over the time period between M4 and RC1 in SB01/SB00.

Additional testing is covered via the vFW, Scale Out, vFW CDS use cases.

No automated tests as this is done manually via the CLAMP GUI.

Recommended for a GO

#1 Can you please provide your tests results?

#2 Any automated tests?

Policy/CCSDK testing was successfully completed via pairwise testing in SB01 by RC0.

Policy/OOF testing successfully completed by RC1 and was done in SB01.

No automated tests.

instantiateVFWCLGRA

HTTP Certificate Expiry Test

(verify_cert.sh)

clamp 3/2020

dmaap 3/2020

Tobe integrated in gate, raise an error in CI when 1 of the certificates is about to expire (in 2 weeks?)