Re: [YANG] mandatory & default

Andy Bierman <ietf@andybierman.com> Mon, 28 January 2008 11:29 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJSAh-0002xU-4e; Mon, 28 Jan 2008 06:29:03 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JJSAf-0002xB-JI for yang-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 06:29:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJSAf-0002w4-7Q for yang@ietf.org; Mon, 28 Jan 2008 06:29:01 -0500
Received: from smtp117.sbc.mail.sp1.yahoo.com ([69.147.64.90]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JJSAe-0005VD-Ni for yang@ietf.org; Mon, 28 Jan 2008 06:29:01 -0500
Received: (qmail 68022 invoked from network); 28 Jan 2008 11:29:00 -0000
Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@67.121.104.118 with plain) by smtp117.sbc.mail.sp1.yahoo.com with SMTP; 28 Jan 2008 11:28:59 -0000
X-YMail-OSG: HaESxf0VM1kAXn4ZabOX3jXylEpKlbWvxH6BlV082ilqdvzECYnu3SYTCjUd9D7EOcN1UmLNBt3jqNbOCMqhyZDe
X-Yahoo-Newman-Property: ymail-3
Message-ID: <479DBC89.5010503@andybierman.com>
Date: Mon, 28 Jan 2008 03:29:13 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Phil Shafer <phil@juniper.net>
Subject: Re: [YANG] mandatory & default
References: <200801280650.m0S6o9wi052898@idle.juniper.net>
In-Reply-To: <200801280650.m0S6o9wi052898@idle.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: yang@ietf.org
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

Phil Shafer wrote:
> "Randy Presuhn" writes:
>> 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.
> 
> Loading the saved file with defaults won't make this
> any saner, safer, or stronger.  It increases the fragility,
> but incorporating into the saved file tons of stuff about
> which you don't care.  It something fails on these values
> that you don't care about, you are broken.
> 

this is not correct.
If you load a config with the full set of values, then
agent is forced to accept the value or issue an error.
This is not fragile.  This is debugging.

Fragile is when the new software image sees that no value
is given for the foo-knob, so it assigns a *different*
default value than the last SW image, and does not complain
at all.


Andy


>> 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.
> 
> The chance of a change in defaults (which annoy customers to
> no end) is minor compared to the change of adding features (which
> customers insist on) and the need to support downgrading (which
> customers insist on).
> 
> Consider this example from JUNOS-land.  We have a set of foo-options
> containers that are used to hold media-specific options under
> the [interfaces] statement.  These options are numerous, verbose,
> and rarely used.  If I add a new statement in release 9.0 and
> start emitting a boring default value for it, I can no longer
> load that config in any release predating 9.0.
> 
> In avoiding a rare bug (changing defaults), you'll break real
> operational usage.
> 
> Thanks,
>  Phil
> 
> 
> _______________________________________________
> YANG mailing list
> YANG@ietf.org
> https://www1.ietf.org/mailman/listinfo/yang
> 
> 



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