JP2018037047A - Resource allocation device, resource allocation method and resource allocation program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a resource allocation device, a resource allocation method and a resource allocation program that can change a physical CPU (CPU core) allocated for each virtual resource in an automatic dispensing system of the virtual resource, and that can perform fixed allocation of the virtual resource as a portion of automatic dispensing.SOLUTION: A resource allocation device 3 of a virtual computer system according to the present invention comprises an input unit 311 to which resource request information having designation information of a CPU resource for a virtual CPU to be fixedly allocated to a CPU core unit in one-to-one relation is input, a resource extraction unit 313 that extracts an allocatable CPU resource based on the resource request information, an allocation resource selection unit 314 that selects the CPU resource to be allocated from the extracted resource, a resource fixed allocation unit 315 that fixedly allocates the selected CPU resource, and a resource multiple allocation unit 316 that performs multiple allocation of the selected CPU resource.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a resource allocation device, a resource allocation method, and a resource allocation program for a virtual machine system.

  If the processing of the network function or the like realized by the dedicated server by the virtual computer system is virtualized (software), the performance and quality of the processing of the network function or the like may not be maintained due to switching of the CPU resource of the scheduler or the like. For this reason, fixed allocation of CPU resources for associating a virtual CPU with a fixed physical CPU (CPU core) is required.

  However, in a virtual machine system based on a system (virtual resource automatic payout system) that automatically pays out virtual resources in response to a virtual resource request from an end user, fixed allocation of CPU resources cannot be performed automatically.

For this reason, for example, Non-Patent Document 1 discloses a method for fixedly allocating CPU resources by setting a range in which virtual CPUs are allocated to physical CPUs in the vcpu_pin_set parameter of a configuration file in OpenStack.
Non-Patent Document 2 discloses a method of assigning a virtual CPU to a physical CPU core by a virsh command.

OpenStack Foundation “Consider NUMA topology when booting instances”, [online], UPDATED: 2016-07-7 05:25, [Search 7/7/2016] Internet <URL: http://docs.openstack.org/admin -guide / cli-nova-numa-libvirt.html> redhat “Red Hat Enterprise Linux 6 Virtualization Tuning and Optimization Guide”, [online], 2013-10-31, [2016/7/7 search], Internet <URL: https://access.redhat.com/ documentation / en-US / Red_Hat_Enterprise_Linux / 6 / html-single / Virtualization_Tuning_and_Optimization_Guide / index.html # sect-Virtualization_Tuning_Optimization_Guide-NUMA-NUMA_and_libvirt-vcpu_pinning_with_virsh>

According to the prior art of Non-Patent Document 1 described above, fixed allocation of CPU resources is possible, but a plurality of virtual resources are allocated to a common physical CPU, and the physical CPU allocated to each virtual resource cannot be changed. There's a problem.
Further, according to the prior art of the above-mentioned Patent Document 2, fixed allocation of CPU resources is possible. However, because of setting by the command line, it is a procedure after automatic allocation of virtual resources, and the environment construction procedure becomes complicated. There is a problem.

  An object of the present invention is to provide a resource allocation device capable of changing the physical CPU (CPU core) allocated to each virtual resource and performing fixed allocation of virtual resources as part of automatic allocation in an automatic resource allocation system for virtual resources, To provide a resource allocation method and a resource allocation program.

In order to solve the above-described problem, the invention according to claim 1 is a resource allocation device for a virtual machine system, and includes a resource request having CPU resource designation information for fixedly allocating virtual CPUs in a one-to-one correspondence in CPU core units. An input unit for inputting information, a resource extraction unit for extracting a CPU resource that can be allocated based on the resource request information, an allocation destination resource selection unit for selecting a CPU resource to be allocated from the extracted resource, A resource fixed allocation unit for fixed allocation of CPU resources and a resource multiple allocation unit for multiple allocation of selected CPU resources are provided.
By doing so, it is possible to change the CPU core assigned to each virtual resource, and to automatically pay out the fixed assignment of the virtual resource, thereby facilitating the environment construction.

According to a second aspect of the present invention, in the resource allocation device according to the first aspect, the resource request information includes information that specifies a CPU usage rate of the CPU to be allocated, or information that specifies a CPU identification number of the CPU to be allocated. Alternatively, the instruction information for instructing fixed allocation includes at least one CPU resource specification information for fixed allocation.
I did it.
In this way, it is possible to easily specify a resource to be fixedly assigned.

