JP6040083B2 - Management server device, information processing method, and program - Google Patents

Description

  The present invention relates to a management server device, an information processing method, and a program.

Systems that reduce resource ownership costs and operation management costs by aggregating virtual servers on resources using server virtualization technology are known.
As an example, we determine the predicted peak usage for each time interval from the resource usage history, solve the optimization problem that minimizes the total amount of resources, and derive the placement configuration (allocation) of the virtual machine An allocation method has been proposed (Patent Document 1).

JP2012-159928A

However, since the technique disclosed in Patent Document 1 derives resource allocation based on past performance values, the calculation amount is enormous, and in addition, the resource allocation is estimated when there is no similar performance in the past. There is a problem that cannot be done.
On the other hand, there has been a need for an allocation method for planning that allocates resources according to service demand. In the allocation method of the planning system, since the future demand value is given in advance at the time of allocation planning, the amount of calculation can be reduced, and furthermore, the allocation can be estimated even if there is no past actual value.
Here, when allocating a plurality of virtual servers to be planned, it is required that the virtual servers be aggregated and allocated as much as possible based on the virtual server information (for example, information indicating the allocation period and allocated capacity). However, it has been difficult to appropriately aggregate a plurality of virtual servers having various allocation periods and allocation capacities.
An object of the present invention is to consolidate virtual servers for each period of an optimal processing unit when performing allocation.

Therefore, the management server device of the present invention includes a management unit that manages a plurality of virtual server information including allocation request period information indicating an allocation request period related to resource allocation of a virtual server, and a plurality of management servers managed by the management unit. When the allocation request periods indicated by the allocation request period information of the virtual server information overlap, a plurality of virtual servers including the allocation request period information related to the overlapped allocation request periods based on the allocation request period information related to the overlapped allocation request periods a dividing means for dividing each information, and a allocation determining means for determining the allocation destination information is assigned resources to each virtual server information divided by said dividing means.

  According to the present invention, when performing allocation, virtual servers can be aggregated for each period of an optimal processing unit.

FIG. 1 is a diagram illustrating an example of a system configuration. FIG. 2 is a diagram illustrating an example of a hardware configuration of the management server device. FIG. 3 is a diagram illustrating an example of a software configuration of the management server device. FIG. 4 is a diagram illustrating an example of virtual server information according to the first embodiment. FIG. 5 is a diagram illustrating an example of the concept of virtual server information according to the first embodiment. FIG. 6 is a diagram illustrating an example of resource information. FIG. 7 is a diagram illustrating an example of table data of allocation management information. FIG. 8 is a flowchart illustrating an example of processing according to the first embodiment. FIG. 9 is a flowchart illustrating an example of the assignment destination determination process. FIG. 10 is a diagram illustrating an example of virtual server information according to the second embodiment. FIG. 11 is a diagram illustrating an example of the concept of virtual server information according to the second embodiment. FIG. 12 is a flowchart illustrating an example of processing according to the second embodiment. FIG. 13 is a flowchart illustrating an example of processing according to the third embodiment. FIG. 14 is a flowchart illustrating an example of processing according to the fourth embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<Embodiment 1>
FIG. 1 is a diagram illustrating an example of a system configuration of a system according to the present embodiment.
The system according to the present embodiment includes a cloud system 10, a network 14, and a client device 15.
The cloud system 10 includes a plurality of physical server devices connected to each other via a LAN (Local Area Network) 12 and the like, and a management server device 13 that manages the physical server devices. In the present embodiment, for convenience of explanation, the cloud system 10 includes three physical servers 11a, 11b, and 11c (hereinafter, the physical server devices 11a, 11b, and 11c are collectively referred to as the physical server device 11). A description will be given on the assumption that the server apparatus has one management server apparatus 13 that manages the physical server apparatus 11. However, the number of physical server devices and management server devices in the cloud system 10 need not be limited to this. The physical server device 11 is an example of a resource.

The client device 15 transmits virtual server information related to the virtual server assigned to the physical server device 11 to the management server device 13 via the network 14. Details of the virtual server information will be described later with reference to FIG.
The management server device 13 assigns a virtual server to the physical server device 11 based on the resource information of the managed physical server device 11 and the virtual server information received from the client device 15. The resource information will be described later with reference to FIG. Details of the virtual server allocation processing by the management server device 13 will be described later with reference to FIGS.
The physical server device 11 has physical resources such as a processor, a memory, and a disk.
In the following description, the physical server device 11 is referred to as a resource, and the processor, memory, disk, and the like included in the physical server device 11 are referred to as physical resources.

FIG. 2 is a diagram illustrating an example of a hardware configuration of the management server device 13.
The management server device 13 includes an input device 24, a display device 25, a recording medium drive device 26, a ROM (Read Only Memory) 28, a RAM (Random Access Memory) 29, a CPU (Central Processing Unit) 21, and an interface as hardware configurations. A device 22 and an HD (Hard Disk) 23 are included.

