This presentation on Ansible will help you understand why Ansible is needed, what is Ansible, Ansible as a pull configuration tool, Ansible architecture, Ansible playbook, Ansible inventory, how Ansible works, Ansible tower and you will also see a use case on how Hootsuite used Ansible. Increasing team productivity and improving business outcomes have now become easy with Ansible. Ansible is a simple, popular, agent-free tool in the automation domain. Ansible is a tool that allows you to create and control three key areas within the operations environment of software development lifecycle. The first one is IT automation which allows you to write instructions to automate the IT professional's work that you would typically do manually in the past, the second is configuration management which allows you to maintain consistency of all systems in the infrastructure and the third is automatic deployment which allows you to deploy applications automatically on a variety of environments. Now let us get started and understand Ansible and it's architecture. Below topics are explained in this Ansible presentation: 1. Why Ansible? 2. What is Ansible? 3. Ansible - Pull configuration tool 4. Ansible architecture 5. Playbook 6. Inventory 7. Working of Ansible 8. Ansible tower 9. Use case by Hootsuite Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become en expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today. Who should take this course? DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit. 1. This DevOps training course will be of benefit the following professional roles: 2. Software Developers 3. Technical Project Managers 4. Architects 5. Operations Support 6. Deployment engineers 7. IT managers 8. Development managers Learn more at: https://www.simplilearn.com/

2. Why Ansible?
What is Ansible?
Ansible - Pull configuration tool
Ansible architecture
Playbook
What’s in it for you?
Inventory
Working of Ansible
Ansible Tower
Use case by Hootsuite

3. Why Ansible?

4. This is Sam, a system administrator. He is
responsible for his company’s infrastructure
Why Ansible?
[Web Servers]
[Database Servers]

5. Why Ansible?
He must install Apache on all the 3 web servers and
MySQL on the two database servers
[Web Servers]
[Database Servers]

6. Why Ansible?
That’s easy! Wouldn’t take much time either
[Web Servers]
[Database Servers]

7. Why Ansible?
But what if the number of servers increase?
[Web Servers]
[Database Servers]

8. The same task must be repeated multiple times.
Moreover, humans are prone to make errors
Why Ansible?
[Web Servers]
[Database Servers]

9. Why Ansible?
This is where Ansible comes to the rescue
[Web Servers]
[Database Servers]

10. Why Ansible?
With Ansible, a code is written once for the
installation and deployed multiple times
[Web Servers]
[Database Servers]

11. Why Ansible?
Sam can now work on more productive tasks rather
than the repetitive ones
[Web Servers]
[Database Servers]

12. What is Ansible?

13. Sounds great, right?
But what is Ansible?
What is Ansible?

14. IT automation
What is Ansible?
Instructions are written to
automate the IT
professional’s work
Ansible is a tool that provides:

15. IT automation Configuration management
What is Ansible?
Instructions are written to
automate the IT
professional’s work
Consistency of all
systems in the
infrastructure is
maintained
Ansible is a tool that provides:

16. Ansible is a tool that provides:
IT automation
Instructions are written to
automate the IT
professional’s work
Configuration management
Consistency of all
systems in the
infrastructure is
maintained
Automatic deployment
Applications are deployed
automatically on a variety
of environments
What is Ansible?

17. Ansible - Pull configuration tool

18. Pull configuration: Nodes check with the server periodically
and fetch the configurations from it
Ansible - Pull configuration tool

19. Pull configuration: Nodes check with the server periodically
and fetch the configurations from it
Push configuration: Server pushes configuration to
the nodes
Ansible - Pull configuration tool

20. Push configuration: Server pushes configuration to
the nodes
Unlike Chef and Puppet, Ansible is push
type configuration management tool
Ansible - Pull configuration tool

21. Ansible architecture

22. Local Machine
Node
Module
Inventory Node
Node
The local machine is where Ansible is installed
Ansible architecture

23. Ansible architecture
Local Machine
Node
Module
Inventory Node
Node
Nodes are the systems to be configured. They are
controlled by the local machine

24. Ansible architecture
Local Machine
Node
Module
Inventory Node
Node
Module is a collection of configuration code files

25. Playbooks
Ansible architecture
Local Machine
Node
Module
Inventory Node
Node
These configuration code files are called playbooks

26. Ansible architecture
Local Machine
Node
Module
Inventory Node
Node
Inventory is a document that groups the nodes under
specific labels
Playbooks

27. Ansible architecture
Local Machine
Node
Module
Inventory Node
Node
The local machine connects to the nodes through an SSH
client
SSH
Playbooks

