[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=16358945#comment-16358945 ] ASF subversion and git services commented on AIRAVATA-2143: --- Commit a44fa60e5d1cf853b1b7a13a7b3ca779fdf6bd2b in airavata's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=a44fa60 ] Merge pull request #166 from DImuthuUpe/AIRAVATA-2143 Fixing Airavata-2143 > 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 >Assignee: Dimuthu Upeksha >Priority: Major > 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 (v7.6.3#76005)
[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=16343990#comment-16343990 ] ASF subversion and git services commented on AIRAVATA-2143: --- Commit a44fa60e5d1cf853b1b7a13a7b3ca779fdf6bd2b in airavata's branch refs/heads/master from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=a44fa60 ] Merge pull request #166 from DImuthuUpe/AIRAVATA-2143 Fixing Airavata-2143 > 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 >Assignee: Dimuthu Upeksha >Priority: Major > 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 (v7.6.3#76005)
[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=16343809#comment-16343809 ] Dimuthu Upeksha commented on AIRAVATA-2143: --- Fixed in https://github.com/apache/airavata/pull/166 > 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 >Assignee: Dimuthu Upeksha >Priority: Major > 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 (v7.6.3#76005)
[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=16341508#comment-16341508 ] Eroma commented on AIRAVATA-2143: - Tested in [https://dev.seagrid.org|https://dev.seagrid.org/] Test Cases # Submit a job using gateway preferences of community account. Tested using comet.sdsc.edu shared queue without qos or reservation. - PASS # Submit a job using gateway preferences of community account. Tested using comet.sdsc.edu compute queue with qos. - # Submit a job using gateway preferences of community account. Tested using comet.sdsc.edu compute queue with qos and reservation (Since the actual reservation did not exists checked up to the reservation existence in the job script). - # Submit a job using individual preferences of individual account. Tested using comet.sdsc.edu compute queue without qos or reservation. - PASS # Submit a job using individual preferences of individual account. Tested using comet.sdsc.edu shared queue with qos (Since actual qos did not exist for the account tested up to the qos existence in job script). - # Submit a job using gateway preferences of community account. Tested using comet.sdsc.edu shared queue with qos and reservation (Since the actual qos and reservation did not exists checked up to the reservation existence in the job script). - # Submit a SLURM job to a different SLURM cluster. Tested with Stamepde2. - # Submit a PBS job to a PBS cluster using gateway preferences of community account. Tested with BigRed2. - # Submit a PBS job to a PBS cluster using individual preferences of individual account. Tested with BigRed2. - # User shares the experiment with Write access which was executed using community allocation. Shared user clones and submits using same community account. # User shares the experiment with Write access which was executed using individual allocation. Shared user clones and submits using community account. # User shares the experiment with Write access which was executed using individual allocation. Shared user clones and submits using original user's account. Should not be able to submit using that user's individual allocation. # User shares the experiment with Write access which was executed using individual allocation. Shared user clones and submits using her own allocation account. > 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 >Assignee: Dimuthu Upeksha >Priority: Major > 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 (v7.6.3#76005)
[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=16341371#comment-16341371 ] Eroma commented on AIRAVATA-2143: - Changing the JIRA status on behalf of [~dimuthuupe] > 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 >Assignee: Dimuthu Upeksha >Priority: Major > 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 (v7.6.3#76005)
[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=16341370#comment-16341370 ] Eroma commented on AIRAVATA-2143: - It was also discovered that the individual user's project allocation ID is also not considered. This and the issue with qos and reservation now fixed and deployed in dev.seagrid.org > 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 >Priority: Major > 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 (v7.6.3#76005)
[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=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)
