Slides from AIS and Microsoft's half-day session on the recently-announced Windows Azure Infrastructure as a Service (IaaS) offering. After a brief overview of the Azure Platform as a Service (PaaS) model, we will focus on key IaaS concepts. Additionally, we will walk you through a number of scenarios enabled by Azure IaaS and several demonstrations.
Agenda:
Overview of Windows Azure Platform
Azure IaaS
Why IaaS?
IaaS Core Concepts
Supported Applications
Azure Virtual Machines
Disk Mobility
VM export / Import
Availability
Azure Virtual Network
9. Provision Role Instances
Deploy App Code
Configure Network
service
package
virtual machine virtual machine
virtual machine virtual machine
Server Rack 1 Server Rack 2
10. Provision Role Instances
Deploy App Code
Configure Network
service
package
11. Provision Role Instances
Deploy App Code
Configure Network
service
package
12. Provision Role Instances
Deploy App Code
Configure Network
Network load-balancer
configured for traffic
13.
14.
15. The changing cloud continuum
SaaS
COST-EFFICIENCY
software as a service
Simpler Management
PaaS
platform as a service
IaaS
infrastructure as a service
Virtualized
data center
Supply existing Manage ALL aspects of
application support the software stack
CONTROL ABSTRACTION
19. Windows Server 2008 R2 OpenSUSE 12.1
SQL Server 2012 Eval CentOS 6.2
Ubuntu 12.04
Windows Server 2012 RC
SUSE Linux Enterprise Server 11
SP2
20. OS COMPONENT WHY NOT SUPPORTED?
Hyper-V Hyper-V on Hyper-V
DHCP Broadcast
NLB Broadcast
Failover Clustering “Floating” IP
Bitlocker (on OS disk) TPM Chip
27. Integration: VM Images
Moving VHDs
VM VM
ENTERPRISE
App
1 Choose VHD
Virtual Machine VHDs
Controller Manager
2 Copy VHD Private Cloud
IT Admin
VHDs
WINDOWS AZURE
VM VM
Windows Azure
Virtual Machines VHDs
Public Cloud
28. Disks and Images
Base OS image for new Virtual Machines
Sys-Prepped (Generalized)
Read Only
Created by uploading or by capture
OS or Data
Read/Write
Created during provisioning
33. Maximum 127 GB, R/W Cache
Up to 16 disks (XL)
Maximum 1 TB each
No cache for performance workloads
Only 4 disks can have a cache
34. 1 Million for $0.10
100 GB for $12.5/month
Pay for only what you use
35. When the VM is created, the new VHD is locked
When in the library, the VHD is locked
To completely delete, “delete” the disk/image through the
portal, then delete through storage.
40. Networking
ENTERPRISE
VPN connection to
Windows Azure
Extension of your
WINDOWS AZURE
Data Center
41.
42. Load-Balanced Sets with probe control
Availability Sets across fault domains
Open 10.* address connectivity
DNS connectivity without a DNS server
43.
44.
45. Data Storage
Example: Using blob storage
ENTERPRISE
System Center 2012 Applications
Data Protection CommVault StorSimple
Manager
SAN appliance for Store arbitrary binary
Store backup data Store backup data data, e.g., videos
hybrid storage
WINDOWS AZURE
10001101001100 10001101001100 10001101001100 10001101001100
11110111110110 11110111110110 11110111110110 11110111110110
11010001101 11010001101 11010001101 11010001101
Blobs
46. Moving Existing Applications to the Public Cloud
Example: Moving a custom application with data on-premises
ENTERPRISE
Active Windows Azure
DBMS
Directory Management Portal
IT Admin
Users
Windows Azure Windows Azure
WINDOWS AZURE
Virtual Virtual
Custom Active Machines Network
Application
Directory
VMs VM
47. Moving Existing Applications to the Public Cloud
Example: Moving a custom application with data on-premises
ENTERPRISE
Active Windows Azure
DBMS
Directory Management Portal
IT Admin
Users
Windows Azure Windows Azure
WINDOWS AZURE
Virtual Virtual
Custom Active Machines Network
Application
Directory
VMs VM
48. Moving Existing Applications to the Public Cloud
Why do this?
$ Lower cost
EXAMPLE
Two medium VMs ($.23/hour
COSTS
Compute: $335.80/month
each) running continuously Storage: $42.50/month
Bandwidth: $6/month (US and Europe)
Stores 100 gigabytes $9.50 (elsewhere)
Operations on the data:
30,000,000/month Total: $384.30/month
Data transfer out: 50 (US/Europe)
gigabytes/month $387.80 (elsewhere)
Making good decisions here requires
knowing your current costs
49. Disaster Recovery
Example: Failing over to Windows Azure
ENTERPRISE
Application Application
1 DBMS 2 DBMS
...
VM VM
Provision Periodically Create VMs and fail
1 applications, etc. in 2 snapshot data 3 over when needed
advance
WINDOWS AZURE
Application Application
1 DBMS 2 DBMS
VM VM VM VM
51. Integration: Management
Automation
Orchestrator
ENTERPRISE
Virtual Machine A A
Runbook Automate Manager VM VM
Private Cloud
WINDOWS AZURE
Automate
Windows Azure A A
Virtual Machines
VM VM
Public Cloud
52. Integration: Identity
Single sign-on
Access
ENTERPRISE
Windows 1 Login 2 applications A A
Server Active
Directory User VM VM
Access
applications
Private Cloud
3
Exchange Online
WINDOWS AZURE
Windows Azure
A A
OFFICE 365
Active Directory
SharePoint Online
VM VM
Lync Online Public Cloud
53. Management Summary
Managing Windows Azure with Systems Center 2012 SP1
Existing capabilities in SC2012 New capabilities in SP1
• Manage Azure subscription using • Manage certs, end-point
Administer
a single view (AC) IMPROVED URLs, subscription IDs (AC)
subscriptions
• Delegate granular access to
subscriptions (AC)
• N/A • Move VMs from on-premises
Move NEW to Azure, and vice-versa (OC,
AC)
• View number of running instances • Deploy VMs on Azure (AC)
Manage on Azure (AC) IMPROVED • Leverage SPF integration (AC)
• Perform actions (start, stop, scale • Backup running workloads
out) (AC) onto Azure (DPM)
• Generate insights (e.g., performance • Leverage outside-in view of
Monitor data, events) (OM, AC) IMPROVED service health (OM, AC)
• Single view of on-premise and Azure
app performance (OM, AC)
54. 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
63. Why we moved to Azure
• 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
64. 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.