Akamai Cloud Computing (formerly Linode) include scalable and accessible Linux cloud solutions and services. These products and services support developers and enterprises as they build, deploy, secure, and scale applications.
N/A
Longhorn Block Storage
Score 10.0 out of 10
N/A
Longhorn is cloud native distributed block storage for Kubernetes, supported by Rancher Labs headquartered in Cupertino.
N/A
Pricing
Akamai Cloud Computing
Longhorn Block Storage
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Akamai Cloud Computing
Longhorn Block Storage
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
CPU, transfer, storage, and RAM are bundled into one price. Storage capacity can be increased with additional Block Storage or S3-compatible Object Storage. Instant Backups can be added with complete independence to the stack. Linode NodeBalancers ensure applications are available.
Akamai Connected Cloud Linode would be a good service to host a content delivery network (CDN) because of its edge network but I'd prefer not to use Akamai Connected Cloud Linode for tasks that need GPU power such as Machine Learning or Artificial Intelligence (AI) because Akamai Connected Cloud Linode lacks deep GPU compute compared to AWS or Google Cloud or Microsoft Azure
Longhorn Block Storage is well suited for most Kubernetes workloads where data storage is required, but when very high storage speed is essential, Longhorn Block Storage might not be the best solution. For those rare situations, we use local storage mounts. Longhorn Block Storage's ability to easily create/restore volume snapshots is a very frequently used feature among our dev teams because they can easily play multiple scenarios with the same data - modify data, restore it and modify it again.
The (new) 'create custom image' function needs a bit of work before it is useable.
New accounts have limited features until a support requested is made to turn specific ones on. It would be useful to have an account page that tells you what is disabled so unpleasant surprises are not had at the pointy end of a deadline.
Stackscripts would be better if it more info was transferred to the script. Eg the Linode Label given, plan requested, etc. But now I am just nit-picking
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.
In this eight years of being Linode's customer, there hasn't been a single day we faced problem. Even the migration or maintenance activities have been planned, organised and priorly informed. Kudos to taking care of even such small metrics. Though the instances are unmanaged, the support team helps with relevant document links, or their own articles that help us to fix or solve the issues we face.
It's pretty easy for me, but I preferred their old interface before it was called 'cloud' (not a computer science term.) The new interface looks easier but I had to ask for help for things I used to be able to find myself. If someone was new to it--without having used their old interface--it might be easier for them than it originally was for me.
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.
There is very little planned downtime. Whenever planned downtime is necessary I'm always given lots of advanced notice and an explanation that I can pass along to my users that they'll understand. I really appreciate that Linode appreciates my commitment to reliable service to my users. It shows that they believe they've been successful when I'm successful.
Servers are well dimensioned and price performant. Of course one always wants more, so if they were to upgrade their hardware for the same price I'd consider moving more workloads. Networking - never had an issue. Hardware speeds - disks are fast and can grow to great size.
Support was excellent and fast. The documentation is extensive and helpful. I learned many things from their online documentation. I did not contact them by phone, but email took a day or less. Complex problems would probably need a service contract. I liked the friendly and polite tone of the support.
We got kick started with an initial walkthrough along with some free credits. The initial walkthrough helped us to understand Linode's ecosystem and start our hands on with Linode. We tried out some apps from Marketplace initially with the free credits, which not only helped us understand Linode better, but also those apps. We had implemented many such apps to our customers with Linode
We're a small organization. The implementation of our Linode solution was trivial. Once I justified a cloud server to my bosses over a co-location -- the co-lo wasn't as fast as our linode server in load tests -- it was a matter of moving one Linux implementation to another. Trivial.
It is more user-friendly than the big three cloud providers like AWS and GCP. The interface blows them out of the water; pricing is so much more competitive—no egregious bandwidth fees like AWS. As a small startup, cutting out the overhead of ultra-complex UI and pricing dramatically helps. It seems to be matched tit-for-tat with DigitalOcean, and their UI is similar in many ways. DigitalOcean has more mature capabilities, even though Linode/Akamai was founded earlier. Linode/Akamai provides better price-per-performance, though, as DigitalOcean is expensive nowadays.
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)
I completely agree with the above statement. Linode provides the best option in terms of configurations and scalability. We have chosen share CPU instances many times and then moved on with dedicated CPU instances, just with a click of button.
Longhorn is fully open source. One can try and/or use Longhorn for free even in enterprise and buy subscriptions only for environments that must be fully supported. We started with Longhorn in our lab environment and followed on through reference platform to non-production and production environments.
Longhorn subscriptions are not cheap, but its biggest advantage is that price-to-functionality ratio is very reasonable.
We have volumes with hundreds of gigabytes of data and these on Longhorn perform well in solutions where file-based GlusterFS volumes were corrupting data.
