WO2007096963A1 - Programme et procede de controle de serveur et controleur de serveur - Google Patents

Programme et procede de controle de serveur et controleur de serveur Download PDF

Info

Publication number
WO2007096963A1
WO2007096963A1 PCT/JP2006/303227 JP2006303227W WO2007096963A1 WO 2007096963 A1 WO2007096963 A1 WO 2007096963A1 JP 2006303227 W JP2006303227 W JP 2006303227W WO 2007096963 A1 WO2007096963 A1 WO 2007096963A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
patch
information
candidate
performance
Prior art date
Application number
PCT/JP2006/303227
Other languages
English (en)
Japanese (ja)
Inventor
Tsutomu Kawai
Satoshi Tsuchiya
Motomitsu Adachi
Original Assignee
Fujitsu Limited
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 Fujitsu Limited filed Critical Fujitsu Limited
Priority to JP2008501521A priority Critical patent/JP5035237B2/ja
Priority to PCT/JP2006/303227 priority patent/WO2007096963A1/fr
Publication of WO2007096963A1 publication Critical patent/WO2007096963A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment

Definitions

  • the present invention relates to a server management program, a server management apparatus, and a server management method, and more particularly to a server management program, a server management apparatus, and a server management method that perform on-demand operation of a server.
  • Patent Document 1 Japanese Patent No. 3385590
  • the notch may adversely affect the operation depending on the combination and the order of application, and there are problems in applying patches while maintaining consistency. There is a problem that there is no need to select a combination or application order.
  • it is necessary to construct the environment before the delivery deadline and pass it to the customer. Therefore, it is necessary to consider the time to apply the patch, unlike the usual application of a patch.
  • the present invention has been made in view of these points, and an object of the present invention is to provide a server management program, a server management apparatus, and a server management method capable of quickly and surely preparing a server. . Another object of the present invention is to provide a server management program, a server management apparatus, and a server management method that can improve the operational efficiency of data center resources.
  • a server management program for causing a computer to execute a process as shown in FIG. 1 is provided.
  • the server management program according to the present invention is a program mainly for on-demand operation of a server.
  • the computer 1 that executes the server management program has functions of patch information storage means 2, extraction means 3, server preparation means 4, and service provision start means 5.
  • the patch information storage unit 2 stores patch information.
  • the extraction means 3 receives the patch information of the patch information storage means 2 Referring to multiple standby servers 6, 7, 8 ... with different performance, when applying the patch types to be applied, they have the performance to satisfy the server preparation requirements and can be prepared within the deployment upper limit time Judge whether the server is a candidate and wait The machine server is extracted as a server candidate.
  • the server preparation unit 4 prepares a service providing server by applying a patch type patch to the standby server corresponding to the server candidate extracted by the extraction unit 3.
  • the service provision start means 5 starts service provision using the service provision server prepared by the server preparation means 4.
  • the extraction means 3 refers to the patch information in the patch information storage means 2, and the standby servers 6, 7, 8,.
  • the standby server that can be prepared is the server Extracted as a candidate.
  • the server preparation unit 4 prepares a service providing server in which the patch type notch is applied to the standby server corresponding to the server candidate extracted by the extraction unit 3.
  • the service provision start means 5 starts service provision using the service provision server prepared by the server preparation means 4.
  • the patch information storage means storing the patch information and the notification type to be applied from the request source are applied.
  • Prepare a server with the required performance within the maximum deployment time When there is a server preparation request, refer to the patch information and apply the patch type to be applied to each of the standby servers with different performance.
  • Extraction means for extracting whether a standby server that has performance that satisfies the server preparation request and can be prepared within the deployment upper limit time and is ready as a server candidate is extracted by the extraction means
  • Server preparation means for preparing a service providing server by applying a patch of the patch type to the standby server corresponding to the server candidate, and the server preparation
  • a server management apparatus comprising service provision start means for starting service provision using the service provision server prepared by the means.
  • a server management method that performs on-demand server operation If there is a server preparation request that prepares a server with the required performance to which the patch type to be applied is applied from the request source within the deployment upper limit time, refer to the patch information, and multiple standby servers with different performance Each of the above-mentioned patch types to be applied has a performance satisfying the server preparation request, and it is determined whether preparation is possible within the deployment upper limit time.
  • Prepare a service providing server by applying the patch type patch to the standby server corresponding to the extracted server candidate, and start providing the service using the prepared service providing server A server management method is provided.
  • the patch information is referred to.
  • the performance to satisfy the server preparation request is determined, and the ready power is judged within the upper limit of the deployment time.
  • Possible standby servers are extracted as server candidates. Then, a notch for each patch type is applied to the standby server corresponding to the extracted server candidate, and a service providing server is prepared. Thereafter, service provision is started using the prepared server for service provision.
  • the server when a patch type to be applied to each of a plurality of standby servers having different performances is applied, the server has a performance that satisfies the server preparation request and can be prepared within the deployment upper limit time. Since it is determined whether it is a failure or not and a standby server that can be prepared is extracted, server candidates corresponding to the server preparation request can be prepared quickly and surely, and server management can be performed with high reliability. it can.
  • resource management efficiency can be improved by preparing server candidates corresponding to server preparation requests.
  • FIG. 1 is a principle view showing an invention applied to the embodiment.
  • FIG. 2 is a diagram showing an outline of a network system according to an embodiment.
  • FIG. 3 is a diagram illustrating a hardware configuration example of a management server.
  • FIG. 4 is a block diagram showing an internal configuration of the management server.
  • FIG. 5 is a diagram showing required environment information.
  • FIG. 6 shows a master image information table
  • FIG. 7 shows a patch information DB.
  • FIG. 8 is a flowchart showing the main operation of the management server.
  • FIG. 9 is a flowchart for explaining a server replacement operation.
  • FIG. 10 shows an application order list
  • FIG. 11 is a flowchart illustrating a server selection operation.
  • FIG. 12 shows an entry list
  • FIG. 13 is a flowchart illustrating an application order list acquisition operation.
  • FIG. 14 is a diagram showing a master image information table in which a new master image is created.
  • FIG. 15 is a diagram showing an entry list of required patch configurations.
  • FIG. 16 is a diagram showing an application order list of required patch configurations.
  • FIG. 1 is a principle diagram showing the invention applied to the embodiment.
  • the computer 1 shown in FIG. 1 includes patch information storage means 2, extraction means 3, and server preparation means.
  • the patch information storage means 2 stores patch information.
  • a patch is a bug or a patch that corrects something that needs to be corrected.
  • This patch information is used to apply arbitrary notches to multiple standby servers 6, 7, 8,. This information includes the time information required for the server and the performance information of the standby servers 6, 7, 8... When an arbitrary patch is applied.
  • the extraction unit 3 When there is a server preparation request for preparing a server having necessary performance to which the patch type to be applied from the request source is applied within the deployment upper limit time, the extraction unit 3 notifies the patch information storage unit 2 of the notification. Referring to the information, find the patch type to which any patch force should be applied, and have the performance to satisfy the server preparation requirements when applying the applicable patch type for each standby server 6, 7, 8, In addition, it is determined whether preparation is possible within the deployment upper limit time, and ready servers are extracted as server candidates.
  • the extraction unit 3 determines whether or not server candidates for each pattern can be prepared.
  • the server preparation unit 4 prepares a service providing server by applying a patch of a patch type to the server corresponding to the server candidate extracted by the extraction unit 3.
  • FIG. 1 shows a case where the standby server 8 is extracted as a server candidate and the service providing server 8a is prepared.
  • the service provision start means 5 starts service provision using the service provision sano 8 a prepared by the server preparation means 4.
  • the notch may be stored in the force computer 1 exemplifying the case of receiving the external force.
  • the extraction method 3 when there is a server preparation request for preparing a server having the required performance to which the patch type to be applied from the request source is applied within the deployment upper limit time, the extraction method 3 performs patch information storage.
  • the patch information to be applied is applied to each standby server 6, 7, 8, ... with different performance, the patch information of method 2 is referenced, and the deployment upper limit is met.
  • a determination is made as to whether or not preparation is possible in time, and ready standby servers 8 are extracted as server candidates.
  • the server preparation means 4 applies the patch type patch to the standby server 8 and prepares the service providing server 8a. Thereafter, the service providing start means 5 starts providing the service using the service providing server 8a.
  • the server resource (server environment, process) according to the server preparation request of the supplier. Can be quickly and reliably supplied to the supplier.
  • FIG. 2 is a diagram illustrating an overview of the network system according to the embodiment.
  • a management server 100 In the network system 500, a management server 100, a master image holding server 200, a patch holding server 300, and a server pool group 20 are connected via a management network 10.
  • the management server 100 is connected to a client (terminal device) (not shown) via the management network 10.
  • the management server 100 selects a server to be supplied to the client from the server pool group 20 in response to a server deployment request from the client and applies a patch (hereinafter referred to as a “service providing server”). Prepare and supply to clients.
  • a server deployment request from a client is notified by request environment information indicating a server deployment request environment.
  • the required environment information will be described later.
  • the server pool group 20 is composed of a plurality of servers that are actually deployed on demand, and each server has software to which patches have not been applied.
  • the server pool group 20 includes a plurality of server pools in which the calculation speed of each server, the number of mounted CPUs, and the like are different.
  • a server pool 23 having a plurality of servers S3 configured with a 4U size housing with more than the installed CPU power, and a power S are provided.
  • the master image holding server 200 holds a master image that is an image of a system to be assigned when the management server 100 prepares a service providing server.
  • the notch holding server 300 holds patches ⁇ 1, ⁇ 2, ... applied to the server selected when the management server 100 prepares a service providing server.
  • the management server 100 refers to the master image of the master image holding server 200 in response to a server deployment request from a client, and responds to a request from the servers S1 to S3 in the server pool group 20. Select the selected server, and The service providing server is deployed by extracting the patch to be applied from the patch holding server 300 and applying it, and supplying it to the requested client.
  • FIG. 2 the management mechanism for server deployment, other configurations used for server on-demand deployment such as network connection other than the management network, and the server for providing services already supplied to the client!
  • the illustration is omitted.
  • FIG. 3 is a diagram illustrating a hardware configuration example of the management server.
  • the management server 100 is entirely controlled by a CPU (Central Processing Unit) 101.
  • a random access memory (RAM) 102, a hard disk drive (HDD) 103, a graphic processing device 104, an input interface 105, and a communication interface 106 are connected to the CPU 101 via a bus 107 !.
  • the RAM 102 temporarily stores at least part of an OS (Operating System) program application program to be executed by the CPU 101.
  • the RAM 102 stores various data necessary for processing by the CPU 101.
  • the HDD 103 stores an OS application program.
  • a program file is stored in the HDD 103.
  • a monitor 11 is connected to the graphic processing device 104.
  • the graphic processing device 104 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 101.
  • a keyboard 12 and a mouse 13 are connected to the input counter face 105.
  • the input interface 105 transmits a signal sent from the keyboard 12 or mouse 13 to the CPU 101 via the bus 107.
  • the communication interface 106 is connected to the management network 10.
  • the communication interface 106 transmits and receives data to and from other computers via the management network 10.
  • the master image holding server 200 and the patch holding server 300 can also implement the processing functions of the present embodiment with the same hardware configuration.
  • the following functions are provided.
  • FIG. 4 is a block diagram showing the internal configuration of the management server.
  • the management server 100 includes a request environment reception unit 110, a request environment DB 120, and a server selection unit 1
  • master image information DB 140 patch information DB 150, server preparation unit 160, service provision start unit 170, and server reconfiguration unit 180.
  • the request environment receiving unit 110 Upon receiving the request environment information from the client, the request environment receiving unit 110 stores the request environment information in the request environment DB 120. Thereafter, the requested environment receiving unit 110 notifies the server selecting unit 130 that the requested environment information has been received.
  • the required environment DB 120 stores required environment information in a table.
  • FIG. 5 is a diagram showing the required environment information.
  • the required environment information table 121 has columns corresponding to each item of the required environment information, that is, required environment, OS, patch (required Z recommended), performance, and upper limit of deployment time (minutes). . Information arranged in the horizontal direction is associated with each other.
  • a request environment name for identifying the request environment is set.
  • the required environments 1 to 3 are set, respectively.
  • the OS (Operating System) of the requesting client is set in the OS column.
  • OS “01” is required for each.
  • an essential patch that is a minimum required patch and a recommended patch to which a more preferable patch is applied for server operation are set.
  • the recommended patch is indicated by a plus (+) in order to apply the notches.
  • patch P2 is set for each mandatory patch, and patches P1 and P2 are set in this order (P1 + P2) for each recommended patch.
  • a required performance value is set.
  • This numerical value represents a numerical value indicating, for example, instruction processing performance or data processing performance. In this embodiment, the larger the numerical value, the higher the processing operation function. In Figure 5, “50” is set for both.
  • the upper limit of required deployment time is set in minutes.
  • the maximum deployment time for requirement environment 1 is set to 30 minutes, and deployment of requirement environment 2
  • the time limit is set to 20 minutes, and the deployment time limit for requirement environment 3 is set to 10 minutes.
  • Each requested environment information in the requested environment information table 121 is deleted when a service supply server corresponding to each requested environment 1 to 3 is supplied.
  • the server selection unit 130 Upon receiving a notification from the request environment reception unit 110, the server selection unit 130 extracts the corresponding request environment information from the request environment information table 121 of the request environment DB 120, and acquires the master image information DB 140 and the patch information DB 150. Refer to it and create an application order list composed of the recommended patches set in the recommendation field of the required environment information (hereinafter referred to as “application order of recommended patch configuration”).
  • This application order list is a list in which server candidate information created to satisfy the required environment for each server is described.
  • the server selection unit 130 performs a server selection operation for extracting one piece of information (hereinafter, “recommended patch final information” t) from the server candidate information in this application order list! Determine whether the information satisfies the requirements for the recommended patch, performance, and maximum deployment time for the required environment information (whether it is a recommended sano).
  • the server configuration information for realizing the configuration of the server (server candidate) described in the recommended patch final information is transmitted to the server preparation unit 160.
  • the server selection unit 130 extracts the requested environment information from the requested environment information table 121 of the requested environment DB 120, and refers to the master image information DB 140 and the patch information DB 150. Then, create an application order list composed of the required patches set in the required fields of the required environment information (hereinafter referred to as “application order list of required patch configuration”).
  • the server selection unit 130 performs a server selection operation to extract one piece of information (hereinafter referred to as "essential patch final information" t) from the server candidate information in the applied list! Server for realizing the candidate server configuration described in the mandatory patch final information after determining whether the mandatory patch final information satisfies the required patch and performance conditions of the required environment information (whether it is mandatory sano)
  • the configuration information is transmitted to the server preparation unit 160.
  • Server selection unit 130 also transmits server configuration information to server reconfiguration unit 180.
  • Master image information DB 140 is master image information that is information about the OS, patch, model, and performance of each master image. Is stored.
  • the master image information DB 140 stores and stores master image information.
  • FIG. 6 is a diagram showing a master image information table.
  • the master image information table 141 has columns for master image name, OS, patch, model, and performance. Information arranged in the horizontal direction is associated with each other
  • master image name column a master image name for identifying master image information is set.
  • master images Ml and M2 are set.
  • the OS is set in the OS column. In FIG. 6, OS “01” is set.
  • a server corresponding to the master image is set.
  • the server S1 is set in the master image Ml
  • the server S2 is set in the master image M2.
  • a value indicating the server performance is set. This numerical value is consistent with the numerical value set in the performance column of the required environment information table 121.
  • a patch is set in the patch column
  • a numerical value indicating the performance of the server to which the patch is applied is set.
  • the “Notify” column is set to “None”, a value indicating the performance of the server is set.
  • “100” is set in the master image Ml
  • “200” is set in the master image M2.
  • the notch information DB 150 stores a plurality of pieces of patch information in a table.
  • the notch information is information indicating time information necessary for applying patches to the servers S1 to S3 and performance information when applying patches to these servers.
  • One piece of patch information is information when a new patch is applied to a server that has not yet been applied. Or information on applying other patches to a server to which a patch has already been applied.
  • FIG. 7 is a diagram showing the notch information DB.
  • the notch information table 151 includes columns for unit name, application source, before application, model, application order, application time, restart, after application, and performance. Information arranged in the horizontal direction is associated with each other. In the following description, since the function of the column having the same name as the master image information table 141 is the same, the description is omitted.
  • unit name column a unit name for identifying notch information is set.
  • units U1 to U6 are set.
  • the master image or unit that is the application source is set in the application source column.
  • a master image When a master image is set, it indicates that this is information that will be applied to a server that has not yet been patched.
  • the notch information indicates that this patch is further applied to a unit to which the patch has already been applied.
  • master images Ml are set for units Ul and U3
  • master images M2 are set for units U2 and U4
  • unit U1 is set for unit U5
  • unit U2 is set for unit U6. ing.
  • the OS before application is set, and if there is a patch applied, the patch name is set.
  • the OS “01” is set for each of the units U1 to U6, and the patch P1 is set for the units U5 and U6.
  • a server to which the current patch is applied is set in the Model column.
  • the server SI is set for each of the units Ul, U3, and U5
  • the server S2 is set for each of the units U2, U4, and U6.
  • the patch to be applied this time is set according to the patch information.
  • the patch PI is set for each of the units Ul and U2
  • the patch P2 is set for each of the units U3 to U6.
  • the application time of the patch set in the application order column is set.
  • the application time to apply patch P1 to server S1 is “15 minutes”.
  • the application time to apply patch P1 to server S2 is set to ⁇ 10 minutes '', and in units U3 and U5, the application time to apply patch P2 to server S1 is set to ⁇ “10 minutes” is set, and in units U4 and U6, the time to apply patch P2 to server S2 is set to “5 minutes”.
  • the number of times that restart is required is set. If no restart is required, “None” is set.
  • the number of restarts is mainly determined by the type of patch. In Fig. 7, the number of times that Units Ul and U2 need to be restarted is set to "1", and the number of times that Units U3 to U6 need to be restarted is set to "None".
  • the server preparation unit 160 Upon receipt of the server configuration information, the server preparation unit 160 selects a server described in the server configuration information from the server pool group 20, and patches the patch described in the server configuration information to the selected server.
  • a service providing server is prepared by taking it out from the holding server 300 and applying it, and a service providing permission signal is transmitted to the service providing starting unit 170.
  • the service provision start unit 170 When the service provision start unit 170 receives the service provision permission signal, the service provision start unit 170 starts supplying the service provision server prepared by the server preparation unit 160 to the client.
  • the server reconfiguration unit 180 performs the server replacement operation according to the situation together with the server preparation unit 160 and the service provision start unit 170.
  • the server reconfiguration unit 180 When the server reconfiguration unit 180 receives the server configuration information from the server selection unit 130, the server reconfiguration unit 180 among the servers satisfying the recommended patches and performance conditions of the required environment information regardless of the deployment time request (deployment time upper limit).
  • the server information with the lowest performance value (hereinafter referred to as “minimum resource server information”) is created, and it is determined whether the server configuration information matches the minimum resource server information. If they do not match, the minimum resource server information is transmitted to the server preparation unit 160. Thereafter, the server reconfiguration unit 180 newly adds master image information such as server reconfiguration information. Information is registered in the master image information table 141 (added).
  • the server preparation unit 160 Upon receiving the minimum resource server information, the server preparation unit 160 selects a server described in the minimum resource server information from the server pool group 20 and describes the minimum resource server information in the selected server.
  • the reconfigured server is prepared by taking out the applied patch from the patch holding server 300 and applying it, and a server replacement signal is transmitted to the service provision start unit 170.
  • the service provision start unit 170 Upon receiving the server replacement signal, the service provision start unit 170 starts supplying the reconfigured server prepared by the server preparation unit 160 to the client and collects the service provision server supplied to the client last time. .
  • FIG. 8 is a flowchart showing the main operation of the management server.
  • the requested environment receiving unit 110 receives requested environment information from a client, the requested environment information is stored in the requested environment DB 120. Thereafter, the requested environment receiving unit 110 notifies the server selecting unit 130 that the requested environment information has been received (step Sl l).
  • the server selection unit 130 creates a recommended patch configuration application order list, and extracts recommended patch final information (step S 12).
  • the server selection unit 130 determines whether or not the recommended patch final information that has been extracted is sufficient to satisfy the deployment time request (step S13).
  • the recommended patch final information satisfies the deployment time request (Yes in step S13)
  • the recommended patch final information is transmitted as server configuration information to the server preparation unit 160 (step S16).
  • the recommended patch final information does not satisfy the deployment time requirement (No in step S13)
  • an application order list of the required patch configuration is created and the required patch final information is extracted (step S14).
  • it is determined whether or not the mandatory patch final information satisfies the deployment time requirement step S15).
  • step S15 If the mandatory patch final information satisfies the deployment time request (Yes in step S15), the mandatory patch final information is transmitted to the server preparation unit 160 as server configuration information (step S16). On the other hand, if the mandatory patch final information is strong enough to meet the deployment time requirement (No in step S15), the management server 100 administrator is informed, for example, that the mandatory patch final information is strong enough not to meet the deployment time requirement. 11 (step S17), and the mandatory patch final information is used as server configuration information. The data is transmitted to the server preparation unit 160 (step S 16).
  • the server preparation unit 160 prepares a server for providing server configuration information power service (step S18).
  • the service provision start unit 170 starts service provision using the service provision server (step S19).
  • FIG. 9 is a flowchart for explaining the server replacement operation.
  • the minimum resource server information is created (step S51).
  • step S52 it is determined whether or not the minimum resource server information matches the server configuration information.
  • step S52 If the minimum resource server information matches the server configuration information (Yes in step S52), the server replacement operation is terminated. On the other hand, if the minimum resource server information does not match the server configuration information (No in step S52), the minimum resource server information is transmitted to the server preparation unit 160 (step S53).
  • the server preparation unit 160 prepares a reconfiguration server using the minimum resource server information (step S56).
  • the service provision start unit 170 replaces the service provision server supplied to the client last time with the reconfiguration server (step S57).
  • FIG. 10 is a diagram showing an application order list.
  • server candidate information which is information for realizing a server with a recommended patch configuration or a server with a required patch configuration of the required environment 1, is described for each of the servers Sl and S2.
  • the application order list 211 candidates, recommended, required, master images, application order, application time, performance There is a column for this. Information arranged in the horizontal direction is associated with each other, and a candidate name for identifying server candidate information is described in the candidate column.
  • “candidate 1” is described in the candidate name of server S1
  • “candidate 2” is described in the candidate name of server S2.
  • the mandatory column the mandatory patch of the mandatory patch final information is described.
  • the recommended column is blank.
  • candidate patch “P1 + P2” is listed in the recommendation column for both candidate candidates 2.
  • master image column a master image for each server is described.
  • master image Ml is listed in candidate 1 and master image M2 is listed in candidate 2.
  • the application time column the application when applying the patches set in the application order (or recommended) column to the server corresponding to the master image set in the master image column in this order. Time (minutes) is listed. In Figure 10, “25” is listed in Candidate 1. Candidate 2 contains “15”.
  • the performance column the numerical value of the performance when the patches set in the application order (or recommended) column are applied to the server corresponding to the master image set in the master image column. ing. In FIG. 10, “105” is described in candidate 1 and “210” is described in candidate 2.
  • FIG. 11 is a flowchart for explaining the server selection operation.
  • a server type (servers S1 to S3) is selected from the server pool 21 (step S21).
  • server candidate information of the selected server type is acquired (step S22).
  • step S 23 it is determined whether or not the acquired server candidate information is capable of satisfying the performance requirement. If the performance requirement is not satisfied (No in step S23), the process proceeds to step S31. On the other hand, if the performance requirement is satisfied (Yes in step S23), it is determined whether or not the final information already exists (step S24). If there is no final information (No in step S24), the process proceeds to step S30. If the final information already exists (Yes in step S24), it is determined whether or not the acquired server candidate information satisfies the deployment time request and is capable (step S25). If the deployment time request is not satisfied (No in step S25), it is determined whether the registered final information satisfies the deployment time request (step S26).
  • step S31 When the final information satisfies the distribution time requirement (Yes in step S26), the process proceeds to step S31. On the other hand, if the final information does not satisfy the deployment time requirement (No in step S26), whether the acquired server candidate information can be shortened compared to the server candidate information registered in the final information. Judgment is made (step S27). If it is not possible to shorten the deployment time! / (Step S27 No), go to step S31. On the other hand, if the deployment time can be shortened (Yes in step S27), the process proceeds to step S30.
  • step S28 it is determined whether the final information registered is sufficient to satisfy the deployment time request. If the final information does not satisfy the deployment time requirement (No in step S28), the process proceeds to step S30. On the other hand, if the final information satisfies the deployment time requirement (Yes in step S28), the acquired server candidate information is registered in the final information !, which is lower than the server candidate information. Judgment is made on the possibility of specification (Step S29) If the specification can be reduced (Yes in Step S29), the obtained server candidate information is overwritten in the final information (Step S30). If not possible (No in step S29), the process proceeds to step S31.
  • step S31 it is determined whether or not a server selection operation has been executed for all server types in the server pool 21 (step S31). Perform server selection for all server types If not (No in step S31), the process proceeds to step S21 to select another server type and continue the server selection operation. On the other hand, if the server selection operation has been executed for all server types (Yes in step S31), the server selection operation is terminated. As a result, if the server candidate information registered in the final information is the recommended patch configuration final information, it becomes the recommended patch final information, and if the server candidate information registered in the final information is the final information of the mandatory patch configuration, it is required This is the final patch information.
  • the server candidate information extracts the entry information described in the entry list created for each of the servers S1 to S3 (for each server type) by referring to the master image information and the patch information in the required environment information. It is a thing.
  • This entry list is created when the recommended patch configuration application order list is created and when the required patch configuration application order list is created.
  • FIG. 12 shows an entry list
  • the entry lists 221 and 222 include stage, recommended, required, unit, and application source unit, respectively.
  • Patch, Deployment time performance columns are provided.
  • Information arranged in the horizontal direction is associated with each other.
  • Entry information 221a and entry information 221b are set in the entry list 221.
  • entry information 222a and entry information 222b are set!
  • the step column describes a step for identifying entry information. It shows that the entry information is expanded as the number of steps increases.
  • Stepl and Step 2 are listed. The unfolding operation will be described later.
  • the required column a recommended patch of required environment information for creating an application order list of recommended patch configurations is set.
  • the required column is blank.
  • the required field contains information on the required environment information when creating an application order list of required patch configurations. Required patches are set. In this case, the recommended column is blank. In Figure 12, the recommended patch “P1 + P2” is set in the Recommended column!
  • the unit column is integrated with “+” in the order in which the same patch as the patch described in the recommended or required column (hereinafter “corresponding unit” t, u) is applied. Is done.
  • the application source unit set in the application source column of the corresponding unit in the patch information table 151 is set.
  • the entry information is expanded until the applicable unit column becomes the master image.
  • entry information when the column of the application source unit is a master image is extracted as server candidate information.
  • entry information 22 lb and entry information 222b are respectively extracted as server candidate information.
  • the patch column describes the patch set in the column of the application order of the corresponding unit in the patch information table 151 and the application time to apply the patch.
  • the deployment time column describes the time for preparing the service providing server. The deployment time is described only in the server candidate information.
  • a numerical value indicating the server performance is set.
  • FIG. 13 is a flowchart for explaining the application order list acquisition operation.
  • step S42 the required environment information is extracted from the required environment information table 121 (step S42).
  • a unit that matches the condition of the required environment information is searched (step S43). Specifically, a master image having an OS and model name corresponding to the OS set in the OS column of the required environment information is extracted from the master image information table 141 and set in the patch column of the required environment information. A unit having a model name that matches the patch corresponding to the recommended patch and the master image information table 141 is searched from the column after application of the patch information table 151.
  • step S45 it is determined whether or not server candidate information has been created for all entry lists.
  • step S46 to S48 a deployment operation is performed (steps S46 to S48). Specifically, the server candidate information has not been created! /, The entry list is extracted (step S46), and the notch information having a unit name that matches the unit condition set in the application source unit column is patched. Search from information table 151 (step S47). Next, new step entry information is created in the entry list based on the search result. Specifically, the unit or master unit that is set in the patch information application source column of the search result is described in the application source unit column of the entry list, and is set in the application order column of the notch information. The new entry information described on the left side (previous stage) of the notch described in the patch information column of the previous step entry is created (step S48), and the process proceeds to step S45.
  • step S45 if server candidate information has been created for all entry lists (Yes in step S45), all entry lists are referenced, and server candidate information with the shortest deployment time is obtained for each entry list. Store in the application order list. (Step S49).
  • the request environment receiving unit 110 receives the request environment 1 from the client, the request environment 1 is stored in the request environment DB 120. Thereafter, the requested environment receiving unit 110 notifies the server selecting unit 130 that the requested environment information has been received.
  • the server selection unit 130 extracts the requested environment 1 from the requested environment information table 121.
  • a unit having a patch corresponding to the recommended patch “P1 + P2” in the requirement environment 1 as condition 1 in the field after application of the patch information table 151 is searched. Also, as condition 2 For the unit having the OS corresponding to os “01” in the demand environment 1, the field power before application of the master image information table 141 is also searched.
  • Units U5 and U6 that satisfy condition 1 and units U1 to U6 that satisfy condition 2 are listed as search candidates, so units U5 and U6 that satisfy condition 1 and condition 2 are selected, and their entry information is stored in the server.
  • the entry information 221a of the entry list 221 of S1 and the entry information 222a of the entry list 222 of the server S2 are described. Then, the server candidate information is extracted for each of the entry information 221a and 222a.
  • the application source unit column of unit U6 in the patch information table 151 of the entry information 222a is unit U2 (not a master unit), refer to unit U2 and add a new “U2 + ⁇ U6 '', the application source unit M2 is written in the column of application source unit, patch P1 set in the application order of unit U2 and its application time 10 minutes are created in the patch column to create entry information 222b . Then, since the application source unit of the entry information 222b is the master image M2, a total of “15”, which is a time “10” for applying the patch P1 to the server S2 and a time “5” for applying the patch P2 to the server S2 after that. Is stored in the application order list 211 as server candidate information “candidate 2”.
  • two pieces of server candidate information are stored in the application order list 211.
  • the server selection unit 130 performs a server selection operation.
  • server candidate information “candidate 1” is acquired.
  • Server candidate information “Candidate 1" is required environment Satisfies performance “50” required in 1. Since the server candidate information “candidate 1” is the first candidate and there is no final information, the server candidate information “candidate 1” is registered in the recommended patch final information.
  • server candidate information “candidate 2” is acquired.
  • Server candidate information “Candidate 2” satisfies the performance “50” required in the required environment 1.
  • the recommended patch final information already exists! Therefore, the server candidate information “Candidate 2” satisfies the deployment time requirement! Judge whether or not you have the power. Since the deployment time request is also satisfied, it is determined whether or not the recommended patch final information (server candidate information “candidate 1”) satisfies the deployment time request. Since the recommended patch final information satisfies the deployment time requirement, it is determined whether or not the specifications can be saved compared to the server candidate information “Candidate 1”.
  • the server candidate information “candidate 2” has a larger value in the performance column than the server candidate information “candidate 1”! /, (Excess performance), so the recommended patch final information is overwritten.
  • the server selection operation is performed for all server candidate information, the server candidate information “candidate 1” is selected as the recommended patch final information.
  • the server preparation unit 160 and server reconfiguration are performed using the server candidate information “candidate 1” as server configuration information. Send to part 180. Then, the service provision start unit 170 starts service provision using the service provision server.
  • a server replacement operation is performed.
  • the minimum resource server information is created, and it is determined whether or not the minimum resource server information matches the server configuration information.
  • the server replacement operation ends because the minimum resource server information matches the server configuration information.
  • the parameters other than the deployment time upper limit are the same.
  • the same application order list 211 is created.
  • the server candidate information “candidate 1” satisfies the performance “50” required in the required environment 2. Since the server candidate information “candidate 1” is the first candidate and there is no recommended patch final information, the server candidate information “candidate 1” is registered in the recommended patch final information.
  • server candidate information “candidate 2” is acquired.
  • the server candidate information “candidate 1” satisfies the performance “50” required in the requirement environment 2 and satisfies the requirement. Since the recommended patch final information already exists! / ?, it is determined whether or not the server candidate information “Candidate 2” satisfies the deployment time request! /. In order to satisfy the deployment time requirement! /, It is determined whether the recommended patch final information (server candidate information “candidate 1”) satisfies the deployment time requirement. Since the recommended patch final information satisfies the deployment time requirement, the server candidate information “Candidate 2” is overwritten on the recommended patch final information.
  • the server candidate information "candidate 2" is selected as the recommended patch final information.
  • the server preparation unit 160 uses the server candidate information “candidate 2” as the server configuration information. And to the server reconfiguration unit 180.
  • the server preparation unit 160 prepares a server for providing service as well as server configuration information power.
  • the service providing start unit 170 starts providing the service using the service providing server. Also, when the server reconfiguring unit 180 receives the server configuration information, it creates minimum resource server information, and the minimum resource server information and the server configuration information are -Judge whether to match. In the requirement environment 2, the minimum resource server information does not match the server configuration information equal to the server candidate information “candidate 1”, so the minimum resource server information is transmitted to the server preparation unit 160. Then, the performance of the minimum resource server information is evaluated !, and the minimum resource server information is registered (added) in the master image information table 141 as master image information.
  • FIG. 14 shows a master image information table in which a new master image is created. It is.
  • the master image M3 is added to the master image information table 141.
  • a recommended patch is set in the patch field of the master image M3.
  • the server having the lowest performance among the performances that satisfy the required environment and its performance are set.
  • the server preparation unit 160 prepares a reconfiguration server using the minimum resource server information.
  • the service provision start unit 170 replaces the service provision server supplied to the client last time with the reconfiguration server.
  • requirement environment 3 the parameters other than the deployment time upper limit are the same, so the same application order list 211 as in requirement environment 1 is created.
  • the server candidate information “candidate 1” satisfies the performance “50” required in the required environment 3. Since the server candidate information “candidate 1” is the first candidate and there is no recommended patch final information, the server candidate information “candidate 1” is registered in the recommended patch final information.
  • server candidate information “candidate 2” is acquired.
  • the server candidate information “candidate 2” satisfies the performance “50” required in the required environment 2. Since the recommended patch final information already exists, it is determined whether or not the server candidate information “candidate 2” satisfies the deployment time requirement and is capable. Since the deployment time requirement is not satisfied, determine whether the recommended patch final information satisfies the deployment time requirement! Since the recommended patch final information does not satisfy the deployment time requirement, it is determined whether the deployment time can be shortened compared to the recommended patch final information. As a result, the server candidate information “Candidate 2” has a deployment time “15 minutes” shorter than the recommended patch final information deployment time “25 minutes”, so the server candidate information “Candidate 2” is overwritten to the recommended patch final information. I will.
  • the recommended patch final information does not satisfy the deployment time requirement, so the mandatory patch final information is created.
  • To create the mandatory patch final information first create an entry list of mandatory patch configuration.
  • FIG. 15 is a diagram showing an entry list of required patch configuration.
  • the field strength after application of the notch information table 151 is searched for a unit having a patch corresponding to the required patch “P2” of the required environment 3 as the condition 1.
  • a condition 2 a unit having an OS corresponding to the OS “01” in the required environment 1 is searched for the field strength before the master image information table 141 is applied.
  • Units U3 and U4 that satisfy condition 1 and units U1 to U6 that satisfy condition 2 are listed as search candidates, so units U3 and U4 that satisfy condition 1 and condition 2 are selected, and their entry information is stored in the server. It is set as entry information 223a of the entry list 223 of S1 and entry information 224a of the entry list 224 of server S2.
  • FIG. 16 is a diagram showing an application order list of essential patch configurations.
  • the application source unit column of unit U4 of entry information 224a is master unit M2
  • the application time "5 minutes" of patch P2 to server S2 is set in the application time column of entry information 224a And stored in the application order list 212 as server candidate information “candidate 4”.
  • the server selection unit 130 performs a server selection operation.
  • server candidate information “candidate 3” in the application order list 212 is extracted.
  • Server candidate information “Candidate 3” satisfies both performance requirements and deployment time requirements required for essential servers. Also, since there is no mandatory patch final information, server candidate information “Candidate 1” is registered as mandatory patch final information.
  • the server candidate information "candidate 4" contains the performance request and deployment time request required in the required environment 3. Both are satisfied and the server candidate information “Candidate 3” satisfies the deployment time requirement, but the value in the performance column is registered in the current mandatory patch final information and compared to the server candidate information “Candidate 3”. Large !, because it is (over-performance), the mandatory patch final information is not overwritten.
  • server candidate information "candidate 3" is selected as essential patch final information.
  • the server preparation unit 160 uses the server candidate information "Candidate 3" as server configuration information. And to the server reconfiguration unit 180.
  • the management server 100 applies patches P1 to the servers Sl and S2 to which patches are not applied according to the requested environment information (environment requests 1 to 3).
  • the server has the performance to satisfy the server preparation requirements, and it is determined whether it can be prepared within the deployment upper limit time, and ready servers are extracted. Therefore, it is possible to quickly and surely prepare a server (according to the client's request) that meets the required patch configuration, performance, and deployment time requirements, and to perform server management with high reliability.
  • the server replacement operation it is possible to supply a service providing server that meets the minimum request of the client, and then quickly supply a reconfiguration server that responds to the higher request of the client.
  • the reconfiguration server of the server preparation unit 160 Is preferably performed in parallel with the preparation of the service providing server. As a result, the reconfiguration server can be supplied more quickly.
  • the necessary information is captured separately from the notch information and the master image information, so the master image information is the minimum necessary even if the number of patch information increases. It can be limited.
  • the management server, the master image holding server, and the patch holding server are described as separate servers. In the present invention, the present invention is not limited to this.
  • the master image is held in the management server.
  • a function and a patch retention function are provided.
  • the server reconfiguration unit 180 is configured to replace the reconfiguration server even when the service providing server having the recommended patch configuration is supplied.
  • the present invention is not limited to this. If you provide a service providing server with the required patch configuration, V is configured to replace the reconfigurable server only!
  • two types of notches included in the required environment information are required patches and recommended patches.
  • the present invention is not limited to this, and there are three or more types of patches in the present invention. This can also be applied in the case of.
  • the server selection of the recommended patch configuration is performed first.
  • the server selection of the essential patch configuration may be performed first. In this case, the server can be supplied to the client in a shorter time.
  • the server selection unit 130 selects server candidates in consideration of these times.
  • the above processing functions can be realized by a computer (by causing the computer to execute a predetermined server management program).
  • a program describing the processing contents of the functions that the management server should have is provided.
  • the program describing the processing contents can be recorded on a computer-readable recording medium.
  • the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory.
  • the magnetic recording device include a hard disk device (HDD), a flexible disk (FD), and a magnetic tape.
  • optical disc examples include a DVD (Digital Versatile Disc), a DVD—RAM (Random Access Memory), a CD—ROM (Compact Disc Read Only Memory), and a CD-R (Recordable) / RW (Rewritable).
  • magneto-optical recording medium examples include MO (Magneto-Optical disk).
  • a portable recording medium such as a DVD or a CD-ROM in which the program is recorded is sold. It is also possible to store the program in a storage device of the server computer and transfer the program to other computers via the network.
  • the computer that executes the management server program stores, for example, the program recorded on the portable recording medium or the program to which the server computer power is also transferred in its own storage device. Then, the computer also reads the program with its own memory capacity and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, each time the server computer program is transferred, the computer can also execute processing according to the received program. [0156]
  • the above merely illustrates the principle of the present invention. In addition, many variations and modifications will be apparent to those skilled in the art, and the invention is not limited to the precise configuration and application shown and described above, but all corresponding variations and equivalents may be It is regarded as the scope of the present invention by the claims and their equivalents.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Debugging And Monitoring (AREA)

Abstract

La présente invention concerne un contrôleur de serveur capable de préparer un serveur de manière sûre et rapide et d'améliorer l'efficacité de fonctionnement des ressources du centre de données. Un moyen de mémoire des informations de correctif (2) stocke des informations sur le correctif. Un moyen d'extraction (3) possède des performances pour satisfaire la requête de préparation de serveur pour préparer, dans une limite supérieure de temps, un serveur auquel un type de correctif nécessaire est appliqué lorsque, en référence aux informations de correctif du moyen de mémoire des informations de correctif (2), les types de correctifs nécessaires sont appliqués aux serveurs en attente (6), (7) et (8) avec des performances respectives ; il juge si un serveur candidat est disponible dans une limite de temps supérieure pour la préparation. Enfin, il extrait un serveur candidat des serveurs en attente, disponibles pour la préparation. Un moyen de préparation de serveur (4) applique un correctif du type adapté à un serveur en attente correspondant au serveur candidat extrait par le moyen d'extraction (3) pour préparer un serveur de fourniture de service. Un moyen de départ de fourniture de service (5) lance un service de fourniture à l'aide du serveur fournissant le service et préparé par le moyen de préparation du serveur (4).
PCT/JP2006/303227 2006-02-23 2006-02-23 Programme et procede de controle de serveur et controleur de serveur WO2007096963A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2008501521A JP5035237B2 (ja) 2006-02-23 2006-02-23 サーバ管理プログラム、サーバ管理装置およびサーバ管理方法
PCT/JP2006/303227 WO2007096963A1 (fr) 2006-02-23 2006-02-23 Programme et procede de controle de serveur et controleur de serveur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2006/303227 WO2007096963A1 (fr) 2006-02-23 2006-02-23 Programme et procede de controle de serveur et controleur de serveur

Publications (1)

Publication Number Publication Date
WO2007096963A1 true WO2007096963A1 (fr) 2007-08-30

Family

ID=38437025

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2006/303227 WO2007096963A1 (fr) 2006-02-23 2006-02-23 Programme et procede de controle de serveur et controleur de serveur

Country Status (2)

Country Link
JP (1) JP5035237B2 (fr)
WO (1) WO2007096963A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014155693A1 (fr) * 2013-03-29 2014-10-02 株式会社日立製作所 Serveur de gestion d'image de machine virtuelle et procédé de gestion d'image de machine virtuelle
JP2019506682A (ja) * 2016-06-07 2019-03-07 株式会社日立製作所 アプリケーションの頻度及び変化量に基づいて適切なｉｔリソース上にアプリケーションを配備するための方法及び装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005099967A (ja) * 2003-09-24 2005-04-14 Hitachi Ltd 予防保守方法
JP2005250548A (ja) * 2004-03-01 2005-09-15 Fujitsu Ltd 中継制御方法、中継制御プログラム、および中継制御装置
JP2005275573A (ja) * 2004-03-23 2005-10-06 Fujitsu Ltd 最適保守日提案プログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005099967A (ja) * 2003-09-24 2005-04-14 Hitachi Ltd 予防保守方法
JP2005250548A (ja) * 2004-03-01 2005-09-15 Fujitsu Ltd 中継制御方法、中継制御プログラム、および中継制御装置
JP2005275573A (ja) * 2004-03-23 2005-10-06 Fujitsu Ltd 最適保守日提案プログラム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KOUDA K. ET AL.: "Shingyomu no Jinsoku na Kaishi to Kodo na Un'yo Jidoka o Jitsugen suru Middleware", HITACHI HYORON, vol. 86, no. 6, 1 June 2004 (2004-06-01), pages 35 - 38, XP003017216 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014155693A1 (fr) * 2013-03-29 2014-10-02 株式会社日立製作所 Serveur de gestion d'image de machine virtuelle et procédé de gestion d'image de machine virtuelle
JP5996094B2 (ja) * 2013-03-29 2016-09-21 株式会社日立製作所 仮想マシンイメージ管理サーバ、及び仮想マシンイメージ管理方法
JP2019506682A (ja) * 2016-06-07 2019-03-07 株式会社日立製作所 アプリケーションの頻度及び変化量に基づいて適切なｉｔリソース上にアプリケーションを配備するための方法及び装置

Also Published As

Publication number Publication date
JP5035237B2 (ja) 2012-09-26
JPWO2007096963A1 (ja) 2009-07-09

Similar Documents

Publication Publication Date Title
US7958210B2 (en) Update management method and update management unit
RU2429529C2 (ru) Динамическое конфигурирование, выделение и развертывание вычислительных систем
US9405630B2 (en) Methods and apparatus to perform site recovery of a virtual data center
JP4467624B2 (ja) ソフトウェアアップデート管理プログラム、ソフトウェアアップデート管理装置、およびソフトウェアアップデート管理方法
CN100485676C (zh) 文件系统串行化重新初始化装置、方法和系统
US10216514B2 (en) Identification of a component for upgrade
US20140376362A1 (en) Dynamic client fail-over during a rolling patch installation based on temporal server conditions
TWI511046B (zh) 用於群集軟體實體之動態命令列介面映射
US20080244552A1 (en) Upgrading services associated with high availability systems
CN104918114B (zh) 一种操作系统升级方法及装置
JP4141875B2 (ja) リカバリ処理方法及びその実施システム並びにその処理プログラム
CN104657158A (zh) 一种业务系统中业务处理的方法和装置
US20170371641A1 (en) Multi-tenant upgrading
JP4759941B2 (ja) 起動イメージ提供システム及び方法、ブートノード装置、ブートサーバ装置並びにプログラム
CN114385349A (zh) 容器组部署方法和装置
WO2016078326A1 (fr) Procédé, appareil, et système, d'affichage de noms de machine virtuelle
CN113468143A (zh) 数据迁移方法、系统、计算设备及存储介质
JP2008055849A (ja) 画像形成装置及びその管理方法
WO2018010603A1 (fr) Procédé, appareil et système de mise à niveau de mode de stockage basés sur un système de stockage de vidéo de type cloud
WO2007096963A1 (fr) Programme et procede de controle de serveur et controleur de serveur
CN111459530B (zh) 打补丁方法、装置和存储介质
CN106708541A (zh) 版本升级处理方法及装置
CN114205333B (zh) Ip配置方法、集群构建方法、计算机设备及存储介质
JP2006164095A (ja) ディスクシステム
CN114356357A (zh) 镜像文件处理方法、装置和电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase

Ref document number: 2008501521

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06714367

Country of ref document: EP

Kind code of ref document: A1