Evolution of Cloud Computing


Published on

Evolution of Cloud Computing

Published in: Technology, News & Politics
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • A new class forms about every decade. It also takes up to a decade to understand how the class formed, evolved, and is likely to continue. Once formed, a lower priced class may evolve in performance to take over and disrupt an existing class.
  • Create multiple virtual environments on a single physical resourceDecouple OS from hardwareCreate a abstraction between OS and the hardwareOptimization of resource utilizationA virtual machine (VM) is a software implementation of a computing environment in which an operating system (OS) or program can be installed and run.The virtual machine typically emulates a physical computing environment, but requests for CPU, memory, hard disk, network and other hardware resources are managed by a virtualization layer which translates these requests to the underlying physical hardware.VMs are created within a virtualization layer, such as a hypervisor or a virtualization platform that runs on top of a client or server operating system. This operating system is known as the host OS. The virtualization layer can be used to create many individual, isolated VM environments.Increased Flexibility (Better Mobility, Backup and Disaster Recovery capacity, Copy and Move Virtual Machines since they are bunch of files)
  • Type 1 (or native, bare metal) hypervisors run directly on the host's hardware to control the hardware and to manage guest operating systems. A guest operating system thus runs on another level above the hypervisor.This model represents the classic implementation of virtual machine architectures; the original hypervisor was CP/CMS, developed at IBM in the 1960s, ancestor of IBM's z/VM. A modern equivalent of this is the Citrix XenServer, VMware ESXi, and Microsoft Hyper-V hypervisor. Type 2 (or hosted) hypervisors run within a conventional operating system environment. With the hypervisor layer as a distinct second software level, guest operating systems run at the third level above the hardware. KVM and Virtualbox are examples of Type 2 hypervisors.In computing, a hypervisor, also called virtual machine manager (VMM), is one of many hardware virtualization techniques allowing multiple operating systems, termed guests, to run concurrently on a host computer.
  • Server consolidation is the management of the total computer server complement to eliminate multiple, individual servers and maximize available resources by loading several different applications on the same server. Database architects or system managers typically complete this function or role. A server is a computer dedicated to the management of data or software applications. It typically has a basic operating system and the rest of the space is used to support multiple users accessing the same software simultaneously. There are four things to consider when looking at server consolidation: hardware, redundancy, operating system, and maximizing efficiency. The purpose of server consolidation is to decrease the number of individual servers and maximize available resources. Make an inventory list of all your servers, operating system, software installed, versions and their primary function and user group. If possible, review the total traffic load, peak times and overall user demand.
  • Evolution of Cloud Computing

    1. 1. Evolution of Cloud Computing http://clean-clouds.comhttp://clean-clouds.com
    2. 2.  Roughly every decade a new, lower priced computer class forms based on a new programming platform, network, and interface resulting in new usage and the establishment of a new industry. Bells Law of Computer Classeshttp://clean-clouds.com
    3. 3. Evolutionhttp://clean-clouds.com
    4. 4. Apps Apps Dev Test Prod ENVs Dev Test Prod ENVs HR Marketing Apps Apps App Dev Test Prod ENVs Dev Test Prod ENVs Finance IT Typical IT Environmenthttp://clean-clouds.com
    5. 5. NO Request Resources Approval END YES Negotiate Resource Configurations NO Resource Wait Availability YES Resource Delivery Resource Provisioning Typical IT Environmenthttp://clean-clouds.com
    6. 6.  Cost Saving ◦ To reduce up front investment in infrastructure  Elasticity ◦ Need to quickly adjust to changes in infrastructure requirements  Reduce time to market ◦ Requisition->Approval Workflows->Acquisition- >Installation and Configuration->Maintenance ◦ Experimental / Innovative Projects / Proof of concepts Business Drivershttp://clean-clouds.com
    7. 7. Waste of 85% 85% 85% 85% Resources Maximum 15% 15% 15% 15% Utilization App App App App OS OS OS OS (Linux) (Linux) (Windows) (Windows) H/W H/W H/W H/W HR Marketing Finance IT Total Capacity 100% 100% 100% 100% Capacity Utilizationhttp://clean-clouds.com
    8. 8. 60% 15% 15% 15% 15% App App App App VMs OS OS OS OS (Linux) (Linux) (Windows) (Windows) H/W H/W H/W H/W HR Marketing Finance IT Virtual Machine Monitor (VMM) / Hypervisor HardwareTotal Capacity 100% Virtualizationhttp://clean-clouds.com
    9. 9. IT Marketing Finance HR Dev Test Prod 99% Availability 99% Availability 99.99% Availability, Site Failover options, Scalable Virtualization Compute Storage Network Virtualizationhttp://clean-clouds.com
    10. 10. Resource Utilization 4 3 Cloud Computing 2 1 Virtualization Server Consolidation Dedicated Servers Time Cloud Journeyhttp://clean-clouds.com
    11. 11. Request Resources Resource Provisioning Resource De- Provisioning Cloud Deployment Modelhttp://clean-clouds.com
    12. 12. Download with Linkedin Username/Password http://clean-clouds.com
    13. 13. Download with Linkedin Username/Password http://clean-clouds.com
    14. 14. Download with Linkedin Username/Password http://clean-clouds.com
    15. 15. Download with Linkedin Username/Password http://clean-clouds.com
    16. 16. Download with Linkedin Username/Password http://clean-clouds.com
    17. 17. http://clean-clouds.com