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 2018/01/29 19:10:00 UTC
[jira] [Comment Edited] (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=16341508#comment-16341508 ]
Eroma edited comment on AIRAVATA-2143 at 1/29/18 7:09 PM:
----------------------------------------------------------
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. - QOS in job script correctly. - PASS
# 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). – QOS and reservation in job script correctly - PASS
# 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). - PASS
# 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). – Job script printed correctly. Observation: Although both QOS and reservation printed in the job script is incorrect, the error is only for the QOS. - PASS
# Submit a SLURM job to a different SLURM cluster with no QOS or reservation. Tested with Stamepde2. - PASS
# Submit a PBS job to a PBS cluster using gateway preferences of community account. Tested with BigRed2 with a project allocation number. - PASS
# Submit a PBS job to a PBS cluster using individual preferences of individual account. Tested with BigRed2. BigRed2 has no allocation number, QOS or reservation - PASS
# User shares the experiment with Write access which was executed using community allocation. Shared user clones and submits using same community account. - PASS
# User shares the experiment with Write access which was executed using individual allocation. Shared user clones and submits using community account. - For the shared user only available option is to use the community login, since she has no individual account of her own. - PASS
# 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. – This option is not available for the user. - PASS
# User shares the experiment with Write access which was executed using individual allocation. Shared user clones and submits using her own allocation account. -
NOTE: As per current implementation Reservation is applied for all the queues in the resource fro the given period. Testing with LDAP integration for compute clusters are not taken into consideration in this testing.
was (Author: eroma_a):
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)