Presentation is loading. Please wait.

Presentation is loading. Please wait.

Interoperability. Describe the technology Explain the commercial model Consider Workload Patterns and Application Types Discuss Future Direction Objectives.

Similar presentations


Presentation on theme: "Interoperability. Describe the technology Explain the commercial model Consider Workload Patterns and Application Types Discuss Future Direction Objectives."— Presentation transcript:

1 Interoperability

2 Describe the technology Explain the commercial model Consider Workload Patterns and Application Types Discuss Future Direction Objectives of this session

3 Cloud

4 Windows Azure TimeLine Oct 2008 1 st 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

5 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

6 Windows Azure In One Picture Desktop VS Tools WA SDK Storage Cluster Microsoft Datacenters Business Portal Developer Portal Compute Cluster … … Service Management Service REST … Cloud VM Runtime API WA Setup Customer Code

7 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 Web Role Worker Role

8 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

9 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

10 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

11 Example: Running a Java App Run()

12 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

13 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

14 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

15 Windows Azure Platform Consumption Prices $0.12/hour + Variable Instance Sizes $9.99/month (up to 1 GB DB/month ) $99.99/month (up to 10 GB DB/month ) $0.15 GB/month $0.01/10K transactions Prices shown in USD only $1.99/100K Transaction Per Transaction $3.99/Connection Month Per connection International prices are available

16 Windows Azure Instance Sizes Unit of Compute Defined $0.12 $0.24 $0.48 $0.96 1 x 1.6Ghz 2 x 1.6Ghz 4 x 1.6Ghz 8 x 1.6Ghz 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 )

17 North America Region S. Central - US Sub-region N. Central – US Sub-region Europe Region W. Europe Sub-region S.E. Asia Sub-region Asia Pacific Region E. Asia Sub-region N. Europe Sub-region Windows Azure Platform Data Transfer 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 North America PST = UTC-8 PST = UTC-8 Europe WET = UTC Asia Pacific SST = UTC+8

18 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 (English, French, German, Japanese, & Spanish)

19 Windows Azure Platform Purchasing Models

20 Workload Patterns Optimal For Cloud Usage Compute Time Average Inactivity Period On & off workloads (e.g. batch job) Over provisioned capacity is wasted Time to market can be cumbersome Compute Time Average Usage Unexpected/unplanned peak in demand Sudden spike impacts performance Can’t over provision for extreme cases Average Usage Compute Time Successful services needs to grow/scale Keeping up w/ growth is big IT challenge Complex lead time for deployment Compute Time Average Usage Services with micro seasonality trends Peaks due to periodic increased demand IT complexity and wasted capacity

21 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

22 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

23 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 http://www.mygreatwindowsazureidea.com

24 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


Download ppt "Interoperability. Describe the technology Explain the commercial model Consider Workload Patterns and Application Types Discuss Future Direction Objectives."

Similar presentations


Ads by Google