Page History

...

startPhase:
  type: integer
  required: false
  constraints:
  - greater-or-equal: 0
  description: A value indicating the start phase in which this control loop element will be started, the
               first start phase is zero. Control Loop Elements are started in their start_phase order and stopped
               in reverse start phase order. Control Loop Elements with the same start phase are started and
               stopped simultaneously
  metadata:
    common: true

The "common: true" value in the metadata of the startPhase property identifies that property as being a common property. This property will be set on the CLAMP GUI during control loop commissioning.

2.3 Instance Specific Properties

Instance Specific  properties apply to individual instances of a Control Loop and/or Control Loop Element and must be set individually for Control Loop and Control Loop Element instance. Properties are instance specific by default, but can be identified by a special metadata flag in Control Loop and Control Loop Element definitions. For example, the chart parameter on a Policy Control Loop Element has a different value for evey instance of a Policy Control Loop Element, so it can be defined as shown below in the  <INSERT LINK HERE WHEN IT IS MERGED>  yaml file.

# Definition that omits the common flag metadata
policyType:
  type: onap.datatypes.ToscaConceptIdentifier
  required: true

# Definition that specifies the common flag metadata
policyType:
  type: onap.datatypes.ToscaConceptIdentifier
  required: true
  metadata:
    common: false

The "common: false" value in the metadata of the policyId property identifies that property as being an instance specific property. This property will be set on the CLAMP GUI during control loop instantiation.

A Control Loop Definition is made up of several components, those which represent applications, those which represent dynamic config schemas, and the actual node_templates which makes up the loop itself.

...