[bind10-dev] few configuration thoughts

[JINMEI Tatuya / 神明達哉]

At Wed, 4 Apr 2012 11:36:53 -0500 (CDT),
"Jeremy C. Reed" <jreed at isc.org> wrote:

> > > 6) When adding a single boss component, it shouldn't remove all the 
> > > other components.  This happens with other maps or named_sets too. Maybe 
> > > we need to design a new technique for this?
> > 
> > Does that really happen? It never happened for me. What I understand 
> > is it just creates a full copy of the default in the b10_config.db and 
> > acts little bit funny with config diff, but it should work otherwise.
> 
> I mis-stated this. This is not when adding a single boss component, but 
> if someone manually edited b10-config.db to add a single boss component, 
> then they will only get that component. So the workaround is adding all 
> Boss/components to the configuration.  For example, my b10-config.db is 
> empty, and then I remove Boss/components b10-stats-httpd (and commit) 
> and then the new b10-config.db lists all the other components.
> 
> My point is that I'd like to keep b10-config.db short and only contain 
> my custom changes and not include all the default configurations. Maybe 
> this is not a problem. Anyone else have any opinion on this?

I'm not so sure if this is easy or difficult in our current
implementation architecture, but feature-wise I tend to agree that
users would expect a user-editing configuration file only contains
their own customizations.  One thing that may be noteworthy is that
b10-config.db is quite unusual as a "configuration file".  I guess
it's normally not expected to be edited directly.

---
JINMEI, Tatuya