ansible

Design Principles

• Have an extremely simple setup process with a minimal learning curve.
• Manage machines 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.
• Join a Working Group, an organized community devoted to a specific technology domain or platform.
• Submit a proposed code update through a pull request to the devel branch.
• Talk to us before making larger changes to avoid duplicate efforts. This not only helps everyone know what is going on, but it also helps save time and effort if we decide some changes are needed.
• For a list of email lists, IRC channels and Working Groups, see the Communication page

Branch Info

• The devel branch corresponds to the release actively under development.
• The stable-2.X branches correspond to stable releases.
• Create a branch based on devel and set up a dev environment if you want to open a PR.
• See the Ansible release and maintenance page for information about active branches.

Roadmap

Based on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.7, 2.8). The Ansible Roadmap page details what is planned and how to influence the roadmap.

Authors

Ansible was created by Michael DeHaan and has contributions from over 5000 users (and growing). Thanks everyone!

Ansible is sponsored by Red Hat, Inc.