<html><head><META http-equiv="Content-Type" content="text/html;charset=utf-8"></head><body><div id="content" contenteditable="true" spellcheck="true" autocorrect="true" autocapitalize="true" style="font-family: Helvetica;">Redfish is the way to go. We've talked a lot about it. Timing and knowledge was a couple of reasons why we down the proprietary path. As such we insured that while our rest interface was not redfish we did not make our implementation completely incompatible. I think we have learned a lot about redfish and rest and requirements since we started that shows it as winner. I think it is only a matter of time before we move. I think after April it should be the main focus. <div><br></div><div><br></div><div>Chris<br><div><br><br>Sent from my iPhone using IBM Verse<br><br><hr>On Feb 11, 2016, 1:14:38 AM, "Stewart Smith" <stewart@linux.vnet.ibm.com> wrote:<br><div style="margin-left: 15px;" id="MaaS360PIMSDKOriginalMessageId">So, it seems that the standard RESTful API to BMCs is RedFish. With HP,<br>Intel, Dell and others on board (with at least HP iLO shipping product).<br>There's already an OpenStack Ironic driver for Redfish and a bunch of<br>other tooling.<br>It feels that not going this route would paint us into a corner of<br>irrelevance and being the tricky platform to deal with.<br>See https://www.dmtf.org/standards/redfish<br>thoughts?<br>-- <br>Stewart Smith<br>OPAL Architect, IBM.<br>_______________________________________________<br>openbmc mailing list<br>openbmc@lists.ozlabs.org<br>https://lists.ozlabs.org/listinfo/openbmc<br></div></div></div></div><BR>
</body></html>