JP2015184991A - Resource management device, resource management method and resource management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce load applied to a user, and properly supply VM.SOLUTION: A resource management device 10 converts data stored in a cloud management DB group 110 into data which has a structure capable of being retrieved by a retrieval query, according to a schema conversion rule group 111. When the resource management device 10 receives designation of a VM supply policy indicating characteristic of VM operating on a computing machine resource which is required by a user from a user terminal 20, acquires the query corresponding to the policy from a VM supply policy DB 113, uses the query for retrieving with respect to the information which was converted by a schema conversion part 109, and selects a cloud service matching to the policy. Then the resource management device 10 executes creation of a virtual machine operating on a computing machine resource of the selected cloud service, start of the virtual machine, stop of the virtual machine, or delete of the virtual machine.

Description

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

  In recent years, computer virtualization technology has been developed, and cloud services that enable immediate procurement of computer resources by consolidating and operating a plurality of systems on one physical machine have become widespread. One of the characteristics of such cloud services is the cost advantage of resource aggregation. By providing a large amount of aggregated computer resources to many users, it is possible to provide computer resources at low cost. Become. However, it is standardized in order to reduce the price, and cannot respond to detailed user needs. Accordingly, in order to meet user needs, a hybrid cloud service that provides a combination of computer resources of a plurality of cloud services is conceived and attracting attention.

  For example, a cloud controller (for example, PrimeCloud Controller) that can manage multiple clouds in an integrated manner is a basic application for building and operating a hybrid cloud by centrally managing resources provided by multiple cloud services (for example, Non-patent document 1). In such a cloud controller, for example, the user himself / herself selects a VM procurement source and procures a VM in consideration of the difference in services provided by each cloud service.

Control board "PrimeCloud Controller", [online], [March 12, 2014 search], Internet <http://www.primecloud.jp/service/platform/pcc/> Global Cloud Platform Cooperation Technology Forum, [online], [March 12, 2014 search], Internet <http://www.gictf.jp/documents.html>

  However, in the above-described conventional technique, since the user selects a VM procurement destination, there is a problem that the burden on the user is large and the VM may not be procured appropriately. In other words, since it is the user himself / herself who selects the optimal VM procurement source, there is a problem that VMs must be procured in consideration of the difference in services provided by each cloud service, and the burden on the user is large.

  In addition, intercloud is known as a technique for selecting a VM procurement source by providing a computer resource by flexibly combining a plurality of cloud services and performing cooperation between cloud service providers (for example, non-patent) Reference 2). In the intercloud, a resource fitting process is defined in the protocol at the time of VM procurement, and a VM can be automatically acquired from another cloud service in response to a user request. However, since it is a collaboration between cloud service providers, the details of the VMs actually procured cannot be seen from the user, and detailed information such as service level and location is not disclosed to the user. In some cases, the matched VM cannot be procured appropriately.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and an object thereof is to appropriately procure VMs while reducing the burden on the user.

  In order to solve the above-described problems and achieve the object, the resource management apparatus of the present invention includes a storage unit that stores information about each cloud service that provides computer resources, and a search that is created based on the information about the cloud service. A policy storage unit that stores a query in association with a policy indicating the characteristics of the computer resource, and converts information stored in the storage unit into information having a structure that can be searched by the search query according to a predetermined conversion rule. When a policy specification is received by the conversion unit and the user terminal, a search query corresponding to the policy is acquired from the policy storage unit, and the information converted by the conversion unit is searched using the search query And a selection unit that selects a cloud service that matches the policy, and a cluster selected by the selection unit. Creating virtual machines running on computer resources Udo service, a virtual machine starts, stops the virtual machine, or, characterized in that and a management unit for executing deletion of the virtual machine.

  The resource management method of the present invention is a resource management method executed by a resource management device, in which the resource management device stores information regarding each cloud service that provides computer resources, and the cloud service. A policy storage unit that stores a search query created based on information related to the policy indicating the characteristics of the computer resource, and stores the information stored in the storage unit according to a predetermined conversion rule. When converting the information into a structure that can be searched by the search query, and receiving a policy specification by the user terminal, the search query corresponding to the policy is acquired from the policy storage unit, and the search query is used. A search is performed on the information converted by the conversion process, and a cloud server that matches the policy is searched. And a management process for creating a virtual machine that operates on a computer resource of a cloud service selected by the selection process, starting a virtual machine, stopping a virtual machine, or deleting a virtual machine It is characterized by including.

  The resource management device, the resource management method, and the resource management program disclosed in the present application have an effect that VMs can be appropriately procured while reducing the burden on the user.

FIG. 1 is a schematic configuration diagram showing the overall configuration of the resource management system according to the first embodiment. FIG. 2 is a diagram illustrating a configuration example of a table stored in the cloud list DB of the cloud management DB group. FIG. 3 is a diagram illustrating a configuration example of a table stored in the lineup DB of the cloud management DB group. FIG. 4 is a diagram illustrating a configuration example of a table stored in the lineup price DB of the cloud management DB group. FIG. 5 is a diagram illustrating a configuration example of a table stored in the lineup specification information DB of the cloud management DB group. FIG. 6 is a diagram illustrating an example of a table stored in the lineup spec information DB of the cloud management DB group. FIG. 7 is a diagram illustrating a configuration example of a table stored in the lineup performance information DB of the cloud management DB group. FIG. 8 is a diagram illustrating a configuration example of a table stored in the tenant information DB of the cloud management DB group. FIG. 9 is a diagram illustrating a configuration example of a table stored in the cloud service registration information DB of the cloud management DB group. FIG. 10 is a diagram illustrating a configuration example of a table stored in the NW management DB of the cloud management DB group. FIG. 11 is a diagram illustrating a configuration example of a table stored in the inter-cloud NW management DB of the cloud management DB group. FIG. 12 is a diagram illustrating a configuration example of a table stored in the VM information DB of the cloud management DB group. FIG. 13 is a diagram illustrating a configuration example of a table stored in the VM operation information DB of the cloud management DB group. FIG. 14 is a diagram illustrating a configuration example of a table stored in the VM template DB of the cloud management DB group. FIG. 15 is a diagram illustrating a configuration example of a table stored in the monitoring setting DB of the cloud management DB group. FIG. 16 is a diagram illustrating a configuration example of a table stored in the resource performance information DB of the cloud management DB group. FIG. 17 is a diagram illustrating an example of an ID name identification rule. FIG. 18 is a diagram illustrating an example of the name identification conversion table generation rule. FIG. 19 is a diagram illustrating an example of the name identification conversion table. FIG. 20 is a diagram illustrating an example of the name identification conversion table. FIG. 21 is a diagram illustrating an example of RFD data. FIG. 22 is a diagram illustrating a conversion example of a table in the lineup price DB. FIG. 23 is a diagram illustrating a conversion example of a table in the VM operation information DB. FIG. 24 is a diagram illustrating a conversion example of a table in the lineup spec information DB. FIG. 25 is a diagram showing a schema structure after table conversion. FIG. 26 is a diagram illustrating an example of external data addition. FIG. 27 is a diagram illustrating a configuration example of a table stored in the VM procurement policy DB. FIG. 28 is a diagram illustrating an example of a table stored in the VM policy DB. FIG. 29 is a flowchart for explaining the flow of schema conversion processing in the resource management apparatus according to the first embodiment. FIG. 30 is a sequence diagram illustrating the flow of VM creation processing in the resource management device according to the first embodiment. FIG. 31 is a sequence diagram illustrating the flow of the VM activation process in the resource management device according to the first embodiment. FIG. 32 is a sequence diagram illustrating the flow of the VM stop process in the resource management device according to the first embodiment. FIG. 33 is a sequence diagram illustrating the flow of the VM deletion process in the resource management device according to the first embodiment. FIG. 34 is a diagram illustrating a computer that executes a resource management program.

  Hereinafter, embodiments of a resource management device, a resource management method, and a resource management program according to the present application will be described in detail with reference to the drawings. Note that the resource management device, the resource management method, and the resource management program according to the present application are not limited to the embodiment.

[First embodiment]
In the following embodiments, the configuration of the resource management system 1 according to the first embodiment, the configuration of the resource management device 10, and the processing flow in the resource management device 10 will be described in order, and finally the first embodiment The effect of will be described.

[Configuration of Resource Management System According to First Embodiment]
First, the resource management system 1 according to the first embodiment will be described with reference to FIG. FIG. 1 is a schematic configuration diagram showing the overall configuration of the resource management system according to the first embodiment.

  As illustrated in FIG. 1, the resource management system 1 includes a resource management device 10, a user terminal 20, and an administrator terminal 30. The resource management system 1 is a system for managing resources in a hybrid cloud, and includes a cloud service A and a cloud service B. In the following description, two cloud services A and cloud service B will be described as an example. However, the present invention is not limited to this, and there may be three or more cloud services. In addition, each component in the resource management system 1 may be placed at any place where IP connection is possible. For example, each component in the resource management system 1 is arranged as a system on any VM (Virtual Machine) in the private cloud.

  The resource management device 10 is connected to user terminals 20, administrator terminals 30, resource management APIs (Application Programming Interfaces) 41A and 41B of cloud services A and B, and network management APIs 42A and 42B. Although not shown in the figure, the resource management API 105 of the resource management device 10 and the APIs of the cloud services A and B are connected via the Internet, and the performance monitoring unit and the cloud services A and B are connected to each other. It is assumed that the API is connected via a VPN (Virtual Private Network). In addition, the cloud service A and the cloud service B may be connected by IP, or a VPN connection may be established using a virtual router.

  Further, the cloud services A and B may be private clouds that can access physical devices, public clouds that cannot access physical devices, or a plurality of one of the clouds. May be. For example, the cloud services A and B manage one private cloud and one public cloud. Here, the private cloud is a cloud constructed by a company or the like to manage only their own resources. A public cloud is a cloud provided by a public cloud service provider.

  When the resource management apparatus 10 receives a VM procurement policy indicating the characteristics of a VM requested by the user from a user UI (User Interface) 21 of the user terminal 20, the resource management apparatus 10 selects a cloud service that matches the VM procurement policy, and selects the selected cloud Procures VM from service.

  Cloud services A and B construct a cloud by installing hypervisors on a plurality of physical machines. In addition, the cloud services A and B are managed by the cloud service management function, and APIs for cooperation with external services are disclosed.

[Configuration of resource management device]
As shown in FIG. 1, the resource management apparatus 10 includes a user API 101, a resource management unit 102, a network management unit 103, a network management API 104, a resource management API 105, a performance analysis unit 106, a performance monitoring unit 107, a cloud selection unit 108, a schema. A conversion unit 109, a cloud management DB group 110, a schema conversion rule group 111, a post-schema conversion DB 112, a VM procurement policy DB 113, a name identification conversion table group 114, and a management IF 115 are included.

  The user API 101 is an API that accepts a resource procurement request from a user and mediates processing to the resource management unit 102. For example, the user API 101 receives a VM procurement policy indicating the characteristics of the VM requested by the user from the user UI (User Interface) 21 of the user terminal 20.

  The resource management unit 102 controls the VM that operates on the computer resource of the cloud service selected by the cloud selection unit 108. Specifically, the resource management unit 102 creates a VM, starts a VM, stops a VM, deletes a VM, and acquires resource information in response to a request from a user input via the user API 105. . For example, the resource management unit 102 creates a VM running on the computer resource of the cloud service selected by the cloud selection unit 108, starts the VM, stops the VM, or deletes the VM.

  The network management unit 103 performs connection control between resources existing between cloud services at different locations. For example, the network management unit 103 performs VPN connection and VPN disconnection as connection control between resources.

  The network management API 104 receives a command from the network management unit 103 and performs network control on the network management APIs 42A and 42B on the individual cloud services A and B. For example, the network management API 104 performs VPN connection and VPN disconnection as network control.

  Upon receiving an instruction from the resource management unit 102, the resource management API 105 creates a VM, starts a VM, stops a VM, and manages resources for the resource management APIs 41A and 41B on the individual cloud services A and B. Delete VM and get resource information.

  The performance analysis unit 106 analyzes the performance status of each of the cloud services A and B using the resource performance information acquired by the performance monitoring unit 107, and stores the analysis result in a DB (not shown) that stores the cloud performance information. Store.

  The performance monitoring unit 107 is a functional module that receives a command from the resource management unit 102 and acquires the performance information of the VM constituting the hybrid cloud. Specifically, the performance monitoring unit 107 acquires performance information for acquiring information related to the performance of the computer resource from each cloud service through remote access from the monitoring agent installed in each resource or device, or from the monitoring agent.

  In remote access, a monitoring target is accessed using an existing protocol such as Internet Control Message Protocol (ICMP), Secure Shell (SSH), or Simple Network Management Protocol (SNMP), and performance information is acquired by issuing a command. Since existing protocols and commands are used, it is possible to acquire information on many resources and devices. However, there is a limit to the performance information that can be acquired.

  The cloud selection unit 108 is a functional module that receives an instruction from the resource management unit 102 and selects an optimal cloud for the VM procurement policy. Specifically, when the cloud selection unit 108 receives the specification of the VM procurement policy indicating the characteristics of the VM operating on the computer resource requested by the user from the user terminal 20, the cloud selection unit 108 issues a query (search query) corresponding to the policy. The information acquired from the VM procurement policy DB 113 and converted by the schema conversion unit 109 using the query is searched, and a cloud service that matches the policy is selected. For example, the cloud selection unit 108 searches for graph data such as RDF (Resource Description Framework) data converted by the schema conversion unit 109 using a search query, and selects a cloud service that matches the VM procurement policy. select.

  For example, the cloud selection unit 108 changes the “VM procurement query” from the “VM procurement policy definition” based on the operation type (VM creation, activation, stop, deletion) and the VM procurement policy passed from the resource management unit 102. Search for. Then, the cloud selection unit 108 searches the “data after schema conversion” using the “VM procurement query”, obtains information about the optimal cloud service, and returns the result to the resource management unit 102.

  The schema conversion unit 109 converts the data stored in the cloud management DB group 110 into data having a structure searchable by a search query according to the schema conversion rule group 111. For example, the schema conversion unit 109 includes: unifying ID format used for information stored in the cloud management DB group 110, correcting notation fluctuation, value type conversion, value complementing, table format conversion, Perform any one or more. In addition, the schema conversion unit 109 converts, for example, graph data that expresses a relationship between information about cloud services stored in the schema conversion rule group 111. In addition, the schema conversion unit 109 performs data conversion in response to a start instruction from the management IF (Interface) 115 and stores the converted data in the post-schema conversion DB 112.

  The cloud management DB group 110 is a DB group necessary for operating a hybrid cloud, and stores information related to each cloud service that provides computer resources. For example, the cloud management DB group 110 stores one or more of information related to the performance of the computer, information related to the location of the computer, and information related to the price of the computer as information related to each cloud service that provides the computer resources. To do. The cloud management DB group 110 includes a DB that stores service information of each cloud service, a DB that stores network information for connecting between clouds, a DB that stores information about user tenants of the hybrid cloud, and a payout There are many DBs, such as a DB that stores information about resources such as VMs that are stored, and a DB that stores performance monitoring information of resources such as VMs.

  The schema conversion rule group 111 is a DB that stores conversion rules for converting data in the cloud management DB group 110 into data having a unified schema structure so that the cloud selection unit 108 can search the data.

  The post-schema conversion DB 112 is a DB that stores data obtained by converting the data of the cloud management DB group 110 according to the schema conversion rules by the schema conversion unit 109. The information stored in the post-schema conversion DB 112 is information that the cloud selection unit 108 uses for searching when selecting a cloud.

  The VM procurement policy DB 113 is a DB that stores a query (search query) used when the cloud selection unit 108 searches the DB 112 after schema conversion in accordance with the VM procurement policy. For example, the VM procurement policy DB 113 stores a query created based on information about cloud services in association with a VM procurement policy indicating the characteristics of computer resources.

[Example of DB group for cloud management]
The cloud management DB group 110 is a database group required to realize a hybrid cloud system. Hereinafter, an example of information stored in the cloud management DB group 110 will be described.

  The cloud management DB group 110 includes a cloud list DB, a lineup DB, a lineup price DB, a lineup spec information DB, a lineup performance information DB, a tenant information DB, a cloud service registration information DB, an NW management DB, an inter-cloud NW management DB, A VM information DB, a VM operation information DB, a VM template DB, a monitoring setting DB, and a resource performance information DB are included. Hereinafter, each DB will be described with reference to FIGS. Each DB stores a table including a plurality of table columns, and data is stored in each table column in a predetermined format (for example, String). Also, for each table column, whether or not it is a primary key is set.

  First, the cloud list DB will be described with reference to FIG. FIG. 2 is a diagram illustrating a configuration example of a table stored in the cloud list DB of the cloud management DB group 110. The cloud list DB is a DB that manages information on cloud services that can be incorporated into a hybrid cloud environment. This DB is assumed to be registered, updated, and deleted by the hybrid cloud administrator via the management IF 115.

  As illustrated in FIG. 2, in the cloud list DB, as a table column, a “cloud service ID” that identifies a cloud service that provides a VM, a “location” that indicates a location of a computer environment that provides the VM, and a cloud With an “initial cost” indicating the initial cost required to use the VM on the service.

  Next, the lineup DB will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration example of a table stored in the lineup DB of the cloud management DB group 110. The lineup DB is a DB in which lineups provided by each cloud service can be incorporated into a hybrid cloud environment. It is assumed that this information is registered, updated, and deleted by the hybrid cloud operator via the management IF 115. Selection of the lineup to be provided shall be made by the hybrid cloud operator.

  As illustrated in FIG. 3, the lineup DB stores “lineup ID”, which is an ID for identifying the lineup provided by the cloud service, and “cloud service ID” in association with each other as a table column.

  Next, the lineup price DB will be described with reference to FIG. FIG. 4 is a diagram illustrating a configuration example of a table stored in the lineup price DB of the cloud management DB group 110. The lineup price DB is a DB that stores information related to the price of the lineup. It is assumed that this information is registered, updated, and deleted by the hybrid cloud operator via the management IF 115. The price is assumed to be set by a hybrid cloud operator.

  As illustrated in FIG. 4, the run-up price DB includes a “lineup ID” as a table column, a “charging form” that is a charging form using a VM on the cloud service, and a period (month) in the case of fixed charging. A certain “fixed charging period” and a “VM price” that is a VM price are stored in association with each other. The VM price may be, for example, a VM price per hour, or may be a fixed VM price in the case of fixed charging.

  Next, the lineup specification information DB will be described with reference to FIGS. FIG. 5 is a diagram illustrating a configuration example of a table stored in the lineup specification information DB of the cloud management DB group 110. FIG. 6 is a diagram illustrating an example of a table stored in the lineup spec information DB of the cloud management DB group 110. The lineup spec information DB is a DB that stores additional information among the information regarding the specs of VMs provided in each lineup. For example, information that cannot be managed in a unified manner is stored because the presence / absence of each item, the notation method and unit of values, and the like differ significantly depending on the cloud provider. It is assumed that this information is registered, updated, and deleted by the hybrid cloud operator via the management IF 115.

  As illustrated in FIG. 5, the lineup specification information DB stores “lineup ID”, “column name” indicating the column name of the additional information, and “value” that is a value related to the column name in association with each other.

  As illustrated in FIG. 6, for example, in the lineup specification information DB, a VM lineup ID “cloud A-plan V1”, a column name “processor architecture”, and a value “64 bits” are stored in association with each other. Yes.

  Next, the lineup performance information DB will be described with reference to FIG. FIG. 7 is a diagram illustrating a configuration example of a table stored in the lineup performance information DB of the cloud management DB group 110. The lineup performance information DB is a DB related to the lineup performance that can be incorporated into the hybrid cloud environment. The results of performance analysis performed by an external information provider that performs the benchmark, the performance analysis unit 106, and the performance monitoring unit 107 are stored and used for performance comparison between clouds and lineups. This information shall be updated by one of the following methods. The hybrid cloud operator registers, updates, and deletes data via the management IF 115. The result of analyzing the performance monitoring information acquired by the performance analysis unit 106 and the performance monitoring unit 107 is stored.

  As illustrated in FIG. 7, the lineup performance information DB includes “acquisition time” that is the time when the performance information is acquired, “lineup ID”, “performance item” that is a performance item related to the cloud, and values for the performance item. Are stored in association with each other.

  Next, the tenant information DB will be described with reference to FIG. FIG. 8 is a diagram illustrating a configuration example of a table stored in the tenant information DB of the cloud management DB group 110. The tenant information DB stores a table for managing tenant information in the hybrid cloud service. It is assumed that this information is registered, updated, and deleted by the hybrid cloud operator via the administrator IF 115.

  As illustrated in FIG. 8, the tenant information DB includes a “tenant ID” that identifies a user tenant, a “contractor name” that indicates a person or organization that has a contract with the tenant, and the tenant user performs an operation from the user API 101. The “password”, which is a password required when performing, is associated and stored.

  Next, the cloud service registration information DB will be described with reference to FIG. FIG. 9 is a diagram illustrating a configuration example of a table stored in the cloud service registration information DB of the cloud management DB group 110. The cloud service registration information DB is a DB that manages information related to the registered cloud service for each tenant. It is assumed that this information is registered, updated, and deleted by the hybrid cloud operator via the management IF 115.

  As illustrated in FIG. 9, the cloud service registration information DB includes a “cloud service registration ID” that is an ID for identifying a cloud service that the tenant has registered for use, and a “cloud service ID” that is an ID of the registered cloud service. ”,“ Tenant ID ”that is the registered tenant ID,“ user ID ”that is used for cloud service resource management, and“ password ”that is the password used for cloud service resource management. Remember.

  Next, the NW management DB will be described with reference to FIG. FIG. 10 is a diagram illustrating a configuration example of a table stored in the NW management DB of the cloud management DB group 110. It is a DB that manages NW management information such as assigned VLANs for each cloud service registered by each tenant. NW management information differs in data management method depending on the business model. For models managed by the user, the user registers, updates, and deletes data via the user API 101. For models managed by the hybrid cloud operator, the hybrid cloud operator registers, updates, and deletes data via the management IF 115.

  As illustrated in FIG. 10, a “network ID” that is an ID for identifying a network, a “cloud service registration ID” that is a cloud service registration ID of a cloud service with a network, and a resource ID of a VPN connection gateway "Resource ID", "GW user ID" that is a user ID for remote login set in the GW VM template, and "GW user ID" that is a password for remote login set in the GW VM template The “password”, the “VLAN management ID” that is an ID for identifying the VLAN to which this network belongs, the “global address” that is the global address of the network, and the “local address” that is the local address band of the network are associated with each other. Remember.

  Next, the inter-cloud NW management DB will be described with reference to FIG. FIG. 11 is a diagram illustrating a configuration example of a table stored in the inter-cloud NW management DB of the cloud management DB group 110. The inter-cloud NW management DB is a DB that manages information related to the NW connection between cloud services. The data management method of NW configuration information differs depending on the business model. For models managed by the user, the user registers, updates, and deletes data via the user API 101. For models managed by the hybrid cloud operator, the hybrid cloud operator registers, updates, and deletes data via the management IF 115.

  As illustrated in FIG. 11, “inter-cloud connection ID” that is an ID for identifying an inter-cloud VPN connection, “tenant ID” that is an ID for identifying a customer tenant on the hybrid cloud, and a VLAN are identified. For example, “VLAN management ID”, “originating network ID” that is the ID of the originating network that is the target of VPN connection, and “incoming network ID” that is the ID of the destination network that is the subject of VPN connection Store in association with each other.

  Next, the VM information DB will be described with reference to FIG. FIG. 12 is a diagram illustrating a configuration example of a table stored in the VM information DB of the cloud management DB group 110. VM information DB is DB which manages the information regarding VM. The VM information DB is automatically registered when a VM is newly created by the resource management unit 102. However, regarding some attribute information (VM type, IP address, etc.), it is assumed that the user or the hybrid operator updates data via the user API 101.

  As illustrated in FIG. 12, the VM information DB identifies “VMID” that is an ID for identifying a VM, “cloud service ID” that is an ID of a cloud service in which the VM exists, and a lineup provided by the cloud service. "Lineup ID" that is the ID to be registered, "Cloud Service Registration ID" that is the registration ID of the cloud service where the VM is located, "Tenant ID" that is the tenant ID to which the VM belongs, and the VM that was used to create the VM The “VM template ID” that is the template ID, the “VM type” that is the type for the user to identify the VM, the “connection VLAN management ID” that is the VLAN management ID to which the VM is connected, and the IP address of the VM A certain “IP address”, a “CPU core number” that is the number of allocated CPU cores of a VM, and a VM allocated memory That is stored in association with each other "memory amount".

  Next, the VM operation information DB will be described with reference to FIG. FIG. 13 is a diagram illustrating a configuration example of a table stored in the VM operation information DB of the cloud management DB group 110. The VM operation information DB manages the operation state of the VM state, and when the VM state is changed by the resource management unit 102, the VM operation information DB is automatically added.

  As illustrated in FIG. 13, in the VM operation information DB, “time” that is the time when the state of the VM has changed, “VMID” that is an ID for identifying the VM, and “operation state” that is the operation state of the VM. Are stored in association with each other.

  Next, the VM template DB will be described with reference to FIG. FIG. 14 is a diagram illustrating a configuration example of a table stored in the VM template DB of the cloud management DB group 110. In the VM template DB, a VM template used for VM creation is managed when a new VM is created. The VM template is provided with an OS, middleware, and various settings, and can be created without building a system from 1 when creating a VM. It is possible to easily provide general functions such as Web servers and DB servers that are frequently used by many users, and special functions such as virtual routers that provide VPN connection.

  Further, the VM template is managed by the VM template creator. In the VM template provided by the hybrid cloud operator, the hybrid cloud operator registers, updates, and deletes data via the management IF 115. In the VM template created by the user, the user registers, updates, and deletes data via the user API 101.

  As illustrated in FIG. 14, in the VM template DB, “VM template ID” that is an ID for identifying a VM template, “owned tenant ID” that is an ID of the tenant that owns the VM template, and the VM template to another tenant. “Public / non-public” indicating whether or not to release, “OS” which is an OS used in the VM template, and “License list” which is information on the paid license included in the template required when creating the VM ”And“ monitoring setting ”which is a setting when monitoring a VM created using the VM template is stored in association with each other.

  Next, the monitoring setting DB will be described with reference to FIG. FIG. 15 is a diagram illustrating a configuration example of a table stored in the monitoring setting DB of the cloud management DB group 110. The monitoring setting DB manages information on monitoring settings for VMs, physical servers, and NW devices. Monitoring setting information for a VM is automatically registered, updated, or deleted when a VM is created, started, stopped, or deleted through the user API 101. In the monitoring setting, it is possible to set what kind of monitoring is performed for each component.

  The main monitoring settings include “ICMP monitoring” for monitoring system life and death, “Linux monitoring” for monitoring performance information of Linux (registered trademark), and “SNMP monitoring” for monitoring performance information of network devices. . In ICMP monitoring, the IP address of each component is pinged to monitor the system alive status. In addition, Linux monitoring accesses each component using the SSH protocol, and obtains performance information (CPU information, memory information, I / O information, process information, traffic information, syslog information, etc.) using existing Linux commands. To do. The SNMP monitoring acquires performance information (traffic information, memory information, CPU information) that can be acquired via SNMP using the SNMP protocol.

  As illustrated in FIG. 15, in the monitoring setting DB, “resource ID” that is an ID of a resource for which performance information is acquired, “VMID”, “monitoring IP address” that is an IP address used for monitoring, The “monitoring state” that is the operating state and the “monitoring setting” that is the list of the monitoring setting plug-ins are stored in association with each other.

  Next, the resource performance information DB will be described with reference to FIG. FIG. 16 is a diagram illustrating a configuration example of a table stored in the resource performance information DB of the cloud management DB group 110. The resource performance information DB stores a table for storing performance information acquired by the performance monitoring unit. The performance monitoring unit 107 periodically acquires information for resources (VM, physical server, NW device) in operation and adds data.

  As illustrated in FIG. 16, the resource performance information DB includes “acquisition time” that is a time when performance information is acquired, “resource ID”, “monitoring item” that is a performance monitoring item, and acquired performance value. Are stored in association with each other.

