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

David Ball <daviball@cisco.com> Tue, 03 March 2015 09:55 UTC

Return-Path: <daviball@cisco.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 33FA91A1B12 for <rtg-yang-coord@ietfa.amsl.com>; Tue, 3 Mar 2015 01:55:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 buMSFEf6uteW for <rtg-yang-coord@ietfa.amsl.com>; Tue, 3 Mar 2015 01:55:53 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FA911A1B0D for <rtg-yang-coord@ietf.org>; Tue, 3 Mar 2015 01:55:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3498; q=dns/txt; s=iport; t=1425376553; x=1426586153; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=Va9qw092Qe+JnrRyNIe3EqU9Fa7qyVHi6f0UtElfctc=; b=L1ayQ54MhMnL8iNRl3SSKN0PibI4/ue9MW/ryJFMgGKRU5o7PpMwQFxa Ek1/Sz4k+eOixx8uqMDbGDjW6DKrdCwa1DWf9P8v4fdhSwFPYA1LGeV7T 7Wy7pV+GaN+JGndSYfEIW1ijRdRXrGO3i9mkB+dghIsuooeJbENE7ivRp 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A8BQBOhPVU/xbLJq1ag1RawTYBCYVwAoFwAQEBAQEBfIQQAQEEAQEBawoRCwQKCgkWDwkDAgECARUwBgEMBgIBAYgrDdZtAQEBAQEBAQMBAQEBAQEBARYEixKEdYQrAQSZQoZujHEjg24+MYECJIEdAQEB
X-IronPort-AV: E=Sophos;i="5.09,681,1418083200"; d="scan'208,217";a="367879360"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 03 Mar 2015 09:55:51 +0000
Received: from [10.63.23.55] (dhcp-ensft1-uk-vla370-10-63-23-55.cisco.com [10.63.23.55]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t239tpIc017551; Tue, 3 Mar 2015 09:55:51 GMT
Message-ID: <54F58512.2080900@cisco.com>
Date: Tue, 03 Mar 2015 09:55:30 +0000
From: David Ball <daviball@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Mahesh Jethanandani <mjethanandani@gmail.com>, "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>
References: <CAAchPMsaZJE=TRKaDyyA8JRyQ4dt5nptD8o0pkUK-1tfNT9vgA@mail.gmail.com>
In-Reply-To: <CAAchPMsaZJE=TRKaDyyA8JRyQ4dt5nptD8o0pkUK-1tfNT9vgA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090701020806040803070802"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/twKhismvC9OCDE3Jzsu-LEIVLvU>
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 09:55:55 -0000

Wouldn't that be best done with an RPC?


     David


On 02/03/15 22:42, Mahesh Jethanandani wrote:
> Is there a way to restrict having a leaf be written to running 
> datastore only? In other words, the leaf should never be written to 
> startup datastore. Along the lines of an ephemeral datastore, except 
> in this case it is a configuration parameter, and not something the 
> device has learnt.
>
> The particular case that comes to mind is putting an ethernet port in 
> loopback mode. This is done mainly to put the port in a debug mode, 
> and is meant to be temporary. But under no circumstance should it ever 
> be written to a saved datastore in a way that the port comes up in 
> loopback mode.
>
> If there is no such capability today, can we consider adding it?
>
>
> _______________________________________________
> Rtg-yang-coord mailing list
> Rtg-yang-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord

-- 
David Ball
<daviball@cisco.com>