...
Joseph O'Leary to pad out this section
node_templates
which makes up the loop itself.
Applications can be a DCAE microservice, an operational policy, or any other application as long as it can be modelled, and the targeted ecosystem to has a participant client waiting for the event distributions from CLAMP via DMaaP MR.
2.1: Control Loop TOSCA file definition
2.1.1 Application DefinitionÂ
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
org.onap.APP:
properties:
application_name:
type: string
description: Human readable name for the application.
required: true
provider:
type: string
description: Provider of the application and of the descriptor.
required: true
application_version:
type: string
description: Software version of the application.
required: true
resource_id:
type: string
description: The ID of the resource, should be provided if the resource was uploaded to the entitys inventory already.
required: false
resource_content:
type: string
description: the contents of the application 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 |
2.1.2 Loop Definition
The loop definition is implicit in the node_templates
within the topology_template
, any node contained within is expected to be a part of the control loop managed by CLAMP.
2.1: Modelling from TOSCA to Deployment Data in Run Time Catalogue
...