The document provides an extensive overview of cloud computing, detailing its definitions, characteristics, service models, and benefits. It includes perspectives from notable figures like Oracle's CEO and Rich Stallman, as well as technical aspects like service-oriented architecture, scalability, elasticity, and fault tolerance. Additionally, it discusses the importance of security, manageability, interoperability, and performance optimization in cloud environments.

1. Agenda
• What is Cloud Computing ?
▪ Different perspectives
▪ Properties and characteristics
▪ Benefits from cloud computing
• Service and deployment models
▪ Three service models
▪ Four deployment models

5. WHAT IS CLOUD COMPUTING ?
What do they say ?

6. Cloud Disclaimers
• Talk from Oracle CEO Larry Ellison
▪ We’ve redefined Cloud Computing to include everything that we
already do. I don’t understand what we would do differently other
than change the wording of some of our ads.
• Talk from Rich Stallman
▪ It's stupidity. It's worse than stupidity: it's a marketing hype
campaign. Somebody is saying this is inevitable – and whenever
you hear somebody saying that, it's very likely to be a set of
businesses campaigning to make it true.

7. Cloud Definitions
• Definition from NIST(National Institute of Standards and Technology)
▪ Cloud computing is a model for enabling 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.

8. Cloud Definitions
• Definition from Wikipedia
▪ Cloud computing is Internet-based computing, whereby shared
resources, software, and information are provided to computers
and other devices on demand, like the electricity grid.
▪ Cloud computing is a style of computing in which dynamically
scalable and often virtualized resources are provided as a service
over the Internet.

9. Cloud Definitions
• Definition from Whatis.com
▪ The name cloud computing was inspired by the cloud symbol that's
often used to represent the Internet in flowcharts and diagrams.
Cloud computing is a general term for anything that involves
delivering hosted services over the Internet.
• Definition from Whatis.com
▪ The name cloud computing was inspired by the cloud symbol that's
often used to represent the Internet in flowcharts and diagrams.
Cloud computing is a general term for anything that involves
delivering hosted services over the Internet.

10. • Definition from Berkeley
▪ Cloud Computing refers to both the applications delivered as
services over the Internet and the hardware and systems software
in the datacenters that provide those services.
▪ The services themselves have long been referred to as Software as a
Service (SaaS), so we use that term. The datacenter hardware and
software is what we will call a
Cloud.
▪ When a Cloud is made available
in a pay-as-you-go manner to the
public…… The service being sold is
Utility Computing.
• Definition from Berkeley
▪ Cloud Computing refers to both the applications delivered as
services over the Internet and the hardware and systems
software in the datacenters that provide those services.
▪ The services themselves have long been referred to as Software as
a Service (SaaS), so we use that term. The datacenter hardware
and software is what we will call a
Cloud.
▪ When a Cloud is made available
in a pay-as-you-go manner to the
public…… The service being sold is
Utility Computing.
Cloud Definitions

11. Cloud Definitions
• Definition from Buyya
▪ A Cloud is a type of parallel and distributed system consisting of a
collection of interconnected and virtualized computers that are
dynamically provisioned and presented as one or more unified
computing resources based on service-level agreements
established through negotiation between the service provider and
consumers.

12. Even More Confusing ??

13. WHAT IS CLOUD COMPUTING ?
Properties and characteristics

14. In Our Humble Opinion
• Cloud computing is a paradigm of computing, a new way of
thinking about IT industry but not any specific technology.
▪ Central ideas
Utility Computing
SOA - Service Oriented Architecture
SLA - Service Level Agreement
▪ Properties and characteristics
High scalability and elasticity
High availability and reliability
High manageability and interoperability
High accessibility and portability
High performance and optimization
▪ Enabling techniques
Hardware virtualization

15. Properties and Characteristics

16. What Is Service?
• Service is what you connect together using Web Services.
• Service is the endpoint of a connection.
• Functionalities of service :
▪ A service should be well-defined
▪ A service should be self-contained
▪ A service should not depend on the context or state of other services.
Utility
Computing
SOA + SLA

17. What Is Web Service?
• Definition :
▪ Web service is self-describing and stateless modules that perform
discrete units of work and are available over the network
▪ Web service providers offer APIs that enable developers to exploit
functionality over the Internet, rather than delivering full-blown
applications
• Web Services Description Language (WSDL) :
▪ Expressed in XML which include both data type and messages
▪ Four types of operations :
• One-way - Messages sent without a reply required
• Request & response - Sending and replying messages
• Solicit response - A request for a response
• Notification - Messages sent to multiple receivers
Utility
Computing
SOA + SLA

18. Service Oriented Architecture
• Definition
▪ Service Oriented Architecture (SOA) is essentially a collection of
services which communicate with each other
▪ Contain a flexible set of design principles used during the phases of
systems development and integration
▪ Provide a loosely-integrated suite of services that can be used within
multiple business domains
• Approach
▪ Usually implemented by Web Service model
Utility
Computing
SOA + SLA

19. Scalability & Elasticity
Give me the world
without limitation!!

20. Scalability & Elasticity
• What is scalability ?
▪ A desirable property of a system, a network, or a process, which
indicates its ability to either handle growing amounts of work in a
graceful manner or to be readily enlarged.
• What is elasticity ?
▪ The ability to apply a quantifiable methodology that allows for the
basis of an adaptive introspection with in a real time infrastructure.
• But how to achieve these properties ?
▪ Dynamic provisioning
▪ Multi-tenant design

21. Dynamic Provisioning
• What is dynamic provisioning ?
▪ Dynamic Provisioning is a simplified way to explain a complex
networked server computing environment where server
computing instances are provisioned or deployed from a
administrative console or client application by the server
administrator, network administrator, or any other enabled
user.

22. Dynamic Provisioning
• In traditional computing model, two common problems :
▪ Underestimate system utilization which result in under provision
Resource
s
Dem
and
Capa
city
1 2 3
Resourc
es
Dem
and
Capa
city
1 2 3
Resourc
es
Dem
and
Capa
city
Time
(days)
1 2 3
Loss Users
Loss Revenue

23. Dynamic Provisioning
▪ Overestimate system utilization which result in low utilization
• How to solve this problem ??
▪ Dynamically provision resources
Unused resources
Demand
Capacity
Time
Resource
s

24. Dynamic Provisioning
• Cloud resources should be provisioned dynamically
▪ Meet seasonal demand variations
▪ Meet demand variations between different industries
▪ Meet burst demand for some extraordinary events
Demand
Capacity
Time
Resource
s
Demand
Capacity
Time
Resource
s

25. Multi-tenant Design
• What is multi-tenant design ?
▪ Multi-tenant refers to a principle in software architecture where a
single instance of the software runs on a server, serving multiple
client organizations.
▪ With a multi-tenant architecture, a software application is designed
to virtually partition its data and configuration thus each client
organization works with a customized virtual application instance.
• Client oriented requirements :
▪ Customization
• Multi-tenant applications are typically required to provide a high degree
of customization to support each target organization's needs.
▪ Quality of service
• Multi-tenant applications are expected to provide adequate levels of
security and robustness.

26. Availability & Reliability
Data Never Loss
Machine Never Fail

27. Availability & Reliability
• What is availability ?
▪ The degree to which a system, subsystem, or equipment is in a specified
operable and committable state at the start of a mission, when the mission
is called for at an unknown time.
▪ Cloud system usually require high availability
• Ex. “Five Nines” system would statistically provide 99.999% availability
• What is reliability ?
▪ The ability of a system or component to perform its required functions
under stated conditions for a specified period of time.
• But how to achieve these properties ?
▪ Fault tolerance system
▪ Require system resilience
▪ Reliable system security

28. Fault Tolerance
• What is fault tolerant system ?
▪ Fault-tolerance is the property that enables a system to continue
operating properly in the event of the failure of some of its
components.
▪ If its operating quality decreases at all, the decrease is proportional
to the severity of the failure, as compared to a naively-designed
system in which even a small failure can cause total breakdown.
• Four basic characteristics :
▪ No single point of failure
▪ Fault detection and isolation to the failing component
▪ Fault containment to prevent propagation of the failure
▪ Availability of reversion modes

