JP5596716B2 - Resource management apparatus, resource management system, resource management method, and resource management program - Google Patents

Description

  The present invention relates to a resource management device, a resource management system, a resource management method, and a resource management program.

  In recent years, the construction and use of cloud systems are progressing rapidly. In the cloud system, resources are provided to users on demand as appropriate. For example, resources such as servers, networks, and storage are provided on demand in response to user requests. For this reason, system construction can be performed flexibly and in a short time.

  Furthermore, various technologies have been proposed in order to improve resource utilization efficiency, flexibility, and security in cloud systems. For example, an inter-cloud system has been proposed that enables the resources of a plurality of cloud systems to be used longitudinally. In addition, in order to share resources safely in a plurality of dynamically configured virtual organizations, a technique for selecting a virtualization method according to a user or a policy has been proposed. Furthermore, a load balancing technique for improving the utilization efficiency of the computation nodes has been proposed.

Kadoo Hado, Hu Hiroshi, Yuichi Murata, Junichi Murayama, “Proposal of System Architecture for Intercloud”, IEICE Technical Report, IEICE Technical Report, 110 (449), 151-156, 2011-02 -24, The Institute of Electronics, Information and Communication Engineers Shogo Ogura, Kenji Kono, Kei Matsuoka, Hideki Nakata, “Examination of Job Execution on VM in Grid Environment”, Information Processing Society of Japan Research Report, Computer Architecture Study Group Report 2004 (20), 25-30, 2004-03 -01, Information Processing Society of Japan Tachibana Maki, Nakada Hideki, Matsuoka Satoshi, "MPI execution environment for load balancing using virtual machines", IEICE Technical Report, IEICE Technical Report, 105 (225), 7-12, 2005- 07-28, The Institute of Electronics, Information and Communication Engineers

  However, in the conventional technology, it has been impossible for a user to easily combine and use resources having different providers.

  The disclosed technology has been made in view of the above, and includes a resource management device, a resource management system, a resource management method, and a resource management program that enable easy use of resources of different providers The purpose is to provide.

  In order to solve the above-described problems and achieve the object, the present invention receives a connection relationship between each of a plurality of resources requested by the user from a user terminal, and a plurality of cloud systems for the user. Allocation information is determined, correspondence information indicating correspondence between the connection relationship and the connection relationship between the allocation resources is generated, and the correspondence information is output to the terminal.

  According to the resource management device, the resource management system, the resource management method, and the resource management program to be disclosed, there is an effect that it is possible to easily combine and use resources of different providers.

