| Warning |
|---|
Test update for Guilin relase and SO building block flow |
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|
Release Notes:
In order to successfully run whole flow including SO service instantiation there is need to execute manual steps in:
- SO Maria DB in Casablanca and below releases
- dev-mariadb-galera-mariadb-galera-x in Dublin and above releases (mysql -uroot -psecretpassword)
during test time being.
Those changes need to be executed due to fact that in Casablanca release is no present dedicated BPMN workflow for PNF instantiation.
For testing activities there has been introduced adapted CreateVcpeResCustService_simplified bpmn workflow.
There is need to add entry with:
- /mso/async/services/CreateVcpeResCustService_simplified value in ORCHESTRATION_URI column
- createInstance in ACTION column
- UUID of distrubuted PNF SDC Service Model in SERVICE_MODEL_UUID column
in service_recipe table in catalogdb data base.
E.g.
insert into service_recipe values (null, 'createInstance' , '1' , 'pnf service', '/mso/async/services/CreateVcpeResCustService_simplified', null , 180, null, 2017-10-05 , 'a67565af-9f1f-4563-83f8-596d863dd362' );
...
|
| Table of Contents |
|---|
Link to specification:
5G - PNF Plug and Play
...
| Id. | Test Case Name | Test Case Description |
|---|---|---|
| T01 | Create and distribute service which contains PNF based on imported VSP | Verification if in VID is present PNF enabled service. |
| T02 | Waiting for PNFReadyPNF Ready | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. |
| T03 | PNF registration accepted when AAI entry created in advance | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present before first InventoryQuery is done by PRH. |
| T04 | PNF registration accepted when AAI entry created with delay | Verification if PNF resource registration is done properly when correct AAI entry is created after first InventoryQuery is done by PRH. |
| T05 | PNF registration rejected | Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. |
| T06 | Parallel PNF PnP flows | Four parallel PNF PnP flows are hibernated, PNFRegistration event is received in ONAP, proper PNF PnP enabled workflow instance is re-hydrated. |
| T07 | PNF registration accepted when AAI entry is created using AAI API (without SO instantiation) | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present - created using AAI API |
...