29. Fault Tolerance
• Single Point Of Failure (SPOF)
▪ A part of a system which, if it fails, will stop the
entire system from working.
▪ The assessment of a potentially single location of
failure identifies the critical components of a
complex system that would provoke a total
systems failure in case of malfunction.
• Preventing single point of failure
▪ If a system experiences a failure, it must continue
to operate without interruption during the repair
process.

30. Fault Tolerance
• Fault Detection and Isolation (FDI)
▪ A subfield of control engineering which concerns itself with
monitoring a system, identifying when a fault has occurred and
pinpoint the type of fault and its location.
• Isolate failing component
▪ When a failure occurs, the system
must be able to isolate the failure
to the offending component.

31. Fault Tolerance
• Fault Containment
▪ Some failure mechanisms can cause a system to fail by propagating
the failure to the rest of the system.
▪ Mechanisms that isolate a rogue transmitter or failing component
to protect the system are required.
• Available of reversion modes
▪ System should be able to maintain some check points which can be
used in managing the state changes.

32. System Resilience
• What is resilience ?
▪ Resilience is the ability to provide and maintain an acceptable level
of service in the face of faults and challenges to normal operation.
▪ Resiliency pertains to the system's ability to return to its original
state after encountering trouble. In other words, if a risk event
knocks a system offline, a highly resilient system will return back to
work and function as planned as soon as possible.
• Some risk events
▪ If power is lost at a plant for two days, can our system recover ?
▪ If a key service is lost because a database corruption, can the
business recover ?

33. System Resilience
• Disaster Recovery
▪ Disaster recovery is the process, policies and procedures related to
preparing for recovery or continuation of technology infrastructure
critical to an organization after a natural or human-induced
disaster.
• Some common strategies :
▪ Backup
• Make data off-site at regular interval
• Replicate data to an off-site location
• Replicate whole system
▪ Preparing
• Local mirror systems
• Surge protector
• Uninterruptible Power Supply (UPS)

34. System Security
• Security issue in Cloud Computing :
▪ Cloud security is an evolving sub-domain of computer security,
network security, and, more broadly, information security.
▪ It refers to a broad set of policies, technologies, and controls
deployed to protect data, applications, and the associated
infrastructure of cloud computing.

35. System Security
• Important security and privacy issues :
▪ Data Protection
• To be considered protected, data from one customer must be
properly segregated from that of another.
▪ Identity Management
• Every enterprise will have its own identity management system
to control access to information and computing resources.
▪ Application Security
• Cloud providers should ensure that applications available as a
service via the cloud are secure.
▪ Privacy
• Providers ensure that all critical data are masked and that only
authorized users have access to data in its entirety.

36. Manageability & Interoperability
I Want Full Control !!

37. Manageability & Interoperability
• What is manageability ?
▪ Enterprise-wide administration of cloud computing systems.
Systems manageability is strongly influenced by network
management initiatives in telecommunications.
• What is interoperability ?
▪ Interoperability is a property of a product or system, whose
interfaces are completely understood, to work with other products
or systems, present or future, without any restricted access or
implementation.
• But how to achieve these properties ?
▪ System control automation
▪ System state monitoring

38. Control Automation
• What is Autonomic Computing ?
▪ Its ultimate aim is to develop computer systems capable of
self-management, to overcome the rapidly growing complexity of
computing systems management, and to reduce the barrier that
complexity poses to further growth.
• Architectural framework :
▪ Composed by Autonomic Components (AC) which will interact
with each other.
▪ An AC can be modeled in terms of two main control loops (local
and global) with sensors (for self-monitoring), effectors (for
self-adjustment), knowledge and planer/adapter for exploiting
policies based on self- and environment awareness.

39. Control Automation
• Four functional areas :
▪ Self-Configuration
• Automatic configuration of components.
▪ Self-Healing
• Automatic discovery, and correction of faults.
▪ Self-Optimization
• Automatic monitoring and control of resources to ensure the optimal
functioning with respect to the defined requirements.
▪ Self-Protection
• Proactive identification and protection from arbitrary attacks.

40. System Monitoring
• What is system monitor ?
▪ A System Monitor in systems engineering is a process within a
distributed system for collecting and storing state data.
• What should be monitored in the Cloud ?
▪ Physical and virtual hardware state
▪ Resource performance metrics
▪ Network access patterns
▪ System logs
▪ … etc
• Anything more ?
▪ Billing system

