[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237650#comment-16237650
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9972:
--------------------------------------------

blueorangutan commented on issue #2158: CLOUDSTACK-9972: Enhance listVolume API 
to include physical size and …
URL: https://github.com/apache/cloudstack/pull/2158#issuecomment-341717776
 
 
   @nvazquez a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enhance listVolume API to include physical size and utilization.
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9972
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9972
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.9.3.0
>         Environment: VMWare, Xen and KVM
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>            Priority: Major
>             Fix For: 4.10.1.0
>
>
> The Cloudstack stat collector has been extended to include for each volume 
> its physical size and virtual size as reported by the respective hypervisor 
> where the volume resides. This patch includes impl for KVM, Xenserver and 
> VMWare.
> In addition to above, the listVolume API has been fixed to report and filter 
> pod and cluster information.
> The volume_view has been updated and a configuration parameter 
> 'volume.stats.interval' is introduced to control the interval of volume size 
> collection from back-end hypervisor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to