[WG: Sakai QA] QA servers and Config Viewer/Editor

[Jean-Francois Leveque]

Thanks for the update of trunk, Matthew. It seems you're maintaining it 
right now for your own purposes. Why not maintaining it for the 
community in the 2.6.x branch instead of updating your own branch?

Do you mean you're already running Config Editor with a custom kernel?

Do you know if Config Editor still needs to be fixed to get changes 
across load balanced servers?

I don't need property alterations right now, but being on a different 
time zone, I get configuration changes on my next working day or later. 
I would reset the values after making a test, but understand the danger 
and leave the decision to QA server admins.

Matthew Jones a écrit :
> The trunk of both tools are updated to work with 2.6. Config Viewer 
> builds and installs without any problem and only binds to kernel. This 
> should be easy to drop onto a QA server.
> 
> Config Editor requires a patch to the kernel, which is something that 
> generally isn't done on the QA's (kernel builds).
> 
> I agree that having config viewer would be useful. We've been running it 
> at michigan for awhile, and are running the 2.6 modified version. The 
> problem I can see with having config editor is that while it could be 
> useful for one person to test some settings on a QA server, it would 
> make the server settings constantly variable. It also doesn't persist 
> the settings making the QA also a less predictable instance.
> 
> If you need to alter a certain property to verify a change, just send a 
> note to the list and I'm sure one or more of the servers admins could 
> accommodate your request.
> 
> On Wed, Sep 16, 2009 at 6:28 AM, Jean-Francois Leveque 
> <jean-francois.leveque at upmc.fr <mailto:jean-francois.leveque at upmc.fr>> 
> wrote:
> 
>     As far as I can remember, I was involved in a QA discussion at the last
>     conference and everybody thought it was a good idea to include Config
>     Viewer on QA servers, event if it's still a contrib project.
> 
>     I now think it might be a good idea to also include Config Editor to be
>     able to alter the default QA configuration to test such issues that
>     depends on certain values in sakai.properties. This may be the case with
>     SAK-16317, haven't checked the default QA configuration.
> 
>     It seems Config Viewer needs to be updated for 2.6 and it might also be
>     the case for Config Editor. Should the Maintenance Team be involved in
>     this or do we have volunteers right now?
> 
>     What do you think about the whole idea?
> 
>     Cheers,
> 
>     Jean-Francois