You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
--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 CONFIGURATION step.
- Blueprint processor in CCSDK 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-926
-
Getting issue details...
STATUS
CCSDK-1023
-
Getting issue details...
STATUS
SDNC-556
-
Getting issue details...
STATUS
SDNC-621
-
Getting issue details...
STATUS
SO-1506
-
Getting issue details...
STATUS
INT-885
-
Getting 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.
- CCSDK, 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
![](/download/attachments/58229781/SO-CCSDK-SDNC.png?version=1&modificationDate=1550587748000&api=v2)
High Level End-to-End feature integration Testcases :
# | Test Case | Status |
---|
1 | After PNF_READY, SO sends CONFIG-ASSIGN and CONFIGURE request to SSAPI | |
2 | Sends CONFIGURE request to SSAPI |
|
3 | Check SDNC have client cert, private key and trusted certs setup at deployment |
|
4 | Connect SDNC and PNF sim for configuration step |
|
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 | |
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 SSAPI |
Description | Ensure that PNF_READY notification is received by SO from simulated environment then SO sends CONFIG-ASSIGN request to SSAPI |
Release | Dublin |
Pre-conditions | SO should be waiting for PNF_READY notification after registration process and fully configured as per registration process. |
Testing Steps | Steps | Expected Result |
---|
- Send PNF_READY to SO
- SO will send CONFIG-ASSIGN to SSAPI
- Receive it and Check if it is correct
- Send OK response to SO
- SO will send CONFIGURE request to SSAPI
- 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 SSAPI
and receive an OK response from SSAPI
|
|
Conclusion (Pass /Fail) |
|
Testing Lab |
|
Test Case ID | Netconf_TLS_E2E_02 |
---|
Test Case Name | Sends CONFIGURE request to SSAPI |
Description | In this simulated CONFIG-ASSIGN request will be sent to SSAPI 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
| Steps | Expected Result |
---|
- Sends CONFIGURE request to SSAPI
- SSAPI will receive it
- SSAPI send CONFIGURE request to BP proc
- BP processor parse it and sends Mount to SDNC
- Receive this request read it if it is correct
- Send OK 200 response for mount to BP proc
- BP processor sends configuration request to SDNC
- Receive this request read it if it is correct
- send OK 200 response to BP proc
- BP processor sends un-mount request to SDNC
- Receive this request read it if it is correct
- send OK 200 response un-mount to BP proc
| Check for mount, configure and un-mount messages coming out of BP proc. Verify that they are correct. |
|
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
| Steps | Expected Result |
---|
- Send GET request from rest client to SDNC for key store
- Verify if it has all necessary entries for Client cert, trusted certs and private key.
| Get request should get all certs and private key successfully. |
|
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
| Steps | Expected Result |
---|
- Send mount request to SDNC from rest client.
- Check for 200 OK response
- Send GET request for mount
- Check data from GET response
- Send configuration request to SDNC from rest client.
- Check for 200 OK response
- Send GET request for configuration
- Check data from GET response
- Send un-mount request to SDNC from rest client
- check for 200 OK response
- Send GET request for un-mount
- Check data from GET response
| Get response should give correct result for mount, configure and un-mount. |
|
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 Valid blueprint SO is present (mocked if needed) ODL is present (mocked if needed) |
Testing Steps
| Steps | Expected Result |
---|
1. SO sends a request to perform action assignConfig
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
2. SS-API forwards the request to BPP, 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
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
4. SS-API forwards the request to BPP, that will load the blueprint, execute the action specified, retrieve the configlet from the persistence, connect to ODL, send the configlet to the PNF and return a successful message to SO |
|
|
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 SO is present (mocked if needed) To ensure that there is no previous persisted configlet, this should be the first test to be ran |
Testing Steps
| Steps | Expected Result |
---|
1. SO sends a request to perfom action deployConfig
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
2. SS-API forwards the request to BPP, that will load the blueprint and execute the action specified. As part of the action executon, BPP will try to retrieve the configlet from the CDS’ persistence, but it will fail since the assignConfig step did not happen before
3. An error message will be sent to SO |
|
|
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 Valid blueprint SO is present (mocked if needed) ODL is present (mocked if needed) |
Testing Steps
| Steps | Expected Result |
---|
1. SO sends a request to perform action assignConfig
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
2. SS-API forwards the request to BPP, 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
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
4. SS-API forwards the request to BPP, that will load the blueprint, execute the action specified and retrieve the configlet from the persistence
5. The next step is to mount a Netconf server in the PNF, through ODL. Since the IP address of the PNF is not valid, ODL won’t be able to connect to the PNF, failing the operation
6. An error message will be sent to SO
|
|
|
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 Valid blueprint SO is present (mocked if needed) ODL is present (mocked if needed) |
Testing Steps
| Steps | Expected Result |
---|
1. SO sends a request to perform action assignConfig
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
2. SS-API forwards the request to BPP, 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
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
4. SS-API forwards the request to BPP, that will load the blueprint, execute the action specified and retrieve the configlet from the persistence
5. The next step is to mount a Netconf server in the PNF, through ODL. Since there is no ODL available, such connection cannot be established
6. An error message will be sent to SO |
|
|
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 Valid blueprint SO is present (mocked if needed) ODL is present (mocked if needed) |
Testing Steps
| Steps | Expected Result |
---|
1. SO sends a request to perform action assignConfig
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
2. SS-API forwards the request to BPP, 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
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
4. SS-API forwards the request to BPP, that will load the blueprint, execute the action specified, retrieve the configlet from the persistence, connect to ODL and send the configlet to the PNF
5. Since the configlet is not valid, ODL will return an error after receiving the Restconf request
6. An error message will be sent to SO |
|
|
Conclusion (Pass /Fail) |
|
Testing Lab | ? |
Information: