For a long time, we have been using the concept of community users and
community user credentials which were shared by all the users in the
gateway when connecting to compute and storage resources.

But now we have a new requirement where each user will have his/her own
login information for compute and storage resources and when connecting,
Airavata should use that user specific login and authentication information.

We have two use cases at the moment.

1. Ultrascan Julich compute resource: This particular compute resource does
not support the notion of community user concept and every user should use
their own credentials when submitting jobs to Julich (We are planning not
to use Unicore for Julich in the future).

2. Bio team user-specific storage resources: Currently, we have one storage
resource for the entire gateway where all the user inputs and outputs are
staged. But in the Bio team use case users want to provide URI paths for
inputs which are available on a different servers and does not want to
stage those files back to the gateway data store because of the size. In
this case, we are using user-specific storage resource configurations to
read those files.

On Mon, Nov 21, 2016 at 9:48 AM, Amila Jayasekara <[email protected]>
wrote:

> Just curious, what is " user compute and storage resources" ?
>
> -Amila
>
> On Sun, Nov 20, 2016 at 2:44 AM, Supun Nakandala <
> [email protected]> wrote:
>
>> Hi Jarett,
>>
>> The user compute and storage resources implementation is currently in the
>> develop branch. So if you want to use them you will have to try the develop
>> branch.
>>
>> Having said that we are in the process of testing the develop branch and
>> after that, we will merge it to the stable master (probably do a release
>> too). I would recommend you to use the master branch instead of the develop
>> branch. But in the meantime, if you want to try out things you can go
>> forward with develop branch.
>>
>> -Supun
>>
>
>


-- 
Thank you
Supun Nakandala
Dept. Computer Science and Engineering
University of Moratuwa

Reply via email to