- 1. Introduction
- A Note About Versions
- Ansible: What Is It Good For?
- How Ansible Works
- What’s So Great About Ansible?
- Simple
- Powerful
- Secure
- Is Ansible Too Simple?
- What Do I Need to Know?
- What Isn’t Covered
- Installing Ansible
- Setting Up a Server for Testing
- Using Vagrant to Set Up a Test Server
- Telling Ansible About Your Test Server
- Simplifying with the ansible.cfg File
- Kill your darlings
- Moving Forward
- 2. Playbooks: A Beginning
- 3. Inventory: Describing Your Servers
- Inventory/Hosts Files
- Preliminaries: Multiple Vagrant Machines
- Behavioral Inventory Parameters
- ansible_connection
- ansible_shell_type
- ansible_python_interpreter
- ansible_*_interpreter
- Changing Behavioral Parameter Defaults
- Groups and Groups and Groups
- Example: Deploying a Django App
- Aliases and Ports
- Groups of Groups
- Numbered Hosts (Pets versus Cattle)
- Hosts and Group Variables: Inside the Inventory
- Host and Group Variables: In Their Own Files
- Dynamic Inventory
- Inventory Plugins
- Amazon EC2
- Azure Resource Manager
- The Interface for a Dynamic Inventory Script
- Writing a Dynamic Inventory Script
- Breaking the Inventory into Multiple Files
- Adding Entries at Runtime with add_host and group_by
- add_host
- group_by
- 4. Variables and Facts
- Defining Variables in Playbooks
- Viewing the Values of Variables
- Registering Variables
- Facts
- Viewing All Facts Associated with a Server
- Viewing a Subset of Facts
- Any Module Can Return Facts
- Local Facts
- Using set_fact to Define a New Variable
- Built-in Variables
- hostvars
- inventory_hostname
- Groups
- Setting Variables on the Command Line
- Precedence
- 5. Introducing Mezzanine: Our Test Application
- 6. Deploying Mezzanine with Ansible
- Listing Tasks in a Playbook
- Organization of Deployed Files
- Variables and Secret Variables
- Installing Multiple Packages
- Adding the Become Clause to a Task
- Updating the Apt Cache
- Checking Out the Project Using Git
- Installing Mezzanine and Other Packages into a Virtual Environment
- Complex Arguments in Tasks: A Brief Digression
- Configuring the Database
- Generating the local_settings.py File from a Template
- Running django-manage Commands
- Running Custom Python Scripts in the Context of the Application
- Setting Service Configuration Files
- Enabling the Nginx Configuration
- Installing TLS Certificates
- Installing Twitter Cron Job
- The Full Playbook
- Running the Playbook Against a Vagrant Machine
- Troubleshooting
- Cannot Check Out Git Repository
- Cannot Reach 192.168.33.10.nip.io
- Bad Request (400)
- Deploying Mezzanine on Multiple Machines
About the Authors
Bas Meijer (he/him) is a freelance software engineer and devops coach. With a major from the University of Amsterdam he has been pioneering web development since the early nineties. He worked in high-frequency trading, banking, cloud security, aviation, and government. Bas has been an Ansible Ambassador since 2014, and was selected too as a Hashicorp Ambassador in 2020.
Lorin Hochstein is a senior software engineer on the Chaos Team at Netflix, where he works on ensuring that Netflix remains available. He is a coauthor of the OpenStack Operations Guide (O’Reilly), as well as numerous academic publications.
René Moser lives in Switzerland with his wife and three kids, likes simple things that work and scale, and earned an Advanced Diploma of Higher Education in IT. He has been engaged in the Open Source community for the past 15 years, most recently working as an ASF CloudStack Committer and as the author of the Ansible CloudStack integration with over 30 CloudStack modules. He became an Ansible Community Core Member in April 2016 and is currently a senior system engineer at SwissTXT.
-
No Comment