No description
Find a file
Nikhil Singh daf44331c4 Code review changes
1. Passing the module to the various functions so that they can use module.fail_json and module.exit_json methods inside.
2. Because of point 1, install and remove methods do not return anything. Instead, they use the module functions itself.
3. Move the import statement (for apt and apt_pkg) inside main function so on import error, we can use module.fail_json to print the error.
2012-07-26 17:29:15 +05:30
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 Small change to previous patch, make ranges of hosts inclusive. 2012-07-24 20:10:05 -04:00
hacking small tweaks to --help for hacking/test-module 2012-07-23 19:33:26 -04:00
lib/ansible Things that happen inside multiprocessing shouldn't make side effects, ergo append ansible_facts only 2012-07-25 21:30:49 -04:00
library Code review changes 2012-07-26 17:29:15 +05:30
packaging fixed debian changelog format 2012-07-20 14:33:35 +02:00
test Small change to previous patch, make ranges of hosts inclusive. 2012-07-24 20:10:05 -04:00
.gitignore clean exec bits from lib/ansible/*.py, ignore Eclipse/PyDev files 2012-04-14 21:35:51 +02:00
CHANGELOG.md update changelog 2012-07-25 21:05:01 -04:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Added a host expansion feature to ansible's inventory parsing 2012-07-24 12:38:52 -07:00
MANIFEST.in Include license file in MANIFEST.in. Fixes #284 2012-05-01 10:34:36 -04:00
README.md update versions mentioned in README.md 2012-07-04 18:07:19 -04: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 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