FIG. 1 is a diagram illustrating an example of the configuration of the intercloud server according to the first embodiment. FIG. 2 is a diagram illustrating an example of a relationship among the management apparatus, resources, and user terminals according to the first embodiment. FIG. 3A is a schematic diagram illustrating an example of information stored in the storage unit of the intercloud server according to the first embodiment. FIG. 3-2 is a schematic diagram illustrating information stored in the storage unit of the intercloud server according to the first embodiment. FIG. 4 is a flowchart illustrating an example of a flow of resource allocation processing at the time of a new allocation request in the intercloud server according to the first embodiment. FIG. 5 is a flowchart illustrating an example of a flow of resource allocation processing at the time of request for expansion / reduction in the intercloud server according to the first embodiment. FIG. 6 is a flowchart illustrating an example of a flow of resource allocation processing at the time of an excess / deficiency determination request in the intercloud server according to the first embodiment. FIG. 7 is a flowchart illustrating an example of a processing flow when an allocation abolition request is made in the intercloud server according to the first embodiment. FIG. 8 is a schematic diagram of an intercloud server according to the second embodiment. FIG. 9 is a diagram illustrating an example of service configuration information according to the second embodiment. FIG. 10 is a diagram illustrating an example of attribute information of calculation resources included in the service configuration information according to the second embodiment. FIG. 11 is a diagram illustrating an example of storage resource attribute information included in the service configuration information according to the second embodiment. FIG. 12 is a diagram illustrating an example of network resource attribute information included in the service configuration information according to the second embodiment. FIG. 13 is a diagram illustrating an example of resource allocation information according to the second embodiment. FIG. 14 is a diagram illustrating an example of resource / service configuration information according to the second embodiment. FIG. 15 is a diagram for explaining processing at the time of new allocation in the second embodiment. FIG. 16 is a diagram for explaining processing at the time of expansion / reduction in the second embodiment. FIG. 17 is a diagram for explaining a process at the time of excess / deficiency determination in the second embodiment. FIG. 18 is a diagram for explaining processing at the time of abolition of allocation in the second embodiment. FIG. 19 is a diagram illustrating that the information processing by the resource management program, which is a program for executing a series of processes by the intercloud server, is specifically realized using a computer.

  Hereinafter, embodiments of a resource management device, a resource management system, a resource management method, and a resource management program to be disclosed will be described in detail based on the drawings. Note that the disclosed invention is not limited to the embodiments. Moreover, each Example can be combined suitably.

  FIG. 1 is a diagram illustrating an example of the configuration of the intercloud server according to the first embodiment. Hereinafter, the intercloud server is also referred to as a resource management device. The intercloud is realized by cooperation of a plurality of cloud systems, and enables the resources provided by each cloud system to be used longitudinally. Here, the intercloud is realized by linking systems such as a private cloud and a public cloud. However, the present invention can be applied not only to a so-called intercloud but also to an arbitrary system realized by linking a plurality of systems that individually manage resources. In FIG. 1, the intercloud server 100 is connected to a management device 200 and a user terminal 300. The management device 200 and the user terminal 300 are each connected to the resource 400.

  The intercloud server 100 allocates the resource 400 managed by the management apparatus 200 to the user terminal 300 in response to various requests from the user terminal 300. When the intercloud server 100 allocates a plurality of resources 400 to the user terminal 300, the connection relationship information regarding the connection relationship between the plurality of resources included in the request from the user terminal 300, and the plurality of resources 400 that are actually allocated. Correspondence information indicating the correspondence with the connection relationship is generated. Then, the intercloud server 100 notifies the user terminal 300 of the generated correspondence information.

  For example, when the intercloud server 100 receives a new allocation request from the user terminal 300, the intercloud server 100 collects information on the usage status of the resource 400 from the management device 200 in response to the new allocation request. Here, collection means issuing a notification requesting predetermined information, receiving and collecting information corresponding to the notification. That is, the intercloud server 100 issues a notification requesting information regarding the usage status of the resource 400 to the management apparatus 200. And the management apparatus 200 produces | generates the information according to notification, and transmits to the inter cloud server 100. FIG. The intercloud server 100 receives and accumulates information transmitted from the plurality of management devices 200. Based on the information collected in this way, the intercloud server 100 determines a resource 400 to be allocated to the user terminal 300. Then, the intercloud server 100 instructs the management apparatus 200 to allocate the resource 400. Furthermore, the intercloud server 100 generates correspondence information indicating the correspondence between the connection relationship information included in the new allocation request and the connection relationships between the plurality of resources 400 that are actually allocated. Then, the generated correspondence information is transmitted to the user terminal 300.

  In addition, when the intercloud server 100 receives an expansion / reduction request from the user terminal 300, the intercloud server 100 collects information on the usage status of the resource 400 from the management apparatus 200 in response to the expansion / reduction request. That is, the intercloud server 100 collects information on the resource usage status of each management device 200 by transmitting a notification requesting information to the management device 200 and receiving the usage information generated by the management device 200. To do. Based on the information collected in this way, the intercloud server 100 determines a resource 400 to increase / decrease the allocation to the user terminal 300. Then, the intercloud server 100 instructs the management apparatus 200 to allocate or release the resource 400. When the expansion / reduction request involves a change in the connection relationship between resources, the intercloud server 100 further connects the connection relationship information included in the expansion / reduction request and the connection relationship between the expanded / removed resources 400. Correspondence information (see FIG. 3-2 described later) is generated. Then, the generated correspondence information is transmitted to the user terminal 300.

  The expansion / reduction request may always include connection relation information, or may include connection relation information only when the connection relation between requested resources changes. When the expansion / reduction request always includes connection relation information, the intercloud server 100 always generates correspondence information and transmits it to the user terminal 300 regardless of whether the connection relation information is changed. Also good. Alternatively, the connection relation information is stored in the storage unit 110 to be described later at the time of a new allocation request, and the intercloud server 100 reads the connection relation information from the storage unit 110 at the subsequent expansion / reduction request, You may compare with the connection relation information contained in a reduction request. Then, correspondence information may be generated and transmitted to the user terminal 300 only when the connection relation information is changed.

  Further, when the expansion / reduction request includes the connection relationship information only when the connection relationship information is changed, the intercloud server 100 determines whether the expansion / reduction request includes the connection relationship information. It may be determined. In this case, the intercloud server 100 generates correspondence information and transmits it to the user terminal 300 only when it is determined that the connection relation information is included.

  Further, when the intercloud server 100 receives an excess / deficiency determination request from the user terminal 300, the intercloud server 100 collects information on the usage status of the resource 400 from the management device 200 in response to the excess / deficiency determination request. That is, the intercloud server 100 collects information on the resource usage status of each management device 200 by transmitting a notification requesting information to the management device 200 and receiving the usage information generated by the management device 200. To do. Based on the collected information, the intercloud server 100 determines whether the resources allocated to the user terminal 300 are excessive or insufficient. In the case of the excess / deficiency determination, the intercloud server 100 may notify the user terminal 300 only of the excess / deficiency determination result. Further, as a result of occurrence of excess or deficiency, when it is determined that it is desirable to change the connection relationship of the allocated resource 400, correspondence information corresponding to the changed connection relationship may be notified together.

  Note that the excess / deficiency determination may be performed when an excess / deficiency determination request is received from the user terminal 300, or may be determined in advance by providing a clock in the intercloud server 100 in advance for each predetermined period. . In any case, the excess / deficiency determination may be performed.

  Furthermore, when the intercloud server 100 receives an allocation abolition request from the user terminal 300, the intercloud server 100 instructs the corresponding management apparatus 200 to release the resources allocated to the user terminal 300. At the time of abolition of allocation, new resource usage information may be collected, resource allocation to other user terminals may be adjusted, and new allocation resources and correspondence information may be transmitted as appropriate. Then, no particular adjustment is performed, and the resource allocation may be adjusted together with the excess / deficiency determination.

  Here, although it has been described that various requests from the user terminal 300 include connection relation information regarding the connection relation between a plurality of requested resources, the connection relation information may be transmitted separately from the request itself. Good.

  The management device 200 is connected to the intercloud server 100 and the resource 400. The management device 200 manages the resource 400. In addition, the management apparatus 200 collects information regarding the usage status of the resource 400 in response to a request from the intercloud server 100. That is, the intercloud server 100 collects information on the resource usage status of each management device 200 by transmitting a notification requesting information to the management device 200 and receiving the usage information generated by the management device 200. To do. One resource 400 may be managed by one management apparatus 200, or a plurality of resources 400 may be managed together by one management apparatus 200. Moreover, you may provide another management apparatus 200 for every resource of a different kind. For example, in one cloud system, one management apparatus may manage network resources, and another management apparatus may manage calculation resources. Further, different cloud system resources 400 may be managed by different management devices 200, and different cloud system resources 400 may be managed collectively by one management device 200. Furthermore, the management apparatus 200 may manage the resources 400 in units of data centers in which the resources 400 of a plurality of servers are aggregated. In FIG. 1, one management apparatus 200 is provided for each resource of different cloud systems.

  Upon receiving a request from the intercloud server 100, the management apparatus 200 collects information on the usage status of the resource 400 to be managed and notifies the intercloud server 100 in response to the request. For example, the management apparatus 200 collects free resource information indicating the free status of the resource 400 and usage status information indicating the usage status of the resource 400 and notifies the intercloud server 100 of the collected free resource information.

  Further, the management apparatus 200 receives the allocation notification or the allocation abolition notification from the intercloud server 100, and allocates a new resource 400 to the user terminal 300 or releases the previously allocated resource 400. In addition, the management device 200 receives an increase / decrease notification from the intercloud server 100 and increases / decreases the resource 400 to be allocated to the user terminal 300. For this purpose, the management apparatus 200 includes an assignment unit 201. The allocation unit 201 allocates the resource 400 to the user terminal 300 according to the content of the notification from the intercloud server 100, releases the allocated resource, and increases or decreases the allocated resource.

  The user terminal 300 is, for example, an ASP (Application Service Provider) operator's terminal. The user who operates the user terminal 300 determines the number of requested resources and the configuration of resources according to the contents of the service to be provided, and sends a new allocation request for requesting resource allocation to the intercloud server 100. In addition, after the resource is once allocated, the user terminal 300 sends an increase / decrease request for increasing / decreasing the resource to the intercloud server 100. In addition, the user terminal 300 sends an excess / deficiency determination request to the intercloud server 100 for requesting to determine whether there is an excess or deficiency in the resources once allocated. Further, the user terminal 300 sends an allocation cancellation request for requesting allocation cancellation of the allocated resource to the intercloud server 100. Note that the intercloud server 100 is configured to perform resource excess / deficiency determination at regular intervals and reallocate resources as necessary even if there is no request from the user terminal 300 after the resource allocation. Also good.

  The resource 400 is a resource used in the intercloud system. For example, computing resources, storage resources, network resources, and the like correspond to resources. For example, examples of the computing resource include a virtual machine, a server, a CPU (Central Processing Unit), a memory, and a disk. Storage resources include storage devices and the like. Furthermore, examples of network resources include a network, a local area network (LAN), a wide area network (WAN), an optical fiber, an optical path, an IP network, an Ethernet (registered trademark), a tunnel network, and the like.

  With reference to FIG. 2, the relationship among the management apparatus, resources, and user terminals in the first embodiment will be described in more detail. FIG. 2 is a diagram illustrating an example of a relationship among a management apparatus, resources, and user terminals according to the first embodiment.

  In FIG. 2, the inter-cloud server 100 is connected to six management apparatuses 200-1 to 200-6 that manage resources of a plurality of cloud systems. The management devices 200-1 to 200-3 manage the servers 401-1 to 401-3, the servers 401-4 to 401-6, and the servers 401-7 to 401-9 as resources, respectively. In addition, the management devices 200-4 to 200-6 manage the networks 402-1, 402-2, and 402-3 as resources, respectively. The user terminals 300-1 to 300-3 are connected to the resources used by each. For example, the user terminal 300-1 is connected to a server 401-7 managed by the management apparatus 200-3 via a network 402-1 managed by the management apparatus 200-4. The user terminal 300-2 is connected to the server 401-5 managed by the management apparatus 200-2 and the server 401-9 managed by the management apparatus 200-3 via the network 402-2 managed by the management apparatus 200-5. Is done. The user terminal 300-3 is connected to the server 401-1 managed by the management device 200-1 and the server 401-6 managed by the management device 200-2 via the network 402-3 managed by the management device 200-6. Is done.

  Although not shown in FIG. 2, each user terminal 300-1 to 300-3 is connected to the intercloud server 100, and makes a new resource allocation request to the intercloud server 100. In response to the new allocation request, the intercloud server 100 collects free resource information and usage status information from the management devices 200-1 to 200-6. And the intercloud server 100 determines the resource allocated to each user terminal 300-1 to 300-3 based on the collected vacant resource information and utilization status information. Further, the intercloud server 100 issues a resource allocation notification to the corresponding management apparatus, and the corresponding management apparatus allocates resources to the user terminals 300-1 to 300-3 according to the allocation notification. Further, the intercloud server 100 generates correspondence information between the connection relation information included in the new assignment request and the connection relation of the assigned resources, and transmits the correspondence information to the user terminals 300-1 to 300-3. As a result, the user terminals 300-1 to 300-3 can appropriately configure resources according to requests and use the resources.

  As described above, the inter-cloud server 100, the plurality of management devices 200-1 to 200-6 that manage the servers 401-1 to 401-9 and the networks 402-1 to 402-3, which are resources of a plurality of cloud systems, Connect. Then, it is possible to appropriately allocate various types of resources of different cloud systems to user terminals by collectively collating the free resource information and usage status information collected from each management device with a new allocation request for user terminals. it can. For this reason, the user terminal can use the resources of the plurality of cloud systems in a simple combination without being aware of the resources of the plurality of cloud systems.

  Further, the intercloud server 100 generates correspondence information indicating correspondence between the connection relation information included in the request from the user terminal 300 and the connection relation of the allocated resource 400 and transmits the correspondence information to the user terminal 300. For this reason, the user terminal 300 can appropriately configure and use the resource 400 without having to determine the configuration of the resource 400 by itself.

[Configuration of Intercloud Server According to Embodiment 1]
Returning to FIG. 1, the configuration of the intercloud server 100 according to the first embodiment will be described in more detail. As shown in FIG. 1, the intercloud server 100 includes a communication unit 101, a storage unit 110, and a control unit 120. The communication unit 101 communicates with the intercloud server 100 and an external device. In FIG. 1, the communication unit 101 receives information from the management device 200 and the user terminal 300, and transmits information output from the functional unit in the intercloud server 100 to the management device 200 and the user terminal 300. The storage unit 110 stores information used for processing in the intercloud server 100 and information generated as a result of the processing. For example, the storage unit 110 stores a resource restriction condition to be included, which is included in a new allocation request transmitted from the user terminal 300. The control unit 120 controls information collection processing from the management apparatus 200 and resource allocation processing to the user terminal 300. Details of processing in the storage unit 110 and the control unit 120 will be described in more detail below.

