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)
| Group | Maintenance Cycle | Next Scheduled Downtime | Following Scheduled Downtime | Default day and time of day | First warning email sent when | Second warning email sent when | Notes |
|---|---|---|---|---|---|---|---|
| Abruna | 1 | December 7, 2016
|
| 1st Wednesday of the month 9:30am | 2 weeks before | 24 hours before | Need do cluster upgrade, may merge with Widom-Loring? |
| Scheraga | 1 | December 14, 2016 | 2rd Wednesday of the month 9:30am | 2 weeks before | 24 hours before | ||
| Collum | 2 | Oct 3rd
| January 2, 2017 | 1st Monday of the month (if holiday, move to 1st Tuesday) 9:30am | 2 weeks before | 24 hours before | |
| Hoffmann | 2 | Oct 18th | January 17, 2017 | 3nd Tuesday of the month 9:30am | 2 weeks before | 24 hours before | |
| Widom-Loring-Collum | 3 | Nov 1st
| February 7, 2017 | 1st Tuesday of the month 9:30am | 2 weeks before | 24 hours before | |
| Eldor | 3 | Nov 10th | February 9, 2017 | 2nd Thursday of the month 9:30am | 2 weeks before | 24 hours before | |
Crane Linux Workstations | 3 | Nov 16th | February 15, 2017 | 3rd Wednesday of the month 9:30am | 2 weeks before | 24 hours before |