<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Hi all,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
I have also missed Friday's meeting, but I tend to agree with Russ - can't see the need for two DBs.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
To me the RF/SF block in Michael's deck should be the data backend of the resource inventory service that we see depicted in the Fabric Management box. In the end they are all redfish objects and therefore I expect them to belong to one resource tree. Swordfish
is an extension to RedFish and I believe (not an expert by any mean, so please correct me) that RF objects can be part of the same DB as regular RF ones. On the API side I would expect that the OFMF exposes a regular RF API as well as the SF one (do we need
a SF service as parto of the OFMF?). </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
In the main diagram I would separate the OFMF part of the figure into Services and Data Storage, see pic below.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<img style="width: 1152.87px; height: 650px; max-width: initial;" class="w-1561 h-880" width="1152" height="650" size="206623" contenttype="image/png" data-outlook-trace="F:1|T:1" src="cid:0ca92968-693e-4ff9-a4d8-d9dfad5a65fc"><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
The part where we need to do some more thinking is the Composability layer and align our definitions of composability.
<a href="https://www.dmtf.org/sites/default/files/Redfish_School-Composability_2017_0.pdf" title="https://www.dmtf.org/sites/default/files/Redfish_School-Composability_2017_0.pdf">
RF defines a composability API and specific objects </a>(ResourceBlocks - RB) for supporting composition of systems. In this schema, Composability is merely the creation of a new computer system out of a collection of RBs. In my view RB objects should be part
of the OFMF RF DB and be advertised/created by Agents (pic above). Agents work in tandem with FMs and have the knowledge about what components can be composed.
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<span style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); display: inline !important;">The composability Layer/Managers might keep their own representation (DB) of the composable resources for bookkeeping, implementing policies, etc. This DB would
be separated from the OFMF one and not necessarily storing objects in their original RF representation. </span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<span style="">If we want the composability layer to incorporate functionalities from FAM managers and alike, then we would probably need to extend RedFish Composability . e.g., clients request the creation of a new system with some memory related requirements
(latency). The composability layer could decide to serve part of this memory from a FAM chunk that it created and exposed as a RB. As of today, this is not possible with RedFish composability as there is no way of specifying a FAM MemoryType and to include
performance/QoS related constraints in composition requests. FAM is just an example I am using here. </span><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
</div>
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
I am happy to discuss this further on Friday.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Christian</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div id="Signature">
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span><span style="font-size:1.143em"><strong>Christian Pinto, Ph.D.</strong></span></span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div><span><span style="font-size:1.143em">Research Scientist</span></span></div>
<span style="color: rgb(0, 0, 0);">IBM Research Europe - Ireland</span></div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Ofmfwg <ofmfwg-bounces@lists.openfabrics.org> on behalf of Herrell, Russ W (Senior System Architect) <russ.herrell@hpe.com><br>
<b>Sent:</b> Monday 22 August 2022 23:59<br>
<b>To:</b> Aguilar, Michael J. <mjaguil@sandia.gov>; ofmfwg@lists.openfabrics.org <ofmfwg@lists.openfabrics.org>; Cayton, Phil <phil.cayton@intel.com>; Ahlvers, Richelle <richelle.ahlvers@intel.com>; Jim Hull <jmhull@intelliprop.com>; Sandur, Atul <Atul.Sandur@amd.com>;
Blagodurov, Sergey <Sergey.Blagodurov@amd.com><br>
<b>Cc:</b> Michele Gazzetti1 <Michele.Gazzetti1@ibm.com><br>
<b>Subject:</b> [EXTERNAL] Re: [Ofmfwg] OFMFWG---Latest update-to-date OFMF diagram</font>
<div> </div>
</div>
<div>
<div style="display:none!important; display:none; visibility:hidden; font-size:1px; color:#ffffff; line-height:1px; height:0px; max-height:0px; opacity:0; overflow:hidden">
Sorry I was un-available last Friday. I had a similar clarifying viewpoint in mind, except the resource pool data base (my term for Redfish/Swordfish database) is part of the composability layer and the OFMF layer was the keeper of the Redfish
</div>
<div style="display:none!important; display:none; visibility:hidden; font-size:1px; color:#ffffff; line-height:1px; height:0px; max-height:0px; opacity:0; overflow:hidden">
ZjQcmQRYFpfptBannerStart</div>
<div dir="ltr" lang="en" id="x_pfptBannertbipyce" style="display:block!important; text-align:left!important; margin:16px 0px 16px 0px!important; padding:8px 16px 8px 16px!important; border-radius:4px!important; min-width:200px!important; background-color:#D0D8DC!important; background-color:#D0D8DC; border-top:4px solid #90a4ae!important; border-top:4px solid #90a4ae">
<div id="x_pfptBannertbipyce" style="float:left!important; display:block!important; margin:0px 0px 1px 0px!important; max-width:600px!important">
<div id="x_pfptBannertbipyce" style="display:block!important; visibility:visible!important; background-color:#D0D8DC!important; color:#000000!important; color:#000000; font-family:'Arial',sans-serif!important; font-family:'Arial',sans-serif; font-weight:bold!important; font-weight:bold; font-size:14px!important; line-height:18px!important; line-height:18px">
This Message Is From an External Sender </div>
<div id="x_pfptBannertbipyce" style="display:block!important; visibility:visible!important; background-color:#D0D8DC!important; color:#000000!important; color:#000000; font-weight:normal; font-family:'Arial',sans-serif!important; font-family:'Arial',sans-serif; font-size:12px!important; line-height:18px!important; line-height:18px; margin-top:2px!important">
This message came from outside your organization. </div>
</div>
<div style="clear:both!important; display:block!important; visibility:hidden!important; line-height:0!important; font-size:0.01px!important; height:0px">
</div>
</div>
<div style="display:none!important; display:none; visibility:hidden; font-size:1px; color:#ffffff; line-height:1px; height:0px; max-height:0px; opacity:0; overflow:hidden">
ZjQcmQRYFpfptBannerEnd</div>
<style>
<!--
#x_pfptBannertbipyce
{display:block!important;
visibility:visible!important;
opacity:1!important;
background-color:#D0D8DC!important;
max-width:none!important;
max-height:none!important}
-->
</style>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:"Book Antiqua"}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_EmailStyle18
{font-family:"Calibri",sans-serif;
color:windowtext}
span.x_EmailStyle19
{font-family:"Calibri",sans-serif;
color:#1F497D}
.x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="color:#1F497D">Sorry I was un-available last Friday.</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">I had a similar clarifying viewpoint in mind, except the resource pool data base (my term for Redfish/Swordfish database) is part of the composability layer and the OFMF layer was the keeper of the Redfish
description of all fabric inventory. The ‘composability layer’ consists of FAM managers, NVMe managers, compute managers, etc, and they probably have their own bookkeeping DB for details that the OFMF Redfish tree doesn’t need to know. But all HW settings
and logical inventory assignments (ala memoryChunks and address zones) are also tracked in the ONE Redfish DB in the OFMF layer, so Kubernetes tools can interact with other vendor container managers indirectly through the OFMF layer.
</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">I need someone to explain to me what is the difference in the OFM Database and the RF/SF Database, since I thought all objects and resources being tracked by the OFMF Services were represented as Redfish objects
(or Swordfish objects that are essentially expanded Redfish schema and linked back to Redfish objects for physical representation) and there was only need for one database.
</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">Quite frankly, I was thinking that Swordfish is the storage resource manager API. As such, apps and tools that already use the Swordfish APIs just make their calls into the OFMF Redfish / Swordfish API of
the OFMF.</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">The Swordfish API’s StorageService would sit immediately above the OFMF Redfish Service since the physical resources that make up the inventory for Swordfish Storage Pools are part of the fabric based resources
tracked in the OFMF inventory. Below is the SNIA diagram that leads me to think this way:
</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"><img width="866" height="400" id="x_Picture_x0020_2" data-outlook-trace="F:1|T:1" src="cid:image002.png@01D8B63E.1514EC70"></span><span style="color:#1F497D">
</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">However, my vision has all Redfish objects part of the OFMF Redfish tree….</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">Maybe we should be looking at the OFMF layer as an aggregated RF/SF API that allows clients to manipulate storage, compute, fabric, and FAM resources from one ‘Service’ that operates from ONE Redfish/Swordfish
database, like so:</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"><img width="578" height="326" data-outlook-trace="F:1|T:1" src="cid:image005.png@01D8B640.24F0E980"></span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">I can adjust my thinking to the above….
</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">But I don’t see a need for two ‘databases’, from a functional point of view.</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">(Perhaps the problem is the Swordfish services code cannot be merged easily with the Redfish services code? Maybe that’s Richelle’s point?)</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"></span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">Russ</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<p class="x_MsoNormal"><span style="color:blue"><img width="60" height="17" id="x_Picture_x0020_3" alt="hpesm_pri_grn_pos_rgb" data-outlook-trace="F:1|T:1" src="cid:image001.gif@01D8B638.6FCBCA40"></span><b><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black"></span></b></p>
<p class="x_MsoNormal"><b><span style="font-size:4.0pt; font-family:"Arial",sans-serif; color:black"> </span></b></p>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:black">Russ Herrell</span></p>
<p class="x_MsoNormal"><span style="font-size:8.0pt; font-family:"Arial",sans-serif; color:black">Distinguished Technologist | Hewlett Packard Labs | System Architecture Lab
</span></p>
<p class="x_MsoNormal"><span style="font-size:8.0pt; font-family:"Arial",sans-serif; color:black">Hewlett Packard Enterprise |
<a href="mailto:russ.herrell@hpe.com">russ.herrell@hpe.com</a> | Mobile: +1 970 420 1707</span></p>
<p class="x_MsoNormal" style="margin-right:0in; margin-bottom:5.0pt; margin-left:0in; text-autospace:none">
<span style="font-size:8.0pt; font-family:"Book Antiqua",serif; color:black">“The betterment of our society is not a job to be left to a few; it is a responsibility to be shared by all.” -- Dave Packard</span><span style="font-size:8.0pt; font-family:"Book Antiqua",serif; color:black"></span></p>
</div>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="margin-left:.5in"><b>From:</b> Ofmfwg [mailto:ofmfwg-bounces@lists.openfabrics.org]
<b>On Behalf Of </b>Aguilar, Michael J.<br>
<b>Sent:</b> Monday, August 22, 2022 1:58 PM<br>
<b>To:</b> ofmfwg@lists.openfabrics.org; Cayton, Phil <phil.cayton@intel.com>; Ahlvers, Richelle <richelle.ahlvers@intel.com>; Jim Hull <jmhull@intelliprop.com>; Sandur, Atul <Atul.Sandur@amd.com>; Blagodurov, Sergey <Sergey.Blagodurov@amd.com><br>
<b>Cc:</b> Michele Gazzetti1 <Michele.Gazzetti1@ibm.com><br>
<b>Subject:</b> [Ofmfwg] OFMFWG---Latest update-to-date OFMF diagram</p>
</div>
</div>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">Everyone</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">We have a new version of an abstract look at the OFMF to look at.
</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">After the meetings on Wednesday and Friday morning, we have:</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:1.0in; text-indent:-.25in"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span>Separated out some of the memory structures and resource information into a separate Redfish/Swordfish database.</p>
<p class="x_MsoNormal" style="margin-left:1.0in; text-indent:-.25in"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span>Added a ‘Composability Layer’ on the left side of the first slide. The Composability Layer communicates to the OFMF and to the other Redfish/Swordfish database to gather and provide information to the OFMF (fabrics and fabric connections) and
to the other database for resource control and management.</p>
<p class="x_MsoNormal" style="margin-left:1.0in; text-indent:-.25in"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span>The Gen-Z and CXL Agents communicate to the OFMF and to the other database to gather information, as they are capable of working with the end-point resources.
</p>
<p class="x_MsoNormal" style="margin-left:1.0in; text-indent:-.25in"><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">
</span></span>The resources are controlled by the Redfish/Swordfish database and the connections are controlled by the OFMF.</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">I think, it appears, that the Composability Manager, on the left, is the key part of what we were missing. In the end, we want the functionality that Gen-Z and CXL provide through their Agents, but we want separation
of concerns.</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">Please, feel free to edit and we’ll continue to meet and hash out the diagram.
<b>Also, please feel free to respond to this email thread and submit changes, ahead of the meetings, to try to work out, edit, and ‘flesh’ out this diagram.</b> It will be helpful to get some portions done before we meet. We’ll consider this diagram a living
document. In addition, please tag on any Use-Case descriptions, UML, and flow diagrams that you want to test against the current OFMF diagrams, at any step.</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">Right now, I am trying to work out how the left side of the diagram looks and works for HPC clients. That is slide 2.</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">Slide 1: Our current diagram after Friday</p>
<p class="x_MsoNormal" style="margin-left:.5in">Slide 2: Left side clients and the Composability Layer</p>
<p class="x_MsoNormal" style="margin-left:.5in">Slide 3: The old diagram, pre-Wednesday and pre-Friday</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in">Mike</p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
<p class="x_MsoNormal" style="margin-left:.5in"> </p>
</div>
</div>
</body>
</html>