Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications — automate in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com/ansible/
Find a file
Michael DeHaan 432dae769e Merge pull request #669 from nix85/fix_mount_mod
Standardizing the mount module
2012-07-24 04:40:26 -07:00
bin
docs/man
examples fix module name in examples 2012-07-23 21:06:24 -04:00
hacking small tweaks to --help for hacking/test-module 2012-07-23 19:33:26 -04:00
lib/ansible Tweak the way chained callbacks work 2012-07-23 22:12:26 -04:00
library Standardizing the mount module 2012-07-24 17:00:08 +05:30
packaging fixed debian changelog format 2012-07-20 14:33:35 +02:00
test Remove YAML inventory tests since this is now deprecated. 2012-07-20 11:31:28 -04:00
.gitignore
CHANGELOG.md changelog update 2012-07-23 19:34:18 -04:00
COPYING
Makefile
MANIFEST.in
README.md
setup.py
VERSION

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

Branch Info

  • Releases are named after Van Halen songs.
  • The master branch corresponds to release 0.5 "Amsterdam".
  • The devel branch corresponds to release 0.6 "Cabo".
  • All feature work happens on the development branch.
  • Major bug fixes will be made to the master branch, but not minor ones.
  • 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
    • Fixing bugs instead of sending bug reports.
    • 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