I had a discussion earlier this week with Cody Hosterman from EMC. Cody was working on VASA & Profile Driven Storage, and spotted some anomalies in the way the feature works with RDMs, VMware's Raw Device Mappings.
RDMs, as the name implies, using a mapping file to maintain details about a physical LUN that is presented directly to a Virtual Machine. This mapping file sits on a VMFS filesystem. Now, even though the underlying LUN/Raw Device may have a unique set of capabilities, it seems that Profile Driven Storage is using the capabilities of the VMFS volume on which the mapping file resides (and not the physical device) to determine if the RDM is compliant or non-compliant with the capabilities defined in the profile.
It has since transpired that RDMs are not supported by Profile Driven Storage feature at this point in time. Just a heads up in case you come across something similar with your implementation. Good catch Cody.
We'll work on getting a solution to this into a future release, but no timeframes yet I'm afraid.
Get notification of these blogs postings and more VMware Storage information by following me on Twitter: @VMwareStorage
