Welcome to The Virtualization Practice’s week-long coverage of VMworld US 2015. Tune in all week for our daily recap of the major announcements and highlights from the world’s premier virtualization and cloud conference.
VMworld US 2015 continued in force yesterday, beginning with a long but powerful general session/keynote talk. Carl Eschenbach, VMware’s president and COO, set the stage for a slew of announcements around VMware’s “One Cloud, Any Application, Any Device” approach to computing and a seamless federation of all types of clouds, supporting both traditional and new cloud-native applications. A variety of VMware leaders joined him on stage to talk about the various aspects of these announcements and how they mesh with their overall strategy. While each of these areas could give rise a whole series of posts by themselves, I’ll summarize the major points.
Every VMworld conference is different, with a different tone and pace to it. At this year’s VMworld US, it felt like everything was evolutionary and very little was revolutionary. Icing that cake, VMware broke the decade-old trend of new vSphere announcements. Sure, the keynotes mentioned the next version, mostly by talking about some of the features it contains, but release dates, feature sets, and details were scarce, if available at all.
VMware has joined the ranks of the hyperconverged, announcing VMware EVO:RAIL, a solution built on its vSphere foundation coupled with VMware VSAN. Readers here know that the converged infrastructure available for years now solves some problems in IT, but frankly, most of those problems are political. The guts of converged infrastructures are largely business as usual, have many of the same needs and time sinks as traditional infrastructure, and comprise largely the same inflexible hardware you’ve always used.
Let me start out by saying that I see more discussions about greenfield deployments of products than I do of migration/integration by vendors. Personally, I think there is no such thing as a greenfield deployment unless the organization is just starting out, creating a brand new data center, or perhaps has money to waste. In most cases, what is defined as greenfield is really just a grain of sand on an island of technology that still needs to integrate into the greater organization. As such, that integration should be the foremost thought when products are developed. But instead, it is not, and effort goes into becoming that island or into a replacement install that is still an island.