WO2013105186A1

WO2013105186A1 - Service level management device, program and method

Info

Publication number: WO2013105186A1
Application number: PCT/JP2012/008200
Authority: WO
Inventors: 繁細野
Original assignee: 日本電気株式会社
Priority date: 2012-01-10
Filing date: 2012-12-21
Publication date: 2013-07-18
Also published as: JPWO2013105186A1; JP6065843B2

Abstract

[Problem] To appropriately control a resource or other item in response to multiple service level requests. [Solution] A service level management device is provided with a policy extraction unit, a monitoring unit and a control unit. For each of multiple service levels, said policy extraction unit extracts a specified policy associated with a specified service level, said specified policy being extracted by referencing a service level policy relationship storage unit on the basis of the specified service level. In association with each of the service levels, said service level policy relationship storage unit stores a policy in which is written in association therebetween: a threshold value for a load on an execution environment of an application, said threshold value being indicated by a measurement value related to an item to be monitored that exists in the execution environment; and a control rule for the execution environment. Said monitoring unit monitors the measurement value related to the item to be monitored, said measurement value being contained in the extracted specified policy. Said control unit controls the execution environment such that a process corresponding to the control rule is executed if the load indicated by the measurement value is higher than the threshold value contained in the specified policy.

Description

Service level management apparatus, program, and method

The present invention relates to a technical field for managing resources for realizing a cloud computing environment (cloud environment), for example.

Cloud providers provide resources such as CPU (Central Processing Unit) and memory to users who develop applications that run in the cloud environment.

However, it matches the service level (Service Level: hereinafter sometimes abbreviated as “SL”) for the application requested by the user (Application: hereinafter, also abbreviated as “AP” in the present application). It is difficult for cloud service providers to guarantee the service level. This is because it is difficult to consider resources for realizing a cloud environment in which the application is executed at the stage of application design and implementation.

In response to such a problem,

Patent Documents

1, 2, and 3 disclose examples of systems that change resource allocation based on performance information measurement results based on service level targets.

JP 2005-174201 A JP 2007-048315 A JP 2006-252189 A

However, in the technique disclosed in the above-described patent document, performance measurement items and values are fixed in advance in relation to application configuration information. For this reason, there is a problem that resource allocation cannot be appropriately controlled in response to various service level requests from users.

Therefore, in order to solve the above-mentioned problems, the present invention has as its main object to provide a service level management device and the like that can appropriately control resources and the like for a plurality of service level requests.

In order to achieve such an object, one aspect of the present invention provides:
For each of a plurality of service levels, a policy described in association with a threshold for the load of the execution environment represented by a measurement value related to a monitoring target in the execution environment of the application and a control rule of the execution environment, A service level / policy relation storage unit that stores the policies that differ in at least one of the monitoring target, the threshold value, and the control rule according to the service level in association with each service level is set to a specific service level. A policy extractor for extracting a specific policy associated with the specific service level by referring to
A monitoring unit for monitoring a measurement value related to the monitoring target included in the extracted specific policy;
A control unit that controls the execution environment so as to execute a process according to the control rule when the load represented by the measurement value is higher than the threshold included in the specific policy;
A service level management device is provided.

In the present invention, for each of a plurality of service levels, a threshold for the load of the execution environment represented by the measurement value related to the monitoring target in the execution environment of the application and the control rule of the execution environment are described in association with each other. A service level / policy relation storage unit that stores the policies that are different from each other according to the service level in association with each service level, wherein at least one of the monitoring target, the threshold value, and the control rule is a policy A policy extraction process for extracting a specific policy associated with the specific service level by referring to the specific service level;
A monitoring process for monitoring a measurement value related to the monitoring target included in the extracted specific policy;
A control process for controlling the execution environment so as to execute a process according to the control rule when the load represented by the measurement value is higher than the threshold value included in the specific policy;
Provided is a service level management program for causing a computer to execute.

The present invention also provides:
For each of a plurality of service levels, a policy described in association with a threshold for the load of the execution environment represented by a measurement value related to a monitoring target in the execution environment of the application and a control rule of the execution environment, A service level / policy relation storage unit that stores the policies that differ in at least one of the monitoring target, the threshold value, and the control rule according to the service level in association with each service level is set to a specific service level. Extract a specific policy associated with the specific service level by referencing based on
Monitoring the measurement value related to the monitoring target included in the extracted specific policy;
Provided is a service level management method for executing processing according to the control rule when the load represented by the measurement value is higher than the threshold value included in the specific policy.

According to the present invention, it is possible to appropriately control resources and the like for a plurality of service level requests.

It is a block diagram which illustrates the composition of the service level management system concerning a first embodiment. It is a figure which illustrates the table showing the relationship between a service level and a policy in the service level management system which concerns on 1st embodiment. It is a figure holding | maintaining the table showing the relationship different from FIG. 2 of the service level and policy in the service level management system which concerns on 1st embodiment. It is a figure which shows notionally the structure of the virtual machine 21 implement | achieved by the server 2 of the service level management system which concerns on a 1st Example. It is a figure which illustrates the table which the monitoring request | requirement method storage part 17 of the terminal device 1 which concerns on 1st embodiment stores. It is a flowchart which shows the service level management process which the service management apparatus 1 which concerns on 1st embodiment performs. It is a block diagram which illustrates the composition of the service level management system concerning a second embodiment. It is a block diagram which illustrates the hardware constitutions of the computer (information processing apparatus) which can implement | achieve the service level management apparatus (terminal device) in each embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In all the drawings, the same components are denoted by the same reference numerals, and description thereof will be omitted as appropriate.

In addition, each part which comprises the apparatus etc. which concern on each embodiment is comprised by hardware, such as a logic circuit. The apparatus according to each embodiment includes a computer control unit, a memory, a program loaded in the memory, a storage unit such as a hard disk for storing the program, an interface for connection to a communication network, and the like. Such an apparatus may be realized by an arbitrary combination of hardware and software. And as for this invention demonstrated using each embodiment mentioned later as an example, the realization method and the structure of an apparatus are not limited unless there is particular notice.

FIG. 8 is a block diagram illustrating a hardware configuration of a computer (information processing apparatus) capable of realizing the service level management apparatus (terminal apparatus) according to each embodiment of the present invention. As illustrated in FIG. 8, the control unit of the information processing apparatus 1000 includes a CPU (Central Processing Unit) and the like, and controls the entire apparatus by executing an OS (Operating System). For example, the CPU 100 reads programs and data from the recording medium 104 mounted on the drive device 103 and the like to the memory 101, and executes various processes according to the read programs and data. A recording medium 104 mounted on the drive device 103 or the like is, for example, an optical disk, a flexible disk, a magnetic optical disk, an external hard disk, a semiconductor memory, or the like, and records a computer program so that the computer can read it. The computer program may be downloaded from an external computer (not shown) connected to the communication network. The information processing apparatus 1000 also includes an input / output device 106 that forms a user interface such as a keyboard, a mouse, and a display. These components are configured using the bus 105 and can input / output data to / from each other.

<First Embodiment>
Next, a first embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram illustrating the configuration of a service level management system according to the first embodiment of the present invention.

The service level management system shown in FIG. 1 includes a terminal device 1 (hereinafter also referred to as “service level management device”) and a server 2. The terminal device 1 and the server 2 are communicably connected via a communication line or the like.

The terminal device 1 includes an AP deployment unit 11, an AP design unit 12, a policy extraction unit 13, a monitoring unit 14, a control unit 15, an SL / policy relation storage unit 16, a monitoring request method storage unit 17, including.

In the terminal device 1, the AP deployment unit 11 deploys the application designed by the AP design unit 12 on the virtual machine 21 (hereinafter sometimes referred to as “VM”) of the server 2.

The AP design unit 12 includes a function request definition unit 121 and an SL input unit 122.

The AP design unit 12 is, for example, a CASE (Computer Aided Software Engineering) tool. A user or the like designs a desired application by inputting a function request to the terminal device 1 using a function provided by the function request definition unit 121. The AP design unit 12 outputs the designed application to the AP deployment unit 11.

