I wrote about StorageOS almost twelve months ago, and recently had the opportunity to catch up with Chris Brandon about what StorageOS have been up to. They’ve been up to a fair bit as it happens, so I thought I’d share some of the details here.
The Announcement
What’s StorageOS? According to Brandon it’s “[a] software-defined, scale-out/up storage platform for running enterprise containerized applications in production”. The “buzz” is that StorageOS is now generally available for purchase and they’ve secured some more funding.
Cloud Native Storage, Eh?
StorageOS have come up with some thinking around the key tenets of cloud native storage. To wit, it needs to be:
- Application Centric;
- Application Platform Agnostic;
- Declarative and Composable;
- API Driven and Self-Managed;
- Agile;
- Natively Secure;
- Performant; and
- Consistently Available.
What Can StorageOS Do For Me?
According to Brandon, StorageOS offers are a number of benefits:
- It’s Enterprise Class – so you can keep your data safe and available;
- Policy Management allows you to enforce policies and rules while still enabling storage self-service by developers and DevOps teams;
- Deploy It Anywhere – cloud, VM or server – you decide;
- Data Services – Replication for HA, data reduction, storage pooling and agility to scale up or scale out based on application requirements;
- Performance – Optimised to give you the best performance from your platform;
- Cost-Effective Pricing – Only pay for the storage you use. Lower OpEx and CapEx;
- Integrated Storage – Integrated into your favorite platforms with extensible plugins and APIs; and
- Made Easy – Automated configuration and simple management.
Architecture
There is a container installed on each node and this runs both the data plane and control plane.
Data Plane
- Manages data access requests
- Pools aggregated storage for presentation
- Runs as a container
Control Plane
- Manages config, health, scheduling, policy, provisioning and recovery
- API is accessed by plugins, CLI, GUI
- Runs as a container
Containers are also used to create a highly available storage pool.
[Image courtesy of StorageOS]
Thoughts And Further Reading
StorageOS secured some funding recently and have moved their headquarters from London to New York. They’re launching at KubeCon, Red Hat Summit and dockercon. They have a number of retail and media customers and are working closely with strategic partners. They’ll initially be shipping the Enterprise version, and there is a Professional version on the way. They are also committed to always having a free version available for developers to try it out (this is capacity limited to 100GB right now).
We’ve come some way from the one application per host approach of the early 2000s. The problem, however, is that “legacy” storage hasn’t been a good fit for containers. And containers have had some problems with storage in general. StorageOS are working hard to fix some of those issues and are looking to deliver a product that neatly sidesteps some of the issues inherent in container storage while delivering some features that have been previously unavailable in container deployments.
The team behind the company have some great heritage with cloud-native applications, and I like that they’re working hard to make sure this really is a cloud-native solution, not just a LUN being pointed at an operating environment. Ease of consumption is a popular reason for shifting to the cloud, and StorageOS are ensuring that people can leverage their product with a simple to understand subscription model. They’re not your stereotypical cloud neckbeards though (that’s my prejudice, not yours). The financial services background comes through in the product architecture, with a focus on availability and performance being key to the platform. I also like the policy-based approach to data placement and the heavy focus on orchestration and automation. You can read more about some of the product features here.
Things have really progressed since I first spoke to StorageOS last year, and I’m looking forward to seeing what they come up with in the next 12 months.
