Config File Visibility

[GoogleCodeExporter]

Currently all config is done through the Config class and overwritten by
the storage@desk.properties.xml configuration file.

The configuration variables should be split up by application.

1) Only the volume controller should be able to see database configuration
variables
2) File locations are only needed by StorageMachine
3) StorageServer is the only one that needs Target Name

There may be others but the big one is the database configuration, the
StorageMachine and StorageServer should not have database config information.

Original issue reported on code.google.com by tommy.mu...@gmail.com on 16 Mar 2009 at 3:36

[GoogleCodeExporter]

Revision 12 addresses some of this issue.  The new storage@desk.properties.xml 
file
has comments for the visibility of the different parts of the application.

It also lets database variables be configured within the XML.

At this point there is no security concern about the database information, 
unused
variables are ignored and would just not be provided in the default xml file 
for the
storageserver and storagemachine applications.

We still may want to separate it further.

Original comment by tommy.mu...@gmail.com on 30 Mar 2009 at 3:02

• Changed state: Started

[GoogleCodeExporter]

The SCSI.DEFAULT_DISK_BLOCK_SIZE must be standardized across all parts of the 
application along with Config.VOLUME_CHUNK_SIZE.  While not exactly essential 
it 
simplifies the deployment.

Splitting the config up further is a style decision and will not be addressed 
in the 
next release.

Original comment by tommy.mu...@gmail.com on 23 Apr 2009 at 8:43

• Changed state: WontFix