Blog Details

Ansible For Everyone – Part 1: 100 days of Cloud: Day 32

+1
0
+1
0
+1
0
+1
0
+1
0

DAY 32- Ansible For Everyone – Part 1 – Day Thirty Two

100 days of Cloud on GitHub – Read On iCTPro.co.nz – Read on Dev.to


Why you should read this blog Series?

If you are working on NetworkOps, SecOps, DevOps, ITOps & anyone who wants to automate their infrastructure.

Why Ansible?

Automation Automation Automation

  • Orchestrate complex processes on an enterprise scale.
  • Simple Automation and Management.
  • No Agent – Agentless.
  • Ansible executes locally
  • Open Source solution for automation.
  • Works on both Windows and Linux.
  • Can be used on Public cloud and On-Prem.
  • Cloud, Network & security automation.
Image Playbook

Ansible-core

  • In simple it’s the CLI of ansible.

Playbook

  • YAML templates are used to deploy the required infrastructure.
  • Components of Playbook are Plays, Modules, Plugins, Inventory

Plays

  • Top-level specifications for a group of tasks

Modules

  • Most of the Modules are written in python and in windows it uses Powershell. These are the components with internal logic.

Plugins

  • It enables the expansion of Ansible features.

Inventory

Multiple playbooks

Roles

  • Reusable Playbooks

Collections

  • Collections can have Modules, playbooks, Roles, Plugins Docs, and Tests.


✅Connect with me on Twitter
🤝🏽Connect with me on Linkedin
🧑🏼‍🤝‍🧑🏻 Read more post on dev.to or iCTPro.co.nz
💻 Connect with me on GitHub