cloud 101
DESCRIPTION
Slides from the Cloud 101 workshop at Gov 2.0 in Washington, DC on May 25, 2010TRANSCRIPT
Clouds 101Understanding the state of cloud computing
Wednesday, May 26, 2010
http://www.flickr.com/photos/jamesjordan/2751393381/Wednesday, May 26, 2010
Cloud computing is an approach to computing that’s more flexible and lets organizations focus on their core business by insulating them from much of the underlying IT work.
http://www.flickr.com/photos/juniorvelo/3577399832/Wednesday, May 26, 2010
At its most basic, it’s computing as a utility – pay for what you need, when you need it, rather than paying for it all up front.
Wednesday, May 26, 2010
This is what Nicolas Carr talked about in his book The Big Switch.
Wednesday, May 26, 2010
But clouds can be confusing. Part of the reason is that they’re a big deal, which means everyone wants to be a part of them – even companies who have nothing to do with clouds.
http://www.flickr.com/photos/creative_tools/4339787963/http://www.flickr.com/photos/dnorman/168643407/
Wednesday, May 26, 2010
I’m going to try and clear some of this up for you.
Part one:Disruption and the democratization of IT
Wednesday, May 26, 2010
http://www.flickr.com/photos/horiavarlan/4290549806/Wednesday, May 26, 2010
First, let’s talk about disruption.
http://www.flickr.com/photos/harshlight/3235469361Wednesday, May 26, 2010
Once, IT was a monopoly.
http://www.flickr.com/photos/theclevelandkid24/4251408727/Wednesday, May 26, 2010
Today, it’s a free market. The line of business has tremendous choice in what it owns, runs, and uses.
http://www.flickr.com/photos/hyku/2039448524/Wednesday, May 26, 2010
The boardroom loves this: instead of managing machines, they manage services.
http://www.flickr.com/photos/ukanda/4455286483/Wednesday, May 26, 2010
But enterprise IT doesn’t like it much, because it forces them to compete, and puts them side-by-side with organizations that spend their entire day doing detailed usage and billing.
http://en.wikipedia.org/wiki/Adam_SmithWednesday, May 26, 2010
It’s not all bad, though. There’s a lot to be learned from a transition from monopoly to a free market.
Two reasons.
Wednesday, May 26, 2010
There were a couple of reasons IT was a monopoly for so long.
http
://w
ww
.flic
kr.c
om/p
hoto
s/br
ewbo
oks/
3319
7303
27/
(16MB)Wednesday, May 26, 2010
First, the machines were expensive. That meant they were a scarce resource, and someone had to control what we could do with them.
http
://w
ww
.flic
kr.c
om/p
hoto
s/ar
gonn
e/45
6339
4851
/
Wednesday, May 26, 2010
Second, they were complicated. It took a very strange sect of experts to understand them. AVIDAC, Argonne's first digital computer, began operation in January 1953. It was built by the Physics Division for $250,000. Pictured is pioneer Argonne computer scientist Jean F. Hall.
AVIDAC stands for "Argonne Version of the Institute's Digital Automatic Computer" and was based on the IAS architecture developed by John von Neumann.
http://www.flickr.com/photos/ebeam/3586287989/Wednesday, May 26, 2010
This was also a result of scarcity. When computers and humans interact, they need to meet each other halfway. But it takes a lot of computing power to make something that’s easy to use;
http://www.flickr.com/photos/ecastro/3053916892/Wednesday, May 26, 2010
in the early days of computing, humans were cheap and machines weren’t
http://www.flickr.com/photos/binaryape/458758810/Wednesday, May 26, 2010
So we used punched cards,
http://50ans.imag.fr/images/galerie/Source/IBM-1130-1.jpgWednesday, May 26, 2010
and switches,
http
://h
oney
net.o
nofri
.org
/sca
ns/s
can2
2/so
l/sub
mis
sion
/rev
erse
.jpg
Wednesday, May 26, 2010
and esoteric programming languages like assembler.
http://www.flickr.com/photos/flem007_uk/4211743886/Wednesday, May 26, 2010
Think about what a monopoly means.
http
://w
ww
.flic
kr.c
om/p
hoto
s/ca
vem
an_9
2223
/353
1128
799/
Wednesday, May 26, 2010
A monopoly was once awarded for a big project beyond the scope of any one organization, but needed for the public good.
http://www.flickr.com/photos/athomeinscottsdale/2850893998/Wednesday, May 26, 2010
Sometimes, nobody wants the monopoly—like building the roads.
Wednesday, May 26, 2010
For the most part, governments have a monopoly on roadwork, because it’s something we need, but the benefits are hard to quantify or charge back for.
http://www.flickr.com/photos/leokoivulehto/2257818167/Wednesday, May 26, 2010
(IT’s been handed many of these thankless tasks over the years, and the business has never complained.)
http://www.flickr.com/photos/crobj/4148482980/Wednesday, May 26, 2010
The only time we can charge back for roads are when the resource is specific and billable: a toll highway, a bridge.
http://en.wikipedia.org/wiki/File:Bell_System_hires_1900_logo.PNG
Wednesday, May 26, 2010
Sometimes, we form a company with a monopoly, or allow one to operate, in order to build something or allow an inventor to recoup investment. This is how we got the telephone system, or railways.
For much of its history, AT&T and its Bell System functioned as a legally sanctioned, regulated monopoly.
The US accepted this principle, initially in a 1913 agreement known as the Kingsbury Commitment.
Anti-trust suit filed in 1949 led in 1956 to a consent decree whereby AT&T agreed to restrict its activities to the regulated business of the national telephone system and government work.
Changes in telecommunications led to a U.S. government antitrust suit in 1974.
In 1982 when AT&T agreed to divest itself of the wholly owned Bell operating companies that provided local exchange service.
In 1984 Bell was dead. In its place was a new AT&T and seven regional Bell operating companies (collectively, the RBOCs.)
http://www.corp.att.com/history/history3.htmlWednesday, May 26, 2010
When monopolies are created with a specific purpose, that’s good. But when they start to stagnate and restrict competition, we break them apart.
http://www.flickr.com/photos/ktylerconk/4096965228/Wednesday, May 26, 2010
In fact, there’s a lot of antitrust regulation that prevents companies from controlling too much of something because they can stifle innovation and charge whatever they want. That’s one of the things the DOJ does.
First: Monopoly good.
Wednesday, May 26, 2010
In other words, early on monopolies are good because they let us undertake hugely beneficial, but largely unbillable, tasks.
Then: Monopoly bad.
Wednesday, May 26, 2010
Later, however, they’re bad because they reduce the level of creativity and experimentation.
http://www.flickr.com/photos/wikidave/2867257631/
Wednesday, May 26, 2010
Today, computing is cheap. We can buy many times the compute power of the Apollo missions with a swipe of a credit card.
http://www.flickr.com/photos/mbrubeck/4460320021/
Wednesday, May 26, 2010
It’s also not complicated. Everyone can use a computer. Because today, the computer is cheap and the human’s expensive we spend so much time on user interfaces, from GUIs to augmented reality to touchscreens to voice control to geopresence.
http://www.flickr.com/photos/raneko/4203965136/Wednesday, May 26, 2010
What used to take a long time to procure, configure, and deploy is now a mouseclick.
http
://w
ww
.flic
kr.c
om/p
hoto
s/19
6464
81@
N06
/426
3667
827/
Wednesday, May 26, 2010
The way data centers are designed must reflect this shift from IT-as-a-monopoly to IT-as-an-enabler
http://www.flickr.com/photos/seier/3349428961/Wednesday, May 26, 2010
That means building a set of platforms that can adapt and adjust:
http
://w
ww
.flic
kr.c
om/p
hoto
s/ju
lia_m
anze
rova
/932
0555
26/
Wednesday, May 26, 2010
From rack-and-stack servers to click-and-drag deployment
http://www.flickr.com/photos/webtreatsetc/4323914169
Wednesday, May 26, 2010
From underused bare metal to on-demand virtual machines
http://www.flickr.com/photos/reservasdecoches/3199872487/Wednesday, May 26, 2010
From procurement and process to self-service and quick decommissioning.
http://www.flickr.com/photos/flem007_uk/4211743434/
Wednesday, May 26, 2010
The lesson of monopolies is an important one. When a monopoly set out to build a railroad, it didn’t spend a lot of time asking potential travelers what they wanted.
http://ww
w.flickr.com
/photos/dok1/4547024596/
Wednesday, May 26, 2010
When you’re building something huge and expensive, you build what you want, and expect people to be grateful for it.
http://www.flickr.com/photos/mmbrown/3102707594/Wednesday, May 26, 2010
But today’s IT user is driving IT requirements.
Wednesday, May 26, 2010
They can shop around—choosing SaaS, clouds, and internal IT according to their business requirements.
http://www.codeproject.com/KB/miscctrl/ScriptStudio.aspx Wufoo.com
Wednesday, May 26, 2010
They’re increasingly able to build the applications themselves, but expect IT to deliver smooth, fast platforms on which to experiment.
http://www.flickr.com/photos/commensa/4027055357Wednesday, May 26, 2010
As the line of business looks more and more like a consumer in a competitive market—and less and less like a grateful customer of a monopoly—IT has to change its offerings.
HARDWARE
PLATFORMS
APPS
USERS
Wednesday, May 26, 2010
It’s an inversion of the traditional IT “pyramid”, where the hardware dictates the platforms, which in turn dictates, the apps, which dictates what users can do.
HARDWARE
PLATFORMS
APPS
USERS
Wednesday, May 26, 2010
Today, what users want to do drives the apps they use, which drives the platforms and the hardware.
http://www.flickr.com/photos/scriptingnews/3471500626/Wednesday, May 26, 2010
We’ve had big changes since that time. The first was client-server computing: the idea that not everything lived in a mainframe, and some things worked well on the desktop. Software like Visicalc—the first spreadsheet—were useful for businesses, even those who couldn’t afford a mainframe.
http://en.wikipedia.org/wiki/File:NCSA_Mosaic.PNGWednesday, May 26, 2010
A second big change was the Web. This browser-based model made computing accessible to the masses. As a result, it became part of society, and everyone knew how to work it. These days, you don’t have to teach a new hire how to use a web browser: they know what links do; what the back button is; and so on.
!"#$%%&&&'()*+,'*-.%#!-/-0%#)1234566)*/%789:;7<=>%?Wednesday, May 26, 2010
A third change is the move to mobility. This has been bigger overseas, where the mobile phone is the dominant way of accessing the Internet, but it’s still a shift to the always-connected, always-on lifestyles we lead today.
http://img.dailymail.co.uk/i/pix/2008/04_01/tornadoDM3030a_800x533.jpgWednesday, May 26, 2010
And now there’s cloud computing. Clouds are as big a shift as client-server, or the web browser, or mobility.
Part two:A history of virtualization.
Wednesday, May 26, 2010
http://www.flickr.com/photos/mynameisharsha/4092086880/Wednesday, May 26, 2010
The step-‐func-on nature of dedicated machines doesn’t distribute workload very efficiently.
http
://w
ww
.flic
kr.c
om/p
hoto
s/h4
ck/2
4135
6210
8/
Wednesday, May 26, 2010
Virtualization lets us put many workloads on a single machine
http://www.flickr.com/photos/stawarz/3538910787/Wednesday, May 26, 2010
Once workloads are virtualized, several things happen. First, they’re portable
http://www.flickr.com/photos/swimparallel/3391592144/Wednesday, May 26, 2010
Second, they’re ephemeral. That is, they’re short-‐lived: Once people realize that they don’t have to hoard machines, they spin them up and down a lot more.
http://www.flickr.com/photos/genewolf/147722350Wednesday, May 26, 2010Which inevitably leads to automa3on and scrip3ng: We need to spin up and down machines, and move them from place to place. This is hard, error-‐prone work for humans, but perfect for automa3on now that rack-‐and-‐stack has been replaced by point-‐and-‐click
http://www.flickr.com/photos/pinkmoose/3278324276/Wednesday, May 26, 2010
Automa-on, once in place, can have a front end put on it. That leads to self service.
“Cloudy” tech.Wednesday, May 26, 2010
These are the founda-ons on which new IT is being built. Taken together, they’re a big part of the movement towards cloud compu-ng, whether that’s in house or on-‐demand.
Virtualization divorces the app from the machine.
Physicalmachine
Physicalmachine
Physicalmachine
Physicalmachine
Physicalmachine
Physicalmachine
Virtual machine
One on many
Physical machine
Virtual machine
Virtual machine
Virtual machine
Virtual machine
Virtual machine
Virtual machine
Many on one(or)
Wednesday, May 26, 2010
Okay, so these things mean we have applications that run “virtually” – that is, they’re divorced from the underlying hardware. One machine can do ten things; ten machines can do one thing.
That’s the technical definition
Virtualization
Automation
Self-service
Elasticity
Usage tracking & billing
Service-oriented article
Wednesday, May 26, 2010
This is the “technical” definition of cloud computing: virtualized, automated, self-service computing resources. Some people call this a “private cloud”; others think it’s just IT-done-right. Whatever the case, data centers are furiously retooling themselves, much to the enjoyment of companies like VMWare and Citrix.
Part three:Stacks and the separation of concerns.
Wednesday, May 26, 2010
Part three: Stacks and the separation of concerns
http://www.flickr.com/photos/mac-ash/4534203626/Wednesday, May 26, 2010
At its most simple, this is all about a “stack” of services. Stacks are a common idea in computing and networking. Basically, they’re a separation of different tasks.
http://www.flickr.com/photos/easternblot/126112823/Wednesday, May 26, 2010
We’re familiar with the idea of a stack. There’s a stack in the postal service.
Your virtual platform
Their physical infrastructure
Laye
r of
sep
arat
ion
Wednesday, May 26, 2010
You worry about the address, and the stamp. The postal service handles the rest—it doesn’t care what’s inside your envelope; and you don’t care what route your letter takes to its destination, as long as it gets there.
Part four:Clouds as a business model.
Wednesday, May 26, 2010
http://www.flickr.com/photos/37244380@N00/3367107195/Wednesday, May 26, 2010
But wait -- there’s more! There’s another way to look at cloud computing.
This has all been DIY.
Wednesday, May 26, 2010
Notice that so far, nothing I’ve said about clouds implies you can’t just run your own. Up until now, they’ve been DIY.
Cloudsare abusinessmodel.
Wednesday, May 26, 2010
This is the clouds-as-a-business-model definition. In this, cloud computing is a third-party service.
http://www.flickr.com/photos/laenulfean/479831551/Wednesday, May 26, 2010
All of the things we’ve seen about cloud technology make it possible to deliver computing as a utility -- computing on tap.The virtualization provides a blood/brain barrier between the application the user is running, and the machines on which it runs.
Wednesday, May 26, 2010
That means you can focus on the thing your business does that makes you special
Wednesday, May 26, 2010
And stop worrying about many of the tasks you really didn’t want to do anyway.
http://www.oncloudcomputing.com/en/2009/07/fronde-back-to-profit-by-cloud-computing/Wednesday, May 26, 2010
Sharing and economies of scale keep costs down. Cloud providers are poised to make the most of these economies of scale. Consider that in July 2008, Microsoft revealed that it had 96,000 servers at the Quincy facility, consuming "about 11 megawatts"More than 80% dedicated to Microsoft's Live Search and the remaining for HotmailIn August, a really good discovery was posted to a blog called "istartedsomething.com": a screen shot of a software dashboard that illustrates power consumption and server count at each of Microsoft's fifteen data centers, caught in a Microsoft video posted to their web site.
Idle capacity, lack of
automation, etc.
Ping, power, pipe,
efficiencies
IT server costs
Private cloud costs Public
cloud costs
Wednesday, May 26, 2010
The move towards the cloud business model has a lot to do with the economies of scale that exist when you can concentrate infrastructure, and put it near dams. (There’s a good—if hotly debated argument—that clouds-as-a-business-model are inevitable, because of the economics.)
Wednesday, May 26, 2010
Cloud providers are thinking at a scale that nearly every enterprise can’t compete with. That’s because operating efficiency, and accounting for everything, are core to their business; whereas making widgets is core to yours.
Wednesday, May 26, 2010
Self-service means customers can deploy and destroy their own machines.
Dedicatedhardware
On-premiseprivate clouds
Virtualprivate clouds
Third-partypublic clouds
Wednesday, May 26, 2010
So while you can build an automated, self-service, on-demand private cloud, there are also many public options (is that a bad word in DC? )
http://www.flickr.com/photos/carbonnyc/2294144289/Wednesday, May 26, 2010
Most of the time, when you hear someone say they’re concerned about the security of cloud computing, they’re talking about public clouds, and the issues that come with putting your data somewhere virtually but not knowing where it is physically.
Part five:Kinds of clouds.
Wednesday, May 26, 2010
http://www.eo.ucar.edu/webweather/cloud3.htmlWednesday, May 26, 2010
So far, while I’ve told you a lot about clouds, I haven’t really told you what they are. That’s partly because there are many kinds of cloud computing.We can separate clouds into three distinct groups.
Infrastructure as a ServiceAmazon EC2, Rackspace Cloud, Terremark, Gogrid, Joyent (and nearly every private cloud built on Zenserver or VMWare.)
Wednesday, May 26, 2010
The first is called Infrastructure as a Service, because you’re renting pieces of (virtual) infrastructure.
http://aws.amazon.com/ec2/pricing/Wednesday, May 26, 2010
This is what IT people think of when you say “clouds” – virtual machines I can use for just an hour. Here’s Amazon’s “menu” of machines.
•60 seconds per page
•200 machine instances
•1,407 hours of virtual machine time
•Searchable database available 26 hours later
•$144.62 total cost
Desktop EC2
Pages 17,481 17,481
Minutes/page 1 1
# of machines 1 200
Total minutes 17,481
Total hours 291.4 26.0
Total days 12.1 1.1
Wednesday, May 26, 2010
A great example of these clouds in action is what the Washington Post did with Hillarly Clinton’s diaries during her campaign. They needed to get all 17,481 pages of Hillary Clinton’s White House schedule scanned and searchable quickly. Using 200 machines, the Post was able to get the data to reporters in only 26 hours. In fact, the experiment is even more compelling: Desktop OCR took about 30 minutes per page to properly scan, read, resize, and format each page – which means that it would have taken nearly a year, and cost $123 in power, to do the work on a single machine.
Web server
Machine instance
MachineImage
Wednesday, May 26, 2010
In an IaaS model, you’re getting computers as a utility. The unit of the transaction is a virtual machine. It’s still up to you to install an operating system, and software, or at least to choose it from a list. You don’t really have a machine -- you have an image of one, and when you stop the machine, it vanishes.
App Server
Machine instance
Web server
Machine instance
DBserver
Machine instance
Storage
MachineImage
MachineImage
MachineImage
Wednesday, May 26, 2010
Most applications consist of several machines -- web, app, and database, for example. Each is created from an image, and some, like databases, may use other services from the cloud to store and retrieve data from a disk
App Server
Machine instance
Web server
Machine instance
DBserver
Machine instance
StorageDB
server
Biggermachineinstance
Wednesday, May 26, 2010
If you run out of capacity, you can upgrade to a bigger machine (which is called “scaling vertically.”)
App Server
Machine instance
Web server
Machine instance
DBserver
Machine instance
Storage
App Server
Machine instance
Web server
Machine instance
DBserver
Machine instance
LoadbalancerMachine instance
Wednesday, May 26, 2010
Or you can create several machines at each tier, and use a load balancer to share traffic between them. These kinds of scalable, redundant architectures are common -- nay, recommended -- in a cloud computing world where everything is uncertain.
Platform as a ServiceGoogle App Engine, Salesforce Force.com, Rackspace Cloud Sites, Joyent Smart Platform, (and nearly every enterprise mainframe.)
Wednesday, May 26, 2010
The second kind of cloud is called Platform as a Service. In this model, you don’t think about the individual machines—instead, you just copy your code to a cloud, and run it. You never see the machines. In a PaaS cloud, things are very different.
Processing platformData API
Storage
Yourcode
Others’code
Others’code
Others’code
Others’code
Others’code
Auth API
Userdatabase
Image API
Image functions
Blob API
Big objects
...
Governor Console Schedule
Shared components
Wednesday, May 26, 2010
- You write your code; often it needs some customization.- That code runs on a share processing platform- Along with other people’s code- The code calls certain functions to do things like authenticate a user, handle a payment, store an object, or move something to a CDN- To keep everything running smoothly (and bill you) the platform has a scheduler (figuring out what to do next) and a governor (ensuring one program doesn’t use up all the resources) as well as a console.
http://code.google.com/appengine/articles/load_test_screenshot.jpgWednesday, May 26, 2010
Here’s a shot of some code running in Google App Engine. I only know that I’m paying by CPU-hour, or for units like bandwidth, email, or storage. This could be one machine whose CPU was used 8%, or a hundred, or a thousand. I don’t know.
http://code.google.com/appengine/articles/logs_admin.pngWednesday, May 26, 2010
I can see the logs for my application. But these aren’t for a single machine -- they’re for the application itself, everywhere.
http://googleappengine.blogspot.com/2010/03/easy-performance-profiling-with.htmlWednesday, May 26, 2010
I can even find out what parts of my code are consuming the most CPU, across all machines.
Wednesday, May 26, 2010
And even their latency when served to people.
http://ww
w.com
puterhok.nl/JSP
Wiki/attach/G
oogleAppE
ngine/GA
EQ
uota.png
Wednesday, May 26, 2010
It’s a true, pure utility because you pay for what you use.
http://www.flickr.com/photos/olitaillon/3354855989/Wednesday, May 26, 2010
This is a very different model from IaaS. On the one hand, it’s more liberating, because you don’t have to worry about managing the machines. On the other hand, it’s more restrictive, because you can only do what the PaaS lets you.
IaaS and PaaS differences
IaaS
Any operating system you want
Limited by capacity of virtual machine
Scale by adding more machines
Many storage options (file system, object, key-value)
PaaS
Use only selected languages and built-in APIs
Limited by governors to avoid overloading
Scaling is automatic
Use built-in storage (Bigtable, etc.)
Wednesday, May 26, 2010
In the case of Google’s App Engine, you have to use their functions and store things in the way they want you to. You get great performance from doing so, but it probably means rewriting your code a bit.
Quota LimitApps per developer 10Time per request 30sBlobstore (total file size) 1GBMaximum HTTP response size 10MBDatastore item size 1MBApplication code size 150MB
Emails per day 1,500Bandwidth in per day 1 GBBandwidth out per day 1GBCPU time per day 6.5hHTTP requests per day 1,300,000Datastore API calls per day 10,000,000URLFetch API calls per day 657,084
Governor(usage cap)
Daily cap(free quota)
http://en.wikipedia.org/wiki/Google_App_EngineWednesday, May 26, 2010
PaaS platforms impose usage caps and billing tiers. Here’s Google App Engine’s set of quotas and free caps.
http://wiki.developerforce.com/index.php/Apex_Code:_The_World%27s_First_On-Demand_Programming_LanguageWednesday, May 26, 2010
In the case of Salesforce’s Force.com, you have to use an entirely new programming language, called Apex.
Wednesday, May 26, 2010
The third kind of cloud is called Software as a Service, or SaaS. Some people argue that this isn’t a cloud at all, just a new way of delivering software. But it’s also what the masses—the non-technologists—think cloud computing means.
Cloud Web= Internet= Useless=
My mom’s definition
Wednesday, May 26, 2010
(Personally, I think this makes the term “cloud” synonymous with “web” or “Internet”, and therefore a bit useless.)
Wednesday, May 26, 2010
SaaS and PaaS are blurring, too, with the advent of scripting languages. Nobody would argue that Google Apps is a SaaS offering; but now that you can write code for it -- as in this example of a script that sends custom driving directions to everyone in a spreadsheet -- the distinction is less and less clear.
Wednesday, May 26, 2010
But the business model of SaaS is the same as PaaS and IaaS: Sell IT on demand, rather than as software or machines.
Wednesday, May 26, 2010
It’s the form of cloud computing that gets the most lip service in areas like government, particularly with Google Apps.
Part six:It’s all a blend, really.
Wednesday, May 26, 2010
Service What it doesElastic Compute Cloud Virtual machines, by the hourElastic Mapreduce Massively parallel data processingVirtual Private Cloud On demand machines within internal ITElastic Load Balancing Traffic distributionCloudfront Content delivery accelerationFlexible Payments Service Funds transfer & paymentsSimpleDB Realtime structured data queriesSimple Storage Service Eleven nines redundant storageRelational Database Service On-demand RDBMSElastic Block Store Block-level storage (file system)Fulfillment Web Service Merchant delivery systemSimple Queue Service On-demand message busSimple Notification Service System for sending mass notificationsCloudwatch Monitoring of cloud resourcesMechanical turk Humans as an API
Wednesday, May 26, 2010
This division between PaaS and IaaS is a bit of a fiction. In fact, virtual machines are just one of around twenty “cloud services” Amazon offers – called EC2.
Service What it does
App Engine Executing Python or Java code
Bigtable datastore Store data for very fast retrieval
Calendar Data API Create and modify events
Inbox feed API Read a GMail inbox
Contact data API Interact with someone’s GMail contacts
Documents list API Manage a user’s Google Docs
OpenID single signon Use Google authentication to sign in
Secure data connector Link Google Apps to enterprise apps
Memcache Fast front-end for data
Image manipulation Resize, rotate, crop & flip images
Task queue Queue and dispatch tasks to code
Blobstore Serve large objects to visitors
Wednesday, May 26, 2010
The same is true of App Engine - though these are functions called from code, rather than services you pay for separately, they’re still more than just the code.
Cloudsaren’tjustvirtualmachines.
Wednesday, May 26, 2010
This is a really important concept: Clouds aren’t just virtual machines. Clouds are on-demand computing services.
http://www.flickr.com/photos/gezellig-girl/4351078755/Wednesday, May 26, 2010
To understand this, we need to talk for a minute about “composed designs.”
Storage media
Computer hardware
Operating system
Software
Query languageLet’s just call
this a database, ‘mmkay?
Wednesday, May 26, 2010
When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
Wednesday, May 26, 2010
There are other examples of “composed designs” in IT, many of them made from several components. For instance, consider the “message bus.” This is a thing you put messages into, and anyone who wants them can grab a copy of the message. Stock exchanges use publish-and-subscribe message busses to move data around.
http
://c
ouch
db.a
pach
e.or
g/
Wednesday, May 26, 2010
A third example is called a key-value data store. In this case, I put in a key (say, ”username”) and a value (say, “Palin”). Then it’s stored for me. It’s much less fancy than a database, but also much faster and more scalable, and can be backed up more easily so it’s more reliable.
http://www.flickr.com/photos/jackol/133765382/Wednesday, May 26, 2010
When architects want to build an application today, they don’t do so by building everything from scratch. Today’s applications are built on the shoulders of giants—message busses, data stores, authentication systems, payment tools, content delivery networks, and so on.
Wednesday, May 26, 2010
As a result, cloud providers offer a variety of these services. Rackspace has a storage product called Jungledisk; Amazon has S3. The machines that Rackspace or Amazon offer “chew” on data from these storage services.
http://aws.typepad.com/files/JBH_Architecture_Large.pngWednesday, May 26, 2010
If you equate cloud computing with just virtual machines, you’re missing the real point. Clouds applications are built from composed designs, and one of the components happens to be virtual machines.
Managedhosting
Virtualization
Private Public
SaaS
PaaS PaaS
IaaS IaaS
If you want to
talk clouds,
pick one first.
Wednesday, May 26, 2010
So let’s put this in perspective: There are public and private cloud models. Private ones are about the technology; public ones are about the business of outsourcing at scale.And there are Infrastructure, Platform, and Software offerings—IaaS, PaaS, and SaaS.If someone wants to have a conversation with me about clouds, they need to pick a tier, and a private or public model. Then we can compare facts.
Private Public
SaaS
PaaS
IaaS
Security fears
Lock-in concerns
Long-term cost
inefficiencies
High cost of maintaining & scaling machines
Wednesday, May 26, 2010
Just knowing these two dimensions makes you smarter than nearly everyone in IT right now. And when you’re discussing IT, insist that others are specific about what they mean. Discussions around privacy and security are vital to public clouds, but most people don’t consider security different in private clouds. Similarly, lock-in is a real concern in PaaS but negligible in IaaS.
Part seven:The ecosystem
Wednesday, May 26, 2010
Wednesday, May 26, 2010
Lots of people want to move into this space. Some are e-commerce giants (like Amazon) who know how to run many machines well.
Wednesday, May 26, 2010
Some are software companies with legions of developers (like Microsoft) who want to move from software licenses to recurring revenues.
Wednesday, May 26, 2010
Some are managed hosting companies (like Rackspace, Terremark, and Gogrid) who want to sell computing by the hour instead of by the month, and want to have more standardized offerings.
Wednesday, May 26, 2010
Some are giant service companies (like Google) who want people to create millions of applications and keep people using the Web.
Wednesday, May 26, 2010
Some are big systems integrators (like IBM) who want to design and run IT for enterprises.
Wednesday, May 26, 2010
Some are hardware vendors (like Dell) who want to stay in the computing business as it shifts.
Wednesday, May 26, 2010
Some are telecom providers (like AT&T and Verizon) who want to do more than move packets around, and want to make the best use of their existing data centers.
Wednesday, May 26, 2010
Some are even government organizations aiming to build infrastructure for the use of the government itself
http://www.thule-car-roof-boxes.co.uk/pictures/roof-box-with-roof-rack.jpgWednesday, May 26, 2010
This isn’t a comfy place to be right now. Cloud computing has what I call a “roofrack” problem.
Wednesday, May 26, 2010
Wednesday, May 26, 2010
Part eight:So what do I do now?
Wednesday, May 26, 2010
http://www.flickr.com/photos/gideon/6582069/Wednesday, May 26, 2010
Cloud computing isn’t something you can easily ignore.
Wednesday, May 26, 2010
For some applications, particularly those that are bursty or seasonal, the economics are overwhelmingly in its favor.
Cloud Encounters, Peter van Eijk, digitalinfrastructures.nl ! !
"#$$%&'!'()%*!+,#)!-.!
'#!/)01#$!"2#34+,#$'
5%''%,!6%%,($7!0$48#,!9%''%,!,#3'($7:
;
<
=;
=<
>;
><
?;
?<
@;
@<
<;
>@ABA
>;;C
>DABA
>;;C
>CABA
>;;C
?;ABA
>;;C
=ACA
>;;C
?ACA
>;;C
<ACA
>;;C
DACA
>;;C
CACA
>;;C
==ACA
>;;C
=?ACA
>;;C
=<ACA
>;;C
=DACA
>;;C
!"##"$%&'()$*+'*&'((%&+
Connect times to Amazon Cloudfront from NYC
Wednesday, May 26, 2010
Cloud providers keep making their stuff better. Amazon introduced roughly 40 new features last year; and in a single month they upgraded their network in New York twice.
http
://w
ww
.flic
kr.c
om/p
hoto
s/bi
llsel
ak/3
6669
2332
/
Wednesday, May 26, 2010
And clouds make organizations more agile, because they take procurement from weeks to minutes.
Wiley GAAP 2010: Interpreta3on and Applica3on of Generally Accepted Accoun3ng Principles (By Barry J. Epstein, Ralph Nach, Steven M. Bragg)
Expense reports can no longer enforce IT policy.
Wednesday, May 26, 2010
They also remove the false sense of security that came from expense limits.
Airfare
DNS
Cloud
Publictransit
Importantresearch
Hotel
Wednesday, May 26, 2010
These days, supercompu-ng is easier (and cheaper) than booking a flight.
We stop worrying about ROI when I is zero.
Wednesday, May 26, 2010
Because there’s no investment, the concept of an ROI doesn’t really make sense.
http
://w
ww
.flic
kr.c
om/p
hoto
s/av
lxyz
/389
0304
08/
Wednesday, May 26, 2010
Even if you’re only going to run a private cloud, you’re dealing with expectations set by the public Internet. Consider an ATM – once, we didn’t mind taking all of lunch to get money out; today, we worry when the bank machine fails to give us our money back in 10 minutes. That’s a bad thing for organizations that don’t handle IT automatically; humans simply can’t move that fast. Efficiency isn’t about how fast you do things; it’s about how many things you don’t have to do because they’re automated.
http://www.flickr.com/photos/stuartpilbrow/2894451883/Wednesday, May 26, 2010
The Internet has a way of routing around obstacles, so if you try to block people from using them, you’ll likely send your stakeholders underground.
Wednesday, May 26, 2010
The best thing to do is offer people an alternative. Set up self-service computing internally and see what happens.
Virtualmachine
Storage Single sign on
Image processing
Key/value store
Parallelframework
Virtual load balancer
Mailing service
Wednesday, May 26, 2010
It also means surrounding them with composed services like storage and message queues. Fortunately, there is a wide variety of offerings to help with this. Hadoop, Cassandra, CouchDB, Hypertable and others are all tools that handle storage, scaling, and parallel tasks, and that you can deploy internally for your users.
Wednesday, May 26, 2010
It also means setting up platforms (such as a web server that can handle PHP code, or a Drupal platform for creating social sites, or a Status.net instance for microblogging,
Wednesday, May 26, 2010
or a Wordpress instance for blogs.)
Wednesday, May 26, 2010
Finally, it means working with SaaS providers when appropriate, but integrating their applications with your internal data and processes
http
://w
ww
.flic
kr.c
om/p
hoto
s/ja
mes
jord
an/3
4239
0595
9
Wednesday, May 26, 2010
For IT, and governments, cloud computing is a trigger. It means it’s time to rebalance your computing decisions.
http://www.flickr.com/photos/joconnell/504783550/Wednesday, May 26, 2010
With clouds, there’s a spectrum of IT options. Different applications live in different places in this new world.
Baremetal
VirtualizationIaaS
<script>Hello, world!</script>
PaaSMashup,RESTfulservices
Public/privatehybrid models
DevelopersData centers Contracts
Wednesday, May 26, 2010
Different applications live in different places in this new world.
http
://w
ww
.flic
kr.c
om/p
hoto
s/23
9125
76@
N05
/347
6080
117/
Wednesday, May 26, 2010
Here’s a five-step plan for embracing clouds.
http://www.flickr.com/photos/quinnanya/4569703917/Wednesday, May 26, 2010
First, you need to assess your existing applications. Make a list of everything you’ve got, or plan to have. You should also baseline usage, performance, and other “before” metrics so you can compare them to the results of your efforts after you’ve moved.
http://ww
w.flickr.com
/photos/rptnorris/3453936781/
Wednesday, May 26, 2010
Then, you need to rebalance your applications. Evaluate each application along two dimensions: how suitable is the application for migration, and what’s the payoff.
http://www.flickr.com/photos/cowcoptim/4104360701/Wednesday, May 26, 2010
Some applications, like legacy ERPs or old mainframe tools, won’t migrate easily. They’re not well suited to a virtualized, on-demand model where users can spin up resources as needed.
http
://w
ww
.flic
kr.c
om/p
hoto
s/sh
arif/
2423
1440
88/
Wednesday, May 26, 2010
Others, like web front-ends or parallel data processing tasks like analytics, that can be split up, work really well in clouds.
Some thingsaren’t worth moving.
Wednesday, May 26, 2010
At the same time, some applications won’t benefit much from a cloud model. Something that runs constantly may be more affordable to run in-house.
http://www.flickr.com/photos/aprilzosia/3002232587/Wednesday, May 26, 2010
Other applications may have a massive budget savings when they move to the cloud. Something that happens once a year but needs tremendous computing for the three days it runs is a candidate for clouds. So, too, is something that users are constantly requesting, and that your IT team spends a lot of time managing. Automate it!
Always on premise
Private
Compliance-enforced
Need to track and audit
Legislative
Data near local computation
Can be done anywhere
Testing
Training
Prototyping
Batch processing
Seasonal load
Always in cloud
Partner access
Proximity to cloud services (storage,
CDN, etc.)
Massively grid/parallel (genomic,
modelling)Lo
ad/p
ricin
g en
gine
Polic
y en
gine
Virtual machine(infrastructure cloud)
Compute task(service cloud)
Wednesday, May 26, 2010
Going forward, we’ll see hybrid on-premise/on demand hybrid clouds that can intelligently move processing tasks between private an public infrastructure according to performance requirements, pricing policies, and security restrictions.
http://www.flickr.com/photos/rberteig/1451038457/Wednesday, May 26, 2010
Third step: You have to migrate things to the new environments. This means moving stuff around—hopefully the high-payoff, easy-to-move stuff first. There’s no magic here: you’ll need to make your applications portable, which means virtualizing them; and you may need to modify some code.
http
://w
ww
.flic
kr.c
om/p
hoto
s/as
tro-
dude
s/24
2428
3150
/
Wednesday, May 26, 2010
Step four is to optimize things. In their new homes, some applications won’t perform as well. You’ll need to compare how they’re doing now to how they were doing before, and tweak things to ensure equivalent performance, uptime, security, and scalability.
http
://w
ww
.flic
kr.c
om/p
hoto
s/ge
ofth
eref
/225
3511
823/
Wednesday, May 26, 2010
Finally, in step five you need to operate things differently. Cloud computing is as much about a cultural shift in IT: you’re operating a self-service business.
http://www.flickr.com/photos/hojusaram/2527256358/Wednesday, May 26, 2010
You’re not doing the IT work any more; you’re managing the scripts and systems that let users do the IT work themselves. You have a very different relationship with your end users.
http://www.flickr.com/photos/avlxyz/1193082725/Wednesday, May 26, 2010
You’re providing the environment for them to innovate, giving them turnkey sets of services with which to work. Where they come from is immaterial.
http://www.flickr.com/photos/novecentino/2340521934/Wednesday, May 26, 2010
You’re ensuring that the systems you’ve built are functioning properly however end users want to use them, rather than running the applications or data within those systems.
http://www.codeproject.com/KB/miscctrl/ScriptStudio.aspx Wufoo.comWednesday, May 26, 2010
Your end users aren’t necessarily technical -- they’re able to build applications easily, and want the tools to experiment.
http://www.flickr.com/photos/roebot/4271975019/Wednesday, May 26, 2010
At the same time, you’re seeing what tools and processes are getting adopted -- what’s working? what’s popular? -- and doubling down on those things.
http://www.flickr.com/photos/steven_wong/2440355239/Wednesday, May 26, 2010
You’re giving your users places to experiment.
http://www.flickr.com/photos/jelles/2902422030/Wednesday, May 26, 2010
To some extent, you’re “paving the cowpaths.”
http://www.flickr.com/photos/32314864@N02/3253051215/Wednesday, May 26, 2010
This is an old civil engineering trick: Watch where people walk, then put paths there.
Part nine:Conclusions.
Wednesday, May 26, 2010
Massive disruption on the horizonClouds are extremely disruptive to the way IT works
Wednesday, May 26, 2010
Virtualization let the genie out of the bottleClouds arose from virtualization, which made application workloads portable
Wednesday, May 26, 2010
Clouds start with separation
Separation is key
Determines economics, lock-in, responsibility, risk
Wednesday, May 26, 2010
One of the fundamentals of a cloud is the separation of the provider from the user at some layer in the stackWhere that separation happens determines economics, responsibilities, risk, and lock-in
Business vs. technology
Know the difference
Clouds-as-tech: Virtualized, automated
Clouds-as-business: 3rd party, shared
Force others to be clear
Wednesday, May 26, 2010
Two main divisionsIaaS/PaaS/SaaS
Public/Private
Wednesday, May 26, 2010
One size does not fit allUltimately, the blend of these different models will vary from organization to organization
Wednesday, May 26, 2010
Five steps to cloud migration
Assess Balance Migrate Optimize Operate
Wednesday, May 26, 2010
Ecosystem is in fluxThe ecosystem is competitive and confusing right now, with few standards and a lot of noise
Wednesday, May 26, 2010
http://www.flickr.com/photos/sparkys/3434382326/Wednesday, May 26, 2010
It will probably wind up looking like airlines.
http://www.cio.gov/documents/StateOfCloudComputingReport-FINALv3_508.pdf
Wednesday, May 26, 2010
It will probably wind up looking like airlines.
Representation is a hack
The big picture
Wednesday, May 26, 2010
It will probably wind up looking like airlines.
