We use archaius with the zookeeper module for this https://github.com/Netflix/archaius/wiki
On Wed, May 14, 2014 at 1:18 AM, Aaron Zimmerman < [email protected]> wrote: > I would put it in zookeeper, especially since that's already a dependency. > > > > On Tue, May 13, 2014 at 10:14 AM, King, Craig A. > <[email protected]>wrote: > >> I submitted this question back in March, but did not get any responses. >> Since a little time has passed, and there are a few more folks on the mail >> list, I thought I would pop it back up again. >> >> Thanks in advance, >> >> Craig >> >> On Mar 14, 2014, at 10:26 AM, King, Craig A. <[email protected]> >> wrote: >> >> This topic was covered before, but it does not entirely fit my use case. >> >> I am looking for some best practices, or ideas on how to manage user >> names/passwords and other properties that can change at any time. >> >> The previous discussion revolved around "external" configuration at >> submission time, and can be found here: >> >> http://grokbase.com/t/gg/storm-user/134r0rbepz/submitting-a-jar-with-external-config >> >> For background, I am doing an analysis of Storm for a DoD/Navy project. >> Within the Navy there are IA (Information Assurance) rules that govern >> password changes (such as passwords must change every 30 or 45 days etc.) >> We also need to design the administration of the system for 19 year old >> sailors with a few months training. >> >> In order to manage the properties, there would be some web based UI that >> would allow the admin to update passwords and hit a save button. No file >> editing or logging into Nimbus to change configuration files. >> >> The updated passwords (and other changed properties) should become >> immediately available to all currently running topologies. There could be >> dozens or even hundreds of topologies running, so killing and resubmitting >> with new properties is not really an option. >> >> I have a couple of ideas, but I am a storm newbie so I don't know the >> feasibility... >> 1) have the spouts monitor a property server for changes and push >> configuration (would require that all bolts get these streams.) >> 2) have each spout an bolt monitor the said property server. >> 3) use Messaging and have spouts/bolts subscribe to a configuration topic. >> >> All ideas are welcome. Thanks in advance. >> >> Craig >> >> >> >
