Re: [Cats] DMDTF and CATS Metrics

[Peng Liu <[e-mail]>]

Hi Luis,

Thanks for the references. They proposed the compute related metrics which could be considered for cats(may also for alto). 

https://www.rfc-editor.org/rfc/rfc7666.html uses CPU, memory, storage and NIC as the metrics.  

https://www.ietf.org/archive/id/draft-contreras-alto-service-edge-07.txt takes CNTT as an example, including  _Type of instance, _Interface Option, _Compute flavor（virtual CPU, RAM, disk, and bandwidth）,_Optional storage extension，and _Optional hardware acceleration characteristics.

For different use cases, whether and how to uses those metrics should be discussed more, considering the balance between the availability and efficiency.

Regards,
Peng


[e-mail]
 
From: LUIS MIGUEL CONTRERAS MURILLO
Date: 2023-04-12 13:25
To: [e-mail]; 'Dean Bogdanovic'
CC: [e-mail]; '[e-mail]'
Subject: Re: [Cats] DMDTF and CATS Metrics
(Adding ALTO in cc since discussion on metrics is also relevant for that WG)
 
Hi Adrian, Dean, 
 
Another reference work we can consider is https://www.rfc-editor.org/rfc/rfc7666.html. This RFC provides several metrics as part of the MIB definition that could be leveraged on.
 
Apart from that, I think we need to look at what current cloud / VI managers provide nowadays in terms of metrics (i.e., OpenStack, Kubernetes, etc) since the metrics that we could handle will be generated most probably for those non-IETF components. So a good exercise to start with would be to check and compare what kind of metrics these kind of sustems provide nowadays, and derive from that a common / abstract set of metrics that could be consumed by both CATS and ALTO.
 
In https://www.ietf.org/archive/id/draft-contreras-alto-service-edge-07.txt there is reference as well to CNTT and Anuket efforts, which probably need to be revisited and updated. 
 
All in all, an exercise of collecting different sources is needed, and from that select relevant metrics for the purposes of ALTO and CATS.
 
Best regards
 
Luis
 
 
De: Cats <[e-mail]> En nombre de Adrian Farrel
Enviado el: viernes, 7 de abril de 2023 20:17
Para: 'Dean Bogdanovic' <[e-mail]>
CC: [e-mail]
Asunto: Re: [Cats] DMDTF and CATS Metrics
 
Ah, thanks Dean.
 
Interesting coincidence of acronyms. 
 
This work does, indeed, look relevant.
 
Cheers,
Adrian
 
From: Dean Bogdanovic <[e-mail]> 
Sent: 07 April 2023 19:01
To: Adrian Farrel <[e-mail]>
Cc: [e-mail]
Subject: Re: DMDTF and CATS Metrics
 
Hi,
 
I was referring to the work that is being done by Redfish and has been presented at IETF 98 by Joe White (https://datatracker.ietf.org/meeting/98/materials/slides-98-rtgwg-yang-device-profile-for-redfish-network-management-draft-wbl-rtgwg-baseline-switch-model-draft-wbl-rtgwg-yang-ci-profile-bkgd-00). This work didn’t continue within the IETF, but Redfish has published and keeps developing and maintaining their data model (https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2022.2.pdf]. They did lot of compute resource modeling and taking a loot at their work is very useful IMO. DMTF folks know lot about compute, so it might be worth even rekindling the joint work.
 
Dean
 
On Apr 7, 2023, at 12:34 PM, Adrian Farrel <[e-mail]> wrote:
 
Hi all,

In the meeting in Yokohama, Dean Bogdanovic mentioned a presentation from
IETF-98 that might be relevant to our metrics works.

I did some digging and found the presentation by the IEEE 802.3cf - YANG
Data Model Definitions Task Force. The purpose of that work was to migrate
relevant MIB modules to YANG.

The slides for that session are at
https://datatracker.ietf.org/meeting/98/materials/slides-98-netmod-sessa-iee
e-8023cf-yang-data-model-definitions-task-force-00
The presentation is at https://youtu.be/hUSx_Ua3MnY?t=3326 and the presenter
was Rob Wilton who would, I'm sure, be responsive to questions.

I'm not clear how much this is relevant.

Dean, was that the presentation you were referring to?

Cheers,
Adrian


 




Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição