openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Chassis reset
Date: Wed, 23 Sep 2020 16:29:03 -0700	[thread overview]
Message-ID: <4e78f884-a256-6ae7-fefd-ba3c6cdc0d52@linux.intel.com> (raw)
In-Reply-To: <CACWQX827ftfPo-D9gBtDm_bdp7xq71c+hkxfHRVvzVqPoSfztg@mail.gmail.com>



On 9/23/2020 3:35 PM, Ed Tanous wrote:
> On Wed, Sep 23, 2020 at 3:01 PM Bills, Jason M
> <jason.m.bills@linux.intel.com> wrote:
>>
>>
>>
>> On 9/23/2020 2:42 PM, Patrick Williams wrote:
>>>
>>> I'm not understanding what you mean by "come up with an API to steer the
>>> Redfish..."  I think everything is specified here at a dbus level.  The
>>> issue is figuring out the appropriate Redfish model of
>>> Chassis/ComputerSystem objects (along with the included Resource.Reset
>>> types).  To a casual reader, who hasn't been involved much in Redfish
>>> implementation, the current mapping of these ResetTypes seems fairly
>>> arbitrary.
>>>
>>> With CIM there use to be these Profile documents that showed "the right
>>> way" to fit all these pieces together.  Does that not exist with
>>> Redfish?  How does any external application consume Redfish in a
>>> consistent way?
>>
>> I'm not sure it helps with the overall consistency question, but for
>> OpenBMC, we defined our mapping of Redfish ResetType values to Chassis
>> and Host State Transitions on D-Bus, here:
>> https://github.com/openbmc/docs/blob/838fa962b73deb1ef7908ee8dfa1203fa5263517/designs/state-management-and-external-interfaces.md#proposed-design.
>>
>> This is what x86-power-control aspires to match and I think what led to
>> creating new D-Bus interfaces for the chassis_system and AC power state
>> changes (since we didn't want to break this mapping).
> 
> Sounds reasonable, it just makes things slightly more complex for
> Redfish, as now there's two things that could be a redfish Chassis
> reset.  Not a huge deal.
> 
>>
>> Perhaps we need to separate the Host and Chassis on the Redfish side and
>> extend the D-Bus interfaces to support all the needed ResetTypes?
>>>
> 
> I'm not following.  There's a Host (ie ComputerSystem) and Chassis in
> redfish today.  How would we separate them further?
I meant in the table here: 
https://github.com/openbmc/docs/blob/838fa962b73deb1ef7908ee8dfa1203fa5263517/designs/state-management-and-external-interfaces.md#proposed-design.

Extend it to include both Chassis and System ResetType values and map 
them all to the correct State Transition on D-Bus.

> 

  reply	other threads:[~2020-09-23 23:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 19:50 Chassis reset Vijay Khemka
2020-09-18 21:38 ` Ed Tanous
2020-09-18 23:28   ` Vijay Khemka
2020-09-19  0:17     ` Ed Tanous
2020-09-22 19:16       ` Vijay Khemka
2020-09-23  0:17         ` Ed Tanous
2020-09-23  5:45           ` Vijay Khemka
2020-09-23 19:10             ` Patrick Williams
2020-09-23 19:26               ` Ed Tanous
2020-09-23 19:55                 ` Vijay Khemka
2020-09-23 20:21                 ` Patrick Williams
2020-09-23 21:12                   ` Ed Tanous
2020-09-23 21:42                     ` Patrick Williams
2020-09-23 21:59                       ` Bills, Jason M
2020-09-23 22:35                         ` Ed Tanous
2020-09-23 23:29                           ` Bills, Jason M [this message]
2020-09-23 22:31                       ` Ed Tanous
2020-09-24  1:59                         ` Vijay Khemka
2020-09-24  2:24                           ` Ed Tanous
2020-09-29 22:13                             ` Vijay Khemka
2020-09-29 22:22                               ` Ed Tanous
2020-09-29 23:29                                 ` Vijay Khemka
2020-09-24  3:08                       ` Joseph Reynolds
2020-09-24  1:48                     ` Vijay Khemka

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=4e78f884-a256-6ae7-fefd-ba3c6cdc0d52@linux.intel.com \
    --to=jason.m.bills@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).