No description
Find a file
Brian Coca 647170b040 introducing ALSO YAML inventory (#28596)
* introducing ALSO YAML inventory

* Copy edits

(cherry picked from commit c3550b58ed)
2017-09-06 21:57:24 -07:00
.github Add setup for test, docs and packaging labels (#28926) 2017-09-01 11:10:37 -04:00
bin Create persistent socket path using port and connection type (#28492) 2017-08-23 18:28:44 -04:00
contrib fixed incorrect endpoint selection in azure_rm.py 2017-09-01 11:49:56 -07:00
docs introducing ALSO YAML inventory (#28596) 2017-09-06 21:57:24 -07:00
examples fixed typo 2017-08-29 11:49:29 -04:00
hacking [cloud] Update RDS parameter group for boto3 (#25345) 2017-08-28 12:52:22 -04:00
lib/ansible fix check mode for solaris enable/disable (#29049) 2017-09-06 18:11:57 -07:00
packaging Azure acs module (azure_rm_acs.py) (#28522) 2017-08-29 17:59:38 -07:00
test Improve handling of first CI run for new branch. (#29070) 2017-09-06 16:40:48 -07:00
ticket_stubs
.coveragerc
.gitattributes
.gitignore Ignore autogenerated _maintained.rst and config.rst (#28925) 2017-09-01 15:15:45 +01:00
.gitmodules
.mailmap
.yamllint
ansible-core-sitemap.xml
CHANGELOG.md added azure_rm_functionapp/facts to CHANGELOG 2017-08-30 15:18:58 -07:00
CODING_GUIDELINES.md
CONTRIBUTING.md
COPYING
docsite_requirements.txt
Makefile Made the applicable targets as PHONY (#27996) 2017-08-10 17:35:58 -04:00
MANIFEST.in powershell setup fixes (#27516) 2017-07-31 12:16:26 -07:00
MODULE_GUIDELINES.md
README.md
RELEASES.txt Updating RELEASES and packaging vars for 2.3.2 final release 2017-08-04 15:20:41 -05:00
requirements.txt
ROADMAP.rst docs: fix community meetings link (#27264) 2017-07-25 09:23:01 -04:00
setup.py On Py3, nonexistent files raise OSError (#28899) 2017-08-31 17:47:26 -04:00
shippable.yml Revert "Remove windows tests so that we can workaround a timeout running all windows tests on shippable" 2017-09-06 15:26:41 -07:00
tox.ini
VERSION New release v2.4.0.0-0.1.rc1 2017-09-06 13:36:33 -07: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.

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.