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 2017/10/02 16:10:00 UTC

[jira] [Commented] (AIRAVATA-2548) Default values in application deployment is not validated against the gateway level maximum defined values

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

Eroma commented on AIRAVATA-2548:
---------------------------------

Created the issue for recording purposes. This need to be discussed and implemented in a proper way in the application catalog.

> Default values in application deployment is not validated against the gateway level maximum defined values
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2548
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2548
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>    Affects Versions: 0.18
>         Environment: https://dev.seagrid.org
>            Reporter: Eroma
>
> Gateway level maximum values for node and CPU are given in pga_config.php and those are not checked when giving defaults values for node and CPU in application deployment.
> When admin provides default values in application deployment should not be able to define over the values given as maximum values in config file.



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