Ansible
Ansible is a radically simple IT automation system. It handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation, and multi-node orchestration. Ansible makes complex changes like zero-downtime rolling updates with load balancers easy. More information on the Ansible website.
This is the ansible community package. The ansible python package contains a set of independent Ansible collections that are curated by the community, and it pulls in ansible-core. The ansible-core python package contains the core runtime and CLI tools, such as ansible and ansible-playbook, while the ansible package contains extra modules, plugins, and roles.
ansible follows semantic versioning. Each major version of ansible depends on a specific major version of ansible-core and contains specific major versions of the collections it includes.
Design Principles
Have an extremely simple setup process and 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.
Use Ansible
You can install a released version of Ansible with pip or a package manager. See our Installation guide for details on installing Ansible on a variety of platforms.
Reporting Issues
Issues with plugins and modules in the Ansible package should be reported on the individual collection’s issue tracker. Issues with ansible-core should be reported on the ansible-core issue tracker. Issues with the ansible package build process or serious bugs or vulnerabilities in a collection that are not addressed after opening an issue in the collection’s issue tracker should be reported on ansible-build-data’s issue tracker.
Refer to the Communication page for a list of support channels if you need assistance from the community or are unsure where to report your issue.
Get Involved
Read Community Information for ways to contribute to and interact with the project, including forum information and how to submit bug reports and code to Ansible or Ansible collections.
Join Forum Groups you are interested in, which are groups of users that are involved in specific topics, like a technology domain or platform.
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 reference to the Forum, a list of Matrix and IRC channels, and Working Groups, see the Communication page
Coding Guidelines
We document our Coding Guidelines in the Developer Guide. We also suggest you review:
Branch Info
The Ansible package is a ‘batteries included’ package that brings in ansible-core and a curated set of collections. Ansible uses semantic versioning (for example, Ansible 5.6.0).
The Ansible package has only one stable branch, called ‘latest’ in the documentation.
See Ansible release and maintenance for information about active branches and their corresponding ansible-core versions.
Refer to the ansible-build-data repository for the exact versions of ansible-core and collections that are included in each ansible release.
Roadmap
Based on team and community feedback, an initial roadmap will be published for a major version (example: 5, 6). The Ansible Roadmap details what is planned and how to influence the roadmap.
License
GNU General Public License v3.0 or later
See COPYING for the full license text.
10 maintainers
Metadata
10 maintainers
Release files for ansible 11.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ansible-11.4.0.tar.gz | 42.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansible-11.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 96.6 MB
Release files / ansible-11.4.0.tar.gz
| Download URL | ansible-11.4.0.tar.gz |
|---|---|
| Size | 42.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d25a7f26bf5821f8043bc806019822fd2810bd65e6b6bafb698bbeedadba72bf
|
|
BLAKE2b-256 checksum How to use checksums |
f1e30cca4bd57b2c5c39d403d369182080c5eecedeb58df74e39ea4a563ddff5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 25, 2025.
Transparency logRelease files / ansible-11.4.0-py3-none-any.whl
| Download URL | ansible-11.4.0-py3-none-any.whl |
|---|---|
| Size | 54.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb56f6e5d5b08f69499a76f0972ac0b88ddc488ada1f386129ba40cb0b5c6ec7
|
|
BLAKE2b-256 checksum How to use checksums |
58d530374bb92397544d4ba1ca391234e66bfe495c0f094816dc17101c5e18a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 25, 2025.
Transparency log
