JP6001474B2 - Boot image delivery method and boot image delivery system - Google Patents

Description

  The present invention relates to a technique for distributing the same boot image to each server constituting a cluster system.

  In scale-out large-scale distributed processing, clustering is performed across multiple sites. At that time, a boot image including a common OS (Operating System), middleware, application programs, and the like is required for each server constituting the cluster. From the viewpoint of effectively utilizing the bandwidth of the inter-base network, the boot image common to the servers is distributed to the management server at each base, and each server acquires the boot image from the management server at each base when starting up. Should. Therefore, the maintenance person needs to distribute the boot image in advance to all bases where the servers constituting the cluster are installed.

  As a conventional technique related to boot image distribution, Patent Document 1 discloses a technique for dividing a file into chunks of a predetermined size and distributing them in a pipeline manner between servers when distributing the boot image to a large number of servers. Has been.

JP 2012-238095 A

  However, when it is assumed that the above-described conventional technology is applied to boot image distribution to management servers installed at a plurality of bases, all the bases are connected in series. As a result, there is a problem in that only the bandwidth of a specific link between routers that perform routing between bases is occupied, and links between other routers cannot be effectively used.

  The present invention has been made to solve the above-described problem, and efficiently uses a link connecting bases to reduce the distribution time when distributing the same boot image to a plurality of distribution destination servers. The purpose is to shorten.

In order to achieve the above object, the present invention provides a boot image distribution method for distributing the same boot image file to a plurality of distribution destination servers, wherein the distribution source server receives the boot image file distribution request. Dividing the boot image file into a plurality of parts; dividing each of the plurality of parts into chunks of a predetermined size; and sending one of the divided chunks from the distribution source server. Each of the distribution destination servers includes a first distribution step in which distribution in units of chunks as redistribution parts to at least one of the distribution destination servers is performed in parallel to all distribution destination servers. The redistributed parts delivered to itself are transferred to the other delivery destination server predetermined for each delivery destination server. A second distribution step of receiving in parallel in units of chunks from other distribution destination servers predetermined for each distribution destination server, and the remaining parts other than the redistribution parts distributed to itself, A restoration step in which each of the delivery destination servers combines the redistribution part received in the first delivery step and the remaining part received in the second delivery step to restore the boot image file; The allocation method related to the acquisition destination of the remaining parts includes , when the number of distribution destination servers is a multiple of the number of divisions of the parts, grouping the distribution destination servers for each of the division units, The other delivery destination servers in the group are used as the acquisition destinations of the remaining parts, or the number of delivery destination servers is twice the number of divisions of the parts. If the other distribution destination server that is not the distribution destination of the boot image file is added to the distribution destination of the redistribution part, the number of the distribution destination servers becomes a multiple of the division number. adding the other distribution destination server to assist the delivery of the distribution part to the delivery destination of the redistribution part, that in the grouping and acquisition destination of the remaining part, comprises a front Stories second delivery The parallel transmission and parallel reception of the chunk in the step are executed in parallel with the parallel distribution of the next chunk of the chunk in the first distribution step.

By doing so, the divided parts are distributed in parallel between the distribution destination servers, so that the distribution time of the boot image file can be shortened. In addition, since redistribution parts are distributed in parallel, including distribution destination servers that are not subject to distribution, it is possible to increase the parallelism of redistribution parts and further shorten the boot image file distribution time. Increases nature.

In the boot image distribution method according to the present invention, the number of divisions when dividing into the plurality of parts in the division step is the number of the distribution destination servers to which the same boot image file should be distributed. It is determined with reference to a predetermined table that is referred to in order to determine the number of divisions using the number of links per distribution destination server that can be set between the distribution destination servers as a parameter.

  By doing so, it is possible to automatically determine the optimum division number corresponding to the number of distribution destination servers to which the same boot image file should be distributed and the number of links that can be set between the distribution destination servers.

The present invention is also a boot image distribution system in which a distribution source server distributes the same boot image file to a plurality of distribution destination servers, and the distribution source server receives a boot image file distribution request. a receiving unit, and parts dividing portion that divides the boot image file into a plurality of parts, each of said plurality of parts, is divided into chunks of predetermined size, one of the parts consisting of the divided chunks, the A redistribution part distribution unit that performs distribution in units of chunks as a redistribution part from at least one of the distribution source servers to the distribution destination server, in parallel to all distribution destination servers , Each of the distribution destination servers receives a redistribution part that receives the redistribution parts distributed to itself in units of chunks. A receiving unit, a redistributed part transmitting unit that transmits the received redistributed parts in parallel to the other distribution destination server predetermined for each distribution destination server in units of chunks, and the redistribution distributed to itself The remaining parts other than the parts are received in parallel from the other delivery destination servers predetermined for each delivery destination server in units of chunks, and the redistribution parts received by the redistribution parts receiving unit A boot image restoration unit that combines the remaining parts received by the remaining part acquisition unit and restores the boot image file, and the redistribution part distribution unit allocates the acquisition source of the remaining parts As a technique, when the number of the delivery destination servers is a multiple of the number of divisions of the parts, the delivery destination servers are grouped for each of the several divisions. The other delivery destination servers are the acquisition destinations of the remaining parts, or when the number of delivery destination servers is not a multiple of the division number of the parts, the boot image file is not the delivery destination. When another distribution destination server is added to the distribution destination of the redistribution part, and the number of distribution destination servers is a multiple of the division number, the other distribution destination server that assists the distribution of the redistribution part is the addition to the delivery destination of the redistribution parts, that by the grouping and acquisition destination of the remaining part, run comprise, parallel transmission and the remaining part acquisition unit of the chunks before Symbol redistributing part transmission unit The parallel reception of the chunk and the reception of the next chunk of the chunk in the redistribution part reception unit are executed in parallel.

