RedHat Ansible Training
In "Introduction to Course and Learning Environment," you learn about the goals for
this training and how to provision and connect to your lab environment.
"Ansible Architecture" reviews the different Ansible offerings and how they work.
In "Ansible Engine," you learn about the key components of Ansible Engine and how
they work together.
In "Ansible Tower," you learn about the function of Ansible Tower, how its
interface maps onto the key components of Ansible Engine, and how to demonstrate
it.
In "Ansible Networking," you learn about how Ansible works with network devices and
how to demonstrate this.
Foundation in Ansible
This course provides a foundation in Ansible, the open source project, and
introduces the Red Hat Ansible Automation products.
It introduces DevOps, automation, and the role of Ansible in automation. It covers
the scope of the Red Hat Ansible Automation family of products and what Ansible
users can achieve.
It provides foundational knowledge of Ansible’s core architecture and how Ansible
supports different platforms, including servers, cloud, and virtualization.
Architecture
Define what is meant by "Ansible automation"
Describe, in detail, benefits of automation in DevOps
Describe Ansible’s role
Describe role of automation in DevOps
Identify who can use Ansible inside company
Describe Ansible family of products
Describe role and scope of Ansible Engine
Describe scope of Ansible Automation’s features
Outline main platforms Ansible supports and automates
Explain Ansible’s agentless architecture
Understand how Ansible works with servers
Understand how Ansible works with network devices
Describe Ansible’s support for different deployment platforms (cloud,
virtualization, etc.)
Identify where to get more information about Ansible
Describe technical requirements of Ansible
Describe control node’s role
Describe how Ansible communicates
Describe purpose of Ansible inventory
Understand types of Ansible inventories—static, dynamic, in-memory
Understand main components of static inventory—hosts, groups, children
Create static inventory to be used with Ansible
Ansible Engine
Use ad hoc commands to run simple Ansible tasks
Understand role of a module
Describe classes of modules that come with Ansible
Understand common modules: setup, ping, debug, package
Understand role of facts and setup module
Describe simplicity of Ansible Playbooks
Describe typical Ansible Playbook
Use tasks to be run by Ansible
Use YAML to write simple playbooks
Use playbook variables to optimize Ansible Playbook code
Use handlers to start, stop, restart a service during an Ansible run
Use embedded Ansible core modules in Ansible Playbook
Use ansible-playbook command to run more complex orchestration
Use loops and conditionals to orchestrate how tasks are executed by Ansible
Describe purpose of Ansible role
Describe advantage of using a role
Describe structure of Ansible role
Describe possibilities provided by Ansible Galaxy
-----------------------------------------------------------------------------------
---------------------------------
Red Hat Ansible Engine is an automation platform that is comprised of three
fundamental components:
First, the playbooks make up and contain the automation language itself.
Second, this code base is the automation engine that Ansible applies to create and
manage the infrastructure itself.
Third, Red Hat Ansible Tower is the enterprise platform that can manage and perform
automation across the enterprise.
-----------------------------------------------------------------------------------
----------------------------------
Ansible has a number of qualities that help make it the most rapidly growing
automation platform in the world.
Ansible is simple. Playbooks are human and machine readable, with no special coding
skills required, and even people in your IT organization who do not know Ansible
can read an Ansible Playbook and understand what is happening.
This simplicity also means that it is easy to install and you can start to do real
work with it quickly—usually in just minutes.
Ansible also works like you think—tasks are always executed in order and all
together. This simplicity ensures that you can get started quickly.
Ansible is powerful. Simplicity is great, but to be really useful, you also need
the powerful features that ensure you can model even the most complex of IT
workflows.
Ansible is complete automation—it is able to deploy applications, manage
orchestration, and configure the infrastructure, networks, operating systems, and
services that you are already using today.
Together, Ansible’s capabilities allow you to orchestrate the entire application
and environment life cycle, regardless of where it is deployed.
Ansible is agentless. Ansible relies on industry-standard and trusted SSH and WinRM
protocols to automate. There are no agents or other software to install, and no
additional firewall ports to open. With no need to separately set up a management
infrastructure, Ansible further reduces the activation energy required from your
team to start automating today.
-----------------------------------------------------------------------------------
-------------------------------------
Ansible is CROSS PLATFORM, with agentless support for Linux, Windows, and UNIX and
all major OS variants—physical, virtual, cloud, and network.
Ansible is HUMAN READABLE, and YAML can perfectly describe and document every
aspect of your application environment and is accessible across all members of the
DevOps team.
Ansible can hold a PERFECT DESCRIPTION OF AN APPLICATION. Every change can be made
via playbooks, ensuring everyone is on the same page.
Ansible can be VERSION CONTROLLED with infrastructure and configuration as code.
Playbooks are plain text. Treat them like code in your existing version control
system.
Ansible supports DYNAMIC INVENTORIES, capturing all of the servers 100% of the
time, regardless of infrastructure or location.
Ansible provides ORCHESTRATION THAT PLAYS WELL WITH OTHERS, including HP Service
Activator, Puppet, Jenkins, Red Hat Satellite Server, and more. Homogenize existing
environments by leveraging current toolsets and update mechanisms.
