Introduction to Cloud Service Design

Editor's Notes

• #5: Storyline  NetApp provides a cloud data fabric, which will facilitate the established need for seamless connection of cloud resources. Highly efficient transport between systems/clouds to enable the single purview of data management over a cloud data fabric.
• #6: Storyline  Enterprise orgs don’t want to build and run data centers – they will be brokers of services that span on- and off-premises resources. Cloud first. Manage data, not data centers. In the past, CIOs have viewed their IT organizations as a builder of services for the business. But with the explosion of new web services to reach customers, incredible growth in mobile devices, new technologies like flash, the new paradigm of cloud computing, CIOs are dealing with more complexity than ever, and this is driving them to rethink their role. Today, CIOs are moving from being builders of apps and operators of data centers to becoming brokers of information services to the business. They're embracing new technologies and new service models that allow them to make IT faster, cheaper, and smarter and make their companies more responsive and more competitive Moving to the cloud: Customers want lower cost and faster provisioning with scale. Ideally, customers don’t want to manage data center – cloud first if possible. Mandate to move to cloud (we hear the “AWS mandate” all the time). While they need these things, they do not want to (cannot) give up control.
• #7: We’ve all been on an IT journey that started with an application silo using dedicated servers, network, and storage designed to run an application. It’s simple. You can run it under your desk. It’s a pay-for-asset model of service delivery. It’s the kitchen of IT. But then we needed to more rapidly provision infrastructure. With a virtualized infrastructure, I can have a new instance of a server running an application, with network and storage, in just hours or minutes. But its still a pay-for-asset model, and in some ways has more risk because I have to buy hardware and software ahead of time before I can virtualize it and provide rapid provisioning. We all got surprised by VM sprawl, high use of software licenses, and the sudden management problems this created. Shared infrastructure allowed us to either build a hosting model or use external hosted services. IT organizations could start charging for services, instead of just assets, and hosted service providers provided a way to buy hosted services as an operating expense rather than a capital expense. Cloud is the next step and its fundamentally different than hosted services on shared infrastructure. It’s the restaurant of IT. It has a menu of choices. It allows pay-for-use of dynamically consumable service products. There typically is no long term contract, and use can shrink or grow as needed. As you move to the right on this continuum, business agility increases. The cloud model provides maximum business agility with minimum risk for sourcing IT service products.
• #9: Let’s discuss an analogy. You all have a kitchen where you live. It probably cost anywhere from ten thousand to thirty thousand dollars or more to build before you could make your first hamburger. It doesn’t do anything unless someone with knowledge, skills, and resources uses it to produce a custom product. Unless you have all your tools and ingredients ready to use, it may take an hour or more to make food. If you need to go to the store, it might be several hours until you can make lunch or dinner. And if mom is making liver and onions, then that’s what you’re going to eat. Your choices may be very limited. But you may decide that you don’t want liver and onions, so you go three blocks to the nearest restaurant where you can choose the menu and have your food in minutes. You didn’t have to make any investment. Why do you even have a kitchen? How long will it take for your investment in a kitchen to pay off? And then after you invest all that money, you still need people and a well stocked refrigerator before you can produce anything. But what if you could run your kitchen just like a restaurant? How would you do that?
• #13: Service Level Mgt is patented As is the process for the Service Level Mgmt Tool