...
The Design Time Catalogue contains the the metadata primitives for composition of control loops. As shown in the figure above, the Design time component provides a system where Control Loops can be designed and defined in metadata. This means that a Control Loop can have any arbitrary structure and the Control Loop developers can use whatever analytic, policy, or control primitives they like to implement their Control Loop. At deployment time, the user parameterises the Control Loop and deploys it. A design time catalogue is created. This catalogue contains the primitive metadata for any components that can be used to compose a Control Loop. A Control Loop SDK is used to compose a Control Loop by aggregating the metadata for the components chosen to be used in a Control Loop and by constructing the references between the components.
...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
node_types: org.onap.CL_Component: properties: component_name: type: string description: Human readable name for the component. required: true provider: type: string description: Provider of the component and of the descriptor. required: true component_version: type: string description: Software version of the component. required: true resource_id: type: string description: >The ID of the resource, should be provided if the resource was uploaded to the entity's inventory already. required: false resource_content: type: string description: the contents of the component resource, to be uploaded during deploy phase of loop. required: false monitoring_policy: type: string description: A reference to the monitoring policy if applicable. required: false version: 0.0.1 derived_from: tosca.nodes.Root |
...