Automation Configuration Management

“We build clouds”
Configuration Management has been with us since the 1950’s
“If it isn’t broken, don’t fit it!”
Best Practices & How to get started
Start small and build up gradually
Start of with small tasks:
Configure DNS settings
Version control is not longer just for developers
The tool is unimportant, just have a tool. Github, etc
is a key component for
Quality Control
A starting point for Continuous Integration Work follows
If you don’y know, LEARN IT!
* Configuration management requires a change in culture – Make sure the
Table of Tools
Things to consider when choosing tool set
  • Command line or GUI?
  • Agentless?
  • Platform support?
  • Runbook language skills required?
  • Open source or not
Speaker’s favourite (today)
Starting gun…
Moved from Puppet to Ansible as didn’t like ruby runbacks or problems with certs.
RedHat purchased Ansible and have created a paid for version Ansible Tower 3
Build Ansible control machine
Configure version control – Github repo
Example given of playbook
Demo – Project Trillian
Lesson learnt – you can quickly become a victim of your own success. Ensure you have capacity and consider what happens when the tool becomes ‘unavailable.’
Speaker uses two consoles. 1 for managing system he is configuring and the other for runback. As he enters commands to set the desired configuration he also creates the runback command. He then tests the runbook in labs later.

Leave a Reply

  • (will not be published)

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>