41. Performance & Optimization
High Performance
Improvement

42. Performance & Optimization
• Performance guarantees ??
▪ As the great computing power in cloud, application performance
should be guaranteed.
▪ Cloud providers make use of powerful infrastructure or other
underlining resources to build up a highly performed and highly
optimized environment, and then deliver the complete services to
cloud users.
• But how to achieve this property ?
▪ Parallel computing
▪ Load balancing
▪ Job scheduling

43. Parallel Processing
• Parallel Processing
▪ Parallel processing is a form of computation in which many
calculations are carried out simultaneously, operating on the
principle that large problems can often be divided into smaller
ones, which are then solved concurrently.
• Parallelism in different levels :
▪ Bit level parallelism
▪ Instruction level parallelism
▪ Data level parallelism
▪ Task level parallelism

44. Parallel Processing
• Hardware approaches
▪ Multi-core computer
▪ Symmetric multi-processor
▪ General purpose graphic processing unit
▪ Vector processor
▪ Distributed computing
• Cluster computing
• Grid computing
• Software approaches
▪ Parallel programming language
▪ Automatic parallelization

45. Load Balancing
• What is load balancing ?
▪ Load balancing is a technique to distribute workload evenly across
two or more computers, network links, CPUs, hard drives, or other
resources, in order to get optimal resource utilization, maximize
throughput, minimize response time, and avoid overload.
• Why should be load balanced ?
▪ Improve resource utilization
▪ Improve system performance
▪ Improve energy efficiency
Unbalanced

46. Job Scheduling
• What is job scheduler ?
▪ A job scheduler is a software application that is in charge of
unattended background executions, commonly known for historical
reasons as batch processing.
• What should be scheduled in Cloud ?
▪ Computation intensive tasks
▪ Dynamic growing and shrinking tasks
▪ Tasks with complex processing dependency
• How to approach ?
▪ Use pre-defined workflow
▪ System automatic configuration

47. Agenda
• What is Cloud Computing ?
▪ Different perspectives
▪ Properties and characteristics
▪ Benefits from cloud computing
• Service and deployment models
▪ Three service models
▪ Four deployment models

48. Let’s translate to
Cloud Computing !!

49. Service Models Overview
• What if you want to have an IT department ?
▪ Similar to build a new house in previous analogy
• You can rent some virtualized infrastructure and build up your own IT
system among those resources, which may be fully controlled.
• Technical speaking, use the Infrastructure as a Service (IaaS) solution.
▪ Similar to buy an empty house in previous analogy
• You can directly develop your IT system through one cloud platform,
and do not care about any lower level resource management.
• Technical speaking, use the Platform as a Service (PaaS) solution.
▪ Similar to live in a hotel in previous analogy
• You can directly use some existed IT system solutions, which were
provided by some cloud application service provider, without knowing
any detail technique about how these service was achieved.
• Technical speaking, use the Software as a Service (SaaS) solution.

50. Service Model Overview

51. SERVICE MODELS
Infrastructure as a Service
Platform as a Service
Software as a Service

52. Infrastructure as a Service
• Infrastructure as a Service - IaaS
▪ The capability provided to the consumer is to provision processing,
storage, networks, and other fundamental computing resources
where the consumer is able to deploy and run arbitrary software,
which can include operating systems and applications.
▪ The consumer does not manage or control the underlying cloud
infrastructure but has control over operating systems, storage,
deployed applications, and possibly limited control of select
networking components .
• Examples :
▪ Amazon EC2
▪ Eucalyputs
▪ OpenNebula
▪ … etc

53. Infrastructure as a Service
• System architecture :

54. Infrastructure as a Service
• Enabling technique - Virtualization
▪ Virtualization is an abstraction of logical resources away from
underlying physical resources.
• Virtualization technique shift OS onto hypervisor.
• Multiple OS share the physical hardware and provide different services.
• Improve utilization, availability, security and convenience.
VM1 VM2 VM3

55. Infrastructure as a Service
• Properties supported by virtualization technique :
▪ Manageability and Interoperability
▪ Availability and Reliability
▪ Scalability and Elasticity

