...
- Create the MS specific blueprint, component_spec and associated data_format based on DCAE team specification (refer to details under DCAE wiki page - Dublin Deployment Strategy DCAE Service Component (MS) Deployment Options).
Note: For components with dynamic configuration, the component spec MUST include policy schema definition (policy_editable set for required parameter exposed via policy with corresponding policy_schema defined) - Use SDC/ToscaLab tool as documented here to create the base policy model. More about how to create policy types from tosca tool can be found here -> Policy type creation
Note: If the policy model does not get generated, change the "component_type" from "docker" to "cdap" in the componentspec and retry policy model creation.
The base policy model created by the tool is not compliant to R4 model expected by Policy and CLAMP; following hence following manual updates will should be required.
done.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
Rename node_types to policy_types
Replace policy.nodes.Root structure with onap.policies.Monitoring
policy.nodes.Root:
derived_from: tosca.nodes.Root
properties:
policyDescription:
required: false
type: string
policyName:
required: true
type: string
policyScope:
required: true
type: string
policyVersion:
required: true
onap.policies.Monitoring:
derived_from: tosca.policies.Root
description: a base policy type for all policies that govern monitoring provision
version : 1.0.0
Rename “policy.nodes.<component_name>” under policy_types as “onap.policies.monitoring.<component_name> and as derived from onap.policies.Monitoring
Example:
onap.policies.monitoring.cdap.tca.hi.lo.app:
derived_from: onap.policies.Monitoring
version : 1.0.0
properties:
tca_policy:
type: list
description: TCA Policy JSON
entry_schema:
type: onap.datatypes.monitoring.tca_policy
Changing data_types to onap complaint name from policy.data prefix to onap.datatypes.monitoring
Example: policy.data.metricsPerEventName -> onap.datatypes.monitoring.metricsPerEventName
policy.data.tca_policy -> onap.datatypes.monitoring.tca_policy
Update each data_types to indicate relation to tosca.datatypes.Root
Example:
onap.datatypes.monitoring.tca_policy:
derived_from: tosca.datatypes.Root |
More about how to create policy types from tosca tool can be found here Policy type creation
Load Policy Model into SDC repo (Development phase)
...
Example TCA Blueprint - https://nexus.onap.org/content/repositories/raw/org.onap.dcaegen2.platform.blueprints/R4/blueprints/k8s-tca-clampnode.yaml
Steps to onboard DCAE blueprints : https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_scaleout.html (applies to all use cases)
For onboarding VNFs and distribute models from SDC: https://wiki.onap.org/display/DW/Design
Configuration and Deployment from CLAMP
...