--TEST STATUS for Dublin Release ----
The Netconf configuration over TLS use case consists of three main parts:
- SO will implement two more steps in workflow CONFIG-ASSIGN and CONFIGURE step.
- Blueprint processor in CC-SDK will implement a way to send mount , configure and un-mount request to SDNC after getting CONFIGURE request from SO. It currently have ability to read any blueprint from archieve and process it.
- SDNC will load client cert , trusted certs and private key at deployment time. ODL is also upgraded to Flourine SR2 version to serve above requests.l for Dublin release)
JIRAs:
- CCSDK-926Getting issue details... STATUS
- CCSDK-1023Getting issue details... STATUS
- SDNC-556Getting issue details... STATUS
- SDNC-621Getting issue details... STATUS
- SO-1506Getting issue details... STATUS
- INT-885Getting issue details... STATUS
Deployment:
Test environment requirements for above test cases:
- xNF simulator for test cases: PNF Simulator with TLS support.
- Rest Client simulator.
- SO with Config-Assign and Configure steps implemented in workflows.
- CC-SDK, Blueprint processor enhanced so that it can send mount, configure and un-mount rest request to SDNC.
- SDNC enhanced with ODL flourine SR2 and also capable to import client and trusted certificate and private key at deployment time.
This environment can be set up by following the steps below.
- Repo : Yet to update
- RUN : Yet to update
Use Case preconditions:
- xNF simulator.
- Rest Client sim.
E2E Netconf config over TLS Sequence Diagram
High Level End-to-End feature integration Testcases :
# | Test Case | Status |
---|---|---|
1 | After PNF_READY, SO sends CONFIG-ASSIGN and CONFIGURE request to SS-API | |
2 | Sends CONFIGURE request to SS-API | |
3 | Check SDNC have client cert, private key and trusted certs setup at deployment | |
4 | Connect SDNC and PNF sim for configuration step | |
5 | E2E test case for NETCONF over TLS | |
5 | Successful flow: both steps will conclude as expected, and the desired configuration will be applied to the PNF; successful outcome | |
6 | Configlet not found: step deployConfig is called before assignConfig and thus the configlet was never created and persisted in the CDS’ database; failed outcome | |
7 | Non-existing PNF: configuration is called for a PNF that cannot be found on ONAP, that is, IP address does not exist; failed outcome | |
8 | ODL not found: no ODL is available in SDN-C to answer the Restconf requests; failed outcome | |
9 | PNF’s blueprint contains invalid configuration: the blueprint’s Restconf commands are wrong, provoking an error while sending them to ODL; failed outcome | NOT STARTED |
Detailed Description End-to-End Feature Integration Testcases :
Test Case ID | Netconf_TLS_E2E_01 | ||||
---|---|---|---|---|---|
Test Case Name | SO sends CONFIG-ASSIGN and CONFIGURE request to SS-API | ||||
Description | Ensure that PNF_READY notification is received by SO from simulated environment then SO sends CONFIG-ASSIGN request to SS-API | ||||
Release | Dublin | ||||
Pre-conditions | SO should be waiting for PNF_READY notification after registration process and fully configured as per registration process. | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab |
Test Case ID | Netconf_TLS_E2E_02 | ||||
---|---|---|---|---|---|
Test Case Name | Sends CONFIGURE request to SS-API | ||||
Description | In this simulated CONFIG-ASSIGN request will be sent to SS-API and response will be picked to check if response is OK. | ||||
Release | Dublin | ||||
Pre-conditions | BP processor should have access to correct blueprint in archive to process it. SDNC should b | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab |
Test Case ID | Netconf_TLS_E2E_03 | ||||
---|---|---|---|---|---|
Test Case Name | Check SDNC have client cert, private key and trusted certs setup at deployment | ||||
Description | SDNC configure client cert, private key and trusted certs and deployment time. This testcase checks if all certificates are configured fine. | ||||
Release | Dublin | ||||
Pre-conditions | SDNC should be up and running successfully | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab |
Test Case ID | Netconf_TLS_E2E_04 | ||||
---|---|---|---|---|---|
Test Case Name | Connect SDNC and PNF sim for configuration step | ||||
Description | SDNC/ODL will send mount , configure and unmount request to PNF sim and check if PNF sim is configured successfully. | ||||
Release | Dublin | ||||
Pre-conditions | PNF sim should be up and running with TLS port listening. It should also be configured with Yang Models necessary for configuration request. | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab |
Test Case ID | Netconf_TLS_E2E_05 | ||||
---|---|---|---|---|---|
Test Case Name | E2E test case for NETCONF over TLS | ||||
Description | Ensure that PNF_READY notification is received by SO from simulated environment then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API | ||||
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 and PNF simulator should be running with TLS support. | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab |
Test Case ID | Netconf_TLS_E2E_05 | ||||
---|---|---|---|---|---|
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 | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | PASS | ||||
Testing Lab | ? |
Test Case ID | Netconf_TLS_NEG_01 | ||||
---|---|---|---|---|---|
Test Case Name | Configlet not found | ||||
Description | step deployConfig is called before assignConfig and thus the configlet was never created and persisted in the CDS’ database | ||||
Release | Dublin | ||||
Pre-conditions | Valid Blueprint | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab | ? |
Test Case ID | Netconf_TLS_NEG_02 | ||||
---|---|---|---|---|---|
Test Case Name | Non-existing PNF | ||||
Description | Configuration is called for a PNF that cannot be found on ONAP, that is, its IP address does not exist | ||||
Release | Dublin | ||||
Pre-conditions | Valid PNF | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab | ? |
Test Case ID | Netconf_TLS_NEG_03 | ||||
---|---|---|---|---|---|
Test Case Name | ODL not found | ||||
Description | No ODL is available in SDN-C to answer the Restconf requests | ||||
Release | Dublin | ||||
Pre-conditions | Valid PNF | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab | ? |
Test Case ID | Netconf_TLS_NEG_04 | ||||
---|---|---|---|---|---|
Test Case Name | PNF’s blueprint contains invalid configuration | ||||
Description | The blueprint’s Restconf commands are wrong, provoking an error while sending them to ODL | ||||
Release | Dublin | ||||
Pre-conditions | Valid PNF | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | |||||
Testing Lab | ? |
Information:
Next Step(s):