You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2019/03/21 16:28:00 UTC

[jira] [Updated] (AIRAVATA-3000) [GSoC] Refactor parser framework into a generic workflow framework

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

Suresh Marru updated AIRAVATA-3000:
-----------------------------------
    Labels: gsoc2019  (was: )

> [GSoC] Refactor parser framework into a generic workflow framework
> ------------------------------------------------------------------
>
>                 Key: AIRAVATA-3000
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3000
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Dimuthu Upeksha
>            Priority: Major
>              Labels: gsoc2019
>
> This an extension of the work we have done in GSoC 2018. Yasas has worked on developing a workflow framework for Airavata and his mail list discussions and medium post can be found from [1] [2]. Based on his research and the another GSoC project which was done in integrating a parser framework for Airavata, we have developed a new parser framework [3] [4] [5] [6] which utilized Apache Helix task framework [7] as the task execution engine. 
> Even though this framework was specifically developed for parsers, we feel that this implementation shares a lot of common features of the workflow design which Yasas has worked on. So in this project we need to generalize parser framework into a generic workflow framework where we can create and launch workflows with any application registered in Airavata
> Student should be good at Java and distributed system concepts
> Key Expectations
>  # Refactor/ improve parser data models into workflow data models
>  # Refactor/ improve parser tables into workflow database tables
>  # Implement new helix tasks to support workflow operations mentioned in [2]
>  # Refactor/ improve parser API into a workflow level API [5]
>  # Demonstrate that we can still preserve parser workflows in newly created generic workflow engine (This will be final demo). 
> [1] [https://medium.com/@yasgun/gsoc-2018-with-apache-airavata-user-defined-airavata-workflows-39f0e79234ee]
> [2] [http://mail-archives.apache.org/mod_mbox/airavata-dev/201806.mbox/browser]
> [3] [https://github.com/apache/airavata/tree/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/parsing]
> [4] [https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/workflow/ParserWorkflowManager.java]
> [5] [https://github.com/apache/airavata/blob/develop/thrift-interface-descriptions/airavata-apis/airavata_api.thrift#L3505]
> [6] https://github.com/apache/airavata/blob/develop/thrift-interface-descriptions/data-models/app-catalog-models/parser_model.thrift
> [7] [https://helix.apache.org/0.8.4-docs/tutorial_task_framework.html]
>  



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