mirror of https://github.com/ansible/ansible.git
Mirror of https://github.com/ansible/ansible.git
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.
efac68b636
This flag will show playbook output from non-failing commands. -v is also added to /usr/bin/ansible, but not yet used. I also gutted some internals code dealing with 'invocations' which allowed the callback to know what module invoked it. This is not something 0.5 does or needed, so callbacks have been simplified. |
13 years ago | |
---|---|---|
bin | 13 years ago | |
docs/man | 13 years ago | |
examples | 13 years ago | |
hacking | 13 years ago | |
lib/ansible | 13 years ago | |
library | 13 years ago | |
packaging | 13 years ago | |
test | 13 years ago | |
.gitignore | 13 years ago | |
CHANGELOG.md | 13 years ago | |
COPYING | 13 years ago | |
MANIFEST.in | 13 years ago | |
Makefile | 13 years ago | |
README.md | 13 years ago | |
VERSION | 13 years ago | |
setup.py | 13 years ago |
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
- ansible-project mailing list
- irc.freenode.net: #ansible
Branch Info
- The master branch corresponds to release 0.4 "Unchained".
- Major bug fixes will be periodically made to the master branch.
- The devel branch corresponds to release 0.5 "Amsterdam".
- 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