[Ofmfwg] Sunfish meeting notes for June 30, 2025

Lee, Peter peter.lee at necam.com
Mon Jun 30 08:09:24 PDT 2025



  *   Flux NVMe use case
     *   Discuss what is needed to fully implement the Flux NVMe use case with real hardware. (Timing diagram below.)
        *   [cid:image001.png at 01DBE995.DB802950]
        *   The Sunfish NVMe agent needs to be a Centralized Discovery Controller (CDC) to discover the NVMe devices. For this functionality, the Sunfish NVM agent is more like a fabric manager, so it needs to use app_fabric_mgr.py from the sunfish_server_reference code. (The app_appliance_mgr.py is more like talking to a DDC and does not do centralized discovery.) We need to create this. Russ can help create this, first without the CDC backend by serving SNIA mockups.
           *   Phil shared how to leverage NVMe CLI to implement a simple CDC.
           *   Section 6.6.2.14 from https://www.snia.org/sites/default/files/technical-work/swordfish/draft/v1.2.8/pdf/Swordfish_v1.2.8_NVMeMappingGuide.pdf has a mapping guide of how to map the NVMe discovery log pages to Redfish/Swordfish objects. The Sunfish NVMe agent will need to do this mapping.
        *   Need a datacenter NVMe resource manager to tracksall the NVMe resources from Sunfish in terms of those that are assigned and those that are available. This can be part of Sunfish utilities and just a script for simplicity. (Implement the green box from the diagram.)
        *   Need a script that plays the role of HPC Admin (yellow box) that talks with datacenter NVMe resource manager to get its set of NVMe resources to put into the Flux config file. This can be a script for simplicity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofmfwg/attachments/20250630/6366bff3/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 192946 bytes
Desc: image001.png
URL: <http://lists.openfabrics.org/pipermail/ofmfwg/attachments/20250630/6366bff3/attachment-0001.png>


More information about the Ofmfwg mailing list