Versions Compared

Key

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

OSAM Core Onboarding And InstantiationTODO

#Test CasesStatus
1Resource Definition

Status
titleNot yet tested

2Service Definition

Status
titleNot yet tested

3Modeling Artifacts

Status
titleNot yet tested

4Resource Declaration

Status
titleNot yet tested

5Service Declaration

Status
titleNot yet tested

6Service Instantiation

Status
titleNot yet tested


OSAM GW Onboarding And InstantiationTODO

#Test CasesStatus
1Resource Definition

Status
titleNot yet tested

2Service Definition

Status
titleNot yet tested

3Modeling Artifacts

Status
titleNot yet tested

4Resource Declaration

Status
titleNot yet tested

5Service Declaration

Status
titleNot yet tested

6Service Instantiation

Status
titleNot yet tested


SEBA Service Onboarding And Instantiation

...

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.

...