Configuration as Code for Ansible Automation Platform 2 Technical Workshop
IMPORTANT TO NOTE
This is the 4 hour workshop.
Welcome to our interactive lab on using Configuration as code to configure the Ansible Automation Platrom.
Configuration as Code (CasC) is a software development practice that treats infrastructure configurations as code. This approach allows you to version control, track changes, and automate the deployment of your infrastructure configurations. With CasC, your configuration files or scripts serve as the single source of truth for your infrastructure setup. Any changes should be made through this mechanism, avoiding direct changes in the Ansible Automation Platform (AAP) UI. Benefits of CasC By adopting a Configuration as Code approach, you can enjoy numerous benefits, including:
- Version Control : Track changes and collaborate with team members.
- Consistency : Ensure consistent configurations across different environments.
- Repeatability : Repeat the same configuration setup multiple times.
- Automated Deployment : Automate deployment to different environments.
- Auditing and Compliance : Track who made changes, when, and what was changed.
== Lab structure
In this lab, we will demonstrate how to use Configuration as Code to configure various aspects of the Ansible Automation Platform (AAP). This includes:
-
First, We will setup the basics for configuring the Automation Platform.
-
Next we will Create some credentials, inventories, and job templates and everything that is needed to create them.
-
Next we will configure the Hub to load in more content.
-
We will then build an execution environment to be used on the platform.
-
Finally for extra credit, a workflow can be created from scratch.
By following this lab, you will learn how to use CasC to maintain a consistent and repeatable infrastructure configuration across different environments. This approach will help prevent drift in configuration, require approval before implementation, and ensure that both development and production deployments are well-maintained.
Automation controller before, a recomended place to start is this instruct lab, if you have not done so before: Introduction to automation controller
Agenda
Recommended agenda for when there is an instructor teaching.
| Part 1: Creating the Basics for configuring the Automation Platform | ⏱️ 40 minutes |
| Part 2: Creating credentials, inventories, and job templates and everything that is needed to create them. | ⏱️ 40 minutes |
| Part 3: Configuring the Automation hub to load more content | ⏱️ 30 minutes |
| Part 4: Build an execution environment to be used on the platform. | ⏱️ 40 minutes |
| Part 4: Creating an Automation controller Workflow in code | ⏱️ 90 minutes |
Total Time: 4 hours (249 minutes)
Lab Index
| Lab Title | Description | Link |
|---|---|---|
| Config as code Introduction to AAP | Learn about the fundamentals of using Configuration of Code to maintain the Ansible Automation Platform. This is a Red Hat or Partner Only Lab, and requires access to demo.redhat.com, please reach out to your account representative to coordinate access to the Lab | 🚀 Launch Lab |
Going Further
Additional material for Configuration as Code for Ansible Automation Platform 2
| Title | Type | Link |
|---|---|---|
| Demystifying Ansible Automation Platform | Book | 📖 Demystifying Ansible Automation Platform - Book from Packt |
| Infra Collections in Ansible Galaxy | Collections | 📒 Download collections used in this lab and get links to their repos |
Ansible Workshop
This is an official Ansible Workshop
This workshop is maintained by the Infra Config as Code Volunteers Please open an issues on Github
