Comparing Ceph, Linstor, Mayastor and Vitastor Storage Performance in Kubernetes

Re:Comparing Ceph, Linstor, Mayastor and Vitastor Storage Pe... by lukaslalinsky on Friday June 03, 2022 @07:22AM (#31606868)

I wonder if the Linstor integration with Kubernetes got better. A few years back, the CSI driver was full bugs and you couldn't really use it from K8s alone, you had to use Linstor tools on the servers directly to get things unstuck or get orphaned volumes to actually get deleted.

[ Parent | on HN ]

Re:Comparing Ceph, Linstor, Mayastor and Vitastor Storage Pe... by tbronchain on Friday June 03, 2022 @08:11AM (#31607210)

A lot better.

A couple of years ago I could see volumes on Linstor getting completely stuck and unrecoverable whenever the network was getting busy or unstable. Nodes reboot were a nightmare too.

Have a setup now with their Piraeus operator[1], Kubernetes >= 1.20, rancher and calico, and it seems to be very stable. XFS have been giving better results too. Still, better not to try too many reboot loops on the nodes.

1: https://github.com/piraeusdatastore/piraeus-operator/

[ Parent | on HN ]

Re:Comparing Ceph, Linstor, Mayastor and Vitastor Storage Pe... by hardwaresofton on Friday June 03, 2022 @06:29PM (#31614469)

Note, kvaps actually wrote one of the LINSTOR operators (which is no longer maintained):

https://github.com/kvaps/kube-linstor

[ Parent | on HN ]

Re:Comparing Ceph, Linstor, Mayastor and Vitastor Storage Pe... by kvaps on Saturday June 04, 2022 @02:57AM (#31617746)

Yeah, because I have joined to Piraeus project :)

[ Parent | on HN ]