Software change modeling for network devices

• US 8,196,133 B2
• Filed: 04/23/2008
• Issued: 06/05/2012
• Est. Priority Date: 12/02/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Kakumani, Badari, Darling, Glen, Balint, Matthew
• Primary Examiner(s): NGUYEN, PHILLIP H
• Application Number:
  US12/107,874
• Publication Number:
  US 20080209413A1
• Time in Patent Office: 1,504 Days
• Field of Search: 717/172, 717/173, 717/177, 717/178, 717/171, 717/176
• US Class Current: 717/172
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/45537 Provision of facilities of other operating environments, e.g. WINE I/O emulation G06F13/105

Abstract

A method for software change modeling for network devices provides dynamic (on the device) and static (computer) change modeling. The same source code and libraries are used for both modeling applications, allowing a user to see the impact of activating or deactivating specific software modules without affecting the actual node. A master node passes a node the identity of the software package(s) to be updated and the dependencies. The node notifies its running processes about the update. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, it returns a veto to the node which sends a list of the processes that are impacted along with the reasons why to the master node.

Claims

1. A method of software change modeling for nodes in a distributed network of nodes, the method comprising the computer-implemented steps of:

receiving, from a master node at a node in the distributed network of nodes, a software update for the node,

wherein the software update contains a set of one or more software packages,

wherein each software package of the set of software packages contains at least one software module with corresponding software dependency information,

receiving, from the master node at the node, identities of one or more software packages to be updated and software dependency information; and

determining, based on the software dependency information, at the node, one or more processes which are executed on the node at a time the identities are received at the node, and execution of which will be affected by the software update.

2. A method as recited in claim 1, further comprising receiving, from the master node, a notification that a software update is being requested.

3. A method as recited in claim 1, wherein:

the method further comprising notifying one or more processes on the node that have indicated interest in software updates that the software update is being requested;

each notified process evaluates the effect that the software update will have on its operation;

if a first notified process determines that the software update will degrade or have a negative impact on the node'"'"'s normal operation, then the first notified process returns a veto to the node; and

if a second notified process determines that the software update will have no negative effects, then the second notified process returns an acceptance of the software update to the node.

4. A method as recited in claim 3, further comprising:

waiting for all of the notified processes to return results of their respective evaluations; and

after all of the notified processes have reported to the node, notifying the master node if any of the processes have vetoed the software update.

5. A method as recited in claim 4, wherein the master node displays, to a user, a node identifier of the node and process identifiers of one or more processes that have vetoed the software update.

6. A method as recited in claim 1, wherein a user initiates the software update by installing an image containing the software update onto the master node.

7. A method as recited in claim 6, wherein the user indicates what nodes and which software package(s) are to be updated.

8. A method as recited in claim 1, wherein each software package of the set of software packages indicates the type of node to which said each software package applies.

9. A method as recited in claim 1, wherein the software update contains a list of software packages destined for each node.

10. A method as recited in claim 1, wherein each software package of the set of one or more software packages contains version information, dependency information, and other metadata information pertaining to software in said each software package.

11. A method as recited in claim 10, wherein the metadata includes a list of application program interface (API) providers and consumers.

12. An apparatus of software change modeling for nodes in a distributed network of nodes, comprising:

a master node;

means for receiving, from the master node at a node in the distributed network of nodes, a software update for the node,

wherein the software update contains a set of one or more software packages,

wherein each software package of the set of software packages contains at least one software module with corresponding software dependency information,

means for receiving, from the master node at the node, identities of one or more software packages to be updated and software dependency information; and

means for determining, based on the software dependency information, at the node, one or more processes which are executed on the node at a time the identities are received at the node, and execution of which will be affected by the software update.

13. An apparatus as recited in claim 12, wherein:

the apparatus further comprising means for;

notifying one or more processes on the node that have indicated interest in software updates that the software update is being requested;

each notified process evaluates an effect that the software update will have on its operation;

if a first notified process determines that the software update will degrade or have a negative impact on the node'"'"'s normal operation, then the first notified process returns a veto to the node; and

if a second notified process determines that the software update will have no negative effects, then the second notified process returns an acceptance of the software update to the node.

14. An apparatus as recited in claim 13, further comprising means for:

waiting for all of the notified processes to return results of their respective evaluations; and

after all of the notified processes have reported to the node, notifying the master node if any of the processes have vetoed the software update.

15. An apparatus as recited in claim 14, wherein the master node displays, to a user, a node identifier of the node and process identifiers of one or more processes that have vetoed the software update.

16. A non-transitory computer-readable storage medium storing instructions for software change modeling for nodes in a distributed network of nodes, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

receiving, from a master node at a node in the distributed network of nodes, a software update for the node,

wherein the software update contains a set of one or more software packages,

wherein each software package of the set of software packages contains at least one software module with corresponding software dependency information,

receiving, from the master node at the node, identities of one or more software packages to be updated and software dependency information; and

determining, based on the software dependency information, at the node, one or more processes which are executed on the node at a time the identities are received at the node, and execution of which will be affected by the software update.

17. A non-transitory computer-readable storage medium as recited in claim 16, wherein:

the instructions include instructions which, when executed by the one or more processors, further cause the one or more processors to carry out the step of;

notifying one or more processes on the node that have indicated interest in software updates that the software update is being requested;

each notified process evaluates the effect that the software update will have on its operation;

if a first notified process determines that the software update will degrade or have a negative impact on the node'"'"'s normal operation, then the first notified process returns a veto to the node; and

if a second notified process determines that the software update will have no negative effects, then the second notified process returns an acceptance of the software update to the node.

18. A non-transitory computer-readable storage medium as recited in claim 17, wherein the instructions include instructions which, when executed by the one or more processors, further cause the one or more processors to carry out the steps of:

waiting for all of the notified processes to return results of their respective evaluations; and

after all of the notified processes have reported to the node, notifying the master node if any of the processes have vetoed the software update.

19. A non-transitory computer-readable storage medium as recited in claim 18, wherein the master node displays, to a user, a node identifier of the node and process identifiers of one or more processes that have vetoed the software update.

20. An apparatus comprising:

a node;

one or more processors;

instructions which, when executed by the one or more processors, cause the one or more processors to perform;

receiving, from a master node at the node in a distributed network of nodes, a software update for the node,

wherein the software update contains a set of one or more software packages,

wherein each software package of the set of software packages contains at least one software module with corresponding software dependency information,

receiving, from the master node at the node, identities of one or more software packages to be updated and software dependency information; and

determining, based on the software dependency information, at the node, one or more processes which are executed on the node at a time the identities are received at the node, and execution of which will be affected by the software update.

21. An apparatus as recited in claim 20, wherein:

the instructions include additional instructions which, when executed by the one or more processors, further cause the one or more processors to perform;

notifying one or more processes on the node that have indicated interest in software updates that the software update is being requested;

each notified process evaluates an effect that the software update will have on its operation;

if a first notified process determines that the software update will degrade or have a negative impact on the node'"'"'s normal operation, then the first notified process returns a veto to the node; and

if a second notified process determines that the software update will have no negative effects, then the second notified process returns an acceptance of the software update to the node.

22. An apparatus as recited in claim 21, wherein the instructions include additional instructions which, when executed by the one or more processors, further cause the one or more processors to perform:

waiting for all of the notified processes to return results of their respective evaluations; and

after all of the notified processes have reported to the node, notifying the master node if any of the processes have vetoed the software update.

23. An apparatus as recited in claim 22, wherein said master node displays the node identifiers and the processes that have vetoed the software update along with their reasons to a user.