x10

questions - and answers - about cloud computing

But first - Who am I?

1. What is cloud computing?

"Cloud compu+ng is a generic term used to describe the disrup+ve

transforma+on in I.T. towards a service based economy driven by a
set of economic, cultural and technological condi+ons...."

1. The illusion of innite compu3ng resources..

2. The elimina3on of an up-front commitment
by Cloud users..
3. The ability to pay for use as needed

a) Signup for an AWS account

Use your exis+ng Amazon.com account if you want

b) Register a credit card

Billed on the 1st of every month for usage prior

c) hHp://aws.amazon.com/ec2

More views...
Cloud Clients
Cloud Applica3on
Cloud Services
Cloud PlaBorm
Cloud Storage
Cloud Infrastructure

The Cloud's resources

scale with user
demands, and you
only pay for what
you use.

Cloud Security and Privacy, 2009, Tim Mather et al.

2. Why would anyone use it?

Flexibility and scalability

Time to market
Cost savings
Power savings
Green savings
Increased agility in soUware deployment
...

Pay by use instead of provisioning for peak

Capacity
Capacity

Demand

Demand
Time

Time

Static data center

Data center in the cloud

Unused resources

Heavy penalty for under-provisioning

Capacity
Demand
Capacity
Demand
1

2
Time (days)

2
Time (days)

Lost revenue

3
Capacity
Demand
1

2
Time (days)

Lost users

3. Why would anyone deliver it?

Network

Cost in
Medium DC
1000 servers
$95 / Mbps / month

Cost in
Very Large DC
50,000 servers
$13 / Mbps / month

Storage

$2.20 / GB / month

$0.40 / GB / month

5.7x

Administra+on

140 servers/admin

>1000 servers/admin

7.1x

Resource

Price per KWH

Where

Ratio
7.1x

Possible Reasons Why

3.6

Idaho

10.0

California Electricity transmiHed long distance over the grid;

limited transmission lines in Bay Area; no coal red
electricity allowed in California.
Hawaii
Must ship fuel to generate electricity

18.0

Hydroelectric power; not sent long distance

4. What does it cost, and for whom?

Real life example, from Univ of Oklahoma

Amazon EC2 oers a lower price alterna+ve, where you book an en+re
server for up to 3 years, in which case the price is:
$2800 3-year buy-in fee
+ $0.24 * 24 hours per day * 365 days per year * 3 years
= $9107.20 per 3 years
Whereas at OU it's:
$0 buy-in fee + $0.35 * 24 hours per day * 365 days per year * 3 years
= $9198.00 per 3 years

So if you commit to using an Amazon EC2 server for 3 years

all day every day -- it's preLy much breakeven.
Using it less than all day every day makes it more expensive
per server hour, because of the $2800 buy-in fee.

Of course, it's not really breakeven at all, because

Amazon EC2 lacks the following:
(a) high performance interconnect (at OU, Inniband);
(b) high performance parallel lesystem (at OU, Panasas);
(c) user services to help make people produc+ve (everyone on our team has experience
working directly with users).

If any of the following are true, then cloud compu3ng may

be cheaper than centrally-managed resources:
(i) your internal centrally-managed resources are expected to be idle a signicant frac+on
of the +me;
(ii) your users don't need a high performance interconnect;
(iii) your users don't need high performance parallel I/O;
(iv) your users don't need high end user services.

But if any of these is false, then you're probably beLer o, in

terms of cost, having centrally-managed local resources.

But ...
..... comparisons should be done vs total
cost of ownership - from start to finish.
This is one of the tasks in the NEON
project, mentioned later in this Q&A.
And. NEON cost comparisons will include
the value of flexible services and more.

5. Can I trust it?

5. Can I trust it?

Cloud compu+ng is about gracefully
losing control while maintaining
accountability even if the opera+onal
responsibility falls upon one or more
third par+es.

