...
| Test NO: | TEST-03 |
| Project: | SDC |
| Sub Project | Resource 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: - Designer logins to SDC portal.
- Creates certificates(Or reuse)
- Creates a new VSP
- Imports the TOSCA template which is prepared for SEBA, to VSP
- Imports the VSP to Catalogs as a PNF Resource and sends for approval to a tester
- Tester logins to SDC portal and confirm the SEBA resource
|
The Result - The OSAM GW 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. |
...
| Test NO: | TEST-10 |
| Project: | PNF |
| Sub-project: | PNF Registration And Activation |
| Objective: | Register And Activation of SEBA Pod to ONAP |
| Pre-conditions: | - SEBA Pod must be configured and be aware of its CorrelationId(PnfId)
- SEBA Pod must be aware of ONAP IP Address
- SEBA service must be instantiated.
|
Test Steps: - The operator sends a rest request which contains SEBAs CorrelationId and ONAPs IP Address
|
Test Result: - SEBA enters an active state in AAI.
|
Observation: - SEBA Pod should be aware of OSAM GW and needs to connect.
|
10 Service LCM
10.1 OSAM Core Auto Scaling
...
Test Steps:
...
Test Result:
11 Data Storage
1110.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: | - SEBA service must be instantiated
- SEBA pod must be registered to ONAP
- OSAM GW must be matched with SEBA pod
|
Test Steps: - Instantiate OSAM GW service.
- Instantiate SEBA service.
- Trigger SEBA pod to register DCAE
- Plug OLT to SEBA pod
|
Test Result: - SEBA should send an event through OSAM GW to DCAE.
|
Observation: - OSAM UI should receive an event that OLT is plugged
|