JP4863154B2 - Boot image providing system and operation method thereof, boot node device, boot server device, and operation program thereof - Google Patents

Boot image providing system and operation method thereof, boot node device, boot server device, and operation program thereof Download PDF

Info

Publication number
JP4863154B2
JP4863154B2 JP2005094858A JP2005094858A JP4863154B2 JP 4863154 B2 JP4863154 B2 JP 4863154B2 JP 2005094858 A JP2005094858 A JP 2005094858A JP 2005094858 A JP2005094858 A JP 2005094858A JP 4863154 B2 JP4863154 B2 JP 4863154B2
Authority
JP
Japan
Prior art keywords
image
boot
hardware configuration
configuration information
startup
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2005094858A
Other languages
Japanese (ja)
Other versions
JP2006277277A (en
Inventor
智義 菅原
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to JP2005094858A priority Critical patent/JP4863154B2/en
Publication of JP2006277277A publication Critical patent/JP2006277277A/en
Application granted granted Critical
Publication of JP4863154B2 publication Critical patent/JP4863154B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to a system for providing a boot image composed of a group of files necessary for booting a computer, and in particular, a boot image providing system for providing a boot image from a server via a network to a computer that performs network boot. And a method.

  In network booting, a boot image composed of an OS (operating system) and application files required when the computer is booted is held on a server separate from the computer. This is a technology that reads a boot image and boots.

  As a conventional network boot method, PXE (Preboot Execution Environment) boot is well known. In the PXE boot, the MAC address is transmitted from the network card to the server when the computer is booted, and the activation image corresponding to the MAC address is transmitted to the computer. In the network boot method using PXE boot, the administrator needs to set the startup image for each computer in advance on the server side that provides the startup image.

  An example of a conventional startup image providing system is described in Patent Document 1. This conventional startup image providing system includes a user terminal having preboot means and a server storing a startup image including an OS and application programs executed on the user terminal. The server further includes means for authenticating the user and means for transmitting the activation image to the user terminal.

  The conventional boot image providing system having such a configuration operates as follows. That is, when booting the user terminal, the user information selected by the user among the user information for OS boot setting stored in the storage medium accessed by the user terminal is transmitted to the server under the control of the preboot means. The server authenticates the user terminal based on the user information transmitted from the user terminal and transmits a startup image including the specified OS and application to the user terminal. Let it boot. Here, the user information includes the type of OS to be started, the type of application, security information, and a boot option delivered to the OS.

Patent Document 2 discloses a system that installs a boot image that matches a hardware configuration when producing a computer system having a hardware configuration according to order information from a customer. Specifically, a master ID is assigned to the hardware configuration corresponding to the order information, and an installation activation recording medium storing the master ID and the activation program is provided to the computer system. When the installation start recording medium is loaded in the computer system and executed, the master ID is transmitted to the installation system via the network, and the start image including the OS and the application generated in advance corresponding to the master ID is displayed on the installation system side. Selected and installed on the computer system via the network.
JP 2001-356913 A JP 2002-323977 A

  The first problem is that a conventional startup image providing system cannot be provided unless a startup image corresponding to the hardware configuration of the user terminal is prepared in advance on the server side.

  The reason is that in Patent Document 1, since hardware configuration information is not included in user information sent from a user terminal, it is necessary to make a part depending on the hardware in advance for each user terminal. Further, Patent Document 2 has a fundamental difference between “install” and “boot”, and the master ID indirectly indicates the hardware configuration, but it is the one at the time of shipment of the computer. When the hardware configuration is changed later on the user side, a startup image corresponding to the changed hardware configuration cannot be provided.

  An object of the present invention is to provide a boot image providing system capable of creating and providing a boot image according to the hardware configuration at the time of booting.

  The first boot image providing system of the present invention receives a boot image storage means for storing two or more boot images, hardware configuration information, and a boot image most suitable for the hardware configuration indicated by the hardware configuration information. Boot image selection means to select, boot image change means for rewriting data at a specific position shown in the boot image change table in the boot image with data included in the hardware configuration information, and transmitting the rewritten boot image A boot image transmission means, and when the hardware configuration of the node to be booted is given, the boot image selection means selects a boot image from the boot image storage unit, and a part of the boot image is boot image change means Change the boot image and change the boot image There by sending a node activation, it is possible to provide a boot image the hardware configuration information provided is suitable for the hardware depicted.

  The second boot image providing system of the present invention receives a boot image storage means for storing two or more boot images, hardware configuration information, and a boot image most suitable for the hardware configuration indicated by the hardware configuration information. The startup image selection means to be selected, the data at the specific position shown in the startup image change table in the startup image, the data included in the hardware configuration information, and the data after the calculation by the startup image change rule A boot image changing unit for rewriting and a boot image transmitting unit for transmitting the rewritten boot image, and when the hardware configuration of the node to be booted is given, the boot image selecting unit receives the boot image from the boot image storage unit; Select a part of the boot image Change di changing means, by sending to the node where the boot image transmission means a boot image has been changed to start, it is possible to provide a boot image the hardware configuration information provided is suitable for the hardware depicted.

  The third boot image providing system of the present invention receives boot image storage means for storing two or more boot images, hardware configuration information and software configuration information, and for each program designated by the software configuration information, the hardware Boot image selection means for selecting a boot image most suitable for the hardware configuration indicated by the hardware configuration information; boot image creation means for creating a boot image by combining the selected boot images; And a boot image changing means for rewriting data at a specific position shown in the boot image change table with data included in the hardware configuration information, and a boot image transmitting means for sending the rewritten boot image. Given the hardware configuration of the node The boot image selection means selects a plurality of boot images from the boot image storage unit, the boot image creation means creates a boot image by combining the boot images, and creates one boot image. The boot image changing means changes the boot image, and the boot image transmitting means sends the changed boot image to the node to be booted, thereby providing a boot image suitable for the hardware indicated by the given hardware configuration information Can do.

  An advantage of the present invention is that it is possible to provide a startup image suitable for the current hardware configuration of the user terminal. The reason is that the boot server device creates a boot image based on the current hardware configuration information of the user terminal and provides it to the boot node device.

(First embodiment)
Next, a first embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing the configuration of the present embodiment. Referring to FIG. 1, a boot image providing system according to the present embodiment includes a boot server device (hereinafter simply referred to as “boot server”) 100, a boot node device (hereinafter simply referred to as “boot node”) 200, And network 300.

  The boot server 100 and the boot node 200 are both computers having a CPU (Central Processing Unit) and a memory. Further, the boot server 100 and the boot node 200 extend at least one of an HDD (Hard Disk Drive), an FDD (Floppy (registered trademark) Disk Drive), a CD-ROM (Compact Disk Read Only Memory), and other external devices. It can also be included as a device. The boot server 100 and the boot node 200 are connected by a network 300 and can exchange data. As a protocol used for data exchange, IP (Internet Protocol), which is an Internet standard protocol, can be used, but other communication protocols can also be used. The boot node 200 performs a network boot by acquiring a startup image provided by the boot server 100 via the network 300. Note that the boot node 200 does not necessarily have to be a dedicated network boot terminal, and may have a configuration of booting other than network booting, that is, booting from an HDD, CD-ROM, or flash memory. In the present embodiment, a configuration including one boot server and one boot node is shown, but a configuration including a plurality of boot servers and a plurality of boot nodes is also possible.

  The boot server 100 includes a startup image selection unit 101, a startup image storage unit 102, a startup image transmission unit 103, and a startup image change unit 104.

  The boot image selection unit 101 selects one boot image closest to the hardware configuration from the boot image storage unit 102 based on the hardware configuration information included in the boot image transmission request transmitted from the boot node 200. The activation image is transferred to the activation image changing unit 104.

  As shown in FIG. 2, the activation image transmission request includes at least location information of the request transmission source and request-side hardware configuration information. Here, an IP address can be used for the location information. Further, the request-side hardware configuration information can include, for example, a machine type, a CPU or chipset type, a memory or disk size, and the like. FIG. 3 shows an example of request side hardware configuration information. Note that names such as the machine type name and chipset type name in FIG. 3 are not real names but are assumed for convenience of explanation.

  Here, a method in which the boot image selection unit 101 selects the boot image closest to the requesting hardware configuration information will be described.

  The boot image selection unit 101 compares the hardware configuration information in the image included in the boot image and the request side hardware configuration information with respect to the hardware type indicated in the boot image comparison table, so that the hardware configuration is the most. Select a close boot image.

  As shown in FIG. 4, the boot image comparison table is composed of hardware types to be compared with boot image identifiers. The hardware type is a machine type, a CPU type, or the like, and is the same as that placed on the left side of the equal sign (=) of the request side hardware configuration information. In addition, in the case of Windows (registered trademark), for example, in-image hardware configuration information is included under HKEY_LOCAL_MACHINE in the registry.

  The boot image selection unit 101 includes information corresponding to the hardware type indicated in the boot image comparison table in the request side hardware configuration information and the hardware type in the hardware configuration information in the image. Are compared with each other, and when both of the hardware types shown in the startup image comparison table match, it is determined that the hardware configuration is the closest.

  The boot image storage unit 102 stores at least one boot image for booting the boot node 200 and returns one of the boot images in response to a request from the boot image selection unit 101. The boot image storage unit 102 may be configured to be able to add a boot image created externally manually or to be able to delete the stored boot image.

  The startup image changing unit 104 changes a part of the startup image and returns a startup image created as a result. One method of changing the boot image is to use a boot image change table.

  As shown in FIG. 5, the activation image change table includes an address for indicating a specific position in the activation image, its size, and the type of data to be recorded at the address. Here, the data type indicates the type of hardware configuration information.

  Upon receiving the request side hardware configuration information and the selected start image, the start image changing unit 104 first refers to the data type of the start image change table, and sends data matching the data type to the request side hardware. Next, the part indicated by the address and size of the activation image change table of the activation image is changed with the data extracted from the request side hardware configuration information.

  The startup image transmission unit 103 transmits the changed startup image passed from the startup image change unit 104 to the transmission source of the startup image transmission request. When the activation image selection unit 101 fails to select the activation image, the activation image transmission unit 103 transmits selection error information to the transmission source of the activation image transmission request. The selection error information includes at least an error code indicating a selection error.

  Here, the boot image refers to a group of files required for booting the computer. For example, a boot image is an executable file of an OS kernel part, an executable file of a daemon program that provides an OS service, a dynamic library file used by them, a configuration file, and an application that is automatically started after the OS is started Includes program execution files, library files, configuration files, and directories for storing them.

  The boot node 200 includes an HW (hardware) information acquisition unit 201, a startup image request unit 202, and a startup processing unit 203.

  The HW information acquisition unit 201 acquires information on hardware components constituting the boot node 200. The hardware configuration information acquired here is included in the startup image transmission request. An implementation example of the HW information acquisition unit 201 is shown below.

As an implementation example of the HW information acquisition unit 201, a configuration in which information on hardware components that configure the boot node 200 is acquired using an IPMI (Intelligent Platform Management Interface) is conceivable. For example, an NEC Express5800 computer (server) has an on-board operation management chip called BMC (Baseboard Management Controller) mounted on a motherboard, and each BMC is connected to the motherboard and each hardware connected to the motherboard. Various information about parts is collected according to the IPMI specification and transmitted to other places. Therefore, such BMC can be used as the HW information acquisition unit 201. The following documents are available as IPMI documents.
(1) IPMI v2.0 specifications Document
ftp://download.intel.com/design/servers/ipmi/IPMIv2_0rev1_0.pdf
(2) IPMI Platform Management FRU Information Storage Definition
ftp://download.intel.com/design/servers/ipmi/fru1011.pdf
Document (1) describes the overall specifications of IPMI, and document (2) describes the information recording structure of FRU (Field Replaceable Unit) which is a module constituting the computer. In particular, pages 412 to 414 of document (1) describe FRU commands such as “Get FRU Inventory Area Info”, and page 8 of document (2) describes Product Info Area Format.

  As another implementation example of the HW information acquisition unit 201, the boot node 200 is provided with a readable / writable non-volatile memory (for example, a flash memory) for recording the hardware configuration information of the own node, and is collected in the process of booting the OS. A configuration is conceivable in which the hardware configuration information is written to the memory and the hardware configuration information written to the memory is acquired as the latest hardware configuration information of the own node at the next network boot.

  Referring to FIG. 1 again, the boot image request unit 202 creates the boot image transmission request described above, and transmits the created boot image transmission request to the boot server 100.

  The boot processing unit 203 receives the boot image and performs boot processing of the OS included in the received boot image. Here, the startup process means a general OS startup process. For example, the OS included in the received startup image is loaded into the memory, and the process of passing control to the OS startup process is performed.

  The network 300 can be any network as long as it can transfer data included in the startup image. For example, it is conceivable to use Ethernet (registered trademark) widely used in IP communication.

  Next, the overall operation of this embodiment will be described in detail with reference to FIGS.

  When the power of the boot node 200 is turned on, the HW information acquisition unit 201 acquires the hardware configuration information of the boot node 200 (step S101). The hardware configuration information as illustrated in FIG. 3 acquired here is transferred to the activation image request unit 202. The boot image request unit 202 creates a boot image transmission request as shown in FIG. 2 from the hardware configuration information and the location information of the own node, and broadcasts it or IP address for the server set in the BIOS in advance. By transmitting to the address, a startup image transmission request is transmitted to the boot server 100 (step S102).

  On the other hand, the boot image selection unit 101 of the boot server 100 that has received the boot image transmission request searches for the boot image included in the boot image storage unit 102 based on the request-side hardware configuration information and the boot image comparison table (step). S103). If at least one boot image most suitable for the request side hardware configuration information is found (Y in step S104), the boot image is transferred to the boot image changing unit 104 together with the request side hardware configuration information, and the boot image is changed. The unit 104 selects an entry corresponding to the boot image passed from the boot image change table, and changes data at a specific address of the boot image according to the contents of the entry (step S105). If two or more activation images are found as a result of the search in step S103, an appropriate one may be selected at random, or the first activation image found may be selected.

  Next, the activation image changed in step S105 is transferred to the activation image transmission unit 103, and the activation image transmission unit 103 transmits the received activation image to the boot node indicated by the location information of the transmission source node. (Step S106). The activation processing unit 203 of the boot node 200 that has received the activation image activates the OS of the received activation image (step S107).

  On the other hand, if no activation image is found in step S103 (N in step S104), the activation image selection unit 101 transmits an error code indicating that the activation image selection has failed and a transmission included in the activation image transmission request. The location information of the original node is passed to the activation image transmission unit 103, and the activation image transmission unit 103 transmits the selection error information including the error code to the boot node indicated by the location information of the transmission source node (step). S108). The activation processing unit 203 of the boot node 200 that has received the selection error information fails in the activation process (step S109).

