Dynamic handling of multiple software component versions for device management

• US 7,415,706 B1
• Filed: 12/01/2003
• Issued: 08/19/2008
• Est. Priority Date: 12/01/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Ward, David D., Tanner, David Anthony, Raju, Satyanarayana
• Primary Examiner(s): Zhen; Wei Y.
• Assistant Examiner(s): WANG, RONGFA PHILIP
• Application Number:
  US10/726,272
• Time in Patent Office: 1,723 Days
• Field of Search: 717/170
• US Class Current: 717/170
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/44536 Selecting among different versions

Abstract

A method and an apparatus are disclosed for managing multiple software component versions. The method and apparatus detect a version change to one software component on a network. Then, the method and apparatus automatically identify other software components that both need to be changed to remain compatible with the changed software component and also depend on the changed software component.

Claims

1. A method for managing versions of a plurality of software components on a network, comprising:

detecting a version change to a first software component associated with a network device out of the plurality of the software components;

automatically identifying a second software component out of the plurality of the software components that needs to be changed to be compatible with the first software component, wherein the second software component depends on the first software component;

assessing the software dependencies and compatibilities of at least the first and second software components;

downloading upgrades of the first and second software components from a network device;

storing the upgrades of the first and second software components in a computer cache;

a version manager maintaining version information of the upgrades of the first and second software components;

checking the version information of the upgrades of the first and second software components stored in the computer cache;

storing the version manager in the component cache;

wherein the step of assessing the software dependencies and compatibilities is performed by a component manager which is directly connected to the component cache, and reads from the writes to the component cache;

the version manager maintaining the version information of the first and second software components of the network device including requesting the version information from the network device;

the version manager passing the version information to the component manager;

determining whether the component cache contains a current copy of the version manager;

requesting and receiving a current copy of the version manager from the network device; and

retrieving a current copy of the version manager from the component cache.

2. The method as recited in claim 1, further comprising:

collecting attributes of the second software component; and

automatically manipulating the second software component according to the attributes.

3. The method as recited in claim 2, wherein the manipulating further includes:

downloading an upgrade of the second software component as part of performing an instance of the method; and

replacing an existing version of the second software component with the upgrade of the second software component that has been downloaded in the same instance.

4. The method of claim 3, wherein the replacing of the software upgrades is achieved via custom class loader mechanism.

5. The method of claim 1, further comprising:

determining if the software upgrades are already loaded into the component cache.

6. The method of claim 1, further comprising:

determining if a specific software upgrade has already been loaded into the component cache.

7. A method for managing versions of a plurality of software components on a network, comprising:

detecting a version change to a first software component out of the plurality of the software components;

automatically identifying a second software component out of the plurality of the software components that needs to be changed to be compatible with the first software component, wherein the second software component depends on the first software component;

assessing the software dependencies and compatibilities of at least the first and second upgrades of software components;

collecting attributes of the second software component; and

automatically manipulating the second software component according to the attributes, wherein the manipulating step further comprises downloading a copy of an upgrade of the second software component and storing it within a component cache;

a version manager maintaining version information of upgrades of the first and second software components;

storing the upgrades of the first and second software components in a component cache; and

storing the version manager in the component cache;

wherein the step of assessing the software dependencies and compatibilities is performed by a component manager which is directly connected to the component cache, and reads from and writes to the component cache;

the version manager maintaining the version information of the first and second software components of a network device including requesting the version information from the network device;

the version manager passing the version information to a component manager;

determining whether the component cache contains a current copy of the version manager; and

requesting and receiving a current copy of the version manager from the network device; and

retrieving a current copy of the version manager from the component cache;

8. The method as recited in claim 7, wherein the downloading step further comprises:

downloading the upgrade of the second software component as part of performing an instance of the method; and

wherein the manipulating step further comprises replacing an existing version of the second software component with an upgrade of the second software component that has been downloaded in the same instance.

9. The method as recited in claim 7, further comprising:

checking version information of the upgrade of the second software component that is stored in the component cache to determine whether to perform the downloading step.

10. The method of claim 7, further comprising:

determining if the software upgrades are already loaded into the component cache.

11. The method of claim 7, further comprising:

determining if a specific software upgrade has already been loaded into the component cache.

12. An apparatus for managing versions of a plurality of software components on a network, comprising:

at least one processor and a memory;

a user interface; and

a processing engine, coupled to the user interface, wherein the processing engine further comprises;

an event manager that detects a version change to a first software component out of the plurality of the software components;

a component manager that in response obtains version information of first software component from a version manager and automatically identifies an upgrade to a second software component out of the plurality of the software components that needs to be changed to be compatible with the first software component, wherein the second software component depends on the first software component;

wherein the component manager automatically downloads the upgrade of the second software component and stores a copy of the upgrade of the second software component in a component cache, wherein the component manager is directly connected to the component cache and reads from and writes to the component cache;

a version manager maintaining version information of the upgrade of the second software component of a network device including requesting the version information from the network device;

checking the version information of the upgrade of the second software component stored in the component cache;

storing the version manager in the component cache;

the version manager passing the version information to the component manager;

determining whether the component cache contains a current copy of the version manager;

requesting and receiving a current copy of the version manager from the network device; and

