...
Table of Contents |
---|
1. Introduction
MDONS use case was proposed in ONAP Frankfurt release. Extension work in OOF support, asynchronous OpenRoadM service activation response handling and closed loop sub-use cases and scenario was introduced in Guilin release. Associated test cases are covered in the following sessions on this page.
Jira | ||||
---|---|---|---|---|
|
...
|
2. MDONS Primary Test Cases in R6
The test cases and environment set up can be taken as basic preparation for MDONS Extension test.
3. Asynchronous Service Response Handling (ASRH)
3.1 Response handling Upon Successful Open RoadM OTN Service Activation
Test NO: | TEST-01 |
Project: | OTN Service LCM |
Sub-project: | OpenRoadM OTN Service Creation |
Objective: | The OpenRoadM OTN services creation status changed from pending to successful upon service activation is succeeded. |
Pre-condition: |
|
Test steps:
2. Submit a OpenRoadM OTN service creation request 3. Notice service creation is pending from UUI. 4. Send a OTN service activation request from Postman or Restclient to the domain controller (VNC) by call its NB API. 5. Upon an activation success notification respond back from VNC to ONAP (SDNC) 6. The OTN service status become successful at UUI. | |
Test Result:
| |
Observation:
|
4. MDONS OOF Support
4.1 Inter Domain Link/Path Selection at TAPI OTN Service Creation
Test NO: | TEST-02 |
Project: | OTN Service LCM |
Sub-project: | TAPI OTN Service Creation |
Objective: | A cross domain OTN Service is created by calling OOF Interface at inter domain link selection. |
Pre-condition: |
|
Test steps:
2. Create an OTN service between 2 network interface (TAPI UNI) end points which belong 2 different domains. 3. Notice that one of the IDLs is selected for the OTN service instance created. | |
Test Result:
| |
Observation:
|
5. Closed Loop
5.1 Different IDL and Domain OTN Services Associated An Existing Access OTN Service After Node Down Alarm Raised
Test NO: | TEST-03 |
Project: | MDONS Closed Loop |
Sub-project: | Cross Domain OTN Service Re-provisioning |
Objective: | Cross domain OTN service re-provision is supported automatically upon node down alarm(s) raised through VNC to close the loop. |
Pre-condition: |
|
Test steps:
2. Configure and Deploy predefined Apex operation policy at APEX. 3. Generate alarm from SB NE simulator (for the time being). 4. Notice that associated IDL goes down in ONAP by running AAI query. 5. Another IDL is selected for the OTN service instance. 6. Two original domain services associated with the OTN service are replaced by two new domain services. | |
Test Result:
| |
Observation:
Note:
|
1. MDSONS OOF Support
2. Asynchronous Service Response Handling (ASRH)
3. Closed Loop
4. MDONS Primary Test Cases in R6
...