it camp: windows server 2012 and windows azure iaas overview

Harold Wongblogs.technet.com/haroldwong@haroldwong

Windows Server 2012 Beyond VirtualizationEnabling Hyper-V over SMB

Enabling Hyper-V over SMB

Why should I care?

Technology Overview

Demo

Next Steps

Enabling Hyper-V over SMB

• Is a network file sharing protocol that allows applications on a computer to read and write to files and to request services from server programs in a computer network

• Windows Server 2012 introduces the new 3.0 version of the SMB protocol

Hyper-V over SMB

With Windows Server 2012, Hyper-V…

• Can store virtual machine files (configuration, VHD, snapshots) in files shares over the SMB 3.0 protocol

• Is supported for both stand-alone and clustered servers that use Hyper-V with shared file storage for the cluster

• Can support scale-out file shares and clusters• Can leverage SMB Multi-Channel

Server Message Block (SMB) protocol…

Enabling Hyper-V over SMBWhy should I care?

Why should I care?

• Ease of provisioning and management• You can manage file shares instead of storage fabric and logical unit

numbers (LUNs).• Increased flexibility

• You can dynamically migrate virtual machines or databases in the data center.

• Ability to take advantage of existing investment in a converged network • You can use your existing converged network with no specialized

storage networking hardware.• Reduced capital expenditures

• Capital expenses (acquisition costs) are reduced.• Reduced operating expenditures

• You can reduce operating costs because there is no need for specialized storage expertise.

Enabling Hyper-V over SMBTechnical Overview

• One or more computers running Windows Server 2012 with the File Services role installed

• One or more computers running Windows Server 2012 with the Hyper-V role installed (separate from the file server)

• A common Active Directory infrastructure• The servers running Active Directory Domain Services (AD DS) do

not need to run Windows Server 2012• Supported configurations

• Standalone Hyper-V servers (no a high-availability solution)• Hyper-V servers configured in a Failover Cluster

Requirements

Although not required, Failover Clustering is supported on the Hyper-V side, the File Services side, or both. They must be separate clusters.

Common Configurations

Single-Node File Server• Lowest cost for share

storage• Shares not continuously

available

Dual-Node File Server• Low cost for continuously

available shared storage• Limited scalability (up to a

few hundred disks

Multi-Node File Server• Highest scalability (up to

thousands of disks)• Higher cost, but still lower

than connecting all Hyper-V hosts with FC

1. Install the Hyper-V role on a Windows Server 2012 machine

2. Install the File Services role on a Windows Server 2012 machine

3. Create an SMB file share

4. Create a virtual machine and virtual machine hard disk on the file share

5. Migrate existing virtual machine storage to the file share

Hyper-V Over SMB Workflow

Creating an SMB ShareFrom Server Manager:

1. Log on or connect to a Windows Server 2012 computer on which the File and Storage role is installed. Open Server Manager and navigate to File and Storage Services

2. In Server Manager, start the New Share Wizard# Create folder MD X:\VMS # Create file share New-SmbShare -Name VMS1 -Path X:\VMS -FullAccess Domain\HVAdmin, Domain\HV1$, Domain\HV2$, Domain\HVC$ # Set NTFS permissions from the file share permissions (Get-SmbShare VMS1).PresetPathAcl | Set-Acl

With PowerShell:

2

1

Migrating Storage to an SMB Share

1. To determine the current storage being used by a virtual machine:

2. To migrate the virtual machine storage to an SMB file share:

3. To confirm migration:

Get-VM VM1 | FT Name, Path, State Get-VMHardDiskDrive VM1 | FT VMName, Path

Move-VMStorage –VMName VM1 –DestinationStoragePath \\FST\VMS

Get-VM VM1 | FT Name, Path, State Get-VMHardDiskDrive VM1 | FT VMName, Path

You can migrate from…• Direct-Attached Storage to SMB file

share• SMB file share to another SMB file

share

Enabling Hyper-V over SMBDEMO

Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012

System Center 2012 Evaluation Download http://aka.ms/hwsc2012

SMB 3.0 Overviewhttp://technet.microsoft.com/en-us/library/hh831795.aspx

Microsoft Virtual Academyhttp://aka.ms/virtualacademy

Windows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx

http://aka.ms/hwws2012

http://aka.ms/hwsc2012


http://technet.microsoft.com/en-us/library/hh831795.aspx


http://aka.ms/virtualacademy

http://technet.microsoft.com/en-us/windowsserver/hh968267.aspx



Windows Server 2012Beyond VirtualizationHyper-V Replica

What is Hyper-V Replica?

Why should I care?

Technology Overview

Demo

Next Steps

Hyper-V ReplicaWhat is it?

What is Hyper-V Replica?A virtual machine level replication solution which efficiently replicates data over a LAN/WAN to a remote (Replica) site without relying on software or hardware technologies outside of the Windows Server 2012 operating system• New in Windows Server 2012 Hyper-V Role• Storage and Workload agnostic• Servers can be standalone or members of a Failover

Cluster• Servers can be members of a workgroup or a domain

(same or different); Primary and Replica servers do not need to be in the same domain unless part of a Failover Cluster

• Managed locally (Hyper-V Manager) or remotely (Hyper-V Remote Server Administration Tools (RSAT) or System Center Virtual Machine Manager (SCVMM)

• 4 Deployment Scenarios• Head Office and Branch Office (HO-BO)• Enterprise Datacenter• Hosting Provider Datacenter• Customer Office and Hosting Provider Datacenter

(Cross-Premise)

Hyper-V ReplicaWhy should I care?

Why should I care?

Hyper-V Replica provides an efficient, cost-effective solutions…

• Allows a Hyper-V administrator to execute a failover of production workloads to replica servers at a secondary location within minutes (in the event of fire, power outage, server failure, etc.)

• Provides the necessary management APIs to enable IT management vendors to build an enterprise class Disaster Recovery solution for customers

• Enables Infrastructure as a Service (IaaS) for hosting providers that host dedicated/virtual servers for customers

• Seamlessly integrates with Clustering and Volume Shadow Services (VSS)

• Supports heterogeneous storage between primary and recovery

The challenge…

• Provide business continuity and minimal downtime of virtualized servers during times of disruption

Hyper-V ReplicaTechnical Overview

Installation Requirements

• Hardware that supports the Hyper-V Role on Windows Server 2012• Sufficient storage on both Primary and Replica servers to host the

files used by virtualized workloads• Network connectivity between the locations hosting the Primary and

Replica servers• Properly configured firewall rules to permit replication between the

Primary and Replica sites• An X.509v3 certificate to support Mutual Authentication with

certificates (if desired or needed)• For detailed certificate requirements, see http://blogs.technet.com/b/virtualization/archive/2012/03/13/hyper-v-replica-certificate-requirements.aspx

http://blogs.technet.com/b/virtualization/archive/2012/03/13/hyper-v-replica-certificate-requirements.aspx



Installation and Configuration

2. Run Best Practices Analyzer to confirm installation and verify functionality

3. Configure Replication • Standalone• Failover Cluster

4. Enable each Virtual Machine for replication (Enable Replication Wizard)

5. Or use PowerShell

Set-VMReplicationServer -ReplicationEnabled $true -AllowedAuthenticationType Integrated -IntegratedAuthenticationPort $RecoveryPort -DefaultStorageLocation $ReplicaStorageLocation -ReplicationAllowedFromAnyServer $true

1. Add Hyper-V role on Primary and Replica servers • Add Role and Feature Wizard (ARFW) in Server

Manager• Deployment Image and Service Management (DISM)

dism /online /enable-feature

/featurename:Microsoft-Hyper-V

• Server Manager Powershell cmdletInstall-WindowsFeature –Name Hyper-V –

IncludeManagementTools

3

4

Architectural Components

Hyper-V ReplicaDEMO



Hyper-V Replica Overviewhttp://technet.microsoft.com/en-us/library/jj134172.aspx






http://technet.microsoft.com/en-us/library/jj134172.aspx





Windows Server 2012 Beyond VirtualizationHyper-V Scalability

Windows Server 2012 Hyper-V Scalability Improvements

Why should I care?

Technology Overview

Demo

Next Steps

Windows Server 2012 Hyper-VScalability

Windows Server 2012 Hyper-V Scalability Improvements

• Expanded processor and memory support• Virtual Non-Uniform Memory Access (NUMA)• Network Adapter Hardware Acceleration• Offload Data Transfer (ODX)• Support for 4 KB sector disks• Virtual Fibre Channel• SMB 3.0• Improved VM Import• VHDX disk format

Windows Server 2012 Hyper-V ScalabilityWhy should I care?

Why should I care?Enhanced support for high-performance hardware configurations in Windows Server 2012 Hyper-V…

• Provides more options for IT organizations for deploying a wider range of enterprise applications in virtualized environments

• Increases support for high-performance processor and memory configurations, which in turn help support the deployment and operation of mission-critical applications on virtualized systems

Windows Server 2012 Hyper-V ScalabilityTechnical Overview

Expanded Processor & Memory Support

System Resource

Maximum NumberImprovement

FactorWindows

Server 2008 R2

Windows Server 2012

Host

Logical processors on hardware 64 320 5x

Physical Memory 1 TB 4 TB 4x

Virtual processors per host 512 2,048 4x

Virtual Machine

Virtual processors per virtual machine 4 64 16x

Memory per virtual machine 64 GB 1 TB 16x

Active virtual machines per server 384 1,024 2.7x

ClusterNodes 16 64 4x

Virtual machines 1,000 4,000 4x

Virtual NUMAVMs are NUMA-aware

• Dynamic memory cannot be configured on the host

• Performance of applications like SQL Server are significantly better

• Support extends into high-availability solutions built using Windows Server 2012 Failover Clustering How NUMA works…

• Guest OS and applications make intelligent decisions about thread and memory allocation

• Decisions are reflected in the physical NUMA topology of the host

Network Adapter Hardware AccelerationVirtual Machine Queue (VMQ)

• Employs hardware packet filtering to deliver packets from an external VM network directly to VMs using DMA transfers

IPsec task offload• Reduces the load on the system’s

processors by IPsec encryption/decryption using a dedicated processor on the network adapter

Single-Root I/O virtualization (SR-IOV)• Enables a device to divide access to

its resources among various PCIe hardware functions

SR/IOV

IPSec Offload

VMQ

Offload Data Transfer (ODX)

A feature of high-end storage arrays that uses a token-based mechanism to read and write data within and between arrays

Support for Large Sector Disks

To meet demands for increased disk capacity, Windows Server 2012 supports…

• 512-byte sector format is replace by 4,096-byte (4 KB) format

Hyper-V in Windows Server 2012…• Supports hosting VHD files on native

4 KB format or 512-byte emulation (512e) mode

• Mitigates the RMW impact when accessing data within VHD files and when updating metadata structures

Read-Modify-Write (RMW)1. The disk reads the 4 KB physical

sector into its internal cache, which contains the 512-byte logical sector referred to in the write

2. Data in the 4 KB buffer is modified to include the updated 512-byte sector

3. The disk performs a write of the updated 4 KB buffer back to its physical sector on the disk

Dynamic Memory Improvements

• New Minimum Memory setting• Minimum/Maximum memory settings can be modified while VM is

running

PowerShell configuration: Set-VM cmdlet

Memory Settings Smart Paging

Viewing Dynamic Memory

Hyper-V Manager console redesigned for improved display of Dynamic Memory real-time measurements – No Scrolling!

Get-VM cmdlet

Virtual Fibre ChannelProvides Fibre Channel ports within the guest operating system of VM

• Drivers for your HBAs must support Virtual Fibre Channel• Connects only to LUNs - a LUN cannot be used as boot media for

VMsAllows for new scenarios

• Example: running the Failover Clustering feature inside the guest operating system of a virtual machine connected to shared Fibre Channel storage

Protects existing investments• Allows you to use any advanced storage functionality of an existing

SAN directly from VMs Includes support for many related features

• Virtual SAN• Live Migration• Multipath I/O (MPIO)

• Use for host access• Virtualize workloads that use MPIO• Use different device specific modules (DSMs) for the host or

each virtual machine

SMB 3Improvements in SMB 3 are designed to provide increased performance, reliability, and availability in scenarios where data is stored on file sharesSMB Direct

• Provides remote storage solutions equivalent in performance to Fibre Channel, but at a lower cost

SMB Directory leasing• Improves application response time by reducing round-trips from

client to serverSMB Encryption

• Protects network traffic from eavesdropping when travelling over untrusted networks

SMB Multichannel• Server applications become more resilient to network failure

Improved VM ImportTo help prevent configuration problems that prevent the import process from completing successfully

• Configuration validation during import• Can manually copy VM files between hosts and then import them

• No need to export first!• Improved Import wizard

VHDX Disk FormatNew default format for VHDs in Hyper-V in Windows Server 2012

• Supports virtual disks up to 64 TB• Aligns to megabyte boundaries to support large sector disks (4 KB

sector disks)• Uses large block sizes to provide better performance • Includes a new log to protect from corruption due to power failure• Has much greater resiliency• Allows for embedded custom user-defined metadata into VHDX files

Windows Server 2012 Hyper-V ScalabilityDEMO



Hyper-V Support for Scaling Up and Scaling Out Technical Previewhttp://technet.microsoft.com/en-us/library/hh831389.aspx












Windows Server 2012 Beyond VirtualizationShared Nothing Live Migration

What is Shared Nothing Live Migration?

Why should I care?

Technology Overview

Demo

Next Steps

Shared Nothing Live MigrationWhat is it?

Shared Nothing Live Migration

The ability to move a virtual machine while it is powered on from one host to another without requiring shared storage

• Faster and simultaneous migration• Entire VM moved with no downtime

• VHD, configuration files, snapshots, etc.

• Improved performance and flexibility• No longer requires a clustered environment or shared storage*

* Live Migration can be done with shared storage and clustered VMs, but “Shared Nothing” uses neither

Shared Nothing Live MigrationWhy should I care?

Why should I care?

The Windows Server 2012 solution…

• Shared nothing means the hosts needs to share nothing but a simple Ethernet connection to each other

• Data is migrated without the need for a costly infrastructure• No devices are required to assist with buffering

The challenge…

• In Windows Server 2008 R2, migration of Hyper-V data required a shared infrastructure

• Implementing shared storage and failover clustering can be expensive

• In order to migrate data from one host to another, both had to have a simultaneous connection to a shared storage device that could buffer data

Shared Nothing Live MigrationTechnical Overview

Live Migration – Moving a Running VM without Shared Storage

1. Live Migration setup occurs

2. Memory pages are transferred from the source server to the destination server

3. Modified pages are transferred to destination server

4. State is transferred to destination server

5. VM brought online on destination server

6. Network cleanup occurs

standard Ethernet connection

Configuring Live Migration

Performing Live Migration

1

Start the Move

2 Choose Move Type

Performing Live Migration, (Cont.)

3

Select Items4 Select storage move options

5

Choose new location



7

Summary Info

6

Migration begins

Shared Nothing Live MigrationDEMO



Live Migration Shared Nothing Video http://www.aidanfinn.com/?p=12287






http://www.aidanfinn.com/?p=12287





Windows Server 2012 StorageStorage Spaces and Thin Provisioning

Harold Wong

Storage Spaces and Thin Provisioning Overview

Why should I care?

Technology Overview

Demo

Next Steps

Storage Spaces and Thin ProvisioningOverview

What is Storage Spaces & Thin Provisioning?Storage Spaces

• New in Windows Server 2012• Provides an in-box storage virtualization that can use low-cost commodity

storage devices• Aggregates unallocated space on physical disks installed in or connected to

servers through a “pooling” model• Can provide a cost-effective platform for business critical storage across a

variety of scenariosThin Provisioning• “Just-in-Time” allocations of storage with the ability to reclaim storage (“Trim”)• Integrated with Storage Spaces

Storage Spaces and Thin ProvisioningWhy should I care?

Why should I care?

Storage pools• Can be mapped to combinations of hard disks as well as solid-state

drives (SSDs)• Can be expanded dynamically by simply adding additional drives,

thereby seamlessly scaling to cope with unceasing data growthMultitenancy

• Administration of storage pools can be controlled through access control lists (ACLs) and delegated on a per-pool basis

• Can be fully integrated with Active Directory Domain ServicesResilient storage

• Storage Spaces support two optional resiliency modes (mirroring and parity)

• Per-pool support for disks that are reserved for replacing failed disks (hot spares), background scrubbing, and intelligent error correction allow continuous service availability despite storage component failures

The features of Storage Spaces are designed to meet a variety of challenges in support of highly-available storage

Why should I care? (cont.)Continuous Availability

• Failover clustering integration delivers continuously available service deployments

• One or more pools can be clustered across multiple nodes within a single cluster. Storage spaces can then be instantiated on individual nodes, and the storage will seamlessly fail over to a different node when necessary (in response to failure conditions or due to load balancing)

• Integration with CSVs permits scale-out access to dataOptimal storage use through thin provisioning

• To allow businesses to easily share storage capacity among multiple unrelated data sets and thereby maximize capacity use

• Trim support permits capacity reclamation when possibleOperational simplicity

• Easily managed through the File Services role in Server Manager• Fully remoteable and scriptable management through the Windows

Storage Management API, WMI, and Windows PowerShell• Designed to be compatible with existing backup-restore and cloning

tools, as well as snapshotting infrastructures

Storage Spaces and Thin ProvisioningTechnical Overview

Storage Spaces Requirements

• The criterion for determining which drives are eligible to be part of a Pool are:• Minimum drive size is 10 GB• Drive is empty, i.e. no partition data exists on the drive• Drive is not assigned to any other pool

• The Primordial Pool will consist of Physical Disks that are not assigned to any existing Storage Pool

• Windows Server 2012• Serial ATA (SATA) or Serial Attached SCSI

(SAS) connected disks (in an optional just-a-bunch-of-disks [JBOD] enclosure)

• Multinode clustered shared-storage deployments• Two or more servers running Windows

Server 2012• Requirements as specified for failover

clustering and Windows CSV • SAS connected JBODs that comply with

Windows Certification requirements

Drive Type

Stand-Alone File Servers

Clustered File Servers

SATA Supported

SCSI Supported

iSCSI Supported Supported

SAS Supported Supported

USB Supported

How does Storage Spaces Work?

An example…

Drive array presenting 4 100GB LUNs

Disk Management show the 4

disks online and initialized

Primordial Pool is populated in

the File and Storage Services Interface

Process of Handling Resources

Storage Spaces Management Interface

Configuring a Storage Pool

4

21

3New-StoragePool

Creating a Storage Space (Virtual Disk)

1. Select a pool and specify a

name

2. Choose between simple

or redundant virtual disk

3. Choose between

fixed or thin provisioning

4. Create Volumes

Data Redundancy in Storage Spaces

Redundancy Type

Description

Simple • Data is striped across physical disks• Maximizes capacity • Increases throughput

Mirror • Data is duplicated on two or three physical disks• Increases reliability• Reduces capacity by 50 to 66 percent

Parity • Data and parity information are striped across physical disks

• Increases reliability• Reduces capacity by 13 to 33 percent

Deduplication• Capacity Optimization• Scale and Performance• Reliability and Data Integrity

Enable & Configure

Deduplication on volume

Start-DedupJob –type optimization –Volume E:

Saved Space

Managing Storage with PowerShell

Parameters configured with GUI and PowerShell• Underlying storage pool name • Virtual disk name • Resiliency setting (Simple, Mirror, or parity) • Provisioning type (Thin or Fixed) • Virtual disk size

Parameters configured only with PowerShell• Number of columns: the number of columns

the virtual disk contains • Number of data copies - number of

complete copies of data that can be maintained

• Disk interleave - number of bytes forming a stripe

• Physical disks to use - specific disks to use in the virtual disk

PowerShell is required to access many of the advanced features afforded by the new Storage Management application programming interface (API)

Example: New-StoragePool

Integrating Storage Pools with Failover Clustering

• Clustered Storage Spaces require fixed provisioning

• Clustered virtual disks require underlying hardware to support persistent reservations

Thin Provisioning and Trim

Requirements• Enabled by default in Windows Server 2012• Storage infrastructure that complies with the certification that is required for

Windows Server 2012 • Standards-compliant hardware for identification

Capabilities• Identification

• Windows Server 2012 uses a standardized method to detect and identify thinly provisioned virtual disks

• Notification• When configured physical storage use thresholds are reached, Windows

Server 2012 notifies the administrator through events; events can be used for automated actions by sophisticated management applications, such as Microsoft System Center

• Optimization• Windows Server 2012 provides a new API that lets applications return

storage when it is no longer needed. • NTFS issues trim notifications in real time when appropriate.• Trim notifications are issued as part of storage consolidation (optimization),

which is performed regularly on a scheduled basis

Storage Spaces and Thin ProvisioningDEMO



Understanding and Troubleshooting Storage Spaceshttp://www.microsoft.com/en-us/download/details.aspx?id=29002






http://www.microsoft.com/en-us/download/details.aspx?id=29002







Windows Server 2012 Management and InfrastructureContinuously Available File Shares

Harold Wong

Continuously Available File Shares

Why should I care?

Technology Overview

Demo

Next Steps

Continuously Available File Shares What is it?

Scale-Out File Services/Shares

Allow you to scale the capacity of file servers upward or downward dynamically by using Failover Clustering with…

CSV File System (CSVFS)• Appears as a single

consistent file namespace, although the underlying file system remains NTFS

• Allows direct I/O for file data access and supports sparse files

• Allows encryption through BitLocker

• Backups of CSV no longer require redirected I/O

• Supports SMB 3.0 features

SMB 3.0• SMB Scale Out• SMB Transparent Failover• SMB Multichannel• SMB Direct• SMB Performance Counters for

Server Applications• SMB Performance Optimizations• SMB Management with Windows

PowerShell• SMB Remote File Storage

Continuously Available File Shares Why should I care?

Why should I care?

The solution…

• The File Server Role has been expanded to include a new scenario where application data (specifically Hyper-V and SQL Server) is supported on highly available SMB shares

• Provides access with almost zero downtime

The challenge…

• Prior to Windows Server 2012, highly available file services were provided by failover cluster Client Access Point (CAP) that clients could use to connect to SMB (Server Message Block) or Network File System (NFS) shares on physical disk resources

• If you deployed a shared-nothing cluster, only one node in a cluster File Server group could be online

• In the event of a failure or if the File Server group was moved to another cluster node, clients were disconnected and had to reconnect when the group became available on an online node in the cluster

Continuously Available File Shares Technical Overview

Continuously Available File Servers

General Use File Server• Almost identical to Windows Server 2008 R2• Shares can be made continuously available with the help of the SMB 3.0 protocol

Scale Out File Server • Provides continuously available file services for application data • Responds to increased demands quickly by bringing more servers online

• Takes advantage of new features in Windows Server 2012 Failover Clustering

• Distributed Network Name (DNN)• Cluster Shared Volumes Version 2 • Scale Out File Server role (must be enabled on all nodes in the

cluster• Clusters of Scale Out File Servers are limited to 4 servers

Continuously Available Scale Out File Server Architecture

Cluster platform for a continuously available scale out file server• Cluster-wide client access point • Consistent cluster-wide file server configuration• CSV cluster-wide file system

Zero client downtime failover – both planned and unplanned downtime

Single Logical Server (\\Foo\Share)

Accessing VHDs over SMB Hyper-V Cluster

File Server Cluster

Single File System Namespace

Cluster Shared Volumes

Installing and Configuring the General Use File Server Role

1

From Failover Cluster Manager…High Availability Wizard

2

Installing and Configuring the General File Server Role

3

From Failover Cluster Manager…Add File Share

4

Installing the General Use File Server Role (cont.)

65

Installing the Scale Out File Server Role

3

From Failover Cluster Manager…High Availability Wizard

4

Installing the Scale Out File Server Role (Cont.)

3

4

From Failover Cluster Manager…Add File Share

5

Continuously Available File Shares DEMO



High-Performance, Continuously Available File Share Storage for Server Applications Technical Previewhttp://technet.microsoft.com/en-us/library/hh831399.aspx












Windows AzureInfrastructure as a Service

Harold Wong

How Did We Get Here?

2007 Project Red Dog

Launched

PDC2008Windows Azure CTPWeb/Worker Roles

Partial Trust .NET Only

11/2009 Full Trust/Native

PHP & Java Support

2/2010 Windows Azure RTM

11/2010 VM RoleConnect

Admin Mode Startup Tasks

Full IISRemote Desktop

11/2011Cross Language SDKs

Java, Node.JSEclipse Plugin

Infrastructure as a Service

The spring release of Windows Azure Infrastructure

as a Service introduces new functionality that allows

full control and management of virtual machines

along with an extensive virtual networking offering.

If deploying an application requires a developer’s involvement, it’s not IaaS

Cloud Models On Premises

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

You m

an

ag

e

Infrastructure(as a Service)

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

Man

ag

ed

by M

icroso

ft

You m

an

ag

e

Platform(as a Service)

Man

ag

ed

by M

icroso

ft

You m

an

ag

e

Storage

Servers

Networking

O/S

Middleware

Virtualization

Applications

Runtime

Data

Software(as a Service)

Man

ag

ed

by M

icroso

ft

Storage

Servers

Networking

O/S

Middleware

Virtualization

Applications

Runtime

Data

PaaS SaaSPhysical Virtual IaaS

A Continuous Offering From Private to

Public Cloud

Windows Azure Virtual Machines

IT Pro experience

Support for key server applications

Easy storage manageability

High availability features

Advanced networking

Integration with compute PaaS

If it requires a developer, it’s not IaaS

Virtual Machine vs VM Role

VM Role Virtual Machine

Storage Non-Persistent Storage Persistent StorageEasily add additional storage

Deployment Build VHD offsite and upload to storage.

Build VHD directly in the cloud or build the VHD offsite and upload

Networking Internal and Input Endpoints configured through service model.

Internal Endpoints are open by default.Access control with firewall on guest OS. Input endpoints controlled through portal, service model or API/Script.

Primary Use Deploying applications with long or complex installation requirements into stateless PaaS applications

Applications that require persistent storage to easily run in Windows Azure.

Images Available at Preview

OpenSUSE 12.1OpenLogic CentOS 6.2 Ubuntu 12.04 LTSSUSE Linux Enterprise Server SP2

Windows Server 2008 R2 SP1

Biztalk Server 2010 R2 CTP

Windows Server 2008 R2 with• SQL Server 2012 Eval

Windows Server 2012 RTM

WindowsLinux

Current Plans – Specific Distributions Subject to Change

Virtual Machine Sizes

Each Persistent Data Disk Can be up to 1 TB

VM Size CPU Cores Memory Bandwidth# Data Disks

Extra Small

Shared 768 MB 5 (Mbps) 1

Small 1 1.75 GB 100 (Mbps) 2

Medium 2 3.5 GB 200 (Mbps) 4

Large 4 7 GB 400 (Mbps) 8

Extra Large

8 14 GB 800 (Mbps) 16

Persistent Disks and Highly Durable

Windows Azure Storage

Windows Azure Storage (Disaster Recovery)

Virtual Machine

Persistent Disks and Highly Durable

Windows Azure Storage

Windows Azure Storage (Disaster Recovery)

Virtual Machine

Virtual Machine

Disks and ImagesOS Images

• Microsoft• Partner • User

Disks

• OS Disks • Data Disks

Base OS image for new Virtual MachinesSys-Prepped/Generalized/Read Only Created by uploading or by capture

Writable Disks for Virtual MachinesCreated during VM creation or during upload of existing VHDs.

Cross-premise Connectivity

IP-level connectivity

Data SynchronizationSQL Azure Data Sync

Application-layer Connectivity & Messaging

Service Bus

Secure Machine-to-Machine Network Connectivity

Windows Azure Connect

Secure Site-to-Site Network Connectivity

Windows Azure Virtual Network

CLOUD ENTERPRISE

Corpnet

Windows Azure Virtual Network

Your “virtual” branch office / datacenter in the cloudEnables customers to extend their Enterprise Networks into Windows AzureNetworking on-ramp for migrating existing apps and services to Windows AzureEnables “hybrid” apps that span cloud and their premises

A protected private virtual network in the cloudEnables customers to setup secure private IPv4 networks fully contained within Windows AzureIP address persistenceInter-service DIP-to-DIP communication

Subnet 2

Subnet 1

Windows Azure Virtual Network ScenariosHybrid Public/Private CloudEnterprise app in Windows Azure requiring connectivity to on-premises resources

Enterprise Identity and Access ControlManage identity and access control with on-premises resources (on-premises Active Directory)

Monitoring and ManagementRemote monitoring and trouble-shooting of resources running in Windows Azure

Advanced Connectivity RequirementsCloud deployments requiring persistent IP addresses and direct connectivity across services

Bringing Workloads to the Cloud

On Premises

Production

S2S VPN Device

IIS Servers

AD / DNS

SQL Farm

Exchange

S2S VPN tunnelsSharePoin

tPaaS Roles

File Servers Local AD SQL VMs

PaaS SaaSPhysical Virtual IaaS

IaaS and PaaS – Better Together

The Benefits of PaaSA summary

PaaS is fasterReason: There’s less work for developers to doBenefit: Applications can go from idea to availability more quicklyPaaS is cheaperReason: There’s less admin and management work to doBenefit: Organizations spend less supporting applicationsPaaS lowers riskReason: The platform does more, leaving fewer opportunities for errorBenefit: Creating and running applications gets more reliable

IaaS and PaaS Side by Side

Connect Cloud Apps via VIPs• Easily compose services by connecting public

endpoints

Direct Connectivity Using Virtual Networking• For advanced connectivity scenarios such as

Active Directory or DCOM

Mixed Mode: Apps and VMs in the Same Cloud Service• Simple, secure and highly efficient method of using

IaaS and PaaS side-by-side

Connecting Cloud Services via VIPs

StrengthsSimplicityTenant AutonomyVIP Swap (stateless roles)Easy Local Dev/TestPersistent Service is Easily Accessible (even from other services!)

SQL Data Access Traffic Through Public Endpoint

WeaknessesHigher LatencyLess SecureManagement/Deployment Overhead

WA Web Role

Cloud Service 1

Cloud Service 2

SQL Server

Load Balancer

80

2001-1433

Secure Endpoints with Windows Server Firewall

Load Balancer

Connecting Cloud Services with VNETStrengthsMore SecureLow LatencyCloud App AutonomyVIP Swap (stateless roles)Advanced Connectivity Requirements

WeaknessesVNET ComplexityNo Windows Azure provided DNS

Direct Access

via VNET

FrontEndSubnet (10.0.0.0/16)

SQLSubnet (10.1.0.0/16)

Load Balancer

80

WA Web Role

Cloud Service1

Cloud Service 2

AD

SQL Mirror

AD Subnet

(10.2.0.0/16)

ContosoVNet (10.0.0.0/8)

Mixed Mode: PaaS/IaaS in the Same Cloud ServiceStrengthsWindows Azure provided DNSLow latency connectivitySingle deployment, update and management unit

WA Web Role

Virtual Machine

Load Balancer

80

Cloud Service

Available in Fall Release

WeaknessNo VIP Swap (coming in the future)

Demo

Windows Azure Portal, Creating a Virtual Machine



Windows Azure 90 Day Trialhttp://aka.ms/hwazuretrial





http://aka.ms/hwazuretrial


