[
https://issues.apache.org/jira/browse/ARIA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169279#comment-16169279
]
Avia Efrat commented on ARIA-375:
---------------------------------
In v1.1 onwards there are normative TOSCA workflows that are analogous to our
{{install}} and {{uninstall}} workflows - {{deploy}} and {{undeploy}}
[[7.1|http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/cs01/TOSCA-Simple-Profile-YAML-v1.1-cs01.html#_Toc489606747]].
In addition, there are also planned {{scale}} and {{auto-heal}} workflows,
which are yet to be implemented in v1.2.
> Built-in workflows terminology
> ------------------------------
>
> Key: ARIA-375
> URL: https://issues.apache.org/jira/browse/ARIA-375
> Project: AriaTosca
> Issue Type: Task
> Reporter: Ran Ziv
> Priority: Trivial
>
> There are several workflows under the {{workflows/builtin}}
> [package|https://github.com/apache/incubator-ariatosca/blob/0.1.1/aria/orchestrator/workflows/builtin/execute_operation.py]
> which aren't in fact TOSCA normative workflows - yet they are built-in in
> ARIA (i.e. don't require manual declaration by users as custom workflows,
> using the {{aria.Workflow}} policy type).
> There might be room for a change in terminology (perhaps "core workflows" as
> opposed to "builtin"?).
> Beyond that, it might be better not to have any non-normative TOSCA workflows
> be part of the services anyway - and instead have these workflows declared in
> {{aria-1.0.yaml}}, to be optional built-in custom workflows.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
