You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2015/04/09 17:08:12 UTC

[jira] [Closed] (AIRAVATA-1044) API for monitoring the job state

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

Eroma closed AIRAVATA-1044.
---------------------------
    Resolution: Fixed

Fixed with adding a API function to get job status.

> 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.14
>
>
> 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.3.4#6332)