Skip to end of metadata
Go to start of metadata

Triggered by merges in policy/engine, policy/drools-pdp, and policy/drools-applications

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Lab

1

Perform   healthcheck for the Policy  using Healthcheck API

  •   Drools PDP
  •   XACML PDP
  •   PAP
  •   BRMSGateway
  • Policy docker image ready and policy   components (Drools, XACML, PAP, BRMS Gateway) should be up and running
  • Server and authentication details should   be configured at  $POLICY_HOME/config/feature-healthcheck.properties

API – healthcheck

Method - GET

Endpoint: https://<host>:6969/policy/pdpd/v1/engine/healthcheck

(legacy policy system healthcheck with new REST API format)

All the policy components should return health status as “true”

CSIT - DONE

External Lab - DONE

2

Import/Load Use case template for the following use cases (VoLTE,   vCPE, vFW, vDNS)

 Policy components should be up and running

API – policyEngineImport

Method – POST

Endpoint:

https://<host>:8081/pdp/policyEngineImport

(legacy API)

Policy service models should be imported for the specified use cases. We should be able to create policy from here.

CSIT

3

Create and Push Config Policy for the vFW use case.

 Policy components up and   running

API – CreateConfig

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Config Policy should be created in Policy Engine (PAP)

and

Config Policy should be pushed to the PDP group

CSIT - DONE
4Create and Push Config Policy for the vDNS use case.Policy components up and   running

API – CreateConfig

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Config Policy should be created in Policy Engine (PAP)

and


Config Policy should be pushed to the PDP group
CSIT - DONE
5Create and Push config Policy for the vCPE use case.Policy components up and   running

API – CreateConfig

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Config Policy should be created in Policy Engine (PAP)

and


Config Policy should be pushed to the PDP group
CSIT-DONE
6Create and Push vFW SDNC Naming policyPolicy components up and running

API - createPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/createPolicy

Naming policy should be created in Policy Engine

CSIT - DONE

7Create and Push vPG SDNC Naming policyPolicy components up and running

API - createPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/createPolicy

Naming policy should be created in Policy EngineCSIT - DONE

8

Create and Push Operational policy for vFW use case

 Policy components up and running

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Operational Policy should be created in Policy Engine (PAP)

and

Operational Policy should be pushed to the PDP engine

CSIT - DONE

9

Create and Push Operational Policy to the PDP Engines for vDNS use case

 Policy components up and running

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Operational Policy should be created in Policy Engine (PAP)

and

Operational Policy should be pushed to the PDP engine

CSIT - DONE
10Create and Push Operational Policy to the PDP Engines for vCPE use casePolicy components up and running

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Operational Policy should be created in Policy Engine (PAP)

and


Operational Policy should be pushed to the PDP engine

CSIT - DONE
11Create and Push Operational Policy to the PDP Engines for VOLTE use casePolicy components up and running

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Operational Policy should be created in Policy Engine (PAP)

and


Operational Policy should be pushed to the PDP engine

CSIT - DONE

12

Retrieve the Configs for the vFW use case

Policy components up and running

API – getConfig

Method – POST

Endpoint: https://<host>:8081/pdp/api/getConfig

(legacy API)

Both Config and Operational Policies configured should be retrieved successfully

CSIT - DONE
13

Retrieve the Configs for the vDNS use case

Policy components up and running

API – getConfig

Method – POST

Endpoint: https://<host>:8081/pdp/api/getConfig

(legacy API)

Both Config and Operational Policies configured should be retrieved successfullyCSIT - DONE
14Retrieve the Configs for the vCPE use casePolicy components up and running

API – getConfig

Method – POST

Endpoint: https://<host>:8081/pdp/api/getConfig

(legacy API)

Both Config and Operational Policies configured  should be retrieved successfullyCSIT - DONE
15List Configuration PoliciesList all configuration policies

API – listPolicy

Method – POST

Endpoint: https://<host>:8081/pdp/api/listPolicy

Should list all configuration policiesCSIT-Done
16Get ONAP Optimization Framework(OOF) Policy for Hardware Platform Awareness(HPA)Retrieve OOF Policy for HPA

API – getConfig

