Re: [Inventory-yang] 答复: NIMBY WG charter

"Wubo (lana)" <lana.wubo@huawei.com> Thu, 30 March 2023 01:07 UTC

Return-Path: <lana.wubo@huawei.com>
X-Original-To: inventory-yang@ietfa.amsl.com
Delivered-To: inventory-yang@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F5EC15C2B8 for <inventory-yang@ietfa.amsl.com>; Wed, 29 Mar 2023 18:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIWC6PMe0GAs for <inventory-yang@ietfa.amsl.com>; Wed, 29 Mar 2023 18:07:33 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67FDAC1527A6 for <Inventory-yang@ietf.org>; Wed, 29 Mar 2023 18:06:53 -0700 (PDT)
Received: from lhrpeml100002.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Pn4wv22jrz6J74G for <Inventory-yang@ietf.org>; Thu, 30 Mar 2023 09:05:51 +0800 (CST)
Received: from canpemm100008.china.huawei.com (7.192.104.152) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 30 Mar 2023 02:06:27 +0100
Received: from kwepemi500014.china.huawei.com (7.221.188.232) by canpemm100008.china.huawei.com (7.192.104.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 30 Mar 2023 09:06:25 +0800
Received: from kwepemi500014.china.huawei.com ([7.221.188.232]) by kwepemi500014.china.huawei.com ([7.221.188.232]) with mapi id 15.01.2507.021; Thu, 30 Mar 2023 09:06:24 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: Camilo Cardona <camilo@gin.ntt.net>, "Marisol Palmero Amador (mpalmero)" <mpalmero@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Zhenghaomian <zhenghaomian@huawei.com>, Qin Wu <bill.wu@huawei.com>, "'Rob Wilton (rwilton)'" <rwilton@cisco.com>, 'Daniele Ceccarelli' <daniele.ietf@gmail.com>, "Inventory-yang@ietf.org" <Inventory-yang@ietf.org>
Thread-Topic: [Inventory-yang] 答复: NIMBY WG charter
Thread-Index: Adlioe6MUuOUmyCXR7Ge/ioOl/RMfA==
Date: Thu, 30 Mar 2023 01:06:24 +0000
Message-ID: <649b3e9a9058417c98bbfaaf684d41bc@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.153.153]
Content-Type: multipart/alternative; boundary="_000_649b3e9a9058417c98bbfaaf684d41bchuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/inventory-yang/FZGPj2rQABjx472HdeZ634Vt6N8>
Subject: Re: [Inventory-yang] 答复: NIMBY WG charter
X-BeenThere: inventory-yang@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inventory Management using YANG <inventory-yang.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/inventory-yang>, <mailto:inventory-yang-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/inventory-yang/>
List-Post: <mailto:inventory-yang@ietf.org>
List-Help: <mailto:inventory-yang-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/inventory-yang>, <mailto:inventory-yang-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2023 01:07:37 -0000

Hi Camilo,

Thanks for the reply.
My proposal is the definition of common license/entitlement can be used in both inventory model and asset model.

For the specific attributes definition, to me, it is not straightforward how the attributes mapping. It is helpful that draft-asset-lmo can add some mapping or  example to explain.
https://yangcatalog.org/api/services/tree/openconfig-system@2022-12-20.yang
The following is from openconfig-license module:
     +--rw license
     |  +--rw licenses
     |     +--rw license* [license-id]
     |        +--rw license-id    -> ../config/license-id
     |        +--rw config
     |        |  +--rw license-id?     string
     |        |  +--rw license-data?   union
     |        |  +--rw active?         boolean
     |        +--ro state
     |           +--ro license-id?        string
     |           +--ro license-data?      union
     |           +--ro active?            boolean
     |           +--ro description?       string
     |           +--ro issue-date?        uint64
     |           +--ro expiration-date?   uint64
     |           +--ro in-use?            boolean
     |           +--ro expired?           boolean
     |           +--ro valid?             boolean
And here is the reference of https://www.ietf.org/archive/id/draft-palmero-opsawg-dmlmo-09.html#name-entitlements

Thanks,
Bo
发件人: Camilo Cardona <camilo@gin.ntt.net>
发送时间: 2023年3月30日 8:51
收件人: Wubo (lana) <lana.wubo@huawei.com>; Marisol Palmero Amador (mpalmero) <mpalmero@cisco.com>; adrian@olddog.co.uk; Zhenghaomian <zhenghaomian@huawei.com>; Qin Wu <bill.wu@huawei.com>; 'Rob Wilton (rwilton)' <rwilton@cisco.com>; 'Daniele Ceccarelli' <daniele.ietf@gmail.com>; Inventory-yang@ietf.org
主题: Re: [Inventory-yang] 答复: NIMBY WG charter

Hello Bo,

Could  you please be specific in “openconfig-license defines the attributes quite different from draft-dmlmo”?

To me the openconfig-license model  looks simplen and it is a subset of what the dlmo entitlement model contains. Also, if there is something there that it does not cover, it can be adjusted.

Thanks,
Camilo

From: Inventory-yang <inventory-yang-bounces@ietf.org<mailto:inventory-yang-bounces@ietf.org>> on behalf of "Wubo (lana)" <lana.wubo=40huawei.com@dmarc.ietf.org<mailto:lana.wubo=40huawei.com@dmarc.ietf.org>>
Date: Thursday, 30 March 2023 at 09:46
To: "Marisol Palmero Amador (mpalmero)" <mpalmero=40cisco.com@dmarc.ietf.org<mailto:mpalmero=40cisco.com@dmarc.ietf.org>>, Camilo Cardona <camilo@gin.ntt.net<mailto:camilo@gin.ntt.net>>, "adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>" <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, 'Zhenghaomian' <zhenghaomian=40huawei.com@dmarc.ietf.org<mailto:zhenghaomian=40huawei.com@dmarc.ietf.org>>, 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org<mailto:bill.wu=40huawei.com@dmarc.ietf.org>>, "'Rob Wilton (rwilton)'" <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>, 'Daniele Ceccarelli' <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>, "Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>" <Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>>
Subject: Re: [Inventory-yang] 答复: NIMBY WG charter

Hi Marisol, all,

Regarding license management, I have 2 suggestions:
1)perhaps we can change to license/entitlement management?
2)  And should we define common license/entitlement attributes to be employed in both inventory management and asset management?

draft-dmlmo defines the license/entitlement management, and I'm wondering whether the license/entitlement is only used in asset management? For example, a multi-domain IP controller may collect license/entitlement information from different domain to verify configuration or identify faults.

Additionally, openconfig-license defines the attributes quite different from draft-dmlmo. When a domain controller aggregates license information in a domain, the definitions may be inconsistent.

Thanks,
Bo Wu

发件人: Inventory-yang <inventory-yang-bounces@ietf.org<mailto:inventory-yang-bounces@ietf.org>> 代表 Marisol Palmero Amador (mpalmero)
发送时间: 2023年3月29日 22:00
收件人: Camilo Cardona <camilo@gin.ntt.net<mailto:camilo@gin.ntt.net>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Zhenghaomian' <zhenghaomian=40huawei.com@dmarc.ietf.org<mailto:zhenghaomian=40huawei.com@dmarc.ietf.org>>; 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org<mailto:bill.wu=40huawei.com@dmarc.ietf.org>>; 'Rob Wilton (rwilton)' <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>; 'Daniele Ceccarelli' <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>; Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>
主题: Re: [Inventory-yang] 答复: NIMBY WG charter

I've added one paragraph in the doc, that clarifies the usage and extension for the use cases of inventory.
Please feel free to reworded/reduce it, or move it around.

“How the inventory information is used is outside the scope of NIMBY. As an example, DMLMO<https://datatracker.ietf.org/doc/draft-palmero-opsawg-dmlmo/> and in particular ietf-lmo-assets YANG module supports the integration and extension to be harmonized with the different inventory approaches on how to address inventory use cases. Note: The process is explained in detail in Appendix A: ietf-lmo-example-mapping-XXX YANG modules accommodate the ietf-lmo-assets YANG module to any other inventory which might be required in the future to be referenced.”