[Schema conversion processing]
Since the cloud management DB group 110 takes a data schema optimized for hybrid cloud operation, it is difficult to browse data comprehensively as it is. Therefore, it is converted into a unified data schema that facilitates comprehensive browsing.

  Although IDs indicating the same object exist in different tables, if they are expressed in different formats, they are unified to the ID format of any table. Originally it was a database that was necessary to realize different functions, so there was no problem even if each unique ID was assigned. However, when referring to data in a unified manner, it is necessary to unify the ID. There is. For example, “VMID” that is the ID of the VM information DB and the resource ID that is the ID of the monitoring setting DB are both IDs indicating specific VMs.

  Here, a method for realizing ID name identification will be described. Here, ID name identification refers to processing that is performed to unify the formats of IDs that indicate the same target in different DBs (tables) but that are expressed in different formats. There are two patterns of data addition to the cloud management DB group 110: dynamic addition from the resource management unit 102 or manual addition of data from the management IF 115. First, as a definition of the ID name identification rule, the hybrid cloud administrator registers the name identification rule in the schema conversion rule through the management IF 115. For example, as illustrated in FIG. 17, “VMID” that is the ID of the VM information DB, “resource ID” that is the ID of the monitoring setting DB, and “resource ID” that is the ID of the “resource performance information DB” are collated. To do. At that time, the ID of the “VM information DB” is unified. FIG. 17 is a diagram illustrating an example of an ID name identification rule.

  In the case of dynamic addition from the resource management unit 102, as a first method, name identification conversion table data is generated and added using a name identification conversion table generation rule. As a second method, when a table cannot be generated, a value to be identified is registered in the name identification conversion table group 114 when the resource management unit 102 registers an ID in the DB. When data is manually added from the management IF 115, it is manually entered into the name identification conversion table through the management IF 115.

  Here, the name identification conversion table generation rule will be described. When operating on the cloud, since there is no data that records the relationship between different types of IDs, unified management cannot be performed, and therefore there is data that indicates the correspondence between IDs somewhere. For example, as illustrated in FIG. 18, since the resource ID and VMID of the monitoring setting DB are data indicating a correspondence relationship, a method for generating a name identification conversion table using this data is a name identification conversion table indicated in SQL. It is defined in the generation rule. FIG. 18 is a diagram illustrating an example of the name identification conversion table generation rule.

  After adding data to the name identification conversion table, IDs are identified using the name identification conversion table. Here, with respect to an example of the name identification conversion table, for example, as illustrated in FIG. 19, “value before name identification” and “value after name identification” are stored in the name identification conversion table in association with each “column name”. Has been. FIG. 19 is a diagram illustrating an example of the name identification conversion table.

  Information provided from different cloud services includes notation fluctuations indicated in different notation even when the same meaning and value are indicated. In order to compare with other services, it is necessary to correct the notation fluctuation. Examples of notation fluctuations include “Tokyo”, “Asia Pacific (Tokyo)”, and “Tokyo”. Examples of the notation fluctuation include, for example, “vCPU”, “CPU”, “number of cores”, and “virtual CPU”.

  In addition, as a correction method for notation fluctuation, a name identification conversion table is inserted through the management IF 115, and name identification is performed using the name identification conversion table. For example, as illustrated in FIG. 20, in the name identification conversion table, “value before name identification” and “value after name identification” are stored in association with each “column name”. FIG. 20 is a diagram illustrating an example of the name identification conversion table.

  In addition, information provided from different cloud services includes data written in different units even with the same attribute information value. In order to compare, it is necessary to unify the unit of values. As an example in which type conversion is necessary, for example, with respect to a VM price, it is necessary to change the type when the price is Japanese yen and when the price is US dollar. In addition, the type of the memory needs to be changed between an MB unit value and a GB unit value. As a type conversion method, a type conversion rule (script or the like) is defined, and a value is converted using the rule.

  In addition, there is information that is not specified in the cloud management DB group 110. For example, if data is not supplemented, it cannot be compared with other services, so it is necessary to supplement. For example, as an example that needs to be supplemented, the “maximum number of NICs” in the “lineup spec information DB” is not specified because the number of NICs is uniformly N in a cloud service, and this value is not specified. It is necessary to supplement. As a value complementing method, for example, a complementing rule (script or the like) is defined, and the value is converted using the rule.

  In addition, as one of the schema conversion processes, if it is difficult to browse comprehensively, the table format is converted and converted into a unified format to facilitate comprehensive browsing. . For example, as a case where exhaustive browsing becomes difficult, a case where data relating to the same object is distributed in a plurality of tables can be considered. In other words, in order to manage different functions, there are examples in which a table is individually created or a table is divided in order to increase processing efficiency. Explaining with a specific example, information regarding the cloud service lineup is distributed in a plurality of tables such as a lineup price DB, a lineup specification DB, and a lineup performance DB.

  Further, as a case where exhaustive browsing becomes difficult, a case where the storage style in the table is different is considered. For example, in a general table, attribute information associated with an ID is described in a plurality of columns (rows), and one record (column) is recorded in a style indicating data related to one object. To explain with a specific example, in the lineup price DB, ID: lineup ID, attribute information: charge form, fixed charge period, and VM price are stored for the lineup of the target: cloud service.

  When the type of attribute information cannot be specified, it is difficult to store data using a general style. Therefore, it may be stored in a style that stores a triple of ID, attribute information name, and value. For example, it is a table based on 3 sets stored in the above-described lineup spec information DB.

  The unified format after conversion may be a general table or a three-set table. Since the data of the hybrid cloud service has various elements related to each other in a complicated manner, it is easier to browse a table based on three sets than a general table format. An RDF that can express and search complicated semantic relationships is convenient for the three-set base table. Hereinafter, a conversion method to an RDF data model corresponding to a three-set table will be described.

  RDF data is represented by a triple of a subject, a property, and an object. For example, referring to the example shown in FIG. 21, the ellipse node labeled “emp: 1234111” in FIG. 21A is the subject, and the rectangular node labeled “Taro Suzuki” is An object, a directed edge labeled “emp: name” is represented in the properties.

  In RDF data, there are two types of nodes: resources represented by elliptical nodes and literals represented by rectangular nodes. Resources and properties are labeled with uniquely identifiable IDs such as URIs. Resources can be assigned a type with rdf: type. For example, in FIG. 21B, the type of the resource “emp: 1234111” is “emp: employee”. RDF data can be represented by a labeled effective graph.

  The table of the cloud management DB group 110 can be classified into three types: a table with a primary key, a table without a primary key, and a triplet-based table. The table with a primary key is the most general table and is a table having one primary key. For example, a cloud list DB, a lineup DB, a lineup price DB, a tenant information DB, a cloud service registration information DB, an inter-cloud NW management DB, a VM information DB, a VM template DB, and a monitoring setting DB correspond to the primary key presence table.

  The table without a primary key is a table in which a primary key does not exist or a plurality of columns are set as primary keys. For example, the primary keyless table corresponds to a VM operation information DB, a lineup performance information DB, and a resource performance information DB.

  The triple table is a table composed of a triple of ID, column name, and value in the primary keyless table, for example, a lineup specification information DB.

  As an example of conversion of a table with a primary key, processing for converting each record of the table will be described. Specifically, the column name value described in the ID name identification rule is an RDF resource, and other values are literals. The RDF resource type uses the head ID name of the ID name identification rule. Also, the primary key is converted into an RDF resource, which is converted into a subject, a column name other than the primary key is converted into a property name, and the value of the column is converted into an object. In the case of list format values, the column name is added to the property name and the value is added as an object for each value. Note that FIG. 22 shows an example of RDF data obtained by converting a table record in the lineup price DB and an example of a data format for actual computer processing. FIG. 22 is a diagram illustrating a conversion example of a table in the lineup price DB.

  As an example of converting a table without a primary key, a process for converting each record of the table will be described. The column name value described in the ID name identification rule is an RDF resource, and other values are literals. The RDF resource type uses the head ID name of the ID name identification rule. Convert blank node to subject, column name to property name, and column value to object. The table name is used as the type of the blank node. An example of RDF data obtained by converting a table record in the VM operation information DB is shown in FIG. FIG. 23 is a diagram illustrating a conversion example of a table in the VM operation information DB.

  As an example of conversion of a triple table, a process of converting each record of the table will be described. As the resource type, the head ID name of the ID name identification rule is used. Also, the column name value described in the ID name identification rule is an RDF resource, and other values are literals. Also, the ID is converted into an RDF resource, which is converted into a subject, the column name value is converted into a property name, and the value is converted into an object. An example of RDF data obtained by converting a table record in the lineup spec information DB is shown in FIG. FIG. 24 is a diagram illustrating a conversion example of a table in the lineup spec information DB.

  As described above, after the table conversion, schema structure conversion can be easily performed on the RDF data illustrated in FIG. 25 by using an RDF query language such as SPARQL. Schema conversion may be performed again to facilitate policy search. Also, unnecessary values may be deleted or the direction of the arrow (relationship between subject and object) may be reversed. FIG. 25 is a diagram showing a schema structure after table conversion.

  Further, external data may be added to the converted data so that a more convenient policy search is possible. For example, as exemplified in FIG. 26, distance data of prefectures may be added to the conversion data. FIG. 26 is a diagram illustrating an example of external data addition.

