From 16426ad795f450c2e6eaa0df42ebefdb172ddb2a Mon Sep 17 00:00:00 2001 From: sam-at-github Date: Wed, 17 Aug 2016 19:20:13 +1000 Subject: [PATCH] I think that is a better analogy. --- docsite/rst/playbooks.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks.rst b/docsite/rst/playbooks.rst index de8072cb31..97a9f40464 100644 --- a/docsite/rst/playbooks.rst +++ b/docsite/rst/playbooks.rst @@ -3,7 +3,7 @@ Playbooks Playbooks are Ansible's configuration, deployment, and orchestration language. They can describe a policy you want your remote systems to enforce, or a set of steps in a general IT process. -If Ansible modules are the tools in your workshop, playbooks are your design plans. +If Ansible modules are the tools in your workshop, playbooks are your instruction manuals, and your inventory of hosts are your raw material. At a basic level, playbooks can be used to manage configurations of and deployments to remote machines. At a more advanced level, they can sequence multi-tier rollouts involving rolling updates, and can delegate actions to other hosts, interacting with monitoring servers and load balancers along the way.