3 ms·

Kubernetes has a few good storage solutions that are built on well-known technology... https://rook.io https://rook.io (built on ceph) https://www.openebs.io

Kubernetes has a few good storage solutions that are built on well-known technology... https://rook.io https://rook.io (built on ceph) https://www.openebs.io https://www.openebs.io (built on Jiva/cStor) The distributed storage problem is difficult on it's own, this isn't a kubernetes specific issue. IMO Kubernetes is improving on the state of the art by dealing with both the distributed storage problem and dynamic provisioning, and that's why it might seem somewhat flustered. What isn't shown here is how effortless it feels when you do have a solution like rook or openEBS in place -- we've never seen ergonomics like this before for deploying applications. Also, the CSI (Container Storage Interface) that they're building and refining as they go will be extremely valuable to the community going forward. BTW, if you want to do things in a static provisioning sense, support for local volumes (and hostPaths) have been around for a very long time -- just use those and handle your storage how you would have handled it before kubernetes existed. Shameless plug I've also written about this on a fair number of occasions: https://vadosware.io/post/kicking-the-tires-on-openebs-for-cluster-storage/ https://vadosware.io/post/kicking-the-tires-on-openebs-for-c... https://vadosware.io/post/disassembling-raid-on-hetzner-without-rescue-mode/ https://vadosware.io/post/disassembling-raid-on-hetzner-with... I've gone from a hostPath -> Rook (Ceph) -> hostPath (undoing RAID had issues) -> OpenEBS, and now I have easy to spin up, dynamic storage & resiliency on my tiny kubernetes cluster. All of this being capable as someone who is not a sysadmin by trade, should not be understated. The bar is being lowered -- I learned enough about ceph to be dangerous, enough about openebs to be dangerous, and got resiliency and ease of use/integration from kubernetes.

justinclift 8y ago
OpenEBS looked interesting, but it turns out they're spammers. :( Starred the GitHub repo... and a few minutes later received email spam from them to my personal email (it's in my GitHub profile). :( Completely lost interest in their project at that point. Probably best to skip it, as rewarding spammers doesn't lead to good things. :(
- hardwaresofton 8y ago
  I had no idea they did that, just made an issue about it[0]. 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 https://github.com/openebs/openebs/issues/2345
  - justinclift 8y ago
    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. :)
    - traek 8y ago
      They just replied saying they disabled the emails.
    - umamukkara 8y ago
      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.
      - justinclift 8y ago
        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. :)

justinclift 8y ago

OpenEBS looked interesting, but it turns out they're spammers. :( Starred the GitHub repo... and a few minutes later received email spam from them to my personal email (it's in my GitHub profile). :( Completely lost interest in their project at that point. Probably best to skip it, as rewarding spammers doesn't lead to good things. :(

hardwaresofton 8y ago
I had no idea they did that, just made an issue about it[0]. 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 https://github.com/openebs/openebs/issues/2345
- justinclift 8y ago
  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. :)
  - traek 8y ago
    They just replied saying they disabled the emails.
  - umamukkara 8y ago
    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.
    - justinclift 8y ago
      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. :)