28. Playbook

29. The core of Ansible
is it’s playbook
Playbook
Playbook

30. So, what is a
playbook?
Playbook
Playbook

31. Playbook
Playbooks are the instructions to
configure the nodes
Playbook

32. Playbook
Playbooks are the instructions to
configure the nodes
They are written in YAML, a language
used to describe data
Playbook

33. Did you know, YAML
stands for “YAML Ain’t
Markup Language”
Playbook
Playbooks are the instructions to
configure the nodes
They are written in YAML, a language
used to describe data
Playbook

34. Let’s have a look at the
structure of a playbook
Playbook
Playbooks are the instructions to
configure the nodes
They are written in YAML, a language
used to describe data
Playbook

35. Let’s have a look at the
structure of a playbook
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

36. Playbook begins with ‘--
-’
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

37. A playbook is a list of
plays
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

38. Host is the target for the
play
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

39. Each play has a list of
tasks
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

40. Each element in the list
of tasks is given a name
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

41. The name is followed by
instructions to execute
the task
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

42. Have a look at the first
task
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

43. Module yum is used to
install the apache
service
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

44. Simple, isn’t it?
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

45. But where do these host
names come from?
---
-name: play 1
hosts: webserver
tasks:
-name: install apache
yum:
name: apache
state: present
-name: start apache
service:
name: apache
state: start
-name: play 2
hosts: databaseserver
tasks:
-name: install MySQL
yum:
name: MySQL
state: present
Playbook

46. Inventory

47. This is why we have an
inventory
Inventory

48. An inventory file
classifies nodes into
groups
[webserver]
web1.machine
web2.machine
web3.machine
[databaseserver]
db1.machine
Inventory

49. We have two groups
here: ‘webserver’ and
‘databaseserver’
[webserver]
web1.machine
web2.machine
web3.machine
[databaseserver]
db1.machine
Inventory

50. The hostnames of the
nodes are specified
under the group name
[webserver]
web1.machine
web2.machine
web3.machine
[databaseserver]
db1.machine
Inventory

51. Working of Ansible

52. Local Machine
NodeNode Node
Ansible is installed only on the local machine.
This makes Ansible agentless
Working of Ansible

53. Local Machine
NodeNode Node
The playbook and inventory are written at the
local machine
Working of Ansible

54. Local Machine
NodeNode Node
The local machine connects to the nodes
through SSH
SS
H
Working of Ansible

55. Local Machine
NodeNode Node
The local machine gathers the facts of each
node. Facts indicate the state of the nodes
SS
H
Working of Ansible

56. Local Machine
NodeNode Node
The playbooks are sent to the nodes
SS
H
Working of Ansible

57. Local Machine
NodeNode Node
The playbooks are now executed. This
configures the nodes to their desired states
SS
H
Working of Ansible

58. Working of Ansible
So, let’s see if you can
answer a simple
question…

59. Working of Ansible
What is the major
leverage Ansible has
over Chef and Puppet?

60. Working of Ansible
Leave your answers on
the comment!

61. Ansible Tower

62. Now, let’s have a look at
the icing on the cake-
Ansible Tower!
Ansible Tower

63. Ansible Tower is a framework for Ansible
Ansible Tower

64. Ansible Tower is a framework for Ansible
It provides a GUI. Thus, reducing the
dependency on the command prompt
window
Ansible Tower

65. Ansible Tower is a framework for Ansible
It provides a GUI. Thus, reducing the
dependency on the command prompt
window
Instead of typing long commands, tasks
can now be performed in a single click
Ansible Tower

66. Use case by Hootsuite

67. Hootsuite is a social media
management system
Use case by Hootsuite

68. They assist businesses in
campaigning across
social media platforms
Use case by Hootsuite

69. But as they gained
popularity, a crisis struck
Use case by Hootsuite

70. Servers had to be rebuilt continuously
Use case by Hootsuite

71. Unfortunately, there was no standard
documentation and the entire process
relied on memory
Use case by Hootsuite

72. This is when the need for Ansible was
realised
Use case by Hootsuite

73. Now, playbooks are written to deploy
servers providing a standardization
Use case by Hootsuite

74. Servers are built and rebuilt in a matter of
seconds
Use case by Hootsuite

75. Use case by Hootsuite
Servers are built and rebuilt in a matter of
seconds

76. Key Takeaways
Ansible- pull configuration tool
Ansible architecture
What is ansible?Why ansible?
playbook Inventory

77. Key Takeaways
Ansible towerWorking of ansible Use case by hootsuite