[Configuration of storage unit]
The storage unit 110 stores information used for processing in the intercloud server 100 and information generated as a result of the processing. In the example of FIG. 1, the storage unit 110 includes a correspondence information storage unit 111. The correspondence information storage unit 111 creates a correspondence between the connection relation information included in the new assignment request and the connection relation of the assigned resources, which is generated when the intercloud server 100 assigns the resource 400 in response to the new assignment request from the user terminal 300. Is stored. Although only the correspondence information storage unit 111 is shown in FIG. 1, the storage unit 110 may include a functional unit that stores other information. For example, you may provide the memory | storage part which memorize | stores the information regarding the type, number, attribute, etc. of the resource requested | required included in the new allocation request | requirement from the user terminal 300. FIG. Moreover, you may provide the memory | storage part which memorize | stores the vacant resource information and usage status information which are transmitted from the management apparatus 200. FIG.

  An example of information stored in the storage unit 110 will be described with reference to FIG. FIG. 3A is a schematic diagram illustrating an example of information stored in the storage unit 110 of the intercloud server 100 according to the first embodiment. As illustrated in FIG. 3A, the storage unit 110 associates with each user terminal 300 a user ID that uniquely identifies the resource being used by the user terminal, and the resource constraint conditions requested by the user terminal The correspondence information indicating the correspondence between the connection relationship between the resources requested by the user terminal and the allocated resource is stored. The storage information illustrated in FIG. 3A is an example, and other information may be stored in the storage unit 110.

  3-1, for example, the user ID “001” uniquely indicating the user terminal 300-1 in FIG. 2 is associated with the identifier “N01” of the network 402-1 as the “resource in use” and the server 401. The identifier “S07” of −7 is stored. Further, the network bandwidth “150 Mbps” and the delay “10 ms” are stored as “resource constraint conditions”. Furthermore, the server location “Tokyo” is stored as the “resource constraint condition”. Furthermore, as “correspondence information”, the connection relationship between “network N1” and “server S1” which are resources requested by the user terminal 300-1 in the new allocation request, and “network N01” and “server S07” which are allocation resources. "Is stored as" (N1-S1) = (N01-S07) ".

  In FIG. 3A, only the network bandwidth and delay and the server location are shown as resource constraint conditions, but it goes without saying that various other resource constraint conditions can be stored. For example, information corresponding to resource attribute information to be described later can be stored as a resource constraint condition.

[Configuration of control unit]
Referring to FIG. 1 again, the configuration of the control unit 120 will be described in detail. As illustrated in FIG. 1, the control unit 120 includes a reception unit 121, an extraction unit 122, a collection unit 123, a determination unit 124, a notification unit 125, a generation unit 126, and an output unit 127. The receiving unit 121 receives a new allocation request, an allocation abandonment request, an addition / removal request, an excess / deficiency determination request, and the like transmitted from the user terminal 300 via the communication unit 101. The receiving unit 121 determines the type of received information and transmits it to the storage unit 110, the extracting unit 122, the collecting unit 123, and the notification unit 125 according to the type.

  The extraction unit 122 receives information from the reception unit 121, and extracts attribute information of resources requested by the user terminal 300 and the number of requested resources from the information. The resource attribute information is, for example, if the resource is a computational resource, processing performance (benchmark result), CPU (Central Processing Unit) type, number of CPU cores, CPU core clock, memory type, memory capacity, operation system (OS ) Type and version, application type and version, and the like. If the resource is a storage resource, its capacity, throughput, interface type, redundancy type (RAID type), and the like. If the resource is a network resource, its distance (allowable maximum value or allowable minimum value), delay (maximum delay time or average delay time), bandwidth (physical bandwidth guaranteed communication speed, maximum communication speed), packet loss rate, The starting point, the ending point, the connection form (bus, star, P2P, ring, mesh) and the like.

  The collection unit 123 collects information on the resource usage status from the management apparatus 200 in accordance with information from the user terminal 300. For example, the collection unit 123 accesses the management apparatus 200 and collects free resource information of the resources 400 managed by the management apparatus 200 and usage status information for each user. As the free resource information, for example, the total amount of resources 400 and information about resources 400 that are not allocated are collected. Further, the collection unit 123 collects the value of the usage fee of the resource 400, the attribute of the resource 400, and the like. In addition, the collection unit 123 collects information about the resources 400 that are actually used and information about the resources 400 that are not used among the allocated resources 400 as usage status information. The collected information may be stored and updated in the storage unit 110 each time.

  The determination unit 124 assigns the resource 400 to be allocated to the user terminal 300 based on the information on the resource 400 collected by the collection unit 123 and the attribute information and the number of resources requested by the user terminal 300 extracted by the extraction unit 122. Determine as. In addition, the determination unit 124 determines whether the resources allocated to the user terminal 300 are excessive or insufficient based on the information regarding the resources 400 collected by the collection unit 123 and the information stored in the storage unit 110. If it is determined that there is excess or deficiency in resources, a new allocation resource may be further determined.

  The notification unit 125 notifies the management apparatus 200 of the allocation resource determined by the determination unit 124 via the communication unit 101 and instructs to execute the allocation. In addition, when the determination unit 124 determines that the resource is excessive or insufficient, the notification unit 125 notifies the user terminal 300 of the excess / deficiency determination result. Furthermore, when a new allocation resource is determined as a result of excess or deficiency, the notification unit 125 notifies the management apparatus 200 of the allocation resource.

  The generation unit 126 associates the connection relationship information indicating the connection relationship of the requested resource included in the request from the user terminal 300 received by the reception unit 121 with the connection relationship of the allocated resource determined by the determination unit 124. The correspondence information shown is generated. For example, information corresponding to “corresponding information” shown in FIG. The specific configuration of the correspondence information is not limited to the example of FIG. The specific structure of the correspondence information is not particularly limited as long as it is information indicating the correspondence between the connection relationship between resources requested by the user terminal 300 and the connection relationship between resources actually allocated. The correspondence information generated by the generation unit 126 is sent to the storage unit 110 and the output unit 127.

  The correspondence information will be described more specifically with reference to FIG. For example, the user has four computational resources C1, C2, C3, C4, two network resources N1, N2, one storage resource S1, and the connection relationship shown in the lower part of FIG. Suppose you request. As the allocation resources, the calculation resources C01, C02, C03, C04 realized by the data center DC1, the network resource N04, the network resource N03 realized by the WAN, and the storage resource S05 realized by the data center DC2 are allocated. Suppose that In this case, the correspondence information indicates that the calculation resources C01, C02, C03, and C04 respectively correspond to C1, C2, C3, and C4 having the connection relationship requested by the user. In addition, network resources N04 and N03 respectively correspond to N1 and N2 having a connection relationship requested by the user. The storage resource S05 corresponds to S1 requested by the user.

  The output unit 127 transmits the correspondence information generated by the generation unit 126 to the user terminal 300 via the communication unit 101. The format of the correspondence information to be transmitted is not particularly limited, but is preferably information that can be displayed graphically on the user terminal 300. For example, a diagram as illustrated in FIG. 3-2 may be displayed on the user terminal 300.

[Resource allocation processing by inter-cloud server of embodiment 1]
Next, resource allocation processing in the intercloud server 100 according to the first embodiment will be described with reference to FIGS.

[Process when new allocation is requested]
FIG. 4 is a flowchart illustrating an example of a flow of resource allocation processing at the time of a new allocation request in the intercloud server according to the first embodiment. First, the intercloud server 100 always accepts a request from the user terminal 300 while it is in an operating state. When the request from the user terminal 300 is not received (No at Step S401), the intercloud server 100 repeats Step S401.

  In the intercloud server 100, when the reception unit 121 receives a request from the user terminal 300 (Yes in step S401), it is determined whether the request is a new allocation request (step S402). If it is determined that the request is not a new allocation request (No at Step S402), the process proceeds to the process of FIG. If it is determined that the request is a new allocation request (Yes at Step S402), the extraction unit 122 extracts attribute information of the requested resource and the number of requested resources from the request (Step S403). . Next, the collection unit 123 accesses the management apparatus 200 and collects information related to the resource usage status in the intercloud system (step S404). Specifically, free resource information and usage status information are collected. Then, the determination unit 124 determines a resource to be allocated to the user terminal 300 based on the information collected by the collection unit 123 and the information extracted by the extraction unit 122 (Step S405). Then, the notification unit 125 notifies the management device 200 of the allocation resource determined by the determination unit 124 (step S406). Further, the information on the allocation resource is sent to the generation unit 126, and the generation unit 126 associates the connection relationship information indicating the connection relationship of the requested resource included in the new allocation request with the determined connection relationship of the allocation resource. Is generated (step S407). Then, the output unit 127 outputs the correspondence information generated by the generation unit 126 to the user terminal 300 (Step S408), and ends the process.

