Introduction to Windows Azure IaaS

Software & System Engineers

2

Agenda

9:00 9:30 Registration

9:30 9:45 Welcome and Opening Remarks ( Microsoft and AIS)

9:45 10:45 Introduction to IaaS

10:45 11:00 Break

11:00 12:00 Scenario Walkthroughs

Scenarios • Data storage• VMs on demand• Deploying packaged applications• Moving existing applications to the public cloud• Disaster recovery

Ente

rpris

eSM

B

Targ

eted

Cu

stom

ers Force.com

GoogleCompute Engine

Google App Engine

Public Cloud

servicepackage

servicepackage

servicepackage

Server Rack 1 Server Rack 2virtual machine virtual machine

Provision Role Instances Deploy App Code Configure Network

virtual machine virtual machine

servicepackage

Provision Role Instances Deploy App Code Configure Network

servicepackage

Provision Role Instances Deploy App Code Configure Network

Network load-balancer configured for traffic

Provision Role Instances Deploy App Code Configure Network

The changing cloud continuumCO

ST-EFFICIENCY

Simpler M

anagem

ent

PaaS

SaaS

platform as a service

software as a service

IaaSinfrastructure as a service

Virtualizeddata center

CONTROL ABSTRACTION

Manage ALL aspects of the software stack

Supply existing application support

Cloud ServicesVirtual Machines

VMs

Gallery

Worker Roles

WebRoles

VHDs

Compute

User-Supplied

VHDs

Application

Infrastructure as a Service (IaaS)

Platform as a Service (PaaS)

Copyright © 2012 Chappell & Associates

OpenSUSE 12.1

CentOS 6.2

Ubuntu 12.04

SUSE Linux Enterprise Server 11 SP2

Windows Server 2008 R2

SQL Server 2012 Eval

Windows Server 2012 RC

OS COMPONENT WHY NOT SUPPORTED?Hyper-V Hyper-V on Hyper-VDHCP BroadcastNLB BroadcastFailover Clustering “Floating” IPBitlocker (on OS disk) TPM Chip

Per-hour license in the cloud

Bring-Your-Own

Based upon vendor and product

Windows Azure Storage

VM with persistent drive

Windows Azure Storage

VM with persistent drive

Windows Azure Storage

VM with persistent driveHighly Durable Storage

continuous storage geo-replication

WESTDC

EASTDC

> 400 miles

VM with persistent drive

Windows Azure Storage

Geo-Replicated Storage

Windows Azure Storage

Integration: VM ImagesMoving VHDs

ENTE

RPRI

SE

IT Admin Private Cloud

VMVM

VHDs

WIN

DOW

S AZ

URE

Public Cloud

VMVM

VHDs

Windows Azure Virtual Machines

Choose VHD1 Virtual Machine Manager

VHDs

Copy VHD2

App Controller

Disks and ImagesBase OS image for new Virtual MachinesSys-Prepped (Generalized)Read Only Created by uploading or by capture

OS or DataRead/Write Created during provisioning

HyperVisor

VM

OS

Data

Cache

ISO

Cache.VHD

HyperVisor

VM

OS

Cache

Cache.VHD

HyperVisor

VM

OS

Data

Cache

ISO

Cache.VHD

Maximum 127 GB, R/W Cache

Up to 16 disks (XL)Maximum 1 TB each

No cache for performance workloadsOnly 4 disks can have a cache

1 Million for $0.10

100 GB for $12.5/month

Pay for only what you use

When the VM is created, the new VHD is lockedWhen in the library, the VHD is locked

To completely delete, “delete” the disk/image through the portal, then delete through storage.

Windows Azure Storage

Dev/Test Experience

Windows Azure Storage

Dev/Test Experience (Import/Export)

Standalone Virtual MachineCloud Service

LB

ENTE

RPRI

SEW

INDO

WS

AZUR

ENetworking

VPN connection toWindows Azure

Extension of your Data Center

Load-Balanced Sets with probe control

Availability Sets across fault domains

Open 10.* address connectivity

DNS connectivity without a DNS server

ENTE

RPRI

SEW

INDO

WS

AZUR

E

Blobs

Data StorageExample: Using blob storage

1000110100110011110111110110

11010001101

1000110100110011110111110110

11010001101

1000110100110011110111110110

11010001101

1000110100110011110111110110

11010001101

Store backup data

System Center 2012 Data Protection

ManagerCommVault

Store backup data

StorSimple

SAN appliance for hybrid storage

Applications

Store arbitrary binary data, e.g., videos

Moving Existing Applications to the Public CloudExample: Moving a custom application with data on-premises

ENTE

RPRI

SEW

INDO

WS

AZUR

E

Windows Azure Management Portal

Active Directory

Users

VMVMs

ActiveDirectory

CustomApplication

