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

Eroma updated AIRAVATA-3160:
----------------------------
    Priority: Minor  (was: Major)

> When creating group resource profile, user can give more than the maximum 
> node, CPU and walltime defined for the compute resrouce
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-3160
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3160
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Django Portal
>    Affects Versions: 0.18
>         Environment: https://django.staging.seagrid.org
>            Reporter: Eroma
>            Assignee: Marcus Christie
>            Priority: Minor
>
> 1. User creates a own group resource profile
> 2. When adding queue policies, can give node, CPU and walltime exceeding the 
> limits defined at compute resource level in SciGaP.
> 3. e.g.: cluster defines for cloud queue 20 nodes, 200 CPUs and 300 walltime 
> as maximum. In group resource profile compute resource queue limits the user 
> can define higher numbers than 20 nodes, 200 CPUs and 300 walltime.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to