airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shahbaz Memon (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AIRAVATA-945) More intuitive Application Job States
Date Fri, 25 Oct 2013 16:24:32 GMT
Shahbaz Memon created AIRAVATA-945:
--------------------------------------

             Summary: More intuitive Application Job States
                 Key: AIRAVATA-945
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-945
             Project: Airavata
          Issue Type: Improvement
          Components: Registry API
            Reporter: Shahbaz Memon
            Priority: Trivial


The current server version can be improved to have more intuitive names of application states.
I would propose to have a label prefix for each state, which clearly identifies whether  it
is a client (airavata provider) or a server side (any middleware) status. For instance, if
there is a working or temp directory being created and any required files are staged in, the
application job status could be set to CLIENT_DIR_SETUP, CLIENT_DIR_CREATED and transition
to CLIENT_DATA_STAGEIN. Similar to that, the status could be set for download actions. 

Another point, in the application status enumeration I am not able to find Queued state, which
is very essential when airavata is used as a proxy for submitting jobs to grid or hpc services.
After applying my thoughts mentioned above, this could be SERVER_QUEUED state. 

Thanks.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message