No description
Find a file
2012-08-02 17:46:21 -04:00
bin blue on black, tears on a river, push on a shove, it don't mean much 2012-07-25 20:31:26 -04:00
docs/man Small change to previous patch, make ranges of hosts inclusive. 2012-07-24 20:10:05 -04:00
examples Rename: postgresql.yaml -> postgresql.yml 2012-07-29 13:52:30 -04:00
hacking readlink -f does not work on OS X. Replaced with a python solution 2012-07-30 21:35:24 +10:00
lib/ansible remove the tab I found 2012-08-02 17:26:04 -04:00
library make virt module command= work again - better error handling should be in its 2012-08-02 17:46:21 -04:00
packaging Smiting Debian packaging instructions that did not work, and replacing 2012-08-01 16:12:10 -07:00
test fixes for tests 2012-08-01 22:17:16 +03:00
.gitignore clean exec bits from lib/ansible/*.py, ignore Eclipse/PyDev files 2012-04-14 21:35:51 +02:00
CHANGELOG.md changelog / remove a failed=False 2012-08-01 22:35:07 -04:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Place the freshly built RPM directly into rpm-build/ 2012-08-01 15:25:19 +02:00
MANIFEST.in Include license file in MANIFEST.in. Fixes #284 2012-05-01 10:34:36 -04:00
README.md Update README.md 2012-08-01 09:16:21 -03:00
setup.py Split connection code into submodules. 2012-05-30 20:16:31 -04:00
VERSION Release bump to start development on 0.6 2012-07-04 18:07:19 -04:00

Ansible

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

Read the documentation 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