airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lahiru Gunathilake (JIRA)" <>
Subject [jira] [Updated] (AIRAVATA-964) Add single job support as a first class simple Apache Airavata Execution
Date Mon, 31 Mar 2014 15:49:20 GMT


Lahiru Gunathilake updated AIRAVATA-964:

    Fix Version/s:     (was: 0.13)

> Add single job support as a first class simple Apache Airavata Execution
> ------------------------------------------------------------------------
>                 Key: AIRAVATA-964
>                 URL:
>             Project: Airavata
>          Issue Type: Epic
>          Components: Airavata Client, GFac
>            Reporter: Suresh Marru
>              Labels: Architecture
>             Fix For: 0.12
>         Attachments: Airavata-Single-Job-Execution.png
> Currently Airavata supports single jobs by wrapping it as a single node task within a
workflow. This wrapping is justified if workflow is the predominant use of Airavata and single
application execution is a rare usage pattern. As Airavata is getting more usage, the simple
execution but for large number of invocations and diverse applications is getting more widely
> Providing a first class way of a simple application execution will reduce the overhead
in creating and managing workflows. But this takes away all the orchestration capabilities
provided by the Workflow Interpreter. This Epic is to discuss a new component to Airavata
which provides based job orchestration while persisting the request state to registry so the
application management component (GFac) can be stateless and recover the job from a frequently
checkpointed state from the registry

This message was sent by Atlassian JIRA

View raw message