ariatosca-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIA-163) Update node state for stub tasks
Date Mon, 08 May 2017 18:36:05 GMT

    [ https://issues.apache.org/jira/browse/ARIA-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001288#comment-16001288
] 

ASF subversion and git services commented on ARIA-163:
------------------------------------------------------

Commit 8ca3ff297b71e270eccdd9a2e6b8bf468ccdab5d in incubator-ariatosca's branch refs/heads/ARIA-148-extra-cli-commands
from [~Mxmrlv]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-ariatosca.git;h=8ca3ff2 ]

ARIA-163 Update node state for empty tasks

Additional changes:
 * removed `for_node` and `for_relationship` from the api OperationTask.
 * api based OperationTask could also have an empty implementation.
 * each core task wields its own executor.
 * Reordered some of the helper functions for creating tasks.
 * intoduced 2 new executors: StubTaskExecutor (for stub tasks) and EmptyOperationExecutor
(for empty tasks)


> Update node state for stub tasks
> --------------------------------
>
>                 Key: ARIA-163
>                 URL: https://issues.apache.org/jira/browse/ARIA-163
>             Project: AriaTosca
>          Issue Type: Story
>    Affects Versions: 0.1.0
>            Reporter: Maxim Orlov
>            Assignee: Maxim Orlov
>             Fix For: 0.1.0
>
>
> Currently each node that has no implementation for an operation, has its operations labeled
a stub tasks. Those stub tasks aren't run through the normal path of the workflow engine,
and thus no update to the state of the node is being done. this should be fixed.
> This ticket should also take care of the following:
>  - Removal of the now-deprecated {{for_node}} and {{for_relationship}} methods for creating
api tasks
>  - Refactoring of the helper "safe methods" for creating API tasks - i.e., the methods
which are currently under {{workflows/builtin/utils.py}} that catch errors for non-existing
operations (missing interface or operation name - as opposed to empty operation declarations).
These methods should be put under {{worfklows/api/tasks.py}} instead.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message