Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

1.Introduction

This is the integration test cases for CCVPN-MDONS use case.

Test effort and official documentation is tracked and maintained through the following story in JIRA. 

2. Scope

The integration test case for MDONS use case, it includes third party controller registration, SDC design and service LCM.

3. Terms, definitions and abbreviations


Abbreviation

Full Name

PNF

Physical Network Function

DC

Domain Controller

OTN

Optical Transport Network

GUI

Graphic User Interface

UNIUser Network Interface (NI)
NNINetwork NI 
ENNIExternal Network NI 

4. Test Framework


Module introduction:

ONAP

The ONAP system for automation operation.

Domain Controller

A third party controller for L1/L0 network.


5. Test description

The test for ONAP to L1 choreography of the business management, business deployment environment adopting physical manual deployment patterns, ONAP not deploy network, only do L1/OTN service LCM  and L1 Node/PNF, Interface port/Pp-Interface automatically discover functions. The network elements of this test include 3rd domain controller and L1/L0 equipment.

5.1  Test Accounts

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!

6. ONAP External System Registration Test

6.1  Domain Controller Registration

Test No:

TEST-01

Project:

ONAP ESR

Sub Project:

3rd domain controller registration

Objective:

support domain controller registered to ESR-SDNC

Pre-conditions:

  1. 3rd domain 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 domain (VNC) information (IP, port, authentication information, etc.) of from manufacturer, click next to fill in the next page, and finally click save button to complete registration.


Test Result:

  1. We can find domain controller registered in ESR-SDNC portal.

Observation:

When domain controller registered to ONAP. Wait for minutes, DC will synchronize the network topology to ONAP.  Check the topology data of AAI.




7. SDC Service Design

7.1  MDONS resource design

Test NO:

TEST-02

Project:

SDC Service Design

Sub Project:

Resource import for MDONS

Objective:

Support to import the resources for MDONS.

Operator:

Designer, Tester

Pre-conditions:

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

Test step:

  1. Designer login to SDC portal.
  2. Import the resources to SDC :  UNI, ENNI, NNI

Test Result:

  1. The resources are imported to SDC.

 

Observation:

  We can find new resources for MDONS in SDC portal


7.2  MDONS Service Design

Test NO:

TEST-03

Project:

SDC Service Design

Sub-project:

Design MDONS services:  MDONS OTN Service

Objective:

SDC support to design MDONS OTN services

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 ‘L1-L3 Service’??description?contact ID?project code etc. click ‘Create” to create service template.

‘Saved successfully’ information will be shown.

3. Enter ‘Composition’ item?select resources needed for the service.

4. Enter ‘Properties Assignment’ item?config the parameters of the resources?click ‘Declare’ button to declare the parameters of resources as service inputs.

5. Click ‘submit for testing’? ‘Submitted for testing successfully’ will be shown.

6. Tester login to ONAP?click the service to test?and then click ‘start testing’ to test the service template. After test, click ‘accept’.

7. Governor login to ONAP to approve the service template.

8. Operator login to ONAP to distribute the service template.


Test result:

  1. The services for MDONS created successfully.
  2. MDONS services model/template distributed to A&AI and SO.

Observation:






8.Service LCM

8.1  L1/L0 TOPO Automatically synchronization.

Test NO:

TEST-04

Project:

Service LCM

Sub-project:

L1/L0 network topology synchronized to ONAP

Objective:

OTN network topology can be synchronized to ONAP,  saved  and mapped (TAPI, OpenRoadM) in A&AI.

Pre-condition:

  1. All OTN network PNFs/P-Interfaces are ready.
  2. DC controller is ready and the OTN/WDM links have been added to it.

Test steps:

  1. Administrator login to ONAP?click “AAI UI ->view & inspect”?to view the topology synchronized from 3rd domain controller.
  2. Check the nodes of A&AI that used to save topology information.

Test result:

  1. We can find the topology data in A&AI

Observation:



8.2  OTN cross-domain/cross-ONAP link (question) management

Test NO:

TEST-05

Project:

Service LCM

Sub-project:

L1/L0 network topology management

Objective:

UUI can support to view the topology of network and create cross-domain/cross-ONAP links.

Pre-condition:

  1. All OTN links are ready.
  2. 3rd domain controller is ready and the OTN /WDM links have been added to it.
  3. 3rd domain controller have been registered to ONAP ESR

Test steps:

  1. Administrator login to ONAP, click “UUI” to enter the use case UI.
  2. Click ‘Topology management’ to manage the topology of OTN network.
  3. Click ‘Add link’ to add cross-domain/cross-onap links (question).

Test result:

  1. We can find the topology data in UUI. To show the ONAP topologies.
  2. When we add the cross-domain link , a link will be shown between different domains.
  3. When we add the cross-ONAP link, a link with an ONAP icon will be shown in the portal.

Observation:


...

Test NO:

TEST-06

Project:

Service LCM

Sub Project:

Service instantiation for OTN services

Objective:

The OTN services can be instantiated.

Pre-condition:

  1. MDONS OTN service have been designed and distribute successful.
  2. The 3rd domain controllers have been installed and registered to ONAP.
  3. The topology of the network have been synchronized to ONAP and the links cross domain/cross ONAP have been created by UUI.

Test step:

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

2.Click UUI item “Services”?and select ‘Services’ Tab.

3. Select customer and service type

4. Click ‘create’ to create services.

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

6. Click ‘OK’ to instantiate a OTN service.



Test Result:

  1. All services can be created successfully.


Observation:

  1. Check the domain controller, we can find the domain OTN serivces created.
  2. Check the terminal points that connect to from UNI to UNI for OTN network, they can reach to each other (TBD)

It can connect to each other:

  1. For two UNIs, they can connect to each other through OTN connectivity (TBD)

...

Test NO:

TEST-07

Project:

Service LCM

Sub-project:

Service termination for OTN services

Objective:

The OTN services can be terminated.

Pre-condition:

  1. The OTN services have been created successfully.

Test step:

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

2. Click UUI item “Services”?and select ‘Services’ Tab.

3. Select customer and service type

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

5. Click ‘OK’ to terminate a service.

6. We need to delete the services.

Test Result:

  1. All service can be deleted successfully.


Observation:

  1. Check the domain controllers, we can find the services deleted.
  2. Check the AAI in two ONAPs,   the ONAP OTN service, all domain OTN services for CCVPN are deleted and corresponding resources are released.

9.  Use Case Alignment

PartnersUCVerified Components   VUC LeadersStatus
OrangeMDONSSOF
SwissComBBSSOF
HuaweiCCVPNF

 @Henry Yu 

 @ Gaurav


WinRiverIntegrationSOF @ Steven Gooch


10.  Issues Found

ComponentOwnerJira TicketNotes/Status
SOSeshu Kumar Mudiganti

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2827


SDNC


AAI


UUI


Viewtracker