airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AIRAVATA-964) Add single job support as a first class simple Apache Airavata Execution
Date Tue, 10 Dec 2013 01:44:07 GMT
Suresh Marru created AIRAVATA-964:
-------------------------------------

             Summary: Add single job support as a first class simple Apache Airavata Execution
                 Key: AIRAVATA-964
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-964
             Project: Airavata
          Issue Type: Epic
          Components: Airavata Client, GFac
            Reporter: Suresh Marru


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 used.


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
(v6.1.4#6159)

Mime
View raw message