Provisioning DPU management operating systems

Patent metadata

Field	Value
Publication number	US-12197939-B2
Application number	US-202217704052-A
Country	US
Kind code	B2
Filing date	Mar 25, 2022
Priority date	Jan 20, 2022
Publication date	Jan 14, 2025
Grant date	Jan 14, 2025

Abstract

Disclosed are various examples of provisioning a data processing unit (DPU) management operating system (OS). A management hypervisor installer executed on a host device launches or causes a server component to provide a management operating system (OS) installer image at a particular URI accessible over a network internal to the host device. A baseboard management controller (BMC) transfers the DPU management OS installer image to the DPU device. A volatile memory based virtual disk is created using the DPU management OS installer image. The DPU device is booted to a DPU management OS installer on the volatile memory based virtual disk. The DPU management OS installer installs a DPU management operating system to a nonvolatile memory of the DPU device on reboot of the DPU device.

First claim

What is claimed is:

1. A non-transitory computer-readable medium comprising executable instructions, wherein the instructions, when executed by at least one processor, cause at least one computing device to at least:
identify, by a management hypervisor installer executed on a host device, a management operating system (OS) installer image for a data processing unit (DPU) device physically installed to the host device;
launch, by the management hypervisor installer, a server component that provides a management OS installer image at a particular uniform resource identifier (URI) accessible over a network internal to the host device;
transmit, by the management hypervisor installer, the particular URI to a baseboard management controller (BMC) of the host device, wherein the BMC transfers the DPU management OS installer image to the DPU device;
create, by the DPU device, a volatile memory based virtual disk using the DPU management OS installer image; and
update, using the DPU device, boot options of the DPU device to boot to a DPU management OS installer on the volatile memory based virtual disk, wherein the DPU management OS installer installs a DPU management operating system to a nonvolatile memory of the DPU device on reboot of the DPU device.

2. The non-transitory computer-readable medium of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
update, using a DPU Unified Extensible Firmware Interface (UEFI) of the DPU device, boot options of the DPU device to boot to the DPU management operating system using the nonvolatile memory of the DPU device.

3. The non-transitory computer-readable medium of claim 1 , wherein hypertext transfer protocol (HTTP) boot is used to boot to the DPU management OS installer using the volatile memory based virtual disk.

4. The non-transitory computer-readable medium of claim 1 , wherein the management OS installer image is identified based at least in part on a DPU device type or model number specified for the DPU device in a listing.

5. The non-transitory computer-readable medium of claim 1 , wherein when executed by the at least one processor, cause the at least one computing device to at least:
transmit, using a BMC-to-DPU interface, a command to reset the DPU device.

6. The non-transitory computer-readable medium of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, by the management hypervisor installer, an indication that the DPU management operating system is executing on the DPU device.

7. The non-transitory computer-readable medium of claim 6 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
halt, by the management hypervisor installer, execution of the server component based at least in part on the indication that the DPU management operating system is executing on the DPU device.

8. A system, comprising:
at least one computing device comprising at least one processor; and
a data store comprising executable instructions, wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
identify, by a management hypervisor installer executed on a host device, a management operating system (OS) installer image for a data processing unit (DPU) device physically installed to the host device;
launch, by the management hypervisor installer, a server component that provides a management OS installer image at a particular uniform resource identifier (URI) accessible over a network internal to the host device;
transmit, by the management hypervisor installer, the particular URI to a baseboard management controller (BMC) of the host device, wherein the BMC transfers the DPU management OS installer image to the DPU device;
create, by the DPU device, a volatile memory based virtual disk using the DPU management OS installer image; and
boot, by the DPU device, to a DPU management OS installer on the volatile memory based virtual disk, wherein the DPU management OS installer installs a DPU management operating system to a nonvolatile memory of the DPU device on reboot of the DPU device.

9. The system of claim 8 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
update, using a DPU Unified Extensible Firmware Interface (UEFI) of the DPU device, boot options of the DPU device to boot to the DPU management operating system on the nonvolatile memory of the DPU device.

10. The system of claim 8 , wherein hypertext transfer protocol (HTTP) boot is used to boot to the DPU management OS installer using the volatile memory based virtual disk.

11. The system of claim 8 , wherein the management OS installer image is identified based at least in part on a DPU device type or model number specified for the DPU device in a listing.

12. The system of claim 8 , wherein when executed by the at least one processor, cause the at least one computing device to at least:
transmit, using a BMC-to-DPU interface, a command to reset the DPU device.

13. The system of claim 8 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, by the management hypervisor installer, an indication that the DPU management operating system is executing on the DPU device.

14. The system of claim 13 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
halt, by the management hypervisor installer, execution of the server component based at least in part on the indication that the DPU management operating system is executing on the DPU device.

15. A method, comprising:
identifying, by a management hypervisor installer executed on a host device, a management operating system (OS) installer image for a data processing unit (DPU) device physically installed to the host device;
launching, by the management hypervisor installer, a server component that provides a management OS installer image at a particular uniform resource identifier (URI) accessible over a network internal to the host device;
transmitting, by the management hypervisor installer, the particular URI to a baseboard management controller (BMC) of the host device, wherein the BMC transfers the DPU management OS installer image to the DPU device;
creating, by the DPU device, a volatile memory based virtual disk using the DPU management OS installer image; and
booting, by the DPU device, to a DPU management OS installer on the volatile memory based virtual disk, wherein the DPU management OS installer installs a DPU management operating system to a nonvolatile memory of the DPU device on reboot of the DPU device.

16. The method of claim 15 , further comprising:
updating, using a DPU Unified Extensible Firmware Interface (UEFI) of the DPU device, boot options of the DPU device to boot to the DPU management operating system using the nonvolatile memory of the DPU device.

17. The non-transitory computer-readable medium of claim 1 , wherein hypertext transfer protocol (HTTP) boot is used to boot to the DPU management OS installer using the volatile memory based virtual disk.

18. The non-transitory computer-readable medium of claim 1 , wherein the management OS installer image is identified based at least in part on a DPU device type or model number specified for

Assignees

• Vmware Inc
• VMware LLC

Inventors

• Warkentin Andrei
• Haryadi Aravinda
• He Lingyuan
• Boro Suman
• Ramachandra Karthik
• Gondi Anjaneya Prasad
• Voltz Renaud Benjamin

Classifications

• G06F8/61

  Installation · CPC title

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title

• H04L67/1097 Primary

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F2009/45595

  Network integration; Enabling network access in virtual machine instances · CPC title

• G06F9/4406

  Loading of operating system · CPC title