It looks like in 4.2 it is set in VolumeApiServiceImpl.configure(), but that method does not exist in master (and the history only goes back 8 days).
On Aug 21, 2013, at 3:08 PM, "SuichII, Christopher" <[email protected]> wrote: > Yeah, I'm on master. That setting is set to 2000 (as found through the UI). > > On Aug 21, 2013, at 2:12 PM, Koushik Das <[email protected]> > wrote: > >> In 4.2 branch it gets initialized from config property >> "storage.max.volume.size". >> Storage DEFAULT management-server storage.max.volume.size 2000 >> The maximum size for a volume (in GB). >> >> Which branch are you in? Master. Maybe some missing commit in master. >> >>> -----Original Message----- >>> From: SuichII, Christopher [mailto:[email protected]] >>> Sent: Wednesday, August 21, 2013 11:28 PM >>> To: <[email protected]> >>> Subject: Unable to create volume - volume size xxxx, but the maximum size >>> allowed is 0 Gb. >>> >>> I get the error message: 'volume size xxxx, but the maximum size allowed is >>> 0 >>> Gb.' when I attempt to create a new volume. It is thrown from >>> VolumeApiServiceImpl.validateVolumeSizeRange(int size). >>> >>> Unless I'm missing something, it looks like '_maxVolumeSizeInGb' is never >>> initialized in VolumeApiServiceImpl.java. Am I missing the initialization >>> somewhere? >>> >>> -Chris >
