Where I grew up, you could buy individual cigarettes. While I played ball at the park, I’d see the young men approach the paper kiosk to get a cigarette. Not a pack, just one lonely stick. The customers overpaid on per-cigarette basis but it helped them manage their budget I’d watch them and think nothing of it. It was normal.
People also could buy shampoo in ketchup-sized packages. Unilever still sells them in India. I grew up in the third world, it was the bronze age, but only only on good days. We’re back to bronze with cloud computing, and I’m hyper ready.
For me, the biggest invention cloud computing brings about is unreliable level services. And how important it is to have low quality service levels available on a metered basis. A metered basis the customer can manage. Hear me out.
Today, Amazon’s block storage is unpredictable for databases. The latency in the network is funky. Machines fail to start. Machines don’t fail to fail. Service levels in the cloud don’t exist.
This is not your typical datacenter. It’s a bronze age datacenter. No great expectations, but diminished expectations. And for a young segment of the market, it’s just right and couldn’t be be better.
I sat down with a young start up and asked them why do they use cloud computing if it’s so unreliable, if it requires so much more coding.
Answer: They have more time than money. And the money they have, they have to be parsimonious, avaricious and cautious. They are ok coding more to deal with the cloud’s weirdness. But running out of cash would kil them. The bronze age suits them just fine.
So all the cool kids in Silicon Valley are super excited about writing software for “Designed-to-Fail’ infrastructure. We can’t wait for a chaos monkey to spank us. Well… that’s a San Francisco thing.
So what’s the lesson of this meditation? It’s that service levels are important. Too high and they prevent innovation, too low and they prevent operation.
An “architectural-led” approach to your data center, indeed to your overall IT architecture, given the previous discussion in part 1 and part 2 of this blog, is therefore a strategic imperative for progressive organisations. We in Cisco don’t want to see your IT architecture have problems analogous to the Winchester House. So how can you achieve an “architectural-led” approach? I’ll cover 5 key recommendations in this, my final part of this trilogy :-).
Avoiding the Winchester House Scenario for your IT Architecture
Arguably the place to begin a Cisco UCS blade server journey would be with “Why Blade Servers”. ‘Blades’ are cool. There was “Blade Runner” (a cult classic) and the Wesley Snipes “Blade” movies, several TV series with ‘blade’ in the name, on and on; but for data centers and servers? Why blades? Where is the Blade Server TCO & ROI benefit that drives business decisions and therefore innovation and how do blade servers / chassis get there?
Blade servers have been around since about year 2000 and arguably came about as a way to make data center footprints smaller and reduce power consumption (reduced TCO). Nothing new here for blade enthusiasts. Rack servers were taking up more and more space and power in data centers. The concept of blades was brilliant, insightful and simple. Take as many common rack delivered functionalities (services) as possible, and package them together for delivery to a fixed group of servers. The easy targets for this were server power, cooling, and I/O (well, some I/O functions). To look at it another way, a blade chassis takes a data center rack with servers, I/O cables and switches, then shrinks them into a ‘building block unit’. Once you have the ‘unit’, put a single sheet metal wrapper around everything and voila, a blade chassis. Overly simplistic I know, but a close enough visual. If you want a step-by-step evolution, Sean McGee (a colleague of mine here at Cisco) did a darn good overview The “Mini-Rack” Approach To Blade Server Design.
The demise of Apple’s Steve Jobs is a big loss to the tech industry. He was instrumental in changing the way we consume digital media and communicate. With the unveiling of the iPhone 4s, this week, I wonder if it would change my life any further than cell phones and mobile devices already have. Gone are the days when I called friends ahead of time to get directions to their house. Heck, I don’t even bother reconfirming directions to places I vaguely remember. All because I can count on my cell phone to call the friend in case I get lost (happened to me last week).
Will cell phones and other mobile devices change the way I work more than they already have? Will they change how data centers are managed? If the recent spate of news is any indication I think the answer is yes! What do you think?
According to a recent paper on biomedical-engineering-online.com titled How smartphones are changing the face of mobile and participatory healthcare, “Indeed, Georgetown Medical School in the USA, for example, is now requiring every medical student to have an iPhone, and surgeons are finding the device (and its apps) very useful in improving their diagnostic skills and education .” Closer to home, I found some iPhone applications written specifically for the Cisco Unified Computing System (UCS). One iPhone application , SiMU, monitors the UCS. A second application allows users to find the technical specification of UCS components. Another UCS Systems Management ecosystem partner, Cloupia even has an iPad app to manage the FlexPod -- an integrated server and storage data center offering that includes Cisco UCS.
Remote management is not new, but these mobile devices provide new ways to handle data center management. Clearly these apps are a starting point of changes yet to come in the way we monitor and manage data centers. I would expect the number and variety of applications to only grow, and at times radically change the way we work. Do you agree?
I was given the opportunity to walk around the expo floor at Interop NY 2011 today before I spent some time working in the booth, speaking with customers, and presenting in our theater on the show floor. There were many good conversations around the value proposition of UCS, the magic of service profiles (UCS Manager) to drive automation into server management and reduce operator time spent on tedious configuration chores, the new Nexus 7009, and Cisco’s Virtualized Multi-Tenant Data Center (VMDC) solution design for private and service provider clouds.