By Brandy Smith
The proliferation of mobile devices, rapid generation of data, and cheap broadband access (all contributing to the “Digital Tsunami”) has forced many data center providers to re-think how they build capacity, specifically public cloud capacity. Only a few of the traditional providers have transitioned to public cloud. For our part at CenturyLink in the last few years, we’ve expanded our reach to 14 public cloud nodes around the world. Each one offers a compelling mix of elastic services at a competitive price. And we are expanding in each data center constantly. Because of this expertise, many enterprise customers offload infrastructure management to us. But even as many of these businesses shift to public cloud, IT leaders often ask us about how they can run their on-premises deployments more effectively. To paraphrase “how can I bring some public cloud automation pixie dust to my private cloud deployment?” With that backdrop, we wanted to share some of the best practices behind one of our internal automation projects, Tinman. Tinman is a collection of APIs and scripts that ingests a rack of gear, then quickly transforms it into usable compute services. Tinman is how we bring new gear online, in a completely automated way.