[
https://issues.apache.org/jira/browse/AIRAVATA-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2839:
--------------------------------------
Description:
The GatewayResourceProfile has ComputeResourcePreferences that are now used to
specify default values for compute resources, but a GroupResourceProfile's
GroupComputeResourcePreferences should be used for the actual
authentication/allocation charged for the job.
This means that a GroupResourceProfile's GroupComputeResourcePreference should
either specify:
* a different loginUserName
* or a different allocationProjectNumber
from the corresponding ComputeResourcePreference in the GatewayResourceProfile.
This was a GroupResourceProfile can't accidentally use the account specified
in a GatewayResourceProfile ComputeResourcePreference.
The main use case for this is that a gateway admin can create a
ComputeResourcePreference with a loginUserName and credential store token that
handles logging in to the compute resource and then a user can create a
GroupComputeResourcePreference that essentially only needs to specify an
allocation number (well, and the user would need to authorize that
loginUserName to be able to use the allocation, depending on the compute
resource's policy).
was:The GatewayResourceProfile has ComputeResourcePreferences that are now
used to specify default values for
> GroupResourceProfile: require unique login username or unique allocation
> number
> -------------------------------------------------------------------------------
>
> Key: AIRAVATA-2839
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2839
> Project: Airavata
> Issue Type: Story
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> The GatewayResourceProfile has ComputeResourcePreferences that are now used
> to specify default values for compute resources, but a GroupResourceProfile's
> GroupComputeResourcePreferences should be used for the actual
> authentication/allocation charged for the job.
> This means that a GroupResourceProfile's GroupComputeResourcePreference
> should either specify:
> * a different loginUserName
> * or a different allocationProjectNumber
> from the corresponding ComputeResourcePreference in the
> GatewayResourceProfile. This was a GroupResourceProfile can't accidentally
> use the account specified in a GatewayResourceProfile
> ComputeResourcePreference.
> The main use case for this is that a gateway admin can create a
> ComputeResourcePreference with a loginUserName and credential store token
> that handles logging in to the compute resource and then a user can create a
> GroupComputeResourcePreference that essentially only needs to specify an
> allocation number (well, and the user would need to authorize that
> loginUserName to be able to use the allocation, depending on the compute
> resource's policy).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
