Why automation ?
1. Engineers should work on hard things, not easy things. Ticket management, troubleshooting and mundane things are not useful to the business or to
2. Predictable, repeatable changes to operational systems. Manual processes are inconsistent and idiomatic. Hand crafted, artisanal operations delivered by
3. Reduce the man-hour cost of common changes. Scripts require less operational time to action.
4. Controlled configuration – change using an API is inherently a controlled process. Automated change scripts are readily controlled on the source platform (and removes the costs & penalties of ITIL)
5. Testing and validation – automated scripts and SDN platforms should be used to conduct testing and post-change validation to verify that business services is operational and valid.
6. Silo breakdown – orchestration and automation should span multiple silos e.g. provisioning a server should be automated and require interaction between sysadmins, developers, server/virtualization, storage and network teams can break free from silos to co-operate.
7. Enable the Impossible – old saying: ‘man who looks at feet while walking does not see where he is going’. Once freed from low value tasks, bigger problems can be addressed that we not possible before. Equally important, we can see the major issues more clearly as the minor tasks are removed.