Versions Compared

Key

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

...

Once this call is made, now the models query will display the following available models for policy creation, notice the new "onap.policy.monitoring.cdap.tca.hi.lo.app" domain listed.


Code Block
languagejs
linenumberstrue
collapsetrue
http:{url}:{port}/api/v1/models GET


#TODO UPDATE from above modeling
{
	"policy_domains": [
		{
			"domain": "onap.monitoring",
			"id": "dublin.monitoring.base",
			"description": "This is the base domain that is used to help generate monitoring\ndomains for specific DCAE microservice models.\n",
			"pdp_types": [
				"xacml"
			],
			"version": 1
		},
		{
			"domain": "onap.controlloop.operational",
			"id": "dublin.operational.drools",
			"description": "This is the operational policy domain that support action policies for\ncontrol loops that are supported by the Drools PDP engine.\n",
			"pdp_types": [
				"drools"
			],
			"version": 1
		},
		{
			"domain": "onap.controlloop.operational",
			"id": "dublin.operational.apex",
			"description": "This is the operational policy domain that support action policies for\ncontrol loops that are supported by the Apex PDP engine.\n",
			"pdp_types": [
				"apex"
			],
			"version": 1
		},
		{
			"domain": "onap.controlloop.guard",
			"id": "dublin.guard",
			"description": "This is the XACML based guard policy domain that supports frequency limiter, blacklist/whitelist and min/max guard policies.\n",
			"pdp_types": [
				"xacml"
			],
			"version": 1
		},
		{
			"domain": "onap.controlloop.coordination",
			"id": "dublin.coordination",
			"description": "This is the XACML based guard policy domain that supports frequency limiter, blacklist/whitelist and min/max guard policies.\n",
			"pdp_types": [
				"xacml"
			],
			"version": 1
		},
		{
			"domain": "onap.policy.monitoring.cdap.tca.hi.lo.app",
			"id": "dublin.tca",
			"description": null,
			"pdp_types": [
				"xacml"
			],
			"version": 1
		}
	]
}



...

While designing a control loop using CLAMP, a Control Loop Designer will use the Model Schema for a specific DCAE mS component Policy Model and create a specific Policy.

Code Block
languageyml
linenumberstrue
collapsetrue
tosca_definitions_version: tosca_simple_yaml_1_0_0
imports:
    -
      tca_policy_model.yml
policies:
    -
      onap.scaleout.tca_policy:
        type: policy_nodes.tca
        properties:
            domain: measurementsForVfScaling
            metricsPerEventName: 
            - 
                eventName: vLoadBalancer
                controlLoopSchemaType: VNF
                policyScope: "type=configuration"
                policyName: "configuration.dcae.microservice.tca.xml"
                policyVersion: "v0.0.1"
                thresholds: 
                - 
                    closedLoopControlName: "CL-LBAL-LOW-TRAFFIC-SIG-FB480F95-A453-6F24-B767-FD703241AB1A"
                    closedLoopEventStatus: ONSET
                    version: "1.0.2"
                    fieldPath: "$.event.measurementsForVfScalingFields.vNicPerformanceArray[*].receivedBroadcastPacketsAccumulated"
                    thresholdValue: 500
                    direction: LESS_OR_EQUAL
                    severity: MAJOR
                - 
                    closedLoopControlName: "CL-LBAL-LOW-TRAFFIC-SIG-0C5920A6-B564-8035-C878-0E814352BC2B"
                    closedLoopEventStatus: ONSET
                    version: "1.0.2"
                    fieldPath: "$.event.measurementsForVfScalingFields.vNicPerformanceArray[*].receivedBroadcastPacketsAccumulated"
                    thresholdValue: 5000
                    direction: GREATER_OR_EQUAL
                    severity: CRITICAL

...