Next, the effect of this embodiment will be described. In the present embodiment, the hardware configuration of the boot node is acquired, the startup image closest to the hardware configuration is selected, and the parts with different hardware configurations are changed according to the hardware configuration of the boot node. Since it is configured to be provided to the boot node after that, the number of boot images to be saved can be reduced. This has the effect of reducing the storage capacity that the boot server should have.
(Second Embodiment)
Next, a second embodiment of the present invention will be described.

  In the first embodiment, the boot image changing unit 104 changes a part of the boot image based on the request side hardware configuration information. However, in the present embodiment, the request side hardware configuration information is processed. After changing to a different value, the data of a specific part of the boot image can be replaced with that value. The configuration of the present embodiment is different from the configuration of the first embodiment in that a second startup image change unit is provided instead of the startup image change unit 104, but all other configurations are the first implementation. It is the same as the form.

  The second startup image change unit changes a part of the startup image using the startup image change table and the startup image change rule, and returns the startup image created as a result.

  The activation image change table is the same as that in the first embodiment. That is, as shown in FIG. 5, the address for indicating a specific position in the activation image, its size, and the type of data to be recorded at that address are included. Here, the data type indicates the type of hardware and the type of data included in the activation image change rule.

  The activation image change rule includes a data type and a change rule for deriving the data type. The change rule can include an arithmetic expression or a function. Data included in the hardware configuration information can be used as the parameter included in the change rule. An example of the activation image change rule is shown in FIG. For example, when a machine memory size (MEMSIZE) is given as hardware configuration information, the file cache size (FileCacheSize) is obtained by calculation. In this example, FileCacheSize is calculated to be a quarter of MEMSIZE.

  When receiving the requesting hardware configuration information and the selected boot image, the second boot image changing unit first refers to the data type of the boot image change table and changes the data that matches the data type to the change rule. Alternatively, it is extracted from the request-side hardware configuration information, and then the portion indicated by the address and size of the startup image change table of the startup image is changed with the data extracted from the request-side hardware configuration information.

  Next, the effect of this embodiment will be described. In the present embodiment, in addition to the effect of the first embodiment, information that is not included in the hardware configuration of the boot node can be directly processed by calculation to change a part of the boot image. . For this reason, the changeable part in a starting image can be increased, and also the effect that the number of starting images which should be preserve | saved can be reduced can be acquired.

  Next, modified examples of the first and second embodiments will be described.

  In the first and second embodiments, a file group is used as a startup image, but a hibernation image can be used instead of the file group. The hibernation image means data on a memory (main memory) where a running OS or application is developed. This image is used in the form of being stored in the HDD when the computer is temporarily put into the hibernation state, and read from the HDD into the memory when the computer is restarted.

