airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRAVATA-2063) When QOS added in one gateway (seagrid) it is also taken as the qos of the other gateway (testdrive) linked with airavata
Date Wed, 01 Mar 2017 16:15:46 GMT

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

Eroma updated AIRAVATA-2063:
----------------------------
    Fix Version/s: 0.17

> When QOS added in one gateway (seagrid) it is also taken as the qos of the other gateway
(testdrive) linked with airavata
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2063
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2063
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata System, PGA PHP Web Gateway
>         Environment: dev.seagrid.org
> dev.testdrive.org
>            Reporter: Eroma
>            Assignee: Shameera Rathnayaka
>             Fix For: 0.17
>
>
> Ideally the qos assigned in seagrid gateway comet queues should not be considered by
testdrive gateway. qos is gateway specific, resource specific and queue specific.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message