Page History

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 components

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:

http

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

config

and Push Config Policy for the

following

vFW use

cases

vFW
vDNS
vCPE

case.

Policy

components up and running

API – CreateConfig

Method – PUT

Endpoint:

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

Config Policy should be created in Policy Engine (PAP)

4

Push Config policy to the PDP Engines for the following use cases

vFW
vDNS
vCPE

Policy components up and running

(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

5

CSIT - DONE
4	Create

Operational policy

and Push Config Policy for the

following

vDNS use

cases

vFW
vDNS
vCPE

case.

Policy

components up and running

API

- createPolicy Policy components up and running

– CreateConfig

Method – PUT

Endpoint:

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

Operational Policy should be created in Policy Engine (PAP)

6

Push operational Policy to the PDP Engines for each use case

vFW
vDNS
vCPE

(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

Operational

Policy should be pushed to the PDP group

CSIT - DONE

7

5	Create and Push config Policy

Retrieve the configs

for the

following

vCPE use

cases

vFW
vDNS
vCPE

case.

Policy components up and running

API –

getConfig

CreateConfig

Method –

POST

PUT

Endpoint:

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

getConfig

Both Config and Operational Policies configured for each use case should be retrieved successfully

Triggered by merges in policy/distribution

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1

Perform healthcheck of the component

Policy distribution docker image is available

API – healthcheck

Method - GET

Endpoint:

createPolicy

(legacy API)

API - pushPolicy

Method - PUT

Endpoint:

https:// <host>:

6969

8081/

policy

pdp/

distribution

api/

v1/healthcheck

The component should return health status as “true”

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.

Triggered by merges in policy/pap (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1Perform healthcheck of the componentPAP docker image is available

API – healthcheck

Method - GET

Endpoint:

pushPolicy

(legacy API)

Config Policy should be created in Policy Engine (PAP)

and

Config Policy should be pushed to the PDP group

CSIT-DONE

6

Create and Push vFW SDNC Naming policy

Policy 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

7

Create and Push vPG SDNC Naming policy

Policy components up and running

API - createPolicy

Method - PUT

Endpoint:

https:// <host>:

6969

8081/

policy

pdp/

pap

API - statistics

Method - GET

Endpoint:

api/

v1/healthcheckThe component should return health status as “true”2Query component for statisticsPAP docker image is available

createPolicy

Naming policy should be created in Policy Engine

CSIT - DONE

8

Create and Push Operational policy for vFW use case

Policy components up and running

API - createPolicy

Method – PUT

Endpoint:

https://<host>:

6969

8081/

policy

pdp/

pap/v1/statisticsThe component should return the current statistics of the component.3Query pdp group informationPAP docker image is available

API - pdps

Method - GET

Endpoint: https:{url}:{port}/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.4Create PDP group & subgroupPAP docker image is available

API - pdps

Method - POST

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

The component should create the relevant PDP group & subgroup in the database and return with operation success message/code.5Deploy policy to PDP group & subgroup

PAP docker image is available

API - pdps

Method - POST

Endpoint: https:{url}:{port}/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.6Query pdp group statistics

PAP docker image is available

PDP docker image is available

API - pdps

Method - GET

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

The PAP component must return the statistics for PDP groups, subgroups and individual PDPs.7Delete PDP group & subgroup

PAP docker image is available

PDP docker image is available

API - pdps

Method - DELETE

Endpoint: https:{url}:{port}/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.

Triggered by merges in policy/drools-pdp (NOT FINISHED)

...

Test Case Id

...

Description

...

Pre-conditions

...

Test Steps

...

Expected Results

...

Triggered by merges in policy/xacml-pdp (NOT FINISHED)

...

Test Case Id

...

Description

...

Pre-conditions

...

Test Steps

...

Expected Results

...

Xacml-PDP docker image available

...

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
10	Create and Push Operational Policy to the PDP Engines for vCPE 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
11	Create and Push Operational Policy to the PDP Engines for VOLTE 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
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 successfully	CSIT - DONE
14	Retrieve the Configs for the vCPE 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
15	List Configuration Policies	List all configuration policies	API – listPolicy Method – POST Endpoint: https://<host>:8081/pdp/api/listPolicy	Should list all configuration policies	CSIT-Done
16	Get 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
17	Create 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 policy	CSIT-Done
18	Create and Push multiple policies	Create and push multiple operational policies	API - pushPolicy Method - PUT Endpoint: https:// <host>:8081/pdp/api/pushPolicy	Should create and push 3 operational policies	CSIT - Done
19	Delete multiple policies	Delete 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

2

Query component for statistics

Policy 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
1	Perform healthcheck of the component	PAP 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
2	Query component for statistics	PAP 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
3	Query pdp group information	PAP 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
4	Create PDP group & subgroup	PAP 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
5	Create a Policy	API docker image is available	API – policytypes/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
6	Deploy 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
7	UNDeploy 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 policies	CSIT - DONE
8	~~Query 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.~~
9	~~Delete 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

1

Alive

Verify that base barebone PDP-D comes alive

API – telemetry

Method - GET

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

Verify alive field

CSIT-DONE

2 (stretch)

Dynamic Controller Creation

Verify 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 Traffic

Verify 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
1	Healthcheck	Verify that base barebone PDP-D comes alive	API – telemetry Method - GET Endpoint: https://<host>:6969/policy/pdpd/v1/engine/healthcheck	Verify healthcheck	CSIT
2	vFW	Verify vFW use case. Simulators should be installed.	Add vFW Operational Policy Inject ONSET Trace the vFW use case across the complete sequence of messages	Verify vFirewall completes successfully	CSIT
3	vDNS	Verify Scale out use case. Simulators should be installed.	Add vDNS Operational Policy Inject ONSET Trace the vDNS use case across complete sequence of messages	Verify scale out completes successfully	CSIT
4	vCPE	Verify vCPE use case. Simulators should be installed.	Add vCPE Operational Policy Inject ONSET Trace the vCPE use case across the complete sequence of messages	Verify vCPE completes successfully	CSIT

Triggered by merges in policy/xacml-pdp

Test Case Id	Description	Pre-conditions	Test Steps	Expected Results	CSIT/External Lab
1	Health Check	Xacml-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
2	Statistics	Xacml-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
3	Create policy	API docker image available	API – policytypes/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
3	Deploy 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)
4	Statistics	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
5	Decision 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)
6	Statistics	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
7	Undeploy 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
8	Statistics	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

2

Query component for statistics

Apex 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 -
2	Retrieve 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 -
3	Retrieve 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 types	CSIT-DONE
4	Create 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
5	Retrieve 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 types	CSIT-DONE
6	Create 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	API – policytypes/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
7	Retrieve 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.tca	CSIT-DONE
8	Delete 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

Triggered by merges in policy/apex-pdp (NOT FINISHED)

...

Test Case Id

...

Description

...

Pre-conditions

...

Test Steps

...

Expected Results

...

1

Perform healthcheck for the Policy Apex PDP

...

Apex PDP docker image available

...

API – healthcheck

Method - GET

Endpoint: http://<host>:8081/healthcheck(?)

...

The Apex PDP should return health status as “true”

...

2

...

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 Policy Engine

Policy should fire and return a result

...

Triggered by merges in policy/api (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1

Perform healthcheck for policy design API service

Policy API docker image available

API – healthcheck

Method - GET

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

The Policy API should return health status as “true”

2Retrieve statistics of policy design API invocation

Policy API docker image available

API – statistics

Method - GET

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

The Policy API should return API invocation statistics report with code set to "200"3Retrive pre-loaded generic policy types

Policy API docker image available

API – policytypes

Method - GET

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

The Policy API should return a list of pre-loaded generic policy types4Retrive 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/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 types5Create 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/api/v1/policytypes

The Policy API should return code 200 and message "A new policy type has been successfully created."6Retrieve policies that have been created

Policy API docker image available
onap.scaleout.tca policy has been created

API – policies

Method - GET

Endpoint: http://<host>:6969/api/v1/policies

The Policy API should return a list of policies that have been created, including onap.scaleout.tca7Create a new Monitoring TCA policy

Policy API docker image available
onap.scaleout.tca policy has not been created

API – policies

Method - POST

Endpoint: http://<host>:6969/api/v1/policies

The Policy API should return code 200 and message "A new policy has been successfully created."

Space shortcuts

Page tree

Versions Compared

Old Version 16

New Version Current

Key

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

Triggered by merges in policy/distribution

Triggered by merges in policy/pap (NOT FINISHED)

Triggered by merges in policy/drools-pdp (NOT FINISHED)

Triggered by merges in policy/xacml-pdp (NOT FINISHED)

Triggered by merges in policy/distribution

Triggered by merges in policy/pap

Triggered by merges in policy/drools-pdp

Triggered by merges in policy/drools-applications

Triggered by merges in policy/xacml-pdp

Triggered by merges in policy/apex-pdp

Triggered by merges in policy/api

Triggered by merges in policy/apex-pdp (NOT FINISHED)

Triggered by merges in policy/api (NOT FINISHED)