Milestone #15057: Minos SLF5 retirement
Individual Minos SLF5 node shutdowns
Shut down the Minos offline SLF5 systems by April 1 2017.
Make a Subtask Issue for each system.
#1 Updated by Arthur Kreymer over 2 years ago
Summary of SLF5 nodes managed for Minos :
|minos-mysql2||Database server (retired )||15793||03/08||RITM0540867 03/20||archived local files|
|minos-sam04||IF SAM server (retired )||15794||03/16||RITM0539760 03/16||archived local files|
|minos25||Condor master (retired)||15795||03/16||RITM0539526 03/16||archived local files|
|minos27||Data Handling (retired)||15796||03/19||RITM0541265 03/20||archived local files|
|minos50||Interactive||15797||03/17||RITM0542037 03/22||archived local files 03/21|
|minos51||Interactive||15798||03/18||RITM0542039 03/22||archived local files 03/21|
|minos52||Interactive||15799||03/17||RITM0542958 03/24||archived local files 03/21|
|minos53||Interactive||15800||03/27||RITM0543792 03/27||archived local files 03/21|
|minos54||GlideingWMS (retired)||15801||03/16||RITM0541264 03/20||archived local files|
|Interactive VM||15802||ssh only from minos-slf6|
#2 Updated by Arthur Kreymer over 2 years ago
Date: Fri, 17 Mar 2017 13:25:33 +0000 From: Arthur Kreymer <firstname.lastname@example.org> To: email@example.com Cc: firstname.lastname@example.org Subject: Minos SLF5 shutdown schedule All Minos SLF5 systems need to be shut down before 2017 April 1, as the base system is no longer supported. This includes servers not usually used interactively ( minos25, minos27, minos-mysql2, minos-sam04, minos-mysql2 ) as well as the heavily used minos50 through minos54. We would like to shut down minos53,54 early next week, minos51,52 late next week, minos50,51 March 27, close to the deadline. Usage is monitored on the web, see http://minos.fnal.gov/computing/dh/procsum/ Work is being tracked in https://cdcvs.fnal.gov/redmine/issues/15057 We will retain one system, minos-slf5 for reference. Access will be limted. You can ssh to minos-slf5 from node minos-slf6. You should stop using all production Minos SLF5 systems now, shifting necessary SLF5 activity to minos-slf5.
Date: Wed, 22 Mar 2017 15:21:26 +0000 From: Arthur Kreymer <email@example.com> To: firstname.lastname@example.org Cc: email@example.com Subject: Re: Minos SLF5 shutdown schedule On Fri, 17 Mar 2017, Arthur Kreymer wrote: > We would like to shut down > minos53,54 early next week, > minos51,52 late next week, > minos50,51 March 27, close to the deadline. > > Usage is monitored on the web, see > http://minos.fnal.gov/computing/dh/procsum/ > > Work is being tracked in > https://cdcvs.fnal.gov/redmine/issues/15057 minos54 has been shut down as scheduled. Usage of minos50 and minos51 is extremely light, so these systems are being shut down today. I plan to shut down minos52 Fri 03/24 minos53 Mon 03/27
Date: Mon, 27 Mar 2017 16:13:36 +0000 From: Arthur Kreymer <firstname.lastname@example.org> To: email@example.com, firstname.lastname@example.org, email@example.com Subject: minos53 is shut down minos53 was shut down this morning, as planned. See https://cdcvs.fnal.gov/redmine/issues/1579 We can still access one SLF5 node minos-slf5 through Sep 8. Log into minos-slf6, then ssh to minos-slf5.
#3 Updated by Arthur Kreymer over 2 years ago
The /local/scratch directories and ancient scratch0*, scratch1* subdirectories
were archived to /minos/data/users/mindata/localscratch excluding *.root files
The script used was /grid/fermiapp/minos/scripts/backscratch.
File listings were also made before system shutdown.
#4 Updated by Arthur Kreymer over 2 years ago
Took fefganalia 1 year png images of cpu, load, mem and net
for minos27,50-54 and aggregate minos
Also minoslong from 2012, which seems be the oldest available data.