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
James Cammarata f0d3284ead Adding more unit tests for ssh connection plugin 9 years ago
bin Transform tracebacks into unicode before printing 9 years ago
contrib Merge pull request #14297 from keedya/devel 9 years ago
docs Merge pull request #14810 from chouseknecht/docker_network_proposal 9 years ago
docsite Fix various mispellings 9 years ago
examples Support strategy_plugins setting in a configuration file 9 years ago
hacking fixed typo 9 years ago
lib/ansible Little improvement in flow 9 years ago
packaging Add python-setuptools to the requirements for running ansible as 9 years ago
samples
test Adding more unit tests for ssh connection plugin 9 years ago
ticket_stubs Small type 9 years ago
.coveragerc
.gitattributes
.gitignore now generate list of playbook ojbect directives 9 years ago
.gitmodules
.travis.yml Adding irc notifications to travis config 9 years ago
CHANGELOG.md added new modules and feature data 9 years ago
CODING_GUIDELINES.md
CONTRIBUTING.md
COPYING
ISSUE_TEMPLATE.md added note for verbosity 9 years ago
MANIFEST.in added galaxy data 9 years ago
Makefile only send event if tqm exists 9 years ago
PULL_REQUEST_TEMPLATE.md Put the advice to the user as comments in the template 9 years ago
README.md trigger jenkins integration tests 9 years ago
RELEASES.txt The 2.0 release has a name now 9 years ago
ROADMAP.md series of changes based on PR comments 9 years ago
VERSION Correct VERSION in the devel branch 9 years ago
ansible-core-sitemap.xml adding sitemap for swiftype to core 9 years ago
setup.py
test-requirements.txt
tox.ini

README.md

PyPI version PyPI downloads Build Status

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 Led Zeppelin songs. (Releases prior to 2.0 were 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.dehaan/gmail/com) and has contributions from over 1000 users (and growing). Thanks everyone!

Ansible is sponsored by Ansible, Inc