!"#$%&"'($)*+$%,-.($-/$01-2+$3456)7-*$

There are many benets that explain why

to migrate to clouds
Cost savings, power savings, green savings, increased
agility in soUware deployment

Cloud security issues may drive and dene how

we adopt and deploy cloud compu+ng solu+ons

6. I want to try it on my own machines - how?

Hybrid
Private /
Internal

Public /
External

The Cloud

On Premises / Internal

Off Premises / Third Party

7. Who is using this, who is

delivering - today?

!"#$%&'$()*+(),-.)$/#$01/23$0/4(2-#5!6$7/.$89$!
!!"#$!%&'()$*+!,$-.('/!*+0!1+2('3*4(+!5$6&'7-8!9:$+68!;%,159<!!

8. What does it take to

become a cloud provider?

Image Courtesy IDC Architects

Containers: Separating Concerns

Microsoft Advances in DC Deployment

Conquering complexityBuilding
racks of servers & complex
cooling systems all separately is
not efficient.Package and
deploy into bigger units, JITD

Datacenter is the new Server

U"lity compu"ng: enabling innova"on in new services
without rst building & capitalizing a large company.

One of Google's data centers, this one in Oregon

Microso>s data center in San Antonio, Texas

Year 2013: $4B market.... (www.the451group.com)

Google
DCs
today
Text
Text
Text

9. What is being done here

in Norway on clouds?

www.necloud.org

Project +me span: Jan-Dec, 2010

Outcome: recommenda+on to Nordic eScience
community w r t clouds
Learning-by-doing (POFs, collabora+ons)
Cost and risk is key - long term
Collabora+ng with 8 similar projects in EU

Team
ke Edlund - NDGF/KTH coord
Maarten Koopmans - UNINETT SIGMA
Miika Tuisku - UH-HIP
Jukka Kommeri - UH-HIP
Pekka Lehtovuori CSC
Frederik Orrelana NBI
Klaus Marius Hansen HI
Helmut Neukirchen HI
Ebba ra Hvannberg HI
Zeeshan Ali Shah KTH
Michael Gronager NDGF - mgmt
Josva Kleist - NDGF - mgmt

NEON Contacts
ke Edlund
Coordinator, NDGF/KTH
ake.edlund@gmail.com
Maarten Koopmans
Pilot lead, UNINETT-SIGMA
maarten@vrijheid.net

10. ...?

This one is for you to ask us!

Wrapping up
Cloud compu+ng is ....
a generic term used to describe the disrup+ve
transforma+on in I.T. towards a service based economy
driven by a set of economic, cultural and technological
condi+ons....
In prac+ce today you get ...
instantly, scalable, on-demand compute power, storage
and bandwidth - pay only for what you use
... and it is all here now, with many avors and providers.

Our coordinates
ake.edlund@gmail.com
maarten@vrijheid.net
zashah@pdc.kth.se

The rest of the day

10-10:30:
10:30-10.45:
10:45-12:00:
12-13:
13-13:30:
13:30-15:
15-16:

Explain cloud components I

Coffee break
Hands on I
Lunch
Explain Cloud components II
Hands on II
User feedback, discussion, use cases that
want to pilot?

The rest of the day

10-10:30: Explain cloud components I : Storage, computing components named
and explained. Explain command line tools vs AWS console vs Rightscale.
10:30-10.45: Coffee break
10:45-12:00: Hands on I : Obtain AWS credentials, obtain command line tools for
VM management and S3 management. Goal: launch a default Fedora 8 32 bit VM.
12-13 - Lunch
13-13:30: Explain Cloud components II: RDS, SimpleDB, SQS application design
13:30-15: Hands on II : Start a VM (again), install anysoftware you like, then go
through the process of bundling. Start from your bundle. If a user has time left:
create an EBS and attach that to your VM. If a user has no software to install, use
the s3-tools from this morning.
15-16: User feedback, discussion, use cases that want to pilot?

Thanks!