Building & Managing Windows Azure
1 like450 views
This document summarizes a talk on building, deploying, and managing Windows Azure applications. It discusses setting up cloud services and SQL databases using Visual Studio tools. It covers deploying applications to the cloud through Visual Studio, the management portal, or PowerShell. It also describes ways to view applications in the cloud like remote desktop, diagnostics, and SQL distributed views. The talk provides an overview of key concepts like deploying and updating applications, hosting web roles with full IIS, and using resources to learn more.
Building & Managing Windows Azure
- 1. Building, Deploying, and Managing Windows Azure Applications(Adapted from Jim Nakashima’s session in PDC2010)Wely LauMicrosoft MVP, Windows AzureSolutions Architect, NCS Pte LtdEmail : wely@ncs.com.sgBlog: http://wely-lau.net/
- 2. This talk is for developers.ON
- 3. Composition
- 4. AgendaSetting up the cloudDeploying to the cloudViewing into the cloudNew release New release
- 5. Setting up the Cloud
- 6. demo Creating and Managing Windows Azure Services and SQL Azure Databases
- 7. Creating and Managing Services & DatabasesWindows Azure Tools for Microsoft Visual StudioFree Add-in for Visual Studio 2010Updating content without stopping debuggingIntelliTrace on F5 local debugging (32-bit)Improved F5 performanceRedesigned PortalImproved workflows – fewer clicks and less waitingManagement consoleSSMS, sqlcmd, Data Tier Application and other SQL Server tools for SQL AzureNew releaseNew release
- 8. Deploying to the Cloud
- 9. Deploying to the CloudCreate a new deployment:Visual StudioWindows Azure PortalCommand line and PowershellBuilt using the Service Management REST APIVIP is assigned during deployment
- 10. Updating a Deployment in the CloudUpdate the service configuration fileDeveloper web deploy to a single instanceUpgrade a role or all rolesReuse existing instancesDeploy and VIP Swap or “DNS Swap”Delete and DeployOS update
- 11. Update Considerations VIP swap Easier to undoRequires 2 identical environmentsCannot update endpointsUpgradeReuses existing VMs (Preserves VM state i.e. local cache data)Can update a single roleCannot change the service definitionNot as good for the front end Requires compatibility between existing and new deployment
- 12. Update Considerations “DNS Swap”:Requires your own domain nameUpdating the domain record is not immediateNew VIPDelete/recreate:Down time between deploymentsNew VIP
- 13. Hosted Web Core VS Full IISHosted Web Core (HWC)Web Role did not actually run full IIS. It used a component called Hosted Web Core, the core engine for serving up web pages that can be hosted in a different process.Learn more: http://blogs.msdn.com/b/windowsazure/archive/2010/12/02/new-full-iis-capabilities-differences-from-hosted-web-core.aspx
- 14. Multiple IIS Sites and Virtual ApplicationsUpcoming release uses full IIS and not Hosted Web CoreAdd multiple IIS sites and Virtual applications per Web Role in the service definition fileNew release
- 15. Multiple IIS Sites and Virtual ApplicationsUpcoming release uses full IIS and not Hosted Web CoreAdd multiple IIS sites and Virtual applications per Web Role in the service definition fileManual debugger attach and browser launchNew release
- 16. Adding an IIS Site and Virtual Application to a Web RoleServiceDefinition.csdef<WebRole name="WebRole1"> <Sites> <Site name="Web"><VirtualApplication name="mail" physicalDirectory="C:\Users\jnak\Desktop\Scratch\WebSite"/> <Bindings> <Binding name="HttpIn" endpointName="HttpIn" /> </Bindings> </Site><Site name="PDC" physicalDirectory="C:\Users\jnak\Desktop\Scratch\SecondWebSite"><Bindings> <Binding name="HttpIn" endpointName="HttpIn" hostHeader=“pdctest" /> </Bindings> </Site> </Sites>
- 17. Viewing into the Cloud
- 18. How can you see into the cloud?New releaseRemote DesktopIntelliTraceWindows Azure DiagnosticsSQL Distributed Management ViewsWindows Azure Storage ViewersMost SQL Server Tools
- 20. Remote DesktopEnable as a deployment option in Visual StudioUse the Portal to:Deploy an exported certificateConnect to an instanceAdvanced options are available by editing the Service Definition and Service Configuration filesDesignate one role as the remote forwarder
- 21. Windows Azure DiagnosticsFacility that collects diagnostic data from your instances and copies it to a storage accountIIS logs, trace logs, IIS failed request logs, Windows Event logs, Performance counters and crash dumpsTransfer the diagnostic data to a storage accountData is collected locally to each instanceTransfer On Demand or at automatic scheduled intervalsConfigure diagnostics and transfers programmatically from within the role or remotely through a .NET APIWindows Azure Monitoring, Logging, and Management APIs
- 22. What’s New in DiagnosticsEnabled as an option and not programmaticallyDecoupled from the role process – i.e. starts before and will not exit with the role processCan collect data if the role failed to start or if the role is restartingSame configuration and API for VM roles
- 23. SQL Distributed Management ViewsInteresting data can be retrieved using dynamic management views. SQL Azure supports a subsetReturns information regarding your current logical database onlyCommon scenarios:Calculate database sizeMonitoring connections (active user and internal tasks)Monitoring Query PerformanceMonitoring SQL Azure Using Dynamic Management Views
- 24. RecapSetting up the cloudDeploying to the cloudViewing into the cloud
- 25. ResourcesCloudy in Seattle blog: http://blogs.msdn.com/jnakSamplesWindows Azure Code SamplesWindows Azure Service Management CmdLetsRelated videos:Windows Azure Monitoring, Logging, and Management APIsUsing Microsoft Visual Studio 2010 to Build Application that run on Windows Azure
- 26. Wely LauMicrosoft MVP, Windows AzureSolutions Architect, NCS Pte LtdEmail : wely@ncs.com.sgBlog: http://wely-lau.net/Thank you!
Editor's Notes
- #14: What is Full IIS?Windows Azure's Web Role has always allowed you to deploy web sites and services. However many people may not have realised that the Web Role did not actually run the full Internet Information Services (IIS). Instead, it used a component called Hosted Web Core (HWC), which as its name suggests is the core engine for serving up web pages that can be hosted in a different process. For most simple scenarios it doesn't really matter if you're running in HWC or IIS. However there are a number of useful capabilities that only exist in IIS, including support for multiple sites or virtual applications and activation of WCF services over non-HTTP transports through Windows Activation Services.One of the many announcements we made at PDC 2010 is that Windows Azure Web Roles will support Full IIS. This functionality is now publicly available and included inWindows Azure SDK v1.3. To tell the Windows Azure SDK that you want to run under Full IIS rather than HWC, all you need to do is add a valid <Sites> section to your ServiceDefinition.csdef file. Visual Studio creates this section by default when you create a new Cloud Service Project, so you don't even need to think about it!