airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AIRAVATA-2521) Ability define gateway level maximum values for walltime, node and CPU counts
Date Tue, 03 Oct 2017 01:37:00 GMT

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

Eroma closed AIRAVATA-2521.
---------------------------

Tested and verified in dev.seagrid.org and dev.testdrive.airavata.org
executed test scenarios
1. Create and save an experiment with new gateway level max values. User should not be able
to go beyond defined.
2. Create and launch an experiment with new gateway level max values. User should not be able
to go beyond defined.
3. Clone an old experiment which has older values greater than gateway level defined max,
try to save.
3. Clone an old experiment which has older values greater than gateway level defined max,
try to save and launch. 
4. Edit previously saved experiment and enter greater values than the maximum and save.
4. Edit previously saved experiment and enter greater values than the maximum and save and
launch. 
5. Try to give default values in application deployment greater than max values defined at
gateway level. - AIRAVATA-2548

When the maximum values are defined the validation is done against the lowest defined value.
If scigap walltime is 96 minutes and pga config is 120, 96 will be the value input walltime
is validated against.

> 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