airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shameera Rathnayaka (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRAVATA-1426) Handle Job Restriction in Orchestrator Level
Date Mon, 11 Jul 2016 21:10:12 GMT

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

Shameera Rathnayaka updated AIRAVATA-1426:
------------------------------------------
    Fix Version/s:     (was: 0.16)
                   0.17 

> 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.17 
>
>
> 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)

Mime
View raw message