No description
Find a file
Jeroen Hoekx c5cae87eca Refactor inventory code out of Runner.
This introduces the Inventory class.

Playbook uses the internals of Runner to limit the number of hosts to poll
asynchronously. To accomodate this, Inventory can be restricted to specific
hosts.
2012-04-16 09:16:28 +02:00
bin Refactor inventory code out of Runner. 2012-04-16 09:16:28 +02:00
docs/man manpage updates 2012-04-13 19:40:40 -04:00
examples Looping! With items! See examples/playbook/loop_with_items.yml for details 2012-04-14 09:55:24 -04:00
hacking Update env-setup script to make it work better 2012-03-18 12:28:22 -04:00
lib/ansible Refactor inventory code out of Runner. 2012-04-16 09:16:28 +02:00
library comment typos 2012-04-13 11:19:36 +01:00
test Warn if no hosts matched 2012-04-11 21:05:46 -04:00
.gitignore Fixup RPM building: Makefile, Spec File, .gitignore 2012-03-10 14:22:11 -05:00
ansible.spec make dist be ?dist so if it is not there you don't get any noise 2012-04-05 13:28:56 -04:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Disable ohai test as it's hanging for whatever reason, but doesn't do this in real life. 2012-03-31 11:18:26 -04:00
MANIFEST.in Update packaging WRT AUTHORS.md 2012-03-26 22:30:48 -04:00
README.md Patch process info. 2012-03-31 11:38:06 -04:00
setup.py Because folks on RHEL 6 (not CentOS 6) have some issues with asciidoc, do not build the asciidoc from 2012-03-15 20:21:10 -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

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

http://michaeldehaan.net