Re: [netmod] instance data new backward compatibility text
Martin Bjorklund <mbj@tail-f.com> Tue, 26 March 2019 10:53 UTC
Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id BD3BD1202BC
for <netmod@ietfa.amsl.com>; Tue, 26 Mar 2019 03:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
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 lKvRBYMCiTsm for <netmod@ietfa.amsl.com>;
Tue, 26 Mar 2019 03:53:08 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45])
by ietfa.amsl.com (Postfix) with ESMTP id C688A1202A4
for <netmod@ietf.org>; Tue, 26 Mar 2019 03:53:07 -0700 (PDT)
Received: from localhost (dhcp-97ad.meeting.ietf.org [31.133.151.173])
by mail.tail-f.com (Postfix) with ESMTPSA id 8FB581AE02BD;
Tue, 26 Mar 2019 11:53:05 +0100 (CET)
Date: Tue, 26 Mar 2019 11:53:03 +0100 (CET)
Message-Id: <20190326.115303.1797338774709462584.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: balazs.lengyel@ericsson.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20190325232240.ttcddrly3gnmldod@anna.jacobs.jacobs-university.de>
References: <20190325221609.hiuif4fafhheynok@anna.jacobs.jacobs-university.de>
<8cc2ecb9-53b8-36dc-97d9-e7ce92a27d5c@ericsson.com>
<20190325232240.ttcddrly3gnmldod@anna.jacobs.jacobs-university.de>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/WWG03nwXAaIJu5g5mVusghKdMYk>
Subject: Re: [netmod] instance data new backward compatibility text
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>,
<mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>,
<mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2019 10:53:11 -0000
Hi I agree with Juergen. I think section 6 should be removed. This document should specify the document format (which it does), but it shouldn't specify specific rules for the different use cases. /martin Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote: > Your rules are use case specific and I am not convinced they are > applying to all use cases. It should be a perfectly valid use case to > store snapshots of <running> in instance data files. Your rules do not > make sense here and I do not think this is a valid usage of the SHOULD > mechanism. > > /js > > On Mon, Mar 25, 2019 at 11:01:52PM +0000, Balázs Lengyel wrote: > > Hello Jurgen, > > > > I don't think these rules are Ericsson specific. In some of our most > > important use-cases (UC1, UC2, UC6) changing the keys would lead to > > problems. > > > > UC1: If you document server capabilities using ietf-yang-library the name > > of the module sets may be/should be meaningful. It might be used by the > > NMS to compare the capabilities of different versions of the YANG server; > > changing keys without a reason will mislead the NMS into assuming the > > server capabilities changed.. > > > > UC2: Preloading default configuration data. E.g. If you change the > > identifier of NACM ruleset, then during upgrade it might be loaded again > > as the server can not detect, that this is the same ruleset that is > > already in the datastore. > > > > UC6: Storing diagnostics data. If you change the keys used in diagnostic > > data, comparing values before and after the key change will be difficult. > > > > And yes as we were using instance data for the last then years, we did > > have a lot of problem with people changing the keys without considering > > compatibility effects. > > I agree that this is not always a problem, so I only used SHOULD (and not > > MUST) in the text. > > > > regards Balazs > > > > > > On 2019. 03. 25. 23:16, Juergen Schoenwaelder wrote: > > > > On Mon, Mar 25, 2019 at 09:59:43PM +0000, Balázs Lengyel wrote: > > > > Hello Jurgen, > > > > You are right that this is important mostly for instance data prepared as a > > design/implementation activity; while not relevant for data coming from the > > node. > > I will add it. > > > > However in the first case it is vital! > > > > For config files, and also for file documenting server capabilities we have > > had MANY problems with people changing the key values/identities of list > > entries. > > They think it is a nice idea to provide better, more meaningful key values; > > however the NMS designers use these key values to detect changes; also > > during an upgrade process if a default configuration file is loaded again > > with slightly changed key values, then e.g. access control rules become > > duplicated. > > > > > > The conditions under which it is meaningful to change keys and when it > > is not appropriate are very application specific. You may have > > specific use cases at Ericsson where you want internal regulations but > > I do not think this leads to meaningful rules outside your specific > > application scenario. > > > > /js > > > > > > -- > > Balazs Lengyel Ericsson Hungary Ltd. > > Senior Specialist > > Mobile: +36-70-330-7909 email: [1]Balazs.Lengyel@ericsson..com > > > > References > > > > Visible links > > 1. mailto:Balazs.Lengyel@ericsson.com > > > > > _______________________________________________ > > netmod mailing list > > netmod@ietf.org > > https://www.ietf.org/mailman/listinfo/netmod > > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <https://www.jacobs-university.de/> >
- [netmod] instance data new backward compatibility… Juergen Schoenwaelder
- Re: [netmod] instance data new backward compatibi… Balázs Lengyel
- Re: [netmod] instance data new backward compatibi… Juergen Schoenwaelder
- Re: [netmod] instance data new backward compatibi… Balázs Lengyel
- Re: [netmod] instance data new backward compatibi… Juergen Schoenwaelder
- Re: [netmod] instance data new backward compatibi… Martin Bjorklund