You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »

Regular maintenance of clusters requires downtime. A maintenance schedule can reduce surprises and not unnecessarily delay required maintenance.

See also

  • For a snapshot inventory, and the costs to CCB if they were hosted elsewhere, see ChemIT's spreadsheet in <R:\Chem IT\Projects & Tracking>. The data and analysis is in spreadsheet, "Chem IT Support & Services", tab "Alternative server costs".

Documentation for staff, in support of cluster maintenance

Specifics, per research group's cluster

(Table started November 2015)

GroupGroups

Default day and

time of day

First warning

email sent when

Second warning

email sent when
Notes
Abruna1

1st Wednesday of the month

9:30am

2 weeks before24 hours before

Need do cluster upgrade, may merge with

Widom-Loring?

Collum2

1st Monday of the month

(if holiday, move to

1st Tuesday)

9:30am

2 weeks before24 hours before 
Hoffmann2

3nd Tuesday of the month

9:30am

2 weeks before24 hours beforeChanged to morning
Lancaster (w/ Crane) 3

3rd Wednesday of the

month 9:30am

2 weeks before24 hours before 
Scheraga 1

2rd Wednesday of the month

9:30am

2 weeks before24 hours before 
Widom-Loring-Collum 3

1st Tuesday of the month

9:30am

2 weeks before24 hours before 
Eldor3

2nd Thursday of the

month 9:30am

2 weeks before24 hours before 
GroupsGroup memberNext Scheduled DowntimeFollowing Scheduled Downtime
1

Abruna

Scheraga

June 1st

June 8th

Sept 7th

Sept 14th

2

Collum

Hoffmann

July 18th

July 26th

Oct 3rd

Oct 18th

3

Widom-Loring-Collum

Eldor

Lancaster (w/ Crane)

Aug 2nd

Aug 11th

Aug 17th

Nov 1st

Nov 10th

Nov 16th

 

 

  • No labels