No description
b9e3b053f9
not being consistent between runs, even though there wasn't an error. Now we'll just check the final change counts, which should be just as solid and lead to less churn in the events file. |
||
---|---|---|
bin | ||
docs/man | ||
examples | ||
hacking | ||
lib/ansible | ||
library | ||
test | ||
.gitignore | ||
ansible.spec | ||
COPYING | ||
Makefile | ||
MANIFEST.in | ||
README.md | ||
setup.py |
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
- ansible-project mailing list
- irc.freenode.net: #ansible
Patch Instructions
Contributions to the core and modules are greatly welcome.
- Required Process:
- Submit github pull requests to the "ansible/integration" branch
- 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 pull requests to the 'master' branch instead of the integration branch.
- Sending pull requests to mpdehaan's personal ansible fork.
Author
Michael DeHaan -- michael.dehaan@gmail.com