VMM aims to expose a common model for storage across different arrays, with end-to-end visibility of storage as it relates to hypervisor hosts. The aim is to allow IT to do more, providing deep integration into the UI and PowerShell with a minimal learning curve, streamlining storage tasks across different arrays, taking advantage of more advanced storage features.
That said, VMM is not a storage resource manager. There is no value in trying to replace partner specific tools, it is not possible to keep up with new capabilities and to attempt to be an SRM product would mean that VMM would not ship on time!
What this functionality offers the administrator is the ability to control what host groups can access in terms of available storage logical units and available storage pools.
The standard used by VMM is SMI-S and the four companies announced as supported so far are EMC, HP, HDS and NetApp.
There is support for VDS but it is largely deprecated with the future focus being on SMI-S.
For me, this presents quite a challenge if I want to use VMM to manage the storage used with the VMs because I’ve now go to make sure that the storage is “compatible” with VMM. No real news about Dell, which is my preferred supplier, which makes things extra tricky. It may be that I’ll have to stick with something like Dell’s MD3000i array which supports VDS and wait a few years until there is more clarity around SMI-S and VMM’s storage capability, and change to an SMI-S array at that time.
Having said all of that, it looks like it might be possible to get hold of an SMI-S provider for Dell’s MD arrays – both iSCSI and DAS!
… however, that appears to be for an early version of the software that Dell were working on. There seems to be a newer version from what I can gather in a manual I found:
but I haven’t been able to find the corresponding download. I am encouraged, though, that it should be technically feasible to control a Dell MD array from VMM 2012 so the hunt continues!