Re: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure
"Acee Lindem (acee)" <acee@cisco.com> Tue, 12 July 2016 15:52 UTC
Return-Path: <acee@cisco.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 5288512D178 for <netmod@ietfa.amsl.com>; Tue, 12 Jul 2016 08:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 2Zz2Hx8ZATun for <netmod@ietfa.amsl.com>; Tue, 12 Jul 2016 08:52:29 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93FE212D181 for <netmod@ietf.org>; Tue, 12 Jul 2016 08:52:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10622; q=dns/txt; s=iport; t=1468338722; x=1469548322; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=4IXGojc1HkT3FdRiYuNS30LhYu2HRUadH83HKo16XHg=; b=ZxmB700a0OBXPnAfZJL0thZkA9VmhIKAqCu7jC+lTTk1QDRuQatNgbxU UIB8rWpztR4OxD4ExBWaN2qwf7Rz2jzljkmeeZycYOgynC7dleOn8w7Sn fIAQtHMFyoWWn4obrfGE7oxqxks4IJ5DjsPHJch99Tt+UhsDpdcl7Xmyo c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A/AgCWEYVX/4UNJK1cgz5WfAa5A4F5IoUsSgIcgRk4FAEBAQEBAQFlJ4RcAQEEAQEBIRE6GwIBCA4KAgImAgICJQsVEAIEARIbiA0IDrEIjwwBAQEBAQEBAQIBAQEBAQEBARoFgQGJdoRBF4JqgloFjgeLFAGGDohFgWqIB4U9hluJOAEeNoIJHIFMbogmfwEBAQ
X-IronPort-AV: E=Sophos;i="5.28,352,1464652800"; d="scan'208";a="296960804"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Jul 2016 15:52:01 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u6CFq0c1031564 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 12 Jul 2016 15:52:01 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 12 Jul 2016 11:51:59 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 12 Jul 2016 11:52:00 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Lou Berger <lberger@labn.net>, netmod WG <netmod@ietf.org>
Thread-Topic: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure
Thread-Index: AQHR25JaeXwJZYUBL0Wtuo0RKdx74KAVLrsA///EwgA=
Date: Tue, 12 Jul 2016 15:52:00 +0000
Message-ID: <D3AA86F2.6B108%acee@cisco.com>
References: <D3A935F0.6A4DC%acee@cisco.com> <02b5661f-22e0-6ccc-89d2-ef0370c4e87c@labn.net>
In-Reply-To: <02b5661f-22e0-6ccc-89d2-ef0370c4e87c@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <533F69499520664C8979089C5A5B9C4D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/xVu7CBahAgGC__4owApuwLrJse0>
Subject: Re: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure
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: Tue, 12 Jul 2016 15:52:32 -0000
Hi Lou, I’m not advocating this #2. If you are going to rely on the revised data stores to obtain the information, you should go all the way to #3. For example, based on the control-plane-protocols in routing-cfg, we have separate top level containers for config state. +--rw routing +--rw router-id? +--rw control-plane-protocols | +--rw control-plane-protocol* [type name] And: +— ro routing-state +--ro router-id? +--ro interfaces | +--ro interface* +--ro control-plane-protocols | +--ro control-plane-protocol* [type name] | +--ro type | +--ro name The control plane protocols augment these two lists separately. With #2, we leave the bifurcated structure and simply remove the data nodes that are not needed from the protocol state. Thanks, Acee On 7/12/16, 11:23 AM, "Lou Berger" <lberger@labn.net> wrote: >Acee, > > I personally was assuming we'd follow 3, but I'd like to understand >the implication of 2 as I'm not sure I really understand what you're >thinking here. Can you elaborate what you're thinking here? > >Thanks, > >Lou > >On 7/11/2016 12:36 PM, Acee Lindem (acee) wrote: >> While there are details to be worked out between the two data stores >> models (as indicated below), we now have implicit modeling of applied >> configuration. Existing models (both standard and draft) do not take >>this >> into consideration and, consequently, much of the state that is modeled >> explicitly represents the application configuration. For the RFC models, >> it probably doesn’t make much sense to redo them (unless they are being >> reworked for other reasons). This still leaves the existing WG draft >> models for which we have basically 3 options: >> >> 1. Do nothing - allow them proceed as they are with multiple ways of >> representing the applied configuration. This would provide visibility to >> the data independent of whether or not the device supported the revised >> data-stores supporting implicit retrieval of the applied configuration. >> 2. Prune out the redundant data nodes except those required as list >> keys, etc, since they can be obtained from the applied state data store. >> 3. #2 plus collapse the config (read-write) and system-state >> (read-only) into common containers. No more branching of >> <model-name>-config and <model-name>-state at the top level of the >>model. >> >> At I high-level, I feel these are the options. I’m not married to any >>one >> of these and the worse thing we could do is hold up progression of the >> existing YANG model drafts for another couple years while we debate the >> best course. Having said that, #3 is compelling since it will yield the >> most concise models and colocates the schema data nodes for any managed >> object. >> >> Thanks, >> Acee >> >> On 7/1/16, 12:36 PM, "netmod on behalf of Lou Berger" >> <netmod-bounces@ietf.org on behalf of lberger@labn.net> wrote: >> >>> All, >>> >>> It's time to make a consensus call on this topic, so that we can all >>>move >>> on to defining a solution and aligning modules under development. Based >>> on the feedback received and the overall discussions on the topic, we >>>see >>> that there is consensus to follow a datastore based approach to >>> supporting operational state, i.e., direction 'B'. >>> >>> We will be asking the authors of [4] and [5] to review their proposals >>> (individual drafts) in Berlin, as well as to highlight differences and >>> suggest ways that their work could be consolidated. Of course, others >>>may >>> also choose to submit their own proposals. Given the importance of this >>> work, we will be looking to have active discussion on the topic both in >>> Berlin and on the list, with an objective of having a draft ready for >>> considerations as a WG document by the November IETF. >>> >>> We have reviewed this decision with our AD and the NetConf chairs and >>> have agreed to begin this work in NetMod. We certainly expect to >>> coordinate the work with the NetConf WG and re-home work as/if needed. >>> >>> Finally, we'd also like to thank all those who have contributed to this >>> discussion to date, from problem identification to proposed solutions, >>> and we look forward to your continued efforts to publish a standard >>> solution. >>> >>> Lou (and Kent) >>> >>> >>> On 6/7/2016 10:19 AM, Lou Berger wrote: >>>> All, >>>> >>>> We want to provide an update based on the off line discussions >>>> related to OpState Solutions that we have been having and solicit >>>> input from the WG. >>>> >>>> All authors of current solution drafts [1,2,3] together with those >>>> who helped conduct the solutions analysis* were invited to the these >>>> discussions -- with the objective of coming up with a single >>>> consolidated proposal to bring to the WG. (I/Lou acted as facilitator >>>> as Kent and Juergen were and are involved with the technical details.) >>>> >>>> The discussions have yielded some results but, unfortunately, >>>> not a single consolidated proposal as hoped, but rather two >>>> alternate directions -- and clearly we need to choose one: >>>> >>>> 1) Adopt the conventions for representing state/config >>>> based on Section 6 of [1]. >>>> >>>> From a model definition perspective, these conventions >>>> impact every model and every model writer. >>>> >>>> 2) Model OpState using a revised logical datastore definition >>>> as introduced in [4] and also covered in [5]. There is >>>> also a variant of this that we believe doesn't significantly >>>> impact this choice. >>>> >>>> With this approach, model definitions need no explicit >>>> changes to support applied configuration. >>>> >>>> >From a technology/WG standpoint, we believe an approach >>>> that doesn't impact every model written (i.e., #2) is superior. >>>> The counterpoint to this is that the conventions based >>>> approach (i.e., #1) is available today and being followed in >>>> OpenConfig defined models. >>>> >>>> We would like to hear opinions on this from the WG before >>>> declaring one of the following as the WG direction: >>>> >>>> A) models that wish to support applied configuration MUST >>>> follow conventions based on [1] -- and the WG needs to >>>> formalize these conventions. >>>> or >>>> B) no explicit support is required for models to support >>>> applied configuration -- and that the WG needs to >>>> formalize an opstate solution based on the approach >>>> discussed in [4] and [5]. >>>> >>>> We intend to close on this choice before Berlin. >>>> >>>> Thank you, >>>> Lou (and co-chairs) >>>> >>>> [1] https://tools.ietf.org/html/draft-openconfig-netmod-opstate-01 >>>> [2] https://tools.ietf.org/html/draft-kwatsen-netmod-opstate-02 >>>> [3] https://tools.ietf.org/html/draft-wilton-netmod-opstate-yang-02 >>>> [4] >>>> https://tools.ietf.org/html/draft-schoenw-netmod-revised-datastores-00 >>>> [5] >>>> https://tools.ietf.org/html/draft-wilton-netmod-refined-datastores-00 >>>> * - Chris H. and Acee L. >>>> >>>> >>>> _______________________________________________ >>>> netmod mailing list >>>> netmod@ietf.org >>>> https://www.ietf.org/mailman/listinfo/netmod >>>> >>> >>> _______________________________________________ >>> netmod mailing list >>> netmod@ietf.org >>> https://www.ietf.org/mailman/listinfo/netmod >> _______________________________________________ >> netmod mailing list >> netmod@ietf.org >> https://www.ietf.org/mailman/listinfo/netmod > >
- [netmod] OpsState Direction Impact on Recommended… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Rob Shakir
- Re: [netmod] OpsState and Schema-Mount Robert Wilton
- Re: [netmod] OpsState and Schema-Mount Ladislav Lhotka
- Re: [netmod] OpsState and Schema-Mount Alex Campbell
- Re: [netmod] OpsState and Schema-Mount Ladislav Lhotka
- Re: [netmod] OpsState and Schema-Mount Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Juergen Schoenwaelder
- Re: [netmod] OpsState and Schema-Mount Kent Watsen
- Re: [netmod] OpsState and Schema-Mount Andy Bierman
- Re: [netmod] OpsState and Schema-Mount Kent Watsen
- Re: [netmod] OpsState and Schema-Mount Ladislav Lhotka
- Re: [netmod] OpsState and Schema-Mount Andy Bierman
- Re: [netmod] OpsState and Schema-Mount Juergen Schoenwaelder
- Re: [netmod] OpsState and Schema-Mount Robert Wilton
- Re: [netmod] OpsState and Schema-Mount Robert Wilton
- Re: [netmod] OpsState and Schema-Mount Ladislav Lhotka
- Re: [netmod] OpsState and Schema-Mount Kent Watsen
- Re: [netmod] OpsState and Schema-Mount Andy Bierman
- Re: [netmod] OpsState and Schema-Mount Andy Bierman
- Re: [netmod] OpsState and Schema-Mount Kent Watsen
- Re: [netmod] OpsState and Schema-Mount Acee Lindem (acee)
- Re: [netmod] OpsState and Schema-Mount Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Kent Watsen
- Re: [netmod] OpsState and Schema-Mount Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Juergen Schoenwaelder
- Re: [netmod] OpsState Direction Impact on Recomme… Kent Watsen
- Re: [netmod] OpsState and Schema-Mount Robert Wilton
- Re: [netmod] OpsState and Schema-Mount Ladislav Lhotka
- Re: [netmod] OpsState Direction Impact on Recomme… Balazs Lengyel
- [netmod] OpsState and Schema-Mount Balazs Lengyel
- Re: [netmod] OpsState Direction Impact on Recomme… Balazs Lengyel
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Kent Watsen
- Re: [netmod] OpsState Direction Impact on Recomme… Juergen Schoenwaelder
- [netmod] Corollary to [OpsState Direction Impact … Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Lou Berger
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Ladislav Lhotka
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Ladislav Lhotka
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Ladislav Lhotka
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Ladislav Lhotka
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Kent Watsen
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Mahesh Jethanandani
- Re: [netmod] OpsState Direction Impact on Recomme… Xufeng Liu
- Re: [netmod] OpsState Direction Impact on Recomme… thomas nadeau
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Kent Watsen
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Kent Watsen
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Kent Watsen
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Alex Campbell
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Rob Shakir
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Juergen Schoenwaelder
- Re: [netmod] OpsState Direction Impact on Recomme… Lou Berger
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Acee Lindem (acee)
- Re: [netmod] OpsState Direction Impact on Recomme… Lou Berger
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman
- Re: [netmod] OpsState Direction Impact on Recomme… Robert Wilton
- Re: [netmod] OpsState Direction Impact on Recomme… Andy Bierman