Post on 24-Dec-2015
transcript
Migration Approaches
Build Virtual Machine in the Cloud• Lowers upload time and dependency risk• Requires upload and installation of application and data
Migrating an Existing Virtual Machine• Application, Configuration and Data in an installed Working State • Requires uploading a large amount of data and a higher risk of drivers or other
hardware dependencies on VM not available in the cloud
Migrating a Multi-VM Application
Cloud Service Acts as a Networking Boundary• All VMs in the same service can communicate directly• Name resolution between VMs is automatic with Windows Azure provided DNS
Cloud ServiceName: myapp1.cloudapp.net
Virtual MachineVM Name: iisvm110.1.5.6
Virtual MachineVM Name: iisvm210.1.5.7
DIP
Virtual MachineVM Name: sqlvm110.1.5.8
DIP DIP
Load BalancerPublic IP
Virtual Machine Migration
Windows Azure Supports VHD File Format• Other formats will have to be converted or migrated before upload
Upload Existing VHDs using PS (Add-AzureVHD)• Supports Resuming Failed Transfers • Converting from Dynamic to Fixed Disk on Upload• Efficient Upload – does not send empty bytes
Things to Do Before Uploading OS Disk• Enable Remote Access
Migrating a Simple Virtual Machine
On-Premises Virtual MachineMachine Name: APPSRV1Memory: 8 GB Cores: 4Ports: 80/443 for http/https
Guest: C:\Host: C:\VMs\APP-OS.vhd
Guest: D:\Host: D:\VMs\APP-Data.vhd
Guest: E:\Host: E:\VMs\APP-Logs.vhd
Cloud ServiceName: myapp1.cloudapp.net
Virtual MachineRole Name: appsrv14 Cores 7 GB Ram Windows
AzureStorageGuest: C:\
WAStorage\VMs\APP-OS.vhd
Guest: E:\WAStorage\VMs\APP-Data.vhdGuest: F:\WAStorageVMs\APP-Logs.vhd
DeploymentSlot Production
Migration Steps1) Upload VHDs Azure PS or other Tools Add-AzureVHD2) Create VM Configuration with data disks attached Data Disk 1 = APP-Data.vhd Data Disk 2 = App-Logs.vhd New-AzureVMConfig3) Create VM New-AzureVM4) Adjust App for Drive Letters
5) Add Endpoint(s) 80, TCP, http 443, TCP, https
TCP Endpoints 80 and 443
The Benefits of PaaS
PaaS is cheaperReason: There’s less admin and management work to doBenefit: Organizations spend less supporting applications
PaaS is fasterReason: There’s less work for developers to doBenefit: Applications can go from idea to availability more quickly
PaaS is lower riskReason: The platform does more, leaving fewer opportunities for errorBenefit: Creating and running applications gets more reliable
IaaS and PaaS Side by Side
Direct Connectivity Using Virtual NetworkingFor advanced connectivity scenarios such as Active Directory or DCOM
Connect Cloud Apps via VIPsEasily compose services by connecting public endpoints
Windows Azure Virtual NetworkPersistent IP Address Requirements• Virtual Machines deployed into a virtual network have an
infinite DHCP lease
Hybrid On-Premises Cloud Apps• Requirement for connectivity between your data center and
the public cloud
Connectivity between cloud services• Deploying Active Directory in the Cloud or connecting a
PaaS to IaaS Service
Subnet 2
Subnet 1
Connecting Applications and VMsStrengths• Simplicity• Tenant Autonomy• VIP Swap (cloud services)• Easy Local Dev/Test
SQL Data Access Traffic
Through Public
Endpoint
Weaknesses• Higher Latency• Less Secure
Management/Deployment Overhead
Cloud Service or Web Site
Cloud Service
SQL Server
Load Balancer
80
2001-1433
Secure Endpoints with Windows Server Firewall
Load Balancer
Connecting Cloud Services with VNETStrengths• Protect VMs from the open Internet• Lower Latency• VIP Swap (web / worker roles)• Advanced Connectivity Requirements
Weaknesses• VNET Complexity• Windows Azure Provided DNS
does not span cloud services
Direct Access
via VNET
AppSubnet (10.0.0.0/16)
SQLSubnet (10.1.0.0/16)
Load Balancer
80
Web or Worker
Cloud Service1
Cloud Service 2
AD
SQL Mirror
AD Subnet(10.2.0.0/16)
ContosoVNet (10.0.0.0/8)
© 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.