SO triggers Configuration | Netconf Anchor |
---|
SO triggers Configuration | NETCONF_CONFIGURATION_TLS_E2E |
---|
_03 |
---|
Test Case Name | E2E test case for NETCONF over TLS |
Description | Ensure that PNF_READY notification is received by SO from |
simulated environment PRH then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API, to configure the xNF |
Release | Dublin |
Pre-conditions | - SO should be waiting for PNF_READY notification after registration process and fully configured as per registration process.
- Blueprint archive should be configured for correct blueprint.
- SDNC should be installed successfully with keystore preconfigured with certificates of PNF-SIM.
Certificates for PNF simulator can be picked up from here. Copy these certs in /dockerdatanfs/sdnc/certs and
|
PNF simulator - install sdnc.
- PNF-SIM should be running with TLS support.
Install pnf simulator from here using ./simulator.sh start. It will start simulator in TLS/SSH mode at 6503/830 port. Send VES message by changing config/config.json. |
Testing Steps |
Steps | Expected Result |
---|
- Send PNF_READY to SO(This step will trigger a run to SS-API, BP component, SDNC and PNF simulator)
|
|
Send SSH mount/connect request to SDNC/ODL using rest client.- SO sends CONFIG-ASSIGN request to CDS.
- SO receives the response from CDS for CONFIG-ASSIGN as success.
- SO sends CONFIG-DEPLOY async request to CDS.
- CDS sends patch(includes mount, configure and unmount request) to SDNC.
- SDNC sends mount request to PNF-SIM using TLS connection.
- CDS send connection status to SDNC for PNF-SIM.
- SDNC sends configuration request to PNF-SIM.
- SDNC sends unmount request to PNF-SIM
|
|
Send GET request for configuration to get configuration, set in step 1- .
- Verify received configuration is correct on PNF-SIM (Manual verification).
| Get response should give correct result for |
|
configureTesting Lab | Test Case ID Anchor |
---|
Successful flow | Successful flow | Netconf_TLS_E2E_04 | Test Case Name | Successful flow |
Description | Steps assignConfig and deployConfig will conclude as expected, and the desired configuration will be applied to the PNF
|
Release | Dublin |
Pre-conditions | Valid PNF Valid blueprint SO is primed and post PNF registration stage ODL instance is installed and available |
Testing Steps
Steps | Expected Result |
---|
1. SO sends a request to perform action assignConfig Code Block |
---|
| blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String |
2. SS-API forwards the request to BP, that will load the blueprint, execute the action specified, prepare the configlet, persist it and return a successful message to SO 3. SO recognizes the success message and sends a request to perfom action deployConfig Code Block |
---|
| blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String |
4. SS-API forwards the request to Blueprint Processor, that will load the blueprint, execute the action specified, retrieve the configlet from the persistence, connect to ODL, send the configlet(s) to the PNF and return a successful message to SO | |
Testing Lab | Ericsson Lab, Windriver |
Conclusion (Pass /Fail) | Testing