Longhorn is cloud native distributed block storage for Kubernetes, supported by Rancher Labs headquartered in Cupertino.
N/A
OVHcloud Public Cloud
Score 8.2 out of 10
N/A
OVHcloud Public Cloud offers users a large number of cloud solutions that are billed on a pay-as-you-go basis. OVH states their infrastructure is set up in a simple way to enable businesses to harness the flexibility of on-demand resources to scale up from small projects to large-scale deployments.
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).
For demo uploads or for production uploads of companies from different sectors looking for a "general computing" cloud solution, I think that OVH can be a good provider. However, for more delicate or advanced loads or for specific solutions of, for example, AI, OVH has a wide margin for improvement.
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)
Most notably OVHcloud [Public Cloud] has dedicated servers which are a different breed of product than Linode's flagship VPS servers, the unfortunate fact of the matter is that OVHcloud [Public Cloud] can provide a fully-dedicated server at a lower price point than Linode's virtual server. Even worse than that is that with a dedicated server from [OVHcloud Public Cloud] there is zero chance of "cpu theft" (aka, noisy neighbor) which is a very real problem at Linode (we would require multiple migrations every year for servers hosted at Linode that were experiencing cpu theft). In addition to the improvement in quality for network/hardware at OVHcloud [Public Cloud] with their dedicated server offering, their VPS servers are also highly competitive against Linode's VPS servers - in the 2 years we've used OVHcloud [Public Cloud] VPS's we've had zero downtime associated with OVH actions such as host-node reboots or cpu theft or host node upgrades, a stark difference compared to Linode which regularly experiences those types of downtimes and many more on a very regular basis.