According to a third aspect of the present invention, in the resource allocation device according to the first or second aspect, for each CPU resource that can be allocated, an identification number of the CPU resource and an upper limit of the CPU performance ratio that can be allocated. A resource management table storage unit including a multiplexing rate to represent and a CPU usage rate of the allocated CPU resource is provided.
By doing so, the CPU resource can be easily managed.

According to a fourth aspect of the present invention, in the resource allocation device according to the third aspect, the resource request information includes information specifying a CPU usage rate of the CPU to be allocated, and the resource extraction unit indicates the multiplexing rate. When the difference between the value and the value indicated by the CPU usage rate is equal to or higher than the CPU usage rate specified in the resource request information, the CPU is extracted as an assignable CPU.
In this way, it is possible to easily determine whether CPU resources can be allocated.

According to a fifth aspect of the present invention, in the resource allocation device according to any one of the first to fourth aspects, the resource fixed allocation unit specifies, in the resource request information, a CPU usage rate of a CPU to be allocated. When a value of 100% is specified, or a specific CPU resource is specified in the information specifying the CPU identification number of the CPU to be allocated, or instruction information instructing fixed allocation is specified The fixed allocation of the CPU resource selected by the allocation resource selection unit is performed.
In this way, it is possible to easily specify the CPU resource to be fixedly assigned.

The invention according to claim 6 is a resource allocation method for a virtual machine system, wherein resource request information having CPU resource designation information for fixedly allocating virtual CPUs on a one-to-one basis for each CPU core is input. A step of extracting a CPU resource that can be allocated based on the resource request information; a step of selecting a CPU resource to be allocated from the extracted resource; and a fixed allocation of the selected CPU resource or a selected CPU And a step of allocating multiple resources.
In this way, it is possible to automatically issue fixed allocation of virtual resources.

The invention according to claim 7 is the resource allocation method according to claim 6, wherein the resource request information includes information specifying a CPU usage rate of the CPU to be allocated, and sets an upper limit of the CPU performance ratio that can be allocated. The difference between the value indicated by the multiplexing rate and the value indicated by the CPU usage rate with reference to a resource management table that stores, for each assignable CPU resource, the indicated multiplexing rate and the CPU usage rate of the assigned CPU resource However, a CPU resource equal to or higher than the CPU usage rate specified in the resource request information is extracted as an assignable CPU resource.
By doing so, it is possible to easily manage the CPU resources, and it is possible to easily determine whether the CPU resources can be allocated.

The invention according to claim 8 is a resource allocation program, which is a resource allocation program for causing a computer to function as the resource allocation apparatus according to any one of claims 1 to 5.
In this way, fixed allocation of virtual resources can be performed automatically.

  According to the present invention, the CPU core allocated for each virtual resource can be changed, and the fixed allocation of the virtual resource can be performed automatically, so that the CPU core can be used effectively and the virtual computer system can be constructed. It can be done easily.

It is a figure explaining the process outline | summary of a resource allocation apparatus. It is a module block diagram of a resource allocation apparatus. It is an assignment processing outline flow chart of a resource assignment device. It is a figure explaining the definition content of the resource request information of a resource allocation apparatus. It is a figure which shows an example of a structure of the resource management table of a resource allocation apparatus. It is a processing flow of the extraction process of an allocatable resource. It is a figure explaining the extraction list | wrist of an allocatable resource.