The input device 24 includes a keyboard and a mouse that are operated by an administrator of the management server device 13, and is used to input various operation information and the like to the management server device 13.
The display device 25 includes a display or the like used by the administrator of the management server device 13 and is used to display various information or screens.
The interface device 22 is an interface that connects the management server device 13 to a network or the like.

  The program of the management server device 13 is provided to the management server device 13 by a recording medium 27 such as a CD-ROM or downloaded through a network or the like. The recording medium 27 is set in the recording medium drive device 26, and the program is installed from the recording medium 27 to the HD 23 via the recording medium drive device 26. The HD 23 is an example of a storage device.

The ROM 28 stores a program that is read first when the management server device 13 is powered on.
The RAM 29 is a main memory of the management server device 13.
If necessary, the CPU 21 reads a program from the HD 23, stores it in the RAM 29, and executes the program, thereby realizing a function (software configuration) of the management server device 13 described later and a process related to a flowchart.

In addition to the program executed by the CPU 21, the HD 23 stores, for example, the above-described virtual server information, resource information, allocation management information described later, and the like. Note that all or some of the virtual server information, resource information, allocation management information, etc. may be stored in the HD of other devices connected to the management server device 13 via the network. . However, hereinafter, for convenience of explanation, the virtual server information, the resource information, the allocation management information, and the like will be described as being stored in the HD 23 of the management server device 13. The allocation management information will be described later with reference to FIG.
Note that the hardware configurations of the physical server device 11 and the client device 15 in the present embodiment are also the same as the hardware configuration shown in FIG.
Further, the CPU 21 of the physical server device 11 implements the above-described virtual server by executing a program read from the HD 23 of the physical server device 11.

FIG. 3 is a diagram illustrating an example of a software configuration of the management server device 13.
The management unit 31 stores and manages a plurality of virtual server information received from the client device 15 in the HD 23. Hereinafter, the virtual server information will be described.
FIG. 4 is a diagram illustrating an example of virtual server information.
The virtual server information includes allocation request period information indicating an allocation request period when a virtual server is allocated to the physical server device 11, and allocation request capacity information indicating a resource capacity necessary for virtual server allocation. In the present embodiment, the allocation request period indicated by the allocation request period information is a date, but it may be date / time information including information such as time.

In the case of the example of FIG. 4A, the management unit 31 requires allocation of 2 VCPUs (Virtual Central Processing Unit) from January 1 to January 4 (hereinafter simply referred to as 1/1 to 1/4). The virtual server information of the virtual server (V1) is managed. Furthermore, the management unit 31 manages virtual server information of a virtual server (referred to as V2) that requires 2V CPU allocation from 1/3 to 1/6.
In the example of FIG. 4B, the management unit 31 manages virtual server information of a virtual server (referred to as V1) that requires allocation of 2 VCPU from 1/1 to 1/6. Furthermore, the management unit 31 manages virtual server information of a virtual server (referred to as V2) that requires 2 VCPU allocation from 1/2 to 1/4.
In the present embodiment, for convenience of explanation, the management unit 31 manages two pieces of virtual server information, but may manage three or more pieces of virtual server information. Moreover, although the physical resource required for the allocation of the virtual server is a processor, it may be a memory or the like. In this case, the management unit 31 manages virtual server information in which attribute information indicating the type of physical resource, allocation request capacity information, and allocation request period information are associated with each other as illustrated in FIG. In the case of the example of FIG. 4C, the management unit 31 manages virtual server information of a virtual server (referred to as V1) that requires allocation of a 1 VCPU processor and a 1 GB memory from 1/1 to 1/4. ing.

When the allocation request periods based on the allocation request period information of the plurality of virtual server information managed by the management unit 31 overlap, the dividing unit 32 determines the overlapping allocation based on the allocation request period information of the overlapping allocation request period. The virtual server information including the request period allocation request period information is divided. Hereinafter, the details of the dividing process by the dividing unit 32 will be described.
FIG. 5 is a diagram illustrating an example of the concept of virtual server information.
FIG. 5A is a diagram illustrating an example of a concept before the dividing unit 32 divides the virtual server information illustrated in FIG. On the other hand, FIG.5 (b) is a figure which shows an example of the concept at the time of the division | segmentation part 32 dividing | segmenting the virtual server information shown by Fig.4 (a). FIG. 5C is a diagram illustrating an example of a concept before the dividing unit 32 divides the virtual server information illustrated in FIG. On the other hand, FIG.5 (d) is a figure which shows an example of the concept at the time of the division | segmentation part 32 dividing | segmenting the virtual server information shown by FIG.4 (b).

First, the case where the dividing unit 32 divides the virtual server information shown in FIG. 4A will be described with reference to FIG.
In the example of FIG. 4A, the period in which the allocation request period of the virtual server V1 and the allocation request period of the virtual server V2 overlap is from 1/3 to 1/4. In this case, the dividing unit 32 divides the virtual server information of the virtual server V1 using 1/3 which is the allocation start date and time of the allocation request period of the virtual server V2 as a new allocation end date and time and a new allocation start date and time of the virtual server V1. To do. Further, the dividing unit 32 divides the virtual server information of the virtual server V2 by using 1/4 as the allocation end date / time of the allocation request period of the virtual server V1 as a new allocation end date / time and a new allocation start date / time of the virtual server V2. .

More specifically, the dividing unit 32 divides the virtual server information of the virtual server V1 into virtual server information of 1/1 to 1/3 and 1/3 to 1/4. Further, the dividing unit 32 divides the virtual server information of the virtual server V2 into virtual server information of 1/3 to 1/4 and 1/4 to 1/6.
Here, the virtual server information of the virtual server V1 divided by the dividing unit 32 will be referred to as V1-1 and V1-2 in order of the assigned date and time. In addition, the virtual server information of the virtual server V2 divided by the dividing unit 32 is referred to as V2-1 and V2-2 in order of the assigned date and time.
In FIG. 5B, the case where there are two virtual server information has been described as an example. However, the dividing unit 32 divides the virtual server information by the same process even when there are three or more virtual server information.

Next, the case where the dividing unit 32 divides the virtual server information shown in FIG. 4B will be described with reference to FIG.
The example of FIG. 4B is different from the example of FIG. 4A in that the entire allocation request period of the virtual server V2 is included in the allocation request period of the virtual server V1.
In the example of FIG. 4B, the period in which the allocation request period of the virtual server V1 and the allocation request period of the virtual server V2 overlap is from 1/2 to 1/4. In this case, the dividing unit 32 divides the virtual server information of the virtual server V1 with 1/2 as the allocation start date / time of the allocation request period of the virtual server V2 as the new allocation end date / time and the new allocation start date / time of the virtual server V1. To do. Further, the dividing unit 32 divides the virtual server information of the virtual server V1 by using 1/4 as the allocation end date / time of the allocation request period of the virtual server V2 as a new allocation end date / time and a new allocation start date / time of the virtual server V1. .

More specifically, the dividing unit 32 determines virtual server information of the virtual server V1 from 1/1 to 1/2, 1/2 to 1/4, and 1/4 to 1/6. Divide into server information. On the other hand, the dividing unit 32 does not divide the virtual server information of the virtual server V2.
Here, the virtual server information of the virtual server V1 divided by the dividing unit 32 is referred to as V1-1, V1-2, and V1-3 in order of the assigned date and time. The virtual server information of the virtual server V2 that has not been divided by the dividing unit 32 is referred to as V2-1.
In FIG. 5D, the case where there are two virtual server information has been described as an example. However, the dividing unit 32 divides the virtual server information by the same process even when there are three or more virtual server information.
Through the above processing, the management server device 13 divides the virtual server information based on the overlap of the virtual server allocation request periods in the plurality of virtual server information. Thereby, the management server device 13 can divide the virtual server information in a period of an optimal processing unit that can reduce the calculation amount when executing the allocation process. Conversely, if the management server device 13 does not perform the above-described division processing, it may require an excessive amount of calculation when executing the allocation processing. For example, when the virtual server information having a fixed allocation request capacity is divided into a plurality of pieces, the management server device 13 can execute the allocation process in a certain period of time by a single calculation, although the allocation process can be completed by a single calculation. May require calculation. The details of the allocation process will be described later with reference to FIGS.

Returning to the description of FIG. 3, the allocation determination unit 33 determines the physical server device 11 to which a virtual server is allocated for each virtual server information divided by the division unit 32. The process in which the allocation determination unit 33 determines the physical server device 11 to which the virtual server is allocated is an example of an allocation destination determination process that determines allocation destination information of the allocation destination.
FIG. 6 is a diagram illustrating an example of resource information held by the management server device 13.
Here, it is assumed that the management server device 13 holds resource information of resources managed by the management server device 13 as shown in FIG.
For each physical server device 11, the management server device 13 associates resource capacity information, assignable period information to which a virtual server can be assigned, and assignment prohibition period information to which a virtual server cannot be assigned as resource information. I manage.

In the example of FIG. 6A, the management server device 13 manages resource information of the physical server device 11a and the physical server device 11b. The physical server device 11a has a resource capacity of 2 VCPU, and is a resource that can allocate virtual servers from 1/1 to 1/10. On the other hand, the physical server device 11b has a resource capacity of 2 VCPU and can allocate virtual servers from 1/1 to 1/8, but allocates virtual servers from 1/9 to 1/10. This resource cannot be used.
In the present embodiment, resource information in the case where a physical resource is a processor will be described, but the physical resource may be a memory or the like. In this case, the management server device 13, as shown in FIG. 6B, for each physical server device 11, attribute information indicating the type of physical resource, resource capacity information, assignable period information, and assignment prohibition. Manages virtual server information associated with period information. In the example of FIG. 6B, the management server device 13 manages the resource information of the physical server device 11a. The physical server device 11a has a resource capacity of a 1 VCPU processor and a 1 GB memory, both of which are resources to which virtual servers can be allocated from 1/1 to 1/10.

The allocation determining unit 33 determines the physical server device 11 to which the virtual server is allocated for each virtual server information divided by the dividing unit 32 based on the resource information and the virtual server information. At that time, the allocation determination unit 33 obtains a solution to the optimization problem that minimizes the number of physical server devices 11 (number of resources) required for virtual server allocation based on the resource information and the virtual server information. . Then, the allocation determining unit 33 determines the physical server device 11 to which the virtual server is allocated for each virtual server information divided by the dividing unit 32 based on the obtained solution. Details of the virtual server allocation destination determination process by the allocation determination unit 33 will be described later with reference to FIG.
With the above processing, the management server device 13 solves the optimization problem that minimizes the number of physical server devices 11 to which the virtual server of the divided virtual server information is allocated as an objective function, and based on the obtained solution, Allocation destination information is determined for each divided virtual server information. That is, the management server device 13 can aggregate the virtual servers of the divided virtual server information and assign them to the physical server device 11.

The allocation management unit 34 assigns, for each virtual server information divided by the dividing unit 32, allocation period information indicating an allocation period in which the virtual server is actually allocated to the physical server device 11, allocation capacity information indicating allocation capacity, and allocation The table data of the allocation management information that associates the allocation destination information determined by the determination unit 33 is managed.
FIG. 7 is a diagram illustrating an example of table data of allocation management information.
7 shows a state where the management unit 31 has the virtual server information shown in FIG. 4A and the management server device 13 holds the resource information shown in FIG. This is the table data of the allocation management information when the allocation destination is determined in.
Through the above processing, the management server device 13 can manage the allocation status of the virtual servers for the managed physical server device 11 as table data.

FIG. 8 is a flowchart illustrating an example of information processing of the management server device 13 in the present embodiment.
For example, for each period information stored in advance in the HD 23, the management server device 13 executes the following processing on the virtual server information stored and managed in the HD 23 by the management unit 31. That is, the management server device 13 executes the following processing on the virtual server information by batch processing. The management server device 13 may execute the following processing when receiving a processing start instruction from the user via the input device 24.
In S81, the management unit 31 determines whether there is a plurality of virtual server information stored and managed in the HD 23. If it is determined that there are a plurality, the process proceeds to S82. On the other hand, if the management unit 31 determines in step S81 that there is not a plurality of virtual server information, the management unit 31 stands by. The virtual server information stored in the HD 23 is virtual server information received from the client device 15 by the management server device 13.

  In S82, the management unit 31 determines whether or not there is an overlap in the virtual server allocation request periods in the plurality of virtual server information. If it is determined that there is an overlap, the process proceeds to S83. On the other hand, if the management unit 31 determines in S82 that the allocation request periods do not overlap, the process proceeds to S84. More specifically, the management unit 31 determines whether or not there is an overlap of allocation request periods indicated by the allocation request period information of a plurality of virtual server information as illustrated in FIG. 4A or 4B. judge.

  In S83, the dividing unit 32 divides the virtual server information including the allocation request period information of the overlapped allocation request periods based on the allocation request period information of the overlapping allocation request periods. In the example shown in FIG. 5B, the dividing unit 32 divides the virtual server information of the virtual server V1 by ３, and divides the virtual server information of the virtual server V2 by ¼. On the other hand, in the example shown in FIG. 5D, the dividing unit 32 divides the virtual server information of the virtual server V1 by 1/2 and 1/4. The dividing unit 32 divides the virtual server information by the same process even when there are three or more pieces of virtual server information.

In S84, the allocation determination unit 33 determines the physical server device 11 to which the virtual server is allocated for each divided virtual server information. If it is determined in S82 that the allocation request periods do not overlap, the allocation determining unit 33 determines allocation destination information for the virtual server information that is not divided. Here, a case will be described as an example in which the allocation determination unit 33 determines allocation destination information for the divided virtual server information. Details of the process of S84 will be described later with reference to FIG.
In S85, the allocation management unit 34 assigns allocation management information in which allocation period information for each divided virtual server information, allocation capacity information, and allocation destination information determined in S84 are associated as shown in FIG. Update and end the process. The allocation management unit 34 stores and manages allocation management information in the HD 23 as table data.

