Redfish-based API tool for managing bare-metal systems via the Redfish API
[I’m also posting this so any Redfish exploiters realize that this name is already taken. 🙂 There’s actually a few dozen interesting Redfish tools/libraries that I need to make posts on.]
One of the difficulties of using the Redfish host api is the translation of the SMBIOS data above into meaningful application configuration data.[…]redfish-finder: parses the smbios data for Redfish access, translates the device specification to an OS interface name, uses NetworkManager to configure the network interface with the appropriate settings, and adds an entry to /etc/hosts mapping the name redfish-localhost to the Discovered Redfish service address.[…]
DMTF Redfish has updated their schema and specs.
New Redfish Schema, Specification and Developer Resources Now Available. New items just released include:
* 2018.1 Redfish Schema Bundle: A .zip file that contains the current versions of all Redfish schema, including a new ExternalAccountProvider schema for LDAP/ActiveDirectory support. Additional schema updates enable support for Server Sent-Eventing (SSE), provide additional information for Processors and Settings, and more.
* Redfish Specification v1.5.0: Adds new support for SSE, enabling the streaming of events to web-based GUIs and other clients. Other specification updates in this release include a mechanism for specifying deterministic behavior for the application of Create, Delete or Action (POST) operations.
* Redfish Resource and Schema Guide: New for 2018, this human-readable guide to the Redfish Schema is designed to help educate users of Redfish. Application developers and DevOps personnel creating client-side software to communicate with a Redfish service, as well as other consumers of the API, will benefit from the explanations in this resource.
* Redfish 2018.1 Overview: Provides detailed descriptions of each revision in the latest version of the Redfish Schema and Specification.
DMTF and PICMG Form Alliance
DMTF and the PCI Industrial Computer Manufacturer Group (PICMG) have formed an alliance to help ensure the two organizations’ standards are coordinated and aligned in the Industrial Internet of Things (IIoT) domain.
Expect to see Redfish listed as 10th entry here shortly, I am guessing:
The DMTF, NVM Express, Inc. and SNIA have formed a new three-way alliance to coordinate standards for managing SSD storage devices. […] In addition to SNIA’s Swordfish and DMTF’s Redfish, the alliance’s collaborative work will include the following standards:
* NVM Express™(NVMe™) is the register interface and command set for PCI Express attached storage with industry standard software available for numerous operating systems. The NVM Express™Management Interface (NVMe-MI™) is the command set and architecture for management of NVM Express storage (e.g., discovering, monitoring, and updating NVMe devices using a BMC).
* DMTF’s Management Component Transport Protocol (MCTP) is a protocol and Platform Level Data Model (PLDM) is a low-level data model defined by the DMTF Platform Management Components Intercommunications (PMCI) Working Group (https://www.dmtf.org/standards/pmci) . MCTP is designed to support communications between different intelligent hardware components that make up a platform management subsystem that provides monitoring and control functions inside a managed system.
ISO/IEC 30115:2018: The Redfish Scalable Platforms Management API (“Redfish”) is a new specification that uses RESTful interface semantics to access data defined in model format to perform out-of-band systems management. It is suitable for a wide range of servers, from stand-alone servers to rack mount and bladed environments but scales equally well for large scale cloud environments. There are several out-of-band systems management standards (defacto and de jour) available in the industry. They all either vary widely in implementation, were developed for single server embedded environments or have their roots in antiquated software modeling constructs. There is no single industry standard that is simple to use, based on emerging programming standards, embedded friendly and capable of meeting large scale data center & cloud needs.
[…]Redfish-JSON-C-Struct-Converter is a C client library which used to convert Redfish resource in JSON text format to C structure and vice versa. The functions in Redfish-JSON-C-Struct-Converter library provides the C language friendly structure which can be easily utilized in C programs. Bindings also provided on top of C source/header files for different computer languages and build environments, such as UEFI EDK2 environment or akin to the bindings for Java and Python in libredfish library. Each C file is a converter for the specific version of Redfish schema released by SPFM. For example, ServiceRoot.v1_2_0.c under /ServiceRoot/ServiceRoot.v1_2_0 provides functions to convert ServiceRoot.v1_2_0.ServiceRoot property to predefined RedfishServiceRootV1_2_0_CS C structure. It also provides functions to convert RedfishServiceRootV1_2_0_CS C structure to JSON text file. All C files under /src are built into a single library. Other programs which built with Redfish-JSON-C-Struct-Converter library must links with this library and invokes the conversion functions as it needs.[…]
The DMTF has released its new Platform Level Data Model (PLDM) for Redfish® Device Enablement Specification  as a Work in Progress, inviting public review and comment. This standard enables a management controller to present Redfish -conformant management of I/O adapters in a server, without the need for code specific to each adapter family/vendor/model. PLDM for Redfish Device Enablement describes the operation and format of request messages (also referred to as commands) and response messages, designed to be delivered using PLDM messaging. Using Redfish, messages are generated by a Redfish client through interactions with a user or a script, and communicated via JSON over HTTP or HTTPS to a management controller. Using the new standard, the management controller will encode the message into a binary format (Binary Encoded JSON, or BEJ) and communicate it using PLDM to an appropriate device for servicing. The device processes the message and returns the response back using PLDM to the management controller, again in binary format. The management controller then decodes the response and constructs a standard Redfish response in JSON over HTTP or HTTPS for delivery back to the client. PLDM for Redfish Device Enablement is developed by the DMTF’s Platform Management Components Intercommunications (PMCI) Working Group , which defines standards to address “inside the box” communication and functional interfaces. It can be used in conjunction with other PMCI standards, such as the PLDM Firmware Update Specification, to provide a comprehensive, common architecture for improved communication between management subsystem components. The new WIP release is the latest example of the ongoing hard work and close collaboration between DMTF Working Groups (including PMCI, SMBIOS and SPMF) to seamlessly address both internal- and external-facing interfaces and protocols for system management.
” OpenUSM – Let Docker Containers Manage Your Datacenter
OpenUSM is a suite of tools and utilities which configures and manage the lifecycle of system management. OpenUSM has a capability to perform the following functions:
* BIOS Token Change
* Firmware Update
[…]Version 2017.2 of the Redfish Schema and version 1.3.0 of the Redfish Specification are now available for public download. The goal of Redfish is to publish a standard API to meet customer demands for simple and secure management in modern Software Defined Data Center (SDDC) environments, and it was recently announced the standard is being expanded to address Data Center Infrastructure Management (DCIM), as well. The latest release includes updates to the Base Message Registry and more.[…]
Note to DMTF PR team: please stop inserting “(http://www.dmtf.org/standards/redfish)” URL after every use of “Redfish”, half a dozen times per paragraph is more than enough.
American Megatrends Announces Full Support for Redfish™ 1.0 Specification in Aptio® V UEFI BIOS and MegaRAC® BMC Remote Management Firmware
Monday: October 2, 2017
AMI has announced its full support for the Redfish™ 1.0 specification from the Distributed Management Task Force (DMTF), in both its Aptio® V UEFI BIOS Firmware as well as several products within the MegaRAC® Manageability Framework – the most widely used solution in the market today. […] In addition to its industry-leading Aptio® V UEFI BIOS Firmware, known and trusted by Tier One OEMs and ODMs around the globe, products from AMI featuring support for Redfish 1.0 include the fully-integrated MegaRAC Pooled System Management Engine (PSME) firmware solutions, which enable efficient resource management for Network, Storage and Compute hardware throughout the data center, as well as MegaRAC Composer™ Pod Management Software.[…]
DMTF has a new educational video series for Redfish in Chinese available:
If you are looking for code that uses the DMTF Redfish or SMBIOS or CIM standardss, DMTF just created a new list of these projects. It looks like there are multiple new Redfish projects these days.
RackHD is a technology stack created for enabling hardware management and orchestration, to provide cohesive APIs to enable automated infrastructure. In a Converged Infrastructure Platform (CIP) architecture, RackHD software provides hardware management and orchestration (M&O). It serves as an abstraction layer between other M&O layers and the underlying physical hardware. Developers can use the RackHD API to create a user interface that serves as single point of access for managing hardware services regardless of the specific hardware in place.
New Redfish Update Adds Composability Support
Continuing its aggressive development timeline, an important update to the DMTF’s Redfish® standard is now available. The newly-released version 2017.1 of the Redfish Schema and version 1.2.0 of the Redfish Specification contain a number of additions, including support for composable infrastructures. With the ultimate goal of addressing all of the components in the data center with a consistent API, Redfish is an open industry standard that helps enable simple, modern and secure management of scalable platform hardware. DMTF continues to expand Redfish to cover customer use cases and technology, and the new Composition Service provides support for binding resources together into logical constructs. For example, disaggregated hardware – which allows for independent components, such as processors, memory, I/O controllers, and drives, to be bound together to create a composed Computer System – becomes a Computer System from an end user perspective in Redfish. Redfish composability allows clients to adjust their hardware configurations in response to their application needs, without having to touch any hardware.
Redfish Emerges as an Interoperability Standard for SDI
The world’s data centers are working to adopt Software Defined Infrastructure (SDI) – but they are far from reaching their goals. The single biggest challenge in SDI is achieving interoperability between many kinds of hardware. Without that, a data center’s systems become a Tower of Babel, preventing IT system admins from seeing a unified view of all resources – and managing them. Built to leverage virtualized infrastructure, SDI will be easier to achieve if there are more bridges between platforms – leading to better management. This blog focuses on an emerging management standard called Redfish, which is designed to help make SDI a day-to-day reality for hybrid cloud.[…]
Quoting their press release:
“DMTF’s innovative Redfish standard continues its fast progression, thanks to the dedicated efforts of the Scalable Platforms Management Forum (SPMF). To date, Redfish has focused on defining a TCP/IP-based out-of-band interface between a client and a management controller. Today, the newly available Redfish Host Interface Specification expands these capabilities to allow applications and tools running on an Operating System – including in the pre-boot (firmware) stage – to communicate with the Redfish management service. Every device exposes an interface to the host software (Operating System or Hypervisor). Management controllers are no different, and this standard modernizes this interface to equalize the capabilities of “in-band” or “host-based” applications with remote applications using Redfish. To learn more about Redfish or to download the Redfish Host Interface specification, please the Redfish web site. Developers can also visit the Redfish Developer Hub, a one-stop, in-depth technical resource with all the files, tools, community support and education you may need to help you use Redfish. To participate in the Host Interface Task Force, please join the DMTF’s SPMF.”
Ken Spear has a new post on the Cisco blog about Redfish support, and there’s some code on Github related to the post:
Cisco Supports Redfish Standard: API Enhances UCS Programmability
Cisco has added Redfish™ support to IMC to extend our unified and open API to manage server components and to help customers integrate solutions within their existing tool chains. […]