Forem: Jobin Keecheril

Installing Kubernetes on CentOS

Jobin Keecheril — Tue, 21 Apr 2020 14:09:19 +0000

Kubernetes

Kubernetes is a portable, extensible, open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation. It has a large, rapidly growing ecosystem. Kubernetes services, support, and tools are widely available.

The name Kubernetes originates from Greek, meaning helmsman or pilot. Google open-sourced the Kubernetes project in 2014. Kubernetes combines over 15 years of Google’s experience running production workloads at scale with best-of-breed ideas and practices from the community.

Steps for Installing Kubernetes on CentOS

We will be creating a cluster of 3 machines,
One master node
Two worker nodes

Perform the following steps on Master:

SETTING UP KUBERNETES REPOSITORY

Create a file named kube.repo or file_name.repo inside the directory structure i.e. /etc/yum.repos.d/kube.repo.

Note: The filen_name doesn’t matter but the extension must be repo mandatorily.

[kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

DISABLING SELINUX

To do this, you will first need to turn it off directly

[root@master ~]# setenforce 0 [root@master~]# sed -i --follow-symlinks 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/sysconfig/selinux

SWITCH OFF SWAP

Comment out the reference to swap in /etc/fstab. Start by editing the file:

[root@master ~]# swapoff -a [root@master ~]# vi /etc/fstab

Then comment out the appropriate line, as in:

# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point>   <type>  <options>    <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=1d343a19-bd75-47a6-899d-7c8bc93e28ff /            ext4 errors=remount-ro 0    1
# swap was on /dev/sda5 during installation
#UUID=d0200036-b211-4e6e-a194-ac2e51dfb27d none         swap sw           0    0

ENTERING 1 INTO IPTABLES

Now we will configure iptables to receive bridged network traffic. First edit the sysctl.conf file:
[root@master ~]# vi /etc/sysctl.conf

And add these lines at the end of the file

net/bridge/bridge-nf-call-ip6tables = 1
net/bridge/bridge-nf-call-iptables = 1
net/bridge/bridge-nf-call-arptables = 1

OR
Run these 2 simple commands:

[root@master ~]# echo '1' > /proc/sys/net/bridge/bridge-nf-call-iptables [root@master ~]# echo '1' > /proc/sys/net/bridge/bridge-nf-call-ip6tables

INSTALLING DOCKER AND KUBEADM

Once the package repositories are configured, run the given command to install kubeadm and docker packages.

[root@master ~]# yum install kubeadm docker -y

STARTING AND ENABLING DOCKER AND KUBELET SERVICE

Start and enable kubectl and docker service:

[root@master ~]# systemctl restart docker && systemctl enable docker [root@master ~]# systemctl restart kubelet && systemctl enable kubelet
KUBEADM INITIALIZATION

Run the given command to initialize and setup kubernetes master.
[root@master ~]# kubeadm init
Output:

Note: Take note of the following lines that are inside the red block. You have to execute these three commands on your master.

[root@master ~]# mkdir -p $HOME/.kube [root@master ~]# cp -i /etc/kubernetes/admin.conf $HOME/.kube/config [root@master ~]# chown $(id -u):$(id -g) $HOME/.kube/config

DEPLOY POD NETWORK TO THE CLUSTER
[root@master ~]# kubectl get nodes

This will show the master as not ready. To make the cluster status ready and kube-dns status running, deploy the pod network so that containers of different hosts can communicate with each other. POD network is an overlay network between the worker nodes.

Run the given commands to deploy the network.

[root@master ~]# export kubever=$(kubectl version | base64 | tr -d '\n') [root@master ~]# kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$kubever"

serviceaccount "weave-net" created
clusterrole "weave-net" created
clusterrolebinding "weave-net" created
daemonset "weave-net" created

Now again execute the same command:
[root@master ~]# kubectl get nodes

This time you will see the master is Ready.

[root@master ~]# kubectl get nodes
NAME           STATUS    AGE       VERSION
master                  Ready     2h        v1.7.5

Now let’s add worker nodes to the Kubernetes master nodes.

Perform the following steps on each worker node:

DISABLE SELINUX

Before disabling SELinux set the hostname on both the nodes as ‘worker-node1’ and ‘worker-node2’ respectively for understanding purposes.

[root@worker-node1 ~]# setenforce 0 [root@worker-node1 ~]# sed -i --follow-symlinks 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/sysconfig/selinux

CONFIGURE KUBERNETES REPOSITORIES ON BOTH THE WORKER NODES

Create a file named kube.repo or file_name.repo inside the directory structure i.e. /etc/yum.repos.d/kube.repo.

Note: The filen_name doesn’t matter but the extension must be repo mandatorily.

[kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

SWITCH OFF SWAP

Comment out the reference to swap in /etc/fstab. Start by editing the file:
[root@worker-node1 ~]# swapoff -a [root@worker-node1 ~]# vi /etc/fstab

Then comment out the appropriate line, as in:

# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point>   <type>  <options>    <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=1d343a19-bd75-47a6-899d-7c8bc93e28ff /            ext4 errors=remount-ro 0    1
# swap was on /dev/sda5 during installation
#UUID=d0200036-b211-4e6e-a194-ac2e51dfb27d none         swap sw           0    0

ENTERING 1 INTO IPTABLES

Now we will configure iptables to receive bridged network traffic. First edit the sysctl.conf file:
[root@worker-node1 ~]# vi /etc/sysctl.conf

And add these lines at the end of the file

net/bridge/bridge-nf-call-ip6tables = 1
net/bridge/bridge-nf-call-iptables = 1
net/bridge/bridge-nf-call-arptables = 1

OR
Run these 2 simple commands:
[root@worker-node1 ~]# echo '1' > /proc/sys/net/bridge/bridge-nf-call-iptables [root@worker-node1 ~]# echo '1' > /proc/sys/net/bridge/bridge-nf-call-ip6tables

INSTALLING DOCKER AND KUBEADM ON BOTH WORKER NODES

Once the package repositories are configured, run the given command to install kubeadm and docker packages.

[root@worker-node1 ~]# yum install kubeadm docker -y

STARTING AND ENABLING DOCKER AND KUBELET SERVICE

Start and enable kubectl and docker service:

[root@worker-node1 ~]# systemctl restart docker && systemctl enable docker [root@worker-node1 ~]# systemctl restart kubelet && systemctl enable kubelet

NOW JOIN WORKER NODES TO MASTER

To join worker nodes to Master node, a token is required. Whenever kubernetes master is initialized then in the output we get the required commands and token.
Copy that command and run on both nodes: (We've noted the commands while installing Kubernetes on Master)

[root@worker-node1 ~]# kubeadm join --token a3bd48.1bc42347c3b35851 192.168.1.30:6443

Output of above command would be something like below

[root@worker-node2 ~]# kubeadm join --token a3bd48.1bc42347c3b35851 192.168.1.30:6443
Output

Now verify status of Nodes from Master node using kubectl command

[root@master ~]# kubectl get nodes

NAME           STATUS    AGE       VERSION
master         Ready     2h        v1.7.5
worker-node1   Ready     20m       v1.7.5
worker-node2   Ready     18m       v1.7.5

As we can see master and worker nodes are in ready status. This concludes that kubernetes has been installed successfully and also we have successfully joined two worker nodes. Thus we say our Kubernetes Cluster is Ready! Now we can create pods and services.

Do comment and let me know if I've missed any step or if any modifications are needed. Pointers are always welcomed!;)

Thank you!

Monitoring single-node Ceph cluster using Prometheus & Grafana on AWS

Jobin Keecheril — Mon, 02 Mar 2020 17:39:44 +0000

Basic Information:

Ceph-
Ceph is a free-software storage platform, implements object storage on a single distributed computer cluster, and provides interfaces for object-, block- and file-level storage. Ceph aims primarily for completely distributed operation without a single point of failure, and freely available.

Prometheus-
Prometheus is an open-source systems monitoring and alerting toolkit originally built at SoundCloud. Since its inception in 2012, many companies and organizations have adopted Prometheus, and the project has a very active developer and user community.

Grafana-
Grafana allows you to query, visualize, alert on and understand your metrics no matter where they are stored. It allows to create, explore, and share dashboards with your team and foster a data driven culture.

Integration of Ceph with Prometheus and Grafana on AWS:

Let's divide this into 3 tasks so as to get our desired monitoring tool for ceph
1. Installation & configuration of Ceph
2. Installing & configuring Prometheus
3. Installing & configuring Grafana

NOTE: I'm assuming y'all know the basics of AWS. You need to launch an instance with few prerequisites:
1. Add 3 volumes for osds.
2. Security groups. (Allow All_TCP, HTTP and HTTPS from anywhere)

1. Installation & configuration of Ceph:

ssh-keygen:

[root@ip-10-0-0-100 ~]# vim /etc/ssh/sshd_config
Make these changes in the file:

PermitRootLogin yes
PasswordAuthentication yes

[root@ip-10-0-0-100 ~]# systemctl restart sshd

[root@ip-10-0-0-100 ~]# ssh-keygen

[root@ip-10-0-0-100 ~]# ssh-copy-id root@ip-10-0-0-100

Configure Ceph repo:

[root@ip-10-0-0-100 ~]# vim /etc/yum.repos.d/ceph.repo

[ceph]
name=Ceph packages for $basearch
baseurl=https://download.ceph.com/rpm-nautilus/el7/$basearch
enabled=1
priority=1
gpgcheck=1
gpgkey=https://download.ceph.com/keys/release.asc

[ceph-noarch]
name=Ceph noarch packages
baseurl=https://download.ceph.com/rpm-nautilus/el7/noarch
enabled=1
priority=1
gpgcheck=1
gpgkey=https://download.ceph.com/keys/release.asc

[ceph-source]
name=Ceph source packages
baseurl=https://download.ceph.com/rpm-nautilus/el7/SRPMS
enabled=0
priority=1
gpgcheck=1
gpgkey=https://download.ceph.com/keys/release.asc

Install ceph-deploy

[root@ip-10-0-0-100 ~]# yum install ceph-deploy -y

[root@ip-10-0-0-100 ~]# mkdir ceph-deploy
[root@ip-10-0-0-100 ~]# cd ceph-deploy

Create the cluster:

[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy new {initial-monitor-node(s)}
example: [root@ip-10-0-0-100 ceph-deploy]# ceph-deploy new ip-10-0-0-100

Install Ceph packages:

[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy install {node(s)}
example: [root@ip-10-0-0-100 ceph-deploy]# ceph-deploy install ip-10-0-0-100

Deploy the initial monitor(s) and gather the keys

[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy gatherkeys node
example: [root@ip-10-0-0-100 ceph-deploy]# ceph-deploy gatherkeys ip-10-0-0-100
[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy mon create-initial

Create admin

[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy admin ip-10-0-0-100

Create Mgr

[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy mgr create ip-10-0-0-100

Create Mds

[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy mds create ip-10-0-0-100

Create Osds

[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy osd create --data /dev/xvdb ip-10-0-0-100
[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy osd create --data /dev/xvdc ip-10-0-0-100
[root@ip-10-0-0-100 ceph-deploy]# ceph-deploy osd create --data /dev/xvdd ip-10-0-0-100

Check your cluster's status

[root@ip-10-0-0-100 ceph-deploy]# ceph -s

 cluster:
    id:     5e4cfca2-43b5-13fd2-aee2b4808d95
    health: HEALTH_OK

  services:
    mon: 1 daemons, quorum ip-10-0-0-100 (age 3m)
    mgr: ip-10-0-0-100(active, since 3m)
    osd: 3 osds: 3 up (since 3m), 3 in (since 7h)

  data:
    pools:   0 pools, 0 pgs
    objects: 0 objects, 0 B
    usage:   3.0 GiB used, 18 GiB / 21 GiB avail
    pgs:

2. Installation & configuration of Prometheus:

Update System

[root@ip-10-0-0-100 ~]# yum update -y

Download Prometheus package

Go to official Prometheus downloads downloads page, and copy the URL of Linux “tar” file.

[root@ip-10-0-0-100 ~]# wget https://github.com/prometheus/prometheus/releases/download/v2.16.0/prometheus-2.16.0.linux-amd64.tar.gz

Configure Prometheus

Add a Prometheus user.

[root@ip-10-0-0-100 ~]# useradd --no-create-home --shell /bin/false prometheus

Create needed directories.

[root@ip-10-0-0-100 ~]# mkdir /etc/prometheus

[root@ip-10-0-0-100 ~]# mkdir /var/lib/prometheus

Change the owner of the above directories.

[root@ip-10-0-0-100 ~]# chown prometheus:prometheus /etc/prometheus

[root@ip-10-0-0-100 ~]# chown prometheus:prometheus /var/lib/prometheus

Now go to Prometheus downloaded location and extract it.

[root@ip-10-0-0-100 ~]# tar -xvzf prometheus-2.16.0.linux-amd64.tar.gz

Rename it as per your preference.

[root@ip-10-0-0-100 ~]# mv prometheus-2.16.0.linux-amd64 prometheuspackage

Copy “prometheus” and “promtool” binary from the “prometheuspackage” folder to “/usr/local/bin”.

[root@ip-10-0-0-100 ~]# cp prometheuspackage/prometheus /usr/local/bin/

[root@ip-10-0-0-100 ~]# cp prometheuspackage/promtool /usr/local/bin/

Change the ownership to Prometheus user.

[root@ip-10-0-0-100 ~]# chown prometheus:prometheus /usr/local/bin/prometheus

[root@ip-10-0-0-100 ~]# chown prometheus:prometheus /usr/local/bin/promtool

Copy “consoles” and “console_libraries” directories from the “prometheuspackage” to “/etc/prometheus folder”

[root@ip-10-0-0-100 ~]# cp -r prometheuspackage/consoles /etc/prometheus

[root@ip-10-0-0-100 ~]# cp -r prometheuspackage/console_libraries /etc/prometheus

Change the ownership to Prometheus user

[root@ip-10-0-0-100 ~]# chown -R prometheus:prometheus /etc/prometheus/consoles

[root@ip-10-0-0-100 ~]# chown -R prometheus:prometheus /etc/prometheus/console_libraries

Add and modify Prometheus configuration file.

Configurations should be added to the “/etc/prometheus/prometheus.yml”
Now we will create the prometheus.yml file.

[root@ip-10-0-0-100 ~]# vim /etc/prometheus/prometheus.yml

global:
  scrape_interval: 10s

scrape_configs:
  - job_name: 'prometheus_master'
    scrape_interval: 5s
    static_configs:
      - targets: ['localhost:9090']

save and exit the file

Change the ownership of the file.

[root@ip-10-0-0-100 ~]# chown prometheus:prometheus /etc/prometheus/prometheus.yml

Configure the Prometheus Service File.

[root@ip-10-0-0-100 ~]# vim /etc/systemd/system/prometheus.service

Copy the following content to the file.

[Unit]
Description=Prometheus
Wants=network-online.target
After=network-online.target

[Service]
User=prometheus
Group=prometheus
Type=simple
ExecStart=/usr/local/bin/prometheus \
--config.file /etc/prometheus/prometheus.yml \
--storage.tsdb.path /var/lib/prometheus/ \
--web.console.templates=/etc/prometheus/consoles \
--web.console.libraries=/etc/prometheus/console_libraries

[Install]
WantedBy=multi-user.target

Save and the exit file.

Reload the systemd service.

[root@ip-10-0-0-100 ~]# systemctl daemon-reload

Start the Prometheus service.

[root@ip-10-0-0-100 ~]# systemctl start prometheus

Check service status.

[root@ip-10-0-0-100 ~]# systemctl status prometheus

Access Prometheus Web Interface

Use the following Url to access UI.

http://Server-IP:9090/graph

Then you can see the following interface.

3. Installation & configuration of Grafana:

Installing Grafana via YUM Repository

[root@ip-10-0-0-100 ~]# vim /etc/yum.repos.d/grafana.repo
Add these lines:

[grafana]
name=grafana
baseurl=https://packages.grafana.com/oss/rpm
repo_gpgcheck=1
enabled=1
gpgcheck=1
gpgkey=https://packages.grafana.com/gpg.key
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt

Install Grafana

[root@ip-10-0-0-100 ~]# yum install grafana -y

Enable Grafana Service

[root@ip-10-0-0-100 ~]# systemctl start grafana-server
[root@ip-10-0-0-100 ~]# systemctl enable grafana-server
[root@ip-10-0-0-100 ~]# systemctl status grafana-server

Browse Grafana

http://Your Server IP or Host Name:3000/

Mgr enable dashboard

[root@ip-10-0-0-100 ~]# ceph mgr module enable dashboard --force

Mgr enable Prometheus

[root@ip-10-0-0-100 ~]# ceph mgr module enable prometheus --force

Edit the ceph.conf

[root@ip-10-0-0-100 ~]# vim ceph-deploy/ceph.conf
Add:

[mon]
        mgr initial modules = dashboard

Check Mgr Services

[root@ip-10-0-0-100 ~]# ceph mgr services
{
"prometheus": "http://ip-10-0-0-100.ec2.internal:9283/"
}
Copy this port number i.e. 9283

Edit the prometheus.yml

[root@ip-10-0-0-100 ~]# vim /etc/prometheus/prometheus.yml
Modify: Paste 9283 here

- targets: ['localhost:9283']

Restart prometheus Service

[root@ip-10-0-0-100 ~]# systemctl restart prometheus

Now you have successfully installed prometheus and grafana for ceph monitoring

Let us begin the grafana setup now
a. Login to grafana with default username and password as admin
b. Create a datasource

--->Select Prometheus

Click on Save and Test

c. Click on Create---> Import

Enter 7056 in:
Grafana.com Dashboard
7056

d. Choose Name and Ceph Prometheus data source

Finally we have successfully integrated our Ceph Cluster with Prometheus and Grafana!

Using this we can monitor our ceph storage graphically giving us much more and better insights!

ANSIBLE ARCHITECTURE & WORKING

Jobin Keecheril — Fri, 03 Jan 2020 12:44:49 +0000

Hey guys! Let's look on Ansible architecture and it's working.

Terminologies in Ansible:

Control node

Any machine with Ansible installed. You can run commands and playbooks, invoking /usr/bin/ansible or /usr/bin/ansible-playbook, from any control node. You can use any computer that has Python installed on it as a control node - laptops, shared desktops, and servers can all run Ansible. However, you cannot use a Windows machine as a control node. You can have multiple control nodes.

Managed nodes

The network devices (and/or servers) you manage with Ansible. Managed nodes are also sometimes called “hosts”. Ansible is not installed on managed nodes.

Inventory

A list of managed nodes. An inventory file is also sometimes called a “hostfile”. Your inventory can specify information like IP address for each managed node. An inventory can also organize managed nodes, creating and nesting groups for easier scaling. Inventories can be of two types static and dynamic, dynamic inventory can be covered while you go through Ansible thoroughly.

Modules

The units of code Ansible executes. Each module has a particular use, from administering users on a specific type of database to managing VLAN interfaces on a specific type of network device. You can invoke a single module with a task, or invoke several different modules in a playbook.

Tasks

The units of action in Ansible. You can execute a single task once with an ad-hoc command.

Playbooks

Ordered lists of tasks, saved so you can run those tasks in that order repeatedly. Playbooks can include variables as well as tasks. Playbooks are written in YAML and are easy to read, write, share and understand.

WORKING:

We can classify the Ansible architecture into 3 sections

Ansible Users and Playbooks
Ansible Engine
Hosts and Networking

The Ansible Engine consists of Inventory, API, Modules and Plugins. A user writes playbooks i.e. set of tasks, then the playbook scans the inventory and matches for the listed hosts or IP addresses where the tasks must be executed. Ansible copies all the modules to the managed node and using Python API calls and plugins Ansible completes the given tasks. Once the tasks are completed/executed all the modules are destroyed on the Managed Nodes. Ansible on linux executes the modules on managed hosts using SSH.

Please feel free to correct ;)

automation #devops #ansible #discuss #linux

End of an era?!

Jobin Keecheril — Tue, 19 Nov 2019 12:35:59 +0000

Mirantis acquires Docker!

The complete thread can be read here:
https://analyticsindiamag.com/mirantis-docker-acquisition-enterprise-kubernetes-containers/

docker #mirantis #discuss

Top Social Media platforms

Jobin Keecheril — Mon, 18 Nov 2019 02:25:27 +0000

October’s top #SocialMedia #apps by number of downloads 📲
1️⃣ @WhatsApp
2️⃣ @tiktok_us
3️⃣ @facebook
4️⃣ @messenger
5️⃣ @instagram
6️⃣ @bestSHAREit
7️⃣ @clubfactoryapp
8️⃣ @YouTube
9️⃣ @likee_official
🔟 @Snapchat

Check out: @SensorTower and
https://twitter.com/BrianHHough/status/1196162004026875912?s=19

Which is your fave?

EmergingTech #discuss

Towards Automation

Jobin Keecheril — Wed, 13 Nov 2019 09:06:47 +0000

Ansible is an open source automation platform. It is very simple to setup and yet powerful. Ansible can help you with configuration management, application deployment, task automation. It can also
do IT orchestration, where you have to run tasks in sequence and create a chain of events which must happen on several different servers or devices. Unlike Puppet or Chef it doesn’t use an agent on the remote host. Instead Ansible uses SSH which is assumed to be installed on all the systems you want to manage. Also it’s written in Python which needs
to be installed on the remote host. This means that you don’t have to setup a client server environment before using Ansible, you can just run it from any of your machines and from the client’s point of view there is no knowledge of any Ansible server.

IMPORTANCE OF ANSIBLE

Well before I tell you what is Ansible, it is of utmost importance to understand the problems that were faced before Ansible. Let us take a little flashback to the beginning of networked computing when deploying and managing servers reliably and efficiently has been a challenge. Previously, system administrators managed servers by hand, installing software, changing configurations, and administering services on individual servers. As data centres grew, and hosted applications became more complex, administrators realized they couldn’t scale their manual system’s management as fast as the applications they were enabling. It also 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.

Consider the tedious routine of administering a server fleet. We always need to keep updating, pushing changes, copying files on them etc. These tasks make things very complicated and time consuming.

But let me tell you that there is a solution to the above stated problem. The solution is – Ansible. But before I go ahead to explain you all about Ansible, let me get you familiarized with few Ansible terminologies:

1. Controller Machine: The machine where Ansible is installed, responsible for running the provisioning on the servers you are managing.
2. Inventory: An initialization file that contains information about the servers you are managing.
3. Playbook: The real strength of Ansible lies in its Playbooks. A playbook is like a recipe or an instructions manual which tells Ansible what to do when it connects to each machine. Playbooks are written in YAML, which simplistically could be viewed as XML but human readable.
4. Task: A block that defines a single procedure to be executed, e.g. Install a package.
5. Module: A module typically abstracts a system task, like dealing with packages or creating and changing files. Ansible has a multitude of 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.

ORGANIZATIONAL BENEFITS

Ansible reduces the need for dedicated system administrators.

It is an agentless delivery system that makes it a lot easier to manage switches and storage arrays.

Easy to set up results in higher efficiency and reduced costs.

Ansible lets the organization overcome all the project complexities to increase productivity.

USE OF ANSIBLE

JOB OPPORTUNITIES

According to ZipRecruiter, Ansible developers are earning $121,045 annually.
Top companies like Oracle, BOEING, IBM, Capgemini, Target, and so on are hiring Ansible developers.
Become eligible to apply for over 27K jobs available in INDIA for Ansible developers.
An individual without a graduate level computer science degree can also land a high-paying job as an Ansible expert.
Ansible Automation Engineer

Keep Automating!

Written by Jobin Keecheril & Aditi Munde