By doing so, the divided parts are distributed in parallel between the distribution destination servers, so that the distribution time of the boot image file can be shortened. In addition, since redistribution parts are distributed in parallel, including distribution destination servers that are not subject to distribution, it is possible to increase the parallelism of redistribution parts and further shorten the boot image file distribution time. Increases nature.

In the boot image distribution system according to the present invention, the distribution source server may be configured such that the parts dividing unit distributes the number of the distribution destination servers to which the same boot image file is to be distributed, and the distribution destination servers. And a predetermined table referred to for determining the number of divisions when dividing into the plurality of parts, using the number of links per distribution destination server that can be set as a parameter.

  By doing so, it is possible to automatically determine the optimum division number corresponding to the number of distribution destination servers to which the same boot image file should be distributed and the number of links that can be set between the distribution destination servers.

  ADVANTAGE OF THE INVENTION According to this invention, the delivery time when delivering the same boot image file to a several delivery destination server can be shortened.

It is a figure which shows the structural example of a boot image delivery system. It is a functional block diagram which shows the structural example of a delivery origin server. It is a functional block diagram which shows the structural example of a delivery destination server. It is a figure which shows the structure and data example of boot image information on a delivery origin server. It is a figure which shows the structure and data example of parts information on a delivery origin server. It is a figure which shows the structure and data example of the delivery destination server information on a delivery origin server. It is a figure which shows the structure and data example of boot image information on a delivery destination server. It is a figure which shows the structure and data example of parts information on a delivery destination server. It is a figure which shows the structure and data example of the acquisition destination server information on a delivery destination server. It is a flowchart which shows the example of the boot image delivery process which a delivery origin server performs. It is a flowchart which shows the example of the boot image transmission / reception process which a delivery destination server performs. It is a sequence chart which shows the operation example in the case of delivering the boot image file divided | segmented into 2 parts to four delivery destination servers. It is a sequence chart which shows the operation example in the case of delivering the boot image file divided | segmented into 4 parts to four delivery destination servers. It is a sequence chart which shows the operation example in the case of dividing | segmenting five delivery destination servers into two groups of three and two, and delivering a boot image file. It is a sequence chart which shows the operation example in the case of delivering the boot image file divided | segmented into 3 parts to six delivery destination servers. It is the figure which showed as a list the relationship between the optimal division | segmentation number D corresponding to the number M of delivery destination bases, and the number L of links between bases, and a delivery time ratio. It is a figure which shows the structure and example of data of a division number determination table.

  Hereinafter, a mode for carrying out the present invention (hereinafter referred to as “the present embodiment”) will be described in detail with reference to the drawings as appropriate.

  FIG. 1 is a diagram illustrating a configuration example of a boot image distribution system according to the present embodiment. As shown in FIG. 1, a boot image distribution system 100 includes a distribution source server 1 that is a distribution source of a boot image and a plurality of distribution destination servers 2 that are installed at each of N locations. The network 4 is connected and configured. The distribution source server 1 is connected to a maintenance terminal 3 for generating a boot image to be distributed and registering it in the distribution source server 1 or designating a distribution destination. Although not shown, a server group that provides a predetermined service to the user terminal is installed at each base, and a boot image necessary for the server group is distributed from the distribution destination server 2 at each base. By doing so, the operation as a cluster server system is controlled.

  FIG. 2 is a functional block diagram illustrating a configuration example of the distribution source server. As illustrated in FIG. 2, the distribution source server 1 includes a boot image reception unit 11, a parts division unit 12, a redistribution part allocation unit 13, a redistribution part distribution unit 14, and a storage unit 15. The storage unit 15 stores boot image information 151, a plurality of boot image files 152, part information 153, distribution destination server information 154, a division number determination table 155, and the like.

  The distribution source server 1 is configured by a computer, for example, and a CPU (Central Processing Unit) (not shown) executes a predetermined boot image distribution program stored in the storage unit 15, so that each of these functional units is realized. The

  The boot image receiving unit 11 receives a boot image distribution request from the maintenance terminal 3. At this time, the maintenance terminal 3 specifies the boot image main body, information such as the image ID (Identification) that is identification information of the boot image and the applicable model, and the distribution destination base or distribution destination server of the boot image. Information shall be transmitted.

  The boot image reception unit 11 stores the main body of the boot image received from the maintenance terminal 3 in the storage unit 15 as the boot image file 152, and information on the boot image received simultaneously from the maintenance terminal 3 and the storage location of the boot image file 152 Are stored in the storage unit 15 as boot image information 151 (see FIG. 4).

  The parts dividing unit 12 determines the number of divisions for dividing the boot image file 152 to be distributed into a plurality of parts, and divides the boot image file 152 into a plurality of parts. The method of dividing into a plurality of parts is arbitrary, but it is preferable that the size of each part is as biased as possible. For this purpose, the size of the part may be obtained by dividing the size of the boot image file 152 by the number of divisions, and the obtained size may be divided into parts in order from the top. Alternatively, the division position into parts is defined as a boundary between chunks to be described later, and the number of chunks constituting each part is obtained by including the chunk and the data of the fraction in the last part, and using the obtained number of chunks You may make it divide | segment into each part. The parts dividing unit 12 associates the information on each divided part with the transmission data address indicating the storage position of the data of the part, and causes the storage unit 26 to store the information as part information 153 (see FIG. 5). The number of divisions into a plurality of parts is the division number determination table 155 that defines the optimum division number D using the number of distribution destination sites M (2 ≦ M ≦ N) and the number of links L that can be set between the sites as parameters (see FIG. 17 and a predetermined table referred to in order to determine the number of divisions of the present invention.

  The redistribution part allocation unit 13 allocates at least one distribution destination server 2 that distributes each divided part to another distribution destination server 2 as a redistribution part. As an allocation method, M distribution destination servers 2 may be ordered in accordance with an arbitrary standard, and for example, permutations of D redistribution parts that are different from the top may be allocated repeatedly.

  The redistribution part distribution unit 14 divides the redistribution parts assigned to each distribution destination server 2 into chunks of a predetermined size (for example, 64 Kbytes), and performs parallel distribution to all distribution destination servers 2. At this time, the redistribution part distribution unit 14 notifies each distribution destination server 2 together with the image ID, file size, and applicable model of the boot image registered in the boot image information 151 (see FIG. 4). . Furthermore, the distribution destination server 2 may be notified of the acquisition destination of the remaining parts that are the remaining parts other than the redistribution parts.

  The method of assigning the acquisition destination of the remaining parts is arbitrary. For example, each distribution destination server 2 is higher than the M distribution destination servers 2 ordered according to a predetermined standard, and has the highest rank. What is necessary is just to use the near server as the acquisition destination of each remaining part. Alternatively, when the number M of distribution destination bases is a multiple of the division number D, the M servers are grouped by D units, and the other distribution destination servers 2 in the group are acquired from the remaining parts. It is good.

  Further, when the number of distribution destination bases M is not a multiple of the division number D, the distribution destination server number is divided by adding another distribution destination server 2 that is not the distribution destination of the boot image to the distribution destination of the redistribution part. When it is a multiple of D, another distribution destination server 2 that assists the distribution of the redistribution parts may be added to the distribution destination of the redistribution parts. Thereby, the degree of parallelism when all the redistributed parts are redistributed between the distribution destination servers 2 can be maximized.

  FIG. 3 is a functional block diagram illustrating a configuration example of the distribution destination server. As shown in FIG. 3, the distribution destination server 2 includes a redistribution part reception unit 21, a redistribution part transmission unit 22, a remaining part acquisition unit 23, a boot image restoration unit 24, a boot image distribution unit 25, and a storage unit 26. I have. The storage unit 26 stores boot image information 261, a plurality of boot image files 262, parts information 263, acquisition server information 264, a plurality of parts 265, and the like.

  The distribution destination server 2 is configured by, for example, a computer, and a CPU (not shown) executes a predetermined boot image transmission / reception program stored in the storage unit 26, thereby realizing these functional units.

  The redistribution part receiving unit 21 sequentially stores the redistribution part data received from the distribution source server 1 in units of chunks as a part 265 in the storage unit 26, and receives information indicating the storage position of the information and data regarding the redistribution part. The data address is associated and stored in the storage unit 26 as part information 263.

  In addition, when the redistribution part receiving unit 21 receives information specifying another distribution destination server 2 from which the remaining parts should be acquired from the distribution source server 1, the redistribution part receiving unit 21 sets the information specifying the distribution destination server 2 as part information. It registers with the acquisition destination server ID of H.263 (see FIG. 8). On the other hand, when such information is not received from the distribution source server 1, the redistribution parts receiving unit 21 determines a distribution destination server 2 as an acquisition destination according to a predetermined rule, and the information of the distribution destination server 2 is used as part information. It registers with the acquisition destination server ID of H.263.

  The redistribution part transmission unit 22 reads the received redistribution part data from the part 265 and transmits it to the distribution destination server 2 in units of chunks in response to a redistribution part acquisition request from another distribution destination server 2. To do. When receiving a request for acquiring redistributed parts simultaneously from a plurality of distribution destination servers 2, all of the transmissions are executed in parallel.

  The remaining parts acquisition unit 23 determines the remaining parts, which are the remaining parts that have not been distributed from the distribution source server 1, to other distribution destinations identified by the acquisition destination server ID (see FIG. 8) of the part information 263. Obtain from the server 2. Specifically, a redistribution part acquisition request is transmitted to the other distribution destination server 2, and redistribution part data transmitted as a response is received in chunks, and sequentially stored as a part 265. 26, the information on the redistributed part and the received data address indicating the data storage position are associated with each other and stored in the storage unit 26 as the part information 263. Acquisition of these remaining parts is executed in parallel for each part.

  After all the data of the parts 265 are prepared, the boot image restoration unit 24 combines the parts 265 to restore the original boot image file and stores it in the storage unit 26 as the boot image file 262. Further, the information related to the boot image and the file path indicating the storage location of the boot image file 262 are associated with each other and stored in the storage unit 26 as boot image information 261 (see FIG. 7).

  The boot image distribution unit 25 receives a boot image distribution request from a subordinate server group that provides a predetermined service to the user terminal, and receives boot image data corresponding to each of these server groups from the boot image file 262. Read and send to the server.

  FIG. 4 is a diagram illustrating a configuration and data example of boot image information on the distribution source server 1. As shown in FIG. 4, in the boot image information 151 on the distribution source server 1, a record including an image ID, a file path, a file size, and an applicable model is registered for each boot image.

  The image ID is identification information given to uniquely identify each boot image. The file path is information indicating a position where the corresponding boot image file 152 is registered. The file size is the file size of the corresponding boot image file 152. The applied model is information indicating the model of the server to which the corresponding boot image file 152 is distributed.

  FIG. 5 is a diagram illustrating a configuration of part information on the distribution source server 1 and a data example. As shown in FIG. 5, in the part information 153 on the distribution source server 1, a record including a part number, a transmission data address, and a data size is registered for each part.

  The part number is a serial number assigned to uniquely identify each part. The transmission data address is position information of the head data of the corresponding part. The data size is the data size of the corresponding part.

  FIG. 6 is a diagram illustrating a configuration of the distribution destination server information on the distribution source server 1 and a data example. As shown in FIG. 6, in the distribution destination server information 154 on the distribution source server 1, a record including a server ID, an IP address, a redistribution part number, a number of chunks, and a transmission chunk number is stored for each distribution destination server. Registered in

  The server ID is identification information given to uniquely identify each distribution destination server 2. The IP (Internet Protocol) address is address information used for transmitting data to the corresponding distribution destination server 2. The redistribution part number is an identification number of a redistribution part assigned to the corresponding distribution destination server. The number of chunks is the number of chunks constituting the data of the redistributed part. The transmission chunk number is the next chunk number when the redistribution part is transmitted to the corresponding distribution destination server 2, and is initially set to “1”. The value of the transmission chunk number is incremented by 1 every time transmission of one chunk is completed, and becomes equal to the value of the corresponding chunk number when transmission of all chunks is completed.

  FIG. 7 is a diagram illustrating a configuration and data example of boot image information on the distribution destination server 2. The example of FIG. 7 is an example of data for the distribution destination server [SVR2] 2-2, which will be described later with reference to FIG. The boot image information 261 includes an image ID, a file path, a file size, and an application for every boot image to be distributed to the subordinate server group to which the boot image is distributed from the distribution destination server [SVR2] 2-2. A record consisting of the model is registered.

  The image ID is identification information given to uniquely identify each boot image. The file path is information indicating a position where the corresponding boot image file 262 is registered. The file size is the file size of the corresponding boot image file 262. The applicable model is information indicating the model of the server to which the corresponding boot image file 262 is distributed.

  FIG. 8 is a diagram illustrating a configuration and data example of part information on the distribution destination server 2. The example of FIG. 8 is an example of data for the delivery destination server [SVR2] 2-2, which will be described later with reference to FIG. In the part information 263, a record including a part number, an acquisition destination server ID, an IP address, a data size, and a received data address is registered for every part constituting the boot image being distributed.

  The part number is a serial number assigned to uniquely identify each part. The acquisition destination server ID is identification information for specifying another distribution destination server that is an acquisition destination of the corresponding part. The IP address is address information used for transmitting data to the corresponding distribution destination server 2. The data size is the data size of the corresponding part. The reception data address is position information of the head data of the part 265 storing the data of the corresponding part.

  Note that the acquisition destination server ID and the IP address of the record corresponding to P2 which is the redistribution part assigned to the distribution destination server [SVR2] 2-2 are both “-”. In addition, the reception data addresses “rda1” and “rda3” in parentheses have an empty area of a necessary size in the storage unit 26 at the time when reception of data of the corresponding part from the other distribution destination server 2 is started. The address is determined dynamically.

  FIG. 9 is a diagram illustrating a configuration and data example of acquisition destination server information on the distribution destination server 2. The example of FIG. 9 is a data example of the distribution destination server [SVR2] 2-2, which will be described later with reference to FIG. The acquisition destination server information 264 includes a server ID, an IP address, a part number, a separate transmission / reception, a number of chunks, and a transmission / reception chunk number for each acquisition destination and redistribution destination of all the parts constituting the boot image being distributed. Record is registered.

  The server ID is identification information for specifying the server from which the corresponding part is acquired or redistributed. An IP address is address information used for transmitting / receiving data to / from a corresponding server. The part number is an identification number of a part acquired from the corresponding server or redistributed by the corresponding server. By transmission / reception indicates whether the data of the corresponding part is transmitted or received. When the redistribution part is distributed from the distribution source server 1, the remaining parts are acquired from other servers. In some cases, it is “reception”, and in the case of transmitting its own redistribution parts in response to an acquisition request from another server, it is “transmission”. The number of chunks is the number of chunks constituting the data of the corresponding part. The transmission / reception chunk number is the next chunk number when receiving a part from the corresponding acquisition destination or transmitting its own redistribution part to the corresponding redistribution destination, and is initially set to “1”. The value of the transmission / reception chunk number is incremented by 1 every time transmission / reception of one chunk is completed, and becomes equal to the value of the corresponding chunk number when transmission or reception of all the chunks is completed.

  FIG. 10 is a flowchart illustrating an example of boot image distribution processing executed by the distribution source server 1. When the distribution source server 1 is activated, the boot image receiving unit 11 receives a boot image to be distributed from the maintenance terminal 3 in step S11. At this time, the base group or the destination server group to be distributed from the maintenance terminal 3 is also specified at the same time. The boot image reception unit 11 adds the boot image received from the maintenance terminal 3 to the storage unit 15 as a boot image file 152 and stores the boot image file 152, and additionally registers information related to the boot image in the boot image information 151 (see FIG. 4). .

  Next, in step S12, the parts dividing unit 12 divides the received boot image into a plurality of parts of the same size (corresponding to the dividing step of the present invention). At this time, the division number D includes the number of distribution destination servers 2 to be distributed (the number of distribution destination bases) M and the maximum number of links (the number of links between the bases) L that can be set between the distribution destination servers 2. Are determined by referring to the division number determination table 155 (see FIG. 17).

  The division number determination table 155 illustrated in FIG. 17 is a two-dimensional array in which the number of divisions D to be determined at the intersection of the two is entered, with the vertical direction being the number of distribution destination bases M and the horizontal direction being the number L of links between the bases. . The case of M = 5 will be described as an example. When L = 2, it is not applicable (“x” mark), and when L = 3, L = 4 or L = 5, D = 2, L = 6 In this case, when D = 3 and L = 7, D = 4, and when L = 8 or L = 9, D = 5.

  The part dividing unit 12 calculates the data size of the part by dividing the file size of the boot image file 152 by the determined division number D, and transmits the part data of each part in the boot image file 152 and the first data address. A record including an address and a data size is registered in the part information 153.

  Returning to FIG. 10, next, in step S <b> 13, the redistribution part assignment unit 13 assigns parts to be distributed as redistribution parts to each distribution destination server 2. The allocation is performed by the above-described method based on the number M of distribution destination bases and the number D of divisions.

  Next, in step S14, the redistribution part distribution unit 14 transmits the redistribution parts assigned to each distribution destination server 2 in units of chunks (corresponding to the first distribution step of the present invention). Then, in step S15, the redistribution part distribution unit 14 determines whether or not all chunks of data constituting the part have been transmitted. If all chunks have not been transmitted (No in step S15), the process proceeds to step S14. When the processing is returned and the next chunk is transmitted and all chunks are transmitted (Yes in step S15), the processing is terminated.

  FIG. 11 is a flowchart illustrating an example of boot image transmission / reception processing executed by the distribution destination server 2. When the distribution destination server 2 is activated, in step S21, the redistribution part receiving unit 21 receives the redistribution part transmitted from the distribution source server 1 (corresponding to the first distribution step of the present invention). The reception of the redistribution parts is performed in units of chunks, and the redistribution part reception unit 21 stores the received data of the redistribution parts in the part 265 and corresponds to the part in the part information 263 (see FIG. 8). Register additional records. In addition, the redistribution part receiving unit 21 additionally registers in the boot image information 261 a record (file path is undetermined) indicating the image ID, file size, and applicable model of the boot image notified from the distribution source server 1. Further, when the acquisition source of the remaining parts is notified from the distribution source server 1, the information of the acquisition destination is registered in the part information 263 (see FIG. 8).

  Next, in step S22, the redistribution part transmission unit 22 sends the received redistribution part chunk in response to the acquisition request from the other distribution destination server 2 in step S21 to the other distribution destination server. 2 (corresponding to the second distribution step of the present invention). At this time, the redistribution part transmission unit 22 additionally registers a record corresponding to the other distribution destination server 2 of the request source in the acquisition destination server information 264 (see FIG. 9).

  Next, in step S23, the remaining part acquisition unit 23 receives each of the other parts (remaining parts) that were not received in step S21 as other redistribution parts. A received chunk acquisition request is transmitted, and the received chunk of the remaining part is received (corresponding to the second distribution step of the present invention). Which distribution destination server 2 receives each remaining part is determined with reference to part information 263 (see FIG. 8). At this time, the remaining part acquisition unit 23 additionally registers a record corresponding to the other distribution destination server 2 of the acquisition destination in the acquisition destination server information 264 (see FIG. 9).

  Next, in step S24, the boot image restoration unit 24 determines whether or not all chunks constituting each part have been acquired. If all chunks have not yet been acquired (No in step S24), the process proceeds to step S21. And the above processing is repeated for the next chunk. On the other hand, if all chunks have been acquired (Yes in step S24), the process proceeds to step S25.

  In step S25, the boot image restoration unit 24 restores the original boot image file by combining the acquired parts of all the chunks (corresponding to the restoration step of the present invention). The boot image restoration unit 24 stores the restored boot image file in the storage unit 26 as the boot image file 262 and additionally registers the file path storing the boot image file 262 in the boot image information 261 (see FIG. 7). After that, the process ends.

  Note that steps S21 to S23 in FIG. 11 may be executed in parallel. In that case, the next chunk of the chunks transmitted and received in parallel in steps S22 and S23 is received in parallel with them in step S21.

  FIG. 12 is a sequence chart illustrating an operation example in the case of distributing a boot image divided into two parts to four distribution destination servers 2. In the figure, P1 and P2 represent part 1 and part 2, respectively, and C1 and C2 represent chunk 1 and chunk 2, respectively. Therefore, for example, “P1 (C1) transmission” indicates that the first chunk (chunk 1) of part 1 is transmitted.

  In this case, for each chunk, first, the distribution source server 1 (server ID = MASTER) (hereinafter referred to as distribution source server [MASTER] 1) to the distribution destination server 2 (server ID = SVR1) (hereinafter distribution). Transmission of P1 to the destination server [SVR1] 2-1 and other delivery destination servers) and the destination server [SVR3] 2-3, and the destination servers [SVR2] 2-2 and [SVR4 ] Transmission of P2 to 2-4 is executed in parallel. Subsequently, each distribution destination server [SVR1] 2-1 to [SVR4] 2-4 acquires another part chunk that has not been transmitted to itself, for example, from the distribution destination server 2 on the left side of itself. (However, the delivery destination server on the left side of the delivery destination server [SVR1] 2-1 is the delivery destination server [SVR4] 2-4).

  Parts distribution operation from the distribution source server [MASTER] 1 to each distribution destination server [SVR1] 2-1 to [SVR4] 2-4, and each distribution destination server [SVR2] 2- 1 to [SVR4] 2-4 are all executed in parallel with the operation of acquiring the chunk immediately before another part.

  FIG. 13 is a sequence chart illustrating an operation example when a boot image divided into four parts is distributed to four distribution destination servers. In the figure, P1 to P4 represent part 1 to part 4, respectively, and C1 and C2 represent chunk 1 and chunk 2, respectively.

  In this case, for each chunk, first, P1 to P4 are transmitted in parallel from the distribution source server [MASTER] 1 to the distribution destination servers [SVR1] 2-1 to [SVR4] 2-4, respectively. Subsequently, each distribution destination server [SVR1] 2-1 to [SVR4] 2-4 acquires the remaining three part chunks that were not transmitted to itself from the other distribution destination servers 2 that received them. .

  Parts distribution operation from the distribution source server [MASTER] 1 to each distribution destination server [SVR1] 2-1 to [SVR4] 2-4, and each distribution destination server [SVR2] 2- 1 to [SVR4] 2-4 are all executed in parallel with the operation of acquiring the chunk immediately before another part.

  FIG. 14 is a sequence chart showing an operation example in the case of distributing boot images by dividing five distribution destination servers into two groups of three and two. In this example, three groups are formed by the distribution destination servers [SVR1] 2-1 to [SVR3] 2-3, and two groups are formed by the distribution destination servers [SVR4] 2-4 and [SVR5] 2-5. Assume that a group is formed. In the figure, P1 to P3 represent parts distributed to three groups, Pa and Pb represent parts distributed to two groups, and C1 and C2 represent chunk 1 and chunk 2, respectively.

  In this case, for each chunk, first, P1 to P3 are distributed from the distribution source server [MASTER] 1 to the distribution destination servers [SVR1] 2-1 to [SVR3] 2-3, respectively, and the distribution destination server [SVR4] 2 -4 and [SVR5] 2-5 respectively transmit Pa and Pb in parallel. Subsequently, the delivery destination servers [SVR1] 2-1 to [SVR3] 2-3 receive other chunks of the remaining two parts that have not been transmitted to the other delivery destination servers in the same group as the recipient itself. Get from 2. In parallel with this, the delivery destination servers [SVR4] 2-4 and [SVR5] 2-5 send the remaining one part chunk that was not sent to itself to the other delivery destination in the same group as itself. Obtain from the server 2.

  Parts distribution operation from the distribution source server [MASTER] 1 to each distribution destination server [SVR1] 2-1 to [SVR5] 2-5, and each distribution destination server [SVR2] 2- 1 to [SVR5] 2-5 are all executed in parallel with the acquisition operation of the chunk immediately before another part.

  In the example of FIG. 14, the sizes of P1 to P3 distributed to three groups are smaller than the sizes of Pa and Pb distributed to two groups, so that they are distributed to three groups. The number of chunks is smaller, and distribution ends before the two groups. Therefore, the delivery time, which is the time required to complete delivery to all delivery destination servers, is the delivery time to two groups (the entire boot image file is delivered in parallel from the delivery source server 1 to each delivery destination server 2). It is equal to the ratio of distribution time compared to the case (hereinafter, distribution time ratio) = 1/2).

  FIG. 15 is a sequence chart showing an operation example when delivering a boot image divided into three parts to six delivery destination servers. In the figure, P1 to P3 represent parts divided into three, and C1 and C2 represent chunk 1 and chunk 2, respectively.

  In this case, for each chunk, first, P1 is distributed from the distribution source server [MASTER] 1 to the distribution destination servers [SVR1] 2-1 and [SVR4] 2-4, and the distribution destination server [SVR2] 2-2. And [SVR5] 2-5 are transmitted in parallel, and P3 is transmitted in parallel to the delivery destination servers [SVR3] 2-3 and [SVR6] 2-6, respectively. Subsequently, each of the distribution destination servers [SVR1] 2-1 to [SVR6] 2-6 receives other chunks of the remaining two parts that have not been transmitted to itself, on the left side of each of the distribution destination servers [SVR1] 2-1 to [SVR6] 2-6. Obtained from the destination server 2 (provided that the destination server on the left side of the destination server [SVR1] 2-1 is the destination server [SVR6] 2-6).

  Parts distribution operation from the distribution source server [MASTER] 1 to each distribution destination server [SVR1] 2-1 to [SVR6] 2-6, and each distribution destination server [SVR2] 2- 1 to [SVR6] 2-6 are all executed in parallel with the acquisition operation of the chunk immediately before another part.

  In the example of FIG. 15, each delivery destination server 2 receives the chunks of the parts divided into three parts in parallel, so delivery that is the time required to complete delivery to all delivery destination servers 2. The time is equal to the distribution time to three groups (distribution time ratio = 1/3).

  In the example of FIG. 15, each delivery destination server 2 acquires the remaining two parts that were not delivered to itself from the other delivery destination server 2 nearest to its left side. The distribution destination server 2 may be divided into two groups of three, and the remaining two parts that were not distributed to itself may be acquired from another distribution destination server 2 in the same group as itself.

  FIG. 16 is a diagram showing a list of relationships between the number of divisions D corresponding to the number M of distribution destination sites and the number L of links between sites and the distribution time ratio. For example, no. The data of the first row in which “1” is “1” is the distribution time by setting D = 2 when L = 2 and M = 2, 4, 6, 8,... (M is an even number). It represents that the ratio is “1/2”. Similarly, no. The data of the second row with “2” is the distribution time ratio by setting D = 2 even when L = 3 and M = 3, 5, 7, 9,... (M is an odd number). Represents “½”.

  No. The data in the third row with “3” is D = 3 when L = 4 and M = 3, 6, 9, 12,... (M is a multiple of 3). This indicates that the distribution time ratio is “1/3”. Although detailed explanation is omitted about the data after the 4th line, it turns out that a distribution time ratio can be reduced to "1/2"-"1/5" in any case.

