Versions Compared

Version Old Version 9 New Version Current
Changes made by

Cem Turker

Cem Turker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

OSAM Core Onboarding And Instantiation

...

#Test CasesStatus
1

Resource Definition

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

Status
titleNot yet tested

2

Service Definition

Define the requirements of the service

Status
titleNot yet tested

3

Modeling Artifacts

Any required ansible or chef(configuration) might be used

Status
titleNot yet tested

4

Resource Declaration

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

Status
titleNot yet tested

5

Service Declaration

Create a service from OSAM Core GW resource and required artifacts.

Status
titleNot yet tested

6

Service Instantiation

Instantiate OSAM Core GW service from VID UI.

Status
titleNot 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 Alarm Collection Use Case

Test Cases and Status: Alarm Collection 

#

Test Cases

Status

1Confirm that "osam" topic is created in DMAAP.
NOT YET TESTED
2Confirm 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
4Confirm that Service Flow Manager can consume the "osam/alert" topic.
NOT YET TESTED
5Confirm 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.

...