[NLPL Task Force (A)] /proj/nlpl/modules/ on Taito

Stephan Oepen oe at ifi.uio.no
Mon Sep 24 17:45:14 UTC 2018


thanks, joerg.  i will use that as a test of our ‘back-up’ strategy
tomorrow then.

in other words, i shall let the nightly replication complete before i
remove ‘/proj/nlpl/modules/’ on Taito tomorrow.  tomorrow night, we
should then be notified of those files disappearing, which i expect
should become visible to us via a notification that they were moved
into the ‘backup’ folder on NIRD.  off the top of my head, i am not
sure what will happen 24 hours later.  i had originally looked more
closely at how exactly to call rsync(1) before the summer ...  i
believe, with a bit of luck, the removed files should remain in the
NIRD ‘backup’ folder until overwritten by another version, i.e. we
might in practice actually have more than a 24-hour window to deal
with inadvertent data loss.

i sugges we all study the nightly messages with some curiosity and
care the next few days.  as of today, there should be a total of four
message coming to ‘infrastructure’:

+ back-up to NIRD on Abel
+ back-up to NIRD on Taito
+ replication of ‘data/corpora/’ from Abel to Taito
+ replication of ‘data/vectors/’ from Abel to Taito

i am keeping the latter two separate because there is an additional
recipient (andrey) on the notifications for the vectors repository.

good night for today :-), oe


On Mon, Sep 24, 2018 at 5:03 PM, Tiedemann, Jörg
<jorg.tiedemann at helsinki.fi> wrote:
>
> I guess it is. Should be safe to remove ...
>
> Jörg
>
> ********************************************************************************************
> Jörg Tiedemann https://blogs.helsinki.fi/tiedeman/
> Language Technology https://blogs.helsinki.fi/language-technology/
> University of Helsinki
>
> On 24 Sep 2018, at 17:55, Stephan Oepen <oe at ifi.uio.no> wrote:
>
> hi joerg,
>
> i am pretty sure that ‘/proj/nlpl/modules/’ is a left-over the old
> days, before we had landed on our final set of installation
> guidelines?  i would like to remove it, to avoid duplication and
> confusion, okay?
>
> oe
>
>




More information about the infrastructure mailing list