A Virtualization, Photography, Techie, Foodie, Gadget Blog
Header image

I am adding new topic to the Blog.  High Performance Computing and Supercomputing on VMware vSphere.  This topic came up from a recent customer discussion on how they could build a distributed cloud to the purpose of grid computing that scales on par with traditional super computers.   Coming from a family that has been involved with supercomputers for decades, I found this topic to be of keen interest.  As a result, I’ve started to collect a series of notes and white papers on the topic of High Performance Computing (HPC) on VMware vSphere and the changes that must be considered to maximize performance and scalability of a virtual HPC Cluster Environment.

First, an old but mandatory read on the topic is covered in a Paper published by Cam Macdonald and Paul Lau from the University of Alberta titled:  Pragmatics of Virtual Machines for High-Performance Computing: A Quantitative Study of Basic Overheads by Cam Macdonell and Paul Lu
http://www.vmware.com/files/pdf/paullu.vmware.final.pdf

Macdonald and Lau’s paper is currently a little dated but many of the ideas still hold.  Some points to be aware of is understanding how vSphere 5 has been optimized to reduce overhead, allow for better performance, and the automated orchestration features that will allow for capacity on demand.  Macdonald’s and Lau’s closing issues regarding overhead have been reduced to less than 1% for most compute types and with the increase in performance of the CPU every year, this overhead becomes smaller yet.

Next, VMware Employee Jeff Buell posted a blog posts on “HPC Application Performance on ESX 4.1: Stream” back in Sept 2010.

http://blogs.vmware.com/performance/2010/09/hpc-application-performance-on-esx-41-stream.html

Jeff takes great strides in identifying factors that will optimize performance of the compute cluster.  Most notable is the use of local memory when writing applications will ensure optimal memory bandwidth once deployed and keeping the computer resources within a single NUMA node to optimize resource utilization.   While vSphere can address 1TB of RAM and up to 32CPU’s from a single VM, the optimization for performance lays on keeping VM’s tuned and sized to run within the optimal limitations of the server the VM is hosted upon.

Next, I want to make sure you follow the blog posts of Josh Simons.  Josh works in the Office of the CTO at VMware as a strategist specializing in HPC and maintains the VMware Blog posts on HPC here: http://communities.vmware.com/community/vmtn/cto/high-performance

Josh has contributed several videos and discussions on the topics.  With the recent Supercomputing 2011 event in Seattle, John pulled together several interviews and overviews of technologies that will enable Cloud based HPC.

In addition, Josh’s 2010 overview of HPC in the Cloud

http://communities.vmware.com/community/vmtn/cto/high-performance/blog/2010/11/02/video-available-isc-cloud-10-in-frankfurt

Lastly, my own observations and comments:

With the recent release of vSphere 5 and Auto Deploy, the process of maintaining a scalable Cloud infrastructure has become considerably simplified.  The process of updating an entire server farm can be reduced from weeks to minutes by leveraging PXE and an Image Server to refresh entire farms of servers at reboot.  By adding solutions such as templates, workflow orchestration, and capacity management, we can now scale up clusters of computers on demand to accommodate almost any size distributed workload.  Adding vCloud Director and vCloud connector allows us to scale the compute cluster even further into a single or multiple public cloud providers on demand.  In addition, with the new scalability improvements of vSphere 5, we are finding larger VM’s, more addressable RAM, less overhead, and significant IO gains at the Hypervisor.   All of these improvements contribute to the greater acceptance of HPC workloads in the Cloud and in a VM.

As I dig deeper into the topic, I hope I can contribute some of my own personal works to the field and leverage the knowledge of my colleagues to ensure others can explore this emerging growth area.

