A presentation on Ansible explaining the overview and how it helps the technologist to cater their administrative operations.

2. Introduction
To
Ansible

3. We will be learning
• What is Ansible?
• Why do we need Ansible?
• Advantages of using Ansible
• What Ansible can do?
• Ansible Architecture
• Some Ansible terms, to help you understand
Ansible better.

4. What
is
Ansible?

5. Ansible is one of the
tools of DevOps

6. What
is
DevOps?

7. DevOps is a development
method that combines
software development (Dev)
with IT operations (Ops).

8. Ansible - Definition
It is a simple Configuration Management
(automation) tool that helps us in deploying
systems and applications easily.

9. Why do we need Ansible?
• Previously, system administrators managed servers by hand,
installing software, changing configurations, and
administering services on individual servers.
• As data centers grew, and hosted applications became more
complex, administrators realized they couldn’t scale their
manual systems management as fast as the applications they
were enabling.
• It hampered the velocity of the work of the developers since
the development team was agile and releasing software
frequently, but IT operations were spending more time
configuring the systems. That’s why server provisioning and
configuration management tools came to flourish.

10. Why Ansible?
• Free / open source application
• Agentless
• Python/ YAML based
• Ready to use modules
• Custom modules can be added
• Configuration roll-back in case of error
• Simple and human readable
• Self documenting

11. Ansible - Advantages
Simple Agentless
Powerful Efficient

12. What Ansible Can Do?
Provisioning
Configuration
Management
Application
Deployment
Security
Orchestration

13. How is it’s Architecture?

14. Ansible - Terminologies
1. Controller Machine: The machine where Ansible is installed.
2. Inventory: An initialization file that contains information about
the hosts/ servers you are managing.
3. Task: A block that defines a single procedure to be executed, e.g.
Install a package.
4. Playbook: The entry point for Ansible provisioning, where the
automation is defined through tasks using YAML format.

15. Ansible - Terminologies
5. Module: A module describes a system task, like dealing with
packages or creating files. Ansible has built-in modules, but you
can also create custom ones.
6. Role: A pre-defined way for organizing playbooks and other files
in order to facilitate sharing and reusing portions of a
provisioning.
7. Play: A provisioning executed from start to finish is called a play.
In simple words, execution of a playbook is called a play.
8. Facts: Global variables containing information about the system,
like network interfaces or operating system.
9. Handlers: Used to trigger service status changes, like restarting or
stopping a service.
[Cont.,]

16. Ansible - Installation
YUM (RHEL/ CentOS 7)
• wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-
7.noarch.rpm
• yum localinstall epel-release-latest-7.noarch.rpm
• yum --enablerepo=epel install Ansible
PIP
• pip install ansible

17. Understanding Ansible Playbook
The output of the Ansible-playbook is as below