Added initial stub for where playbooks will go, moved to common

constants file so as to not repeat constants between CLI and lib.
This commit is contained in:
Michael DeHaan 2012-02-23 23:26:16 -05:00
commit 6eda2cf383
5 changed files with 136 additions and 44 deletions

View file

@ -37,6 +37,7 @@ Requirements
For the server the tool is running from, *only*:
* python 2.6 -- or the 2.4/2.5 backport of the multiprocessing module
* PyYAML (if using playbooks)
* paramiko
Inventory file
@ -145,6 +146,15 @@ Modules include:
* facter - retrieves facts about the host OS
* copy - add files to remote systems
Playbooks
=========
Playbooks are loosely equivalent to recipes or manifests in most configuration
management or deployment tools and describe a set of operations to run on
a set of hosts. Some tasks can choose to only fire when certain
conditions are true, and if a task in a chain fails the dependent tasks
will not proceed. Playbooks are described in (YAML)[http://yaml.org] format.
Future plans
============