cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <Chiradeep.Vit...@citrix.com>
Subject Re: Global Setting legacy items caused exception when changing the value
Date Tue, 25 Sep 2012 19:12:32 GMT


On 9/21/12 2:50 AM, "Gavin Lee" <gavin.lxh@gmail.com> wrote:

>There are some items not supported in global settings but still kept
>in DB, change them will cause exception and UI popup "Invalid
>configuration variable":
>storage.allocated.capacity.threshold
>storage.capacity.threshold
>cpu.capacity.threshold
>memory.capacity.threshold
>public.ip.capacity.threshold
>private.ip.capacity.threshold
>
>You can get more info here:
>git diff  30793ff08b92b4475c98f66c0ce92e92dadc51d3
>4b21650e233261cc9cf2464d3a5babf7bc80a49b Config.java
>
>These name-value pairs should be removed in DatabaseConfig.java.

Removed or changed as per the commit
30793ff08b92b4475c98f66c0ce92e92dadc51d3?
>
>Another question, is DatabaseConfig.java for testing purpose? If not,
>why put it into test folder?
>

This is used in the ant deploydb step, so it is not part of the server
runtime. 
I agree that it could be in a better place.


Mime
View raw message