• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
IT Camp: Windows Server 2012 and Windows Azure IaaS Overview
 

IT Camp: Windows Server 2012 and Windows Azure IaaS Overview

on

  • 3,735 views

IT Camp focused on Windows Server 2012 (Hyper-V and Storage) and Windows Azure IaaS Overview.

IT Camp focused on Windows Server 2012 (Hyper-V and Storage) and Windows Azure IaaS Overview.

Statistics

Views

Total Views
3,735
Views on SlideShare
2,929
Embed Views
806

Actions

Likes
3
Downloads
194
Comments
0

3 Embeds 806

http://blogs.technet.com 804
http://www.linkedin.com 1
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    IT Camp: Windows Server 2012 and Windows Azure IaaS Overview IT Camp: Windows Server 2012 and Windows Azure IaaS Overview Presentation Transcript

    • Windows Server2012 BeyondVirtualizationEnabling Hyper-V over SMB
    • Enabling Hyper-V over SMBWhy should I care?Technology OverviewDemoNext Steps
    • Enabling Hyper-V overSMB
    • Hyper-V over SMBServer Message Block (SMB) protocol… • Is a network file sharing protocol that allows applications on a computer to read and write to files and to request services from server programs in a computer network • Windows Server 2012 introduces the new 3.0 version of the SMB protocolWith Windows Server 2012, Hyper-V… • Can store virtual machine files (configuration, VHD, snapshots) in files shares over the SMB 3.0 protocol • Is supported for both stand-alone and clustered servers that use Hyper-V with shared file storage for the cluster • Can support scale-out file shares and clusters • Can leverage SMB Multi-Channel
    • Enabling Hyper-V overSMB I care?Why should
    • Why should I care? • Ease of provisioning and management • You can manage file shares instead of storage fabric and logical unit numbers (LUNs). • Increased flexibility • You can dynamically migrate virtual machines or databases in the data center. • Ability to take advantage of existing investment in a converged network • You can use your existing converged network with no specialized storage networking hardware. • Reduced capital expenditures • Capital expenses (acquisition costs) are reduced. • Reduced operating expenditures • You can reduce operating costs because there is no need for specialized storage expertise.
    • Enabling Hyper-V overSMBOverviewTechnical
    • Requirements • One or more computers running Windows Server 2012 with the File Services role installed • One or more computers running Windows Server 2012 with the Hyper-V role installed (separate from the file server) • A common Active Directory infrastructure • The servers running Active Directory Domain Services (AD DS) do not need to run Windows Server 2012 • Supported configurations • Standalone Hyper-V servers (no a high-availability solution) • Hyper-V servers configured in a Failover Cluster Although not required, Failover Clustering is supported on the Hyper-V side, the File Services side, or both. They must be separate clusters.
    • Common Configurations
    • Hyper-V Over SMBWorkflow1. Install the Hyper-V role on a Windows Server 2012 machine2. Install the File Services role on a Windows Server 2012 machine3. Create an SMB file share4. Create a virtual machine and virtual machine hard disk on the file share5. Migrate existing virtual machine storage to the file share
    • Creating an SMB ShareFrom Server Manager: 1. Log on or connect to a Windows Server 2012 computer on which the File and Storage role is installed. Open Server Manager and navigate to File and Storage Services 2. In Server Manager, start the New Share WizardWith PowerShell: # Create folder MD X:VMS # Create file share New-SmbShare -Name VMS1 -Path X:VMS -FullAccess DomainHVAdmin, DomainHV1$, DomainHV2$, DomainHVC$ # Set NTFS permissions from the file share permissions (Get-SmbShare VMS1).PresetPathAcl | Set-Acl
    • Migrating Storage to an SMBShare You can migrate from… • Direct-Attached Storage to SMB file share • SMB file share to another SMB file share 1. To determine the current storage being used by a virtual machine: Get-VM VM1 | FT Name, Path, State Get-VMHardDiskDrive VM1 | FT VMName, Path 2. To migrate the virtual machine storage to an SMB file share: Move-VMStorage –VMName VM1 –DestinationStoragePath FSTVMS 3. To confirm migration: Get-VM VM1 | FT Name, Path, State Get-VMHardDiskDrive VM1 | FT VMName, Path
    • Enabling Hyper-V over SMBDEMO
    • SMB 3.0 Overviewhttp://technet.microsoft.com/en-us/library/hh831795.aspxSystem Center 2012 Evaluation Downloadhttp://aka.ms/hwsc2012Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012Microsoft Virtual Academyhttp://aka.ms/virtualacademyWindows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx
    • Windows Server2012BeyondHyper-V ReplicaVirtualization
    • What is Hyper-V Replica?Why should I care?Technology OverviewDemoNext Steps
    • Hyper-V ReplicaWhat is it?
    • What is Hyper-VReplica?A virtual machine level replication solution which efficiently replicates data over aLAN/WAN to a remote (Replica) site without relying on software or hardwaretechnologies outside of the Windows Server 2012 operating system• New in Windows Server 2012 Hyper-V Role• Storage and Workload agnostic• Servers can be standalone or members of a Failover Cluster• Servers can be members of a workgroup or a domain (same or different); Primary and Replica servers do not need to be in the same domain unless part of a Failover Cluster• Managed locally (Hyper-V Manager) or remotely (Hyper-V Remote Server Administration Tools (RSAT) or System Center Virtual Machine Manager (SCVMM)• 4 Deployment Scenarios • Head Office and Branch Office (HO-BO) • Enterprise Datacenter • Hosting Provider Datacenter • Customer Office and Hosting Provider Datacenter (Cross- Premise)
    • Hyper-V ReplicaWhy should I care?
    • Why should I care?The challenge… • Provide business continuity and minimal downtime of virtualized servers during times of disruptionHyper-V Replica provides an efficient, cost-effective solutions… • Allows a Hyper-V administrator to execute a failover of production workloads to replica servers at a secondary location within minutes (in the event of fire, power outage, server failure, etc.) • Provides the necessary management APIs to enable IT management vendors to build an enterprise class Disaster Recovery solution for customers • Enables Infrastructure as a Service (IaaS) for hosting providers that host dedicated/virtual servers for customers • Seamlessly integrates with Clustering and Volume Shadow Services (VSS) • Supports heterogeneous storage between primary and recovery
    • Hyper-V ReplicaTechnical Overview
    • Installation Requirements • Hardware that supports the Hyper-V Role on Windows Server 2012 • Sufficient storage on both Primary and Replica servers to host the files used by virtualized workloads • Network connectivity between the locations hosting the Primary and Replica servers • Properly configured firewall rules to permit replication between the Primary and Replica sites • An X.509v3 certificate to support Mutual Authentication with certificates (if desired or needed) • For detailed certificate requirements, see http://blogs.technet.com/b/virtualization/archive/2012/03/13/hyper-v- replica-certificate-requirements.aspx
    • Installation andConfiguration1. Add Hyper-V role on Primary and Replica servers • Add Role and Feature Wizard (ARFW) in Server Manager • Deployment Image and Service Management (DISM) dism /online /enable-feature /featurename:Microsoft-Hyper-V • Server Manager Powershell cmdlet Install-WindowsFeature –Name Hyper-V –IncludeManagementTools2. Run Best Practices Analyzer to confirm installation and verify functionality3. Configure Replication • Standalone • Failover Cluster4. Enable each Virtual Machine for replication (Enable Replication Wizard)5. Or use PowerShellSet-VMReplicationServer -ReplicationEnabled $true -AllowedAuthenticationType Integrated -IntegratedAuthenticationPort$RecoveryPort -DefaultStorageLocation $ReplicaStorageLocation -ReplicationAllowedFromAnyServer $true
    • Architectural Components
    • Hyper-V ReplicaDEMO
    • Hyper-V Replica Overviewhttp://technet.microsoft.com/en-us/library/jj134172.aspxSystem Center 2012 Evaluation Downloadhttp://aka.ms/hwsc2012Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012Microsoft Virtual Academyhttp://aka.ms/virtualacademyWindows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx
    • Windows Server2012 BeyondVirtualizationHyper-V Scalability
    • Windows Server 2012 Hyper-V Scalability ImprovementsWhy should I care?Technology OverviewDemoNext Steps
    • Windows Server 2012 Hyper-VScalability
    • Windows Server 2012 Hyper-V Scalability Improvements • Expanded processor and memory support • Virtual Non-Uniform Memory Access (NUMA) • Network Adapter Hardware Acceleration • Offload Data Transfer (ODX) • Support for 4 KB sector disks • Virtual Fibre Channel • SMB 3.0 • Improved VM Import • VHDX disk format
    • Windows Server 2012 Hyper-V ScalabilityWhy should I care?
    • Why should I care?Enhanced support for high-performance hardware configurations in Windows Server 2012Hyper-V… • Provides more options for IT organizations for deploying a wider range of enterprise applications in virtualized environments • Increases support for high-performance processor and memory configurations, which in turn help support the deployment and operation of mission-critical applications on virtualized systems
    • Windows Server 2012Hyper-V ScalabilityTechnical Overview
    • Expanded Processor &Memory Support Maximum Number Improvement System Resource Windows Server Windows Server Factor 2008 R2 2012 Logical processors on 64 320 5x hardware Host Physical Memory 1 TB 4 TB 4x Virtual processors per 512 2,048 4x host Virtual processors per 4 64 16x virtual machine Memory per virtualVirtual Machine 64 GB 1 TB 16x machine Active virtual machines 384 1,024 2.7x per server Nodes 16 64 4x Cluster Virtual machines 1,000 4,000 4x
    • Virtual NUMA VMs are NUMA-aware • Dynamic memory cannot be configured on the host • Performance of applications like SQL Server are significantly better • Support extends into high-availability solutions built using Windows Server 2012 Failover Clustering How NUMA works… • Guest OS and applications make intelligent decisions about thread and memory allocation • Decisions are reflected in the physical NUMA topology of the host
    • Network Adapter HardwareAccelerationVirtual Machine Queue (VMQ) • Employs hardware packet filtering to deliver packets from an external VM network directly to VMs using DMA transfersIPsec task offload • Reduces the load on the system’s processors by IPsec encryption/decryption using a dedicated processor on the network adapterSingle-Root I/O virtualization (SR-IOV) • Enables a device to divide access to its resources among various PCIe hardware functions
    • Offload Data Transfer (ODX) A feature of high-end storage arrays that uses a token-based mechanism to read and write data within and between arrays
    • Support for Large Sector Disks To meet demands for increased disk capacity, Windows Server 2012 supports… Read-Modify-Write (RMW) • 512-byte sector format is replace by 1. The disk reads the 4 KB physical 4,096-byte (4 KB) format sector into its internal cache, which contains the 512-byte logical sector Hyper-V in Windows Server 2012… referred to in the write • Supports hosting VHD files on native 4 2. Data in the 4 KB buffer is modified to KB format or 512-byte emulation (512e) include the updated 512-byte sector mode 3. The disk performs a write of the • Mitigates the RMW impact when updated 4 KB buffer back to its accessing data within VHD files and when physical sector on the disk updating metadata structures
    • Dynamic MemoryImprovements • New Minimum Memory setting • Minimum/Maximum memory settings can be modified while VM is running
    • Viewing DynamicMemory Hyper-V Manager console redesigned for improved display of Dynamic Memory real-time measurements – No Scrolling! Get-VM cmdlet
    • Virtual Fibre Channel Provides Fibre Channel ports within the guest operating system of VM • Drivers for your HBAs must support Virtual Fibre Channel • Connects only to LUNs - a LUN cannot be used as boot media for VMs Allows for new scenarios • Example: running the Failover Clustering feature inside the guest operating system of a virtual machine connected to shared Fibre Channel storage Protects existing investments • Allows you to use any advanced storage functionality of an existing SAN directly from VMs Includes support for many related features • Virtual SAN • Live Migration • Multipath I/O (MPIO) • Use for host access • Virtualize workloads that use MPIO • Use different device specific modules (DSMs) for the host or each virtual machine
    • SMB 3 Improvements in SMB 3 are designed to provide increased performance, reliability, and availability in scenarios where data is stored on file shares SMB Direct • Provides remote storage solutions equivalent in performance to Fibre Channel, but at a lower cost SMB Directory leasing • Improves application response time by reducing round-trips from client to server SMB Encryption • Protects network traffic from eavesdropping when travelling over untrusted networks SMB Multichannel • Server applications become more resilient to network failure
    • Improved VM Import To help prevent configuration problems that prevent the import process from completing successfully • Configuration validation during import • Can manually copy VM files between hosts and then import them • No need to export first! • Improved Import wizard
    • VHDX Disk Format New default format for VHDs in Hyper-V in Windows Server 2012 • Supports virtual disks up to 64 TB • Aligns to megabyte boundaries to support large sector disks (4 KB sector disks) • Uses large block sizes to provide better performance • Includes a new log to protect from corruption due to power failure • Has much greater resiliency • Allows for embedded custom user-defined metadata into VHDX files
    • Windows Server 2012 Hyper-V ScalabilityDEMO
    • Hyper-V Support for Scaling Up and Scaling Out TechnicalPreviewhttp://technet.microsoft.com/en-us/library/hh831389.aspxSystem Center 2012 Evaluation Downloadhttp://aka.ms/hwsc2012Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012Microsoft Virtual Academyhttp://aka.ms/virtualacademyWindows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx
    • Windows Server2012 BeyondVirtualizationShared Nothing Live Migration
    • What is Shared Nothing Live Migration?Why should I care?Technology OverviewDemoNext Steps
    • Shared Nothing LiveMigrationWhat is it?
    • Shared Nothing Live Migration The ability to move a virtual machine while it is powered on from one host to another without requiring shared storage • Faster and simultaneous migration • Entire VM moved with no downtime • VHD, configuration files, snapshots, etc. • Improved performance and flexibility • No longer requires a clustered environment or shared storage* Live Migration can be done with shared storage and clustered VMs, but “Shared Nothing” uses neither
    • Shared Nothing LiveMigrationWhy should I care?
    • Why should I care?The challenge… • In Windows Server 2008 R2, migration of Hyper-V data required a shared infrastructure • Implementing shared storage and failover clustering can be expensive • In order to migrate data from one host to another, both had to have a simultaneous connection to a shared storage device that could buffer dataThe Windows Server 2012 solution… • Shared nothing means the hosts needs to share nothing but a simple Ethernet connection to each other • Data is migrated without the need for a costly infrastructure • No devices are required to assist with buffering
    • Shared Nothing Live MigrationTechnical Overview
    • Live Migration – Moving aRunning VM without SharedStorage 1. Live Migration setup occurs 2. Memory pages are transferred from the source server to the destination server 3. Modified pages are transferred to destination server 4. State is transferred to destination server 5. VM brought online on standard Ethernet connection destination server 6. Network cleanup occurs
    • Configuring Live Migration
    • Performing Live Migration
    • Performing Live Migration, (Cont.)
    • Performing Live Migration, (Cont.)
    • Performing Live Migration, (Cont.)
    • Shared Nothing LiveMigrationDEMO
    • Live Migration Shared Nothing Videohttp://www.aidanfinn.com/?p=12287System Center 2012 Evaluation Downloadhttp://aka.ms/hwsc2012Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012Microsoft Virtual Academyhttp://aka.ms/virtualacademyWindows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx
    • Windows Server2012 StorageStorage Spaces and Thin ProvisioningHarold Wong
    • Storage Spaces and Thin Provisioning OverviewWhy should I care?Technology OverviewDemoNext Steps
    • Storage Spaces and ThinProvisioningOverview
    • What is Storage Spaces & ThinProvisioning?Storage Spaces • New in Windows Server 2012 • Provides an in-box storage virtualization that can use low-cost commodity storage devices • Aggregates unallocated space on physical disks installed in or connected to servers through a “pooling” model • Can provide a cost-effective platform for business critical storage across a variety of scenariosThin Provisioning • “Just-in-Time” allocations of storage with the ability to reclaim storage (“Trim”) • Integrated with Storage Spaces
    • Storage Spaces and ThinProvisioningWhy should I care?
    • Why should I care?The features of Storage Spaces are designed to meet a variety of challenges insupport of highly-available storage Storage pools • Can be mapped to combinations of hard disks as well as solid-state drives (SSDs) • Can be expanded dynamically by simply adding additional drives, thereby seamlessly scaling to cope with unceasing data growth Multitenancy • Administration of storage pools can be controlled through access control lists (ACLs) and delegated on a per-pool basis • Can be fully integrated with Active Directory Domain Services Resilient storage • Storage Spaces support two optional resiliency modes (mirroring and parity) • Per-pool support for disks that are reserved for replacing failed disks (hot spares), background scrubbing, and intelligent error correction allow continuous service availability despite storage component failures
    • Why should I care? (cont.)Continuous Availability • Failover clustering integration delivers continuously available service deployments • One or more pools can be clustered across multiple nodes within a single cluster. Storage spaces can then be instantiated on individual nodes, and the storage will seamlessly fail over to a different node when necessary (in response to failure conditions or due to load balancing) • Integration with CSVs permits scale-out access to dataOptimal storage use through thin provisioning • To allow businesses to easily share storage capacity among multiple unrelated data sets and thereby maximize capacity use • Trim support permits capacity reclamation when possibleOperational simplicity • Easily managed through the File Services role in Server Manager • Fully remoteable and scriptable management through the Windows Storage Management API, WMI, and Windows PowerShell • Designed to be compatible with existing backup-restore and cloning tools, as well as snapshotting infrastructures
    • Storage Spaces and ThinProvisioningTechnical Overview
    • Storage SpacesRequirements• Windows Server 2012 Drive Stand-Alone Clustered• Serial ATA (SATA) or Serial Attached SCSI (SAS) Type File Servers File Servers connected disks (in an optional just-a-bunch-of- SATA Supported disks [JBOD] enclosure)• Multinode clustered shared-storage deployments SCSI Supported • Two or more servers running Windows Server iSCSI Supported Supported 2012 SAS Supported Supported • Requirements as specified for failover USB Supported clustering and Windows CSV • SAS connected JBODs that comply with Windows Certification requirements• The criterion for determining which drives are eligible to be part of a Pool are: • Minimum drive size is 10 GB • Drive is empty, i.e. no partition data exists on the drive • Drive is not assigned to any other pool • The Primordial Pool will consist of Physical Disks that are not assigned to any existing Storage Pool
    • How does Storage SpacesWork? An example…
    • Process of HandlingResources
    • Storage SpacesManagement Interface
    • Configuring a Storage Pool
    • Creating a Storage Space(Virtual Disk)
    • Data Redundancy inStorage Spaces Redundancy Description Type Simple • Data is striped across physical disks • Maximizes capacity • Increases throughput Mirror • Data is duplicated on two or three physical disks • Increases reliability • Reduces capacity by 50 to 66 percent Parity • Data and parity information are striped across physical disks • Increases reliability • Reduces capacity by 13 to 33 percent
    • Deduplication• Capacity Optimization• Scale and Performance• Reliability and Data Integrity
    • Managing Storage withPowerShell PowerShell is required to access many of the advanced features afforded by the new Storage Management application programming interface (API)Example: New-StoragePool Parameters configured with GUI and PowerShell • Underlying storage pool name • Virtual disk name • Resiliency setting (Simple, Mirror, or parity) • Provisioning type (Thin or Fixed) • Virtual disk sizeParameters configured only with PowerShell • Number of columns: the number of columns the virtual disk contains • Number of data copies - number of complete copies of data that can be maintained • Disk interleave - number of bytes forming a stripe • Physical disks to use - specific disks to use in the virtual disk
    • Integrating Storage Poolswith Failover Clustering • Clustered Storage Spaces require fixed provisioning • Clustered virtual disks require underlying hardware to support persistent reservations
    • Thin Provisioning and TrimRequirements • Enabled by default in Windows Server 2012 • Storage infrastructure that complies with the certification that is required for Windows Server 2012 • Standards-compliant hardware for identificationCapabilities • Identification • Windows Server 2012 uses a standardized method to detect and identify thinly provisioned virtual disks • Notification • When configured physical storage use thresholds are reached, Windows Server 2012 notifies the administrator through events; events can be used for automated actions by sophisticated management applications, such as Microsoft System Center • Optimization • Windows Server 2012 provides a new API that lets applications return storage when it is no longer needed. • NTFS issues trim notifications in real time when appropriate. • Trim notifications are issued as part of storage consolidation (optimization), which is performed regularly on a scheduled basis
    • Storage Spaces andThin ProvisioningDEMO
    • Understanding and Troubleshooting Storage Spaceshttp://www.microsoft.com/en-us/download/details.aspx?id=29002System Center 2012 Evaluation Downloadhttp://aka.ms/hwsc2012Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012Microsoft Virtual Academyhttp://aka.ms/virtualacademyWindows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx
    • Windows Server 2012Management andInfrastructure SharesContinuously Available FileHarold Wong
    • Continuously Available File SharesWhy should I care?Technology OverviewDemoNext Steps
    • Continuously Available FileSharesWhat is it?
    • Scale-Out FileServices/Shares Allow you to scale the capacity of file servers upward or downward dynamically by using Failover Clustering with… CSV File System (CSVFS) SMB 3.0 • Appears as a single consistent • SMB Scale Out file namespace, although the • SMB Transparent Failover underlying file system remains • SMB Multichannel NTFS • SMB Direct • Allows direct I/O for file data • SMB Performance Counters for Server access and supports sparse Applications files • SMB Performance Optimizations • Allows encryption through • SMB Management with Windows BitLocker PowerShell • Backups of CSV no longer • SMB Remote File Storage require redirected I/O • Supports SMB 3.0 features
    • Continuously Available FileSharescare?Why should I
    • Why should I care?The challenge… • Prior to Windows Server 2012, highly available file services were provided by failover cluster Client Access Point (CAP) that clients could use to connect to SMB (Server Message Block) or Network File System (NFS) shares on physical disk resources • If you deployed a shared-nothing cluster, only one node in a cluster File Server group could be online • In the event of a failure or if the File Server group was moved to another cluster node, clients were disconnected and had to reconnect when the group became available on an online node in the clusterThe solution… • The File Server Role has been expanded to include a new scenario where application data (specifically Hyper-V and SQL Server) is supported on highly available SMB shares • Provides access with almost zero downtime
    • Continuously Available FileSharesTechnical Overview
    • Continuously Available FileServers General Use File Server • Almost identical to Windows Server 2008 R2 • Shares can be made continuously available with the help of the SMB 3.0 protocol Scale Out File Server • Provides continuously available file services for application data • Responds to increased demands quickly by bringing more servers online • Takes advantage of new features in Windows Server 2012 Failover Clustering • Distributed Network Name (DNN) • Cluster Shared Volumes Version 2 • Scale Out File Server role (must be enabled on all nodes in the cluster • Clusters of Scale Out File Servers are limited to 4 servers
    • Continuously Available ScaleOut File Server Architecture Cluster platform for a continuously available scale out file server • Cluster-wide client access point • Consistent cluster-wide file server configuration • CSV cluster-wide file system Zero client downtime failover – both planned and unplanned downtime Accessing VHDs over SMB Hyper-V Cluster Single Logical Server (FooShare) Single File System Namespace Cluster Shared Volumes File Server Cluster
    • the General Use File ServerRole From Failover Cluster Manager…High Availability Wizard
    • Installing and Configuring theGeneral File Server Role From Failover Cluster Manager…Add File Share
    • Installing the GeneralUse File Server Role(cont.)
    • Installing the Scale OutFile Server Role From Failover Cluster Manager…High Availability Wizard
    • Installing the Scale Out FileServer Role (Cont.) From Failover Cluster Manager…Add File Share
    • Continuously Available FileSharesDEMO
    • High-Performance, Continuously Available File Share Storage forServer Applications Technical Previewhttp://technet.microsoft.com/en-us/library/hh831399.aspxSystem Center 2012 Evaluation Downloadhttp://aka.ms/hwsc2012Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012Microsoft Virtual Academyhttp://aka.ms/virtualacademyWindows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx
    • How Did We Get Here? 11/2010 VM Role Connect Admin Mode 11/2009 Startup Tasks 2007 Full Trust/Native Full IISProject Red Dog Launched PHP & Java Support Remote Desktop PDC2008 2/2010 11/2011 Windows Azure CTP Windows Azure RTM Cross Language SDKs Web/Worker Roles Java, Node.JS Partial Trust .NET Only Eclipse Plugin
    • Infrastructure as a Service If deploying an application requires a developer’s involvement, it’s not IaaS
    • Cloud Models
    • A Continuous Offering From Private to Public Cloud
    • Windows Azure Virtual Machines
    • Virtual Machine vs VM Role VM Role Virtual Machine Storage Non-Persistent Storage Persistent Storage Easily add additional storage Deployment Build VHD offsite and upload to Build VHD directly in the cloud or build storage. the VHD offsite and upload Networking Internal and Input Endpoints Internal Endpoints are open by default. configured through service Access control with firewall on guest model. OS. Input endpoints controlled through portal, service model or API/Script. Primary Use Deploying applications with Applications that require persistent long or complex installation storage to easily run in Windows Azure. requirements into stateless PaaS applications
    • Images Available at Preview Windows Server 2008 R2 SP1 OpenSUSE 12.1 Biztalk Server 2010 R2 CTP OpenLogic CentOS 6.2 Windows Server 2008 R2 with Ubuntu 12.04 LTS • SQL Server 2012 Eval SUSE Linux Enterprise Server Windows Server 2012 RTM SP2
    • Virtual Machine Sizes # Data VM Size CPU Cores Memory Bandwidth Disks Extra Small Shared 768 MB 5 (Mbps) 1 Small 1 1.75 GB 100 (Mbps) 2 Medium 2 3.5 GB 200 (Mbps) 4 Large 4 7 GB 400 (Mbps) 8 Extra Large 8 14 GB 800 (Mbps) 16 Each Persistent Data Disk Can be up to 1 TB
    • Persistent Disks and Highly Durable
    • Persistent Disks and Highly Durable
    • Base OS image for new Virtual MachinesSys-Prepped/Generalized/Read OnlyCreated by uploading or by captureWritable Disks for Virtual MachinesCreated during VM creation or duringupload of existing VHDs.
    • Cross-premise Connectivity Data Synchronization SQL Azure Data Sync Application-layer Connectivity & Messaging Service Bus Secure Machine-to-Machine Network Connectivity Windows Azure Connect Secure Site-to-Site Network Connectivity Windows Azure Virtual Network IP-level connectivity
    • Windows Azure Virtual NetworkEnables customers to extend their Enterprise Networksinto Windows AzureNetworking on-ramp for migrating existing appsand services to Windows AzureEnables “hybrid” apps that span cloud and their premisesEnables customers to setup secure private IPv4networks fully contained within Windows AzureIP address persistenceInter-service DIP-to-DIP communication
    • Windows Azure Virtual NetworkScenarios CloudHybrid Public/PrivateEnterprise app in Windows Azure requiring connectivity to on-premises resourcesManage identity and access control with on-premises resources(on-premises Active Directory)Remote monitoring and trouble-shooting of resourcesrunning in Windows AzureCloud deployments requiring persistent IP addressesand direct connectivity across services
    • Bringing Workloads to the Cloud SharePoint PaaS Roles File Servers Local AD SQL VMs
    • IaaS and PaaS – Better Together
    • The Benefits of PaaSA summaryPaaS is fasterReason: There’s less work for developers to doBenefit: Applications can go from idea to availability more quicklyPaaS is cheaperReason: There’s less admin and management work to doBenefit: Organizations spend less supporting applicationsPaaS lowers riskReason: The platform does more, leaving fewer opportunities for errorBenefit: Creating and running applications gets more reliable
    • IaaS and PaaS Side by SideConnect Cloud Apps via VIPs• Easily compose services by connecting public endpoints• For advanced connectivity scenarios such as Active Directory or DCOM• Simple, secure and highly efficient method of using IaaS and PaaS side-by-side
    • Connecting Cloud Services via VIPsSimplicityTenant AutonomyVIP Swap (stateless roles)Easy Local Dev/TestPersistent Service isEasily Accessible(even from other services!)
    • Connecting Cloud Services with VNETMore SecureLow LatencyCloud App AutonomyVIP Swap (stateless roles)Advanced Connectivity Requirements
    • Mixed Mode: PaaS/IaaS in the Same CloudServiceWindows Azure provided DNSLow latency connectivitySingle deployment, updateand management unit
    • Windows Azure 90 Day Trialhttp://aka.ms/hwazuretrialSystem Center 2012 Evaluation Downloadhttp://aka.ms/hwsc2012Windows Server 2012 Product Downloadhttp://aka.ms/hwws2012Microsoft Virtual Academyhttp://aka.ms/virtualacademyWindows Server 2012 Virtual Labshttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspx