Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

anchorOOF001OOF
Test case IDComponentsTest caseStatus
POLICY_OOF_PAIRWISE_001Policy, OOF(Initial) Configuration of OOFNot tested
POLICY_PCIMS_PAIRWISE_001Policy, PCI-MS(Initial) Configuration of PCI-MSNot tested
SDNR_RAN_PAIRWISE_001SDN-R, RAN (Sim)

Connecting SDN-R with RAN (Sim) (netconf servers)

Not tested
SDNR_RAN_PAIRWISE_002SDN-R, RAN (Sim)

Receiving neighbor list change notification from RAN

Not tested
SDNR_PCIMS_PAIRWISE_001SDN-R, PCI-MS

Handle neighbor list change notification from SDN-R

Not tested
SDNR_PCIMS_PAIRWISE_002SDN-R, PCI-MSConfig DB API access (for getNbrList)Not tested
OOF_PCIMS_PAIRWISE_001OOF, PCI-MSRequest for PCI optimizationNot tested
OOF_SDNR_PAIRWISE_001OOF, SDN-RConfig DB API access (for getNbrList)Not tested
OOF_PCIMS_PAIRWISE_002OOF, PCI-MSPCI optimization resultNot tested

Test Case ID

SDNR_PCIMS_PAIRWISE_003SDN-R, PCI-MSConfig DB API access (for pnfName)Not tested
POLICY_
PCIMS_PAIRWISE_
002Policy, PCI-MSSending DMaaP message by PCI-MS to PolicyNot tested
POLICY_
SDNR_PAIRWISE_001Policy, SDN-RInvoking control loop in PolicyNot tested



Test Case ID

Anchor
POLICY_OOF_PAIRWISE_001
POLICY_OOF_PAIRWISE_001
POLICY_OOF_PAIRWISE_001

Test Case Name

Configuration of OOF


Description

Test if the OOF is onboarded and configuration policies are fetched and loaded correctly (Step 1c of flow)

Release

Casablanca

Pre-conditions

(a) Policy module is onboarded.

(b) Config policies related to OOF are provisioned properly in Policy module.

Testing Steps

Steps

Expected Result

  1. Bring up the OOF using the installation steps.
  2. Check the OOF database to see the contents of the OOF config policy for PCI optimization use case.
  1. OOF comes online and the database and local datastructures for PCI optimization use case are initialized correctly.
  2. Config-policy is correctly fetched and stored in the OOF DB.
    Sample config policy contents are given below:
    ALGO_CATEGORY:OOF-PCI-OPTIMIZATION
    PCI_OPTMIZATION_ALGO_NAME:OOF-PCI-OPTIMIZATION-LEVEL1
    PCI_OPTIMIZATION_NW_CONSTRAINT:MAX5PCICHANGESONLY
    PCI_OPTIMIZATION_PRIORITY: 2
    PCI_OPTIMIZATION_TIME_CONSTRAINT:NONE

Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

...

Test Case ID

Anchor
SDNR_PCIMS_PAIRWISE_002
SDNR_PCIMS_PAIRWISE_002
SDNR_PCIMS_PAIRWISE_002

Test Case Name

Config DB API access

Description

Test the working of Config DB APIs

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file.

(c) SDNR_PCIMS_PAIRWISE_001 has been completed (if not, write some stub code in PCI-MS to do the ConfigDB query after initialization).

Testing Steps

Steps

Expected Result

  1. PCI-MS does a query to the configDB using the APIs getNbrList API to get the neighbor list.
  1. API query is successful and results match with DB contents.
    Sample API query and results:
    (a) getNbrList
    API contents are provided in SDN-R impacts document.