In the present modification, the boot server startup image storage unit 102 in the first or second embodiment stores the above hibernation image as a startup image, and the boot node startup processing unit 203 Instead of performing network boot processing, the network is changed to perform hibernation return processing via the network. At this time, instead of acquiring all of the hibernation images at once, it is possible to acquire and activate only the minimum image necessary for activation, and then acquire the remaining images as necessary.
(Third embodiment)
Next, a third embodiment of the present invention will be described in detail with reference to the drawings.

  In the modification of the first and second embodiments, a method of using a hibernation image as a startup image has been shown. When a hibernation image is used as a boot image, the hibernation image is a file in which the data on the memory (main memory) on which the running OS or application is deployed is directly used as a file. It was not possible to add an application or upgrade the OS alone. In the third embodiment, partial hibernation images are combined to create an entire hibernation image. In the following description, the startup image is the same as that shown in the modifications of the first and second embodiments, and indicates a hibernation image required for starting up the computer.

  FIG. 8 is a block diagram showing the configuration of the present embodiment.

  Referring to FIG. 8, the boot image providing system according to the present embodiment includes a boot server device (hereinafter simply referred to as a boot server) 110, a boot node device (hereinafter simply referred to as a boot node) 200, and a network 300. Is done.

  The boot server 110 and the boot node 200 have substantially the same configuration as the boot server 100 and the boot node 200 of the first embodiment, respectively. That is, both are computers having a CPU and a memory, can have expansion devices, are connected by the network 300, and can exchange data. Similarly to the boot node 200, the boot node 200 may perform a network boot and have an activation method other than the network boot. In the present embodiment, a configuration including one boot server and one boot node is shown, but a configuration including a plurality of boot servers and a plurality of boot nodes is also possible.

  The boot server 110 includes a startup image selection unit 111, a startup image storage unit 112, a startup image creation unit 113, a startup image change unit 104, and a startup image transmission unit 103.

  The boot image selection unit 111 selects the OS and application memory images (hereinafter referred to as individual boot images) from the boot image storage unit 112 based on the request-side hardware configuration information and software configuration information, and the individual boot images. To the activation image creation unit 113. The activation image transmission request includes at least location information of the request transmission source and request-side hardware configuration information, as in the first best mode. The software configuration information is information included in an entry selected based on the identifier of the boot node from the software configuration information table as shown in FIG. The software configuration information table includes entries indicating the software configuration information of the boot node. Each entry includes a list of boot node identifiers and names of programs to be started, that is, OS and application program names. Note that location information similar to that included in the startup image transmission request can be used as the identifier of the boot node, but the name of the boot node may also be used. Further, the software configuration information may be transmitted from the boot node instead of being searched from the software configuration information table.

The startup image storage unit 112 stores individual startup images of the OS and various applications as files. In order to create an OS individual boot image, hibernation can be performed while no application is running. In addition, a technique called a checkpoint may be used to create an individual activation image of an application. Checkpoint is a technology that saves the image on the memory of the program being executed and the execution state information of the program managed in the OS to a hard disk or the like. Condor developed at the University of Wisconsin, USA
(http://www.cs.wisc.edu/condor/checkpointing.html)
And SCore developed by the New Information Processing Development Organization
(http://www.pccluster.org/score/dist/score/html/en/reference/scored/checkpoint.html) Here, the boot image selection unit 111 selects an individual boot image. A method will be described. When the activation image selection unit 111 receives the activation image transmission request, the activation image selection unit 111 specifies the software configuration information based on the location information of the boot node included in the request. First, a candidate individual boot image is selected from the boot image storage unit 112 from the OS information included in the identified software configuration information. One method for selecting a boot image of a candidate OS is to make a part of the file name of the individual boot image the same as the OS name included in the software configuration information and select a file of the individual boot image having the same OS name. Is the method.

  Next, based on the request side hardware configuration information, an individual startup image closest to the request side hardware configuration is further selected from the individual startup image candidates. When the selection of the OS individual boot image is completed, next, for the application included in the software configuration information, the boot image of each application is selected from the boot image storage unit 112 in the same manner as in the case of the OS.

  Note that, similarly to the boot image selection unit 101 of the first embodiment, the boot image selection unit 111 relates to the hardware type indicated in the boot image comparison table, and the hardware configuration information in the image included in the boot image, By comparing the request side hardware configuration information, the startup image with the closest hardware configuration is selected. However, the boot image comparison table is different from the first best mode in that it is prepared for each type of OS and application.

  The startup image creation unit 113 first expands the received OS startup image on the memory, and then expands the startup image of the application on the same memory. When all application memory images are expanded, a boot image is created. One method of expanding the boot image on the memory is a method using Virtual Machine (VM). First, the OS startup image is resumed on the VM, and the OS and application startup image can be expanded on the VM memory by performing resume from the checkpoint of the application on the OS. The startup image creation unit 113 passes the completed startup image to the startup image change unit 104.

  The activation image changing unit 104 and the activation image transmitting unit 103 are the same as those in the first embodiment. That is, using the requesting hardware configuration information and the startup image change table, change the data of a specific part of the startup image, and then change the startup according to the location information of the source node included in the startup image transmission request Send an image.

  The boot node 200 includes a HW information acquisition unit 201, a startup image request unit 202, and a startup processing unit 203, as in the first embodiment. The boot processing unit 203 of the boot node 200 that has received the boot image is expanded on the memory and executed. The network 300 can be any network as long as it can transfer data included in the startup image.

  Next, the overall operation of the present embodiment will be described in detail with reference to FIGS.

  The operations in steps S201 and S202 are the same as those in the first embodiment. That is, when the power of the boot node 200 is turned on, the HW information acquisition unit 201 acquires the hardware configuration information of the boot node 200, and the startup image request unit 202 determines the startup image from the hardware configuration information and the location information of the own node. By creating a transmission request and transmitting it to the boot server, a startup image transmission request is transmitted to the boot server 110.

  On the other hand, the boot image selection unit 111 of the boot server 110 that has received the boot image transmission request boots the OS included in the boot image storage unit 102 based on the software configuration information, the requesting hardware configuration information, and the boot image comparison table. The image and the activation image of the application are searched (step S203).

  When a boot image closest to the requesting hardware configuration information is found for all OSs and applications included in the software configuration information (Y in step S204), those boot images are passed to the boot image creation unit 113 and booted. The image creating unit 113 develops the OS boot image on the memory, further develops the application boot image on the memory, and creates the boot image in which the OS and the application are deployed on one memory (step 205). ).

  The created boot image is transferred to the boot image changing unit 104 together with the requesting hardware configuration information, and the boot image changing unit 104 selects a corresponding entry from the boot image changing table for all the boot images passed. Then, the data of the specific address of the activation image is changed according to the contents of the entry (step S206). As a result of the search in step S203, when two or more boot images suitable for each OS and application are found, an appropriate one is selected at random, or the boot image found first is selected. It's okay.

  Next, the activation image changed in step S206 is transferred to the activation image transmission unit 103, and the activation image transmission unit 103 transmits the received activation image to the boot node indicated by the location information of the transmission source node. (Step S207). The activation processing unit 203 of the boot node 200 that has received the activation image activates the OS of the received activation image (step S208).

  On the other hand, if no activation image is found in step S203 (N in step S204), the activation image selection unit 111 transmits an error code indicating that the activation image selection has failed and a transmission included in the activation image transmission request. The location information of the original node is passed to the activation image transmission unit 103, and the activation image transmission unit 103 transmits the selection error information including the error code to the boot node indicated by the location information of the transmission source node (step). S209). The activation processing unit 203 of the boot node 200 that has received the selection error information fails in the activation process (step S210).

  Next, the effect of this embodiment will be described. In this embodiment, since a boot image is created from an individual boot image of an OS or application each time it is requested, it is necessary to prepare separate boot images that have slightly different OS versions and applications to be booted. There is no. For this reason, in addition to the effect of the modification of 1st and 2nd embodiment, the effect that the number of the starting images which should be preserve | saved can be reduced further can be acquired.

  Next, the first embodiment will be described more specifically using specific examples.

  The configuration of this embodiment will be described with reference to FIGS. In the present embodiment, the PC 810 is used as the boot node, and the server 800 is used as the boot server 100.

  The PC 810 includes a ROM 815 that stores a CPU 811, a chip set 812, a memory 813, a video card 814, and a BIOS 816. The CPU 811 uses “N-CPU 2.6 GHz”, the memory 813 uses “DDR SDRAM 1 GB”, the chip set 812 uses “N-Chipset 900”, and the video card 814 uses “N-Video 505”. Further, the HW information acquisition unit 201, the activation image request unit 202, and the activation processing unit 203 exist as functional units included in a program incorporated in the BIOS 816 of the PC 810.

  The server 800 includes a CPU 801, a memory 802, and an HDD 803. A service program 804 (also called a daemon) for network boot is running on the server 800, and the boot image selection unit 101, the boot image storage unit 102, the boot image transmission unit 103, and the boot image change unit 104 are the programs. Exist as part of the functional means. The service program 804 is loaded from the HDD 803 to the memory 802 and executed by the CPU 801. In addition, the startup image storage unit 102 stores a startup image in the HDD 803.

  The server 800 and the PC 810 are connected by a LAN 900 based on Ethernet (registered trademark), and the server 800 and the PC 810 communicate with each other using the IP protocol. The server 800 and the PC 810 are assigned IP addresses “192.168.1.1” and “192.168.1.9”, respectively. The IP address of the PC 810 is registered on a nonvolatile memory managed by the BIOS 816.

  When the power of the PC 810 is turned on, the BIOS 816 is activated, and the OS activation process is started following the HW initialization process. At the beginning of the OS startup process, the HW information acquisition unit 201 acquires hardware configuration information configuring the PC 810. Next, a startup image transmission request including the hardware configuration information acquired by the startup image request unit 202 and the IP address set in the PC 810 is created. The startup image transmission request 600 created here is shown in FIG. In FIG. 12, an entry 601 indicates the IP address of the PC 810. The IP address is represented as a character string. An entry 602 to an entry 605 indicate hardware configuration information. The hardware configuration information is also expressed as a character string, and up to the colon (:) in each entry represents the type of hardware configuration information. For example, “CPU:” of the entry 602 indicates that the entry 602 includes information on the CPU. Similarly, “MEM:” represents a memory size, “CSET:” represents a chip set, and “VIDEO:” represents information about a video chip.

  The startup image transmission request 600 is sent to the server 800 by the IP protocol. Upon receiving the boot image transmission request 600, the boot image selection unit 101 of the server 800 includes the hardware configuration information included in the boot image transmission request 600, that is, the boot image comparison table illustrated in FIG. 13 among the entries 602 to 605. The startup image included in the startup image storage unit 102 is searched using the type of hardware included in 700 as a search key.

  In this case, the entry 701 of the activation image comparison table 700 relates to the activation image 711 of “/Boot/F-IMG-1.0”, and indicates that the keys used for comparison are “CPU” and “CSET”. ing. Regarding these keys, the hardware configuration information included in the startup image transmission request 600 does not match the hardware configuration information included in the startup image 710. The entry 702 of the activation image comparison table 700 relates to the activation image 712 of “/Boot/N-IMG-2.0-B”, and the keys used for comparison are “CPU”, “CSET”, and “VIDEO”. It is shown that. With respect to these keys, the hardware configuration information included in the startup image transmission request 600 matches the hardware configuration information included in the startup image 712. Similarly, the entry 703 relates to the activation image 713, but does not match the hardware configuration information included in the activation image transmission request 600. As a result of these comparisons, an identifier of the activation image “/Boot/N-IMG-2.0-A” is returned. Here, the identifier represents the path name of the file.

  The activation image selection unit 101 passes the activation image identifier “/Boot/N-IMG-2.0-A” and the activation image transmission request 600 to the activation image change unit 104. The activation image changing unit 104 extracts an entry 722 corresponding to the identifier of the activation image from the activation image change table 720 shown in FIG. The entry 722 includes information that the address is “BASE_HW_INFO: 50”, the size is “50”, and the data type is “MEMSIZE”. The area of 20 bytes includes data “MEMSIZE”.

  The boot image changing unit 104 reads the file specified by the boot image identifier from the HDD 803, and further, based on the information included in the entry 722, from the position of the offset 50 bytes of the file “BASE_HW_INFO”, 20 bytes worth. Change "Area". The value to be changed is obtained from the information “MEMSIZE: 1 GB” included in the entry 603 of the activation image transmission request 600.

  Eventually, a startup image in which the 20-byte area is rewritten from 2 GB to 1 GB from the position of the offset 50 bytes of the file BASE_HW_INFO in the startup image “/Boot/N-IMG-2.0-A” Is sent from the activation image changing unit 104 to the activation image transmitting unit 103. The file passed here is a set of files for activation, and is archived in the TAR format or the ZIP format. The activation image transmission unit 103 transmits an activation image file by IP communication to the node having the IP address “192.168.1.9”, that is, the PC 810.

  Upon receiving the boot image file, the boot image processing unit 203 of the PC 810 performs boot processing. Here, the boot process is development of a boot image file and execution of an OS loader. The OS loader reads the main part of the OS (also called a kernel) into the memory 813 and starts execution of the kernel.

  Next, the second embodiment will be described more specifically using specific examples.

  The configuration of the present embodiment will be described with reference to FIG. In the present embodiment, the PC 810 is used as the boot node, and the server 800 is used as the boot server 100.

  The configuration of the second embodiment is almost the same as that of the first embodiment. The only difference is that the activation image changing unit 104 included in the service program 805 is replaced with the second activation image changing unit. Therefore, the process of the second startup image changing unit will be described in detail.

  When the activation image identifier and activation image transmission request 600 “/Boot/N-IMG-2.0-A” are passed from the activation image selection unit 101 to the activation image change unit 104, the activation image change unit 104 The entry 742 corresponding to the identifier of the startup image is extracted from the startup image change table 740 shown in FIG. The entry 742 includes information whose data type is “FCCacheSize”, but this is not included in the hardware configuration information of the startup image transmission request 600, but is calculated using the startup image change rule 750. It is obtained by.

  The second boot image changing unit reads the file specified by the boot image identifier from the HDD 803, and further, based on the information included in the entry 742, “BASE_HW_INFO from the position of the file offset of 50 bytes, 20 bytes. The “minute area” is changed to a value indicating 1 GB, and in addition to that, based on the information included in the entry 742 and the activation image change rule 750, “the area for 20 bytes from the position of the 200-byte offset of the file BASE_HW_INFO” Is changed to a value indicating 250 MB. The value to be changed is obtained from the information “MEMSIZE: 1 GB” included in the entry 603 of the activation image transmission request 600.

  Finally, the 20-byte area is rewritten from 2 GB to 1 GB from the position of offset 50 bytes of the file BASE_HW_INFO in the startup image “/Boot/N-IMG-2.0-A”, and offset 200 The activation image in which the 20-byte area is rewritten from 500 MB to 250 MB from the byte position is passed from the second activation image changing unit to the activation image transmitting unit 103. The file passed here is a set of files for activation, and is archived in the TAR format or the ZIP format. The activation image transmission unit 103 transmits an activation image file by IP communication to the node having the IP address “192.168.1.9”, that is, the PC 810.

  Upon receiving the boot image file, the boot image processing unit 203 of the PC 810 performs boot processing. Here, the boot process is development of a boot image file and execution of an OS loader. The OS loader reads the main part of the OS (also called “kernel”) into the memory 813 and starts execution of the kernel.

  Next, the third embodiment will be described more specifically using specific examples.

  The configuration of the present embodiment will be described with reference to FIGS. In this embodiment, a PC 810 is used as a boot node, and a server 820 is used as a boot server.

  The PC 810 is the same as that of the first embodiment and includes a CPU 811, a chip set 812, a memory 813, a video card 814, and a ROM 815 that stores a BIOS 816. The CPU 811 uses “N-CPU 2.6 GHz”, the memory 813 uses “DDR SDRAM 1 GB”, the chip set 812 uses “N-Chipset 900”, and the video card 814 uses “N-Video 505”. Further, the HW information acquisition unit 201, the activation image request unit 202, and the activation processing unit 203 exist as functional units included in a program incorporated in the BIOS 816 of the PC 810.

  The server 820 includes a CPU 821, a memory 822, and an HDD 823. On the server 820, a service program 824 (also called a daemon) for network booting is running, and a boot image selection unit 111, a boot image storage unit 112, a boot image creation unit 113, a boot image transmission unit 103, and a boot image. The changing unit 104 exists as a part of functional means of the program. This service program 824 is loaded from the HDD 823 into the memory 802 and executed by the CPU 801. In addition, the startup image storage unit 112 stores a startup image in the HDD 823.

  The server 820 and the PC 810 are connected by a LAN 900 based on Ethernet (registered trademark), and the server 820 and the PC 810 communicate with each other using the IP protocol. The server 820 and the PC 810 are assigned IP addresses “192.168.1.1” and “192.168.1.9”, respectively. The IP address of the PC 810 is registered on a nonvolatile memory managed by the BIOS 816.

  The processing on the boot node side is the same as in the first embodiment. Similarly to the first embodiment, the activation image transmission request has the contents shown in FIG.

  Upon receiving the boot image transmission request 600, the boot image selection unit 111 of the server 820 selects an entry 761 corresponding to the IP address of the boot node included in the boot image transmission request 600 from the software configuration information table as shown in FIG. The entry 761 includes program names “N-OS-2.0-A”, “N-Editor”, “N-Mail”, and “N-Browser”. The boot image selection unit 111 searches the boot image storage unit 112 and selects individual boot image files that partially match these program names.

  First, regarding “N-OS-2.0-A”, two of “N-OS-2.0-A-N505” and “N-OS-2.0-A-S1” match. Here, hardware configuration information “VIDEO: N-Video 505” is embedded in “N-OS-2.0-A-N505”, and “N-OS-2.0-A-S1” is embedded. If the hardware configuration information “VIDEO: S-Video1” is embedded, the individual boot image of “N-OS-2.0-A-505” that matches the entry 605 of the boot image transmission request 600. 701 is selected. Similarly, the individual activation image 773 of “N-Editor”, the individual activation image 774 of “N-Mail”, and the individual activation image 775 of “N-Browser” are selected as applications.

  Next, the boot image creation unit 113 creates one boot image by combining the selected individual boot images. This operation is shown in FIG.

  The boot image creation unit 113 first prepares a VM on which no program is loaded, and develops the individual boot image 771 of “N-OS-2.0-A-505” therein. This deployment is done using the normal hibernation return mechanism.

  Next, the activation image creation unit 113 expands the individual activation image 773 of “N-Editor”. This expansion is performed by using a mechanism for returning from checkpointing realized by Condor or the like. Similar recovery processing is performed on the individual boot image 774 of “N-Mail” and the individual boot image 775 of “N-Browser”, thereby creating a VM memory space for creating a final boot image.

  The boot image creation unit 113 creates a boot image including the OS and the application by performing hibernation of the VM in this state. The operation after the startup image is completed is the same as that in the first embodiment.

  The present invention can be applied to a use as a boot server for a network bootable PC. The present invention can also be applied to a boot server for network booting of server devices in a cluster system.

It is a block diagram showing the structure of the 1st Embodiment of this invention. It is a figure showing the structure of a starting image transmission request. It is a figure which shows an example of hardware configuration information. It is a figure showing the structure of a starting image comparison table. It is a figure showing the structure of a starting image change table. It is a flowchart showing operation | movement of the 1st Embodiment of this invention. It is a figure showing an example of a starting image change rule. It is a block diagram showing the structure of the 3rd Embodiment of this invention. It is a figure showing the structure of a software structure information table. It is a flowchart showing operation | movement of the 3rd Embodiment of this invention. 1 is a block diagram illustrating a configuration of Example 1. FIG. It is a figure showing the starting image transmission request | requirement of Example 1. FIG. FIG. 6 is a diagram illustrating the operation of a startup image selection unit 101 according to the first embodiment. FIG. 6 is a diagram illustrating the operation of a startup image changing unit 104 according to the first embodiment. It is a figure explaining operation | movement of the 2nd starting image change part of Example 2. FIG. FIG. 10 is a block diagram illustrating a configuration of a third embodiment. It is a figure explaining operation | movement of the starting image selection part 111 of Example 3. FIG. FIG. 10 is a diagram illustrating the operation of a startup image creation unit 113 according to the third embodiment.

Explanation of symbols

100, 110 Boot server 101, 111 Boot image selection unit 102, 112 Boot image storage unit 103 Boot image transmission unit 104 Boot image change unit 113 Boot image creation unit 200 Boot node 201 HW information acquisition unit 202 Boot image request unit 203 Boot process 300 network 800 server (boot server)
810 PC (boot node)
811 CPU
812 Chipset 813 Memory 814 Video card 815 ROM
816 BIOS
821 CPU
822 Memory 823 HDD
824 service program

