Re: [netmod] Inventory YANG model (entity-MIB)

"Susan Hares" <shares@ndzh.com> Fri, 06 March 2015 11:53 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90CB61ACDB6 for <netmod@ietfa.amsl.com>; Fri, 6 Mar 2015 03:53:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001] autolearn=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 Bg6l6kutZei2 for <netmod@ietfa.amsl.com>; Fri, 6 Mar 2015 03:53:44 -0800 (PST)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id D0EB81ACDAD for <netmod@ietf.org>; Fri, 6 Mar 2015 03:53:42 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=74.43.47.92;
From: Susan Hares <shares@ndzh.com>
To: 'Juergen Schoenwaelder' <j.schoenwaelder@jacobs-university.de>, 'Benoit Claise' <bclaise@cisco.com>
References: <54F985E2.6020304@cisco.com> <20150306110536.GA73575@elstar.local>
In-Reply-To: <20150306110536.GA73575@elstar.local>
Date: Fri, 06 Mar 2015 06:53:37 -0500
Message-ID: <0e7201d05804$2ef8dfc0$8cea9f40$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQC/r0YkLKSuBfrYEPhLebwn/CNVWgGB/IaPnySUmXA=
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/0uXTtf4EHLyO_eWbBvdZNqnLZqw>
Cc: draft-dong-i2rs-network-inventory@tools.ietf.org, i2rs-chairs@tools.ietf.org, 'NETMOD Working Group' <netmod@ietf.org>
Subject: Re: [netmod] Inventory YANG model (entity-MIB)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 11:53:46 -0000

Juergen:

<chair hat on> 
Thank you for your input on location of work.  I will discuss this with Alia
and Jeff this morning.  If you do have input where a yang module updating
the Entity-MIB might be worked on, please drop me a note. 
<chair hat off>

Jie Dong, I, and other members of the I2RS topology task simply want to get
the inventory information added to some yang model.  In our multiple vendor
(Cisco, Ericsson, Juniper, Huawei, packet-design),  many people felt it was
reasonable.  

As technical advisor, do you know if the Entity-MIB work scheduled for
upgrading to a yang module?  If not, is there a working group where we could
suggest an equivalent model. 
  
As to config true,  this Data model seems IMHO (jie may correct me) one of
the I2RS model that wants to have ephemeral state but also change things in
the data store.  

<chair hat on> 
I asked the design teams to focus on the functions they desired in the
datastore so that we could see more test cases.  I hope you as the I2RS
technical advisor will help us dive into protocol issues with specific
models. 
<chair hat off> 


 
-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: Friday, March 06, 2015 6:06 AM
To: Benoit Claise
Cc: NETMOD Working Group; draft-dong-i2rs-network-inventory@tools.ietf.org;
i2rs-chairs@tools.ietf.org
Subject: Re: [netmod] Inventory YANG model (entity-MIB)

On Fri, Mar 06, 2015 at 11:48:02AM +0100, Benoit Claise wrote:
> Dear all,
> 
> The I2RS interim meeting yesterday focused on topology.
> Let me cut/paste a high level slide, with pointers to the relevant drafts.
> 
> 
> If interested, the meeting minutes are at 
> http://etherpad.tools.ietf.org:9000/p/i2rs-interim-march-5-2015-v-blue
> sheets
> 
> Part of the inventory draft
> (http://datatracker.ietf.org/doc/draft-dong-i2rs-network-inventory/)
> discussion, the overlap with the ENTITY-MIB RFC 6933 was discussed 
> (and RFC 7223 btw).
> 
> 
> The message was that I2RS should not re-invent something similar to 
> the ENTITY-MIB So, are you aware of any initiatives to "YANGify" the 
> ENTITY-MIB?
> It's true that there is a way to translate MIB into YANG with RFC 6643. 
> This could be a good start. However, I wonder if a hand-written YANG 
> model that closely follows the entPhysical would not be more beneficial.
> Is this something we should take on board in NETMOD?
> 
> What do you think?
> 
> Note: As commented by the I2RS people, indexing is appropriate in the 
> MIB module for its original purpose, but may not be for the topology.
> I'm not sure we want to change the indexing just for the topology, but 
> the integration within the topology draft should be thought of.
>

My first question is (perhaps not surprising) whether inventory falls
into the I2RS charter, I2RS = interface to the routing system. That
said, RFC 6643 gives you a read-only translation. There are not many
read-write objects in the ENTITY-MIB so perhaps this is good enough
for now. I guess it would help what I2RS needs to know in order to
make the interface to the routing system work.

Anyway, if YANG models overlapping the ENTITY-MIB are done, they they
should at least allow implementation of both in a predictable manner.
Looking at draft-dong-i2rs-network-inventory-00, it seems the whole
interface list is already covered by RFC 7223 and interfaces should be
references not repeated (this is what the ENTITY-MIB does). So what is
left is essentially a (not yet hierarchy) of 'cards' that seem to more
or less match the entPhysicalTable of the ENTITY-MIB (but then the
ENTITY-MIB has a more flexible model that distinguishes between
different kind of hardware components). I also notice that the model
in draft-dong-i2rs-network-inventory-00 is config true - so I am not
sure how this is supposed to use. Is the idea that this model is an
interface to an inventory database where I configure what I have
instead of a model sitting on a device where I can query what the
device actually has?

/js

PS: I personally would have preferred if generic topology and perhaps
    inventory would have split off into a short-lived targeted WG
    instead of doing all of this in I2RS but it seems leadership has
    already decided that I2RS is the home for all of this.

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