Fully support local storage domains in hypervisor clusters.
Description of feature:
Currently, multiple clustered hypervisors can't each run their own local storage domain. The request is to allow that functionality, and all normal storage operation controls (except for the shared-only features, like migration). Treat local storage like we treat shared storage in a clustered environment. This means also allowing multiple local storage domains (say, one per host in a cluster), as well as shared storage across the cluster.
Example use case:
For high-IO virtualized workloads, local storage is orders of magnitude cheaper than the equivalent performance out of shared storage, especially when the physical footprint is quite small. Here's an actual customer example (customer name removed):
$COMPANY does live video streaming. The [virtualized] workload requires high IO and low storage latency. They have clustered hypervisors running this workload, using SSDs installed locally to each hypervisor. This affords them high IOPS at a "low" cost. The application itself is designed to be highly available, so HA/migration at the virtualization level is not necessary.
This customer also has a small footprint colocated at 30+ sites where the streaming originates running a similar workload to SSD, running on two clustered hypervisors per site. It would be especially uneconomical to purchase high-IO shared storage for this use case, so local SSDs are the best fit.
*** This bug has been marked as a duplicate of bug 1109597 ***