Redfish or Irrelevance?
Chris Austen
austenc at us.ibm.com
Fri Feb 12 00:36:36 AEDT 2016
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.
Chris
Sent from my iPhone using IBM Verse
On Feb 11, 2016, 1:14:38 AM, "Stewart Smith" <stewart at linux.vnet.ibm.com> wrote:
So, it seems that the standard RESTful API to BMCs is RedFish. With HP,
Intel, Dell and others on board (with at least HP iLO shipping product).
There's already an OpenStack Ironic driver for Redfish and a bunch of
other tooling.
It feels that not going this route would paint us into a corner of
irrelevance and being the tricky platform to deal with.
See https://www.dmtf.org/standards/redfish
thoughts?
--
Stewart Smith
OPAL Architect, IBM.
_______________________________________________
openbmc mailing list
openbmc at lists.ozlabs.org
https://lists.ozlabs.org/listinfo/openbmc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160211/f5e83eb1/attachment-0001.html>
More information about the openbmc
mailing list