Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Properties are used to define the configuration for Control Loops and Control Loop Elements. At design time, the types, constraints, and descriptions of the properties are specified. The values for properties are specified in the CLAMP GUI at runtime. TOSCA provides support fir defining properties, see Section 3.6.10: TOSCA Property Definition in the TOSCA documentation.

...

Instance Specific Property Value: The value of a Property Type that applies to an individual instance of a Control Loop Type. The value is assigned at run time for each control loop instance.

Control Loop Properties can be common or instance specific. See Section 2 of TOSCA Defined Control Loops: Architecture and Design for a detailed description of the usage of common and instance specific properties.

2.2 Common Properties

Common properties apply to all instances of a control loop. Common properties are identified by a special metadata flag in Control Loop and Control Loop Element definitions. For example, the startPhase parameter on any Control Loop Element has the same value for any instance of that control loop element, so it is defined as shown below in the Definition of TOSCA fundamental Control Loop Types yaml file.


Code Block
languageyml
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




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.

...