8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

RED HAT BLOG

BLOG MENU 

Latest posts

By product

By channel

A system administrator's guide to

getting started with Ansible - FAST!
March 12, 2018 Curtis Rempel

SHARE

< Back to all posts Tags: Automation, Technical Account Managers

Are you a typical system administrator with too much work and not enough time?
Does the prospect of making a simple DNS server change or adjusting kernel
parameters across your entire server farm make you cringe? Or worse, making
changes based on variable system characteristics such as installed memory or
release version? Are the developers in your organization speaking another
language to you with this whole DevOps thing?  

Red Hat Ansible Automation is an agentless human readable automation tool that
uses
We use SSHon
cookies toour
orchestrate configuration
websites to deliver management,
our online services. application
Details about how we usedeployment,
cookies and howand
you
mayprovisioning
disable them are
inset out inor
a flat our Privacy Statement.
multi-tier By using It
environment. this
iswebsite
basedyouonagree to our use
the open of cookies.
source

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 1/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

Ansible technology, which has become one of the world’s most popular open
source IT automation technologies.

This blog post will help you understand the basics of Ansible and how it can be
used in your role as a system administrator to more efficiently manage your
systems.

Before getting started, we need to define some terminology:

Control node: the host on which you use Ansible to execute tasks on the
managed nodes

Managed node: a host that is configured by the control node

Host inventory: a list of managed nodes

Ad-hoc command: a simple one-off task

Playbook: a set of repeatable tasks for more complex configurations

Module: code that performs a particular common task such as adding a user,
installing a package, etc.

Idempotency: an operation is idempotent if the result of performing it once is

exactly the same as the result of performing it repeatedly without any intervening
actions

Environment
The environment in this post consists of one control node (vm1) and four
managed nodes (vm2, vm3, vm4, vm5) all running in a virtual environment with a
minimal Red Hat Enterprise Linux 7.4 installation. For sake of simplicity, the
control node has the following entries in the /etc/hosts file:

192.168.102.211 vm1 vm1.redhat.lab

192.168.102.212 vm2 vm2.redhat.lab
192.168.102.213 vm3 vm3.redhat.lab
192.168.102.214 vm4 vm4.redhat.lab
We use cookies on our websites
192.168.102.215 vm5to vm5.redhat.lab
deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 2/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

For ease of use I'm going to give my system user passwordless sudo in this
demonstration, your security policy may vary, and Ansible can handle a wide
variety of privilege escalation use-cases. This user account has been configured
for privilege escalation via the following entry in the /etc/sudoers file:

%wheel ALL=(ALL) NOPASSWD: ALL

This is only an example and you may wish to use your own sudo configuration
variant.  

Finally, SSH public key authentication has been configured and tested for this
user account from the control node to each of the managed nodes.

Installation
Ansible for Red Hat Enterprise Linux 7 is located in the Extras channel. If you’re
using Red Hat Enterprise Linux 6, enable the EPEL repository. For Extra Packages
for Enterprise Linux (EPEL), this solution in the customer portal may also be
helpful. On Fedora systems you will find Ansible in the base repository.

Once the appropriate repository has been configured, it’s a quick and simple
install:

[curtis@vm1 ~]$ sudo yum install -y ansible

Let’s check the version:

[curtis@vm1 ~]$ ansible --version

ansible 2.4.1.0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/curtis/.ansible/plugins/module
ansible python module location = /usr/lib/python2.7/site-packages/ansib
executable location = /bin/ansible
python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150

Note the default configuration file, and that python is required and present in our
We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
minimal Red Hat Enterprise Linux 7.4 installation.
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 3/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

Configuration
Since we have already configured the managed nodes with a user account,
privilege escalation, and SSH public key authentication, we will continue by
configuring the control node.

The configuration of the control node consists of both an Ansible configuration

file and a host inventory file.

Configuration file
As we have just discovered, the default configuration file is
/etc/ansible/ansible.cfg

You can modify this global configuration file or make a copy specific to a
particular directory. The order in which a configuration file is located is as follows:

ANSIBLE_CONFIG (environment variable)

ansible.cfg (per directory)

~/.ansible.cfg (home directory)

/etc/ansible/ansible.cfg (global)

In this post, I will be using a minimal configuration file in the home directory of the
user account added previously:

[curtis@vm1 ~]$ cat ansible.cfg

[defaults]
inventory = $HOME/hosts

