Re: [YANG] new pyang errors

Phil Shafer <phil@juniper.net> Wed, 23 January 2008 06:00 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 1JHYef-0004MY-8f; Wed, 23 Jan 2008 01:00:09 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHYee-0004JA-Fp for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 01:00:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHYee-0004IS-5e for yang@ietf.org; Wed, 23 Jan 2008 01:00:08 -0500
Received: from exprod7og106.obsmtp.com ([64.18.2.165]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHYed-0003KV-Pe for yang@ietf.org; Wed, 23 Jan 2008 01:00:08 -0500
Received: from source ([66.129.224.36]) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP; Tue, 22 Jan 2008 21:59:45 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 22 Jan 2008 21:59:53 -0800
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m0N5xr906306; Tue, 22 Jan 2008 21:59:53 -0800 (PST) (envelope-from phil@idle.juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m0N5xoXf020086; Wed, 23 Jan 2008 05:59:51 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801230559.m0N5xoXf020086@idle.juniper.net>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
Subject: Re: [YANG] new pyang errors
In-reply-to: <000401c85d82$c082fa40$6801a8c0@oemcomputer>
Date: Wed, 23 Jan 2008 00:59:50 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 23 Jan 2008 05:59:53.0891 (UTC) FILETIME=[2C838730:01C85D85]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
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

"Randy Presuhn" writes:
>Strongly disagree.  Operationally, one needs to be able to
>determine what the configuration actually *is*, regardless of
>whether it was ever expressed by a user or application.

One can use alternative views ("with-defaults") or external information
(YANG modules) to acquire this information.  The main target of
configuration remains (and will remain for some time) the human
users.  Verbose configurations breed confusion and most of my efforts
in my day job are targeted to simplifying configurations and reducing
the volume of data human users need to look at.

>This is sufficient to configure a device, but it's not
>configuration management.

I don't follow you here.  Please explain how the alternative
interpretation of "mandatory" aids in configuration management.
Is the "with-defaults" view key to a good solution?

Thanks,
 Phil


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