[
https://issues.apache.org/jira/browse/AIRAVATA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raminderjeet Singh updated AIRAVATA-1044:
-----------------------------------------
Description: 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.
> 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
> 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)