First, an outline of processing of the resource allocation device 3 of the embodiment will be described with reference to FIG.
The resource allocation device 3 according to the embodiment manages resources in units of CPU cores in a system that automatically pays out virtual resources (virtual resource automatic payout system) in response to a virtual resource (VM) request from an end user. In response to a resource request, an allocatable CPU core is extracted, an allocation destination resource is selected, and a virtual resource subjected to fixed allocation is paid out.
In this specification, assigning virtual CPUs (virtual resources) on a CPU core (physical resource) basis on a one-to-one basis is referred to as fixed assignment, and assigning virtual CPUs including a one-to-one basis to CPU cores on an n-to-one basis. This is called multiple allocation.

  More specifically, the three virtual CPUs of the virtual resource VM # 1 (1a), the virtual resource VM # 2 (1b), and the virtual resource VM # 3 (1c) in FIG. 1 are assigned to the physical resource HW # 1 (2a). The physical resource HW # 2 (2b) and the physical resource HW # 3 (2c) are allocated to the respective 8 CPU cores. Needless to say, the number of CPU cores is not limited to eight.

  Here, the virtual resource VM # 1 (1a) has a virtual CPU and a physical resource so that the virtual resource VM # 1 (1a) becomes an occupation mode in which overhead can be reduced and performance bandwidth can be maintained in order to maintain performance / quality even by virtualization. The CPU core is assigned with a one-to-one fixed assignment. The virtual resource VM # 2 (1b) and the virtual resource VM # 3 (1c) are configured so that the virtual CPU is in a shared mode in which the CPU core of the physical resource can be shared (superposed) among a plurality of virtual CPUs. Assign to CPU core (multiple assignment).

Next, the configuration of the resource allocation device 3 of the embodiment will be described in detail with reference to the module configuration diagram of FIG. 2 and the allocation processing outline flowchart of FIG.
First, the module configuration will be described with reference to FIG.

  The resource allocation device 3 according to the embodiment includes a resource payout control unit 31 and a storage unit for the resource management table 32. Then, the resource payout control unit 31 refers to the resource management table 32 and assigns a physical resource having a free resource that satisfies the condition of the resource request information 4 input from the resource request unit 30 that allocates the virtual resource to the physical resource 2a. 2b, 2c, and 2d, one physical resource is selected, the requested virtual resource is allocated to the selected physical resource, and resource allocation information that is the allocation result is notified to the resource request unit 30.

  The resource payout control unit 31 includes a request reception processing unit 311, a resource management unit 312, an allocatable resource extraction unit 313, an allocation destination resource selection unit 314, a resource fixed allocation unit 315, and a resource multiple allocation unit 316.

Here, the request reception processing unit 311 inputs / outputs resource request information 4 and resource payout information, which will be described later, and performs a cooperative operation of processing modules described below.
Based on the resource management table 32 that holds the resource status of each physical resource CPU core, the resource management unit 312 manages the allocation-destination resource and the fixedly assigned CPU core when generating the virtual resource.

The allocatable resource extraction unit 313 cooperates with the resource management unit 312 to obtain a list of allocatable resources (allocation destination physical resource candidates) that satisfy the condition of the resource request information 4 by an extraction method described later.
The allocation destination resource selection unit 314 determines an allocation destination physical resource and an allocation destination CPU core of each virtual CPU from a list of allocatable resources (allocation destination physical resource candidates) according to a predetermined rule.

The resource fixed allocation unit 315 is a processing unit that performs fixed allocation of the CPU selected by the allocation destination resource selection unit 314.
The resource multiple allocation unit 316 is a processing unit that performs multiple allocation of CPUs selected by the allocation destination resource selection unit 314.

Next, the resource allocation device 3 according to the embodiment will be described in more detail with reference to the allocation processing outline flowchart of FIG.
First, the request reception processing unit 311 (see FIG. 2) of the resource allocation device 3 receives the resource request information 4 shown in FIG. 4 as an example (step S31).

Here, the definition content of the resource request information 4 will be described with reference to FIG.
The resource request information 4 in FIG. 4 defines the allocation condition (attribute) of the virtual CPU to be allocated, and sets the number of virtual CPUs to be allocated by the num_vcpu attribute. Then, the allocation condition of each virtual CPU is set by the vcpu0 attribute, vcpu1 attribute,..., Vcpu5 attribute.

Furthermore, virtual CPU relations (pair / range list) that cannot be assigned to the same CPU core are set by the anti-affinity attribute. In FIG. 4, since the virtual CPUs vcpu0 to vcpu5 cannot be assigned to the same CPU core, the virtual CPUs are assigned to different (six) CPU cores.
The allocation condition (attribute) of the virtual CPU includes a load parameter indicating the virtual CPU usage rate, a core parameter specifying the allocation CPU core, and a role parameter specifying the allocation importance.

  Although details will be described later, in the allocation processing of the embodiment, the load parameter of the resource request information 4 is set to 100% to perform fixed allocation of virtual CPUs. However, an occupying attribute for designating a fixedly assigned CPU core may be provided and designated directly.

  Returning to FIG. 3, the request reception processing unit 311 that has received the resource request information 4 activates the allocatable resource extraction unit 313. The allocatable resource extraction unit 313 performs an allocatable resource extraction process in cooperation with the resource management unit 312 that manages the resource management table 32 (S32).

