Written By Corey Quinn. We are excited to share our Guest Blog from Corey Quinn. Corey is a former Taoser and huge community advocate of Taos. During my consulting tenure with Taos, I had the privilege of architecting numerous cloud migrations. Now that I curate https://www.lastweekinaws.com, I’ve gained particular insight into many more. I want […]
This past week, I had the honor of being invited to speak at SaltConf 2015. I additionally was asked to serve on a panel that discussed using multiple configuration management systems in the same environment.
The panel got me thinking about what DevOps in 2015 means (from a technical sense; the cultural shifts and methodologies will have to wait for another blog post someday!). I believe I’ve narrowed it down to four primitives, which I term the Four Horsemen of DevOps. Since I was at SaltConf, I was naturally thinking in terms of Saltstack. It struck me that each one of these four primitives is served rather well by various Saltstack components.
Like most consultants who’ve been in the game for more than a year or two, I periodically receive opportunities to “convert” to being a full time employee, either with our clients or from third parties who’ve heard of me through the grapevine. It’s always flattering, I always appreciate the gesture, and I always politely decline the offer.
Why? On the face of it, this doesn’t make a whole lot of sense. As a consultant, I generally don’t get the chance to gain equity in my clients. Compensation generally takes the form of cash rather than an ownership stake, and as for the rest of the typical fringe benefit suite? Forget it! As a consultant, I frequently find myself sitting next to the printer breathing toner. (“Sorry about that, it was the last available seat we had…”)
[caption id="attachment_559" align="alignright" width="203"] Corey Quinn | Senior Technical Consultant at Taos[/caption]
Earlier last week, the fine folks from SaltStack conducted an on-site training for us at Taos. For those who are unaware, Salt is a remote execution / configuration management system written in Python, and a project to which I’ve been a contributor for several years.
As often happens during such trainings, someone asked a question about how to achieve a certain goal. The answer was “that’s a good idea; we can’t do it yet, but patches are welcome!”
Corey Quinn | Senior Technical Consultant at Taos[/caption][caption id="attachment_480" align="alignright" width="160"]
A part of what I do at Taos involves interviewing prospective consultants for our Unix/DevOps practice via a thorough technical assessment. Our technical interview spans virtually the entire breadth of topics that encompass the practice of systems administration.
One focus area that I like to spend a bit of time on is DNS. This essential service acts as the underpinning behind almost everything else a system does; when DNS goes away, your system is likely to be very, very unhappy. Despite this, few people tend to have a grasp upon how DNS works underneath the hood. I went searching for a decent write-up that explains the name resolution process, and struggled to find anything succinct that hit the points I felt were important.