Configuration as Code Lab Overview
Transcript
Sean Selphin and Dave Danson discussed the benefits of using Infrastructure as Code (IaC) for AV configuration, emphasizing that code should be the source of truth to avoid manual UI changes. They highlighted the advantages of tracking changes, reducing reliance on backups, and faster PRs. However, they noted the learning curve and increased effort compared to simple UI changes. The conversation also covered the use of CI/CD pipelines, standard data models, and certified collections for AAP configuration. The lab includes four sections: configuration basics, controller-based configuration, execution environments, and control workflows, with resources available for further learning and support.
Action Items
[ ] Make the lab available online in the next few days.
[ ] Provide access to the lab materials to attendees after the session.
[ ] Encourage attendees to provide feedback on the lab and documentation through the Ansible community forum or GitHub.
Outline
Introduction and Overview of Configuration as Code for AV
Sean Selphin introduces himself as a Principal Consultant through Red House Consultant, co-maintaining the AV configuration collection.
Dave Danson introduces himself as a Guest Automation Architect in North American services.
The meeting aims to cover the basics of configuration as code, its benefits, and the recovery process.
The focus is on managing infrastructure as code, reducing reliance on UI changes, and the pros and cons of the approach.
Benefits and Challenges of Configuration as Code
Dave Danson emphasizes that code should be the source of truth, eliminating manual changes in the UI.
The process reduces reliance on backups and allows for better tracking and requiring changes.
Faster PR and access to clusters in the same data center are benefits.
The learning curve and increased effort compared to simple UI changes are noted as cons.
CI/CD Integration and Standard Data Model
Dave Danson discusses the use of CI/CD to ensure configurations work correctly.
A standard data model for input is introduced, focusing on including only necessary changes.
The process involves setting up inventory, playbooks, and modules to deploy configurations.
Separate playbooks for different environments are mentioned, with modules provided by certified collections.
Certified Collections and Lab Setup
Speaker 3 introduces certified collections, fully supported by the government, for configuration and controller automation.
The AAP configuration collection is highlighted, focusing on deploying configurations within AMP.
AMP utilities are discussed, helping to define execution requirements as code and push them into an automation platform.
The lab setup is described, with four sections covering configuration as code basics, controller-based configuration, execution environments, and control workflows.
Lab Details and Participant Interaction
Speaker 3 outlines the lab's structure, emphasizing that it is designed for learning rather than completion.
Participants are encouraged to raise hands for help if needed.
Speaker 4 inquires about the availability of the lab code online, to which Speaker 3 responds that the lab is not currently available but will be soon.
Instructions and documentation links are provided for further learning and support.