Red Hat’s virtualization strategy has redundancy – Quo vadis?

A couple of days there have been some reports that Red Hat will release a commercialized version of deltacloud, an abstraction layer for different kinds of virtualization technologies and clouds such as VMware, RHEV, Amazon EC2 etc.

Red Hat puts a lot of resources on virtualization, they maintain and/or sponsor multiple projects in parallel. The most important from my point of view is libvirt which is as well an abstraction layer for different virtulization technologies such as VMware, KVM, Xen and others. Libvirt and deltacloud are partially redundant.

It is not the only redundancy created by Red Hat. There is also O-virt “competing” with RHEV. Both are not tightly bound to RHN satellite or Spacewalk.

RHEV works with system templates similar to those at VMware. On the other hand: Koan, together with cobbler is a deployment software for virtual hosts and was recently bundled with RHN satellite.

Not all of those Red Hat virtualization projects are working well together. So the question arises: What is the strategy of having such redundancies of projects? Why not integrating all of this projects and glue them together?

Lots of questions…

Have fun!

2 thoughts on “Red Hat’s virtualization strategy has redundancy – Quo vadis?

  1. wariola says:


    Just to share regarding the Red Hat technology. I dont think redundant is the right word for it, “open” should be the right word. Red hat always open up all their technology with the community regardless if its make sense to business for now.

    Also just to share regarding Libvirt, RHEV and Deltacloud. Libvirt is the hypervisor agnostic toolkit to abstract the hypervisor regardless of the technology. This means u can use Libvirt to connect to Xen, KVM, VMWare, Virtualbox etc and manage them using standardize tool.

    On the other hand Deltacloud is the abstraction layer to abstract cloud platform e.g. Amazon, Rackspace, RHEV, VMWare cloud, Eucalyptus etc. This is another layer on top of virtualization but more for the cloud management tool.

    RHEV on the other hand is different software altogether from a company called Qumranet (creator of KVM). Red Hat is now merging both RHEV and oVirt (which was being done before the Qumranet acquisition) and even some RHEV component using tools from the oVirt project.

    More info you can get at my blog

    • Luc de Louw says:

      Red Hat is well known for being open and I’m not questioning that. Some projects mentioned are doing partially the same job, thus redundancy.

      Why having RHEV (which will be open-sourced next year when rewriten to Jboss and Hibernate) when O-virt can do ~80% of its job? Why using VMware-like templating of KVM guests in RHEV when having Spacewalk and Cobbler for deployment?

      They should think about glue together some of those projects.

      BTW: does not exist. Did you mean ? Found some nice articles there.



Leave a Reply

Your email address will not be published. Required fields are marked *