PNF PNP message flow diagram
Rainy day scenario - PNF is sending registration request to ONAP where required AAI entry is not present:
Positive scenario - PNF is sending registration request to ONAP where required AAI entry is prepared by SO workflow:
PNF PNP deployment diagram
PNF PNP hardware requirements
- ONAP - standard ONAP instance located in Wind River lab
- 4 Virtual machines dedicated for PNF Simulator:
- 2 VCPU
- 8 GB of RAM
- 32 GB of HDD
PNF PNP test cases
| Id. | Test Case Name | Test Case Description | Status |
|---|---|---|---|
| 1. | AAI entry creation from SO side | Verification if AAI entry is created properly. Entry contains pnf-name and pnf-id equal to correlationID. | NOT TESTED |
| 2. | SO awaiting for PNF to be ready | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. | NOT TESTED |
| 3. | AAI entry update from PRH side | Verification if AAI entry is updated properly with pnfOamIpv4Address / pnfOamIpv6Address based on correlationID. | NOT TESTED |
| 4. | PNF rejection when no entry in AAI present | Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. | NOT TESTED |
| 5. | PNF PnP when AAI entry created in advance | Verification if PNF resource instantiation is done properly when correct AAI record (based on correlationID) is present before first InventoryQuery is done by PRH. | NOT TESTED |
| 6. | PNF PnP when AAI entry created with delay | Verification if PNF resource instantiation is done properly when correct AAI entry is created after first InventoryQuery is done by PRH. | NOT TESTED |
| 7. | Parallel PNF PnP flows | Four parallel PNF PnP flows are hibernated, PNFRegistration event is received in ONAP, proper PNF PnP instance is re-hydrated. | NOT TESTED |
| 8. | SO waiting for PNF max timeout | Verification if SO max PNF waiting period can be set up to 2 weeks. | NOT TESTED |