IETF Logo Mail Archive

Re: [Rtg-yang-coord] YANG leaf writing to running-datastore

"Sterne, Jason (Jason)" <jason.sterne@alcatel-lucent.com> Tue, 03 March 2015 13:42 UTC

Return-Path: <jason.sterne@alcatel-lucent.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD091A7018; Tue, 3 Mar 2015 05:42:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdwrSy98lDT0; Tue, 3 Mar 2015 05:42:26 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 313521A7007; Tue, 3 Mar 2015 05:42:25 -0800 (PST)
Received: from us70uusmtp4.zam.alcatel-lucent.com (unknown [135.5.2.66]) by Websense Email Security Gateway with ESMTPS id 272BB8905B13E; Tue, 3 Mar 2015 13:42:20 +0000 (GMT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id t23DgLIT015235 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Mar 2015 08:42:21 -0500
Received: from US70TWXCHMBA11.zam.alcatel-lucent.com ([169.254.5.170]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0195.001; Tue, 3 Mar 2015 08:42:21 -0500
From: "Sterne, Jason (Jason)" <jason.sterne@alcatel-lucent.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, David Ball <daviball@cisco.com>
Thread-Topic: [Rtg-yang-coord] YANG leaf writing to running-datastore
Thread-Index: AQHQVTpEq/zNRT6jCUKq/19v/CWVfp0K2boAgAAEp4D//+UsUA==
Date: Tue, 3 Mar 2015 13:42:20 +0000
Message-ID: <A125E53CE190A749957C19483DC79F9F5C9D04AD@US70TWXCHMBA11.zam.alcatel-lucent.com>
References: <CAAchPMsaZJE=TRKaDyyA8JRyQ4dt5nptD8o0pkUK-1tfNT9vgA@mail.gmail.com> <54F58512.2080900@cisco.com> <20150303101209.GB62331@elstar.local>
In-Reply-To: <20150303101209.GB62331@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/X4edv1RJXBeFKoTd-4hOUjBp0KQ>
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
Subject: Re: [Rtg-yang-coord] YANG leaf writing to running-datastore
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2015 13:42:28 -0000

Adding netconf into this as we're talking about generic netconf functionality here.

The concept of having other (somewhat arbitrary) data stores is something that may be useful for this "debug" type of configuration.  It may even make sense to have both a debug-running & a debug-startup datastore for debug (and perhaps a debug-candidate as well).  Some implementations effectively treat debug as a separate datastore (e.g. allow saving debug info separately from the rest of the configuration).

A similar approach may also make sense for Lawful Interception configuration which is often treated separately from the rest of config.

I think we'd have to extend the <hello> in some way to indicate which capabilities (which yang modules) apply to which datastores.

Jason

-----Original Message-----
From: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
Sent: Tuesday, March 03, 2015 5:12 AM
To: David Ball
Cc: Mahesh Jethanandani; rtg-yang-coord@ietf.org
Subject: Re: [Rtg-yang-coord] YANG leaf writing to running-datastore

On Tue, Mar 03, 2015 at 09:55:30AM +0000, David Ball wrote:
> Wouldn't that be best done with an RPC?
>

An ephemeral data store would provide a generic solution for this kind of problem. RPCs tend to be specific (or you invent a generic RPC that actually models an ephemeral data store).

/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/>

_______________________________________________
Rtg-yang-coord mailing list
Rtg-yang-coord@ietf.org
https://www.ietf.org/mailman/listinfo/rtg-yang-coord

v2.8.7 | Report a Bug | By Email