|
|
@ -145,29 +145,44 @@ than "/usr/share/ansible". This means anyone can use Ansible, even without
|
|
|
|
root permissions.
|
|
|
|
root permissions.
|
|
|
|
|
|
|
|
|
|
|
|
There is potential for a sizeable community to build
|
|
|
|
There is potential for a sizeable community to build
|
|
|
|
up around the library scripts.
|
|
|
|
up around the library scripts, and you can easily write your own.
|
|
|
|
|
|
|
|
|
|
|
|
Modules include:
|
|
|
|
Current modules include:
|
|
|
|
|
|
|
|
|
|
|
|
* command -- runs commands, giving output, return codes, and run time info
|
|
|
|
* command -- runs commands, giving output, return codes, and run time info
|
|
|
|
* ping - just returns if the system is up or not
|
|
|
|
* ping - just returns if the system is up or not
|
|
|
|
* facter - retrieves facts about the host OS
|
|
|
|
* facter - retrieves facts about the host OS
|
|
|
|
* ohai - similar to facter, but returns structured data
|
|
|
|
* ohai - similar to facter, but returns structured data
|
|
|
|
* copy - add files to remote systems
|
|
|
|
* copy - add files to remote systems
|
|
|
|
|
|
|
|
* setup - pushes key/value data onto the system for use in templating
|
|
|
|
|
|
|
|
* template - takes a local template file and saves a templated version remotely
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service, package, and user modules, supporting puppet-like ensure semantics
|
|
|
|
|
|
|
|
are coming soon.
|
|
|
|
|
|
|
|
|
|
|
|
Playbooks
|
|
|
|
Playbooks
|
|
|
|
=========
|
|
|
|
=========
|
|
|
|
|
|
|
|
|
|
|
|
Playbooks are loosely equivalent to recipes or manifests in most configuration
|
|
|
|
Playbooks are particularly awesome. Playbooks can batch ansible commands
|
|
|
|
management or deployment tools and describe a set of operations to run on
|
|
|
|
together, and run some commands only when ansible modifies certain higher
|
|
|
|
a set of hosts. Some tasks can choose to only fire when certain
|
|
|
|
level resources -- such as restarting apache when a configuration file is
|
|
|
|
conditions are true, and if a task in a chain fails the dependent tasks
|
|
|
|
replaced. They generate detailed reports of what happend on each node.
|
|
|
|
will not proceed. Playbooks are described in (YAML)[http://yaml.org] format.
|
|
|
|
|
|
|
|
|
|
|
|
See examples/playbook.yml for what the syntax looks like.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To run a playbook:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ansible -r playbook.yml
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An ansible-playbook CLI command is pending. Until then, remember that when
|
|
|
|
|
|
|
|
using playbooks, the pattern and host list options come from the playbook
|
|
|
|
|
|
|
|
and are ignored. Other options still apply.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Future plans
|
|
|
|
Future plans
|
|
|
|
============
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
|
|
* see TODO.md
|
|
|
|
* see github's issue tracker for what we're thinking about
|
|
|
|
|
|
|
|
|
|
|
|
License
|
|
|
|
License
|
|
|
|
=======
|
|
|
|
=======
|
|
|
|