Agenda

Motivation & OverviewRemote Desktop / Re-image / RebootAdmin Mode / Service Modeling

EnhancementsVM RoleQ&A

Get more control & flexibility of the

Windows Azure environmentDevelopersIT Pros

Easier migration of existing Windows applications to Windows Azure

Use these capabilities within Windows Azure service model for lower management costs and improved agilityAutomated service managementBest practices for the cloud

Motivation & Overview

Anatomy of a Windows Azure ServiceA Windows Azure service consists of:An isolation boundaryA set of component roles, each with endpoints

Numbered, multiple instances of each roleA Windows Azure application behaves correctly when any role instance failsAll of this is specified in a service model

Comparison of Role Types

Abstraction (i.e. Less IT & Less Plumbing Code)

Control

Web RoleThe role is hosted on IIS

Worker RoleThe role is an executable (you can create your own web server, host a database, …)

VM RoleThe role is the VMUse Windows services, scheduled tasks, etc.You configure and maintain the OS

demo

Remote DesktopROLE 1 ROLE 2

Remote Forwarder

PORT 3389

Internal Port 3389

<?xml version="1.0" encoding="utf-8"?><ServiceDefinition name="RemoteAccess" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition">

<WorkerRole name="GatewayRole"><ConfigurationSettings>

<Setting name="DiagnosticsConnectionString" /></ConfigurationSettings><Imports>

<Import moduleName="RemoteAccess" /><Import moduleName="RemoteForwarder" />

</Imports></WorkerRole><WorkerRole name="TargetRole">

<ConfigurationSettings><Setting name="DiagnosticsConnectionString" />

</ConfigurationSettings><Imports>

<Import moduleName="RemoteAccess" /></Imports>

</WorkerRole></ServiceDefinition>

<Role name="WorkerRole1"><Instances count="1" /><ConfigurationSettings><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername" value="myuser" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword"

value="[base64]" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration" value="2010-06-16T13:04:02.9666425-07:00" />

</ConfigurationSettings><Certificates><Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordCertificate"

thumbprint="c0c23e1cdd7bfb20c14dce97b37ea67bd9f24918" thumbprintAlgorithm="sha1" /></Certificates>

</Role>

VM Role – Overview

Developers have full control over the OS image

Ability to upload your own customized WS08R2 Enterprise images

Operators can reboot, re-image and Remote Desktop

Continue to benefit from automated service management, including service model enhancements described on subsequent slides

VM Role LifecycleConvert product DVD to a VHD, or use existing VHDPrepare the VHD (Install Integration Components/SysPrep)

Create a service model with the above image

Store VHD in Windows Azure blob storage

Include in service model. Specify instance countPackage as cspkg, upload cskpgRemote DesktopReboot / Reimage

Repeat above steps, with a new OS image

VM Role Lifecycle

& Additional Software& Windows Azure Integration Components:AgentRuntime Interface (topo, config, shutdown notification, …)Remote Desktop configuratorDiagnosticsWindows Azure Drives driverWindows Azure Connect

& Generalize (Recommended)

Base.VHD

Identical/similar deployment instances using common uploaded OS image (base.VHD +

diff.VHD)

On-Premises Cloud

<ServiceDefinition name="MyVMRoleService" xmlns="…"><VirtualMachineRole name="MachineRole" vmsize="Medium"><Imports><Import moduleName="RemoteAccess" /><Import moduleName="RemoteForwarder" /><Import moduleName="Diagnostics" />

</Imports></VirtualMachineRole>

</ServiceDefinition>

<ServiceConfiguration serviceName="MyVMRoleService" xmlns="…"><Role name="MachineRole">

<OsImage href="20101020BaseVM.vhd" /><Instances count="2" /><ConfigurationSettings>

<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString“value="DefaultEndpointsProtocol=http;AccountName=mohittest;AccountKey=JEBzeqFeP1g==" />

<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername" value="" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword"

value="" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration"

value="2012-07-23T23:59:59.0000000-07:00" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" />

</ConfigurationSettings> <Certificates>

<Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="195FD938F86D8785FF53C660BCBD283819E0271A" thumbprintAlgorithm="sha1" />

</Certificates></Role>

</ServiceConfiguration>

demo

VM Role – Common QuestionsWill any WS08 R2-based application work?No, VM Role inherits some Web/worker restrictions:SLA requires at least two identical/similar instancesNo durability of OS image on hardware failureOne public IP per service (unless using Windows Azure Virtual Network)

Does Windows Azure take care of *everything*?No, with VM Role, the customer creates & maintains the OS. Windows Azure does not automatically understand the health of the applications running in our VM.But, since you deploy services instead of individual VM’s, Windows Azure does automate many management tasks.

VM Role – Common QuestionsHow will it be priced?It will be priced the same as Web and Worker roles. Customers will be charged at an hourly rate depending on the compute instance size.

How does licensing in the cloud work?Windows: Included in the CPU-hour priceLicensing status of uploaded image is not consideredApplications: Per the licensing terms of the application

© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION

IN THIS PRESENTATION.