You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 47
Next »
Link to specification:
PNF PNP message flow diagram
Rainy day scenario - PNF is sending registration request to ONAP where required AAI entry is not present:
Sunny day 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
High-Level descriptions
Id. | Test Case Name | Test Case Description | Status |
---|
T01 | Create and distribute service which contains PNF | Verification if in VID is present PNF enabled service. | |
T02 | Waiting for PNFReady | 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. Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on pnfRegistration message contents. | |
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. Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on pnfRegistration message contents. | |
T05 | PNF registration rejected | Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. AAI entries shall not be created by PRH. | |
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. | |
Detailed descriptions
Test Case ID | T02 |
Test Case Name | Waiting for PNFReady |
Description | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. |
Release | Casablanca |
Preconditions | - Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
|
Testing Steps | Step | Expected Result |
[Currently under specification] | ... |
Actual Results | Correct entry is present in AAI. Entry contains pnf-name equal to correlationID. SO service is waiting for PNFReady to be published by PRH |
Conclusion (Pass/Fail) |
|
Testing Lab |
|
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T03 |
Test Case Name | PNF registration accepting when AAI entry created in advance |
Description | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present before first InventoryQuery is done by PRH. Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID. |
Release | Casablanca |
Preconditions | - Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
- Instantiated service for PNF using Test Case T02 (Waiting for PNFReady)
- Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
|
Testing Steps | Step | Expected Result |
- Verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Login to virtual machine with simulator
- In config.json file :
- fill value for sourceName key - use correlationId value used during service instantiation in prerequisite no. 3
- fill pnfOamIpv4Address, pnfOamIpv6Address with some value
- Run script
./simulator.sh start-dev in order to start simulator - Run script
./simulator.sh run simulator in order to start sending registration request messages - Once again verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Verify if SO service has reacted on PNFReady message from PRH and has ended
| - Command should return JSON with empty value for IPv4 and IPv6 address
- User is logged in
- config.json file is updated accordingly
- PnP PNF simulator is in started state
- PnP PNF simulator sends registration request
- Command should return JSON with IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
- Instantiated SO service has been ended. Verification can be done:
- VID,
- SO audit log
- AAI registry
|
Actual Results | PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID. |
Conclusion (Pass/Fail) |
|
Testing Lab |
|
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T04 |
Test Case Name | PNF registration accepted when AAI entry created with delay |
Description | Verification if PNF resource registration is done properly when correct AAI entry is created after first InventoryQuery is done by PRH. Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on pnfRegistration message contents.
|
Release | Casablanca |
Preconditions | - Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
- Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
|
Testing Steps | Step | Expected Result |
- Verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Login to virtual machine with simulator
- In config.json file :
- fill value for sourceName key - use correlationId value that will be used during service instantiation in step no. 7
- fill pnfOamIpv4Address, pnfOamIpv6Address with some value
- set testDuration (amount of registration requests) to value that allows incinerate SO service during period of time when messages are send to ONAP
- set messageInterval interval with which messages are send to ONAP
- Run script
./simulator.sh start-dev in order to start simulator - Run script
./simulator.sh run simulator in order to start sending registration request messages
- Download PRH logs and check that registration requests has been rejected.
- Instantiated service for PNF using Test Case T02 (Waiting for PNFReady) - use corelationID from step no. 3
- Once again verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Verify if SO service has reacted on PNFReady message from PRH and has ended
| - Command should return empty JSON
- User is logged in
- config.json file is updated accordingly
- PnP PNF simulator is in started state
- PnP PNF simulator sends registration request
- Command should return JSON with IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
- In PRH log should appear following message:
"org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow" - Command should return JSON with IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
- Instantiated SO service has been ended. Verification can be done in:
- VID,
- SO audit log
- AAI registry
|
Actual Results | PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID even AAI entry has been created after first InventoryQuery is done by PRH
|
Conclusion (Pass/Fail) |
|
Testing Lab |
|
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T05 |
Test Case Name | PNF registration rejected |
Description | Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. AAI entries shall not be created by PRH.
|
Release | Casablanca |
Preconditions | - Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
|
Testing Steps | Step | Expected Result |
- Verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Login to virtual machine with simulator
- In config.json file :
- fill value for sourceName
- fill pnfOamIpv4Address, pnfOamIpv6Address with some value
- Run script
./simulator.sh start-dev in order to start simulator - Run script
./simulator.sh run simulator in order to start sending registration request messages
- Download PRH logs and check that registration requests has been rejected.
- Once again verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
| - Command should return HTTP 400 code
- User is logged in
- config.json file is updated accordingly
- PnP PNF simulator is in started state
- PnP PNF simulator sends registration request
- In PRH log should appear following message:
"org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow" - Command should return HTTP 400 code
|
Actual Results | PNF registration is rejected and AAI entries has not be created.
|
Conclusion (Pass/Fail) |
|
Testing Lab |
|
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T06 |
Test Case Name | Parallel PNF PnP flows |
Description | Four parallel PNF PnP flows are hibernated, PNFRegistration event is received in ONAP, proper PNF PnP enabled workflow instance is re-hydrated. |
Release | Casablanca |
Preconditions | - Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
|
Testing Steps | Step | Expected Result |
- ...
| - ...
|
Actual Results |
|
Conclusion (Pass/Fail) |
|
Testing Lab |
|
Tester Name | Krzysztof Kuzmicki |