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/09/15 00:24:00 UTC

[jira] [Commented] (AIRAVATA-2143) Experiments with overridden resource allocation details tries to use qos and reservation from community user

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

Eroma commented on AIRAVATA-2143:
---------------------------------

Same issue exists at the latest airavata version. When users have their own allocations set for job submissions, uses that login name but uses the qos set at community account level irrespective of the queue.
user's own login name = xxx
user's allocation project number =ww123

community allocation name =yyy
community allocation project number =ww123
community qos = compute=oneweek

In this scenario, when user submits the job with own login, the job script contains the qos for both compute and shared queues.

> Experiments with overridden resource allocation details tries to use qos and reservation from  community user
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2143
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2143
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Eroma
>             Fix For: 0.18
>
>
> Experiments with overridden resource allocation details tries to use qos and reservation from  community user.
> Remote resource login details sent at experiment creation is used to submit jobs but refers to qos and reservation for the community allocation of the remote resource.



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