Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Tue, 4 Mar 2014 18:23:28 +0000 (UTC)
From: "Raminderjeet Singh (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12698515.1393883551279.12381.1393957408386@arcas>
In-Reply-To: <JIRA.12698515.1393883551279@arcas>
References: <JIRA.12698515.1393883551279@arcas>
Subject: [jira] [Assigned] (AIRAVATA-1044) API for monitoring the job state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Raminderjeet Singh reassigned AIRAVATA-1044:
--------------------------------------------

    Assignee: Raminderjeet Singh

> API for monitoring the job state
> --------------------------------
>
>                 Key: AIRAVATA-1044
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1044
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Airavata Client
>            Reporter: Raminderjeet Singh
>            Assignee: Raminderjeet Singh
>             Fix For: 0.12
>
>
> We have Experiment > Task >  DataTransfer, Job Details in the data models with status objects. Status object need to be populated based on airavata client request. Gateways like Ultrscan want to get data transfer status, job status, application status etc but CIPRES just want to know the experiment status and don't care about the lower level status. API need to be designed to address both the use cases. Currently we are saving only job details and data transfer status. We need to identify components to persist other status so we have status at various states in sync.  


--
This message was sent by Atlassian JIRA
(v6.2#6252)