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

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

Github user kishankavala commented on the pull request:

    https://github.com/apache/cloudstack/pull/780#issuecomment-199222784
  
    @swill @remibergsma @DaanHoogland PR was open since Sep 2015. Review from 
@swill came after the PR was merged on Mar 17 2016. By then, there were code 
reviews and tests done with 3 LGTMs. I merged the PR as per the current 
process.  
    Unfortunately all reviewers missed the issued mentioned by @swill   
    Thanks to @rafaelweingartner https://github.com/apache/cloudstack/pull/1444 
addresses the runtime exception issues.
    Unless there are issues with PR 1444, I do not see a need to revert this 
merge. Can we all please review PR 1444 and close this issue?



> Improve the listVirtualMachines API call to include memory utilization 
> information for a VM
> -------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8800
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8800
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.5.2
>            Reporter: Maneesha
>            Assignee: Maneesha
>             Fix For: 4.6.1
>
>
> Currently the feature of memory utilization is not available via API call 
> (listVirtualMachines).
> https://cloudstack.apache.org/api/apidocs-4.5/root_admin/listVirtualMachines.html
>  
> The listVirtualMachine get its values from the "user_vm_view" table in the 
> database. Currently it shows the CPU utilization of the VM's.
> The only way to find out the memory utilization of VM's running on XenServer, 
> is to run the "xentop" command on the pool master of the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to