Redfish or Irrelevance?

Redfish or Irrelevance?

[Stewart Smith]

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.

Re: Redfish or Irrelevance?

[Norman James]

[-- Attachment #1.1: Type: text/plain, Size: 1142 bytes --]


There is no question that OpenBMC should support Redfish in the near
future.    We were hoping someone outside might help implement Redfish as
OpenBMC got traction.


Regards,
Norman James
IBM - POWER Systems Architect
Phone: 1-512-286-6807 (T/L: 363-6807)
Internet: njames@us.ibm.com




From:	Stewart Smith <stewart@linux.vnet.ibm.com>
To:	openbmc <openbmc@lists.ozlabs.org>
Date:	02/11/2016 01:14 AM
Subject:	Redfish or Irrelevance?
Sent by:	"openbmc" <openbmc-bounces+njames=us.ibm.com@lists.ozlabs.org>



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@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/openbmc


[-- Attachment #1.2: Type: text/html, Size: 2247 bytes --]

[-- Attachment #2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]

Re: Redfish or Irrelevance?

[Chris Austen]

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

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@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@lists.ozlabs.org
    https://lists.ozlabs.org/listinfo/openbmc

[-- Attachment #2: Type: text/html, Size: 1990 bytes --]