As described above, according to the present embodiment, the distribution of the redistribution parts from the distribution source server 1 to each distribution destination server 2 and the redistribution of the redistribution parts between the distribution destination servers 2 are chunked. Since the processes can be executed in parallel in units, it is possible to shorten the delivery time when delivering the same boot image file to a plurality of delivery destination servers 2.
be able to.

  Although the description of the embodiment of the present invention has been completed above, the embodiment of the present invention is not limited to this, and various modifications can be made without departing from the spirit of the present invention.

DESCRIPTION OF SYMBOLS 1 Distribution origin server 11 Boot image reception part 12 Parts division part 13 Redistribution part allocation part 14 Redistribution part delivery part 15 Storage part 151 Boot image information 152 Boot image file 153 Parts information 154 Delivery destination server information 155 Division number determination table ( A predetermined table that is referenced to determine the number of partitions)
2, 2-1 to 2-6 Distribution destination server 21 Redistributed parts receiving unit 22 Redistributed parts transmitting unit 23 Remaining parts acquiring unit 24 Boot image restoring unit 25 Boot image distributing unit 26 Storage unit 261 Boot image information 262 Boot image file 263 Parts information 264 Acquisition destination server information 265 Parts 3 Maintenance terminal 4 Network between bases 100 Boot image distribution system

Claims (4)

A boot image distribution method for distributing the same boot image file to a plurality of distribution destination servers,
A distribution step in which the distribution source server receives the boot image file distribution request and divides the boot image file into a plurality of parts;
Each of the plurality of parts, is divided into chunks of predetermined size, one of the parts consisting of the divided chunks, as at least redistribute part to one of said distribution destination server from said distribution source server, A first distribution step of performing distribution in units of chunks in parallel to all distribution destination servers ;
Each of the delivery destination servers transmits the redistributed parts delivered to itself in parallel to the other delivery destination servers predetermined for each delivery destination server in units of chunks, and the redistributed parts delivered to itself. A second distribution step of receiving, in parallel, the remaining parts other than the distribution parts in units of the chunks from other distribution destination servers predetermined for each distribution destination server;
A restoration step in which each of the delivery destination servers combines the redistribution part received in the first delivery step and the remaining part received in the second delivery step to restore the boot image file; Including ,
When the number of distribution destination servers is a multiple of the number of divisions of the parts, the allocation method related to the acquisition destination of the remaining parts is to group the distribution destination servers into the division units, The other delivery destination servers are the acquisition destinations of the remaining parts, or when the number of delivery destination servers is not a multiple of the division number of the parts, the boot image file is not the delivery destination. When another distribution destination server is added to the distribution destination of the redistribution part, and the number of distribution destination servers is a multiple of the division number, the other distribution destination server that assists the distribution of the redistribution part is In addition to the distribution destination of the redistributed parts, the grouping is made an acquisition destination of the remaining parts,
Before SL parallel transmission and parallel reception of the chunk in the second delivery step, the boot image distribution method characterized in that it is performed in parallel distributed in parallel with the next chunk of the chunk in the first distribution step. The boot image delivery method according to claim 1,
The number of divisions when dividing into the plurality of parts in the division step is the number of the distribution destination servers to which the same boot image file should be distributed and the distribution destination servers that can be set between the distribution destination servers. A boot image distribution method characterized by being determined with reference to a predetermined table referred to for determining the number of divisions using the number of links as a parameter. The distribution source server is a boot image distribution system that distributes the same boot image file to a plurality of distribution destination servers,
The distribution source server is:
A boot image receiving unit that receives a distribution request for the boot image file;
A parts dividing unit for dividing the boot image file into a plurality of parts;
Each of the plurality of parts, is divided into chunks of predetermined size, one of the parts consisting of the divided chunks, as at least redistribute part to one of said distribution destination server from said distribution source server, A redistribution part distribution unit that performs distribution in units of chunks in parallel to all distribution destination servers ;
Each of the delivery destination servers is
A redistribution part receiving unit that receives the redistribution part distributed to itself in units of chunks;
A redistribution part transmitting unit that transmits the received redistribution part in parallel to the other distribution destination server predetermined for each distribution destination server in units of chunks;
Remaining parts other than the redistributed parts distributed to itself, a remaining parts acquisition unit that receives in parallel in units of chunks from other distribution destination servers predetermined for each distribution destination server;
A boot image restoration unit that combines the redistribution part received by the redistribution part receiving unit and the remaining part received by the remaining part acquisition unit to restore the boot image file ;
The redistribution part distribution unit, as an allocation method related to the acquisition destination of the remaining parts, when the number of distribution destination servers is a multiple of the number of divisions of the parts, When the group is divided and the other distribution destination servers in the group are obtained from the remaining parts, or the number of the distribution destination servers is not a multiple of the division number of the parts, the boot When the other distribution destination server that is not the image file distribution destination is added to the redistribution part distribution destination, and the number of the distribution destination servers is a multiple of the division number, the distribution of the redistribution part is assisted. Adding the other distribution destination server to the distribution destination of the redistribution parts, and grouping it as the acquisition destination of the remaining parts.
And parallel receiving of the chunks in the parallel transmission and the remaining part acquisition unit of the chunks before Symbol redistributing part transmitting unit, and the reception of the next chunk of the chunk in the re-distribution part receiving unit is performed in parallel A boot image distribution system characterized by that. In the boot image delivery system according to claim 3 ,
The distribution source server is:
The part divided parts, the number of the same boot image file the destination server to be delivered to, and the number of links per destination server configurable between their delivery destination server as a parameter, the plurality of parts A boot image distribution system comprising a predetermined table referred to in order to determine the number of divisions when dividing into two.

Images