5 Frequently Asked Questions About DevOps (Including Answers)
In this FAQ I will attempt to answer 5 frequently asked questions about DevOps.
Let’s jump right in...
#One. Are You Right For DevOps?
DevOps can only succeed when people with the right mindset and skills pull together.
You need both. Mindset. Skills.
First, let's talk about the DevOps mindset for a minute.
- Are you the type of technical person who works best alone?
- Do you have a hard time communicating with other people?
- Do you just want to be left alone in a dark corner?
If I just described you then transforming your mindset isn't going to be easy.
The DevOps mindset is crucial and should be the first goal you focus your learning on.
I know what you're thinking, really? Yes, really!
Everyone wants to focus on DevOps tools and automation all the time, and we'll get there soon enough.
- DevOps happens when people communicate.
- Or go to lunch together and just talk.
- Or when someone says, let's get a meeting room and review logs to see if we can figure out a problem.
All to often we're looking for shiny stuff, but often DevOps shows up in small acts of kindness and human interaction.
Are you understanding me? Because You 'become' DevOps!
#Two. Where To Use DevOps?
Now with that out of the way, let's look at where to use DevOps.
There are 3 use cases I'll focus on but there are more:
1. Automation of day to day operational tasks such as clearing logs, patching servers, rebooting or restarting services.
Anything that fits into this list of daily operational tasks that can be automated with tools such as: Ansible, Chef, Puppet, Powershell, bash or other scripting are included in this use case.
2. Automating deployment of resources such as virtual servers, networks, storage, DNS, VIPs, IPs, hardware configurations, or anything similar is included in this use case.
And this includes everything on premise or in the cloud.
Anything a SysAdmin does manually is open game for DevOps automation.
3. Automation code deployments and releases, web service updates, micro-services, scripts or other manual tasks that operations staff do for developers, both on premise or in the cloud. Think big here because this DevOps use case can be almost anything.
All 3 of these DevOps use cases can be accomplished by people with the right set of skills, people who have spent the time learning tools that are widely available and free to download, such as: Git, Jenkins, Ansible, Chef, Puppet, Docker and Powershell.
There are plenty more configuration management tools available that work with AWS, Google and Microsoft cloud platforms but mastering these 4 tools whether you're a Linux or Windows Admin will open new opportunities for you where you are now.
My goal is not to teach you DevOps, it's to give you a new perspective of DevOps.
So STOP buying into all the hype that's spread on the Internet by ignorant people trying to get you to buy their products.
#Three. What Are DevOps Tools To Learn?
Master a few tools and you'll be much better off than the average SysAdmin...
I can guaranty you that resumes with extensive Ansible, Jenkins, Git and/or Powershell experience get more attention than resumes with college degrees.
So if your goal is to become a DevOps engineer then focus time and energy on your mindset and a few key tools because this will set you apart...
Changing how you think and work with other people is a personal journey and I spend a lot of time writing about it so start there...
As for DevOps tools to learn, this is where I've decided to let you in on my secret. I use Udemy for my online training.
Because DevOps video training courses on Udemy are Awesome!
Every DevOps tool you can imagine using has a training video course - Docker, AWS, Cloud, etc.
But not so fast because I want to narrow the training down to only Ansible, Jenkins, Git and Powershell video courses.
This will all makes sense in the real world, as opposed to Internet hyped-up stories on LinkedIn or Buzzfeed.
Before you know it you'll imagine writing code for everything, and yes, some people won't want you changing manual processes because they're afraid.
But you need to focus on the big picture because staying relevant is more important than worrying about job security via old manual processes.
#Four. Who is doing DevOps?
Take your time and be consistent because for every 100 people who reads this page, maybe 2 will take it serious and take action to start learning.
That's why DevOps engineers are so rare and hard to find.
Because only 2 out of 100 people who know what's required to learn DevOps tools will actually do it.
This may be for various reasons, such as: time, money, availability or even talent.
Frankly, it doesn't matter why. Because you'll be in that 2%.
You are doing DevOps!
And if you're wondering where I got this data from, it comes in the form of resumes I review all the time.
For every 100 resumes I read, maybe 2 people have any real DevOps tool experience, and yet, if you do a job search on Dice 98% of IT jobs list some sort of automation or coding requirement in the job description.
Will it be you who stands-out in the stack of resumes because you know how to full deploy Ansible, Git, Jenkins?
Or because you can write amazing Powershell scripts that make managing Windows or Microsoft products look like playing video games?
Stay with me and you will be the one who stand out with DevOps skills that make you different...
#Five. What is DevOps?
- DevOps is people, morale, and culture.
- It's developers and operations staff working closely together.
- It's management empowering and getting out of the way.
- It's automation of code and infrastructure.
- It's continuous deployments using configuration tools.
- It's the fulfillment of business needs using agile processes.
These frequently asked questions about DevOps come from years of first hand experience. In summary we answered 5 questions:
- Are you right for DevOps?
- Where to use DevOps?
- What are DevOps tools to learn?
- Who is doing DevOps
- And finally, what is DevOps?