One of the reasons I was originally so blas\u00e9 about Cloud was that it was old-hat. The same way that mainframe jockeys yawned and rolled their eyes when midrange people started talking about the wonders of virtualisation, I listened to people in IT extolling Cloud and found myself rolling my eyes \u2013 not just over the lack of data protection in early Cloud solutions \u2013 but to the stories about how Cloud was agile<\/em>. And there’s no prizes for guessing where agility comes from: automation.<\/p>\nIt surprises me twenty years on that the automation debate is still going on, and some people remain unconvinced.<\/p>\n
There are three fundamental results of automation:<\/p>\n
\nRepeatability<\/li>\n Reliability<\/li>\n Verifiability<\/li>\n<\/ul>\nWhen something is properly automated, it can be repeated easily and readily. That’s a fundamental tenet driving Cloud agility: you click on a button on a portal and hey presto!<\/em>, a virtual machine is spun up and you receive an IP address to access it from. Or you click on a button on a portal and suddenly you’ve got yourself a SQL database or Exchange server or CRM system or any one of hundreds of different applications or business functions. If there’s human intervention at the back-end between when you click the button and when you get your service it’s not agile<\/em>. It’s not Cloud<\/em>. And it’s certainly not automated<\/em>. Well, not fully or properly.<\/p>\nWith repeatability becomes reliability \u2013 accuracy. It doesn’t matter whether the portal has been up for 1 hour or 1000 hours, it doesn’t matter whether it’s 01:00 or 13:00, and it doesn’t matter how many requests the portal has got: it’s not prone to error, it won’t miss a check-box because it’s rushed or tired or can’t remember what the correct option is. It doesn’t matter whether the computer doing the work in the background has never done it before because it’s just been added to the resource pool, or whether it’s done the process a million times before. Automation isn’t just about repeatability, it’s about reliable <\/em>repeatability.<\/p>\nEqually as importantly, with automation \u2013 with repeatability \u2013 there comes verifiability<\/em>. Not only can you reliably repeat the same activity time and time again, but every time it’s executed you can verify it was<\/em> executed. You can monitor, measure and report. This can be from the simplest \u2013 verifying it was performed successfully or throwing an exception for a human to investigate \u2013 to the more complex, such as tracking and reporting the trends on how long it takes automated processes to complete, so you can see keep an eye on how the system is scaling.<\/p>\nOnce you’ve got automation in place, you’ve freed up your IT staff from boring and repetitive duties. That’s not to remove them from their jobs, but to let the humans in your staff do the jobs humans do best: those involving dealing with the unexpected, or thinking of new solutions. Automated, repeatable tasks are best left to scripts and processes and even robots (when it comes to production). The purpose of being a lazy system administrator was not so that you could sit at your desk doing nothing all day, but so you could spend time handling exceptions and errors, designing new systems, working on new projects, and yes, automating new systems.<\/p>\n
Automation is not just a Cloud thing. Automation is not just a system administration thing. Or a database\/application administration thing. Or a build thing. Or a…<\/p>\n
Automation is every<\/em>thing in IT, particularly in the infrastructure space. Cloud has well and truly raised the profile of automation, but the fundamental concept is not new. I’d go so far as to say that if your business isn’t focused on automation, you’re doing IT wrong.<\/p>\n","protected":false},"excerpt":{"rendered":"It was not long after I started in IT that I got the most important advice of my career. It came from a…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[3,1133,12],"tags":[132],"class_list":["post-5858","post","type-post","status-publish","format-standard","hentry","category-architecture","category-best-practice","category-general-technology","tag-automation"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t
![\"Automation\"](\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2016\/04\/bigStock-Robot-Hand.jpg\")
<\/a><\/p>\n