On the 7/28 Virtualization Security Podcast, we were joined by Robert Martin of Mitre to discuss Mitre’s new CWE, CWSS, and CWRAF tools to aid in software and system security evaluation. We put a decidedly cloud based discussion around these tools to determine how they would be used by those that program within a PaaS environment, make use of SaaS, or other cloud services.
Business Agility ...
• • 0 Comments
So you are a loyal VMware customer. You have licenses for vSphere 4 and you are about 40% virtualized. Based upon the revised vRAM entitlements in the revised vSphere 5 licensing, you think you are going to be OK as you progress through the more demanding business critical purchased and custom developed applications that lie in front of you. But you would like a hedge and a simple way to manage the second hypervisor that is a part of that hedge. Help has arrived.
Over the last few months we have identified a trend towards “diversity” in the PaaS provider marketplace. Platform as a Service has become Platforms as a Service, the providers are offering multiple choices at each layer of the platform infrastructure, and seeing their role as automating the provisioning of properly-configured instances as required at each layer of the stack.
On Aug 2nd, there was another entrant to this “diverse” PaaS provider marketplace called Cumulogic, a startup with a PaaS cloud positioned alongside Red Hat OpenShift and VMware CloudFoundry that we identified earlier.
Trend Micro provided us a very interesting info graphic on a Journey to the Public Cloud with a list of which of their tools secure that Journey. What is interesting about this info graphic is the steps outlined in this journey to the Cloud and the threats and issues as you step along this path. These steps are well thought out and are useful to everyone as they look at their virtualization and cloud security options moving forward.
Cloud Computing ...
Impact of Latest vSphere 5 vRAM Licensing Model upon Data Center Virtualization and Virtualization Management
, • • 7 Comments
VMware has updated the vRAM pricing for vSphere 5 to address certain customer issues, and deserves a great deal of credit for acting this quickly and decisively to the feedback that was generated by the initial announcement. However, even with the new vSphere 5 vRAM pricing the question is now raised as to whether competing and less expensive virtualization platforms are acceptable for some entire companies, and some use cases within what used to be 100% VMware shops. VMware has created an opening for Microsoft, Citrix, and Red Hat. As this sorts itself out, the virtualization platform landscape will change – resulting in a minimum in a new focus on tools to manage multiple virtualization platforms.
VMware has made significant changes to the recently announced vRAM based pricing. The single most significant change is that potential barriers to the virtualization of memory intensive business critical applications have been eliminated by ensuring that no application no matter how big can cause a charge of more than 96GB to be levied against the pool of available vRAM.
I was reading through a recent article about the new Java 7 release, which contradicts Oracle’s current support statement with respect to licensing. The License from Oracle exclusively states Java 7 is only supported on those hypervisors Oracle currently supports: Oracle VM, VirtualBox, Solaris Containers, and Solaris LDOMs except where noted. That last phrase is rather tricky, so where do we find such notes. Is the noted the support document stating that they support Oracle products within a VMware VM? Or is it somewhere else in the license? This leaves out all major hypervisors: Citrix, VMware, and Microsoft. If you cannot find a note saying things are supported, somewhere.
This implies quite a bit for the future of Java support within most PaaS environments being built today. In essence, they cannot upgrade to Java 7. Which means they may fall behind. This would impact OpenShift, Amazon, Google, CloudFoundry, SalesForce, and others.
VMware has done the right thing by taking care of their enterprise customers and making sure that they know that they can purchase vSphere 5 licenses under the terms of their existing ELA’s. The vast majority of smaller customers who run a small number of purchased applications are unlikely to be impacted by the new vRAM licensing, as their is probably plenty of vRAM headroom to take care of their needs. The issue is with customers who are not quite large enough to have an ELA, and who have sophisticated mixes of purchased and internally developed applications – and who are trying to push the density envelope in order to maximize their return from their investment in VMware. This customers are going to have to look at the new licensing in the above terms and make their own decisions.
Five months since Goldman Sachs took a reported 28% stake in UK desktop virtualization specialist AppSense, the signs are that it is starting to expand its US presence by hiring a new Silicon Valley design team that will be based in the company’s Santa Clara offices.