FIG. 9 is a flowchart illustrating an example of an assignment destination determination process by the assignment determination unit 33.
In S91, the allocation determination unit 33 searches the table data managed by the allocation management unit 34, determines whether there is a virtual server for which the allocation-destination physical server device 11 has been determined, and determines that there is If so, the process proceeds to S92. On the other hand, if the allocation determination unit 33 determines in S91 that there is no virtual server that has been determined by the allocation-destination physical server device 11, the process proceeds to S93.

  In S92, the allocation determination unit 33 obtains the remaining resource capacity of the physical server device 11 that can be used for virtual server allocation. More specifically, the allocation determination unit 33 determines the remaining resource based on allocation management information related to the virtual server whose allocation destination has been determined searched in S91 and resource information held by the management server device 13. Find capacity. For example, it is assumed that the allocation management information searched by the allocation determination unit 33 indicates that there is a virtual server allocated to the physical server device 11a with an allocation capacity of 1 VCPU from 1/1 to 1/2. Furthermore, it is assumed that the management server device 13 holds the resource information shown in FIG. In this case, the allocation determination unit 33 determines that the remaining resource capacity of the physical server device 11a is 1 VCPU from 1/1 to 1/2, and 2 VCPU from 1/2 to 1/10. Further, since there is no virtual server that has been determined to be allocated to the physical server device 11b, the allocation determination unit 33 determines that the remaining resource capacity of the physical server device 11b is 2 VCPU from 1/1 to 1/8.

  In S93, the allocation determination unit 33 obtains the resource capacity based on the resource information held by the management server device 13 as the remaining resource capacity that can be used for virtual server allocation. For example, when the management server device 13 holds the resource information shown in FIG. 6A, the allocation determination unit 33 is 2 VCPU from 1/1 to 1/10 of the remaining resource capacity of the physical server device 11a. I ask. Further, the allocation determining unit 33 determines that the remaining resource capacity of the physical server device 11b is 2 VCPU from 1/1 to 1/8.

  In S94, the allocation determination unit 33 finds a solution for an optimization problem that minimizes the number of physical server apparatuses 11 required for virtual server allocation as an objective function. This is because the running cost of the physical server device 11 can be reduced by reducing the number of activated physical server devices 11. Here, the allocation determination unit 33 sets a constraint condition that ensures that the required resource capacity of the virtual server in the divided virtual server information is within the remaining resource capacity obtained in S92 or S93 in the allocation period. At that time, the allocation determining unit 33 sets the constraint condition on the assumption that the resource capacity between the allocation prohibition of the virtual server indicated by the allocation prohibition information of the resource information is 0 VCPU. Then, the allocation determining unit 33 finds a solution for an optimization problem that minimizes the number of physical server devices 11 required for virtual server allocation in the divided virtual server information as an objective function based on the constraint condition.

Hereinafter, the details of the optimization problem solving process by the allocation determination unit 33 will be described.
Here, as an example, it is assumed that the remaining resource capacity is as described above in S93. Further, the dividing unit 32 divides the virtual server information shown in FIG. 4A into virtual server information as shown in FIG. 5B.
In this case, since the required resource capacity from 1/1 to 1/3 is 2 VCPU, the allocation determining unit 33 finds the number of necessary physical server devices as only one physical server device 11a. Further, the allocation determining unit 33 has a required resource capacity from 1/3 to 1/4 of 4 VCPU, and the physical server device 11a alone is not sufficient. Therefore, the number of required physical server devices is determined as the physical server device 11a and the physical server. Solve with two devices 11b. Further, since the necessary resource capacity from ¼ to ６ is 2 VCPU, the allocation determination unit 33 finds the number of necessary physical server devices as only one physical server device 11a.

In S95, the allocation determination unit 33 determines the physical server device 11 to which the virtual server is allocated for each divided virtual server information based on the solution of the optimization problem obtained in S94. For example, in the case of the example described above in S94, the assignment determination unit 33 determines assignment destination information of the assignment destination of the virtual server as illustrated in FIG.
Note that the allocation determination unit 33 may determine allocation destination information in order from virtual server information with earlier date information included in the allocation request period information. In this case, the dividing unit 32 sorts the divided virtual server information in order from the earliest date information included in the allocation request period information. Then, the allocation determination unit 33 performs allocation destination determination processing in the sorted order with respect to the divided virtual server information. Thereby, the allocation determination unit 33 can complete the allocation destination determination process in a practical time.

  As mentioned above, according to this embodiment mentioned above, the management server apparatus 13 divides | segments virtual server information based on the overlap of the allocation request | requirement period of the virtual server in several virtual server information. Thereby, the management server device 13 can divide the virtual server information in a period of an optimal processing unit that can reduce the calculation amount when executing the allocation process. Further, the management server device 13 solves an optimization problem that minimizes the number of physical server devices 11 to which virtual servers are assigned as an objective function, and assigns each divided virtual server information based on the found solution. Determine the destination information. As a result, the management server apparatus 13 can aggregate the allocation target virtual servers and allocate them to the physical server apparatus 11. That is, the management server device 13 can reduce resource ownership costs and operation management costs.

<Embodiment 2>
In the first embodiment, the case where the dividing unit 32 divides a plurality of pieces of virtual server information as illustrated in FIG. 4A or FIG. 4B has been described. More specifically, when the dividing unit 32 overlaps a part of the virtual server allocation request period of one virtual server information and a part of the virtual server allocation request period of the other virtual server information, The case has been described where the entire virtual server allocation request period of the virtual server information is included in the virtual server allocation request period of the other virtual server information.
In the present embodiment, a description will be given of a dividing process when the resource capacity required for virtual server allocation changes in the virtual server allocation request period of one virtual server information or other virtual server information.

FIG. 10 is a diagram illustrating an example of virtual server information.
In the example of FIG. 10, the virtual server information of the virtual server V1 indicates that there is a virtual server allocation request (V1 (1)) that requires 1 VCPU resource capacity from 1/1 to 1/2. . The virtual server information of the virtual server V1 indicates that there is a virtual server allocation request (referred to as V1 (2)) that requires a resource capacity of 2 VCPU from 1/2 to 1/4. Furthermore, the virtual server information of the virtual server V1 indicates that there is a virtual server allocation request (referred to as V1 (3)) that requires a resource capacity of 1 VCPU from ¼ to ６. On the other hand, the virtual server information of the virtual server V2 indicates that there is an allocation request for the virtual server 2 requiring 1 VCPU resource capacity from 1/3 to 1/7.

  When the resource capacity necessary for the virtual server allocation based on the allocation request capacity information included in the virtual server information of the virtual server V1 or the virtual server V2 changes in the allocation request period, the dividing unit 32 assigns the change date and time to the new allocation date. The virtual server information of the virtual server V1 and the virtual server V2 is divided as the end date and time and the new allocation start date and time. That is, in the example of FIG. 10, the dividing unit 32 uses the virtual server V1 as the new allocation end date and time and the new allocation start date and time as 1/2 and 1/4 that are the change date and time of the required resource capacity. The virtual server information of V1 and virtual server V2 is divided. More specifically, the dividing unit 32 determines virtual server information of the virtual server V1 from 1/1 to 1/2, 1/2 to 1/4, and 1/4 to 1/6. Divide into server information. Further, the dividing unit 32 divides the virtual server information of the virtual server V2 into virtual server information of 1/3 to 1/4 and 1/4 to 1/7.

The dividing unit 32 divides the virtual server information in FIG. 10 based on the above dividing process and the dividing process described in the first embodiment.
FIG. 11 is a diagram illustrating an example of the concept of virtual server information.
FIG. 11A is a diagram illustrating an example of a concept before the dividing unit 32 divides the virtual server information illustrated in FIG. On the other hand, FIG.11 (b) is a figure which shows an example of the concept at the time of the division | segmentation part 32 dividing | segmenting the virtual server information shown by FIG.
More specifically, the dividing unit 32 sets the virtual server information of the virtual server V1 from 1/1 to 1/2, from 1/2 to 1/3, from 1/3 to 1/4, and 1 The virtual server information is divided into / 4 to 1/6. Further, the dividing unit 32 divides the virtual server information of the virtual server V2 into virtual server information of 1/3 to 1/4, 1/4 to 1/6, and 1/6 to 1/7. To do. Here, it is assumed that the virtual server information of the virtual server V1 divided by the dividing unit 32 is V1-1, V1-2, V1-3, and V1-4 in order from the earliest allocation date. Further, the virtual server information of the virtual server V2 divided by the dividing unit 32 is set to V2-1, V2-2, and V2-3 in order from the earliest allocation date.

FIG. 12 is a flowchart illustrating an example of information processing of the management server device 13 in the present embodiment.
The processing from S121 to S123 is the same as the processing from S81 to S83 in FIG.
In S124, the dividing unit 32 determines whether or not there is a change in the resource capacity necessary for virtual server allocation during the virtual server allocation request period. If it is determined that there is, the process proceeds to S125. On the other hand, if the dividing unit 32 determines in S124 that there is no change in the resource capacity, the process proceeds to S126.
In S125, the dividing unit 32 divides the virtual server information based on the date and time when the resource capacity required for virtual server allocation changes in the allocation request period. Note that the details of the processing of S124 and S125 are as described above with reference to FIGS. 10 and 11, and thus detailed description thereof is omitted.
The processing from S126 to S127 is the same as the processing from S84 to S85 in FIG.
The dividing unit 32 divides the virtual server information by the same process even when there are three or more pieces of virtual server information.

  As described above, according to this embodiment described above, the management server device 13 obtains virtual server information based on the overlap of the virtual server allocation request periods and the change in the required resource capacity in the allocation request period. To divide. As a result, the management server device 13 performs virtual processing in an optimal processing unit period that can reduce the amount of calculation when executing the allocation process even if the required resource amount changes within the allocation request period of the virtual server. Server information can be divided.

<Embodiment 3>
In this embodiment, after the processing by the management server device 13 as described in the first and second embodiments is completed, the management server device 13 receives an addition request related to virtual server allocation from the client device 15. Examples will be described.
FIG. 13 is a flowchart illustrating an example of information processing of the management server device 13 in the present embodiment.
In S131, the management unit 31 determines whether there is virtual server information to be allocated and added, and if it is determined, the process proceeds to S132. On the other hand, if the management unit 31 determines in step S131 that there is no allocation-added target virtual server information, the management unit 31 waits. That is, when the virtual server information of the allocation target virtual server is added to the HD 23 based on the request from the client device 15, the management unit 31 advances the process to S132.

In S132, the dividing unit 32 divides the allocation-added target virtual server information added by the management unit 31 to the HD 23, and advances the processing to S133. The virtual server information dividing process by the dividing unit 32 is the same as the dividing process described in the first and second embodiments, and thus the description thereof is omitted.
In S133, the allocation determining unit 33 determines the virtual server allocation destination information of the virtual server information to be allocated and divided in S132. More specifically, the assignment determination unit 33 determines assignment destination information by a process similar to the process described with reference to FIG. That is, the allocation determining unit 33 determines that there is a virtual server for which the allocation destination physical server device 11 has been determined in S91 illustrated in FIG. The processing from S92 to S95 is as described above with reference to FIG.
In S134, the allocation management unit 34 updates the allocation management information and ends the process. The allocation management unit 34 stores and manages allocation management information in the HD 23 as table data.

  As described above, according to the above-described embodiment, even when the management server device 13 receives an addition request related to virtual server allocation from the client device 15, the management server device 13 can aggregate the virtual servers and execute resource allocation. .

<Embodiment 4>
In the present embodiment, a case where the management server device 13 receives a deletion request for virtual server allocation from the client device 15 after the processing by the management server device 13 as described in the first and second embodiments is completed. explain.
FIG. 14 is a flowchart illustrating an example of information processing of the management server device 13 in the present embodiment.
In S141, the management unit 31 determines whether or not there is virtual server information to be deleted, and if it is determined, the process proceeds to S142. On the other hand, if the management unit 31 determines in S141 that there is no virtual server information to be allocated and deleted, the management unit 31 stands by. That is, when the virtual server information of the allocation target virtual server is deleted from the HD 23 based on the request from the client device 15, the management unit 31 advances the process to S142.

Here, as an example, a case where the management unit 31 deletes the virtual server information of the allocation target virtual server V1 from the HD 23 among the virtual server information shown in FIG. 4 based on a request from the client device 15 will be described. . In this case, it is assumed that the assignment management unit 34 manages the table data of the assignment management information shown in FIG.
In S142, the assignment management unit 34 deletes the assignment management information of the virtual server V1-1 and the assignment management information of the virtual server V1-2 from the table data shown in FIG. 7, and the process proceeds to S143. That is, the allocation management unit 34 deletes the allocation management information corresponding to the virtual server information of the virtual server V1 deleted by the management unit 31 from the table data.

In S143, the allocation determination unit 33 performs the virtual again based on the table data after the allocation management information is deleted in S142 and the resource information shown in FIG. 6A managed by the management server device 13. The server allocation destination information is determined, and the process proceeds to S144.
More specifically, the allocation determination unit 33 re-determines the allocation destination of the virtual server V2-1 shown in FIG. 7 as the physical server device 11a and the allocation destination of the virtual server V2-2 as the physical server device 11a. In other words, the allocation determining unit 33 solves an optimization problem for minimizing the number of physical server apparatuses 11 required for allocation based on the table data after the allocation management information is deleted in S142 and the resource information. . Then, the allocation determining unit 33 determines the allocation destination information of the virtual server based on the solved optimization problem. Note that the optimization problem solving process and the assignment destination determination process based on the solved solution are as described above with reference to FIG.
In S144, the allocation management unit 34 updates the allocation management information and ends the process. The allocation management unit 34 stores and manages allocation management information in the HD 23 as table data.

  As described above, according to the above-described embodiment, even when the management server device 13 receives a deletion request related to virtual server allocation from the client device 15, the management server device 13 can aggregate the virtual servers and execute resource allocation. .

<Other embodiments>
Moreover, this embodiment is implement | achieved also by performing the following processes. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, etc.) of the system or apparatus reads the program. It is a process to be executed.

  As mentioned above, according to each embodiment mentioned above, virtual server information can be divided | segmented in the period of the optimal process unit which can reduce the computational complexity at the time of performing an allocation process. Thereby, the management server device 13 can reduce the calculation amount and complete the resource allocation in a practical time. Further, the management server device 13 can perform resource allocation by aggregating virtual servers. In other words, the management server device 13 can aggregate the virtual servers every period of the optimum processing unit when performing the allocation.

  The preferred embodiment of the present invention has been described in detail above, but the present embodiment is not limited to the specific embodiment, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

10 cloud server, 11a physical server device, 11b physical server device, 11c physical server device, 12 LAN, 13 management server device, 14 network, 15 client device

Claims (11)

Management means for managing a plurality of virtual server information including allocation request period information indicating an allocation request period relating to resource allocation of the virtual server;
When allocation request periods indicated by allocation request period information of a plurality of virtual server information managed by the management unit overlap, the allocation request periods related to the overlapped allocation request periods are determined based on the allocation request period information related to the overlapping allocation request periods. A dividing means for dividing each of the plurality of virtual server information including the allocation request period information;
Allocation determining means for determining allocation destination information of an allocation destination resource for each virtual server information divided by the dividing means;
A management server device. In the case where a part of the allocation request period of one virtual server information and a part of the allocation request period of other virtual server information overlap among the plurality of virtual server information,
When the allocation start date / time based on the allocation request period information of one virtual server information is included in the allocation request period based on the allocation request period information of other virtual server information, the allocation start date / time is set as a new allocation end date / time and a new allocation Divide the other virtual server information as the start date and time,
When the allocation end date / time based on the allocation request period information of the other virtual server information is included in the allocation period based on the allocation request period information of the one virtual server information, the allocation end date / time is changed to a new allocation end date / time and a new allocation end date / time. The management server device according to claim 1, wherein the one virtual server information is divided as an allocation start date and time.   When the allocation request period of one virtual server information is included in the allocation request period of the other virtual server information, the dividing unit sets a new allocation start date and time based on the allocation request period information of the one virtual server information. The other virtual server information is divided using the allocation end date / time and the new allocation start date / time as the allocation end date / time based on the allocation request period information of the one virtual server information as the new allocation end date / time and the new allocation start date / time. Item 3. The management server device according to item 1 or 2. The virtual server information further includes allocation request capacity information indicating a resource capacity necessary for virtual server allocation in the allocation request period,
When the required resource capacity based on the allocation request capacity information of the one virtual server information or the other virtual server information changes in the allocation request period, the dividing unit sets the date and time related to the change to a new allocation end date and time The management server device according to claim 2 or 3, wherein the one virtual server information and the other virtual server information are divided as a proper allocation start date and time.   The allocation determining unit obtains a solution of an optimization problem that minimizes the number of resources required for virtual server allocation as an objective function, and assigns a resource of an allocation destination for each of the divided virtual server information based on the obtained solution. The management server device according to claim 1, wherein the allocation destination information is determined. It holds resource information that associates the capacity information of the managed resource with the allocatable period information,
The allocation determining means allocates a virtual server based on virtual server information including allocation request capacity information indicating a capacity of a resource necessary for allocation of a virtual server associated with allocation request period information, and the resource information. 6. A solution to an optimization problem that minimizes the number of required resources as an objective function is obtained, and assignment destination information of an assignment destination resource is determined for each of the divided virtual server information based on the obtained solution. Management server device.   It further has an allocation management means for managing allocation management information associating allocation period information related to virtual server allocation, allocated capacity information related to the allocation, and allocation destination information determined by the allocation determination means as table data. The management server device according to any one of claims 1 to 6.   When the virtual server information of a virtual server to be newly allocated by the management unit is added to the storage device, the allocation determination unit includes resource information that associates capacity information and allocatable period information of the managed resource, 8. The management server device according to claim 7, wherein allocation information of the virtual server is determined based on server information and table data managed by the allocation management unit.   When the virtual server information related to resource allocation is deleted by the management unit, the allocation determination unit deletes the allocation management information corresponding to the deleted virtual server information from the table data managed by the allocation management unit The allocation destination information of the remaining virtual servers is newly determined based on the table data after the deletion and the resource information in which the capacity information of the managed resource and the allocatable period information are associated. The management server device described. An information processing method executed by a management server device,
A management step for managing a plurality of virtual server information including allocation request period information indicating an allocation request period relating to resource allocation of the virtual server;
When the allocation request periods indicated by the allocation request period information of the plurality of virtual server information managed by the management step overlap, the allocation request periods related to the overlapped allocation request periods are based on the allocation request period information related to the overlapping allocation request periods. A dividing step of dividing each of the plurality of virtual server information including the allocation request period information;
An allocation determination step for determining allocation destination information of an allocation destination resource for each virtual server information divided by the division step;
An information processing method including: On the computer,
A management step for managing a plurality of virtual server information including allocation request period information indicating an allocation request period relating to resource allocation of the virtual server;
When the allocation request periods indicated by the allocation request period information of the plurality of virtual server information managed by the management step overlap, the allocation request periods related to the overlapped allocation request periods are based on the allocation request period information related to the overlapping allocation request periods. A dividing step of dividing each of the plurality of virtual server information including the allocation request period information;
An allocation determination step for determining allocation destination information of an allocation destination resource for each virtual server information divided by the division step;
A program for running

Images