Host inventory
The default host inventory file is /etc/ansible/hosts but can be changed via the
configuration
We use cookies on ourfile (as shown
websites above)
to deliver or services.
our online by using the about
Details -i option onuse
how we the ansible
cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.
command. We will be using a simple static inventory file. Dynamic inventories are

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 4/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

also possible, but outside the scope of this post.

Our host inventory file is as follows:

[webservers]
vm2
vm3

[dbservers]
vm4

[logservers]
vm5

[lamp:children]
webservers
dbservers

We have defined four groups: webservers on vm2 and vm3, dbservers on vm4,
logservers on vm5 and lamp which consists of the webservers and dbservers
groups.

Let’s confirm that all hosts can be located using this configuration file:

[curtis@vm1 ~]$ ansible all --list-hosts

hosts (4):
vm5
vm2
vm3
vm4

Similarly for individual groups, such as the webservers group:

[curtis@vm1 ~]$ ansible webservers --list-hosts

hosts (2):
vm2
vm3

Now that we have validated our host inventory, let’s do a quick check to make
We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
maysure allthem
disable our are
hosts areinup
set out ourand running.
Privacy WeBy
Statement. will dothis
using thiswebsite
usingyou
anagree
ad-hoc command
to our use of cookies.
that uses the ping module:
https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 5/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

[curtis@vm1 ~]$ ansible all -m ping

vm4 | SUCCESS => {
"changed": false,
"failed": false,
"ping": "pong"
}
vm5 | SUCCESS => {
"changed": false,
"failed": false,
"ping": "pong"
}
vm3 | SUCCESS => {
"changed": false,
"failed": false,
"ping": "pong"
}
vm2 | SUCCESS => {
"changed": false,
"failed": false,
"ping": "pong"
}

We can see from the above output that all systems returned a successful result,
nothing changed, and the result of each "ping" was "pong".

You can obtain a list of available modules using:

[curtis@vm1 ~]$ ansible-doc -l

The number of built-in modules continues to grow with each Ansible release:

[curtis@vm1 ~]$ ansible-doc -l | wc -l

1378

Documentation for each module can be found at

http://docs.ansible.com/ansible/latest/modules_by_category.html

The final setup task in our environment is to configure vm1 with Apache and a Red
Hatcookies
We use Enterprise Linux 7toyum
on our websites repository
deliver in orderDetails
our online services. for the managed
about nodes
how we use cookiesto install
and how you
mayadditional
disable thempackages:
are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 6/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

[root@vm1 ~]# yum install -y httpd

[root@vm1 ~]# systemctl enable httpd
[root@vm1 ~]# systemctl start httpd
[root@vm1 ~]# mkdir /media/iso
[root@vm1 ~]# mount -o loop /root/rhel-server-7.4-x86_64-dvd.iso /media/
[root@vm1 ~]# ln -s /media/iso /var/www/html/rhel7

Ready, set, Ansible!

Now that we have our environment configured and ready to go, let’s do some real
work with Ansible.

Since the managed nodes will need to have some additional packages installed,
our first task is to configure a yum repository on each host using this
configuration file:

[curtis@vm1 ~]$ cat dvd.repo

[RHEL7]
name = RHEL 7
baseurl = http://vm1/rhel7/
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled = 1
gpgcheck = 1

We can copy this file to each of the managed nodes using an ad-hoc command
with the copy module using the -m option and specify the required arguments
using the -a option as follows:

We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 7/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

[curtis@vm1 ~]$ ansible all -m copy -a 'src=dvd.repo dest=/etc/yum.repos

vm5 | SUCCESS => {
"changed": true,
"checksum": "c15fdb5c1183f360ce29a1274c5f69e4e43060f5",
"dest": "/etc/yum.repos.d/dvd.repo",
"failed": false,
"gid": 0,
"group": "root",
"md5sum": "db5a5da08d1c4be953cd0ae6625d8358",
"mode": "0644",
"owner": "root",
"secontext": "system_u:object_r:system_conf_t:s0",
"size": 135,
"src": "/home/curtis/.ansible/tmp/ansible-tmp-1516898124.58-210025572
"state": "file",
"uid": 0
}

[...]

Additional output from the remaining hosts has been removed for sake of brevity.

A few items are worth noting at this point:

