Cloud Computing


Published on

It is on Cloud Computing presented by Sweta Agarwal, Radhika Gupta, Shivi Agarwal, Madhusudan Partani of FMG-18A, FORE School of Management

Published in: Business
  • Be the first to comment

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

No notes for slide
  • Evolved over a period of timeRoots traced back to Application Service Providers in the 1990’sParallels to SaaSEvolved from Utility computing and is a broader concept
  • Grid Computing – a form of distributed computingCluster of loosely coupled, networked computers acting in concert to perform very large tasksUtility Computing – packaging of computing resources such as computing power, storage, also a metered servicesAutonomic computing – self managed
  • Application Services(services on demand)Gmail, GoogleCalenderPayroll, HR, CRM etcSugarm CRM, IBM Lotus LivePlatform Services (resources on demand)Middleware, Intergation, Messaging, Information, connectivity etcAWS, IBM Virtual images, Boomi, CastIron, Google AppengineInfrastructure as services(physical assets as services)IBM Blue house, VMWare, Amazon EC2, Microsoft Azure Platform, Sun Parascale and more
  • Sometimes called Utility computing
  • Cloud Computing

    1. 1. Cloud computing<br />
    2. 2.
    3. 3. Cloud computing and other computing techniques<br />
    4. 4. Evolution<br />
    5. 5. Cloud Computing - Some terms<br /><ul><li>Term cloud is used as a metaphor for internet
    6. 6. Concept generally incorporates combinations of the following
    7. 7. Infrastructure as a service (IaaS)
    8. 8. Platform as a service (PaaS)
    9. 9. Software as a service(SaaS)
    10. 10. Not to be confused with
    11. 11. Grid Computing
    12. 12. Utility Computing
    13. 13. Autonomic computing </li></li></ul><li>Grid Computing<br /><ul><li>Share Computers and data
    14. 14. Evolved to harness inexpensive computers in Data center to solve variety of problems
    15. 15. Harness power of loosely coupled computers to solve a technical or mathematical problem
    16. 16. Used in commercial applications for drug discovery, economic forecasting, sesimic analysis and back-office
    17. 17. Most financial firms has grids like this
    18. 18. Grids lack automation, agility, simplicity and SLA guarantees</li></li></ul><li>Grid Computing ~ Cont…<br /><ul><li>Small to big
    19. 19. Can be confined to a corporation
    20. 20. Large public collaboration across many companies and networks
    21. 21. Most grid solutions are built on
    22. 22. Computer Agents
    23. 23. Resource Manager
    24. 24. Scheduler
    25. 25. Compute grids
    26. 26. Batch up jobs
    27. 27. Submit the job to the scheduler, specifying requirements and SLA(specs) required for running the job
    28. 28. Scheduler matches specs with available resources and schedules the job to be run
    29. 29. Farms could be as large as 10K CPUs</li></li></ul><li>Utility Computing<br /><ul><li>More related to cloud computing
    30. 30. Applications, storage, computing power and network
    31. 31. Requires cloud like infrastructure
    32. 32. Pay by the drink model
    33. 33. Similar to electric service at home
    34. 34. Pay for extra resources when needed
    35. 35. To handle expected surge in demand
    36. 36. Unanticipated surges in demand
    37. 37. Better economics</li></li></ul><li>What is cloud and cloud computing?<br />Cloud Demand resources or services over Internet scale and reliability of a data center.<br />Cloud computing is a style of computing in which dynamically scalable and often virtualized resources are provided as a serve over the Internet. <br /> Users need not have knowledge of, expertise in, or control over the technology infrastructure in the "cloud" that supports them.<br />
    38. 38. Clouds Versus Grids<br /> Clouds and Grids are distinct<br /><ul><li>Cloud
    39. 39. Full private cluster is provisioned
    40. 40. Individual user can only get a tiny fraction of the total resource pool
    41. 41. No support for cloud federation except through the client interface
    42. 42. Opaque with respect to resources
    43. 43. Grid
    44. 44. Built so that individual users can get most, if not all of the resources in a single request
    45. 45. Middleware approach takes federation as a first principle
    46. 46. Resources are exposed, often as bare metal
    47. 47. These differences mandate different architectures for each</li></li></ul><li>Commercial clouds<br />
    48. 48. Cloud Computing - layers<br />Architecture<br />Layers<br />
    49. 49. The architecture of cloud computing system<br />
    50. 50. What is a Cloud?<br />Individuals<br />Non-Commercial<br />Corporations<br />Cloud Middle Ware<br />Storage <br />Provisioning<br />Service(apps)<br />Provisioning<br />Network<br />Provisioning<br />SLA(monitor), <br />Security, Billing,<br /> Payment<br />OS<br />Provisioning<br />Resources<br />Services<br />OS<br />Network<br />Storage<br />
    51. 51. Why we use cloud computing?<br />
    52. 52. Why we use cloud computing? Simple example<br />Case 1:<br />Write a file <br />Save<br />Computer down, file is lost  <br />Case 2: <br /> Files are always stored in cloud, never lost  <br />
    53. 53. Why cloud computing<br /><ul><li>Data centers are notoriously underutilized, often idle 85% of the time
    54. 54. Over provisioning
    55. 55. Insufficient capacity planning and sizing
    56. 56. Improper understanding of scalability requirements etc</li></li></ul><li>Why to Use Cloud Computing?<br />Cloud computing offers three potential benefits:<br />Cost<br />Flexibility/Speed of implementation <br />Scalability (sometimes called Elasticity)<br />
    57. 57. Cloud computing - Characteristics<br /><ul><li>Agility – On demand computing infrastructure
    58. 58. Linearly scalable – challenge
    59. 59. Reliability and fault tolerance
    60. 60. Self healing – Hot backups, etc
    61. 61. SLA driven – Policies on how quickly requests are processed
    62. 62. Multi-tenancy – Several customers share infrastructure, without compromising privacy and security of each of the customer’s data</li></li></ul><li>Cloud computing - Characteristics<br /><ul><li>Service-oriented – compose applications out of loosely coupled services. One service failure will not disrupt other services. Expose these services as API’s
    63. 63. Virtualized – decoupled from underlying hardware. Multiple applications can run in one computer
    64. 64. Data, Data, Data
    65. 65. Distributing, partitioning, security, and synchronization</li></li></ul><li>How do they work?<br /><ul><li>Public clouds are opaque
    66. 66. What applications will work well in a cloud?
    67. 67. Many of the advantages offered by Public Clouds appear useful for “on premise” IT
    68. 68. Self-service provisioning
    69. 69. Legacy support
    70. 70. Flexible resource allocation
    71. 71. What extensions or modifications are required to support a wider variety of services and applications?
    72. 72. Data assimilation
    73. 73. Multiplayer gaming
    74. 74. Mobile devices</li></li></ul><li>Public, Private and Hybrid clouds<br />
    75. 75. Public clouds<br /><ul><li>Open for use by general public
    76. 76. Exist beyond firewall, fully hosted and managed by the vendor
    77. 77. Individuals, corporations and others
    78. 78. Amazon's Web Services and Google appEngine are examples
    79. 79. Offers startups and SMB’s quick setup, scalability, flexibility and automated management. Pay as you go model helps startups to start small and go big
    80. 80. Security and compliance?
    81. 81. Reliability concerns hinder the adoption of cloud
    82. 82. Amazon S3 services were down for 6 hours</li></li></ul><li>Public Clouds (Now)<br /><ul><li>Large scale infrastructure available on a rental basis
    83. 83. Operating System virtualization (e.g. Xen, kvm) provides CPU isolation
    84. 84. “Roll-your-own” network provisioning provides network isolation
    85. 85. Locally specific storage abstractions
    86. 86. Fully customer self-service
    87. 87. Service Level Agreements (SLAs) are advertized
    88. 88. Requests are accepted and resources granted via web services
    89. 89. Customers access resources remotely via the Internet
    90. 90. Accountability is e-commerce based
    91. 91. Web-based transaction
    92. 92. “Pay-as-you-go” and flat-rate subscription
    93. 93. Customer service, refunds, etc.</li></li></ul><li>Private Clouds<br /><ul><li>Within the boundaries(firewall) of the organization
    94. 94. All advantages of public cloud with one major difference
    95. 95. Reduce operation costs
    96. 96. Has to be managed by the enterprise
    97. 97. Fine grained control over resources
    98. 98. More secure as they are internal to org
    99. 99. Schedule and reshuffle resources based on business demands
    100. 100. Ideal for apps related to tight security and regulatory concerns
    101. 101. Development requires hardware investments and in-house expertise
    102. 102. Cost could be prohibitive and cost might exceed public clouds </li></li></ul><li>Cloud Anatomy<br />
    103. 103. Types of cloud service<br />SaaS<br />Software as a Service<br />PaaS<br />Platform as a Service<br />IaaS<br />Infrastructure as a Service<br />
    104. 104. SaaS<br />Software delivery model<br />No hardware or software to manage<br />Service delivered through a browser<br />Customers use the service on demand<br />Instant Scalability<br />
    105. 105. SaaS<br />Examples<br />Your current CRM package is not managing the load or you simply don’t want to host it in-house. Use a SaaS provider such as<br />Your email is hosted on an exchange server in your office and it is very slow. Outsource this using Hosted Exchange.<br />
    106. 106. Software as a Service - SaaS<br /><ul><li>Gmail & Yahoo Mail
    107. 107. Google Docs
    108. 108. Mozy Online Backups
    109. 109. CRM</li></ul>Remember Application Service Providers? <br /> The next big thing of 2000 that didn't happen.<br />
    110. 110. PaaS<br />Platform delivery model<br />Platforms are built upon Infrastructure, which is expensive<br />Estimating demand is not a science!<br />Platform management is not fun!<br />
    111. 111. PaaS<br />Examples<br />You need to host a large file (5Mb) on your website and make it available for 35,000 users for only two months duration. Use Cloud Front from Amazon.<br />You want to start storage services on your network for a large number of files and you do not have the storage capacity…use Amazon S3.<br />
    112. 112. Platform as a Service<br />© Copyright 2009 Reliable Software, Inc.<br />Google App Engine<br />Amazon EC2<br />Microsoft Azure<br /><br />Rackspace Intensive<br />…<br />
    113. 113. IaaS<br />Computer infrastructure delivery model<br />A platform virtualization environment<br />Computing resources, such as storing and processing capacity.<br />Virtualization taken a step further<br />
    114. 114. IaaS<br />Examples<br />You want to run a batch job but you don’t have the infrastructure necessary to run it in a timely manner. Use Amazon EC2.<br />You want to host a website, but only for a few days. Use Flexiscale.<br />
    115. 115. Infrastructure as a Service<br />© Copyright 2009 Reliable Software, Inc.<br />Hosted Exchange<br /><br />Facebook<br />Gmail<br />Mozy<br />
    116. 116. Cloud computing and Ecommerce<br />At least 90 percent of ecommerce businesses will be using some form of cloud computing in the next five years.<br />
    117. 117. Cloud computing open issues<br /><ul><li>Governance
    118. 118. Security, Privacy and control
    119. 119. SLA guarantees
    120. 120. Ownership and control
    121. 121. Compliance and auditing
    122. 122. Sarbanes and Oxley Act
    123. 123. Reliability
    124. 124. Good servive provider with 99.999% availability
    125. 125. Cloud independence – Vendor lockin?
    126. 126. Cloud provider goes out of business
    127. 127. Data Security
    128. 128. Cloud lockin and Loss of control
    129. 129. Plan for moving data along with Cloud provider
    130. 130. Cost?
    131. 131. Simplicity?
    132. 132. Tools
    133. 133. Controls on sensitive data?
    134. 134. Out of business
    135. 135. Big and small
    136. 136. Scalability and cost outweigh reliability for small businesses
    137. 137. Big businesses may have a problem</li>