You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »


PNF PNP Flow - positive scenario Copy

Link to specification:

5G - PNF Plug and Play

PNF PNP message flow diagram

Rainy day scenario - PNF is sending registration request to ONAP where required AAI entry is not present:

PNF PNP Flow - Rainy day

Sunny day scenario - PNF is sending registration request to ONAP where required AAI entry is prepared by SO workflow:

PNF PNP Flow - positive scenario


PNF PNP deployment diagram

PNF_PNP_deployment

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 NameTest Case DescriptionStatus
T01Create and distribute service which contains PNFVerification if in VID is present PNF enabled service.

NOT TESTED

T02Waiting for PNFReadyVerification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH.

NOT TESTED

T03PNF 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.

NOT TESTED

T04PNF 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.

NOT TESTED

T05PNF 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.

NOT TESTED

T06Parallel PNF PnP flowsFour parallel PNF PnP flows are hibernated, PNFRegistration event is received in ONAP, proper PNF PnP enabled workflow instance is re-hydrated.

NOT TESTED

Detailed descriptions

Test Case IDT01
Test Case Name

Create and distribute service which contains PNF

Description

Verification if in VID is present PNF enabled service.
Test case covers following steps from message flow in 5G - PNF Plug and Play:

  • STEP 1 RESOURCE DEFINITION
  • STEP 2 SERVICE DEFINITION
  • STEP 3 ARTIFACTS DISTRIBUTION
ReleaseCasablanca
Preconditions
  1. PNF license has been created
  2. Users with roles: Designer, Tester, Governance Rep, Ops, Admin should be available
Testing StepsStepExpected Result
  1. Login to ONAP portal as a designer user
  2. Navigate to SDC application
  3. Click on ADD + button and select  Add PNF
  4. In HOME > Create new resource > General page fill all mandatory fields and press Create button in right top corner
  5. Next press Submit for Testing button, fill Message field and press OK button
  6. Re-login as a tester user
  7. Navigate to SDC tab / HOME menu
  8. From main view select PNF submitted for testing
  9. Press Start Testing button in left top corner and next Accept button.
  10. Put comment message in Certification confirmation pop-up and press OK button
  11. Re-login as a a designer user
  12. Navigate to SDC tab / HOME menu
  13. Click on ADD + button and select  Add Service
  14. In HOME > Create new service > General page fill all mandatory fields and press Create button in right top corner
  15. Go to Composition in left menu
  16. In search box find crated PNF using its name
  17. Drag ad drop it to main view
  18. Next press Submit for Testing button, fill Message field and press OK button
  19. Re-login as a a tester user
  20. Navigate to SDC tab / HOME menu
  21. From main view select Service submitted for testing
  22. Press Start Testing button in left top corner and next Accept button.
  23. Put comment message in Certification confirmation pop-up and press OK button
  24. Re-login as a a governance user
  25. Navigate to SDC tab / HOME menu
  26. From main view select previously created Service
  27. Press Approve button in left top corner and put comment message in Certification confirmation pop-up and press OK button
  28. Re-login as a l as a ops user
  29. Navigate to SDC tab / HOME menu
  30. From main view select previously created Service
  31. Press Distribute button in left top corner
  32. Press Monitor button in left top corner and verify distribution status, use refresh button
  33. Re-login as a a demo user
  34. VID Navigate to  application
  35. From left menu select Browse SDC Service Models
  1. User is logged in
  2. SDC application is open
  3. Page HOME > Create new resource > General page with fields that must be filled out is open
  4. Create/Update saved successfully message is present in left top corner
  5. Submitted For Testing Submitted successfully for testing message is present in left top corner
  6. User is re-logged
  7. SDC application is open and newly created PNF is visible in main view
  8. Page with PNF configuration is open
  9. Start Testing Tested successfully message is present in left top corner
  10. Accept Accepted successfully message is present in left top corner
  11. User is re-logged
  12. SDC application is open
  13. Page HOME > Create new service > General with fields that must be filled out is open
  14. Create/Update saved successfully message is present in left top corner
  15. Composition main view is open
  16. PNF is visible
  17. PNF is added to service
  18. Submitted For Testing Submitted successfully for testing message is present in left top corner
  19. User is re-logged
  20. SDC application is open and newly created Service is visible in main view
  21. Page with Service configuration is open
  22. Start Testing Tested successfully message is present in left top corner
  23. Accept Accepted successfully message is present in left top corner
  24. User is re-logged
  25. SDC application is open and newly created Service is visible in main view
  26. Page with Service configuration is open
  27. Approve Approved successfully message is present in left top corner
  28. User is re-logged
  29. SDC application is open and newly created Service is visible in main view
  30. Page with Service configuration is open
  31. Distribute Distribute successfully message is present in left top corner
  32. Monitor main view is opened with information about distribution
  33. User is re-logged
  34. VID application is open
  35. in Browse SDC Service Models main view is present entry about newly created service
Actual ResultsIn VID is present PNF enabled service.
Conclusion (Pass/Fail)
Testing Lab
Tester NameKrzysztof Kuzmicki



Test Case IDT02
Test Case Name

Waiting for PNFReady

Description

Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH.

Test case covers following steps from message flow in 5G - PNF Plug and Play:

  • STEP 16 – SERVICE INSTANTIATION
  • STEP 18 – RESOURCE LEVEL FLOW STEP 20 – PNF A&AI ENTRY MISSING
  • STEP 21 – SUBSCRIBE
  • STEP 22 – RESOURCE LEVEL FLOW (RLF) TERMINATES
ReleaseCasablanca
Preconditions
  1. Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
Testing StepsStepExpected 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 NameKrzysztof Kuzmicki