retrieving a current copy of the version manager from the component cache.

13. The apparatus as recited in claim 12, wherein the component manager informs an operator of the apparatus of the upgrade of the second software component via the user interface.

14. The apparatus as recited in claim 12, wherein the component manager checks version information of the upgrade of the second software component that is stored in the cache to determine whether to download a copy of the upgrade of the second software component.

15. The apparatus as recited in claim 12, wherein the processing engine further comprises:

a desktop manager, coupled to the component manager, wherein the desktop manager collects attributes of the second software component; and

manipulates the second software component according to the attributes.

16. The apparatus as recited in claim 15, wherein the desktop manager manipulates the second software component by causing the component manager to

download the copy of the upgrade version of the second software component as part of executing an instance of the processing engine;

and

replace an existing version of the second software component with the copy of the upgrade version of the second software component that has been downloaded in the same instance.

17. The apparatus of claim 16, wherein the desktop manager initializes the component manager so that the component manager can evaluate current states of the processing engine without considering any remnants from any prior instances of the processing engine.

18. The apparatus of claim 12, wherein the processing engine employs a metadata driven interface to communicate with the network devices.

19. The apparatus of claim 12, wherein a user activates the user interface via a launch applet.

20. The apparatus of claim 19, wherein the launch applet originates from a network device.

21. A computer-readable medium storing one or more sequences of instructions for managing a plurality of network devices on a network, which instructions, when executed by one or more processors, cause the one or more processors to:

detect a version change to a first software component out of the plurality of the software components; and

automatically identify a second software component out of the plurality of the software components that needs to be changed to be compatible with the first software component, wherein the second software component depends on the first software component;

assess the software dependencies and compatibilities of at least the first and second upgrades of software components performed by a component manager which is directly connected to the component cache, and reads from and writes to the component cache;

download a copy of an upgrade of the second software component; and

store a copy of the upgrade of the second software component in a component cache;

a version manager maintaining version information of the upgrades of the first and second software components of a network device including requesting the version information from the network device;

check the version information of the upgrades of the first and second software components stored in the component cache; and

store the version manager in the component cache, pass the version information to the component manager;

determine whether the component cache contains a current copy of the version manager;

request and receive a current copy of the version manager from the network device; and

retrieve a current copy of the version manager from the component cache.

22. The computer-readable medium as recited in claim 21, further comprising instructions which, when executed by the one or more processors, cause the one or more processors to automatically download the copy of the upgrade of the second software component.

23. The computer-readable medium as recited in claim 22, further comprising instructions which, when executed by the one or more processors, cause the one or more processors to check version information of the copy of the upgrade of the second software component that is stored in the cache to determine whether to download the copy of the upgrade of the second software component.

24. The computer-readable medium as recited in claim 21, further comprising instructions which, when executed by the one or more processors, cause the one or more processors to

collect attributes of the second software component;

and

automatically manipulate the second software component according to the attributes.

25. The computer-readable medium as recited in claim 24, further comprising instructions which, when executed by the one or more processors, cause the one or more processors to:

download a copy of the upgrade of the second software component; and

replace an existing version of the second software component with the upgrade of the second software component that has been downloaded.

26. An apparatus for managing versions of a plurality of software components on a network, comprising:

at least one processor and a memory;

a user interface means; and

a processing means, coupled to the user interface, wherein the processing means further includes;

a detection means for detecting a version change to a first software component out of the plurality of the software components; and

a component manager means, stored within a component cache, for assessing the software dependencies and compatibilities for upgrades of the plurality of software components wherein the component manager means is directly connected to the component cache, reads from and writes to the component cache, and assesses the software dependencies and compatibilities of the software components;

a compatibility verification means for automatically identifying a second software component out of the plurality of the software components that needs to be changed to be compatible with the first software component, wherein the second software component depends on the first software component;

a version manager means for maintaining version information of the upgrade of the second software component of a network device including requesting the version information from the network device and passing the version information to the component manager;

checking the version information of the upgrade of the second software component stored in the component cache;

storing the version manager in the component cache;

determining whether the component cache contains a current copy of the version manager;

requesting and receiving a current copy of the version manager from the network device; and

retrieving a current copy of the version manager from the component cache.

27. The apparatus as recited in claim 26, wherein the compatibility verification means automatically downloads an upgrade of the second software component.

28. The apparatus as recited in claim 26, wherein the compatibility verification means informs an operator of the apparatus of the second software component via the user interface means.

29. The apparatus as recited in claim 27, wherein the compatibility verification means checks version information of the copy of the upgrade of the second software component that is stored in the component cache to determine whether to download the upgrade of the second software component.

30. The apparatus as recited in claim 29, wherein the compatibility verification means stores a copy of a copy of the upgrade of the second software component in a component cache.

31. The apparatus as recited in claim 26, wherein the processing means further comprises:

a management means for collecting attributes of the second software component; and

manipulating the second software component according to the attributes.

32. The apparatus as recited in claim 31, wherein the management means further comprises:

means for downloading a copy of an upgrade of the second software component as part of executing an instance of the processing means; and

means for replacing an existing version of the second software component with the copy of the upgrade of the second software component that has been downloaded in the same instance.