Capture CTRL-C and exit gracefully

Registered by aeva black on 2012-03-09

Instead of simply aborting if the user presses "CTRL-C" during a flip, we should catch this and be graceful.
Ideally, where possible, Ctrl-C should leave all hosts in a predictable state, but I'm not certain yet what this is in every case.

Should it...
* roll back any successful VIP moves, or make sure the VIP is not reachable?
* make any hosts writable that were writable, and read-only if they were read-only ... or make all hosts read-only?
* something else?

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.