You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Michael DeHaan b7c3fd1246 failed should not be in the result returns for a module upon success 12 years ago
bin blue on black, tears on a river, push on a shove, it don't mean much 12 years ago
docs/man Small change to previous patch, make ranges of hosts inclusive. 12 years ago
examples Rename: postgresql.yaml -> postgresql.yml 12 years ago
hacking readlink -f does not work on OS X. Replaced with a python solution 12 years ago
lib/ansible Raise exception when sudo user does not exist 12 years ago
library failed should not be in the result returns for a module upon success 12 years ago
packaging Smiting Debian packaging instructions that did not work, and replacing 12 years ago
test fixes for tests 12 years ago
.gitignore clean exec bits from lib/ansible/*.py, ignore Eclipse/PyDev files 12 years ago
CHANGELOG.md changelog updates 12 years ago
COPYING license file should be in source tree 12 years ago
MANIFEST.in Include license file in MANIFEST.in. Fixes #284 12 years ago
Makefile Place the freshly built RPM directly into rpm-build/ 12 years ago
README.md Update README.md 12 years ago
VERSION Release bump to start development on 0.6 12 years ago
setup.py Split connection code into submodules. 12 years ago

README.md

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