Hi Daniele,

Thanks for the clarification.
Now I understand what you want to include is static value.

Best,
Tianran

________________________________

Sent from WeLink
发件人: Daniele Ceccarelli<[email protected]<mailto:[email protected]>>
收件人: Tianran Zhou<[email protected]<mailto:[email protected]>>
抄送: Alexander L 
Clemm<[email protected]<mailto:[email protected]>>;opsawg<[email protected]<mailto:[email protected]>>
主题: Re: [OPSAWG] Some thoughts on Green Networking Metrics
时间: 2023-08-21 20:33:57

HI Tianran, Alex,

the power consumed at a given time is highly changing over time, but parameters 
like e.g. power consumption of a card at 50%, 75% and 100% of the load don't.
I don't disagree with Alex when saying that this is not directly inventory, but 
it's strictly related to it and should probably be an augmentation of the 
device inventory.

BR
Daniele

On Fri, Aug 18, 2023 at 3:20 AM Tianran Zhou 
<[email protected]<mailto:[email protected]>> 
wrote:
I am not quite clear about the applicability of the inventory.
What’s the difference with hardware model or entity model.
I see energy work was related to entity mib in eman before:
https://datatracker.ietf.org/wg/eman/documents/

It seems inventory should be something static from the name. But IMO, the 
energy metrics are dynamic, can will change all the time.

Best,
Tianran

From: OPSAWG [mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Alexander L Clemm
Sent: Friday, August 18, 2023 7:05 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [OPSAWG] Some thoughts on Green Networking Metrics


Hi Daniele,

apologies for the late reply.

I think inventory is somewhat orthogonal to this, but of course devices and 
equipment (including chassis, line cards, equipment holders etc) will be 
considered part of inventory.   Therefore via transitive closure it is 
certainly conceivable to make power consumption data accessible via inventory.  
This could make sense as part of a consolidated controller view of a network.  
However, on a network element itself, the network inventory aspect would not 
apply but the metrics should still be available so the device/equipment level 
category still applies.  As to whether device level data should be replicated 
as part of network inventory data  would presumably depend on the use case.

--- Alex
On 7/26/2023 6:35 PM, Daniele Ceccarelli (dceccare) wrote:
Hi Alex, all,

Just following up on the comment I did ad the mic earlier today.

The drafts speaks about metrics at: device/equipment level, flow level, path 
level, network level.
The  device/equipment level covers power consumption per chassis, line card and 
port at different loads of traffic, hence IMO should fall into the inventory 
category.
Would you agree?

Cheers,
Daniele




_______________________________________________

OPSAWG mailing list

[email protected]<mailto:[email protected]>

https://www.ietf.org/mailman/listinfo/opsawg

_______________________________________________
OPSAWG mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to