[Ofmfwg] OFMF tentative meeting agenda for 20 July 2022

Aguilar, Michael J. mjaguil at sandia.gov
Wed Jul 20 13:59:16 PDT 2022


Everyone

We are meeting today.  I made a typo before I sent the agenda

Mike

From: "Aguilar, Michael J." <mjaguil at sandia.gov>
Date: Wednesday, July 20, 2022 at 2:36 PM
To: "ofmfwg at lists.openfabrics.org" <ofmfwg at lists.openfabrics.org>, "Cayton, Phil" <phil.cayton at intel.com>, "Ahlvers, Richelle" <richelle.ahlvers at intel.com>, "Hanke, Erich" <ehanke at intelliprop.com>, Jim Hull <jmhull at intelliprop.com>, "Sandur, Atul" <Atul.Sandur at amd.com>, "Blagodurov, Sergey" <Sergey.Blagodurov at amd.com>
Subject: OFMF tentative meeting agenda for 20 July 2022

Everyone

Here is a tentative meeting agenda for 29 July 2022

Mike


  *   Quick updates on development

     *   Servers are in place.  Group keys are mostly in place.
     *   Documentation on how to interact with OFMF server.
     *   Russ has some issues that need to be addressed on the ofmfgenz server.
     *   Mike A will be creating SSH tunnels for the OFMF transaction requests to the ofmfserv machine over the weekend.  Testing the tunnels.

  *   Upcoming conferences

     *   SDC-----Small table with a demo station?  OFA presentation---Mike or Phil or Russ?
     *   FMS----Richelle will represent OFA in the SNIA booth.  We will be getting an invite for sponsorship of the Monday evening reception.
     *   SC22---Approval for the booth for OFA.  We can use the new servers for demos.

  *   Website work----pending and soon

     *   Agent build documentation—A how to
     *   Transaction guide for the OFMF for Agents and Clients

  *   Next Proof-of-Concept work for SC22

     *   CXL OFMF demo.
•         Are we going to produce another Python-based PoC code stack to demo features or are we going to shoot for a more robust ‘reference implementation’ that anticipates re-use of code? -----Let’s discuss further, with a target of making the code more robust.  Do we have CXL hardware to run on?  We have the cloud servers, now.  We need to have a reference architecture of the OFMF.  We are able to make sure our fabric model is abstract enough.  Can hardware be provided for a CXL demo?
•         Will we have CXL – based hardware to back an OFMF / CXL Agent PoC demo?---We are sharing the same Open Source Pavilion, does that help?
•         Will we have a CXL ‘fabric manager’ / Agent layer to merge onto the OFMF layer?-----CXL is very different but the concepts are the same
•         Are we going to add events and messaging to the OFMF layer so we don’t have to make the Agent layer POST the initial inventory?  (OFMF will query the Agent for inventory)-----We need a CXL Switch and next-generation hardware (September?)---Resources---2 Parts Composability Manager and Agent
•         Need to have CXL components represented in the OFMF
•         CXL emulator ofmfcxl---in lieu of the hardware.   That way we aren’t ‘gated’ by hardware availability.

        *   Create mockups
        *   What pieces of the full Redfish schema does the CXL framework understand?
o    Generic FAM models could be re-applied to the CXL work
•  Work out how to use Composability
•  Improved ordered start-up of services
•         Restructure of agents
•         CXL fabric manager

        *   CXL Composability Use-Case description and CXL Agent
•         Are we going to be showing any of the Gen-Z PoC stack or HW ?----IntelliProp?  We need to be more succinct in the documentation and make a reference implementation.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofmfwg/attachments/20220720/cc1bef38/attachment-0001.htm>


More information about the Ofmfwg mailing list