airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2521) Ability define gateway level maximum values for walltime, node and CPU counts
Date Mon, 02 Oct 2017 14:39:02 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188196#comment-16188196
] 

ASF subversion and git services commented on AIRAVATA-2521:
-----------------------------------------------------------

Commit 85c0766dace86296365f975ea0c36b3d6819c696 in airavata-php-gateway's branch refs/heads/develop
from [~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=85c0766 ]

AIRAVATA-2521 Some pull requests fixes


> Ability define gateway level maximum values for walltime, node and CPU counts
> -----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2521
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2521
>             Project: Airavata
>          Issue Type: New Feature
>          Components: PGA PHP Web Gateway
>    Affects Versions: 0.18
>            Reporter: Eroma
>            Assignee: Marcus Christie
>
> Currently at SciGaP level (common and applicable for all the gateways) can provide maximum
values for node, CPUs and walltime. At individual gateway level these values cannot be exceeded
at job submission. 
> The new requirement is to have maximum values set at gateway level, so users cannot exceed
at job submissions. When defining these values at gateway level, should not be able to go
above the SciGaP level maximum values. Only applicable for that particular gateway. The values
should be applicable at create, edit and clone experiment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message