Re: [netmod] FW: a question about ietf-hardware yang module

Martin Bjorklund <mbj@tail-f.com> Tue, 25 June 2019 07:13 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 7BAEE12009E for <netmod@ietfa.amsl.com>; Tue, 25 Jun 2019 00:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 qAgVO1xwewXX for <netmod@ietfa.amsl.com>; Tue, 25 Jun 2019 00:13:50 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5E49C120077 for <netmod@ietf.org>; Tue, 25 Jun 2019 00:13:50 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 2580C1AE02F0; Tue, 25 Jun 2019 09:13:48 +0200 (CEST)
Date: Tue, 25 Jun 2019 09:13:51 +0200 (CEST)
Message-Id: <20190625.091351.1767393704172151256.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: andy@yumaworks.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20190625055123.ia2k5vv5tfhzqqs2@anna.jacobs.jacobs-university.de>
References: <5756FB984666AD4BB8E1D63E2E3AA3D001ED25CD@dggemm513-mbx.china.huawei.com> <CABCOCHTZzGycEYDnaWk0aUgGQwnD-joRcGjGoESrg-iCJ_9r0w@mail.gmail.com> <20190625055123.ia2k5vv5tfhzqqs2@anna.jacobs.jacobs-university.de>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/XZ_xQwJIpogbN6tuWnBfwDg_0Nk>
Subject: Re: [netmod] FW: a question about ietf-hardware yang module
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, 25 Jun 2019 07:13:52 -0000

Hi,

I don't understand what is unclear about the current descriptions.  Is
it the relations to the MIB objects that are unclear or is it the
descriptions in the YANG module?  The original question was:

  My question is whether only configuration change of hardware
  component will cause the update of /hardware/last-change?

The answer is clearly "no", since /hardware/last-change says:

        "The time the '/hardware/component' list changed in the
         operational state.";

and this list has e.g.:

           When the server detects a new hardware component, it
           initializes a list entry in the operational state.

So it is clear that if a hardware component is added (not a
configuration change) this list is changed, and last-change is
updated.


/martin


Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Mon, Jun 24, 2019 at 07:14:18PM -0700, Andy Bierman wrote:
> > On Mon, Jun 24, 2019 at 6:59 PM Fengchong (frank) <
> > frank.fengchong@huawei.com> wrote:
> > 
> > > Andy,
> > >
> > >     Can you clarify this question?
> > >
> > >
> > >
> > 
> > Since state-last-changed seems to cover state data changing, last-change
> > seems to apply to
> > the operational value of the config=true nodes in the /hardware/component
> > subtree
> > 
> > Andy
> >
> 
> It could be that the intention was that ietf-hardware:last-change
> matches ENTITY-MIB:entLastChangeTime, which has this description (see
> RFC 6933):
> 
>             "The value of sysUpTime at the time a conceptual row is
>             created, modified, or deleted in any of these tables:
>                     - entPhysicalTable
>                     - entLogicalTable
>                     - entLPMappingTable
>                     - entAliasMappingTable
>                     - entPhysicalContainsTable
>             "
> 
> If so, ietf-hardware:last-change should change whenever the an element
> in the hardware/component list changes, e.g., pluggable hardware is
> added or removed.
> 
> If this interpretation is correct, then an entry in the table "YANG
> Data Nodes and Related ENTITY-MIB Objects" is missing. Anyway, the
> description of ietf-hardware:last-change is obviously not precise
> enough and this thread should perhaps lead to an errata if we find
> agreement what the intention here was.
> 
> /js
> 
> -- 
> 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 mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>