Preface
[ viii ]
Chapter 7, Troubleshooting Ansible, explores the various methods that can be employed
to examine, introspect, modify, and debug the operations of Ansible.
Chapter 8, Extending Ansible, discovers the various ways in which new capabilities
can be added to Ansible via modules, plugins, and inventory sources.
What you need for this book
To follow the examples provided in this book, you will need access to a computer
platform capable of running Ansible. Currently, Ansible can be run from any
machine with Python 2.6 or 2.7 installed (Windows isn't supported for the control
machine). This includes Red Hat, Debian, CentOS, OS X, any of the BSDs, and so on.
This book uses the Ansible 1.9.x series release.
Ansible installation instructions can be found at
http://docs.ansible.com/
ansible/intro_installation.html
.
Who this book is for
This book is intended for Ansible developers and operators who have an understanding
of the core elements and applications but are now looking to enhance their skills in
applying automation using Ansible.
Conventions
In this book, you will nd a number of text styles that distinguish between different
kinds of information. Here are some examples of these styles and an explanation of
their meaning.
Code words in text, database table names, folder names, lenames, le extensions,
pathnames, dummy URLs, user input, and Twitter handles are shown as follows:
"When
ansible or ansible-playbook is directed at an executable le for an
inventory source, Ansible will execute that script with a single argument, --list."
A block of code is set as follows:
- name: add new node into runtime inventory
add_host:
name: newmastery.example.name
groups: web
ansible_ssh_host: 192.168.10.30
我的内容管理
展开
