« VMworld 2014: Link Library! | Main | VMworld 2014 SDS Data Protection = Recoverpoint for VM »

August 22, 2014


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

Fletch Hasues

I agree with most of your comments. The reason I like VIO is that it gives one access to VMWare assets via its API and use so end users and developers can utilize that API to make use of what ever "stack" one is using (KVM+Ceph), (ESX+EMC), etc. I've been investigating VOVA for the last month to get an understanding how the configuration of such works and it seems really interesting. It also allows one to leverage existing VMWare infrastructure to test deployments.
I am a bit interested in noting that the above diagrams listing ViPR as more of an object store as opposed to block. It would seem to me ViPR could be at least used as block more so even than object, so I'm not sure if I understand the diagram above.
Also, regarding comments with Red Had and Ceph, I wonder if the community will see a large delay in packages for CentOS on Ceph's site for newer releases of Ceph as opposed to Red Hat. That is currently the case (but is easy to work around at the moment), however, I don't want to speculate as I'd rather let Ceph/Inktank community discuss this over my opinion of the matter.

On a separate note, why is typepad requesting to "manage my G+ profile"? That...seems a bit involved, and unless those granular things are explained, I would advise anyone merely using the federation to post.

Kenneth Hui


Cinder block services in VIO is implemented via VSAN so ViPR/ScaleIO is not required.


Chad Sakac

@Ken, @Fletch - I think the key observation I'm trying to make is that VIO for BETTER and for WORSE has a core linkage to the full vSphere stack. So, yeah - you can use VSAN to bolt right to Cinder as Ken notes - thus not needing the ScaleIO stack or the ViPR Controller. Since vSphere doesn't have a Object stack - hence the ViPR Object stack.

My observation (from the customers I talk to) - they are split. Many feel (like you do, Fletch) that they like that it gives them leverage from their existing vSphere assets. Others feel as strongly that they don't want to be "pinned" into the vSphere stack under the openstack framework.

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.