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 in:
   
   1. VID,
      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>

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" "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 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" "https://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 :VID,
   Service is instantiated. It is visible in Search for Existing Service Instances menu
   
   1. 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>

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.