from Maish Saidel-Keesing got the ball rolling.
Could it be that the design of the client itself helps perpetuate the myth the resource pools is an organizational unit, one that should be used as a way of grouping VMs? As Frank says;
Now, if you could redesign the vSphere Client, based on your own experience, what would you change?
I can see that in many cases, a lightweight vCenter Simple Mode client would do the trick. Give your VM admins the Simple Mode client, and they won’t have to worry about resource pools, HA/DRS and other advanced features. Let them administer the VMs, like adding networking, powering on/off etc. The same applies for your storage admins. Give them a small, limited, client that only allows them to configure storage aspects.
I know you can do most of this with permissions etc, but I still feel a limited client could be one way to go.
In other cases, like mine, it won’t help splitting up the client into smaller chunks. As in most SMBs, I wear a lot of different hats during a normal working day. I’m the networking-/storage-/operating-systems-guy in a small shop, where there simply isn’t room for delegating all these tasks to specialized teams or even other admins.
Perhaps dividing the client into specialized sub-topics would help?
A task based user experience where you can select between “VM Operations”, “vSphere Operations”, “Storage Operations” or “Network Operations” as your initial choice, and then limit what you can configure based on your initial choice would help organize the screen real estate? You could also have sub-sections like “Monitoring VMs”, “Monitoring Storage” and so on, displaying a performance overview as the initial point of entry.
You could still have an “Advanced Mode” that works the same way the vCenter Client works today, but the default would be a simplified experience that is based on the task you have at hand.
Am I completely out on a limb here, or is this semi-rant making some sense, somewhere? What would you change, and how?
- Developer meets PowerCLI - awesomeness ensues —
- VMware vSphere Hypervisor Licensing and Cost —
- Using USB Pass-through in vSphere 4.1 —
- Automatically Name Datastores in vSphere? —
- Can you combine vSphere Host Cache and vFlash on a single SSD? —