What Does Automation Look Like?Posted by Duke Skarda in Executive Blog, Infrastructure, SoftLayer, Technology
Innovation. Automation. Innovation. Automation. Innovation. Automation. That’s been our heartbeat since SoftLayer was born on May 5, 2005. The “Innovation” piece is usually the most visible component of that heartbeat while “Automation” usually hangs out behind the scenes (enabling the “Innovation”). When we launch a new product line like Object Storage, add new functionality to the SoftLayer API, announce a partnership with a service provider like RightScale, or simply receive and rack the latest and greatest server hardware from our vendors, our automated platform allows us to do it quickly and seamlessly. Because our platform is built to do exactly what it’s supposed to without any manual intervention, it’s easily overlooked.
But what if we wanted to show what automation actually looks like?
It seems like a silly question to ask. If our automated platform is powered by software built by the SoftLayer development team, there’s no easy way to show what that automation looks like … At least not directly. While the bits and bytes aren’t easily visible, the operational results of automation are exceptionally photogenic. Let’s take a look at a few examples of what automation enables to get an indirect view of what it actually looks like.
Example: A New Server Order
A customer orders a dedicated server. That customer wants a specific hardware configuration with a specific suite of software in a specific data center, and it needs to be delivered within four hours. What does that usually look like from an operations perspective?
If you want to watch those blinking lights for two or three hours, you’ll have effectively watched a new server get provisioned at SoftLayer. When an order comes in, the automated provisioning system will find a server matching the order’s hardware requirements in the requested data center facility, and the software will be installed before it is handed over to the the customer.
Example: Server Reboot or Operating System Reload
A customer needs to reboot a server or install a new operating system. Whether they want a soft reboot, a hard reboot with a full power cycle or a blank operating system install, the scene in the data center will look eerily familiar:
Gone are the days of server build technicians wheeling a terminal over to every server that needs work done. From thousands of miles away, a customer can remotely “unplug” his or her server via the rack’s power strip, initiate a soft reboot or reinstall an operating system. But what if they want even more accessibility?
Example: What’s on the Screen?
When remotely rebooting or power cycling a server isn’t enough, a customer might want someone in the data center to wheel over to their server in the rack to look at any of the messages that can only be read with a monitor attached. This would generally happen behind the server, but for the sake of this example, we’ll just watch the data center technician pass in front of the servers to get to the back:
Yeah, you probably could have seen that one coming.
Because KVM over IP is included on every server, physical carts carrying “keyboard, video and mouse” are few and far between. By automating customers’ access to their server and providing as much virtual access as we possibly can, we’re able to “get out of the way” of our technical users and only step in to help when that help is needed.
I could go on and on with examples of cloud computing upgrades and downgrades, provisioning a firewall or adding a load balancers, but I’ll practice a little restraint. If you want the full effect, you can scroll up and watch the blinking lights a little while longer.
Automation looks like what you don’t see. No humanoid robots or needlessly complex machines (that I know of) … Just a data center humming along with some beautiful flashing server lights.
P.S. If you want to be able to remotely bask in the glow of some blinking server lights, bookmark the larger-sized SoftLayer Rack animated gif … You could even title the bookmark, “Check on the Servers.”