Many Thanks,

Marisol Palmero
M: +34.629.634.595


From: Inventory-yang <inventory-yang-bounces@ietf.org<mailto:inventory-yang-bounces@ietf.org>> on behalf of Camilo Cardona <camilo@gin.ntt.net<mailto:camilo@gin.ntt.net>>
Date: Wednesday, 29 March 2023 at 15:33
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk> <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, 'Zhenghaomian' <zhenghaomian=40huawei.com@dmarc.ietf.org<mailto:zhenghaomian=40huawei.com@dmarc.ietf.org>>, 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org<mailto:bill.wu=40huawei.com@dmarc.ietf.org>>, 'Rob Wilton (rwilton)' <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>, 'Daniele Ceccarelli' <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>, Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org> <Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>>
Subject: Re: [Inventory-yang] 答复: NIMBY WG charter
Hi Adrian,

Yes, all you say makes sense to me.

Thanks,
Camilo

From: Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Organisation: Old Dog Consulting
Reply to: <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Date: Wednesday, 29 March 2023 at 10:10
To: 'Camilo Cardona' <camilo@gin.ntt.net<mailto:camilo@gin.ntt.net>>, 'Zhenghaomian' <zhenghaomian=40huawei.com@dmarc.ietf.org<mailto:zhenghaomian=40huawei.com@dmarc.ietf.org>>, 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org<mailto:bill.wu=40huawei.com@dmarc.ietf.org>>, "'Rob Wilton (rwilton)'" <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>, 'Daniele Ceccarelli' <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>, <Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>>
Subject: RE: [Inventory-yang] 答复: NIMBY WG charter

Hi Camilo,

I think this is a good question.

Isn’t it the case that “inventory” is a step or stage in LMO? But isn’t it the case that Nimby is just focussed on the inventory, not how it is used, how elements are put into service or taken out of service?

So, of course, I would not want to banish LMO and have no one work on it. But it seems (to me) to be a lot of feature creep to include it in Nimby.

Perhaps the solution here is to explain (one line in the charter) the relevance and applicability of an inventory model to the LMO set of operations. That would make it clear how we expect the inventory model to be used, but not do the LMO work within Nimby.

--- Just my opinion.

A

From: Camilo Cardona <camilo@gin.ntt.net<mailto:camilo@gin.ntt.net>>
Sent: 29 March 2023 01:56
To: Zhenghaomian <zhenghaomian=40huawei.com@dmarc.ietf.org<mailto:zhenghaomian=40huawei.com@dmarc.ietf.org>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org<mailto:bill.wu=40huawei.com@dmarc.ietf.org>>; 'Rob Wilton (rwilton)' <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>; 'Daniele Ceccarelli' <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>; Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>
Subject: Re: [Inventory-yang] 答复: NIMBY WG charter

Hello all,

Thanks for all this work.

I might not be grasping all the concepts clearly, but I feel LMO is not clearly fitting the group description and we are just trying to push it in. Should we better keep it out?

Thanks,
Camilo C

From: Inventory-yang <inventory-yang-bounces@ietf.org<mailto:inventory-yang-bounces@ietf.org>> on behalf of Zhenghaomian <zhenghaomian=40huawei.com@dmarc.ietf.org<mailto:zhenghaomian=40huawei.com@dmarc.ietf.org>>
Date: Tuesday, 28 March 2023 at 11:20
To: "adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>" <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org<mailto:bill.wu=40huawei.com@dmarc.ietf.org>>, "'Rob Wilton (rwilton)'" <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>, 'Daniele Ceccarelli' <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>, "Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>" <Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>>
Subject: [Inventory-yang] 答复: NIMBY WG charter

Some editorial from my side as well, can be summarized:

1)      Instead of considering only ‘installed’, do we also cover what is ‘planned’?

