Optimize Your IT Infrastructure with Software Defined Storage
IBM Software Defined 2700052JD4 Visits (5225)
One of the primary goals of a Software Defined Environment (SDE) is to make data center infrastructure cloud ready. In geek speak, SDE abstracts compute, networking, and storage resources in the datacenter as “services on demand” and makes them available to applications through a set of well-defined APIs. In doing so, SDE enables applications to provision, configure, and consume data center resources through programmatic interfaces. These capabilities drive automation of data center processes, increased efficiency, and business velocity and are at the core of what makes cloud computing attractive.
Today’s Storage setups consist of diverse Storage systems that must be manually provisioned by system administrators according to the requirements of applications, configured in a such a way that it caters to the application’s performance needs, re-provisioned as the application requirements change and eventually de-provisioned when there is no longer a need for the information. As storage requirements changes both in terms of capacity and performance requirements, administrators must reconfigure storage to cater to the changing needs by moving data back and forth across different types of storage, provisioning storage across multiple systems, allocating faster storage types like FLASH, etc. The complexity assumes an extra dimension because applications can now move around (e.g. vMotion) the data center as they are provisioned and re-provisioned. Manually catering to these requirements & statically configuring storage to cater to these requirements is simply untenable i.e. extremely complex, error-prone and therefore risky. And needless to say that administration costs escalate non-linearly.
These APIs must cater to the needs of integrated Software Defined Environments that are built around Cloud Operating Systems like OpenStack. Existing storage systems do provide a lot of these functions. Therefore the first step is to ensure that these functions can be integrated and packaged as APIs that can be consumed by use cases provided by SDE stacks.