1. Each node reports SUCCESS and "changed" : true meaning the module
execution was successful and the file was created/changed. If we run the
command again, the output will include "changed" : false meaning the file is
already present and configured as required. In other words, Ansible will only
make the required changes if they do not already exist. This is what is known as
"idempotence".
2. The -b option (see http://docs.ansible.com/ansible/latest/become.html)
causes the remote task to use privilege escalation (i.e. sudo) which is required
to copy files into the /etc/yum.repos.d directory
3. You can find out what arguments the copy module requires using:

[curtis@vm1
We use ~]$ ansible-doc
cookies on our websites to deliver our copy
online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 8/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

Playbooks
While ad-hoc commands are useful for testing and simple one-off tasks,
playbooks can be used to capture a set of repeatable tasks to run in the future. A
playbook contains one or more plays which define a set of hosts to configure and
a list of tasks to be performed.

In our scenario, we need to configure web servers, database servers, and a

centralized logging server. The specific requirements are:

1. The httpd package is installed on the web servers, enabled, and started

2. Each web server has a default page with text "Welcome to <hostname> on <ip
address>"
3. Each web server has a user account with suitable access for content
management

4. The MariaDB package is installed on the database servers, enabled, and

started
5. The log server host is configured to accept remote logging messages

6. Hosts in the webservers and dbservers groups send a copy of log messages to
the log server host

The following playbook (myplaybook.yml) will configure everything we need.

As you review the playbook, please note the following:

1. The user module requires a hash of the plaintext password (see "ansible-doc
user" for details).  This can be achieved as follows

[curtis@vm1 ~]$ python -c "from passlib.hash import sha512_crypt; i

We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 9/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

2. The default web page content is created using "facts" gathered from the host.
You can discover and use host facts using the setup module:

We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 10/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

[curtis@vm1 ~]$ ansible vm2 -m setup

---
- hosts: webservers
become: yes
tasks:
- name: install Apache server
yum:
name: httpd
state: latest

- name: enable and start Apache server

service:
name: httpd
enabled: yes
state: started

- name: open firewall port

firewalld:
service: http
immediate: true
permanent: true
state: enabled

- name: create web admin group

group:
name: web
state: present

- name: create web admin user

user:
name: webadm
comment: "Web Admin"
password: $6$rounds=656000$bp7zTIl.nar2WQPS$U5CBB15GHnzBqnhY0r7UX
groups: web
append: yes

- name: set content directory group/permissions

file:
We use cookies path: /var/www/html
on our websites to deliver our online services. Details about how we use cookies and how you
owner:
may disable them root
are set out in our Privacy Statement. By using this website you agree to our use of cookies.
group: web
https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 11/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

state: directory
mode: u=rwx,g=rwx,o=rx,g+s

- name: create default page content

copy:
content: "Welcome to {{ ansible_fqdn}} on {{ ansible_default_ipv4
dest: /var/www/html/index.html
owner: webadm
group: web
mode: u=rw,g=rw,o=r

- hosts: dbservers
become: yes
tasks:
- name: install MariaDB server
yum:
name: mariadb-server
state: latest

- name: enable and start MariaDB server

service:
name: mariadb
enabled: yes
state: started

- hosts: logservers
become: yes
tasks:
- name: configure rsyslog remote log reception over udp
lineinfile:
path: /etc/rsyslog.conf
line: "{{ item }}"
state: present
with_items:
- '$ModLoad imudp'
- '$UDPServerRun 514'
notify:
- restart rsyslogd

- name: open firewall port

We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
firewalld:
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.
port: 514/udp

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 12/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

immediate: true
permanent: true
state: enabled

handlers:
- name: restart rsyslogd
service:
name: rsyslog
state: restarted

- hosts: lamp
become: yes
tasks:
- name: configure rsyslog
lineinfile:
path: /etc/rsyslog.conf
line: '*.* @192.168.102.215:514'
state: present
notify:
- restart rsyslogd

handlers:
- name: restart rsyslogd
service:
name: rsyslog
state: restarted

Running the playbook

Our playbook can be run using:

[curtis@vm1 ~]$ ansible-playbook myplaybook.yml

From the output below, we can see that the web server configuration occurs only
on vm2 and vm3 (play 1) while the database is installed on vm4 (play 2) and the
logserver (vm5) is configured with play 3. Finally, play 4 configures the
webservers and dbservers hosts via the "lamp" group for remote logging.

We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 13/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

PLAY [webservers] ******************************************************

TASK [Gathering Facts] *************************************************

ok: [vm2]
ok: [vm3]

TASK [install Apache server] *******************************************

changed: [vm3]
changed: [vm2]

TASK [enable and start Apache server] **********************************

changed: [vm2]
changed: [vm3]

TASK [open firewall port] **********************************************

changed: [vm2]
changed: [vm3]

TASK [create web admin group] ******************************************

changed: [vm3]
changed: [vm2]

TASK [create web admin user] *******************************************

changed: [vm3]
changed: [vm2]

TASK [set content directory group/permissions] *************************

changed: [vm3]
changed: [vm2]

TASK [create default page content] *************************************

changed: [vm3]
changed: [vm2]

PLAY [dbservers] *******************************************************

TASK [Gathering Facts] *************************************************

ok: [vm4]

TASK
We use [install
cookies MariaDB
on our websites server]
to deliver ******************************************
our online services. Details about how we use cookies and how you
changed:
may disable [vm4]
them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 14/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

TASK [enable and start MariaDB server] *********************************

changed: [vm4]

PLAY [logservers] ******************************************************

TASK [Gathering Facts] *************************************************

ok: [vm5]

TASK [configure rsyslog remote log reception over udp] *****************

changed: [vm5] => (item=$ModLoad imudp)
changed: [vm5] => (item=$UDPServerRun 514)

TASK [open firewall port] **********************************************

changed: [vm5]

RUNNING HANDLER [restart rsyslogd] *************************************

changed: [vm5]

PLAY [lamp] ************************************************************

TASK [Gathering Facts] *************************************************

ok: [vm3]
ok: [vm2]
ok: [vm4]

TASK [configure rsyslog] ***********************************************

changed: [vm2]
changed: [vm3]
changed: [vm4]

RUNNING HANDLER [restart rsyslogd] *************************************

changed: [vm3]
changed: [vm2]
changed: [vm4]

PLAY RECAP *************************************************************

vm2 : ok=11 changed=9 unreachable=0 failed=0
vm3 : ok=11 changed=9 unreachable=0 failed=0
vm4 : ok=6 changed=4 unreachable=0 failed=0
vm5 : ok=4 changed=3 unreachable=0 failed=0
We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 15/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

And you’re done!

You can verify the webserver hosts using:

[curtis@vm1 ~]$ curl http://vm2

Welcome to vm2 on 192.168.102.212
[curtis@vm1 ~]$ curl http://vm3
Welcome to vm3 on 192.168.102.213

and remote logging using the logger command on the webservers and dbservers
hosts:

[curtis@vm1 ~]$ ansible lamp -m command -a 'logger hurray it works'

vm3 | SUCCESS | rc=0 >>

vm4 | SUCCESS | rc=0 >>

vm2 | SUCCESS | rc=0 >>

Confirmation on the central logging server:

[curtis@vm1 ~]$ ansible logservers -m command -a "grep 'hurray it works$

vm5 | SUCCESS | rc=0 >>
Jan 30 13:28:29 vm3 curtis: hurray it works
Jan 30 13:28:29 vm2 curtis: hurray it works
Jan 30 13:28:29 vm4 curtis: hurray it works

Tips & tricks

If you’re new to YAML, the syntax can be tricky at first,
particularly with spacing (no tabs).
Before running a playbook, you can check the syntax using:

$ ansible-playbook --syntax-check myplaybook.yml

Using vim with syntax highlighting is helpful not only in learning yaml, but in
We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
mayfinding syntax
disable them problems.
are set A quick
out in our Privacy way to enable
Statement. vimwebsite
By using this for yaml syntax
you agree is by
to our useadding
of cookies.
the following line to your ~/.vimrc file:
https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 16/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

autocmd Filetype yaml setlocal tabstop=2 ai colorcolumn=1,3,5,7,9,80

If you’d like something with a few more features, including color, one such plugin
can be found here.
If you prefer to use emacs instead of vim, enable the EPEL repository and install
the emacs-yaml-mode package.

You can test a playbook without actually making any

changes to the target hosts:
$ ansible-playbook --check myplaybook.yml

Stepping through a playbook may also be useful:

$ ansible-playbook --step myplaybook.yml

Similar to a shell script, you can make your Ansible playbook

executable and add the following to the top of the file:
#!/bin/ansible-playbook

To execute arbitrary ad-hoc shell commands, use the

command module (the default module if -m is not
specified). If you need to use things like redirection,
pipelines, etc., then use the shell module instead.
Speed up writing playbooks by checking the "EXAMPLES:"
section in the documentation for a particular module.
Use string quoting in playbooks to avoid issues with special
characters within a string.
Logging is disabled by default. To enable logging, use the
log_path
We use parameter
cookies on our inour
websites to deliver the Ansible
online configuration
services. Details file. and how you
about how we use cookies
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 17/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

I hope this post has given you a better idea of how Ansible works and how it can
save you both time and effort using playbooks to document and repeat mundane
tasks with ease and accuracy. Be sure to continue learning at
http://docs.ansible.com and
https://www.redhat.com/en/technologies/management/ansible.

Happy automating!

Curtis Rempel, RHCA, is a senior Platform TAM and

team lead in Canada and a former Red Hat Certified
Instructor and Examiner (RHCI/RHCX). His Linux
journey started in 1994 with a Red Hat Linux 2.1 CD
from Jon "maddog" Hall. As a TAM, he has supported
enterprise customers in the finance,
telecommunications, and airline industries with
expertise in automation, kernel, and storage. Learn more about Curtis.

A Red Hat Technical Account Manager (TAM) is a specialized product expert who
works collaboratively with IT organizations to strategically plan for successful
deployments and help realize optimal performance and growth. The TAM is part
of Red Hat’s world class Customer Experience and Engagement organization and
provides proactive advice and guidance to help you identify and address potential
problems before they occur. Should a problem arise, your TAM will own the issue
and engage the best resources to resolve it as quickly as possible with minimal
disruption to your business.

Connect with TAMs at a Red Hat Convergence event near you! Red Hat
Convergence is a free, invitation-only event offering technical users an
opportunity to deepen their Red Hat product knowledge and discover new ways
to apply open source technology to meet their business goals. These events
travel to cities around the world to provide you with a convenient, local one-day
experience to learn and connect with Red Hat experts and industry peers.

Open source is collaborative curiosity. Join us at Red Hat Summit, May 8-10, in
We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
San Francisco to connect with TAMs and other Red Hat experts in person!
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.
Register now for only US$1,100 using code CEE18.
https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 18/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

Red Hat Cloud Success is designed to help simplify your IT transformation and
accelerate your adoption of cloud technologies with deep product expertise,
guidance, and support. From the proof of concept stage to production, a highly
skilled cloud technical specialist will partner with you to provide continuity and
help ensure successful implementation of your cloud solution. Through this
limited time engagement, Red Hat Cloud Success can help you effectively plan
and deploy cloud solutions and strategically plan for the future.

We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 19/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

SUBSCRIBE VIA RSS

PREVIOUS OLDER POST

 Friday Five — March 9, 2018

NEXT NEWER POST

Flying with a Safety Net: High Availability for SAP HANA in Public Clouds

OF INTEREST

News to note—just for you

UPCOMING EVENT

Ansible Automation Technical Workshops

August 21, 2019

RELATED WEBINAR
We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.
Red Hat Enterprise Linux for SAP Solutions
https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 20/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

August 21, 2019

CUSTOMER STORY

Ascend Money builds centralized app platform

ABOUT

We’re the world’s leading provider of enterprise open source solutions, using a community-powered approach to
deliver high-performing Linux, cloud, container, and Kubernetes technologies. We help you standardize across
environments, develop cloud-native applications, and integrate, automate, secure, and manage complex
environments with award-winning support, training, and consulting services.

Company information Investor relations

Locations Blog

Newsroom Development model

Events Jobs

   

 FEATURED

Red Hat Enterprise Linux

Red Hat Gluster Storage

Red Hat Satellite

Red Hat OpenShift Container Platform

Red Hat OpenStack Platform

 TOOLS

My account
We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
For customers
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.
For partners
https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 21/22
8/21/2019 A system administrator's guide to getting started with Ansible - FAST!

For developers

Hardware catalog

Resource library

 PURCHASE

Red Hat Store

Buy online (Japan)

Red Hat merchandise

Contact sales

Contact training

Contact consulting

Find a partner

 COMMUNICATE

Contact us

Feedback

Social

Red Hat newsletter

Copyright ©2019 Red Hat, Inc.

Privacy statement Terms of use All policies and guidelines Cookie Preferences

We use cookies on our websites to deliver our online services. Details about how we use cookies and how you
may disable them are set out in our Privacy Statement. By using this website you agree to our use of cookies.

https://www.redhat.com/en/blog/system-administrators-guide-getting-started-ansible-fast 22/22