The user or the like inputs the service level using the SL input unit 122. In the service management system, the service level is an index or the like representing the quality of service provided to the user by the system provider or the like. The service level may include so-called non-functional requirements such as performance and reliability. In the present embodiment, as described later, the service level is represented by numerical values such as

service levels

1, 2, and 3.

FIG. 2 is a diagram illustrating a table representing the relationship between the service level and the policy in the service level management system according to the first embodiment. As shown in FIG. 2, the SL / policy relation storage unit 16 stores the service level and the policy in association with each other. The policy is information that associates an SLO (Service Level Objective) with a control rule.

The SLO of the present embodiment is a condition indicating the allowable range of the load that is the monitoring target, and is given by the relationship between the monitoring target and the threshold value. For example, “CPU> 0.8” described in the SLO column indicates that the usage rate of the CPU is higher than 0.8. “Disk IO> 1000” indicates that the number of times of input / output per unit time of the disk is higher than 1000 times.

The monitoring target is a monitoring item specified according to the service level, such as the state of a device such as a CPU or Disk IO (Input / Output) and the number of transactions.

Further, in the table shown in FIG. 2, the control rule is the content of control performed by the control unit 15 when the condition shown in the SLO column is satisfied. For example, the control rule “AddVM: 1” illustrated in FIG. 2 indicates that the server 2 has one virtual machine 21 when the conditions “CPU> 0.8” and “Disk IO> 1000” are satisfied. It shows that the control part 15 transmits a control signal to the server 2 so that it may generate | occur | produce.

Here, in the table shown in FIG. 2, as the service level becomes higher, a value that makes the condition shown in the SLO column included in the policy associated with the service level stricter may be registered.

For example, in the example shown in FIG. 2, the control rule included in the policy associated with service level 1 and the control rule included in the policy associated with service level 2 are both “AddVM: 1”. However, the conditions shown in the SLO column included in the policy related to service level 1 are “CPU> 0.8” and “Disk IO> 1000”. On the other hand, the conditions shown in the SLO column included in the policy related to service level 2 are “CPU> 0.7” and “Disk IO> 900”. When the service level is high, the threshold for the monitoring target is high. Indicates that it is low. This means that if the service level is high, one virtual machine 21 is added to the server 2 when the load on the CPU or disk is low. That is, in the table illustrated in FIG. 2, if the service level is high, the condition indicated by the SLO column is severe, and one virtual machine 21 is added to the server 2 before the load status to be monitored becomes high.

FIG. 3 is a diagram for holding a table representing a relationship between the service level and the policy in the service level management system according to the first embodiment, which is different from FIG. In the example of the SL / policy relation storage unit 16 shown in FIG. 2,

service levels

1, 2, and 3 are described, and one policy is associated with each service level. On the other hand, the SL / policy relation storage unit 16 may store a plurality of policies in association with each service level as shown in FIG. At that time, the number of policies may be different depending on the service level.

For example, in the example of the SL / policy relation storage unit 16 shown in FIG. 3, there are two policies related to the service level 1, but there are three policies related to the service level 2 and related to the service level 3. There are four policies. In this way, the number of policies associated with the service level may be different for each service level. Thereby, according to the service level management apparatus system concerning this embodiment, appropriate control of an application execution environment is attained according to a service level.

Further, as shown in FIG. 3, as the service level becomes higher, the SL / policy relationship storage unit 16 may store a table representing a relationship in which the number of monitoring targets increases. This means that the monitoring items increase when the service level is high. Therefore, according to the service level management apparatus system that refers to such a table, more detailed monitoring and control in the application execution environment is possible as the service level increases.

In the example shown in FIG. 2, the CPU and the Disk IO are included as monitoring targets in all the SLOs in the table. However, as shown in FIG. 3, the type of monitoring target may be different depending on the service level.

For example, in the example illustrated in FIG. 3, the policy associated with service level 1 does not include “Network” as a monitoring target, but one of the policies associated with service level 2 includes “Network” as a monitoring target. Is included. “Network” is a usage rate of the network band, and “Network> 0.5” indicates that the usage rate is higher than 0.5.

As described above, in the table stored in the SL / policy relation storage unit 16, the types of monitoring items may differ depending on the service level. As a result, according to the present embodiment, it is possible to set appropriate monitoring items according to the service level.

Also, the SLO stored in the SL / policy relation storage unit 16 may include a complex condition (composite condition) between a plurality of monitoring targets as shown in service level 3 in FIGS.

For example, the policy associated with service level 1 in FIG. 2 includes SLOs “CPU> 0.8” and “Disk IO> 1000”. The policy described at the bottom relating to service level 3 shown in FIG. 3 includes SLOs with the conditions “CPU> 0.6”, “Disk IO> 700”, and “Network> 0.3”. . As described above, one control rule according to the present embodiment may be designated for a complex condition (complex condition) between a plurality of monitoring targets. Thereby, according to this embodiment, the application execution environment can be monitored and controlled in more detail.

In addition, the control rule for the complex condition may be a control rule indicating that a virtual machine is added. For example, in a complex condition between a plurality of monitoring targets (for example, “CPU> 0.6” and “Disk IO> 700” and “Network> 0.3” at service level 3), the virtual machine 21 (details) Is described later with reference to FIG. 4.) A control rule that increases itself is associated (for example, “AddVM: 1”). On the other hand, when the condition is not a compound condition (for example, “CPU> 0.8” at service level 2 shown in FIG. 3), a control rule instructing to increase the resource indicated by the monitoring target is associated. (For example, “AddCPU: 1”). As described above, the control rule for the complex condition between the plurality of monitoring targets may be a control rule for instructing to increase the virtual machine 21 itself, instead of increasing the resources indicated by the individual monitoring targets.

In the above description, the case where the service level is high when the service level number is large is described (for example, service level 2 is higher than service level 1). However, the present embodiment is not limited to such a case. For example, the size of the service level number is not related to the high service level, and the number can be set as appropriate. That is, for example, the service level 1 may be set higher than the service level 2.

The policy extraction unit 13 acquires the service level input from the SL input unit 122. Then, the policy relating to the service level is extracted from the SL / policy relation storage unit 16. For example, consider a case where the SL / policy relation storage unit 16 stores a service level and a policy as shown in FIG. 3 in association with each other as shown in FIG. In this case, when the service level 2 is input from the SL input unit 122, the policy extraction unit 13 includes three policies (“CPU> 0.8”; “Warn”), (“Disk”) associated with the service level 2. IO> 1000 ”;“ AddDisk: 1 ”), (“ Network> 0.5 ”;“ AddNWsocket: 1 ”). The notation (α; β) is a policy indicating that β of the control rule is executed when α of SLO is satisfied.

Here, (“CPU> 0.8”; “Warn”) is a policy indicating that a warning message is transmitted to the terminal device 1 when the CPU usage rate is higher than 0.8, as described above. . Further, (“Disk IO> 1000”; “AddDisk: 1”) adds only one unit of disk to the virtual machine 21 of this embodiment when the number of input / outputs per unit time of the disk is higher than 1000 times. This is a policy indicating that Also, (“Network> 0.5”; “AddNWsocket: 1”) is a policy indicating that only one unit of communication line is added to the virtual machine 21 when the network bandwidth usage rate is higher than 0.5. is there.

FIG. 4 is a diagram conceptually showing the configuration of the virtual machine 21 realized by the server 2 of the service level management system according to the first embodiment. Here, adding a storage device (Disk) to the virtual machine 21 means that a part of the Disk included in the server 2 which is a real machine is newly added to the Disk of the virtual machine 21 as shown in FIG. Means assigning. Similarly, adding a communication line to the virtual machine 21 means, for example, newly adding and assigning a communication line included in the server 2 to the communication line of the virtual machine 21. The same applies to other resources such as memory and CPU.

