Lab infrastructure preparation: including hardware, VIMs, SD-WAN controller, PNFs / VNFs installation  

100%

T00001

 Install ONAP and health check 

100%

DMAAP-1180: Dmaap healthcheck failedClosed

DCAEGEN2-1459: DCAE health check failed Closed

OPTFRA-488: OOF pods don't start upClosed

SDC-2284: SDC Pod couldn't start upClosed

SDC-2286: When reinstall SDC in an existing ONAP , SDC couldn't detect Dmaap serviceClosed reinstall SDC need to reinstall dmaap

OOM-1843: Using the oom master branch, there is no aai chart ,this cause onap deploy failedClosed

redeploy SO and SDC with the master images 

T00002

SD-WAN Controllers Registration

100%

T00003

CCVPN Resource Template Import  

100%

T00004

CCVPN Service Design

100%

Service Design and distribute successfully

T00005

CCVPN Service Creation with one vpn and one site

100%

VFC-1375: fix docker-entrypoint.sh file of catalogClosed

UUI is updating parser address

UUI update parser address—— finished
The resource template exported from SDC lack of properties —— SDC bug fixed
The properties couldn't be declared as the list input in SDC —— SDC bug fixed

SO is debug the distributed model ——passed

SO testing is going on and ready to go to the SDNC -passed

The resource creation request has entered into SDNC, is debuging the sdnc resource creation

zte vCPE create via VF-C 100%

zte vCPE instantiate via VF-C 100%

SDNC-764: SDNC integration test failedClosed

SO-1393

SO-1393: Support the CCVPN ExtensionClosed

Waiting UUI to integrate with SO to do the e2e service creation.

T00006

CCVPN Service Creation with one vpn and multi-stie

100%

The service creation with one vpn and multiple site using postman has been finished
Today the service template redesigned, because UUI didn’t show the input properly. Now all the input can be showed properly in UUI with new service template.
Waiting UUI to integrate with SO to do the e2e service creation.

T00007

CCVPN Service Termination

T00008

CCVPN Service Change

T00009

Closed Loop in bandwidth adjustment

100%

SDNC-753: Could not install software in SDNC using apkClosed

POLICY-1774: Incorrect SDNC API called for CCVPN Bandwidth on demand policyClosed

update policy with the latest version 

Couldn't visit the holmes by msb, remove the duplicate register node from msb, it can work now.

Simulated the ves event, but event generated by holmes doesn’t have close loop control name, Vidya have figured out the problem and waiting Rama re-test tomorrow
homing issue is fixed now , but getting an issue with the controller and SDNC team is checking further.

Abbreviation

Full Name

PNF

Physical Network Function

NFV

Network Function Virtualization

NFVI

Network Function Virtualization Infrastructure

SOTN

Software Defined OTN

SD-WAN

Software Defined WAN

CPE

Customer Premise Equipment

GUI

Graphic User Interface

Module

Function

ONAP

The ONAP system for automation operation.

SD-WAN Controller

A third party controller for SD-WAN solution

Name

Responsibility

Account

Administrator

Responsible for system management; Personnel permission configuration; ONAP external system registration; Operational life cycle management

demo/demo123456!

Designer

Service template design

cs0008/demo123456!

Tester

Service template test

jm0007/demo123456!

Governor

Service template approve

gv0001/demo123456!

Operator

Service template distribution

op0001/demo123456!

Test No:

TEST-01

Project:

ONAP ESR

Sub Project:

3^rd SDNC controller registration

Objective:

support SD-WAN controller registered to ESR-SDNC

Pre-conditions:

1. 3rd SD-WAN controller have been installed

Test step:

1. Login to ONAP by administrator user.

2.  In the ONAP esr-sdnc UI, click Register button to Register SDNC information (IP, port, authentication information, etc.) of SDNC manufacturer, click next to fill in the next page, and finally click save button to complete registration.

Test Result:

1. We can find 3rd SD-WAN controller registered in ESR-SDNC portal.

Observation:

Test NO:

TEST-02

Project:

SDC Service Design

Sub Project:

Resource import for CCVPN

Objective:

Support to import the resources for CCVPN.

Operator:

Designer, Tester

Pre-conditions:

1. The resources node-types for CCVPN are ready.

Test step:

1. Designer login to SDC portal.

2. Import the resources to SDC?

Test Result:

1. The resources are imported to SDC.

Observation:

  We can find new resources for CCVPN in SDC portal

Test NO:

TEST-03

Project:

SDC Service Design

Sub-project:

Design CCVPN services

Objective:

SDC support to design CCVPN services with list input

Pre-condition:

1. All resources have been ready.

Test step:

1. Designer login to ONAP, click "Add Service" to create a service template.

2. Enter the service general parameters including name, category select `E2E service`, description, contact ID, Project code, etc. 

And click `Create` to create service template.

3. Enter `Composition` item, select resources needed for the service.

