[Simfactory] Automatically updating Cactus configuration options?
knarf at cct.lsu.edu
Thu Feb 24 09:15:31 CST 2011
On Thu, Feb 24, 2011 at 09:52:27AM +0100, Ian Hinder wrote:
> I would like any changes to optionlists, submit script and run
> scripts to also be included in the configuration.
I second this. I can see the problems with both approaches, though. New
users probably expect those to be updated - as can be seen by bug
reports about this already, but overwriting a working configuration for
a production simulation would be bad as well.
Erik already pointed out the problems with making that globally
configurable, and I agree. Another idea would be to give configurations
within simfactory some kind of 'state', e.g. 'development' (by default)
or 'production'. This state could be set/changed by simfactory and would
influence things like the automatic update of the configuration options.
This could also be useful for e.g. deciding if some notifications about
jobs starting/stopping are sent, or other things people do differently
for development and production configurations.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available
Url : http://mail.cct.lsu.edu/pipermail/simfactory/attachments/20110224/a1edb1f4/attachment.bin
More information about the SimFactory