Why Hyper- V is Your Best Virtualization Cloud OS Platform?

Editor's Notes

• #4: Now how we think about cloud?Microsoft cloud is divided into 3 segmentIn your organization, you have your workload running in physical server start to virtualize for consolidation .When you have a lot of VM running, it is very important to have management tool and This is where System Center come into picture. b) Then we want to have elastic, scalability and self service approach. This is where Iaas, Paas and Saas come into the picture in Windows Azure. Private Cloud is about control.Public Cloud is about scale andService Provider is about reach and customizationYou may want to workload run in specific rack ,or server. This is where service provider come into picture.Cloud is about everything and we -provide excellent Development platform-Management that consistent in 3 cloud-Data platform either use sql server in your organization, Azure or Hoster-Identity platform. Guess what we have AD running in Azure.-Then finally on Virtualization Platform. Hyper-V run in private cloud, Hyper-V in Azure. Guess what you want a case study, we use win Server 2012 to powered the VM
• #8: So in Win 2012 we deliver a lot- one of the them is scale and performance. You told us that you want to virtualize any workload. And this is what we did.On host, we support 320 and 4 TB. That is 16 socket with 10 cores each.Just now I mentioned virtualize any workload, we can now assign 64 vpu and up to 1 TB to the VM. We can hold large data up to 64TB per disk.For HA, we support up to 64 nodes in a cluster and 8000 VM. You can basically run 8000 VM in just 10 Host. But we don’t recommend that. So if you look at the number 8000/ 64. That’s 125 VM per host.
• #10: Are you ready for more?Let look into R2
• #11: We make some major improvement and divided into 5 themes.We going to continue data center without boundaries. Able to move VM from one place to another back to our core Cloud VisionCloud innovation literally everywhere. That’s Windows , System Center and Azure and think about cloud. We know that you want flexibility to run your app everywhere.Dynamic application delivery which work in anywhere, everywhere and any devices either Windows Phone OS, Android or IOSFlexible and consistent application platform. We want to have a similar interface to manage private cloud or public cloud. That application must be consistent Lastly enable people centric IT. You want deploy app, remote destop or bunch of vm or devices
• #12: With that, let talk about virtualization. Since launching of Win 2012, Microsoft has gathered a lot of feedback and tell usReduce complexity , cost & downtime. One of the comment is they love Hyper-V Replica. Why? Before Hyper-V Replica, this it is so painful, expensive and difficultNow, It is so easy to use, interface is so simple with just right click and follow few wizards. Once complete, you have a set of replica VM @ your DR.Next criteria is ease of deployment and support lifecycle of workloads and flexible virtualization platform for maximum agility.So with that comment, in R2 we responded with variety of things.Cross version live migration. Able to upgrade Win 2012 to R2.Online VHDX resize Automatic VM Activation. If your host is Win 2012 DC, then we can auto activateLive VM ExportRemote Access via VMBusLive Migration compression & RDMAMore robust linux supportDEMO – TeaserStorage QOSLinux BackupCluster without any connection to iscsi or FC. We just attached to virtual disk.
• #13: Next section is storage. The most expensive in your deployment. What storage does Windows Azure use? We just use JBOD.If you want to do Cloud scale, we need to keep it cheap, simple and scalable without impact to the performance.
• #14: In current version , we can implement storage spaces which combine multiple disk either any bunch of disk either SATA, SAS or SSD into JBOD enclosure. Then from there we can create a pool of disk so we can create virtual disk. How about resilient? Well, you assign assign RAID 5 or 1. For capacity , you can assign RAID 0.Capacity is not the main issue for storage. The most important is IOPS. In R2, we move 1 step further whereby we introduce storage tiering to increase IOPS by combine SSD with SAS to give a higher IOPS. Built in into Win 2012 R2, we automatically run in background of moving frequent use data to SSD (hot data) and less use to SATA without human interaction.Of coz, we can also pin high priority data to SSD.
• #15: If you look at the diagram . This is the most commonhoster infrastructureHoster – which focus on bottom layer/below red line. They provide great compute, storage and networking, Upgrade and changes without let customer know.As customer, we are reside on the upper layer/above the red line. We don’t know what server, network and storage that we running at and normally we don’t care. We just a VM that run our workloadNow the problem started when we want to setup guest clustering. SQL cluster / file Server cluster in a VM. We need present a LUN, FC/ ISCSI and zoning to VM. But most of the time, hoster wont do the configuration and do not want to go above the boundarySo how?
• #16: With Guest clustering Shared VHDX, we do not need to present LUN, FC/ISCSI and zoning. We just present a shared disk and it stay above the red line.Now Hoster happy and they just bill the additional storage without FC/zoning issue.Customer happy – get their guest clustering up
• #18: Now let back to cloud vision- we got private cloud, public cloud and service provider. How easy for us to move the VM from one cloud to another cloud without changing the ip address.
• #19: To solve this problem, we have software define networking (network virtualization). We separate the network into logical network and 2 conflict subnet can exist together.Example:- Blue network & red network. Both having same subnet and they is not IP address conflict. It is on their own virtual subnet and only same virtual subnet ID can communicate each other.Where this scenario is suitableLimited VLAN id (4096)Merger of companyRunning multiple tenantCurrent version, Blue VM talk to Blue VM, Red VM talk to Red VM. To communicate to outside, you need to get appliance gateway.In R2, we provide in box network virtualization gateway so we provide connectivity to different tenant and communicate to other world.
• #20: Shift gear to 4.
• #21: 1st thing that we are going to look at is backup.Well, I’m not going to ask you to change your backup software but here is what we had to offered in Windows Server 2012There are 2 scenarioScenario 1 – few server probably at branch. You can use Windows Server 2012 to backup data to Windows Azure.Scenario 2- let say if you have dpm in placed. DPM is best software to backup Microsoft platform to disk or tape. Now we can also extend further by backup to Windows Azure.
• #22: Now let move to replication.How many of your have replication between DR?1Q- Are you happy with it? Big long pause….hmmm…You probably not happy becauseCostlyGuess what our current version ship with in box Hyper-V replica. Customer love itBut hoster not very happy because most customer replica from datacenter A to B.How about replica to Service Provider?
• #23: In R2, we include extended replica.You can replicate to A -> B -> CAnother comment is the frequency of replication. Customer complained about fixed 5 minute replication frequency. Guess what? In R2, we allow you to set 30 sec, 5 min or 15min. Is this great!!!
• #24: Let go beyond. How do we control Hyper-V replica when you have many data center and VM.Won’t be good if we can use Windows Azure to manage protection & recovery.Here we introduce Hyper-V Recovery Manager whereby you use Azure to orchestrator planned, unplanned or test failover.
• #25: - Case study – We tested… tested…tested….i repeat again We tested Hyper-V in a production environment. The best case study is Windows Azure.