[bind10-dev] few configuration thoughts

[Jelte Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/04/2012 11:00 PM, JINMEI Tatuya / 神明達哉 wrote:
> 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.
>> 

it actually did happen in some cases, but that was a bug that has been
fixed.

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

yes, the .db file was never intended to be edited. And it does indeed
only contain 'nondefault' values. It wouldn't be that hard to change
that, but IMO wouldn't make much sense either.

- From the UI (i.e. bindctl point of view), there is no command to show
every non-default setting, but we could make that; it does already
show in 'config show' whether options are default, modified, or
changed (modified but not committed).

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk99uvcACgkQ4nZCKsdOncVV2ACfRhlklAQM5h08RDTwesCQ28lZ
kVEAnRZb4RMBY0df9sXq7zPsiOg1QiND
=xBLX
-----END PGP SIGNATURE-----