4
edits
CloudServices/Principles: Difference between revisions
Jump to navigation
Jump to search
s/yammer/slack
m (Telliott moved page Services/Principles to CloudServices/Principles) |
Milescrabill (talk | contribs) (s/yammer/slack) |
||
| Line 9: | Line 9: | ||
* a secondary person helps with / checks plans for complex changes (buddy system) | * a secondary person helps with / checks plans for complex changes (buddy system) | ||
* points of commitment (or "no return") have go/no-go calls with a clear owner / deterministic datapoint | * points of commitment (or "no return") have go/no-go calls with a clear owner / deterministic datapoint | ||
* all change plan worthy events must have a clearly defined owner who is responsible for "heads-up", "starting", & "all-clear" email communications (and twitter, | * all change plan worthy events must have a clearly defined owner who is responsible for "heads-up", "starting", & "all-clear" email communications (and twitter, IRC, Slack, etc as needed), as well as any write-up on deviations from the plan or other problems. | ||
== Rules of engagement == | == Rules of engagement == | ||
| Line 34: | Line 34: | ||
To avoid critical failures: | To avoid critical failures: | ||
* redundant multi- | * redundant multi-host & round-robin systems are preferred over cold fail-over systems | ||
* the single host is the smallest unit of allowed (and expected) failure | * the single host is the smallest unit of allowed (and expected) failure | ||
* solutions for redundancy are evaluated purely on merit -- not hardware vs software or by vendor / project | * solutions for redundancy are evaluated purely on merit -- not hardware vs software or by vendor / project | ||