Table of Contents |
---|
Overview:
The Netconf configuration over TLS use case consists The E2E integration test consists of three main parts:
- SO will implement two more steps in workflow CONFIG-ASSIGN and CONFIGURE step.
- CDS Blueprint Processor will implement the mount, configure and un-mount requests to SDNC after getting CONFIGURE request from SO. The processor currently has the ability to read a blueprint from archive and process it.
- SDNC will load client cert , trusted certs and private key at deployment time. ODL should also be upgraded to Flourine SR2 version to serve above requests. The upgrade is being tracked as part of SDNC-555
JIRAs:
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
Deployment:
Test environment requirements for the test cases:
- xNF simulator for test cases: PNF Simulator with TLS & YANG support.Rest Client simulator.
- SO with Config-Assign and Configure steps implemented in workflows.
- CDS 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
Test cases :
# | Test Case |
---|
Description |
---|
Reference | Tester | |||
---|---|---|---|---|
1 | Create and distribute service which contains PNF | Verify distribution and ingestion of PNF service csar to VID, AAI & SO. | 5G - PNF Onboarding Test Cases and Status : PNF-OB-5 | Andy Walshe |
2 | Waiting for PNFReady | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. | 5G - PNF PnP -WaitingforPNFReady | |
3 | PNF registration accepted | Verification if PNF resource registration is done properly | 5G : Configuration with NETCONF - E2E test case for Netconf over TLS | |
4 | Send Configuration with NETCONF over TLS | Verify the configuration is sent to the PNF with NETCONF | 5G : Configuration with NETCONF - Success Flow |
Detailed Description End-to-End Feature Integration Testcases :
Test Case ID | NETCONF_CONFIGURATION_TLS_E2E |
---|
Successful flow: CONFIG-ASSIGN and CONFIGURE steps will conclude as expected, and the desired configuration will be applied to the PNF; successful outcome
Detailed Description End-to-End Feature Integration Testcases :
SO should be waiting for PNF_READY notification after registration process and fully configured as per registration process.
Follow the 5G - PNF PnP - Integration Test Cases T01, T02, T03, T04 to complete the PNF registration and waiting for the PNF_READY notification.
- Send PNF_READY to SO
- SO will send CONFIG-ASSIGN to SS-API
- Receive it and Check if it is correct
- Send OK response to SO
- SO will send CONFIGURE request to SS-API
- Receive it and check if it is correct
- Send OK response to SO
The SO accepted the "PNF_READY" Notification.
and sends out the CONFIG-ASSIGN request to SS-APIand receive an OK response from SS-API
Sends CONFIGURE request to SS-API
Blueprint processor should have access to correct blueprint in archive to process it.
SDN-C should be available
Testing Steps
Check for mount, configure and un-mount messages triggered by the Blueprint processor component.
Verify that messages are valid and reflect all the expected parameters.
Check SDN-C has client cert, private key and trusted certs setup at deployment
SDN-C should be up and running successfully
Testing Steps
Steps | Expected Result |
---|---|
| Get request should get all certs and private key successfully. |
Connect SDN-C and PNF simulator for configuration step
PNF simulator should be up and running with TLS port listening. It should also be configured with Yang Models necessary for configuration request.
Testing Steps
Get response should give correct result for mount, configure and un-mount.
Test Case Name | E2E test case for NETCONF over TLS |
Description | Ensure that PNF_READY notification is received by SO from |
PRH then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API, to configure the xNF | |
Release | Dublin |
Pre-conditions |
|
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 |
|
Successful flow
Dublin
Valid PNF
Valid blueprint
SO is primed and post PNF registration stage
ODL instance is installed and available
Testing Steps
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 |
|
Conclusion (Pass /Fail) |
| ||||||
Testing Lab |
Ericsson Lab, Windriver Lab |
Information:
Next Step(s):