[bind10-dev] few configuration thoughts

[Jeremy C. Reed]

On Mon, 2 Apr 2012, Michal 'vorner' Vaner wrote:

> > 4) bindctl should be able to show configurations in use. For example in 
> > the postfix world, "postconf" will report all the configurations 
> > (parameters and settings). And "postconf -n" will show just the 
> > custom settings.
> 
> Doesn't some kind of config show work? I think config show_json was 
> doing that.

config show_json module (you need the module) shows just "null" if no 
change.  But if you change one item within the set, then it will show 
the other defaults too.

I don't see any feature that specifically shows the custom settings.

> > 5) Boss components configurations should indicate msgq and sockcreator 
> > too? Maybe add to configuration but make it so not optional (they are 
> > mandatory).
> 
> Why? Are they really components? The boss itself is not included 
> either. I don't see any advantage in that for an administrator and it 
> would need quite some hacks.

Not sure yet about this. But I think I'd like to see what commands are 
ran by bind10.  Also is sockcreator required? (Is it needed for DHCP 
only if not using cmdctl?)

> > 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?

Thanks for your comments.