Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I guess the question is what do you do if you don't have one of those "existing storage providers" at your disposal. For example, I have a "traditional" collection of VPS instances hosting a variety of services. I want to containerize those services and run them on some kind of a cluster. My VPS provider doesn't offer anything besides local volumes. How do I manage persistent volumes such that they are created/destroyed as needed (say for scaling up/down database read-only slaves) and follow their containers around?

The answer to, "Ultimately how do you manage data when it's not in a container?" is, "Well, today, I spin up a new VPS and clone the database from the master (or a designated read-only slave) on first boot." Obviously that is not the pattern we want to pursue here.

It seems like the answer to the GP's question is that you have to build out the storage container cluster infrastructure in addition to your compute container cluster infrastructure, or move to a provider that offers both aaS. I don't know if that's GlusterFS or something else. This is where people like me need guidance, and on how to orchestrate storage containers with compute containers.



Yes, Docker does not provide storage infrastructure services. If all you are looking for is advice on how to handle storage, this is not a problem of the platform but rather education.

All someone can do is educate on the pros and cons of different solutions.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: