...
| Name | Responsibility | Account |
| Administrator | Responsible for system management; Personnel permission configuration; ONAP external system registration; Operational life cycle lifecycle management | demo/demo123456! |
| Designer | Service template design | cs0008/demo123456! |
| Tester | Service template test | jm0007/demo123456! |
| Governor | Service template approve | gv0001/demo123456! |
| Operator | Service template distribution | op0001/demo123456! |
...
| 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-04 |
| Project: | SDC |
| Sub Project: | Design OSAM Core service |
| Objective: | SDC support to design OSAM Core service |
| Pre-condition: | - OSAM Core resource must be cataloged as a VF
|
Test Step: - Designer logins to SDC portal.
- Creates a new service from the catalog page
- Fill the required parameters such as category etc.
- Clicks composition and drags and drop the OSAM Core VF resource
- Saves the service and sends for testing to a tester user
- Tester logins to ONAP and approves the service template
- Governer logins to ONAP and approves the service template
- Operator logins to ONAP and distributes the service template
|
Test Result: - The service must be cataloged for OSAM
- The service must be distributed to AAI, DCAE, APPC, SDNC and SO.
|
Observation: 1. We can find a new service for OSAM Core catalog in SDC catalog 2. We can find a new service to instantiate in VID |
...
| Test NO: | TEST-06 |
| Project: | SDC |
| Sub Project: | Design SEBA service |
| Objective: | SDC support to design SEBA service |
| Pre-condition: | - OSAM GW resource must be cataloged as a VF and must be instantiated.
- SEBA resource must be cataloged as a PNF
|
Test Step: - Designer logins to SDC portal.
- Creates a new service from the catalog page
- Fill the required parameters such as category etc.
- Clicks composition and drags and drop the SEBA resource and the alloted resource.
- Enters the alloted resource configuration related to OSAM GW.
- Saves the service and sends for testing to a tester user
- Tester logins to ONAP and approves the service template
- Governer logins to ONAP and approves the service template
- Operator logins to ONAP and distributes the service template
|
Test Result: - The service must be cataloged for OSAM
- The service must be distributed to AAI, DCAE, APPC, SDNC and SO.
|
Observation: 1. We can find a new service for SEBA in SDC catalog 2. We can find a new service to instantiate in VID |
8 Service Instantiation
8.1 OSAM Core Service Instantiation
| Test NO: | TEST-07 |
| Project: | Service LCM |
Sub-project: | Service instantiation for OSAM Core |
Objective: | The Service for OSAM Core can be instantiated. |
| Pre-conditions: | - OSAM Core must be distributed to related ONAP components successfully.
- Subscriber and Cloud Region must already be added. (can be from robot script...)
|
Test step: - Admin enters the VID UI and selects the service
- Clicks the create service and selects customer and cloud region and clicks create service.
- Clicks to create VNF
- Admin uploads the Preload from SDNC using service information
- Creates VF inside the VNF.
|
Test Result: - OSAM Core service can be created successfully.
|
Observation: - At the OpenStack, there must be a stack and instances related to OSAM Core.
|
8.2 OSAM GW Service Instantiation
| Test NO: | TEST-08 |
| Project: | Service LCM |
| Sub-project: | Service instantiation for OSAM GW |
| Objective: | The Service for OSAM GW can be instantiated. |
| Pre-conditions: | - OSAM Core must be distributed to related ONAP components successfully.
- Subscriber and Cloud Region must already be added. (can be from robot script...)
|
Test step: - Admin enters the VID UI and selects the service
- Clicks the create service and selects customer and cloud region and clicks create service.
- Clicks to create VNF
- Admin uploads the Preload from SDNC using service information
- Creates VF inside the VNF.
|
Test Result: - OSAM GW service can be created successfully.
|
Observation: - At the OpenStack, there must be a stack and instances related to OSAM GW.
|
8.3 SEBA Service Instantiation
| Test NO: | TEST-09 |
| Project: | Service LCM |
| Sub-project: | Service instantiation for SEBA |
| Objective: | The Service for SEBA can be instantiated. |
| Pre-conditions: | - OSAM GW must be instantiated in any cloud region where it can able to reach SEBA pod.
- Subscriber must already be added.(can be from robot script...)
- SEBA service must be cataloged.
|
Test Steps: - Admin enters the VID UI and selects the service
- Enters CorrelationId(PnfId) and location for SEBA PNF
- Clicks to create service.
NOTE: Test steps can be changed when VID UI is ready for PNF services. |
Test Result: - SEBA Service can be created successfully.
|
Observation: - ONAP will be waiting for SEBA Pod to Register.
|
9 PNF
9.1 SEBA Registration And Activation
| 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 Data Storage
10.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
|