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
Cosmin Luță fba4d9232d Prevent facter stderr messages from confusing ansible 13 years ago
bin Fixup the previous sudo_user support patch to work with playbooks. 13 years ago
docs/man Update manpage to mention -U (--sudo-user). 13 years ago
examples
hacking
lib/ansible Fixup the previous sudo_user support patch to work with playbooks. 13 years ago
library Prevent facter stderr messages from confusing ansible 13 years ago
packaging
test Add tests for new advanced inventory features (groups of groups, group variables) in the default INI format file. 13 years ago
.gitignore
CHANGELOG.md Update development changelog. 13 years ago
COPYING
MANIFEST.in
Makefile
README.md
VERSION
setup.py

README.md

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