6. defining the cloud by “the book”
cloud computing is the delivery of computing as a service rather than
a product, whereby shared resources, software, and information are
provided to computers and other devices as a utility (like the electricity
grid) over a network (typically the internet)
wikipedia
7. defining the cloud by “the book”
cloud computing is the delivery of computing as a service rather than
a product, whereby shared resources, software, and information are
provided to computers and other devices as a utility (like the electricity
grid) over a network (typically the internet)
wikipedia
8. defining the cloud by “the book”
cloud computing is the delivery of computing as a service rather than
a product, whereby shared resources, software, and information are
provided to computers and other devices as a utility (like the electricity
grid) over a network (typically the internet)
wikipedia
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
NIST
9. defining the cloud by “the book”
cloud computing is the delivery of computing as a service rather than
a product, whereby shared resources, software, and information are
provided to computers and other devices as a utility (like the electricity
grid) over a network (typically the internet)
wikipedia
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
NIST
10. defining the cloud, the “purist” way
• leverage, mashup parts of history, current
definitions
– distributed computing
– single instance with replication
– uses systems management
– computing as a service
– separation into three layers
– open network
– connected and integrated
– measured by the usage, not by the user
– public, public, and public
19. debunking integration: solution a
S
P
I
S
P
I
S
P
I
S
P
I
SaaS-SaaS integration, within
the application, leveraging
the cloud
similar to existing, uses
service calls, middleware
20. debunking integration: solution b
S
P
I
S
P
I
S
P
I
S
P
IPaaS-PaaS integration,
leveraging the cloud, no need
for middleware,
easiest for elasticity (scale
out), establish once, reuse
many times as necessary
21. scalability: three sustaining pillars
design for
scalability
in the
cloud
scalability
must occur
in two
ways – up
and out
define
scalability by
Capacity
Availability
Performance
cloud scalability
the entire concept of cloud computing was conceived for scalability
sake
23. making the case for cloud computing E1
conomics
easiest part of the equation: someone else hosts hardware, software,
maintenance
anyway to look at it, remote, distributed computing is cheaper
move from CAPEX to OPEX is very attractive to managing stakeholders
cloud ROI traditionally done by comparing IT budgets to cloud expenses
#mmmkay
scalability, integration are cheaper and easier, security is still under (hot)
debate
25. making the case for cloud computing E2
lasticity
inherent to cloud architectures
makes case for scalability, high-availability, failover planning
done wrong – remember the failure of amazon EC2 and the
problems it caused
is a scale-out model in single-tenancy, multi-instance, that cannot
be tested
requires systems management for proper instance maintenance
27. making the case for cloud computing E3
nterprise application stores
mobile, social, user empowerment – all changed the game
users aren’t putting up with big, complex applications – they want “apps” on
iPad
best bet for support for all business is adoption of EAS, cloud is a must for that
model scalability, flexible interfaces, myriad device access via platform – all
part of the cloud two-to-three year trend, if you haven’t started – better get
going
29. making the case for cloud computing E4
xpansion
plans for all business units in next few years include “cloud” and SaaS
plans for IT over next three-to-four years include cloud infrastructure
integration, plans from partners, providers, suppliers, associates include cloud
in next five years
expansion of any organization must include cloud going forward, no questions
if all other fails, cite the fact that competitors are expanding into cloud
#Winning
31. making the case for cloud computing E5
volution
evolution of the world comes down to cloud, organizations have to adapt
vendors are evolving their products from hosted, on-demand to cloud
ventures with partners, other organizations will demand cloud; three-to-four
years
customers are demanding cloud –stirred up by microsoft “to the cloud” TV ads
with differentiation of what is cloud and how to deploy in it, definitely a must-
do
33. making the case for cloud computing E6
infrastructur
reports say from 10% to 30% of IT budgets put on cloud infrastructure
reports highlight more money spent by BU than IT on SaaS applications;
continuing
organizations cannot leverage the cloud as an external service only, must
integrate
to make cloud work across organization, to retain security, to enhance
integration – IT must be responsible for centralized cloud infrastructure; CEOs
are seeing this
34. issues: hosted != on-demand != cloud
• hosted: a vendor puts a web-interface to their apps
– MT (multitenancy) is a big deal here
– licensing is by the user, as usual
– reduced functionality or poor performance by comparison
• on-demand: vendors leverages SaaS, PaaS model
– web interface
– MT benefits vendor; not so much clients
– usually SaaS and PaaS “all in one” failing to leverage cloud
• cloud: three layer distributed computing model
– MT, single-instance hard to scale; ST, multi-instance better
– licensing by usage, starting, is winner model for biz
35. issues: private cloud
• short, simple, sweet
• today’s private cloud is used as a bridge between
client-server, web-based, on-demand, and SaaS
worlds to get to the real cloud infrastructure
• use if you must, you are better off planning around it
any well done definition of the cloud specifically
calls for open networks to support the cloud;
private clouds violate core tenet of cloud
36. your next steps
• define the cloud (for you)
• take charge of your existing “cloud” initiatives
–across stakeholders
–make case for central IT control
• setup 3-5 years strategy and investment
• get going, do your infrastructure while you
leverage SaaS and on demand solutions
• learn, implement, learn, implement – you get the
idea
American society of mechanical engineersNew concepts technologies, such as distributed computingUsing computers? No, but the concept was developed with views to the future
American society of mechanical engineersNew concepts technologies, such as distributed computingUsing computers? No, but the concept was developed with views to the future
1931 –Air Force invest $3MM towards understanding how distributed computing can change the world1946 – RAND defines distributed computing models1970 – IBM starts playing with models for grid computing (not like today, think shared timeshare, plus the “owned” most of the “iron)1976 – NCC the future of distributed computing systems, “future trends in distributed computing systems” mentions grid computing1984 – SUN (stanford university network) computer1991,1993 –- CORBA, COM/DCOM - Larry Elison, networking computing is nothing new – why make such a fuss?1999 – salesforce launches using SaaS model (from distributed computing fame, does not mention cloud yet – no software, hosted was their model – MT begins in earnest)2004 – eric schmidt make first reference to cloud computing since internet came about, starts craziness - 2009 – sirocco (wikipedia -
FearChange of infrastructureUpgrade cycleThree core problemsScalabilityIntegrationSecurity