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. […]
“Redfish: this is a tool designed to test Redfish for BMC. it’s a GUI programe writen by Python tkinter.”
If you are looking to write a Redfish security research tool, beyond the DMTF’s redfishtool, you might want to look at this one.
AMI is now offering firmware for both BIOS and BMC on Intel customer reference boards (CRB) for the Intel Xeon® processor D-1500 product family and the 4th generation baseboard management controller (BMC) from Aspeed, the Aspeed AST2300 BMC. AMI has developed generic Redfish BIOS and BMC firmware support and has tested on the next generation AMD silicon. AMI’s BIOS and BMC firmware are highly integrated, allowing data center administrators to simultaneously, remotely and securely manage a number of server platforms out-of-box. Other features include BIOS-level firmware configuration and firmware updating. BMC functionality is based on the open industry standard specification and schema from DMTF’s Redfish™ API with the goal of creating seamless integration into existing tool chains.
Apparently Lenovo’s XClarity Administrator software uses the Redfish API:
“Lenovo XClarity is a fast, flexible, and scalable hardware systems management application that enables administrators to deploy infrastructure faster and with less effort. This video provides a brief overview of XClarity Administrator, VMware Integration, the XClarity Mobile App, and new features supporting extended management of storage and network switches.”
Here’s a Lenovo video showing the tech:
The DMTF has a Github project for DMTF. They’ve recently updated it to include new tools, including ‘redfishtool’. Quoting their press release:
New tools recently shared include:
* Redfish Service Validator – a Python 2.7 tool for checking conformance of any “device” with a Redfish service interface against a Redfish CSDL schema.
* Redfish Profile Simulator – a Flask-based real simulator of the initial OCP Feature profile. Resources are loaded from a mockup into Python dictionary structures.
* Redfishtool CLI tool – a Python 3.4 program that implements a commandline tool for accessing the Redfish API. The tool outputs Redfish JSON responses for common use cases, and shows the proper way to implement the hypermedia aspects of the Redfish API.
* Mockup Creator – a Python 3.4 program that creates a Redfish Mockup folder structure from a real live Redfish service. The program executes Redfish GET requests to the Redfish service and saves the response in a file structure.
These new items join additional tools currently available in the GitHub repo:
* CSDL to JSON-schema converter – converts a valid Redfish CSDL schema to the JSON-schema (draft v4) format.
* OData CSDL Validator – a Python 3.0 tool that crawls through OData-formatted metadata, parses it and validates that it conforms to OData V4.0.
* Mockup Server – a simple Python 3.4 program that can be copied into a folder at the top of any Redfish mockup and serve Redfish requests on the specified IP/port.
* Documentation Generator – a utility to format text and values extracted from the Redfish JSON-schema files and incorporate text from additional Markdown documents to generate either web-based (Slate) or easily printed (converted to PDF) end-user documentation of the Redfish schema.
Quoting their press release:
DMTF Launches YouTube Channel with Redfish™ School Series
Get schooled in Redfish™ by tuning in to DMTF’s new YouTube channel! () The DMTF is excited to announce this new resource, which offers short technical webinars on a variety of topics related to the Redfish API and other DMTF standards. Currently, DMTF’s YouTube channel features “Redfish School,” a five-webinar series that covers Redfish Model Architecture; Common Properties; Chassis, Systems and Managers; and more. In addition, you’ll find Why Redfish™?, a short webinar – hosted by Scalable Platforms Management Forum (SPMF) Co-Chair Jeff Autor – that provides an overview of the standard and how it enables simple and secure management of modern scalable platform hardware. Visit today to see DMTF’s latest videos, and be sure to subscribe to the DMTF YouTube Channel to stay up-to-date with our upcoming webinars!
[…]Intel Rack Scale Design is the first framework to be based upon and use the Redfish™ industry standard from DMTFOpens in a new window for modern and secure management of scalable platform hardware in the modern data center. The framework allows for dynamic management of compute, memory, PCIe, and storage resources and the pooling of those resources for more efficient use of data center assets. The framework simplifies advanced technology to accelerate the adoption of open, interoperable solutions for tomorrow’s data centers today.[…]
DMTF SMASH and DASH are pre-os technologies, somewhat like IPMI and Redfish. SMASH is for servers, DASH is for desktops. AMI and Realtek have DASH working over WiFi now. The new risk brought with this feature is that, if attacker can find exploit in WiFi DASH implementation, they can attack system remotely. Before, they needed an Ethernet connection, now they can use WiFi. IPMI and Redfish have similar risks. I wonder if servers are also available via WiFi with SMASH? Excerpt from press release:
American Megatrends Inc. (AMI), in collaboration with Realtek Semiconductor, an AMI Technology Partner, is pleased to introduce RealManage™ 2.0, a WiFi DASH solution integrated with the RTL8111FP-CG NIC controller chip from Realtek.
DASH (Desktop and mobile Architecture for System Hardware) is a client management standard released by the DMTF (Distributed Management Task Force) and is a web services-based standard for secure out-of-band and remote management of desktops and mobile systems. Realtek has long been an Ethernet NIC market leader and with the RTL8111FP-based next-generation DASH remote management solution called RealManage 2.0, Realtek aims to keep its market position and remain a force for technology innovation.
“With the rising popularity of the GUI BIOS, enterprise customers required out-of-band KVM (Keyboard, Video, and Mouse) functions beyond the standard ‘Text Console Redirection’ feature. Realtek’s RealManage 2.0 is our answer; a powerful DASH solution that supports Wi-Fi and Ethernet DASH, and is compliant with a GUI BIOS,” said Realtek’s Vice President and Spokesman, Yee-Wei Huang. “It brings a whole new application methodology and experience to commercial customers, providing a wealth of data and tools for remote out-of-band client management tasks.”
Full press release:
DMTF released Redfish 1.0 a while ago, and now they’ve done their first revision to this IPMI replacement technology. Excerpting DMTF’s press release:
The latest specification and schemas for the DMTF’s Redfish standard are now available. Now available for download, the 2016.1 publication includes new Redfish schemas for AttributeRegistry, Bios, Drive, Memory, MemoryCollection, MemoryMetrics, SecureBoot, Storage, StorageCollection and Volume. In addition, this release includes minor updates to the Chassis, ComputerSystem, Event, Manager, Power, Resource, SimpleStorage and Thermal schemas, along with all previously released schemas using updated file naming conventions. Released separately as a Work in Progress (WIP) for public comment, the DSP8010-WIP-2016.0.9a () publication includes new Redfish schemas for providing firmware update services (UpdateService, FirmwareInventory) and PCIe switch and device management (PCIeDevice, PCIeFunction, PCIePort, PCIeSwitch, and PCIeZone, and respective Collection schemas). In addition, DMTF has released version 1.0.2 of the Redfish Scalable Platforms Management API Specification, which defines the protocols, data model, and behaviors for Redfish.
Brian Richardson of Intel UEFI team has a new blog post, showing HP vendor data using DMTF Redfish as well as viewing UEFI x-UEFI Configuration Language data.
For more on the x-UEFI Configuration language, see Vincent’s post:
AMI has announced Redfish support for their UEFI implementation:
American Megatrends Announces Out-of-Band BIOS Configuration through Redfish
AMI is proud to announce out-of-band BIOS configuration compatible with DMTF Redfish. DMTF’s Redfish API platform was created by DMTF’s Scalable Platforms Management Forum as an open industry standard specification designed to provide end users simple and powerful, yet scalable management platform hardware. To meet the needs of end users, Redfish allows users to develop solutions that combat homogenous interfaces and reduced functionality. Redfish utilizes a combination of REST, JSON and OData and serves as a secure replacement for IPMI-over-LAN. AMI’s OOB (Out-of-Band) Firmware Management delivers extended management solutions through the adoption of Redfish between BIOS, BMC and Extensible Management Architecture (EMA). AMI OOB Firmware Management provides complete Redfish support and allows for the consistent exchange of information between the BIOS and BMC. AMI has been diligently working on providing an OOB firmware solution for datacenter solutions providers such as QCT (Quanta Cloud Technology).
I just learned about Facebook’s OpenBMC, thanks to Sai Dasari of Facebook, who just posted a message to the Open Compute Project’s hardware management list, talking about DMTF Redfish and Facebook’s OpenBMC.
OpenBMC is an open software framework to build a complete Linux image for a Board Management Controller (BMC).
When we were developing Facebook’s top-of-rack “Wedge” switch, we followed our usual process in the beginning; our partner was responsible for developing the BMC software. However, in the first months of the project, many requirements for the BMC software emerged, introducing extra complexity, coordination, and delays into the BMC software-development process. To address these challenges, at one of Facebook’s hackathon events, four engineers worked to create our own BMC software. Within 24 hours, we were able to build a minimum BMC software image, including an SSH server and the ability to change fan speed, power-on the host CPU, and blink some LEDs. It was far from a production image, but it gave us a strong confidence that we could eventually develop our own BMC software for “Wedge.” Fast-forward eight months, and we’ve deployed our solution — code-named “OpenBMC” — into production along with Wedge. And today we’re sharing OpenBMC with the open source community in the hope that we can collaborate based on this open software framework for next-generation system management.
Hank Bruning of JBlade has released a new Java-based library to interact with Redfish. He announced it today on the Open Compute Project’s Hardware Management mailing list. He’s also looking for vendors with actual hardware, beyond the DMTF RedFish Mockup; if you can help him out, please get in touch with Hank.
Lee Calcote of Seagate wrote an article on the recent DMTF Redfish 1.0 release, and about Seagate’s support of this new API, and IPMI. Excerpts:
Like most systems manufacturers, Seagate supports IPMI and will continue to support it as a critical standard in the data center in lieu of broad adoption of Redfish. Where IPMI strains to meet the requirements of today’s massive multiscale environments, Redfish addresses IPMI inadequacies of interoperability, security, simplicity and scalability.
Redfish 1.0 is only the beginning. Seagate and other industry leaders are already engaging within the DMTF Scalable Platform Management Forum on enhancements beyond Redfish 1.0 standard.
What does Redfish mean for Seagate partners and customers? It means a new level of control, management and monitoring for the data center, using a modern, secure RESTful API that is commonly understood and will be widely supported.
Read the full post here:
This week at Intel Developer Forum (IDF), AMI showcased their MegaRAC manageability solutions. MegaRAC is AMI’s Remote Management Firmware family of products for both in-band and out-of-band management, including supporting IPMI, Intel AMT, AMD systems with DMTF DASH. Amongst the new features of MegaRAC SP-X are DMTF Redfish support, and Intel(R) Innovation Engine support.
I don’t know much about Intel’s new “Innovation Engine” is yet, so I’ll excerpt one paragraph from the AMI press release:
“The Innovation Engine is a small, embedded, Intel-architecture processor and I/O subsystem built into future Intel data center platforms,” said Lisa Spelman, General Manager of Data Center Marketing at Intel. “Firmware such as MegaRAC PM-X running on the IE can improve or differentiate the system-builders’ platforms in a wide range of ways, including manageability, cost reduction or security.”
Maybe this means that AMI is the second vendor to support Redfish, after HP?
Read AMI’s full press release here: