[Opensim-dev] Round 2: Config changes preview

[Melanie]

That is exactly what I proposed. DO away with any and all *.example 
files. Provide defaults in external files. Never write/overwrite 
configuration files. Allow override, including multi-level. Support 
network loading of settings.

Melanie

Mister Blue wrote:
> I would like to hear from people running a large configuration of
> simulators and regions -- how do they want configuration?
> 
> For our installation, we use a --inimaster on each simulator
> invocation to set up site wide settings (physics engine, etc) and then
> each simulator has an very small OpenSim.ini file in it's bin
> directory to set simulator specific configuration. We also have
> scripts that 'hide' the OpenSim.ini file in the Regions directory
> because that is a directory of information that you save when you
> upgrade the binaries.
> 
> It's nice to have the defaults around so you know what you can tune,
> but it is of no use to a running simulator.
> 
> I would prefer a directory of default ini files (a directory so the
> installation of a module can easily add a new set of parameters) and
> then a single ini file that the simulator reads which overrides any of
> the defaults. That would make administration easier since you would
> know what you have change from the defaults. Also, ideally, the
> overriding ini file should be in a 'user' directory -- not in the main
> bin directory so one could upgrade the binaries by just slamming the
> contents of a bin directory from a build on top of it.
> 
> Some more two cents.
> 
> -- mb
> 
> On Sat, Mar 14, 2009 at 6:52 AM, Stefan Andersson <stefan at tribalmedia.se> wrote:
>> Some random thoughts;
>>
>> Our config files serves three purposes, as it seems
>> a) specifying default values (though why on earth these are ever different
>> from the hardcoded defaults escapes me)
>> b) specifying user overriding values
>> c) documenting available settings and their use
>> d) pushing changing defaults from the svn to installed instances
>>
>> I think we need to address these concerns separately.
>>
>> As I understand it, the config dir is so that we can
>> a) split humongous default config files into smaller ones
>> b) to be able to 'drop' module default config files into an installation
>> without having to merge them into one big ini.
>>
>> I think the settings can be split thrice;
>> 1) Stuff that _must_ be reconfigured per installation : ip number, shared
>> ports and stuff like that. (All users, should need no expertise)
>> 2) Stuff that _can_ be reconfigured per installation. (Special installation
>> cases, needs some knowledge)
>> 3) Stuff that _seldom_ needs tampering. (Advanced user, special
>> installation)
>>
>> I would suggest we break free of the current mindset and think about how
>> 1) could be solved differently.
>>
>> Maybe we should say "either supply these settings on the command line, or
>> create an OpenSim.ini file, look at OpenSim.ini.example for an example"
>>
>> Most users would probably go a long way just by specifying the 1) params on
>> the command line.
>>
>> Of course, the created OpenSim.ini should need to be a bare minimum, and
>> would probably need to change very seldom.
>>
>> Best regards,
>> Stefan Andersson
>> Tribal Media AB
>>
>>
>>
>>
>>> Date: Sat, 14 Mar 2009 04:25:25 -0700
>>> From: aerowolf at gmail.com
>>> To: opensim-dev at lists.berlios.de
>>> CC: opensim-users at lists.berlios.de
>>> Subject: Re: [Opensim-dev] Round 2: Config changes preview
>>>
>>> because many people run their servers from inside their bin/
>>> directory, and if it's named OpenSim.ini then any changes that are
>>> made to that file will get overwritten (not just overridden) at the
>>> next svn update.
>>>
>>> That's why it was renamed to OpenSim.ini.example -- originally, it was
>>> set to OpenSim.ini, and that problem was pretty much the number one
>>> support issue at that time.
>>>
>>> -Kyle H
>>>
>>> On Fri, Mar 13, 2009 at 5:00 PM, Paul Fishwick <fishwick at cise.ufl.edu>
>>> wrote:
>>> > Justin Clark-Casey wrote:
>>> >> To get OpenSim to run at all, the user still has to copy
>>> >> OpenSim.ini.example to OpenSim.ini (though it should be
>>> >> possible to override this if config is supplied over the network).
>>> >
>>> > This may be a silly question, but is there some reason why we keep on
>>> > suggesting
>>> > that people copy OpenSim.ini.example to OpenSim.ini? Why not just make
>>> > OpenSim.ini what happens to be in OpenSim.ini.example?
>>> >
>>> > -p
>>> >
>>> >
>>> > Paul Fishwick, PhD
>>> > Professor and Director, Digital Arts and Sciences Programs
>>> > University of Florida
>>> > Computer & Information Science and Eng. Dept.
>>> > Bldg. CSE, Room 301
>>> > P.O. Box 116120
>>> > Gainesville, FL 32611
>>> > Email: fishwick at cise.ufl.edu
>>> > Phone: (352) 392-1414
>>> > Fax: (352) 392-1220
>>> > Web: http://www.cise.ufl.edu/~fishwick
>>> >
>>> > _______________________________________________
>>> > Opensim-dev mailing list
>>> > Opensim-dev at lists.berlios.de
>>> > https://lists.berlios.de/mailman/listinfo/opensim-dev
>>> >
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
>>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> 
>