Re: [YANG] mandatory & default

On Sun, Jan 27, 2008 at 08:54:51PM -0800, Randy Presuhn wrote:

> If I'm archiving a configuration, I want to know *exactly*
> what it is.  One of the reasons for archiving configurations
> is so that if a box fails, a replacement can be quickly made
> to function in its place.   If there is even a remote chance
> that a default value might change between releases or on
> different versions of a hardware platform, that value needs
> to be included in an archive of the configuration.

If your replacement is using the exact same hardware configuration and
the exact same firmware version, you do not need to worry about the
defaults.

If your replacement is not using the exact same hardware configuration
and the exact same firmware version, there is a chance that things
won't work as expected, with and without saved defaults.

If things fail, you need to have a human to figure out what is the
configuration and what is saved default noise. So the bottom line of
my thinking is that you like to have both - the explicitly set config
and the full configuration state including the defaults. Only if you
have both, you can reasonably debug configuration playback errors on
replacement hardware.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang