[
https://issues.apache.org/jira/browse/AIRAVATA-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma closed AIRAVATA-2200.
---------------------------
tested and verified in
https://dev.seagrid.org/
Individual users can define their own account details in compute resources and
run jobs. When they have their own account registered in the gateway they it
will be selected as the default allocation to submit the job unless user
selects community allocation by deselecting the use of his own allocation.
> Allow user to select their own compute resource account when creating
> experiment
> --------------------------------------------------------------------------------
>
> Key: AIRAVATA-2200
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2200
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Fix For: 0.17
>
>
> If the user has configured their own compute resource account (see EINT-2152)
> then they should be able to select that and run an experiment under their own
> account.
> h3. Testing to do once backend is updated
> * (/) Scenario: User A creates an experiment to run under their own compute
> resource account. User A shares experiment with User B, read only. User B
> clones the experiment but User B doesn't have their own compute resource
> account on that compute resource. User B's cloned experiment should not have
> useUserCRPref checkbox checked
> ** verified on dev.seagrid.org
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
