[Ofmfwg] Sunfish meeting agenda for 7 February 2025

[Aguilar, Michael James]

Everyone

Here is a tentative meeting agenda for 7 February 2025.

Mike


  1.  Russ is now the new Co-Chair of Sunfish along with Mike
  2.  Merge of Russ’ branch of commits to the Master Sunfish Library branch
  3.  Brian Pan (H3) demo of new CXL fabric attached memory to Sunfish Core.
  4.  Report back from team of Russ and Phil
  5.  Approach for translating Sunfish Agent Redfish Tree into Flux Resource Edge/Vertex Mapping for hwloc
     *   https://flux-framework.readthedocs.io/projects/flux-core/en/latest/guide/admin.html#configuring-resources
     *   The Flux system instance must be configured with a static resource set. The resource.config TOML array in the example above is the preferred way to configure clusters with a resource set consisting of only nodes, cores, and GPUs.More complex resource sets may be represented by generating a file in RFC 20 (R version 1) form with scheduler extensions using a combination of flux R encode and flux ion-R encode and then configuring resource.path to its fully-qualified file path.
     *   https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_6.html , https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_27.html, https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_20.html, https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_44.html, https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_4.html
     *   A resource pool with size 1 SHALL be the finest granularity at which a resource can be described. Although this is identical to describing the resource as a scalar, we SHALL still call it a resource pool to avoid introducing a new concept. When a distinction is needed, a pool with size 1 SHALL be called a “degenerate resource pool”.  The second concept borrows from graph theory to describe relationships among such individual resource pools. A graph consists of a set of vertices and edges, where each vertex represents an individual resource pool and an edge a certain relationship between them.  Each edge SHALL be either directional or bidirectional and have a type as well as a subsystem name such that the union of the set of all edges with a same name and the set of all vertices connected by these edges SHALL represent a unique subsystem of resources (e.g., a compute subsystem, a parallel I/O subsystem, a power subsystem, etc).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofmfwg/attachments/20250207/16a94c5d/attachment.htm>