[Example of VM procurement policy DB]
Here, information stored in the VM procurement policy DB will be described with reference to FIGS. 27 and 28. FIG. 27 is a diagram illustrating a configuration example of a table stored in the VM procurement policy DB. FIG. 28 is a diagram illustrating an example of a table stored in the VM policy DB.

  The VM procurement policy is a query used to search for lineups and VMs that meet user needs from among computer resources in a plurality of cloud services. The VM procurement policy is stored in the VM procurement policy DB, and the hybrid cloud operator registers, updates, and deletes data via the management IF 115.

  As shown in FIG. 27, in the VM procurement policy DB, a “policy ID” that is an ID for identifying a policy, a “VM operation” that is a description of the type of VM operation related to the policy, and a list of input parameters required for the search “Input parameters”, “output parameters” that are types of values that are output as search results, and “queries” that are queries for searching for lineup IDs to be subject to VM operations in accordance with policies are stored in association with each other. In the example of FIG. 27, the query is written in a SPARQL style.

Here, with reference to FIG. 28, an example of a query to be searched for the schema-converted DB 112 having the schema structure illustrated in FIG. 25 will be described. As illustrated in FIG. 28, for example, a query whose policy ID is “performance priority VM stop”, VM operation is “VM stop”, input parameter is {“tenant ID”}, and output parameter is “VMID” is as follows: It is written like this.
SELECT? VMID {
? VMID tenant %% tenant ID %%.
? VMID VM lineup? Lineup ID.
? VMID operating status “Started”.
Lineup ID Lineup performance information Lineup performance information
Lineup performance information CPU benchmark results CPU benchmark results
} ORDER BY DESC (? CPU benchmark result)

[Processing by resource management device]
Next, processing performed by the resource management apparatus 10 according to the first embodiment will be described with reference to FIGS. 29 to 33. FIG. 29 is a flowchart for explaining the flow of schema conversion processing in the resource management apparatus according to the first embodiment. FIG. 30 is a sequence diagram illustrating the flow of VM creation processing in the resource management device according to the first embodiment. FIG. 31 is a sequence diagram illustrating the flow of the VM activation process in the resource management device according to the first embodiment. FIG. 32 is a sequence diagram illustrating the flow of the VM stop process in the resource management device according to the first embodiment. FIG. 33 is a sequence diagram illustrating the flow of the VM deletion process in the resource management device according to the first embodiment.

  First, the flow of schema conversion processing in the resource management apparatus 10 will be described with reference to FIG. As shown in FIG. 29, the schema conversion unit 109 of the resource management device 10 reads data stored in the cloud management DB group 110 (step S101) and performs ID name identification (step S102). This unifies the table ID format.

  Then, the schema conversion unit 109 corrects notation fluctuation (step S103), and performs value type conversion (step S104). Subsequently, when the value is not specified, the schema conversion unit 109 performs value complementation (step S105) and performs table format conversion (step S106).

  Then, the schema conversion unit 109 adds external data (step S107), and outputs the converted data to the post-schema conversion DB 112 (step S108). The data group 110 for cloud management has a data schema optimized for hybrid cloud operation, and it is difficult to browse data comprehensively as it is. In order to convert to a unified data schema, the above processing is performed.

  Next, the VM creation process will be described with reference to FIG. As illustrated in FIG. 30, when the user API 101 receives a VM creation condition from the user UI 21 (step S201), the user API 101 notifies the resource management unit 102 of the VM creation condition (step S202). Then, the resource management unit 102 searches for a cloud registration ID that allows VM creation from the creation conditions and the NW management information (step S203). As a result of the search, if the number of searches is two or more, the process proceeds to step S204. If the number of searches is one, the process proceeds to step S207. If the number is zero, the process proceeds to step S212. To do.

  Then, the resource management unit 102 notifies the cloud selection unit 108 of a lineup selection request for creating a VM (step S204). Subsequently, the cloud selection unit 108 selects a cloud service lineup ID suitable for creating a VM based on the data of the policy definition information (step S205). Then, the cloud selection unit 108 notifies the resource management unit 102 of the lineup selection result for creating the VM (step S206).

  Thereafter, the resource management unit 102 extracts information necessary for creating the VM from the cloud list information and the VM template information, and creates a query for the cloud service (step S207). Then, the resource management unit 102 makes a VM creation request to the resource management API 105 (step S208). Then, the resource management API 105 makes a VM creation request to the cloud management API of the target cloud service (step S209) and notifies the resource management unit 102 of the VM creation request result (step S210).

  If the VM creation is successful, the resource management unit 102 registers information on the new VM in the resource information, and adds the new VM monitoring setting to the monitoring setting information (step S211). The resource management unit 102 creates a VM creation result to be returned to the user API 101 (step S212), and notifies the VM creation result to the user API 101 (step S213). Then, the user API 101 transmits the VM creation result to the user UI 21 (step S214).

  Next, a VM activation process for activating a VM will be described with reference to FIG. As illustrated in FIG. 31, when the user API 101 receives a VM activation condition from the user UI 21 (step S301), the user API 101 notifies the resource management unit 102 of the VM activation condition (step S302). Then, the resource management unit 102 searches for VMs that match the activation condition from the VMs whose resource information is stopped (step S303). If the number of searches is 0, the process proceeds to step S314. If there is only one registered cloud ID from the search results, the process proceeds to step S307.

  Then, the resource management unit 102 notifies the cloud selection unit 108 of an activation VMID selection request for starting the VM (step S304). Subsequently, the cloud selection unit 108 selects a suitable cloud service lineup ID from the cloud service lineup IDs to which the VM belongs based on the data of the policy definition information (step S305). Then, the cloud selection unit 108 notifies the resource management unit 102 of the activation VMID selection result (step S306).

  Then, the resource management unit 102 selects one VM of the selected cloud service lineup ID, extracts necessary data from the “cloud list information”, and creates a query for the cloud service (step S307). Then, the resource management unit 102 notifies the VM management API 105 of the VM activation request (step S308), makes a VM activation request to the cloud management API of the target cloud service (step S309), and sends the VM activation result to the resource management unit 102. (Step S310).

  Then, when the VM activation is successful, the resource management unit 102 updates the resource information and the monitoring setting information (step S311). Then, the resource management unit 102 requests the performance monitoring unit 107 to start VM performance monitoring (step S312). Subsequently, the performance monitoring unit 107 starts monitoring the resource ID of the startup VM (step S313). Further, the resource management unit 102 creates a VM activation result to be returned to the user API 101 (step S314), and notifies the VM activation result to the user API 101 (step S315). Then, the user API 101 transmits the VM activation result to the user UI 21 (step S316).

  Next, a VM stop process for stopping the VM will be described with reference to FIG. As illustrated in FIG. 32, when the user API 101 receives a VM stop condition from the user UI 21 (step S401), the user API 101 notifies the resource management unit 102 of the VM stop condition (step S402). Then, the resource management unit 102 searches for VMs that match the stop condition from the VMs whose resource information is stopped (step S403). If the number of searches is 0, the process proceeds to step S414, and if there is only one type of registered cloud ID from the search result, the process proceeds to step S407.

  Then, the resource management unit 102 notifies the cloud selection unit 108 of a cloud service lineup selection request for stopping the VM (step S404). Subsequently, the cloud selection unit 108 selects a suitable cloud service lineup ID from the cloud service lineup IDs to which the VM belongs based on the data of the policy definition information (step S405). Then, the cloud selection unit 108 notifies the resource management unit 102 of the cloud service lineup selection result (step S406).

  Then, the resource management unit 102 selects one VM of the selected cloud service lineup ID, extracts necessary data from the “cloud list information”, and creates a query for the cloud service (step S407). Then, the resource management unit 102 notifies the resource management API 105 of a VM stop request (step S408), makes a VM stop request to the cloud management API of the target cloud service (step S409), and sends the VM stop result to the resource management unit 102. (Step S410).

  Then, when the VM stop is successful, the resource management unit 102 updates the resource information and the monitoring setting information (step S411). Then, the resource management unit 102 requests the performance monitoring unit 107 to stop the VM performance monitoring (step S412). Subsequently, the performance monitoring unit 107 stops monitoring the resource ID of the stopped VM (step S413). Further, the resource management unit 102 creates a VM stop result to be returned to the user API 101 (step S414), and notifies the user API 101 of the VM stop result (step S415). Then, the user API 101 transmits the VM stop result to the user UI 21 (step S416).

  Next, a VM deletion process for deleting a VM will be described with reference to FIG. As illustrated in FIG. 33, when the user API 101 receives a VM deletion condition from the user UI 21 (step S501), the user API 101 notifies the resource management unit 102 of the VM deletion condition (step S502). Then, the resource management unit 102 searches for a cloud registration ID that allows VM deletion from the deletion condition and the NW management information (step S503). As a result of the search, if the number of searches is two or more, the process proceeds to step S504. If the number of searches is one, the process proceeds to step S507. If the number is zero, the process proceeds to step S512. To do.

  Then, the resource management unit 102 notifies the cloud selection unit 108 of a lineup selection request for VM deletion (step S504). Subsequently, the cloud selection unit 108 selects a cloud service lineup ID suitable for deleting the VM based on the data of the policy definition information (step S505). Then, the cloud selection unit 108 notifies the resource management unit 102 of the lineup selection result for VM deletion (step S506).

  Thereafter, the resource management unit 102 extracts information necessary for deleting the VM from the cloud list information and the VM template information, and creates a query for the cloud service (step S507). Then, the resource management unit 102 makes a VM deletion request to the resource management API 105 (step S508). Then, the resource management API 105 makes a VM deletion request to the cloud management API of the target cloud service (step S509), and notifies the resource management unit 102 of the VM deletion request result (step S510).

  When the VM deletion is successful, the resource management unit 102 registers information on the new VM in the resource information, and adds the new VM monitoring setting to the monitoring setting information (step S511). Then, the resource management unit 102 deletes the VM deletion result returned to the user API 101 (step S512), and notifies the user API 101 of the VM deletion result (step S513). Then, the user API 101 transmits the VM deletion result to the user UI 21 (step S514).

[Effect of the first embodiment]
As described above, the resource management device 10 uses a cloud management DB group 110 that stores information about each cloud service that provides computer resources, and a query that is created based on information about the cloud service, as a feature of the computer resource. And a VM procurement policy DB 113 that stores the VM procurement policy in association with the VM procurement policy. In accordance with the schema conversion rule group 111, the resource management device 10 converts the data stored in the cloud management DB group 110 into data having a structure that can be searched by a search query. In addition, when the resource management apparatus 10 receives a VM procurement policy specification indicating the characteristics of a VM operating on a computer resource requested by the user from the user terminal 20, the resource management apparatus 10 acquires a query corresponding to the policy from the VM procurement policy DB 113. Using the query, the information converted by the schema conversion unit 109 is searched, and a cloud service that matches the policy is selected. Then, the resource management device 10 creates a virtual machine that operates on the computer resource of the selected cloud service, starts the virtual machine, stops the virtual machine, or deletes the virtual machine. For this reason, it is possible to procure VMs appropriately while reducing the burden on the user.

  In other words, conventionally, since the user selects a cloud service to be used, it is not clear which cloud service the user should use, which is a burden on the user side. On the other hand, in the resource management apparatus 10 according to the first implementation, the user can use the VM according to the needs without being aware of the individual cloud services. Register cloud service information such as performance, price, and location from cloud services registered in advance, define VM procurement policy and cloud service selection rules, and select VM procurement destination from VM procurement policy selected by user Automatically select cloud services and secure VMs. Therefore, it is possible to easily provide a VM that meets the user needs from among a plurality of cloud services. As a result, for example, it is possible to provide an inexpensive VM with “priority”, provide a high-performance VM with “priority”, or provide VMs at multiple locations with “risk distribution”. is there.

  The hybrid cloud service in the resource management system 1 manages and operates various information such as service information of available cloud services, information about NWs, information about tenants (customers), and information on operating VM specifications. . The operation information includes information required by the user for VM selection, such as the physical location of computer resources, NW line types, available VM lineups (price and specifications), and VM performance information. Scattered. In the resource management apparatus 10, the hybrid cloud service administrator defines a VM procurement policy and a VM procurement query pair in advance, and the hybrid cloud service is operated using the VM procurement query corresponding to the VM procurement policy selected by the user. Provide a mechanism to select cloud services that match user needs by searching for information. As a result, the user can procure a VM that meets the user needs simply by selecting the VM procurement policy.

  Moreover, since the operation information of the hybrid cloud service is a DB group for operation, it has a schema structure that enables efficient search for data necessary for operation. When a search based on a VM procurement policy other than the original purpose is performed, the search query becomes complicated, and it becomes difficult for the hybrid cloud service administrator to add or modify the VM procurement policy. Therefore, a schema conversion rule for converting the data structure of the operation information from the viewpoint of VM procurement, such as extracting only data related to VM procurement, is defined, and a query is executed on the operation information after the schema conversion.

  Further, by using the search via the schema conversion rule, the VM procurement query becomes simple, and it becomes possible to easily add or modify the VM procurement policy. Furthermore, it is possible to flexibly cope with a change in operation information due to a change in the hybrid cloud operation system. Further, by presenting the operation information schema information after applying the schema change rule and the VM procurement query to the user, the basis of the VM procurement can be shown, and the user side can be controlled.

  As described above, the resource management apparatus 10 registers cloud service information such as performance, price, and location from the cloud service registered in advance, defines the VM procurement policy and the cloud service selection rule, and the user In order to automatically select the VM procurement destination cloud service from the VM procurement policy selected by the user and secure the VM, the user simply selects the VM procurement policy and selects the VM on the cloud service having the service specifications required by the user. It becomes possible to provide.

