public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Abner Chang" <abner.chang@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Nickle (HPS SW)" <nickle.wang@hpe.com>,
	"Chen, Aaron" <aaron.chen@hpe.com>,
	"Chang, Abner (HPS SW/FW Technologist)" <abner.chang@hpe.com>
Subject: [RFC] EDK2 Redfish client is upstream to edk2-staging
Date: Thu, 4 Nov 2021 14:34:53 +0000	[thread overview]
Message-ID: <CS1PR8401MB114468611FA75565F0300140FF8D9@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM> (raw)

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

Hi, EDK2 community,

Just FYI, base on RedfishPkg which is the EDK2 Redfish foundation, we upstream EDK2 Redfish Client implementation to edk2-staging repo.


In case you don’t know this project, below is the information regarding edk2 Redfish foundation,

https://github.com/tianocore/edk2/blob/master/RedfishPkg/Readme.md

And the link to the branch of EDK2 Redfish client implementation we just upstream to edk2-staging.

https://github.com/tianocore/edk2-staging/blob/edk2-redfish-client/RedfishClientPkg/Readme.md



The goal of EDK2 Redfish client is to provide an open-source solution for the interoperability of platform BIOS configuration using Redfish. On EDK2, the implementation is to map HII configuration to the standardized Redfish property defined in the Redfish schema. This reduces the OEM proprietary Redfish BIOS properties (BIOS Attribute) which are used to configure the same setting on the platforms produced by different OEMs. This also facilitates having a common server management tool that can configure platform BIOS settings on the different brands of server in out-of-band.

You can take a look at the above links if you are interested in this project, evaluate it, and you are welcome to report the issues or comments.


Thanks and regards,

Abner


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

                 reply	other threads:[~2021-11-04 14:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-list 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=CS1PR8401MB114468611FA75565F0300140FF8D9@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM \
    --to=devel@edk2.groups.io \
    /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