Tintri, which has earned a good reputation for providing storage for VMware virtual machines, this week made its Microsoft Hyper-V support generally available on its VMstore systems. That paves the way for multiple-hypervisor users on VMstore.
Tintri also supports Red Hat Enterprise Virtualization (RHEV) hypervisors, and Tintri customers can use VMStore with different hypervisors for production data on the same box. That’s still unusual, however. Saradhi Sreegiriraju, Tintri VP of Product Management, said Tintri customers are overwhelmingly using VMware in production but like to kick the tires with Hyper-V and RHEV — particularly in test/dev.
“We have customers who want to explore other hypervisors,” he said. “Some like to use Hyper-V for non-production workloads and VMware for production – that’s what they’ve been using and they don’t want to upset that applecart.”
Sreegiriraju said customers who used Hyper-V in beta had the same use cases typical to Tintri’s VMware customers – a lot of VDI, for instance.
He also said the Hyper-V beta program brought Tintri into many shops that weren’t customers. “We’ve had a lot of prospects who want to deploy Hyper-V or who had asked us to come back when we have Hyper-V support,” he said.
Hyper-V support could provide a nice benefit for Tintri after VMware makes Virtual Volumes (VVOLS) available. VVOLS will enable traditional storage systems to natively store virtual machine disks (VMDKs), which Tintri has done from the start. But if VVOLS helps competitors catch up with Tintri on VMware storage, it can still expand into Hyper-V’s installed base.
Sreegiriraju said VVOLs won’t change Tintri’s value proposition because many legacy vendors who adopt it still have storage systems based on LUNs and volume management. Tintri will also support VVOLs. “VVOLs are nothing more than APIs that storage systems need to implement,” he said. “It doesn’t fundamentally change anything for those systems. We believe there will be a lot of challenges adopting old storage systems that worked on LUNs and volumes to now work with VVOLs.
“And VVOLs will be limited to VMware, and we now work on Hyper-V and Red Hat too.”