[Second Embodiment]
The embodiments of the present invention have been described so far, but the present invention may be implemented in various different forms other than the above-described embodiments. Therefore, another second embodiment included in the present invention will be described below as a second embodiment.

(1) System Configuration, etc. Further, each component of each illustrated apparatus is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Further, all or any part of each processing function performed in each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

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

(2) Program It is also possible to create a program that describes the processing executed by the resource management apparatus 10 according to the above embodiment in a language that can be executed by a computer. In this case, the same effect as the above-described embodiment can be obtained by the computer executing the program. Further, such a program may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by a computer and executed to execute the same processing as in the above embodiment. Hereinafter, an example of a computer that executes a resource management program that realizes the same function as the resource management apparatus 10 will be described.

  FIG. 34 is a diagram illustrating a computer that executes a resource management program. As shown in FIG. 34, the computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM (Random Access Memory) 1012. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1090. The disk drive interface 1040 is connected to the disk drive 1041. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1041. For example, a mouse 1110 and a keyboard 1120 are connected to the serial port interface 1050. For example, a display 1130 is connected to the video adapter 1060.

  Here, as shown in FIG. 34, the hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. Each table described in the above embodiment is stored in the hard disk drive 1090 or the memory 1010, for example.

  Further, the resource management program is stored in the hard disk drive 1090 as a program module in which commands executed by the computer 1000 are described, for example. Specifically, a program module describing each process executed by the resource management apparatus 10 described in the above embodiment is stored in the hard disk drive 1090.

  Data used for information processing by the resource management program is stored as program data in, for example, the hard disk drive 1090. Then, the CPU 1020 reads out the program module 1093 and the program data 1094 stored in the hard disk drive 1090 to the RAM 1012 as necessary, and executes the above-described procedures.

  The program module 1093 and the program data 1094 related to the resource management program are not limited to being stored in the hard disk drive 1090. For example, the program module 1093 and the program data 1094 are stored in a removable storage medium and read by the CPU 1020 via the disk drive 1041 or the like. May be issued. Alternatively, the program module 1093 and the program data 1094 related to the resource management program are stored in another computer connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network), and are transmitted via the network interface 1070. May be read by the CPU 1020.

10 Resource management device 101 User API
102 resource management unit 103 network management unit 104 network management API
105 Resource management API
106 Performance Analysis Unit 107 Performance Monitoring Unit 108 Cloud Selection Unit 109 Schema Conversion Unit 110 Cloud Management DB Group 111 Schema Conversion Rule Group 112 DB After Schema Conversion
113 VM procurement policy DB
114 Name conversion table group 115 IF for management

Claims (7)

A storage unit that stores information about each cloud service that provides computer resources;
A policy storage unit that stores a search query created based on information about the cloud service in association with a policy indicating the characteristics of the computer resource;
A conversion unit that converts information stored in the storage unit into information having a structure searchable by the search query according to a predetermined conversion rule;
When a policy specification is received by the user terminal, a search query corresponding to the policy is acquired from the policy storage unit, and the information converted by the conversion unit is searched using the search query, and the policy A selection unit that selects a cloud service that matches
A management unit that executes creation of a virtual machine that operates on the computer resource of the cloud service selected by the selection unit, startup of the virtual machine, stop of the virtual machine, or deletion of the virtual machine;
A resource management device comprising:   The conversion unit is one or more of unification of identifier formats used for information stored in the storage unit, correction of notation fluctuation, value type conversion, value completion, and table format conversion The resource management apparatus according to claim 1, wherein: The conversion unit converts the graph data representing the relationship between information about the cloud service stored in the storage unit,
The resource management device according to claim 1, wherein the selection unit searches the graph data using the search query and selects a cloud service that matches the policy. A monitoring unit that acquires information about the performance of the computer resource from each cloud service;
The analysis part which analyzes the performance condition of each cloud service using the information acquired by the said monitoring part, and stores an analysis result in the said memory | storage part is further provided. The resource management device described in 1.   The storage unit stores, as information about each cloud service that provides the computer resources, one or more of information about the performance of the computer, information about the location of the computer, and information about the price of the computer. The resource management device according to claim 1, wherein the resource management device is a device. A resource management method executed by a resource management device,
The resource management device is
A storage unit that stores information about each cloud service that provides computer resources;
A policy storage unit that stores a search query created based on information about the cloud service in association with a policy indicating the characteristics of the computer resource;
With
A conversion step of converting the information stored in the storage unit into information having a structure searchable by the search query according to a predetermined conversion rule;
When a policy specification is received by the user terminal, a search query corresponding to the policy is acquired from the policy storage unit, and the information converted by the conversion step is searched using the search query, and the policy A selection process for selecting a cloud service that matches
A management step of executing creation of a virtual machine operating on a computer resource of the cloud service selected by the selection step, start of the virtual machine, stop of the virtual machine, or deletion of the virtual machine;
A resource management method comprising:   A resource management program for causing a computer to function as the resource management device according to claim 1.

Images