No description
Find a file
Michael DeHaan bb1d72f2b4 Merge pull request #235 from skvidal/devel
fix for issue #230 - handle template taking 3  args
2012-04-25 09:05:55 -07:00
bin Unused imports 2012-04-21 12:04:21 -04:00
docs/man Fix man page option description indentation. 2012-04-17 11:39:51 -04:00
examples Add another example to file_secontext.yml 2012-04-22 00:14:40 -07:00
hacking Make it possible to use facts from hosts in templates for other hosts. 2012-04-21 12:45:37 -04:00
lib/ansible fix for issue #230 - handle template taking 3 args 2012-04-25 11:59:19 -04:00
library Bugfix for issue no. 229 2012-04-25 21:02:44 +08:00
packaging Version bump for 0.3 release 2012-04-23 21:11:43 -04:00
test Fix tests for facter and the ansible_facts API. 2012-04-24 17:01:48 +02:00
.gitignore clean exec bits from lib/ansible/*.py, ignore Eclipse/PyDev files 2012-04-14 21:35:51 +02:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile debian packaging 2012-04-23 19:17:01 -04:00
MANIFEST.in Move setup.py stuff back to top level as "make sdist" was not working, plus, it makes sources cleaner. 2012-04-21 11:56:06 -04:00
README.md Update README to indicate new branch name 2012-04-23 21:18:57 -04:00
setup.py Add requirements in setup.py. 2012-04-22 16:33:19 +02:00
VERSION Version bump for integration branch (soon to be renamed 'devel'), didn't update package 2012-04-23 21:14:48 -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/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