Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ovirt provider Storage uncommitted does not match the common definition #681

Open
agrare opened this issue Nov 20, 2024 · 2 comments
Open
Assignees
Labels

Comments

@agrare
Copy link
Member

agrare commented Nov 20, 2024

Discussed in https://github.com/orgs/ManageIQ/discussions/23272

Originally posted by szajac01 November 20, 2024
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....

@agrare agrare added the bug label Nov 20, 2024
@agrare agrare transferred this issue from ManageIQ/manageiq Nov 20, 2024
@agrare
Copy link
Member Author

agrare commented Nov 21, 2024

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).

@szajac01
Copy link

To get the coherent value in ManageIQ, i had to change ref

#:uncommitted => total - committed,
:uncommitted => committed,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants