[
https://issues.apache.org/jira/browse/CLOUDSTACK-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204110#comment-15204110
]
ASF GitHub Bot commented on CLOUDSTACK-8800:
--------------------------------------------
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/780#issuecomment-199254175
@DaanHoogland I don't see any reason for closing master in this case. If an
issue is noticed after a merge, it definitely needs to be tracked and fixed.
Releasing a branch can definitely be blocked if the issues (particularly
regressions) are not addressed but I don't see any reason to close master for
other commits. I think that closing master makes sense only if build is broken
or there is a blocking regression introduced after the last release.
> 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)