FIG. 5 is a diagram illustrating an example of the configuration of the resource management table 32.
The resource management table 32 includes an HW item 321 that is identification information (access ID) of a physical resource identified by a host name, an IP address, and the like, a core item 322 that is identification information of a CPU core, and a reference CPU performance. CPU core performance ratio (CPU performance ratio), a multiplexing rate 323 that represents the upper limit of the assignable CPU usage rate, a usage rate 324 that represents the accumulated CPU usage rate of the allocated virtual CPU, a virtual CPU and its virtual And an allocation destination 326 representing a resource.
The resource management unit 312 uses a pair of the HW item 321 and the core item 322 as a management unit.

Further, the resource management table 32 may have a status item 325 indicating an allocation status so that a CPU core to which a virtual CPU is fixedly allocated is not allocated by multiple resource request information 4. For example, “occupied” is set in the state item 325 of the CPU core that is fixedly assigned, and “shared” is set in the state item 325 of the CPU core to which other virtual CPUs can be assigned.
The status item 325 indicating the allocation status is not limited to “occupied”, but the CPU core usage rate 324 that is uniquely allocated is changed to a value of the multiplexing rate 323 that represents the upper limit of the CPU usage rate of the CPU core. However, multiple allocation of other CPU resources can be prevented.

In FIG. 5, the value of the multiplexing rate 323 in the resource management table 32 is 100%, but 100% is not the upper limit value, and is set according to the performance ratio of the physical resource. For high-performance physical resources, a value larger than 100% is set. Thereby, even in a system composed of physical resources having different performances, resource allocation can be performed based on one resource request information 4.
In FIG. 5, the CPU core whose HW item 321 is “# 0” and the core item 322 is “0” and whose allocation destination 326 is “for Host OS” is that the multiplexing rate 323 is 0%, and the virtual resource is stored in the CPU core. It is not assigned. As a result, the operation occupied by the HostOS is performed.

Returning to FIG. 3, the assignable resource extraction process in step S32 will be described.
FIG. 6 is a detailed process flow of an allocatable resource extraction process performed by the allocatable resource extraction unit 313.
In the processing flow of FIG. 6, whether or not allocation is possible is determined for each allocation core that is a CPU core specified by a pair of the HW item 321 and the core item 322 of the resource management table 32 illustrated in FIG. An extraction list 7 of possible resources is created.

  7 includes an HW item 71 that is physical resource identification information, a core item 72 that is CPU core identification information, and a multiplexing rate 73 that represents the upper limit of the CPU performance ratio of the CPU core. , Vcpu0 (75), Vcpu1 (76),..., Vcpu5 (78), which are items for recording the determination result of whether or not the virtual CPU can be allocated. Here, the HW item 71, the core item 72, and the multiplexing rate 73 correspond to the resource management table 32 of FIG.

Returning to FIG. 6, the processing flow will be described.
In step S601, the allocatable resource extraction unit 313 starts the processing up to step S614, which is repeated for each virtual CPU by the number of virtual CPUs set in the num_vcpu attribute of the resource request information 4.
In step S602, the allocatable resource extraction unit 313 starts the processing up to step S606, which is repeated for each allocation core (allocation CPU core) specified by the core parameter.

In step S603, it is determined whether the value obtained by subtracting the usage rate 324 from the multiplexing rate 323 for each assigned core is equal to or greater than the request usage rate set in the load parameter of the resource request information 4. That is, it is determined whether or not the required performance is satisfied when a virtual CPU is assigned to a CPU core.
If it is equal to or greater than the required usage rate (Yes in S603), the process proceeds to step S604, where “permitted” is recorded in the allocatable resource extraction list 7 and allocation is set. Further, the required usage rate is added to the usage rate 74. Then, the process proceeds to step S606, and the next assigned core is processed. If it is less than the requested usage rate (No in S603), the process proceeds to step S605, where “impossible” is recorded in the assignable resource extraction list 7 and assignment is disabled. Then, the process proceeds to step S606, and the next assigned core is processed.

