WO2013031999A1 - Extraction device, system, program, and method - Google Patents

Extraction device, system, program, and method Download PDF

Info

Publication number
WO2013031999A1
WO2013031999A1 PCT/JP2012/072284 JP2012072284W WO2013031999A1 WO 2013031999 A1 WO2013031999 A1 WO 2013031999A1 JP 2012072284 W JP2012072284 W JP 2012072284W WO 2013031999 A1 WO2013031999 A1 WO 2013031999A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
request
extraction
processing devices
amount
Prior art date
Application number
PCT/JP2012/072284
Other languages
French (fr)
Japanese (ja)
Inventor
繁 細野
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Publication of WO2013031999A1 publication Critical patent/WO2013031999A1/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]

Definitions

  • the present invention relates to an extraction apparatus, a system, a program, and a method.
  • Cloud providers and the like provide resources such as a CPU (Central Processing Unit) and memory to users who develop applications that are executed in a cloud environment.
  • resources such as a CPU (Central Processing Unit) and memory
  • CPU Central Processing Unit
  • cited document 1 discloses an example of a method for managing a plurality of computer resources and allocating requested computer resources to a user in response to a resource request for requesting allocation of computer resources.
  • cited document 2 discloses an example of a system that determines a combination of components from requirements with high importance based on a user request for system requirements.
  • cited document 3 discloses an example of a sizing support system that estimates hardware requirements when constructing an application system. JP2011-18198A JP 2009-105503 A JP 2011-060053 A
  • an object of the present invention is to provide an extraction device, system, program, and method that can appropriately extract processing devices and the like that have resources that satisfy the requirements in order to solve the above-described problems.
  • one aspect of the present invention is an extraction device that stores a request item, a resource condition including one or more resource types, and a request amount for each resource in association with each other.
  • Resource condition storage means for acquiring the amount of the resource of each of the plurality of processing devices for each type of the resource, and one or more processing devices that acquire the request item from the outside
  • the identification information of the one or more processing devices is obtained from the plurality of processing devices. Extracting means for extracting and outputting.
  • the present invention provides a computer including resource condition storage means for storing a request item, a resource condition including one or more resource types and a request amount for each resource, in association with each resource type.
  • resource status acquisition step for acquiring the amount of the resource held by each of the plurality of processing devices, and the request item is acquired from the outside, and the amount of the resource held by one or more of the processing devices is acquired. Extraction that extracts and outputs identification information of the one or more processing devices from the plurality of processing devices when the resource request amount for each resource type included in the resource condition corresponding to the request item is satisfied And an extraction program for executing the steps.
  • the present invention stores a request item, a resource condition including one or more resource types and a request amount for each resource in association with each other, and each of the plurality of processing devices for each resource type.
  • the resource holding amount is acquired, the request item is acquired from the outside, and the resource holding amount held by one or more of the processing devices includes the resource condition corresponding to the acquired request item
  • the present invention provides an extraction device, a system, a program, and a method that can appropriately extract a processing device or the like having a resource that satisfies a request.
  • each part which comprises the apparatus of each embodiment is comprised by hardware, such as a logic circuit.
  • Each unit includes a computer control unit, a memory, a program loaded in the memory, a storage unit such as a hard disk for storing the program, a network connection interface, and the like, and may be realized by any combination of hardware and software. Good. And unless there is particular notice, the realization method and apparatus are not limited.
  • the control unit is composed of a CPU (Central Processing Unit) or the like, and operates an OS (Operating System) to control the entire apparatus and the like.
  • FIG. 1 shows an extraction system 4 according to the present embodiment.
  • the extraction system 4 includes an extraction device 1, a resource management server 2, and a server group 3. An example of the extraction system 4 is shown in FIG.
  • the extraction device 1 and the resource management server 2 are connected by a communication line or the like.
  • the resource management server 2 and the server group 3 are connected by a communication line or the like.
  • the server group 3 includes a plurality of servers (information processing apparatuses), and each server includes resources such as a CPU, a memory, and a communication line.
  • the hardware included in each server has characteristics such as quantity and performance that affect the performance and reliability of the system using the server, and each characteristic is called a resource type.
  • the types of resources included in each server include CPU performance and network bandwidth.
  • the resource holding amount is defined corresponding to the resource type.
  • the resource holding amount is a numerical value indicating the degree to which the characteristic contributes to performance and reliability.
  • the amount of resources held by each server is not limited to the amount of physical resources held by each server, but includes the performance value of each server.
  • the resource holding amount is xMIPS (Million Instructions Per Second) for CPU performance, y for the number of CPU cores, zGbps (Gigabit per second) for the network bandwidth, and the like.
  • the extraction device 1 includes a request input unit 11, an extraction unit 12, a resource condition storage unit 13, a resource state acquisition unit 14, and a display unit 15.
  • the request input unit 11 is an input means for a user or the like to input a function request or a non-function request.
  • the user or the like may use the request input unit 11 to input a resource type or a resource request amount that the user or the like requests from the cloud environment system.
  • the resource type is a type for distinguishing resources, and is not limited to the amount of hardware such as the number of CPU cores as described above, but also includes performance such as CPU performance and network bandwidth.
  • the resource request amount is an amount by which a user or the like requests each resource type. For example, xMIPS (Million Instructions Per second) for CPU performance, y for the number of CPU cores, and zGbps (for network bandwidth). Gigabit per second).
  • the request input by the user or the like may include a request item and a request level.
  • the request item is a non-functional request item such as response time, operation time, reliability, and extensibility requested by the user or the like to the cloud environment system.
  • the request item may be a function request item such as hot standby or encryption.
  • the request level indicates whether a request from a user or the like is high or low for each request item. For example, if the request item is a response time, the request level is within 10 seconds, and the request item is an operation time. If so, the required level is, for example, an average failure time of 6 months. In some cases, the request does not include the request level and is only a request item.
  • a user or the like inputs a request via the request input unit 11.
  • the request input unit 11 outputs the input request to the extraction unit 12 described later.
  • the resource condition storage unit 13 stores the request and the resource condition in association with each other. As shown in FIG. 2, the resource condition is information in which one or more resource types are associated with a resource request amount for each resource type.
  • the resource condition for satisfying the request whose request item is the response time and the request level is within 10 seconds is the resource type and the resource request amount of the resource type.
  • Combination CPU performance is aMIPS, number of CPU cores is 1, network bandwidth is bGbps, HD (Hard Disc) rotation speed is crpm (revolution per minute / rotation per minute), maximum IO (Input / Output) waiting time is dmsec ( milli-second)).
  • the resource condition storage unit 13 stores, for example, a request (request item and its request level) and a resource condition (one or more resource types and its resource request amount) satisfying the request in association with each other. Yes.
  • the resource state acquisition unit 14 acquires a resource holding amount (resource holding amount) for each resource type (resource type) included in each of the plurality of servers.
  • the resource status acquisition unit 14 may acquire the resource holding amount of each of the plurality of servers from the resource status storage unit 22 described later, or may acquire from the server group 3 as shown in FIG. .
  • the extraction unit 12 extracts server identification information of one or more servers from the server.
  • the condition is that the resource holding amount for each resource type held by the one or more servers satisfies the resource request amount for each resource type included in the resource condition corresponding to the request input from the request input unit 11 ( It is simply referred to as a resource condition).
  • the extraction unit 12 may extract the server identification information from the resource state storage unit 22 instead of extracting the server identification information directly from the server. Further, the extraction unit 12 outputs the extracted server identification information. Although the output destination is not limited, for example, the extracting unit 12 may output the extracted server identification information to the display unit 15. In addition, when the above-described server does not exist, the extraction unit 12 may output to the display unit 15 that no server that satisfies the resource condition exists. In addition, the extraction unit 12 includes a plurality of servers in which a total amount of resource holding amounts for each resource type held by a plurality of servers satisfies a resource request amount for each resource type included in a resource condition corresponding to the input request.
  • the identification information may be extracted from the server group 3 and output.
  • the server identification information is A server
  • the server identification information is B server.
  • the extraction unit 12 may extract the server identification information A and B.
  • the extraction unit 12 extracts a plurality of servers in which the total amount of resources held by each server satisfies the resource condition, thereby constructing a cloud environment that cannot be realized by a single server. It becomes possible.
  • the extraction unit 12 receives the server identification information of one or more servers that satisfy all the resource conditions corresponding to each of the requests, the resource state storage unit 22, and the like. May be extracted from Specific examples will be described later.
  • the display unit 15 is a display unit such as a display that displays the server identification information acquired from the extraction unit 12. The user looks at the server identification information displayed on the display unit 15 or sees information indicating that there is no server that satisfies the resource condition, thereby determining whether there is a server that satisfies the user's request. I can grasp it.
  • the resource management server 2 includes a resource management unit 21 and a resource state storage unit 22.
  • the resource management unit 21 periodically obtains, from the server group 3, the identification information of the server that holds the currently available resource, the resource type of the resource held by each server, and the resource holding amount for each resource type. And stored in the resource state storage unit 22.
  • the server identification information, the resource type, and the resource holding amount of the server that holds the currently available resource, which is information acquired by the resource management unit 21, are also referred to as a resource state.
  • the resource management unit 21 may periodically acquire a resource state every predetermined time and store it in the resource state storage unit 22.
  • the resource state storage unit 22 stores the resource state acquired by the resource management unit 21.
  • FIG. 3 is an example of a resource state stored in the resource state storage unit 22. The top row of the table of FIG.
  • the server 3 indicates that there is a server whose server identification information is A in the server group 3 at a certain point in time.
  • the server A resource type and its resource holding amount are: CPU performance: eMIPS, number of CPU cores: 2, network bandwidth: fGbps, HD rotation speed: grpm, maximum IO wait time: hmsec, standby system 3 units, HDRAID 1 (Redundant Arrays of Independent Disks): 2 units.
  • the resource management server 2 may be managed by a cloud provider or the like different from the extraction device 1. In this case, there is an advantage that the person who operates the extraction apparatus 1 does not have to manage the server group 3 directly.
  • a cloud operator or the like that manages the resource management server 2 can appropriately correct the contents of the resource state acquired by the resource management unit 21 via a correction unit (not shown) provided in the management server 2. .
  • a cloud business operator or the like adds resources that are scheduled to become available soon (for example, resources that are scheduled to be purchased or that will end maintenance) to the resource state storage unit 22. May be.
  • the cloud service provider deletes resources that the user does not want to allocate from the resource state storage unit 22 because maintenance is required or the user does not want to share resources with other users. Also good.
  • movement of the extraction system 4 of this Embodiment is demonstrated. The operation of the resource management server 2 will be described. FIG.
  • the resource management unit 21 of the resource management server 2 periodically acquires from the server group 3 server identification information of servers that have resources available at that time, resource types of resources held by each server, and resource types. Each resource holding amount is acquired (step S1), and those resource states are stored in the resource state storage unit 22 (step S2). In addition, the cloud business operator etc. which manage the resource management server 2 may correct the content of the resource state which the resource management part 21 acquired suitably.
  • the operation of the extraction device 1 will be described. 5 and 6 show the operation of the extraction device 1. First, the request input unit 11 acquires a request from a user or the like (step S11).
  • the extraction unit 12 acquires a resource condition corresponding to the request input from the user or the like in step S11 from the resource condition storage unit 13 (step S12). For example, when a user or the like inputs a request that the response time is within 10 seconds, the extraction unit 12 refers to the resource condition storage unit 13 and extracts a resource condition corresponding to the request.
  • the resource conditions corresponding to the request are CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, and maximum IO waiting time: dmsec.
  • the extraction unit 12 searches the resource state storage unit 22 for the server identification information that satisfies the resource condition extracted in step S12.
  • step S13 If there is server identification information that satisfies the resource conditions, the server identification information is extracted and output. If there is no server identification information that satisfies the resource condition, a process of outputting that there is no server that satisfies the resource condition (server extraction process) is performed (step S13).
  • N (1 here) servers that satisfy the resource condition
  • the extraction unit 12 extracts the server identification information of such servers from the resource state storage unit 22 and outputs the extracted server identification information to the display unit 15 (step 15). S133).
  • N here, 1
  • the extraction unit 12 adds 1 to N (step S134).
  • N exceeds a predetermined value (step S135).
  • the predetermined value is, for example, a value designated in advance by a cloud operator or the like. If N does not exceed the predetermined value, the extraction unit 12 repeats step S132.
  • Step S132 it is determined by referring to the resource state acquired by the resource state acquisition unit 14 whether or not there are N servers that satisfy the resource condition (N is 1 in this case because N is added in step S134). That is, the extraction unit 12 makes the total amount of resources held for each resource type held by N (here 2) servers satisfy the resource request amount for each resource type corresponding to the input request. It is determined whether there are N (here, 2) servers. If there are N (here 2) servers that satisfy the resource condition, the extraction unit 12 extracts the server identification information of such servers from the server group 3 and the resource state storage unit 22 and displays them on the display unit 15 and the like. Output (step S133).
  • the extraction unit 12 adds 1 to N again (step S134), and determines whether N exceeds a predetermined value (step S134). S135). If N does not exceed the predetermined value, the extraction unit 12 performs Step S132 again. As described above, as long as N does not exceed the predetermined value, the extraction unit 12 repeats step S132, and when there are N servers that satisfy the resource condition, the value of N is sequentially increased by one in step S134. Repeat the process.
  • the extraction unit 12 determines that N exceeds a predetermined value in step S135, the extraction unit 12 outputs to the display unit 15 or the like that there is no server that satisfies the resource condition (step S136).
  • the extraction unit 12 receives the server identification information of one or more servers that satisfy all the resource conditions corresponding to each of the requests, the resource state storage unit 22, and the like. May be extracted from A specific example will be described with reference to FIG. For example, when a response time: within 10 seconds and an operation time: an average failure time of 6 months are input as requests, the extraction unit 12 determines the CPU performance as a resource condition corresponding to the request with a response time: within 10 seconds.
  • the extraction unit 12 extracts one or more HDRAID 1: 1, which is a resource condition corresponding to a request of operating time: average failure time of 6 months. Then, the extraction unit 12 extracts server identification information of one or more servers that satisfy all of the extracted resource conditions from the resource state storage unit 22 and the like. As described above, the extraction unit 12 regards a condition obtained by combining resource conditions corresponding to each of a plurality of requests as a new resource condition. Whether or not there is a server that satisfies the new resource condition may be extracted according to the operations shown in FIGS.
  • the extraction unit 12 is a resource condition corresponding to the request with a response time: within 10 seconds.
  • CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: crpm, maximum IO waiting time: dmsec are extracted.
  • the extraction unit 12 extracts one standby system that is a resource condition corresponding to a request of operating time: average failure time of 10 months.
  • the extraction unit 12 displays the server identification information of the server that satisfies all the resource conditions excluding the “standby system” condition as “standby system”.
  • An extra amount is extracted from the resource state storage unit 22 and the like by the required resource amount required for the “system”. That is, in this example, the extraction unit 12 selects one or more servers that satisfy CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, and maximum IO waiting time: dmsec. Only one resource, which is the required resource amount required for the “standby system”, is extracted from the resource state storage unit 22 and the like. That is, two sets of server identification information of one or more servers satisfying CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, and maximum IO waiting time: dmsec are extracted.
  • the extraction unit 12 may perform a process (server extraction process) for directly searching the server group 3 as to whether or not the server group 3 includes a server that satisfies the resource condition extracted in step S12. In this process, if a server that satisfies the resource condition exists in the server group 3, the server identification information is extracted and output. If there is no server identification information that satisfies the resource condition, a message that no server satisfies the resource condition is output.
  • the extraction unit 12 can extract identification information of a plurality of servers in which the total amount of resources held satisfies the resource request amount corresponding to the input request.
  • the resource condition storage unit 13 associates a plurality of resource conditions including a plurality of resource types and a request amount of each resource of the plurality of resources with respect to the same request. Storing.
  • the second embodiment is different from the first embodiment in that a plurality of resource conditions that satisfy the same request are stored.
  • each resource condition is set as an alternative condition that satisfies the same request. For example, among a plurality of resource conditions corresponding to a certain request, the resource type included in one resource condition is the same as the resource type included in another resource condition, and the resource request amount corresponding to the resource type is different.
  • the CPU performance included in a certain resource condition is 1000 MIPS
  • the network bandwidth is 1 Gbps
  • the CPU performance included in other resource conditions is 50 MIPS
  • the network bandwidth is 20 Gbps.
  • communication data compression can be simplified when the CPU performance is low, for example.
  • the CPU resource request amount is small instead of the CPU resource request amount, and in other resource conditions, the CPU resource request amount is small but the memory resource request amount is large. .
  • each resource condition is set as an alternative condition that satisfies the same request.
  • a plurality of resource conditions including different resource types may exist for the same request.
  • the extraction unit 12 includes identification information of one or more servers that satisfy any of the resource conditions stored in the resource condition storage unit 13 and corresponding to the request input from the user or the like. Extract and output.
  • the resource condition storage unit 13 may store a resource condition and a priority order in association with each resource condition.
  • the extraction part 12 may extract and output the identification information of one or more servers which satisfy
  • the priority order may be preset by, for example, a cloud operator.
  • the request input unit 11 acquires a request from a user or the like (step S21).
  • the extraction unit 12 acquires a resource condition corresponding to the request input from the user or the like in step S21 from the resource condition storage unit 13 (step S22). For example, when the user or the like inputs a request that the response time is within 10 seconds, the extraction unit 12 refers to the resource condition storage unit 13 and, as shown in FIG. CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, maximum IO waiting time: dmsec are extracted.
  • the extraction unit 12 since a plurality of resource conditions satisfying the same request are stored in the resource condition storage unit 13, the extraction unit 12 satisfies the same request stored in the resource condition storage unit 13. Extract all resource conditions. This point is different from the first embodiment.
  • the server extraction process in step S24 is the same as the server extraction process of FIG.
  • the extraction unit 12 determines whether or not server identification information satisfying the resource condition of the priority K (here, 1) is obtained as a result of the server extraction process (step S25).
  • the extraction unit 12 displays the identification information of the server in the resource state storage unit 22 (resource The resource state acquired by the resource state acquisition unit 14 from the state storage unit 22 is extracted and output to the display unit 15 or the like.
  • the extraction unit 12 adds 1 to K (step S27).
  • the extraction unit 12 determines whether or not K exceeds a predetermined value (step S28).
  • the predetermined value is, for example, a value designated in advance by a cloud operator or the like.
  • step S28 When K does not exceed the predetermined value (step S28, Yes), the extraction unit 12 performs step S24 again. As described above, when the identification information of the server with the Kth priority cannot be extracted, the extraction unit 12 repeats Step S24, Step S25, and Step S27 until K exceeds a predetermined value. On the other hand, if K exceeds a predetermined value (step S28, No), the extraction unit 12 outputs to the display unit 15 or the like that there is no server that satisfies the resource condition (step S29). As a result of the above processing, the extraction device 1 is the server that satisfies the resource condition of the Kth priority, and the identification information of the N servers whose total resource holding amount for each resource type satisfies the resource request amount is the resource.
  • K which is a priority number associated with a resource condition
  • N the number N of servers satisfying the Kth resource condition
  • the extraction unit 12 first searches whether there is one server that satisfies the first priority resource condition. When one server does not exist, the extraction unit 12 searches whether there are two servers that satisfy the first resource condition of the priority order. When there are no two servers, the extraction unit 12 increases the number N of servers sequentially in the same manner, and determines whether or not there are N servers that satisfy the first priority resource condition. Search for.
  • the extraction unit 12 When N exceeds a predetermined value, the extraction unit 12 next increases the priority by 1 and searches whether there is a server that satisfies the second priority resource condition. In the same manner, first, the value of K is determined while sequentially increasing the priority K, and whether or not there are N servers satisfying the Kth resource priority is determined by sequentially increasing N. Search for.
  • This method emphasizes the construction of a cloud environment by extracting servers that satisfy the higher priority resource conditions rather than emphasizing the construction of a cloud environment with a small number of servers. It is a method to do.
  • the extraction device 1 may first determine the number N of servers, and then sequentially increase the priority number K.
  • the extraction unit 12 first searches whether there is a server that satisfies the first resource condition with the number of servers being one. If there is no server, the extraction unit 12 searches for a set of servers that satisfy the second priority resource condition with one server. If there is no such server, the extraction unit 12 increases the priority number K sequentially in the same manner, and determines whether there is one server that satisfies the Kth resource condition. Search for no. When K exceeds a predetermined value, the extraction unit 12 then increases the number of servers by 1, and whether there is a server that satisfies the first resource condition with the number of servers being 2 and the first priority. Search for.
  • the extracting unit 12 determines the value of N while sequentially increasing the number N of servers, and then sequentially increases the priority number K to satisfy the resource condition of the Kth priority. Search whether a server exists. This method focuses on building a cloud environment with a small number of servers, rather than focusing on building a cloud environment by extracting servers that satisfy the higher priority resource conditions when building a cloud environment. It is a method to do.
  • the resource condition storage unit 13 stores a plurality of resource conditions in association with the same request. Therefore, the extraction unit 12 can extract and output identification information of one or more servers that satisfy any of a plurality of resource conditions corresponding to the input request.
  • FIG. 10 shows an example of the configuration of the extraction device 1 according to the present embodiment.
  • the extraction device 1 includes a resource condition storage unit 13, a resource state acquisition unit 14, and an extraction unit 12.
  • the resource condition storage unit 13 stores a request and a resource condition including the resource type and the requested amount of the resource in association with each other.
  • the resource status acquisition unit 14 acquires the resource holding amount of each of the plurality of information processing apparatuses for each resource type.
  • the extraction unit 12 satisfies the resource request amount for each resource type stored in the resource condition storage unit 13 corresponding to the input request, with the resource holding amount for each resource type held by one or more information processing apparatuses.
  • the identification information of the one or more information processing devices is extracted from a plurality of information processing devices and output.
  • the extraction unit 12 may extract the identification information directly from the information processing apparatus (server group 3) (see FIG. 9) or may be extracted from the resource management server 2 (see FIG. 1).
  • an extraction device, a system, a program, and a method that can extract an information processing device that has a resource that satisfies a request are provided.
  • This application claims the priority on the basis of Japanese application Japanese Patent Application No. 2011-191897 for which it applied on September 2, 2011, and takes in those the indications of all here.
  • the extraction unit 12 may extract not only a server but also other devices such as a disk device.

Landscapes

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

Abstract

[Problem] To appropriately extract a processing device holding resources fulfilling requirements. [Solution] An extraction device, comprising: a resource conditions storage means that associates and stores requirement items and resource conditions including at least one resource type and the requirement amount for each resource; a resource status acquisition means that obtains the amount of each resource held in a plurality of processing devices, for each resource type; and an extraction means that obtains the requirement items from outside, and, if the resource holding for each resource type held by at least one said processing device meets the resource requirement amount for each resource type included in the resource conditions associated with the obtained requirements, extracts identification information for the at least one processing device from a plurality of processing devices and outputs same.

Description

抽出装置、システム、プログラム、及び、方法Extraction apparatus, system, program, and method
 本発明は抽出装置、システム、プログラム、及び、方法に関する。 The present invention relates to an extraction apparatus, a system, a program, and a method.
 クラウド事業者等は、CPU(Central Processing Unit)やメモリなどのリソースを、クラウド環境で実行するアプリケーション等の開発を行なうユーザ等に提供している。
 しかし、クラウド事業者等が、ユーザの要求に合致するように、ユーザに対してリソースを割り当てるのは必ずしも容易ではない。その理由は、クラウド環境運用中には、同じリソースを複数のアプリーションで共有したり、時間とともに利用可能なリソースが変動したりするため、クラウド事業者等は、リソースの状況に応じてユーザに適切にリソースを割り当てるようにしなければならないためである。
 この課題に対し、引用文献1には、複数の計算機リソースを管理し、計算機リソースの割り当てを要求するリソース要求に応じて、要求された計算機リソースをユーザに割り当てる方法の一例が開示されている。また、引用文献2には、システム要件についての利用者の要求に基づいてコンポーネントの組み合わせを重要度の高い要件から決定するシステムの一例が開示されている。また、引用文献3には、アプリケーションシステムの構築を行なう際に、ハードウェア要件を見積もるサイジング支援システムの一例が開示されている。
特開2011−18198号公報 特開2009−105503号公報 特開2011−060053号公報
Cloud providers and the like provide resources such as a CPU (Central Processing Unit) and memory to users who develop applications that are executed in a cloud environment.
However, it is not always easy for a cloud business operator or the like to allocate resources to a user so as to match the user's request. The reason for this is that while operating the cloud environment, the same resource is shared by multiple applications, and the resources that can be used change over time. This is because resources must be allocated appropriately.
In response to this problem, cited document 1 discloses an example of a method for managing a plurality of computer resources and allocating requested computer resources to a user in response to a resource request for requesting allocation of computer resources. Also, cited document 2 discloses an example of a system that determines a combination of components from requirements with high importance based on a user request for system requirements. Also, cited document 3 discloses an example of a sizing support system that estimates hardware requirements when constructing an application system.
JP2011-18198A JP 2009-105503 A JP 2011-060053 A
 しかし、上述の技術では、複数の処理装置の中から、ユーザの要求を満たすリソースを保有する処理装置等を適切に抽出することは困難であるという問題があった。
 そこで、本発明は上記課題を解決すべく、要求を満たすリソースを保有する処理装置等を適切に抽出できる抽出装置、システム、プログラム、及び、方法を提供することを目的とする。
However, the above-described technique has a problem that it is difficult to appropriately extract a processing device or the like having resources that satisfy a user's request from a plurality of processing devices.
Therefore, an object of the present invention is to provide an extraction device, system, program, and method that can appropriately extract processing devices and the like that have resources that satisfy the requirements in order to solve the above-described problems.
 かかる目的を達成するため、本発明の一形態は、抽出装置であって、要求項目と、1以上のリソースの種別と当該リソースごとの要求量とを含むリソース条件と、を対応付けて格納するリソース条件格納手段と、前記リソースの種別ごとに、複数の処理装置の各々の前記リソースの保有量を取得するリソース状態取得手段と、外部から前記要求項目を取得し、1台以上の前記処理装置が保有するリソースの保有量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース要求量を満たす場合に、当該1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する抽出手段と、を備える。
 また、本発明は、要求項目と、1以上のリソースの種別と当該リソースごとの要求量とを含むリソース条件と、を対応付けて格納するリソース条件格納手段を備えるコンピュータに、前記リソースの種別ごとに、複数の処理装置の各々の前記リソースの保有量を取得するリソース状態取得ステップと、外部から前記要求項目を取得し、1台以上の前記処理装置が保有するリソースの保有量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす場合に、当該1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する抽出ステップと、を実行させる抽出プログラムを提供する。
 また、本発明は、要求項目と、1以上のリソースの種別と当該リソースごとの要求量とを含むリソース条件と、を対応付けて格納し、前記リソースの種別ごとに、複数の処理装置の各々の前記リソースの保有量を取得し、外部から前記要求項目を取得し、1台以上の前記処理装置が保有するリソースの保有量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす場合に、当該1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する抽出方法を提供する。
In order to achieve such an object, one aspect of the present invention is an extraction device that stores a request item, a resource condition including one or more resource types, and a request amount for each resource in association with each other. Resource condition storage means, resource status acquisition means for acquiring the amount of the resource of each of the plurality of processing devices for each type of the resource, and one or more processing devices that acquire the request item from the outside When the amount of resources held by the resource satisfies the resource request amount included in the resource condition corresponding to the acquired request item, the identification information of the one or more processing devices is obtained from the plurality of processing devices. Extracting means for extracting and outputting.
Further, the present invention provides a computer including resource condition storage means for storing a request item, a resource condition including one or more resource types and a request amount for each resource, in association with each resource type. In addition, a resource status acquisition step for acquiring the amount of the resource held by each of the plurality of processing devices, and the request item is acquired from the outside, and the amount of the resource held by one or more of the processing devices is acquired. Extraction that extracts and outputs identification information of the one or more processing devices from the plurality of processing devices when the resource request amount for each resource type included in the resource condition corresponding to the request item is satisfied And an extraction program for executing the steps.
Further, the present invention stores a request item, a resource condition including one or more resource types and a request amount for each resource in association with each other, and each of the plurality of processing devices for each resource type. The resource holding amount is acquired, the request item is acquired from the outside, and the resource holding amount held by one or more of the processing devices includes the resource condition corresponding to the acquired request item Provided is an extraction method for extracting the identification information of the one or more processing devices from the plurality of processing devices when the resource requirement amount for each type is satisfied.
 本発明は、要求を満たすリソースを保有する処理装置等を適切に抽出できる抽出装置、システム、プログラム、及び、方法を提供する。 The present invention provides an extraction device, a system, a program, and a method that can appropriately extract a processing device or the like having a resource that satisfies a request.
第1の実施形態の構成の一例を示す図である。It is a figure which shows an example of a structure of 1st Embodiment. 第1の実施形態のリソース条件格納部の一例を示す図である。It is a figure which shows an example of the resource condition storage part of 1st Embodiment. 第1の実施形態のリソース状態格納部の一例を示す図である。It is a figure which shows an example of the resource state storage part of 1st Embodiment. リソース管理サーバの動作の一例を示す図である。It is a figure which shows an example of operation | movement of a resource management server. 抽出装置の動作の一例を示す図である。It is a figure which shows an example of operation | movement of an extracting device. 抽出装置の動作の一例を示す図である。It is a figure which shows an example of operation | movement of an extracting device. 第2の実施形態のリソース条件格納部の一例を示す図である。It is a figure which shows an example of the resource condition storage part of 2nd Embodiment. 第2の実施形態の抽出装置の動作の一例を示す図である。It is a figure which shows an example of operation | movement of the extraction apparatus of 2nd Embodiment. 抽出装置の構成の一例を示す図である。It is a figure which shows an example of a structure of an extraction apparatus. 第3の実施の形態の抽出装置の構成の一例を示す図である。It is a figure which shows an example of a structure of the extraction apparatus of 3rd Embodiment.
 以下、本発明の実施の形態について、図面を用いて説明する。すべての図面において、同様な構成要素には同様の符号を付し、適宜説明を省略する。
 なお、各実施形態の装置等を構成する各部は、論理回路等のハードウェアで構成される。また、各部は、コンピュータの制御部、メモリ、メモリにロードされたプログラム、プログラムを格納するハードディスク等の記憶ユニット、ネットワーク接続用インターフェースなどからなり、ハードウェアとソフトウェアの任意の組合せによって実現されてもよい。そして特に断りのない限り、その実現方法、装置は限定されない。
 また、制御部はCPU(Central Processing Unit)などからなり、OS(Operating system)を動作させて装置等の全体を制御するとともに、例えばドライブ装置などに装着された記録媒体からメモリにプログラムやデータを読み出し、これに従って各種の処理を実行する。記録媒体は、例えば光ディスク、フレキシブルディスク、磁気光ディスク、外付けハードディスク、半導体メモリ等であって、コンピュータプログラムをコンピュータが読み取り可能に記録する。また、コンピュータプログラムは、通信網に接続されている図示しない外部コンピュータからダウンロードされても良い。
 <実施形態1>
 次に、本発明の第1の実施形態について図面を用いて説明する。図1には、本実施の形態にかかる抽出システム4が示されている。
 抽出システム4は、抽出装置1と、リソース管理サーバ2と、サーバ群3とを含む。図1には、抽出システム4の一例が示されている。抽出装置1とリソース管理サーバ2とは通信回線等で接続されている。リソース管理サーバ2とサーバ群3とは通信回線等で接続されている。
 サーバ群3は、複数台のサーバ(情報処理装置)を含み、各サーバはCPUやメモリ、通信回線などのリソースを備えている。各サーバが備えるハードウェアは、サーバを用いたシステムの性能や信頼性等に影響を与える量や性能等の特性があり、各々の特性をリソース種別と言う。各サーバの備えるリソースの種別は、CPU性能やネットワーク帯域などがある。また、リソース種別対応に、リソース保有量が定義される。リソース保有量は、その特性が性能や信頼性に貢献する度合いを示した数値である。すなわち、各サーバの保有するリソースの保有量とは、各サーバの保有する物理的な資源量に限られるものではなく、各サーバの備える性能値も含む。例えば、リソース保有量とは、CPU性能であればxMIPS(Million Instructions Per Second)、CPUコア数であればy個、ネットワーク帯域であればzGbps(Gigabit per second)などである。
 抽出装置1は、要求入力部11と、抽出部12と、リソース条件格納部13と、リソース状態取得部14と、表示部15とを含む。
 要求入力部11は、ユーザ等が機能要求や非機能要求等を入力する入力手段である。ユーザ等は、要求入力部11を用いて、ユーザ等がクラウド環境システムに要求するリソース種別やリソース要求量などを入力しても良い。
 ここで、リソース種別とは、リソースを区別する種類であり、上述のようにCPUコア数などのハードウェア量に限られるものではなく、CPU性能やネットワーク帯域などの性能も含む。リソース要求量とは、ユーザ等が各リソース種別を要求する量であり、例えば、CPU性能であればxMIPS(Million Instructions Per second)、CPUコア数であればy個、ネットワーク帯域であればzGbps(Gigabit per second)などである。
 ユーザ等が入力する要求は、要求項目と、要求レベルとを含んでいても良い。要求項目とは、ユーザ等がクラウド環境システムに要求する応答時間や稼働時間、信頼性、拡張性などの非機能要求の項目である。要求項目は、ホットスタンバイ、暗号化等の機能要求の項目でも良い。要求レベルとは、各要求項目に対して、ユーザ等の要求が高いか低いかを示すものであり、例えば、要求項目が応答時間であれば、要求レベルは10秒以内、要求項目が稼働時間であれば、要求レベルは平均故障時間6ヶ月などである。なお、要求が、要求レベルを包含せず、要求項目だけである場合もある。
 ユーザ等は、要求入力部11を介して、要求を入力する。要求入力部11は、入力された要求を後述の抽出部12へ出力する。
 リソース条件格納部13は、図2に示すように、要求とリソース条件とを対応付けて記憶する。リソース条件とは、図2に示すように、1以上のリソース種別と、リソース種別ごとのリソース要求量と、を対応付けた情報である。
 図2のテーブルの最上段には、要求項目が応答時間であり、要求レベルが10秒以内であるような要求を満たすためのリソース条件が、リソース種別と、そのリソース種別のリソース要求量との組み合わせ(CPU性能はaMIPS、CPUコア数は1個、ネットワーク帯域はbGbps、HD(Hard Disc)回転速度はcrpm(revolution per minute/rotation per minute)、最大IO(Input/Output)待ち時間はdmsec(milli−second))として格納されている。このように、リソース条件格納部13は、例えば、要求(要求項目とその要求レベル)と、該要求を満たすリソース条件(1以上のリソース種別とそのリソース要求量)とを対応付けて格納している。
 リソース状態取得部14は、複数のサーバの各々が備えるリソースの種別(リソース種別)ごとにリソースの保有量(リソース保有量)を取得する。リソース状態取得部14は、複数のサーバの各々のリソースの保有量を、後述のリソース状態格納部22から取得しても良いし、図9に示すように、サーバ群3から取得しても良い。
 抽出部12は、条件が満たされた場合に、1台以上のサーバのサーバ識別情報を当該サーバから抽出する。その条件とは、当該1台以上のサーバが保有するリソース種別ごとのリソース保有量が、要求入力部11から入力された要求と対応する、リソース条件が含むリソース種別ごとのリソース要求量を満たす(単に、リソース条件を満たすともいう)ことである。後述するように、抽出部12は、サーバ識別情報をサーバから直接抽出するのではなく、リソース状態格納部22から抽出しても良い。
 また、抽出部12は、抽出したサーバ識別情報を出力する。出力先は限定されないが、例えば、抽出部12は、抽出したサーバ識別情報を表示部15に出力しても良い。また、抽出部12は、上述のサーバが存在しない場合には、リソース条件を満たすサーバは存在しない旨の出力を表示部15にしても良い。
 また、抽出部12は、複数台のサーバが保有するリソース種別ごとのリソース保有量の合計量が、入力された要求と対応するリソース条件が含むリソース種別ごとのリソース要求量を満たす複数台のサーバの識別情報を、サーバ群3から抽出して出力しても良い。例えば、ユーザが入力した要求に対応するリソース条件の1つとして、リソース種別がCPU性能で、リソース要求量が100MIPSである場合、サーバ識別情報がAのサーバと、サーバ識別情報がBのサーバとのCPU性能が合計して100MIPS以上である場合には、抽出部12は、サーバ識別情報AとBを抽出しても良い。
 このように、各サーバの保有するリソース保有量の合計量がリソース条件を満たすようなサーバを、抽出部12が複数台抽出することにより、1台のサーバでは実現できないようなクラウド環境も構築することが可能となる。
 なお、抽出部12は、複数の要求が要求入力部11から入力されたとき、それら各々の要求に対応するリソース条件を全て満たす1台以上のサーバのサーバ識別情報を、リソース状態格納部22等から抽出しても良い。具体例は後述する。
 表示部15は、抽出部12から取得したサーバ識別情報を表示するディスプレイなどの表示手段である。ユーザは、表示部15に表示されたサーバ識別情報を見たり、あるいは、リソース条件を満たすサーバが存在しない旨の情報を見たりすることで、自己の要求を満たすサーバが存在するか否かを把握することができる。
 リソース管理サーバ2は、リソース管理部21とリソース状態格納部22とを含む。
 リソース管理部21は、サーバ群3から、現在利用可能なリソースを保有するサーバの識別情報と、該各サーバの保有するリソースのリソース種別と、該リソース種別ごとのリソース保有量と、を定期的に取得してリソース状態格納部22に保管する。リソース管理部21が取得した情報である、現在利用可能なリソースを保有するサーバのサーバ識別情報、リソース種別、リソース保有量をリソース状態ともいう。リソース管理部21は、例えば、予め指定された時間ごとに定期的にリソース状態を取得してリソース状態格納部22へ格納しても良い。
 リソース状態格納部22は、リソース管理部21が取得したリソース状態を格納する。図3は、リソース状態格納部22が格納するリソース状態の例である。図3のテーブルの最上段は、ある時点でサーバ群3には、サーバ識別情報がAであるサーバが存在することを示している。サーバAのリソース種別とそのリソース保有量はそれぞれ、CPU性能:eMIPS、CPUコア数:2個、ネットワーク帯域:fGbps、HD回転速度:grpm、最大IO待ち時間:hmsec、待機系システム3台、HDRAID 1(Redundant Arrays of Independent Disks):2台である。
 リソース管理サーバ2は抽出装置1とは別のクラウド事業者等が管理しても良い。この場合、抽出装置1を運用する者は、サーバ群3の管理を直接しないで済むという利点がある。また、リソース管理サーバ2を管理するクラウド事業者等は、管理サーバ2が備える修正部(不図示)を介して、リソース管理部21が取得したリソース状態の内容を適宜修正することが可能である。例えば、現在利用可能なリソースの他に、近々利用可能となる予定のリソース(例えば、購入予定がある、あるいは、メンテナンスが終了するリソースなど)をクラウド事業者等がリソース状態格納部22に追加しても良い。逆に、クラウド事業者等は、メンテナンス等が必要なために、あるいは、他の利用者とリソース共有したくないため等に、ユーザ等に割り当てたくないリソースをリソース状態格納部22から削除しても良い。
 次に、本実施の形態の抽出システム4の動作について説明する。
 リソース管理サーバ2の動作について説明する。図4には、リソース管理サーバ2の動作が示されている。リソース管理サーバ2のリソース管理部21は、サーバ群3から、定期的に、その時点において利用可能なリソースを保有するサーバのサーバ識別情報と、各サーバの保有するリソースのリソース種別と、リソース種別ごとのリソース保有量とを取得し(ステップS1)、リソース状態格納部22にそれらのリソース状態を保管する(ステップS2)。なお、リソース管理サーバ2を管理するクラウド事業者等が、リソース管理部21が取得したリソース状態の内容を適宜修正しても良い。
 抽出装置1の動作について説明する。図5、図6には、抽出装置1の動作が示されている。
 まず、要求入力部11は、ユーザ等から要求を取得する(ステップS11)。次に、抽出部12は、ステップS11でユーザ等から入力された要求に対応するリソース条件をリソース条件格納部13から取得する(ステップS12)。例えば、ユーザ等が、応答時間が10秒以内であるとの要求を入力した場合、抽出部12は、リソース条件格納部13を参照して、該要求に対応するリソース条件を抽出する。この場合、図2に示すように、該要求に対応するリソース条件は、CPU性能:aMIPS、CPUコア数:1個、ネットワーク帯域:bGbps、HD回転速度:crpm、最大IO待ち時間:dmsecである。
 次に、抽出部12は、ステップS12で抽出したリソース条件を満たすサーバの識別情報がリソース状態格納部22に存在するかどうかを検索する。リソース条件を満たすサーバの識別情報が存在する場合には該サーバの識別情報を抽出して出力する。リソース条件を満たすサーバの識別情報が存在しない場合には、リソース条件を満たすサーバが存在しない旨を出力する処理(サーバの抽出処理)を行う(ステップS13)。
 ステップS13のサーバの抽出処理について、詳細な動作を図6を用いて説明する。
 まず、抽出部12は、N=1とする(ステップS131)。続いて、抽出したリソース条件のリソース種別ごとのリソース保有量が、ステップS12で抽出したリソース条件を満たすようなN(ここでは1)台のサーバの識別情報がリソース状態格納部22に存在するか否かを、判定する(ステップS132)。この判定は、リソース状態取得部14がリソース状態格納部22から取得したリソース状態を参照して行われる。
 リソース条件を満たすN(ここでは1)台のサーバが存在すれば、抽出部12は、そのようなサーバのサーバ識別情報をリソース状態格納部22から抽出して表示部15等に出力する(ステップS133)。
 一方、リソース条件を満たすN(ここでは1)台のサーバが存在しない場合、抽出部12は、Nに1を加える(ステップS134)。また、Nが所定値を超えたか否かを判定する(ステップS135)。所定値は、例えば、クラウド事業者等によって予め指定された値である。
 Nが所定値を越えていない場合、抽出部12は、ステップS132を繰り返す。すなわち、リソース条件を満たすN(ステップS134でNに1を加えたため、ここではN=2)台のサーバが存在するか否かを、リソース状態取得部14が取得したリソース状態を参照して判定する(ステップS132)。すなわち、抽出部12は、N(ここでは2)台のサーバが保有するリソース種別ごとのリソースの保有量の合計量が、入力された要求と対応する、リソース種別ごとのリソース要求量を満たすような、N(ここでは2)台のサーバが存在するか否かを判定する。
 リソース条件を満たすN(ここでは2)台のサーバが存在すれば、抽出部12は、そのようなサーバのサーバ識別情報をサーバ群3やリソース状態格納部22から抽出して表示部15等に出力する(ステップS133)。
 一方、リソース条件を満たすN(ここでは2)台のサーバが存在しない場合、抽出部12は、再びNに1を加え(ステップS134)、Nが所定値を超えたか否かを判定する(ステップS135)。Nが所定値を越えていない場合、抽出部12は、ステップS132を再び行なう。このように、Nが所定値を超えない限り、抽出部12は、ステップS132を繰り返し、リソース条件を満たすN台のサーバが存在しない場合には、Nの値を順次1ずつ増加させるステップS134の処理を繰り返す。
 一方、ステップS135にてNが所定値を越えたと抽出部12が判定した場合、抽出部12は、リソース条件を満たすサーバが存在しない旨を表示部15等に出力する(ステップS136)。
 なお、抽出部12は、複数の要求が要求入力部11から入力されたとき、それら各々の要求に対応するリソース条件を全て満たす1台以上のサーバのサーバ識別情報を、リソース状態格納部22等から抽出しても良い。図2を用いて具体例を説明する。例えば、要求として、応答時間:10秒以内と、稼働時間:平均故障時間6ヶ月とが入力された場合、抽出部12は、応答時間:10秒以内という要求に対応するリソース条件であるCPU性能:aMIPS、CPUコア数:1個、ネットワーク帯域:bGbps、HD回転速度:crpm、最大IO待ち時間:dmsecを抽出する。また、抽出部12は、稼働時間:平均故障時間6ヶ月という要求に対応するリソース条件であるHDRAID1:1台以上を抽出する。そして、抽出部12は、抽出したこれらのリソース条件を全て満たす1台以上のサーバのサーバ識別情報を、リソース状態格納部22等から抽出する。このように、抽出部12は、複数の要求の各々に対応するリソース条件を結合した条件を新たなリソース条件とみなす。その新たなリソース条件を満たすサーバが存在するか否かを、上述した図5、6に示した動作に従って抽出しても良い。
 また、例えば、要求として、応答時間:10秒以内と、稼働時間:平均故障時間10ヶ月とが入力された場合、抽出部12は、応答時間:10秒以内という要求に対応するリソース条件であるCPU性能:aMIPS、CPUコア数:1個、ネットワーク帯域:bGbps、HD回転速度:crpm、最大IO待ち時間:dmsecを抽出する。また、抽出部12は、稼働時間:平均故障時間10ヶ月という要求に対応するリソース条件である待機系システム:1台を抽出する。ここで、抽出部12は、抽出したリソース条件の中に「待機系システム」を含む場合には、「待機系システム」の条件を除いたリソース条件を全て満たすサーバのサーバ識別情報を、「待機系システム」に要求されるリソース要求量分だけ余分にリソース状態格納部22等から抽出する。すなわち、この例においては、抽出部12は、CPU性能:aMIPS、CPUコア数:1個、ネットワーク帯域:bGbps、HD回転速度:crpm、最大IO待ち時間:dmsecを満たす1台以上のサーバを「待機系システム」に要求されるリソース要求量である1台分だけ余分にリソース状態格納部22等から抽出する。すなわち、CPU性能:aMIPS、CPUコア数:1個、ネットワーク帯域:bGbps、HD回転速度:crpm、最大IO待ち時間:dmsecを満たす1台以上のサーバのサーバ識別情報が2セット抽出される。
 上述の説明では、リソース管理サーバ2が存在することを前提に説明をした。リソース管理サーバ2が存在しない場合には、以下のようにしても良い。すなわち、抽出部12は、ステップS12で抽出したリソース条件を満たすサーバがサーバ群3に存在するか否かをサーバ群3から直接検索する処理(サーバの抽出処理)を行っても良い。この処理においては、リソース条件を満たすサーバがサーバ群3内に存在する場合には該サーバの識別情報を抽出して出力する。リソース条件を満たすサーバの識別情報が存在しない場合には、リソース条件を満たすサーバが存在しない旨を出力する。
 本実施の形態によれば、リソースの種別ごとに、複数のサーバの各々が備えるリソースの保有量を取得しておき、1台以上のサーバが備えるリソース種別ごとのリソースの保有量が、ユーザ等から入力された要求と対応するリソース種別ごとのリソース要求量を満たす場合に、当該1台以上のサーバの識別情報を抽出する。そのため、ユーザ等の要求を満たすリソースを保有する処理装置を適切に抽出できる。
 また、特に、抽出部12は、リソースの保有量の合計量が、入力された要求と対応するリソース要求量を満たす、複数台のサーバの識別情報を抽出することができる。そのため、1台のサーバではリソース要求量を満たさなくとも、複数台のサーバのリソース保有量の合計量がリソース要求量を満たすような場合に、ユーザにそれら複数のサーバを割り当てる。このようにして、ユーザの要求を満たすクラウド環境を構築することが可能となる。
 <実施形態2>
 次に、本発明の第2の実施の形態について図面を用いて説明する。本実施の形態の抽出システム4の構成図は、図1で示したものと同一であるが、リソース条件格納部13の格納している情報と、抽出部12の処理が、第1の実施の形態とは異なる。
 本実施の形態のリソース条件格納部13について説明する。
 図7には、本実施の形態におけるリソース条件格納部13が格納する情報の一例が示されている。図7に示すように、リソース条件格納部13は、同一の要求に対し、複数のリソースの種別と、当該複数のリソースの各々のリソースの要求量と、を含む複数のリソース条件を対応付けて格納している。このように、同一の要求を満たす複数のリソース条件が格納されている点で第1の実施の形態と異なる。
 同一の要求を満たすリソース種別とリソース要求量との組み合わせに様々な組み合わせがありうる場合、各々のリソース条件は、互いに同一の要求を満たす代替的な条件として設定される。
 例えば、ある要求に対応する複数のリソース条件のうちの、あるリソース条件に含まれるリソース種別と別のリソース条件に含まれるリソース種別とが同一であり、そのリソース種別に対応するリソース要求量が異なる場合がある。すなわち、同一の要求を満たす際、あるリソースの不足を、他のリソースの増加で補うことができる場合がある。例えば、ある要求に対応する複数のリソース条件のうちの、あるリソース条件に含まれるCPU性能は1000MIPS、ネットワーク帯域は1Gbpsであり、他のリソース条件に含まれるCPU性能は50MIPS、ネットワーク帯域は20Gbpsである場合がある。これは、例えば、CPU性能が小さい場合、通信のデータ圧縮を単純化できる場合である。また、例えば、あるリソース条件ではCPUのリソース要求量が大きい代わりにメモリのリソース要求量が小さく、他のリソース条件ではCPUのリソース要求量が小さい代わりにメモリのリソース要求量が大きいという場合がある。このように、各々のリソース条件は、同一の要求を満たす代替的な条件として設定されている。なお、同一の要求に対し、異なるリソース種別を含む、複数のリソース条件が存在しても良い。
 本実施の形態における抽出部12は、リソース条件格納部13に格納されたリソース条件のうち、ユーザ等から入力された要求と対応するリソース条件のいずれかを満たす1台以上のサーバの識別情報を抽出して出力する。
 また、リソース条件格納部13は、図7に示すように、リソース条件ごとに、リソース条件と優先順位とを対応付けて格納しても良い。そして、抽出部12は、リソース条件のうち、優先順位の高いリソース条件を満たす1台以上のサーバの識別情報を抽出して出力しても良い。優先順位は、例えば、クラウド事業者等が予め設定しておいても良い。
 次に、図6~図8を参照して、本実施の形態の抽出システム4の動作について説明する。リソース管理サーバ2の動作については、第1の実施の形態と同様であるから説明を省略する。
 図8、図6には、抽出装置1の動作が示されている。
 まず、要求入力部11は、ユーザ等から要求を取得する(ステップS21)。次に、抽出部12は、リソース条件格納部13から、ステップS21でユーザ等から入力された要求に対応するリソース条件を取得する(ステップS22)。例えば、ユーザ等が、応答時間が10秒以内であるとの要求を入力した場合、抽出部12は、リソース条件格納部13を参照して、図7に示すように、該要求に対応するリソース条件であるCPU性能:aMIPS、CPUコア数:1個、ネットワーク帯域:bGbps、HD回転速度:crpm、最大IO待ち時間:dmsecを抽出する。また、本実施の形態では、同一の要求を満たすリソース条件がリソース条件格納部13に複数格納されているため、抽出部12は、リソース条件格納部13に格納されている、同一の要求を満たすリソース条件を全て抽出する。この点は第1の実施の形態と異なる点である。
 次に、抽出部12は、K=1として(ステップS23)、優先順位がK(ここでは1)番目のリソース条件を満たすサーバの識別情報がリソース状態格納部22に存在するか否かを検索して抽出する処理(サーバの抽出処理)を行う(ステップS24)。
 ステップS24におけるサーバの抽出処理は、実施の形態1で説明した図6のサーバ抽出処理と同様であるため説明を省略する。
 次に、抽出部12は、サーバの抽出処理を行った結果、優先順位がK(ここでは1)のリソース条件を満たすサーバの識別情報が得られたかどうかを判定する(ステップS25)。
 優先順位がK(ここでは1)のリソース条件を満たすサーバの識別情報が得られた場合には(ステップS25、Yes)、抽出部12は、該サーバの識別情報をリソース状態格納部22(リソース状態格納部22からリソース状態取得部14が取得したリソース状態)から抽出して、表示部15等に出力する。
 一方、優先順位がK(ここでは1)のリソース条件を満たすサーバの識別情報が得られなかった場合には(ステップS25、No)、抽出部12は、Kに1を加える(ステップS27)。次に、抽出部12は、Kが所定値を超えたか否かを判定する(ステップS28)。所定値は、例えば、クラウド事業者等によって予め指定された値である。
 Kが所定値を越えていない場合(ステップS28、Yes)、抽出部12は、ステップS24を再度行なう。このように、抽出部12は、優先順位がK番目のサーバの識別情報の抽出ができない場合、Kが所定値を超えるまで、ステップS24、ステップS25、ステップS27を繰り返す。一方、Kが所定値を越えた場合(ステップS28、No)、抽出部12は、リソース条件を満たすサーバが存在しない旨を表示部15等に出力する(ステップS29)。
 上記の処理によって、抽出装置1は、優先順位がK番目のリソース条件を満たすサーバであって、リソース種別ごとのリソース保有量の合計量がリソース要求量を満たすN台のサーバの識別情報がリソース状態格納部22に存在するか否かを、K、Nの値を順次大きくしながら検索していくことができる。
 上記の処理では、まず、リソース条件に対応付けられた優先順位の番号であるKを決めて、次に、優先順位がK番目のリソース条件を満たすサーバの数Nを順次大きくする例を説明した。
 すなわち、例えば、抽出部12は、まず優先順位が1番目のリソース条件を満たす1台のサーバが存在するか否かを検索する。1台のサーバが存在しない場合、抽出部12は、優先順位が1番目のリソース条件を満たす2台のサーバが存在するか否かを検索する。
 2台のサーバが存在しない場合、抽出部12は、以下同様にして、サーバの台数Nを順次大きくして、優先順位が1番目のリソース条件を満たすN台のサーバが存在するか否かを検索する。
 Nが所定値を越えた場合、次に、抽出部12は、優先順位を1増加させて、優先順位が2番目のリソース条件を満たすサーバが存在するか否かを検索する。以下同様にして、まず優先順位のKを順次大きくしながらKの値を決定し、優先順位がK番目のリソース条件を満たすN台のサーバが存在するか否かを、Nを順次大きくして検索する。
 この方法は、クラウド環境を構築するに当たり、少ないサーバの台数でクラウド環境を構築することを重視するよりも、優先順位が上位のリソース条件を満たすサーバを抽出してクラウド環境を構築することを重視する方法である。
 一方、抽出装置1は、最初にサーバの台数Nを決定し、その後に、優先順位の番号Kを順次大きくしても良い。
 すなわち、例えば、抽出部12は、まずサーバ台数が1台で、優先順位が1番目のリソース条件を満たすサーバが存在するか否かを検索する。サーバが存在しない場合には、抽出部12は、1台のサーバで、優先順位が2番目のリソース条件を満たすサーバの組が存在するか否かを検索する。そのようなサーバが存在しない場合には、抽出部12は、以下同様にして、優先順位の番号Kを順次大きくして、優先順位がK番目のリソース条件を満たす1台のサーバが存在するか否かを検索する。
 Kが所定値を越えた場合、次に、抽出部12は、サーバ台数を1増加させ、サーバ台数が2台で、優先順位が1番目のリソース条件を満たすようなサーバが存在するか否かを検索する。以下同様にして、抽出部12は、サーバの台数Nを順次大きくしながらNの値を決定し、その後に、優先順位の番号Kを順次大きくして、優先順位がK番目のリソース条件を満たすサーバが存在するか否かを検索する。
 この方法は、クラウド環境を構築するに当たり、優先順位が上位のリソース条件を満たすサーバを抽出してクラウド環境を構築することを重視するよりも、少ないサーバの台数でクラウド環境を構築することを重視する方法である。
 本実施の形態によれば、リソース条件格納部13は、同一の要求に対し、複数のリソース条件を対応付けて格納している。そのため、抽出部12は、入力された要求と対応する複数のリソース条件のうちのいずれかを満たす1台以上のサーバの識別情報を抽出して出力することができる。
 また、リソース条件格納部13は、リソース条件ごとに優先順位を格納しているため、抽出部12は、複数のリソース条件のうち、優先順位の高いリソース条件を満たす1台以上のサーバの識別情報を抽出して出力することができる。
 このように、本実施の形態の抽出システム4によれば、ユーザ等の要求を満たすリソースを保有するサーバを適切に抽出することができる。
 <実施形態3>
 次に、本発明の第3の実施の形態について図面を用いて説明する。図10には、本実施の形態にかかる抽出装置1の構成の一例が示されている。
 抽出装置1は、リソース条件格納部13と、リソース状態取得部14と、抽出部12とを含む。
 リソース条件格納部13は、要求と、リソースの種別と当該リソースの要求量とを含むリソース条件と、を対応付けて格納する。
 リソース状態取得部14、リソースの種別ごとに、複数の情報処理装置の各々のリソースの保有量を取得する。
 抽出部12は、1台以上の情報処理装置が保有するリソース種別ごとのリソースの保有量が、入力された要求と対応するリソース条件格納部13に格納されたリソース種別ごとのリソース要求量を満たす場合に、当該1台以上の情報処理装置の識別情報を、複数の情報処理装置から抽出して出力する。ここで、抽出部12は、識別情報を情報処理装置(サーバ群3)から直接抽出しても良いし(図9参照)、リソース管理サーバ2から抽出しても良い(図1参照)。
 本実施の形態によれば、要求を満たすリソースを保有する情報処理装置を抽出できる抽出装置、システム、プログラム、及び、方法が提供される。
 この出願は、2011年9月2日に出願された日本出願特願2011−191897を基礎とする優先権を主張し、その開示の全てをここに取り込む。
 以上、実施形態を参照して本願発明を説明したが、本願発明は上記実施形態に限定されるものではない。本願発明の構成や詳細には、本願発明のスコープ内で当業者が理解しうる様々な変更をすることができる。例えば、抽出部12は、サーバを抽出するだけではなく、他の装置、例えば、ディスク装置等を抽出しても良い。
Hereinafter, embodiments of the present invention will be described with reference to the drawings. In all the drawings, the same components are denoted by the same reference numerals, and description thereof will be omitted as appropriate.
In addition, each part which comprises the apparatus of each embodiment is comprised by hardware, such as a logic circuit. Each unit includes a computer control unit, a memory, a program loaded in the memory, a storage unit such as a hard disk for storing the program, a network connection interface, and the like, and may be realized by any combination of hardware and software. Good. And unless there is particular notice, the realization method and apparatus are not limited.
The control unit is composed of a CPU (Central Processing Unit) or the like, and operates an OS (Operating System) to control the entire apparatus and the like. For example, a program and data are stored in a memory from a recording medium mounted on a drive device or the like. Read and execute various processes according to this. The recording medium is, for example, an optical disk, a flexible disk, a magnetic optical disk, an external hard disk, a semiconductor memory, or the like, and records a computer program so that the computer can read it. The computer program may be downloaded from an external computer (not shown) connected to the communication network.
<Embodiment 1>
Next, a first embodiment of the present invention will be described with reference to the drawings. FIG. 1 shows an extraction system 4 according to the present embodiment.
The extraction system 4 includes an extraction device 1, a resource management server 2, and a server group 3. An example of the extraction system 4 is shown in FIG. The extraction device 1 and the resource management server 2 are connected by a communication line or the like. The resource management server 2 and the server group 3 are connected by a communication line or the like.
The server group 3 includes a plurality of servers (information processing apparatuses), and each server includes resources such as a CPU, a memory, and a communication line. The hardware included in each server has characteristics such as quantity and performance that affect the performance and reliability of the system using the server, and each characteristic is called a resource type. The types of resources included in each server include CPU performance and network bandwidth. Also, the resource holding amount is defined corresponding to the resource type. The resource holding amount is a numerical value indicating the degree to which the characteristic contributes to performance and reliability. That is, the amount of resources held by each server is not limited to the amount of physical resources held by each server, but includes the performance value of each server. For example, the resource holding amount is xMIPS (Million Instructions Per Second) for CPU performance, y for the number of CPU cores, zGbps (Gigabit per second) for the network bandwidth, and the like.
The extraction device 1 includes a request input unit 11, an extraction unit 12, a resource condition storage unit 13, a resource state acquisition unit 14, and a display unit 15.
The request input unit 11 is an input means for a user or the like to input a function request or a non-function request. The user or the like may use the request input unit 11 to input a resource type or a resource request amount that the user or the like requests from the cloud environment system.
Here, the resource type is a type for distinguishing resources, and is not limited to the amount of hardware such as the number of CPU cores as described above, but also includes performance such as CPU performance and network bandwidth. The resource request amount is an amount by which a user or the like requests each resource type. For example, xMIPS (Million Instructions Per second) for CPU performance, y for the number of CPU cores, and zGbps (for network bandwidth). Gigabit per second).
The request input by the user or the like may include a request item and a request level. The request item is a non-functional request item such as response time, operation time, reliability, and extensibility requested by the user or the like to the cloud environment system. The request item may be a function request item such as hot standby or encryption. The request level indicates whether a request from a user or the like is high or low for each request item. For example, if the request item is a response time, the request level is within 10 seconds, and the request item is an operation time. If so, the required level is, for example, an average failure time of 6 months. In some cases, the request does not include the request level and is only a request item.
A user or the like inputs a request via the request input unit 11. The request input unit 11 outputs the input request to the extraction unit 12 described later.
As shown in FIG. 2, the resource condition storage unit 13 stores the request and the resource condition in association with each other. As shown in FIG. 2, the resource condition is information in which one or more resource types are associated with a resource request amount for each resource type.
At the top of the table in FIG. 2, the resource condition for satisfying the request whose request item is the response time and the request level is within 10 seconds is the resource type and the resource request amount of the resource type. Combination (CPU performance is aMIPS, number of CPU cores is 1, network bandwidth is bGbps, HD (Hard Disc) rotation speed is crpm (revolution per minute / rotation per minute), maximum IO (Input / Output) waiting time is dmsec ( milli-second)). In this way, the resource condition storage unit 13 stores, for example, a request (request item and its request level) and a resource condition (one or more resource types and its resource request amount) satisfying the request in association with each other. Yes.
The resource state acquisition unit 14 acquires a resource holding amount (resource holding amount) for each resource type (resource type) included in each of the plurality of servers. The resource status acquisition unit 14 may acquire the resource holding amount of each of the plurality of servers from the resource status storage unit 22 described later, or may acquire from the server group 3 as shown in FIG. .
When the condition is satisfied, the extraction unit 12 extracts server identification information of one or more servers from the server. The condition is that the resource holding amount for each resource type held by the one or more servers satisfies the resource request amount for each resource type included in the resource condition corresponding to the request input from the request input unit 11 ( It is simply referred to as a resource condition). As will be described later, the extraction unit 12 may extract the server identification information from the resource state storage unit 22 instead of extracting the server identification information directly from the server.
Further, the extraction unit 12 outputs the extracted server identification information. Although the output destination is not limited, for example, the extracting unit 12 may output the extracted server identification information to the display unit 15. In addition, when the above-described server does not exist, the extraction unit 12 may output to the display unit 15 that no server that satisfies the resource condition exists.
In addition, the extraction unit 12 includes a plurality of servers in which a total amount of resource holding amounts for each resource type held by a plurality of servers satisfies a resource request amount for each resource type included in a resource condition corresponding to the input request. The identification information may be extracted from the server group 3 and output. For example, as one of the resource conditions corresponding to the request input by the user, when the resource type is CPU performance and the resource request amount is 100 MIPS, the server identification information is A server, and the server identification information is B server. In the case where the CPU performances in total are 100 MIPS or more, the extraction unit 12 may extract the server identification information A and B.
As described above, the extraction unit 12 extracts a plurality of servers in which the total amount of resources held by each server satisfies the resource condition, thereby constructing a cloud environment that cannot be realized by a single server. It becomes possible.
In addition, when a plurality of requests are input from the request input unit 11, the extraction unit 12 receives the server identification information of one or more servers that satisfy all the resource conditions corresponding to each of the requests, the resource state storage unit 22, and the like. May be extracted from Specific examples will be described later.
The display unit 15 is a display unit such as a display that displays the server identification information acquired from the extraction unit 12. The user looks at the server identification information displayed on the display unit 15 or sees information indicating that there is no server that satisfies the resource condition, thereby determining whether there is a server that satisfies the user's request. I can grasp it.
The resource management server 2 includes a resource management unit 21 and a resource state storage unit 22.
The resource management unit 21 periodically obtains, from the server group 3, the identification information of the server that holds the currently available resource, the resource type of the resource held by each server, and the resource holding amount for each resource type. And stored in the resource state storage unit 22. The server identification information, the resource type, and the resource holding amount of the server that holds the currently available resource, which is information acquired by the resource management unit 21, are also referred to as a resource state. For example, the resource management unit 21 may periodically acquire a resource state every predetermined time and store it in the resource state storage unit 22.
The resource state storage unit 22 stores the resource state acquired by the resource management unit 21. FIG. 3 is an example of a resource state stored in the resource state storage unit 22. The top row of the table of FIG. 3 indicates that there is a server whose server identification information is A in the server group 3 at a certain point in time. The server A resource type and its resource holding amount are: CPU performance: eMIPS, number of CPU cores: 2, network bandwidth: fGbps, HD rotation speed: grpm, maximum IO wait time: hmsec, standby system 3 units, HDRAID 1 (Redundant Arrays of Independent Disks): 2 units.
The resource management server 2 may be managed by a cloud provider or the like different from the extraction device 1. In this case, there is an advantage that the person who operates the extraction apparatus 1 does not have to manage the server group 3 directly. In addition, a cloud operator or the like that manages the resource management server 2 can appropriately correct the contents of the resource state acquired by the resource management unit 21 via a correction unit (not shown) provided in the management server 2. . For example, in addition to resources that are currently available, a cloud business operator or the like adds resources that are scheduled to become available soon (for example, resources that are scheduled to be purchased or that will end maintenance) to the resource state storage unit 22. May be. Conversely, the cloud service provider deletes resources that the user does not want to allocate from the resource state storage unit 22 because maintenance is required or the user does not want to share resources with other users. Also good.
Next, operation | movement of the extraction system 4 of this Embodiment is demonstrated.
The operation of the resource management server 2 will be described. FIG. 4 shows the operation of the resource management server 2. The resource management unit 21 of the resource management server 2 periodically acquires from the server group 3 server identification information of servers that have resources available at that time, resource types of resources held by each server, and resource types. Each resource holding amount is acquired (step S1), and those resource states are stored in the resource state storage unit 22 (step S2). In addition, the cloud business operator etc. which manage the resource management server 2 may correct the content of the resource state which the resource management part 21 acquired suitably.
The operation of the extraction device 1 will be described. 5 and 6 show the operation of the extraction device 1.
First, the request input unit 11 acquires a request from a user or the like (step S11). Next, the extraction unit 12 acquires a resource condition corresponding to the request input from the user or the like in step S11 from the resource condition storage unit 13 (step S12). For example, when a user or the like inputs a request that the response time is within 10 seconds, the extraction unit 12 refers to the resource condition storage unit 13 and extracts a resource condition corresponding to the request. In this case, as shown in FIG. 2, the resource conditions corresponding to the request are CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, and maximum IO waiting time: dmsec. .
Next, the extraction unit 12 searches the resource state storage unit 22 for the server identification information that satisfies the resource condition extracted in step S12. If there is server identification information that satisfies the resource conditions, the server identification information is extracted and output. If there is no server identification information that satisfies the resource condition, a process of outputting that there is no server that satisfies the resource condition (server extraction process) is performed (step S13).
The detailed operation of the server extraction process in step S13 will be described with reference to FIG.
First, the extraction unit 12 sets N = 1 (step S131). Subsequently, identification information of N (here, 1) servers whose resource holding amount for each resource type of the extracted resource condition satisfies the resource condition extracted in step S12 exists in the resource state storage unit 22. It is determined whether or not (step S132). This determination is made with reference to the resource state acquired by the resource state acquisition unit 14 from the resource state storage unit 22.
If there are N (1 here) servers that satisfy the resource condition, the extraction unit 12 extracts the server identification information of such servers from the resource state storage unit 22 and outputs the extracted server identification information to the display unit 15 (step 15). S133).
On the other hand, when there are N (here, 1) servers that satisfy the resource condition, the extraction unit 12 adds 1 to N (step S134). Further, it is determined whether N exceeds a predetermined value (step S135). The predetermined value is, for example, a value designated in advance by a cloud operator or the like.
If N does not exceed the predetermined value, the extraction unit 12 repeats step S132. That is, it is determined by referring to the resource state acquired by the resource state acquisition unit 14 whether or not there are N servers that satisfy the resource condition (N is 1 in this case because N is added in step S134). (Step S132). That is, the extraction unit 12 makes the total amount of resources held for each resource type held by N (here 2) servers satisfy the resource request amount for each resource type corresponding to the input request. It is determined whether there are N (here, 2) servers.
If there are N (here 2) servers that satisfy the resource condition, the extraction unit 12 extracts the server identification information of such servers from the server group 3 and the resource state storage unit 22 and displays them on the display unit 15 and the like. Output (step S133).
On the other hand, when there are N (here, 2) servers that satisfy the resource condition, the extraction unit 12 adds 1 to N again (step S134), and determines whether N exceeds a predetermined value (step S134). S135). If N does not exceed the predetermined value, the extraction unit 12 performs Step S132 again. As described above, as long as N does not exceed the predetermined value, the extraction unit 12 repeats step S132, and when there are N servers that satisfy the resource condition, the value of N is sequentially increased by one in step S134. Repeat the process.
On the other hand, if the extraction unit 12 determines that N exceeds a predetermined value in step S135, the extraction unit 12 outputs to the display unit 15 or the like that there is no server that satisfies the resource condition (step S136).
In addition, when a plurality of requests are input from the request input unit 11, the extraction unit 12 receives the server identification information of one or more servers that satisfy all the resource conditions corresponding to each of the requests, the resource state storage unit 22, and the like. May be extracted from A specific example will be described with reference to FIG. For example, when a response time: within 10 seconds and an operation time: an average failure time of 6 months are input as requests, the extraction unit 12 determines the CPU performance as a resource condition corresponding to the request with a response time: within 10 seconds. : AMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, maximum IO waiting time: dmsec are extracted. Further, the extraction unit 12 extracts one or more HDRAID 1: 1, which is a resource condition corresponding to a request of operating time: average failure time of 6 months. Then, the extraction unit 12 extracts server identification information of one or more servers that satisfy all of the extracted resource conditions from the resource state storage unit 22 and the like. As described above, the extraction unit 12 regards a condition obtained by combining resource conditions corresponding to each of a plurality of requests as a new resource condition. Whether or not there is a server that satisfies the new resource condition may be extracted according to the operations shown in FIGS.
Also, for example, when a response time: within 10 seconds and an operation time: an average failure time of 10 months are input as requests, the extraction unit 12 is a resource condition corresponding to the request with a response time: within 10 seconds. CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: crpm, maximum IO waiting time: dmsec are extracted. In addition, the extraction unit 12 extracts one standby system that is a resource condition corresponding to a request of operating time: average failure time of 10 months. Here, when the extracted resource condition includes “standby system”, the extraction unit 12 displays the server identification information of the server that satisfies all the resource conditions excluding the “standby system” condition as “standby system”. An extra amount is extracted from the resource state storage unit 22 and the like by the required resource amount required for the “system”. That is, in this example, the extraction unit 12 selects one or more servers that satisfy CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, and maximum IO waiting time: dmsec. Only one resource, which is the required resource amount required for the “standby system”, is extracted from the resource state storage unit 22 and the like. That is, two sets of server identification information of one or more servers satisfying CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, and maximum IO waiting time: dmsec are extracted.
The above description is based on the assumption that the resource management server 2 exists. When the resource management server 2 does not exist, the following may be performed. That is, the extraction unit 12 may perform a process (server extraction process) for directly searching the server group 3 as to whether or not the server group 3 includes a server that satisfies the resource condition extracted in step S12. In this process, if a server that satisfies the resource condition exists in the server group 3, the server identification information is extracted and output. If there is no server identification information that satisfies the resource condition, a message that no server satisfies the resource condition is output.
According to the present embodiment, for each resource type, the amount of resource possessed by each of the plurality of servers is acquired, and the amount of resource retained for each resource type possessed by one or more servers is determined by the user, etc. When the resource request amount corresponding to the resource type corresponding to the request input from is satisfied, the identification information of the one or more servers is extracted. Therefore, it is possible to appropriately extract a processing apparatus that has resources that satisfy a user's request.
In particular, the extraction unit 12 can extract identification information of a plurality of servers in which the total amount of resources held satisfies the resource request amount corresponding to the input request. For this reason, even if one server does not satisfy the resource request amount, the plurality of servers are allocated to the user when the total amount of the resource holding amount of the plurality of servers satisfies the resource request amount. In this way, it is possible to construct a cloud environment that satisfies the user's request.
<Embodiment 2>
Next, a second embodiment of the present invention will be described with reference to the drawings. The configuration diagram of the extraction system 4 of the present embodiment is the same as that shown in FIG. 1, but the information stored in the resource condition storage unit 13 and the processing of the extraction unit 12 are the same as those in the first embodiment. Different from form.
The resource condition storage unit 13 of this embodiment will be described.
FIG. 7 shows an example of information stored in the resource condition storage unit 13 in the present embodiment. As illustrated in FIG. 7, the resource condition storage unit 13 associates a plurality of resource conditions including a plurality of resource types and a request amount of each resource of the plurality of resources with respect to the same request. Storing. Thus, the second embodiment is different from the first embodiment in that a plurality of resource conditions that satisfy the same request are stored.
When there are various combinations of resource types and resource request amounts that satisfy the same request, each resource condition is set as an alternative condition that satisfies the same request.
For example, among a plurality of resource conditions corresponding to a certain request, the resource type included in one resource condition is the same as the resource type included in another resource condition, and the resource request amount corresponding to the resource type is different. There is a case. That is, when satisfying the same request, a shortage of one resource may be compensated by an increase in other resources. For example, among a plurality of resource conditions corresponding to a certain request, the CPU performance included in a certain resource condition is 1000 MIPS, the network bandwidth is 1 Gbps, the CPU performance included in other resource conditions is 50 MIPS, and the network bandwidth is 20 Gbps. There may be. This is a case where communication data compression can be simplified when the CPU performance is low, for example. In addition, for example, in some resource conditions, the CPU resource request amount is small instead of the CPU resource request amount, and in other resource conditions, the CPU resource request amount is small but the memory resource request amount is large. . In this way, each resource condition is set as an alternative condition that satisfies the same request. A plurality of resource conditions including different resource types may exist for the same request.
In the present embodiment, the extraction unit 12 includes identification information of one or more servers that satisfy any of the resource conditions stored in the resource condition storage unit 13 and corresponding to the request input from the user or the like. Extract and output.
Further, as shown in FIG. 7, the resource condition storage unit 13 may store a resource condition and a priority order in association with each resource condition. And the extraction part 12 may extract and output the identification information of one or more servers which satisfy | fill the resource conditions with high priority among resource conditions. The priority order may be preset by, for example, a cloud operator.
Next, the operation of the extraction system 4 of the present embodiment will be described with reference to FIGS. Since the operation of the resource management server 2 is the same as that of the first embodiment, the description thereof is omitted.
8 and 6 show the operation of the extraction device 1.
First, the request input unit 11 acquires a request from a user or the like (step S21). Next, the extraction unit 12 acquires a resource condition corresponding to the request input from the user or the like in step S21 from the resource condition storage unit 13 (step S22). For example, when the user or the like inputs a request that the response time is within 10 seconds, the extraction unit 12 refers to the resource condition storage unit 13 and, as shown in FIG. CPU performance: aMIPS, number of CPU cores: 1, network bandwidth: b Gbps, HD rotation speed: c rpm, maximum IO waiting time: dmsec are extracted. In the present embodiment, since a plurality of resource conditions satisfying the same request are stored in the resource condition storage unit 13, the extraction unit 12 satisfies the same request stored in the resource condition storage unit 13. Extract all resource conditions. This point is different from the first embodiment.
Next, the extraction unit 12 sets K = 1 (step S23), and searches for whether or not the identification information of the server that satisfies the Kth (here, 1) priority resource condition exists in the resource state storage unit 22 Then, the extraction process (server extraction process) is performed (step S24).
The server extraction process in step S24 is the same as the server extraction process of FIG.
Next, the extraction unit 12 determines whether or not server identification information satisfying the resource condition of the priority K (here, 1) is obtained as a result of the server extraction process (step S25).
When the identification information of the server that satisfies the resource condition of priority K (here, 1) is obtained (step S25, Yes), the extraction unit 12 displays the identification information of the server in the resource state storage unit 22 (resource The resource state acquired by the resource state acquisition unit 14 from the state storage unit 22 is extracted and output to the display unit 15 or the like.
On the other hand, when the identification information of the server that satisfies the resource condition of priority K (here 1) is not obtained (No in step S25), the extraction unit 12 adds 1 to K (step S27). Next, the extraction unit 12 determines whether or not K exceeds a predetermined value (step S28). The predetermined value is, for example, a value designated in advance by a cloud operator or the like.
When K does not exceed the predetermined value (step S28, Yes), the extraction unit 12 performs step S24 again. As described above, when the identification information of the server with the Kth priority cannot be extracted, the extraction unit 12 repeats Step S24, Step S25, and Step S27 until K exceeds a predetermined value. On the other hand, if K exceeds a predetermined value (step S28, No), the extraction unit 12 outputs to the display unit 15 or the like that there is no server that satisfies the resource condition (step S29).
As a result of the above processing, the extraction device 1 is the server that satisfies the resource condition of the Kth priority, and the identification information of the N servers whose total resource holding amount for each resource type satisfies the resource request amount is the resource. Whether or not it exists in the state storage unit 22 can be searched while increasing the values of K and N sequentially.
In the above processing, an example has been described in which K, which is a priority number associated with a resource condition, is first determined, and then the number N of servers satisfying the Kth resource condition is sequentially increased. .
That is, for example, the extraction unit 12 first searches whether there is one server that satisfies the first priority resource condition. When one server does not exist, the extraction unit 12 searches whether there are two servers that satisfy the first resource condition of the priority order.
When there are no two servers, the extraction unit 12 increases the number N of servers sequentially in the same manner, and determines whether or not there are N servers that satisfy the first priority resource condition. Search for.
When N exceeds a predetermined value, the extraction unit 12 next increases the priority by 1 and searches whether there is a server that satisfies the second priority resource condition. In the same manner, first, the value of K is determined while sequentially increasing the priority K, and whether or not there are N servers satisfying the Kth resource priority is determined by sequentially increasing N. Search for.
This method emphasizes the construction of a cloud environment by extracting servers that satisfy the higher priority resource conditions rather than emphasizing the construction of a cloud environment with a small number of servers. It is a method to do.
On the other hand, the extraction device 1 may first determine the number N of servers, and then sequentially increase the priority number K.
That is, for example, the extraction unit 12 first searches whether there is a server that satisfies the first resource condition with the number of servers being one. If there is no server, the extraction unit 12 searches for a set of servers that satisfy the second priority resource condition with one server. If there is no such server, the extraction unit 12 increases the priority number K sequentially in the same manner, and determines whether there is one server that satisfies the Kth resource condition. Search for no.
When K exceeds a predetermined value, the extraction unit 12 then increases the number of servers by 1, and whether there is a server that satisfies the first resource condition with the number of servers being 2 and the first priority. Search for. Similarly, the extracting unit 12 determines the value of N while sequentially increasing the number N of servers, and then sequentially increases the priority number K to satisfy the resource condition of the Kth priority. Search whether a server exists.
This method focuses on building a cloud environment with a small number of servers, rather than focusing on building a cloud environment by extracting servers that satisfy the higher priority resource conditions when building a cloud environment. It is a method to do.
According to the present embodiment, the resource condition storage unit 13 stores a plurality of resource conditions in association with the same request. Therefore, the extraction unit 12 can extract and output identification information of one or more servers that satisfy any of a plurality of resource conditions corresponding to the input request.
Further, since the resource condition storage unit 13 stores the priority for each resource condition, the extraction unit 12 identifies the identification information of one or more servers that satisfy the resource condition with the higher priority among the plurality of resource conditions. Can be extracted and output.
As described above, according to the extraction system 4 of the present embodiment, it is possible to appropriately extract a server having resources that satisfy a request from a user or the like.
<Embodiment 3>
Next, a third embodiment of the present invention will be described with reference to the drawings. FIG. 10 shows an example of the configuration of the extraction device 1 according to the present embodiment.
The extraction device 1 includes a resource condition storage unit 13, a resource state acquisition unit 14, and an extraction unit 12.
The resource condition storage unit 13 stores a request and a resource condition including the resource type and the requested amount of the resource in association with each other.
The resource status acquisition unit 14 acquires the resource holding amount of each of the plurality of information processing apparatuses for each resource type.
The extraction unit 12 satisfies the resource request amount for each resource type stored in the resource condition storage unit 13 corresponding to the input request, with the resource holding amount for each resource type held by one or more information processing apparatuses. In this case, the identification information of the one or more information processing devices is extracted from a plurality of information processing devices and output. Here, the extraction unit 12 may extract the identification information directly from the information processing apparatus (server group 3) (see FIG. 9) or may be extracted from the resource management server 2 (see FIG. 1).
According to the present embodiment, an extraction device, a system, a program, and a method that can extract an information processing device that has a resource that satisfies a request are provided.
This application claims the priority on the basis of Japanese application Japanese Patent Application No. 2011-191897 for which it applied on September 2, 2011, and takes in those the indications of all here.
While the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. For example, the extraction unit 12 may extract not only a server but also other devices such as a disk device.
 1  抽出装置
 11 要求入力部
 12 抽出部
 13 リソース条件格納部
 14 リソース状態取得部
 15 表示部
 2  リソース管理サーバ
 21 リソース管理部
 22 リソース状態格納部
 3  サーバ群
DESCRIPTION OF SYMBOLS 1 Extraction apparatus 11 Request input part 12 Extraction part 13 Resource condition storage part 14 Resource state acquisition part 15 Display part 2 Resource management server 21 Resource management part 22 Resource state storage part 3 Server group

Claims (16)

  1.  要求項目と、1以上のリソースの種別と当該リソースごとの要求量とを含むリソース条件と、を対応付けて格納するリソース条件格納手段と、
     前記リソースの種別ごとに、複数の処理装置の各々の前記リソースの保有量を取得するリソース状態取得手段と、
     外部から前記要求項目を取得して、1台以上の前記処理装置が保有する前記リソース種別ごとのリソースの保有量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす場合に、当該1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する抽出手段と、を備える抽出装置。
    Resource condition storage means for storing a request item, a resource condition including one or more resource types and a request amount for each resource, in association with each other;
    Resource status acquisition means for acquiring the amount of the resource held by each of a plurality of processing devices for each type of the resource,
    The request item is acquired from the outside, and the possession amount of the resource for each resource type held by one or more of the processing devices is the resource type included in the resource condition corresponding to the acquired request item. An extraction device comprising: extraction means for extracting the identification information of the one or more processing devices from the plurality of processing devices and outputting them when the resource request amount is satisfied.
  2.  前記抽出手段は、前記リソースの保有量の合計量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす、複数台の前記処理装置の識別情報を、前記複数台の処理装置から抽出して出力する請求項1に記載の抽出装置。 The extraction unit is configured to obtain identification information of a plurality of the processing devices in which a total amount of the resources held satisfies the resource request amount for each resource type included in the resource condition corresponding to the acquired request item. The extraction apparatus according to claim 1, wherein the extraction apparatus extracts and outputs from the plurality of processing apparatuses.
  3.  前記リソース条件格納手段は、同一の前記要求項目に対し、複数のリソースの種別と当該複数のリソースの各々のリソースの要求量とを含む複数のリソース条件を対応付けて格納し、
     前記抽出手段は、取得した前記要求項目と対応する前記リソース条件格納手段に格納された複数の前記リソース条件のいずれかを満たす1台以上の前記処理装置の識別情報を抽出して出力する
     請求項1乃至2のいずれかに記載の抽出装置。
    The resource condition storage unit stores a plurality of resource conditions in association with a plurality of resource types and a request amount of each resource of the plurality of resources for the same request item,
    The extraction unit extracts and outputs identification information of one or more of the processing devices that satisfy any one of the plurality of resource conditions stored in the resource condition storage unit corresponding to the acquired request item. The extraction device according to any one of 1 to 2.
  4.  前記リソース条件格納手段は、複数(n、nは1以上の自然数)の前記要求項目ごとに、前記リソース条件を格納し、
     前記抽出手段は、複数(m、mは1以上の自然数で、m≦n)の前記要求項目を取得し、前記m個の取得した前記要求項目の各々に対応する前記リソース条件を満たす1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する請求項1乃至3のいずれかに記載の抽出装置。
    The resource condition storage means stores the resource condition for each of a plurality (n, n is a natural number of 1 or more) of the request items,
    The extraction means acquires a plurality (m, m are natural numbers of 1 or more, m ≦ n) of the request items, and one unit that satisfies the resource condition corresponding to each of the m acquired request items The extraction apparatus according to claim 1, wherein the identification information of the processing apparatus is extracted from the plurality of processing apparatuses and output.
  5.  前記リソース条件格納手段は、前記リソース条件ごとに優先順位を格納し、
     前記抽出手段は、前記リソース条件のうち、優先順位の高いリソース条件を満たす1台以上の前記処理装置の識別情報を抽出して出力する請求項3に記載の抽出装置。
    The resource condition storage means stores a priority for each resource condition,
    The extraction device according to claim 3, wherein the extraction unit extracts and outputs identification information of one or more of the processing devices that satisfy a resource condition having a high priority among the resource conditions.
  6.  前記処理装置から、定期的に前記リソース種別と前記リソース保有量を収集してリソース状態格納手段に格納するリソース管理手段を備えるリソース管理サーバと、
     前記リソース状態格納手段から前記リソース種別と前記リソース保有量を取得する前記リソース状態取得手段を備える請求項1乃至5のいずれかに記載の抽出装置と、を含む抽出システム。
    A resource management server comprising resource management means for periodically collecting the resource type and the resource holding amount from the processing device and storing them in a resource state storage means;
    An extraction system comprising: the resource state acquisition unit that acquires the resource type and the resource holding amount from the resource state storage unit.
  7.  要求項目と、1以上のリソースの種別と当該リソースごとの要求量とを含むリソース条件と、を対応付けて格納するリソース条件格納手段を備えるコンピュータに、
     前記リソースの種別ごとに、複数の処理装置の各々の前記リソースの保有量を取得するリソース状態取得ステップと、
     外部から前記要求項目を取得して、1台以上の前記処理装置が保有する前記リソース種別ごとのリソースの保有量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす場合に、当該1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する抽出ステップと、を実行させる抽出プログラム。
    A computer comprising resource condition storage means for storing a request item, a resource condition including one or more resource types and a request amount for each resource, in association with each other,
    A resource status acquisition step of acquiring the amount of the resource held by each of a plurality of processing devices for each resource type;
    The request item is acquired from the outside, and the possession amount of the resource for each resource type held by one or more of the processing devices is the resource type included in the resource condition corresponding to the acquired request item. An extraction program for executing an extraction step of extracting identification information of the one or more processing devices from the plurality of processing devices and outputting them when the resource request amount is satisfied.
  8.  前記リソースの保有量の合計量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす、複数台の前記処理装置の識別情報を、前記複数台の処理装置から抽出して出力する前記抽出ステップを、前記コンピュータに実行させる請求項7に記載の抽出プログラム。 The identification information of the plurality of processing devices satisfying the resource request amount for each of the resource types included in the resource condition corresponding to the acquired request item is the total amount of the resource possessed. The extraction program according to claim 7, wherein the extraction step of extracting and outputting from a processing device is executed by the computer.
  9.  前記リソース条件格納手段は、同一の前記要求項目に対し、複数のリソースの種別と当該複数のリソースの各々のリソースの要求量とを含む複数のリソース条件を対応付けて格納し、
     取得した前記要求項目と対応する前記リソース条件格納手段に格納された複数の前記リソース条件のいずれかを満たす1台以上の前記処理装置の識別情報を抽出して出力する前記抽出ステップを前記コンピュータに実行させる請求項7乃至8のいずれかに記載の抽出プログラム。
    The resource condition storage unit stores a plurality of resource conditions in association with a plurality of resource types and a request amount of each resource of the plurality of resources for the same request item,
    The extraction step of extracting and outputting identification information of one or more processing devices that satisfy any one of the plurality of resource conditions stored in the resource condition storage unit corresponding to the acquired request item to the computer The extraction program according to any one of claims 7 to 8, which is executed.
  10.  前記リソース条件格納手段は、複数(n、nは1以上の自然数)の前記要求項目ごとに、前記リソース条件を格納し、
     複数(m、mは1以上の自然数で、m≦n)の前記要求項目を取得し、前記m個の取得した前記要求項目の各々に対応する前記リソース条件を満たす1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する前記抽出ステップを、前記コンピュータに実行させる請求項7乃至9のいずれかに記載の抽出プログラム。
    The resource condition storage means stores the resource condition for each of a plurality (n, n is a natural number of 1 or more) of the request items,
    A plurality (m, m are natural numbers greater than or equal to 1 and m ≦ n) is acquired, and one or more processing devices satisfying the resource condition corresponding to each of the m acquired request items The extraction program according to any one of claims 7 to 9, which causes the computer to execute the extraction step of extracting and outputting the identification information from the plurality of processing devices.
  11.  前記リソース条件格納手段は、前記リソース条件ごとに優先順位を格納し、
     前記リソース条件のうち、優先順位の高いリソース条件を満たす1台以上の前記処理装置の識別情報を抽出して出力する前記抽出ステップを、前記コンピュータに実行させる請求項9に記載の抽出プログラム。
    The resource condition storage means stores a priority for each resource condition,
    The extraction program according to claim 9, which causes the computer to execute the extraction step of extracting and outputting identification information of one or more of the processing devices satisfying a resource condition having a high priority among the resource conditions.
  12.  要求項目と、1以上のリソースの種別と当該リソースごとの要求量とを含むリソース条件と、を対応付けて格納し、
     前記リソースの種別ごとに、複数の処理装置の各々の前記リソースの保有量を取得し、
     外部から前記要求項目を取得し、1台以上の前記処理装置が保有する前記リソース種別ごとのリソースの保有量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす場合に、当該1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する抽出方法。
    A request item, one or more resource types, and a resource condition including a request amount for each resource are stored in association with each other,
    For each resource type, obtain the amount of the resource held by each of a plurality of processing devices,
    The resource for each resource type included in the resource condition corresponding to the acquired request item is acquired from the outside, and the amount of the resource for each resource type held by one or more of the processing devices is included in the resource condition corresponding to the acquired request item An extraction method for extracting identification information of the one or more processing devices from the plurality of processing devices and outputting them when the required amount is satisfied.
  13.  前記リソースの保有量の合計量が、取得した前記要求項目と対応する前記リソース条件が含む前記リソース種別ごとの前記リソース要求量を満たす、複数台の前記処理装置の識別情報を、前記複数台の処理装置から抽出して出力する請求項12に記載の抽出方法。 The identification information of the plurality of processing devices satisfying the resource request amount for each of the resource types included in the resource condition corresponding to the acquired request item is the total amount of the resource possessed. The extraction method according to claim 12, wherein the data is extracted from the processing device and output.
  14.  同一の要求に対し、複数のリソースの種別と当該複数のリソースの各々のリソースの要求量とを含む複数のリソース条件を対応付けて格納し、
     取得した前記要求と対応する前記リソース条件のいずれかを満たす1台以上の前記処理装置の識別情報を抽出して出力する請求項12乃至13のいずれかに記載の抽出方法。
    For the same request, a plurality of resource conditions including a plurality of resource types and a request amount of each resource of the plurality of resources are stored in association with each other,
    The extraction method according to claim 12, wherein identification information of one or more processing devices that satisfy any of the resource conditions corresponding to the acquired request is extracted and output.
  15.  複数(n、nは1以上の自然数)の前記要求項目ごとに、前記リソース条件を格納し、
     複数(m、mは1以上の自然数で、m≦n)の前記要求項目を取得し、前記m個の取得した前記要求項目の各々に対応する前記リソース条件を満たす1台以上の前記処理装置の識別情報を、前記複数の処理装置から抽出して出力する請求項12乃至14のいずれかに記載の抽出方法。
    The resource condition is stored for each of the plurality of request items (n, n is a natural number of 1 or more),
    A plurality (m, m are natural numbers greater than or equal to 1 and m ≦ n) is acquired, and one or more processing devices satisfying the resource condition corresponding to each of the m acquired request items The extraction method according to claim 12, wherein the identification information is extracted from the plurality of processing devices and output.
  16.  前記リソース条件ごとに優先順位を格納し、
     前記リソース条件のうち、優先順位の高いリソース条件を満たす1台以上の前記処理装置の識別情報を抽出して出力する請求項14に記載の抽出方法。
    Store priorities for each resource condition,
    The extraction method according to claim 14, wherein identification information of one or more of the processing devices that satisfy a resource condition having a high priority among the resource conditions is extracted and output.
PCT/JP2012/072284 2011-09-02 2012-08-28 Extraction device, system, program, and method WO2013031999A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2011-191897 2011-09-02
JP2011191897 2011-09-02

Publications (1)

Publication Number Publication Date
WO2013031999A1 true WO2013031999A1 (en) 2013-03-07

Family

ID=47756471

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/072284 WO2013031999A1 (en) 2011-09-02 2012-08-28 Extraction device, system, program, and method

Country Status (1)

Country Link
WO (1) WO2013031999A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04271454A (en) * 1991-02-27 1992-09-28 Toshiba Corp Loosely-coupled computer system
JP2004046372A (en) * 2002-07-09 2004-02-12 Nippon Telegr & Teleph Corp <Ntt> Distributed system, resource allocation method, program, and recording medium with which resource allocation program is recorded
JP2011018198A (en) * 2009-07-09 2011-01-27 Hitachi Ltd Management device and management method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04271454A (en) * 1991-02-27 1992-09-28 Toshiba Corp Loosely-coupled computer system
JP2004046372A (en) * 2002-07-09 2004-02-12 Nippon Telegr & Teleph Corp <Ntt> Distributed system, resource allocation method, program, and recording medium with which resource allocation program is recorded
JP2011018198A (en) * 2009-07-09 2011-01-27 Hitachi Ltd Management device and management method

Similar Documents

Publication Publication Date Title
US10657061B1 (en) Resource distribution using attributes of versioned hash rings
US11461329B2 (en) Tracking query execution status for selectively routing queries
US11494380B2 (en) Management of distributed computing framework components in a data fabric service system
US9971823B2 (en) Dynamic replica failure detection and healing
US10338958B1 (en) Stream adapter for batch-oriented processing frameworks
US9276959B2 (en) Client-configurable security options for data streams
US20180089312A1 (en) Multi-layer partition allocation for query execution
US20180089258A1 (en) Resource allocation for multiple datasets
KR101221205B1 (en) Method and apparatus for collecting data for characterizing http session workloads
JP5244236B2 (en) Computer system, method, and program
JP4428483B2 (en) Information processing apparatus, control method, program, and recording medium
CN102281190B (en) Networking method for load balancing apparatus, server and client access method
US8843632B2 (en) Allocation of resources between web services in a composite service
JP2012038152A (en) Connection management system and connection management server cooperation method in thin client system
JP5503678B2 (en) Host providing system and host providing method
EP2264601B1 (en) Integrated configuration management device, disparate configuration management device, and backup data management system
JP2016051446A (en) Calculator system, calculator, and load dispersing method and program
US11418583B2 (en) Transaction process management by dynamic transaction aggregation
JP2017091330A (en) Computer system and task executing method of computer system
US9015371B1 (en) Method to discover multiple paths to disk devices cluster wide
US20140040479A1 (en) Method for a self organizing load balance in a cloud file server network
US20180234491A1 (en) Program deployment according to server efficiency rankings
US11256440B2 (en) Method and distributed storage system for aggregating statistics
US10635997B1 (en) Finite life instances
WO2013031999A1 (en) Extraction device, system, program, and method

Legal Events

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

Ref document number: 12829044

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12829044

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP