The OpenEBS project has taken a different approach to storage when it comes to containers. Instead of using existing storage systems and making them work with containers; what if you were to redesign something from scratch using the same paradigms used in the container world? This resulted in the effort of containerizing the storage controller. Also, as applications that consume storage are changing over, do we need a scale-out distributed storage systems?
The OpenEBS project has taken a different approach to storage when it comes to containers. Instead of using existing storage systems and making them work with containers; what if you were to redesign something from scratch using the same paradigms used in the container world? This resulted in the effort of containerizing the storage controller. Also, as applications that consume storage are changing over, do we need a scale-out distributed storage systems?
Also, as we in effect have a storage instance per containerized applications, what other benefits could we get? Is there something we can do now that we have a one to one mapping between application and controller? We like to think so and will go over a couple.
Finally, how can we make enterprise-class like storage features (i.e., snapshots, clones, compression, replication, etc.) available in a typical container in such a way, that we do not depend on OS and or cloud provider specifics?
Speakers: Jeffry Molanus