FIG. 3 shows a policy in which the above-described compound condition is associated with the control rule (“CPU> 0.6”, “Disk IO> 700”, “Network> 0.3”; “AddVM: 1”). Are listed. As described above, when the CPU usage rate is higher than 0.6, the number of times of input / output per unit time of the disk is higher than 700 times, and the network bandwidth usage rate is higher than 0.3, the policy is virtual. This is a policy indicating that one unit of the machine 21 itself is added.

Here, adding a new virtual machine means, for example, adding a new virtual machine having the specifications of the current virtual machine 21, and resources such as a memory and a disk included in the server 2 are added to the new virtual machine. Means assigned.

In the terminal device 1, the monitoring unit 14 acquires the measurement value of the monitoring target included in the extracted policy. For example, when the extracted policy is (“CPU> 0.6”, “Disk IO> 700”, “Network> 0.3”; “AddVM: 1”), “CPU”, “Disk IO”, Three “Network” are monitoring targets. The monitoring unit 14 acquires the measurement values for these monitoring targets by, for example, a method according to the monitoring request method stored in the monitoring request method storage unit 17 illustrated in FIG. Note that the monitoring targets may include the number of transactions per unit time of the application, SQL (Structured Query Language), and the like.

In the terminal device 1, FIG. 5 is a diagram illustrating a table stored in the monitoring request method storage unit 17 of the terminal device 1 according to the first embodiment. The monitoring request method storage unit 17 stores the monitoring target and the monitoring request method in association with each other as shown in the table of FIG. In the present embodiment, the monitoring request method is a method by which the monitoring unit 14 acquires a measurement value to be monitored. For example, when the monitoring target is “Disk IO”, the monitoring request method is “instruction transmission”. This indicates that the server 2 transmits an instruction to the server 2 to transmit the Disk IO measurement value to the monitoring unit 14.

On the other hand, when the monitoring target is “transaction”, the monitoring request method is “send program A”. This indicates that the monitoring unit 14 transmits to the server 2 a monitoring program (here, program A) for acquiring the number of transactions per unit time.
Note that it is not necessary for the monitoring unit 14 to transmit the monitoring program. For example, when the AP deployment unit 11 deploys the application designed by the AP design unit 12 to the server 2, the AP deployment unit 11 may deploy the monitoring program together with the application to the server 2.

For example, first, the AP deployment unit 11 in the terminal device 1 causes the server 2 to deploy the application. Thereafter, the monitoring unit 14 or the like may transmit a monitoring program to the server 2. According to such a configuration, it is not necessary to prepare a monitoring program in the server 2 on the application execution environment side in advance, so that the degree of freedom of policy setting can be increased.

In the terminal device 1, the control unit 15 refers to the measurement value and policy to be monitored. The control unit 15 executes the control rule when the load indicated by the measurement value to be monitored is higher than the threshold included in the policy (for example, the server 2 is instructed to execute a predetermined process according to the control rule). ). Here, the load indicated by the measurement value of the monitoring target being higher than the threshold value does not mean that the measurement value indicated by the monitoring target is larger than the threshold value. For example, instead of measuring the CPU usage rate, the CPU vacancy rate may be measured. In that case, since the magnitude of the measurement value to be monitored and the magnitude relationship with the threshold value are also switched, there is no relation between an increase in load and a measurement value that is larger than the threshold value.

The server 2 includes a virtual machine 21, and an application is deployed from the AP deployment unit 11 to the virtual machine 21.

When the server 2 receives an instruction to acquire the measurement value of the monitoring target from the monitoring unit 14, the server 2 measures the monitoring target and transmits the measurement value to the monitoring unit 14.

In addition, when the server 2 receives an instruction to execute a predetermined process according to the control rule from the control unit 15, the server 2 executes a specific process.

Next, the operation of the service level management apparatus 1 according to this embodiment will be described in detail.

FIG. 6 is a flowchart showing service level management processing performed by the service management apparatus 1 according to the first embodiment. The AP design unit 12 of the service management apparatus 1 acquires a function request from a user or the like via the function request definition unit 121. Then, the AP design unit 12 designs an application (step S11).

