Runbook: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|tech|}}In a computer [[network]], a [[runbook]] is a glorified checklist: a manual of routine procedures that the system administrator carries out when maintaining the system, and handling special requests and contingencies on the network. It allows other operators to effectively manage and troubleshoot a system. Through runbook automation, these processes can be carried out using software tools in a predetermined manner. | {{a|tech|}}In a computer [[network]], a [[runbook]] is a glorified [[checklist]]: a manual of routine procedures that the system administrator carries out when maintaining the system, and handling special requests and contingencies on the network. It allows other operators to effectively manage and troubleshoot a system. Through runbook automation, these processes can be carried out using software tools in a predetermined manner. | ||
So: a cheat sheet for steering complex but stupid machines. As such, the [[runbook]] has a natural attraction for a [[chief operating officer]], who looks upon employees in exactly those terms. so expect to see [[runbook]]s applied to the [[operations]] department, especially when it is going through a period of stress or significant change. In the wild world of negotiation, they are called “[[playbook]]s,” whcih makes them sound fun. | |||
Judge for yourself | Judge for yourself how machine-age dogma has infected operations management orthodoxy, by this paragraph from Wikipedia: | ||
:“''Operational [[runbook]]s may be tied to IT Infrastructure Library (ITIL)<ref>No idea, sorry.</ref> incidents to allow repeatable processes<ref>AKA drudgery.</ref> supporting specific aspects of the [[service catalog]]. The [[runbook]] is typically divided into routine automated processes and routine manual processes. The [[runbook catalog]] begins with an index of processes covered and may be broken down in outline form to align the processes to the major elements they support in the [[service catalog]].''” | :“''Operational [[runbook]]s may be tied to IT Infrastructure Library (ITIL)<ref>No idea, sorry.</ref> incidents to allow repeatable processes<ref>AKA drudgery.</ref> supporting specific aspects of the [[service catalog]]. The [[runbook]] is typically divided into routine automated processes and routine manual processes. The [[runbook catalog]] begins with an index of processes covered and may be broken down in outline form to align the processes to the major elements they support in the [[service catalog]].''” | ||
| Line 10: | Line 10: | ||
{{seealso}} | {{seealso}} | ||
*[[Meatware]] | *[[Meatware]] | ||
*[[Playbook]] | |||
*[[Algorithm]] | *[[Algorithm]] | ||
*{{br|The Checklist Manifesto: How to Get Things Right}} by {{author|Atul Gawande}} | *{{br|The Checklist Manifesto: How to Get Things Right}} by {{author|Atul Gawande}} | ||
{{ref}} | {{ref}} | ||