openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Reynolds <jrey@linux.ibm.com>
To: Patrick Williams <patrick@stwcx.xyz>, Ed Tanous <ed@tanous.net>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Vijay Khemka <vijaykhemka@fb.com>
Subject: Re: Chassis reset
Date: Wed, 23 Sep 2020 22:08:29 -0500	[thread overview]
Message-ID: <c1252b83-ce94-40d5-9bfe-62e796c96af9@linux.ibm.com> (raw)
In-Reply-To: <20200923214237.GV6152@heinlein>

On 9/23/20 4:42 PM, Patrick Williams wrote:
> On Wed, Sep 23, 2020 at 02:12:10PM -0700, Ed Tanous wrote:
>> On Wed, Sep 23, 2020 at 1:21 PM Patrick Williams <patrick@stwcx.xyz> wrote:
>>> On Wed, Sep 23, 2020 at 12:26:58PM -0700, Ed Tanous wrote:
>>>> On Wed, Sep 23, 2020 at 12:10 PM Patrick Williams <patrick@stwcx.xyz> wrote:
>>>>> On Wed, Sep 23, 2020 at 05:45:51AM +0000, Vijay Khemka wrote:
>>>>>> Yes I have 2 chassis instance xyz/openbmc_project/chassis0 and xyz/openbmc_project/chassis_system0.
>>>>>> Later one is used for AC reset.
>>>>> Can we do a query to see if 'chassis_system0' exists and use it first
>>>>> and then 'chassis0' if not?
>>>>
...snip...
> 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 don't know much about this area.  I understand Redfish is always 
looking for more system configurations:
https://redfish.dmtf.org/redfish/mockups/v1

Otherwise, you could post this question here:
https://redfishforum.com/board/1/protocol-specification

- Joseph


  parent reply	other threads:[~2020-09-24  3:09 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
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 [this message]
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=c1252b83-ce94-40d5-9bfe-62e796c96af9@linux.ibm.com \
    --to=jrey@linux.ibm.com \
    --cc=ed@tanous.net \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    --cc=vijaykhemka@fb.com \
    /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).