Method and apparatus for software loading and initialization in a distributed network

• US 7,506,335 B1
• Filed: 11/29/2003
• Issued: 03/17/2009
• Est. Priority Date: 11/29/2003
• Status: Expired due to Fees

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Akiya, Nobushige, Balint, Matthew, Wooff, Douglas
• Primary Examiner(s): VU, TUAN A
• Application Number:
  US10/725,190
• Time in Patent Office: 1,935 Days
• Field of Search: 717168-178, 709/201, 709/226, 709221-223, 709/242, 709/248, 709219-220, 709/202, 713/2, 713/100, 713/164, 713/165, 713/201, 726/4, 726/6, 714/50, 714/4, 714/6
• US Class Current: 717/173
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A method for software loading and initialization in a distributed network of nodes. A master node provides a node information database and a software package database. A node performing an initial boot requests a boot image and software package download from the master node. The master node finds the node'"'"'s software configuration information in the node information database and sends the boot image and software packages to the node from the software package database. The node reboots into the boot image and verifies the software versions with the master node. If the node has the correct software, then it completes the boot sequence, otherwise, the master node sends the correct software packages to the node which then continues with the boot sequence.

Claims

1. A method of software loading and initialization in a distributed network of nodes, the method comprising:

persistently storing, in a first storage of a master node, a plurality of software packages and a plurality of boot images, wherein the plurality of software packages and the plurality of boot images will be used by the nodes in the distributed network;

persistently storing, in a second storage of the master node, software version information and node type information for each node in the distributed network;

receiving, at the master node, a request for a boot image and software packages from a node, in the distributed network, that is performing an initial boot;

based on the request, the master node determining software version information of the node to retrieve from the second storage;

the master node retrieving the software version information of the node from the second storage;

the master node determining, based on the software version information of the node, a boot image of the plurality of boot images and one or more software packages of the plurality of software packages to extract from the first storage;

the master node extracting the boot image and the one or more software packages from the first storage;

the master node delivering, to the node, the boot image and the one or more software packages;

wherein said node;

(a) stores the boot image and the one or more software packages in its local persistent storage,

(b) extracts software version information from the one or more software packages and stores the software version information in the local persistent storage,

(c) reboots and executes the boot image stored in the local persistent storage, and

(d) in response to executing the boot image, verifies the software version information with said master node by sending the software version information to the master node;

the master node receiving the software version information from the node;

in response to receiving the software version information, the master node determining whether the node has the correct software versions;

in response to the master node determining that said node does not have the correct software versions, then the master node retrieving correct software packages from the first storage and sending the correct software packages to said node, wherein said node stores the correct software packages in the local persistent storage and completes booting by executing the correct software packages stored in the local persistent storage.

2. A method as recited in claim 1, wherein said node, based on a command from said master node, does not store the one or more software packages in its local persistent storage device, allowing said master node to download test software packages to said node and temporarily run said node using the test software packages, and wherein when said node reboots, the test software packages will no longer exist on said node.

3. A method as recited in claim 1, wherein if said node has the correct software versions, then said node completes booting by executing the one or more software packages stored in the local persistent storage.

4. A method as recited in claim 1, wherein the master node has the ability to categorize nodes into classes where all of the nodes in a particular class of nodes have the same software configuration and may have differing processor types.

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

6. A method as recited in claim 1, wherein the boot image is customized for a particular type of node and provides basic low-level communications.

7. A method as recited in claim 1, further comprising:

executing a composite image, that is installed by a user onto said master node, to create a subset of the plurality of boot images, a subset of the plurality of software packages, and node information; and

placing the subset of the plurality of boot images and the subset of the plurality of software packages in the first storage and the node information in the second storage.

8. A method as recited in claim 1, wherein the master node retrieving the software version information creates the software version information from the second storage based on functional features included in the request.

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

the request includes node type information of the node;

the master node determining software version information of the node includes the master node using the node type information of the node to determine the software version information of the node.

10. A computer-readable storage medium carrying one or more sequences of instructions for software loading and initialization in a distributed network of nodes, which instructions, when executed by one or more processors, cause the one or more processors to perform:

persistently storing, in a first storage of a master node, a plurality of software packages and a plurality of boot images, wherein the plurality of software packages and the plurality of boot images will be used by the nodes in the distributed network;

persistently storing, in a second storage of the master node, software version information and node type information for each node in the distributed network;

receiving, at the master node, a request for a boot image and software packages from a node, in the distributed network, that is performing an initial boot;

based on the request, the master node determining software version information of the node to retrieve from the second storage;

