In this short blog I’d like to share an entrepreneur’s perspective on what achieving OpenEBS 1.0 means, first in terms of the evolution of use cases and secondly in terms of progress on OpenEBS and MayaData itself.
Oxygen = new use cases such as auto-devops or ML
Here’s where the title of this blog comes in — for a certain set of users and use cases OpenEBS is a no brainer.
I summarized a question from a large OpenEBS user recently on Twitter:
This user is a leader of an organization that runs Kubernetes and many other pieces of software in order to deliver capabilities to their internal users who in turn are building applications and machine learning models and so forth. So they really do spend millions building distributed applications and really do not understand the thought process behind scale out storage.
This user’s users are themselves consuming OpenEBS and customizing it and deploying and managing it as needed — and since it is a Kubernetes native application it fits into their mental models and their tool chains.
Conversely they are not talking to a …