Red Hat Provider

[szajac01]

Hi
I do use Redhat Virtualization provider to create integration with OLVM.
Integration seems to be fine, objects are discovered. (Datastores,Clusters, Networks, Vm, etc...)
I have a strange behavior with Datastore objects.
v_total_provisioned attribute does not show a coherent value...
It should be the Allocated value present in OLVM. but it shows a larger higher value as if all space was allocated.
I don't find any other value in attributes that could fit....

[Fryguy]

That's interesting that the RHV provider works with OLVM - maybe we should just make it a real provider? cc @agrare

With respect to the actual value, it's possible it's a bug in the provider code - do you happen to also have a RHV system with the same problem?

[szajac01]

I don't have any RHV instance sorry...

[agrare]

So v_total_provisioned in core is used + uncommitted [ref]. In Ovirt/RHV uncommitted is total - committed [ref]

I think the issue here is that in VMware uncommitted is the theoretical size of a vmdk - the allocated size (e.g. 10GiB thin prov vmdk with 8GiB used would be 2GiB of uncommitted).

So I agree the Ovirt calculation of uncommitted here is likely incorrect, I'll create an issue from this discussion and transfer to the ovirt provider repo.

[szajac01]

I did check the values with this calculation , and that fits with those definitions.

With this example for OLVM Gui,
Size: 6143 GiB
Available: 5038 GiB
Used: 1105 GiB
Allocated: 1772 GiB

uncommitted = total (Size) - committed (Allocated) = 6143 - 1772 = 4371
v_total_provisioned = used_space + uncommitted.to_i = 1105 + 4371 = 5478, and that's wrong

v_total_provisoned here should be Used + Allocated
So Basically if core definition stays like this , in Ovirt/RHV uncommited should be defined : uncommitted = commited (Allocated) ?

[Fryguy]

👉 ManageIQ/manageiq-providers-ovirt#681

[agrare]

That's interesting that the RHV provider works with OLVM - maybe we should just make it a real provider?

Yes, we have discussed exactly this in another issue the big open question for me was if the Ovirt/RHV provider would work without modification and based on this it sounds like it would. It would be a "simple" process of subclassing Ovirt -> OLVM then.

https://github.com/orgs/ManageIQ/discussions/23173