NOTE: This page contains documentation about how to use Ansible and covers the latest DEVELOPMENT version (1.2). For the current released version, see Ansible 1.1 Docs instead. You might be one of them. We hope you find what you are looking for in the documentation, and would like to point out that you may also be interested in taking a class:
Before we dive into playbooks, configuration management, deployment, and orchestration, we’ll learn how to get Ansible installed and some basic information. We’ll go over how to execute ad-hoc commands in parallel across your nodes using /usr/bin/ansible. We’ll also see what sort of modules are available in Ansible’s core (though you can also write your own, which we’ll also show later).
Playbooks are Ansible’s orchestration language. At a basic level, playbooks can be used to manage configurations and deployments of 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. You can start small and pick up more features over time as you need them. Playbooks are designed to be human-readable and are developed in a basic text language. There are multiple ways to organize playbooks and the files they include, and we’ll offer up some suggestions on that and making the most out of Ansible.
Learn how to build modules of your own in any language. Explore Ansible’s Python API and write Python plugins to integrate with other solutions in your environment.
Learn and share neat Ansible tricks on Coderwall - sign-in using GitHub or Twitter to vote on top tips and add your own!