Jump to content

Redfish (specification): Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Bcornec (talk | contribs)
No edit summary
Bcornec (talk | contribs)
No edit summary
Line 43: Line 43:
* [https://git.openstack.org/cgit/openstack/sushy Sushy]
* [https://git.openstack.org/cgit/openstack/sushy Sushy]


== Features ==

Redfish allows the retrieval of hardware data such as asset info, platform identification, firmware versions, health state, temperature, fans, power supplies, power consumption, event logs, CPU, RAM, NIC and storage details,

Redfish allows in addition the modification of a subset of the data it can retrieve such as Boot order, power thresholds, BMC settings and user accounts, and to perform actions such as power cycle/reboot of the system.

It has a large scope for hardware architecture support, managing simple servers, blade enclosures and servers, multi-node servers (such as the HPE Moonshot cartridges), and has been designed to be extendable as needed. It also provides support for private extensions (not yet standardized e.g.) in an Oem schema (similar in function to the private part of the MIB for the SNMP protocol).

It is now used by both proprietary software (such as HPE OneView) as well as FLOSS ones<ref>{{cite web|title=Open Source Projects Using DMTF Technologies|url=https://www.dmtf.org/standards/opensource|accessdate=3 February 2019}}</ref>
== See also ==
== See also ==
* [[Intelligent Platform Management Interface|IPMI]]
* [[Intelligent Platform Management Interface|IPMI]]

Revision as of 00:52, 7 February 2019

This sandbox is in the article namespace. Either move this page into your userspace, or remove the {{User sandbox}} template.

Redfish
AbbreviationRedfish
StatusPublished
Year started2014
OrganizationDistributed Management Task Force
Related standardsSystems Management Architecture for Server Hardware
DomainData center management
Websitewww.dmtf.org/standards/redfish

The Redfish standard is a suite of specifications that deliver an industry standard protocol providing Software Defined Management for Converged infrastructure.

Distributed Management Task Force developed Redfish Standard is a suite of specifications that deliver architectural semantics, industry standard protocols and profiles to unify the management of the data center. Through the development of conformance testing programs, the Redfish Forum will extend these capabilities by helping deliver additional compatibility in cross-platform servers.

History

The Redfish standard has been elaborated under the SPMF umbrella at the DMTF in 2014. The first specification with base models (1.0) was published in August 2015[1]. In 2016, Models for BIOS, disk drives, memory, storage, volume, endpoint, fabric, switch, PCIe device, zone, software/firmware inventory & update, multi-function NICs), host interface (KCS replacement) and privilege mapping were added. In 2017, Models for Composability, Location and errata were added[2]. There is WIP for Telemetry, Ethernet Switching, DCIM, and OCP & Profiles.

In August 2016, SNIA released a first model for network storage services (Swordfish[3]), an extension of the Redfish specification.

Industry adoption

Redfish support on server

  • DELL iDRAC BMC with Minimum iDRAC 7/8 FW 2.40.40.40, iDRAC9 FW 3.00.00.0
  • HPE iLO BMC with minimum iLO4 FW 2.30, iLO5
  • HPE Moonshot BMC with minimum FW 1.41
  • Supermicro X10 BMC with minimum FW 3.0 and X11 with minimum FW 1.0

Redfish support on BMC

Software using Redfish APIs

Redfish libraries and tools

Features

Redfish allows the retrieval of hardware data such as asset info, platform identification, firmware versions, health state, temperature, fans, power supplies, power consumption, event logs, CPU, RAM, NIC and storage details,

Redfish allows in addition the modification of a subset of the data it can retrieve such as Boot order, power thresholds, BMC settings and user accounts, and to perform actions such as power cycle/reboot of the system.

It has a large scope for hardware architecture support, managing simple servers, blade enclosures and servers, multi-node servers (such as the HPE Moonshot cartridges), and has been designed to be extendable as needed. It also provides support for private extensions (not yet standardized e.g.) in an Oem schema (similar in function to the private part of the MIB for the SNMP protocol).

It is now used by both proprietary software (such as HPE OneView) as well as FLOSS ones[5]

See also

References

  1. ^ "DMTF signs off Redfish server management spec v 1.0". Retrieved 29 January 2019.
  2. ^ "DMTF announces Redfish API advancements". Retrieved 29 January 2019.
  3. ^ "How to get started with the Swordfish storage management standard". Retrieved 29 January 2019.
  4. ^ "BMC Firmware Products". Retrieved 29 January 2019.
  5. ^ "Open Source Projects Using DMTF Technologies". Retrieved 3 February 2019.