Page History

PNF registration accepting 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 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

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

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" "https://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" "https://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 sends registration request
5. Command should return JSON with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json 
6. Instantiated SO service has been ended. Verification can be done:
   1. VID,
      
   2. SO audit log
   3. Service is instantiated. It is visible in Search for Existing Service Instances menu
   4. SO-BPMN pod in /app/logs/bpmn/debug.log should be present following message:
      o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - pnf ready event got from dmaap for correlationId: <correlationId>AAI registry
      

PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID. SO service is instantieted.

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.

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

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

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" "httphttps://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 run simulator in order to start sending registration request messages
   
5. Download  PRH logs and check that registration requests has been rejected.
6. Instantiated service for PNF using Test Case T02 (Waiting for PNFReady) - use corelationID from step no. 3
   
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" "httphttps://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
8. 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 sends registration request
5. Command should return JSON with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
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 JSON with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
8. Instantiated SO service has been ended. Verification can be done in:
   1. VID,
      
   2. SO audit log
   3. Service is instantiated. It is visible in Search for Existing Service Instances menu
   4. SO-BPMN pod in /app/logs/bpmn/debug.log should be present following message:
      o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - pnf ready event got from dmaap for correlationId: <correlationId>AAI registry

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. SO service is instantieted.

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.

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

1. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator

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" "httphttps://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 run simulator in order to start sending registration request messages
   
5. Download  PRH logs and check that registration requests has been rejected.
   
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" "httphttps://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 sends registration request
5. In PRH log should appear following message:
   "org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow"
6. Command should return HTTP 400 code

PNF registration is rejected and AAI entries has not be created.

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.

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

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

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" "httphttps://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" "httphttps://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.
   1. Service is instantiated. It is visible in Search for Existing Service Instances menu
   2. SO-BPMN pod in /app/logs/bpmn/debug.log should be present following message:
      o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - pnf ready event got from dmaap for correlationId: <correlationId>
   For PNF which don't have working simulator SO service is in waiting state.

PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID exept PNF which don't have working simulator.

SO service are intatntieted for PNF except PNF which don't have working simulator. For this PNF service is in progress state.

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

1. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator

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" "httphttps://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" "httphttps://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

PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID