Oracle Licensing on VMware: The truth is revealed!
One of the main pain points of virtualizing Oracle is not the technical aspect of it (there are tons of technical white papers that can help you with that), but instead, licensing.
VMware always defended that fact that their host affinity rules along with vMotion logging is a valid way of partitioning clusters for licensing purposes. Oracle sales reps and licensing whitepapers have always defended that VMware’s partitioning (unlike OracleVM) is not recongnized has “hard partitioning” but rather soft partitioning, although OracleVM uses a very similar technique to keep the VMs on specific set of hosts in a cluster.
This being said, Richard Garsthagen, Director of Cloud Business Development EMEA for Oracle has publicly stated that VMware’s host affinity rules and vMotion logging (used inclusively) are valid for purposes of establishing where Oracle software is “installed and/or running” for purposes of the Oracle Software License Agreement (OSLA).
Want proof? Watch the video below.
Now here is the kicker. Oracle requested a takedown of that video, although it is still up on youtube, it has been unlisted and can only be access directly via a link. Oracle has also updated their Virtualization Blog with a statement that “clears up” misconceptions from VMworld 2012.
-that your definition is pointing out that you need to license those processors where the Oracle software is installed and/or running.
-no useless whitepaper, LMS or Salesrep should convince you otherwise.
-external lawyers support this position.
Hopefully, spreading the word on this issue will help rattle some cages and maybe one day we may have some consistent answers from Oracle.