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 | Months | Default day and time of day | First warning email sent when | Second warning email sent when | Notes | Next Scheduled downtime |
|---|---|---|---|---|---|---|
| Abruna | March | 1st Wednesday of the month 9:30am | 2 weeks before | 24 hours before | Need do cluster upgrade, may merge with Widom-Loring? | TBD |
| Collum | March | 1st Monday of the month (if holiday, move to 1st Tuesday) 9:30am | 2 weeks before | 24 hours before | TBD | |
| Hoffmann | March | 2nd Tuesday of the month 9:30am | 2 weeks before | 24 hours before | Changed to morning | TBD |
| Lancaster (w/ Crane) | March | 3rd Monday of the month 9:30am | 2 weeks before | 24 hours before | TBD | |
| Scheraga | March | 3rd Wednesday of the month 9:30am | 2 weeks before | 24 hours before | TBD | |
| Widom-Loring | March | 1st Thursday of the month 9:30am | 2 weeks before | 24 hours before | TBD | |
| Eldor | March | 2nd Thursday of the month 9:30am | 2 weeks before | 24 hours before | TBD |