Test Case IDT03
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.

Test case covers following steps from message flow in 5G - PNF Plug and Play:

  • STEP 26 PNF SENDS PNF REGISTRATION
  • STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
  • STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
  • STEP 27 PRH DOES INVENTORY QUERY
  • STEP 29 INVENTORY QUERY
  • STEP 30 UPDATE PNF ENTRY
  • STEP 31 PNF READY EVENT
  • STEP 34 UPDATE PNF WORKFLOW
  • STEP 43 INFORM OSS
ReleaseCasablanca
Preconditions
  1. Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
  2. Instantiated service for PNF using Test Case T02 (Waiting for PNFReady)
  3. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
Testing StepsStepExpected Result
  1. 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>"
  2. Login to virtual machine with simulator
  3. In config.json file :
    1. fill value for sourceName key - use correlationId value used during service instantiation in prerequisite no. 3
    2. fill pnfOamIpv4Address, pnfOamIpv6Address with some value
  4. Run script ./simulator.sh start-dev in order to start simulator
  5. Run script ./simulator.sh run simulator in order to start sending registration request messages 
  6. 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>"
  7. Verify if SO service has reacted on PNFReady message from PRH and has ended
  1. Command should return JSON with empty value for IPv4 and IPv6 address
  2. User is logged in
  3. config.json file is updated accordingly
  4. PnP PNF simulator is in started state
  5. PnP PNF simulator sends registration request
  6. Command should return JSON with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json 
  7. Instantiated SO service has been ended. Verification can be done:
    1. VID,
    2. SO audit log
    3. 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 NameKrzysztof Kuzmicki



Test Case IDT04
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.

Test case covers following steps from message flow in 5G - PNF Plug and Play:

  • STEP 26 PNF SENDS PNF REGISTRATION
  • STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
  • STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
  • STEP 27 PRH DOES INVENTORY QUERY
  • STEP 28 PNF SENDS PNF REGISTRATION
  • STEP 29 INVENTORY QUERY
  • STEP 30 UPDATE PNF ENTRY
  • STEP 31 PNF READY EVENT
  • STEP 34 UPDATE PNF WORKFLOW
  • STEP 43 INFORM OSS
ReleaseCasablanca
Preconditions
  1. Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
  2. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
Testing StepsStepExpected Result
  1. 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>"
  2. Login to virtual machine with simulator
  3. In config.json file :
    1. fill value for sourceName key - use correlationId value that will be used during service instantiation in step no. 7
    2. fill pnfOamIpv4Address, pnfOamIpv6Address with some value
    3. set  testDuration (amount of registration requests) to value that allows incinerate SO service during  period of time when messages are send to ONAP
    4. set messageInterval interval with which messages are send to ONAP
  4. Run script ./simulator.sh start-dev in order to start simulator
  5. Run script ./simulator.sh run simulator in order to start sending registration request messages
  6. Download  PRH logs and check that registration requests has been rejected.
  7. Instantiated service for PNF using Test Case T02 (Waiting for PNFReady) - use corelationID from step no. 3
  8. 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>"
  9. Verify if SO service has reacted on PNFReady message from PRH and has ended
  1. Command should return empty JSON
  2. User is logged in
  3. config.json file is updated accordingly
  4. PnP PNF simulator is in started state
  5. PnP PNF simulator sends registration request
  6. Command should return JSON with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
  7. In PRH log should appear following message:
    "org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow"
  8. Command should return JSON with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
  9. Instantiated SO service has been ended. Verification can be done in:
    1. VID,
    2. SO audit log
    3. 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 NameKrzysztof Kuzmicki



Test Case IDT05
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.

Test case covers following steps from message flow in 5G - PNF Plug and Play:

  • STEP 26 PNF SENDS PNF REGISTRATION
  • STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
  • STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
  • STEP 27 PRH DOES INVENTORY QUERY
  • STEP 28 PNF SENDS PNF REGISTRATION
  • STEP 29 INVENTORY QUERY
ReleaseCasablanca
Preconditions
  1. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
Testing StepsStepExpected Result
  1. 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>"
  2. Login to virtual machine with simulator
  3. In config.json file :
    1. fill value for sourceName
    2. fill pnfOamIpv4Address, pnfOamIpv6Address with some value
  4. Run script ./simulator.sh start-dev in order to start simulator
  5. Run script ./simulator.sh run simulator in order to start sending registration request messages
  6. Download  PRH logs and check that registration requests has been rejected.
  7. 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>"
  1. Command should return HTTP 400 code
  2. User is logged in
  3. config.json file is updated accordingly
  4. PnP PNF simulator is in started state
  5. PnP PNF simulator sends registration request
  6. In PRH log should appear following message:
    "org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow"
  7. 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 NameKrzysztof Kuzmicki




Test Case IDT06
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.

Test case covers following steps from message flow in 5G - PNF Plug and Play:

  • STEP 26 PNF SENDS PNF REGISTRATION
  • STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
  • STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
  • STEP 27 PRH DOES INVENTORY QUERY
  • STEP 28 PNF SENDS PNF REGISTRATION
  • STEP 29 INVENTORY QUERY
  • STEP 30 UPDATE PNF ENTRY
  • STEP 31 PNF READY EVENT
  • STEP 34 UPDATE PNF WORKFLOW
  • STEP 43 INFORM OSS
ReleaseCasablanca
Preconditions
  1. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
Testing StepsStepExpected Result
  1. ...
  1. ...
Actual Results


Conclusion (Pass/Fail)
Testing Lab
Tester NameKrzysztof Kuzmicki
  • No labels