With this post I’m kicking off a new series of blog post covering cross platform and DevOps topics for IT Pros.
Back in the days Microsoft was focused on it’s own operating system flagship, called Windows. Remember..anyone? 🙂
Nowadays the boundaries between Microsoft and the OpenSource world are disappearing more and more. To prove this a little bit I’ve collected some facts:
- In 2014, Microsoft open sourced .Net
- In 2016, Satja Nadella stated, that Microsoft loves Linux
- In 2017, Microsoft announced Linux Containers on Windows
- 60% of all Azure Marketplace offerings are Linux-based
- Last months: 50% of all new VMs are running Linux
- Microsoft offers Linux certifications and MVP awards for Linux
DevOps is not a tool, it’s nor a software or a specific technology. DevOps is a process driven software engineering practice framework. It’s primary goal is to tighten the relationship between developers, engineers and operators by implementing agile and continous development/deployment processes. DevOps aims at shorter development cycles and increased deployment frequency. Not only software can be developed using this methodology, also infrastructure can be configured and deployed using code only.
Why mentioning IT Pros?
(Disclaimer: The following statements, are reflecting my personal opinion, and may not apply to everyone reading this post 🙂
- IT Pros are a generally focused on getting things to just work, mainly on infrastructure level
- IT Pros don’t care about code
- IT Pros are used to do things once, often with GUI based admin- and config tools
- If they have to repeat their work, tons of print-screen based documentation is consulted (if present though :-))
- IT Pros have some batch-script or vb-script know how from the past, now trying to arrange themselves with PowerShell just because everyone tells them to do so
- IT Pros believe, automation just being a hype and a cost driver, being too complex and not applicable to infrastructure
The truth is, that automation is a key success factor for user self service, large environments, distributed environments, applications based on micro services and containers, etc. Don’t get me wrong here. Not every IT Pro will become a professional automation engineer, nor will a developer typically become a infrastructure architect or network engineer. The thing is, that all of us have to open their minds for change, and things will change, faster than we might like it.
With that said, I’m trying to create a series of blog posts, which targets IT Pros willing to change, to learn and to be open minded for future trends and technologies.
The topics for the first series of posts will be:
#1 Using Posh-SSH to automate Linux with PowerShell
#2 PowerShell Desired State Configuration (from zero to hero in 60 minutes)
#3 Manage Linux with PowerShell DSC and PowerShell Core
#4 Leveraging Azure Automation / OMS to follow “infrastructure as code principle”
#5 Version Control / Continuous Release Pipeline (CI/CD)
Stay tuned 🙂