You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Saurabh Agrawal (JIRA)" <ji...@apache.org> on 2017/12/16 07:30:00 UTC

[jira] [Updated] (AIRAVATA-2555) Standardizing Workflow execution by using CWL

     [ https://issues.apache.org/jira/browse/AIRAVATA-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saurabh Agrawal updated AIRAVATA-2555:
--------------------------------------
    Description: 
[Pull request|https://github.com/apache/airavata-sandbox/pull/35]
*Wikis*
* [Assignment 4|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-4]
* [Assignment 5|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-5]
* [Assignment 6|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-6]
* [Assignment 7|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-7]

The current workflow execution and monitoring are not very user-friendly.
We would like to make these simpler and use standard technologies.

The goals of this project are as follows:
1) A specification for passing task DAG information from the client to the Airavata API
2) Interpreting the DAG inside workflow engine
3) Executing and monitoring the tasks

1) A specification for passing task DAG information from the client to the Airavata API:
We are considering [Common Workflow Language|https://github.com/common-workflow-language/common-workflow-language]

2) Interpreting the DAG inside workflow engine: We considered [Airflow|https://airflow.incubator.apache.org/], but it is probably not the best fit for our requirements. We are currently looking at [CWL tool|https://github.com/common-workflow-language/cwltool]

3) Executing and monitoring the tasks: Need to confirm whether to keep this task in this project or not

  was:
[Pull request|https://github.com/apache/airavata-sandbox/pull/35]
**Wikis**
* [Assignment 4|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-4]
* [Assignment 5|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-5]
* [Assignment 6|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-6]
* [Assignment 7|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-7]

The current workflow execution and monitoring are not very user-friendly.
We would like to make these simpler and use standard technologies.

The goals of this project are as follows:
1) A specification for passing task DAG information from the client to the Airavata API
2) Interpreting the DAG inside workflow engine
3) Executing and monitoring the tasks

1) A specification for passing task DAG information from the client to the Airavata API:
We are considering [Common Workflow Language|https://github.com/common-workflow-language/common-workflow-language]

2) Interpreting the DAG inside workflow engine: We considered [Airflow|https://airflow.incubator.apache.org/], but it is probably not the best fit for our requirements. We are currently looking at [CWL tool|https://github.com/common-workflow-language/cwltool]

3) Executing and monitoring the tasks: Need to confirm whether to keep this task in this project or not


> Standardizing Workflow execution by using CWL
> ---------------------------------------------
>
>                 Key: AIRAVATA-2555
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2555
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Workflow Engine, Workflow Tracking
>            Reporter: Saurabh Agrawal
>            Assignee: Saurabh Agrawal
>
> [Pull request|https://github.com/apache/airavata-sandbox/pull/35]
> *Wikis*
> * [Assignment 4|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-4]
> * [Assignment 5|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-5]
> * [Assignment 6|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-6]
> * [Assignment 7|https://github.com/saurabhagrawal0412/airavata-sandbox/wiki/Assignment-7]
> The current workflow execution and monitoring are not very user-friendly.
> We would like to make these simpler and use standard technologies.
> The goals of this project are as follows:
> 1) A specification for passing task DAG information from the client to the Airavata API
> 2) Interpreting the DAG inside workflow engine
> 3) Executing and monitoring the tasks
> 1) A specification for passing task DAG information from the client to the Airavata API:
> We are considering [Common Workflow Language|https://github.com/common-workflow-language/common-workflow-language]
> 2) Interpreting the DAG inside workflow engine: We considered [Airflow|https://airflow.incubator.apache.org/], but it is probably not the best fit for our requirements. We are currently looking at [CWL tool|https://github.com/common-workflow-language/cwltool]
> 3) Executing and monitoring the tasks: Need to confirm whether to keep this task in this project or not



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)