Longhorn is cloud native distributed block storage for Kubernetes, supported by Rancher Labs headquartered in Cupertino.
N/A
StorPool
Score8 out of 10
N/A
StorPool is a block-storage software that uses standard hardware and builds a storage system out of this hardware. It is installed on the servers and creates a shared storage pool from their local drives in these servers. Compared to traditional SANs, all-flash arrays, or other storage software StorPool is faster, more reliable and scalable.
Longhorn is performing well as storage for databases and in almost any solution that uses exclusive access to volumes (ReadWriteOnce in Kubernetes nomenclature). When write access is required from many clients (ReadWriteMany) Longhorn Block Storage covers its volumes with NFS (file-based) access. Longhorn Block Storage also is well fitted in every architecture where data security (snapshots, backups, multiple replicas) is more important than access speed (in terms on IOPS and MiB/s).
Storpool performs well on block level (and that is what we use it for). It is not yet supporting a kind of distributed filesystem or object storage - a filesystem layer needs to be built on top of it.
ReadWriteMany Longhorn volumes are still using NFS (file-based) protocol in the core.
Using iSCSI as main protocol instead of FC ties Longhorn to Ethernet-based LAN which is in most architectures much slower that FC-based SAN.
Longhorn could implement S3 as alternative access protocol to its volumes.
Backups, and snapshots configuration could be configured at each volume-level by administrators (maybe from additional CRD object?), because currently is configured at storage-class level which is not granular enough.
Longhorn is mature software defined storage solution that is still developed and receive new functionalities. From the beginning every Longhorn volume have multiple (at least two) replicas, can leverage manual or automatic snapshots and backup to external S3 volume. Longhorn provides nice and clear GUI for administrators, but also can be managed from CLI.
GlusterFS was first Persistent Storage solution used in our Kubernetes-based clusters. It is file-based what in some usages led us to many data corruptions. CEPH is object-based persistent storage which can be used as file-based Persistent Storage in Kubernetes. It is also is much more resource-hungry than other solutions including Longhorn. Dell PowerScale (or Isilon) is a hardware-software solution, that provides volumes that can be accessed by file-based NFS and CIFS protocols. Recently was added access to its volumes with object-based S3 protocol. Longhorn is in the middle. It is block-based, it is build on industry standards like iSCSI, performs very well on 10Gbit or faster LAN and commodity hardware (or in virtual machines)
We made a very careful selection of our storage vendor and solution. After researching the newest technologies, our team decided to deploy a software-defined storage solution from StorPool.
We have not calculated precise ROI. We focused on getting the best solution at a reasonable price, based on market research. Initially, we didn’t need a lot of capacity, so we invested in servers and network, which could handle several times more capacity, but bought smaller drives to keep the investment low. We achieved a starting price of $3.2/GB usable and $1.4/GB logical. Later we expanded the capacity by adding more drives to the system. Currently, the system has a price of approximately $2.3/GB usable and $0.99/GB logical and a price of $0.09/IOPS.
