Ticket #1180 (closed task: fixed)

Opened 12 years ago

Last modified 10 years ago

Policy on scheduled downtime and reboot announcements

Reported by: adehnert Owned by:
Priority: normal Milestone: The Distant Future
Component: linerva Keywords: transition, layer9
Cc: Fixed in version:
Upstream bug:


If we're moving our users to athena.dialup, it would be nice if there were an established policy on scheduling downtime and announcing reboots for the dialups.

Change History

comment:1 Changed 12 years ago by adehnert

  • Keywords transition, layer9 added; transition removed

comment:2 Changed 11 years ago by adehnert

achernya reports:

Furthermore, #1180 and #1181 are not solvable, because jweiss has
already told us that the best Ops can do is best-effort.

We should probably pursue what "best effort" means --- is that "we will try to keep the dialups up as long as possible, excepting critical updates that require rebooting"? Is that "we will try to announce things $time in advance, unless it's really urgent"? Is that "we'll reboot when it's convenient"? I *suspect* that "best effort" doesn't mean the last one, but it might be nice to verify that and maybe figure out which of the first two (or something else) it is.

comment:3 Changed 10 years ago by adehnert

  • Status changed from new to closed
  • Resolution set to fixed

For planned outages, jweiss has been trying to give 24ish hours outage notices with wall, and has been averaging about once a semester. This seems fine, so resolving.

Note: See TracTickets for help on using tickets.