Claims (12)

  1. Including one or more boot server devices and boot node devices connected to each other through a network,
    The boot node device is:
    Hardware configuration information acquisition means for acquiring hardware configuration information of the own node device;
    Boot image request means for sending a boot image transmission request including the hardware configuration information acquired by the hardware configuration information acquisition means to the boot server device;
    A boot processing unit that receives a boot image from the boot server device and performs boot processing of the own node device using the received boot image;
    The boot server device
    Boot image storage means for storing a file group required for booting the computer as the boot image set in advance and hardware configuration information in the image corresponding thereto,
    Included in the startup image transmission request received from the boot node device among the startup images stored in the startup image storage unit based on the startup image comparison table including the type of hardware to be compared for each startup image Of the request side hardware configuration information , the information corresponding to the hardware type indicated in the startup image comparison table and the hardware type in the in-image hardware configuration information corresponding to the startup image A boot image selecting means for selecting the boot image as the boot image having the closest hardware configuration when both of the hardware types indicated in the boot image comparison table match .
    Based on a startup image change table including identification information for indicating a specific data area in the startup image set in advance for each startup image and the type of data to be recorded in the area indicated by the identification information The data matching the type of data corresponding to the selected boot image in the boot image change table is extracted from the requesting hardware configuration information and included in the in-image hardware configuration information corresponding to the selected boot image. A boot image changing means for changing the area indicated by the identification information corresponding to the selected boot image in the boot image change table with the data extracted from the request side hardware configuration information ;
    An activation image providing system comprising: an activation image transmission unit that transmits the activation image in which data included in the hardware configuration information in the image has been changed by the activation image changing unit to the boot node device.
  2. Including one or more boot server devices and boot node devices connected to each other through a network,
    The boot node device is:
    Hardware configuration information acquisition means for acquiring hardware configuration information of the own node device;
    Boot image request means for sending a boot image transmission request including the hardware configuration information acquired by the hardware configuration information acquisition means to the boot server device;
    A boot processing unit that receives a boot image from the boot server device and performs boot processing of the own node device using the received boot image;
    The boot server device
    Boot image storage means for storing a file group required for booting the computer as the boot image set in advance and hardware configuration information in the image corresponding thereto,
    Based on the boot image comparison table including the type of hardware to be compared for each boot image , included in the boot image transmission request received from the boot node device among the boot images stored in the boot image storage means Compares the information corresponding to the hardware type indicated in the boot image comparison table in the request side hardware configuration information with the part corresponding to the hardware type in the hardware configuration information in the image, A boot image selection means for selecting the boot image as the boot image having the closest hardware configuration when both of the hardware types shown in the boot image comparison table match .
    Identification information for indicating a region of specific data in the startup image preset for each startup image among the data included in the hardware configuration information in the image corresponding to the startup image selected by the startup image selection means , And a startup image change table including the type of data to be recorded in the area indicated by the identification information, and changed based on the startup image change rule composed of the data type and the change rule for deriving the data For data designated to be changed, the hardware configuration information in the image corresponding to the selected startup image is changed to a value converted by the startup image change rule, and changed based on the startup image change rule. respect it is not specified data, selection of the boot image change table The data corresponding to the type of data corresponding to the selected boot image is extracted from the requesting hardware configuration information, and the boot image change is included in the data included in the hardware configuration information in the image corresponding to the selected boot image Second activation image changing means for changing an area indicated by the identification information corresponding to the selected activation image in the table with data extracted from the request side hardware configuration information ;
    Boot image providing means, comprising boot image transmitting means for sending the boot image whose data included in the hardware configuration information in the image has been changed by the second boot image changing means to the boot node device. system.
  3. Including one or more boot server devices and boot node devices connected to each other through a network,
    The boot node device is:
    Hardware configuration information acquisition means for acquiring hardware configuration information of the own node device;
    Boot image request means for sending a boot image transmission request including the hardware configuration information acquired by the hardware configuration information acquisition means to the boot server device;
    A boot processing unit that receives a boot image from the boot server device and performs boot processing of the own node device using the received boot image;
    The boot server device
    Second boot image storage means for storing an individual boot image obtained by dividing a file group required for booting the computer for each program as the boot image set in advance and hardware configuration information in the image corresponding thereto. When,
    Based on the software configuration information for each boot node device set in advance, one or more boot image candidates corresponding to the specified program are extracted from the second boot image storage means, and further compared for each boot image. based on the starting image comparison table comprising types should do hardware, the boot image of the requesting hardware configuration information contained from candidates of said one or more boot image boot image transmission request received from the boot node device Hardware corresponding to the type of hardware indicated in the comparison table is compared with the portion corresponding to the type of hardware in the hardware configuration information in the image, and the hardware indicated in the startup image comparison table If both match for all types of A second boot image selection means adware configuration is selected as the boot image for each nearest program,
    Boot image creation means for creating boot images for each program selected by the second boot image selection means together;
    Identification information for indicating data area included in the hardware configuration information in the image corresponding to the activation image created by the activation image creation means, and a specific data area in the preset activation image, and the identification information A startup image change rule comprising a startup image change table including the type of data to be recorded in the area indicated by, a data type set in advance corresponding thereto, and a change rule for deriving the data Based on the above, data corresponding to the type of data corresponding to the selected boot image in the boot image change table is extracted from the boot image change rule or the requesting hardware configuration information, and corresponds to the selected boot image Of the data included in the hardware configuration information in the image to be The area indicated by the identification information corresponding to the selected boot image change table, the third boot image changing means for changing the data retrieved from the boot image change rule or the requesting hardware configuration information,
    Boot image providing means comprising boot image transmitting means for sending the boot image whose data included in the hardware configuration information in the image has been changed by the third boot image changing means to the boot node device system.
  4. A boot server device connected to a boot node device through a network so that they can communicate with each other,
    Boot image storage means for storing a file group required for booting the computer as a preset boot image and hardware configuration information in the image corresponding to the file group;
    Based on the boot image comparison table including the type of hardware to be compared with the boot image identifier based on the boot image comparison table including the type of hardware to be compared for each boot image, the boot image storage means Among the stored startup images, information corresponding to the type of hardware indicated in the startup image comparison table among the request side hardware configuration information included in the startup image transmission request received from the boot node device ; The hardware configuration information in the image is compared with the corresponding part of the hardware type, and when both of the hardware types shown in the startup image comparison table match, the startup image is selected. start-up hardware configuration is selected as the closest start-up image Ime And di-selection means,
    Based on a startup image change table including identification information for indicating a specific data area in the startup image set in advance for each startup image and the type of data to be recorded in the area indicated by the identification information The data matching the type of data corresponding to the selected boot image in the boot image change table is extracted from the requesting hardware configuration information and included in the in-image hardware configuration information corresponding to the selected boot image. A boot image changing means for changing the area indicated by the identification information corresponding to the selected boot image in the boot image change table with the data extracted from the request side hardware configuration information ;
    A boot server device comprising: a boot image transmission unit configured to transmit the boot image whose data included in the hardware configuration information in the image has been changed by the boot image changing unit to the boot node device.
  5. A boot server device connected to a boot node device through a network so that they can communicate with each other,
    Boot image storage means for storing a file group required for booting the computer as a preset boot image and hardware configuration information in the image corresponding to the file group;
    Included in the startup image transmission request received from the boot node device among the startup images stored in the startup image storage unit based on the startup image comparison table including the type of hardware to be compared for each startup image Compares the information corresponding to the hardware type indicated in the boot image comparison table in the request side hardware configuration information with the part corresponding to the hardware type in the hardware configuration information in the image, A boot image selection means for selecting the boot image as the boot image having the closest hardware configuration when both of the hardware types shown in the boot image comparison table match .
    Identification information for indicating a region of specific data in the startup image preset for each startup image among the data included in the hardware configuration information in the image corresponding to the startup image selected by the startup image selection means , And a startup image change table including the type of data to be recorded in the area indicated by the identification information, and changed based on the startup image change rule composed of the data type and the change rule for deriving the data For data designated to be changed, the hardware configuration information in the image corresponding to the selected startup image is changed to a value converted by the startup image change rule, and changed based on the startup image change rule. respect it is not specified data, selection of the boot image change table The data corresponding to the type of data corresponding to the selected boot image is extracted from the requesting hardware configuration information, and the boot image change is included in the data included in the hardware configuration information in the image corresponding to the selected boot image Second activation image changing means for changing an area indicated by the identification information corresponding to the selected activation image in the table with data extracted from the request side hardware configuration information ;
    A boot server device comprising: a boot image transmission unit configured to transmit the boot image whose data included in the hardware configuration information in the image has been changed by the second boot image change unit to the boot node device; .
  6. A boot server device connected to a boot node device through a network so that they can communicate with each other,
    Second boot image storage means for storing an individual boot image obtained by dividing a file group required for booting the computer for each program as a preset boot image and hardware configuration information in the image corresponding thereto; ,
    Based on the software configuration information for each boot node device set in advance, one or more boot image candidates corresponding to the specified program are extracted from the second boot image storage means, and further compared for each boot image. Based on the boot image comparison table including the type of hardware to be performed, the boot image comparison among the request side hardware configuration information included in the boot image transmission request received from the boot node device from the one or more boot image candidates The information corresponding to the hardware type indicated in the table is compared with the part corresponding to the hardware type in the hardware configuration information in the image, and the hardware indicated in the boot image comparison table is compared. If both match for all types, the boot image is A second boot image selection means hardware configuration is selected as the boot image for each nearest program,
    Boot image creation means for creating boot images for each program selected by the second boot image selection means together;
    The data included in the hardware configuration information in the image corresponding to the boot image created by the boot image creating means is the identification information for indicating the area of specific data in the preset boot image, and the identification information. A startup image change rule including a startup image change table including the type of data to be recorded in the indicated area, a type of data set in advance corresponding thereto, and a change rule for deriving the data ; The data corresponding to the type of data corresponding to the selected boot image in the boot image change table is extracted from the boot image change rule or the requesting hardware configuration information and corresponds to the selected boot image. Among the data included in the hardware configuration information in the image, the boot image change The area indicated by the identification information corresponding to the selected boot image of Buru, the third boot image changing means for changing the data retrieved from the boot image change rule or the requesting hardware configuration information,
    A boot server device comprising: a boot image device for sending the boot image whose data included in the hardware configuration information in the image has been changed by the third boot image changing unit to the boot node device; .
  7. An operating method of a startup image providing system including one or more boot server devices and a boot node device connected to each other through a network,
    The boot server device stores a file group required for starting the computer as a preset startup image and hardware configuration information in the image corresponding thereto,
    The boot node device acquires hardware configuration information of the node device;
    The boot node device transmitting a startup image transmission request including the hardware configuration information acquired by the hardware configuration information acquisition means to the boot server device;
    The boot server device receives the boot received from the boot node device out of the boot images stored in the boot image storage unit based on the boot image comparison table including the type of hardware to be compared for each boot image. Of the hardware configuration information on the request side included in the image transmission request, information corresponding to the hardware type indicated in the boot image comparison table corresponds to the hardware type in the intra-image hardware configuration information. Comparing the parts, and when both match for all of the hardware types shown in the boot image comparison table, selecting the boot image as the boot image with the closest hardware configuration ;
    The boot server device includes identification information for indicating an area of specific data in a startup image set in advance for each startup image and a type of data to be recorded in the area indicated by the identification information Based on the image change table, data matching the type of data corresponding to the selected boot image in the boot image change table is extracted from the requesting hardware configuration information, and the data corresponding to the selected boot image is stored. Of the data included in the hardware configuration information, changing the area indicated by the identification information corresponding to the selected startup image of the startup image change table with the data extracted from the requesting hardware configuration information ;
    The boot server device transmitting the boot image in which data included in the image hardware configuration information is changed to the boot node device;
    The boot node device includes a step of receiving the boot image from the boot server device and performing boot processing of the own node device using the received boot image.
  8. An operating method of a startup image providing system including one or more boot server devices and a boot node device connected to each other through a network,
    The boot server device stores a file group required for computer startup as the preset startup image and hardware configuration information in the image corresponding thereto,
    The boot node device acquires hardware configuration information of the node device;
    The boot node device transmitting a startup image transmission request including the acquired hardware configuration information to the boot server device;
    The boot server device includes the startup image transmission request received from the boot node device among the stored startup images based on the startup image comparison table including the type of hardware to be compared for each startup image. Compares the information corresponding to the hardware type indicated in the boot image comparison table in the request side hardware configuration information with the part corresponding to the hardware type in the hardware configuration information in the image, When both match for all of the hardware types shown in the boot image comparison table, selecting the boot image as the boot image with the closest hardware configuration ;
    Identification information for indicating an area of specific data in the startup image preset for each startup image among the data included in the hardware configuration information in the image corresponding to the selected startup image by the boot server device , And a startup image change table including the type of data to be recorded in the area indicated by the identification information, and changed based on the startup image change rule composed of the data type and the change rule for deriving the data For data designated to be changed, the hardware configuration information in the image corresponding to the selected startup image is changed to a value converted by the startup image change rule, and changed based on the startup image change rule. respect it is not specified data, selection of the boot image change table The data corresponding to the type of data corresponding to the selected boot image is extracted from the requesting hardware configuration information, and the boot image change is included in the data included in the hardware configuration information in the image corresponding to the selected boot image Changing the area indicated by the identification information corresponding to the selected startup image in the table with data extracted from the requesting hardware configuration information ;
    The boot server device transmitting the boot image in which data included in the image hardware configuration information is changed to the boot node device;
    The boot node device includes a step of receiving the boot image from the boot server device and performing boot processing of the own node device using the received boot image.
  9. An operating method of a startup image providing system including one or more boot server devices and a boot node device connected to each other through a network,
    The boot server device storing an individual boot image obtained by dividing a file group required for booting the computer as a preset boot image for each program and hardware configuration information in the image corresponding thereto; ,
    The boot node device acquires hardware configuration information of the node device;
    The boot node device transmitting a startup image transmission request including the acquired hardware configuration information to the boot server device;
    The boot server device extracts one or more boot image candidates corresponding to a program designated from the second boot image storage unit based on software configuration information for each boot node device set in advance, and A request-side hardware configuration included in a startup image transmission request received from the boot node device from the one or more startup image candidates based on a startup image comparison table including hardware types to be compared for each startup image The information corresponding to the hardware type indicated in the boot image comparison table in the information is compared with the part corresponding to the hardware type in the hardware configuration information in the image, and the boot image comparison table If they match for all of the hardware types shown in , Selecting the boot image as boot image for each nearest program the hardware configuration,
    The boot server device creating a single boot image by combining the boot images for each program selected by the second boot image selection means;
    Identification information for the boot server device to indicate the data included in the hardware configuration information in the image corresponding to the created startup image, the area of specific data in the preset startup image, and the identification information A startup image change rule comprising a startup image change table including the type of data to be recorded in the area indicated by, a data type set in advance corresponding thereto, and a change rule for deriving the data Based on the above, data corresponding to the type of data corresponding to the selected boot image in the boot image change table is extracted from the boot image change rule or the requesting hardware configuration information, and corresponds to the selected boot image Among the data included in the hardware configuration information in the image to be The area indicated by the identification information corresponding to the selected table of boot image, and changing the data retrieved from the boot image change rule or the requesting hardware configuration information,
    The boot server device transmitting the boot image in which data included in the image hardware configuration information is changed to the boot node device;
    The boot node device includes a step of receiving a boot image from the boot server device and performing boot processing of the own node device using the received boot image.
  10. An operation program for a boot server device connected to a boot node device through a network so that they can communicate with each other,
    On the computer,
    Storing a file group required for starting the computer as a preset startup image and hardware configuration information in the image corresponding to the file group;
    Based on the boot image comparison table including the type of hardware to be compared for each boot image, out of the saved boot images, request side hardware configuration information included in the boot image transmission request received from the boot node device Information corresponding to the hardware type indicated in the boot image comparison table is compared with a portion corresponding to the hardware type in the hardware configuration information in the image, and is stored in the boot image comparison table. Selecting the boot image as the boot image with the closest hardware configuration if both match for all of the indicated hardware types ;
    Based on a startup image change table including identification information for indicating a specific data area in the startup image set in advance for each startup image and the type of data to be recorded in the area indicated by the identification information The data matching the type of data corresponding to the selected boot image in the boot image change table is extracted from the requesting hardware configuration information and included in the in-image hardware configuration information corresponding to the selected boot image. Of the data, changing the area indicated by the identification information corresponding to the selected boot image of the boot image change table with the data extracted from the request side hardware configuration information ;
    And a step of transmitting the boot image in which the data included in the hardware configuration information in the image has been changed to the boot node device.
  11. An operation program for a boot server device connected to a boot node device through a network so that they can communicate with each other,
    On the computer,
    Storing a file group required for starting the computer as a preset startup image and hardware configuration information in the image corresponding to the file group;
    Based on the boot image comparison table including the type of hardware to be compared for each boot image, out of the saved boot images, request side hardware configuration information included in the boot image transmission request received from the boot node device Information corresponding to the hardware type indicated in the boot image comparison table is compared with a portion corresponding to the hardware type in the hardware configuration information in the image, and is stored in the boot image comparison table. Selecting the boot image as the boot image with the closest hardware configuration if both match for all of the indicated hardware types ;
    Among the data included in the hardware configuration information in the image corresponding to the selected boot image, identification information for indicating a specific data area in the boot image preset for each boot image, and the identification information The activation image change table including the type of data to be recorded in the indicated area is specified to be changed based on the activation image change rule composed of the data type and the change rule for deriving the data. As for the existing data, it is not specified that the hardware configuration information in the image corresponding to the selected boot image is changed to a value converted by the boot image change rule, while changing based on the boot image change rule is not specified. for data is corresponding to the selected boot image of the boot image change table Data corresponding to the type of data to be selected is extracted from the request-side hardware configuration information, and the selected activation in the activation image change table among the data included in the hardware configuration information in the image corresponding to the selected activation image Changing an area indicated by identification information corresponding to an image with data extracted from the requesting hardware configuration information ;
    And a step of transmitting the boot image in which the data included in the hardware configuration information in the image has been changed to the boot node device.
  12. An operation program for a boot server device connected to a boot node device through a network so that they can communicate with each other,
    On the computer,
    A step of storing an individual boot image obtained by dividing a file group required for booting the computer as a preset boot image for each program and hardware configuration information in the image corresponding thereto;
    Based on the software configuration information for each boot node device set in advance, one or more boot image candidates corresponding to the specified program are extracted from the second boot image storage means, and further compared for each boot image. Based on the boot image comparison table including the type of hardware to be performed, the boot image comparison among the request side hardware configuration information included in the boot image transmission request received from the boot node device from the one or more boot image candidates The information corresponding to the hardware type indicated in the table is compared with the part corresponding to the hardware type in the hardware configuration information in the image, and the hardware indicated in the boot image comparison table is compared. If both match for all types, the boot image is A step of hardware configuration is selected as the boot image for each nearest program,
    Creating a single startup image by combining the startup images for each selected program;
    The data included in the hardware configuration information in the image corresponding to the created startup image is stored in the identification information for indicating the area of specific data in the preset startup image, and the area indicated by the identification information Based on the startup image change table including the type of data to be recorded, and the startup image change rule composed of the change type for deriving the data and the type of data set in advance corresponding thereto , Data that matches the type of data corresponding to the selected boot image in the boot image change table is extracted from the boot image change rule or the requesting hardware configuration information, and the hardware configuration in the image corresponding to the selected boot image Of the data included in the information, the selected startup image in the startup image change table is selected. The area indicated by the identification information corresponding to the image, and changing the data retrieved from the boot image change rule or the requesting hardware configuration information,
    And a step of transmitting the boot image in which the data included in the hardware configuration information in the image has been changed to the boot node device.
