IETF Logo Mail Archive

Re: [netmod] OpsState and Schema-Mount

Ladislav Lhotka <lhotka@nic.cz> Wed, 03 August 2016 06:49 UTC

Return-Path: <lhotka@nic.cz>
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 3AB1512B05C for <netmod@ietfa.amsl.com>; Tue, 2 Aug 2016 23:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.287
X-Spam-Level:
X-Spam-Status: No, score=-8.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 9p5_zsCe0JA3 for <netmod@ietfa.amsl.com>; Tue, 2 Aug 2016 23:49:02 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 927BB12B020 for <netmod@ietf.org>; Tue, 2 Aug 2016 23:49:02 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:ffff:ffff:ffff:d] (unknown [IPv6:2001:1488:fffe:6:ffff:ffff:ffff:d]) by mail.nic.cz (Postfix) with ESMTPSA id 1833561846; Wed, 3 Aug 2016 08:49:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1470206940; bh=CbS3pjJBPU/e1sgbxyBIqP/ywPXM9ptKoH8ZJSqQaa4=; h=From:Date:To; b=S8G5FiPztIQqWwdiY9BTTUocZfWu5RuzV2Ywv4tB8i44Dfw4QKN1HUni7ryTATIgZ pRFXJUs737OmTdkbD4dFdcRHBRMtmHbXaO4c8s/zu2VG7AX+jpRZ1pG9+2Q6U5DEJH SMUCwApkOEQVRDZRJIgjU0B1zfDiJin1oWna7s9c=
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <68421198-703c-bb26-0fcc-f560e6fe108d@ericsson.com>
Date: Wed, 03 Aug 2016 08:49:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <100B5D71-C23E-4C72-9EA2-2DB6574DEB87@nic.cz>
References: <bed9398c-0e6a-450e-d2ac-b381b6bebf87@cisco.com> <5296754B-8178-4B1B-B4A6-FE228ABB8E7F@juniper.net> <9367f4b1-7814-e175-32e8-d518438b841d@cisco.com> <m24m79c1ja.fsf@birdie.labs.nic.cz> <D3BF8708.72620%acee@cisco.com> <552008CB-F216-4578-A709-AE0613C2EFB9@nic.cz> <12ed1a4d-44c5-9a51-b6d4-95e1620a24ee@cisco.com> <m260roedim.fsf@birdie.labs.nic.cz> <CABCOCHRF98sTa=MA1VTkZovOufL-=yQr9Gzy+ojnncjSfK1y0Q@mail.gmail.com> <e307c2fc-e621-b5c6-4fcc-67bbcdcb87b9@cisco.com> <20160729163220.GA3579@elstar.local> <68421198-703c-bb26-0fcc-f560e6fe108d@ericsson.com>
To: Balazs Lengyel <balazs.lengyel@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-Virus-Scanned: clamav-milter 0.98.7 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/yjA8iFtSjkm43QRD3eXL4XGnHI4>
Cc: netmod WG <netmod@ietf.org>
Subject: Re: [netmod] OpsState and Schema-Mount
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 03 Aug 2016 06:49:04 -0000

> On 02 Aug 2016, at 18:35, Balazs Lengyel <balazs.lengyel@ericsson.com> wrote:
> 
> Hello,
> If we allow foo and foo-state for opstate, mounting models atop such a multi rooted yang module will be fun.
> mount modB-config-part onto modA-config-part
> mount modB-state-part onto modA-state-part
> One mount becomes two and you have to maintain parallel mounts otherwise you are mounting half modules.

This is already happenning with augments. It means some work but nothing terribly complex.

> 
> Actually the problem is not caused by opstate, but rather by multi-rooted models. but avoiding foo-state would make life easier once more.

We already agreed that some items (such as RIBs) are "true" state which don't have direct counterparts in configuration. If we don't have foo-state, where are these supposed to be placed?

Lada 

> 
> regards Balazs
> 
> -- 
> Balazs Lengyel                       Ericsson Hungary Ltd.
> Senior Specialist
> Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com
> 

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C

v2.23.0 | Report a Bug | By Email