Really ? That's pretty bad and another downside unfortunately.
The fact that the only option for block storage is LVM (so there is not
suitable Clustered Filesystem to run QCOW2 files) and now that LVM2
Thinprovisioned is not supported can be a real issue where
Thinprovisioned LUNs are not available in the Storage Controller.
Have these topics ever came up in the feature/product management
meetings are any of them something being considered ?
The same way CPU and Memory overprovision are key features in order to
justify the overall solution cost Storage Thinprovision equally
necessary otherwise the Storage stuff end up costing more than half of
whole platform solution.
Thanks for the answer anyway. Hopefully at least LVM2 Thinprovisioning
comes up anytime soon.
Fernando
Em 11/08/2016 12:54, Nir Soffer escreveu:
On Tue, Aug 9, 2016 at 3:16 PM, Fernando Frediani
<fernando.frediani(a)upx.com.br> wrote:
> Hello all.
>
> When you use oVirt with a Block Storage the only option available to store
> de VMs is LVM.
>
> Does LVM in oVirt use Thinprovisoned (supported in LVM2) instead of having
> to use the SAN Thinprovisioned features ?
No, we use regular lvs. thin pool are not supported in a cluster.
Using thin provisioned LUN for ovirt storage domain is the best option
(supported
since 4.0). We discard removed lvs, so you get back the storage on the storage
server and can use it for other thin provisioned LUNs.
Nir