Skip to end of banner
Go to start of banner

2021-06-10 - Anuket: Hardware Acceleration Abstraction

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »


Topic Leader(s)

Topic Overview

60m, arkady kanevsky

Anuket is promote HW independent RM, RAs and RC. For accelerators for RAN workload oRAN Alliance is defining Acceleration Abstraction Layer and APIs - https://oranalliance.atlassian.net/wiki/download/attachments/872841331/O-RAN.WG6.AAL-GAnP-v01.00.pdf?api=v2. However Kubernetes currently does not have an abstraction for accelerators and each accelerator is handled and need to be programmed to independently. This session will discuss current state of affairs and what can be done to remedy it.

Slides & Recording


YouTube

Please indicate your session type in the blank space below and then remove this Info field.

  • Demo / Informational (non-interactive)
    • You may be asked to pre-record this session which will be made available on-demand.
  • Live Interactive Session

LFN Staff may elect to publish some videos to YouTube.  Please indicate here if you do not want your session to be published to YouTube.


Recording: Hardware Acceleration Abstraction.mp4

Agenda

Awesome presentation

  • Point 1
  • Point 2

Minutes

  • Current status in Anuket
    • RM Ch3 describes
      • accelerators in an abstract way,
      • motivations for accelerators (time precision, power or space envelopes, simple optimisation)
      • Categorization of accelerators
      • How to consume accelerators
    • RA2 Ch3 and Ch4
      • NFD and device plugins
  • What is missing
    • RA1
      • Cyborg is planned to be introduced in Lakese. This was a strong motivation to change the OpenStack baseline version to Walaby.
    • RA2
      • Device plugin API-s are fragmented
        • We should aim for a more portable API design
        • At the moment there is no consensus on this, but maybe Anuket has enough vendors and operators to build a consensus and convince device plugin vendors to modify their API design
    • RI1
      • No progress until RA1 work is finished
    • RI2
      • Support exist in the tools used to install RI2 (Intel BMRA), even some of these features are enabled
      • HW availability is the biggest issue
    • RC1
    • RC2
      • Work towards basic testcases started
  • AAL in O-RAN
    • The aim is to provide an abstract API to consume accelerators
    • RM mentions AAL
    • Anuket should align with O-RAN

Action Items

  •  
  • No labels