IETF Logo Mail Archive

Re: [YANG] new pyang errors

Balazs Lengyel <balazs.lengyel@ericsson.com> Wed, 23 January 2008 08:38 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 1JHb7q-0000ul-6K; Wed, 23 Jan 2008 03:38:26 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHb7o-0000u7-Ph for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 03:38:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHb7o-0000s0-BW for yang@ietf.org; Wed, 23 Jan 2008 03:38:24 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHb7n-00080N-MV for yang@ietf.org; Wed, 23 Jan 2008 03:38:24 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id F3DEB21420; Wed, 23 Jan 2008 09:38:22 +0100 (CET)
X-AuditID: c1b4fb3e-abdeabb0000007e1-59-4796fcfecfdb
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id E082C2134E; Wed, 23 Jan 2008 09:38:22 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jan 2008 09:38:22 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jan 2008 09:38:22 +0100
Message-ID: <4796FCFD.5000102@ericsson.com>
Date: Wed, 23 Jan 2008 09:38:21 +0100
From: Balazs Lengyel <balazs.lengyel@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Ladislav Lhotka <lhotka@cesnet.cz>
Subject: Re: [YANG] new pyang errors
References: <200801230559.m0N5xoXf020086@idle.juniper.net> <1201074051.17304.35.camel@missotis> <20080123074427.GE7105@elstar.local> <1201076756.17304.62.camel@missotis>
In-Reply-To: <1201076756.17304.62.camel@missotis>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 23 Jan 2008 08:38:22.0372 (UTC) FILETIME=[50029640:01C85D9B]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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


Ladislav Lhotka wrote:
> Juergen Schoenwaelder píše v St 23. 01. 2008 v 08:44 +0100:
>> On Wed, Jan 23, 2008 at 08:40:51AM +0100, Ladislav Lhotka wrote:
>>
>>> I agree, but im my view of the NETCONF world this (optional) filtering
>>> can and should be done at the user's side, by the management
>>> application. The size/complexity of the data is not an issue for
>>> machine-machine exchange.
>> a) ssh is not going to do that for me anytime soon
> 
> It's important that raw ssh works in principle but let's face it -
> reading and typing NETCONF XML stuff via stdin/stdout is only for
> masochists.
>  
Our testers very often write the NETCONF requests/replies in a file, and send that over SSH.
So while Netconf is not a CLI, we do use raw SSH. I also think operators stated they like to 
understand raw output.
Balazs


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

v2.8.7 | Report a Bug | By Email