1. Infrastructure as a Service
Karl-Heinz Sütterlin
Technology Solution Professional Application Platform
Microsoft Corporation

2. Project Red Dog Launched
How Did We Get Here?
2007
Project Red Dog Launched
PDC2008
Windows Azure CTP
Web/Worker Roles
Partial Trust .NET Only
11/2009
Full Trust/Native
PHP & Java Support
2/2010
Windows Azure RTM
11/2010
VM Role
Connect
Admin Mode
Startup Tasks
Full IIS
Remote Desktop
11/2011
Cross Language SDKs
Java, Node.JS
Eclipse Plugin

3. Windows Azure Virtual Machines
Windows Azure Virtual Machines allow you to easily move your applications and infrastructure back and forth from on-premises to the cloud without requiring any changes to the existing code.
Expanding Windows Azure capabilities to provide infrastructure as a service
Provides us with a full continuum of offerings
Brings us relative parity with Amazon, who focuses on IaaS
IaaS Details
Durable virtual machines with Windows Server or Linux
Commercial and community Linux distributions
Select from a library of images or bring your own
E.g. Select an image with SQL Server
Licensing approach
Support SharePoint, SQL Server & Active Directory within IaaS images
Enable deployments containing both PaaS and IaaS services
Create virtual private networks (VPNs) between on-premise servers and Windows Azure
Single Instance SLA (99.9%)
Planned Upgrade Notification Support
Integration between on-premises and public cloud
Easily create a hybrid virtual private network (VPN) between on-premise servers and Windows Azure
Public / Private cloud symmetry
Write apps to common APIs and services that are available within both Windows Azure and on-premise Windows Server

4. PaaS
SaaS
Physical
Virtual
IaaS
Virtual Machines expand Microsoft’s continuous offering from private to public cloud
If you're in the infrastructure as a service layer (IaaS), you're thinking about your datacenter as a set of pooled virtual resources (including compute, network and storage), not in terms of individual hosts or VMs. That said, you still have to manage the virtual infrastructure, operating system and the full application stack.
When you're in the platform as a service layer (PaaS), you're talking about building applications which will then be delivered as a service – the platform providing all the required building blocks for your app. You don’t have to worry about the underlying infrastructure, operating systems or the application platform infrastructure. You can focus all your energies on your applications. With Windows Azure we primarily offer PaaS but are moving towards robust IaaS capabilities
A couple of data points from internal Microsoft research:
41% of our customers are using services across on premise and public clouds
80% of our customers over next 3 to 5 years will use hybrid models

5. What is IaaS? On Premises Infrastructure Platform Software
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
You manage
Infrastructure
(as a Service)
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
Managed by Microsoft
You manage
Platform
(as a Service)
Managed by Microsoft
You manage
Storage
Servers
Networking
O/S
Middleware
Virtualization
Applications
Runtime
Data
Software
(as a Service)
Managed by Microsoft
Storage
Servers
Networking
O/S
Middleware
Virtualization
Applications
Runtime
Data
Slide Objectives:
Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.
Speaking Points:
Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure.
Packaged Software
With packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications.
IaaS
With Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering.
Very few actually provide an OS
The customer is still responsible for managing the OS through the Applications.
For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines.
This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2).
Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’.
The only requirement was a credit card to pay for the services.
PaaS
With Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor.
The Windows Azure best fits in this category today.
In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.
PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services.
With PaaS, the developer can, almost immediately, begin creating the business logic for an application.
Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.
SaaS
Finally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.
Windows Azure Virtual Machines
Windows Server Hyper-V
Office 365
Dynamics CRM
Windows Server
Windows Azure Cloud Services

6. Why Use Virtual Machines for Existing Applications?
Management
Retain full control to configure & maintain the OS. Manage public & private cloud VMs centrally with Microsoft System Center.
Application Mobility
Move your virtual hard drives (VHDs) back and forth between on-premises and the cloud. No need to rebuild your app to run in the cloud.
Run popular Microsoft server applications
Run the same on-premises enterprise applications & infrastructure in the cloud, such as Microsoft SQL Server

7. Run Popular Microsoft Server Applications
Standalone or connect to on-premises applications. Database mirroring for high availability.
Standalone or connect to AD on-premises through a virtual private network.
Standalone or connect to on-premises applications through a virtual private network.
Update, once all applications have completed testing
Microsoft Distributed Transaction Coordinator - Passed
IIS - Passed
BizTalk
SC AppController 2012
SC Operations Manager 2012
Not Supported:
Lync Sever 2010
Dynamics CRM 2011
Remote Desktop Services
Supported Versions:
SQL Server 2008, SQL Server 2008 R2, & SQL Server 2012
Supported Versions:
Windows Server 2008 R2 & Windows Server 8 Beta
Supported Version:
SharePoint 2010

8. Supported Operating Systems
Windows Server 2008 R2
64-bit
Library Images:
Windows Server 2012
Windows Server 2008 R2 with SQL Server 2008 or (Available at GA)
Supported:
Community & commercial distributions including
Library Images:
OpenSUSE 12.1
CentOS 6.2
Ubuntu 12.04
SUSE Linux Enterprise Server SP2
Linux
*Linux images to be finalized by launch date. Agreements not yet completed.

9. How it Works Select from Image Gallery
Log in to
Windows Azure
Management Portal
Create new VM from
image gallery
The image is copied to
your blob storage account
Virtual Machine booted. Changes copied to blob storage

