IP Library Granted Patent US 11,669,325
Granted Patent B2
US 11,669,325 · App. 17/725,421 · Granted Jun 6, 2023

Desired state model for managing lifecycle of virtualization software

Inventors: Aravinda Haryadi (Bangalore, IN); Mukund Gunti (Sunnyvale, CA); Olivier Alain Cremel (Los Altos, CA); Jeffrey Hu (Palo Alto, CA); Patrick William Penzias Dirks (Monte Sereno, CA)
Assignee: VMware, Inc.
G06F8/65G06F8/63G06F9/45516
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 11,669,325
App. No.
17/725,421
Filed
Apr 20, 2022
Granted
Jun 6, 2023
Kind
B2
Examiner
LEE, MARINA
Art Unit
2192
USPC
717/169
Abstract

An image of a virtualization software in a plurality of hosts is installed or upgraded by performing the steps of: in response to a user input, generating a software specification that specifies a desired state of the virtualization software; based on the software specification, preparing a desired image of the virtualization software by retrieving metadata of the desired state of the virtualization software and determining components that make up the desired state of the virtualization software; and instructing each of the hosts to install the desired image of the virtualization software or upgrade a current image of the virtualization software to the desired image of the virtualization software. One of the components defines a set of payloads for a core kernel of the virtualization software.

Claims (29)

1. A method of installing or upgrading an image of a virtualization software in a plurality of hosts, said method comprising:

in response to a user input, generating a software specification that specifies a desired state of the virtualization software;

based on the software specification, preparing a desired image of the virtualization software by retrieving metadata of the desired state of the virtualization software and determining components that make up the desired state of the virtualization software; and

instructing each of the hosts to install the desired image of the virtualization software or upgrade a current image of the virtualization software to the desired image of the virtualization software,

wherein one of the components defines a set of payloads for a core kernel of the virtualization software and one or more other payloads that have inter-dependencies with the core kernel.

2. The method of claim 1 , wherein the components each define a set of payloads that are executed to enable a user-visible feature of the virtualization software.

3. The method of claim 1 , wherein the user input specifies one of a first version of the virtualization software and a second version of the virtualization software, and first metadata that specifies one or more components that make up the first version and second metadata that specifies one or more components that make up the second version are stored in an image depot.

4. The method of claim 3 , wherein the hosts are bootable with an image of the virtualization software, that includes only the first version of the virtualization software or only the second version of the virtualization software, installed therein.

5. The method of claim 4 , wherein the first version is released as a complete release and the second version is released as a partial release.

6. The method of claim 1 , wherein each of the hosts has an image database in which a state of the current image of the virtualization software is stored prior to an upgrade to the desired image and a state of the desired image of the virtualization software is stored after the upgrade to the desired image.

7. A non-transitory computer readable medium comprising instructions that are executable in a processor for the processor to carry out a method of installing or upgrading an image of a virtualization software in a plurality of hosts, said method comprising:

in response to a user input, generating a software specification that specifies a desired state of the virtualization software;

based on the software specification, preparing a desired image of the virtualization software by retrieving metadata of the desired state of the virtualization software and determining components that make up the desired state of the virtualization software; and

instructing each of the hosts to install the desired image of the virtualization software or upgrade a current image of the virtualization software to the desired image of the virtualization software,

wherein one of the components defines a set of payloads for a core kernel of the virtualization software and one or more other payloads that have inter-dependencies with the core kernel.

8. The non-transitory computer readable medium of claim 7 , wherein the components each define a set of payloads that are executed to enable a user-visible feature of the virtualization software.

9. The non-transitory computer readable medium of claim 7 , wherein the user input specifies one of a first version of the virtualization software and a second version of the virtualization software, and first metadata that specifies one or more components that make up the first version and second metadata that specifies one or more components that make up the second version are stored in an image depot.

10. The non-transitory computer readable medium of claim 9 , wherein the hosts are bootable with an image of the virtualization software, that includes only the first version of the virtualization software or only the second version of the virtualization software, installed therein.

11. The non-transitory computer readable medium of claim 10 , wherein the first version is released as a complete release and the second version is released as a partial release.

12. The non-transitory computer readable medium of claim 7 , wherein each of the hosts has an image database in which a state of the current image of the virtualization software is stored prior to an upgrade to the desired image and a state of the desired image of the virtualization software is stored after the upgrade to the desired image.

13. A computer system comprising a management server, a cluster of hosts in which virtualization software is to be installed or upgraded, wherein the management server includes a processor that is programmed to execute a method of installing or upgrading an image of the virtualization software in the hosts, said method comprising:

in response to a user input, generating a software specification that specifies a desired state of the virtualization software;

based on the software specification, preparing a desired image of the virtualization software by retrieving metadata of the desired state of the virtualization software and determining components that make up the desired state of the virtualization software; and

instructing each of the hosts to install the desired image of the virtualization software or upgrade a current image of the virtualization software to the desired image of the virtualization software,

wherein one of the components defines a set of payloads for a core kernel of the virtualization software and one or more other payloads that have inter-dependencies with the core kernel.

14. The computer system of claim 13 , wherein the components each define a set of payloads that are executed to enable a user-visible feature of the virtualization software.

15. The computer system of claim 13 , wherein the user input specifies one of a first version of the virtualization software and a second version of the virtualization software, and first metadata that specifies one or more components that make up the first version and second metadata that specifies one or more components that make up the second version are stored in an image depot.

16. The computer system of claim 15 , wherein the hosts are bootable with an image of the virtualization software, that includes only the first version of the virtualization software or only the second version of the virtualization software, installed therein.

17. The computer system of claim 16 , wherein the first version is released as a complete release and the second version is released as a partial release.

Assignments (1)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
Priority Claims (1)
IN 202041014680 · Apr 2, 2020 · national
Continuity (2)
Continuation 16939117 · Jul 27, 2020
Related Publication 20220244944A1 · Aug 4, 2022