Snippet from Wikipedia: Ansible (software)

Ansible is an open-source software provisioning, configuration management, and application-deployment tool enabling infrastructure as code. It runs on many Unix-like systems, and can configure both Unix-like systems as well as Microsoft Windows. It includes its own declarative language to describe system configuration. Ansible was written by Michael DeHaan and acquired by Red Hat in 2015. Ansible is agentless, temporarily connecting remotely via SSH or Windows Remote Management (allowing remote PowerShell execution) to do its tasks.



Ansible is a free-software platform for configuring and managing computers which combines multi-node software deployment, ad hoc task execution, and configuration management. (Reference: “Achieving Rolling Updates and Continuous Deployment with Zero Downtime”) It manages nodes over SSH or over PowerShell. (Reference: Getting Started | Ansible, 2014-02-06) Modules work over JSON and standard output and can be written in any programming language. The system uses YAML to express reusable descriptions of systems. (Reference: Ansible: CM, Deployment, and Ad Hoc Task Execution All in One, Publisher DZone, 18 April 2012)

Michael DeHaan, the author of the provisioning server application Cobbler and co-author of the Func framework for remote administration, developed the platform.<ref>

</ref> It is included as part of the Fedora distribution of Linux, owned by Red Hat Inc., and is also available for Red Hat Enterprise Linux, CentOS, and Scientific Linux via Extra Packages for Enterprise Linux (EPEL) as well as for other operating systems.<ref>


Ansible, Inc. (originally AnsibleWorks, Inc.) was the company set up to commercially support and sponsor Ansible.<ref>


</ref> It was acquired by Red Hat in October 2015.<ref>



The name “Ansible” references the fictional instantaneous hyperspace communication system (featured in Orson Scott Card's Ender's Game,<ref>

</ref> and originally invented by Ursula K. Le Guin for her 1966 novel Rocannon's World).


As with most configuration management software, Ansible distinguishes two types of servers: controlling machines and nodes. First, there is a single controlling machine which is where orchestration begins. Nodes are managed by a controlling machine over SSH. The controlling machine describes the location of nodes through its inventory.

To orchestrate nodes, Ansible deploys modules to nodes over SSH. Modules are temporarily stored in the nodes and communicate with the controlling machine through a JSON protocol over the standard output.<ref name=“Ansible_in_Depth”>

</ref> When Ansible is not managing nodes, it does not consume resources because no daemons or programs are executing for Ansible in the background.<ref name=“The_Benefits_of_Agentless_Architecture” />

In contrast with popular configuration management software &mdash; such as Chef, Puppet, and CFEngine &mdash; Ansible uses an agentless architecture.<ref name=“The_Benefits_of_Agentless_Architecture”>

</ref> With an agent-based architecture, nodes must have a locally installed daemon that communicates with a controlling machine. With an agentless architecture, nodes are not required to install and run background daemons to connect with a controlling machine. This type of architecture reduces the overhead on the network by preventing the nodes from polling the controlling machine.<ref name=“The_Benefits_of_Agentless_Architecture” />

Design goals

The design goals of Ansible<ref name=“Ansible_in_Depth” /> include:

  • Minimal in nature. Management systems should not impose additional dependencies on the environment.<ref name=“The_Benefits_of_Agentless_Architecture” />
  • Consistent.
  • Secure. Ansible does not deploy agents to nodes. Only OpenSSH is required, which is thoroughly tested.<ref name=“The_Benefits_of_Agentless_Architecture” />
  • Highly reliable. When carefully written, an Ansible playbook can be idempotent, in order to prevent unexpected side-effects on the managed systems.<ref name=“Achieving_Rolling_Updates_and_Continuous_Deployment_with_Zero_Downtime”>

    </ref> It has to be noted, anyway, that it is perfectly possible to have a poorly written playbook that is not idempotent.

  • Low learning curve. Playbooks use an easy and descriptive language based on YAML and Jinja templates.


Modules are considered to be the units of work in Ansible. Each module is mostly standalone and can be written in a standard scripting language (such as Python, Perl, Ruby, bash, etc.). One of the guiding properties of modules is idempotency, which means that even if an operation is repeated multiple times (e.g. upon recovery from an outage), it will always place the system into the same state.<ref name=“Ansible_in_Depth” />

Inventory configuration

The Inventory is a description of the nodes that can be accessed by Ansible. By default, the Inventory is described by a configuration file, in INI format, whose default location is in


. The configuration file lists either the IP address or hostname of each node that is accessible by Ansible. In addition, nodes can be assigned to groups.<ref>


An example configuration file:


This configuration file specifies three nodes. The first node is specified by an IP address and the latter two nodes are specified by hostnames. Additionally, the latter two nodes are grouped under the


group name.

Ansible can also be pointed towards a custom “Dynamic Inventory” script, which can pull data from any different software system.


Playbooks express configurations, deployment, and orchestration in Ansible.<ref>

</ref> The Playbook format is YAML. Each Playbook maps a group of hosts to a set of roles. Each role is represented by calls to Ansible call tasks.

Platform support

Control machines must have Python 2.6 or 2.7. Operating systems supported on control machines include most Linux and Unix distributions, such as Red Hat, Debian, CentOS, OS X, BSD, and Ubuntu among others.

Managed nodes must have Python 2.4 or later. For managed nodes with Python 2.5 or earlier, the


package is also required.<ref name=“Intro_Getting_Started” /> Ansible can manage Windows<ref>

</ref> nodes starting from version 1.7.<ref name=“Intro_Getting_Started”>


Cloud integration

Ansible can deploy to virtualization environments and public and private cloud environments, including Amazon Web Services, CloudStack, DigitalOcean, Eucalyptus Cloud, Google Cloud Platform, KVM, Microsoft Azure, OpenStack, Rackspace, SoftLayer, VMware, and XenServer.<ref name=“Ansible_in_Depth” />

Big data integration

Ansible can deploy big data, storage, and analytics environments, including Hadoop, Riak, and Aerospike. In these environments, Ansible helps manage each node's resource consumption, consuming little CPU time and memory in the process. Furthermore, Ansible provides monitoring capabilities that measure such properties as available CPU resources, which can help in the supervision of these nodes.<ref name=“Ansible_in_Depth” />

See also


Etymology of the name Ansible from Fiction

An ansible is a fictional device capable of instantaneous or superluminal (faster than light) communication. It can send and receive messages to and from a corresponding device over any distance whatsoever with no delay.


See also

External sites


ansible.txt · Last modified: 2016/10/10 09:52 by Cloud Monk Losang Jinpa PhD MCSE MCT Microsoft Cloud Ecosystem DevOps Engineer