4. Enter ‘Properties Assignment’ item, configure the parameters of the resources.

And click ‘Create List Input’ button to declare properties as list input, then `Declare Properties as List Input' dialog will open.

5. Enter the list input parameters including name, new schema type, description to the dialog.

And click `Save` button to create list input.

6. Enter ‘TOSCA Artifacts’ item, click `Tosca Model` download icon to get the csar file.

Test result:

1. The services for CCVPN created successfully.

2. In the downloaded csar file, check the below points.

[service template yaml file's check point]

Declared properties as list input in design time is defined by multiple arguments, and created list input is defined in inputs.

    • Each declared property by `Create List Input' has a value with get_input function

    • get_input function takes three arguments like: [<list input name>, "INDEX", <property name>]

    • Created list input is defined in "inputs" section

[service template interface yaml file's check point]

New datatype is defined in service template interface yaml file.

Observation:

Test NO:

TEST-04

Project:

Service LCM

Sub Project:

Service instantiation for CCVPN service

Objective:

CCVPN service can be instantiated and data can be passed between CPEs

Pre-condition:

1. CCVPN service has been designed and distribute successful.

2. The 3rd SD-WAN controller have been installed and registered to ONAP.

Test step:

1. Administrator login to ONAP portal, select ‘UUI-biz’ to entry use case UI.

2. Administrator Click UUI item “Services”.

3. Click ‘create’ to create services.

4. On ‘Create Service’ dialog, select the service template and enter the inputs for the service.

5. Click ‘OK’ to instantiate a service.

Test Result:

1. CCVPN service can be created successfully from U-UI.

Observation:

1. Check the SD-WAN controller we can find the SD-WAN instance created.

2. For two CPEs, they can connect to each by internet.

3. The status of CCVPN service in U-UI is ‘alive’.

4. CCVPN service instance was stored in A&AI.

Test NO:

TEST-05

Project:

Service LCM

Sub-project:

Service termination for CCVPN service

Objective:

CCVPN service can be terminated.

Pre-condition:

1. CCVPN service has been created successfully.

Test step:

1. Administrator login to ONAP portal select ‘UUI-biz’ to entry use case UI.

2. Administrator click UUI item “Services”.

3. Select service and click ‘delete’ to delete services.

4. Click ‘OK’ to terminate a service.

Test Result:

1. CCVPN service can be deleted successfully.

Observation:

1. Check the SD-WAN controller we can find the SD-WAN instance deleted.

2. Check the AAI in ONAP, CCVPN service has been deleted.

3. U-UI shows that ‘Service delete successfully ‘

Test NO:

TEST-06

Project:

Service LCM

Sub-project:

Service change for CCVPN service

Objective:

A new site can be added to an existing CCVPN service

Pre-condition:

1.     CCVPN service has been created successfully.

Test step:

1.     Administrator login to ONAP portal select ‘UUI-biz’ to entry use case UI.

2.     Administrator click UUI item “Services”.

3.     Select service and click ‘add’ to add a site.

4.     Input the site parameters

5.     Click ‘OK’ to add the site

Test Result:

1.     Site can be added successfully

Observation:

1.     Check the SD-WAN controller we can find the SD-WAN instance includes the new site.

2.     Check the AAI in ONAP, new site resource instance has been related to the existing CCVPN service instance.

3.     UUI shows the new site in the existing service

Test NO:

TEST-07

Project:

Service LCM

Sub-project:

Service change for CCVPN service

Objective:

A site in CCVPN service can be deleted

Pre-condition:

1.     CCVPN service has been created successfully.

Test step:

1.     Administrator login to ONAP portal select ‘UUI-biz’ to entry use case UI.

2.     Administrator click UUI item “Services”.

3.     Select service and click ‘delete’ to delete the site.

4.     Click ‘OK’ to delete the site

Test Result:

1.     Site can be deleted successfully.

Observation:

1.     Check the SD-WAN controller we can find the site was not included in the SD-WAN instance

2.     Check the AAI in ONAP, the site resource instance has been disconnected with the CCVPN service instance.

3.     Deleted Site information disappear in UUI.

Test NO:

TEST-09

Project:

Closed Loop

Sub-project:

Closed Loop in bandwidth adjustment

Objective:

ONAP can receive the anomaly alarm, trigger related policy, and call SDN-C to change the bandwidth automatically.

Pre-condition:

1. All elements of SD-WAN network TOPO environment has been completed.

2. CCVPN services have been created and business is working fine.

Test step:

1. Interrupt the cross domain link in the CMCC side ONAP manually.

2.     Make an alarm(sound or crowd) at the edge site branch

3.     Anomaly alarm is reported to ONAP by the intelligent security system.

Test Result:

1. Closed-loop triggered automatically, bandwidth will be changed higher and will be changed to normal after an assigned timeslot.

Observation:

1. The real time video will be played more smoothly at the enterprise HQ after the bandwidth was changed to a high level.