No description
Find a file
Aaron Brady bd226eb826 Refactor user_and_group so it works off of numbers
There are various cases where a UID to username to UID mapping breaks
down. One UID can be used by two usernames, or no username. If we
always use UIDs internally, then these ambiguous cases won't be a
problem.
2013-04-25 13:23:07 +01:00
bin Resolve merge conflict 2013-04-22 23:57:20 -04:00
docs/man Update release version. 2013-04-02 20:48:30 -04:00
docsite Merge pull request #2733 from chadoh/patch-1 2013-04-22 21:21:30 -07:00
examples Update role example to show tag usage 2013-04-24 22:31:21 -04:00
hacking Changes to allow WANT_JSON to allow JSON to non-Python modules 2013-04-24 22:00:40 -04:00
lib/ansible Refactor user_and_group so it works off of numbers 2013-04-25 13:23:07 +01:00
library Corrected instance password data check. Previously broken after adding region support. 2013-04-24 09:45:01 -07:00
packaging added missing build deps for debian/ubuntu to readme 2013-04-03 12:27:18 -04:00
plugins Instantiate callback plugins only once so we can set play/task objects on them and they'll stick. 2013-04-20 09:09:35 -04:00
test copy action plug-in check mode respects force=no 2013-04-16 20:22:51 -04:00
.gitignore Smush Jinja2 braces in playbooks so unresolved variables get parsed nicely 2013-04-12 18:38:48 -04:00
CHANGELOG.md Update changelog 2013-04-23 00:43:55 -04:00
CONTRIBUTING.md Add a line about testing. 2013-02-23 12:41:00 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Smush Jinja2 braces in playbooks so unresolved variables get parsed nicely 2013-04-12 18:38:48 -04:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md Update README.md 2013-04-06 17:22:21 -03:00
RELEASES.txt Update the release date & code names in the releases file. 2013-04-20 18:21:25 -04:00
setup.py CLI: ansible-doc shows lists of modules & module docs on command-line 2012-11-30 21:57:25 -05:00
VERSION Update release version. 2013-04-02 20:48:30 -04:00

Ansible

Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework.

Read the documentation and more at http://ansible.cc

Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release. You can find instructions on http://ansible.cc/docs/gettingstarted.html for a variety of platforms. If you want a tarball of the last release, go to http://ansible.cc/releases/ and you can also install with pip (though that will bring in some optional binary dependencies you normally do not need).

Design Principles

  • Dead simple setup
  • Super fast & parallel by default
  • No server or client daemons; use existing SSHd
  • No additional software required on client boxes
  • Modules can be written in ANY language
  • Awesome API for creating very powerful distributed scripts
  • Be usable as non-root
  • The easiest config management system to use, ever.

Get Involved

Branch Info

  • Releases are named after Van Halen songs.
  • The devel branch corresponds to the release actively under development.
  • Various release-X.Y branches exist for previous releases
  • We'd love to have your contributions, read "CONTRIBUTING.md" for process notes.

Author

Michael DeHaan -- michael@ansibleworks.com

AnsibleWorks