10. How it Works Bring your own VHD
Create your own VHD
Upload image to blob storage
Create a disk using the uploaded image in the Windows Azure Management Portal
Virtual Machine booted. Changes copied to blob storage

11. What is Meant by Persistent?
Storage
VHD
Within the compute node there are two types of storage. Local disk is available to each Windows Azure role, but this is not persistent. If your role process goes down it may be restarted on another node, so the local disk is not for persistent data. However, XDrives are virtual drives that can be mounted on a Windows Azure VM instance and they are backed by the blob storage system so that they are persistent. The queue system is also part of the persistent Windows Azure storage model.

12. Cross-Premise Connectivity
CLOUD
ENTERPRISE
Data Synchronization
SQL Data Sync
Application-Layer
Connectivity & Messaging
Service Bus
Secure Machine-to-Machine Network Connectivity Windows Azure Connect
Microsoft think about the stack to provide connectivity between on-premise and cloud.
Specifically this deck focuses on the last two layers
FAQ: Diff between Servicebus and Connect
Servicebus vs connect – SB requires app code change, Connect doesn’t. With Connect, all apps can use the connection, With SB – only the app.
Secure Site-to-Site
Network Connectivity
Windows Azure Virtual Network
Windows Azure Networking

13. Bringing Workloads to the Cloud
On Premises
Production
SQL Farm
IIS Servers
AD / DNS
SharePoint
PaaS Roles
S2S VPN tunnels
S2S VPN Device
Exchange
File Servers
Local AD
SQL VMs

14. Example: Contoso’s Deployment
Contoso Production VNet in Windows Azure ( /16)
/24
/24
The Corp. HQ ( /16)
SQL Farm
IIS Servers
AD / DNS
S2S VPN tunnels
Contoso Test in Windows Azure ( /16)
S2S VPN Device
BRK Gateway
Exchange
/24
/24

15. Supported VPN Device List
Cisco
Juniper
Platform
OS Family
Examples
ASA 5500 Series (Adaptive Security Appliances)
ASA Software 8.4+
5505, 5550
ASR 1000 Series Aggregation Services Routers
IOS XE 2.1+
1002
ISR Series Integrated Services Routers
IOS 12.2+
2801, 2901, 2911
Platform
OS Family
Examples
SRX Series Routers
JunOS 10.2+
210, 650
J Series Routers
JunOS 9.4+
4350
ISG Series Routers
ScreenOS 6.2+
SX2
SSG Series Routers
550
Generic VPN devices must support
IKE v1
AES 128, 256
SHA1, SHA2

16. Migrating Active Directory Workloads

17. Domain Controller On-Premises
Contoso Corp Network
IIS Servers
AD / DNS
SQL Servers
Exchange
S2S VPN Device
Contoso.com Active Directory
Contoso.com Active Directory
The Virtual Network
in Windows Azure
Gateway
Site to Site VPN Tunnel
AD Authentication +
On-Premises Resources
IIS Servers
SQL Servers
Load Balancer
Public IP

18. Domain Controller in the Cloud
Contoso Corp Network
IIS Servers
AD / DNS
SQL Servers
Exchange
S2S VPN Device
Contoso.com Active Directory
Contoso.com Active Directory
The Virtual Network
in Windows Azure
Gateway
AD / DNS
AD Auth
Site to Site VPN Tunnel
AD Authentication +
On-Premises Resources
IIS Servers
SQL Servers
Load Balancer
Public IP

19. SharePoint Workloads

20. SharePoint Farm Configuration
WFE
AppSvr
SQL LB
AD/DC/DNS
AD/DC/DNS
Cloud Svc 80
VPN Tunnel
Cloud Svc
Virtual Network
2012
Azure
OnPrem

22. How it Works Scenario 1: Create a new virtual machine from a library image
service package
Sign in to the Windows Azure Management Portal
Click “Create New”, then select “Virtual Machine”
Select the “Base Image” or “OS Disk” (storage)
Base Images include pre-built images
Disk storage includes VHDs you uploaded to your storage account
Select the instance size (XS, S, M, L, XL)
Create the name and admin password
Identify DNS name

23. Comparison of Offerings
Virtual Machines
Stateless VM Role
Launch Date
May 2012
October 2008
Availability
Limited preview
Capability
Durable/persistent state
Stateless
Capability Overview
All changes are written back to the VHD, which is maintained within your storage account. If the virtual machine fails, a new instance comes online and points to the disk in storage
All changes are written locally. If the virtual machine fails, all changes are lost and the new instance points to the original VHD OS
Windows Server 2008 R2, Windows Server 2012, Linux
Windows Server 2008 R2
Agent
No agent required. Leverage SysPrep
(Agent required for Linux)
Agent required
Management
Manage virtual machines within the Windows Azure Management Portal, in the “virtual machines” section
Manage stateless VM roles within the Windows Azure Management Portal, in the “cloud apps” section

24. Benefits of Virtual Machines
easy
open & flexible
powerful
Easily migrate existing applications as-is to the cloud Set up new virtual machines in Windows Azure with only a few clicks (images provided) No need to run an agent when preparing your own VHD. Simply SysPrep. (agent required for Linux)
Upload your own VHD from on-premises
Choose a pre-built image from a library (Windows Server 2008 R2, Windows Server 2012 or Windows Server R2 with SQL Server GA Only)
Support for community and commercial versions of Linux
Run enterprise applications such as SQL Server, SharePoint or Active Directory in the cloud
Create a virtual network between virtual machines in Windows Azure and on- premises virtual machines