BIND 10 #123: 'stopping' messages and 'alive' channel

BIND 10 Development do-not-reply at isc.org
Tue Dec 14 10:09:40 UTC 2010


#123: 'stopping' messages and 'alive' channel
---------------------------------------------+------------------------------
      Reporter:  jelte                       |        Owner:  jelte
          Type:  enhancement                 |       Status:  new  
      Priority:  major                       |    Milestone:       
     Component:  Inter-module communication  |   Resolution:       
      Keywords:                              |    Sensitive:  0    
Estimatedhours:  0.0                         |        Hours:       
      Billable:  0                           |   Totalhours:       
      Internal:  0                           |  
---------------------------------------------+------------------------------

Comment(by jelte):

 We appear to have a fundamental disagreement here :)

 I think that whether or not a module should be running (i.e. started,
 restarted, or stopped), is a property of boss, not the module itself.

 Taking that as a base, I think that the configuration and user-visible
 commands should also be for boss; i.e. we should remove the shutdown
 commands in modules (or rather, make them internal only), skipping one
 important detail for now, that would mean:
 - Boss has a list of modules that should be running (hardcoded at this
 moment)
 - Boss starts and restarts all modules in that list
 - By changing that list, you can stop modules

 Additionally, for more runtime control, we add the following direct Boss
 commands:
 Boss restart <module>, stop the module, and restart it
 Boss start <module>, start the module, and restart it if it fails
 Boss stop <module>, stop the module, but do not restart it
 (these last two could either have the effect of updating the config list,
 or only run this during the current run of the boss process)

 The detail I'm ignoring here is inter-module dependencies, which boss
 should have no knowledge of, and which may depend on specific module
 configuration. I have some diverging ideas on how to get to that, but none
 fully formed yet.

 Chair-throwing may commence.

-- 
Ticket URL: <http://bind10.isc.org/ticket/123#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list