HPE VM Essentials

[BostjanUNIJA]

Hey. Thank you for your reply. So in this moment, there is no way to get a beta? Or a RTM version? Thank you.

[tholyoak]

As much as I like to hear it, please don't overemphasize our role for example, Proxmox already had significant market share before we delivered its native support.

I think there's a big difference between the 2 products. Companies looking at HPE VME are already running Veeam, and they need to know the support will be there. Proxmox was popular among hobbyists to start with (that will never use Veeam) and has suddenly had to grow up - Veeam support has given it credibility it didn't have before.

[TedLaurent]

I'm getting ready to deploy VME at several sites. We are a Veeam partner and an HPE Partner. It would be great if Veeam moved beyond supporting oVirt and included libvirt based solutions. Given Ubuntu's widespread support I'm very surprised that hasn't already happened. Isn't Proxmox based on libvirt???

Why is this so difficult????

[cody.ault]

Hey Ted, Proxmox doesn't use libvirt, but several other vendors do. Libvirt integration would allow us to manage individual hosts, however most customers expect our solution to be able to manage the entire virtualization platform and track VMs when they migrate or get deployed through some sort of centralized management/cluster API. Those control plane API's tend to differ quite a bit between platforms. The underlying API's to manage a checkpoint/track changes through dirty bitmaps can be reused across platforms but we also need to be able to integrate with the Management APIs to perform operations like restoring to the original location/register the VM with the management servers UUID, track VMs when they migrate etc. It would be like trying to manage individual ESXi hosts without vCenter. It's possible but not ideal. We aren't using oVirt for our HPE integration, however it is the base model for our UHAPI that some alliance partners are looking at implementing due to it being an opensource API that offers a rest API for data transfer vs needing SSH access to every host and worrying about different versions of Libvirt/Qemu/KVM and Host OS features. Some virtualization platforms also have unique storage implementations such as HCI vendors that might not be using Qcow2/RAW formats, in which case we need to work with those vendors to properly snapshot/track changes on their platform.