[Process when adding / removing]
Next, with reference to FIG. 5, the flow of resource allocation processing at the time of request for expansion / reduction in the intercloud server according to the first embodiment will be described. FIG. 5 is a flowchart illustrating an example of a flow of resource allocation processing at the time of request for expansion / reduction in the intercloud server according to the first embodiment.

  First, when it is determined that the request received in step S402 in FIG. 4 is not a new allocation request (No in step S402), the receiving unit 121 determines whether the request is an addition / reduction request. (Step S501). If it is determined that the request is not an addition / reduction request (No in step S501), the process proceeds to the process of FIG. If it is determined that the request is an addition / reduction request (Yes at step S501), the extraction unit 122 extracts the attribute information and the number of resources that require addition / reduction from the request (step S502). Next, the collection unit 123 accesses the management apparatus 200 and collects information regarding the resource usage status in the inter-cloud system (step S503). Then, the determination unit 124 determines a resource for adding / removing the allocation to the user terminal 300 based on the information collected by the collection unit 123 and the information extracted by the extraction unit 122 (step S504). Then, the notification unit 125 notifies the management device 200 of the allocated resource determined to be added or removed by the determination unit 124 (step S505). Further, information on the allocation resource is sent to the generation unit 126, which generates the allocation resource, information stored in the storage unit 110, information included in the addition / removal request, information collected by the collection unit 123, and the like. Based on the above, it is determined whether or not the connection relationship of the resources allocated to the user terminal 300 has changed (step S506). If the generation unit 126 determines that the connection relationship has not changed, the process ends. When the generation unit 126 determines that the connection relationship has changed, the generation unit 126 generates correspondence information between the connection relationship between the resources requested by the user terminal 300 and the connection relationship between the newly allocated resources (step). S507). Then, the output unit 127 outputs the correspondence information generated by the generation unit 126 (step S508) and ends the process.

  In the example of FIG. 5, the correspondence information is not generated / output when there is no change in the connection relationship. However, the correspondence information may be generated / output even when there is no change in the connection relationship. Good.

[Processing when excess or deficiency is judged]
Next, with reference to FIG. 6, the flow of the resource allocation process at the time of the excess / deficiency determination request in the intercloud server according to the first embodiment will be described. FIG. 6 is a flowchart illustrating an example of a flow of resource allocation processing at the time of an excess / deficiency determination request in the intercloud server according to the first embodiment.

  First, in step S501 of FIG. 5, when it is determined that the received request is not an expansion / reduction request (No in step S501), the reception unit 121 determines whether the request is an excess / deficiency determination request. Determination is made (step S601). If it is determined that the request is not an excess / deficiency determination request (No in step S601), the process proceeds to the process of FIG. When it is determined that the request is an excess / deficiency determination request (Yes in step S601), the collection unit 123 accesses the management apparatus 200 and collects information on the usage status of resources in the intercloud (step S602). Next, the determination unit 124 determines whether the resources allocated to the user terminal 300 are excessive or insufficient based on the information collected by the collection unit 123 and the information related to the user terminal 300 read from the storage unit 110 (step S603). . Here, the determination unit 124 performs the excess / deficiency determination. However, a function unit that performs the excess / deficiency determination separately from the determination unit 124 may be provided. The determination unit 124 determines whether the resource allocation is changed as a result of the excess / deficiency as a result of the excess / deficiency (step S604). Then, the notification unit 125 notifies the management device 200 of the allocated resource (step S605). Further, the determination unit 124 determines whether or not there is a change in the correspondence information between the connection relationship of the resource requested by the user terminal 300 and the connection relationship of the allocation resource as a result of the allocation change (step S606). When there is no change in the correspondence information (No at Step S606), the notification unit 125 notifies the user terminal 300 of the excess / deficiency determination result (Step S609) and ends the process. When there is a change in the correspondence information (Yes in step S606), the generation unit 126 generates new correspondence information (step S607), and the output unit 127 outputs the correspondence information to the user terminal 300 (step S608). ) Finish the process.

  In the example of FIG. 6, the determination unit 124 determines whether or not the allocation change is necessary together with the excess / deficiency determination, and determines a new allocation resource as necessary. However, at the time of excess / deficiency determination, it is possible to output the excess / deficiency determination result and finish the process without changing allocation or determining a new allocation resource. Further, it is possible to always transmit the correspondence information without determining whether or not the correspondence relationship is changed.

[Process when allocation is abolished]
Next, with reference to FIG. 7, the flow of the resource allocation process at the time of allocation abolition request in the intercloud server according to the first embodiment will be described. FIG. 7 is a flowchart illustrating an example of a processing flow when an allocation abolition request is made in the intercloud server according to the first embodiment.

  First, in step S601 in FIG. 6, when it is determined that the received request is not an excess / deficiency determination request (No in step S601), the reception unit 121 determines whether the request is an allocation abolition request. (Step S701). If it is determined that the request is not an allocation abolition request (No in step S701), the process ends. When it is determined that the request is an allocation abolition request (Yes in step S701), the notification unit 125 transmits an allocation abolition notification to the management apparatus 200 (step S702). And the information in the memory | storage part 110 stored corresponding to the user terminal 300 which issued the allocation abolition request | requirement is updated (step S703), and a process is complete | finished.

  In addition, when allocation is abolished, resource allocation allocated to other users may be reviewed and new allocation resources and correspondence information may be notified to each user.

  As described above, when a new allocation request, an expansion / reduction request, or an excess / deficiency determination request is received, the intercloud server 100 appropriately determines the connection relationship between the resources 400 allocated to the user terminal 300 that issued the request, and the user terminal. Correspondence with the connection relation between resources requested by 300 is determined and correspondence information is generated. Then, the generated correspondence information is transmitted to the user terminal 300. For this reason, in the user terminal 300, it is not necessary for the user to determine the connection relationship of the allocated resources, and it is possible to easily construct a service using the resource and use the resource.

[Effect of Example 1]
As described above, according to the first embodiment, the intercloud server 100 receives a request including information related to a connection relationship between resources that the user terminal 300 requests allocation from the user terminal 300. Then, an allocation resource is determined in response to the request, and the management apparatus 200 that manages the resource 400 is notified to allocate the resource 400 to the user terminal 300. Furthermore, the intercloud server 100 generates correspondence information indicating the correspondence between the connection relationship between the allocated resources and the connection relationship between the resources requested by the user terminal 300. Then, the generated correspondence information is transmitted to the user terminal 300. For this reason, the user of the user terminal 300 can easily combine and use the resources 400 having different providers. In addition, since the user of the user terminal 300 can determine which requested resource corresponds to which allocated resource based on the correspondence information, the user terminal 300 determines by itself how to configure the allocated resource. Therefore, it is possible to easily configure the allocated resource and provide the service.

  In addition, according to the first embodiment, the intercloud server 100 also accepts a resource addition / removal request from the user terminal 300, and connection relations and allocations between resources requested from the user terminal 300 as necessary. Correspondence information indicating the correspondence with the resource connection relationship is transmitted to the user terminal 300. Therefore, the user can easily configure the allocated resource and provide the service.

  Further, according to the first embodiment, the inter-cloud server 100 can systematically collect the usage status of resources provided by a plurality of cloud systems and allocate resources to the user terminals 300. Therefore, the user can easily configure the allocated resource and provide the service without being aware of the complicated configuration of the inter-cloud system including a plurality of cloud systems.

  In the second embodiment, details of the intercloud server will be further described. In the second embodiment, a case where a program installed in the inter-cloud server 500 executes a series of processes to allocate resources provided by different cloud systems will be described. More specifically, the case where the intercloud server 500 allocates network resources and data center resources will be described.

  In the following description, the resource provided by the cloud system is assigned to an ASP (Application Service Provider) operator and the user uses a service provided by the ASP operator.

  FIG. 8 is a schematic diagram of an intercloud server according to the second embodiment. The inter-cloud server 500 according to the second embodiment collects information indicating the resource status for each cloud system that provides data center resources and network resources, and allocates resources belonging to different cloud systems to the ASP operator. For example, the inter-cloud server 500 according to the second embodiment supports migration such as scale-out by providing a combination of resources provided by different cloud systems.

  The intercloud server according to the second embodiment includes a constraint condition database (DB) 511 that stores conditions related to resource allocation, and a management information DB 512 that stores management information related to resources. The constraint condition DB 511 and the management information DB 512 correspond to the storage unit 110 included in the intercloud server 100 according to the first embodiment.

  The constraint condition DB 511 stores a user ID that identifies an ASP operator to whom resources provided by the intercloud system are assigned and information (hereinafter also referred to as a constraint condition) related to the resource requested by the ASP operator. To do. For example, the constraint condition DB 511 stores service configuration information, resource allocation information, resource / service configuration information, and the like described below.

  The management information DB 512 stores management information about a management device that manages resources. For example, management information about DC-OPS 603-1 is stored, and management information about NW-OPS 604-1 is stored. The management information corresponds to, for example, an identification name of the management device, a URL used when accessing the management device, and a password used when accessing the management device.

  In the example shown in FIG. 8, in addition to the intercloud server 500, an operator terminal 601, an ASP terminal 602, DC-OPS (Data Center-Operation System) 603-1 to 603-4, and NW-OPS (Network- Operation System) 604-1 to 604-4, DC (Data Center) 605-1 to 605-4, R (Router) 606-1 to 606-4, and user terminal 607-1 607-3.

  The operator terminal 601 is connected to the intercloud server 500. The operator terminal 601 is used by an operator who manages the intercloud server 500. The operator terminal 601 has a web browser. For example, the operator terminal 601 displays an interface for performing setting, operation, management, and the like of the intercloud server 500 on the Web browser.

  The ASP terminal 602 is connected to the intercloud server 500. The ASP terminal 602 is used by an ASP operator who provides a service using resources provided by the cloud system. The ASP terminal 602 has a web browser. For example, the ASP terminal 602 displays an interface for performing setting, operation, management, and the like of the intercloud server 500 on the Web browser.

  R606-1 to 606-4 are connected to NW-OPSs 604-1 to 604-4, DC 605-1 to 605-4, and user terminals 607-1 to 607-3. R606-1 to 606-4 are network devices, for example, routers. R606-1 to 606-4 form a network. DC 605-1 to 605-4 and user terminals 607-1 to 607-3 are connected by a network 608 formed by R606-1 to 606-4, and each of a plurality of DCs 605-1 to 605-4 is connected. Connected. R606-1 to 606-4 are managed by the NW-OPSs 604-1 to 604-4.

  The DCs 605-1 to 605-4 are connected to the DC-OPSs 603-1 to 603-4 and R606-1 to 606-4. The DCs 605-1 to 605-4 provide a virtual machine service. The DCs 605-1 to 605-4 are managed by the DC-OPSs 603-1 to 603-4. Note that a virtual machine (VM) indicates a virtual PC provided by software.

  The DC-OPSs 603-1 to 603-4 are connected to the intercloud server 500 and the DCs 605-1 to 605-4. The DC-OPSs 603-1 to 603-4 are management devices that manage the resources of the DCs 605-1 to 605-4. Specifically, the DC-OPSs 603-1 to 603-4 grasp the usage status information of the DCs 605-1 to 605-4 for each ASP operator, and grasp the free resource information of each of the DCs 605-1 to 605-4. To do. For example, the DC-OPS 603-1 manages one or more DCs among the DCs 605-1 to 605-4.

  The NW-OPSs 604-1 to 604-4 are connected to the intercloud server 500 and R606-1 to 606-4. NW-OPSs 604-1 to 604-4 are management devices that manage R606-1 to 606-4. Specifically, the NW-OPSs 604-1 to 604-4 grasp the usage status information of the network 608 for each ASP operator regarding the network 608 formed by the R606-1 to 606-4, and R606-1 The free resource information is grasped about the network 608 formed by 606-4. For example, the NW-OPS 604-1 manages one or more Rs out of R606-1 to 606-4.

  In the example shown in FIG. 8, for convenience of explanation, there is one operator terminal, one ASP terminal, four DC-OPS, four NW-OPS, four DC, and R The case where there are four and three user terminals is shown. However, it is not limited to this, The number of each apparatus may be arbitrary. For example, there may be two or more ASP terminals, and the number of DC-OPS, NW-OPS, DC, R, etc. may be three or less, or five or more.

  In the example illustrated in FIG. 8, the case where the operator terminal 601, the ASP terminal 602, and the user terminal 607 are separate devices is illustrated as an example, but the present invention is not limited to this. For example, any one of the operator terminal 601, the ASP terminal 602, and the user terminal 607 may be combined into one device.

  The intercloud server 500 has various hardware, and various programs such as OS and middleware are installed in advance. Specifically, as will be described in detail later, the intercloud server 500 includes an ICS software 501, an RAF (resource requirement estimation algorithm) 502, and the like as programs executed by various hardware included in the intercloud server 500. Execute.

  The ICS software 501 executes processing executed by each unit of the control unit 120 in the first embodiment. Further, the RAF 502 estimates the resource requirements of resources recommended to be allocated to the ASP operator based on the usage status information and the constraint conditions for the resources allocated to the ASP operator. For example, the RAF 502 estimates the resource amount required by the ASP operator by analyzing the usage status information, and estimates the resource requirement that satisfies the estimated resource amount according to the constraint condition. In addition, the estimation process by RAF502 may use arbitrary methods. Further, the method used for resource allocation is not particularly limited, and any method may be used.

  Further, the ICS software 501 in the second embodiment accepts input of service configuration information from the ASP terminal 602, as will be described later. Then, the resource attribute information requested by the ASP terminal 602 and the number of resources are extracted from the service configuration information. And the information regarding DC605-1 to 605-4 and R606-1 to 606-4 which are resources is collected from DC-OPS 603-1 to 603-4 and NW-OPS 604-1 to 604-4. Then, a resource to be allocated to the ASP terminal 602 is determined based on the attribute information and number of the extracted resources and the collected information. The determined allocation resource is notified to the system that manages the allocation resource among DC-OPS 603-1 to 603-4 and NW-OPS 604-1 to 604-4. Then, correspondence information indicating the correspondence between the connection relationship between resources included in the service configuration information input from the ASP terminal 602 and the determined connection relationship with the allocated resource is generated. The ICS software 501 further generates resource / service configuration information including the generated correspondence information, service configuration information, and resource allocation information, and transmits the resource / service configuration information to the ASP terminal 602. In the ASP terminal 602, the transmitted information can be schematized and viewed on a web browser.

  Details of various data used in the second embodiment, such as service configuration information, resource allocation information, and resource / service configuration information, will be described later.

  In the following, the case where the RAF 502 is a program installed in the same computer as the ICS software 501 will be described. However, the RAF 502 is not limited to this, and may be installed in a computer different from the ICS software 501 or may be a device separate from the intercloud server 500.

[Example of data structure of various data used in Embodiment 2]
The data structure of various data used in the second embodiment will be described below.

[Example of service configuration information]
The intercloud server 500 according to the second embodiment accepts input of service configuration information from the ASP terminal 602. An example of the structure of service configuration information will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of service configuration information according to the second embodiment. The service configuration information is information defined by the user of the ASP terminal 602. The service configuration information is information that is included in, for example, a new resource allocation request or expansion / reduction request in the first embodiment and includes connection relation information. The user of the ASP terminal 602 can input service configuration information from a screen displayed on the Web browser of the ASP terminal 602, for example.

  As illustrated in FIG. 9, the service configuration information includes “resource type”, “number of resources”, “connection relationship between resources”, and “resource attributes”. The “resource type” is information indicating the type of resource, such as “calculation”, “storage”, “network”, and the like. The “number of resources” is the number of requested resources for each resource type. The “connection relationship between resources” is information indicating how to connect a plurality of requested resources. The “resource attribute” is information indicating a resource attribute predetermined for each resource type. For example, in the case of calculation resources, the CPU type, the number of CPU cores, and the like. In the case of a storage resource, the capacity, throughput, and the like. In the case of network resources, the bandwidth, delay, and the like. Details of the attribute information are not shown in FIG. The attribute information will be described in more detail later with reference to FIGS.

  The service configuration information received by the intercloud server 500 is stored in, for example, the constraint DB 511 illustrated in FIG. The constraint DB 511 stores service configuration information in association with a user ID that uniquely identifies the ASP terminal 602. For example, in the example of FIG. 9, information about each of calculation resources, storage resources, and network resources required by the ASP terminal 602 identified by the ID is stored in association with the user ID “001”. For example, as indicated by “number of resources”, the user with the user ID “001” requests three computational resources, three storage resources, and two network resources. Further, “connection relation between resources” is stored for each resource in association with the user ID “001”. For example, connection information “C1 (S1, R1), C2 (S2, R1, R2), C3 (S3, R2)” for the three computational resources C1, C2, C3 requested by the user with the user ID “001”. Is memorized. This connection information indicates that the calculation resource C1 is connected to the storage resource S1 and the network resource R1. In addition, the calculation resource C2 is connected to the storage resource S2 and the network resources R1 and R2. In addition, the calculation resource C3 is connected to the storage resource S3 and the network resource R2.

  Further, the constraint DB 511 stores information on the attribute of each resource requested by the ASP terminal 602 with the user ID “001” as “resource attribute”. For example, when three calculation resources are requested, the request resource IDs “C1”, “C2”, and “C3” are automatically given to each calculation resource, and the information of each “resource attribute” is the request resource ID. Are stored in association with each other. The attribute information will be described later.

