f6a09bc4c1
commit ea14bbfb52587bf5b97b5577c0439b01cb0b4836 Merge:82819a9285aaf8Author: Michael DeHaan <michael.dehaan@gmail.com> Date: Sun Jul 15 14:38:28 2012 -0400 Merge branch 'devel' of https://github.com/skvidal/ansible into skvidal_mount commit285aaf836cMerge:634c11732b6879Author: Seth Vidal <skvidal@fedoraproject.org> Date: Mon Jul 16 12:42:21 2012 -0400 Merge remote-tracking branch 'upstream/devel' into devel * upstream/devel: (52 commits) format fixes to make fetch more usable ... commit634c11748eAuthor: Seth Vidal <skvidal@fedoraproject.org> Date: Thu Jul 12 01:16:00 2012 -0400 fix a bunch of small bugs in mount module - test with bind and local mounts commitfcfd73de71Author: Seth Vidal <skvidal@fedoraproject.org> Date: Wed Jul 11 20:46:14 2012 -0400 fix some obvious bugs pointed out by #ansible commit13c3080383Author: Seth Vidal <skvidal@fedoraproject.org> Date: Wed Jul 11 19:35:34 2012 -0400 mount/fstab editor
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
- 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