Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »


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

release. Associated test cases are covered in the following sessions on this page. 

INT-1659 - Getting issue details... STATUS

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:

  1. OpenRoadM domain controller (Fujitsu VNC) is running and OpenRoadM (MSA) topology has been discovered and loaded in ONAP.
  2. The OTN services creation request is pending because synchronous response indicates that a following async-response will be received by ONAP. 

Test step:

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

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:

  1. The OpenRoadM OTN  service creation become successful.


Observation:

  1. Check UUI, we can find the associated OTN service creation status changed from pending to successful.

4.  MDSONS OOF Support

5.  Closed Loop

  • No labels