56. Infrastructure as a Service
• Provide service –Resource Management Interface
▪ Several types of virtualized resource :
• Virtual Machine – As an IaaS provider, we should be able to provide the
basic virtual machine operations, such as creation, suspension, resumption
and termination, …etc.
• Virtual Storage – As an IaaS provider, we should be able to provide the
basic virtual storage operations, such as space allocation, space release,
data writing and data reading, …etc.
• Virtual Network – As an IaaS provider, we should be able to provide the
basic virtual network operations, such as IP address allocation, domain
name register, connection establishment and bandwidth provision, …etc.

57. Infrastructure as a Service
• Provide service – System Monitoring Interface
▪ Several types of monitoring metrics :
• Virtual Machine – As an IaaS provider, we should be able to monitor some
system states of each virtual machine, such as CPU loading, memory
utilization, IO loading and internal network loading, …etc.
• Virtual Storage – As an IaaS provider, we should be able to monitor some
storage states of each virtual storage, such as virtual space utilization,
data duplication and storage device access bandwidth, …etc.
• Virtual Network – As an IaaS provider, we should be able to monitor some
network states of each virtual network, such as virtual network
bandwidth, network connectivity and network load balancing, …etc.

58. IaaS - Summary
• IaaS is the deployment platform that abstract the infrastructure.
• IaaS enabling technique
▪ Virtualization
• Server Virtualization
• Storage Virtualization
• Network Virtualization
• IaaS provided services
▪ Resource Management Interface
▪ System Monitoring Interface

59. SERVICE MODELS
Infrastructure as a Service
Platform as a Service
Software as a Service

60. Platform as a Service
• Platform as a Service - PaaS
▪ The capability provided to the consumer is to deploy onto the cloud
infrastructure consumer-created or acquired applications created
using programming languages and tools supported by the provider.
▪ The consumer does not manage or control the underlying cloud
infrastructure including network, servers, operating systems, or
storage, but has control over the deployed applications and
possibly application hosting environment configurations.
• Examples :
▪ Microsoft Windows Azure
▪ Google App Engine
▪ Hadoop
▪ … etc

61. Platform as a Service
• System architecture :

62. Platform as a Service
• Enabling technique – Runtime Environment Design
▪ Runtime environment refers to collection of software services
available. Usually implemented by a collection of program libraries.
• Common properties in Runtime Environment :
▪ Manageability and Interoperability
▪ Performance and Optimization
▪ Availability and Reliability
▪ Scalability and Elasticity

63. Platform as a Service
• Provide service – Programming IDE
▪ Users make use of programming IDE to develop their service
among PaaS.
• This IDE should integrate the full functionalities which supported from the
underling runtime environment.
• This IDE should also provide some development tools, such as profiler,
debugger and testing environment.
▪ The programming APIs supported from runtime environment may
be various between different cloud providers, but there are still
some common operating functions.
• Computation, storage and communication resource operation

64. Platform as a Service
• Provide service – System Control Interface
▪ Police-Based Control
• Typically described as a principle or rule to guide decisions and achieve
rational outcome(s)
• Make the decision according to some requirements
▪ Workflow Control
• Describe the flow of installation and configuration of resources
• Workflow processing daemon delivers speedy and efficient construction
and management of cloud resources

65. PaaS - Summary
• PaaS is the development platform that abstract the infrastructure,
OS, and middleware to drive developer productivity.
• PaaS enabling technique
▪ Runtime Environment
• PaaS provide services
▪ Programming IDE
• Programming APIs
• Development tools
▪ System Control Interface
• Policy based approach
• Workflow based approach

66. SERVICE MODELS
Infrastructure as a Service
Platform as a Service
Software as a Service

67. Software as a Service
• Software as a Service - SaaS
▪ The capability provided to the consumer is to use the provider’s
applications running on a cloud infrastructure. The applications are
accessible from various client devices through a thin client
interface such as a web browser (e.g., web-based email).
▪ The consumer does not manage or control the underlying cloud
infrastructure including network, servers, operating systems,
storage, or even individual application capabilities, with the
possible exception of limited user-specific application
configuration settings.
• Examples :
▪ Google Apps (e.g., Gmail, Google Docs, Google sites, …etc)
▪ SalesForce.com
▪ EyeOS
▪ … etc

