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.
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.
DMTF Releases Updated MCTP SMBus/I2C Transport Binding Specification
The DMTF’s Platform Management Components Intercommunication (PMCI) Working Group defines standards to address “inside the box” communication and functional interfaces between the components of the platform management subsystem (e.g., management controllers, managed devices, etc.). PMCI’s Management Component Transport Protocol (MCTP) over SMBus/I2C Transport Binding Specification is now available in version 1.1.0 . This specification addresses how MCTP packets are delivered over a physical SMBus or I2C medium using SMBus transactions. It defines how physical addresses are used, how fixed addresses are accommodated, how physical address assignment is accomplished for hot-plug or other devices that require dynamic physical address assignment, and how MCTP support is discovered. In addition, timing specifications for bus and MCTP control operations are included, and a “fairness” protocol is defined for the purpose of avoiding deadlock and starvation/lockout situations among MCTP endpoints. The binding has been designed to be able to share the same bus as devices communicating using earlier SMBus/I2C management protocols, such as Alert Standard Format (ASF) and Intelligent Platform Management (IPMI), and with vendor-specific devices using SMBus/I2C protocols. The specification also allows a given device to incorporate non-MCTP SMBus functions alongside MCTP.
As William points out, the DMTF updated SMBIOS, and the Tianocore project updated EDK2 appropriately.
DMTF has just released version 2.0 of the Conformance Test Suite (CTS) for its Desktop and mobile Architecture for System Hardware (DASH) standard. DASH provides secure out-of-band and remote management of desktop and mobile systems. The DASH CTS serves to improve interoperability by validating conforming implementations. The new DASH CTS 2.0 includes the necessary updates, policies and procedures to test the latest DASH specifications, which address current requirements for managing modern hardware in a networked environment. With DASH CTS 2.0, companies can continue to self-test their implementations and submit digitally signed results to the DASH Conformance Program Administrator (an independent third party) for validation. Once validated, participants can have their submission information included in the DMTF Certification Registry.[…]
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.”