[Details of resource attribute information]
When receiving the service configuration information, the ICS software 501 extracts “resource attributes” and “number of resources” included in the service configuration information. The “resource attribute” included in the service configuration information is also referred to as resource attribute information. Hereinafter, resource attribute information will be described.

  As described below, there are various types of resource attribute information. However, when the ASP terminal 602 transmits service configuration information, it is not necessary to input information regarding all attributes described below. For example, only attributes predetermined by the intercloud system may be displayed on the Web browser of the ASP terminal 602, and the ASP operator may select the attributes using a pull-down menu or the like. Further, the ASP operator may arbitrarily designate only the attribute that is particularly desired to be designated. Alternatively, a combination of attributes predetermined by the intercloud system may be displayed on the Web browser of the ASP terminal 602, and the ASP operator may select an appropriate attribute combination from the displayed options.

[Attribute information common to each resource]
Resource price information common to all types of resources includes “price”, “SLA (Service Level Agreement)”, “available time”, “location”, “redundancy”, “multiplicity”, “security level”, “power consumption”, and the like. . For example, “price” is a fee generated for the use of the resource, and is “200,000 yen” or the like. “SLA” is a quality set by a communication service provider to guarantee the quality of service to a user. “Service availability: 99%”, “Average recovery time: 1 hour”, “Communication Encryption level: SSL "and the like are included. “Available time” is a time during which resources can be used, such as “9:00 to 20:00”. “Location” refers to the location of a resource, such as “Tokyo”. “Redundancy” refers to the redundancy of the resource, and is “2”, for example. “Multiplicity” refers to the multiplicity allowed by the resource, and is “5”, for example. The “security level” indicates the safety level of the resource, and is “4”, for example. “Power consumption” indicates the amount of power consumed by the resource, and is “10 W”, for example.

[Calculation resource attribute information]
In the case of a calculation resource, in addition to the above common attribute information, “processing performance (benchmark result)” “CPU type” “number of CPU cores” “CPU core clock” “memory type” “memory capacity” “OS type and OS “Version”, “Application type and version”, and the like are stored. An example of calculation resource attribute information included in the service configuration information and stored in the constraint DB 511 is shown in FIG. FIG. 10 is a diagram illustrating an example of attribute information of calculation resources included in the service configuration information according to the second embodiment.

  As an example, FIG. 10 shows attribute information of a calculation resource stored when the ASP terminal 602 with the user ID “001” requests three calculation resources in the service configuration information. Requested resource IDs “C1”, “C2”, and “C3” are automatically assigned to the three computing resources. For example, for the calculation resource with the requested resource ID “C1”, “30 seconds”, which is the time required for the predetermined processing, is stored as “processing performance (benchmark result)”. Further, “Core 7” which is the type of CPU is stored as “CPU type”. Further, “8” is stored as the “CPU core number”. Further, “3 GHz” and “16 GB” are stored as “CPU core clock” and “memory capacity”, respectively.

[Attribute information of storage resource]
In the case of a storage resource, “capacity”, “throughput”, “interface type”, “redundancy type (RAID type)”, and the like are stored in addition to the common attribute information. An example of the storage resource attribute information included in the service configuration information and stored in the constraint DB 511 is shown in FIG. FIG. 11 is a diagram illustrating an example of storage resource attribute information included in the service configuration information according to the second embodiment.

  As an example, FIG. 11 shows storage resource attribute information stored when the ASP terminal 602 with the user ID “001” requests three storage resources. Requested resource IDs “S1”, “S2”, and “S3” are automatically assigned to the three storage resources. For example, for the storage resource with the requested resource ID “S1”, “400 GB” that is the capacity required for the resource is stored as “capacity”. Further, the processing capacity “150 Mbps” is stored as “throughput”. Further, “Fiber channel” is stored as “Interface type”, and “5” is stored as “RAID type”.

[Network resource attribute information]
In the case of network resources, in addition to the above common attribute information, "distance (maximum allowable value, allowable minimum value)""delay (maximum delay time, average delay time)""bandwidth (physical bandwidth guaranteed communication speed, maximum communication) (Speed) "" packet loss rate "" starting point "" ending point "" connection type "(bus, star, P2P, ring, mesh, etc.) and the like are stored. An example of network resource attribute information contained in the service configuration information and stored in the constraint DB 511 is shown in FIG. FIG. 12 is a diagram illustrating an example of network resource attribute information included in the service configuration information according to the second embodiment.

  As an example, FIG. 12 shows network resource attribute information stored when the ASP terminal 602 having the user ID “001” requests two network resources. Request resource IDs “R1” and “R2” are automatically assigned to the two network resources. For example, for the network resource with the requested resource ID “R1”, the maximum and minimum allowable network distances are stored as “300 m, 100 m” as “distance (allowable maximum value, allowable minimum value)”. ing. As “delay (maximum delay time, average delay time)”, the maximum delay time and the average delay time in the network are stored as “10 s, 5 s”. In addition, as the “band (physical band guaranteed communication speed, maximum communication speed)”, the band of the network is stored as “250 kbps, 1 Mbps”. Further, as the “packet loss rate”, the packet loss rate “0.1%” of the network is stored.

[Structure of resource allocation information]
The ICS software 501 in the second embodiment extracts resource attribute information and the number of resources from the service configuration information received from the ASP terminal 602. Then, the DC-OPS 603-1 to 603-4 and the NW-OPS 604-1 to 604-4 are accessed to collect information on the usage status of the DC 605-1 to 605-4 and the R606-1 to 606-4. Based on the collected usage information, the resource attribute information extracted from the service configuration information, and the number of resources, resources to be allocated to the ASP terminal 602, that is, DC and R are determined.

  When the resource to be allocated is determined, the ICS software 501 generates resource allocation information. The resource allocation information is information for identifying an allocated resource including information for uniquely identifying the allocated resource. For example, an example of resource allocation information is shown in FIG.

  FIG. 13 is a diagram illustrating an example of resource allocation information according to the second embodiment. For example, as shown in FIG. 13, the resource allocation information provides the ID assigned to the resource requested by the user, the ID of the allocated resource, and the allocated resource in association with the user ID. And the merchant ID. First, the requested resource ID “C1, C2, C3, S1, S2, S3, R1, R2” for identifying the resource requested by the user terminal identified by the user ID “001” is included. Then, “allocation resource ID” is included in association with each requested resource ID. The “assigned resource ID” is an identifier (ID) that uniquely identifies the assigned resource. In the example of FIG. 13, the allocated resource ID “C001” is associated with the requested resource ID “C1”. Furthermore, “provider ID” is associated with the assigned resource ID. The “provider ID” is an identifier that uniquely identifies a supplier that provides the associated allocation resource. In the example of FIG. 13, the provider ID “N105” is associated with the allocated resource ID “C001”.

  Note that the allocated resource ID and the provider ID do not need to be configured separately, and the resource allocation information is obtained by combining one identifier for identifying the allocated resource and the provider with the requested resource ID and the user ID. Needless to say.

[Structure of resource service configuration information]
When the ICS software 501 according to the second embodiment determines the allocation resource and generates the resource allocation information, the ICS software 501 next generates the resource service configuration information.

  The resource service configuration information is information related to a correspondence between a connection relationship between desired resources presented by a terminal requesting resource allocation, such as the ASP terminal 602, and a connection relationship between resources actually allocated. It is information to include. For example, the information includes correspondence information of the first embodiment. Specifically, the resource / service configuration information includes the above-described service configuration information, resource allocation information, and correspondence information between resources in the service configuration information and allocated resources in the resource allocation information.

  The structure of the resource / service configuration information will be described with reference to FIG. FIG. 14 is a diagram illustrating an example of resource / service configuration information according to the second embodiment. Since the service configuration information included in the resource / service configuration information is the same as that shown in FIG. 9, the illustration is omitted in FIG.

  As shown in FIG. 14, in the resource / service configuration information, a user ID and various types of information are associated with each other. For example, in FIG. 14, the user ID “001” is associated with service configuration information and resource allocation information. The user ID “001” corresponds to service configuration information as shown in FIG. 9, specifically, “resource type”, “number of resources”, “connection relationship between resources”, “resource attributes”, etc. Attached. Further, the user ID “001” is associated with resource allocation information, specifically, “request resource ID”, “allocation resource ID”, and “provider ID” as shown in FIG. In this case, the correspondence information substantially corresponds to the resource allocation information in which “request resource ID” and “allocation resource ID” are associated with each other and “connection relationship between resources” is indicated in the service configuration information. -It is included in the service configuration information. For this reason, in the example of FIG. 14, the item of correspondence information is not shown separately from the service configuration information and the resource allocation information. However, as shown in FIG. 14, the configuration of the resource / service configuration information includes the resource attribute requested by the user and the connection relationship between the resources, the allocation resource information, the connection relationship of the requested resource, and the connection relationship of the allocation resource. 14 is not limited to the example shown in FIG.

