Patent Grant
RE44299
The invention relates to a system and method for providing automated run-time input to network bootstrap processes.
During the startup of a computer device, a process commonly known as “booting” or “bootstrapping” is executed. The bootstrapping process employs a “bootstrap” program that contain a specific set of instructions to initialize and load the operating system that manages the computer device. Traditionally, such bootstrap programs were stored in the computer device's memory.
Many computer devices, however, currently support network booting processes that enable the devices to communicate with a remote server and obtain system files over a network. Examples of such processes include the use of the Pre-boot Execution Environment (PXE) to download an operating system from a network. Generally, for such processes, the computer device is configured with some type of code in non-volatile memory that will enable the device to obtain the identity of the appropriate bootstrap program from the remote server. The computer device may then gain access and load the identified bootstrap program from a remote file server. Once loaded, the bootstrap program then obtains the operating system image used to manage the device.
Existing network bootstrap programs are geared towards allowing the user to have the flexibility to boot in almost any manner he chooses. These programs typically require entry of input parameters by the user during the run time of the bootstrapping process and, therefore, have no mechanisms to automate the boot selection process or the entry of input parameters.
A system and method are provided for enabling automated run-time input during a network bootstrapping process. The system may include on or more computer devices communicatively coupled to a management server and a TFTP server. The management server may store one or more boot options used to provide a first set of bootstrap instructions. The TFTP server may store one or more configuration files used to control the boot process of the computer device. Each configuration file may include one or more macros.
The first set of bootstrap instructions may include a boot determination module and an initialization module. The boot determination module may be configured to determine an appropriate configuration file for the computer device and to determine the values for any macros included in the configuration file.
The initialization module may be configured to choose an arbitrary block of memory not used for other processing. This block of memory may be used to store the name of the configuration file and the values of the macros, as determined by the boot determination module.
When a computer device first powers on, a request may be sent to the management server to obtain a first set of bootstrap instructions. The first set of bootstrap instructions then determines a configuration file corresponding to the computer device based in part on a unique attribute associated with the computer device.
A memory block is then initialized with the name of the configuration file and values for any macros in the configuration file. The first set of bootstrap instructions then launches a second set of bootstrap instructions used to initiate the booting of the computer device.
The second set of bootstrap instructions may parse the memory block to determine the needed configuration file. The second set of bootstrap instructions may then parse the configuration file, resolving any macros by referring to the memory block.
In accordance with the various disclosed embodiments, the present invention contemplates systems and methods that enable automated run-time input to network bootstrap processes. These systems and methods allow a determination to be made at boot time whether a computer device should boot the operating system installed in the computer device's memory or download and boot a special purpose operating system to accomplish an assigned task. The required input parameters may be supplied without user input or intervention. For example, a memory block may be initialized to store parameter values that would otherwise require user input.
Consistent with these embodiments,
As depicted in
Management server 120 may be configured to store boot options 120n consistent with the operation of computer device 110n. According to some embodiments of the invention, management server 120 may comprise a PXE boot server.
TFTP server 130 may be constructed and arranged to store one or more configuration files 130n. Such configuration files may be designed to enable run-time inputs to a bootstrap program, in accordance with various embodiments of the present invention. Configuration file 130n may include one or more macros. The macros enable configuration file 130n to be used by a plurality of computer devices having different booting requirements. For example, configuration file 130n may store kernel parameters, such as, for example, the IP address of a policy server. By including a macros instead of the actual value of the parameter, the configuration file may be used by devices with differing parameters.
As noted above, when computer device 110n is powered on, it is configured to send a bootstrap request to management server 120. In response to this request, computer device 110n may receive an initial bootstrap program 200. As depicted in
Boot determination module 202 may also determine which configuration file 130n should be used. For example, determining which configuration file 130n to use may be determined by analyzing the computer's MAC address, serial number, hardware profile, and/or other characteristics. Boot determination module 202 may be configured to read data from the hard drive of computer device 110n to determine the appropriate configuration file. In other embodiments, the configuration file 130n may be passed to a second bootstrap program, which will be described below, via a custom DHCP tag.
Each configuration file 130a-130n may include macros as values for one or more fields. These macros may be resolved at runtime and their values substituted for the macro. As such, boot determination module 202 may also be configured to determine the values of any macros included in the selected configuration file. The appropriate configuration file and the appropriate values for macros within the configuration file may be determined by consulting a device profile associated with the computer device.
As noted above, initial bootstrap program 200 may also include an initialization module 204. Initialization module 204 may be configured to store the macro values and related information used in the configuration file 130n on computer device 110n. The stored information may be stored in a dedicated area of memory device 114n, that is, an area not used for other processing.
The number of macro-value pairs in memory block 300 is determined by the requirements of the configuration file. According to some embodiments, the first macro-value pair in macro-value field 310 may indicate the name of the configuration file to use. The name and value for each macro used in the configuration file may then be included in subsequent fields.
Turning now to
The initial NBP may be configured to determine the appropriate configuration file and to initialize a block of memory used to determine the appropriate configuration file and macro values, as depicted at operation 404. As discussed above, the appropriate configuration file may be determined by examining the MAC address and/or other device features. The device features may be compared to predetermined profiles to determine which configuration file is needed, and the values of any macros included in the configuration file. In other embodiments, the name of the configuration file may be passed to a secondary NBP.
As noted above, in addition to determining the appropriate configuration file at operation 404, the initial NBP may also initialize a memory block. Initializing the memory block may include storing the name of the appropriate configuration file and macro-value pairs used to resolve any macros in the configuration file. As discussed below, such initialization enables a secondary NBP to determine the appropriate configuration file and macro values.
Once the memory block has been initialized, a secondary NBP is launched, as depicted at operation 406. The initial NBP causes the secondary NBP to be loaded onto computer device 110n from management server 120. As depicted at operation 408, the secondary NBP may then parse the memory block to determine the appropriate configuration file. The secondary NBP enables the computer device to boot in accordance with the contents of the configuration file. As described above, the secondary NBP may receive the name of the configuration file through a customized DHCP tag, thus eliminating the need to parse the memory block to determine the appropriate configuration file. The secondary NBP may then parse the configuration file, looking up the values for any macros encountered in the configuration file by consulting the memory block.
An exemplary embodiment of the invention is further illustrated by the following example. Suppose that to boot a computer device for a specific task, the following configuration file is needed:
If this same service is deployed on a different server, then that server would need its own copy of “pxelinux.cfg/default”. The file contents would need to be modified to reflect the second server's address. According to various embodiments of the invention, the address in the configuration file may be changed to a macro so that its value is determined on the fly. As such, the configuration file would not have to be changed each time it is deployed to other servers.
As described above, the initial NBP would create and initialize an input memory block. The memory block would specify the name of the configuration file and the value of the address macro used in the configuration file. When the secondary NBP is loaded, it then parses the input memory block, determines the configuration file that it should use, and parses the configuration file. While parsing the configuration file, the secondary NBP encounters the address macro, looks up the value in the memory block, and substitutes the value for the macro.
In this manner, the computer device is capable of booting a special purpose operating system to accomplish an assigned task without the need for immediate user input or intervention.
While described above in reference to the use of configuration files and macros to provide runtime input, the system and method of the present invention may otherwise provide runtime input. According to some embodiments of the invention, boot determination module 202, described above, may be configured to obtain characteristics associated with a requesting computer device, in order to determine the run time parameters needed by the secondary bootstrap program.
The determined runtime parameters may be stored in memory device 114n. The secondary bootstrap program may then be loaded to complete the boot process. The secondary boot process may consult memory block 114n whenever user input would ordinarily be required. Rather than waiting for user input, the bootstrap program is able to continue by reading the appropriate values from memory block 114n.
Other embodiments, uses, and advantages of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification should be considered exemplary only, and the scope of the invention is accordingly intended to be limited only by the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6560699 | Konkle | May 2003 | B1 |
| 6598057 | Synnestvedt et al. | Jul 2003 | B1 |
| 6735692 | Murphrey et al. | May 2004 | B1 |
| 6810478 | Anand et al. | Oct 2004 | B1 |
| 7013385 | Abbondanzio et al. | Mar 2006 | B2 |
| 7085921 | Frye, Jr. | Aug 2006 | B2 |
| 7159106 | Meaney et al. | Jan 2007 | B2 |
| 20030005096 | Paul et al. | Jan 2003 | A1 |
| 20030005276 | French et al. | Jan 2003 | A1 |
| 20030217126 | Polcha et al. | Nov 2003 | A1 |
| 20040049671 | Miyamoto et al. | Mar 2004 | A1 |
| 20040268340 | Steeb et al. | Dec 2004 | A1 |
| 20050097310 | Chu et al. | May 2005 | A1 |
| 20060047792 | Dharmarajan et al. | Mar 2006 | A1 |
| 20060129788 | Maeda et al. | Jun 2006 | A1 |
| 20060143146 | Bognar | Jun 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11171266 | Jul 2005 | US |
| Child | 12756653 | US |
