537853 - Need to dynamically update various configuration data without restarting the cron process

Status: RESOLVED WONTFIX

(Socorro :: Infra, task)

Description

[Frank Griswold [:griswolf] [:fgriswold]]

One example: the Option prefixSignatureRegEx for the processor code. As developers discover signatures that could be improved, they want us to be able to adjust the way signatures are created. There are other places where being able to dynamically change a configuration detail would be good.

This is a four step dance: 
 - Create code to allow dynamic config updates (done with r1672)
 - Refactor various cron code to make use of the dynamic capability
 - Create a database table to specify config details
 - Create a UI that allows that table to be manipulated by those authorized to do so.

Comment 1

[Frank Griswold [:griswolf] [:fgriswold]]

I see that the reference to the code change is bogus. dynamic configuration is now available in .../socorro/lib/dynamicConfigurationManager.py which appeared at revision 1672: Text Last Updated: 2010-01-04 15:26:05

Comment 2

[Austin King [:ozten]]

(In reply to comment #1)
Is this bug still valid?

Comment 3

[Frank Griswold [:griswolf] [:fgriswold]]

Yes in the sense that we could/should do this task to make life easier. 

The first obvious beneficiary is signature munging: Once we set (processor?) up to use dynamic configuration, we could have a nice GUI front end to a table of regular expressions (or any other reasonable technique) and let the processor look there periodically. DynamicConfiguration class can also look at the environment or a file (or anything else you can code: A web service could work). Whatever makes sense.

Comment 4

[Frank Griswold [:griswolf] [:fgriswold]]

In discussion with metrics group, they prefer looking at a file that can be updated as needed.

Comment 5

[Michael Morgan [:morgamic]]

-> 1.6 unless this is super urgent.

Comment 6

[Laura Thomson :laura]

Leaving in future...although I suspect switching to hbase will make most of this go away.

Comment 7

[Laura Thomson :laura]

I think this is a wontfix at this point: configuration has moved on a long long way from when this bug was filed (puppet, and now configman), and we also no longer care much about kicking components since we have plenty of redundancy.