This content is part of the Essential Guide: Data storage considerations for a DevOps environment

Tintri OS storage upgrade focuses on cloud, containers for DevOps

Tintri storage moves 'in lockstep' with VMware for cloud, container and DevOps support with a vRealize Orchestrator plug-in and vSphere Integrated Containers support.

Virtual machine-aware storage vendor Tintri is following VMware's path for supporting cloud and containers with...

the new release of the Tintri Operating System.

The Tintri OS upgrade that launched today includes a VMware vRealize Orchestrator (vRO) plug-in and support for vSphere Integrated Containers (VIC).

Tintri also revealed that its roadmap includes greater support for containers, with a Flocker plug-in to store persistent Docker volumes. The Tintri storage roadmap also includes integration with object storage on public clouds, beginning with Amazon Simple Storage Service and IBM Cloud Object Storage. The Tintri OS S3 Connector for the cloud will provide data-at-rest and data-in-flight encryption for backup data. 

The Tintri OS vRO plug-in enables automation of storage features, such as snapshots, replication, clones and copy data management, at the VM level.

Chuck Dubuque, vice president of product marketing at Tintri, based in Mountain View, Calif., said the vRO plug-in is aimed at helping cloud developers use Tintri storage.

"Today, our typical user is core IT," he said. "But, as you move into DevOps, you have developers provisioning storage. They don't know or care about the infrastructure. Instead of needing an admin to set up a VM or a protection policy, we allow you to push that functionality to a user on the development team. When building a cloud, that's where you want to automate."

VIC allows admins to deploy and manage containers within VMs from inside VMware's vSphere management software on Tintri storage arrays.

The coming Flocker plug-in will enable customers running containers on bare metal to store persistent Docker volumes on Tintri storage. Flocker integration will allow Tintri to plug into container orchestration platforms, such as Kubernetes, Apache Mesos and Docker Swarm.

The Tintri OS update is expected in December, soon after VMware releases vSphere 6.5.

"Tintri is in lockstep with VMware," said Jim Miller, senior analyst at Enterprise Management Associates Inc., in Boulder, Colo. "VMware looked at containers and said, 'We have to jump on this or it's going to get away from us.' Now, Tintri also has a way of dealing with containers. Copy data management, snapshots and clones will come not too much later, but people using containers today are still in test/dev, so Tintri's ahead of the curve."

Containers make sense for Tintri OS

Mike Matchett, senior analyst at the Taneja Group Inc., in Hopkinton, Mass., said using containers is the next logical step for DevOps storage for developers who dealt with VMs for years.

Containers are the new VMs. The original idea for containers was they were just for microservices, just an offshoot.
Mike Matchettsenior analyst, Taneja Group

"Containers are the new VMs," Matchett said. "The original idea for containers was they were just for microservices, just an offshoot. But people took a look at that and said, 'Hey, here's how I can get away from licensing and overhead, I can get more agile' ... It works at a level that DevOps is more comfortable working at. Developers don't care about infrastructure; they want to deal with chunks of application code. That's what a container is."

Container support is also the next logical step for Tintri storage, which already supports vSphere, Microsoft Hyper-V, Red Hat storage, Citrix XenDesktop and OpenStack at the VM level.

"This will be our first foray into other types of abstracted storage, starting with container support," Tintri's Dubuque said. "We will support open source containers through our Flocker driver. We'll use the Flocker driver to present persistent storage to containers. We'll also support bare-metal containers for latency-sensitive applications, such as financial services trading, where an extra 5% latency for VMs is too much."

Next Steps

The guide to Docker volumes and containers

How to handle Docker storage and containerization

The difference between virtual storage and Docker

Dig Deeper on Storage for DevOps