I know, I know, what the hell am I doing talking about windows, right? Well, unfortunately, even I get stuck having to run it in some instances, like when a vendor we work with uses a vpn that is only supported in win32. On the bright side, it is just a vm.
Ok, you're back. I'm confident one of the first questions you are going to be asking is, "Why are you writing another article to define 'devops', you already did that." Well, to clarify, I did not define devops, I described it. Now, I am going to actually give you what everyone in the industry has been in search of. An actual, real life definition for the craze 'devops'.
What is DevOps? We hear the term almost daily. It has taken the industry hostage, and yet, there is a great deal of confusion as to what it really means.
Before we dive in to what DevOps is, let's clarify what it isn't. DevOps is not magic. It is not hocus pocus, mystical powers granted to select engineers that fixes all of your problems with little to no effort. DevOps is not perfect, nor is DevOps easy.
Welcome readers!
As you are sure to notice (and pretty quickly, too), the site has undergone extensive changes.
It has been far too long since I made my last post entry. Now, I finally have a few reasons to start blogging again. The first being, I redesigned my home lab/network. It’s nothing extraordinary, but it will work well for what I need.
Well, that was a rather entertaining hour plus wasted. Doesn’t everyone love it when your vendor changes things that you have done for YEARS, and are quite accustomed to, all for “organization” or “improvement” ?
First things first, this post is not intended to be an attack. It is going to go over what my own feelings were with #AnsibleFest, which I attended yesterday for my birthday gift from my wife. If you were there, you may agree, you may disagree. All in all, it is an opinion that I myself have of the situation.