IP Library › Granted Patent US 12,197,939
Granted Patent B2
US 12,197,939 · App. 17/704,052 · Granted Jan 14, 2025

Provisioning DPU management operating systems

Inventors: Andrei Warkentin (South Elgin, IL); Aravinda Haryadi (Bangalore, IN); Lingyuan He (Sunnyvale, CA); Suman Boro (Bangalore, IN); Karthik Ramachandra (Bangalore, IN); Anjaneya Prasad Gondi (Fremont, CA); Renaud Benjamin Voltz (Grass Valley, CA)
Assignee: VMware LLC
G06F9/45558G06F8/61G06F9/4406H04L67/1097G06F2009/45562G06F2009/45595
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,197,939
App. No.
17/704,052
Granted
Jan 14, 2025
Kind
B2
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.

Claims (49)

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 the DPU device in a listing.

19. The method of claim 15 , further comprising:

transmitting, using a BMC-to-DPU interface, a command to reset the DPU device.

20. The method of claim 15 , further comprising:

receiving, by the management hypervisor installer, an indication that the DPU management operating system is executing on the DPU device; and

deleting, by the management hypervisor installer, the DPU management OS installer image from the host device based at least in part on the indication that the DPU management operating system is executing.

Assignments (2)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0242 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 25, 2022
From: WARKENTIN, ANDREI; HARYADI, ARAVINDA; HE, LINGYUAN; BORO, SUMAN; RAMACHANDRA, KARTHIK; GONDI, ANJANEYA PRASAD; VOLTZ, RENAUD BENJAMIN
To: VMWARE, INC.
Reel/Frame 059397/0230 →
Priority Claims (1)
IN 202241003405 · Jan 20, 2022 · national
Continuity (1)
Related Publication 20230229481A1 · Jul 20, 2023
References Cited (8)
US 20080155245A1 · Lipscombe et al. · 2008 [cited by applicant]
US 20200167094A1 · Sariel · 2020 [cited by examiner]
US 20210117249A1 · Doshi · 2021 [cited by examiner]
US 20210224061A1 · Pillilli et al. · 2021 [cited by applicant]
US 20220027186A1 · Preimesberger · 2022 [cited by examiner]
US 20230009689A1 · Yeh · 2023 [cited by examiner]
Cui Neo: “Using HTTP Boot to Install an Operating System on Lenovo ThinkSystem”, May 31, 2019 (May 31, 2019), pp. 1-24, XP093034482, Retrieved from the Internet: URL:https://lenovopress.lenovo.com/1p0736.pdf [retrieved … [cited by applicant]
International Search Report and Written Opinion in PCT/US2023/010839 mailed Apr. 4, 2023. [cited by applicant]