Looks like VMware made public a revised vSphere 5.0 License Model today. A lot of very good changes that directly benefit the end user. ( http://www.vmware.com/files/pdf/vsphere_pricing.pdf )

The biggest changes are around vRAM Maximums per processor.

vRAM Entitlement per CPU Socket by vSphere edition
- 32GB vRAM/CPU for Essentials Kit (up from 24GB)
- 32GB vRAM/CPU for Essentials Plus Kit (up from 24GB)
- 32GB vRAM/CPU for Standard (up from 24GB)
- 64GB vRAM/CPU for Enterprise (up from 32GB)
- 96GB vRAM/CPU for Enterprise Plus (up from 48GB)

This means a 4CPU Server of Enterprise Plus is entitled to 384GB of powered on VM’s, a 100% increase over the initial model. These entitlements can also still be pooled across vCenter Server (including vCenter Servers in Linked Mode) and only apply to the actual configured virtual RAM of powered on VM’s. VDI Users and VMware View users have a different license model for High Density VDI servers. (Discussed below)

VMware Server (the free hypervisor) users will also be happier. Under the old model, VMware Server was capped at 8GB. The revisions have increased the cap to 32GB per server (not a per CPU limit). This is a hard limit and cannot be exceed like the retail versions. Personally, I felt the 8GB limit was very limiting. The 32GB change is a significant step in the right direction and should accommodation most SMB’s/Branch Office/Home Office users. Those that feel hindered by the 32GB hard limit should look at vSphere Essentials and Essentials Plus (starting at $560) which provides 6 CPU’s (up to three servers with 2CPU’s each) with a vRAM entitlement of 192GB. Alternative Options are to move to the revised vSphere Acceleration Kits (Standard, Enterprise, and Enterprise Plus) which provide bundles of 6 CPU’s at substantial discounts. Pricing has vSphere Essential starts at $83/CPU retail!

Even better, There is no longer a penalty for very large VM’s. All VM’s only count vRAM consumption up to 96GB. Any vRAM over 96GB is not counted. That means a 1TB VM would be covered by a single CPU license. A 1TB VM is now covered by a single Enterprise Plus CPU server license. I can’t imagine running more than a single 1TB VM on a host, but people will always surprise you.

vRAM usage is now monitored on a 12 month rolling average with daily high water marks. This makes large infrequent deployments less of an issue for customer who anticipate going over the vRAM entitlement but know that they will be removing VM’s later.

As before, VMware View environments don’t follow the vRAM model. View is a CPU Socket based license for View Desktops. Non-VMware View users will be able to leverage a vSphere for Desktops product just for VDI. vSphere Desktop edition is licensed based on the total number of Powered On Desktop Virtual Machines and can be purchased either stand-alone in a pack size of 100 desktop VM or included with the VMware View Bundle.

Another interesting note for current vSphere 4.1 users with valid Support and Subscription (SnS). Customers who purchased licenses for vSphere 4.x (or previous versions) prior to September 30, 2011 to host desktop virtualization, and hold current SnS agreements, may upgrade to vSphere 5.0 while retaining access to unlimited vRAM entitlement. Desktop licenses covered by this provision, however, may not be managed by the same instance of Virtual Center which is being used to manage non-desktop OS virtual machines.

Lastly, I have heard that vCenter will get an update in the near future after release to accurately report these last minute changes. In the mean time we should be expecting a new tool to report the actual vRAM consumption.

There are lots of key aspects that were addressed in the initial vSphere 5 guide that have not changed but are different form the vSphere 4 model. Over all, I think the consumer gains a lot more value in the new editions! Unlimited RAM capabilities per server, no more Core/CPU limits, substantial increase in CPU’s per VM limit by edition (32 CPUs/VM for Ent+!) and vMotion all the way down to the Standard Edition.

A lot has changed. I see it all as a major improvement for both the SMB users and for the Enterprise.

vSphere 5 Feature Model per Edition

Taken from revised the vSphere 5 Pricing Guide

The VMware View iPad client is now available in the Apple App store.
App Store: http://bit.ly/iPadClient

The VMware View Client for iPad features include:
Easy to Setup and Use

  • - Add your VMware View server in a few simple steps and then quickly get to back to your desktop with a single click.
  • Optimized for VMware View 4.6

  • - Takes full advantage of the PCoIP Security Gateway for access to your desktop without a VPN.
  • Brings the Ease of the iPad to the Windows desktop

  • - Rich gesture support makes it easy to work with Windows on the iPad
  • - Innovative virtual trackpad makes it easy to navigate Windows to more PC savvy users
  • Market Leading Performance

  • - Exclusive support for PCoIP, providing the fastest, richest user experience
  • Engadget’s Review and Video! : http://www.engadget.com/2011/03/09/vmware-view-brings-virtual-desktops-to-ipad-with-touchscreen-fri/

    VMware View for iPad Documentations: http://communities.vmware.com/docs/DOC-15085

    VMware View for iPad release notes: http://communities.vmware.com/docs/DOC-15084

    The ThinApp team has taken down and reposted the packaging steps for building a Microsoft Office 2010 ThinApp. The revised packaging steps work with ThinApp 4.61. The ThinApp 4.61 version update has specific tuning to enable the packaging of several larger enterprise package.

    The details steps for Packaging Office 2010 can be found here:
    http://blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html

    It is interesting to note that they address both the Volume License (MKS) and Retail Package packaging steps.

    Everyone is talking about cloud these days. And no one is saying the same thing. With so much conflicting information out there, it’s hard to figure out what type of cloud solution is right for you.

    Register for this free, technical best practices event and learn how VMware can help you cut through the market hype and determine which cloud solution is right for you. We’ll show you the latest research and answer the tough questions:

    • - What is the business impact of cloud computing?
    • - Which cloud is right for my organization?
    • - How secure is my data?
    • - How do I get started?

    Learn how to leverage you existing IT infrastructure and virtualization investments to accelerate your journey to the cloud. Register Now.

    “Running a data center will become increasingly a business discussion and not a series of technical decisions.”
    —Paul Maritz quoted in the WSJ, August 29, 2010

    Agenda
    8:00 a.m. – 8:30 a.m. Breakfast, Partner Networking and Registration
    8:30 a.m. – 9:45 a.m. VMware Presentation: Building a Secure Hybrid Cloud
    9:45 a.m. – 10:15 a.m. Break and Partner Networking
    10:15 a.m. – 11:00 a.m. Partner Presentation
    11:00 a.m. – 11:30 a.m. VMware Technical Demonstration
    11:30 a.m. – 12:00 p.m. Wrap up, Q&A and Raffle

    === Register Now ===
    http://info.vmware.com/forms/KS_Reg?src=inv1

    === Refer a Friend ===
    http://info.vmware.com/forms/KS_RAF?src=inv1

    With downtime over the holidays, I’ve been pretty busy working in the home “Lab” in preparation for 2011. Part of the recent upgrades has included a complete deployment of VMware vCloud Director, vCloud Request Manager, and updates to all of my installed applications.

    I am also taking the time to make 2011 a more secure year by incorporating a few of the Virtual Appliances from the VMware Marketplace. Most notable is the installation of several VPN, Proxy, and Security appliances. I am trying the OpenVPn Mini appliance. This little gem should allow me to gain access to my home lab while traveling. I had been using just VMware View, but from time to time I find that I want to copy large amounts of data from the network to my laptop. For this, a simple VPN connection will do the trick.

    A second Virtual Appliance I am trying out is the Astaro Security Gateway appliance. This will serve as an inbound firewall for the web servers and an outbound filter for my desktops. Yes, it also has a SSLVPN, but I’ll hold off on that unless the OpenVPN turns out to be more hassle than the value I get from it. Interesting aspect of the Astaro Security Gateway is that it is free for home use. Some of the key included features to this virtual appliance include:

    • HTTP/HTTPS Filter
    • Mail Filter
    • IM/P2P Filter
    • Intrusion Protection System
    • Logging and Reporting Engine
    • WAN Link Balancer
    • Integrated Backup System
    • Firewall/NAT Router
    • Bridged or Gateway Mode Support

    I still have a wish list for 2011. More than anything, I want to upgrade the servers to something that provides a little more CPU performance, more RAM (ideally 48GB/Server), consume less electricity and produce far less noise! If you have ever been around the DELL 1950′s when they power up, you would understand. Looks like I had better start saving!

    With the addition of a few router firmware upgrades, new QOS configurations, and a SAN Upgrade, 2011 should prove to be a more productive year in the home lab.

    Are you looking to automate the Installation of the VMware Tools with a Silent Install? if you, you are in luck! Leveraging the “VMware Tools.msi” you can deploy the VMware Tools using SCCM, Altiris, or other software delivery mechanism. Valentine Hamburger, a Technical Account Manager at VMware has put together a great little guide for Silent and unattended Installations on the VMware Communities site.

    Before you begin, be sure you have all the required modules in the same directory as your “VMware Tools.MSI”. You can find all the files in the “VMware Tools.ISO” CD-ROM image. While not all the modules are technically required, the modules you intend to install will need to be present at the time of installation. So, if you want to pass on the GUEST SDK Module installation, you can exclude the GuestSDK.CAB from your install package.

    • Command.cab
    • GuestSDK.cab
    • Micros~1.cab
    • Sync.cab
    • VMXNET3.cab
    • WYSE.cab

    Depending on if this is an update or a new deployment, we need to plan ahead for a little different delivery mechanism since the command line are slightly different. Depending on your required install options, a different set of command line parameters are required. Here is the list :

    Installation options 4.0 MSI parameter Name Comment
    Toolbox ToolsCore required
    Memory Control Driver MemCtl required
    SCSI Driver Buslogic required
    Paravirtual SCSI PVSCSI not required
    SVGA Driver SVGA required
    Mouse Driver Mouse required
    VMXNet NIC Driver VMXNet required
    VMXNet 3 NIC Driver VMXNet3 not required
    Filesystem Sync Driver sync required
    Descheduled-Time-Accounting vmdesched not required
    Volume Shadow Copy Services Support VSS not required
    Shared Folders Hgfs not required
    Guest SDK GuestSDK not required
    Wyse Multimedia Support WYSE not required
    Audio Driver Audio not required
    VMCI Driver VMCI required
    WMI Performance Logging Debug not required
    VAssert SDK VAssertSDK not required
    VMCF SDK VICFSDK not required
    Thin Print driver ThinPrint not required

     

    The parameters are required to control what is installed and what modules are left out. Using the MSIEXEC command, your installation command line might look like the following.

    msiexec /i “VMware Tools.msi” ADDLOCAL=ALL REMOVE=”Hgfs,WYSE,GuestSDK,vmdesched” /qn /l* C:\temp\toolsinst.log /norestart

    Some important command line parameters include:

    • /norestart – Prevents a reboot after install. This may come in handy if you want to get the tools installed but wait until the next maintenance window to reboot.
    • /qn – Queit Installation without GUI or prompts for user input.
    • /l* <pathToFile> – Provide a location to log the installation of the VMware Tools.

     

    If you intend to update your VMware Tools, we two additional command.

    • REINSTALL=ALL – Updates the previously installed modules
    • REINSTALLMODE=vomus – Forces the installation of the new .MSI

    Our new update commandline would look like the following:

    msiexec /i “VMware Tools.msi” REINSTALL=ALL REINSTALLMODE=vomus /l* C:\temp\toolsinst.log /qn /norestart

     

    Additional commands for modifying or uninstalling the VMware Tools is addressed by Valentine in his guide as well as a detailed description of each of the modules you can install.


    Read the guide:
    http://communities.vmware.com/servlet/JiveServlet/downloadBody/12413-102-4-13370/VMware%20Tools%20-%20Unattended_Install.pdf

    Over the past four years, I have been amazed at how many companies have resisted virtualizing Oracle on VMware products because of fear of support from Oracle. Most had heard FUD over the years regarding corrupt data, performance issues, and DR nightmares from their Oracle account teams while at the same time being told to virtualize Oracle on the Oracle VM Virtualbox. While Oracle never claims the platform is better, the reasoning was Oracle could be accountable for the entire stack and the performance issues would be solely their own. This logic is flawed.

    Fortunately, we no longer need to worry about Oracle denying support for a solution on VMware vSphere. AS of November, 2010, Oracle finally opened its eye, and ears, to the customer’s feedback. The single document maintained by Oracle covering the support statements for Oracle products on VMware hypervisors has been updated. Document ID #249212.1, available on MyOracleSupport.com, now addresses all Oracle products, including Oracle Real Application Clusters (RAC) on VMware vSphere.

    From the VMware side, we wil ltakr a pro-active role in your oracle support. From the VMware Oracle Support Page, we share the following steps to ensure your issues are resolved smoothly between Oracle and VMware.

    Should you encounter a problem while running Oracle in a VMware environment, please follow these steps to ensure rapid resolution to your issue:

    When troubleshooting Oracle 10 or 11 running on VMware vSphere 4:

        Open a Support Request with Oracle Support.
        Concurrently open a separate ticket with VMware Global Support Services (GSS) using your VMware Production Support, Business Critical Support or Mission Critical Support agreement.

    VMware GSS provides support for our customers running Oracle products. VMware GSS will open a Support Request for all Oracle cases referred to VMware technical support, and will take complete ownership of the issue until resolution.

     

    If your organization is concerned about running Oracle products in a VMware vSphere Environment, take a moment to review the VMware Customer Success Stories of customers running Oracle in a virtualized environment on vSphere.

    Also, be sure to check out the VMware Communities post on Oracle RAC Performance on vSphere 4.1 posted December 16th, 2010.
     

    Links:

    Oracle RAC on vSphere 4.1
    http://blogs.vmware.com/performance/2010/12/oracle-rac-performance-on-vsphere-41.html

    VMware Support Policy for Oracle Products
    http://vmware.com/support/policies/oracle-support.html

    Oracle Database Customer Success Stories
    http://vmware.com/solutions/partners/alliances/oracle-database-customers.html

    VMware announced a promtion to get free VMware Alive VM when you purchase an eligible VMware vSphere product.  The promotion indicates you can receive VMware Alive VM allowing you to manage up to 50 virtual machines and one year of basic support at nor additional charge.  This is a great way to get in on a production product without any additional investment.

    As I stated a few days ago with the release of VMware Alive 7.2, Alive is a uniquely designed product that enables the VM administrator to have a comprehensive view of the overall performance of their complete vSphere environment.

    • Indicators of health, workload and capacity
    • Heat maps to easily locate trouble areas
    • Mapping of virtual machines to host to cluster and datacenter to get to root cause analysis
    • Trending and analytics for quick and effective problem solving

    To qualify, you must purchase an eligible product between Nov 23, 2010 and March 1, 2011.

    Promotion Details: http://www.vmware.com/landing_pages/vsphere-promotion/
    Eligible products for vSphere Promotion

    SecPoint releases their WPA Penetrator as a VM that can be run from almost any Laptop.

    WPA Cracking VMware Portable Penetrator from secpoint on Vimeo.

    WPA Cracking VMware Portable Penetrator.
    The Portable Penetrator now runs on VMware

    http://www.secpoint.com/wpa-crack-portable-penetrator-vmware.html