From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Chris Austen <austenc@us.ibm.com>, openbmc@lists.ozlabs.org
Subject: Re: OpenBMC and Redfish - intro
Date: Wed, 21 Jun 2017 14:07:03 +1000 [thread overview]
Message-ID: <87bmpi2dco.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <OFFA529A42.5FDE064B-ON86258145.00576CCE-86258145.005CA593@notes.na.collabserv.com>
Chris Austen <austenc@us.ibm.com> writes:
> Well that is a loaded subject line!
>
> We have talked for a while about wanting to support the DMTF Redfish REST
> interface. Support would allow operators to adhere to a growing industry
> standard and allow communities such as OCP (Open Compute Project) a
> platform to put in to practice their profiles. I think Operators and API
> developers would also appreciate the interface.
AS someone who's likely to consume it (via our test infrastructure for
OpenPOWER firmware), I'm really keen to see it.
I know at least one other BMC implementation we interact with is doing
RedFish, and it'd be good to have only one set of code to talk to BMCs,
rather than the current situation.
--
Stewart Smith
OPAL Architect, IBM.
prev parent reply other threads:[~2017-06-21 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 16:51 OpenBMC and Redfish - intro Chris Austen
2017-06-21 4:07 ` Stewart Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmpi2dco.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=austenc@us.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.