On the other hand, the SL input unit 122 acquires a service level from a user or the like (step S21).

Next, the policy extraction unit 13 acquires a service level from the SL input unit 122. Then, the policy extraction unit 13 refers to the SL / policy relation storage unit 16 to extract a policy associated with a specific service level (step S22). Here, when there are a plurality of policies related to the service level in the SL / policy relation storage unit 16, the policy extraction unit 13 extracts all of these policies.

Next, the monitoring unit 14 extracts a monitoring target included in the policy extracted in step S22. The monitoring unit 14 acquires a monitoring program for monitoring the monitoring target by referring to the monitoring request method storage unit 17 (see FIG. 5) (step S24). For example, when the monitoring target is “transaction”, for example, the monitoring unit 14 acquires “program A” that is a monitoring program for measuring the number of transactions per unit time.

Next, the AP deployment unit 11 deploys the designed application and the monitoring program to the VM 21 executed by the server 2 (step S24).

Next, the monitoring unit 14 instructs the monitoring to the server 2 to monitor the monitoring target by the function of the monitoring program executed by the server 2 (step S25).

Next, the monitoring unit 14 receives the measurement value measured by the function of the monitoring program with respect to the monitoring target from the server 2, and the load as the monitoring target (in this embodiment, the number of transactions represented by the measurement value) is a threshold value. It is judged whether it is higher than (step S26).

When the load as the monitoring target is lower than the threshold value, the process returns to step S25, and the monitoring unit 14 continues monitoring. On the other hand, when the load as the monitoring target is higher than the threshold (when the SLO is satisfied), the control unit 15 executes a control rule related to the SLO (step S27).

In the above description, in steps S23 to 25, the monitoring unit 14 refers to the monitoring request method storage unit 17 to acquire a monitoring program, and the monitoring program is deployed to the server 2 together with the application. However, the present invention described using this embodiment as an example is not limited to such an example. For example, when the monitoring target monitored by the monitoring unit 14 does not depend on the application, the monitoring unit 14 only transmits an instruction to the server 2 to transmit a measurement value related to the monitoring target to the monitoring unit 14. There may be.

A specific example will be described. For example, when the SL / policy relation storage unit 16 stores the SLO and the control rule shown in FIG. 3 in association with each other, the user or the like inputs the service level 3 via the SL input unit 122 (step S21).

Next, the policy extraction unit 13 is a policy related to the service level 3 (“CPU> 0.7”; “AddCPU: 1”), (“Disk IO> 800”; “AddDisk: 1”), ( “Network> 0.5”; “AddNWSSocket: 1”), (“CPU> 0.6”, “Disk IO> 700”, “Network> 0.3”; “AddVM: 1”) 16 is extracted (step S22).

Next, the monitoring unit 14 extracts “CPU”, “Disk IO”, and “Network”, which are monitoring targets, from the extracted policy (step S23).

Then, the monitoring unit 14 refers to the monitoring request method storage unit 17 to perform “instruction transmission” which is a monitoring request method related to each of these monitoring targets. That is, the monitoring unit 14 transmits an instruction to the server 2 to transmit measurement values related to these monitoring targets to the monitoring unit 14.

Next, the server 2 transmits measurement values related to these monitoring targets to the monitoring unit 14. As a result, for example, when the measured values of CPU usage rate = 0.5, Disk IO = 850, and Network bandwidth usage rate = 0.2 of the server 2 are transmitted from the server 2 to the monitoring unit 14 in the terminal device 1. Therefore, in this case, since the SLO described in the policy (“Disk IO> 800”; “AddDisk: 1”) is satisfied in the terminal device 1, the control unit 15 sets the control rule “AddDisk: 1”. Execute (steps S26, 27). That is, the control unit 15 transmits an instruction to the server 2 so as to add one unit of disk to the virtual machine 21.

On the other hand, since the SLO described in another policy is not satisfied, the control unit 15 does not execute another control rule.

According to the present embodiment, the SL / policy relation storage unit 16 stores, for each of a plurality of service levels, a policy described in association with a threshold value and a control rule for a load as a monitoring target in the application execution environment. Store. In the policy, at least one of the monitoring target, the threshold value, and the control rule is different depending on the service level. Since the control unit 15 executes the control rule when the load to be monitored is higher than the threshold value, the service level management device 1 can appropriately control resources and the like for a plurality of service level requests.

<Second Embodiment>
Next, a second embodiment of the present invention will be described in detail with reference to the drawings. FIG. 7 is a block diagram conceptually showing the structure of the service level management apparatus according to the second embodiment of the present invention.

The service level management apparatus 1 of the present embodiment includes a policy extraction unit 13, a monitoring unit 14, a control unit 15, and an SL / policy relation storage unit 16. Note that the SL / policy relation storage unit 16 may be arranged in a database or the like provided outside the service level management apparatus 1 as long as it can be referred (accessed).

The SL / policy relation storage unit 16 stores each of a plurality of service levels in association with a policy described by associating a threshold value with respect to a load indicated by a measurement value related to a monitoring target in an application execution environment and a control rule. Here, in the policy, at least one of a monitoring target, a threshold value, and a control rule differs depending on the service level.

The policy extraction unit 13 acquires a service level input from the outside. Then, the policy extraction unit 13 refers to the SL / policy relation storage unit 16 and extracts a policy related to the acquired service level.

The monitoring unit 14 acquires a measurement value related to the monitoring target included in the extracted policy. Here, the monitoring unit 14 refers to the monitoring request method storage unit 17 (not shown) that stores the monitoring target and the monitoring request method in association with each other, for example, by the monitoring request method corresponding to each of the monitoring targets. Get the measured values for each.

The control unit 15 executes a predetermined process according to the control rule when the load indicated by the measurement value related to the monitoring target is higher than the threshold included in the policy.

According to the present embodiment, the SL / policy relation storage unit 16 associates a policy in which a threshold value and a control rule for a load to be monitored in an application execution environment are associated with each of a plurality of service levels. Store. In the policy, at least one of the monitoring target, the threshold value, and the control rule is different depending on the service level. The control unit 15 executes the control rule when the load to be monitored is higher than the threshold value. Therefore, according to the present embodiment, it is possible to appropriately control resources and the like for a plurality of service level requests.

Although the present invention has been described with reference to the embodiments (and examples), the present invention is not limited to the above embodiments (and examples). Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.
This application claims the priority on the basis of Japanese application Japanese Patent Application No. 2012-002392 for which it applied on January 10, 2012, and takes in those the indications of all here.

DESCRIPTION OF SYMBOLS 1 Terminal device 11 AP deployment part 12 AP design part 13 Policy extraction part 14 Monitoring part 15 Control part 16 SL and policy corresponding | compatible storage part 17 Monitoring request method storage part 100 CPU
101 Memory 102 Hard disk drive (HDD)
103 Drive Device 104 Storage Device 105 Bus 1000 Information Processing Device (Computer)

Claims

For each of a plurality of service levels, a policy described in association with a threshold for the load of the execution environment represented by a measurement value related to a monitoring target in the execution environment of the application and a control rule of the execution environment, A service level / policy relation storage unit that stores the policies that differ in at least one of the monitoring target, the threshold value, and the control rule according to the service level in association with each service level is set to a specific service level. A policy extractor for extracting a specific policy associated with the specific service level by referring to
A monitoring unit for monitoring a measurement value related to the monitoring target included in the extracted specific policy;
A control unit that controls the execution environment so as to execute a process according to the control rule when the load represented by the measurement value is higher than the threshold included in the specific policy;
A service level management device comprising:
The number of monitoring targets stored in the service level / policy relation storage unit increases as the service level increases.
The service level management apparatus according to claim 1.
The threshold stored in the service level / policy relation storage unit is lower as the service level is higher.
The service level management apparatus according to claim 1 or 2.
A function request definition unit capable of inputting a function request used for designing the application;
An application deployment unit that deploys the application designed according to the function request to a virtual machine as a monitoring target of the monitoring unit;
Further comprising
The monitoring unit extracts a monitoring program for measuring the performance of the monitoring target from a storage unit in which information indicating a monitoring request method is stored, and receives a measurement value related to the monitoring target measured by the extracted monitoring program And
The application deployment unit deploys the monitoring program to the virtual machine together with the application.
The service level management apparatus according to any one of claims 1 to 3.
The monitoring unit extracts a monitoring program that measures the performance of the monitoring target from a storage unit that stores information indicating a monitoring request method, transmits the extracted monitoring program to the execution environment of the application, and Receiving a measurement value relating to the monitoring object measured by the monitoring program;
The service level management apparatus according to any one of claims 1 to 3.
The service level management apparatus according to claim 1, wherein the service level / policy relation storage unit is provided in the own apparatus.
For each of a plurality of service levels, a policy described in association with a threshold for the load of the execution environment represented by a measurement value related to a monitoring target in the execution environment of the application and a control rule of the execution environment, A service level / policy relation storage unit that stores the policies that differ in at least one of the monitoring target, the threshold value, and the control rule according to the service level in association with each service level is set to a specific service level. A policy extraction process for extracting a specific policy associated with the specific service level by referring to
A monitoring process for monitoring a measurement value related to the monitoring target included in the extracted specific policy;
A control process for controlling the execution environment so as to execute a process according to the control rule when the load represented by the measurement value is higher than the threshold value included in the specific policy;
Service level management program that causes a computer to execute.
The service level management program according to claim 7, further causing the computer to execute storage processing for storing the number of monitoring targets in the service level / policy relation storage unit as the service level is higher.
The service level management program according to claim 7 or 8, which causes the computer to execute a storage process of storing the threshold value in the service level / policy relation storage unit as the service level increases.
A function request definition process capable of inputting a function request used for designing the application; and
The monitoring process for measuring the performance of the monitoring target is extracted from a storage unit in which information representing a monitoring request method is stored, and the monitoring process for receiving the measurement value related to the monitoring target measured by the monitoring program;
An application deployment process for deploying the application designed according to the function request to a virtual machine as a monitoring target together with the monitoring program;
10. The service level program according to claim 7, wherein the program is executed by the computer.
The monitoring process extracts a monitoring program for measuring the performance of the monitoring target from a storage unit storing information indicating a monitoring request method, and transmits the extracted monitoring program to the execution environment of the application. The service level management program according to any one of claims 7 to 9, which causes the computer to execute a process of receiving a measurement value related to the monitoring target measured by a monitoring program.
For each of a plurality of service levels, a policy described in association with a threshold for the load of the execution environment represented by a measurement value related to a monitoring target in the execution environment of the application and a control rule of the execution environment, A service level / policy relation storage unit that stores the policies that differ in at least one of the monitoring target, the threshold value, and the control rule according to the service level in association with each service level is set to a specific service level. Extract a specific policy associated with the specific service level by referencing based on
Monitoring the measurement value related to the monitoring target included in the extracted specific policy;
A service level management method for executing processing according to the control rule when the load represented by the measurement value is higher than the threshold value included in the specific policy.
13. The service level management method according to claim 12, wherein the number of monitoring targets is stored in the service level / policy relation storage unit as the service level increases.
The service level management method according to any one of claims 11 to 13, wherein the threshold value is stored in the service level / policy relation storage unit as the service level increases.
In response to the input of a function request used for designing the application, a monitoring program for measuring the performance of the monitoring target is extracted from a storage unit storing information representing a monitoring request method,
The application designed according to the function request is deployed in a virtual machine together with the monitoring program as a monitoring target,
The service level management method according to claim 12, wherein a measurement value related to the monitoring target measured by the monitoring program is received.
A monitoring program for measuring the performance of the monitoring target is extracted from a storage unit in which information indicating a monitoring request method is stored, and the extracted monitoring program is transmitted to the execution environment of the application and measured by the monitoring program. 15. The service level management method according to claim 12, wherein a measurement value related to the monitoring target is received.