No description
Find a file
Toshio Kuratomi 9f7b0dfc30 Remove automatic use of system six
* Enable the pylint no-name-in-module check.  Checks that identifiers in
  imports actually exist.  When we do this, we also have to ignore
  _MovedItems used in our bundled six.  This means pylint won't check
  for bad imports below ansible.module_utils.six.moves but that's
  something that pylint punts on with a system copy of six so this is
  still an improvement.
* Remove automatic use of system six.  The exec in the six code which
  tried to use a system library if available destroyed pylint's ability
  to check for imports of identifiers which did not exist (the
  no-name-in-module check).  That test is important enough that we
  should sacrifice the bundling detection in favour of the test.
  Distributions that want to unbundle six can replace the bundled six in
  ansible/module_utils/six/__init__.py to unbundle.  however, be aware
  that six is tricky to unbundle.  They may want to base their efforts
  off the code we were using:

  2fff690caa/lib/ansible/module_utils/six/__init__.py

* Update tests for new location of bundled six Several code-smell tests
  whitelist the bundled six library.  Update the path to the library so
  that they work.

* Also check for basestring in modules as the enabled pylint tests will
  also point out basestring usage for us.
2017-07-25 15:58:23 -07:00
.github Add maintainer for gce_labels module 2017-07-25 09:36:33 -04:00
bin ansible-connection Python3 fix (#26441) 2017-07-05 14:07:26 -04:00
contrib updated readme with vault and 2.4 inv plugins (#26361) 2017-07-24 16:37:59 -04:00
docs docs: fix community meetings link (#27264) 2017-07-25 09:23:01 -04:00
examples add any_errors_fatal global config 2017-07-03 17:05:44 -04:00
hacking Use Boto3 for ec2_group Fixes #23507 (#25340) 2017-07-17 12:03:31 +10:00
lib/ansible Remove automatic use of system six 2017-07-25 15:58:23 -07:00
packaging Fix pycrypto backend setting to work when multiple distros are specified in DEB_DIST 2017-07-13 12:13:54 -07:00
test Remove automatic use of system six 2017-07-25 15:58:23 -07:00
ticket_stubs Remove obsolete ticket stubs. 2016-12-08 11:35:20 -05:00
.coveragerc Docker image updates for integration tests. (#26054) 2017-06-23 12:45:38 -07:00
.gitattributes avoid exporting files useless to dist 2017-06-23 15:56:43 -04:00
.gitignore Remove old/obsolete directories from .gitignore (#26680) 2017-07-15 10:19:58 +02: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 Remove automatic use of system six 2017-07-25 15:58:23 -07:00
CODING_GUIDELINES.md Use pycodestyle instead of pep8 (#25947) 2017-07-13 11:46:31 -07: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 Add make target for printing version (#26657) 2017-07-12 13:51:38 +01:00
MANIFEST.in include .psm1 files in MANIFEST (#27286) 2017-07-26 07:46:05 +10:00
MODULE_GUIDELINES.md Add a direct link to the maintainer's file (#26450) 2017-07-06 09:19:27 +01:00
README.md Fix installation instructions link in the README (#24754) 2017-05-18 08:09:53 +01:00
RELEASES.txt Replace RELEASES.txt with the latest version. 2017-07-10 23:18:51 -07:00
requirements.txt Cyptography pr 20566 rebase (#25560) 2017-06-27 06:00:15 -07:00
ROADMAP.rst docs: fix community meetings link (#27264) 2017-07-25 09:23:01 -04:00
setup.py Maintain symlinks in setup.py sdist, build, and install commands (#27149) 2017-07-24 09:25:12 -07:00
shippable.yml Use subset of Windows tests for "all" tests. (#26830) 2017-07-14 16:51:32 -07:00
tox.ini Update tox.ini to use ansible-test. 2017-06-30 16:41:30 -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.

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.