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 Scherer 7bffc1a29e add a default path in ~/.ansible to place plugins, so ansible is a bit
more usable out of the box as simple user
2014-12-11 23:33:51 +01:00
bin used del instead of pop, removed unused pprint import 2014-11-20 15:36:55 -05:00
docs/man Document the --offline parameter to galaxy init 2014-12-09 10:50:10 -08:00
docsite Fix typo for the word "maintaining" 2014-12-11 02:10:44 -06:00
examples typofixes - https://github.com/vlajos/misspell_fixer 2014-12-04 22:23:35 +00:00
hacking typofixes - https://github.com/vlajos/misspell_fixer 2014-12-04 22:23:35 +00:00
lib/ansible add a default path in ~/.ansible to place plugins, so ansible is a bit 2014-12-11 23:33:51 +01:00
packaging Ansible is available in the main Gentoo repository 2014-12-02 08:42:49 +01:00
plugins Merge pull request #9530 from sivel/rax-inventory-access-network 2014-11-17 12:12:13 -08:00
test Merge pull request #9764 from bcoca/moar_tests 2014-12-11 01:03:54 -05:00
ticket_stubs typofixes - https://github.com/vlajos/misspell_fixer 2014-12-04 22:23:35 +00:00
v2 typofixes - https://github.com/vlajos/misspell_fixer 2014-12-04 22:23:35 +00:00
.gitignore Updated DEB build workflow 2014-06-20 16:09:02 -04:00
.gitmodules Add branch info for our submodules 2014-10-28 15:55:24 -04:00
CHANGELOG.md Have changelog reflect 1.8.1 on devel branch 2014-11-26 23:29:05 -05:00
CODING_GUIDELINES.md CODING_GUIDELINES: Fix typo: / => \ 2014-06-28 08:21:15 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-09-10 13:00:57 -04:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
ISSUE_TEMPLATE.md Replacing the issues template with the updated one from examples 2014-09-09 11:10:49 -05:00
Makefile Tell nose to include branches in its coverage reporting 2014-10-21 16:41:16 -04:00
MANIFEST.in prune vs exclude 2014-11-27 20:07:24 -05:00
README.md Update contributor info in README 2014-11-18 18:42:55 -05:00
RELEASES.txt Update releases 2014-11-26 23:29:29 -05:00
setup.py Need to include extras in setup to accomodate future windows extras modules 2014-11-29 18:11:10 -05:00
VERSION Bumping files for 1.9 2014-11-25 16:49:45 -06:00

PyPI version PyPI downloads

Ansible

Ansible is a radically simple IT automation system. It handles configuration-management, application deployment, cloud provisioning, ad-hoc task-execution, and multinode orchestration - including trivializing things like zero downtime rolling updates with load balancers.

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 decide to go with the development branch, be sure to run "git submodule update --init --recursive" after doing a checkout.

If you want to download a tarball of a release, go to releases.ansible.com, though most users use yum (using the EPEL instructions linked above), apt (using the PPA instructions linked above), or "pip install ansible".

Design Principles

  • Have a dead simple setup process and a minimal learning curve
  • Manage machines very quickly and in parallel
  • Avoid custom-agents and additional open ports, be agentless by leveraging the existing SSH daemon
  • Describe infrastructure in a language that is both machine and human friendly
  • Focus on security and easy auditability/review/rewriting of content
  • Manage new remote machines instantly, without bootstrapping any software
  • 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 Community Information 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.
  • Users list: ansible-project
  • Development list: ansible-devel
  • Announcement list: ansible-announce - read only
  • irc.freenode.net: #ansible

Branch Info

  • Releases are named after Van Halen songs.
  • The devel branch corresponds to the release actively under development.
  • As of 1.8, modules are kept in different repos, you'll want to follow core and extras
  • Various release-X.Y branches exist for previous releases.
  • We'd love to have your contributions, read Community Information for notes on how to get started.

Authors

Ansible was created by Michael DeHaan (michael@ansible.com) and has contributions from over 900 users (and growing). Thanks everyone!

Ansible is sponsored by Ansible, Inc