All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Redfish Mapped Commands
Date: Tue, 4 Aug 2020 13:06:18 -0700	[thread overview]
Message-ID: <adda0f71-217c-70e9-4dd6-d7300a018e48@linux.intel.com> (raw)
In-Reply-To: <SG2PR04MB30935D495AA522C5C4742004E14A0@SG2PR04MB3093.apcprd04.prod.outlook.com>



On 8/4/2020 7:53 AM, Jayashree D wrote:
> Hi All,
> 
> I am about to test redfish commands for the following features.
> 
> Can anyone point me the related redfish commands for those features?
> 
> 1. We are using X86 power control, is there any compatible commands in 
> redfish to test?
 From the system resource (/redfish/v1/Systems/system), you can find the 
ComputerSystem.Reset action which can be used to initiate resets:
     "Actions": {
         "#ComputerSystem.Reset": {
             "@Redfish.ActionInfo": 
"/redfish/v1/Systems/system/ResetActionInfo",
             "target": 
"/redfish/v1/Systems/system/Actions/ComputerSystem.Reset"
         }
     },

The allowable values for ResetType are here: 
/redfish/v1/Systems/system/ResetActionInfo.

> 
> 2. FRU information.
> 
> 3. obmc-console-client to connect the host.
> 
> 4. To set, start and stop the fan speed controller.
> 
> 5. Host Logger.
If you mean the event log, it is here: 
/redfish/v1/Systems/system/LogServices/EventLog.

> 
> 6. LED
> 
> 7. BIOS Upgrade
> 
> 8. Settings Manager
> 
> Thanks,
> 
> Regards,
> 
> Jayashree
> 
> ::DISCLAIMER::
> ------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be 
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
> may contain viruses in transmission. The e mail and its contents (with 
> or without referred errors) shall therefore not attach any liability on 
> the originator or HCL or its affiliates. Views or opinions, if any, 
> presented in this email are solely those of the author and may not 
> necessarily reflect the views or opinions of HCL or its affiliates. Any 
> form of reproduction, dissemination, copying, disclosure, modification, 
> distribution and / or publication of this message without the prior 
> written consent of authorized representative of HCL is strictly 
> prohibited. If you have received this email in error please delete it 
> and notify the sender immediately. Before opening any email and/or 
> attachments, please check them for viruses and other defects.
> ------------------------------------------------------------------------

  reply	other threads:[~2020-08-04 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 14:53 Redfish Mapped Commands Jayashree D
2020-08-04 20:06 ` Bills, Jason M [this message]
2020-08-05  7:24 Jayashree D
2020-08-10 16:39 Jayashree D

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=adda0f71-217c-70e9-4dd6-d7300a018e48@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 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.