You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

THIS PAGE IS UNDER DEV.


---TEST STATUS for Dublin Release ----

The Bulk PM feature consists of two main parts:

  • Event-driven bulk transfer of monitoring data from an xNF to ONAP/DCAE. A micro-service will listen for 'FileReady' VES events sent from an xNF via the VES collector. Once files become available the collector micro-service will fetch them using protocol such as FTPES (committed) or SFTP. The collected data files are published internally on a DMaaP Data Router (DR) feed. (committed goal for Casablanca release)
  • For 3GPP formatted measurement data and for consumers that prefer such data in VES format, an optional 3GPP PM Mapper micro-service is planned that can extract selected measurements from a 3GPP XML file and publish them as VES events on a DMaaP Message Router topic. The mapper receives the files by subscribing to a Data Router feed (committed goal 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.

  1. Clone the integration/csit repo (git clone ssh://gerrit.onap.org:29418/integration/csit).
  2. Run:

Use Case preconditions:

    • xNF simulator.
    • Rest Client sim.


E2E Netconf config over TLS Sequence Diagram



High Level End-to-End feature integration Testcases :


#Test CaseStatus
1After PNF_READY, SO sends CONFIG-ASSIGN request to SSAPI


2After CONFIG_ASSIGN response, SO sends CONFIGURE request

Successful flow: both steps will conclude as expected, and the desired configuration will be applied to the PNF; successful outcome



Configlet not found: step deployConfig is called before assignConfig and thus the configlet was never created and persisted in the CDS’ database; failed outcome



Non-existing PNF: configuration is called for a PNF that cannot be found on ONAP, that is, IP address does not exist; failed outcome



ODL not found: no ODL is available in SDN-C to answer the Restconf requests; failed outcome



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 NameSO sends CONFIG-ASSIGN and CONFIGURE request to SSAPI
DescriptionEnsure that PNF_READY notification is received by SO from simulated environment then SO sends CONFIG-ASSIGN request to SSAPI
ReleaseDublin
Pre-conditionsSO should be waiting for PNF_READY notification after registration process and fully configured as per registration process.
Testing Steps
StepsExpected Result
  1. Send PNF_READY to SO
  2. SO will send CONFIG-ASSIGN to SSAPI
  3. Receive it and Check if it is correct
  4. Send OK response to SO
  5. SO will send CONFIGURE request to SSAPI
  6. Receive it and check if it is correct
  7. 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 IDNetconf_TLS_E2E_02
Test Case Name

Sends CONFIGURE request to SSAPI

DescriptionIn this simulated CONFIG-ASSIGN request will be sent to SSAPI and response will be picked to check if response is OK.
ReleaseDublin
Pre-conditions

BP processor should have access to correct blueprint in archive to process it. SDNC should b

Testing Steps



StepsExpected Result
  1. Sends CONFIGURE request to SSAPI
  2. SSAPI will receive it
  3. SSAPI send CONFIGURE request to BP proc

  4. BP processor parse it and sends Mount to SDNC
  5. Receive this request read it if it is correct
  6. Send OK 200 response for mount to BP proc

  7. BP processor sends configuration request to SDNC
  8. Receive this request read it if it is correct
  9. send OK 200 response to BP proc

  10. BP processor sends un-mount request to SDNC
  11. Receive this request read it if it is correct
  12. 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 IDNetconf_TLS_E2E_03
Test Case Name

Check SDNC have client cert, private key and trusted certs setup at deployment

DescriptionSDNC configure client cert, private key and trusted certs and deployment time. This testcase checks if all certificates are configured fine.
ReleaseDublin
Pre-conditions

SDNC should be up and running successfully

Testing Steps



StepsExpected Result
  1. Send GET request from rest client to SDNC for key store
  2. 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 IDNetconf_TLS_E2E_04
Test Case Name


Description
ReleaseDublin
Pre-conditions


Testing Steps



StepsExpected Result



Conclusion (Pass /Fail)
Testing Lab


Test Case ID
Test Case Name

Successful flow

DescriptionSteps 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



StepsExpected 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
Test Case Name

Configlet not found

Descriptionstep deployConfig is called before assignConfig and thus the configlet was never created and persisted in the CDS’ database
ReleaseDublin
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



StepsExpected 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)

FAIL

Testing Lab

?


Test Case ID
Test Case Name

Non-existing PNF

DescriptionConfiguration is called for a PNF that cannot be found on ONAP, that is, its IP address does not exist
ReleaseDublin
Pre-conditions

Valid PNF
Valid blueprint
SO is present (mocked if needed)
ODL is present (mocked if needed)

Testing Steps



StepsExpected 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)FAIL
Testing Lab

?

Test Case ID
Test Case Name

ODL not found

DescriptionNo ODL is available in SDN-C to answer the Restconf requests
ReleaseDublin
Pre-conditions

Valid PNF
Valid blueprint
SO is present (mocked if needed)
ODL is present (mocked if needed)

Testing Steps



StepsExpected 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)FAIL
Testing Lab?
Test Case ID
Test Case Name

PNF’s blueprint contains invalid configuration

DescriptionThe blueprint’s Restconf commands are wrong, provoking an error while sending them to ODL
ReleaseDublin
Pre-conditions

Valid PNF
Valid blueprint
SO is present (mocked if needed)
ODL is present (mocked if needed)

Testing Steps



StepsExpected 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)FAIL
Testing Lab

?


Test Case ID
Test Case Name


Description
ReleaseDublin
Pre-conditions


Testing Steps



StepsExpected Result



Conclusion (Pass /Fail)
Testing Lab


Information:

For more information on the DMaaP API's see this link DMaaP API

Next Step(s):


  • No labels