Interoperability

The A to Z ofWindows AZure

Simon DaviesWindows Azure Incubation Team

Microsoftsdavies@microsoft.com

http://blogs.msdn.com/simondavies

• Describe the technology• Explain the commercial model• Consider Workload Patterns and Application

Types • Discuss Future Direction

Objectives of this session

Cloud “A style of computing where SCALABLE and E L A S T I C IT-enabled capabilities are provided as a service to external customers using Internet technologies.”

Gartner, Inc. “Hype Cycle for Cloud Computing,” 2009, by Daryl Plummer et al, July 16, 2009.

”A standardized IT capability, such as SOFTWARE, APP PLATFORM, OR INFRASTRUCTURE, delivered via Internet technologies in a pay-per-use and self-service way. “

“How To Message "Cloud" Offerings And Not Get Lost In The Fog,” Forrester Research, Inc., July 2009.

Windows Azure TimeLine

• Oct 2008 1st CTP announced – supports .Net “Medium Trust” code, Blobs, Queues, Table and Automatic Service Management.

• March 2009 – .Net Full Trust, Native Code, Geo-Location, FastCGI

• May 2009 Storage Enhancements, PHP SDK CTP, new VS tools and SDK.

• July 2009 New SDK version and Business Model

Windows Azure Timeline

• Aug 2009 New Blob Features • September 2009 Management API, Portal, New

Upgrade Options• Oct 2009 Eclipse plug in for PHP, Java SDK• Nov 2009 CDN and Custom Domains for Blob

Storage.• Jan 2010 Customer selectable guest OS version• Feb 2010 Cloud Drive v1.1 SDK

Windows Azure In One Picture

Desktop

VS Tools

WA SDK

Stor

age

Clus

ter

Microsoft Datacenters

Business Portal

Developer Portal

Com

pute

Clu

ster

……

Service Management Service

REST

REST

…

Cloud VM

Runtime API

WA Setup

Customer Code

Service Model

• A service is made up of components called roles– Arbitrary # of endpoints per role– Arbitrary # of identical instances of

each role, one per VM, variable size– Arbitrary # of roles

• 2 kinds of roles– Web Role: We host your role

on IIS – Worker Role: Provides an entry

point for you to run your code, can have both external and internal network conectivity

• Service architecture

Worker Role

Web Role

Worker Role

Service Model

• Internal to service: – Any role instance can reach any

endpoint by IP/Port#– Port #s assigned by platform, a query

API is provided

• External to service:– Outbound: No restrictions– Inbound: Single VIP; port slicing for

multiple endpoints– Developer can specify port # for any

input endpoint

• Communication (TCP, HTTP, HTTPS)

LB

Programing Model

• Code can run with full trust• Languages & APIs– Support any language supported by Windows

Server 2008 • Support standard .NET, Win64 APIs • Azure Specific APIs– Logging And Monitoring– Service Configuration– Storage Library

What about existing code?

• Has to fit the service model• Will It Run?– Windows– Non-admin user– Copy to Deploy – no install

• General Approach– Declare network requirements– “Copy” your code to a compute node on startup– Query for IP\Port information– Create a process from a Worker Role

Example: Running a Java App

Worker Role

JRE

Worker.class

.NET

Worker.dll

Run() Process.Start()

Windows Azure Storage• Blobs

– Small to very large files – Can be block (sequential) or page (random)

• Drives– A page blob formatted as a fixed sizevhd.– Can be mounted on a compute instance read\write or read only

• CDN– Content Distribution Network for blob storage

• Tables– Partitioned, dynamic schema, entity sets

• Queues– FIFO –like persisted storage for inter process communication

• All automatically managed by Windows Azure

• Service automatically maintains running service instances– failure of hardware or software managed– Network automatically managed

• Portal and API for management operations– E.g. deploy app, change configuration

• Choice of Data Centre Location

Service Management

• Application Deployment Options– Virtual IP Swap– Planned Downtime– Rolling Upgrade

• Windows Azure Guest OS Upgrade Options– Fix to a specific version via service config– Automatic upgrade

Service Management

Windows Azure Platform Consumption Prices

Elastic, scalable, secure, & highly available automated service platform

Pay as you go and grow for only what you use when you use it

Compute

$0.12/hour

+ Variable Instance Sizes

Per service hour

Highly available, scalable, and self managed distributed database

service

Web EditionPer database/month

$9.99/month(up to 1 GB DB/month)

Business Edition

$99.99/month(up to 10 GB DB/month)

Per database/month

Storage Per GB stored &

transactions$0.15 GB/month

$0.01/10K transactions

Prices shown in USD only

Windows Azure platform AppFabric Service Bus & Access ControlScalable, automated, highly available services for secure connectivity

Access Control

$1.99/100K Transaction

Per Transaction $3.99/Connection Month

Per connection

Service Bus

International prices are available

Windows Azure Instance Sizes

Unit of Compute Defined

Small

$0.12

Per service hour

Medium

$0.24

Per service hour

Large

$0.48

Per service hour

X Large

$0.96

Per service hour

Variable instance sizes to handle complex workloads of any size

 

Small

1 x 1.6Ghz (moderate IO)

Medium

2 x 1.6Ghz (high IO)

Large

4 x 1.6Ghz (high IO)

X-Large

8 x 1.6Ghz(high IO)

Equivalent compute capacity of a 1.6Ghz processor (on 64bit platform)

1.75 GB memory 3.5 GB memory 7.0 GB memory 14 GB memory

250 GB storage(instance storage)

500 GB storage(instance storage)

1000 GB storage(instance storage)

2000 GB (instance storage)

North America Region

S. Central - US Sub-region

N. Central – US Sub-region

Europe Region

W. Europe Sub-region

S.E. AsiaSub-region

Asia Pacific Region

E. AsiaSub-region

$0.10 GB Ingress

$0.15 GB Egress

$0.10 GB Ingress

$0.15 GB Egress

$0.30 GB Ingress

$0.45 GB Egress

N. Europe Sub-region

Windows Azure Platform Data Transfer Priced per GB transferred/month (prices shown in USD)

No Charge For Off Peak Ingress Promotion (ends 30/6/10)

On-board to Windows Azure platform at no charge Off peak times defined as: 10pm-6am Mon-Fri & from 10pm-Fri to 6am-Mon for weekends

in each designated regional time zones below

North America PST = UTC-8

Europe WET = UTC

Asia PacificSST = UTC+8

Available in 11 currencies Jan 2010

Available in 12 currencies Q2 2010

Windows Azure Platform purchasing availability in worldwide currencies

International Pricing

11. Australian Dollar (AUD) / FX Rate 1.25

1. US Dollar (USD)

2. Canadian Dollar (CAD) / FX Rate 1.11

3. British Pound (GBP) / FX Rate 0.6061

4. Danish Krone (DKK) / FX Rate 5.46

6. EURO (EUR) / FX Rate 0.7092

7. Norwegian Kroner (NOK) / FX Rate 6.15

8. Swedish Krona (SEK) / FX Rate 7.5

9. Swiss Franc (CHF) / FX Rate 1.1

10. Japanese Yen (JPY) / FX Rate 98

11. New Zealand Dollar (NZD) / FX Rate 1.563

Billing localized in 5 languages Jan 2010

(English, French, German, Japanese, & Spanish)

International prices determined by using USD prices and applying FX rates

Windows Azure Platform Purchasing Models

“Pay as you go and grow”

Low barrier to entry & flexibility

Optimized for cloud elasticity

Available Now

Consumption

“Value for a commitment“

Discounts for commitment

Plans for payment predictability

Subscription

Select offers available Now

“Coordinated purchasing”

Centralized purchasing experience

Introduction to volume discounts

Planned for future

Additional Licensing

Promotional

Offers Partner Discount

Development Pricing

Integration withPrograms

Workload Patterns Optimal For Cloud

Usage

Com

pute

Time

Average

Inactivity

Period

“On and Off “

On & off workloads (e.g. batch job)Over provisioned capacity is wasted Time to market can be cumbersome

Com

pute

Time

“Unpredictable Bursting“

Average Usage

Unexpected/unplanned peak in demand Sudden spike impacts performance Can’t over provision for extreme cases

Average UsageCom

pute

Time

“Growing Fast“

Successful services needs to grow/scale Keeping up w/ growth is big IT challenge Complex lead time for deployment

Com

pute

Time

Average Usage

“Predictable Bursting“

Services with micro seasonality trends Peaks due to periodic increased demandIT complexity and wasted capacity

• Information Sharing– “Edge of the Enterprise” – marketing campaigns,

customer\employee\partner information portals, mobile enablement ,Data As A Service

• Compute Intensive– Some types of HPC

• New or extensions to existing applications more likely

Application Types

Future Direction

• Improve Symmetry of on-premise and cloud platform– across multiple layers of the system

• Impact many areas– Management Tools– Server Platform– Cloud Platform– Application Runtime Capability

Future Direction

• For Windows Azure:– VM Role – Admin Access– RDP Access

• More details to come throughout the year• Suggest\Vote for enhancements:– http://www.mygreatwindowsazureidea.com

• Windows Azure is released and commercially available– Many scenarios for use today

• Based on customer\partner feedback, we are:– adding functionality, and– adding tooling– Enhancing business model

• To enable new scenarios:– more sophisticated applications – more existing applications

More information: http://blogs.msdn.com/windowsazure http://www.windowsazure.com

Summary