Let's Define "Software-Defined Storage"
Join the DZone community and get the full member experience.Join For Free
every few years, a new buzzword pops up in the data storage industry. this is our queue to quibble over the exact definition, hopefully drumming up some interesting conversation in the process, mainstreaming the term, and pushing for clearer roadmaps from the participating vendors.
ten years ago, the word of the day was “virtualization.” five years ago, it was “cloud.” today, i believe it is “software-defined.”
let’s get right to it – my simple definition for software-defined storage (sds) is as follows:
“a hardware-agnostic application installed into a standard (relatively unmodified) operating system that acts as a storage system and has a feature-set sufficient to host today’s applications and services at scale.”
now, let’s break down each of those key points.
this point is key in deciding what is and what isn’t sds, and all other defining characteristics really rely on this one main value. the software should run on any modern x86 server from the hardware vendor of your choice. software that only ships on a specific set of hardware and does not allow the end-user to install that software onto the hardware of their choice is not software-defined storage. that is a storage appliance.
i’d like to be clear on one thing – sds does not automatically equal “whitebox” servers. there are a handful of customers in the world who will always build their own solutions, from the hardware to the software. think amazon and google. however, the rest of the world is looking for a reliable platform that is easy to manage and gets through procurement without any major red tape. these customers see the “hardware agnostic” functionality as allowing them to choose the commercial server of their choice running in environments with mixed hardware generations and mixed configurations as things like drive capacities increase over time.
major business value: decreased acquisition cost using standard servers, remain free to alter buying decisions with each upgrade based on business requirements and product availability. increase business agility, speeding time to market by deploying new applications on a known platform.
standard (relatively unmodified) operating system
point number two is what allows us to accomplish point number one. remember 10 years ago, when we started talking about hypervisors acting as a layer of “abstraction” between the hardware and the software? this is exactly what we are talking about here. sds should use a standard os (linux is the obvious choice here) as a way to create logical separation between the hardware and the software. the os kernel will handle things like addressing block devices and the sds layer will simply utilize the storage, compute, and network resources that are presented up into user space.
i use the words “standard” and “relatively unmodified” here with purpose. the more tweaking that is done to the operating system, the closer we are getting to traditional storage and the concept of firmware running on proprietary controllers. the value in sds is in the software, and we need that software to be portable across hardware platforms that may or may not support highly-customized operating systems.
major business value: decreased opex costs and complexity by utilizing a familiar os as a baseline for many services in the organization, possibly including servers, storage, and networking.
acting as a storage system, and with a feature set sufficient to host today’s applications and services at scale.
the first part of this sentence should be pretty self-explanatory. the next gets a little murky. servers have been providing storage services to clients for quite some time now. a quick example here is something like an nfs (network file system) share running on a linux server, or even the more recent windows storage server from microsoft. are these sds? i would say no. they still rely on underlying storage devices with the ability to protect and manage data at scale.
once again, i will fall back to point number one: hardware agnostic. in order to support this key value, sds will need to take responsibility for protecting any storage resources it is managing. modern systems, especially of the scale out variety, tend to leverage replication and erasure coding to accomplish this. however, i think that any system that can guarantee availability and durability at or exceeding current levels (five nines and up) can rightfully call itself sds.
there are many, many other features that are “nice to have” depending on the goals of the end user.
we can argue about those in another post.
major business value: enhanced reliability by distributing the data protection methodology across traditional physical boundaries. depending on the feature set, increased agility by allowing organizations to deploy new applications to a shared pool of data without custom programming.
to sum it up, a modern software-defined storage platform should give the end user the freedom to make their own decisions, while still giving them the peace of mind to sleep at night.
what do you think? am i missing any critical pieces, or is anything i’m saying completely out of line with what you are seeing in the market today?
Published at DZone with permission of Leo Leung, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.