No description
Find a file
2012-05-01 23:22:23 -04:00
bin Add some comments to ansible-pull and the example playbook 2012-05-01 23:22:23 -04:00
docs/man Because paramiko using a pty can't distinguish stderr and stdout, remove handling that 2012-04-27 01:25:38 -04:00
examples Add some comments to ansible-pull and the example playbook 2012-05-01 23:22:23 -04:00
hacking Adding a missing '~' to use the user's home directory instead of the root file system for the module arguments 2012-05-02 09:50:20 -07:00
lib/ansible Define 'inventory_hostname' variable for hosts. 2012-05-02 09:56:58 +02:00
library Group order in user module should not matter. 2012-05-02 11:54:27 +02:00
packaging
test Define 'inventory_hostname' variable for hosts. 2012-05-02 09:56:58 +02:00
.gitignore
CHANGELOG.md changelog update 2012-05-01 23:05:40 -04:00
COPYING
Makefile
MANIFEST.in Include license file in MANIFEST.in. Fixes #284 2012-05-01 10:34:36 -04:00
README.md changelog and readme 2012-04-25 21:32:08 -04:00
setup.py
VERSION

Ansible

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

Read all about at it at (http://ansible.github.com)

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

  • The master branch corresponds to release 0.3 "Baluchitherium".
  • Bug fixes WILL be periodically made to the master branch.
  • The devel branch corresponds to release 0.4 "Unchained".
  • Note: sudo support works much better in 0.4/devel, consider trying it.
  • See CHANGELOG.md for release notes to track each release.

Patch Instructions

Contributions to the core and modules are greatly welcome.

  • Required Process:
    • Submit github pull requests to the "ansible/devel" branch for features
    • Fixes for bugs may be submitted to "ansible/master"
    • Make sure "make tests" passes before submitting any requests.
  • Bonus points:
    • Joining the mailing list
    • Using squash merges
    • Updating the "rst/*" files in the docs project and "docs/" manpage content
    • Adding more unit tests
  • Avoid:
    • Sending patches to the mailing list directly.
    • Sending feature pull requests to the 'master' branch instead of the devel branch
    • Sending pull requests to mpdehaan's personal ansible fork.

Author

Michael DeHaan -- michael.dehaan@gmail.com

http://michaeldehaan.net