<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:805241678;
mso-list-template-ids:-41278886;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1715616261;
mso-list-template-ids:-20922434;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Michael,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I can meet any of the times you proposed. ( I have a conflict 2-3 CST on Monday but you didn’t propose that).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">To the list of Implementations to look at:<o:p></o:p></span></p>
<p class="MsoNormal"><tt><span style="font-size:10.0pt"> Overview of existing implementations and work</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt> Bmcweb implementation by Intel – Ed Tanous</tt><br>
<tt> Go-redfish implementation by Dell – Michael Brown</tt><br>
<tt> Redfish implementation by Microsoft – Ali Larijani/Yugi Mani/Bryan Kelly</tt></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Please add:<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:red">RedDrum python implementation by Dell
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-- Paul Vancil/Balaji B Rao<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> --We have this open sourced now on github. At: github.com/RedDrum-Redfish-Project
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> --there is both a Simulator backend and an OpenBMC backend<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> --Balaji is finishing the Yocto recipes to build it into an image now<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> --we have it running on a Power9 board with most of the HW interfaces integrated<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> --we will have this setup as a demo at OCP (the Simulator and the Power9 openBMC)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> --we will update the measurements on performance and size next week, but we have some earlier measurements if we need to share on Mon.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> -- this is python which has some advantages in some cases buy not probably the best for some.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Paul Vancil<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Hariharasubramanian Ramasubramanian [mailto:hramasub@in.ibm.com]
<br>
<b>Sent:</b> Thursday, February 22, 2018 9:16 PM<br>
<b>To:</b> Ali Larijani <alirhas@microsoft.com><br>
<b>Cc:</b> Rao, Balaji B <Balaji_B_Rao@dell.com>; bradleyb@fuzziesquirrel.com; Chris Ong <Chris.Ong@microsoft.com>; Tanous, Ed <ed.tanous@intel.com>; jwcarman@us.ibm.com; Brown, Michael E <Michael_E_Brown@Dell.com>; openbmc@lists.ozlabs.org; Vancil, Paul <Paul_Vancil@Dell.com>;
pradeep.kumar36@tcs.com; rolfb@us.ibm.com; Yugi Mani <yupalani@microsoft.com><br>
<b>Subject:</b> RE: Redfish on OpenBMC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt">Sound like we are ready for a take off :-)</span><br>
<br>
<br>
<span style="font-size:10.0pt">2PM PST(1:30AM IST) is a little inconvenient. My votes are for the below times:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><tt><span style="font-size:10.0pt">> Wed evening 9pm CST</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>> Thursday morning 9am CST</tt><br>
<tt>> Friday 8am CST</tt></span><o:p></o:p></p>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt">Also BlueJeans is a paid offering. Zoom probably would suit us better if we can limit our meetings to 40 mins.</span><br>
<br>
<span style="font-size:10.0pt">Michael & me had an irc conversation earlier and my thoughts align with Ed. My wishlist was:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt">1) Targeted discussion with the contributors. (irc/webex/whatever else works).
</span><br>
<span style="font-size:10.0pt">2) Setting up the wiki for documenting our discussions.</span><br>
<span style="font-size:10.0pt">3) Get the contributors code onto github and review</span><br>
<span style="font-size:10.0pt">4) A hackathon may be to "add a new resource" using each of the implementations.</span><o:p></o:p></p>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt">regards,</span><br>
<span style="font-size:10.0pt">Hari !</span><br>
<br>
<img width="16" height="16" id="_x0000_i1025" src="cid:image001.gif@01D3ACA1.21348AC0" alt="Inactive hide details for Ali Larijani ---02/23/2018 08:19:20 AM---Thanks Ed, your agenda looks very good to me. If it works fo"><span style="font-size:10.0pt;color:#424282">Ali
Larijani ---02/23/2018 08:19:20 AM---Thanks Ed, your agenda looks very good to me. If it works for everybody, let's schedule a meeting on</span><br>
<br>
<span style="font-size:10.0pt;color:#5F5F5F">From: </span><span style="font-size:10.0pt">Ali Larijani <<a href="mailto:alirhas@microsoft.com">alirhas@microsoft.com</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">To: </span><span style="font-size:10.0pt">"Tanous, Ed" <<a href="mailto:ed.tanous@intel.com">ed.tanous@intel.com</a>>, "<a href="mailto:Michael.E.Brown@dell.com">Michael.E.Brown@dell.com</a>" <<a href="mailto:Michael.E.Brown@dell.com">Michael.E.Brown@dell.com</a>>,
Yugi Mani <<a href="mailto:yupalani@microsoft.com">yupalani@microsoft.com</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Cc: </span><span style="font-size:10.0pt">"<a href="mailto:Paul.Vancil@dell.com">Paul.Vancil@dell.com</a>" <<a href="mailto:Paul.Vancil@dell.com">Paul.Vancil@dell.com</a>>, "<a href="mailto:hramasub@in.ibm.com">hramasub@in.ibm.com</a>"
<<a href="mailto:hramasub@in.ibm.com">hramasub@in.ibm.com</a>>, "<a href="mailto:Balaji.B.Rao@dell.com">Balaji.B.Rao@dell.com</a>" <<a href="mailto:Balaji.B.Rao@dell.com">Balaji.B.Rao@dell.com</a>>, "<a href="mailto:bradleyb@fuzziesquirrel.com">bradleyb@fuzziesquirrel.com</a>"
<<a href="mailto:bradleyb@fuzziesquirrel.com">bradleyb@fuzziesquirrel.com</a>>, "<a href="mailto:jwcarman@us.ibm.com">jwcarman@us.ibm.com</a>" <<a href="mailto:jwcarman@us.ibm.com">jwcarman@us.ibm.com</a>>, "<a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a>"
<<a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a>>, "<a href="mailto:pradeep.kumar36@tcs.com">pradeep.kumar36@tcs.com</a>" <<a href="mailto:pradeep.kumar36@tcs.com">pradeep.kumar36@tcs.com</a>>, "<a href="mailto:rolfb@us.ibm.com">rolfb@us.ibm.com</a>"
<<a href="mailto:rolfb@us.ibm.com">rolfb@us.ibm.com</a>>, Chris Ong <<a href="mailto:Chris.Ong@microsoft.com">Chris.Ong@microsoft.com</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Date: </span><span style="font-size:10.0pt">02/23/2018 08:19 AM</span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Subject: </span><span style="font-size:10.0pt">RE: Redfish on OpenBMC</span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style="font-size:10.0pt">Thanks Ed, your agenda looks very good to me.</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>If it works for everybody, let's schedule a meeting on Monday 2/26 next week at 2pm PST as a kick-off, and we can discuss time/frequency, agenda, etc...during that meeting.</tt><br>
<br>
<br>
<br>
<tt>Regards,</tt><br>
<br>
<tt>Ali</tt><br>
<br>
<br>
<br>
<tt>-----Original Message-----</tt><br>
<br>
<tt>From: Tanous, Ed <<a href="mailto:ed.tanous@intel.com">ed.tanous@intel.com</a>>
</tt><br>
<br>
<tt>Sent: Thursday, February 22, 2018 2:31 PM</tt><br>
<br>
<tt>To: <a href="mailto:Michael.E.Brown@dell.com">Michael.E.Brown@dell.com</a>; Ali Larijani <<a href="mailto:alirhas@microsoft.com">alirhas@microsoft.com</a>>; Yugi Mani <<a href="mailto:yupalani@microsoft.com">yupalani@microsoft.com</a>></tt><br>
<br>
<tt>Cc: <a href="mailto:Paul.Vancil@dell.com">Paul.Vancil@dell.com</a>; <a href="mailto:hramasub@in.ibm.com">
hramasub@in.ibm.com</a>; <a href="mailto:Balaji.B.Rao@dell.com">Balaji.B.Rao@dell.com</a>;
<a href="mailto:bradleyb@fuzziesquirrel.com">bradleyb@fuzziesquirrel.com</a>; <a href="mailto:jwcarman@us.ibm.com">
jwcarman@us.ibm.com</a>; <a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a>;
<a href="mailto:pradeep.kumar36@tcs.com">pradeep.kumar36@tcs.com</a>; <a href="mailto:rolfb@us.ibm.com">
rolfb@us.ibm.com</a>; Chris Ong <<a href="mailto:Chris.Ong@microsoft.com">Chris.Ong@microsoft.com</a>></tt><br>
<br>
<tt>Subject: RE: Redfish on OpenBMC</tt><br>
<br>
<br>
<br>
<tt>Hah, you guys beat me to it.</tt><br>
<br>
<br>
<br>
<tt>My preference would be Monday at 4pm CST, 2PM PST, but I think I can make any of them that aren't Wednesday.</tt><br>
<br>
<br>
<br>
<tt>Also, If I'm reading this correct, this email only went out to a few of us. Once we have a time, we should post it to the main email list as well.</tt><br>
<br>
<tt>I'm also happy to host if Michael can't. BlueJeans seemed to work quite well for the TSC meetings, so I was thinking of doing that for sharing.</tt><br>
<br>
<br>
<br>
<br>
<br>
<tt>Here was the email I was typing up yesterday:</tt><br>
<br>
<br>
<br>
<tt>I’d like to start a Redfish working group for OpenBMC.</tt><br>
<br>
<br>
<br>
<tt>Primary goals of this working group will be:</tt><br>
<br>
<tt>1. Disseminate information on various redfish implementations for OpenBMC</tt><br>
<br>
<tt>2. Discuss technical requirements and implementation specifics</tt><br>
<br>
<tt>3. Make an effort to consolidate work on a “phosphor” OpenBMC redfish implementation</tt><br>
<br>
<br>
<br>
<tt>Initial Agenda for the first meeting will be</tt><br>
<br>
<br>
<br>
<tt>Initial introductions</tt><br>
<br>
<tt>Overview of existing implementations and work</tt><br>
<br>
<tt>Bmcweb implementation by Intel – Ed Tanous</tt><br>
<br>
<tt>Go-redfish implementation by Dell – Michael Brown</tt><br>
<br>
<tt>Redfish implementation by Microsoft – Ali Larijani/Yugi Mani/Bryan Kelly</tt><br>
<br>
<tt>Others?</tt><br>
<br>
<br>
<br>
<tt>Meeting time and frequency.</tt><br>
<br>
<tt>Daily/Weekly/monthly/quarterly?</tt><br>
<br>
<tt>What times work for the most people?</tt><br>
<br>
<br>
<br>
<tt>Consolidated requirements</tt><br>
<br>
<tt>Do we want/need them?</tt><br>
<br>
<tt>How will we handle them?</tt><br>
<br>
<tt>How will we discuss architectural changes?</tt><br>
<br>
<br>
<br>
<tt>Language choice</tt><br>
<br>
<tt>Python/C++/Golang preferences?</tt><br>
<br>
<br>
<br>
<tt>Other Topics?</tt><br>
<br>
<br>
<br>
<tt>> -----Original Message-----</tt><br>
<br>
<tt>> From: <a href="mailto:Michael.E.Brown@dell.com">Michael.E.Brown@dell.com</a> [<a href="mailto:Michael.E.Brown@dell.com">mailto:Michael.E.Brown@dell.com</a>]</tt><br>
<br>
<tt>> Sent: Thursday, February 22, 2018 2:03 PM</tt><br>
<br>
<tt>> To: <a href="mailto:alirhas@microsoft.com">alirhas@microsoft.com</a>; <a href="mailto:yupalani@microsoft.com">
yupalani@microsoft.com</a></tt><br>
<br>
<tt>> Cc: <a href="mailto:Paul.Vancil@dell.com">Paul.Vancil@dell.com</a>; <a href="mailto:hramasub@in.ibm.com">
hramasub@in.ibm.com</a>; <a href="mailto:Balaji.B.Rao@dell.com">Balaji.B.Rao@dell.com</a>;
</tt><br>
<br>
<tt>> <a href="mailto:bradleyb@fuzziesquirrel.com">bradleyb@fuzziesquirrel.com</a>; Tanous, Ed <<a href="mailto:ed.tanous@intel.com">ed.tanous@intel.com</a>>;
</tt><br>
<br>
<tt>> <a href="mailto:jwcarman@us.ibm.com">jwcarman@us.ibm.com</a>; <a href="mailto:openbmc@lists.ozlabs.org">
openbmc@lists.ozlabs.org</a>; </tt><br>
<br>
<tt>> <a href="mailto:pradeep.kumar36@tcs.com">pradeep.kumar36@tcs.com</a>; <a href="mailto:rolfb@us.ibm.com">
rolfb@us.ibm.com</a>; <a href="mailto:Chris.Ong@microsoft.com">Chris.Ong@microsoft.com</a></tt><br>
<br>
<tt>> Subject: RE: Redfish on OpenBMC</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Yes, I think it would be valuable to have a call. Do you have a time </tt><br>
<br>
<tt>> proposal? I can host from Dell skype.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Proposed time slots. Here are a variety that personally work ok for me.</tt><br>
<br>
<tt>> Votes?</tt><br>
<br>
<tt>> Monday 4pm CST</tt><br>
<br>
<tt>> Wed evening 9pm CST</tt><br>
<br>
<tt>> Thursday morning 9am CST</tt><br>
<br>
<tt>> Thursday 12pm CST</tt><br>
<br>
<tt>> Friday 8am CST</tt><br>
<br>
<tt>> --</tt><br>
<br>
<tt>> Michael</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> -----Original Message-----</tt><br>
<br>
<tt>> From: Ali Larijani [<a href="mailto:alirhas@microsoft.com">mailto:alirhas@microsoft.com</a>]</tt><br>
<br>
<tt>> Sent: Thursday, February 22, 2018 3:54 PM</tt><br>
<br>
<tt>> To: Brown, Michael E <<a href="mailto:Michael_E_Brown@Dell.com">Michael_E_Brown@Dell.com</a>>; Yugi Mani
</tt><br>
<br>
<tt>> <<a href="mailto:yupalani@microsoft.com">yupalani@microsoft.com</a>></tt><br>
<br>
<tt>> Cc: Vancil, Paul <<a href="mailto:Paul_Vancil@Dell.com">Paul_Vancil@Dell.com</a>>;
<a href="mailto:hramasub@in.ibm.com">hramasub@in.ibm.com</a>; Rao, </tt><br>
<br>
<tt>> Balaji B <<a href="mailto:Balaji_B_Rao@dell.com">Balaji_B_Rao@dell.com</a>>;
<a href="mailto:bradleyb@fuzziesquirrel.com">bradleyb@fuzziesquirrel.com</a>; </tt>
<br>
<br>
<tt>> <a href="mailto:ed.tanous@intel.com">ed.tanous@intel.com</a>; <a href="mailto:jwcarman@us.ibm.com">
jwcarman@us.ibm.com</a>; <a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a>;
</tt><br>
<br>
<tt>> <a href="mailto:pradeep.kumar36@tcs.com">pradeep.kumar36@tcs.com</a>; <a href="mailto:rolfb@us.ibm.com">
rolfb@us.ibm.com</a>; Chris Ong </tt><br>
<br>
<tt>> <<a href="mailto:Chris.Ong@microsoft.com">Chris.Ong@microsoft.com</a>></tt><br>
<br>
<tt>> Subject: RE: Redfish on OpenBMC</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Hi everybody,</tt><br>
<br>
<tt>> Can I propose we get together on a call to discuss a plan moving </tt><br>
<br>
<tt>> forward with Redfish implementation?</tt><br>
<br>
<tt>> Do you see any value of having a weekly sync up call?</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Thanks</tt><br>
<br>
<tt>> Ali</tt><br>
<br>
<tt>> -----Original Message-----</tt><br>
<br>
<tt>> From: Michael E Brown <<a href="mailto:Michael.E.Brown@dell.com">Michael.E.Brown@dell.com</a>></tt><br>
<br>
<tt>> Sent: Wednesday, February 14, 2018 11:37 AM</tt><br>
<br>
<tt>> To: Yugi Mani <<a href="mailto:yupalani@microsoft.com">yupalani@microsoft.com</a>></tt><br>
<br>
<tt>> Cc: Ali Larijani <<a href="mailto:alirhas@microsoft.com">alirhas@microsoft.com</a>>;
<a href="mailto:Paul.Vancil@dell.com">Paul.Vancil@dell.com</a>; </tt><br>
<br>
<tt>> <a href="mailto:hramasub@in.ibm.com">hramasub@in.ibm.com</a>; <a href="mailto:Michael.E.Brown@dell.com">
Michael.E.Brown@dell.com</a>; <a href="mailto:Balaji.B.Rao@dell.com">Balaji.B.Rao@dell.com</a>;
</tt><br>
<br>
<tt>> <a href="mailto:bradleyb@fuzziesquirrel.com">bradleyb@fuzziesquirrel.com</a>;
<a href="mailto:ed.tanous@intel.com">ed.tanous@intel.com</a>; <a href="mailto:jwcarman@us.ibm.com">
jwcarman@us.ibm.com</a>; </tt><br>
<br>
<tt>> <a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a>; <a href="mailto:pradeep.kumar36@tcs.com">
pradeep.kumar36@tcs.com</a>; <a href="mailto:rolfb@us.ibm.com">rolfb@us.ibm.com</a>;
</tt><br>
<br>
<tt>> Chris Ong <<a href="mailto:Chris.Ong@microsoft.com">Chris.Ong@microsoft.com</a>></tt><br>
<br>
<tt>> Subject: Re: Redfish on OpenBMC</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Stats for go-redfish running on Nuvoton Poleg. First, processor stats. </tt>
<br>
<br>
<tt>> Since we agreed on AST2500 as the baseline, I don't have one of those </tt>
<br>
<br>
<tt>> to do benchmarks. If somebody could run the benchmarks on an AST2500 </tt><br>
<br>
<tt>> that would be very helpful.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> $ cat /proc/cpuinfo</tt><br>
<br>
<tt>> processor : 0</tt><br>
<br>
<tt>> model name : ARMv7 Processor rev 1 (v7l)</tt><br>
<br>
<tt>> BogoMIPS : 1594.16</tt><br>
<br>
<tt>> Features : half thumb fastmult edsp tls</tt><br>
<br>
<tt>> CPU implementer : 0x41</tt><br>
<br>
<tt>> CPU architecture: 7</tt><br>
<br>
<tt>> CPU variant : 0x4</tt><br>
<br>
<tt>> CPU part : 0xc09</tt><br>
<br>
<tt>> CPU revision : 1</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> processor : 1</tt><br>
<br>
<tt>> model name : ARMv7 Processor rev 1 (v7l)</tt><br>
<br>
<tt>> BogoMIPS : 1594.16</tt><br>
<br>
<tt>> Features : half thumb fastmult edsp tls</tt><br>
<br>
<tt>> CPU implementer : 0x41</tt><br>
<br>
<tt>> CPU architecture: 7</tt><br>
<br>
<tt>> CPU variant : 0x4</tt><br>
<br>
<tt>> CPU part : 0xc09</tt><br>
<br>
<tt>> CPU revision : 1</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Hardware : NPCMX50 Chip family</tt><br>
<br>
<tt>> Revision : 0000</tt><br>
<br>
<tt>> Serial : 0000000000000000</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Go-redfish was checked out per the readme on </tt><br>
<br>
<tt>> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_superchalupa_go-2Dredfish&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=0V5mbubQ_XiZn1wp-lyxRsX_oDp_ZU7L7TB3taw6jnY&s=Jx5_QlMbwpuLrpxlue61p7uHJvoIZLLO-UiRz_Eohlk&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_superchalupa_go-2Dredfish&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=0V5mbubQ_XiZn1wp-lyxRsX_oDp_ZU7L7TB3taw6jnY&s=Jx5_QlMbwpuLrpxlue61p7uHJvoIZLLO-UiRz_Eohlk&e=</a> and
built like this:</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> $ BUILD_TAGS="spacemonkey" ./scripts/build-arm-obmc.sh</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Using the 'openssl' based HTTPS support because it's faster on 32-bit ARM.</tt><br>
<br>
<tt>> For x86 and 64-bit ARM, go native SSL is almost equal in performance. </tt>
<br>
<br>
<tt>> Read the readme for details.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> I use a benchmark tool called 'hey': <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_rakyll_hey&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=0V5mbubQ_XiZn1wp-lyxRsX_oDp_ZU7L7TB3taw6jnY&s=rj8l_-oJwvoZhuKeQBtdNhHF22_w46dLHGS5Dgwi1Pk&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_rakyll_hey&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=0V5mbubQ_XiZn1wp-lyxRsX_oDp_ZU7L7TB3taw6jnY&s=rj8l_-oJwvoZhuKeQBtdNhHF22_w46dLHGS5Dgwi1Pk&e=</a>, it
</tt><br>
<br>
<tt>> is a load generator. You can install it like this: "go get </tt><br>
<br>
<tt>> github.com/rakyll/hey". It will put 'hey' in $GOPATH/bin/. The </tt><br>
<br>
<tt>> go-redfish server supports the redfish standard X-Auth-Token as well </tt><br>
<br>
<tt>> as Basic auth. The benchmarks below are using basic auth in the </tt><br>
<br>
<tt>> interest of brevity, but it's also simple to benchmark tokens. The numbers don't appear much different.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Here is a run against the most complicated output currently implemented.</tt><br>
<br>
<tt>> This run is for 10 seconds, with the default concurrency of 50 </tt><br>
<br>
<tt>> parallel requests. The result is that the average request is 0.1588s </tt><br>
<br>
<tt>> and the server handles an average of 312 requests per second.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> $ hey -z 10s</tt><br>
<br>
<tt>> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__Administrator-3Apassword-4010.35.174.126-3A8443_redfish_v1_Chassis_A&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=0V5mbubQ_XiZn1wp-lyxRsX_oDp_ZU7L7TB3taw6jnY&s=39htxfH8ZCgtnHsY85iUfsJYfVNHk5Hy1w0u3N6S73s&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__Administrator-3Apassword-4010.35.174.126-3A8443_redfish_v1_Chassis_A&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=pH43eFdHEcrwxCxoIddEpbqszBn5JkXE8WT1-pzfg5U&m=0V5mbubQ_XiZn1wp-lyxRsX_oDp_ZU7L7TB3taw6jnY&s=39htxfH8ZCgtnHsY85iUfsJYfVNHk5Hy1w0u3N6S73s&e=</a></tt><br>
<br>
<tt>> 33</tt><br>
<br>
<tt>> /Thermal</tt><br>
<br>
<tt>> Summary:</tt><br>
<br>
<tt>> Total: 10.1230 secs</tt><br>
<br>
<tt>> Slowest: 1.9524 secs</tt><br>
<br>
<tt>> Fastest: 0.0051 secs</tt><br>
<br>
<tt>> Average: 0.1588 secs</tt><br>
<br>
<tt>> Requests/sec: 312.8521</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Response time histogram:</tt><br>
<br>
<tt>> 0.005 [1] |</tt><br>
<br>
<tt>> 0.200 [3062] |</tt></span><tt><span style="font-size:10.0pt;font-family:"Cambria Math",serif">∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>> 0.395 [31] |</tt><br>
<br>
<tt>> 0.589 [5] |</tt><br>
<br>
<tt>> 0.784 [9] |</tt><br>
<br>
<tt>> 0.979 [10] |</tt><br>
<br>
<tt>> 1.173 [9] |</tt><br>
<br>
<tt>> 1.368 [8] |</tt><br>
<br>
<tt>> 1.563 [5] |</tt><br>
<br>
<tt>> 1.758 [2] |</tt><br>
<br>
<tt>> 1.952 [25] |</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Latency distribution:</tt><br>
<br>
<tt>> 10% in 0.0840 secs</tt><br>
<br>
<tt>> 25% in 0.1159 secs</tt><br>
<br>
<tt>> 50% in 0.1374 secs</tt><br>
<br>
<tt>> 75% in 0.1576 secs</tt><br>
<br>
<tt>> 90% in 0.1748 secs</tt><br>
<br>
<tt>> 95% in 0.1874 secs</tt><br>
<br>
<tt>> 99% in 1.3962 secs</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Details (average, fastest, slowest):</tt><br>
<br>
<tt>> DNS+dialup: 0.0036 secs, 0.0000 secs, 1.2168 secs</tt><br>
<br>
<tt>> DNS-lookup: 0.0000 secs, 0.0000 secs, 0.0000 secs</tt><br>
<br>
<tt>> req write: 0.0000 secs, 0.0000 secs, 0.0007 secs</tt><br>
<br>
<tt>> resp wait: 0.1411 secs, 0.0049 secs, 1.1510 secs</tt><br>
<br>
<tt>> resp read: 0.0001 secs, 0.0000 secs, 0.0002 secs</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Status code distribution:</tt><br>
<br>
<tt>> [200] 3167 responses</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> The memory usage of the program under load (Resident size, IOW, RAM </tt><br>
<br>
<tt>> usage during load is roughly 16MB):</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> # cat /proc/$(pidof ocp-server.arm)/status</tt><br>
<br>
<tt>> Name: ocp-server.arm</tt><br>
<br>
<tt>> Umask: 0022</tt><br>
<br>
<tt>> State: S (sleeping)</tt><br>
<br>
<tt>> Tgid: 2737</tt><br>
<br>
<tt>> Ngid: 0</tt><br>
<br>
<tt>> Pid: 2737</tt><br>
<br>
<tt>> PPid: 2710</tt><br>
<br>
<tt>> TracerPid: 0</tt><br>
<br>
<tt>> Uid: 0 0 0 0</tt><br>
<br>
<tt>> Gid: 0 0 0 0</tt><br>
<br>
<tt>> FDSize: 256</tt><br>
<br>
<tt>> Groups: 0</tt><br>
<br>
<tt>> VmPeak: 1167212 kB</tt><br>
<br>
<tt>> VmSize: 1167212 kB</tt><br>
<br>
<tt>> VmLck: 0 kB</tt><br>
<br>
<tt>> VmPin: 0 kB</tt><br>
<br>
<tt>> VmHWM: 16924 kB</tt><br>
<br>
<tt>> VmRSS: 16844 kB</tt><br>
<br>
<tt>> RssAnon: 9200 kB</tt><br>
<br>
<tt>> RssFile: 1788 kB</tt><br>
<br>
<tt>> RssShmem: 5856 kB</tt><br>
<br>
<tt>> VmData: 395108 kB</tt><br>
<br>
<tt>> VmStk: 136 kB</tt><br>
<br>
<tt>> VmExe: 6304 kB</tt><br>
<br>
<tt>> VmLib: 2792 kB</tt><br>
<br>
<tt>> VmPTE: 130 kB</tt><br>
<br>
<tt>> VmPMD: 0 kB</tt><br>
<br>
<tt>> VmSwap: 0 kB</tt><br>
<br>
<tt>> Threads: 45</tt><br>
<br>
<tt>> SigQ: 0/3577</tt><br>
<br>
<tt>> SigPnd: 0000000000000000</tt><br>
<br>
<tt>> ShdPnd: 0000000000000000</tt><br>
<br>
<tt>> SigBlk: fffffffe7bfa7a25</tt><br>
<br>
<tt>> SigIgn: 0000000000000000</tt><br>
<br>
<tt>> SigCgt: ffffffffffc1feff</tt><br>
<br>
<tt>> CapInh: 0000000000000000</tt><br>
<br>
<tt>> CapPrm: 0000003fffffffff</tt><br>
<br>
<tt>> CapEff: 0000003fffffffff</tt><br>
<br>
<tt>> CapBnd: 0000003fffffffff</tt><br>
<br>
<tt>> CapAmb: 0000000000000000</tt><br>
<br>
<tt>> NoNewPrivs: 0</tt><br>
<br>
<tt>> Cpus_allowed: 3</tt><br>
<br>
<tt>> Cpus_allowed_list: 0-1</tt><br>
<br>
<tt>> voluntary_ctxt_switches: 92</tt><br>
<br>
<tt>> nonvoluntary_ctxt_switches: 21</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> The binary size is 10MB uncompressed and 2MB compressed (xz level 9)</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> $ cat ocp-server.arm | xz -9 -c > ocp-server.arm.xz $ ls -l </tt><br>
<br>
<tt>> ocp-server.arm* - rwxrwxr-x 1 michael_e_brown michael_e_brown 11169052 </tt>
<br>
<br>
<tt>> Feb 14 13:14 ocp- server.arm</tt><br>
<br>
<tt>> -rw-rw-r-- 1 michael_e_brown michael_e_brown 2712208 Feb 14 13:26 </tt><br>
<br>
<tt>> ocp- server.arm.xz</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> The source is currently sitting at under 5k LoC implementing a few </tt><br>
<br>
<tt>> proof of concept openbmc implementations calling DBUS, as well as a simulation.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Concurrency:</tt><br>
<br>
<tt>> - Highly concurrent. On ARM serves >300 requests per second. On X86, </tt><br>
<br>
<tt>> goes up to about 3k requests per second</tt><br>
<br>
<tt>> - For individual requests: can concurrently get data from multiple </tt><br>
<br>
<tt>> data sources and runs all the plugins for a redfish resource in </tt><br>
<br>
<tt>> parallel</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Deterministic:</tt><br>
<br>
<tt>> - The design should be fairly deterministic.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Cached:</tt><br>
<br>
<tt>> - Completely flexible here. The default model is caching the data, but </tt>
<br>
<br>
<tt>> it's also supported to make dbus calls per request (though that's not </tt>
<br>
<br>
<tt>> really recommended). Currently it caches sensor results and refreshes </tt>
<br>
<br>
<tt>> those at a fixed interval, though that could easily be changed.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> Platform dependent/independent:</tt><br>
<br>
<tt>> - Core is completely platform independent.</tt><br>
<br>
<tt>> - Working on an OCP profile implementation that also has platform </tt><br>
<br>
<tt>> independent + platform specific hooks. Currently in place are </tt><br>
<br>
<tt>> simulation implementation plus openbmc dbus implementation for sensors </tt>
<br>
<br>
<tt>> (temperature now, working fans next).</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> DMTF support:</tt><br>
<br>
<tt>> - In progress. Help needed.</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> --</tt><br>
<br>
<tt>> Michael</tt><br>
<br>
<tt>> </tt><br>
<br>
<tt>> On Wed, Feb 07, 2018 at 03:48:41AM +0000, Yugi Mani wrote:</tt><br>
<br>
<tt>> > Here are some more requirements based on our experience with Redfish:</tt><br>
<br>
<tt>> > 1. Concurrency</tt><br>
<br>
<tt>> > Web Server and Framework should be able to serve multiple GET </tt><br>
<br>
<tt>> > requests</tt><br>
<br>
<tt>> at a time.</tt><br>
<br>
<tt>> > POST/PATCH/PUT/DELETE requests can be sequential.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 2. Deterministic</tt><br>
</span><br>
<tt><span style="font-size:10.0pt">> > Service should be time deterministic, both boot time and run time.</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>> > Concurrency shall not impact deterministic property of the service.</tt><br>
<br>
<tt>> > All requests shall be responded (success/failure) within acceptable </tt>
<br>
<br>
<tt>> > time</tt><br>
<br>
<tt>> limits.</tt><br>
<br>
<tt>> > Where some requests cannot be completed within time limits, service </tt>
<br>
<br>
<tt>> > shall respond with status and expected time to complete.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 3. Cached Data</tt><br>
<br>
<tt>> > Data shall be cached by Redfish service and updated on dbus signals.</tt><br>
<br>
<tt>> > Collecting required information on demand adversely impacts</tt><br>
<br>
<tt>> performance.</tt><br>
<br>
<tt>> > Redfish should rather cache the information and keep updating its </tt><br>
<br>
<tt>> > cache on notification from dbus that the property(ies) of interest </tt><br>
<br>
<tt>> > has been</tt><br>
<br>
<tt>> modified.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 4. Platform dependent/independent layer Shall provide a clear </tt><br>
<br>
<tt>> > isolation between core vs platform properties.</tt><br>
<br>
<tt>> > Can consider object oriented approach for platform & oem layer to </tt><br>
<br>
<tt>> > override core methods and objects. Customized hooks and handlers can </tt>
<br>
<br>
<tt>> > be provided by platform layer while the data model between layers is </tt>
<br>
<br>
<tt>> > maintained consistent across platforms.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 5. DMTF Support</tt><br>
<br>
<tt>> > Redfish have quite a lot of gaps in some of the basic requirements </tt><br>
<br>
<tt>> > of a</tt><br>
<br>
<tt>> BMC.</tt><br>
<br>
<tt>> > a) FRU & FRU Collection Schema</tt><br>
<br>
<tt>> > b) Sensor & Sensor Collection Schema</tt><br>
<br>
<tt>> > c) Component Firmware Update (PSU, BIOS, CPLD, etc)</tt><br>
<br>
<tt>> > d) Master Write-Read</tt><br>
<br>
<tt>> > e) Clear PSU Faults</tt><br>
<br>
<tt>> > We need DMTF to actively add/update Redfish schemas that are</tt><br>
<br>
<tt>> fundamental to any BMC.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 7. Error Codes</tt><br>
<br>
<tt>> > Redfish LogEntry schema doesn’t offer a placeholder for error codes </tt>
<br>
<br>
<tt>> > that automation tools can read to categorize the events and trigger</tt><br>
<br>
<tt>> actuators.</tt><br>
<br>
<tt>> > One option is to repurpose OEM field.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 8. Pagination</tt><br>
<br>
<tt>> > Event logs can get too big and paginated view is helpful</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 9. Filtering</tt><br>
<br>
<tt>> > Query parameter to filter the response limited to certain criteria</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 10. Anchors</tt><br>
<br>
<tt>> > Schemas like Chassis and Manager have a bunch of properties that not </tt>
<br>
<br>
<tt>> > all requests might be interested in.</tt><br>
<br>
<tt>> > It is better to be able to request just a fragment of a resource using ‘#’.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > 11. Rate Limiting</tt><br>
<br>
<tt>> > Server shall return HTTP 429 when number of requests cross max limit</tt><br>
<br>
<tt>> permissible from a client.</tt><br>
<br>
<tt>> > We need some protection against Denial of Service.</tt><br>
<br>
<tt>> ></tt><br>
<br>
<tt>> > -Yugi</tt><br>
<br>
<br>
</span><br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>