cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4882) listClusters API not accounting for reserved in the used capacity percentage.
Date Wed, 16 Oct 2013 22:02:41 GMT

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

ASF subversion and git services commented on CLOUDSTACK-4882:
-------------------------------------------------------------

Commit f91b649b3b56099528fd8e6958a3bd45b7a353f8 in branch refs/heads/4.2 from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f91b649 ]

CLOUDSTACK-4882:
list Clusters/pods/zones API not accounting for reserved in the used capacity percentage.
Fix listCapacity cmd for reserved as well
Signed off by : nitin mehta<nitin.mehta@citrix.com>


> listClusters API not accounting for reserved in the used capacity percentage.
> -----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4882
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4882
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>             Fix For: 4.2.1
>
>
> I looked at the code and logs and it seems like there is a bug in the listClusters API
where we are just showing the used / total percentage instead of (used + reserved) / total
ratio.
> But the allocator logic is working perfectly fine. As an alternative to listClusters
api the admin can use listCapacity api with clusterid and that is working fine right now.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message