Cloud computing allows for on-demand access to shared computing resources like networks, servers, storage, applications and services. It provides accessibility, agility and flexibility through rapid provisioning and releasing of resources with minimal management effort. Some key aspects of cloud computing include virtualization, multi-tenancy, broad network access, resource pooling and measured service. Cloud computing is changing the nature of IT by moving computing resources from local desktops and data centers to the internet.

1. Cloud Computing
P.Sarala M.E., (Ph.d).,
Associate Professor
Nandha Engineering College
Erode

2. 2

4. Ease of Use
Resource Sharing
Necessity
Cost Effectiveness

5. Cloud Computing
About the Cloud
Cloud Computing
The “Cloud” is the default The broader term of “Computing”
symbol of the internet in encompasses:
diagrams. - Computation
- Coordination logic
- Storage
Cloud Computing is about moving computing
from the single desktop pc/data centers to the
Aneka a Platform for internet.
Enterprise Grid/Cloud
Computing 5

6. Introduction
Cloud Computing:
Cloud computing is a pay-per-use
model for enabling available, convenient,
on-demand network access to a shared pool
of configurable computing resources (e.g.,
networks, servers, storage, applications,
services) that can be rapidly provisioned and
released with minimal management effort
or service provider interaction.

7. 7

8. 8

9. Commercial clouds

10. What is Cloud Computing
Adopted from: Effectively and Securely Using the Cloud Computing Paradigm by peter Mell, Tim Grance
10

11. IT should be able to…
 Manage hardware  Deliver value to business
 Upgrade software through innovation in IT
IT should not have to…
 Tune databases  Respond quickly to change
 Manage backups or disaster  Develop and deploy new IT
recovery systems
 Customize and integrate IT
systems
Cloud Computing is Changing
the Nature of IT
11

13. Cloud Architecture
13

14. Cloud Service Requirement
 Availability- with loss less DR
 Portability of Data & Applications
 Data Security
 Manageability
 Elasticity
 Federated System

16. Cloud Computing - The Coming Storm
Cloud Computing
Characteristics
Accessibility Agility
Service Management Flexibility
User Metering Cost Efficiency
Automation Virtualization
Cloud Computing is a model of how IT should operate as a business!
Slide 16 Cloud Computing

18. Cloud computing And
Virtualization
 Cloud computing operates with the help of virtualized
resources like some computing devices, servers and
networks.
 Virtualization deals with the creation of virtual versions
of these servers, operating systems to be used in cloud
computing, resources for networks and storage devices.
It is with the help of this virtualization are we able to
access multiple and many physical devices.
 This concept makes use of either one operating system
operating many computers to evaluate
its functionalists or a single computer that controls all
other equipment’s and machines.

19. The NIST Cloud Definition Framework
Hybrid Clouds
Deployment
Models Private Community
Public Cloud
Cloud Cloud
Service Software as a Platform as a Infrastructure as a
Models Service (SaaS) Service (PaaS) Service (IaaS)
On Demand Self-Service
Essential
Broad Network Access Rapid Elasticity
Characteristics
Resource Pooling Measured Service
Massive Scale Resilient Computing
Common Homogeneity Geographic Distribution
Characteristics Virtualization Service Orientation
Low Cost Software Advanced Security
19
Based upon original chart created by Alex Dowbor - http://ornot.wordpress.com

20. Cloud Deployment Model
NIST Deployment Models
Cloud infrastructure made available to the
Public Cloud
general public.
Cloud infrastructure operated solely for an
Private Cloud organization.
Cloud infrastructure composed of two or
Hybrid Cloud more clouds that interoperate or federate
through technology
Cloud infrastructure shared by several
Community organizations and supporting a specific
Cloud community
… and one other
Cloud services that simulate the private cloud
Virtual Private experience in public cloud infrastructure
Cloud
Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential

21. Public, Private, and Hybrid Clouds

22. Public Cloud vs. Private Cloud
Rationale for Private Cloud:
Security and privacy of business data was a big
concern
Potential for vendor lock-in
SLA’s required for real-time performance and
reliability
Cost savings of the shared model achieved
because of the multiple projects involving
semantic technologies that the company is
actively developing
6/23/2010 Wipro Chennai 2011 22

23. Why is Cloud Security Perceived as Such
a Big Problem?
Who Has Control?
Where is it located?
Where is it stored?
Who backs it up?
Who has access?
How do auditors observe?
How does our security team engaged?

24. Some ways to Hack
Fake –mailer- www.anonymizer.in/fake-
mailer/
Trojan – Remote access to victim’s
computer
SMS spoofing-www.spranked.com
Mobile phone spying-
spyphonegold,mobile spy

26. Security in Public Cloud
Hardened through continual hacking attempts
Attract the best security people available
Get the latest security gear due to economies of
scale
 IaaS- offers Virtualized Environment
 Paas- Development Environment
 SaaS- Complete Application

28. MODELS
Highly scalable internet based applications
SAAS are hosted on the cloud and offered as a
service to the end users
Platform used to design, develop, build
PAAS and test the applications are provided as a
service
Storage. Database management and
IAAS compute capabilities are offered on
demand

29. Cloud services

31. Cloud Deployment Model
NIST Deployment Models
Application Applications at Scale
(SaaS) (End users)
Platform Execution Platforms at Scale
as a Service (Developers)
Infrastructure Infrastructure at Scale
as a Service (System Administrators)
Enabling Cloud Service Delivery at Scale
Technology (Public / Private Cloud Providers)
Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential

32. Conceptual Cloud
Model
-represents concepts and relationship
between them.

33. Cloud Ecosystem
Describe the complex system of
interdependent components that work
together to enable cloud services.
Consultants, integrators, partners, third
parties

34. Cloud BPM
Low Cost. Low Risk. High Value.
Low startup costs
Fast deployment with no manual
maintenance
Predictable costs during the life of the
application
Fast return-on-investment

35. The Cloud Stack

36. The Cloud Stack– The Full
Monty
Services
Applications
Data Marketplace
Eco-System – Access – Billing – Analytics – Integration - Monitoring
Development – Framework – Database - Provisioning
Hardware – CPU Cycles – Storage - Virtualization
Hosting – Network – Real-estate - Power

37. Computing on Demand
On-demand computing is a business
computing model that allows companies
to provide access to computing resources
as they become necessary, rather than
full time.

38. Information security

39. Cloud storage
Agility
 The ability of a [system] to rapidly respond to change by adapting its
initial stable configuration
Scalability
 The system can grow without limits as demand increases
Elasticity
 Resource allocation can be increased or decreased according to the
demand
Multi-tenancy
 A principle in software architecture where a single instance of the software
runs on a server, serving multiple client organizations

40. Availability and Disaster
Recovery
more than one data center will be active
at all times and customer can access
seamlessly.
Transparent to the end user
Hadoop

41. THE PRIMARY CONCEPTS OF IAAS
BILLING AND METERING INCLUDE
Servers per hour serving an on-demand
model
Reserved servers for better planning
Higher and lower compute resource
units based on application performance
Volume-based metering on the number
of instances consumed
Prepaid and reserved infrastructure
resources
Clustered server resources

42. The primary concepts for PaaS
metering and billing include
Incoming and outgoing network
bandwidth
CPU time per hour
Stored data
High availability
Monthly service charge

43. The primary concepts for SaaS
billing and metering include
 Monthly subscription fees
 Per-user monthly fees

44. BILLING AND METERING

45. Virtualization & SOA
Many kinds: platform, network,
resource (includes storage) &
application virtualization
Generally focus on abstracting
operating systems & other
physical resources
The Service abstraction is
technically a form of virtualization,
but not in practice
Virtualization projects can
support highly available SOA
infrastructures
Copyright © 2009, ZapThink, LLC 45

46. Grid
Computing
Cloud Computing
Virtualization Utility
Virtualization
Computing

47. 47

48. What is Virtualization
 Virtualization is one of the hardware reducing,
cost saving and energy saving technology that is
rapidly transforming the IT landscape and
fundamentally changing the way that
people compute.
 With VMware virtualization solutions you
can reduce IT costs while increasing the
efficiency, utilization and flexibility of their
existing computer hardware.
 With Virtualization it is possible to run multiple
operating systems and multiple applications on
the same SERVER at the same time, increasing
the utilization and flexibility of hardware.

49. Virtual Machines
VM technology allows multiple virtual
machines to run on a single physical machine.
App App App App App
Xen
Guest OS Guest OS Guest OS
(Linux) (NetBSD) (Windows)
VMWare
VM VM VM
UML
Virtual Machine Monitor (VMM) / Hypervisor
Denali
Hardware
etc.
Performance: Para-virtualization (e.g. Xen) is very close to raw physical performance!
49

50. Virtualization Tools

51. Before Virtualization
 Single OS image per
machine
Software and hardware
tightly coupled
Running multiple
applications on same
machine often creates
conflict
Inflexible and costly
infrastructure

52. After Virtualization
 Hardware-independence of
operating system and
applications
 Virtual machines can be
provisioned to any system
 Can manage OS and
application as a single unit
by encapsulating them into
virtual Machines

53. Good
Bye~~ Hello ^^

