Most servers have a local storage. Some servers have very reliable storages with hardware RAID controllers and battery units. The best way to use such storages in multi server datacenters is exporting it over NFS. Treating a local NFS storage as a local storage improves performance for local VMs by removing NFS server/client layers. Currently setting up of NFS exports is out of scope of oVirt. However this would be a way to get rid of "Local/Shared" storage types of datacenter. So all storages are shared, but local storages are used as local.
fixed oVirt gerrit id
(In reply to Pavel Gashev from comment #1) > fixed oVirt gerrit id I can't find that gerrit ID still.
https://gerrit.ovirt.org/#/c/68822/
(In reply to Pavel Gashev from comment #3) > https://gerrit.ovirt.org/#/c/68822/ "The page you requested was not found, or you do not have permission to view this page."
This is more of a feature than a bug, and I'd be happy to see a feature page for it on ovirt.org, or at least some discussion around it on the devel mailing list. Specifically, if you are mounting it locally, why do you need NFS? Or is it a case where host A is sharing an NFS mount point with all hosts, so while host B will use that same export over NFS, host A could benefit from local storage access to the same mount point?
(In reply to Yaniv Kaul from comment #5) I've open a discussion on the devel mailing list. Shortly, the solution provides ability to use a local storage with no drawbacks in a shared storage multi server datacenter. I would consider this as an enhancement. The patch would work in 3.6/4.0. A feature of 4.1 would be to get rid of storage types of datacenters. It would require this enhancement.
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
commenting that I may have a customer who is interested in this feature.
This request is not currently committed to 4.4.z, moving it to 4.5
Possible duplicate: https://bugzilla.redhat.com/show_bug.cgi?id=1889138
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
This bug has not been prioritized or updated for a long time and therefore deemed stale. Closing for now, please feel free to update and reopen, but kindly provide justification or development plan how/when to address this bug