JP5988505B2 - Virtual resource management apparatus, selection method, and selection program - Google Patents

Description

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

  As a foundation of an IaaS (Infrastructure as a Service) type cloud service, an open stack of Open Source is known. The open stack is mainly intended to provide an API (Application Programming Interface) having a primitive function as an IaaS platform.

  Also, in IaaS constructed using an open stack, a technique for aggregating virtual servers (also referred to as VMs (Virtual Machines)) while keeping SLA (Service Level Agreement) is known.

OpenStack web site, [searched on November 13, 2013], Internet (URL: http://www.openstack.org/) A. Corradi, M. Fanelli, L. Foschini, "VM consolidation: A real case based on OpenStack Cloud," Elsevier Future Generation Computer Systems, June 2012.

  However, the above-described conventional technology has a problem that it is not possible to provide a high-quality cloud service by reducing operation costs.

  For example, the open stack has a problem in the effective use of physical equipment that meets the business requirements of the carrier. For example, the open stack randomly arranges VMs when determining a VM generation destination physical device. For this reason, business requirements such as wanting to effectively use physical equipment cannot be satisfied.

  For example, if VMs are randomly placed on physical devices, the performance of the physical devices being used may not be maximized. More specifically, when a physical device includes a CPU and a memory, many VMs that use a lot of CPU operate on one physical device, and many virtual machines use a lot of memory on another physical device. When operating, each physical device cannot exhibit sufficient performance.

  Further, in the conventional technology for consolidating VMs, consideration is not given to consolidating VMs to physical devices that satisfy the software license conditions used by the VMs.

  The disclosed technique has been made in view of the above, and an object thereof is to provide a high-quality cloud service by reducing operation costs.

  The virtual resource management device disclosed in the present application includes a receiving unit, a first specifying unit, a second specifying unit, and a request unit. The accepting unit accepts a virtual resource generation request. The first specifying unit refers to information indicating software operable in the physical device, and specifies a physical device capable of operating the software used by the generated virtual resource. The second specifying unit refers to the physical device information in which the physical resource capacity of the physical device and the physical resource capacity allocated to the virtual resource among the physical resource capacities are associated with each other, and newly creates a virtual resource. A physical device having a physical resource capacity that can be generated is specified. The request unit specifies the physical device specified by both the first specifying unit and the second specifying unit, and requests generation of the virtual resource that has received the generation request.

  The selection method disclosed in the present application includes a reception process, a first identification process, a second identification process, and a request process. The accepting process accepts a virtual resource generation request. In the first specifying step, a physical device capable of operating software used by the generated virtual resource is specified with reference to information indicating software operable in the physical device. The second specific step refers to the physical device information in which the physical resource capacity of the physical device and the physical resource capacity allocated to the virtual resource among the physical resource capacities are associated with each other, and a new virtual resource is created. A physical device having a physical resource capacity that can be generated is specified. In the requesting process, the physical device specified by both the first specifying process and the second specifying process is specified, and the generation of the virtual resource that has received the generation request is requested.

  The selection program disclosed in the present application causes a computer to execute a reception procedure, a first identification procedure, a second identification procedure, and a request procedure. The acceptance procedure accepts a virtual resource generation request. The first specifying procedure specifies a physical device capable of operating software used by the generated virtual resource with reference to information indicating software operable in the physical device. The second specific procedure refers to physical device information in which a physical resource capacity of a physical device and a physical resource capacity allocated to the virtual resource among the physical resource capacities are associated with each other, and a new virtual resource is created. A physical device having a physical resource capacity that can be generated is specified. The request procedure designates the physical device identified by both the first identification procedure and the second identification procedure, and requests the generation of the virtual resource that has accepted the generation request.

  According to one aspect of the disclosed virtual resource management apparatus, there is an effect that it is possible to provide a high-quality cloud service by reducing the operation cost.

FIG. 1 is a diagram illustrating an example of a configuration of a virtual resource providing system according to the first embodiment. FIG. 2 is a diagram for explaining the processing operation in the virtual resource providing system. FIG. 3 is a diagram for explaining a physical device selection function DB and a physical device selection function unit realized by the virtual resource management apparatus. FIG. 4 is a diagram illustrating an example of a data structure of physical device information. FIG. 5 is a diagram for explaining a software license management method used in the VM. FIG. 6 is a diagram illustrating an example of a data structure of software group information. FIG. 7 is a diagram illustrating an example of a data structure of virtual resource information. FIG. 8 is a flowchart illustrating a processing procedure performed by the physical device selection function unit. FIG. 9 is a flowchart illustrating a processing procedure by the physical device selection function unit when a virtual resource migration is requested. FIG. 10 is a diagram illustrating a computer that executes a selection program.

  Hereinafter, embodiments of a disclosed virtual resource management device, selection method, and selection program will be described in detail with reference to the drawings. The invention disclosed by this embodiment is not limited.

(First embodiment)
FIG. 1 is a diagram illustrating an example of a configuration of a virtual resource providing system according to the first embodiment. As illustrated in FIG. 1, the virtual resource providing system includes a user terminal 101, a provider operator terminal 102, a physical device 103 a, a physical device 103 b, a physical device 103 c, an IaaS controller 104, and a virtual resource management device 105. In the case where the physical device 103a, the physical device 103b, and the physical device 103c are not distinguished, they are described as the physical device 103. Further, the number of physical devices 103 included in the virtual resource providing system is not limited to the number illustrated in FIG. 1 and can be arbitrarily changed.

  The user terminal 101 is a terminal used by the user, and requests the virtual resource management apparatus 105 to generate virtual resources and migrate virtual resources in accordance with user instructions. The provider operator terminal 102 is a terminal used by the provider of the virtual resource providing system, and requests the virtual resource management apparatus 105 to generate a virtual resource and migrate a virtual resource in accordance with an operator instruction, for example. The physical device 103 is, for example, a physical server device or a storage device, receives a virtual resource generation instruction from the IaaS controller 104, and generates a virtual resource. In addition, the physical device 103 receives a virtual resource migration instruction from the IaaS controller 104 and migrates the virtual resource.

  The IaaS controller 104 is connected to the physical device 103 and the virtual resource management apparatus 105. The IaaS controller 104 is a device having a CPU (Central Processing Unit), a memory, a data holding area, and a network communication function. The IaaS controller 104 receives a virtual resource generation request or a virtual resource migration request from the virtual resource management apparatus 105, and generates a virtual resource or a virtual resource migration to the physical device 103 based on the accepted generation request or migration request. Instruct.

  The virtual resource management device 105 is connected to the user terminal 101, the operator operator terminal 102, and the IaaS controller 104. The virtual resource management apparatus 105 is an apparatus having a CPU, a memory, a data holding area, and a network communication function. For example, as shown in FIG. 1, the virtual resource management apparatus 105 includes a physical device selection function DB (Data Base). 106 and a physical device selection function unit 107.

  For example, when a virtual resource generation is requested from the user terminal 101 or the operator operator terminal 102, such a virtual resource management apparatus 105 uses the virtual resource generation request and information of the physical device selection function DB 106. Then, the physical device 103 of the virtual resource generation destination is selected. The virtual resource management apparatus 105 then designates the selected physical device and requests the IaaS controller 104 to generate a virtual resource. In the following, a VM (Virtual Machine) will be described as an example of a virtual resource.

  Next, processing operations in such a virtual resource providing system will be described. FIG. 2 is a diagram for explaining the processing operation in the virtual resource providing system. As shown in FIG. 2, the user terminal 101 or the operator operator terminal 102 requests the physical device selection function unit 107 to generate a virtual resource (step S1). Here, the user terminal 101 or the operator operator terminal 102 transmits a virtual resource generation request including the user identifier, the user usage area, the usage (or contract type), and the like. Note that user attributes such as a user's usage area and usage may be stored in association with a user identifier as user information. Further, the physical device selection function unit 107 may determine the user attribute with reference to the user information.

  The physical device selection function unit 107 refers to the physical device selection function DB 106 (step S2) and acquires physical device information (step S3). Subsequently, the physical device selection function unit 107 selects a physical device (step S4), and requests the IaaS controller 104 to generate a virtual resource (step S5). The process for selecting a physical device will be described later. Then, the IaaS controller 104 instructs the selected physical device 103 to generate a virtual resource (step S6). Thereby, in the physical device 103, a virtual resource is generated (step S7). When the generation of the virtual resource is completed, the physical device 103 notifies the IaaS controller 104 that the generation of the virtual resource is completed (step S8).

  The IaaS controller 104 notifies the physical device selection function unit 107 that the generation of the virtual resource is completed (step S9). Subsequently, the physical device selection function unit 107 notifies the user terminal 101 or the operator operator terminal 102 that the generation of the virtual resource is completed (step S10).

  Next, the physical device selection function DB 106 and the physical device selection function unit 107 realized by the virtual resource management apparatus 105 will be described with reference to FIG. FIG. 3 is a diagram for explaining the physical device selection function DB 106 and the physical device selection function unit 107 realized by the virtual resource management apparatus 105.

  As shown in FIG. 3, the physical device selection function DB 106 stores physical device information 106a, software group information 106b, and virtual resource information 106c. The physical device information 106a is information in which the physical resource capacity of the physical device 103 is associated with the physical resource capacity allocated to the virtual resource among the physical resource capacity. More specifically, the physical device information 106a includes physical device ID (identifier), affiliation zone, operable software group, usage (normal or isolated), status (in use or in stock), This is information in which resource specifications, virtual resources on physical devices, and the like are associated with each other.

  FIG. 4 is a diagram illustrating an example of a data structure of the physical device information 106a. As shown in FIG. 4, the physical device information 106a includes “physical device ID”, “affiliation zone”, “operable software group”, “usage usage”, “status”, and “resource spec”. , “Used resources” and “virtual resources” are associated with each other.

  Here, the “physical device ID” stored in the physical device information 106 a indicates an identifier for uniquely identifying the physical device 103. For example, data values such as “0001” and “0002” are stored in the “physical device ID”. The “affiliation zone” stored in the physical device information 106a is information for specifying the position where the physical device 103 is installed. For example, the “affiliation zone” stores data values such as “district A” and “district B”.

  The “operable software group” stored in the physical device information 106a indicates the type of software group in which the physical device can operate. A software group is a concept of bundling software. For example, the “operable software group” stores data values such as “OS (Operating System) A” and “OS A, DBMS (DataBase Management System) B”.

  The “use purpose” stored in the physical device information 106 a indicates the type of use purpose of the physical device 103. For example, “use usage” stores data values such as “isolation use” for isolating and using a specific virtual resource having a high use frequency and “normal use” for normal use. The “state” stored in the physical device information 106a indicates the usage state of the physical device. For example, “status” indicates that the physical device 103 has generated any virtual resource and is being used, and indicates that the physical device 103 has not generated any virtual resource. Data values such as “inventory” are stored.

  The “resource specification” stored in the physical device information 106 a indicates the performance of the physical resource of the physical device 103. For example, the “resource spec” stores a data value such as “CPU core number: 16, memory: 32 GB” indicating that the number of CPU cores is 16 cores and the memory capacity is 32 GB. Further, the manufacturer of the CPU may be stored as “resource specifications”. In addition to the CPU type information, the disk size may be stored as “resource spec”. The “used resource” stored in the physical device information 106 a indicates the capacity allocated to the virtual resource among the physical resources implemented in the physical device 103. For example, a data value such as “CPU core number: 4, memory: 6 GB” is stored in “used resource”. Note that the type information of the CPU mounted on the physical device 103 may be stored as the resource specification. The CPU type information includes information indicating the CPU manufacturer, CPU type, and the like.

  The “virtual resource” stored in the physical device information 106a indicates the type of virtual resource that the physical device 103 generates and operates. For example, “virtual resource” stores a data value such as “VMa” indicating the type of VM. Note that no data value is stored in the “virtual resource” when the physical device 103 is in a stock state or when a virtual resource is not generated even when the physical device 103 is in operation.

  For example, in the physical device information 106a shown in FIG. 4, the physical device 103 with the identifier “0001” is located in “area A”, the number of CPU cores is 16 cores, and the memory capacity is 32 GB. It shows that. The physical device information 106a indicates that the physical device 103 with the identifier “0001” can operate the software group with “OS A”, generates a VMa as a virtual resource, and is currently used for normal use. Indicates that it is in use. The physical device information 106a indicates that the number of CPU cores of the physical device 103 with the identifier “0001” is 4 cores, and the memory capacity is 6 GB.

  Returning to FIG. The software group information 106b and the virtual resource information 106c are information for managing software licenses used in the VM. Here, before describing the software group information 106b and the virtual resource information 106c, a software license management method used in the VM will be described with reference to FIG. FIG. 5 is a diagram for explaining a software license management method used in the VM.

  A plurality of software license information can be assigned to volumes and images that can start VMs. For example, in the example shown in FIG. 5, “virtual volume A” is associated with “OS A6.1”, and “image B” is associated with “OS A6.2” and “DBMS B9”. . In the following, it is assumed that VMa is started from “virtual volume A” and VMb is started from “image B”. Note that the virtual resource information 106c manages these relationships in association with each other.

  Also, as shown in FIG. 5, the relationship of which software group is associated with each physical device 103 is managed. Here, a plurality of software groups can be associated with each physical device 103. In the example illustrated in FIG. 5, the software group “OS A” is associated with the physical device 103 whose physical device ID is “0001” and the physical device 103 whose physical device ID is “0002”. These correspondence relationships are managed as “physical device ID” and “operable software group” in the physical device information 106a. The correspondence relationship between the software group and the individual software included in the software group is managed by the software group information 106b.

  As described above, in the example illustrated in FIG. 5, as a result, the VMa activated from “virtual volume A” can operate on the physical device 103 with the identifier “0001” and the physical device 103 with the identifier “0002”. Can be managed. In addition, although the example which assumed VM was demonstrated in FIG. 5, it is applicable similarly to another virtual resource. In such a case, the relationship among physical devices, software groups, individual software, and virtual resources is managed.

  Returning to FIG. The software group information 106b is information indicating individual software that can be operated by the software group. FIG. 6 is a diagram illustrating an example of the data structure of the software group information 106b. As illustrated in FIG. 6, the software group information 106 b is information in which “software group” and “individual software” are associated with each other.

  Here, the “software group” stored in the software group information 106b indicates the type of software group. For example, data values such as “OS A” and “DBMS B” are stored in “Software Group”. The “individual software” stored in the software group information 106b indicates the type of individual software included in the software group. The individual software indicates software that is a part of the software group. For example, “individual software” stores data values such as “OS A6.1, OS A6.2, OS A6.3”, “DBMS B9, DBMS B10, DBMS B11”.

  For example, the software group information 106b shown in FIG. 6 indicates that the software group “OS A” includes “OS A6.1, OS A6.2, OS A6.3” as individual software. It is shown that “DBMS B9, DBMS B10, DBMS B11” is included as individual software in the software group “DBMS B”.

  Returning to FIG. The virtual resource information 106c is information indicating individual software capable of operating the virtual resource. FIG. 7 is a diagram illustrating an example of the data structure of the virtual resource information 106c. As shown in FIG. 7, the virtual resource information 106c is information in which “virtual resource” and “individual software” are associated with each other.

  Here, the “virtual resource” stored in the virtual resource information 106c indicates the type of the virtual resource. For example, data values such as “virtual volume A” and “image B” are stored in “virtual resource”. The “individual software” stored in the virtual resource information 106c indicates the type of individual software that can operate the virtual resource. For example, data values such as “OS A6.1”, “OS A6.2, DBMS B9” are stored in “individual software”.

  Here, when the VMa is started from the “virtual volume A” and the VMb is started from the “image B”, the virtual resource information 106c illustrated in FIG. 7 is obtained from the virtual resource “virtual volume A”. This indicates that the VMa to be started uses “OS A6.1”. Further, the virtual resource information 106c illustrated in FIG. 7 indicates that the VMb started from the virtual resource “image B” uses “OS A6.2” and “DBMS B9”.

  Returning to FIG. The physical device selection function unit 107 includes a reception unit 107a, a first specification unit 107b, a second specification unit 107c, and a request unit 107d. The accepting unit 107 a accepts a virtual resource generation request from the user terminal 101 or the operator operator terminal 102. The accepting unit 107a delivers the accepted virtual resource generation request to the first specifying unit 107b.

  The first specifying unit 107b refers to the physical device information 106a and specifies a physical device for which another virtual resource has already been generated. For example, the first specifying unit 107b specifies a physical device whose “state” in the physical device information 106a illustrated in FIG. 4 is “in use”.

  The first specifying unit 107b refers to information indicating software that can operate in the physical device, and specifies a physical device that can operate the software used by the generated virtual resource. A case where the VMa is operated will be described. For example, the first specifying unit 107b refers to the virtual resource information 106c illustrated in FIG. 7, and as software that can be used by the VMa, the individual software “OS A6.1” associated with the “virtual volume A” that activates the VMa. Is identified. Then, the first specifying unit 107b specifies the software group “OS A” including “OS A6.1” from the software group information 106b illustrated in FIG. Subsequently, the first specifying unit 107b specifies the physical device 103 capable of operating the software group “OS A” from the physical device information 106a illustrated in FIG. For example, the first specifying unit 107b specifies the physical device 103 having the identifier “0001” as a physical device that operates the VMa.

  Returning to FIG. The first specifying unit 107b refers to the physical device information 106a, and among the physical devices 103 that can generate a virtual resource, the physical device 103 installed in an area designated by the user who has requested provision of the virtual resource. Is identified. For example, the first specifying unit 107b specifies a physical device whose “affiliation zone” in the physical device information 106a shown in FIG.

  Further, the first specifying unit 107b refers to the physical device information 106a and specifies the physical device 103 corresponding to the usage of the virtual resource. For example, the first specifying unit 107b determines that a user whose usage frequency is high according to the contract type is an isolated usage usage, and a user whose usage frequency is not high is a normal usage usage. For example, the first specifying unit 107b specifies the physical device 103 whose “usage usage” in the physical device information 106a illustrated in FIG. . Further, for example, when the contract type is frequently used by the user, the first specifying unit 107b specifies a physical device whose “use usage” in the physical device information 106a illustrated in FIG. 4 is “isolation use”. In this way, it is possible to consider that there are virtual resources that use a great deal of physical device resources depending on how the user uses them. Thus, by isolating users with high usage frequency, it is possible to prevent the service quality of a plurality of users from degrading for one user with high usage frequency.

  The second specifying unit 107c newly creates a virtual resource from the physical resource capacity of the physical device and the physical resource usage of the virtual resource already generated on the physical device among the physical devices that can generate the virtual resource. Identify the physical device that generates the

  For example, a case will be described in which a certain physical device 103 has 16 CPU cores and 32 GB of memory. Further, it is assumed that the CPU core number allocation of the VM created by the user is 4 cores and the memory is 6 GB. In this case, when there are two operated VMs, the second specifying unit 107c determines that a newly requested VM can be created. On the other hand, if the number of already operated VMs is four, the second specifying unit 107c determines that a new VM cannot be created because the number of CPU cores 16 has already been allocated. However, there are few cases where 100% of the number of cores and memory allocated to the user are used. For this reason, the second specifying unit 107c may allocate a virtual resource that exceeds the resource amount of the physical device when all users use the 100% contract capacity depending on the policy of the operator.

  Also, when there are a plurality of candidates, the second specifying unit 107c determines the physical device 103 that creates the virtual resource according to a predetermined calculation formula. That is, since the plurality of physical devices 103 in use are candidates, the second specifying unit 107c selects in accordance with a predetermined calculation formula as to which one of the physical devices 103 can be used effectively.

  For example, among physical devices that can generate a virtual resource, a physical device that newly generates a virtual resource is calculated from the physical resource capacity of the physical device and the physical resource usage of the virtual resource that has already been generated on the physical device. Identify. For example, the second specifying unit 107c determines a certain constant determined from the resource specification of the physical device 103, the physical resource usage of the virtual resource already generated in the physical device 103, and the physical resource usage of the newly generated virtual resource. The physical device 103 is specified with reference to a variable calculated from the sum of the quantities.

  More specifically, when creating a VM on a certain physical device, if either of the physical device CPU and memory is used excessively, physical device resources cannot be used effectively. For this reason, a calculation formula is set so that the ratio between the total number of CPU cores of the VM to be operated and the total number of memory of the VMs to be operated approaches the ratio between the number of CPU cores of the physical device and the memory. Further, the second specifying unit 107c arranges a VM in a physical device that uses few resources in the case of the isolation use. For this reason, the second specifying unit 107c specifies not the ratio between the CPU and the memory, but the physical device 103 with few VMs operating on the physical device 103, and the physical device 103 with few CPUs or memory being used. To do.

  The requesting unit 107d specifies the physical device 103 specified by both the first specifying unit 107b and the second specifying unit 107c, and requests the IaaS controller 104 to generate a virtual resource that has received the generation request.

  FIG. 8 is a flowchart illustrating a processing procedure performed by the physical device selection function unit 107. The receiving unit 107a of the physical device selection function unit 107 receives a virtual resource generation request from the user terminal 101 or the operator operator terminal 102 (step S101). Here, the accepting unit 107a accepts a generation request including a designated zone and a usage application, for example.

  The first specifying unit 107b specifies a physical device corresponding to the designated zone (step S102). It is assumed that the physical device 103 identified in step S102 is condition A. Subsequently, the first specifying unit 107b determines whether the specified physical device candidate is 1 or more (step S103). If the first specifying unit 107b determines that the specified physical device candidate is not 1 or more (No in step S103), the first specifying unit 107b determines that a physical device cannot be selected (step S120), and ends the process. . On the other hand, when the first specifying unit 107b determines that the specified physical device candidate is 1 or more (Yes in step S103), the first specifying unit 107b determines whether the use application is a normal use application (step S104). .

  When the first specifying unit 107b determines that the use application is a normal use application (Yes in step S104), the first specifying unit 107b specifies and narrows down physical devices whose use application is the normal use application among the physical devices 103 of the condition A. (Step S105). Note that the physical device 103 identified in step S105 is defined as condition B1. On the other hand, if the first specifying unit 107b determines that the use application is not the normal use application (No in step S104), the first specifying unit 107b specifies the physical device whose use application is the isolated use application among the physical devices 103 of the condition A. (Step S106). Note that the physical device 103 identified in step S106 is defined as condition B2. After step S105 or step S106, the first specifying unit 107b determines whether the specified physical device candidate is 1 or more (step S107).

  If the first specifying unit 107b determines that the specified physical device candidate is not 1 or more (No in step S107), the first specifying unit 107b determines that the physical device cannot be selected (step S120), and ends the process. . On the other hand, when the first specifying unit 107b determines that the specified physical device candidate is 1 or more (Yes in step S107), the state is used among the physical devices 103 in the condition B (condition B1 or condition B2). A physical device in the middle is specified and narrowed down (step S108).

  Then, the first specifying unit 107b determines whether or not the specified physical device candidate is 1 or more (step S109). If the first specifying unit 107b determines that the specified physical device candidate is not 1 or more (No in step S109), the first specifying unit 107b proceeds to step S117. On the other hand, if the first specifying unit 107b determines that the specified physical device candidate is 1 or more (Yes in step S109), the first specifying unit 107b can operate the specified virtual resource among the physical devices 103 narrowed down in step S108. A specific physical device is identified and narrowed down (step S110). It is assumed that the physical device 103 identified in step S110 is a condition C. Then, the first specifying unit 107b determines whether the specified physical device candidate is 1 or more (step S111).

  If the first specifying unit 107b determines that the specified physical device candidate is not 1 or more (step S111, No), the first specifying unit 107b proceeds to step S117. On the other hand, when the first specifying unit 107b determines that the specified physical device candidate is 1 or more (Yes in step S111), the second specifying unit 107c determines that the physical device among the physical devices 103 of the condition C is a physical device. The physical device capable of generating a new virtual resource is identified and narrowed down from the resource specifications and the usage amount of the virtual resource on the physical device (step S112). Note that the physical device 103 identified in step S112 is defined as condition D.

  Subsequently, the second specifying unit 107c determines whether or not the specified physical device candidate is 1 or more (step S113). Here, if the second specifying unit 107c determines that the specified physical device candidate is not 1 or more (step S113, No), the process proceeds to step S117. On the other hand, when the second specifying unit 107c determines that the specified physical device candidate is 1 or more (step S113, Yes), the second specifying unit 107c determines whether the specified physical device candidate is 2 or more ( Step S114).

  If the second specifying unit 107c determines that there are two or more candidates for the specified physical device (step S114, Yes), the second specifying unit 107c selects a physical device based on a predetermined calculation formula (step S115), and ends the process. To do. On the other hand, if the second specifying unit 107c determines that the specified physical device candidates are not two or more (No in step S114), that is, if it is determined that there is one physical device candidate, Is selected (step S116), and the process ends.

  In step S117, the first specifying unit 107b specifies the physical device 103 that satisfies the condition A, the condition B, the condition C, and the condition D from the physical devices 103 in the inventory state (step S117). Then, the first specifying unit 107b determines whether or not there are one or more candidate physical devices in stock that satisfy the conditions A, B, C, and D (step S118). When a physical device whose usage is a normal usage is specified, the first specifying unit 107b has one or more candidates for physical devices in stock that satisfy all of the conditions A, B1, C, and D. It is determined whether or not. On the other hand, when a physical device whose usage is an isolated usage is identified, the first identification unit 107b has one or more candidates for physical devices in stock that satisfy all of the conditions A, B2, C, and D. It is determined whether or not.

  Here, when the first specifying unit 107b determines that the number of candidates for physical devices in stock that satisfy the conditions A, B, C, and D is not 1 or more (No in step S118), the process proceeds to step S120. Transition. On the other hand, when the first specifying unit 107b determines that there are one or more candidates for physical devices in stock that satisfy the conditions A, B, C, and D (Yes in step S118), the state is in stock. Is selected (step S119), and the process is terminated. Further, the first specifying unit 107b determines in step S120 that a physical device cannot be selected (step S120), and ends the process.

  As described above, the virtual resource management apparatus 105 according to the first embodiment selects a physical device that has room for generating a new virtual resource. Thereby, the user can obtain sufficient performance with the generated virtual resource.

  Further, the virtual resource management apparatus 105 according to the first embodiment selects a physical device corresponding to the operating condition of software. This eliminates the need to purchase software licenses for all physical devices, thereby reducing operating costs.

  In addition, the virtual resource management apparatus 105 according to the first embodiment selects a physical device with reference to a device status in use or in stock. Thereby, the apparatus to be used can be preferentially selected, and the apparatus to be used can be reduced to reduce the operation cost such as the electricity bill.

  Further, the virtual resource management apparatus 105 according to the first embodiment selects a physical device so that the resource usage of the physical device approaches a specific value. As a result, inefficient use of physical device resources such as excessive use of only the CPU or excessive use of only the memory can be prevented, and the physical device can be effectively used.

  In addition, the virtual resource management apparatus 105 according to the first embodiment selects a physical device with reference to a device usage for isolation or normal use. As a result, it is possible to isolate a specific virtual resource, such as a high usage frequency, in a specific isolating device and prevent other users from being affected. Thereby, the quality of the whole service can be improved.

  In the above-described embodiment, a case has been described in which the virtual resource management apparatus 105 selects the physical device 103 when, for example, the user terminal 101 or the operator operator terminal 102 requests generation of a virtual resource. The embodiment is not limited to this. For example, the virtual resource management apparatus 105 selects the physical device 103 in the same manner when, for example, the migration of the virtual resource is requested from the user terminal 101 or the operator operator terminal 102. Also, when migrating a virtual resource to a different physical device 103, if there is no device compatibility between the migration source physical device 103 and the migration destination physical device 103, the migration of the virtual resource fails and the user uses the virtual resource. It becomes impossible. For this reason, when migrating a virtual resource to a different physical device, the first specifying unit 107b refers to the physical device information 106a and is compatible with the performance of the physical resource of the migration source physical device. Identify the physical equipment. Specifically, when a hypervisor migrates a VM on KVM (Kernel based Virtual Machine), KVM does not have any device restrictions when creating a new VM. There is a restriction that VMs can only be migrated between devices.

  For this reason, when migrating a virtual resource to a different physical device 103, the first specifying unit 107b refers to the physical device information 106a and determines the CPU manufacturer and migration destination of the migration source physical device 103. A physical device 103 having the same CPU manufacturer as the physical device 103 is identified.

  FIG. 9 is a flowchart illustrating a processing procedure performed by the physical device selection function unit 107 when a virtual resource migration is requested. In FIG. 9, processes that are the same as the process procedure shown in FIG. 8 are given the same reference numerals, and detailed descriptions thereof are omitted.

  As illustrated in FIG. 9, the reception unit 107a of the physical device selection function unit 107 receives a virtual resource migration request (step S201). The accepting unit 107a delivers the accepted migration request to the first specifying unit 107b. Thereby, the first specifying unit 107b executes the processing from step S202 to step S209. Note that the processing from step S202 to step S209 is the same as the processing from step S102 to step S109 shown in FIG.

  Then, the first identification unit 107b identifies the physical device 103 that can be migrated from the resource specifications of the migration source physical device and the migration destination physical device (step S210). For example, the first specifying unit 107b specifies the physical device 103 in which the CPU manufacturer of the migration source physical device 103 is the same as the CPU manufacturer of the migration destination physical device 103. The physical device 103 identified in step S210 is defined as condition E.

  Subsequently, the first specifying unit 107b determines whether the specified physical device candidate is 1 or more (step S211). Here, when the first specifying unit 107b determines that the specified physical device candidate is 1 or more (Yes in step S211), the first specifying unit 107b executes the processing from step S212 to step S218. Note that the processing from step S212 to step S218 is the same as the processing from step S110 to step S116.

  On the other hand, if the first specifying unit 107b determines that the specified physical device candidate is not 1 or more (step S211, No), the first specifying unit 107b proceeds to step S219. Then, the first specifying unit 107b specifies the physical device 103 that satisfies the conditions A, B, C, D, and E from the physical devices 103 in the inventory state (step S219). Then, the first specifying unit 107b determines whether or not the number of candidates for the physical device 103 in stock that satisfies the conditions A, B, C, D, and E is one or more (step S220).

  Here, when the first specifying unit 107b determines that the number of physical device candidates in stock that satisfy the conditions A, B, C, D, and E is not one or more (No in step S220), The process proceeds to step S222. Then, in step S222, the first specifying unit 107b determines that a physical device cannot be selected (step S222), and ends the process. On the other hand, when the first specifying unit 107b determines that there are one or more candidates for physical devices in stock that satisfy the conditions A, B, C, D, and E (Yes in step S220), the state Is selected from the stock state (step S221), and the process is terminated.

  As described above, the virtual resource management apparatus 105 selects the migration destination physical device with reference to the migration source and migration destination physical device resource specifications. As a result, it is possible to prevent the virtual resource from failing due to a device compatibility problem and the user from being able to use the virtual resource.

  The first specifying unit 107b specifies the physical device 103 in which the CPU manufacturer of the migration source physical device 103 is the same as the CPU manufacturer of the migration destination physical device 103 as the migration destination physical device 103. Although the case has been described, the embodiment is not limited to this. For example, the first specifying unit 107b compares the physical resource performance of the migration source physical device 103 with the physical resource performance of the migration destination physical device 103, and the virtual resource to be migrated can also operate on the migration destination physical device 103. It may be determined whether or not. In such a case, for example, the first specifying unit 107b specifies the physical device 103 that is equal to or larger than the number of CPU cores and the memory capacity of the migration source physical device 103 as the migration destination physical device 103.

  Note that the processing sequence described in FIGS. 8 and 9 can be changed in the order in which the processing does not contradict. For example, the processing order may be arbitrarily changed between step S102, processing from step S104 to step S106, and step S108 and step S110 shown in FIG. Further, the process from step S102, step S104 to step S106, or the process from step S108 to step S110 shown in FIG. 8 may be omitted.

  In the above-described embodiment, a VM (Virtual Machine) has been described as an example of a virtual resource, but the embodiment is not limited to this. For example, the virtual resource may be a virtual router, a virtual switch, a virtual load balancer, a virtual firewall, a virtual gateway, a virtual volume, a virtual snapshot, or the like. Then, the virtual resource management apparatus 105 can select which physical device to create the virtual resource based on the physical device information 106a and the virtual resource generation request.

(Second Embodiment)
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. Therefore, other embodiments will be described below.

(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-mentioned documents and drawings (for example, FIGS. 1 to 9) are optional unless otherwise specified. Can be changed.

  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.

(program)
It is also possible to generate a selection program in which processing executed by the virtual resource management apparatus 105 according to the first embodiment is described in a language that can be executed by a computer. In this case, when the computer executes the selection program, the same effect as in the above embodiment can be obtained. Further, the same processing as in the above embodiment may be realized by recording the selection program on a computer-readable recording medium, and reading and executing the selection program recorded on the recording medium. Hereinafter, an example of a computer that executes a selection program that realizes the same function as the virtual resource management apparatus 105 illustrated in FIG. 1 and the like will be described.

  FIG. 10 is a diagram illustrating a computer 1000 that executes a selection program. As shown in FIG. 10, 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 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 1031. 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 1051 and a keyboard 1052 are connected to the serial port interface 1050. For example, a display 1061 is connected to the video adapter 1060.

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

  The selection program is stored in, for example, the hard disk drive 1031 as a program module in which a command to be executed by the computer 1000 is described. Specifically, a reception procedure for executing information processing similar to that of the reception unit 107a described in the above embodiment, a first specification procedure for executing information processing similar to that of the first specification unit 107b, and a second A hard disk drive 1031 stores a program module 1093 in which a second specific procedure for executing information processing similar to that of the specifying unit 107c and a request procedure for executing information processing similar to that of the requesting unit 107d are described.

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

  Note that the program module 1093 and the program data 1094 related to the selected program are not limited to being stored in the hard disk drive 1031, but are stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive 1041 or the like. May be. Alternatively, the program module 1093 and the program data 1094 related to the selection 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. It may be read by the CPU 1020.

(Other)
The specific program described in this embodiment can be distributed via a network such as the Internet. The specific 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.

105 Virtual Resource Management Device 106 Physical Device Selection Function DB
106a Physical device information 106b Software group information 106c Virtual resource information 107 Physical device selection function unit 107a Reception unit 107b First specification unit 107c Second specification unit 107d Request unit 1000 Computer 1010 Memory 1011 ROM
1012 RAM
1020 CPU
1030 Hard disk drive interface 1031 Hard disk drive 1040 Disk drive interface 1041 Disk drive 1050 Serial port interface 1051 Mouse 1052 Keyboard 1060 Video adapter 1061 Display 1070 Network interface 1080 Bus 1091 OS
1092 Application program 1093 Program module 1094 Program data

Claims (7)

A reception unit that receives a virtual resource generation request;
A first specifying unit for specifying a physical device capable of operating software used by the generated virtual resource with reference to software license management information that is information indicating software that is licensed and operable in the physical device;
A physical that can generate a new virtual resource by referring to physical device information in which the physical resource capacity of the physical device is associated with the physical resource capacity allocated to the virtual resource in the physical resource capacity. A second specifying unit for specifying a physical device having a resource capacity;
A request unit that specifies the physical device specified by both the first specification unit and the second specification unit, and requests generation of the virtual resource that has received the generation request ;
In the physical device information, the physical device is further associated with information indicating that the use application of the physical device is an isolation use or a normal use,
The first identifying unit further refers to the physical device information and identifies a physical device corresponding to a usage purpose of the virtual resource.   The virtual resource management apparatus according to claim 1, wherein the first specifying unit further specifies a physical device for which another virtual resource has already been generated with reference to the physical device information. In the physical device information, the physical device is further associated with information indicating the position where the physical device is installed,
The first specifying unit further refers to the physical device information, and among physical devices capable of generating a virtual resource, a physical device installed in an area designated by a user who has requested provision of the virtual resource The virtual resource management device according to claim 1, wherein the virtual resource management device is specified. When the virtual resource is migrated to a different physical device, the first identifying unit refers to the physical device information and identifies a physical device that is compatible with the physical resource performance of the migration source physical device. virtual resource management apparatus according to any one of claims 1-3, characterized in that. The second specifying unit allocates a predetermined constant determined from a physical resource capacity of a physical device, a physical resource capacity allocated to a virtual resource already generated in the physical device, and a newly generated virtual resource. It refers to a variable calculated from the physical resource capacity and being, virtual resource management apparatus according to any one of claims 1-4, characterized in that identifying the physical device. A reception process for receiving a virtual resource generation request;
A first specifying step of specifying a physical device capable of operating software used by the generated virtual resource with reference to software license management information that is information indicating software that is licensed and operable in the physical device;
A physical that can generate a new virtual resource by referring to physical device information in which the physical resource capacity of the physical device is associated with the physical resource capacity allocated to the virtual resource in the physical resource capacity. A second specifying step of specifying a physical device having a resource capacity;
A requesting step for requesting generation of the virtual resource that has received the generation request by designating the physical device specified by both the first specifying step and the second specifying step;
Only including,
In the physical device information, the physical device is further associated with information indicating that the use application of the physical device is an isolation use or a normal use,
The selection method characterized in that the first specifying step further specifies a physical device corresponding to a use purpose of a virtual resource with reference to the physical device information . A reception procedure for receiving a virtual resource generation request;
A first identification procedure for identifying a physical device capable of operating software used by a generated virtual resource with reference to software license management information that is information indicating software that is licensed and operable in the physical device;
A physical that can generate a new virtual resource by referring to physical device information in which the physical resource capacity of the physical device is associated with the physical resource capacity allocated to the virtual resource in the physical resource capacity. A second identification procedure for identifying a physical device having a resource capacity;
A selection for causing the computer to execute a request procedure for requesting generation of the virtual resource that has specified the physical device specified by both the first specification procedure and the second specification procedure and has received the generation request. Program ,
In the physical device information, the physical device is further associated with information indicating that the use application of the physical device is an isolation use or a normal use,
The first specifying procedure further specifies a physical device corresponding to the use purpose of the virtual resource with reference to the physical device information.
The selection program characterized by the above .

Images