The Mission-Critical Automation Workshop is a dynamic 3.5-hour hands-on experience designed to introduce participants to Ansible Automation Platform and to immerse participants in the journey of a new automator joining a team, progressing from using automation for information gathering to maturing their automation journey and building responsive automation that prevents and mitigates outages, minimizes downtime, and ensures mission-critical workloads remain operational.
| Resource | Link |
|---|---|
| Workshop content and exercises | Reference document |
| Follow-up assets | Red Hat Ansible Automation Platform - Training + Certification slides |
| Certain registration page & promotional email copy | Registration page & promotional email copy |
| Presenter instructions and guide | Train-the-trainer video |
| Certain event banners | Creative from Ansible flex kit (Google Drive) |
This workshop is tailored for individuals with limited or no experience in writing Ansible Playbooks or using Ansible Automation Platform. It’s perfect for IT infrastructure engineers, DevOps engineers, and operations teams eager to experience the automation journey.
IT infrastructure engineers, DevOps engineers, and operations teams eager to experience the automation journey.
None.
Request labs via the lab environment request form. After you submit your request you will immediately get an email and the link at the bottom is what you will provide to your users/students. Select the three labs under the Getting Started section of the internal Google Form.
Topics covered:
| Activity | Estimated Time |
|---|---|
| Slides: Welcome / Introduction / Learning objectives | ⏱️ 5 minutes |
| Lab: Infrastructure Awareness and Reporting | ⏱️ 45 minutes |
| Lab: Configuration and Application Deployment | ⏱️ 90 minutes |
| Lab: Mission Critical Automation with Event-Driven Ansible | ⏱️ 45 minutes |
| Slides: Q&A and closing | ⏱️ 10 minutes |
This is an official Ansible Workshop
This workshop is maintained by the Red Hat Ansible Technical Marketing Team.
Please open an issues on Github