[Outline of Resource Allocation Processing of Intercloud Server According to Second Embodiment]
An outline of operation of resource allocation processing by the intercloud server 500 according to the second embodiment will be described. First, an overview of operations when newly allocating resources to ASP operators, then an overview of operations when adding / removing resources allocated to ASP operators, and finally, assigning to ASP operators An outline of the operation at the time of abolition that releases a given resource will be explained in order.

[Overview of operation when newly established]
Next, with reference to FIG. 15, an outline of the operation at the time of new allocation in the second embodiment will be described. FIG. 15 is a diagram illustrating an operation outline when a resource is newly allocated to an ASP operator according to the second embodiment.

  First, a new allocation request is sent from the ASP terminal 602 to the intercloud server 500 ((1) in FIG. 15). The new allocation request includes the service configuration information shown in FIG. The intercloud server 500 that has received the new allocation request stores the constraint conditions such as the resource type, the number of resources, and the resource attributes from the request in the constraint condition DB 511. Further, the ICS software 501 of the intercloud server 500 analyzes the received new allocation request, and extracts the attributes and number of resources requested by the ASP terminal 602. Then, information related to the resource usage status is requested to a device that manages the resources of the intercloud system, such as DC-OPS 603-1, 603-2, and NW-OPS 604-1 ((2) in FIG. 15). In response to this, each device sends information on the resource usage status to the intercloud server 500. Then, the ICS software 501 calculates a resource allocation for each user and determines an allocation resource for the ASP terminal 602 ((3) in FIG. 15). Further, the ICS software 501 generates resource allocation information including an allocation resource ID that uniquely identifies the allocation resource. The generated resource allocation information is stored in the constraint condition DB 511. Then, the ICS software 501 instructs resource allocation to a device that manages the resources of the intercloud system such as the DC-OPS 603-1, 603-2, and NW-OPS 604-1 ((4) in FIG. 15). . Further, the ICS software 501 refers to the connection relationship between resources included in the service configuration information in the new allocation request transmitted from the ASP terminal 602, and generates correspondence information with the connection relationship of the allocated resources. Then, the ICS software 501 integrates the service configuration information, the resource allocation information, and the correspondence information, generates resource / service configuration information, and outputs it to the ASP terminal 602 ((5) in FIG. 15). . The generated resource / service configuration information is stored in the constraint DB 511. Then, the ICS software 501 notifies the user of the resource / service configuration information ((6) in FIG. 15).

[Overview of operation when adding / removing]
Next, with reference to FIG. 16, an outline of operation at the time of expansion / reduction in the second embodiment will be described. FIG. 16 is a diagram for explaining processing at the time of expansion / reduction in the second embodiment.

  First, the intercloud server 500 receives an expansion / reduction request from the user of the ASP terminal 602 ((1) in FIG. 16). The intercloud server 500 that has received the expansion / reduction request stores the service configuration information included in the request in the constraint condition DB 511. Then, the ICS software 501 requests information related to the resource usage status to a device that manages the resources of the intercloud system, such as the DC-OPS 603-1, 603-2, and NW-OPS 604-1 (FIG. 16). (2)). In response to this, each device sends information on the resource usage status to the intercloud server 500. Then, the ICS software 501 calculates a resource allocation for each user and determines an allocation resource for the ASP terminal 602 ((3) in FIG. 16). Further, the ICS software 501 generates resource allocation information including an allocation resource ID that uniquely identifies the allocation resource. The generated resource allocation information is stored in the constraint condition DB 511. Then, the ICS software 501 instructs resource allocation to a device that manages the resources of the intercloud system such as the DC-OPS 603-1, 603-2, and NW-OPS 604-1 ((4) in FIG. 16). . Furthermore, the ICS software 501 refers to the information stored in the constraint condition DB 511 and determines whether or not there is a change in the connection relationship between resources ((5) in FIG. 16). When the connection relationship is changed, the ICS software 501 newly generates resource / service configuration information ((6) in FIG. 16). Then, the ICS software 501 notifies the user of the generated resource / service configuration information ((7) in FIG. 16). Resource service configuration information is stored in the constraint DB 511.

  When it is determined in (5) of FIG. 16 that there is no change in the connection relationship, the processes (6) and (7) may not be performed.

[Overview of operation when determining excess or deficiency]
Next, with reference to FIG. 17, an outline of the operation at the time of excess / deficiency determination in the second embodiment will be described. FIG. 17 is a diagram for explaining a process at the time of excess / deficiency determination in the second embodiment.

  First, the intercloud server 500 receives an excess / deficiency determination request from the operator terminal 601 or the ASP terminal 602 ((1) in FIG. 17). The excess / deficiency determination request may be transmitted by the operator operating the intercloud system through the operator terminal 601 or may be transmitted from the ASP terminal 602 by the ASP operator for system management.

  Upon receiving the excess / deficiency determination request, the ICS software 501 sends information on the resource usage status to the devices managing the resources of the intercloud system, such as the DC-OPS 603-1, 603-2, and NW-OPS 604-1. Request. ((2) in FIG. 17). The requested information may be information related to the usage status of a single user or information related to the usage status of a predetermined user who uses the intercloud system, depending on the content of the excess / deficiency determination request. . In response to this, each device sends information related to the resource usage status by the designated user to the intercloud server 500.

  Then, the ICS software 501 notifies the RAF 502 of the specified user usage status and constraint conditions, and performs an excess / deficiency determination ((3) in FIG. 17). If it is determined that there is an excess or deficiency, the ICS software 501 further transmits each resource to an apparatus that manages the resources of the intercloud system such as the DC-OPS 603-1, 603-2, and NW-OPS 604-1. Information on the usage status is requested ((4) in FIG. 17).

  The ICS software 501 calculates the resource allocation for each user based on the information transmitted from each device ((5) in FIG. 17). Then, the ICS software 501 instructs resource allocation to a device that manages the resources of the intercloud system, such as the DC-OPS 603-1, 603-2, and NW-OPS 604-1 ((6) in FIG. 17). . Further, the ICS software 501 generates resource allocation information including an allocation resource ID that uniquely identifies the allocation resource. The generated resource allocation information is stored in the constraint condition DB 511. Further, the ICS software 501 refers to the information stored in the constraint condition DB 511 and determines whether or not there is a change in the connection relationship between resources ((7) in FIG. 17). When the connection relationship is changed, the ICS software 501 newly generates resource / service configuration information ((8) in FIG. 17). The ICS software 501 notifies the user of the excess / deficiency determination result and the generated resource / service configuration information ((9) in FIG. 17). Resource service configuration information is stored in the constraint DB 511.

  In FIG. 17, if there is a change in resource allocation in accordance with the excess / deficiency determination, it is determined whether there is a change in connection relationship, and resource / service configuration information is generated again. The resource allocation may not be changed, and only the excess / deficiency determination result may be transmitted to the user.

[Overview of operation when abandoned]
Next, with reference to FIG. 18, an outline of the operation at the time of abolition of allocation in the second embodiment will be described. FIG. 18 is a diagram for explaining processing at the time of abolition of allocation in the second embodiment.

  First, the intercloud server 500 receives an allocation abolition request from the ASP terminal 602 ((1) in FIG. 18). When receiving the allocation abolition request, the ICS software 501 updates the information about the ASP terminal 602 stored in the constraint DB 511 in response to the allocation abolition request. Then, information related to the resource usage status is requested to a device that manages the resources of the intercloud system, such as DC-OPS 603-1, 603-2, and NW-OPS 604-1. ((2) in FIG. 18). In response to this, each device sends information on the resource usage status to the intercloud server 500.

  The ICS software 501 calculates the resource allocation for each user based on the information transmitted from each device ((3) in FIG. 18). Then, the ICS software 501 instructs resource allocation to a device that manages the resources of the intercloud system such as the DC-OPS 603-1, 603-2, and NW-OPS 604-1 ((4) in FIG. 18). . Further, the ICS software 501 generates resource allocation information including an allocation resource ID that uniquely identifies the allocation resource. The generated resource allocation information is stored in the constraint condition DB 511. Further, the ICS software 501 refers to the information stored in the constraint DB 511 and determines whether or not there is a change in the connection relationship between resources ((5) in FIG. 18). When the connection relationship is changed, the ICS software 501 newly generates resource / service configuration information ((6) in FIG. 18). Then, the ICS software 501 notifies the user of the generated resource / service configuration information ((7) in FIG. 18). Resource service configuration information is stored in the constraint DB 511.

  In FIG. 18, when there is an allocation abolition request, the resource allocation for other users is reviewed and the resource / service configuration information is transmitted as appropriate. However, the resource redistribution is not particularly performed when the allocation abandonment request is made, and may be performed in response to another request such as an excess / deficiency determination request.

[Effect of inter-cloud server according to embodiment 2]
As described above, according to the intercloud server 500 according to the second embodiment, the correspondence information between the requested resource connection relationship and the actually allocated resource connection relationship for the user who uses the resources of the intercloud system. Are notified as resource service configuration information. For this reason, the user of the intercloud system can easily configure the allocated resource and provide the service.

  Further, the inter-cloud server 500 according to the second embodiment notifies the user of resource / service configuration information including an allocated resource ID that can uniquely identify each of the resources provided by the plurality of cloud systems. Therefore, the user can easily configure the allocated resource and provide the service without being aware of the complicated configuration of the inter-cloud system including a plurality of cloud systems.

  Also, the intercloud server 500 according to the second embodiment generates resource / service configuration information as appropriate when various requests such as a new allocation request, an expansion / reduction request, an excess / deficiency determination request, an allocation abolition request, etc. are received. Thus, the user can be notified of the resource connection relationship. For this reason, the user can be notified of the connection relation of the allocated resources as appropriate without performing special processing, and can easily configure the allocated resources and provide the service.

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in other embodiments besides the above-described embodiments. Other embodiments will be described below.

[Login function]
For example, the intercloud server may request a password when accessing. That is, the authentication process may be executed using a user name and a password at the time of login so that only an operator who is permitted at the time of using the system can log in.

[System configuration]
Also, among the processes described in this embodiment, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part of the distribution / integration may be functionally or physically distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, in the example illustrated in FIG. 1, the storage unit 110 is disposed inside the intercloud server 100, but the storage unit 110 may be connected as an external device of the intercloud server 100 via a network. In addition, for example, in the example illustrated in FIG. 1, the control unit 120 may include an excess / deficiency determination unit that determines the excess / deficiency of resources allocated to the user terminal, in addition to the determination unit 124. You may integrate with the reception part 121. FIG.

[program]
FIG. 19 is a diagram illustrating that the information processing by the resource management program, which is a program for executing a series of processes by the intercloud server, is specifically realized using a computer. As illustrated in FIG. 19, the computer 3000 includes, for example, a memory 3010, a CPU (Central Processing Unit) 3020, a hard disk drive 3080, and a network interface 3070. Each part of the computer 3000 is connected by a bus 3100.

  The memory 3010 includes a ROM 3011 and a RAM 3012 as illustrated in FIG. The ROM 3011 stores a boot program such as BIOS (Basic Input Output System).

  Here, as illustrated in FIG. 19, the hard disk drive 3080 stores, for example, an OS 3081, an application program 3082, a program module 3083, and program data 3084. In other words, the resource management program according to the disclosed technology is stored in, for example, the hard disk drive 3080 as the program module 3083 in which instructions executed by the computer are described. For example, a program module 3083 in which procedures for executing the same information processing as each unit of the control unit 120 are described is stored in the hard disk drive 3080.

  Further, like data stored in the storage unit 110, data used for information processing by the resource management program is stored as, for example, the hard disk drive 3080 as the program data 3084. The CPU 3020 reads the program module 3083 and program data 3084 stored in the hard disk drive 3080 to the RAM 3012 as necessary, and executes various procedures.

  The program module 3083 and the program data 3084 related to the resource management program are not limited to being stored in the hard disk drive 3080. For example, the program module 3083 and the program data 3084 may be stored in a removable storage medium. In this case, the CPU 3020 reads data via a removable storage medium such as a disk drive. Similarly, the program module 3083 and the program data 3084 related to the update program may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.). . In this case, the CPU 3020 reads various data by accessing another computer via the network interface 3070.

[Others]
The resource management program described in the present embodiment can be distributed via a network such as the Internet. The resource management program can also be executed by being recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, or a DVD, and being read from the recording medium by the computer.

DESCRIPTION OF SYMBOLS 100 Intercloud server 101 Communication part 110 Storage part 111 Corresponding information storage part 120 Control part 121 Reception part 122 Extraction part 123 Collection part 124 Determination part 125 Notification part 126 Generation part 127 Output part 200 Management apparatus 201 Assignment part 300 User terminal 400 Resource 500 Intercloud server 501 ICS software 511 Constraint DB
512 management information DB
601 Operator terminal 602 ASP terminal 603-1 to 603-4 DC-OPS
604-1 to 604-4 NW-OPS
607-1 to 607-3 user terminal

Claims (10)

A receiving unit that receives, from a user terminal, a connection relationship between a calculation or storage resource, which is a resource for which the user requests allocation, and a network resource that connects the resources;
A determination unit that determines allocation resources of a plurality of cloud systems for the user;
On the image diagram showing the connection relationship received by the reception unit and the connection relationship between the allocation resources determined by the determination unit for each of the resources constituting the connection relationship, the allocation resource for the resource is connected by a line. A generating unit for generating the indicated correspondence information;
An output unit that outputs the correspondence information generated by the generation unit to the terminal;
With
When the accepting unit accepts the request to increase or reduce the resource,
The determining unit determines whether or not there is a change in the connection relationship of the allocated resources determined based on the request,
When the determination unit determines that the connection relationship is changed, the generation unit generates new correspondence information .   The resource management device according to claim 1, wherein the generation unit generates the correspondence information including attribute information of a plurality of resources requested by the user.   The resource management device according to claim 1, wherein the generation unit generates the correspondence information including identification information that uniquely identifies the allocation resource determined by the determination unit.   4. The resource management apparatus according to claim 1, wherein the reception unit receives the type, number, and attributes of a plurality of resources requested by the user together with the connection relationship. A storage unit;
The resource management device according to claim 1, wherein the generation unit further stores the generated correspondence information in the storage unit. A collection unit that collects information on resource usage of multiple cloud systems;
A notification unit for notifying the resource management apparatus of the allocated resource determined by the determination unit;
Further,
The resource determination apparatus according to claim 1, wherein the determination unit determines an allocation resource to be allocated to the terminal based on information collected by the collection unit.   The resource determining apparatus according to claim 1, wherein the determining unit determines any one of a calculation resource, a storage resource, and a network resource as the allocation resource. A resource management system comprising a resource management device and a management device connected to the resource management device via a network,
The resource management device includes:
A receiving unit that receives, from a user terminal, a connection relationship between a calculation or storage resource, which is a resource for which the user requests allocation, and a network resource that connects the resources;
A determination unit that determines allocation resources of a plurality of cloud systems for the user;
On the image diagram showing the connection relationship received by the reception unit and the connection relationship between the allocation resources determined by the determination unit for each of the resources constituting the connection relationship, the allocation resource for the resource is connected by a line. A generating unit for generating the indicated correspondence information;
An output unit that outputs the correspondence information generated by the generation unit to the terminal;
With
When the accepting unit accepts the request to increase or reduce the resource,
The determining unit determines whether or not there is a change in the connection relationship of the allocated resources determined based on the request,
When the determination unit determines that there is a change in the connection relationship, the generation unit generates new correspondence information,
The management device
An allocating unit for allocating the resource determined by the resource management device;
A resource management system comprising: A resource management method executed by a resource management device,
An accepting step of receiving, from a user terminal, a connection relationship between a calculation or storage resource, which is a resource for which the user requests allocation, and a network resource that connects the resources;
Determining a plurality of cloud system allocation resources for the user;
On the image diagram showing the connection relationship received by the reception step and the connection relationship between the allocation resources determined by the determination step for each of the resources constituting the connection relationship, the allocation resource for the resource is connected by a line. A generation process for generating the indicated correspondence information;
An output step of outputting the correspondence information generated by the generation step to the terminal;
Contains
In the receiving step, when receiving an increase request or a reduction request for the resource,
In the determination step, it is determined whether there is a change in the connection relationship of the allocation resource determined based on the request,
A resource management method characterized in that , in the determination step, when it is determined that the connection relationship is changed, new correspondence information is generated in the generation step .   A resource management program for causing a computer to function as the resource management device according to claim 1.

Images