the master node retrieving the software version information of the node from the second storage;

the master node determining, based on the software version information of the node, a boot image of the plurality of boot images and one or more software packages of the plurality of software packages to extract from the first storage;

the master node extracting the boot image and the one or more software packages from the first storage;

the master node delivering, to the node, the boot image and the one or more software packages,

wherein said node;

(a) stores the boot image and the one or more software packages in its local persistent storage,

(b) extracts software version information from the one or more software packages and stores the software version information in the local persistent storage,

(c) reboots and executes the boot image stored in the local persistent storage, and

(d) in response to executing the boot image, verifies the software version information with said master node by sending the software version information to the master node;

the master node receiving the software version information from the node;

in response to receiving the software version information, the master node determining whether the node has the correct software versions;

in response to the master node determining that said node does not have the correct software versions, then the master node retrieving correct software packages from the first storage and sending the correct software packages to said node, wherein said node stores the correct software packages in the local persistent storage and completes booting by executing the correct software packages stored in the local persistent storage.

11. A computer-readable storage medium as recited in claim 10, wherein said node, based on a command from said master node, does not store the one or more software packages in its local persistent storage device, allowing said master node to download test software packages to said node and temporarily run said node using the test software packages, and wherein when said node reboots, the test software packages will no longer exist on said node.

12. A computer-readable storage medium as recited in claim 10, wherein if said node has the correct software versions, then said node completes booting by executing the one or more software packages stored in the local persistent storage.

13. A computer-readable storage medium as recited in claim 10, wherein the master node has the ability to categorize nodes into classes where all of the nodes in a particular class of nodes have the same software configuration and may have differing processor types.

14. A computer-readable storage medium as recited in claim 10, wherein each of the one or more software packages contains version information, dependency information, and other metadata information pertaining to software in the package.

15. A computer-readable storage medium as recited in claim 10, wherein the boot image is customized for a particular type of node and provides basic low-level communications.

16. A computer-readable storage medium as recited in claim 10, further comprising:

executing a composite image, that was installed by a user, to create a subset of the plurality of boot images, a subset of the plurality of software packages, and node information; and

placing the subset of the plurality of boot images and the subset of the plurality of software packages in the first storage and the node information in the second storage.

17. A computer-readable storage medium as recited in claim 10, wherein the master node retrieving the software version information creates the software version information from the second storage based on functional features included in the request.

18. A computer-readable storage medium as recited in claim 10, wherein:

the request includes node type information of the node;

the master node determining software version information of the node includes the master node using the node type information of the node to determine the software version information of the node.

19. An apparatus of software loading and initialization in a distributed network of nodes, comprising:

a master node;

a first storage on said master node for persistently storing a plurality of software packages and a plurality of boot images that the nodes in the distributed network will use;

a second storage on said master node for persistently storing software version information and node type information for each node in the network;

means for receiving a request for a boot image and software packages from a node, in the distributed network, that is performing an initial boot;

means for the master node determining, based on the request, software version information of the node to retrieve from the second storage;

means for the master node retrieving the software version information of the node from the second storage;

means for the master node determining, based on the software version information of the node, a boot image of the plurality of boot images and one or more software packages of the plurality of software packages to extract from the first storage;

means for the master node extracting the boot image and the one or more software packages from the first storage; and

means for the master node delivering, to the node, the boot image and the one or more software packages,

wherein said node;

(a) stores the boot image and the one or more software packages in its local persistent storage,

(b) extracts software version information from the one or more software packages and stores the software version information in the local persistent storage,

(c) reboots and executes the boot image stored in the local persistent storage, and

(d) in response to executing the boot image, verifies the software version information with said master node by sending the software version information to the master node;

means for the master node receiving the software version information from the node;

means for the master node determining, in response to receiving the software version information, whether the node has the correct software versions;

means for the master node retrieving, in response to the master node determining that said node does not have the correct software versions, correct software packages from the first storage and sending the correct software packages to said node, wherein said node stores the correct software packages in the local persistent storage and completes booting by executing the correct software packages stored in the local persistent storage.

20. An apparatus as recited in claim 19, wherein said node, based on a command from said master node, does not store the one or more software packages in its local persistent storage device, allowing said master node to download test software packages to said node and temporarily run said node using the test software packages, and wherein when said node reboots, the test software packages will no longer exist on said node.

21. An apparatus as recited in claim 19, wherein if said node has the correct software versions, then said node completes booting by executing the one or more software packages stored in the local persistent storage.

22. An apparatus as recited in claim 19, wherein the master node has the ability to categorize nodes into classes where all of the nodes in a particular class of nodes have the same software configuration and may have differing processor types.

23. An apparatus as recited in claim 19, wherein each of the one or more software packages contains version information, dependency information, and other metadata information pertaining to software in the package.

24. An apparatus as recited in claim 19, wherein the boot image is customized for a particular type of node and provides basic low-level communications.

25. An apparatus as recited in claim 19, further comprising:

means for executing a composite image to create a subset of the plurality of boot images, a subset of the plurality of software packages, and node information; and

means for placing the subset of the plurality of boot images and the subset of the plurality of software packages in the first storage and the node information in the second storage.

26. An apparatus as recited in claim 19, wherein said means for the master node retrieving the software version information creates the software version information from the second storage based on functional features included in the request.

27. An apparatus as recited in claim 19, wherein:

the request includes node type information of the node;

the means for the master node determining software version information of the node includes means for the master node using the node type information of the node to determine the software version information of the node.

28. A system for software loading and initialization in a distributed network of nodes, the system comprising:

a master node;

a node in the distributed network;

a first storage on the master node, wherein the first storage persistently stores a plurality of boot images and a plurality of software packages that nodes in the distributed network will use;

a second storage on the master node, wherein the second storage persistently stores software version information and node type information for each node in the distributed network;

one or more processors on the master node;

one or more sequences of instructions which, when executed by the one or more processors on the master node, cause the one or more processors on the master node to perform;

receiving a request for a boot image and software packages from the node that is performing an initial boot;

based on the request, the master node determining software version information of the node to retrieve from the second storage;

the master node retrieving the software version information of the node from the second storage;

the master node determining, based on the software version information of the node, a boot image of the plurality of boot images and one or more software packages of the plurality of software packages to extract from the first storage;

the master node extracting the boot image and the one or more software packages from the first storage;

the master node delivering, to the node, the boot image and the one or more software packages;

one or more other processors on the node;

one or more other sequences of instructions which, when executed by the one or more other processors on the node, cause the one or more other processors on the node to perform;

storing the boot image and the one or more software packages in local persistent storage of the node;

extracting software version information from the software packages;

storing the software version information in the local persistent storage;

executing the boot image, that is stored in the local persistent storage, to reboot the node;

in response to executing the boot image, verifying the software version information with the master node by sending the software version information to the master node;

one or more further sequences of instructions which, when executed by the one or more processors on the master node, cause the one or more processors on the master node to perform;

receiving the software version information from the node;

in response to receiving the software version information, determining whether the node has the correct software versions;

retrieving correct software packages from the first storage and sending the correct software packages to the node in response to determining that the node does not have the correct software versions;

one or more additional sequences of instructions which, when executed by the one or more processors on the node, cause the one or more processors on the node to perform;

in response to receiving the correct software packages from the master node, storing the correct software packages in the local persistent storage and executing the correct software packages stored in the local persistent storage to complete booting.

29. A system as recited in claim 28, wherein the node, based on a command from said master node, does not store the software packages in the local persistent storage device, allowing said master node to download test software packages to said node and temporarily run said node using the test software packages, and wherein when said node reboots, the test software packages will no longer exist on said node.

30. A system as recited in claim 28, wherein the one or more other sequences of instructions which, when executed by the one or more other processors, further cause the one or more other processors to perform executing the one or more software packages stored in the local persistent storage to complete booting if the node has the correct software versions.

31. A system as recited in claim 28, wherein the master node has the ability to categorize nodes into classes where all of the nodes in a particular class of nodes have the same software configuration and may have differing processor types.

32. A system as recited in claim 28, wherein each of the one or more software packages contains version information, dependency information, and other metadata information pertaining to software in the package.

33. A system as recited in claim 28, wherein the boot image is customized for a particular type of node and provides basic low-level communications.

34. A system as recited in claim 28, wherein the one or more sequences of instructions which, when executed by the one or more processors, further cause the one or more processors to perform:

executing a composite image, that a user installs on the master node, to create a subset of the plurality of boot images, a subset of the plurality of software packages, and node information; and

placing the subset of the plurality of boot images and the subset of the plurality of software packages in the first storage and the node information in the second storage.

35. A system as recited in claim 28, wherein the master node retrieving the software version information creates the software version information from the second storage based on functional features included in the request.

36. A system as recited in claim 28, wherein:

the request includes node type information of the node;

the master node determining software version information of the node includes the master node using the node type information of the node to determine the software version information of the node.