HI Fengchong,
Thanks for your email. Related to the ietf-lmo-incident-management YANG module<mailto:ietf-lmo-incident-managem...@2022-09-20.yang> The YANG module doesn’t contain and doesn’t have the objective to include the insight of the incident: if any negative impact is involved on the incident, ietf-lmo-incident-management is not covering such use case. The main objective for ietf-lmo-incident-management: A user might decide to record and report any incident faced, related to asset, entitlement or feature (please note that we might need to include entitlement and feature to the “Incident class” definition in the draft, only asset is mentioned) Mainly the module covers incident management attributes to handle incidents, but doesn’t go to the analysis of those incidents. It is a good catch though as the incident might be raised automatically. In our case, the module doesn’t go to details of the specific alarm raised(if any) related to the incident, or the threshold crossed that might raise that alarm/incident. ietf-lmo-incident-management should cover the use case when the incident occurs a ticket much be dispatched. Hth, Marisol From: Inventory-yang <inventory-yang-boun...@ietf.org> on behalf of Fengchong (frank) <frank.fengchong=40huawei....@dmarc.ietf.org> Date: Tuesday, 21 March 2023 at 03:19 To: Marisol Palmero Amador (mpalmero) <mpalmero=40cisco....@dmarc.ietf.org>, Tianran Zhou <zhoutianran=40huawei....@dmarc.ietf.org>, opsawg@ietf.org <opsawg@ietf.org>, Rob Wilton (rwilton) <rwil...@cisco.com> Cc: Sudhendu Kumar <sudhendu.kumar....@gmail.com>, Shwetha Bhandari <shwetha.bhand...@thoughtspot.com>, Jan Lindblad (jlindbla) <jlind...@cisco.com>, inventory-y...@ietf.org <inventory-y...@ietf.org> Subject: [Inventory-yang] 答复: New Version Notification for draft-palmero-opsawg-dmlmo-09.txt Hi Marisol, I’m the author of draft-feng-opsawg-incident-management, in this document, alarms, metrics and some trace information can be aggregated into an incident, incident often have negative impact on network services. I have some questions about the concept of incident in your document. 1. Does the incident contains the negative impact on network services? I see network service are one type of asset. 2. Is alarm also an incident? Or only root cause problem is an incident? 3. Metrics break the threshold, is this situation treated as incident? 4. If an incident occurs, a ticket must be dispatched? 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 Marisol Palmero Amador (mpalmero) 发送时间: 2023年3月21日 8:36 收件人: Tianran Zhou <zhoutianran=40huawei....@dmarc.ietf.org>; opsawg@ietf.org; Rob Wilton (rwilton) <rwil...@cisco.com> 抄送: Sudhendu Kumar <sudhendu.kumar....@gmail.com>; Shwetha Bhandari <shwetha.bhand...@thoughtspot.com>; Jan Lindblad (jlindbla) <jlind...@cisco.com>; inventory-y...@ietf.org 主题: Re: [OPSAWG] New Version Notification for draft-palmero-opsawg-dmlmo-09.txt Many thanks for your email, Just to clarify our approach to “dis-engage” from the inventory drafts/RFC’s discussions: * The asset module, doesn’t contain any more “inventory” on the name of the module, * it was reduced drastically to consume from any existing inventory RFC/draft reference. * Asset module cannot be eliminated from the DMLMO draft because it needs still to host the link to “entitlement” and “feature/usage”. * Asset represents refers to hardware, software, applications, or services. From my research, inventory related drafts are dedicated to hardware or software, independently, what means that we have to relay on the asset module to be able to make that reference. The mentioned Incident-management draft has been recently submitted; from my reading the approach is different from the incident-management module in DMLMO: https://datatracker.ietf.org/doc/draft-feng-opsawg-incident-management/ v00 released March-13 2023 In DMLMO, incident management module includes the incident management attributes to handle incidents. Where incident refers to the record and report of any problem the user has faced with the asset, feature or entitlement. Many Thanks, Marisol Palmero From: Tianran Zhou <zhoutianran=40huawei....@dmarc.ietf.org<mailto:zhoutianran=40huawei....@dmarc.ietf.org>> Date: Thursday, 16 March 2023 at 07:43 To: Marisol Palmero Amador (mpalmero) <mpalm...@cisco.com<mailto:mpalm...@cisco.com>>, opsawg@ietf.org<mailto:opsawg@ietf.org> <opsawg@ietf.org<mailto:opsawg@ietf.org>>, Rob Wilton (rwilton) <rwil...@cisco.com<mailto:rwil...@cisco.com>> Cc: Camilo Cardona <juancamilo.card...@imdea.org<mailto:juancamilo.card...@imdea.org>>, Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>>, Diego R. Lopez <diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com>>, Shwetha Bhandari <shwetha.bhand...@thoughtspot.com<mailto:shwetha.bhand...@thoughtspot.com>>, Sudhendu Kumar <sudhendu.kumar....@gmail.com<mailto:sudhendu.kumar....@gmail.com>>, Eric Vyncke (evyncke) <evyn...@cisco.com<mailto:evyn...@cisco.com>>, inventory-y...@ietf.org<mailto:inventory-y...@ietf.org> <inventory-y...@ietf.org<mailto:inventory-y...@ietf.org>>, Jan Lindblad (jlindbla) <jlind...@cisco.com<mailto:jlind...@cisco.com>> Subject: RE: New Version Notification for draft-palmero-opsawg-dmlmo-09.txt Hi Marisol, Thanks very much for this revision. It’s good to see you think about the adaption to other inventory models. Here I would like to raise my proposal on the inventory collaboration. I think this draft covers too many things. My understanding, according to figure 1, the focus should be on Entitlements and Usage. The Asset has many overlap with the inventory model. I am thinking if you can just reuse the ietf inventory model, i.e., not to define a new asset. So that, all the ietf models could build a big picture. The ietf inventory model can deal with the mapping to openconfig model. So this draft can also reduce the mapping work. I see there is a new specific Incident draft “draft-feng-opsawg-incident-management”. Maybe you can also reuse this. What’s your thoughts? Best, Tianran From: Inventory-yang [mailto:inventory-yang-boun...@ietf.org] On Behalf Of Marisol Palmero Amador (mpalmero) Sent: Wednesday, January 18, 2023 1:58 AM To: opsawg@ietf.org<mailto:opsawg@ietf.org>; Rob Wilton (rwilton) <rwil...@cisco.com<mailto:rwil...@cisco.com>> Cc: Camilo Cardona <juancamilo.card...@imdea.org<mailto:juancamilo.card...@imdea.org>>; Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>>; Diego R. Lopez <diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com>>; Shwetha Bhandari <shwetha.bhand...@thoughtspot.com<mailto:shwetha.bhand...@thoughtspot.com>>; Sudhendu Kumar <sudhendu.kumar....@gmail.com<mailto:sudhendu.kumar....@gmail.com>>; Eric Vyncke (evyncke) <evyn...@cisco.com<mailto:evyn...@cisco.com>>; inventory-y...@ietf.org<mailto:inventory-y...@ietf.org>; Jan Lindblad (jlindbla) <jlind...@cisco.com<mailto:jlind...@cisco.com>> Subject: [Inventory-yang] FW: New Version Notification for draft-palmero-opsawg-dmlmo-09.txt Dear OPSA WG/AD, We've just posted a new version, v09, for DMLMO, data model for lifecycle management and operations: https://www.ietf.org/archive/id/draft-palmero-opsawg-dmlmo-09.txt Where we have been addressing the comments given during OPSA WG meeting and inventory side meeting, part of IETF #115. DMLMO version 09 is independent from inventory, where the DMLMO YANG modules, as specific ietf-lmo-assets YANG module, can consume from any other specific inventory YANG module(s). An example is given in Appendix A. version 09 * Rename "license" to "entitlement". * renamed ietf-lmo-assets-inventory to ietf-lmo-assets. * ietf-lmo-assets provides capability of integration and extention for a different approach on how to address inventory use cases. Process is explained in the Appendix A. * ietf-lmo-example-mapping-XXX YANG modules accommodates the ietf-lmo-assets YANG module to any other inventory which will be required in the future to be referenced. We greatly appreciate your thoughts, comments and evaluation. Many thanks, Marisol Palmero From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> Date: Tuesday, 17 January 2023 at 18:28 To: Camilo Cardona <cam...@ntt.net<mailto:cam...@ntt.net>>, Diego Lopez <diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com>>, Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>>, Marisol Palmero Amador (mpalmero) <mpalm...@cisco.com<mailto:mpalm...@cisco.com>>, Shwetha Bhandari <shwetha.bhand...@thoughtspot.com<mailto:shwetha.bhand...@thoughtspot.com>>, Sudhendu Kumar <skuma...@ncsu.edu<mailto:skuma...@ncsu.edu>> Subject: New Version Notification for draft-palmero-opsawg-dmlmo-09.txt A new version of I-D, draft-palmero-opsawg-dmlmo-09.txt has been successfully submitted by Marisol Palmero and posted to the IETF repository. Name: draft-palmero-opsawg-dmlmo Revision: 09 Title: Data Model for Lifecycle Management and Operations Document date: 2023-01-17 Group: Individual Submission Pages: 80 URL: https://www.ietf.org/archive/id/draft-palmero-opsawg-dmlmo-09.txt Status: https://datatracker.ietf.org/doc/draft-palmero-opsawg-dmlmo/ Htmlized: https://datatracker.ietf.org/doc/html/draft-palmero-opsawg-dmlmo Diff: https://author-tools.ietf.org/iddiff?url2=draft-palmero-opsawg-dmlmo-09 Abstract: This document motivates and specifies a data model for lifecycle management and operations. It describes the motivation and requirements to collect asset-centric metrics including but not limited to asset adoption and usability, licensing, supported features and capabilities, enabled features and capabilities, etc.; with the primary objective to measure and improve the overall user experience along the lifecycle journey, from technical requirements and technology selection through advocacy and renewal, including the end of life of an asset. The IETF Secretariat
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
