[
https://issues.apache.org/jira/browse/ARIA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avia Efrat updated ARIA-375:
----------------------------
Description:
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.
was:
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.
> 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)
