Red hat enterprise_virtualization_load

Editor's Notes

1. On this slide, introduce yourself and say you'll be talking about the Red Hat Enterprise Virtualization portfolio
2. What is Red Hat Enterprise Virtualization? It's a portfolio of products consisting of an open source hypervisor called the RHEV hypervisor, based on KVM (kernel based virtual machine) and a centralized management system for servers and desktops called RHEV Manager The KVM hypervisor leverages the Red Hat Enterprise Linux kernel, so we the get industry leading scalability, performance and security and the hardware and software ecosystem of thousands of vendors from Red Hat Enterprise Linux. And, as you'll see, we can deliver this at a significantly lower cost of ownership than proprietary virtualization products like VMware.
3. We introduced RHEV 2.1 in November 2009, and since then we've seen a lot of market momentum in Red Hat Enterprise Virtualization and I'll share a few stories briefly here... (feel free to highlight the ones you want) Qualcomm – Chose RHEV as a strategic virtualization platform. They didn't rip and replace VMware, but are using RHEV to increase their virtualization footprint even more while holding down costs, and developing a second source solution for cloud. IBM has built their Small Business Test and Development Cloud on RHEV (proof point—ready for cloud, ready for production, IBM chose RHEV over Xen and third party KVM) NTT has built their cloud offering on RHEV (same value as above) Voddler (Swedish Hulu) serving video on demand based on RHEV and integrated with the Cisco UCS platform Oxilion built their self-service cloud portal based on the RHEV stack and the RHEV API Euronet secures millions of ATM and card transactions on RHEV Etisalat serves millions of cellular users in SE Asia on RHEV This is just the beginning. We've been on the market < a year. RHEV customers run the gamut—from large companies to smaller ones. Watch for more announcements.
4. In June 2010, we launched RHEV 2.2, which includes both updates to the server virtualization product as well as the first release of the desktop virtualization or VDI offering built on RHEV. Let's take a look at what's new...
5. Red Hat Enterprise Virtualization from 2.1 has had the enterprise virtualization features such as HA, live migration (vMotion), power management and load balancing. There's a couple of new features: > OVF import and export of virtual machines. OVF is a flat file that allows you to do disaster recovery and move your virtual machines images from one datacenter to another > Hand-in-hand with OVF is our V2V conversion tools, that allow you to take VMware or RHEL Xen/KVM virtual machines and import them into RHEV > Finally, RHEV 2.2 is based on RHEL 5.5, so we get all the hardware enablement for the newest Intel and AMD servers, and we've also expanded our largest VMs to 16 virtual CPUs and 256GB RAM RHEV 2.2 is also the first release of the RHEV for Desktops product, which adds a connection broker, desktop deployment tools, and our open source SPICE remote rendering protocol, which gives you high definition video, bi-directional audio and video for video conferencing, USB support, multiple monitors and more.
6. The RHEV product includes a central management server called RHEV Manager, and it has the ability to manage both servers and desktops. Depending on the use case, there are some functions that are exclusively for desktops or for servers, but you are using the same interface to manage both. RHEV Manager scales to hundreds of hosts in a cluster (which VMware calls a resource pool), and thousands of virtual machines. Each element in the user interface is a database object against which you can run queries in the user interface. For example, rather than being limited to a hierarchical view of your environment, you can very easily ask RHEV to show you all Windows 2003 servers created by Jim in San Francisco. It's a very powerful tool to help you manage and troubleshoot hundreds of VMs. And there is a robust API based on PowerShell technology which you can use to interface with RHEV, script and automate, and extend the product.
7. The RHEV hypervisor is based on the KVM (kernel-based virtual machine) hypervisor integrated into the Linux kernel. Since it is integrated with Linux, unlike Xen (the other open source hypervisor), KVM just loads as a driver. It's a very clean architecture, and it allows us to use all the advanced technologies built into Red Hat Enterprise Linux. For hosts, we can use up to 96 cores and 2 TB of RAM, which are essentially the tested limits of RHEL, and as RHEL supports more we automatically inherit that in RHEV For guests, we support 16 VCPU and 256 GB RAM We use the same memory sharing, SELinux security, and other advanced features designed for Linux and make them available for hosting virtual machines And our performance is commonly 85-95% of bare metal depending on the application.
8. (Slide may be more important for RHEL Xen customers) Some customers have asked us why KVM and not Xen. First of all, we will continue to support Xen in RHEL 5 until EOL in 2014. We have already announced that RHEL 6 will only support KVM. Why is that? KVM leverages Linux, so we don't have to reinvent the wheel We get to code and certify once and use the same technology that gives great application performance and use it for VMS. And, in future versions of RHEV we will support a hybrid mode of operation where you can run true bare-metal RHEL applications side-by-side with virtual machines running disparate operating systems; with guaranteed performance and security. That's something Microsoft can't do with Hyper-V and something that VMware can't do either.
9. Here's an example of a technology built into Red Hat Enterprise Linux which we are able to take advantage of in RHEV for hosting virtual machines. KSM or Kernel Same-Page Merging is a technology that allows multiple applications in Linux to use more memory than is physically installed by merging or deduplicating redundant memory pages. The RHEV hypervisor with KVM allows us to use the same technology to overcommit memory in virtual machines. Here we are running multiple instances of a Windows 2003 server VM with 3GB RAM running an intensive Java benchmark. On the horizontal we are increasing the number of Vms on a single physical server with 24 GB of physical RAM, and on the horizontal we are measuring IO. You can see that from 1 VM to about 16 VM we get near linear scaling of performance. That's 200% overcommit. After that, we can get up to 400% overcommit and the workloads still run, although with diminishing returns. This is a feature we inherit from Linux, that we don't need to code from scratch. And as the performance of this feature evolves in Linux, so it does in RHEV. That's the power of KVM.
10. The RHEV Hypervisor, which comes with the RHEV products, is a slimmed down version of Red Hat Enterprise Linux with just enough bits to run and manage virtual machines. It's extremely small, PXE and SAN bootable. For Windows users, it's set-and-forget so you don't need any Linux skills. It's also a small security footprint and a persistent image. RHEV also can take a normal install of Red Hat Enterprise Linux and make it into a RHEV hypervisor. This gives it a full GUI, so it can be administered from the host as well as RHEV Manager. It allows you to add any third party monitoring agents that you require. In future, it will also be hybrid mode capable.
11. The RHEV Manager itself gives you the ability to create and deploy Vms from scratch or from templates, add live migration, high availability, power management, load balancing, and central management of your virtual storage, network, and configuration information.
12. RHEV Manager is also the administration tool for your virtual desktop infrastructure. It allows you to centrally manage pools of virtual desktops, assign rights to those desktops based on active directory membership, and gives you access to the SPICE protocol for remote rendering of those desktop machines.
13. For security, RHEV uses the SELinux security engine built into RHEL and designed for government security. This feature is on by default and effectively isolates Vms from each other and from the physical host. In future versions of RHEV, we'll be leveraging the sVirt project, which is a VM-enabled version of SELinux, that provides multilevel security, access control of resources such as disk storage and network, and can be tuned to the most challenging security requirements.
14. SPICE is remote desktop rendering technology Red Hat open sourced in December 2009. SPICE provides a user experience identical to a real desktop to users. It can do this based on its unique architecture. SPICE has three components: SPICE driver in the VM, the SPICE engine in the hypervisor host, and the SPICE client on the thin client or PC used to access the VM. Based on the video workload and network conditions, SPICE will adaptively choose to render either in the datacenter on the hypervisor host, or on the client by sending graphics primitives to directly to the client. Think about any laptop or desktop, even a 3-5 year old repurposed PC has more graphics processing power than can be emulated in the datacenter. In this case, SPICE will render on the client, which provides a better user experience and offloads more processing out of your datacenter.
15. RHEV also inherits the Red Hat Enterprise Linux ecosystem. On the server side, any server that is certified for RHEL 5 and has the Intel VT or AMD-V extensions can run a RHEV hypervisor. For customers running RHEL virtual machines, Red Hat has committed that any application that is certified for RHEL on bare metal is automatically certified for RHEL running on RHEV. Most of our ISV partners have signed on for this... [optional---] with certain exceptions. For example, SAP supports RHEV for test/dev in version RHEV 2.2, while we work on certification for RHEV 2.3 of production workloads.
16. And I also want to emphasize that not only do we support Windows guest operating systems, but Microsoft supports RHEV as well. In February 2009 we signed a commitment with Microsoft for support of Windows operating systems and many of their application servers under the SVVP (Server Virtualization Validation Program) We also have WHQL signed drivers for XP and Windows 7 for both server and desktop operating systems, and support Windows desktop operating systems on RHEV for Desktops.
17. RHEV gives you great performance on enterprise applications. VMware doesn't allow us to publish competitive benchmarks, but I will say that for real applications like DB2, SAP, Oracle, Java, and others, you see about 90-96% of bare metal performance. For older applications and operating systems that may not be able to take advantage of a 32 core 128GB machine, you can actually get better-than-bare metal performance by stacking multiple VM instances on a single physical server than you can get by installing on bare metal, which is the number you see for the LAMP stack here.
18. If you're familiar with Red Hat, you'll know we sell on a subscription basis. We don't sell you an upfront software license and then annual support. We sell an annual subscription that's the same cost each year which includes product access, updated, patches, support and the certified ecosystem. We think it's a better way to buy software, especially in these uncertain economic times, and more and more people agree.
19. So how do we sell RHEV? Again, we sell on the subscription model, so it's the same cost each year for the same deployment. We have one edition of RHEV for Servers that includes all the features you need. We only charge for the number of managed hypervisor sockets. We don't charge extra for 6 and 8 core machines, and we don't charge extra for multiple RHEV Managers. RHEV for Servers is $499/socket/year for Business Hour support, and $749/socket/year for 24x7 mission critical support. RHEV for Desktops is an add-on to RHEV for Servers, so you must have RHEV for Servers on your hypervisors first. Then add RHEV for Desktops in packs of 25. RHEV for Desktops is $375/25 desktops/year for Business Hour support and $563/25 desktops/year for 24 x 7, which works out to $15/year and $22.50/year respectively.
20. You can see here how we compare to Vmware and Microsoft for server virtualization. For nearly the same feature set, our acquisition cost is less than 1/7 of Vmware, and less than 1/3 over 3 years. What that means to you is that you can virtualize a lot more workloads today with the same budget, and you get to break-even a lot faster with Red Hat. CONFIGURATION DETAILS: Cost for 10 servers, 2 sockets each (20 sockets total), Business Hours Support
21. For desktop virtualization, it's the same story. For less than ¼ the first year cost, and ½ the three year cost, you get the same functionality allowing you to complete a VDI project faster and see an early return on investment. CONFIGURATION DETAILS: For Red Hat: 100 Desktops (4 x RHEV-D 25 Packs), hosted on three 2 socket servers (3 x 2 = 6 RHEV-S), Standard Support For Vmware: 100 Desktop of Vmware View Enterprise Concurrent User License (includes hypervisor) + Standard Support. NOT SHOWN is VSPHERE + VIEW add-on model which is more comparable to Red Hat (i.e. can do servers and desktops) but is much more expensive ($40K+). For Citrix: XenDesktop VDI Edition Concurrent User License + Standard support, using included XenServer. NOT SHOWN is named user license, or XenDesktop on Vmware or Hyper-V (more $$)
22. So why is Red Hat entering the virtualization space now? Well, we see the same thing happening in the virtualization space that we saw 10 years ago in Enterprise UNIX. Proprietary solutions were driving up costs and driving down innovation. 10 years ago, incumbents like IBM in mainframe, Microsoft and Sun in enterprise were positioning themselves as the safe choice for enterprise customers, while keeping prices high. Red Hat, Linux and Open Source changed that. Today, players like Oracle and VMware are positioning themselves the same way. With the power of RHEV, Red Hat intends to do to virtualization what we did in the UNIX space: use open source to bring choice, drive up innovation, and drive down costs.
23. We're starting to see this message resonating. In April 2011, Red Hat competed with VMware, Citrix, and Microsoft in InfoWorld's Virtualization ShootOut. The result? With RHEV 2.2 in the market less than 2 years, we placed a close second to a vendor with 10 years in the market, and beat two other players that had been competing longer than us. And we did it on pure features and performance. Our significant open source value through our subscription model was not taken into account.
24. In open benchmark comparisons, RHEV 2.2 (Red bars) is neck and neck in performance with VMware (green bar). And in the future, RHEV 3 with the RHEL 6 KVM hypervisor will give us even better performance—better than anything VMware is showing today, and up to 30% more on the same hardware as our current product. That's the power of open source.
25. When we talk about RHEV, we often talk about “feature velocity.” Here I want to show you what that means. After 7 years of developing their proprietary virtualization solution, VMware has reached a certain point in features and scalability. RHEV has been on the market for six months, and has already matched or surpassed VMware in many key metrics. What's exciting is with the release of RHEL 6, we take a quantum leap ahead in terms of scalability limits. All of this within a year of entering the virtualization market.
26. That's the power of the open source community, where we leverage all the development of virtualization technologies in the broader community. That's also the power of Red Hat, where we bring together not just the community but the large hardware and software vendors to create an enterprise-ready ecosystem for our partners. And the RHEV KVM hypervisor leverages all the work in the broader Linux kernel community, giving RHEV incredible velocity in features and scalability.
27. But don't take my word for it. You can go to our website and under the Cost section for either Desktops or Servers you can run a detailed analysis to see how much Red Hat can save you in both the overall benefits of virtualization as well as compared to other solutions.