« Grr make your pick. Do you want Open Everything or Agility? | Main | Enterprise Hybrid Cloud Applied to SAP, and HINT: TOMORROW. »

October 24, 2014


Feed You can follow this conversation by subscribing to the comment feed for this post.

David Owen

Great insight here Chad,

As a VCE employee im really exited about all this. It opens so many doors EMC and VCE would have struggled to open individually.

It now enables VCE to have conversations with customers at every level of the spectrum.

I know its been said already but this takes VCE to that next level it would have taken a long time to achieve as a JV.


David Lapadula

Nice post -- high level flowchart summary (executive summary) with optional detailed explanations!
But we probably do want to ensure our customers and partners that this VCE+EMC announcement will not impact our ongoing vSpex investments. There are many more vSpex architectures/configs being developed, tested and released.
I believe one of EMC's 'super powers' is the ability to give customers CHOICE -- and continuing to give them the choice between VCE, individual platforms (VNX, VMax, etc.), vSpex, and others solutions you've described is a testament to how we help maximize the Total Customer Experience, and also continue to develop new solutions that meet their requirements and (hopefully) exceed their expectations.

Mark Burgess

Hi Chad,

Great stuff as always.

I have to mention the "elephant in the room" that is NSX.

I have done a lot of investigation into NSX (please see my thoughts at http://blog.snsltd.co.uk/an-introduction-to-vmware-nsx-software-defined-networking-technology/) and you have to say it looks game changing.

How much impact do you think NSX had on Cisco's decision?

Martin Casado made a great comment (over at http://www.networkworld.com/article/2691482/sdn/vmwares-casado-talks-about-evolving-sdn-use-cases-including-a-prominent-role-for-security.html?page=3) that really stuck with me - "Networks are going to be much simpler and cheaper in the future."

Doesn't sound like something that is in Cisco's best interest to me.

Best regards

Mark Burgess

Hi Chad,

I also wanted to get your thoughts on a debate that has been going on over at http://blog.nigelpoulton.com/vsan-is-no-better-than-a-hw-array/.

I understand where Nigel is coming from, but I do not really believe there is any real lock-in with hypervisors or storage - there are just too many options (more thoughts at http://blog.snsltd.co.uk/lock-in-choice-competition-innovation-commoditisation-and-the-software-defined-data-centre/).

What I am also interested in is your thoughts on:


I just do not get this, it looks like about as locked-in as you can get and way to inflexible and expensive for its target market (more thoughts at http://blog.snsltd.co.uk/vmware-evorail-or-vsan-which-makes-the-most-sense/).

I really like what VMware is doing with VSAN and NSX, and what EMC are doing with RecoverPoint for VMs, but EVO:RAIL just does not make sense - or am I missing something?

2. VSAN Kernel Modules v VSA

I completely understand the portability argument with regard to a VSA, but if you were the hypervisor/OS vendor you would not build this as a VM, you would surely bake it into the hypervisor/OS as it will be more efficient (CPU and Memory).

It reminds me of what some of VMware's NSX guys said to me recently:

1. The Kernel Module based Distributed Firewall can do 20Gbs
2. The 3rd party VM based Firewall can do 2Gbs

I think Kernel Modules win the efficiency battle by a fair margin!!!

I know you had some views on this a little while back with regard to ScaleIO.

My understanding was that ScaleIO is Kernel Modules on Windows and Linux, and currently a VSA for VMware, but this would be moving to Kernel Modules soon.

Can you explain why EMC are making these changes for VMware and what the benefits are compared to the old VSA?

Any comments would be appreciated.

Best regards

The comments to this entry are closed.

  • BlogWithIntegrity.com


  • The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by Dell Technologies and does not necessarily reflect the views and opinions of Dell Technologies or any part of Dell Technologies. This is my blog, it is not an Dell Technologies blog.