No description
Find a file
Spencer Krum 3887173c2c Use cfacter instead of facter if possible
CFacter is the facter replacement written in C++. It is available from
the puppetlabs repo.
2015-07-04 09:13:20 -07:00
bin switched to argv[0] from __file__ as it is what we actually wanted 2015-06-09 17:29:46 -04:00
docs/man Re-Generate man pages 2015-05-05 16:55:09 +02:00
docsite Merge pull request #11370 from halberom/doc_magic_var 2015-07-02 18:17:07 -04:00
examples added ramfs to selinux ignored filesystems 2015-07-02 17:25:05 -04:00
hacking minor docs reformat 2015-06-03 22:19:26 -04:00
lib/ansible Use cfacter instead of facter if possible 2015-07-04 09:13:20 -07:00
packaging Add six as a dependency for packaging 2015-06-02 11:43:35 -07:00
plugins Merge pull request #11261 from schrodervictor/adds-elasticache-to-ec2-dynamic-inventory 2015-06-30 16:51:11 -04:00
samples Fix playbook includes so tags are obeyed (v2) 2015-05-11 12:48:03 -05:00
test assertRaises should be given an exception type. Fixes 11441 2015-06-30 11:02:33 -05:00
ticket_stubs typofixes - https://github.com/vlajos/misspell_fixer 2014-12-04 22:23:35 +00:00
v1 cloudstack: fix domain name is not unique, use full path 2015-06-26 09:25:26 +02:00
.coveragerc Add tox and travis-ci support 2015-03-13 08:20:24 -04:00
.gitattributes updated changelog with 1.8.2-4 content, added .gitattributes 2015-02-23 22:20:33 +00:00
.gitignore Add tox and travis-ci support 2015-03-13 08:20:24 -04:00
.gitmodules Re-adding submodules after moving things around 2015-05-03 22:30:51 -05:00
.travis.yml Disable docs checks 2015-07-01 07:24:15 -07:00
CHANGELOG.md added bundler to changelog 2015-06-29 20:46:04 -04: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 Config might be important for issues. 2015-05-07 22:26:16 +00:00
Makefile avoid removing test all~ file 2015-06-05 18:42:14 -04:00
MANIFEST.in Add and subtract some things from the tarball 2015-03-06 21:02:40 -08:00
README.md Update README.md 2015-06-10 15:42:30 +02:00
RELEASES.txt Backporting release info/changelog stuff to devel 2015-05-05 10:28:43 -05:00
setup.py Testing additions and fixes 2015-05-08 13:40:02 -05:00
test-requirements.txt Testing additions and fixes 2015-05-08 13:40:02 -05:00
tox.ini Correct typo 2015-06-11 09:03:20 -07:00
VERSION Fixing the VERSION file to match the expected "version release" format 2015-04-07 08:22:56 -05: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 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