Content deleted Content added
Jpaulturner (talk | contribs) m added object storage as an example implementation |
Mark viking (talk | contribs) Merging content from Storage hypervisor per the AfD outcome |
||
Line 34:
* Automation with policy-driven storage provisioning with [[service-level agreement]]s replacing technology details. This requires management interfaces that span traditional storage-array products, as a particular definition of separating "control plane" from "data plane", in the spirit of [[OpenFlow]]. Prior industry standardization efforts included the [[Storage Management Initiative – Specification]] (SMI-S) which began in 2000.
* Commodity hardware with storage logic abstracted into a software layer. This is also described{{by whom|date=August 2014}} as a [[clustered file system]] for [[converged storage]].
==Storage hypervisor ==
In [[computing]], a '''storage hypervisor''' is a software program which can run on a physical server hardware platform, on a [[virtual machine]], inside a hypervisor OS or in the storage network. It may co-reside with virtual machine [[Supervisory program|supervisors]] or have exclusive control of its platform. Similar to virtual server [[hypervisor]]s a storage hypervisor may run on a specific hardware platform, a specific hardware architecture, or be hardware independent.<ref>{{cite web|title=Comparison of virtualization technologies|url=http://virt.kernelnewbies.org/TechComparison}}</ref>
The storage hypervisor software virtualizes the individual storage resources it controls and creates one or more flexible pools of storage capacity. In this way it separates the direct link between physical and logical resources in parallel to virtual server hypervisors. By moving storage management into isolated layer it also helps to increase system uptime and [[High Availability]]. "Similarly, a storage hypervisor can be used to manage virtualized storage resources to increase utilization rates of disk while maintaining high reliability."<ref>{{cite web|title=Evaluation and design of highly reliable and highly utilized cloud computing systems, Page 12|url=http://journalofcloudcomputing.springeropen.com/articles/10.1186/s13677-015-0036-6|publisher=Journal of Cloud Computing | date=June 9, 2014 | author= Brett Snyder, Jordan Ringenberg, Robert GreenEmail author, Vijay Devabhaktuni and Mansoor Alam}}</ref>
The storage hypervisor, a centrally-managed supervisory software program, provides a comprehensive set of storage control and monitoring functions that operate as a transparent virtual layer across consolidated disk pools to improve their [[high availability|availability]], speed and utilization.
Storage hypervisors enhance the combined value of multiple [[disk storage]] systems, including dissimilar and incompatible models, by supplementing their individual capabilities with extended provisioning, data protection, replication and performance acceleration services.
In contrast to embedded software or disk controller [[firmware]] confined to a packaged storage system or appliance, the storage hypervisor and its functionality spans different models and brands and types of storage [including SSD ([[solid state disks]]), SAN ([[storage area network]]) and DAS ([[direct attached storage]]) and Unified Storage(SAN and NAS)] covering a wide range of price and performance characteristics or tiers. The underlying devices need not be explicitly integrated with each other nor bundled together.
A storage hypervisor enables hardware interchangeability. The storage hardware underlying a storage hypervisor matters only in a generic way with regard to performance and capacity. While underlying "features" may be passed through the hypervisor, the benefits of a storage hypervisor underline its ability to present uniform virtual devices and services from dissimilar and incompatible hardware, thus making these devices interchangeable. Continuous replacement and substitution of the underlying physical storage may take place, without altering or interrupting the virtual storage environment that is presented.
The storage hypervisor manages, virtualizes and controls all storage resources, allocating and providing the needed attributes (performance, availability) and services (automated [[Thin provisioning|provisioning]], [[Snapshot (computer storage)|snapshots]], [[Replication (computer science)|replication]]), either directly or over a storage network, as required to serve the needs of each individual environment.
The term "hypervisor" within "storage hypervisor" is so named because it goes beyond a supervisor,<ref>{{cite web|title=Hypervisor glossary definition|url=http://www.xen.org/files/xen_user_manual.pdf|work=Xen v2.0 for x86 Users' Manual (PDF)|publisher=Xen.org on August 20, 2011}}</ref> it is conceptually a level higher than a supervisor and therefore acts as the next higher level of management and intelligence that sits above and spans its control over device-level storage controllers, disk arrays, and virtualization middleware.
A storage hypervisor has also been defined as a higher level of storage virtualization <ref>{{cite web|title=SearchStorage.com definition|url=http://searchstorage.techtarget.com/definition/storage-virtualization|publisher=What is storage virtualization? Definition on SearchStorage.com}}</ref> software, providing a "Consolidation and cost: Storage pooling increases utilization and decreases costs. Business availability: Data mobility of virtual volumes can improve availability. Application support: Tiered storage optimization aligns storage costs with required application service levels".<ref>{{cite web|title=IBM SmartCloud Virtual Storage Center|url=https://books.google.co.uk/books?id=_pbABgAAQBAJ&pg=PA28#v=twopage&q&f=false|publisher=IBM Redbooks}}</ref> The term has also been used in reference to use cases including its reference to its role with storage virtualization in disaster recovery <ref>{{cite web|title=SearchDisasterRecovery Article:|url=http://searchdisasterrecovery.techtarget.com/news/2240037212/The-cloud-and-virtualization-havent-make-IT-disaster-recovery-plans-obsolete|publisher=Published in SearchDisasterRecovery.com on June 23, 2011 and written by Todd Erickson}}</ref> and, in a more limited way, defined as a volume migration capability across SANs.<ref>{{cite web|title=ComputerWorld Article:|url=http://www.computerworld.com.au/article/368886/compellent_adds_virtualization_hardware_upgrades_its_san/|publisher=Published on November 23, 2010 and written by Lucas Mearian
}}</ref>
===Server vs. storage hypervisor===
An analogy can be drawn between the concept of a server hypervisor and the concept of a storage hypervisor. By virtualizing servers, server hypervisors ([[VMware ESX]], [[Microsoft Hyper-V]], Citrix XenServer, Linux KVM, Xen) increased the utilization rates for server resources, and provided management flexibility by de-coupling servers from hardware. This led to cost savings in server infrastructure since fewer physical servers were needed to handle the same workload, and provided flexibility in administrative operations like backup, failover and disaster recovery.
A storage hypervisor does for storage resources what the server hypervisor did for server resources. A storage hypervisor changes how the server hypervisor handles storage I/O to get more performance out of existing storage resources, and increases efficiency in storage capacity consumption, storage provisioning and snapshot/clone technology. A storage hypervisor, like a server hypervisor, increases performance and management flexibility for improved resource utilization.
==See also==
* [[Hypervisor]]
* [[Software-defined networking]]
* [[Software-defined data center]]
| |||