55. Server virtualization
Server virtualization Creates multiple
isolated environments
Allows multiple OS’s and workloads to
run on the same physical hardware
Solves the problem of tight coupling
between OS’s and hardware

56. System Virtualization

58. Provisioning of Storage Resources

59. Service Oriented Architectures
Service Oriented Architectures
◦ Model for using web services
 service requestors, service registry, service providers
◦ Use of web services to compose complex, customizable,
distributed applications
◦ Encapsulate legacy applications
◦ Organize stovepiped applications into collective
integrated services
◦ Interoperability and extensibility
59

60. Cloud Computing & SOA
SaaS + virtualization delivered via loosely-coupled
Services
SOA taken to the next level?
What’s really outside the SOA box?
Cloud computing architectures are
inherently Service-oriented
Copyright © 2009, ZapThink, LLC 60

61. Cloud Computing and SOA:
Same but Different
61

62. Enabling Technologies
Cloud applications: data-intensive,
Cloud applications: data-intensive,
compute-intensive, storage-intensive
compute-intensive, storage-intensive
Bandwidth
WS
Services interface
Web-services, SOA, WS standards
VM0 VM1 VMn
Storage Virtualization: bare metal, hypervisor. …
Models: S3,
BigTable,
BlobStore, ... Multi-core architectures
64-bit
processor
6/23/2010 Wipro Chennai 2011 62

63. Cloud Infrastructure as a Service (IaaS)
(DaaS & HaaS)
◦ Rent processing, storage, network capacity,
memory and other fundamental computing
resources
◦ Virtualisation
◦ billing,
◦ SLA
◦ Amazon EC2 and S3,…
◦ Open Nebula, Eucalyptus,…

64. Software-as-a-Service & SOA
 Software deployment over the Internet
 Traditionally delivered via a browser
interface
 Increasingly delivered via Web Services
interface as well
 SaaS is Service-oriented when Services
are Business Services that support
business processes via metadata-driven
The CRM is particularly good this evening.
composition
Location independence taken to its
natural conclusion!
Copyright © 2009, ZapThink, LLC 64

65. How can SOA help?
 Driving standards. Similar to the http force that made the
web usable, XML, WS security and UDDI are enabling
discovery, profiling and binding
 Reduced fixed costs by service rationalization
 Increased transactional capability by virtualization
 Increased flexibility to switch interfaces. More contact based
than asset based.
 Reduced time to market by leveraging on existing
applications esp. in the Software as a Service mode
 Synergizes IT and business
 Creates
opportunities to work on strategy and
communication inside the organization

66. SOA - Perspectives

67. SOA Usage & Supporting Platforms
 SOA Usage
◦ B2B
◦ Enterprise Application Integration (EAI)
◦ Application to Application
◦ Government
 Major Players in SOA Space
◦ IBM: WebSphere SOA Product Suite
◦ BEA: Aqualogic (WebLogic)
◦ Oracle: Fusion Middleware
◦ Microsoft: .NET ©C
aye
◦ SAP: NetWeaver tan
o
Tec
hno
Source: H. Taylor, “Service-Oriented Architecture (SOA) 101 ‘What’s Hype, What’s Real?’“, Juniper Networks, Inc.,2007. logy
Gro
up-
68

68. SOA: All Hype?
 In a profound sense, the industry hype about SOA is actually
true.
◦ It does work
◦ It is being used in major deployments
◦ It does cut costs and enable agility
◦ It’s an incremental shift that is possible to adopt without scrapping
earlier IT efforts
©C
aye
tan
o
Tec
hno
Source: H. Taylor, “Service-Oriented Architecture (SOA) 101 ‘What’s Hype, What’s Real?’“, Juniper Networks, Inc.,2007. logy
Gro
up-
69

69. SOA Is Not a Silver Bullet
 Assumes costs and challenges inherent in reuse
 SOA does not make politics go away
 Your IT organization still has to master it
 Governance is a major challenge
 Security can be a big issue
 Vendors may not necessarily cooperate in an effort that commoditizes their
products
 Vendors may be embedded in your organization, rendering some of the
theoretical benefits of SOA moot
 Getting started with SOA may require longer and more expensive project
cycles the first time around ©C
◦ Need high reuse potential & reuse aptitude aye
tan
 Some SOA standards are still immature, leading to confusion and vendor- o
driven proprietary creep Tec
hno
Source: H. Taylor, “Service-Oriented Architecture (SOA) 101 ‘What’s Hype, What’s Real?’“, Juniper Networks, Inc.,2007. logy
Gro
up-
70

70. Benefits & Limitations of SOA
 Benefits
◦ Flexibility in new software design
◦ Reuse of business components in networks
◦ Interoperability and integration capability
◦ Ease of assembling new business processes
 Limits and Open Issues
