<ul><li>Rafiul Ahad, Ph.D. </li></ul><ul><li>Vice President,
Product Development </li></ul><ul><li>Oracle Corporation </li></ul>Cloud Computing: What, Why and How

This presentation reflects my own
view on cloud computing and does not necessarily represent Oracle’s cloud computing strategy. To understand Oracle’s cloud computing strategy, please see various Oracle Open World 2010 presentations available at www.oracle.com/rednetwork

Why

Rationale for Cloud Computing: Application
Developer Perspective <ul><li>Capital Expenditure (CapEx) for development env could be high </li></ul><ul><ul><li>Acquisition of hardware, software, necessary services, etc. </li></ul></ul><ul><ul><li>HW, SW upgrades, back up/restore of dev env, etc. </li></ul></ul><ul><li>Some Operational Expenditure (OpEx) for support, etc. </li></ul><ul><li>Dev env utilization low => Cost per unit time used high </li></ul><ul><li>Wouldn't it be nice if the developer has a basic desktop/laptop and someone else hosts the entire development environment/service for a fee based on usage? </li></ul><ul><li>capex ≈ 0; opex constant for the duration of use </li></ul><ul><li>If development takes too long it may not make economical sense </li></ul><ul><li>For large enterprises, the in-house IT dept can host the dev env </li></ul>

Rationale for Cloud Computing: Quality
Assurance Perspective <ul><li>CapEx for test environment is very high </li></ul><ul><ul><li>Scalability, availability, DR tests require a lot of HW + SW </li></ul></ul><ul><ul><li>Testing permutations of supported technologies requires HW + SW </li></ul></ul><ul><li>OpEx for support, etc. could also be high </li></ul><ul><li>QA env utilization is bursty </li></ul><ul><ul><li>Utilization is very high from end of development to deployment </li></ul></ul><ul><ul><li>Utilization tapers off after deployment </li></ul></ul><ul><li>Cost per unit time used is very high </li></ul><ul><li>Wouldn't it be nice if someone else hosts the testing environment/service and QA pays only for the usage? </li></ul><ul><li>CapEx ≈ 0; OpEx is pay-per-use </li></ul><ul><li>For short release cycles, it may not make economical sense </li></ul><ul><li>For large enterprises, in-house IT dept can host the QA env </li></ul>

Rationale for Cloud Computing: Enterprise
Perspective <ul><li>Application deployment and upgrade cost is very high </li></ul><ul><ul><li>In-house evaluation requires resources </li></ul></ul><ul><ul><li>Pilot deployment requires more resources </li></ul></ul><ul><ul><li>Production deployment requires even more resources </li></ul></ul><ul><li>Cost per end user is very high </li></ul><ul><li>Wouldn't it be nice if someone else hosts your application with a certain service level agreement (SLA) and you pay for the usage? Hosted system should support variations in number of users, compute power, network usage, data storage volume, etc. </li></ul><ul><li>CapEx ≈ 0; OpEx is pay-per-use or per user </li></ul><ul><li>Based on the number of users and resource usage hosted apps can make more economical sense </li></ul><ul><li>Ideal for Small and Medium Businesses (SMB) </li></ul>

Rationale for Cloud Computing: Enterprise
Perspective Source: “An SME perspective on Cloud Computing, a Survey”, The European Network and Information Security Agency, Nov, 2009

Rationale for Cloud Computing: IT
Perspective <ul><li>CapEx for the data center is very high </li></ul><ul><ul><li>Scalability, availability, and DR require redundant HW + SW </li></ul></ul><ul><li>OpEx can also be high </li></ul><ul><ul><li>App administrators, DBA, storage administrators are expensive </li></ul></ul><ul><ul><li>Data center power usage has also become a big issue </li></ul></ul><ul><li>Data center resource utilization is typically low </li></ul><ul><ul><li>Primary system utilization is typically low at non-peak hours </li></ul></ul><ul><ul><li>Redundant HW + SW usually sit idle for a long time </li></ul></ul><ul><li>Cost per unit time used is very high </li></ul><ul><li>Wouldn't it be nice if the resources can be shared among different applications and/or different functions (e.g. QA and production) and/or different departments and/or different tenants to more efficiently use the resources and reduce the HW, space, and power cost? </li></ul>

Hosting Alone is Not Cloud
Computing

What

NIST Definition of Cloud Computing
<ul><li>Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five essential characteristics , three service models, and four deployment models. </li></ul>Source: NIST Definition of Cloud Computing v15 <ul><li>3 Service Models </li></ul><ul><li>SaaS </li></ul><ul><li>PaaS </li></ul><ul><li>IaaS </li></ul><ul><li>4 Deployment Models </li></ul><ul><li>Public Cloud </li></ul><ul><li>Private Cloud </li></ul><ul><li>Community Cloud </li></ul><ul><li>Hybrid Cloud </li></ul><ul><li>5 Essential Characteristics </li></ul><ul><li>On-demand self-service </li></ul><ul><li>Broad network access </li></ul><ul><li>Resource pooling </li></ul><ul><li>Rapid elasticity </li></ul><ul><li>Measured service </li></ul>

Cloud Computing Characteristics: On-Demand Self-Service
<ul><li>A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service’s provider. </li></ul>

Cloud Computing Characteristics: Broad Network
Access <ul><li>Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs). </li></ul>Wireless WAN LAN Etc. HTTP TCP/IP UDP Etc. REST Web Service DAV IMAP Etc.

Cloud Computing Characteristics: Resource Pooling
<ul><li>The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand... Examples of resources include storage, processing, memory, network bandwidth, and virtual machines. </li></ul>

Cloud Computing Characteristics: Rapid Elasticity
<ul><li>Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out, and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time. </li></ul>Enterprise 1 Cluster 1 Enterprise 2 Cluster 2

Cloud Computing Characteristics: Measured Service
<ul><li>Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. </li></ul>

Cloud Computing Service Models: Software-as-a-Service
(SaaS) <ul><li>Consumer uses the provider’s applications running on a cloud. </li></ul>Examples

Cloud Computing Service Models: Platform-as-a-Service
(PaaS) <ul><li>Consumer uses the programming languages and tools supported by the provider to create and deploy applications or deploy acquired applications </li></ul>Examples Elastic Beanstalk (beta)

Cloud Computing Service Models: Infrastructure-as-a-Service
(IaaS) <ul><li>Consumer uses provider’s processing, storage, networks, and other fundamental computing resources to deploy and run arbitrary software, which can include operating systems and applications. </li></ul>Examples Elastic Compute Cloud (EC2)

Cloud Computing Deployment Models <ul><li>Private
cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise. </li></ul><ul><li>Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns. </li></ul><ul><li>Public cloud. The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services. </li></ul><ul><li>Hybrid cloud . The cloud infrastructure is a composition of two or more clouds that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability. </li></ul>

Cloud Computing Deployment Models: Public
Clouds and Private Clouds <ul><li>Used by multiple tenants on a shared basis </li></ul><ul><li>Hosted and managed by cloud service provider </li></ul><ul><li>Exclusively used by a single organization </li></ul><ul><li>Usually managed by in-house IT </li></ul>Public Clouds IaaS PaaS SaaS I N T R A N E T Private Cloud IaaS PaaS SaaS I N T E R N E T Enterprises will adopt a mix of public and private clouds Source:“Enterprise Cloud Computing: What, Why and How” by Rex Wang, Oracle Lower upfront costs Outsourced management OpEx Lower total costs Greater control over security, compliance, QoS CapEx & OpEx Trade-offs IaaS PaaS IaaS PaaS Apps SaaS

Datacenter Evolution From Consolidation to
Private Cloud Private Cloud <ul><li>Self-service </li></ul><ul><li>Policy-based resource management </li></ul><ul><li>Chargeback </li></ul><ul><li>Capacity planning </li></ul>App2 App3 Private IaaS Private PaaS App1 Silo’ d <ul><li>Physical </li></ul><ul><li>Dedicated </li></ul><ul><li>Static </li></ul><ul><li>Heterogeneous </li></ul>App1 App2 App3 Grid <ul><li>Virtual </li></ul><ul><li>Shared services </li></ul><ul><li>Dynamic </li></ul><ul><li>Standardized appliances </li></ul>App1 App2 App3 Private IaaS Private PaaS Consolidate Standardize

Evolution of Private and Public
Clouds Private Cloud Evolution Silo’d Grid <ul><li>Physical </li></ul><ul><li>Dedicated </li></ul><ul><li>Static </li></ul><ul><li>Heterogeneous </li></ul><ul><li>Virtual </li></ul><ul><li>Shared services </li></ul><ul><li>Dynamic </li></ul><ul><li>Standardized appliances </li></ul>App1 App2 App3 App1 App2 App3 Private IaaS Private PaaS Consolidate Standardize Hybrid <ul><li>Federation with public clouds </li></ul><ul><li>Interoperability </li></ul><ul><li>Cloud bursting </li></ul>App1 App2 App3 Private IaaS Private PaaS Virtual Private Cloud Hybrid PaaS SaaS IaaS Private Cloud <ul><li>Self-service </li></ul><ul><li>Policy-based resource mgmt </li></ul><ul><li>Chargeback </li></ul><ul><li>Capacity planning </li></ul>App2 App3 Private IaaS Private PaaS App1 Public Clouds PaaS SaaS IaaS Public Cloud Evolution ASP ISP MSP ISV CSP/ Telcos

How The Technologies Behind the
Cloud

Technologies Behind the Cloud: Resource
Pooling <ul><li>Virtualization </li></ul><ul><li>Clustering </li></ul><ul><li>Grid </li></ul>

