VM Sprawl?

We all know how it starts. You said, 'sure, just this once.' Someone said, 'psst, buddy, try this out.' You were at that wall. You needed a boost. Your business partners needed faster turn around, your budget dollars got crunched. Everyone else was doing it. Maybe you just though it would be cool.

You virtualized your first production server.

And it was good. It was great. You repurposed some VMware licenses from your test lab, grabbed some under-utilized hardware and went to town. Print servers? Check. Ten to one consolidation. Secondary domain controllers? Why not put one on the print host? Great. Marketing database running at single-digit CPU loads? Why not guest that on the new eight-way box in the lab; Marketing will never know...

Another year rolls around, your ops budget received formal approval for an ESX rollout and you learned the joys of vMotioning across 20 hosts. Downtime is a thing of the past. Your x86 service manager is queued up for a fat performance bonus; delivery and performance metrics for service have never been better.

Then it happens. The hairs on the back of your neck start to itch.A compliance audit.

You realize that you can't get an accurate inventory of production 'servers.'

Your ops managers are having difficulty tracing root cause for intermittent performance problems.

You're suffering from an acute case of vMotion-sickness.

You need to manage your VM sprawl.All major virtualization host platforms have some level of bundled management tools. XenCenter offers a bunch of management options for free... VMware Infrastructure 3's Virtual Center starts to sound like a good idea in hindsight. A $6K license and a SQL build later and that "VMotion + storage VMotion" module is looking pretty good, too.

Are bundled tools good enough? Should you start spending some serious bank on ESX plug-ins or 3rd party management tools? As with most questions in IT, the correct answer, as always, is 'it depends...'

What do you think? Any good stories from the real world out there?