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/06/18 15:53:00 UTC

[jira] [Updated] (AIRAVATA-1426) Handle Job Restriction in Orchestrator Level

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

Eroma updated AIRAVATA-1426:
----------------------------
    Fix Version/s:     (was: 0.15 )
                   0.16

> Handle Job Restriction in Orchestrator Level
> --------------------------------------------
>
>                 Key: AIRAVATA-1426
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1426
>             Project: Airavata
>          Issue Type: Improvement
>    Affects Versions: 0.13
>            Reporter: Shameera Rathnayaka
>            Assignee: Shameera Rathnayaka
>             Fix For: 0.16
>
>
> When user submits a new experiment to the airavata, user selects the resource (Machine) where airavata should run that experiment (Job). That resource may have job count restriction like under one user there can only be have X number of jobs either in Q or R state. So we need to handle this at Orchestrator level rather than handing over the experiment to GFac to submit the jobs where it gets rejected because of that restriction. To do that Orchestrator need to know the job count of particular user in that given resource.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)