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:
Two e-mails will be 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 date and time.
- The second email will be sent to all group users 24 hours before.
One email about maintenance status update will be sent before 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 | First warning email sent when | Second warning email sent when | Notes | Next Scheduled downtime |
|---|---|---|---|---|---|---|
| Abruna | March | 1st Wednesday of the month 9am | 2 weeks before | 24 hours before | Need do cluster upgrade, may merge with Widom-Loring? | Wed. 03/02/2016 at 9am |
| Collum | March | 1st Monday of the month (if holiday, move to 1st Tuesday) 9am | 2 weeks before | 24 hours before | Mon. 03/07/2016 at 9am | |
| Hoffmann | March | 2nd Tuesday of the month Noon | 2 weeks before | 24 hours before | Group meeting at noon on Tuesdays, as of Nov. 2015. We hope half day will be good enough. | Tues. 03/08/2016 at 12pm |
| Lancaster (w/ Crane) | March | 3rd Monday of the month 9am | 2 weeks before | 24 hours before | Tues. 03/14/2016 at 9am | |
| Scheraga | March | 3rd Wednesday of the month 9am | 2 weeks before | 24 hours before | Thur. 03/16/2016 at 9am | |
| Widom-Loring | March | 1st Thursday of the month 9am | 2 weeks before | 24 hours before | Thur. 03/03/2016 at 9am | |
| Eldor | March | 2nd Thursday of the month 9am | 2 weeks before | 24 hours before | Thur. 03/10/2016 at 9am |