Re: [alto] [Cats] New draft on joint exposure of network and compute information

["[e-mail]" <[e-mail]>]

Hi Adrian, all,

I think that the approach is for what purpose we need the compute metrics, rather than who will make use of them (i.e. CATS, ALTO, etc).

In our view we need compute-related metrics for the entire service lifecycle: instantiation, traffic steering, assurance, migration, etc. So our proposal is to define consistent metrics that could serve for all those purposes, independently of who use them (which could happen at different stages of the service lifecycle by different solutions).

In a simple analogy with networking metrics, latency or packet loss apply to whatever stage of the service lifecycle we are considering (e.g., path computation, traffic forwarding, monitoring of communication service health, etc).

Best regards

Luis

De: alto <[e-mail]> En nombre de Adrian Farrel
Enviado el: jueves, 2 de noviembre de 2023 21:43
Para: 'Jordi Ros Giralt' <[e-mail]>; 'Linda Dunbar' <[e-mail]>; [e-mail]; [e-mail]
Asunto: Re: [alto] New draft on joint exposure of network and compute information

So, my view is that CATS is specifically chartered to look at these metrics. I think the metrics could equally be applied in ALTO (as I said at IETF-117 in the ALTO WG meeting).
I had hoped that we might hold an interim to discuss metrics, but progress has been slow.
That said, the CATS list has recently been discussing metrics a bit, and I hope we can build on that.
I would like to hear lots of opinions. At the moment, I don't mind much whether there is consensus or strong debate. I'd just like to hear many voices.
What are the factors:

  *   Simple?
  *   Generic?
  *   Variable or static?
  *   Actual compute load/capability versus anticipated delay for a "standard" compute action?
  *   <your idea here>

Cheers,
Adrian

From: alto <[e-mail]<mailto:[e-mail]>> On Behalf Of Jordi Ros Giralt
Sent: 02 November 2023 17:58
To: Linda Dunbar <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Re: [alto] New draft on joint exposure of network and compute information

Thanks Linda.

These metrics can be common to a variety of use cases. That is, the same common metrics can be used to support the CATS use cases (exposure to the ingress point) or (as suggested by this draft) to support service providers and applications to make service deployment and selection decisions. The two efforts (network and application layer) can complement each other to achieve the performance requirements.

As for metrics, it depends on the application, but certainly on the compute side, CPU, GPU, NPU, memory, storage are all important to make proper placement and selection decisions. A good part is that, in general, for a given application (e.g., AI inference), the requirements to run it are generally well-known at deployment/selection time.

Thanks,
Jordi
________________________________
From: Linda Dunbar <[e-mail]<mailto:[e-mail]>>
Sent: Wednesday, November 1, 2023 18:15
To: Jordi Ros Giralt <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: RE: New draft on joint exposure of network and compute information


WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Jordi,



In addition, CATS WG is discussing many more metrics that can impact the service performance.



Really appreciate if you can elaborate more on the new metrics that impact the deployment and path section. It will be very useful.



Thanks, Linda







From: Linda Dunbar
Sent: Wednesday, November 1, 2023 12:11 PM
To: Jordi Ros Giralt <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Subject: RE: New draft on joint exposure of network and compute information



Jordi,



Your draft describes two aspects of the service performance impacted by the Computing: Service Deployment and  Service (Path) Selection. Those two should be separated, as the Service Deployment belongs to the OpsArea, and the Service selection (including Network Path & DCs that host the services) belongs to the Routing area.



https://datatracker.ietf.org/doc/draft-ietf-idr-5g-edge-service-metadata/ has proposed a new Metadata Path Attribute and some Sub-TLVs  for egress routers to advertise the Metadata about the attached edge  services (ES).  The Edge Service Metadata can be used by the ingress routers in the 5G Local Data Network to make path selections not only based on the routing cost but also the running environment of the edge services.  The goal is to improve latency and performance for 5G  edge services.





Can this Metadata Path Attribute address the problem stated in your draft?  I CC'ed the IDR WG, so your comments on the Path Selection can be visible to them.



Thanks, Linda





From: Cats <[e-mail]<mailto:[e-mail]>> On Behalf Of Jordi Ros Giralt
Sent: Tuesday, October 24, 2023 6:47 AM
To: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: [Cats] New draft on joint exposure of network and compute information



Dear CATS and ALTO WG mailing list members,



We submitted a new draft on joint exposure of network and compute information for service placement and selection: https://datatracker.ietf.org/doc/draft-rcr-opsawg-operational-compute-metrics/




Joint Exposure of Network and Compute Information for Infrastructure-Aware Service DeploymentJoint Exposure of Network and Compute Information for Infrastructure-Aware Service Deployment

This draft focuses on the problem of exposing both network and compute information to the service provider/application to support service placement and selection decisions. ALTO provides an interface for network information exposure to the service provider/application; thus, an approach is to leverage and extend it with compute metrics. CATS also needs to develop compute metrics to support traffic steering decisions. The common ground is in these compute metrics, which could be reused across the various use cases (e.g., consumed by the network as in CATS or consumed by the application as in ALTO).



This draft also aims at providing a framework for continuing the discussion initiated during IETF 117 regarding the presentation "Compute-aware metrics: CATS working with ALTO": https://datatracker.ietf.org/doc/slides-117-alto-compute-aware-metrics-cats-working-with-alto/



We would like to seek feedback from both working groups on developing compute metrics that can be reused for different use cases, to avoid duplicated work and increase the effectiveness of future standards.



Thanks,

Jordi





________________________________

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
________________________________

Le informamos de que el responsable del tratamiento de sus datos es la entidad del Grupo Telef?nica vinculada al remitente, con la finalidad de mantener el contacto profesional y gestionar la relaci?n establecida con el destinatario o con la entidad a la que est? vinculado. Puede contactar con el responsable del tratamiento y ejercitar sus derechos escribiendo a [e-mail]<mailto:[e-mail]>. Puede consultar informaci?n adicional sobre el tratamiento de sus datos en nuestra Pol?tica de Privacidad<https://www.telefonica.com/es/telefonica-politica-de-privacidad-de-terceros/>.

We inform you that the data controller is the Telef?nica Group entity linked to the sender, for the purpose of maintaining professional contact and managing the relationship established with the recipient or with the entity to which it is linked. You may contact the data controller and exercise your rights by writing to [e-mail]<mailto:[e-mail]>. You may consult additional information on the processing of your data in our Privacy Policy<https://www.telefonica.com/en/wp-content/uploads/sites/5/2022/12/Telefonica-Third-data-subjects-Privacy-Policy.pdf>.

Informamos que o respons?vel pelo tratamento dos seus dados ? a entidade do Grupo Telef?nica vinculada ao remetente, a fim de manter o contato professional e administrar a rela??o estabelecida com o destinat?rio ou com a entidade ? qual esteja vinculado. Voc? pode entrar em contato com o respons?vel do tratamento de dados e exercer os seus direitos escrevendo a [e-mail]<mailto:[e-mail]>. Voc? pode consultar informa??o adicional sobre o tratamento do seus dados na nossa Pol?tica de Privacidade<https://www.telefonica.com/es/politica-de-privacidade-de-terceiros/>.