68. Software as a Service

69. Software as a Service
• Enabling Technique – Web Service
▪ Web 2.0 is the trend of using the full potential of the web
• Viewing the Internet as a computing platform
• Running interactive applications through a web browser
• Leveraging interconnectivity and mobility of devices
• Enhanced effectiveness with greater human participation
• Properties provided by Internet :
▪ Accessibility and Portability

70. Software as a Service
• Provide service – Web-based Applications
▪ Conventional applications should translate their access interface
onto web-based platform.
▪ Applications in different domains
• General Applications – Applications which are designed for general
propose, such as office suit, multimedia and instant message, …etc.
• Business Applications – Application which are designed for business
propose, such as ERP, CRM and market trading system, …etc.
• Scientific Applications – Application which are designed for scientific
propose, such as aerospace simulation and biochemistry simulation,
…etc.
• Government Applications – Applications which are designed for
government propose, such as national medical system and public
transportation system service, …etc.

71. Software as a Service
• Provide service – Web Portal
▪ Apart from the standard search engine feature, web portals offer
other services such as e-mail, news, stock prices, information,
databases and entertainment.
▪ Portals provide a way for enterprises to provide a consistent look
and feel with access control and procedures for multiple
applications and databases, which otherwise would have been
different entities altogether.
▪ Some examples :
• iGoogle
• MSNBC
• Netvibes
• Yahoo!

72. SaaS - Summary
• SaaS is the finished applications that you rent and customize.
• SaaS enabling technique
▪ Web Service
• SaaS provide services
▪ Web-based Applications
• General applications
• Business applications
• Scientific applications
• Government applications
▪ Web Portal

73. DEPLOYMENT MODELS
How to deploy a cloud system ?

74. Deployment Model
• There are four primary cloud deployment models :
▪ Public Cloud
▪ Private Cloud
▪ Community Cloud
▪ Hybrid Cloud
• Each can exhibit the previously discussed characteristics;
their differences lie primarily in the scope and access of
published cloud services, as they are made available to
service consumers.

75. Public Cloud
• Public cloud definition
▪ The cloud infrastructure is made available to the general public or a
large industry group and is owned by an organization selling cloud
services.
▪ Also known as external cloud or multi-tenant cloud, this model
essentially represents a cloud environment that is openly accessible.
▪ Basic characteristics :
• Homogeneous infrastructure
• Common policies
• Shared resources and multi-tenant
• Leased or rented infrastructure
• Economies of scale

76. Private Cloud
• Private cloud definition
▪ 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.
▪ Also referred to as internal cloud or on-premise cloud, a private
cloud intentionally limits access to its resources to service
consumers that belong to the same organization that owns the
cloud.
▪ Basic characteristics :
• Heterogeneous infrastructure
• Customized and tailored policies
• Dedicated resources
• In-house infrastructure
• End-to-end control

77. Public vs. Private
• Comparison :
Public Cloud Private Cloud
Infrastructure Homogeneous Heterogeneous
Policy Model Common defined Customized & Tailored
Resource Model Shared & Multi-tenant Dedicated
Cost Model Operational expenditure Capital expenditure
Economy Model Large economy of scale End-to-end control

78. Community Cloud
• Community cloud definition
▪ The cloud infrastructure is shared by several organizations and
supports a specific community that has shared concerns (e.g.,
mission, security requirements, policy, and compliance
considerations).

79. Hybrid Cloud
• Hybrid cloud definition
▪ The cloud infrastructure is a composition of two or more clouds
(private, community, or public) that remain unique entities but are
bound together by standardized or proprietary technology that
enables data and application
portability (e.g., cloud bursting
for load-balancing between
clouds).

80. Cloud Ecosystem

81. Summary
• What is cloud computing in your mind
▪ Clear or Cloudy?
• Cloud computing is a new paradigm shift of computing
• Cloud computing can provide high quality of properties
and characteristics based on essentially central ideas
• Service models and deployment models provide services
that can be used to
▪ Rent fundamental computing resources
▪ Deploy and develop customer-created applications on clouds
▪ Access provider’s applications over network (wired or wireless)