Re: [YANG] new pyang errors

Balazs Lengyel <balazs.lengyel@ericsson.com> Thu, 24 January 2008 08:48 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 1JHxlX-0006QL-HD; Thu, 24 Jan 2008 03:48:55 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHxlV-0006QA-8J for yang-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 03:48:53 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHxlU-0006Q1-RL for yang@ietf.org; Thu, 24 Jan 2008 03:48:52 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHxlU-0003WJ-EL for yang@ietf.org; Thu, 24 Jan 2008 03:48:52 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 6B49520D63; Thu, 24 Jan 2008 09:48:51 +0100 (CET)
X-AuditID: c1b4fb3c-aa2ecbb0000007e0-81-479850f3b412
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 4F8F7209F2; Thu, 24 Jan 2008 09:48:51 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 Jan 2008 09:48:51 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 Jan 2008 09:48:50 +0100
Message-ID: <479850F2.8090106@ericsson.com>
Date: Thu, 24 Jan 2008 09:48:50 +0100
From: Balazs Lengyel <balazs.lengyel@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Phil Shafer <phil@juniper.net>
Subject: Re: [YANG] new pyang errors
References: <200801232035.m0NKZamr024518@idle.juniper.net>
In-Reply-To: <200801232035.m0NKZamr024518@idle.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2008 08:48:50.0802 (UTC) FILETIME=[F0FF2520:01C85E65]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: yang@ietf.org, Ladislav Lhotka <lhotka@cesnet.cz>
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

For us the default would be: give me the full config with all defaults; and the option, 
without-defaults.
But I agree that both solutions have value.
Balazs

Phil Shafer wrote:
> Andy Bierman writes:
>> huh -- it uses up an extra second of bandwidth so the system is fragile?
> 
> No, the human element is fragile.  Having a config file littered
> with values that the user didn't ask for and doesn't need it a
> great way to help them ignore the parts of the config that they
> did ask for and do need.
> 
>> There are lots of scenarios that cause an operator or application
>> to need to full configuration, not just the values that do not have
>> the default value.
> 
> If you see a value in this, make it an option to <get-config>.
> It should not be the default behaviour.
> 
> Thanks,
>  Phil
> 
> 
> _______________________________________________
> YANG mailing list
> YANG@ietf.org
> https://www1.ietf.org/mailman/listinfo/yang

-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
TSP System Manager
ECN: 831 7320                        Fax: +36 1 4377792
Tel: +36-1-437-7320     email: Balazs.Lengyel@ericsson.com


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