No description
Find a file
2012-07-13 11:07:32 +02:00
bin Merge pull request #576 from davehatton/adjust_playbook_output_formating 2012-07-11 17:42:39 -07:00
docs/man
examples Allow include statements from plays to specify tags (see tags.yml example file). 2012-07-11 20:33:46 -04:00
hacking
lib/ansible Wrong evaluation of a local file before fetching the remote file 2012-07-13 11:07:32 +02:00
library Removed unused recurse option in file module. 2012-07-12 02:04:51 -04:00
packaging bump rpm spec to 0.6 2012-07-05 07:18:43 +01:00
test
.gitignore
CHANGELOG.md changelog update 2012-07-11 20:51:07 -04:00
COPYING
Makefile
MANIFEST.in
README.md update versions mentioned in README.md 2012-07-04 18:07:19 -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

  • Releases are named after Van Halen songs.
  • The master branch corresponds to release 0.5 "Amsterdam".
  • The devel branch corresponds to release 0.6 "Cabo".
  • All feature work happens on the development branch.
  • Major bug fixes will be made to the master branch, but not minor ones.
  • 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
    • Fixing bugs instead of sending bug reports.
    • 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