Last week’s Office Hours Hangout featured Racker Justin Phelps, who’s been working in our DevOps Engineering teams for three and a half years. He was one of the first 40 people certified as a SaltStack Engineer, and just last week earned his Certified Ansible Engineer award.
We asked Justin about Ansible, how it can help our customers, and where they can get started with Ansible. We also spent some time talking about creating and hosting static websites, and how to incorporate those into a larger application design.
I had a hard time choosing highlights this week; I pretty much recommend the entire episode. I have a few links to highlights in the sections below, and the entire video is embedded at the end of the blog post. I hope you enjoy watching as much as I enjoyed hosting.
Ansible’s simplicity and consistency
One of Justin’s favorite aspects of Ansible is the simplicity. In this clip, Justin describes how easy it is to get started with Ansible. A bit later, Justin and I chatted about how he uses Ansible in his own projects to achieve a consistent environment. Finally, we talked about using images vs configuration management to build new servers. Justin recommends using configuration management in your development environment, then creating a stable image from that dev environment once you push to production.
Ansible vs other configuration management solutions
Just like pitting two colas, or text editors against each other, configuration management solutions are often matters of personal preference and project use case. Justin gives a good description of the pros and cons of Ansible and other configuration management systems.
Getting started with Ansible
Justin had a few tips for getting started with Ansible. His first suggestion is to just start playing with Ansible. They have a great getting started section in their documentation, including a very easy to follow video. He also recommends starting off with automating the installation of packages and services. Especially for common web tools like Apache and PHP, the modules for these tools are very useful. Another good use of Ansible with a high return on time investment is pushing security updates to multiple nodes in your environment, especially when using a dynamic inventory.
Finally, we discussed how developers can include static sites as a failover provision within more dynamic web applications – the “circuit breaker pattern.”
This episode is just packed full of great information, I recommend watching the whole video below.
Join us every Thursday at 1pm for our weekly hangout.