Let’s face it! We live in a world now where we are seeing a heavy reliance on software instead of hardware. With Software Defined Everything popping up all over the place we are seeing traditional hardware oriented tasks being built into software – this provides an extreme amount of flexibility and portability on how we chose to deploy and configure various pieces of our environments.
With this software management layer taking hold of our virtualized datacenters we are going through a phase where technologies such as private and hybrid cloud are now within our grasp. As the cloud descends upon us there is one key player that we need to focus on – the automation and orchestration that quietly executes in the background, the key component to providing the flexibility, efficiency, and simplicity that we as sysadmins are expected to provide to our end users.
To help drive home the importance and reliance of automation let’s take a look at a simple task – that of deploying a VM. When we do this in the cloud, mainly public, it’s just a matter of swiping a credit card, providing some information in regards to a name and network configuration, waiting a few minutes/seconds and away we go. Our end users can have a VM setup almost instantaneously!
The ease of use and efficiency of the public cloud, such as the above scenario is putting extended pressure on IT within their respective organizations – we are now expected to create, deliver and maintain these flexible like services within our businesses, and do so with the same efficiency and simplicity that cloud brings to the table. Virtualization certainly provides a decent starting point for this, but it is automation and orchestration that will take us to the finish line.
So how do we do it?
Within our enterprise I think we can all agree that we don’t simply just create a VM and call it “done”! There are many other steps that come after we power up that new VM. We have server naming to contend with, networking configuration (IP, DNS, Firewall, etc). We have monitoring solutions that need to be configured in order to properly monitor and respond to outages and issues that may pop up, as well as I’m pretty certain we will want to include our newly created VM within some sort of backup or replication job in order to protect it. With more and more software vendors exposing public API’s we are now living in a world where its possible to tie all of these different pieces of our datacenter together.
Automation and orchestration doesn’t stop at just creating VMs either – there’s room for it throughout the whole VM life cycle. The concept of the self-healing datacenter comes to mind – having scripts and actions performed automatically by monitoring software in efforts to fix issues within your environment as the occur – this is all made possible by automation.
So with this I think we can all conclude that automation is a key player within our environments but the questions always remains – should I automate task x? Meaning, will the time savings and benefits of creating the automation supersede the efforts and resources it will take to create the process? So with all this in mind I have a few questions- Do you use automation and orchestration within your environment? If so what tasks have you automated thus far? Do you have a rule of thumb that dictates when you will automate a certain task? Believe it or not there are people within this world that are somewhat against automation, whether it be in fear of their jobs or simply not adapting – how do you help “push” these people down the path of automation?