<html><body><p><font size="2">Hi Ed,</font><br><br><font size="2" color="#800000">Replied </font><font size="2">inline.</font><br><br><font size="2">Hari !</font><br><br><br><img width="16" height="16" src="cid:1__=EABB08B8DFC66F688f9e8a93df938690918cEAB@" border="0" alt="Inactive hide details for "Tanous, Ed" ---02/01/2018 11:26:48 PM---A couple questions inline below. -Ed"><font size="2" color="#424282">"Tanous, Ed" ---02/01/2018 11:26:48 PM---A couple questions inline below. -Ed</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Tanous, Ed" <ed.tanous@intel.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Hariharasubramanian Ramasubramanian <hramasub@in.ibm.com>, "Michael.E.Brown@dell.com" <Michael.E.Brown@dell.com></font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">"alirhas@microsoft.com" <alirhas@microsoft.com>, "Balaji.B.Rao@dell.com" <Balaji.B.Rao@dell.com>, "bradleyb@fuzziesquirrel.com" <bradleyb@fuzziesquirrel.com>, "jwcarman@us.ibm.com" <jwcarman@us.ibm.com>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>, "Paul.Vancil@dell.com" <Paul.Vancil@dell.com>, "pradeep.kumar36@tcs.com" <pradeep.kumar36@tcs.com>, "rolfb@us.ibm.com" <rolfb@us.ibm.com></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">02/01/2018 11:26 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">RE: Redfish on OpenBMC</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font color="#1F497D" face="Calibri">A couple questions inline below.</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">-Ed</font><br><font color="#1F497D" face="Calibri"> </font><br><b><font face="Calibri">From:</font></b><font face="Calibri"> Hariharasubramanian Ramasubramanian [</font><font face="Calibri"><a href="mailto:hramasub@in.ibm.com">mailto:hramasub@in.ibm.com</a></font><font face="Calibri">] </font><b><font face="Calibri"><br>Sent:</font></b><font face="Calibri"> Thursday, February 1, 2018 1:09 AM</font><b><font face="Calibri"><br>To:</font></b><font face="Calibri"> Michael.E.Brown@dell.com</font><b><font face="Calibri"><br>Cc:</font></b><font face="Calibri"> alirhas@microsoft.com; Balaji.B.Rao@dell.com; bradleyb@fuzziesquirrel.com; Tanous, Ed <ed.tanous@intel.com>; jwcarman@us.ibm.com; openbmc@lists.ozlabs.org; Paul.Vancil@dell.com; pradeep.kumar36@tcs.com; rolfb@us.ibm.com</font><b><font face="Calibri"><br>Subject:</font></b><font face="Calibri"> RE: Redfish on OpenBMC</font><br><font face="Times New Roman"> </font><p><font size="2" face="Times New Roman">Hi Michael,</font><font face="Times New Roman"><br></font><font size="2" face="Times New Roman"><br>Thanks for enumerating the attributes for comparison.</font><font face="Times New Roman"><br></font><font size="2" face="Times New Roman"><br>I want to list down a few additional criteria that may be evaluated:<br><br>1) Data-Driven Resource Discovery:<br>- The Redfish server should ideally build it's resource model from a "config file". This config file could potentially be hand-coded or built out of a "system definition file". The following are examples of system definition files for 2 of the systems currently running OpenBMC firmware.</font><u><font color="#0000FF" face="Times New Roman"><br></font></u><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__raw.githubusercontent.com_open-2Dpower_zaius-2Dxml_master_zaius.xml&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=R95M9A3s5inBJUNXdc38WluBfQav8cUQDsgddg-niDY&s=-0M5Xc0wZo-ePshVyX993AT-2snCSlWmz84-KAF8MY8&e="><u><font size="2" color="#0000FF" face="Times New Roman">https://raw.githubusercontent.com/open-power/zaius-xml/master/zaius.xml</font></u></a><u><font color="#0000FF" face="Times New Roman"><br></font></u><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__raw.githubusercontent.com_open-2Dpower_witherspoon-2Dxml_master_witherspoon.xml&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=R95M9A3s5inBJUNXdc38WluBfQav8cUQDsgddg-niDY&s=N-la3JJ76Cdcnw3zojpzXSP6YNQ1S2WVTCN4Xp8FeJw&e="><u><font size="2" color="#0000FF" face="Times New Roman">https://raw.githubusercontent.com/open-power/witherspoon-xml/master/witherspoon.xml</font></u></a><font size="2" face="Times New Roman"><br>The system architecture (sled vs blade etc.), number of processors, number of fans etc. can be determined from the system definition file to generate the config file. </font><p><font color="#1F497D" face="Times New Roman">Are you expecting that the config file would differ significantly from the dbus objects available on openbmc? My running assumption was that dbus would be the source of truth for dbus objects, and would give the avenues for expansion. Could we simply agree on a dbus schema, then have platforms expose the necessary data through dbus rather than have an extensive config file? It seems like certain things (sensors for example) we would get the schema for “free” and wouldn’t need to do anything redfish specific. For things like chassis, it might take a couple redfish specific types.</font><p><font color="#800000" face="Times New Roman">Hari>> Yes. I completely favor dbus as the means to discover the objects. All I was suggesting that the implementation be data-driven.<br><br>That said, I find that "list" and "enumerate" are 2 *introspection* API at the root level to discover *all* the resources. While with the Redfish API, the discovery recurses starting at the service root, the OpenBMC REST API is offering a flat discovery structure. The containment relationship between resources has to be inferred from the URI path. For a resource such as a CPU, we still need a means to identify how processors make up the system and how many cores make up a processor/cpu.</font><font face="Times New Roman"><br></font><font size="2" face="Times New Roman"><br>The intent is to make the redfish implementation as system agnostic as possible.<br><br>2) Separation of the Redfish front-end (view) and back-end (infrastructure) layers. The infrastructure API exposed as dbus services would be one of the means to make this separation of concerns.</font><p><font color="#1F497D" face="Calibri">Can you elaborate on this? Do you mean separating daemons? There are options to expose as dbus interfaces, but the initial performance numbers weren’t great; And the level of control that it gave was a little troubling for complex constructs like sensors. I’m sure this could be accomplished, but given the level of complexity, my team wasn’t able to build any abstract concepts that worked well in practice.</font><p><font size="2" color="#800000" face="Times New Roman">Hari>> You are right, I was expecting the backend implementation to exposed as dbus interfaces. Are you suggesting that this architecture has performance bottlenecks ?</font><p><font size="2" face="Times New Roman"><br>3) Performance :<br>- Runtime memory foot print.This could potentially have a negative impact on "how fast" the server is. Hence the trade-off should consider what can be cached vs what needs to be queried from the infrastructure.</font><font size="2" color="#1F497D" face="Times New Roman"><br>In my spaces, fixed and transient memory usage is generally an order below CPU usage, both at startup and at steady state. I think there are some tradeoffs to be had here, possibly invalidating caches on property change events, but not actually regenerating them. Things like sensors tend to be </font><i><font size="2" color="#1F497D" face="Times New Roman">very</font></i><font size="2" color="#1F497D" face="Times New Roman"> chatty, and coming up with a general purpose caching solution that handles all cases gets a little difficult. </font><p><font size="2" face="Times New Roman">- Michael, why did you consider SSL being separately implemented by the Redfish server? Would this be in the scope of the webserver ?</font><font face="Times New Roman"><br></font><font size="2" face="Times New Roman"><br>4) Eventing: Current version of the Redfish spec has left it open for the OEMs to define the specific Event Messages. i.e. there is no standard / common Event Registry. Redfish server implementation on the OpenBMC should define this common Event Registry and perhaps accepted by DMTF. Does the Eventing support filtering of events based on the event type, source resource and the message Id ?</font><p><font color="#1F497D" face="Calibri">Agreed.</font><font face="Times New Roman"><br></font><font size="2" face="Times New Roman"><br>5) Leverage existing open source projects:<br>- Does the implementation compose existing services and frameworks ? Such as a webserver(say, nginx) and a rest framework (flask).</font><p><font color="#1F497D" face="Calibri">In my testing, flask was a non-starter for performance on low end systems, and while reasonably performant when measured externally with response times, it consumed quite a bit of system CPU cycles for most tasks. Also, the startup time for python was suspect, and difficult to improve on without lots of gymnastics.</font><p><font color="#800000" face="Times New Roman">Hari>> I haven't evaluated flask and it's good to know the performance limitations with flask and python. <br></font><font size="2" face="Times New Roman"><br>regards,<br>Hari !</font><font face="Times New Roman"><br><br><br></font><img src="cid:1__=EABB08B8DFC66F688f9e8a93df938690918cEAB@" width="16" height="16" alt="Inactive hide details for ---01/31/2018 10:17:36 PM---So, I think that the first thing we ought to do is get a survey of the di"><font size="2" color="#424282" face="Times New Roman">---01/31/2018 10:17:36 PM---So, I think that the first thing we ought to do is get a survey of the different implementations tha</font><font face="Times New Roman"><br></font><font size="2" color="#5F5F5F" face="Times New Roman"><br>From: </font><font size="2" face="Times New Roman"><</font><a href="mailto:Michael.E.Brown@dell.com"><u><font size="2" color="#0000FF" face="Times New Roman">Michael.E.Brown@dell.com</font></u></a><font size="2" face="Times New Roman">></font><font size="2" color="#5F5F5F" face="Times New Roman"><br>To: </font><font size="2" face="Times New Roman"><</font><a href="mailto:bradleyb@fuzziesquirrel.com"><u><font size="2" color="#0000FF" face="Times New Roman">bradleyb@fuzziesquirrel.com</font></u></a><font size="2" face="Times New Roman">></font><font size="2" color="#5F5F5F" face="Times New Roman"><br>Cc: </font><font size="2" face="Times New Roman"><</font><a href="mailto:alirhas@microsoft.com"><u><font size="2" color="#0000FF" face="Times New Roman">alirhas@microsoft.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:Balaji.B.Rao@dell.com"><u><font size="2" color="#0000FF" face="Times New Roman">Balaji.B.Rao@dell.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:Paul.Vancil@dell.com"><u><font size="2" color="#0000FF" face="Times New Roman">Paul.Vancil@dell.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:ed.tanous@intel.com"><u><font size="2" color="#0000FF" face="Times New Roman">ed.tanous@intel.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:rolfb@us.ibm.com"><u><font size="2" color="#0000FF" face="Times New Roman">rolfb@us.ibm.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:jwcarman@us.ibm.com"><u><font size="2" color="#0000FF" face="Times New Roman">jwcarman@us.ibm.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:hramasub@in.ibm.com"><u><font size="2" color="#0000FF" face="Times New Roman">hramasub@in.ibm.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:pradeep.kumar36@tcs.com"><u><font size="2" color="#0000FF" face="Times New Roman">pradeep.kumar36@tcs.com</font></u></a><font size="2" face="Times New Roman">>, <</font><a href="mailto:openbmc@lists.ozlabs.org"><u><font size="2" color="#0000FF" face="Times New Roman">openbmc@lists.ozlabs.org</font></u></a><font size="2" face="Times New Roman">></font><font size="2" color="#5F5F5F" face="Times New Roman"><br>Date: </font><font size="2" face="Times New Roman">01/31/2018 10:17 PM</font><font size="2" color="#5F5F5F" face="Times New Roman"><br>Subject: </font><font size="2" face="Times New Roman">RE: Redfish on OpenBMC</font><br><hr width="100%" size="2" align="left" noshade><br><font face="Times New Roman"><br><br></font><font size="2" face="Courier New"><br>So, I think that the first thing we ought to do is get a survey of the different implementations that are out there, and establish criteria for judging different implementations.<br><br>Here would be a list of questions I would have for everybody on the list. I think it would probably be best to compile all of these into a wiki page somewhere.<br><br> - Do you have a redfish server implementation?<br> - Is it Open Source?<br>- If not, are you planning on open sourcing it?<br>- What is the license?<br>- Is it posted to github or other public source control?<br> - Does it pass the DMTF redfish service validator?<br> - What language is it written in?<br> - How big is it?<br> - Can it be easily extended/re-used by anybody else shipping compliant openbmc implementations?<br>- Can you add OEM extensions to existing Redfish Resources without "forking" the codebase?<br>- Can you change the implementation for a single Redfish Resource Property without forking?<br>- Can you add new Redfish Resources without forking?<br> - Performance<br>- How fast is it?<br>- Does it implement SSL?<br> - Security<br>- What is the security model?<br>- Non-root support? Can it run as a non-privileged user?<br>- Does it implement basic authentication and the redfish spec x-auth-token authentication?<br>- Does it implement the redfish standard privilege map model?<br> - Eventing:<br>- For writing a UI on top of redfish, something like SSE is a nice-to-have to avoid polling in the browser. There are a couple of proposed SSE extensions that have not yet been approved.<br>- How much work to implement SSE support to do things like watch Property changes?<br>- Is the standard redfish eventing model supported?<br>- Security model integrated with eventing? Do eventing records get the same security treatment as GET requests?<br> - Development: can it run outside of openbmc?<br> - Special sauce: is there anything not captured above that makes the implementation special in any way?<br><br>--<br>Michael<br><br>-----Original Message-----<br>From: Brad Bishop [</font><a href="mailto:bradleyb@fuzziesquirrel.com"><u><font size="2" color="#0000FF" face="Courier New">mailto:bradleyb@fuzziesquirrel.com</font></u></a><font size="2" face="Courier New">] <br>Sent: Tuesday, January 30, 2018 7:30 PM<br>To: Brown, Michael E <</font><a href="mailto:Michael_E_Brown@Dell.com"><u><font size="2" color="#0000FF" face="Courier New">Michael_E_Brown@Dell.com</font></u></a><font size="2" face="Courier New">><br>Cc: </font><a href="mailto:alirhas@microsoft.com"><u><font size="2" color="#0000FF" face="Courier New">alirhas@microsoft.com</font></u></a><font size="2" face="Courier New">; Rao, Balaji B <</font><a href="mailto:Balaji_B_Rao@dell.com"><u><font size="2" color="#0000FF" face="Courier New">Balaji_B_Rao@dell.com</font></u></a><font size="2" face="Courier New">>; Vancil, Paul <</font><a href="mailto:Paul_Vancil@Dell.com"><u><font size="2" color="#0000FF" face="Courier New">Paul_Vancil@Dell.com</font></u></a><font size="2" face="Courier New">>; Tanous, Ed <</font><a href="mailto:ed.tanous@intel.com"><u><font size="2" color="#0000FF" face="Courier New">ed.tanous@intel.com</font></u></a><font size="2" face="Courier New">>; </font><a href="mailto:rolfb@us.ibm.com"><u><font size="2" color="#0000FF" face="Courier New">rolfb@us.ibm.com</font></u></a><font size="2" face="Courier New">; </font><a href="mailto:jwcarman@us.ibm.com"><u><font size="2" color="#0000FF" face="Courier New">jwcarman@us.ibm.com</font></u></a><font size="2" face="Courier New">; Hariharasubramanian Ramasubramanian <</font><a href="mailto:hramasub@in.ibm.com"><u><font size="2" color="#0000FF" face="Courier New">hramasub@in.ibm.com</font></u></a><font size="2" face="Courier New">>; </font><a href="mailto:pradeep.kumar36@tcs.com"><u><font size="2" color="#0000FF" face="Courier New">pradeep.kumar36@tcs.com</font></u></a><font size="2" face="Courier New">; OpenBMC Maillist <</font><a href="mailto:openbmc@lists.ozlabs.org"><u><font size="2" color="#0000FF" face="Courier New">openbmc@lists.ozlabs.org</font></u></a><font size="2" face="Courier New">><br>Subject: Redfish on OpenBMC<br><br>Hi Michael<br><br>The project could really use someone to get everyone that has expressed interest in the future of Redfish support in OpenBMC rowing in the same direction. So thank you for volunteering to lead that conversation at the community call yesterday.<br><br>I’ve CC’ed everyone that I know of that has expressed an interest.<br>OpenBMC community: feel free to speak up if you’d like to be involved and I forgot you.<br><br>The only thing I’d ask is to please post links to any meetings, minutes, or correspondence here on the list, so everyone can easily keep up with how things are going or jump in to provide feedback.<br><br>thanks again<br><br>-brad</font><font face="Times New Roman"><br><br></font><br><br><BR>
</body></html>