YANIV LAVI
SENIOR TECHNICAL PRODUCT MANAGER
Red Hat Israel Ltd. <
https://www.redhat.com/>
34 Jerusalem Road, Building A, 1st floor
Ra'anana, Israel 4350109
ylavi(a)redhat.com T: +972-9-7692306 <javascript:void(0);>/8272306
<javascript:void(0);> F: +972-9-7692223 <javascript:void(0);>
IM: ylavi
<
https://red.ht/sig> TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
@redhatnews <
https://twitter.com/redhatnews> Red Hat
<
https://www.linkedin.com/company/red-hat> Red Hat
<
https://www.facebook.com/RedHatInc>
On Mon, Aug 6, 2018 at 11:40 AM Tomas Jelinek <tjelinek(a)redhat.com> wrote:
On Sun, Aug 5, 2018 at 4:52 PM, Yaniv Lavi <ylavi(a)redhat.com> wrote:
>
> YANIV LAVI
>
> SENIOR TECHNICAL PRODUCT MANAGER
>
> Red Hat Israel Ltd. <
https://www.redhat.com/>
>
> 34 Jerusalem Road, Building A, 1st floor
>
> Ra'anana, Israel 4350109
>
> ylavi(a)redhat.com T: +972-9-7692306/8272306 F: +972-9-7692223 IM: ylavi
> <
https://red.ht/sig> TRIED. TESTED. TRUSTED.
<
https://redhat.com/trusted>
> @redhatnews <
https://twitter.com/redhatnews> Red Hat
<
https://www.linkedin.com/company/red-hat> Red Hat
<
https://www.facebook.com/RedHatInc>
>
>
>
> On Fri, Aug 3, 2018 at 2:58 PM Michal Skrivanek <
> michal.skrivanek(a)redhat.com> wrote:
>
>>
>>
>> On 2 Aug 2018, at 18:46, Yaniv Kaul <ykaul(a)redhat.com> wrote:
>>
>>
>>
>> On Thu, Aug 2, 2018 at 6:39 PM, Scott Dickerson <sdickers(a)redhat.com>
>> wrote:
>>
>>> I have a pair of questions I could use some help with.
>>>
>>> 1. Does the oVirt guest agent collect filesystem level information?
>>> I'm hoping something like what `df -h` would report. File systems, free
vs
>>> used space, etc. Bonus points if we can get that kind of info from linux
>>> and windows agents.
>>>
>>
>> It did in the past, I hope we've removed it!
>>
>>
>> on the contrary, it’s being added to qemu-ga!:)
>>
>>
>>
>>>
>>> 2. Assuming that info is available, where can I access it? I assume it
>>> isn't surfaced via the REST api (yet), but it would be good to know
where
>>> it is available.
>>>
>>
>> Somewhere in DWH.
>>
>>
>> and hence the engine db too. That’s where it stops, I do not see anyone
>> else reading it once we persist it
>>
>
> DWH collects this from engine and stores it as a JSON.
> It can be queried historically.
>
indeed, and no one else. And it seems to be intentional according to this
comment:
/**
* Field for history db, not intended to be accessible to clients.
*/
public String getDisksUsage() {
return disksUsage;
}
does anyone know why? Is there any reason not to expose it?
We never got a RFE on exposing this info anywhere else.
>
>
>>
>>
>>
>>>
>>>
>>> Why? I'm updating VM Portal (web-ui), and it would be great to
>>> chart/report guest derived data rather than infrastructure disk provisioned
>>> vs allocated space.
>>>
>>
>> In theory. In practice, it was never accurate (LVM layers, not to
>> mention block, etc.)
>>
>>
>> right, what we observe from storage is inaccurate. But we can report
>> guest POV. After all that’s the most interesting thing to see for users
>> that their / is getting full. Admins should observe real storage usage in
>> webadmin.
>>
>> Y.
>>
>>
>>>
>>> Thanks!
>>>
>>> --
>>> Scott Dickerson
>>> Senior Software Engineer
>>> RHV-M Engineering - UX Team
>>> Red Hat, Inc
>>>
>>> _______________________________________________
>>> Devel mailing list -- devel(a)ovirt.org
>>> To unsubscribe send an email to devel-leave(a)ovirt.org
>>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>>
https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZF6QNDMV5VL...
>>>
>>>
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org
>> To unsubscribe send an email to devel-leave(a)ovirt.org
>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>>
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VOAHEVG5A2P...
>>
>>
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org
>> To unsubscribe send an email to devel-leave(a)ovirt.org
>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>>
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/KHOBC5NSXMG...
>>
>
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4OACOKCGM23...
>
>