Twitte

One of the early innovators in the container ecosystem, ClusterHQ, just announced that they are shutting down. They were justifiably proud of their role as an early proponent of stateful containers. We agree. As containerization became a key consideration for enterprises, it was inevitable that stateful applications would be containerized. Challenging problems of providing data persistence and data availability appeared. ClusterHQ was one of the first companies to address this via Flocker, connecting Docker containers natively to legacy storage.

So what went wrong? ClusterHQ customers are not wrong. Infrastructure software needs to support stateful containers. And the problems of managing data state and availability are not insurmountable. ClusterHQ’s Flocker was a good first step, just not the last step.

The problem was that Flocker was connecting to the wrong storage. Legacy storage arrays are fundamentally siloed, not cloud-native, and require manual provisioning. LUNs were designed to provide storage to servers, not applications running in containers. For example, they cannot plug-andplay with container orchestration and scheduling software. Tools like Flocker and RexRay try to connect traditional LUNs to containers. There are worse and better architectures for managing stateful containers. Here’s our view.

We applaud ClusterHQ’s efforts over the years. They set the industry on the path of stateful containers. The good news is that stateful containers are here and being deployed successfully.  Follow our blog and Twitter feed to see how Portworx is leading the charge.

Share
Subscribe for Updates

About Us
Portworx is the leader in cloud native storage for containers.

Murli Thirumale

Murli Thirumale

Portworx | Co-Founder and CEO
link
clusterHQ
January 5, 2017 News & Commentary
Helping ClusterHQ Customers Move Forward in 2017
Jeff Silberman
Jeff Silberman
link
Blog Placeholder
October 2, 2015 News & Commentary
The Case for Container Aware Storage
Gou Rao
Gou Rao
link
Twitter
January 5, 2018 News & Commentary
What Portworx Customers Need to Know About Meltdown and Spectre
Eric Han
Eric Han