Sideband Bare Metal Provisioning via UEFI and WebSocket
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional provisioning approaches for information handling systems, particularly bare metal servers, face challenges such as flexibility, security, scalability, and multi-tenancy, and lack efficient methods to inject cloud image metadata during UEFI or PXE boot processes.
Innovation Solution
The method involves a management controller detecting a provisioning request, rebooting the system to initiate a UEFI boot sequence, establishing a WebSocket for streaming OS image data, and writing this data to a boot device, allowing for efficient cloud-native provisioning without relying on in-band networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional in-band provisioning technologies are used for traditional OS deployments, then existing infrastructure can be utilized, but efficient and native functionality to inject cloud image metadata over PXE boot or UEFI HTTP boot is lacking
Solution Approach 1:
The patent introduces a sideband network as an intermediary communication channel between the management controller and the information handling system. This sideband network enables cloud-native provisioning by carrying provisioning requests and responses separately from the in-band network traffic, allowing efficient injection of cloud image metadata during UEFI or HTTP boot without complicating the existing in-band network infrastructure.
2Productivity
If OS image data is streamed to the management controller for writing to boot device, then cloud-ready images can be provisioned efficiently, but storage resources at the management controller are consumed
Solution Approach 1:
The patent extracts the OS image data storage function from the management controller and relocates it to the information handling system's boot device. The management controller only temporarily buffers the data during the streaming process from the external source, then immediately writes it to the boot device. This extraction eliminates the need for the management controller to store large OS images permanently, preserving its limited storage resources while maintaining fast provisioning speeds.
3Reliability
If UEFI boot technology based on HTTP is used, then issues with legacy PXE boot technology are improved, but it still relies too heavily on an in-band network and is not cloud-native
Solution Approach 1:
The patent segments the provisioning functionality into two separate communication channels: the in-band network (HTTP/UEFI) for general boot operations and the sideband network for cloud-native provisioning operations. This segmentation allows the system to maintain the reliability of UEFI HTTP boot while simultaneously enabling cloud-native provisioning capabilities through the dedicated sideband channel, eliminating the conflict between the two requirements.
Data Source
AI summary
Disclosed methods respond to detecting the receipt, by a management controller, such as a baseboard management controller (BMC), of an information handling system, of a provisioning request from a management client, by rebooting the information handling system to initiate a Universal Extensible Firmware Interface (UEFI) boot sequence that is configured to load an EFI application, referred to herein a provisioning application. A two way communication channel such as a WebSocket is established between the management client and the management controller to stream OS image data corresponding to an OS image to the management controller. The OS image data streamed to the management controller is written to an OS image partition of a boot device, after which the stored OS image may be booted to load the OS. The provisioning request may be communicated as a representational state transfer (REST) compliant (RESTful) request using, in at least some deployments, a Redfish application programming interface (API).