Programs licensed on a processor basis may be accessed by your internal users (including agents and contractors) and by your third-party users. Processor shall be defined as all processors where the Oracle programs are installed and/or running. But as Spithoven’s article is more detailed, let’s use it as the foundation for our analysis. Spithoven’s article literally glamorizes the idea of Oracle on VMware customers amending their Oracle agreements with non-standard terms.ĭata Intensity’s 23 August 2018 post arrived at similar conclusions. I wrote: “How arrogant of any of us to ever have assumed to stand on our contractual privileges.” Thompson posted the comment: “Excellent analysis, thanks.” Yet ITAM’s posting of Spithoven’s 5 September 2018 article “Oracle on VMware – adding non-standard terms to your Oracle agreement” has had me wondering if Thompson changed his mind. In that post, I called out b.lay’s Richard Spithoven for his assertion that IP owners could determine the rights with which end users use their software, and ITAM’s Martin Thompson for his concern over our advising licensees to take a gutsy approach with Oracle. Oracle blog post and the supporting links in it made clear there is no obligation to go along with Oracle’s attempt to redefine “installed” and to license the prospect of movement to additional vSphere servers. But now that vSphere 5.5 Extended Support expires September 19, 2020, and vSphere 6.x is designed to allow live migration anywhere on the planet, what are these organizations to do? Might agreeing to non-standard terms with Oracle resolve the issue? As vSphere 5.5 only allowed vMotion within a vCenter, these VMware users licensed an entire vCenter for Oracle, thus avoiding the argument with Oracle. If an organization’s vSphere 5.5 Extended Support was motivated by Oracle licensing concerns, I’m confident that’s dirty money that VMware didn’t want. I suppose the extended support fee acts as an incentive to upgrade to vSphere 6.x. This Micronauts post lists the vSphere 5.5 Extended Support fee at $300,000. – Everyone else that’s wondering what this article is really about. – Those that paid the vSphere 5.5 extended support fee out of fear of Oracle licensing consequences, and I imagine those reading that title will be divided into two groups: That said, if you bought 5.5 Extended Support primarily out of concern for Oracle licensing, we strongly suggest you have better things to do with your money than continue to pay this fee. We have updated our blog post’s title and body text accordingly. VMware Corporation has affirmed to us that since our original publication of this blog post, the availability of vSphere 5.5 Extended Support was changed to two years - through September 19, 2020. VMware KB 51491 originally published vSphere 5.5 Extended Support as available for one year only, through September 19, 2019.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |