Book Image

Mastering Ansible, 4th Edition - Fourth Edition

By : James Freeman, Jesse Keating
Book Image

Mastering Ansible, 4th Edition - Fourth Edition

By: James Freeman, Jesse Keating

Overview of this book

Ansible is a modern, YAML-based automation tool (built on top of Python, one of the world’s most popular programming languages) with a massive and ever-growing user base. Its popularity and Python underpinnings make it essential learning for all in the DevOps space. This fourth edition of Mastering Ansible provides complete coverage of Ansible automation, from the design and architecture of the tool and basic automation with playbooks to writing and debugging your own Python-based extensions. You'll learn how to build automation workflows with Ansible’s extensive built-in library of collections, modules, and plugins. You'll then look at extending the modules and plugins with Python-based code and even build your own collections — ultimately learning how to give back to the Ansible community. By the end of this Ansible book, you'll be confident in all aspects of Ansible automation, from the fundamentals of playbook design to getting under the hood and extending and adapting Ansible to solve new automation challenges.
Table of Contents (18 chapters)
1
Section 1: Ansible Overview and Fundamentals
7
Section 2: Writing and Troubleshooting Ansible Playbooks
13
Section 3: Orchestration with Ansible

Questions

  1. What level of verbosity would you need to launch Ansible with to see details such as connection attempts?

    a) Level 3 or above

    b) Level 2 or above

    c) Level 1 or above

    d) Level 4

  2. Why should you be careful with verbosity levels above level one if you are using sensitive data in your playbook?

    a) Higher verbosity levels don't support the use of vaults.

    b) Higher verbosity levels may log sensitive data to the console and/or log file.

    c) Higher verbosity levels will print SSH passwords.

  3. Ansible can be centrally configured to log its output to a file by:

    a) Using the ANSIBLE_LOG_PATH environment variable

    b) Using the log_path directive in ansible.cfg

    c) Redirecting the output of each playbook run to a file

    d) All of these

  4. The name of the module used for variable introspection is:

    a) ansible.builtin.analyze

    b) ansible.builtin.introspect

    c) ansible.builtin.debug

    d) ansible.builtin.print

  5. When referencing subelements in Ansible variables, which syntax is the safest to...