Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 3 PnP PNF Simualtors according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
  2. Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF) for 4 PNF
  3. Instantiated service for PNF using Test Case T02 (Waiting for PNFReady) for 4 PNF
Testing StepsStepExpected Resul
  1. Verify AAI entry created by SO service for 4 PNFs 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 each 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 run simulator in order to start sending registration request messages 
  5. Once again verify AAI entry created by SO service  4 PNFs 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>"
  6. Verify if SO service has reacted on PNFReady message from PRH and has ended
  1. Command should return JSONs with empty value for IPv4 and IPv6 address
  2. User is logged in
  3. config.json file is updated accordingly
  4. PnP PNF simulator sends registration request
  5. Command should return JSONs with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json for 3 PNFs
    For PNF which don't have working simulator command should return once again JSONs with empty value for IPv4 and IPv6 address
  6. Instantiated SO service has been ended for 3 PNFs. Verification can be done:
    1. VID,
    2. SO audit log
    3. AAI registry
    For PNF which don't have working simulator SO service is in waiting state.
Actual Results


Conclusion (Pass/Fail)
Testing Lab
Tester NameKrzysztof Kuzmicki
Test Case IDT07
Test Case Name

PNF registration accepted when AAI entry is created using AAI (without SO instantiation)

Description

Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present - created using AAI API
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
ReleaseCasablanca
Preconditions
  1. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
Testing StepsStepExpected Result
  1. Create PNF entry AAI entry using AAI API
    curl -i -X PUT -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" -d '{"pnf-name":"<correlationID>","pnf-name2":"example-pnf-name2-val-78244","pnf-name2-source":"example-pnf-name2-source-val-99275","pnf-id":"example-pnf-id-val-7989","equip-type":"example-equip-type-val-20348","equip-vendor":"example-equip-vendor-val-52182","equip-model":"example-equip-model-val-8370","management-option":"example-management-option-val-72881", "ipaddress-v4-oam": "", "ipaddress-v6-oam": ""}' "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
  2. Verify AAI entry:
    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>"
  3. Login to each virtual machine with simulator
  4. 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
  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  4 PNFs 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 available message in Message Router topic
    curl -i -X GET http://<kubernetes noed ip address>:<message router service port>/events/unauthenticated.PNF_READY/2/1
  1. Command should return HTTP 202 code
  2. Command should return JSONs
    with empty value for IPv4 and IPv6 address
  3. User is logged in
  4. config.json file is updated accordingly
  5. PnP PNF simulator sends registration request
  6. Command should return JSONs with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
  7. Command should return JSONs with  IPv4, IPv6 and correlationID filled accordingly with inputs from simulator's config.json
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