Conclusion (Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

...

Test Case ID

Anchor
OOF_SDNR_PAIRWISE_001
OOF_SDNR_PAIRWISE_001
OOF_SDNR_PAIRWISE_001

Test Case Name

Config DB API access by OOF

Description

Accessing Config DB APIs by OOF for PCI optimization algorithm execution

Release

Casablanca

Pre-conditions

(a) OOF has fetched the config policies successfully from the Policy module.

(b) OOF_PCIMS_PAIRWISE_001 has been completed successfully (otherwise some dummy code for REST API call to Config DB to be written in OOF).

Testing Steps

Steps

Expected Result

  1. After receiving a request for PCI optimization, OOF does a Config DB API query for getting the cellList (for a given networkID) and nbrList (for the set of cells sent in the PCI optimization request by PCI-MS).
  2. API contents are available in https://wiki.onap.org/download/attachments/28382769/5GUseCase_OOFPCI_SDN_R_Impacts_v_0_11.docx?api=v2 SDN-R impacts document.


SDN-R accepts the API and sends a response with the requested details.

Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

Test Case ID

Anchor
OOF_PCIMS_PAIRWISE_002
OOF_PCIMS_PAIRWISE_002
OOF_PCIPCIMS_PAIRWISE_002

Test Case Name

PCI optimization result reported by OOF to PCI-MS

Description

PCI optimization result sent by OOF to PCI-MS via REST call.


Release

Casablanca

Pre-conditions

(a) OOF has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network.

(c) OOF_PCIMS_PAIRWISE_001 has been completed (otherwise some dummy code for REST API call to PCI-MS to be written in OOF).

Testing Steps

Steps

Expected Result

  1. After executing the PCI optimization algorithm, OOF invokes the callback API provided by the PCI-MS in the PCI optimization request API call. This API contains the results of the PCI optimization, i.e., the cells whose PCI values should be modified.
  2. An example of the API contents is available in PCI Optimization API

PCI-MS accepts the API and sends a 200 OK response.


Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

Test Case ID

Anchor
SDNR_PCIMS_PAIRWISE_003
SDNR_PCIMS_PAIRWISE_003
SDNR_PCIMS_PAIRWISE_003

Test Case Name

Config DB API access

Description

Test the working of Config DB APIs (getPnfName)

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file.

(c) OOF_PCIMS_PAIRWISE_002 has been completed (if not, write some stub code in PCI-MS to do the ConfigDB query).

Testing Steps

Steps

Expected Result

  1. For the list of cells (whose PCI values should be changed) received from OOF in the PCI-optimization result, PCI-MS does a query to the configDB using the getPnfName for obtaining the PNF names for those cells whose PNF names are not available in its local DB.
  1. API query is successful and results match with DB contents. API details are provided in SDN-R impacts document.

Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine



Test Case ID

Anchor
POLICY_PCIMS_PAIRWISE_002
POLICY_PCIMS_PAIRWISE_002
POLICY_PCIMS_PAIRWISE_002

Test Case Name

Sending DMaaP message to Policy module with the PCI changes.


Description

Sending of DMaaP message (Topic: DCAE_EVENT_OUTPUT) by PCI-MS to Policy with the PCI changes


Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file.

(c) SDNR_PCIMS_PAIRWISE_003 has been completed (if not, write some stub code in PCI-MS to send the DMaaP message).

Testing Steps

Steps

Expected Result

  1. PCI-MS prepares the DMaaP message (with payload layout corresponding to the yang model) to be sent to Policy. It sends 1 message for each PNF.
  1. DMaaP message(s) is successfully received by Policy.

Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

Test Case ID

Anchor
POLICY_SDNR_PAIRWISE_001
POLICY_SDNR_PAIRWISE_001
POLICY_SDNR_PAIRWISE_001

Test Case Name

Invoking the control loop in Policy


Description

Invoking the control loop and sending DMaaP message to SDN-R with the PCI changes.

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file.

(c) SDNR_PCIMS_PAIRWISE_003 has been completed (if not, write some stub code in PCI-MS to send the DMaaP message).

Testing Steps

Steps

Expected Result

  1. PCI-MS prepares the DMaaP message (with payload layout corresponding to the yang model) to be sent to Policy. It sends 1 message for each PNF.
  1. DMaaP message(s) is successfully received by Policy.

Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine