Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So OpenShift virt replaces oVirt? What was the reason for dropping oVirt?


Remember, oVirt an upstream virtualization project, the product we derive from it is Red Hat Virtualization (RHV). From the development and deployment side of things, Red Hat has chosen a direction that is primarily container based going into the future, betting a lot of this on OpenShift. This decision was made a few years ago before anything with Broadcom/VMware was occurring.

OpenShift Virtualization (based on KubeVirt) exists to provide a path of migration for "legacy" VM environments to containers, allowing admins to maintain one platform in a consistent manner (Kubernetes resources) while giving the teams that can to evolve their applications to containerized deployments.

I believe there are plans to get the management capabilities of RHV into OpenShift Virtualization, I'm not quite sure how far that's gotten. In terms of virtualization solutions from Red Hat, we have the following:

- KVM on RHEL. With the announcement of the RHV EOL, we removed the restrictions on how many guest VMs you can run simultaneously on RHEL. Note that this is different from the RHEL for Virtual Data Center (VDC) subscriptions we sell; it's just the removal of the contractual limitation, it doesn't entitle your guests.

- Red Hat OpenShift Virtualization: already discussed.

- Red Hat OpenStack: If you need to be running a broad private cloud platform that has a virtualization component.


KubeVirt is the upstream. Essentially so there is common management/operational model between virtualization and containers rather than having a Kubernetes-based one and a largely independent virtualization one.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: