Sequence of communications for cluster maintenance.
1) ChemIT notifies group rep. of planned date.
2) Group rep. confirms there is no better date (or negotiates a better date, with ChemIT staff).
3) ChemIT sends notification email to all group's cluster users, to their <NetID@cornell.edu> address (via cluster's AD group). From <chemit>
4) The work day before the shut down, ChemIT sends a reminder notification.
(Not done, right? 5) When cluster is shutdown, ChemIT sends a statement to that affect.
6) ChemIT sends a status report if cluster not going to be up when expected, providing new time estimate.
- Do this as soon as known- don't wait for original deadline!
7) ChemIT sends a report when the server is again available.