by Brandon Knitter | Technical Consultant at Taos The software industry has seen a lot of change over the past many years. There was the mainframe. At some point we moved to client-server. The web gave birth to the three-tier architecture. Eventually there was SOA, and CORBA reared it’s head like a dyslexic snake. There […]
My son plays baseball. He’s a catcher. As a catcher, he is charged with seeing the entire field of play, and calling actions out to his teammates based on his predictions of what is going down. He’s told me before, “Dad I have a choice, I either catch the game they throw me, or I make them throw the game I want to catch.” If he waits to figure out what he’s going to do if the guy on first tries to steal on the pitch once the guy has started to run. He’ll never stop them from trying to steal. But if he learns the patterns a runner executes when they intend to steal, calls a pitchout, has the shortstop move over to 2nd at the right time. He’ll look like the hero and get the runner out.
Attacking overtrodden topics almost always a bad idea. The questions of “what is DevOps” and “what isn’t DevOps” have been used, reused, and rehashed to such an extent that there remains little ground to cover in those arenas. But even though that ground has been walked into a muddy rut, while so many people seem to “get” DevOps to the point that discussing it further seems a pointless waste, many organizational leaders still seem unsatisfied with the answers. If you’re among the unconvinced, unhappy with all the direct and explicit answers that abound, let me tempt you with an esoteric and obscure assertion instead.
By Jeff Lucchesi DevOps started out as a necessity for development and IT Operations to collaborate on rapid deployment and better efficiency in operating and supporting the product. With products in the high tech world changing rapidly, keeping up with the engineering organizations has proven to be a challenge for CIOs. In the last few months, […]
by Jess Males | Technical Consultant at Taos I had the opportunity, recently, to attend AutomaCon, an exciting new conference dedicated to all things automation. It was three days of sharing and discussion around systems automation. Attending, one question that floated in the back of my mind was: what is DevOps? I don’t subscribe to […]
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.
There are a lot of different ways that people define the role “Devops”. Devops is a role that proves to be confusing for most and obvious to few. As I continue to make connections with people and broaden my network it is clear that not everyone is aware that they are a Devops candidate. Some see it as […]