Introduction
This is the integration test case for SO VNFM Adapter test case. Test Description
Due to lack of SDC SOL004 VNF package and distribution, the test of VNFM Adapter functionalities is limited to manual-based testing, which injects REST requests/responses.
Automated CSIT testing has been deferred to El Alto underSO-1899 - SO VNFM Adapter CSIT testOPEN
Test Descriptions
1 Create VNF
A Create VNF request invokes both SOL003 Create and Instantiate VNF operations at the VNFM Adapter
1.1 Create VNF1 Create VNF through the VNFM Adapter NBI directly
| Test No: | Test-01 |
|---|---|
| Project | SO |
| Module | VNFM Adapter |
| Objective/Description | Test the VNFM adapter handles create VNF request, sending create and instantiate request to the VNFM, responding correctly to grant request from VNFM and updating AAI based on notifications received from the VNFM resulting from the instantiate request |
| Pre-Conditions | The generic VNF has been added in AAI. The VNF package has been distributed from SDC. The VNFM and VIM have been defined in AAI. VNFM simulator deployed as VNFM. SDNC preload completed through SDNC access site. Add the ETSI "Create_VNF" and "Terminate_VNF" building blocks to the "building_block_detail" table in MariaDB's "catalogdb". Edit the "orchestration_status_state_transition_directive" table in MariaDB's "catalogdb" to allow a service with "operationStatus" set to "CREATED" to allow a building block with a "TARGET_ACTION" of "ACTIVATE" to "CONTINUE". |
| Test Step | Invoke a POST request on the VNFM adpater NBI, path: /so/vnfm-adapter/v1/vnfs/<vnf-id> |
| Test Result | AAI updated with information on the instantiated VNF |
| Observation |
...
| Create and instantiate requests were correctly sent to the VNFM, the grant request from the VNFM was handled and reply sent to the VNFM and AAI was updated in accordance with the notifications received from the VNFM as a result of the VNF being instantiated |
1.2 Create VNF through VID
| Test No: | Test-0102 |
|---|---|
| Project | SO |
| Module | VNFM Adapter |
| Objective/Description | Test the VNFM adapter handles create VNF request, sending create and instantiate request to the VNFM, responding correctly to grant request from VNFM and updating AAI based on notifications received from the VNFM resulting from the VID instantiate request |
| Pre-Conditions | The generic VNF has been added in AAI. The VNF package has been distributed from SDC. The VNFM and VIM have been defined in AAI. VNFM simulator deployed as VNFM. SDNC preload completed through SDNC access site. Add the ETSI "Create_VNF" and "Terminate_VNF" building blocks to the "building_block_detail" table in MariaDB's "catalogdb". Edit the "orchestration_status_state_transition_directive" table in MariaDB's "catalogdb" to allow a service with "operationStatus" set to "CREATED" to allow a building block with a "TARGET_ACTION" of "ACTIVATE" to "CONTINUE". |
| Test Step | Deploy a service through VID, followed by deploying the VNF of the service through VID. |
| Test Result | AAI updated with information on the instantiated VNF. VID shows the VNF instantiated. |
| Observation | The deploy requests through VID were correctly sent through to the VNFM, the grant request from the VNFM was handled and reply sent to the VNFM and AAI was updated in accordance with the notifications received from the VNFM as a result of the VNF being instantiated. |
2 Delete VNF
A Delete VNF request invokes both SOL003 Terminate and Delete VNF operations
2.1 Terminate VNF1 Delete VNF through the VNFM Adapter NBI directly
| Test No: | Test-0103 |
|---|---|
| Project | SO |
| Module | VNFM Adapter |
| Objective/Description | Test the VNFM adapter handles delete request, sending terminate and delete request to the VNFM, responding correctly to grant request from VNFM and updating AAI based on notifications received from the VNFM resulting from the termination request |
| Pre-Conditions | The VNF has been created via the VNFM adapter |
| Test Step | Invoke a DELETE request on the VNFM adpater NBI, path: /so/vnfm-adapter/v1/vnfs/<vnf-id> |
| Test Result | AAI updated as a result of the VNF deletion, including the removal of the vserver information for the VNF, removal of self link and changing of the orchestration status |
| Observation | Terminate and delete requests were correctly sent to the VNFM, the grant request from the VNFM was handled and reply sent to the VNFM and AAI was updated in accordance with the notifications received from the VNFM as a result of the VNF being terminated. |
2.2 Delete VNF through VID
| Test No: | Test-0104 |
|---|---|
| Project | SO |
| Module | VNFM Adapter |
| Objective/Description | Test the VNFM adapter handles delete request, sending terminate and delete request to the VNFM, responding correctly to grant request from VNFM and updating AAI based on notifications received from the VNFM resulting from the termination request |
| Pre-Conditions | The VNF has been created, using VID, via the VNFM adapter. |
| Test Step | Delete the VNF through the VID GUI. |
| Test Result | VNF deleted from VID. AAI updated as a result of the VNF deletion, including the removal of the vserver information for the VNF, removal of self link and changing of the orchestration status. |
| Observation | The delete was correctly executed through VID and sent to the VNFM, the grant request from the VNFM was handled and reply sent to the VNFM and AAI was updated in accordance with the notifications received from the VNFM as a result of the VNF being terminated. |