Regular maintenance of clusters requires downtime. By creating a maintenance schedule we can reduce surprises and not unnecessarily delay required maintenance.
Our maintenance operating steps:
There are two e-mails sent before the maintenance:
- One email will be sent to group users at two weeks before the maintenance down time. If there is any problem with the date and time, the group users should contact group IT representative. Then group IT representative should contact and discuss with us about the new picked data and time.
The second email will be sent to all group users 24 hours before.
There are one e-mails sent before the maintenance deadline:
- one email will be sent to all group users about the completion of the work or extension of the downtime will be posted.
Created November 2015
| Group | Months | Default day and time of day | Notes |
|---|---|---|---|
| Abruna | March | 1st Wednesday of the month 9am | Need do cluster upgrade, may merge with Widom-Loring? |
| Collum | March | 1st Monday of the month (if holiday, move to 1st Tuesday) 9am | |
| Hoffmann | March | 2nd Tuesday of the month Noon | Group meeting at noon on Tuesdays, as of Nov. 2015. We hope half day will be good enough. |
| Lancaster (w/ Crane) | March | 3rd Tuesday of the month 9am | |
| Scheraga | March | 3rd Thursday of the month 9am | |
| Widom-Loring | March | 1st Thursday of the month 9am | |
| Eldor | March | 2nd Thursday of the month 9am |