No description
Find a file
Dag Wieers 9a5a61bdca hacking/: PEP8 compliancy (#24683)
- Make PEP8 compliant
2017-05-16 18:52:07 +01:00
.github Move summary to be next to where github places the commit message. (#22368) 2017-03-07 18:00:22 +01:00
bin Fix timeout issue in ansible-connection (#24556) 2017-05-13 18:28:14 +05:30
contrib pep8 fixes for contrib (#24344) 2017-05-09 16:38:08 -05:00
docs Limit sphinx version on python 2.6. (#24678) 2017-05-17 01:00:15 +08:00
examples Update hosts.yaml (#24513) 2017-05-11 15:01:20 -07:00
hacking hacking/: PEP8 compliancy (#24683) 2017-05-16 18:52:07 +01:00
lib/ansible ansible/vars/: PEP8 compliancy (#24685) 2017-05-16 18:51:27 +01:00
packaging Add prompt to release playbook regarding completion of CHANGELOG edits 2017-05-11 16:28:07 -05:00
test hacking/: PEP8 compliancy (#24683) 2017-05-16 18:52:07 +01:00
ticket_stubs Remove obsolete ticket stubs. 2016-12-08 11:35:20 -05:00
.coveragerc Enable codecov.io and add coverage grouping. 2017-05-15 19:14:05 +08:00
.gitattributes
.gitignore Enable codecov.io and add coverage grouping. 2017-05-15 19:14:05 +08:00
.gitmodules Code cleanup. 2016-12-08 11:35:04 -05:00
.mailmap add mailmap entries for @resmo 2017-04-09 11:56:37 +02:00
.yamllint Lint YAML files under test/ 2016-11-11 14:50:57 -08:00
ansible-core-sitemap.xml Remove remnants of obsolete fireball mode. 2016-12-09 16:56:34 -07:00
CHANGELOG.md New network/avi modules in 2.4 (#24293) 2017-05-04 13:40:04 +01:00
CODING_GUIDELINES.md A couple more places where compat.six was used converted to module_utils.six (#22976) 2017-03-27 14:41:31 -04:00
CONTRIBUTING.md
COPYING
docsite_requirements.txt Fixes the build issue pertaining to sphinx-build which is required to build ansible (#22480) 2017-03-14 14:19:46 -07:00
Makefile added epub entry for makefile 2017-05-01 13:41:04 -04:00
MANIFEST.in Include .yamllint in manifest so yamllint works. 2017-04-12 10:59:52 -07:00
MODULE_GUIDELINES.md Move GUIDELINES.md from modules repo (#19313) 2016-12-14 11:46:14 -05:00
README.md Remove obsolete files and instructions. (#19079) 2016-12-09 12:42:29 -05:00
RELEASES.txt updated release info 2017-05-03 18:21:32 -04:00
requirements.txt Move to using a requirements.txt to install the python packages. (#21430) 2017-02-15 06:58:09 -08:00
ROADMAP.rst Update ROADMAP (#20002) 2017-01-16 11:36:53 +00:00
setup.py Include .git_keep files in role template skeleton (#24381) 2017-05-09 09:57:30 -04:00
shippable.yml Run vyos_command Network tests in Shippable (#24514) 2017-05-12 12:49:12 +01:00
tox.ini update the flake8 config in tox.ini 2017-04-05 09:43:37 -07:00
VERSION Bumping devel version to 2.4.0 2017-03-15 09:42:01 -05:00

PyPI version 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 https://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 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.
  • For releases 1.8 - 2.2, 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

Licence

GNU Click on the Link to see the full text.