◦ Not a universal remedy for today’s mix and match architectures
◦ It is not a solution for all upcoming challenges
◦ Not best practice for long-running asynchronous processes
◦ Natural strengths in real-time request-response exchanges (asynchronous and
synchronous) ©C
◦ SOA requires an environmental framework aye
tan
 .NET, SAP NetWeaver, IBM WebSphere, BEA WebLogic o
 Platform independence not yet achieved Tec
hno
logy
Gro
up-
71

71. Benefits & Limitations of SOA Cont’d
 Limits and Open Issues Cont’d
◦ Most critical issues are pending security issues
 Physical Network
 Need Intra- and Inter-organizational security
 SOAP Messages
 Need to protect content of SOAP Messages
 Endpoint (Web Service) Security
 Need Intra- and Inter-organizational security
 Extensive security framework worked out
 Applicable products on the market
 For mission critical processes, security measures still an issue
◦ Not valuable for applications whose business logic components are in a closed
©C
application domain aye
◦ Not valuable if there is no intention for reuse tan
o
Tec
hno
logy
Gro
up-
72

72. SaaS Maturity Model
Level 1: Ad-Hoc/Custom –
One Instance per customer
Level 2: Configurable per
customer
Level 3: configurable &
Multi-Tenant-Efficient
Level 4: Scalable, Configurable
& Multi-Tenant-Efficient
73 Source: Frederick Chong and Gianpaolo Carraro, “Architectures Strategies for Catching the Long Tail”

73. Enterprise Software Revolution
Software as a Service (SaaS)
SaaS is hosting applications on the Internet as
a service (both consumer and enterprise)
Jon Williams, CTO of Kaplan Test Prep on
SaaS
◦ “I love the fact that I don't need to deal with servers,
staging, version maintenance, security, performance”
Eric Knorr with Computerworld says that
“[there is an] increasing desperation on the
part of IT to minimize application deployment
and maintenance hassles”
74

74. Where Software as a service and
“packages” fit in
Business Differentiator
Function or geo 1
Best people
Business Unit Support need to focus
here
Function 2
Industry wide Standard
Business Differentiator
Business Unit Support
Function 3
Industry wide Standard
Ideal candidates
to consolidate Business Differentiator
or for
Software as a Business Unit Support
service
Industry wide Standard

75. The Technical View of Cloud
Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential

76. Software as a Service (SaaS)
SaaS is a model of software deployment where an
application is hosted as a service provided to
customers across the Internet.
Saas alleviates the burden of software
maintenance/support
◦ but users relinquish control over software versions and
requirements.
Terms that are used in this sphere include
◦ Platform as a Service (PaaS) and
◦ Infrastructure as a Service (IaaS)
77

77. Platform-as-a-Service (PaaS)
Definition
– Platform providing all the facilities necessary to
support the complete process of building and
delivering web applications and services, all available
over the Internet
– Entirely virtualized platform that includes one or
more servers, operating systems and specific
applications
78

78. Infrastructure-as-a-Service (IaaS)
Definition
– Provision model in which an organization
outsources
the equipment used to support operations,
including
storage, hardware, servers and networking
components.
– Also known as Hardware as a Service (HaaS).
– Service provider owns the equipment;
responsible for housing, running and maintaining
it.
– Client typically pays on a per-use basis.
79

79. e-Business Architecture for B2B
 1 External Provider, 2 Enterprises: A & B
 Enterprise B Purchasing accesses
Enterprise A’s Inventory Web Service
 Both enterprises access an
authentication Web service provided by
an external provider
 Enterprises A & B separately access Web
services that provide Payment and
Logistics Web Services
©C
aye
tan
o
Tec
Source: Mobility, Security and Web Services: Technologies and hno
Service-Oriented Architectures for a new Era of IT Solutions by Gerhard Wiehler, p. 101. logy
Gro
up-
80

81. The Consumer’s View of Cloud
...Everything is Cloud
Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential

82. RESEARCH ISSUES
Cloud Computing or Cloudy Computing
A maz
on E
Virt QoS
Amazo
ualiz SaaS C2
ati o IaaS
n
PaaS
n S3
Storage g
Billing Pricin
s
vi ce
Reso er
W are l
u rce M e bS
VM e et er
Hy
pe Lev t i ng W
ce men
rv
is o rvi ee Utility
rs Se gr Provisionin
g
A on Demand Computing
rity Man
Publ Secu jraso
ic Clo ft An
ud eka
Web 2.0
Privacy Uhm, I am not quite
Private Clo clear…Yet another
ud
pr ise Goo
En t er u d gle A
ppE
buzzword..?
Clo m ngin
.co e
Fo rce
Sa les Mosso
83