Runbook: Difference between revisions

Jump to navigation Jump to search
No change in size ,  12 July 2019
no edit summary
No edit summary
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.
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,” which makes them sound fun.


Judge for yourself how machine-age dogma has infected operations management orthodoxy, by this paragraph from Wikipedia:
Judge for yourself how machine-age dogma has infected operations management orthodoxy, by this paragraph from Wikipedia:

Navigation menu