[NLPL Task Force (A)] [NLPL Team] news on our technical infrastructure

[Martin Matthiesen]

Hei, 

Some comments to the process outlined below. I think this is indeed how it works in practice. 

> From: "Joakim Nivre" <joakim.nivre at lingfil.uu.se>
> To: "Stephan Oepen" <oe at ifi.uio.no>
> Cc: "infrastructure" <infrastructure at nlpl.eu>, "board" <board at nlpl.eu>
> Sent: Tuesday, 17 October, 2017 22:58:45
> Subject: Re: [NLPL Task Force (A)] [NLPL Team] news on our technical
> infrastructure

> Thanks, Stephan. Here is an attempt to follow your proposed procedure for adding
> Aaron Smith as a team member.

>> (0) the ‘team’ mailing list and personnel summary at

>> [
>> https://wiki.neic.no/wiki/Nordic_language_processing_laboratory#Project_Personnel
>> |
>> https://wiki.neic.no/wiki/Nordic_language_processing_laboratory#Project_Personnel
>> ]

>> bjørn is the maintainer of both of these, so maybe start by announcing
>> a new team member to him and the ‘infrastructure’ task force: we will
>> probably need the full name, email address, and maybe the anticipated
>> duration of involvement.

> Full name: Aaron Smith
> Email: [ mailto:aaron.smith at lingfil.uu.se | aaron.smith at lingfil.uu.se ]
> Duration: until the end of the project

>> (1) accounts on Abel and Taito and membership in the various project
>> groups that control usage of cpu hours and, optionally, write access
>> to the NLPL project directories. either way, the first step to
>> obtaining access should be along these lines:

>> [ http://wiki.nlpl.eu/index.php/Infrastructure/resources |
>> http://wiki.nlpl.eu/index.php/Infrastructure/resources ]

>> not sure who controls the uppsala Taito project group—is that martin
>> or you?

On Taito each PI controls his own project, since /proj/nlpl is linked to Stephan's project he in fact controls write access via group membership there, as he mentions below. 

>> probably the above instructions should ask that new users
>> coordinate with their NLPL site manager about gaining access to Taito,
>> i.e. you in the UU case.

Yes, access to Taito can be gained via existing PIs, my understanding is that in Abel this is defacto only Stephan. 

>> for the latter two groups (write access to the project directories on
>> Abel and Taito), i am the one to add new users to these groups, both
>> on Abel and Taito. i suggest the emails from step (0) above include
>> an optional statement about expected involvement in software
>> installations and, if so, for which of the two HPC systems.

> Aaron already has accounts on Abel and Taito, but he needs to be given write
> access at least on Abel, because he is going to work on installing things for
> Activity C.

>> (2) write access to the NLPL wiki (which we are taking into active use
>> these days; instructions to come to ‘team’ shortly). bjørn and i have
>> administrator rights on the wiki, so i would suggest that bjørn
>> remembers to generate new wiki accounts at the same time as he adds
>> new members to the ‘team’ list.

>> bjørn (and martin and joerg), does the above sound feasible? maybe i
>> am overlooking some additional records that need to be maintained?
>> either way, we should sooner or later spell out the procedures for new
>> users on the wiki :-).

I think this sounds fine for now. As for the future I find the concentration on one PI for write access to NLPL a bit restricting, NLPL is bending the "Project" concept on both Abel and Taito. But at least this works with current workflows. 

Cheers, 
Martin 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlpl.eu/archives/infrastructure/attachments/20171024/bb431bee/attachment.htm>