Method – POST

Endpoint: https://<host>:8081/pdp/api/getConfig

Should return the HPA policy.CSIT-Done
17Create and Push OOF Policy for Hardware Platform Awareness(HPA)Create and Push OOF Policy for HPA

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

(legacy API)

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

(legacy API)

Should Create and Push the config policyCSIT-Done
18Create and Push multiple policiesCreate and push multiple operational policies

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

Should create and push 3 operational policiesCSIT - Done
19Delete multiple policiesDelete multiple operational policies

API - deletePolicy  

Method - DELETE

Endpoint:

https:// <host>:8081/pdp/api/deletePolicy

Should delete the 3 operational policies created before this (from test #18)CSIT - Done

Triggered by merges in policy/distribution

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Lab

1

Perform healthcheck of the component

Policy distribution docker image is available

API – healthcheck

Method - GET

Endpoint: https://<host>:6969/policy/distribution/v1/healthcheck

The component should return health status as “true”

CSIT - DONE

External Lab

2Query component for statisticsPolicy distribution docker image is available

API - statistics

Method - GET

Endpoint: https://<host>:6969/policy/distribution/v1/statistics

The component should return the current statistics of the component.CSIT - DONE

Triggered by merges in policy/pap

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Lab
1Perform healthcheck of the componentPAP docker image is available

API – healthcheck

Method - GET

Endpoint: https://<host>:6969/policy/pap/v1/healthcheck

The component should return health status as “true”

CSIT - DONE

External Lab - DONE

2Query component for statisticsPAP docker image is available

API - statistics

Method - GET

Endpoint: https://<host>:6969/policy/pap/v1/statistics

The component should return the current statistics of the component.

CSIT - DONE

External Lab

3Query pdp group informationPAP docker image is available

API - pdps

Method - GET

Endpoint: https:{url}:{port}/policy/pap/v1/pdps

The component should return the list of PDP groups and subgroups together with the policies that are deployed on each PDP group and subgroup.CSIT - DONE
4Create PDP group & subgroupPAP docker image is available

API - pdps

Method - POST

Endpoint: https:{url}:{port}/policy/pap/v1/pdps

The component should create the relevant PDP group & subgroup in the database and return with operation success message/code.CSIT - DONE
5Create a PolicyAPI docker image is available

APIpolicytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

Method - POST

Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

The Policy API should return code 201 and message "A new policy has been successfully created."CSIT
6Deploy policy to PDP group & subgroup

PAP docker image is available

API docker image is available

DMaaP simulator docker image is needed; a PDP can be simulated using curl


API - pdps

Method - POST

Endpoint: https:{url}:{port}/policy/pap/v1/pdps

The component should map the relevant policies with the corresponding PDP group & subgroup in database. Deploy the policy in relevant PDP and return with operation success message/code.CSIT
7UNDeploy policy to PDP group & subgroup

PAP docker image is available

API docker image is available

NOTE: PDP's not needed for this test in Dublin.

API - pdps

Method - POST

Endpoint: https:{url}:{port}/policy/pap/v1/pdps

Based on test #5 - undeploy those policiesCSIT - DONE
8Query pdp group statistics

PAP docker image is available

PDP docker image is available

API - pdps

Method - GET

Endpoint: https:{url}:{port}/policy/pap/v1/pdps/statistics

The PAP component must return the statistics for PDP groups, subgroups and individual PDPs.

CSIT (Not done in this release)

The API will be implemented in next release.

9Delete PDP group & subgroup

PAP docker image is available

PDP docker image is available

API - pdps

Method - DELETE

Endpoint: https:{url}:{port}/policy/pap/v1/pdps?name=<group_name>&version=<version>

The component should delete the relevant PDP group & subgroup from database and kill the corresponding PDP instances (running as kubernetes pods). Finally, return with operation success message/code.

CSIT (Not done in this release)

The API will be implemented in next release.


Triggered by merges in policy/drools-pdp

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Labs
1AliveVerify that base barebone PDP-D comes alive

API – telemetry

Method - GET

Endpoint: https://<host>:9696/policy/pdpd/v1/engine

Verify alive fieldCSIT-DONE
2 (stretch)Dynamic Controller CreationVerify dynamic addition of a PDP-D controller

API – telemetry

Method - GET

Endpoint: https://<host>:9696/policy/pdpd/v1/controllers/<controller>

Verify that the dynamically create controller is alive.CSIT
3 (stretch)Dynamic Controller TrafficVerify that PDP-D can process traffic for the controller created in step-2.

API – telemetry

Method - GET

Endpoint: https://<host>:9696/policy/pdpd/v1/controllers/<controller>/drools

Verify that the events structure contains input and expected output messages.CSIT


Triggered by merges in policy/drools-applications

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Labs
1HealthcheckVerify that base barebone PDP-D comes alive

API – telemetry

Method - GET

Endpoint: https://<host>:6969/policy/pdpd/v1/engine/healthcheck

Verify healthcheckCSIT
2vFW

Verify vFW use case.

Simulators should be installed.

  1. Add vFW Operational Policy
  2. Inject ONSET
  3. Trace the vFW use case across the complete sequence of messages
Verify vFirewall completes successfullyCSIT
3vDNS

Verify Scale out use case.

Simulators should be installed.

  1. Add vDNS Operational Policy
  2. Inject ONSET
  3. Trace the vDNS use case across complete sequence of messages
Verify scale out completes successfullyCSIT
4vCPE

Verify vCPE use case.

Simulators should be installed.

  1. Add vCPE Operational Policy
  2. Inject ONSET
  3. Trace the vCPE use case across the complete sequence of messages
Verify vCPE completes successfullyCSIT

Triggered by merges in policy/xacml-pdp

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Lab
1Health CheckXacml-PDP docker image available

API – healthcheck

Method - GET

Endpoint: http://<host>:6969/policy/pdpx/v1/healthcheck

The component should return health status as “true”

Status code 200

CSIT - DONE

External Lab

2StatisticsXacml-PDP docker image available

API – statistics

Method - GET

Endpoint: http://<host>:6969/policy/pdpx/v1/statistics

The Xacml PDP should return statistics report consisting of 0 policies loaded and 0 decisions

Status code 200


CSIT - DONE
3Create policyAPI docker image available

APIpolicytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

Method - POST

Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

The Policy API should return code 201 and message "A new policy has been successfully created."CSIT
3Deploy Policy

Xacml-PDP and PAP docker images available

Policy created on the PAP

API – deployPolicy

Method - POST

Endpoint: http://<host>:6969/policy/pdpx/v1/deployPolicy

Successfully deploy a policy to the XACML PDP

Statistics should increment policy count

Status code 201

CSIT/External Lab (stretch)
4Statistics

Xacml-PDP and PAP docker images available

Test Case 3 success

API – statistics

Method - GET

Endpoint: http://<host>:6969/policy/pdpx/v1/statistics

The Xacml PDP should return statistics report consisting of 1 policy loaded and 0 decisions

Status code 200

CSIT
5Decision API

Xacml-PDP docker image available

Test Case 4 success

API – decision

Method - POST

Endpoint: http://<host>:6969/policy/pdpx/v1/decision

The Xacml PDP should return a Decision object containing the decision

Statistics should increment decision count

Status code 200

CSIT/External Lab (stretch)
6Statistics

Xacml-PDP docker image available

Test Case 5 success

API – statistics

Method - GET

Endpoint: http://<host>:6969/policy/pdpx/v1/statistics

Xacml PDP should return a statistics report consisting of 1 policy loaded and 1 decisions

Status code 200

CSIT
7Undeploy Policy

Xacml-PDP and PAP docker images available


API – deployPolicy

Method - POST

Endpoint: http://<host>:6969/policy/pdpx/v1/undeployPolicy

Successfully undeploy of policy from the Xacml PDP

Statistics should decrement the policy count

Status code 201

CSIT
8Statistics

Xacml-PDP docker image available

Test Case 7 success

API – statistics

Method - GET

Endpoint: http://<host>:6969/policy/pdpx/v1/statistics

Xacml PDP should return a statistics report consisting of 0 policies loaded and 1 decision

Status code 200

CSIT


Triggered by merges in policy/apex-pdp

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Labs

1

Perform healthcheck of the component


Apex PDP docker image is available

API – healthcheck

Method - GET

Endpoint: https://<host>:6969/policy/apex-pdp/v1/healthcheck

The component should return health status as “true”

CSIT - DONE

External Lab

2Query component for statisticsApex PDP docker image is available

API - statistics

Method - GET

Endpoint: https://<host>:6969/policy/apex-pdp/v1/statistics

The component should return the current statistics of the component.CSIT (Stretch)

3

Create Operational policies for the following use cases  

  • SampleDomain
  • BBS (if this is not a POC)

Policy components up and running

(Will be added once API page approved)

(Current integration tests for REST client moved to CSIT)

Operational Policy should be created in apex-pdp

CSIT (Stretch)


Triggered by merges in policy/api

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT External Labs

1

Perform healthcheck for policy design API service


  • Policy API docker image available

API – healthcheck

Method - GET

Endpoint: http://<host>:6969/policy/api/v1/healthcheck

The Policy API should return health status as “true”

CSIT - DONE

External Lab -

2Retrieve statistics of policy design API invocation
  • Policy API docker image available

API – statistics

Method - GET

Endpoint: http://<host>:6969/policy/api/v1/statistics

The Policy API should return API invocation statistics report with code set to "200"

CSIT - DONE

External Lab -

3Retrieve pre-loaded generic policy types
  • Policy API docker image available

API – policytypes

Method - GET

Endpoint: http://<host>:6969/policy/api/v1/policytypes

The Policy API should return a list of pre-loaded generic policy typesCSIT-DONE
4Create a new TCA policy type for DCAE TCA microservice
  • Policy API docker image available
  • DCAE TCA ms policy type is not created yet

API – policytypes

Method - POST

Endpoint: http://<host>:6969/policy/api/v1/policytypes

The Policy API should return code 201 and message "A new policy type has been successfully created."CSIT-DONE
5Retrieve Monitoring related policy types
  • Policy API docker image available
  • DCAE TCA ms policy type is created

API – policytypes/onap.policies.Monitoring

Method - GET

Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring

The Policy API should return a list of onap.policies.Monitoring and derived onap.policies.Monitoring.cdap.tca.hi.lo.app policy typesCSIT-DONE
6Create a new Monitoring TCA policy
  • Policy API docker image available
  • onap.policies.Monitoring.cdap.tca.hi.lo.app version 1.0.0 policy type has been created

APIpolicytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

Method - POST

Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

The Policy API should return code 201 and message "A new policy has been successfully created."CSIT-DONE
7Retrieve  all policies created for a specific policy type
  • Policy API docker image available
  • onap.policies.Monitoring.cdap.tca.hi.lo.app version 1.0.0 policy type has been created
  • onap.restart.tca policy has been created

API – policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

Method - GET

Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies

The Policy API should return a list of policies that have been created for onap.policies.Monitoring.cdap.tca.hi.lo.app version 1.0.0 policy type, including onap.restart.tcaCSIT-DONE
8Delete one specific version of a policy
  • Policy API docker image available
  • onap.policies.Monitoring.cdap.tca.hi.lo.app version 1.0.0 policy type has been created
  • onap.restart.tca version 1.0.0 policy has been created

API –  policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies/onap.restart.tca/versions/1.0.0

Method - DELETE

Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies/onap.restart.tca/versions/1.0.0

The Policy API should delete specific version of onap.restart.tca policy and return code 200 with Non-NULL response.

Second Call for same version would return 404.

CSIT-DONE

1 Comment

  1. With regards to healthchecks, I think we are at least partially in sync, almost all there perhaps with the exception on 2 below.    I can modify page once we all confirm.

    1. global legacy healthchecks - going through pdp-d endpoint, to reflect status of pdp-d, legacy-pap, legacy-pdp-x - after merges in  drools-pdp, drools-applications, engine, and common repos.
    2. global new healthchecks (new architecture) - going threw new pap after merge changes in pap, distribution, drools-pdp, drools-applications, models, api, pdp, and common repos.
    3. single component healthcheck, addressing all components individually on a per repo basis.