----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/12427/#review23239 -----------------------------------------------------------
server/src/com/cloud/alert/AlertManagerImpl.java <https://reviews.apache.org/r/12427/#comment47131> Write a function getOverProvisioningFactor(clusterId, capacityType) server/src/com/cloud/alert/AlertManagerImpl.java <https://reviews.apache.org/r/12427/#comment47132> capacityValue is misleading ---- call it threshhold server/src/com/cloud/configuration/Config.java <https://reviews.apache.org/r/12427/#comment47133> Please clarify - Are they not at cluster level anymore ? server/src/com/cloud/vm/VirtualMachineManagerImpl.java <https://reviews.apache.org/r/12427/#comment47135> What was wrong here...why not taking it from Config ? - Nitin Mehta On July 10, 2013, 10:56 a.m., Harikrishna Patnala wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/12427/ > ----------------------------------------------------------- > > (Updated July 10, 2013, 10:56 a.m.) > > > Review request for cloudstack, Abhinandan Prateek, Koushik Das, and Nitin > Mehta. > > > Bugs: CLOUDSTACK-2536 and CLOUDSTACK-3365 > > > Repository: cloudstack-git > > > Description > ------- > > CLOUDSTACK-3365: cluster level parameters > cluster.(cpu/memory).allocated.capacity.notificationthreshold is not > considering overcommit value > > CLOUDSTACK-2536: parameters (cpu/memory)overcommit ratio and > (cpu/memory).overprosioning.factor are redundant(cluster level) > > > Diffs > ----- > > server/src/com/cloud/alert/AlertManagerImpl.java 9b7cd27 > server/src/com/cloud/configuration/Config.java d3ed718 > server/src/com/cloud/vm/VirtualMachineManagerImpl.java 30ee2d7 > server/test/com/cloud/vm/VirtualMachineManagerImplTest.java 44e22e2 > > Diff: https://reviews.apache.org/r/12427/diff/ > > > Testing > ------- > > Tested locally both with actual usage and over committed values for memory. > > > Thanks, > > Harikrishna Patnala > >