JP2005094858A 2005-03-29 2005-03-29 Boot image providing system and operation method thereof, boot node device, boot server device, and operation program thereof Active JP4863154B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2005094858A JP4863154B2 (en) 2005-03-29 2005-03-29 Boot image providing system and operation method thereof, boot node device, boot server device, and operation program thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2005094858A JP4863154B2 (en) 2005-03-29 2005-03-29 Boot image providing system and operation method thereof, boot node device, boot server device, and operation program thereof

Publications (2)

Publication Number Publication Date
JP2006277277A JP2006277277A (en) 2006-10-12
JP4863154B2 true JP4863154B2 (en) 2012-01-25

Family

ID=37211985

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2005094858A Active JP4863154B2 (en) 2005-03-29 2005-03-29 Boot image providing system and operation method thereof, boot node device, boot server device, and operation program thereof

Country Status (1)

Country Link
JP (1) JP4863154B2 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009020748A (en) * 2007-07-12 2009-01-29 Hitachi Ltd Equipment management apparatus, equipment management method and equipment management program
US9262366B2 (en) * 2007-09-21 2016-02-16 Microsoft Technology Licensing, Llc Software deployment in large-scale networked systems
JP2009157802A (en) * 2007-12-27 2009-07-16 Kyocera Corp Portable terminal and information processor
JP2009223778A (en) * 2008-03-18 2009-10-01 Hitachi Software Eng Co Ltd Program distribution device by virtual machine image
JP2009301504A (en) * 2008-06-17 2009-12-24 Sharp Corp Computer, recording medium, and information processing method
JP2010152704A (en) * 2008-12-25 2010-07-08 Hitachi Ltd System and method for operational management of computer system
EP2416244A4 (en) 2009-03-30 2012-08-29 Fujitsu Ltd Control server, boot server, network boot system, network boot method, boot image selection program, and boot image provision program
JP5146495B2 (en) * 2010-07-08 2013-02-20 コニカミノルタビジネステクノロジーズ株式会社 Image processing apparatus and hibernation activation method
US8688812B2 (en) * 2010-09-23 2014-04-01 Intel Corporation Cluster computing—NIC based OS provision

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6080207A (en) * 1998-06-04 2000-06-27 Gateway 2000, Inc. System and method of creating and delivering software
JP3714119B2 (en) * 2000-06-13 2005-11-09 日本電気株式会社 User authentication type network OS boot method and system using BIOS preboot environment
JP3997735B2 (en) * 2000-08-01 2007-10-24 富士通株式会社 Processing system and processing apparatus
US7379982B2 (en) * 2002-04-15 2008-05-27 Bassam Tabbara System and method for custom installation of an operating system on a remote client
AU2002367880A1 (en) * 2002-04-18 2003-11-03 Venturcom, Inc. System for and method of network booting of an operating system to a client computer using hibernation

