No description
Find a file
Michael DeHaan 3d72260887 Make it such that modules with no arguments work fine in playbooks (like ping, which is
non-sensical, but also if the user wrote a module that took none)
2012-04-21 11:26:48 -04:00
bin Update bin/ansible to fix usage of inventory API + no more verbose option 2012-04-19 09:21:21 -04:00
docs/man Fix man page option description indentation. 2012-04-17 11:39:51 -04:00
examples Port shouldn't be in this example 2012-04-16 22:04:23 -04:00
hacking Update hacking with MANPATH. Correct hacking README details. 2012-04-17 10:53:32 -04:00
lib/ansible Make it such that modules with no arguments work fine in playbooks (like ping, which is 2012-04-21 11:26:48 -04:00
library Fix bug in src. Should not code this early :) 2012-04-20 08:09:43 -04:00
packaging Merge pull request #181 from leucos/integration 2012-04-19 15:57:22 -07:00
test Fix bug in src. Should not code this early :) 2012-04-20 08:09:43 -04:00
.gitignore Fixup RPM building: Makefile, Spec File, .gitignore 2012-03-10 14:22:11 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Move packaging related things out of the root directory: 2012-04-19 13:50:09 -04:00
README.md Patch process info. 2012-03-31 11:38:06 -04:00
VERSION Docs build using version in the VERSION file. 2012-04-17 10:45:17 -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