Re:Why Is Storage on Kubernetes So Hard?
by justinclift on Monday January 14, 2019 @12:48AM
(#18900961)
Thanks for doing that. I have personal strong aversion to spammers. To the point where their product doesn't matter, I'll just use/help a competitor instead.
Reaching out to the occasional person who stars a project, if there's some strong overlap of stuff then maybe sure. An automatic spam approach though... that's not on. That makes starring projects a "dangerous" thing for end users, as they'd have to be open to emails for every one. :/
And yeah, it did look useful up until this point. Lets see what their response to the GH issue is like. :)
Re:Why Is Storage on Kubernetes So Hard?
by umamukkara on Monday January 14, 2019 @01:11AM
(#18901028)
Thank you for the feedback. Feedback like this will help us understand the best practices in community building. We have disabled the email trigger on starring. Thanks again for this open feedback.
Re:Why Is Storage on Kubernetes So Hard?
by justinclift on Monday January 14, 2019 @02:14AM
(#18901251)
No worries Uma. The project looks interesting, and it's even written in Go, so I'll probably take it for a spin in the next few weeks. :)
Also, I wouldn't be so quick to write them off -- their solution is based on Container Attached Storage (CAS), and is the only relatively mature solution so far I've seen (I haven't seen any others that do CAS) that sort of take the Ceph model and turn it inside out -- pods talk to volumes over iSCSI via "controller" pods, and writes are replicated amongst these controller pods (controller pods have anti-affinity to ensure they end up on separate machines).
I have yet to do any performance testing on ceph vs openebs but I can tell you it was easier to wrap my head around than Ceph (though of course ceph is a pretty robust system), and way easier to debug/trace through the system.
[0]: https://github.com/openebs/openebs/issues/2345