Page Comparison

Test Step:

1. Designer logins to SDC portal.
2. Creates certificates(Or reuse)
3. Creates a new VSP
4. Imports the TOSCA template which is prepared for OSAM GW

1. , to VSP
2. Imports the VSP to Catalogs as a VF Resource and sends for approval to a tester
3. Tester logins to SDC portal and confirm the OSAM GW resource

The Result

1. The OSAM GW resource is imported to catalog as a VF and ready for usage at a service design level.

Observation:

We can find a new resource for OSAM GW in SDC catalog.

Test Step:

1. Designer logins to SDC portal.
2. Creates certificates(Or reuse)
3. Creates a new VSP
4. Imports the TOSCA template which is prepared for SEBA, to VSP
5. Imports the VSP to Catalogs as a PNF Resource and sends for approval to a tester
6. Tester logins to SDC portal and confirm the SEBA resource

The Result

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

1. OSAM Core resource must be cataloged as a VF

Test Step:

1. Designer logins to SDC portal.
2. Creates a new service from the catalog page
3. Fill the required parameters such as category etc.
4. Clicks composition and drags and drop the OSAM Core VF resource
5. Saves the service and sends for testing to a tester user
6. Tester logins to ONAP and approves the service template
7. Governer logins to ONAP and approves the service template
8. Operator logins to ONAP and distributes the service template

Test Result:

1. The service must be cataloged for OSAM
2. The service must be distributed to AAI, DCAE, APPC, SDNC and SO.

Observation:

1. We can find a new service for OSAM Core in SDC catalog

2. We can find a new service to instantiate in VID

1. OSAM GW resource must be cataloged as a VF

Test Step:

1. Designer logins to SDC portal.
2. Creates a new service from the catalog page
3. Fill the required parameters such as category etc.
4. Clicks composition and drags and drop the OSAM GW VF resource
5. Saves the service and sends for testing to a tester user
6. Tester logins to ONAP and approves the service template
7. Governer logins to ONAP and approves the service template
8. Operator logins to ONAP and distributes the service template

Test Result:

1. The service must be cataloged for OSAM
2. The service must be distributed to AAI, DCAE, APPC, SDNC and SO.

Observation:

1. We can find a new service for OSAM GW catalog in SDC

2. We can find a new service to instantiate in VID

1. OSAM GW resource must be cataloged as a VF and must be instantiated.
2. SEBA resource must be cataloged as a PNF

Test Step:

1. Designer logins to SDC portal.
2. Creates a new service from the catalog page
3. Fill the required parameters such as category etc.
4. Clicks composition and drags and drop the SEBA resource and the alloted resource.
5. Enters the alloted resource configuration related to OSAM GW.
6. Saves the service and sends for testing to a tester user
7. Tester logins to ONAP and approves the service template
8. Governer logins to ONAP and approves the service template
9. Operator logins to ONAP and distributes the service template

Test Result:

1. The service must be cataloged for OSAM
2. 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

Sub-project:

Objective:

1. OSAM Core must be distributed to related ONAP components successfully.
2. Subscriber and Cloud Region must already be added. (can be from robot script...)

Test step:

1. Admin enters the VID UI and selects the service
2. Clicks the create service and selects customer and cloud region and clicks create service.
3. Clicks to create VNF
4. Admin uploads the Preload from SDNC using service information
5. Creates VF inside the VNF.

Test Result:

1. OSAM Core service can be created successfully.

Observation:

1. At the OpenStack, there must be a stack and instances related to OSAM Core.
   

1. OSAM Core must be distributed to related ONAP components successfully.
2. Subscriber and Cloud Region must already be added. (can be from robot script...)

Test step:

1. Admin enters the VID UI and selects the service
2. Clicks the create service and selects customer and cloud region and clicks create service.
3. Clicks to create VNF
4. Admin uploads the Preload from SDNC using service information
5. Creates VF inside the VNF.

Test Result:

1. OSAM GW service can be created successfully.

Observation:

1. At the OpenStack, there must be a stack and instances related to OSAM GW.

1. OSAM GW must be instantiated in any cloud region where it can able to reach SEBA pod.
2. Subscriber must already be added.(can be from robot script...)
3. SEBA service must be cataloged.

Test Steps:

1. Admin enters the VID UI and selects the service
2. Enters CorrelationId(PnfId) and location for SEBA PNF
3. Clicks to create service.

NOTE: Test steps can be changed when VID UI is ready for PNF services.

Test Result:

1. SEBA Service can be created successfully.

Observation:

1. ONAP will be waiting for SEBA Pod to Register.

1. SEBA Pod must be configured and be aware of its CorrelationId(PnfId)
2. SEBA Pod must be aware of ONAP IP Address
3. SEBA service must be instantiated.

Test Steps:

1. The operator sends a rest request which contains SEBAs CorrelationId and ONAPs IP Address

Test Result:

1. SEBA enters an active state in AAI.

Observation:

1. SEBA Pod should be aware of OSAM GW and needs to connect.

1. SEBA service must be instantiated
2. SEBA pod must be registered to ONAP
3. OSAM GW must be matched with SEBA pod

Test Steps:

1. Instantiate OSAM GW service.
2. Instantiate SEBA service.
3. Trigger SEBA pod to register DCAE
4. Plug OLT to SEBA pod

Test Result:

1. SEBA should send an event through OSAM GW to DCAE.

Observation:

1. OSAM UI should receive an event that OLT is plugged