ndoli and openmind7 gone?

[jwodder]

Based on the daily report e-mails, the ndoli client has been inactive since mid-September, and the openmind7 client has been inactive since early January.

@yarikoptic Are these clients still around? Can you bring them back up, or should we remove their definitions from clients.yaml and delete their "build" branches from datalad/git-annex-ci-client-jobs?

[yarikoptic]

ndoli is up, not sure what caused cron job to stop. since it was under that special service account, requires digging to recall how, thus never got to it.

Should also check on what happened with openmind, may be @djarecka knows?

❯ ssh openmind7.mit.edu
ssh: connect to host openmind7.mit.edu port 22: No route to host

[jwodder]

openmind7 is back up.

[djarecka]

btw. are you keeping any data on openmind? this should migrate somewhere else.

[yarikoptic]

@djarecka only about 500MB in my home folder there for this testing -- where/why should it be migrated?

[djarecka]

@aaronkanzer - I now you already moved the data for our group, but do you think you could still add @yarikoptic home folder?
Yarik had MIT password and account on openmind, so perhaps he can also have on Engaging?

[aaronkanzer]

@aaronkanzer - I now you already moved the data for our group, but do you think you could still add @yarikoptic home folder? Yarik had MIT password and account on openmind, so perhaps he can also have on Engaging?

@yarikoptic -- do you recall the path in which your data was located on OpenMind? I can request that MIT ORCD migrate the data to Engaging

OpenMind should still have available nodes; however, it is soon-to-be replaced entirely with Engaging.

Cc @djarecka

[yarikoptic]

FWIW -- my home is /home/yhalchen

[aaronkanzer]

FWIW -- my home is /home/yhalchen

Thanks @yarikoptic and @djarecka -- Yarik, you should be Cc'd now on an email to MIT ORCD to request this transfer.

[yarikoptic]

FTR, last report from ndoli was Sep 28, 2024 datalad/git-annex-ci-client-jobs@3987c7f. inquiring dartmouth IT on what could have lead to cronjob being gone (and setup there is quite "intriguing" thanks due to kerberos etc)

[f006dyc@ndoli ~]$ crontab -l
no crontab for f006dyc