Virtualization to Cloud Evolution: "IT as a Service
•Download as PPTX, PDF•
1 like•513 views
The document summarizes the evolution from virtualization to cloud computing. It discusses how virtualization is the foundation for cloud infrastructure by providing secure sandboxes and reliability. Virtualization allows for server consolidation, cost reductions, and load balancing by migrating VMs. The document then outlines the evolution from virtualizing to operationalizing and offering services, as well as changes to IT roles. It defines cloud computing and various service models like IaaS, SaaS, and PaaS. Finally, it provides statistics on cloud adoption and discusses challenges and the future of cloud computing.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Virtualization to Cloud Evolution: "IT as a Service
Similar to Virtualization to Cloud Evolution: "IT as a Service (20)
Recently uploaded
Recently uploaded (20)
Virtualization to Cloud Evolution: "IT as a Service
- 2. October 14th 2012 Virtualization to Cloud Evolution: “IT as a Service” Presented by: Mohamed El Shorbagy Virtualization Engineer at TOPTECH Egypt & President of the “Inevitable Cloud” community
- 4. Advancements in Information Technology
- 5. Data is Growing Exponentially
- 6. Evolution of Virtualization Strategies
- 7. Virtualization Advantages ● Virtualization is the foundation on which cloud infrastructure is built. ● provide secure, isolated sandboxes for running untrusted applications. ● Reliability and Availability, – A software failure in one VM does not affect other VMs. ● Cost, – Server consolidation can bring cost reductions from hardware economies of scale, personnel cost reductions, floor space, and software licenses. - Typical savings: 29% to 64%. ● Load Balancing, – The state of a VM is completely encapsulated in the VMM: easy to migrate VMs to other platforms to improve performance.
- 8. Traditional Architecture Vs. Virtual Architecture
- 13. Virtualization to Cloud Evolution
- 14. Virtualization to Cloud Evolution: Virtualize
- 15. Virtualization to Cloud Evolution: Operationalize
- 16. Virtualization to Cloud Evolution: IT as a Service
- 17. Evolution of IT Roles
- 18. Examples of Cloud Eco-systems
- 19. Service Models
- 20. Myths
- 23. Rabid Elasticity
- 26. Recourse Pooling
- 32. Deployment Model examples: By Market size
- 33. Deployment Model examples: By Market Segment
- 34. Example: Consumer Archive Start-up
- 35. Example: Small to Medium Business Software Manufacturer
- 36. Example: Start-up Hedge Fund Software
- 37. Example: Amazon Public Cloud
- 38. Cloud Statistics 77% Of IT professionals prefer to deploy their infrastructure using virtualization. 38% Acknowledge that “their organization has a written strategic plan for cloud adoption.” 90% Of small business energy costs could be saved using Cloud computing. 84% Of IT managers report that their enterprise uses at least one cloud application. 58% Agree that being on the cloud has given them better control of their data.
- 39. Cloud Future Survey 65% Agree that cloud will be all out reality by 2015, and not just a conceptual idea. 62% Of respondents agree that between 2011 and 2014, most CIOs will deploy only non-mission-critical apps in the public cloud. 36% Agreed that by 2015, at least 30% of Fortune 1000 enterprises will deploy at least one business-critical system in the cloud. 80% Of IT executives surveyed believe metrics related to cloud would grow in importance over the next 12 months. 90% Of IT leaders surveyed believe it will be either “important” or “very critical” to improve IT services tracking in virtualized and cloud environments in the coming year.
- 40. Cloud Components
- 41. Cloud Challenges: Customer’s Perspective
- 42. Summary
- 43. Q&A and Open Discussion
- 44. Thanks for our Academic Sponsor:
- 45. Thanks
Editor's Notes
- As the business shifts to an IT-as-a-Servicemodel new roles may emerge. In the virtualized environment, the role of the VM administrator has evolved (as the tools have evolved), This enables the VM admin to fully manage storage. As these tools continue to evolve, the role of infrastructure manager will be covered by architects who will: design the VDC/Cloud, administrators across the layers, and as things become more automated orchestration and capacity management will grow in importance. Does this mean there are new jobs and old ones are removed? We don’t think that is likely. What we see is a trend to new duties and roles for existing resources. For example, they will spend less time performing the manual tasks, such as change management. As more of the tasks become automated, they will use their time creating templates that have a broader impact and perform automated rolling upgrades.
- This chart shows the basic definitions of different types of service models with some example service providers.Co-location -usually means that the provider has a place in the data center dedicated to your company’s equipment. Your company owns and operates all the equipment and is responsible for managing and operating it. The Colo provides “power, pipe (network), and ping (routing)” and of course heating/cooling and physical security. A Colo usually offers to put your equipment in its own caged off area or in a shared caged area providing a second level of security.Managed Service Provider (MSP) –the equipment can still be owned by the customer and the MSP will add services that help with the management of a customers systems such as: update/patch management, security, backups, DR. Or, the MSP can own the systems and manage them up to the application layer and the customer manages the application and the user community that uses the application.Cloud –in a full public Cloud the equipment is owned by the Cloud provider and seems limitless in terms of scale and power. The customer can use resources based on application demand and pays for the resources used.
- In this example, a consumerarchive start-up collects “captured” information that is in hardcopy format and stores it in the Cloud, encrypted with tags for search/lookups.They used Amazon Web Services Cloud for development and production—all OPEXcosts with almost no capital expenses. They forecasted that if they grew by double every year for 6 years they would save money by using Cloud services for their application development and production. Location of the resources doesn’t matter –as the dev/test environments are served by federated Clouds. Risk is traded off against cost and convenience.