[jira] [Commented] (AIRAVATA-2717) [GSoC] Resurrect User-Defined Airavata Workflows

["Yasas Gunarathne (JIRA)" <ji...@apache.org>]

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

Yasas Gunarathne commented on AIRAVATA-2717:
--------------------------------------------

Hi All,

I am a final year undergraduate from the Department of Computer Science and Engineering, University of Moratuwa, Sri Lanka. During last few weeks, I went through the documentations and the code base of Apache Airavata, and deployed it locally to understand its functionalities.

I found this [1] page (last modified on Feb 29, 2016) describing about Airavata workflow requirements, and I want to know whether these requirements are changed or updated. Furthermore, kindly let me know how to proceed in order to apply for this project, since I am really interested in this project for Google Summer of Code 2018. 

[1] [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62685248|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62685248]

Regards

> [GSoC] Resurrect User-Defined Airavata Workflows 
> -------------------------------------------------
>
>                 Key: AIRAVATA-2717
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2717
>             Project: Airavata
>          Issue Type: Epic
>    Affects Versions: 0.17
>            Reporter: Suresh Marru
>            Priority: Major
>              Labels: gsoc2018
>
> Airavata used to support user-defined workflows using an interface XBaya to drag and drop application components to a workspace and define data flow and control flow dependencies among the application nodes. Airavata's workflow system was used for composing, executing, and monitoring workflow graphs primarly web service components. The workflow description was high level abstraction and used to be converted to lower level execution run times like BPEL, SCUFL and Python scripts.
>  
> Airavata has evolved significantly and the current development version is being built-over Apache Helix for DAG orchestration. This provides an opportunity to resurrect workflow capabilities in Airavata. 
> This GSoC project involves finalizing a Airavata Workflow Language; modify the orchestrator to parse user described workflow and translate to equivalent Helix DAG's; execute and monitor the worklfows; develop a simple UI to demonstrate the capabilities. 
> To describe the workflows, you can build on this - [https://docs.google.com/document/d/1eh7BV8CHupxyM2jeqcM2tUG5MnXFt7hNDX4PQDfxCcM/edit] or follow other discussions like - https://issues.apache.org/jira/browse/AIRAVATA-2555 and 
> User community & Impact of the software: Airavata is primarily targeted to build science gateways using computational resources from various disciplines. The initial targeted set of gateways include projects supporting research and education in chemistry, biophysics, and geosciences . The goal of airavata is to enhance productivity of these gateways to utilize cyberinfrastructure of resources (e.g., local lab resources, the Extreme Science and Engineering Discovery Environment (XSEDE), University Clusters, Academic and Commercial Computational Clouds. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)