[NLPL Task Force (A)] Fwd: [rt.uio.no #2703759] add non-UiO users to Un*x group ‘hpc-nlpl’

[Stephan Oepen]

just fyi: for the time being, there is no facility for us to directly
update the Un*x group that controls write access to the NLPL project
directory on Abel.

i put this thread into our mailing archive (and copy tomasz) because i
feel this is the kind of functionality we should discuss with the
dellingr project at some point; maybe there will be an opportunity to
reflect on our experiences jointly during the NeIC all-hands meeting
next january?

semi-relatedly, it is also clear that we will need to migrate from
Abel to a new norwegian supercluster (called Fram and physically no
longer located in oslo) sometime next year.  once more is known about
the overall migration schedule, we should discuss with the right
people (at Sigma2 or USIT, maybe) how the transition will affect NLPL
infrastructure, e.g. the shared project directory and staging to and
from the NorStore successor NIRD.

best, oe



---------- Forwarded message ----------
From: Thomas Röblitz via RT <hpc-drift at usit.uio.no>
Date: Tue, Oct 17, 2017 at 9:06 AM
Subject: [rt.uio.no #2703759] add non-UiO users to Un*x group ‘hpc-nlpl’
To: oe at ifi.uio.no


Yep, because UiO means, e.g., brukerinfo, only know about UiO users.

I guess if groups would be managed via Notur like user accounts this
might be possible.

Cheers

Thomas

On 2017-10-17 09:02:30, oe wrote:
> thanks, thomas!
>
> so i take it there is no current way for me to add non-UiO users to this
> group?
>
> what would have to happen to make that possible in the future?
>
> cheers, oe
>
>
> On Tue, 17 Oct 2017 at 08:49 Thomas Röblitz via RT <hpc-drift at usit.uio.no>
> wrote:
>
> >
> > Vi oppfatter det slik at denne henvendelsen fra deg kan avsluttes nå, og
> > vi har
> > lukket saken. Vennligst ikke svar på denne meldingen, med mindre du har
> > noe å tilføye og ønsker at saken skal åpnes igjen.
> >
> > -------------------------------------------------------------------------
> >
> > According to our records, your request has been resolved. Please do not
> > respond to this message, unless you have further questions or concerns,
> > since a response will reopen the ticket.
> >