Hi Bo,
Answering your questions here:
1)
Identities for offer-type-t can be extended, those might not be limited to the
identities listed in the draft.
Please recall that assets related to hardware, software, applications, or
services. An asset can be physical or virtual.
Note:
There is a good catch on your question! we will replace license terms by
entitlement terms as we did for the other YANG data modules for offer-type-t
offer-type-t relates to assets or features, as entitlements could be related to
both, we will modify this on the description in our next release
2)
An entitlement is a class of LMO, because it is part of the Lifecycle
Management and Operations of the asset.
If needed more clarification in the descriptions, we will add into it, also in
the next release.
I hope it clarifies, please let me know if this is not the case.
Many thanks
Marisol Palmero
From: Inventory-yang <inventory-yang-boun...@ietf.org> on behalf of Wubo (lana)
<lana.wubo=40huawei....@dmarc.ietf.org>
Date: Thursday, 23 February 2023 at 13:18
To: Marisol Palmero Amador (mpalmero) <mpalmero=40cisco....@dmarc.ietf.org>,
Wubo (lana) <lana.wubo=40huawei....@dmarc.ietf.org>, opsawg@ietf.org
<opsawg@ietf.org>, inventory-y...@ietf.org <inventory-y...@ietf.org>
Subject: Re: [Inventory-yang] New Version Notification for
draft-wzwb-opsawg-network-inventory-management-01.txt
Hi Marisol,
Thanks for your question. The note is about the questions on the definition of
entitlement/license in the asset YANG model.
1)It seems the following is related to the attributes of the inventory, such as
whether the license is applied to hardware, or deployed in the enterprise
sites, etc..Correct?
identity offer-type-t {
description
"License Offer Type, part of the plan to generate revenue
for specific asset";
}
identity perpetual-software {
base offer-type-t;
description
"Perpetual softwar gives the user the right to use the
program indefinitely";
}
identity standalone-hardware {
base offer-type-t;
description
"Standalone hardware is able to function independently
of other hardware";
}
identity on-premise-software-subscription {
base offer-type-t;
description
"On-Premise software subscription, relates to a temporary
on-prem licencing model, allowing users to pay a per user
fee";
}
identity cloud-software-saas-subscription {
base offer-type-t;
description
"Cloud Software (SaaS) subscription is a service busines
model where the user is entitled to use the cloud software
for a specific time period";
}
identity third-party-software {
base offer-type-t;
description
"It includes licenses, entitlements, agreements, obligations
or other commitment under which the user can use the asset
not directly sold by the manufacturer";
}
identity flex-cloud-prem-subscription {
base offer-type-t;
description
"Flex Cloud-Prem subscription allows software vendors to
limit the number of entitlements for the use of the specific
asset";
}
2) :The draft says the focus is on asset-centric lifecycle management and refer
it as Lifecycle Management and Operations (LMO). Could you elaborate on why an
entitlement is also a class of lmo?
A entitlement is a class of lmo that represents how the asset(s) or feature(s)
can be leveraged and what is required in cases the asset(s) or feature(s) are
changed
Thanks,
Bo
From: Inventory-yang [mailto:inventory-yang-boun...@ietf.org] On Behalf Of
Marisol Palmero Amador (mpalmero)
Sent: Friday, February 17, 2023 6:53 PM
To: Wubo (lana) <lana.wubo=40huawei....@dmarc.ietf.org>; opsawg@ietf.org;
inventory-y...@ietf.org
Subject: Re: [Inventory-yang] New Version Notification for
draft-wzwb-opsawg-network-inventory-management-01.txt
Hi Bo,
Could you please elaborate on your note?
>From your email:
Regarding licenses (or entitlements in draft-palmero-opsawg-dmlmo-09), some
licenses may affect the functions of physical components or software
components, though having removed from the current model, but we feel further
discussion is needed.
Please let me know how I could help to clarify or facilitate the discussion,
Many thanks,
Marisol
Marisol Palmero
CCIE #5122 | Technical Leader EMEA | Cisco CPX TEAO | P: +34.91.201.2643 | M:
+34.629.634.595
From: Inventory-yang
<inventory-yang-boun...@ietf.org<mailto:inventory-yang-boun...@ietf.org>> on
behalf of Wubo (lana)
<lana.wubo=40huawei....@dmarc.ietf.org<mailto:lana.wubo=40huawei....@dmarc.ietf.org>>
Date: Thursday, 16 February 2023 at 11:02
To: opsawg@ietf.org<mailto:opsawg@ietf.org>
<opsawg@ietf.org<mailto:opsawg@ietf.org>>,
inventory-y...@ietf.org<mailto:inventory-y...@ietf.org>
<inventory-y...@ietf.org<mailto:inventory-y...@ietf.org>>
Subject: Re: [Inventory-yang] New Version Notification for
draft-wzwb-opsawg-network-inventory-management-01.txt
Dear Opsawg, inventory colleges,
Based on the review comments from Marisol and authors of
draft-ietf-ccamp-network-inventory-yang, we update the network inventory draft.
Compared with the network hardware inventory in CCAMP, this model has following
consideration:
1) Augment RFC 8345, so that the logical L2 or L3 or TE network topology can
have mapping association with underlying physical infrastructure inventory.
Therefore, a new " network-inventory" network type has been defined.
2) More device and device component types are supported, such as device
software component, virtual network devices and network endpoint devices.
Regarding licenses (or entitlements in draft-palmero-opsawg-dmlmo-09), some
licenses may affect the functions of physical components or software
components, though having removed from the current model, but we feel further
discussion is needed.
Thanks,
Bo
-----Original Message-----
From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>
[mailto:internet-dra...@ietf.org]
Sent: Friday, February 10, 2023 7:04 PM
To: Wubo (lana) <lana.w...@huawei.com<mailto:lana.w...@huawei.com>>; Cheng Zhou
<zhoucheng...@chinamobile.com<mailto:zhoucheng...@chinamobile.com>>; Mohamed
Boucadair <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>>;
Qin Wu <bill...@huawei.com<mailto:bill...@huawei.com>>; Qin Wu
<bill...@huawei.com<mailto:bill...@huawei.com>>
Subject: New Version Notification for
draft-wzwb-opsawg-network-inventory-management-01.txt
A new version of I-D, draft-wzwb-opsawg-network-inventory-management-01.txt
has been successfully submitted by Bo Wu and posted to the IETF repository.
Name: draft-wzwb-opsawg-network-inventory-management
Revision: 01
Title: An Inventory Management Model for Enterprise Networks
Document date: 2023-02-10
Group: Individual Submission
Pages: 28
URL:
https://www.ietf.org/archive/id/draft-wzwb-opsawg-network-inventory-management-01.txt
Status:
https://datatracker.ietf.org/doc/draft-wzwb-opsawg-network-inventory-management/
Htmlized:
https://datatracker.ietf.org/doc/html/draft-wzwb-opsawg-network-inventory-management
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-wzwb-opsawg-network-inventory-management-01
Abstract:
This document defines a YANG model for network inventory management,
which provides consistent representation and reporting of network
nodes (including endpoints) inventory and enable a network
orchestrator in the enterprise network to maintain a centralized view
of all the endpoint types across multiple domains of the underlying
network to implement a coherent control strategy.
The IETF Secretariat
--
Inventory-yang mailing list
inventory-y...@ietf.org<mailto:inventory-y...@ietf.org>
https://www.ietf.org/mailman/listinfo/inventory-yang
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
