Windows Azure Kick Start - Get Started in Cloud Computing

Editor's Notes

• #4: Peak is never what we expectHave to buy more hardware and make data center more expensiveMore than half of data center cost is electricity and cooling
• #5: Slide Objectives:Explain how Microsoft thinks of the cloudSpeaking Points:There are numerous terms and definitions floating around in the industry for “the cloud”, “cloud computing”, “cloud services”, etc.Microsoft thinks of the cloud as simply an approach to computing that enables applications to be delivered at scale for a variety of workloads and client devices.The cloud can help deliver IT as a standardized service…freeing you up to focus on your businessDynamic Resources
• #6: Container – 2500 serversPing, Power, PipeEuropean Disco TechAzure Fabric Controller, Guarantees the SLA
• #7: Speaking Points:3 core services: Compute, Storage, DatabaseLet’s take a look at the platform starting with the core services.Compute:Scalable environment for running codeEnables .NET, C++, PHP, Ruby, Python, …Automated service managementStorage:Scalable and highly available cloud storageBlobs, Tables, Queues, DrivesREST APIs and several client librariesDatabase:SQL Relational DatabaseFamiliar programming model & tools--Speaking Points:I suspect most if not all of you in this room are familiar with the Windows Azure today.Today the platform consists of a set of foundational services SQL Azure relational databaseWindows Azure provides services that can be used by any apps – hosted in Windows Azure, on-premises, or hosted in another environment. Questions:How many of you are building applications for Windows Azure?How many are using SQL Azure?How many are using the Access Control service today? The Service Bus?Notes:Windows Azure StoryWe are building an open platform to run your applications in the cloud. Your apps are .NET, Java, PHP, etc. We love everyone.We are going to help you migrate your existing apps to the cloud. The cloud platform is the future. Enables scale, self-service, lowers friction, etc. We provide the best cloud platform for building new apps. (aka n-tier, web services, etc.)
• #8: Slide Objectives:Provide overview and detail on pricingDiscuss localization of pricingSpeaking Points:Windows Azure is charged per compute hour.Pricing is localized for global marketsDifferent VM sizes have a different number of CPUs and therefore are a multiple the single CPU rateCompute time, measured in service hours: Windows Azure compute hours are charged only for when your application is deployed.remove the compute instances that are not being used to minimize compute hour billing. Partial compute hours are billed as full hours.Storage, measured in GB: Storage is metered in units of average daily amount of data stored (in GB) over a monthly period. Data transfers measured in GB (transmissions to and from the Windows Azure datacenter).Data transfers within a sub region are free. Transactions, measured as application requests to the REST serviceSQL Azure is priced on a per database per month basisService Bus is based on a per connection modelAccess control is based on a per transaction modelService Bus connections can be provisioned individually on a “pay-as-you-go” basis or in a pack of 5, 25, 100 or 500 connections. For individually provisioned connections, you will be charged based on the maximum number of connections you use for each day. For connection packs, you will be charged daily for a pro rata amount of the connections in that pack (i.e., the number of connections in the pack divided by the number of days in the month). You can only update the connections you provision as a pack once every seven days. You can modify the number of connections you provision individually at any time.For Access Control transactions, customers will be charged the actual number of transactions utilized for the billing period (i.e., not in discrete blocks of 100,000 transactions), plus data transfers in or out.Notes:http://www.microsoft.com/windowsazure/pricing/http://blogs.msdn.com/b/netservices/archive/2010/01/04/announcing-windows-azure-platform-commercial-offer-availability-and-updated-appfabric-pricing.aspx http://www.microsoft.com/windowsazure/pricing/
• #9: Slide Objectives:Explain that there are different VM instance sizes available within Windows AzureSpeaking Points:---Speaking Points:One of the key areas of feedback has been to reduce the cost and size of Windows Azure instances. At PDC we will announce..Notes:(*) 20GB with a limitation on VHD size if they are deploying VMRole on XSmall: the VHD can only be up to 15GB.each tenant can support 20 instances just like regular subscriptions with Small VM. We do not scale based on core counts.There is no SLA on the network bandwidth for each VM size as this resource is shared among all the VM. That said, we need to provide guidance for customer so they could design their applications correctly. From the engineering side, this is what we mean by Low, Moderate and High. • Low currently means 0-15Mbps with short burst up to 25-50Mbps (Megabit/s). These are sufficient for some web sites with low traffic. • Moderate means 0-100Mbps with short burst up to 200Mbps (100Mbps is the norm). This is what we currently reserve for the Small VM.• High means 200-800 Mbps. If you divide this into 3 spectrums for Medium, Large and XL. Then Medium is in the low end, Large hovers around the middle zone and of course XL takes the high-end spot.These rates should be used as guidance. Nothing can beat a test run to see what the application requires but using these bandwidth ranges, hopefully it reduces the guess work for the customers
• #12: Slide objectives: Summarize what the audience just saw with the Hello Windows Azure demo.Speaking Points: What you sawSo we just saw a number of things within this simple demo.First you saw a simple ASP.NET web application, like many of you have built before.We created the application using Visual Studio 2010, tools many of you are familiar with.We were able to model the roles and instances for our Windows Azure application in a simple config file.You saw how the Windows Azure development fabric provides a local environment for developing, debugging, and testing our applications – which is integrated directly with Visual Studio. Finally, you saw how we could deploy our applications to Windows Azure and in a matter of minutes have the application running in the cloud and switch from staging to production.What Windows Azure ProvidedWhat is more exciting then this simple application is what you didn’t see, but what Windows Azure provided.First, Windows Azure provided an environment to run code – to run our ASP.NET application.It provided all of the infrastructure such as machines, rack space, connectivity, and switches.It also automated and simplified the deployment and configuration. At no point did we have to remote into machines or FTP files or synchronize our application across machines. This automated service management was provided by Windows Azure.Windows Azure also provided isolation for us – where our application is isolated from other apps that either we would develop or other organizations would develop. We also saw how by simply specifying the number of instances in the service model, Windows Azure delivered key capabilities such as redundancy and load balancing for our application.Ultimately, what this results in is abstraction and flexibility.