-
Notifications
You must be signed in to change notification settings - Fork 69
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
Top Storage Consumers Report: Total Used Disk space is not accurate #98
Comments
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
I will check against Gapri-1 release to see if disk usage report is still not correct. |
I think the issue here is that the It would be possible to add vm-level used storage and override this core |
Thanks for the hint Adam.
…On Mon, Nov 26, 2018, 14:48 Adam Grare ***@***.*** wrote:
I think the issue here is that the :used_storage for a VM ends up using
the disks' size_on_disk property and we can't get the actual used storage
per disk from the VIM SDK. We can only get this per datastore at the VM
level.
It would be possible to add vm-level used storage and override this core
used_disk_storage method for vmware.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAXHDrXzd6imTz7pq2clG2vo1SbttLXLks5uzFOZgaJpZM4O214S>
.
|
Have this been fixed? or a workaround? |
@paltaa , I reported this issue for vCenter provider. |
Hi All I did another verification on this issue.
So this issue can be closed. VMWare VM actual space usage reported once it is scanned by smart analysis. |
Thanks @tjyang ! Yeah it should be more obvious that smartstate is required for these, we had issues with this recently with the snapshot size as well. |
@agrare , I think this issue happened even the VM got scanned by S.A. in earlier versions of MIQ. |
@tjyang Will test and confirm, thanks alot |
@tjyang Okay, so it was in fact a smart analysis problem, but since it creates snapshots of the VM's to get the analysis and the real disk usage, this creates a downtime of a few seconds that we cannot afford, so is there any other way we could get those metrics, or point me in the right direction to do it in the manageiq enviroment? |
@paltaa we are unable to get file sizes from the VIM API which is used for refresh to smartstate is the only way to get this data. |
@paltaa , I don't believe the snapshot will be a few seconds long in a production VMWare setting that has hight end (flash) storage systems. I know netbackup/rubrik for VMWare are using snapshots for backup purpose. Unless your VM has very very high I/O otherwise taking snapshot should be fine. You can try S.A. on less busy VM first. Also looks like you are using miq to manage production environment which is not recommended by miq team ;). Also I voiced in another ticket that S.A. should not rely only on snapshot approach to gather system information. a simple ansible/ssh login shell script can collect most of the system info. Another point is that miq is is now managing phyiscal machines also.(no way to take snapshot). Hope your question can be addressed by manageiq team members. |
@tjyang Thats the point, dont see the necesity to do a disk usage analysis by taking a snapshot if a small ansible playbook could get the metrics and return them to manageiq or any other system. |
Do you want me to open up a RFE on S.A. without snaptshot action on providers ? |
@tjyang It would be nice, also is there a url to join that discussion/follow the thread or contribute to that solution |
@paltaa well we wouldn't use an ansible playbook because we already have an efficient connection broker so we'd save sessions on your VC by not using ansible :) @tjyang Yes I think that would be a good enhancement request, the description would be "Acquire disk usage with datastore smartstate not vm smartstate". It isn't going to be easy and will require a good bit of refactoring but there is a workaround. Also @paltaa taking a snapshot for smartstate should not create "a few seconds of downtime". The only "downtime" is a momentary stun/unstun when coalescing the last of the writes into the base disk. If that takes longer than a tenth of a second there is something wrong. Snapshots are used on production VMs all the time, this is not unique to manageiq. |
@agrare, pls see HOW.3 at ManageIQ/manageiq-smartstate#84, |
…tring Changed ${/#ae_reason} to a string value in on_error methods.
I have VM instance in miq version fine-3
Ex2: miq report showing both are used and provisioned are at 4TB.
Ex2: while from vcenter GUI, Used storage is only 1.76TB
The text was updated successfully, but these errors were encountered: