THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Currently ONAP uses a TOSCA 1.1 Simple YAML profile to create service models. However, these models cannot be validated by AriaTosca until it supports 1.1 (AriaTosca currently supports 1.0 only).
Service-template Type
The extension of the service-template can be 'yaml' or 'yml'. Currently, aria supports only 'yaml' extension.
Changes/Updates from Simple Profile 1.0
...
Updated to support the common keynames listed in newly added abstract type TOSCA Entity Schema. This TOSCA Entity Schema includes four properties named derived_from, version, metadata, description. metadata in the new property which will get added to all these types.
| Key | Type | Mandatory | Description |
|---|---|---|---|
| metadata | map of Strings | No | Defines a section used to declare additional metadata information. |
Example:
<Type_name>:
type: <TOSCA type>
metadata:
creation_date: 2015-04-14
date_updated: 2015-05-01
status: developmental
3.6.10
...
Group Type
Following three new attributes added.
...
| Attribute | Type | Mandatory | Description |
|---|---|---|---|
| attributes | List of attributed definitions | No | An optional list of attribute definitions for the Group Type |
...
| requirements |
...
| List of requirements definitions | No | An optional sequenced list of requirement definitions for the Group Type. | |
| capabilities |
...
| List of capabilities definitions | No | An optional list of capability definitions for the Group Type. |
Example:
3.6.12 Policy Type
Following new attribute added.
| Attribute | Type | Mandatory |
|---|
...
| Description | |||
|---|---|---|---|
| triggers | List of trigger | No | An optional list of policy triggers for the Policy types |
Example:
Definition of a Trigger
| Keyname | Mandatory | Type | Description |
|---|---|---|---|
description | no | description | The optional description string for the named trigger. |
event_type | yes | string | The required name of the event type that activates the trigger’s action. |
schedule | no | TimeInterval | The optional time interval during which the trigger is valid (i.e., during which the declared actions will be processed). |
target_filter | no | event filter | The optional filter used to locate the attribute to monitor for the trigger’s defined condition. This filter helps locate the TOSCA entity (i.e., node or relationship) or further a specific capability of that entity that contains the attribute to monitor. |
condition | no | constraint clause | The optional condition which contains an attribute constraint that can be monitored. Note: this is optional since sometimes the event occurrence itself is enough to trigger the action. |
constraint | no | constraint clause | The optional condition which contains an attribute constraint that can be monitored. Note: this is optional since sometimes the event occurrence itself is enough to trigger the action. |
period | no | scalar-unit.time | The optional period to use to evaluate for the condition. |
evaluations | no | integer | The optional number of evaluations that must be performed over the period to assert the condition exists. |
method | no | string | The optional statistical method name to use to perform the evaluation of the condition. |
action | yes | string or operation | The if of the workflow to be invoked when the event is triggered and the condition is met (i.e, evaluates to true). Or The required operation to invoke when the event is triggered and the condition is met (i.e., evaluates to true). |
3.7 Template-specific definitions
...