Windows Azure Virtual

Machines

Windows Azure Virtual

Network

DBMS

IT Admin

Moving Existing Applications to the Public CloudExample: Moving a custom application with data on-premises

ENTE

RPRI

SEW

INDO

WS

AZUR

E

Windows Azure Management Portal

Active Directory

Users

VMVMs

ActiveDirectory

CustomApplication

Windows Azure Virtual

Machines

Windows Azure Virtual

Network

DBMS

IT Admin

Moving Existing Applications to the Public CloudWhy do this?

Lower cost EXAMPLETwo medium VMs ($.23/hour each) running continuously

Stores 100 gigabytes Operations on the data:

30,000,000/month Data transfer out: 50

gigabytes/month

COSTSCompute: $335.80/monthStorage: $42.50/month Bandwidth: $6/month (US and Europe)

$9.50 (elsewhere)

Total: $384.30/month (US/Europe)

$387.80 (elsewhere)

$

Making good decisions here requires knowing your current costs

Disaster RecoveryExample: Failing over to Windows Azure

ENTE

RPRI

SEW

INDO

WS

AZUR

E

VM VM

. . .Application

1 DBMSApplication

2 DBMS

VM VMVM VM

Application 2 DBMS

Application 1 DBMS

1 Provision applications, etc. in advance

2 Periodically snapshot data 3 Create VMs and fail

over when needed

Integration: ManagementMonitoring

ENTE

RPRI

SE

IT Admin

WIN

DOW

S AZ

URE

Private CloudVMVM

A A

Public CloudVMVM

A A

Monitor

Monitor

Operations Manager

Integration: ManagementAutomation

ENTE

RPRI

SE

Private Cloud

VMVMA A

Automate

Orchestrator

RunbookVirtual Machine

Manager

WIN

DOW

S AZ

URE

Public Cloud

VMVMA A

WIN

DOW

S AZ

URE

Windows Azure Virtual Machines

Automate

Integration: IdentitySingle sign-on

ENTE

RPRI

SE

Private CloudVMVM

A A

WIN

DOW

S AZ

URE

Public CloudVMVM

A AWindows Azure Active Directory

User

OFF

ICE

365

Exchange Online

SharePoint Online

Lync Online

Windows Server Active

Directory

Login1Access applications2

Access applications3

Management Summary Managing Windows Azure with Systems Center 2012 SP1

Existing capabilities in SC2012

Administer subscriptions

New capabilities in SP1

• Manage Azure subscription using a single view (AC)

• Delegate granular access to subscriptions (AC)

• Manage certs, end-point URLs, subscription IDs (AC)

Move• N/A • Move VMs from on-premises

to Azure, and vice-versa (OC, AC)

Manage• View number of running instances

on Azure (AC)• Perform actions (start, stop, scale

out) (AC)

• Deploy VMs on Azure (AC)• Leverage SPF integration (AC)• Backup running workloads

onto Azure (DPM)

Monitor• Generate insights (e.g., performance

data, events) (OM, AC)• Single view of on-premise and Azure

app performance (OM, AC)

• Leverage outside-in view of service health (OM, AC)

IMPROVED

NEW

IMPROVED

IMPROVED

Extend On- Premises Apps to Azure IaaS

Monitoring Windows Azure Apps with System Center

IaaS PaaS side-by-side

Dev / Test - SharePoint on Azure IaaS

Corp. HQ

Corp. HQ

Dev / Test - SharePoint on Azure IaaS

TFS Integration Build v1

TFS ServerSQL

Developer Workstations

Build Controller Build Drop Location

TFS Integration Build v2 – Local Virtualization

TFS ServerSQL

Developer Workstations

Build Controller Build Drop Location

TFS Integration Build v3 – Azure Virtualization

TFS ServerSQL

Developer Workstations

Build Controller

Build output, additional media

Virtual Machines Blob Storage

• Our competency is application architecture• Unrestricted capacity

– Constraints on resources not limited by other projects– Easily configure and test alternate configuration, edge cases, scale out scenarios

• “Future-proofed”  virtualization  platform• Access to published configured base images

Why we moved to Azure

Highlights

• Uploads latest copy of scripts to blob storage when the script starts.• Connects to each machine via WinRM to download provisioning scripts and build

environment.• Uses Azure Service Bus to coordinate steps between machines so that the entire builds

in order without interaction.• Creates  Storage  Account,  Networks,  etc…  required  to  provision  machine.• Cleans up after itself. Run the script again it can automatically remove the previously

deployed environment.• Build script is entirely PowerShell based. • Using Cerebrata for interaction with Azure storage.• Complete environment build out in under two hours.

Step 1 – No Machines

Step 2 – Provisioning

Step 3 – Machines Provisioned

Step 4 – Build Script Execution

Step 7 – Finished