Rainy day scenario - PNF is sending registration request to ONAP where required AAI entry is not present:
Gliffy
name
PNF PNP Flow - Rainy day
pagePin
1
Sunny day scenario - PNF is sending registration request to ONAP where required AAI entry is prepared by SO workflow:
Gliffy
name
PNF PNP Flow - positive scenario
pagePin
1
PNF PNP deployment diagram
Gliffy
name
PNF_PNP_deployment
pagePin
5
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
...
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.
...
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.
...
Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. AAI entries shall not be created by PRH.
...
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.
Detailed descriptions
...
Create and distribute service which contains PNF based on imported VSP
...
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
...
Robot init sucesfully executed. In intsalation server followin script shoulkd be sucesfully ececuted.~/oom/kubernetes/robot/demo-k8s.sh onap init
Press Submit button and next COMMIT & SUBMIT button
Navigate to Home tab
Click on IMPORT button and select IMPORT VSP
Select previously created VSP and press IMPORT VSP button
In newly opened window yoiu can moduify PNF name.
Next click Create and Certify button
Next press Certify button. Put comment message in Certification confirmation pop-up and press OK button
Navigate to SDC tab / HOME menu
Click on ADD + button and select Add Service
In HOME > Create new service > General page fill all mandatory fields (change service type from default a'lacarte to macro) and press Create button in right top corner
Go to Composition in left menu
In search box find crated PNF using its name
Drag ad drop it to main view
Next click Certify button
Next Press Distribute button in left top corner
Press Monitor button in left top corner and verify distribution status, use refresh button
Re-login as a a demo user
VID Navigate to application
From left menu select Browse SDC Service Models
...
User is logged in
SDC application is open
ONBOARD CATALOG is visible
New License Model window is present
All mandatory parameters are fulfilled
License Key Group is added
Entitlement Pool is added
Feature Group is added
License Agreement is added
VLM is submitted sucesfully
VLM is visible
New Software Product window is present
All mandatory parameters are fulfilled
Licensing Version, License Agreement and Feature Groups and warning is not present
Licensing Version, License Agreement and Feature Groups are defined
Select file window is opened
File is selected
File is sucesfully uploaded and VSP is submited
Home tab is opened
Import VSP window is presnet with list of dubmited VSPs
Previously create VSP is imported as VSP and Create window is opened
All modifications are present
PNF is successfully Certified
SDC application is open
Page HOME > Create new service > General with fields that must be filled out is open
Create/Update saved successfully message is present in left top corner
Composition main view is open
PNF is visible
PNF is added to service
Service is Cerified and ready for Distribution
Distribute Distribute successfully message is present in left top corner
Monitor main view is opened with information about distribution. Thesr should not be any errors.Image Removed
User is re-logged
VID application is open
In Browse SDC Service Models main view is present entry about newly created service - it can take couple of minutes ~ 15 minutes Image Removed
...
Waiting for PNFReady
...
Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH.
Rainy day scenario - PNF is sending registration request to ONAP where required AAI entry is not present:
Gliffy
name
PNF PNP Flow - Rainy day
pagePin
1
Sunny day scenario - PNF is sending registration request to ONAP where required AAI entry is prepared by SO workflow:
Gliffy
name
PNF PNP Flow - positive scenario
pagePin
1
PNF PNP deployment diagram
Gliffy
name
PNF_PNP_deployment
pagePin
5
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
T01
Create and distribute service which contains PNF based on imported VSP
Verification if in VID is present PNF enabled service.
T02
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 pnfRegistration message contents.
T03
Delete pnf service and pnf resource
T04
Delete pnf service instance and reasign pnf resource to another service instance
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
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.
Detailed descriptions
Anchor
Create and distribute service which contains PNF based on imported VSP
Create and distribute service which contains PNF based on imported VSP
Test Case ID
T01
Test Case Name
Create and distribute service which contains PNF based on imported VSP
Description
Verification if in VID is present PNF enabled service. Test case covers following steps from message flow in 5G - PNF Plug and Play:
Release
Frankfurt/Guilin
Preconditions
Users with roles: Designer (Carlos Santana - cs0008), Admin (demo) should be available
Robot init sucesfully executed. In intsalation server followin script shoulkd be sucesfully ececuted.~/oom/kubernetes/robot/demo-k8s.sh onap init
Press Submit button and next COMMIT & SUBMIT button
Navigate to Home tab
Click on IMPORT button and select IMPORT VSP
Select previously created VSP and press IMPORT VSP button
In newly opened window yoiu can moduify PNF name.
Next click Create and Certify button
Next press Certify button. Put comment message in Certification confirmation pop-up and press OK button
Navigate to SDC tab / HOME menu
Click on ADD + button and select Add Service
In HOME > Create new service > General page fill all mandatory fields (change service type from default a'lacarte to macro) and press Create button in right top corner
Go to Composition in left menu
In search box find crated PNF using its name
Drag ad drop it to main view
Next click Certify button
Next Press Distribute button in left top corner
PressDistribution button in left top corner and verify distribution status, use refresh button
Re-login as a a demo user
VID Navigate to application
From left menu select Browse SDC Service Models
User is logged in
SDC application is open
ONBOARD CATALOG is visible
New License Model window is present
All mandatory parameters are fulfilled
License Key Group is added
Entitlement Pool is added
Feature Group is added
License Agreement is added
VLM is submitted sucesfully
VLM is visible
New Software Product window is present
All mandatory parameters are fulfilled
Licensing Version, License Agreement and Feature Groups and warning is not present
Licensing Version, License Agreement and Feature Groups are defined
Select file window is opened
File is selected
File is sucesfully uploaded and VSP is submited
Home tab is opened
Import VSP window is presnet with list of dubmited VSPs
Previously create VSP is imported as VSP and Create window is opened
All modifications are present
PNF is successfully Certified
SDC application is open
Page HOME > Create new service > General with fields that must be filled out is open
Create/Update saved successfully message is present in left top corner
Composition main view is open
PNF is visible
PNF is added to service
Service is Cerified and ready for Distribution
Distribute Distribute successfully message is present in left top corner
Monitor main view is opened with information about distribution. Thesr should not be any errors.Image Added
User is re-logged
VID application is open
In Browse SDC Service Models main view is present entry about newly created service - it can take couple of minutes ~ 15 minutes Image Added
Actual Results
In VID is present enabled PNF service.
Conclusion (Pass/Fail)
Testing Lab
Tester Name
Krzysztof Kuzmicki
Anchor
PNF registration accepting when AAI entry created in advance
PNF registration accepting when AAI entry created in advance
...
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.
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>"
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" "https://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 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:
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>
Actual Results
PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID. SO service is instantieted.
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.
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>"
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 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" "https://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 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:
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.
Whole test case can be also executed using postman collection PNF_service_instantiation_v2.postman_collection.json. In order to execute it successfully there is need to set two variables in collection variables:
name of servcie model for pNF
ip onap worker/k8s VM
Image Added
Also whole test case including T01 is automated in robot/xtesting robot smoke image - ~/oom/kubernetes/robot/demo-k8s.sh onap pnf_registarte
Release
Frankfurt/Guilin
Preconditions
Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF based on imported VSP )
Testing Steps
Step
Expected Result
Get created service model in Test Case T01 curl --location --request GET 'https://{worker_ip}:30204/sdc2/rest/v1/catalog/services/serviceName/{service model name}/serviceVersion/1.0' \ --header 'USER_ID: cs0008' \ --header 'X-FromAppId: robot-ete' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --header 'Authorization: Basic YmVlcDpib29w'
Fill all mandatory parameters. To "PNF (Correlation) ID" field put correlationId that will be setup in PNF simulator. Press "Confirm" button.
Close "In Progress" pop-up window
Login to so-so-bpmn-infra pod via rancher console: kubectl exec -it dev-so-so-bpmn-infra-7584f4f887-p9tmn -n onap /bin/sh open debug.log vi logs/bpmn/debug.log
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>"
Service model is present
Paremeters are present
Owning Entity ID is presnet
Product Familiy ID is present
SO_request.json is filled accodingly
SO request is send sucesfully.
Service_instance_id is saved from POST response
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
2020-08-20T20:59:35.865Z|87f367b7-5d84-47e9-a955-6b2143e8424a|o.o.l.filter.spring.SpringClientPayloadFilter - =======================response end=================================================
2020-08-20T20:59:35.875Z|87f367b7-5d84-47e9-a955-6b2143e8424a|o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - registering for pnf ready dmaap event for pnf correlation id: test_pnf_name
2020-08-20T20:59:35.881Z|87f367b7-5d84-47e9-a955-6b2143e8424a|org.onap.so.client.RestClient - RestClientSSL using default SSL context!
2020-08-20T20:59:35.894Z|87f367b7-5d84-47e9-a955-6b2143e8424a|o.o.logging.filter.base.PayloadLoggingClientFilter - Sending HTTP POST (overridden to PATCH) to:https://aai.onap:8443/aai/v19/network/pnfs/pnf
/test_pnf_name with request headers:{Authorization=[***REDACTED***], X-RequestID=[87f367b7-5d84-47e9-a955-6b2143e8424a], X-FromAppId=[MSO], X-ONAP-PartnerName=[UNKNOWN], X-HTTP-Method-Override=[PATCH], Ac
cept=[application/json], X-InvocationID=[a9b7b7c1-4912-4e48-8f3a-df7cd3123a54], X-ECOMP-RequestID=[87f367b7-5d84-47e9-a955-6b2143e8424a], X-TransactionId=[], X-ONAP-RequestID=[87f367b7-5d84-47e9-a955-6b21
43e8424a], Content-Type=[application/merge-patch+json]}
2020-08-20T20:59:35.895Z|87f367b7-5d84-47e9-a955-6b2143e8424a|o.o.logging.filter.base.PayloadLoggingClientFilter - {"pnf-id":"f792d78d-7c2c-4858-980b-23968923b3f4","orchestration-status":"Register"}
2020-08-20T20:59:35.982Z|87f367b7-5d84-47e9-a955-6b2143e8424a|o.o.logging.filter.base.PayloadLoggingClientFilter - Response from method:POST (overridden to PATCH) performed on uri:https://aai.onap:8443/aa
i/v19/network/pnfs/pnf/test_pnf_name has http status code:200 and response headers:{Content-Length=[0], content-type=[application/json], Date=[Thu, 20 Aug 2020 20:59:35 GMT], Strict-Transport-Security=[ma
x-age=16000000; includeSubDomains; preload;], vertex-id=[254096], X-AAI-TXID=[2-aai-resources-200820-20:59:35:904-22741]}
2020-08-20T20:59:35.983Z|87f367b7-5d84-47e9-a955-6b2143e8424a|o.o.logging.filter.base.PayloadLoggingClientFilter - Response was returned with an empty entity.
2020-08-20T20:59:39.896Z||o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - dmaap listener starts listening pnf ready dmaap topic
2020-08-20T20:59:54.485Z||o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - dmaap listener starts listening pnf ready dmaap topic
2020-08-20T21:00:09.016Z||o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - dmaap listener starts listening pnf ready dmaap topic
especially following entries: correlation id: test_pnf_name same as nf_instance_name from SO request and dmaap listener starts listening pnf ready dmaap topic is pnf name
Request is successful. Request should contain following values:
"pnf-name": equals tonf_instance_name
"orchestration-status": in status Register
"relationship-list": with information about service id (instanceId) to which PNF is connected
Request is successful. Request should contain following values:
"service-instance-name": equals to service_model_name_nf_instance_name
"model-invariant-id": equals to service_model_invariant_uuid
"model-version-id": equals to service_model_uuid
"orchestration-status": equals to "Assigned",
"relationship-list": with information pnf name (nf_instance_name)
Regitration request is send sucesfully.
SO-BPMN pod in /app/logs/bpmn/debug.log should be present following message: 2020-08-21T08:01:19.862Z||o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - unregistering from pnf ready dmaap event
got from dmaap for correlationId: <correlationId>
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. SO service is instantieted.
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.
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>"
Login to virtual machine with simulator
In config.json file :
fill value for sourceName
fill pnfOamIpv4Address, pnfOamIpv6Address with some value
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" "https://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 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.
for pnf correlation id: nf_instance_name 2020-08-21T08:01:19.862Z||o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - dmaap listener gets pnf ready event for pnfCorrelationId: nf_instance_name 2020-08-21T08:01:19.930Z|626785f1-baea-427d-aa7a-cdfddc209f5d|org.onap.so.client.RestClient - RestClientSSL using default SSL context!
Request is successful. Request should contain following values:
"pnf-name": equals tonf_instance_name
"orchestration-status": in status Active
"relationship-list": with information about service id (instanceId) to which PNF is connected
"ipaddress-v4-oam": should be filled according to registration_request,json
"ipaddress-v6-oam": should be filled according to registration_request,json
"equip-type": should be filled according to registration_request,json
"equip-vendor": should be filled according to registration_request,json
"equip-model":should be filled according to registration_request,json
"sw-version": should be filled according to registration_request,json
"serial-number": should be filled according to registration_request,json
"nf-role":should be filled according to registration_request,json
Request is successful. Request should contain following values:
"service-instance-name": equals to service_model_name_nf_instance_name
"model-invariant-id": equals to service_model_invariant_uuid
"model-version-id": equals to service_model_uuid
"orchestration-status": equals to Active
"relationship-list": with information pnf name (nf_instance_name)
Actual Results
PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID. SO service is instantieted.
Conclusion (Pass/Fail)
Testing Lab
Tester Name
Krzysztof Kuzmicki
Anchor
Delete pnf service and pnf resource
Delete pnf service and pnf resource
Test Case ID
T03
Test Case Name
Delete pnf service and pnf resource
Description
Release
Guilin
Preconditions
Testing Steps
Step
Expected Result
Actual Results
Conclusion (Pass/Fail)
Testing Lab
Tester Name
Krzysztof Kuzmicki
Anchor
Delete pnf service instance and reasign pnf resource to another service instance
Delete pnf service instance and reasign pnf resource to another service instance
Test Case ID
T06
T04
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.
Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF) for 4 PNF
Instantiated service for PNF using Test Case T02(Waiting for PNFReady) for 4 PNF
Testing Steps
Step
Expected
Resul
Result
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" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
Login to
each
virtual machine with simulator
In config.json file :
fill
value for sourceName key - use correlationId value used during service instantiation in prerequisite no. 3
value for sourceName
fill pnfOamIpv4Address, pnfOamIpv6Address with some value
Run script./simulator.sh run simulator in order to start sending registration request
messages
messages
Download PRH logs and check that registration requests has been rejected.
Once again verify AAI entry created by SO
service 4 PNFs
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>"
Verify if SO service has reacted on PNFReady message from PRH and has ended
Command should return JSONs with empty value for IPv4 and IPv6 address
User is logged in
config.json file is updated accordingly
PnP PNF simulator sends registration request
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
Instantiated SO service has been ended for 3 PNFs. Verification can be done:
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.
Actual Results
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
/pnfs/pnf/<correlationID>"
Command should return HTTP 400 code
User is logged in
config.json file is updated accordingly
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
T07T06
Test Case Name
PNF registration accepted when AAI entry is created using AAI API (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.
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>"
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" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
Login to each 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 run simulator in order to start sending registration request messages
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" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"