2)      The boundary between software and hardware is getting blurred. It’s okay to cover both of them but clarifications are needed;

3)       Besides working on the inventory model itself, the mapping between these models and the current network topology would be greatly useful. Will the WG consider the work on this?

My 2 cents,
Haomian

发件人: Inventory-yang [mailto:inventory-yang-bounces@ietf.org] 代表 Adrian Farrel
发送时间: 2023年3月28日 8:49
收件人: 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org<mailto:bill.wu=40huawei.com@dmarc.ietf.org>>; 'Rob Wilton (rwilton)' <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>; 'Daniele Ceccarelli' <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>; Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>
主题: Re: [Inventory-yang] NIMBY WG charter

Hi,

Changes are just polishing words.

Here are updates. I think the main thing left to do is fill in the placeholder for LMO text. I have no clues about this, so someone else needs to start the text.

I hereby release the pen.

Cheers,
Adrian

From: Inventory-yang <inventory-yang-bounces@ietf.org<mailto:inventory-yang-bounces@ietf.org>> On Behalf Of Qin Wu
Sent: 27 March 2023 15:26
To: Rob Wilton (rwilton) <rwilton=40cisco.com@dmarc.ietf.org<mailto:rwilton=40cisco.com@dmarc.ietf.org>>; Daniele Ceccarelli <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>; Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>
Subject: Re: [Inventory-yang] NIMBY WG charter

Hi, Rob:
Thanks Med, Oscar, Diego, Daniele, Adrian, Sergio, Victor, Italo, Marisol, Yuchaode, BoWu, many other team members.
We have a second side meeting to go through NIMBY WG Charter, we have got all main proponents of each drafts  to review charter proposal paragraph by paragraph,
Unfortunately due to time limitation, we only complete review the first four paragraphs, See attached,
We will continue to polish the charter proposal. Marisol agreed to add additional pieces related to dmlmo which will add another layer on top of inventory model.

Talking with many proponents,  we can continue to discuss on this thread, but we think it will be also great we can Strike while the iron is hot and
have the third side meeting inventory yang during IETF week to reach agreement on the scope of inventory management.


-Qin (on behalf of the team)
发件人: Inventory-yang [mailto:inventory-yang-bounces@ietf.org] 代表 Rob Wilton (rwilton)
发送时间: 2023年3月27日 18:21
收件人: Daniele Ceccarelli <daniele.ietf@gmail.com<mailto:daniele.ietf@gmail.com>>; Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>
主题: Re: [Inventory-yang] NIMBY WG charter

Hi all,

Adrian, Daniele, thanks for putting this together so quickly. Sorry but I can’t make today’s follow up meeting as I have a clash, but some quick thoughts/comments in case you discuss this further.

My main comment is that I think that the charter should be somewhat open as to whether this new WG directly progresses the technology specific augmentation drafts (with agreement of the technology specific WGs/Areas), or whether the drafts are taken to the technology specific WGs.

I hope that this will help mitigate the potential question of whether why, if the WG is only producing one document, a whole new WG is needed.

But really, I think that you had me sold with just the name. :-)

Thanks,
Rob


From: Inventory-yang <inventory-yang-bounces@ietf.org<mailto:inventory-yang-bounces@ietf.org>> On Behalf Of Daniele Ceccarelli
Sent: 27 March 2023 17:02
To: Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org>
Subject: [Inventory-yang] NIMBY WG charter

Hi everyone,

as promised , here is a WG charter proposal that Adrian and I have put together.

We might use the slot later this afternoon to discuss about it.

Please note that in the milestones we identified a single draft but this doesn't mean that we are committing to have everything in a single document, if along the road we find that splitting the work in more than one document is needed, we might do so.

Thanks
Adrian & Daniele
-- Inventory-yang mailing list Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org> https://www.ietf.org/mailman/listinfo/inventory-yang
-- Inventory-yang mailing list Inventory-yang@ietf.org<mailto:Inventory-yang@ietf.org> https://www.ietf.org/mailman/listinfo/inventory-yang