When the iterative processing for each allocation core from step S602 to step S606 is completed, the role parameter of the resource request information 4 is determined (step S607), and if the role parameter is “must” meaning that the allocation importance is essential (step S607). In step S607, the process proceeds to step S614, where the next virtual CPU is processed. If the role parameter is “should” meaning assignment within a range where assignment importance is possible (should be step S607), the process proceeds to step S608.
In step S608, it is determined whether the virtual CPU can be assigned to the assigned core (assigned CPU core) specified by the core parameter. If the virtual CPU can be assigned to any assigned CPU core (Yes in S608), In step S614, the next virtual CPU is processed.

  In step S608, if the virtual CPU could not be allocated to the allocation core (allocation CPU core) specified by the core parameter (No in S608), the allocation core specified by the core parameter (No in S608) (step S613) Whether or not a virtual CPU can be allocated to other than (allocated CPU core) is determined. Since the processing contents are the same as those in steps S602 to S606, description thereof will be omitted.

In step S614, when the allocation of the virtual CPU specified by the resource request information 4 is completed, the process proceeds to step S615, and it is determined whether there is an allocation combination that satisfies the HW allocation condition such as the anti-affinity attribute. If the HW allocation condition is satisfied (Yes in S615), the process ends. When the HW allocation condition is not satisfied (No in S615), a process of changing to another HW such as the physical resource HW # 2 (2b) (see FIG. 1) is performed (Step S616), and the process from Step S601 is performed. Repeat the process.
Instead of performing the determination in step S615, the allocatable resource extraction process in steps S601 to S614 may be performed for all physical resources HW, and the allocation destination HW selection process described later may be performed.
Through the above-described processing, the allocatable resource extraction unit 313 creates the allocatable resource extraction list 7.

  Further, the allocatable resource extraction processing from step S601 to step S614 may be performed for a virtual CPU whose role parameter is “must” and then for a virtual CPU whose role parameter is “should”. As a result, it is possible to extract with priority given to the allocation of the virtual CPU whose role parameter is “must”.

Returning to FIG. 3, the assignment destination HW selection process in step S33 will be described.
The allocation destination resource selection unit 314 that performs allocation destination HW selection processing refers to the allocation list 7 of the allocatable resources, and when the virtual CPU can be allocated to a plurality of physical resources (HW), A physical resource (HW) is selected.

  More specifically, when there are allocation cores (allocation CPU cores) that are multiple extracted as allocation candidates by core parameters of a plurality of virtual CPUs, CPU cores are allocated in preference to virtual CPUs whose role parameter is “must”. The selection process is performed as follows.

The selection of the specific physical resource (HW) can select a physical resource (HW) having a minimum sum of usage rates of CPU cores that can be allocated from the viewpoint of load distribution.
Further, from the viewpoint of physical resource usage efficiency, a physical resource (HW) having the maximum sum of usage rates of CPU cores that can be allocated may be selected.
If one virtual CPU can be assigned to a plurality of CPU cores, the core item is assigned to a CPU core having a lower number.

  Next, in step S34, it is determined whether or not the virtual CPU allocation is a fixed allocation request. This determination is specified in the resource request information 4 when the core parameter is specified (including range specification) and the load parameter is specified as 100% or when the occupying attribute is specified. This is done by determining whether it has been done.

If the allocation of the virtual CPU is a fixed allocation request in step S34 (Yes in S34), the fixed resource allocation unit 315 performs a fixed allocation process (step S35).
This fixed allocation process is performed by issuing a libvirt command (vcpupin). Further, a virtual resource (VM) definition file may be generated.

  If the allocation of the virtual CPU is not a fixed allocation request in step S34 (No in S34), the resource multiple allocation unit 316 performs multiple allocation processing (step S36).

In step S37, for the CPU cores that are fixedly allocated, the usage rate 324 of the resource management table 32 is set to the multiplexing rate 323 to prevent multiple allocation.
Furthermore, the CPU core allocation destination virtual CPU name is set in the allocation destination 326 of the resource management table 32.
The resource management table 32 is updated by the above processing.

