[
https://issues.apache.org/jira/browse/AIRAVATA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma closed AIRAVATA-2063.
---------------------------
tested and verified in
testdrive (http://149.165.156.148/) & PGA (http://149.165.156.11/) in JS.
With same comet user in preferences added different QOS and also tested with
adding QOS only in seagrid. Both scenarios worked successfully.
> 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)
