Work in progress
Table of Contents |
---|
Brief introduction
Definitions and abbreviations
AC = analytic component
CL = control loop
TCA
Holmes
ONAP artifacts descriptions
Describes ONAP artifacts used in various scenarios in this document.
DCAE blueprint
- used in SDC to describe AC
- TOSCA-based (YAML)
- artifact name needs to end with event_proc.bp
- example name: dcae_blueprint.event_proc_bp.yaml
- example name: dcae_blueprint.event_proc_bp.yaml
...
title | Example DCAE blueprint (TCA) |
---|
...
Work in progress
Table of Contents | ||
---|---|---|
|
Brief introduction
Definitions and abbreviations
AC = analytic component
CL = control loop
TCA
Holmes
ONAP artifacts descriptions
Describes ONAP artifacts used in various scenarios in this document.
DCAE blueprint
- used in SDC to describe AC
- TOSCA-based (YAML)
- artifact name needs to end with event_proc.bp
- example name: dcae_blueprint.event_proc_bp.yaml
- example name: dcae_blueprint.event_proc_bp.yaml
Expand | ||
---|---|---|
| ||
|
Micro-service schema
Schema that can be used by Tosca Lab (SDC DCAE-D Tosca Lab) to generate Micro-service policy model (more info: MicroServices Onboarding in ONAP)
Expand | ||
---|---|---|
|
Micro-service policy model
Model generated by tosca lab. It's currently not used. It could be translated into Micro-service policy schema.
Expand | ||
---|---|---|
|
Micro-service policy schema
Schema that currently can by used by Policy to generate form to configure Micro-service policy
Expand |
---|
{CONFIG_BINDING_SERVICE: "config_binding_service" ports: - concat: ["11011:", { get_input: external_port }] tca_policy: type: dcae.nodes.policy properties: policy_id: get_input: policy_id |
Micro-service config policy
...
"param2": "java.lang.String:defaultValue-NA:required-false:MANY-true", |
Micro-service policy (instance)
Configured micro-service policy. In this case Clamp is creating it using Policy API.
e.g. in Beijing TCA configuration Micro-service policy contains information about metrics and tresholds
Operational policy (instance)
Policy with configured Drools Rule. In this case Clamp is creating it using Policy API.
e.g. in Beijing this policy decided whether to start APPC LCM or not.
Current control loop design and execution
Stages required to run control loop:
AC blueprint design (SDC)
AC blueprint distribution (SDC)
- AC/
CL configuration (CLAMP)
CL submit (CLAMP)
CL deploy (CLAMP)
Desired control loop design and execution
Stages required to run control loop:
Deployment Artifact design using SDC DCAE-D
Currently we are able to write schema json and using tosca-lab (example: tcaSpec.json) create artifacts out of it. Required artifactsIn this step user should design and add to service 2 deployment artifacts:
AC blueprint (DCAE_BLUEPRINT)
Policy model (example: policy.yaml)
Distribution of CSAR containing Policy model and AC blueprint (SDC)
AC/CL- Both Policy and Clamp should receive Artifact distribution notification.
Gliffy name Policy Model saving (Policy) pagePin 510 Gliffy name CL model saving (Clamp) pagePin 1
- Both Policy and Clamp should receive Artifact distribution notification.
Both Policy and Clamp should receive Artifact distribution notification.
6
AC configuration (CLAMP)
Gliffy name Generic AT Policy Configuration pagePin 2 - Policy should extract logic of creating forms for configuring Policy using micro-service policy schema (in this confluence it's called Policy SDK)
- Clamp should use Policy SDK to create generic form out of saved micro-service policy schema.
Action Policy configuration (CLAMP)
- CL
CL submit (CLAMP)
CL deploy (CLAMP)