Virtual Machines

Report
WINDOWS AZURE IAAS
Patriek van Dorp
Technology Consultant Microsoft
Private Cloud to
Public Cloud
1
Cloud Models
2
Only Pay For What You Use
3
CLOUD SERVICES (PAAS)
4
What is a Cloud Service?
5
Roles and RoleInstances
6
Packaging and Configuration
Service Definition (*.csdef)
Service Configuration (*.cscfg)
Encrypted(Zipped(Code + *.csdef)) == *.cspkg
7
Everything goes to the Cloud!
8
We trust Microsoft without question!
9
WINDOWS AZURE
VIRTUAL MACHINES
10
Infrastructure as a Service
If deploying an application requires a developer’s involvement, it’s not IaaS
11
Windows Azure Virtual Machines
12
Things That Don’t Work (yet)
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
13
Demo
GETTING STARTED WITH
VIRTUAL MACHINES
14
Images Available in Preview
Windows Server 2008 R2
Windows Server 2008 R2 with
•
SQL Server 2012 Evaluation
Windows Server 2012 RTM
OpenSUSE 12.1
CentOS 6.2
Ubuntu 12.04
SUSE Linux Enterprise Server SP2
15
Persistent Disks and High Durability
16
Persistent Disks and High Durability
17
Provisioning a Platform Image
18
Persistent Disk Management
Capability
OS Disk
Data Disk
Host Cache
Default
ReadWrite
None
Max Capacity
127 GB
1 TB
Imaging Capable
Yes
No
Hot Update
Cache Setting
Requires Reboot
Change Cache Without
Reboot, Add/Remove
without Reboot.
19
Disks and Images
Base OS image for new Virtual Machines
Sys-Prepped/Generalized/Read Only
Created by uploading or by capture
Writable Disks for Virtual Machines
Created during VM creation or during
upload of existing VHDs.
20
VIRTUAL MACHINES AND
CLOUD SERVICES
21
Cloud Services, Roles and Instances
22
Virtual Machines
23
Cloud Services with Virtual Machines
Multiple Virtual Machines can be hosted within the same cloud service
24
VIRTUAL MACHINE
NETWORKING
25
Virtual Machine Names and DNS
Resolves VMs by name within the same cloud service
Machine names are modeled explicitly and registered in the DNS
service
Use your on-premises DNS servers
Deploy a DNS server in Windows Azure
Use public DNS services
26
Protocols and Endpoints
Load-balanced incoming traffic and allows outbound traffic
Instance-to-instance communication
TCP, UDP and ICMP, dynamic ports
Direct communication to multiple VMs in the same cloud app
Health check with probe timeouts
HTTP based probing, allowing granular control of health checks
27
Port Forwarding Input Endpoints
28
Load Balanced Sets
29
Demo
LOAD BALANCED SETS
30
VIRTUAL MACHINE
AVAILABILITY
31
Service Level Agreement
4.38 hours of downtime per year
8.75 hours of downtime per year
Compute Hardware failure (disk, cpu, memory)
Datacenter failures - Network failure, power failure
Hardware upgrades, Software maintenance – Host OS Updates
Planned downtime – 6 day notice, 6 hour window, 25 minute downtime
VM crashes caused by 3rd party software, Guest OS Updates
32
Fault and Update Domains
Represent groups of resources anticipated to fail
together (i.e. Same rack, same server)
Represents groups of resources that will be
updated together
Host OS updates honour service update domains
Specified in service definition
Default of 5 (up to 20)
33
Fault and Update Domains
34
Virtual Machines Availability Sets
35
WINDOWS AZURE
VIRTUAL NETWORKS
36
Windows Azure Connectivity Options
37
Windows Azure Virtual Networks
Enables customers to extend their Enterprise Networks into
Windows Azure
Networking on-ramp for migrating existing apps and services to
Windows Azure
Enables customers to run “hybrid” apps that span cloud and their
premises
Enables customers to setup secure private IPv4 networks fully
contained within Windows Azure
IP address persistence
Inter-service DIP-to-DIP communication
38
Virtual Network Features
Bring your own IPv4 addresses
Control over placement of Windows Azure Roles within the network
Stable IPv4 addresses for VMs
Automated provisioning & management
Support existing on-premises VPN devices
Enables customers to use their on-premise DNS servers for name
resolution
Enables VMs running in Windows Azure to be joined to corporate domains
running on-premise (use your on-premise Active Directory) 39
Demo
GETTING STARTED WITH
VIRTUAL NETWORKS
40
Supported VPN Device List
IKE v1
AES 128, 256
SHA1, SHA2
41
SCENARIOS
42
Virtual Network Scenarios
Enterprise app in Windows Azure requiring connectivity to onpremise resources
Manage identity and access control with on-premise resources
(on-premises Active Directory)
Remote monitoring and trouble-shooting of resources
running in Windows Azure
Cloud deployments requiring persistent IP addresses
and direct connectivity across services
43
Connecting Applications and VMs
Simplicity
Tenant Autonomy
VIP Swap (cloud services)
Easy Local Dev/Test
Higher Latency
Less Secure
Management/Deployment
Overhead
44
Connecting Cloud Services with VNET
More Secure
Low Latency
Cloud App Autonomy
VIP Swap (stateless roles)
Advanced Connectivity
Requirements
VNET Complexity
No Windows Azure provided DNS
45
Mixing PaaS and IaaS in the Same Cloud Service
Windows Azure provided DNS
Low latency connectivity
Single deployment, update and
management unit
No VIP Swap (coming in the
future)
46
Summary
With PaaS (Web/Worker Roles) you loose some control and you need to fit
the mold of the Cloud vendor
With IaaS you have full control over your platform and you can run (almost)
any software you like
Use the existing IT Pro skills present in your organization to extend your
corporate network to the Cloud
Create subnets to control the applications that can access resources onpremises
Mix and Match PaaS and IaaS to create the most desirable architectures
fast and save
47
[email protected]
@pvandorp
http://onwindowsazure.com
http://windowsazure.com
QUESTIONS
48
Local touch - Global reach
49

similar documents