Interesting, but this does rather assume that Oracle LMS will recognise licence partitioning beneath the VMware cluster level - is there any documentation to support this?
Of course Oracle and DRS host affinity rules (i.e. allowed or not) got a lot of publicity last year following this interview: http://www.licenseconsulting.eu/2012/08/29/vmworld-richard-garsthagen-oracle-on-licensing-vmware-virtualized-environments/
And whether Oracle wlll extend something like Oracle Trusted Partitions (http://www.veriton.co.uk/roller/fmw/entry/oracle_trusted_partitions_dynamic_and), to apply to any hardware/hypervisor remains to be seen...
As part of the process of releasing the Blue Medora Oracle EM Plugin for VMware we’ve had discussions with over 100 customers who, despite Oracle’s ambiguity re: VMware support and licensing, are moving ahead and deploying Oracle on VMware.
Our aim with this new Oracle EM-based plugin is to simply provide a set of tooling that enables customers to more safely deploy their Oracle virtual machines into vSphere Cluster and sub Clusters by monitoring VMware virtual machines containing Oracle and ESX configuration and alerting if any Oracle workload has traveled to a non-licensed ESX host OR if warning that the risk exists that the Oracle workload may travel to a non-licensed ESX host in the future via a “non-locked down configuration”. Host affinity is one of those configuration values monitored for risk.
Finally, we are going to provide an Oracle-EM based audit log of virtual machine mobility so that administrators can look back a day, week, month, year, etc and understand which ESX hypervisors (licensed or unlicensed) a particular virtual machines running Oracle has existed on.