airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saminda Wijeratne (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AIRAVATA-1301) Update Airavata 0.13 to support workflows
Date Wed, 25 Jun 2014 17:18:27 GMT

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

Saminda Wijeratne edited comment on AIRAVATA-1301 at 6/25/14 5:17 PM:
----------------------------------------------------------------------

After a few offline discussions we came up with the following steps to achieve this,

1. Updating Orchcestrator CPI to add launchTask(...) and deprecate/remove launchExperiment(...)
2. Update TaskDetails thrift model object so that we can move the host selecting scheduling
part that is currently in gfac to the orchestrator and save it in taskdetails. the GFac will
use this information to create the JEC (job execution context)
3. Introduce a new workflow submitter (similar to a jobsubmitter for gfac) class to trigger
the updated workflow interpreter
4. Update the workflow interpreter to
----a. use the new registry for saving and retrieving workflow and node data
----b. call the orchestrator when required to launch tasks related to a workflow node
----c. use the monitor publisher to do task status monitor to update node statuses and take
workflow execution decisions
5. Update the API to allow launching workflows
6. Update the thrift API service to launch single apps and workflows

note: these steps will trigger considerable registry changes and updates to scheduling in
gfac changes


was (Author: samindaw):
After a few offline discussions we came up with the following steps to achieve this,

1. Updating Orchcestrator CPI to add launchTask(...) and deprecate/remove launchExperiment(...)
2. Update TaskDetails thrift model object so that we can move the host selecting scheduling
part that is currently in gfac to the orchestrator and save it in taskdetails. the GFac will
use this information to create the JEC (job execution context)
3. Introduce a new workflow submitter (similar to a jobsubmitter for gfac) class to trigger
the updated workflow interpreter
4. Update the workflow interpreter to
          a. use the new registry for saving and retrieving workflow and node data
          b. call the orchestrator when required to launch tasks related to a workflow node
          c. use the monitor publisher to do task status monitor to update node statuses and
take workflow execution decisions
5. Update the API to allow launching workflows
6. Update the thrift API service to launch single apps and workflows

> Update Airavata 0.13 to support workflows
> -----------------------------------------
>
>                 Key: AIRAVATA-1301
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1301
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Saminda Wijeratne
>            Assignee: Saminda Wijeratne
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message