cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9986) Consider overcommit ratios with total/threshold values in Metrics View
Date Fri, 08 Dec 2017 12:54:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-9986:

rhtyd commented on issue #2353: CLOUDSTACK-9986: Use host table to iterate for zone/cluster
   @borisstoyanov we can run smoke tests, however the changes are limited to plugin and travis
tests are enough to validate this. I'll still kick them ;)
   @blueorangutan test

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:

> Consider overcommit ratios with total/threshold values in Metrics View
> ----------------------------------------------------------------------
>                 Key: CLOUDSTACK-9986
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: Future,
> On code analysis and discussions, I found that overcommit ratios are used with the allocated
values, instead they should be used/compared with the total/threshold values during comparison
for determining where the allocated values have gone beyond the thresholds (considering overcommit
ratios) or not.

This message was sent by Atlassian JIRA

View raw message