posted

11 Comments

Introduction to VMware vSphere , vSAN & VxRAIL

Some key things to keep in mind when we talk about VMware vSphere Platform , ESXi hypervisor , vSAN & VxRAIL Appliance :

  • VMware vSphere is a platform of virtualized hardware that creates a total abstraction layer between the O/S and the Hardware
  • ESXi, is a non-Para virtualized, Type1 hypervisor and therefore makes no changes to the kernel of the guest operating system
  • VMware vSAN , the industry-leading software powering Hyper-Converged Infrastructure solution,  in no  way changes the location of where compute runs, and hence does not directly impact the licensing impact of any CPU Core or Socket based licensing
  • VxRail Appliances are jointly developed by Dell EMC and VMware and are the only fully integrated, preconfigured, and tested HCI appliance powered by VMware vSAN technology for software-defined storage. Managed through the ubiquitous VMware vCenter Server interface, VxRail provides a familiar vSphere experience that enables streamlined deployment and the ability to extend the use of existing IT tools and processes.

 

Oracle Licensing Myths

There are myths floating around that

  • Oracle Licensing requires licensing every vSphere host attached to a given vCenter
  • Oracle licensing requires licensing every Site connected to the Primary site where the Oracle workloads primarily resides

 

 

These myths are perpetuated by overzealous licensing and sales teams which is in contrast of the reality of the actual Contractually Impactful documents.

 

If this were true , it would require you to license EVERY existing vSphere host in EVERY datacenter and cloud , be that yours or a company down the street as vCenter’s and SSO domains are not an obstacle to vMotion. and So by this faulty logic you would need to license every host in the galaxy.

That faulty logic would cost you many $$$ , probably buy you a beautiful island 🙂

 

island

 

This post intends to clear up the reality of how to effectively license Oracle workload on VMware vSphere & vSAN and to make it a cost effective one as well.

Oracle licensing DOES NOT change from a licensing perspective, whether you run Oracle workloads on a classic vSphere environment or Hyper-Converged Infrastructure solution like vSAN.

 

Oracle Licensing on VMware vSphere and Contractual Documents

Oracle Licensing on VMware sessions have been run successfully in many Trade shows / Events ( notably IOUG, EMC World, VMworld ) , also Webinars, where it has been proved beyond any doubt , that there are only there are only 3 documents which are contractual and relevant for any Oracle licensing discussion and contractual:

 

Oracle Partitioning Policy – Non-Contractual

There is another document called “Oracle Partitioning Policy which is often mentioned by the licensing and sales team, what they very conveniently fail to mention is that “Oracle Partitioning Policy”  is NOT a contractual document.

Two things to keep in mind about the “Oracle Partitioning Policy”

  • “Oracle Partitioning Policy” is NOT referenced in any way in the OLSA/OMA and hence is not an artifact in any Oracle Licensing discussion
  • Read the disclaimer in the document “This document is for educational purposes only and provides guidelines regarding Oracle’s policies in effect as of April 5, 2016. It may not be incorporated into any contract and does not constitute a contract or a commitment to any specific terms

Capture

So we can safely dispel with this noise and focus on the facts ie the Contractual documents.

Thanks to numerous collateral and efforts by our premier partners notably House of Brick and License Consulting , we are able to dismiss the ridiculous claim by Oracle Sales about licensing “All Sites” or “Galaxy licensing” as we call it , when it comes to licensing Oracle on VMware.

Anyone who has read the Oracle licensing document, most important, the OLSA / OMA, is well aware that Oracle licenses are either User based (Named User Plus) or Processor(Socket in case of SE2 or cores in case of EE edition)  based.

More information about it can be found in the below documents:

SOFTWARE INVESTMENT GUIDE

Database Licensing

Oracle licensing is not Memory, Storage, Cluster, vCenter or Network based, its either User based (Named User Plus) or Processor(Socket in case of SE2 or cores in case of EE edition)  based.

So you do not need any memory segmentation, storage segmentation or for that matter any network segmentation based on the above.

Keep in mind none of these segmentation requirements are stipulated in the OLSA / OMA which is a contractual document.

The illustration below of an “Oracle Parking Garage” from House of Brick sums up the FUD!!!

 

hobhttp://houseofbrick.com/the-oracle-parking-garage/

 

Example of Licensing Oracle workloads on classic VMware vSphere Cluster

For example, let’s say we have a vSphere Cluster dedicated to run Oracle workloads called “OraCluster” with 3 ESXi servers, each ESXi server having 2 socket x 10 cores each.The processor is Intel Family.

Total no of effective cores for licensing Oracle workloads in “OraCluster” using Enterprise Edition (EE)
= Absolute number of cores in cluster * Processor Core Factor
= 3 servers * 2 sockets * 10 cores/socket * Processor Core Factor
= 60 * 0.5
= 30 Effective cores liable for Oracle licensing

The Processor Core factor table is published by Oracle and can be found at the below url:

corefactorhttp://www.oracle.com/us/corporate/contracts/processor-core-factor-table-070634.pdf

 

 

VMware vSAN / VxRAIL Appliances

It should be known that running vSAN In no  way impacts Oracle licensing and existing tools of segmentation (DRS affinity groups and rules) and existing auditing tools (VMware LogInsight) perform as expected.

vSAN 6.5 is the fifth generation of VMware’s industry-leading software powering Hyper-Converged Infrastructure solutions. vSAN’s unique in-kernel architecture delivers flash-optimized performance and elastically scalable storage for any virtualized application, with TCO savings of up to 50%.

 

 

Running Oracle workloads on VMware vSAN (Hybrid/All Flash)

As part of the effort to validate VMware Virtual SAN ability to host business critical applications we have published a reference architecture (RA) which covers the design, configuration and performance study of Oracle Real Application Clusters (RAC) on Virtual SAN Hybrid 6.1.

With VMware All Flash Virtual SAN 6.2, we introduced a suite of new features for data integrity and space efficiency including Checksum, Erasure Coding, Deduplication and Compression.

Using these features we developed an architecture for deploying and running Oracle 12c OLTP and DSS workloads on VMware All Flash Virtual SAN 6.2.

Oracle Database 12c on VMware VSAN — Day 2 Operations and Management

 

 

Licensing Oracle workloads on VMware vSAN (Hybrid/All Flash)

Oracle licensing DOES NOT change from a licensing perspective, whether you run Oracle workloads on a classic vSphere environment or Hyper-Converged Infrastructure solution like vSAN.

Oracle VM uses the compute power of the ESXi servers in the vSAN Cluster to run the Oracle workload just as in the case of a Classic vSphere Cluster.

As pointed our earlier, Oracle licenses are either User based (Named User Plus) or Processor(Socket in case of SE2 or cores in case of EE edition)  based regardless of whether Oracle workloads run on ESXI servers in a vSAN cluster OR vSphere cluster.

In the example below, we have a vSAN cluster called “vSANCluster” comprising of 4 ESXi servers contributing Compute, Storage & Network resources to the cluster.

vsan1

Each ESXi server has 2 socket x 16 cores as shown below. The processor is Intel Family.

vsan2

Oracle VM’s created can be pinned using CPU Affinity to a set of ESXi servers in the “vSANCluster” for Oracle licensing reasons.

Let’s see how we can go about doing it.

Create a VM/Host Group mapping as shown below. In the example below, “OracleVM” is the group created which has a VM “testoravm”. There is a 1:1 mapping between the “OracleVM” group and “testoravm” VM.

vsan3

Create a new Host Group “OracleVM-Host” as shown below. Hosts w2-pe-vsan-esx-029.eng.vmware.com and w2-pe-vsan-esx-030.eng.vmware.com are part of this host group.

vsan4

Create new VM/Host rules as shown below which basically will have the VM group “OracleVM” created above (with the “testoravm” VM in the group) mapped to the Host Group “OracleVM-Host” with a  “must run on hosts in group”.

vsan5 vsan6

In effect, the Oracle VM “testoravm” is now constricted and contained to run in the Compute Segmentation effectively created above.

In the example above, to run Oracle workloads in the above scenario:

Total no of effective cores for licensing Oracle workloads on 2 ESXi servers in the vSAN Cluster above using Enterprise Edition (EE)
= Absolute number of cores in cluster * Processor Core Factor
= 2 servers * 2 sockets * 16 cores/socket * Processor Core Factor
= 64 * 0.5
= 32 Effective cores liable for Oracle licensing

As we can see from the above example, we only need to license 2 ESXI servers for Oracle workloads as Oracle workloads runs only 2 ESXI servers, regardless of the size of the vSAN Cluster.

The ultimate proof of the above statement comes from the Oracle OLSA/OMA which defines Processor as “Processor: shall be defined as all processors where the Oracle programs are installed and/or running.”

