/
OSAM Use Case Tracking (Casablanca Release)

OSAM Use Case Tracking (Casablanca Release)

Owned by Cem Turker
Last updated: Jul 31, 2018
3 min read

OSAM Core Onboarding And Instantiation

#

Test Cases

Status

#

Test Cases

Status

1

Resource Definition

OSAM Core specific heat(also the Tosca for ks8) template needs to be created

Not yet tested

2

Service Definition

Define the requirements of the service

Not yet tested

3

Modeling Artifacts

Any required ansible or chef(configuration) might be used

Not yet tested

4

Resource Declaration

Deploy created heat template to SDC. Import to SDC catalog as a resource

Not yet tested

5

Service Declaration

Create a service from OSAM Core resource and required artifacts.

Not yet tested

6

Service Instantiation

Instantiate OSAM Core service from VID UI.

Not yet tested















Test environment requirements for above test cases:

  • ONAP Pod should be ready

  • Subscribers should be registered to the ONAP system.

  • Any cloud region should be added to the ONAP system.





OSAM GW Onboarding And Instantiation

#

Test Cases

Status

#

Test Cases

Status

1

Resource Definition

OSAM GW specific heat(also the Tosca for ks8) template needs to be created

Not yet tested

2

Service Definition

Define the requirements of the service

Not yet tested

3

Modeling Artifacts

Any required ansible or chef(configuration) might be used

Not yet tested

4

Resource Declaration

Deploy created heat template to SDC. Import to SDC catalog as a resource

Not yet tested

5

Service Declaration

Create a service from OSAM GW resource and required artifacts.

Not yet tested

6

Service Instantiation

Instantiate OSAM GW service from VID UI.

Not yet tested















Test environment requirements for above test cases:

  • ONAP Pod should be ready

  • Subscribers should be registered to the ONAP system.

  • Any cloud region should be added to the ONAP system.





SEBA Service Onboarding And Instantiation

Since OSAM benefits from 5G use-case, some test cases will be the same. But, they are needed to be tested as well again for OSAM;

#

Test Cases

Status

#

Test Cases

Status

1

 Resource Definition



Not yet tested

2

 Service Definition

Not yet tested



3

Type Modeling Artifacts

Not yet tested

4

Resource Declaration

Not Yet Tested

5

Create A&AI PNF Entry

Not yet tested

6

Service Instantiation

Not yet tested

7

Homing OOF Scenario

Not yet tested

8

Resource RLF

Not yet tested

9

Check A&AI Entry

Not yet tested

10

Create A&AI Entry

Not yet tested

11

Subscribe VES Event

Not yet tested

12

RLF Thread Terminates

Not yet tested

13

Authenticates PNF Connection

Not yet tested

14

PNF Registration VES Events

Not yet tested

15

Inventory Query

Not yet tested

16

Update PNF Entry

Not yet tested

17

PNF Ready

Not yet tested



OSAM SEBA(PNF) Activation Use Case

Test Cases and Status: SEBA Activation

#

Test Cases

Status

#

Test Cases

Status

1

Confirm that SDNC applies connection points between OSAM GW and SEBA pod.(Similar to 5G but might be different for OSAM. Might add direct graph)

NOT YET TESTED

2

Confirm that APPC is sending PNFId and OSAM GW IP address other additional configurations. (Info in the design time this info will be delivered)

NOT YET TESTED

3

Confirm that SEBA pod is receiving PNFId, OSAM GW IP address, and configuration from APPC.

Expected final action: SEBA pod will try to register OSAM GW with received IP Address

NOT YET TESTED















Test environment requirements for above test cases:

  • PNF registration flow from 5G use case must be completed.

  • OSAM GW must be onboarded and instantiated.

  • SEBA PNFD must be onboard

    • SEBA specific PNFD should be prepared.

    • A required configuration such as SEBA specific Direct Graph must be given from CDT UI in SDC

  • SEBA service must be created from SDC and instantiated from VID.

  • SEBA Pod must be registered the ONAP pod via HTTP and SO should send the registration event(Most likely be similar to 5G use case)





OSAM Alarm Collection Use Case

Test Cases and Status: Alarm Collection 

#

Test Cases

Status

#

Test Cases

Status

1

Confirm that "osam" topic is created in DMAAP.

NOT YET TESTED

2

Confirm that VES Collector receives events from OSAM GW's Ves Agent.

NOT YET TESTED

3

Confirm that Ves Collector publishes the alarm event to DMAAP with "osam/alert"

topic tag.

NOT YET TESTED

4

Confirm that Service Flow Manager can consume the "osam/alert" topic.

NOT YET TESTED

5

Confirm that TCA receives the topic and stores in the BigData DB

NOT YET TESTED















Test environment requirements for above test cases:

  • OSAM GW must be onboarded and instantiated.

  • OSAM Core must be onboarded and instantiated.

  • SEBA service must be onboarded and instantiated.

  • Somehow(maybe from SDC) "osam" topic must be created on DMAAP.

  • At design time CLAMP must be used for OSAM specific Ves flows.