OSAM Use Case Tracking (Casablanca Release)

OSAM Core Onboarding And Instantiation

TODO

OSAM GW Onboarding And Instantiation

TODO

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
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
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
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.