From the example above Oracle VM “testoravm” can run only on hosts w2-pe-vsan-esx-029.eng.vmware.com and w2-pe-vsan-esx-030.eng.vmware.com based on the DRS Affinity Rules.

 

Virtual Machine log file

The second important artifact which helps to prove without any doubt that the Oracle VM “testoravm” ran on only 2 ESXI servers is via audit trail in the Virtual Machine log file.

By default, ESXi/ESX hosts store virtual machine-specific logging in the same directory as the virtual machine’s configuration files. The default log file name is vmware.log.

Let’s see the contents of the vmware.log file for “testoravm” when we power it up.

[root@w2-pe-vsan-esx-029:/vmfs/volumes/vsan:52803547e520f694-1f6104395ada7b7c/05735458-cc86-e1e9-ca71-0025b501004e] cat vmware.log
2016-12-27T21:09:09.124Z| vmx| I125: Log for VMware ESX pid=2597049 version=6.5.0 build=build-4564106 option=Release
2016-12-27T21:09:09.124Z| vmx| I125: The process is 64-bit.
2016-12-27T21:09:09.124Z| vmx| I125: Host codepage=UTF-8 encoding=UTF-8
2016-12-27T21:09:09.124Z| vmx| I125: Host is VMkernel 6.5.0
2016-12-27T21:09:09.091Z| vmx| I125: VTHREAD initialize main thread 0 “vmx” tid 2597049
2016-12-27T21:09:09.092Z| vmx| I125: Msg_SetLocaleEx: HostLocale=UTF-8 UserLocale=NULL
……….
……….
2016-12-27T21:09:09.124Z| vmx| I125: Hostname=w2-pe-vsan-esx-029
2016-12-27T21:09:09.124Z| vmx| I125: IP=127.0.0.1 (lo0)
…..
[root@w2-pe-vsan-esx-029:/vmfs/volumes/vsan:52803547e520f694-1f6104395ada7b7c/05735458-cc86-e1e9-ca71-0025b501004e]

Based on the DRS Affinity rules, “testoravm” can only power on ESXi servers w2-pe-vsan-esx-029 or w2-pe-vsan-esx-030.

More information about the vmware.log files can be found in the below KB articles:

Locating virtual machine log files on an ESXi/ESX host (1007805)

Location of log files for VMware products (1021806)

Another product from VMware which helps for purpose of Oracle Auditing is the VMware vRealize Log Insight which delivers heterogeneous and highly scalable log management with intuitive, actionable dashboards, sophisticated analytics and broad third-party extensibility. It provides deep operational visibility and faster troubleshooting across physical, virtual and cloud environments.

VMware LogInsight dashboard can help customers gather by means of audit trail records which can then be presented to Oracle LMS team as proof of Oracle workload footprint within a vSphere Cluster or a vSAN cluster.

This video demonstrates the capabilities of VMware vRealize LogInsight for Oracle License Compliance.

Important factor to keep in mind is vSAN’s in kernel design reduces the need for compute sprawl and hence more Oracle licensing as compared to some of the other competitor products found in the market.

Conclusion

In conclusion, Oracle licensing does not change from a licensing perspective, whether you run Oracle workloads on a classic vSphere environment or Hyper-Converged Infrastructure solution like vSAN. Keep in mind, Oracle licensing is not Memory, Storage, Cluster, vCenter or Network based, its either User based (Named User Plus) or Processor(Socket in case of SE2 or cores in case of EE edition).

To reiterate, there are only 3 documents which are contractual and relevant for any Oracle licensing discussion and contractual:

  • Technical Support Policy
  • Processor Core Factor Table
  • Oracle License and Service Agreement (OLSA)  / Oracle Master Agreement(OMA)
    • The OLSA/OMA defines Processor as “Processor: shall be defined as all processors where the Oracle programs are installed and/or running.”

All Oracle licensing collateral on vSphere can be found at

 

To sum it up , the myths perpetuated by overzealous licensing and sales teams is the cause of FUD which customers are facing today.

Who you gonna call ?  “Myth busters”

For any Oracle Licensing on VMware help , please reach out to your respective VMware Account teams who can get our team involved in a discussion (Internal VMware folks can reach directly to us at the Tier1-Apps-Sales-Support team mailing list) and we can definitely help guide you and connect you to some of our premier partners if required for further discussions.