Further, in step S37, the value of the status item 325 of the resource management table 32 may be set to “occupied” for the fixedly assigned CPU core.
As a result, the value of the state item 325 of the resource management table 32 is set to “occupied” for the fixedly assigned CPU core, so when determining whether or not to allocate in step S32 of the allocation process of other virtual CPUs, By excluding allocation cores (allocation CPU cores) whose status item 325 is “occupied” from the target allocation cores (allocation CPU cores), multiple allocation to CPU cores is prevented.

  Finally, in step S38, the resource allocation information is returned to the resource request unit 30 (see FIG. 2), and the resource allocation process of the resource allocation device 3 of the embodiment is ended.

  By the way, the resource allocation device 3 of the embodiment is an information processing device that is equipped with a CPU (Central Processing Unit), and that implements a hard disk drive, ROM (Read only memory), and RAM (Random access memory) for storing programs and data. The CPU can execute the resource allocation program recorded on the hard disk drive.

3 Resource allocation device 30 Resource request unit 31 Resource payout control unit 311 Request reception processing unit (input unit)
312 Resource management unit 313 Assignable resource extraction unit (resource extraction unit)
314 Allocation destination resource selection unit 315 Resource fixed allocation unit 316 Resource multiple allocation unit 32 Resource management table 2a, 2b, 2c, 2d Physical resource

Claims (8)

A resource allocation device for a virtual machine system,
An input unit for receiving resource request information having CPU resource designation information for fixedly assigning virtual CPUs in a one-to-one basis for each CPU core;
A resource extraction unit that extracts an assignable CPU resource based on the resource request information;
An allocation resource selection unit that selects a CPU resource to be allocated from the extracted resources;
A fixed resource allocation unit for fixed allocation of the selected CPU resource;
A resource multiplex allocation unit that multiplexly allocates the selected CPU resources;
A resource allocation device comprising: The resource allocation device according to claim 1,
The resource request information is
Information specifying the CPU usage rate of the CPU to be allocated, information specifying the CPU identification number of the CPU to be allocated, or specifying information of the CPU resource to be fixedly allocated of at least one instruction information for instructing fixed allocation Resource allocation device. In the resource allocation device according to claim 1 or 2,
Further, for each assignable CPU resource, a resource management table storage unit including an identification number of the CPU resource, a multiplexing rate indicating an upper limit of the assignable CPU usage rate, and a CPU usage rate of the assigned CPU resource. A resource allocating device comprising: The resource allocation device according to claim 3,
The resource request information includes information for specifying a CPU usage rate of an assigned CPU,
The resource extraction unit extracts a CPU as an assignable CPU when the difference between the value indicated by the multiplexing rate and the value indicated by the CPU usage rate is equal to or higher than the CPU usage rate specified in the resource request information. Resource allocation device. In the resource allocation apparatus in any one of Claims 1-4,
In the resource request information, the resource fixed allocation unit is designated with a value indicating the upper limit of the CPU usage rate of the CPU resource to be assigned to the information for designating the CPU usage rate of the CPU to be assigned, and specifies the CPU identification number of the CPU to be assigned When a specific CPU resource is specified in the information to be performed, or when instruction information for instructing fixed allocation is specified, the CPU resource selected by the allocation destination resource selection unit is fixedly allocated. A resource allocation device characterized by the above. A resource allocation method for a virtual machine system,
A step of inputting resource request information having CPU resource designation information for fixedly assigning a virtual CPU to a CPU core one-to-one;
Extracting an assignable CPU resource based on the resource request information;
Selecting a CPU resource to be allocated from the extracted resources;
Fixed allocation of selected CPU resources;
A resource allocation method comprising: The resource allocation method according to claim 6,
The resource request information includes information specifying the CPU usage rate of the CPU to be allocated,
With reference to a resource management table that stores a multiplexing rate representing the upper limit of the assignable CPU usage rate and a CPU usage rate of the assigned CPU resource for each assignable CPU resource, A resource allocation method, wherein a CPU resource whose difference from a value indicated by a CPU usage rate is equal to or higher than a CPU usage rate specified in the resource request information is extracted as an allocatable CPU resource.   A resource allocation program for causing a computer to function as the resource allocation device according to any one of claims 1 to 5.