You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Serge van Ginderachter be58808fe4 inventory script parser: do not add all the groups to *all* group 11 years ago
bin Fixes #4777 add --force-handlers option to run handlers even if tasks fail 11 years ago
docs/man Adding a man page for ansible-vault 11 years ago
docsite Documentation updates for accelerate mode improvements 11 years ago
examples Change default gathering policy, add to docs. 11 years ago
hacking Add tesing deps installation into hacking/README 11 years ago
legacy Various tests using datafiles are being moved into the integration test framework (tests_new right now). 11 years ago
lib/ansible inventory script parser: do not add all the groups to *all* group 11 years ago
library Merge branch 'file_fixes_agg' of https://github.com/bcoca/ansible into bcoca-file_fixes_agg 11 years ago
packaging Merge pull request #6053 from cgtx/devel 11 years ago
plugins Correct overly broad import from chube in linode inventory script 11 years ago
test Merge pull request #6586 from sivel/probline-logic-fix 11 years ago
.gitignore Add generated test files to .gitignore 11 years ago
CHANGELOG.md Update changelog for force-handlers 11 years ago
CODING_GUIDELINES.md Update CODING_GUIDELINES.md 11 years ago
CONTRIBUTING.md Update CONTRIBUTING.md 11 years ago
COPYING license file should be in source tree 13 years ago
MANIFEST.in Add some docs/examples 12 years ago
Makefile Adding a man page for ansible-vault 11 years ago
README.md Update README.md 11 years ago
RELEASES.txt Updating CHANGELOG/RELEASES in devel for 1.5.3 and older releases 11 years ago
VERSION Set version to 1.6 11 years ago
setup.py Added ansible-vault to the installer 11 years ago

README.md

PyPI version

Ansible

Ansible is a radically simple configuration-management, application deployment, task-execution, and multinode orchestration engine.

Read the documentation and more at http://ansible.com/

Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release. You can find instructions here for a variety of platforms. If you want a tarball of the last release, go to releases.ansible.com and you can also install with pip.

Design Principles

  • Have a dead simple setup process and a minimal learning curve
  • Be super fast & parallel by default
  • Require no server or client daemons; use existing SSHd
  • Use a language that is both machine and human friendly
  • Focus on security and easy auditability/review/rewriting of content
  • Manage remote machines instantly, without bootstrapping
  • Allow module development in any dynamic language, not just Python
  • Be usable as non-root
  • Be the easiest IT automation system to use, ever.

Get Involved

  • Read Contributing.md for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
  • All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use "git rebase" vs "git merge" for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed.
  • irc.freenode.net: #ansible

Branch Info

  • Releases are named after Van Halen songs.
  • The devel branch corresponds to the release actively under development.
  • Various release-X.Y branches exist for previous releases
  • We'd love to have your contributions, read "CONTRIBUTING.md" for process notes.

Author

Michael DeHaan -- michael@ansible.com

Ansible, Inc