----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/12427/#review23576 -----------------------------------------------------------
Ship it! master -> 78f1092df12928f06646b3bc42d69cc45dd3b1d3 4.2 -> f604e3d9cc9073c8863bbd7dfc47fb6693a0b6f0 Currently in the db. for total capacity of a resource actual value is stored but for used capacity the value stored takes into account over provisioning factor. As a result of this for any comparison the total capacity needs to be re-calibrated in the code everywhere based on over provisioning factor. Please open a new bug for future to store used/total capacity values in db. based on same scale factor. - Koushik Das On July 19, 2013, 10:14 a.m., Harikrishna Patnala wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/12427/ > ----------------------------------------------------------- > > (Updated July 19, 2013, 10:14 a.m.) > > > Review request for cloudstack, Abhinandan Prateek, Koushik Das, and Nitin > Mehta. > > > Bugs: CLOUDSTACK-3365 > > > Repository: cloudstack-git > > > Description > ------- > > CLOUDSTACK-3365: cluster level parameters > cluster.(cpu/memory).allocated.capacity.notificationthreshold is not > considering overcommit value > > > Diffs > ----- > > server/src/com/cloud/alert/AlertManagerImpl.java 9b7cd27 > > Diff: https://reviews.apache.org/r/12427/diff/ > > > Testing > ------- > > Tested locally both with actual usage and over committed values for memory. > > > Thanks, > > Harikrishna Patnala > >
