1. Introduction

This is the integration test cases for OSAM use case.

2. Scope

The integration test case for OSAM use case, it includes VNF and PNF design from SDC, PNF registration, PNF activation, VNF instantiation and closed loop for VNFs

3.Terms, definitions and abbreviations

AbbreviationFull Name
PNFPhysical Network Function
VNFVirtual Network Function
GUIGraphic User Interface
GWGateway
SEBASDN-Enabled Broadband Access


4. Test Framework

TODO here: Add image to show test framework... can use architecture picture...


Module Introduction

ModuleFunction
OSAM CoreSeba specific operations are done on this VNF
OSAM GWAdapter between SEBA and OSAM Core
ONAPThe ONAP system for automation operation


5. Test Description

Test cases for ONAP, existing VF functions are going to be used for OSAM GW and OSAM Core. OSAM GW and OSAM Core specific designs should be applied also designed VFs should be deployed and their LCM should be managed as well.  ONAP's PNF functionally such as PNFD at onboarding time, PNF registration, PNF instantiation and PNF activation should be tested for SEBA.

5.1 Test Accounts

NameResponsibilityAccount
AdministratorResponsible for system management; Personnel permission configuration; ONAP external system registration; Operational lifecycle managementdemo/demo123456!
DesignerService template designcs0008/demo123456!
TesterService template testjm0007/demo123456!
GovernorService template approvegv0001/demo123456!
OperatorService template distributionop0001/demo123456!


6. SDC Resource Design

6.1 OSAM Core Resource Design

Test NO:TEST-01
Project:SDC
Sub ProjectResource import for OSAM Core
Objective:Support to import the resources for OSAM
Operator:Designer, Tester
Pre-conditions:
  1. Required Tosca template should be ready for OSAM Core

Test Step:

  1. Designer logins to SDC portal.
  2. Creates certificates(Or reuse)
  3. Creates a new VSP
  4. Imports the TOSCA template which is prepared for OSAM Core, to VSP
  5. Imports the VSP to Catalogs as a VF Resource and sends for approval to a tester
  6. Tester logins to SDC portal and confirm the OSAM Core resource

The Result

  1. The OSAM Core resource is imported to catalog as a VF and ready for usage at a service design level.

Observation:

We can find a new resource for OSAM Core in SDC catalog.


6.2 OSAM GW Resource Design

Test NO:TEST-02
Project:SDC
Sub ProjectResource import for OSAM GW
Objective:Support to import the resource for OSAM
Operator:Designer, Tester
Pre-conditions:1.Required Tosca template should be ready for OSAM GW

Test Step:

  1. Designer logins to SDC portal.
  2. Creates certificates(Or reuse)
  3. Creates a new VSP
  4. Imports the TOSCA template which is prepared for OSAM GW, to VSP
  5. Imports the VSP to Catalogs as a VF Resource and sends for approval to a tester
  6. Tester logins to SDC portal and confirm the OSAM GW resource

The Result

  1. The OSAM GW resource is imported to catalog as a VF and ready for usage at a service design level.

Observation:

We can find a new resource for OSAM GW in SDC catalog.


6.3 SEBA Resource Design

Test NO:TEST-03
Project:SDC
Sub ProjectResource import for SEBA
Objective:Support to import the resource for OSAM
Operator:Designer, Tester
Pre-conditions:1. Required Tosca template should be ready for SEBA

Test Step:

  1. Designer logins to SDC portal.
  2. Creates certificates(Or reuse)
  3. Creates a new VSP
  4. Imports the TOSCA template which is prepared for SEBA, to VSP
  5. Imports the VSP to Catalogs as a PNF Resource and sends for approval to a tester
  6. Tester logins to SDC portal and confirm the SEBA resource

The Result

  1. The SEBA resource is imported to catalog as a PNF and ready for usage at a service design level.

Observation:

We can find a new resource for SEBA in SDC catalog.


7. SDC Service Design

7.1 OSAM Core Service Design

Test NO:TEST-04
Project:SDC
Sub Project:Design OSAM Core service
Objective:SDC support to design OSAM Core service
Pre-condition:
  1. OSAM Core resource must be cataloged as a VF

Test Step:

  1. Designer logins to SDC portal.
  2. Creates a new service from the catalog page
  3. Fill the required parameters such as category etc.
  4. Clicks composition and drags and drop the OSAM Core VF resource
  5. Saves the service and sends for testing to a tester user
  6. Tester logins to ONAP and approves the service template
  7. Governer logins to ONAP and approves the service template
  8. Operator logins to ONAP and distributes the service template

Test Result:

  1. The service must be cataloged for OSAM
  2. The service must be distributed to AAI, DCAE, APPC, SDNC and SO.

Observation:

1. We can find a new service for OSAM Core in SDC catalog

2. We can find a new service to instantiate in VID

7.2 OSAM GW Service Design

Test NO:TEST-05
Project:SDC
Sub Project:Design OSAM GW service
Objective:SDC support to design OSAM GW service
Pre-condition:
  1. OSAM GW resource must be cataloged as a VF

Test Step:

  1. Designer logins to SDC portal.
  2. Creates a new service from the catalog page
  3. Fill the required parameters such as category etc.
  4. Clicks composition and drags and drop the OSAM GW VF resource
  5. Saves the service and sends for testing to a tester user
  6. Tester logins to ONAP and approves the service template
  7. Governer logins to ONAP and approves the service template
  8. Operator logins to ONAP and distributes the service template

Test Result:

  1. The service must be cataloged for OSAM
  2. The service must be distributed to AAI, DCAE, APPC, SDNC and SO.

Observation:

1. We can find a new service for OSAM GW catalog in SDC

2. We can find a new service to instantiate in VID


7.3 SEBA Service Design

Test NO:TEST-06
Project:SDC
Sub Project:Design SEBA service
Objective:SDC support to design SEBA service
Pre-condition:
  1. OSAM GW resource must be cataloged as a VF and must be instantiated.
  2. SEBA resource must be cataloged as a PNF

Test Step:

  1. Designer logins to SDC portal.
  2. Creates a new service from the catalog page
  3. Fill the required parameters such as category etc.
  4. Clicks composition and drags and drop the SEBA resource and the alloted resource.
  5. Enters the alloted resource configuration related to OSAM GW.
  6. Saves the service and sends for testing to a tester user
  7. Tester logins to ONAP and approves the service template
  8. Governer logins to ONAP and approves the service template
  9. Operator logins to ONAP and distributes the service template

Test Result:

  1. The service must be cataloged for OSAM
  2. The service must be distributed to AAI, DCAE, APPC, SDNC and SO.

Observation:

1. We can find a new service for SEBA in SDC catalog

2. We can find a new service to instantiate in VID


8 Service Instantiation

8.1 OSAM Core Service Instantiation

Test NO:TEST-07
Project:Service LCM

Sub-project:

Service instantiation for OSAM Core

Objective:

The Service for OSAM Core can be instantiated.
Pre-conditions:
  1. OSAM Core must be distributed to related ONAP components successfully.
  2. Subscriber and Cloud Region must already be added. (can be from robot script...)

Test step:

  1. Admin enters the VID UI and selects the service
  2. Clicks the create service and selects customer and cloud region and clicks create service.
  3. Clicks to create VNF
  4. Admin uploads the Preload from SDNC using service information
  5. Creates VF inside the VNF.

Test Result:

  1. OSAM Core service can be created successfully.

Observation:

  1. At the OpenStack, there must be a stack and instances related to OSAM Core.


8.2 OSAM GW Service Instantiation

Test NO:TEST-08
Project:Service LCM
Sub-project:Service instantiation for OSAM GW
Objective:The Service for OSAM GW can be instantiated.
Pre-conditions:
  1. OSAM Core must be distributed to related ONAP components successfully.
  2. Subscriber and Cloud Region must already be added. (can be from robot script...)

Test step:

  1. Admin enters the VID UI and selects the service
  2. Clicks the create service and selects customer and cloud region and clicks create service.
  3. Clicks to create VNF
  4. Admin uploads the Preload from SDNC using service information
  5. Creates VF inside the VNF.

Test Result:

  1. OSAM GW service can be created successfully.

Observation:

  1. At the OpenStack, there must be a stack and instances related to OSAM GW.


8.3 SEBA Service Instantiation

Test NO:TEST-09
Project:Service LCM
Sub-project:Service instantiation for SEBA
Objective:The Service for SEBA can be instantiated.
Pre-conditions:
  1. OSAM GW must be instantiated in any cloud region where it can able to reach SEBA pod.
  2. Subscriber must already be added.(can be from robot script...)
  3. SEBA service must be cataloged.

Test Steps:

  1. Admin enters the VID UI and selects the service
  2. Enters CorrelationId(PnfId) and location for SEBA PNF
  3. Clicks to create service.

NOTE: Test steps can be changed when VID UI is ready for PNF services.

Test Result:

  1. SEBA Service can be created successfully.

Observation:

  1. ONAP will be waiting for SEBA Pod to Register.


9 PNF

9.1 SEBA Registration And Activation

Test NO:TEST-10
Project:PNF
Sub-project:PNF Registration And Activation
Objective:Register And Activation of SEBA Pod to ONAP
Pre-conditions:
  1. SEBA Pod must be configured and be aware of its CorrelationId(PnfId)
  2. SEBA Pod must be aware of ONAP IP Address
  3. SEBA service must be instantiated.

Test Steps:

  1. The operator sends a rest request which contains SEBAs CorrelationId and ONAPs IP Address

Test Result:

  1. SEBA enters an active state in AAI.

Observation:

  1. SEBA Pod should be aware of OSAM GW and needs to connect.


10 Data Storage

10.1 Alarm Collection(Check the Use case tracking flow...)

Test NO:TEST-12
Project:DCAE
Sub-project:Data Collection
Objective:Use DCAE for storing alarms
Pre-conditions:
  1. SEBA service must be instantiated
  2. SEBA pod must be registered to ONAP
  3. OSAM GW must be matched with SEBA pod

Test Steps:

  1. Instantiate OSAM GW service.
  2. Instantiate SEBA service.
  3. Trigger SEBA pod to register DCAE
  4. Plug OLT to SEBA pod

Test Result:

  1. SEBA should send an event through OSAM GW to DCAE.

Observation:

  1. OSAM UI should receive an event that OLT is plugged
  • No labels

2 Comments

  1. David Perez Caparros

    Hi, thanks a lot for defining the integration test cases. So far all integration test cases are related to the provisioning of infrastructure services (registration of the access pod (PNF), instantiation of OSAM GW, instantiation of OSAM Core...). The instantiation, monitoring and termination of customer facing services (e.g. fixed broadband internet access) via OSAM Core are not being considered in the test cases, as these are out of scope for ONAP in R3 (in the context of OSAM), is my understanding correct?

    1. Cem Türker

      Hi David, 

      As you mention at R3 phase, we will focus on infrastructure service provisioning. Customer service provision will be done in R4(Dublin). Osam Core flows (expect alarm collection from ONAP) is not related to ONAP.