No description
Find a file
2016-03-10 11:41:17 +01:00
bin draft 1st release of ansible-console 2016-03-07 20:25:21 -05:00
contrib Detect empty cache files in openstack inventory 2016-03-09 11:54:30 -06:00
docs Merge pull request #14810 from chouseknecht/docker_network_proposal 2016-03-07 15:34:12 -05:00
docsite docsite, cloudstack: add limited VPC support 2016-03-10 11:41:17 +01:00
examples draft 1st release of ansible-console 2016-03-07 20:25:21 -05:00
hacking avoid private attributes 2016-03-10 01:00:33 -05:00
lib/ansible Merge pull request #14892 from dagwieers/patch-14 2016-03-09 23:57:56 -05:00
packaging Add python-setuptools to the requirements for running ansible as 2016-01-13 17:24:47 -08:00
samples Break apart a looped dependency to show a warning when parsing playbooks 2015-10-27 12:39:42 -07:00
test removed test_infra from setup as it fails when using --tags 2016-03-10 00:29:32 -05:00
ticket_stubs Small type 2016-02-27 12:36:08 +01:00
.coveragerc
.gitattributes
.gitignore now generate list of playbook ojbect directives 2016-02-25 16:48:37 -05:00
.gitmodules remove old dead code 2015-08-27 12:27:38 -04:00
.travis.yml Don't use notices for travis irc messages 2016-03-08 15:35:04 -05:00
ansible-core-sitemap.xml adding sitemap for swiftype to core 2016-01-11 11:30:28 -05:00
CHANGELOG.md draft 1st release of ansible-console 2016-03-07 20:25:21 -05:00
CODING_GUIDELINES.md
CONTRIBUTING.md
COPYING
ISSUE_TEMPLATE.md added note for verbosity 2016-02-24 19:22:15 -05:00
Makefile only send event if tqm exists 2016-01-13 10:18:36 -05:00
MANIFEST.in added galaxy data 2016-01-12 16:22:01 +01:00
PULL_REQUEST_TEMPLATE.md Put the advice to the user as comments in the template 2016-02-23 12:15:24 +01:00
README.md trigger jenkins integration tests 2015-12-08 10:03:20 -05:00
RELEASES.txt The 2.0 release has a name now 2015-11-14 09:59:04 +05:30
ROADMAP.md series of changes based on PR comments 2016-02-11 20:56:33 -05:00
setup.py renamed shell to console in last spot 2016-03-09 13:57:45 -05:00
test-requirements.txt
tox.ini Start a pyflakes section to cut down on extra messages that we don't agree are problems 2015-11-11 07:50:19 -08:00
VERSION Correct VERSION in the devel branch 2015-12-04 15:17:24 -08:00

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