Server Virtualization and Clustering Deliver
Resource Pooling and Elastic Scalability Both server virtualization and clustering are key technologies for cloud Single Physical Resource Consumers Multiple Virtual Resources Server Virtualization Make one physical resource look like many Virtualization Software Clustering Software Consumers Multiple Physical Resources Clustering Make many physical resource look like one Single Virtual Resource

Xen Paravirtulization

Rationale for Virtualization App1 App1
App2 App2 Free Free Free Free Before Virtualization: 2 physical machines for App1, 2 for App2 (why 2?) After Virtualization: 3 physical machines each hosting App1, App2 on VM <ul><li>25% savings in </li></ul><ul><li>HW cost </li></ul><ul><li>Space and power usage </li></ul><ul><li>Better availability characteristic (why?) </li></ul>OS OS OS OS HOS/VMM VM1 GOS1 GOS2 VM2 HOS/VMM VM1 GOS1 GOS2 VM2 HOS/VMM VM1 GOS1 GOS2 VM2

Technologies Behind the Cloud: Rapid
Elasticity <ul><li>Cloud Uses Distributed Resource Scheduler </li></ul><ul><li>Sense the change in load </li></ul><ul><ul><li>Reactive or Predictive </li></ul></ul><ul><ul><li>Black box (server level) or clear box (queuing model) </li></ul></ul><ul><li>React to the load changes to avoid bottlenecks </li></ul><ul><ul><li>Add more resources where needed </li></ul></ul><ul><ul><ul><li>Challenge is to react quickly to avoid SLA violation and still be optimal in resource usage </li></ul></ul></ul><ul><ul><li>Remove resources where not needed </li></ul></ul><ul><ul><li>Throttle load if needed </li></ul></ul><ul><ul><ul><li>Triage based on different SLA with different enterprise </li></ul></ul></ul><ul><li>AIT’s Iqbal Waheed and Mathew Dailey do research on this topic </li></ul>

Cloud Reference Architecture

Taxonomy for Cloud Computing Source:
Cloud Computing Use Cases White Paper V2, Cloud Computing Use Case Discussion Group http://creativecommons.org/licenses/by-sa/3.0/

Build Time vs. Run Time
Perspectives Need to Separate Development / Operations Horizons BUILD TIME RUN TIME Source “Enterprise Cloud Computing: What, Why and How” by Rex Wang, Oracle Process Modeling, Simulation and Documentation Deployment Engineering Cloud Monitoring and Metrics Service Identification & Discovery End Users Application Owner Service Developer Service Deployer Cloud Operator Cloud Builder

Example of Build vs. Run
Time 1. Set Up Cloud 2. Build App 3. Use App 4. Manage App BUILD TIME RUN TIME Set up Cloud Platform Set up self-service portal Set up shared components Dept App Build app using shared components IT App Developer Deploy using self service App Users App Owner Manage Adjust Capacity Review Charge-back Use app Self-Service Interface Shared Components Application Server Integration / SOA BPM Portal Security & Identity System Manager Database Operating System,Virtualization,Server,Storage Cloud Platform

Complete Cloud Lifecycle Management Setup
Cloud Infrastructure Build App & Package as Appliance Setup Cloud Policies Deploy Scale Up/Down Decommission Monitor Patch

Is it Real?

Do You Provide or Use
Internal or Private Clouds? Source: IOUG ResearchWire member study on Cloud Computing, conducted in August-September 2010. 28.6% 28.6% of respondents have internal or private clouds today Yes, in production at scale 11.3% Yes, in limited use 12.8% Yes, in pilot stage 4.5% Preliminary planning 4.9% Under consideration 10.5% No 47.4% Don ’t know/unsure 8.7%

What Type of Private Platform
and Infrastructure Cloud Services Is Your Company Providing? Source: IOUG ResearchWire member study on Cloud Computing, conducted in August-September 2010. Most popular: App Server as a service Database as a service PaaS IaaS Application server platform as a service 24.7% Database platform as a service 21.4% Identity as a service 4.7% Compute as a service 10.2% Storage as a service 18.1% Software development and test as a service 14.9% Don ’t know/unsure 20.5% None 37.2%

Cloud Computing Challenges <ul><li>Security </li></ul><ul><ul><li>Consumers
don’t necessarily know who has access to their data and how it is managed </li></ul></ul><ul><ul><li>Records management and compliance </li></ul></ul><ul><li>Service Level Agreement </li></ul><ul><ul><li>May not be good enough for some mission critical applications </li></ul></ul><ul><li>Payment </li></ul><ul><ul><li>Metering is not mature yet. Not easy for consumers to verify his/her usage easily </li></ul></ul>

Summary <ul><li>Cloud computing attempts to
formalize the characteristics of a next generation application development and deployment environment that can </li></ul><ul><ul><li>Lower the cost of application development and deployment specially for small and medium businesses </li></ul></ul><ul><ul><li>Increase the efficiency of data centers </li></ul></ul><ul><li>To learn more about cloud computing, please attend Oracle Cloud Summit event in Bangkok. See www.oracle.com/goto/cloudevents for details. </li></ul>

A Q &