This page contains a Flash digital edition of a book.
europe SNIA


“Software-defined storage (SDS) is virtualized storage with a service management interface. SDS includes pools of storage with data service characteristics that may be applied to meet the requirements specified through the service management interface.”


including networking, storage, compute, and security, are virtualized and delivered as a service to the consumer. An SDDC infrastructure is abstracted from the entire underlying physical infrastructure (and even the virtual infrastructure in some cases). This abstraction enables programmatic and automated provisioning, deployment, configuration, and management of the SDDC.”


While other definitions have been proposed by the various vendors and standards organizations, they all have similar, if not identical, intent or wording. For example, SNIA succinctly puts it this way in their dictionary; “A Software Defined Data Center (SDDC) is a virtualized data center with a service management interface. Application requirements determine the service levels provided.”


Roots in cloud and virtualization Cloud Computing has been the new operational model for IT Services built upon virtualization technologies. SDDC, as the next phase in the evolution of this entire technology domain, promises to deliver greater more intelligent services, better management solutions and value on top of commodity and standardized hardware platforms.


SDDC incorporates and is heavily dependent upon the use of topologies that abstract, pool and automates the use of virtualized resources. Virtualization technologies can be thought of as a commodity, or the common resources that when integrated are used by SDDC. Industry standardized management models and APIs provides this level of abstraction.


With these topologies we can describe compute, network, and storage resources, and then, with a suitable set of APIs (application programming interfaces) we can manage, organize and manipulate them. With these abstractions, management of resources becomes standardized and simplified. That’s the attraction of SDDC.


A virtualized X isn’t software defined X


It’s important to note that a “software defined X” is not the same as a “virtualized X”. Storage virtualization enables the pooling of physical storage facilities and devices from various physical networked devices into what appears to be a single (or one to many as well) storage resource pool or pools.


Software defined storage (SDS) on the other hand, is an ecosystem of products that decouples the application from underlying storage network hardware. SDS software makes visible all physical and virtual resources and enables programmability and automated provisioning based on consumption or need.


In essence, software defined separates the control plane (how we manage a resource and what we manage it with) from the data plane (how and what we use to access the resource). SDS does that for storage; the data plane is separate from the control plane. This matches well the definition used in SDN, where exactly (and unsurprisingly) the same facilities are provided.


In many respects, SDS is more about packaging and how IT users think about and design data centers. Storage has been largely software-defined for more than a decade: the vast majority of storage features have been designed and delivered as software components within a specific storage-optimized environment.


Again turning to SNIA’s definition; “Software-defined storage (SDS) is virtualized storage with a service management interface. SDS includes pools of storage with data service characteristics that may be applied to meet the requirements specified through the service management interface.”


What does software defined storage look like? There’s no rigid set of features that differentiates SDS from storage you can buy and deploy today. Storage that meets SDS


requirements needs to include: £Automation – Simplified management that reduces the cost of maintaining the storage infrastructure.


£Standard Interfaces – APIs for the management, provisioning and maintenance of storage devices and services.


£Scalability – Seamless ability to scale the storage infrastructure without disruption to availability or performance.


£Virtualized Data Path – Block, File and Object interfaces (or some combination of them) that support applications written to these interfaces.


Some analysts claim that a needed characteristic is that only block storage is suitable for the SDS treatment. That’s not true; any storage, as long as it clearly separates out the control plane from the data plane and has some form of programmatic interface for provisioning and managing virtual instances of itself is required.


Ideally, SDS offerings allow applications and data producers to manage the treatment of their data by the storage infrastructure without the need for intervention from storage administrators, without explicit provisioning operations, and with automatic service level management.


In essence, SDS is like SDN is like any other resource that we may wish to manage. Taken together, these represent the elements of an SDDC.


If SDx isn’t a virtualized X, then SDDC isn’t virtualization SDDC differs from Cloud and virtualization in these ways: £SDDC builds upon the successes of server virtualization, by broadening the individual components of the data center that have been virtualized and envisioning a unified control console & management solution for all the data center’s parts.


£Cloud is a relatively new IT operational model (and marketing model!) focusing on the delivery and consumption of IT


Summer 2014 I www.dcseurope.info 13


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56