[ https://issues.apache.org/jira/browse/AIRAVATA-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake resolved AIRAVATA-945. ----------------------------------------- Resolution: Fixed We come up with a data modelwhich contains new job states and used it accross the airavata. these are the states. SUBMITTED(0), UN_SUBMITTED(1), SETUP(2), QUEUED(3), ACTIVE(4), COMPLETE(5), CANCELED(6), FAILED(7), HELD(8), SUSPENDED(9), UNKNOWN(10); Please look in to our thrift datamodel(airavataAPI.thrift) to learn more about the data model. > 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 > Labels: features > Original Estimate: 4h > Remaining Estimate: 4h > > 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.2#6252)