Also Published As

Publication number Publication date
JP2006277277A (en) 2006-10-12

Similar Documents

Publication Publication Date Title
TWI547875B (en) Converting machines to virtual machines
US8195624B2 (en) Shared file system management between independent operating systems
US5325532A (en) Automatic development of operating system boot image
JP4411076B2 (en) Localized read-only storage for distributing files across a network
US9239814B2 (en) System and method for creating or reconfiguring a virtual server image for cloud deployment
US7797507B2 (en) Virtual machine system and operating method thereof
US6810478B1 (en) System for remote booting of muntliple operating systems using chained bootstrap mechanism in a network
JP5403771B2 (en) System and method for providing secure updates to firmware
US7334227B2 (en) Device driver installing method
US8209680B1 (en) System and method for disk imaging on diverse computers
EP0797800B1 (en) System for providing bios to host computer
KR20100068392A (en) Software deployment in large-scale networked systems
JP5680961B2 (en) Integrated provision of physical and virtual images
US6725178B2 (en) Use of hidden partitions in a storage device for storing BIOS extension files
US7191327B2 (en) Internet-enabled device provisioning, upgrade and recovery mechanism
EP1922617B1 (en) Preboot memory of a computer system
US7941470B2 (en) Synchronization and customization of a clone computer
US6373498B1 (en) Displaying images during boot-up and shutdown
JP2011118873A (en) Automated modular and secure boot firmware update
JP2012118827A (en) Information processing system, information processing apparatus, preparation method, program and recording medium
JP5146174B2 (en) Virtual machine monitor device and program, and virtual machine memory sharing management method
US7702894B2 (en) System and method for loading programs from HDD independent of operating system
US7664836B2 (en) Device and method for booting an operation system for a computer from a passive directly attached network device
US8417796B2 (en) System and method for transferring a computing environment between computers of dissimilar configurations
US7631173B2 (en) Method and system for performing pre-boot operations from an external memory including memory address and geometry

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20070710

RD04 Notification of resignation of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7424

Effective date: 20080516

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20100427

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20100726

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20100924

RD03 Notification of appointment of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7423

Effective date: 20101001

RD04 Notification of resignation of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7424

Effective date: 20101001

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20110509

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20110708

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20111017

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

R150 Certificate of patent or registration of utility model

Ref document number: 4863154

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150

Free format text: JAPANESE INTERMEDIATE CODE: R150

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20141118

Year of fee payment: 3

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20111030