No description
Find a file
Hugh Saunders 2e07567c16 Retry exec command via ssh_retry
This PR adds the option to retry failed ssh executions, if the failure
is caused by ssh itself, not the remote command. This can be helpful if
there are transient network issues. Retries are only implemented in the
openssh connection plugin and are disabled by default. Retries are
enabled by setting ssh_connection > retries to an integer greater
than 0.

Running a long series of playbooks, or a short playbook against a large
cluster may result in transient ssh failures, some examples logged
[here](https://trello.com/c/1yh6csEQ/13-ssh-errors).

Ansible should be able to retry an ssh connection in order to survive
transient failures.

Ansible marks a host as failed the first time it fails to contact it.
2015-05-18 14:22:52 -07:00
bin slight changes to error handling to align with v1 2015-05-13 11:15:32 -04:00
docs/man Add --list-hosts to man pages. 2015-02-27 08:38:45 -05:00
docsite Add optional 'skip_missing' flag to subelements 2015-05-12 12:52:16 -05:00
examples made special treatment of certain filesystem for selinux configurable 2015-05-15 13:52:27 -04:00
hacking egg_info is now written directly to lib 2015-03-27 12:03:20 -05:00
lib/ansible Retry exec command via ssh_retry 2015-05-18 14:22:52 -07:00
packaging Improve generation of debian changelog 2015-04-09 09:30:56 -04:00
plugins Merge pull request #9835 from resmo/feature/cloudstack-inventory 2015-05-04 11:30:04 -04:00
samples Fix playbook includes so tags are obeyed (v2) 2015-05-11 12:48:03 -05:00
test Adding module_utils tests from v1 to v2 2015-05-17 01:29:40 -05:00
ticket_stubs typofixes - https://github.com/vlajos/misspell_fixer 2014-12-04 22:23:35 +00:00
v1 Retry exec command via ssh_retry 2015-05-18 14:22:52 -07: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 Testing additions and fixes 2015-05-08 13:40:02 -05:00
CHANGELOG.md deprecated nova_compute and added new os_server for openstack to changelog 2015-05-04 12:04:18 -04:00
CODING_GUIDELINES.md
CONTRIBUTING.md Update CONTRIBUTING.md 2014-09-10 13:00:57 -04:00
COPYING
ISSUE_TEMPLATE.md
Makefile Improve generation of debian changelog 2015-04-09 09:30:56 -04:00
MANIFEST.in Add and subtract some things from the tarball 2015-03-06 21:02:40 -08:00
README.md Use correct URL for travis status badge 2015-03-13 10:56:30 -04:00
RELEASES.txt Update releases 2014-11-26 23:29:29 -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 Testing additions and fixes 2015-05-08 13:40:02 -05: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 900 users (and growing). Thanks everyone!

Ansible is sponsored by Ansible, Inc