You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 12
Next »
1.Introduction
This is the integration test cases for CCVPN use case.
2. Scope
The integration test case for CCVPN use case, it include third party system registration, SDC design, service LCM, closed loop.
3. Terms, definitions and abbreviations
Abbreviation | Full Name |
PNF | Physical Network Function |
NFV | Network Function Virtualization |
NFVI | Network Function Virtualization Infrastructure |
SOTN | Software Defined OTN |
CPE | Customer Premise Equipment |
GUI | Graphic User Interface |
4. Test Framework
![](/download/attachments/38111461/image2018-7-23_10-43-39.png?version=1&modificationDate=1532313822000&api=v2)
Module introduction:
Module | Function |
ONAP | The ONAP system for automation operation. |
SOTN Controller | A third party controller for OTN network. |
SD-WAN Controller | A third party controller for SD-WAN solution |
5. Test description
The test for ONAP to SOTN choreography of the business management, business deployment environment adopting physical manual deployment patterns, ONAP not deploy work, only do business configuration and OTN PNF SOTN automatically discover functions. The network elements of this test include CPE, 3rd SOTN controller and OTN 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 SOTN Controller Registration
Test No: | TEST-01 |
Project: | ONAP ESR |
Sub Project: | 3rd SDNC controller registration |
Objective: | support SOTN controller registered to ESR-SDNC |
Pre-conditions: | - 3rd SOTN Controller have been installed
|
Test step: - Login to ONAP by administrator user.
- 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: - We can find SOTN controller registered in ESR-SDNC portal.
|
Observation: When SOTN controller registered to ONAP. Wait for minutes, SDNC will synchronize the network topology to ONAP. Please check the topology data of AAI.
|
6.2 SD-WAN Controller Registration
Test No: | TEST-02 |
Project: | ONAP ESR |
Sub Project: | 3rd SDNC controller registration |
Objective: | support SD-WAN controller registered to ESR-SDNC |
Pre-conditions: | 1. 3rd SD-WAN controller have been installed |
Test step: - Login to ONAP by administrator user.
- 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: - We can find 3rd SD-WAN controller registered in ESR-SDNC portal.
|
Observation:
|
7. SDC Service Design
7.1 CCVPN resource design
Test NO: | TEST-03 |
Project: | SDC Service Design |
Sub Project: | Resource import for CCVPN |
Objective: | Support to import the resources for CCVPN. |
Operator: | Designer, Tester |
Pre-conditions: | - The resources node-types for CCVPN are ready.
|
Test step: - Designer login to SDC portal.
- Import the resources to SDC?
|
Test Result: - The resources are imported to SDC.
|
Observation: We can find new resources for CCVPN in SDC portal |
7.2 CCVPN Service Design
Test NO: | TEST-04 |
Project: | SDC Service Design |
Sub-project: | Design CCVPN services: SOTN VPN Infra Service?Site Enterprise Service?Site DC Service?SDWAN VPN Infra |
Objective: | SDC support to design CCVPN services |
Pre-condition: | - All resources have been ready.
|
Test step: - Designer login to ONAP?click “add service” to create a service template?
- Enter the service general parameters?including name?category?select ‘E2E service’??description?contact ID?project code etc. click ‘Create” to create service template.
‘Saved successfully’ information will be shown.
- Enter ‘Composition’ item?select resources needed for the service.
- Enter ‘Properties Assignment’ item?config the parameters of the resources?click ‘Declare’ button to declare the parameters of resources as service inputs.
- Click ‘submit for testing’? ‘Submitted for testing successfully’ will be shown.
- Tester login to ONAP?click the service to test?and then click ‘start testing’ to test the service template. After test, click ‘accept’.
- Governor login to ONAP to approve the service template.
- Operator login to ONAP to distribute the service template.
|
Test result: - The services for CCVPN created successfully.
- CCVPN services distributed to A&AI and SO.
|
Observation:
|
8.Service LCM
8.1 SOTN TOPO Automatically synchronization.
Test NO: | TEST-05 |
Project: | Service LCM |
Sub-project: | SOTN network topology synchronized to ONAP |
Objective: | SOTN network topology can be synchronized to ONAP and be saved in A&AI. |
Pre-condition: | - All OTN network PNFs are ready.
- 3rd SOTN controller is ready and the OTN PNFs have been added to it.
|
Test steps: - Administrator login to ONAP?click “AAI UI ->view & inspect”?to view the topology synchronized from 3rd SOTN controller.
- Check the nodes of A&AI that used to save topology information.
|
Test result: - We can find the topology data in A&AI
|
Observation:
|
8.2 SOTN cross-domain/cross-ONAP link management
Test NO: | TEST-05 |
Project: | Service LCM |
Sub-project: | SOTN network topology management |
Objective: | UUI can support to view the topology of network and create cross-domain/cross-ONAP links. |
Pre-condition: | - All OTN network PNFs are ready.
- 3rd SOTN controller is ready and the OTN PNFs have been added to it.
- 3rd SOTN controller have been registered to ONAP ESR
|
Test steps: - Administrator login to ONAP, click “UUI” to enter the use case UI.
- Click ‘Topology management’ to manage the topology of OTN network.
- Click ‘Add link’ to add cross-domain/cross-onap links.
|
Test result: - We can find the topology data in UUI. To show the ONAP topologies.
- When we add the cross-domain link , a link will be shown between different domains.
- When we add the cross-ONAP link, a link with an ONAP icon will be shown in the portal.
|
Observation:
|
8.3 CCVPN Service Instantiation
Test NO: | TEST-06 |
Project: | Service LCM |
Sub Project: | Service instantiation for CCVPN services: SOTN VPN Infra Service?Site Enterprise Service?Site DC Service?SD-WAN VPN Infra service. |
Objective: | The services for CCVPN can be instantiated and the CPEs from two different service provider can talk with each other. |
Pre-condition: | - Four services for CCVPN have been designed and distribute successful.
- The 3rd SOTN controller and SD-WAN controller have been installed and registered to ONAP.
- The topology of the network have been synchronized to ONAP and the links cross domain/cross ONAP have been created by UUI.
|
Test step: - Administrator login to ONAP portal?select ‘UUI-biz’ to entry use case UI.
- Click UUI item “Services”?and select ‘Services’ Tab.
- Select customer and service type
- Click ‘create’ to create services.
- On ‘Create Service’ dialog, select the service template and enter the inputs for the service.
- Click ‘OK’ to instantiate a service.
- We need to create the services follow the sequence: SOTN VPN Infra Service, SD-WAN VPN Infra Service, Site Enterprise Service, Site DC Service.
|
Test Result: - All service can be created successfully.
|
Observation: - Check the SOTN controller, we can find the SOTN EPL created.
- Check the SD-WAN controller we can find the SD-WAN instance created.
- Check the terminal points that connect to CPE/vCPE for OTN network, they can reach to each other.
- Check the sites between two different ONAP, try to ‘Ping’ from one CPE to another,
It can connect to each other. - For two CPEs, they can connect to each by internet or OTN special connectivity.
|
8.4 Service termination
Test NO: | TEST-08 |
Project: | Service LCM |
Sub-project: | Service termination for CCVPN services: SOTN VPN Infra Service?Site Enterprise Service?Site DC Service?SD-WAN VPN Infra service |
Objective: | The services for CCVPN can be terminated. |
Pre-condition: | - Four services for CCVPN have been created successfully.
|
Test step: - Administrator login to ONAP portal?select ‘UUI-biz’ to entry use case UI.
- Click UUI item “Services”?and select ‘Services’ Tab.
- Select customer and service type
- Select service and click ‘delete’ to delete services.
- Click ‘OK’ to terminate a service.
- We need to delete the services follow the sequence: Site DC Service, Site Enterprise Service, SD-WAN VPN Infra Service, SOTN VPN Infra Service.
|
Test Result: - All service can be deleted successfully.
|
Observation: - Check the SOTN controller, we can find the SOTN EPL deleted.
- Check the SD-WAN controller we can find the SD-WAN instance deleted.
- Check the AAI in two ONAPs, all services for CCVPN are deleted.
|
9. Closed Loop
Test NO: | TEST-09 |
Project: | Closed Loop |
Sub-project: | Closed Loop in ONAP SOTN link |
Objective: | ONAP can find SOTN network cross domain link interruption automatically, and rebuild SOTN business automatically. |
Pre-condition: | - All elements of OTN network TOPO environment has been completed.
- CCVPN services have been created and bussiness is working fine.
|
Test step: - Interrupt the cross domain link in the CMCC side ONAP manually.
|
Test Result: - Closed-loop triggered automatically, SOTN link will be recreated through another cross domain link.
|
Observation: - Check all the CCVPN services are work fine as in “CCVPN Service Instantiation”
|