VM Junkie

August 31, 2010

VMworld session TA7805 – Tech Preview: Storage DRS

Filed under: vmworld — ermac318 @ 4:52 pm

Irfan Ahmad presenting, he presented last year on what became Storage I/O Control.

  • Storage DRS is a “stealth” project at VMware
  • Big problem is a VM admin doesn’t necessarily know what class of disk or how many spindles are behind a particular datastore.
  • Create a new primitive called a “datastore group” which is a new domain like a DRS cluster. Note from me: This will of course dovetail nicely into vCD service levels!
  • Storage DRS would automatically load balance across multiple datastores in a datastore pool.
  • When you create a new VM, you place it on a datastore group and it does auto-placement. Takes both free space and I/O into consideration
  • ESX host will gather both free space and I/O stats to help balance for initial placement as well as Storage VMotions.
  • Cluster-datastore group relationship is many to many – a datastore group can span clusters and a cluster can have multiple datastore groups.
  • Recommend all datastore groups are visible from all hosts but not enforced, much like existing datastore presentation in clusters. Storage DRS will do best effort if you don’t follow this, though.
  • You can have Storage DRS affinity rules – keep these two VMs on different arrays or keep all disks from this VM on the same datastore.
  • Datastore Maintenance Mode! Say this datastore is going down and it’ll auto SVMotion all VMs off into other LUNs in the same pool.
  • You can of course add datastores to an existing group like adding a host to a cluster.
  • When you enable it you can do it on Capacity or Capacity and I/O (important for virtualized arrays like EVA where a group of LUNs shares same performance pool)
  • You can set an I/O latency metric so that if latency gets above 15ms it’ll move stuff to a datastore with lower latency. Really smart way to determine if I/O capacity is too high.
  • Balancing will only happen every few days, not every hour like a VMotion.
  • Initial placement will take into account both DRS and StorageDRS metrics, as well as how well connected the datastore is. For example, if datastore is hooked up to all hosts it will prefer that over a datastore only connected to 1 or 2.
  • You can balance capacity based on keeping them all withing a % of each other (in other words prefer balance) or just try to keep them below a certain % (just try to avoid making a datastore full)
  • It even takes into account growth rate of thinly provisioned disks when determining a good placement! Wow, that’s smart. Weights powered-off VMs less since their I/O is generally 0 when off.
  • Prefers moving VMs with low SvMotion overhead (like move smaller VMs before big ones, like DRS).
  • Does load balancing by knowing a more powerful datastore (one with more disks behind it) will have latency degrade slower than a less powerful datastore. This insight is used to model the performance to make smart migration choices.
  • Also model metrics of individual virtual disks and feeds that into the model.
  • They did a man vs. machine test. Made 13 VMs with standard workloads, gave all info to 2 storage admins at VMware vs. Storage DRS algorithm. While IOPS were about the same between experts and algorithm, algorithm beat them significantly on latency!

This was the best session I went to all day. This once again reminds me why VMware makes such cool products – they really understand problems and they have really smart people trying to solve them.

Advertisements

VMworld sesson DV7180 – ThinApp Futures

Filed under: thinapp, Uncategorized, vmware, vmworld — ermac318 @ 3:17 pm

Cool highlights from this session, I’m going to skip all the pre-ThinApp 4.6 stuff since it’s old news:

  • ThinApp (as of 4.6) now does transparent page sharing for applications (like in TS environments) just like ESX does for VMs. Pretty neat!
  • In ThinApp 4.6 you can “harvest” IE6 straight out of an XP system and run it on Win7. Only WinXP specific file that gets put in the package is Shell32.dll, otherwise icons and menus don’t work correctly. The resulting ThinApp performs like IE6 SP1.
  • ThinApp Converter which is included in ThinApp 4.6 allows you to automatically build a package from an automated installer. You can take existing install packages (like from Wise, Alritis, or LANDesk) and convert them to ThinApp packages easily with a simple command line and a blank VM.
  • The futures stuff was talking about a new features called “ThinApp Factory.” It’s a prototype which can download RSS feeds of applications and automatically download the app installer, silently install it and capture the package using ThinApp Converter, and then publish it to users or allow users to download it from an “App Store” kind of thing. This will probably feed into the Horizon stuff they showed this morning in the keynote.

VMworld session DV7907: View Reference Architecture

Filed under: Uncategorized, view, vmworld — ermac318 @ 12:34 pm

Session is around updating the reference architecture for View 4.0 to View 4.5.

  • Goal of View is to delivery Consumer Cloud experience for the Enterprise.
  • Goal of the 4.0 reference architecture was to simulate a realistic desktop workload, validate 2,048 users.
  • Session turning into a pitch for UCS very quickly…
  • Now they’re off to talk about RAWC, which is really old news. New version of RAWC supports simulating workloads on Win7. Still can only simulate a preselected set of apps, no custom app load testing. You can learn more about rock on its Youtube channel.
  • View 4 reference architecture was run on UCS, CX4, vSphere 4.0 and WinXP SP3.
  • Just released – Win7 optimization guide, includes a BAT file that optimizes the VM for you! Already found it here.
  • Going through all the stuff they had to do to the Storage to make it perform. Wouldn’t it have been nice if it was on virtualized storage and you didn’t have to worry about RAID groups and all that crap? 🙂
  • View 4.0 Reference architecture they got up to 16VMs/core. I think this is super aggressive and I don’t recommend customers size for this #.
  • Finally we get to View 4.5 stuff! Talking about the new Tiered storage capabilities of View 4.5
  • They’re putting SSDs in each physical server… again more Cisco specific stuff. I think sticking SSDs in every server drives up the cost too much. Plus wouldn’t it kill vMotion.
  • They did the View 4.5 test with a single non-persistent pool.
  • They see CPU being a bottleneck on optimized Win7 32b deployments… but they were only giving each Win7 VM 1GB of RAM.
  • During the Q&A, asked about HA/VMotion. This reference architecture doesn’t allow for VMotion or HA. And Non-Persistent pools require some sort of 3rd party profile management to make it work. If you want to take a system down you’ll have to do it after hours. Don’t like it! I’ll stick with SANs to give full functionality instead of neutering 1/2 the Enterprise functionality.

August 30, 2010

Un-announced feature of vCenter 4.1: VMware Server 1.0 support!

Filed under: Uncategorized — ermac318 @ 10:54 am

Something amusing that I noticed in the compatibility matrix a couple weeks ago:

Holy cow, they finally got VMware Server support in vCenter! It only took them… 4 years? I wonder why they even bothered. Anyone wanna try it out?

August 29, 2010

VMworld 2010 coverage!

Filed under: Uncategorized — ermac318 @ 10:29 pm

I”m here in San Francisco and I will be blogging and tweeting about VMworld! Follow along on twitter (I’m @justinemerson) or check the recent tweets on the right.

Sunday and Monday I’ll be busy with PTAB meetings (Partner Technical Advisory Board) doing stuff I can’t tell any of you about. =) But Tuesday through Thursday expect content from here. Hope to see you all there! I’m the nerdy looking redhead. Come up and say hi!

Create a free website or blog at WordPress.com.