Management of software updates in a virtualized environment of a datacenter using dependency relationships

Patent metadata

Field	Value
Publication number	US-9535684-B2
Application number	US-201414554015-A
Country	US
Kind code	B2
Filing date	Nov 25, 2014
Priority date	Aug 26, 2011
Publication date	Jan 3, 2017
Grant date	Jan 3, 2017

Abstract

An approach to managing software components in a datacenter having virtualized components includes maintaining a suitable data construct for representing the virtualized elements. In embodiments, virtualized elements include knowledge relating to instantiations of virtual machines. Management of software components includes traversing a data representation of the datacenter, and assessing the compatibility of the software component with components in the datacenter that relate to the target of the software component.

First claim

What is claimed is:

1. A method of managing software in a datacenter comprising operating a computer to perform steps of:
storing a data construct representative of at least a portion of a datacenter having a distributed computer architecture, the data construct comprising a first component portion, a second component portion, and a relating portion, the first component portion comprising a first list of components within the datacenter, the second component portion comprising a second list of components within the datacenter, and the relating portion comprising a list of dependencies that signify a relationship between each component in the first list of components and a corresponding component in the second list of components;
receiving a request to change software on a target component in the datacenter;
receiving target information representative of the target component;
receiving a software bundle that includes the software to be installed on the target component, metadata that includes information used to describe a relationship between the software and components, and one or more probe scripts that discover a component dependency not listed in the relating portion;
updating the list of dependencies to include the component dependency not listed in the relating portion;
identifying, by a processor, the target component within at least one of the first component portion and the second component portion;
identifying, within the relating portion, one or more dependencies that associate the target component with one or more other components listed within at least one of the first component portion and the second component portion, the one or more dependencies including the component dependency discovered by the one or more probe scripts;
using the metadata and the identified one more dependencies to identify, by the processor, any affected components from among the one or more other components listed within at least one of the first component portion and the second component portion, wherein the affected components reflect a set of possible conflicts that occur due to the installing of the software;
when the set of possible conflicts cannot be resolved, outputting information for the set of possible conflicts that cannot be resolved for one or more of the affected components; and
when the set of possible conflicts are resolvable, enabling the change of the software to be performed on the target component.

2. The method of claim 1 , further comprising receiving task information representative of a desired change for the target component for installing software on the target component, and wherein the method further comprises using at least the task information to further identify the affected components.

3. The method of claim 2 , wherein the affected components reflect a set of possible conflicts that occur due to the installing of the software.

4. The method of claim 1 , further comprising adding the affected components to a data structure that includes the identified dependencies to allow the change of the software to be performed on the target component.

5. The method of claim 4 , further comprising:
transforming the data structure into a workflow that enables changes to the software on the target component by:
obtaining a set of action scripts from a set of feature bundles associated with the affected components, wherein the set of action scripts is added to the workflow based on the dependency relationships; and
remediating the affected components to resolve the set of possible conflicts by executing the action scripts in the workflow, each action script performing an action to resolve the possible conflicts.

6. The method of claim 1 , further comprising receiving input from a user indicating whether or not to proceed with installing the software component when one or more affected components are identified.

7. The method of claim 1 , wherein when the set of possible conflicts are resolvable, receive a request from a user to enable the change of the software to be performed on the target component.

8. The method of claim 1 , wherein the metadata identifies the target component as needing an update prior to installing the software.

9. A system for managing software in a datacenter, the system comprising:
memory for storing a data construct representative of at least a portion of a datacenter having a distributed computer architecture, the data construct comprising a first component portion, a second component portion, and a relating portion, the first component portion comprising a first list of components within the datacenter, the second component portion comprising a second list of components within the datacenter, and the relating portion comprising a list of dependencies that signify a relationship between each component in the first list of components and a corresponding component in the second list of components; and
a processor programmed to:
receive a request to change software on a target component in the datacenter;
receive target information representative of the target component;
receive a software bundle that includes the software to be installed on the target component, metadata that includes information used to describe a relationship between the software and components, and one or more probe scripts that discover a component dependency not listed in the relating portion;
update the list of dependencies to include the component dependency not listed in the relating portion;
identify the target component within at least one of the first component portion and the second component portion;
identify, within the relating portion, one or more dependencies that associate the target component with one or more other components listed within at least one of the first component portion and the second component portion, the one or more dependencies including the component dependency discovered by the one or more probe scripts; and
use metadata and the identified one more dependencies to identify any affected components from among the one or more other components listed within at least one of the first component portion and the second component portion, wherein the affected components reflect a set of possible conflicts that occur due to the installing of the software;
when the set of possible conflicts cannot be resolved, output information for the set of possible conflicts that cannot be resolved for one or more of the affected components; and
when the set of possible conflicts are resolvable, enable the change of the software to be performed on the target component.

10. The system of claim 9 , wherein the processor is further programmed to:
receive task information representative of a desired change for the target component for installing software on the target component; and
use at least the task information to further identify the affected components.

11. The system of claim 10 , wherein the affected components reflect a set of possible conflicts that occur due to the installing of the software.

12. The system of claim 9 , wherein the processor is further programmed to add the affected components to a data structure that includes the identified dependencies to allow the change of the software to be performed on the target component.

13. The system of claim 12 , wherein the processor is further programmed to:
transform the data structure into a workflow that enables changes to the software on the target component by:
obtaining a set of action scripts from a set of feature bundles associated with the affected components, wherein the set of action scripts is added to the workflow based on the dependency relationships;

Assignees

• Vmware Inc

Inventors

• Hiltgen Daniel Kerry
• Devine Christopher P

Classifications

• G06F8/60 Primary

  Software deployment · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title