WO2011138879A1 - Operation management device and operation management method of information processing system - Google Patents
Operation management device and operation management method of information processing system Download PDFInfo
- Publication number
- WO2011138879A1 WO2011138879A1 PCT/JP2011/053044 JP2011053044W WO2011138879A1 WO 2011138879 A1 WO2011138879 A1 WO 2011138879A1 JP 2011053044 W JP2011053044 W JP 2011053044W WO 2011138879 A1 WO2011138879 A1 WO 2011138879A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- configuration
- influence
- processing system
- information processing
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Definitions
- the present invention relates to prevention of failures in an information processing system, and more particularly to a technique for preventing in advance failures that may occur based on configuration information of the information processing system.
- Business operation management for the former executes business programs according to the operation schedule and load so that processing requests and service requests from users of the information processing system can be met with a predetermined performance (for example, response time). It controls the selection of resources such as computers, storage devices, and network interfaces, and start / stop of business programs.
- System operation management for the latter manages the resource configuration of the information processing system, monitors the operating status, monitors the occurrence of failures due to overloads and failures, and determines the extent and extent of the impact when a failure occurs. Control suppression.
- System operation management must be implemented under the constraints on the performance and number of resources associated with the cost performance and operation plan of the information processing system.
- Patent Document 1 discloses a technique related to control when a failure occurs in an information processing system.
- Patent Document 1 shows that the degree of influence of a resource on a service is calculated in consideration of the state of the system, and the priority of the resource is calculated based on the importance of the service and the calculated degree of influence. Yes.
- a failure occurs in a resource used by a service with high importance, it becomes possible to allocate a resource used by a service with low importance to a service with high importance.
- Patent Document 1 discloses a technique for dealing with a case where a failure occurs. However, a system operation management that is unlikely to cause a failure and particularly has a large influence on business operations is desired.
- the disclosed operation management device is connected to an information processing system whose configuration is to be managed. Connect to the management client.
- the operation management device receives a configuration information acquisition unit that acquires configuration information of an information processing system from an operating information processing system, and processes information when a failure occurs in a resource that constitutes the information processing system from the acquired configuration information.
- the impact of a resource when there is an impact calculator that calculates the impact that indicates the impact on the performance of the system for each resource, and when the calculated impact exceeds a predetermined upper limit of impact.
- a configuration generation unit that generates a configuration plan of the information processing system whose degree is lower than the upper limit value;
- Another desirable mode of the disclosed operation management apparatus is a configuration change plan of a distributed configuration and a multiplexed configuration of an information processing system in which the influence degree of resources falls below the upper limit value.
- Still another desirable mode of the disclosed operation management apparatus is that the impact calculation unit, when a failure occurs in a resource constituting the information processing system, affects other resource impacts that the resource affects and the resource The sum of importance is calculated as the influence of the resource.
- Still another desirable mode of the disclosed operation management apparatus is a multiplicity calculation unit that corrects the calculated influence degree with respect to resources that are multiplexed in the resources for which the influence degree calculation unit has calculated the influence degree. It has further.
- Still another desirable mode of the disclosed operation management apparatus includes an alert policy setting unit that sets an upper limit value of a predetermined influence level input from a management client, and an influence level calculated for each resource has a predetermined influence level.
- An alert detection unit that determines whether or not the upper limit value is exceeded, and an alert output unit that outputs an alert to the management client when the calculated influence degree exceeds a predetermined upper limit value of the influence degree.
- the present invention it is possible to perform system operation management in which a failure is unlikely to occur in an information processing system, and particularly a failure that has a large influence on business operations is unlikely to occur.
- FIG. 1 shows a system configuration example of the embodiment.
- the system according to this embodiment includes a management target device 1 including one or more server devices 2 and one or more switches (network switches) 4, a configuration management server 5, and a management client 6 connected via a communication network.
- the configuration management system manages and controls the configuration of the management target device 1 as an information processing system managed by the business manager.
- the configuration management server 5 (operation management device) is connected to the management target device 1 which is a target for managing the configuration.
- the configuration management server 5 acquires the configuration information of the managed device 1 from the managed device 1 that is in operation, and manages the management target when a failure occurs in the resource that configures the managed device 1 from the acquired configuration information.
- the degree of influence indicating the influence on the business execution of the device 1 is calculated for each resource, and when there is a resource whose calculated degree of influence exceeds the upper limit value of the predetermined influence degree, the influence degree of the resource is set to the upper limit value.
- a configuration plan of the management target apparatus 1 below is created.
- the configuration plan of the managed device 1 to be created is a configuration change plan of the distributed configuration and the multiplexed configuration of the managed device 1 whose resource influence level is lower than the upper limit value.
- the configuration management server 5 calculates, as a resource influence degree, the sum of the influence degree of other resources that the resource affects and the importance of the resource when a failure occurs in the resource that constitutes the managed device 1. .
- the configuration management server 5 corrects the calculated influence level with respect to the resource having the multiplexed configuration among the resources for which the influence degree is calculated. Further, the configuration management server 5 sets a predetermined upper limit value of influence input from the management client 6 and determines whether or not the calculated influence degree for each resource exceeds the predetermined upper limit value of the influence degree. When the calculated influence degree exceeds the predetermined upper limit value of the influence degree, an alert is output to the management client.
- FIG. 2 shows each part and each table necessary for the description of the present embodiment of the configuration management system including the management target device 1, the configuration management server 5, and the management client 6.
- the configuration information providing unit 16 stored in the memory of the management target device 1 is executed by the CPU.
- Each unit stored in the memory of the configuration management server 5 is executed by the CPU.
- the configuration information providing unit 16 of the management target device 1 transmits the configuration information of the management target device 1 in response to a request from the configuration management server 5.
- the configuration management server 5 functions by controlling the execution of each unit by the configuration information control unit 35.
- Each information table stored in the auxiliary storage device is used for execution of each unit. A description will be given below of each unit including the configuration information control unit 35 and each information table.
- FIG. 3 shows a processing flow of the configuration control unit 35. An outline of the operation of the configuration management system will be described using this processing flow, and details of the operation of each part will be described later.
- the configuration control unit 35 executes each processing unit, and manages and controls the configuration of the management target device 1.
- the configuration information acquisition unit 17 collects configuration information of the management target device 1 (step 7). Based on the collected configuration information, the importance calculator 18 calculates the importance of the resource (step 8), and the influence calculator 19 calculates the influence of the resource. (Step 9).
- the multiplicity calculation unit 20 calculates the multiplicity of the resource, and corrects the influence based on the calculated multiplicity (step 10).
- the alert policy detection unit 21 determines whether or not the obtained influence degree matches the alert policy (steps 11 and 12). When the alert policy does not match the alert policy, the process ends.
- the alert policy is set in the alert policy table 34 in advance by the input from the system administrator via the management client 6 accompanying the execution of the alert policy setting unit 24.
- Step 13 If it matches the alert policy, the alert output unit 23 issues an alert (step 13).
- step 14 a configuration change plan recommended by the recommended configuration generation unit 22 is created (step 14), and the configuration change plan created by the recommended configuration display unit 25 is displayed on the management client 5 (step 15).
- Step 7 to Step 14 of the configuration control unit 35 each processing of Step 7 to Step 14 of the configuration control unit 35 will be described.
- the configuration information acquisition unit 17 of the configuration management server 5 requests the configuration information providing unit 16 of the management target device 1 to transmit the configuration information, and the configuration information providing unit 16 of the management target device 1 obtains the configuration information of the management target device 1.
- the configuration information of the management target device 1 is associated with the resource name and identifier of the management target device 1 including virtualized ones, and the configuration is based on the system operation management such as the attribute and the relationship with other resources.
- Information and configuration information based on business operation management such as which resources are used by business programs (applications). From the point of view of system operation management, applications and the like can be handled as software resources, so in the following, they are called resources regardless of hardware and software.
- the configuration information of the management target device 1 varies depending on the result of the business operation management of the information processing system (the management target device 1) in operation by the business manager.
- the configuration information collection unit 17 stores the received configuration information in the configuration information table 26.
- the configuration information collection unit 17 stores related information between resources included in the configuration information in the resource related information table 27, and displays a resource list (resource identifier and resource type for each resource) of the management target device 1 as impact information.
- a resource list resource identifier and resource type for each resource
- the influence information table 28 will be described later.
- the configuration information table 26 is composed of tables for each resource type as shown in FIGS.
- FIG. 4 shows an application configuration information table 100 as an example of the configuration information table 26 in which the resource type 101 is “application”, such as an identifier 102 for identifying a resource included in the collected configuration information, an application name 103, an installation path 104, and the like. Stores attribute values.
- FIG. 5 shows an example of the host configuration information table 105, which stores a host name, an IP address, and the like as attribute values.
- FIG. 6 shows an example of the processor configuration information table 106, which stores the operating frequency of the processor, the number of cores, and the like as attribute values.
- the resource type further includes resources, switches, and the like that constitute a host such as a processor and a memory.
- FIG. 7 shows an example of the resource related information table 27, which stores related information between resources and the type of relationship.
- Associations between resources include an association source (resource identifier and resource type) 108 and an association destination (resource identifier and resource type) 109.
- the relationship between “host-A” and “application-A” in which the association type 110 is “owned” indicates that “host-A” as the association source owns “application-A”.
- the relation type 110 “used” indicates that the relation source 108 uses the relation destination 109. In other words, “own” represents an inclusion relationship, and “use” represents a connection relationship.
- the configuration information collection unit 17 displays the configuration confirmation screen 111 shown in FIG. 8 on the display of the management client 6 based on the related information stored in the resource related information table 27.
- the example of the configuration confirmation screen 111 shown in FIG. 8 indicates that, for example, “Host-A” owns “Application-A” corresponding to the resource related information table 27 shown in FIG.
- the resources included in the collected configuration information have attributes for each resource type.
- the application name 103, the installation path 104, and the like are attributes.
- the importance level calculation unit 18 refers to the importance level 203 that matches the condition 202 regarding the resource type 201 and its attributes defined in the importance level definition table 31 shown in FIG. 9, and calculates the importance level for each resource.
- the importance of a resource that does not match the condition of the resource type 201 is set to 1, which is the minimum value.
- the obtained importance is stored in the importance column of the influence information table 28.
- the definition contents of the resource type 201, the condition 202, and the importance 203 in the importance definition table 31 are input and updated by the system administrator through the management client 6 according to the configuration change of the management target device 1.
- the value of the importance 203 that matches the condition 202 regarding the resource type 201 and its attributes is defined according to the importance of the resource from the viewpoint of business operation management, and the importance of the resource related to business operation management such as an application. The degree is obtained from the business manager in advance.
- FIG. 10 is an example of the impact information table 28.
- the resource identifier 301 and the resource type 302 are already stored by the configuration information collection unit 17. Since the resource identifier “application-A” hits the importance level definition table 31 and the importance level 203 is 5, 5 is stored in the importance level 303 of the resource identifier 301 “application-A” in the influence level information table 28. . Similarly, importance is obtained and stored for all records (all resources of the management target device 1) in the influence information table 28.
- ⁇ Calculation of resource influence (step 9)> The degree of influence for each resource is obtained by the following formula.
- Resource impact (sum of impacts of all affected resources) + (resource importance)
- the degree of influence indicates the degree of influence on the business execution of the managed device 1 (information processing system) when a failure occurs in a certain resource.
- the degree of influence indicates the degree of influence on the business execution of the managed device 1 (information processing system) when a failure occurs in a certain resource.
- the above equation when a failure occurs in a certain resource, Define the sum of the impact level of the resource affected by the resource failure and the importance level of the resource.
- the influence degree calculation unit 19 uses the dependency definition table 30 shown in FIG. 11 in order to obtain the target resource for which the influence degree of the above equation is obtained (the sum of the influence degrees of all the affecting resources).
- the dependency relationship definition table 30 stores an influence source resource type 401 that is an influence source, an influence destination resource type 402 that is affected, and an influence source relation type 403.
- the influence source relation type 403 indicates which of the relation source resource and the relation destination resource is stored in the resource relation information table 27.
- the influence degree calculation unit 19 obtains the influence degree of each resource by the above formula and stores it in the influence degree 304 of the influence degree information table 28.
- the processing flow of the influence calculation unit 19 is shown in FIGS.
- the processing flow shows processing related to one of the resource identifiers 301 of the influence degree information table 28, but is repeated until the influence degree 304 is stored for all of the resource identifiers 301 of the influence degree information table 28.
- step 503 is repeated for each dependency, and if not, the process branches to step 505 (step 502).
- the importance degree 303 of the resource in the influence degree information table 28 is set as the influence degree 304 (step 505).
- step 503 is executed to calculate the degree of influence for each dependency relationship.
- the influence degree calculation process for each dependency will be described with reference to FIG. It is determined whether or not the relation type 403 of the influence source resource type 401 in the dependency relation definition table 30 is the relation source (step 601). If the relation type is the relation source, the corresponding resource is the relation source, and the dependency relation definition table 30 The resource relation information table 27 is searched for the relation of the relation destination resource type equal to the influence destination resource type 402 (step 602). If it is not the association source, the relevant resource is the association destination, and the association source resource type equal to the influence source resource type 401 of the dependency relationship definition table 30 is searched from the resource association information table 27 (step 605).
- the influence source resource type 401 is “host”, since “related source” is defined as the related type in the dependency definition table 30, “host-A” is the related source, and the related destination is
- “application-A”, “application-B”, and “application-C” are found as related resources. .
- the degree of influence is obtained (step 603).
- “application”, which is the resource type of “application-A” is not included in the influence source resource type 401 of the dependency definition table 30, there is no resource that is affected by “application-A”.
- the “application-A” (the sum of the influence levels of all the affected resources) is 0.
- the importance level of “application-A” is obtained as 5 from the influence degree table 28.
- the degree of influence of “application-B” and “application-C” is both 1.
- the sum of the influence level of all the dependencies of the corresponding resource and the importance level of the corresponding resource is set as the influence level of the corresponding resource (step 504).
- the influence degree calculation unit 19 displays an influence degree confirmation screen 112 shown in FIG. 14 representing the calculated influence degree on the display of the management client 6.
- the influence degree confirmation screen 112 is a screen in which the influence degree of each resource is superimposed on the configuration information confirmation screen 111 shown in FIG.
- ⁇ Calculation of resource multiplicity (step 10)>
- the resource multiplicity calculation unit 20 searches for multiplexed resources and corrects the influence.
- FIG. 15 is an example of the multiplicity definition table 29 in which a resource type 701 to be multiplexed and a condition 702 for multiplexing are defined.
- the resource multiplicity calculation unit 20 searches the multiplicity definition table 29 for each collected resource to find a set of multiplexed resources.
- the discovered resource set is handled as one resource in the impact information table 28, and the impact is corrected according to the multiplicity.
- the influence degree of the duplicated resource is corrected to 1 / (multiplicity) so that the influence degree of the resource is 1/2, and the influence degree 304 of the influence degree information table 28 is updated.
- the alert detection unit 21 refers to the alert policy 34 to determine whether to issue an alert.
- the alert output unit 23 issues an alert.
- the alert output unit 23 notifies the user of an alert by at least one of GUI display, mail transmission, SNMP (Simple Network Management Protocol), etc. on the display of the management client 6.
- FIG. 16 is an example of the alert policy table 34, in which an excluded resource type is defined as an upper limit value (threshold value) 801 of the degree of influence, a threshold value 802 of the number of resources exceeding the upper limit value, and an exclusion condition 803.
- an excluded resource type is defined as an upper limit value (threshold value) 801 of the degree of influence, a threshold value 802 of the number of resources exceeding the upper limit value, and an exclusion condition 803.
- a resource whose impact level exceeds the upper limit value 801 and whose number (the number of resources) is not less than the threshold value 802 for the number of resources is not subject to the exclusion condition 803.
- Fig. 17 shows the processing flow for alert determination and issue.
- the degree of influence exceeds a threshold specified by the user, an alert is issued regarding the resource and notified to the system administrator.
- the upper limit value of the influence degree of the alert policy table 34 is obtained from the influence degree information table 28 in which the influence degree 304 is obtained by the influence degree calculation part 19 (including correction by the multiplicity calculation part 20) for each resource.
- the alert is sent to the user through the alert output unit 23. Notification is made (step 901).
- a simple determination may be made such that a resource exceeding the upper limit 801 of the influence degree is set as a resource to be alerted.
- the threshold value 802 for the number of resources is 1, this is substantially the same as the simple determination.
- ⁇ Recommended configuration change proposal creation (step 14)>
- an alert is issued and a recommended configuration change proposal is provided to the user.
- the recommended configuration generation unit 22 creates a recommended configuration change plan, and the recommended configuration display unit 25 displays the created configuration change plan.
- FIG. 18 shows a processing flow of the recommended configuration generation unit 22.
- the recommended configuration generation unit 22 executes the distributed configuration creation processing (step 1002) and the multiplexed configuration creation processing (step 1004), and changes the configuration of the distributed configuration and the multiplexed configuration as a new configuration plan of the management target device 1. Create a draft.
- step 1002 the distributed configuration creation processing (step 1002) and the multiplexed configuration creation processing (step 1004) will be described.
- FIG. 19 shows a processing flow for creating a distributed configuration.
- the distributed recommended configuration is stored in the distributed configuration information table 32.
- a list of affected resources 305 of the corresponding resource is acquired from the impact information table 28 (step 1105).
- the corresponding resource is a resource whose influence level exceeds a prescribed threshold value.
- the resources that can be allocated are searched in the order of the resources having the greatest influence on the resource (step 1106).
- the resources that affect “Host A” are arranged in order of impact, they are in the order of “Application-A”, “Application-B”, and “Application-C” (in the case of the same impact, they are in no particular order).
- a resource to which “application A” is allocated is searched.
- FIG. 20 shows a process flow for searching for resources that can be allocated in step 1106.
- a list of resources is acquired (step 1109).
- the resource list is a list of resources of the management target device 1 and is stored and managed in the configuration management server 5. Note that the resource list includes resources that constitute the management target device 1 but are not used.
- the only resource that can be allocated is “Host-A”, and no association is assigned to “Host-A” (for reassignment, (Assuming an initial state in which no association is assigned to “Host-A” without considering the association collected by the configuration change collection unit), “Application-A” is assigned to “Host-A”.
- FIG. 22 is an example of the distributed configuration information table 32, and shows that the resource identifier 1103 assigns “application-A” to the resource with the resource identifier 1101 “host A” (step 1108).
- FIG. 22 shows a decentralized table (one of the forms for realizing decentralized change plan information) created for “Host-A” as described above. Also, the degree of influence 1104 of the created recommended configuration is stored in the distributed table 1100.
- additional host is in the resource list as a new resource, that is, there is a resource (host) that is a resource (host) that constitutes the managed device 1 but is not used. There may be no new resources. In this case, it is necessary to adopt a decentralized configuration, but there is no additional resource, and the system administrator is notified via the management client 6 that the decentralized configuration cannot be taken. Create a configuration proposal and notify the system administrator of a message prompting you to add resources.
- FIG. 21 shows a processing flow for creating a multiplexed configuration.
- the recommended multiplexing configuration is stored in the multiplexing configuration information table 33.
- the multiplicity is calculated from the current influence level and threshold value by the following formula (step 1204).
- Multiplicity Resource impact / Resource threshold ⁇ (however, rounded up after the decimal point)
- “Host-A” will be taken up as a resource, but if there are multiple resources whose impact exceeds the specified threshold , The processing described below is repeated for the plurality of resources.
- the created multiplexing configuration resource identifier 1201 and resource type 1202 and the calculated recommended configuration impact 1203 are stored in the multiplexing table 1200 (one of the implementation forms of multiplexing change plan information).
- FIG. 23 shows an example of a multiplexing configuration table.
- additional host as in the case of creating a distributed configuration change proposal, if there is no resource as an additional host, it is necessary to adopt a multiplexing configuration, but there is no additional resource and a multiplexing configuration is adopted.
- the system administrator is notified via the management client 6 that the system cannot perform the operation, or a multiplexing configuration plan is created on the assumption that there are additional resources, and a message prompting the addition of resources is notified to the system administrator.
- the recommended configuration display unit 25 displays a recommended configuration change plan on the management client 6.
- FIG. 24 shows an example of a recommended configuration display screen 1300. Further, since the information necessary for the recommended configuration display screen is stored in the distributed configuration information table 32 and the multiplexed configuration information table 33, the recommended configuration display screen 1300 can be displayed even after the configuration is changed.
- the system administrator can change the configuration to the same by displaying the impact after the configuration change on the impact confirmation screen after making the configuration change according to the recommended configuration and comparing it with the recommended configuration screen 1300. Can be confirmed.
- the present embodiment it is possible to perform system operation management in which a failure is unlikely to occur in the information processing system, and particularly, a failure that has a large influence on business operations is unlikely to occur. Specifically, it is possible to detect in advance resources that may have a serious impact on the information system in the event of a failure, and propose a configuration change proposal corresponding to the detected content to the system administrator. Become. In addition, it is possible to verify whether the configuration can be changed according to the configuration change plan after the actual configuration change.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
- Hardware Redundancy (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
System operation management is needed such that, for an information processing system, failure is unlikely to occur, and in particular, failure imparting a large effect on business operation is unlikely to occur. An operation management device connects to an information processing system for which the configuration is to be managed. The operation management device acquires, from an information processing system in operation, configuration information of the information processing system. From the acquired configuration information, if failure has occurred in a resource constituting the information processing system, the operation management device calculates a degree of effect indicating an effect imparted to business operations of the information processing system for each resource. If there is a resource such that the calculated degree of effect exceeds a predefined upper bound of degree of effect, the operation management device creates configuration plans of the information processing system such that the degree of effect for the resource falls under the upper bound. The configuration plans of the information processing system which are to be created are configuration modification plans of a decentralized configuration and a redundancy configuration of the information processing system such that the degree of effect for the resource falls under the upper bound.
Description
本発明は,情報処理システムの障害予防に関し,とくに情報処理システムの構成情報を基に,発生する可能性のある障害を事前に予防するための技術に関する。
The present invention relates to prevention of failures in an information processing system, and more particularly to a technique for preventing in advance failures that may occur based on configuration information of the information processing system.
情報処理システムの大規模化に伴って,情報処理システムにおける業務プログラム(アプリケーションプログラム)の実行による業務やサービスの運用と,情報処理システムのリソースの効率的な運用とが分けられている。前者のための業務運用管理は,情報処理システムのユーザからの処理要求やサービス要求に,所定のパフォーマンス(たとえば,応答時間)をもって応えられるように,運用スケジュールや負荷に応じて,業務プログラムを実行するための計算機,ストレージ装置,ネットワークインタフェイスなどのリソースの選択,業務プログラムの起動・停止などを制御する。後者のためのシステム運用管理は,情報処理システムのリソースの構成を管理し,稼動状況の監視,過負荷や故障などに伴う障害発生の監視,障害が発生した場合にその影響の範囲や度合いの抑制などを制御する。システム運用管理は,情報処理システムのコストパフォーマンスや運用計画などに伴うリソースの性能や数の制約の下に実現されなければならない。
With the increase in the size of information processing systems, operations of services and services by execution of business programs (application programs) in information processing systems and efficient operations of information processing system resources are separated. Business operation management for the former executes business programs according to the operation schedule and load so that processing requests and service requests from users of the information processing system can be met with a predetermined performance (for example, response time). It controls the selection of resources such as computers, storage devices, and network interfaces, and start / stop of business programs. System operation management for the latter manages the resource configuration of the information processing system, monitors the operating status, monitors the occurrence of failures due to overloads and failures, and determines the extent and extent of the impact when a failure occurs. Control suppression. System operation management must be implemented under the constraints on the performance and number of resources associated with the cost performance and operation plan of the information processing system.
情報処理システムに障害が発生した場合の制御に関連する技術が特許文献1に記載されている。特許文献1には,システムの状態を考慮して,リソースがサービスに及ぼす影響度を算出し,サービスの重要度および算出した影響度に基づいて,リソースの優先度を算出することが示されている。これにより,重要度の高いサービスが利用しているリソースに障害が発生した場合,重要度の低いサービスが利用しているリソースを重要度の高いサービスに割り当てることが可能になる。
Patent Document 1 discloses a technique related to control when a failure occurs in an information processing system. Patent Document 1 shows that the degree of influence of a resource on a service is calculated in consideration of the state of the system, and the priority of the resource is calculated based on the importance of the service and the calculated degree of influence. Yes. As a result, when a failure occurs in a resource used by a service with high importance, it becomes possible to allocate a resource used by a service with low importance to a service with high importance.
昨今では計算機やストレージ装置などの仮想化技術の進展に伴い,業務運用管理もシステム運用管理も,制御の幅(管理の対象,対象を制御するための構成や手順の選択肢,など)が拡大している。また,業務運用管理とシステム運用管理とが分けられて運用される情報処理システムにおいては,そのための管理者も分けられる。ここでは,業務運用管理の管理者を業務管理者,システム運用管理の管理者をシステム管理者と呼ぶ。
In recent years, with the advancement of virtualization technologies such as computers and storage devices, the scope of control for both business operation management and system operation management (targets of management, configuration and procedure options for controlling targets, etc.) has expanded. ing. In an information processing system in which business operation management and system operation management are separately operated, managers for the information processing system are also divided. Here, a business operation management administrator is referred to as a business administrator, and a system operation management administrator is referred to as a system administrator.
このような状況の下では,業務管理者による情報処理システムの業務運用管理の結果が,情報処理システムに障害を発生させ易い,障害が発生した場合にその影響が大きいシステム状態を招く場合が生じる。特許文献1は,障害が発生した場合に対処する技術を開示しているが,障害が発生しにくい,特に業務運用に与える影響が大きい障害が発生しにくいシステム運用管理が望まれる。
Under such circumstances, the result of the business operation management of the information processing system by the business administrator may easily cause a failure in the information processing system, or may cause a system state that has a large effect when a failure occurs. . Patent Document 1 discloses a technique for dealing with a case where a failure occurs. However, a system operation management that is unlikely to cause a failure and particularly has a large influence on business operations is desired.
開示される運用管理装置は,構成を管理する対象である情報処理システムと接続する。また,管理クライアントと接続する。運用管理装置は,稼動中の情報処理システムから,情報処理システムの構成情報を取得する構成情報取得部,取得した構成情報から,情報処理システムを構成するリソースに障害が発生した場合に,情報処理システムの業務遂行に与える影響を示す影響度を各リソースについて算出する影響度計算部,及び,算出した影響度が予め定めた影響度の上限値を超えているリソースがある場合に,リソースの影響度が上限値を下回る情報処理システムの構成案を作成する構成生成部を有する。
The disclosed operation management device is connected to an information processing system whose configuration is to be managed. Connect to the management client. The operation management device receives a configuration information acquisition unit that acquires configuration information of an information processing system from an operating information processing system, and processes information when a failure occurs in a resource that constitutes the information processing system from the acquired configuration information. The impact of a resource when there is an impact calculator that calculates the impact that indicates the impact on the performance of the system for each resource, and when the calculated impact exceeds a predetermined upper limit of impact. A configuration generation unit that generates a configuration plan of the information processing system whose degree is lower than the upper limit value;
開示される運用管理装置の望ましい他の態様は,情報処理システムの構成案は,リソースの影響度が上限値を下回る情報処理システムの分散化構成と多重化構成の構成変更案である。
Another desirable mode of the disclosed operation management apparatus is a configuration change plan of a distributed configuration and a multiplexed configuration of an information processing system in which the influence degree of resources falls below the upper limit value.
開示される運用管理装置の望ましいさらに他の態様は,影響度計算部は,情報処理システムを構成するリソースに障害が発生した場合に,そのリソースが影響を与える他のリソース影響度とそのリソースの重要度の和をそのリソースの影響度として算出する。
Still another desirable mode of the disclosed operation management apparatus is that the impact calculation unit, when a failure occurs in a resource constituting the information processing system, affects other resource impacts that the resource affects and the resource The sum of importance is calculated as the influence of the resource.
開示される運用管理装置の望ましいさらに他の態様は,影響度計算部が影響度を算出した各リソースの中で,多重化構成されているリソースに関して,算出した影響度を修正する多重度計算部をさらに有する。
Still another desirable mode of the disclosed operation management apparatus is a multiplicity calculation unit that corrects the calculated influence degree with respect to resources that are multiplexed in the resources for which the influence degree calculation unit has calculated the influence degree. It has further.
開示される運用管理装置の望ましいさらに他の態様は,管理クライアントから入力される予め定めた影響度の上限値を設定するアラートポリシー設定部,各リソースについて算出した影響度が予め定めた影響度の上限値を超えているか否かを判定するアラート検出部,および,算出した影響度が予め定めた影響度の上限値を超えている場合にアラートを管理クライアントに出力するアラート出力部をさらに有する。
その他本願が開示する課題やその解決方法については,発明の実施形態の欄及び図面により明らかにされる。 Still another desirable mode of the disclosed operation management apparatus includes an alert policy setting unit that sets an upper limit value of a predetermined influence level input from a management client, and an influence level calculated for each resource has a predetermined influence level. An alert detection unit that determines whether or not the upper limit value is exceeded, and an alert output unit that outputs an alert to the management client when the calculated influence degree exceeds a predetermined upper limit value of the influence degree.
Other problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.
その他本願が開示する課題やその解決方法については,発明の実施形態の欄及び図面により明らかにされる。 Still another desirable mode of the disclosed operation management apparatus includes an alert policy setting unit that sets an upper limit value of a predetermined influence level input from a management client, and an influence level calculated for each resource has a predetermined influence level. An alert detection unit that determines whether or not the upper limit value is exceeded, and an alert output unit that outputs an alert to the management client when the calculated influence degree exceeds a predetermined upper limit value of the influence degree.
Other problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.
本発明によれば,情報処理システムに障害が発生しにくい,特に業務運用に与える影響が大きい障害が発生しにくいシステム運用管理が可能になる。
According to the present invention, it is possible to perform system operation management in which a failure is unlikely to occur in an information processing system, and particularly a failure that has a large influence on business operations is unlikely to occur.
図1に,実施形態のシステム構成例を示す。本実施形態のシステムは,通信ネットワークを介して接続する,一つ以上のサーバ装置2及び一つ以上のスイッチ(ネットワークスイッチ)4を含む管理対象装置1と,構成管理サーバ5及び管理クライアント6を含む構成管理システムを備え,構成管理システムが,業務管理者により業務運用管理されている情報処理システムとしての管理対象装置1の構成を管理・制御する。
FIG. 1 shows a system configuration example of the embodiment. The system according to this embodiment includes a management target device 1 including one or more server devices 2 and one or more switches (network switches) 4, a configuration management server 5, and a management client 6 connected via a communication network. The configuration management system manages and controls the configuration of the management target device 1 as an information processing system managed by the business manager.
構成管理サーバ5(運用管理装置)は,構成を管理する対象である管理対象装置1と接続する。構成管理サーバ5は,稼動中の管理対象装置1から,管理対象装置1の構成情報を取得し,取得した構成情報から,管理対象装置1を構成するリソースに障害が発生した場合に,管理対象装置1の業務遂行に与える影響を示す影響度を各リソースについて算出し,算出した影響度が予め定めた影響度の上限値を超えているリソースがある場合に,リソースの影響度が上限値を下回る管理対象装置1の構成案を作成する。
The configuration management server 5 (operation management device) is connected to the management target device 1 which is a target for managing the configuration. The configuration management server 5 acquires the configuration information of the managed device 1 from the managed device 1 that is in operation, and manages the management target when a failure occurs in the resource that configures the managed device 1 from the acquired configuration information. The degree of influence indicating the influence on the business execution of the device 1 is calculated for each resource, and when there is a resource whose calculated degree of influence exceeds the upper limit value of the predetermined influence degree, the influence degree of the resource is set to the upper limit value. A configuration plan of the management target apparatus 1 below is created.
作成する管理対象装置1の構成案は,リソースの影響度が上限値を下回る管理対象装置1の分散化構成と多重化構成の構成変更案である。構成管理サーバ5は,管理対象装置1を構成するリソースに障害が発生した場合に,そのリソースが影響を与える他のリソース影響度とそのリソースの重要度の和をそのリソースの影響度として算出する。構成管理サーバ5は,影響度を算出した各リソースの中で,多重化構成されているリソースに関して,算出した影響度を修正する。また構成管理サーバ5は,管理クライアント6から入力される予め定めた影響度の上限値を設定し,各リソースについて算出した影響度が予め定めた影響度の上限値を超えているか否かを判定し,算出した影響度が予め定めた影響度の上限値を超えている場合にアラートを管理クライアントに出力する。
The configuration plan of the managed device 1 to be created is a configuration change plan of the distributed configuration and the multiplexed configuration of the managed device 1 whose resource influence level is lower than the upper limit value. The configuration management server 5 calculates, as a resource influence degree, the sum of the influence degree of other resources that the resource affects and the importance of the resource when a failure occurs in the resource that constitutes the managed device 1. . The configuration management server 5 corrects the calculated influence level with respect to the resource having the multiplexed configuration among the resources for which the influence degree is calculated. Further, the configuration management server 5 sets a predetermined upper limit value of influence input from the management client 6 and determines whether or not the calculated influence degree for each resource exceeds the predetermined upper limit value of the influence degree. When the calculated influence degree exceeds the predetermined upper limit value of the influence degree, an alert is output to the management client.
図2に,管理対象装置1と,構成管理サーバ5及び管理クライアント6を含む構成管理システムの,本実施形態の説明に必要な各部及び各テーブルを示す。管理対象装置1のメモリに格納される構成情報提供部16は,そのCPUによって実行される。また,構成管理サーバ5のメモリに格納される各部は,そのCPUによって実行される。
FIG. 2 shows each part and each table necessary for the description of the present embodiment of the configuration management system including the management target device 1, the configuration management server 5, and the management client 6. The configuration information providing unit 16 stored in the memory of the management target device 1 is executed by the CPU. Each unit stored in the memory of the configuration management server 5 is executed by the CPU.
管理対象装置1の構成情報提供部16は,構成管理サーバ5からの要求に応じて,管理対象装置1の構成情報を送信する。構成管理サーバ5は,構成情報制御部35によって各部の実行を制御することによって機能する。補助記憶装置に格納される各情報テーブルは,各部の実行に用いられる。構成情報制御部35を初めとする各部および各情報テーブルに関して,以下に説明する。
The configuration information providing unit 16 of the management target device 1 transmits the configuration information of the management target device 1 in response to a request from the configuration management server 5. The configuration management server 5 functions by controlling the execution of each unit by the configuration information control unit 35. Each information table stored in the auxiliary storage device is used for execution of each unit. A description will be given below of each unit including the configuration information control unit 35 and each information table.
図3に,構成制御部35の処理フローを示す。この処理フローを用いて,構成管理システムの動作概要を説明し,各部の動作の詳細は後述する。構成制御部35が各処理部を実行させ,管理対象装置1の構成を管理・制御する。構成情報取得部17が管理対象装置1の構成情報を収集する(ステップ7)。収集した構成情報を基に,重要度計算部18がリソースの重要度を算出し(ステップ8),影響度計算部19がリソースの影響度を算出する。(ステップ9)。次に多重度計算部20がリソースの多重度を算出して,算出した多重度に基づいて影響度を修正する(ステップ10)。その後,アラートポリシー検出部21が,求めた影響度がアラートポリシーに合致するか判定し(ステップ11,ステップ12),アラートポリシーに合致しない場合は,処理を終了する。なお,アラートポリシーは,予めアラートポリシー設定部24の実行に伴う,管理クライアント6を介したシステム管理者からの入力により,アラートポリシーテーブル34に設定されている。
FIG. 3 shows a processing flow of the configuration control unit 35. An outline of the operation of the configuration management system will be described using this processing flow, and details of the operation of each part will be described later. The configuration control unit 35 executes each processing unit, and manages and controls the configuration of the management target device 1. The configuration information acquisition unit 17 collects configuration information of the management target device 1 (step 7). Based on the collected configuration information, the importance calculator 18 calculates the importance of the resource (step 8), and the influence calculator 19 calculates the influence of the resource. (Step 9). Next, the multiplicity calculation unit 20 calculates the multiplicity of the resource, and corrects the influence based on the calculated multiplicity (step 10). Thereafter, the alert policy detection unit 21 determines whether or not the obtained influence degree matches the alert policy (steps 11 and 12). When the alert policy does not match the alert policy, the process ends. The alert policy is set in the alert policy table 34 in advance by the input from the system administrator via the management client 6 accompanying the execution of the alert policy setting unit 24.
アラートポリシーと合致している場合,アラート出力部23がアラートを発行する(ステップ13)。次に,推奨構成生成部22が推奨する構成変更案を作成し(ステップ14),推奨構成表示部25が管理クライアント5に作成した構成変更案を表示する(ステップ15)。以下,構成制御部35のステップ7~ステップ14の各処理について説明する。
If it matches the alert policy, the alert output unit 23 issues an alert (step 13). Next, a configuration change plan recommended by the recommended configuration generation unit 22 is created (step 14), and the configuration change plan created by the recommended configuration display unit 25 is displayed on the management client 5 (step 15). Hereinafter, each processing of Step 7 to Step 14 of the configuration control unit 35 will be described.
<管理対象装置1の構成情報収集(ステップ7)>
構成管理サーバ5の構成情報取得部17が,管理対象装置1の構成情報提供部16に構成情報の送信を要求し,管理対象装置1の構成情報提供部16が管理対象装置1の構成情報を返信する。管理対象装置1の構成情報は,仮想化されたものも含めて管理対象装置1のリソースの名称や識別子に対応付けられて,その属性や他のリソースとの関係などのシステム運用管理に基づく構成情報と,業務プログラム(アプリケーション)がどのリソースを使用しているかなどの業務運用管理に基づく構成情報とを含む。システム運用管理の観点からは,アプリケーションなどもソフトウエアリソースとして扱えるので,以下では,ハードウェア,ソフトウェアにとらわれずにリソースと呼ぶ。 <Collecting configuration information of managed device 1 (step 7)>
The configurationinformation acquisition unit 17 of the configuration management server 5 requests the configuration information providing unit 16 of the management target device 1 to transmit the configuration information, and the configuration information providing unit 16 of the management target device 1 obtains the configuration information of the management target device 1. Send back. The configuration information of the management target device 1 is associated with the resource name and identifier of the management target device 1 including virtualized ones, and the configuration is based on the system operation management such as the attribute and the relationship with other resources. Information and configuration information based on business operation management such as which resources are used by business programs (applications). From the point of view of system operation management, applications and the like can be handled as software resources, so in the following, they are called resources regardless of hardware and software.
構成管理サーバ5の構成情報取得部17が,管理対象装置1の構成情報提供部16に構成情報の送信を要求し,管理対象装置1の構成情報提供部16が管理対象装置1の構成情報を返信する。管理対象装置1の構成情報は,仮想化されたものも含めて管理対象装置1のリソースの名称や識別子に対応付けられて,その属性や他のリソースとの関係などのシステム運用管理に基づく構成情報と,業務プログラム(アプリケーション)がどのリソースを使用しているかなどの業務運用管理に基づく構成情報とを含む。システム運用管理の観点からは,アプリケーションなどもソフトウエアリソースとして扱えるので,以下では,ハードウェア,ソフトウェアにとらわれずにリソースと呼ぶ。 <Collecting configuration information of managed device 1 (step 7)>
The configuration
管理対象装置1の構成情報は,業務管理者による稼動中の情報処理システム(管理対象装置1)の業務運用管理の結果によって変化する。
The configuration information of the management target device 1 varies depending on the result of the business operation management of the information processing system (the management target device 1) in operation by the business manager.
構成情報収集部17は,受信した構成情報を,構成情報テーブル26に格納する。また,構成情報収集部17は,構成情報に含まれるリソース間の関連情報をリソース関連情報テーブル27に格納し,管理対象装置1のリソース一覧(各リソースについてリソース識別子およびリソース種別)を影響度情報テーブル28に格納する。影響度情報テーブル28については後述する。
The configuration information collection unit 17 stores the received configuration information in the configuration information table 26. In addition, the configuration information collection unit 17 stores related information between resources included in the configuration information in the resource related information table 27, and displays a resource list (resource identifier and resource type for each resource) of the management target device 1 as impact information. Store in table 28. The influence information table 28 will be described later.
構成情報テーブル26は,図4~図6に示すように,リソース種別毎のテーブルで構成される。図4は,リソース種別101が“アプリケーション”の構成情報テーブル26の例のアプリケーション構成情報テーブル100であり,収集した構成情報に含まれるリソースを識別する識別子102,アプリケーション名103やインストールパス104などの属性値を格納する。図5はホスト構成情報テーブル105の例であり,属性値としてホスト名,IPアドレスなどを格納する。図6はプロセッサ構成情報テーブル106の例であり,属性値としてプロセッサの動作周波数やコア数などを格納する。例示を省略するが,リソース種別には,さらに,プロセッサやメモリなどのホストを構成するリソース,スイッチなどがある。
The configuration information table 26 is composed of tables for each resource type as shown in FIGS. FIG. 4 shows an application configuration information table 100 as an example of the configuration information table 26 in which the resource type 101 is “application”, such as an identifier 102 for identifying a resource included in the collected configuration information, an application name 103, an installation path 104, and the like. Stores attribute values. FIG. 5 shows an example of the host configuration information table 105, which stores a host name, an IP address, and the like as attribute values. FIG. 6 shows an example of the processor configuration information table 106, which stores the operating frequency of the processor, the number of cores, and the like as attribute values. Although illustration is omitted, the resource type further includes resources, switches, and the like that constitute a host such as a processor and a memory.
図7は,リソース関連情報テーブル27の例であり,リソース間の関連情報と関連の種別を格納する。リソース間の関連には関連元(リソース識別子およびリソース種別)108と関連先(リソース識別子およびリソース種別)109がある。関連種別110が“所有”であるたとえば“ホスト-A”と“アプリケーション-A”の関連は,関連元の“ホスト-A”が“アプリケーション-A”を所有していることを表す。関連種別110が“使用”は,関連元108が関連先109を使用してることを表す。換言すると,“所有”は包含関係を表し,“使用”は接続関係を表す。
FIG. 7 shows an example of the resource related information table 27, which stores related information between resources and the type of relationship. Associations between resources include an association source (resource identifier and resource type) 108 and an association destination (resource identifier and resource type) 109. For example, the relationship between “host-A” and “application-A” in which the association type 110 is “owned” indicates that “host-A” as the association source owns “application-A”. The relation type 110 “used” indicates that the relation source 108 uses the relation destination 109. In other words, “own” represents an inclusion relationship, and “use” represents a connection relationship.
構成情報収集部17は,リソース関連情報テーブル27に格納した関連情報を基にして,図8に示す構成確認画面111を,管理クライアント6のディスプレイに表示する。図8に示す構成確認画面111の例は,図7に示すリソース関連情報テーブル27に対応して,たとえば“ホスト-A”が“アプリケーション-A” 所有していることを示している。
The configuration information collection unit 17 displays the configuration confirmation screen 111 shown in FIG. 8 on the display of the management client 6 based on the related information stored in the resource related information table 27. The example of the configuration confirmation screen 111 shown in FIG. 8 indicates that, for example, “Host-A” owns “Application-A” corresponding to the resource related information table 27 shown in FIG.
<リソースの重要度算出(ステップ8)>
収集した構成情報に含まれるリソースにはリソース種別ごとの属性がある。図4のアプリケーション構成情報テーブル100では,アプリケーション名103やインストールパス104などが属性である。重要度計算部18は,図9に示す重要度定義テーブル31に定義されたリソースの種別201とその属性に関する条件202にマッチした重要度203を参照し,リソースごとの重要度を算出する。リソースの種別201と条件にマッチしないリソースの重要度は最小値の1とする。求めた重要度を影響度情報テーブル28の重要度カラムに格納する。 <Calculation of resource importance (step 8)>
The resources included in the collected configuration information have attributes for each resource type. In the application configuration information table 100 of FIG. 4, theapplication name 103, the installation path 104, and the like are attributes. The importance level calculation unit 18 refers to the importance level 203 that matches the condition 202 regarding the resource type 201 and its attributes defined in the importance level definition table 31 shown in FIG. 9, and calculates the importance level for each resource. The importance of a resource that does not match the condition of the resource type 201 is set to 1, which is the minimum value. The obtained importance is stored in the importance column of the influence information table 28.
収集した構成情報に含まれるリソースにはリソース種別ごとの属性がある。図4のアプリケーション構成情報テーブル100では,アプリケーション名103やインストールパス104などが属性である。重要度計算部18は,図9に示す重要度定義テーブル31に定義されたリソースの種別201とその属性に関する条件202にマッチした重要度203を参照し,リソースごとの重要度を算出する。リソースの種別201と条件にマッチしないリソースの重要度は最小値の1とする。求めた重要度を影響度情報テーブル28の重要度カラムに格納する。 <Calculation of resource importance (step 8)>
The resources included in the collected configuration information have attributes for each resource type. In the application configuration information table 100 of FIG. 4, the
重要度定義テーブル31のリソース種別201,条件202,重要度203の定義内容は,管理対象装置1の構成変更に応じて,管理クライアント6を通じて,システム管理者が入力,更新する。なお,リソースの種別201とその属性に関する条件202にマッチした重要度203の値は,業務運用管理の観点からのリソースの重要性に応じて定義され,アプリケーションなどの業務運用管理に係るリソースの重要度などは,予め業務管理者から得ておく。
The definition contents of the resource type 201, the condition 202, and the importance 203 in the importance definition table 31 are input and updated by the system administrator through the management client 6 according to the configuration change of the management target device 1. Note that the value of the importance 203 that matches the condition 202 regarding the resource type 201 and its attributes is defined according to the importance of the resource from the viewpoint of business operation management, and the importance of the resource related to business operation management such as an application. The degree is obtained from the business manager in advance.
図10は影響度情報テーブル28の例である。影響度情報テーブル28には,構成情報収集部17によってリソース識別子301,リソース種別302が既に格納されている。リソース識別子“アプリケーション-A”は重要度定義テーブル31にヒットし,その重要度203は5であるので,影響度情報テーブル28のリソース識別子301“アプリケーション-A”の重要度303に5を格納する。同様に,影響度情報テーブル28の全レコード(管理対象装置1の全リソース)に対して重要度を求め格納する。
FIG. 10 is an example of the impact information table 28. In the influence level information table 28, the resource identifier 301 and the resource type 302 are already stored by the configuration information collection unit 17. Since the resource identifier “application-A” hits the importance level definition table 31 and the importance level 203 is 5, 5 is stored in the importance level 303 of the resource identifier 301 “application-A” in the influence level information table 28. . Similarly, importance is obtained and stored for all records (all resources of the management target device 1) in the influence information table 28.
<リソースの影響度算出(ステップ9)>
リソース毎の影響度を次式により求める。
リソースの影響度 = (影響を与える全リソースの影響度の和) + (リソースの重要度)
影響度は,あるリソースに障害が発生した場合の管理対象装置1(情報処理システム)の業務遂行に与える影響の度合いを示し,上式に示すように,あるリソースに障害が発生した場合に,そのリソースの障害が影響するリソースの影響度と,そのリソースの重要度の和で定義する。 <Calculation of resource influence (step 9)>
The degree of influence for each resource is obtained by the following formula.
Resource impact = (sum of impacts of all affected resources) + (resource importance)
The degree of influence indicates the degree of influence on the business execution of the managed device 1 (information processing system) when a failure occurs in a certain resource. As shown in the above equation, when a failure occurs in a certain resource, Define the sum of the impact level of the resource affected by the resource failure and the importance level of the resource.
リソース毎の影響度を次式により求める。
リソースの影響度 = (影響を与える全リソースの影響度の和) + (リソースの重要度)
影響度は,あるリソースに障害が発生した場合の管理対象装置1(情報処理システム)の業務遂行に与える影響の度合いを示し,上式に示すように,あるリソースに障害が発生した場合に,そのリソースの障害が影響するリソースの影響度と,そのリソースの重要度の和で定義する。 <Calculation of resource influence (step 9)>
The degree of influence for each resource is obtained by the following formula.
Resource impact = (sum of impacts of all affected resources) + (resource importance)
The degree of influence indicates the degree of influence on the business execution of the managed device 1 (information processing system) when a failure occurs in a certain resource. As shown in the above equation, when a failure occurs in a certain resource, Define the sum of the impact level of the resource affected by the resource failure and the importance level of the resource.
影響度計算部19は,上式の影響度を求める対象のリソースが(影響を与える全リソースの影響度の和)を求めるために,図11に示す依存関係定義テーブル30を用いる。依存関係定義テーブル30は,影響を与える元である影響元リソース種別401,影響を受ける影響先リソース種別402,及び影響元の関連種別403を格納する。影響元の関連種別403は,リソース関連情報テーブル27に関連元のリソースと関連先のリソースのいずれとして格納されるかを示す。
The influence degree calculation unit 19 uses the dependency definition table 30 shown in FIG. 11 in order to obtain the target resource for which the influence degree of the above equation is obtained (the sum of the influence degrees of all the affecting resources). The dependency relationship definition table 30 stores an influence source resource type 401 that is an influence source, an influence destination resource type 402 that is affected, and an influence source relation type 403. The influence source relation type 403 indicates which of the relation source resource and the relation destination resource is stored in the resource relation information table 27.
影響度計算部19は,上式により各リソースの影響度を求め,影響度情報テーブル28の影響度304に格納する。影響度計算部19の処理フローを図12,図13に示す。
The influence degree calculation unit 19 obtains the influence degree of each resource by the above formula and stores it in the influence degree 304 of the influence degree information table 28. The processing flow of the influence calculation unit 19 is shown in FIGS.
影響度情報テーブル28のリソース識別子301に対応するリソース種別302が,依存関係定義テーブル30の影響元リソース種別401にあるかを検索する(ステップ501)。処理フローは,影響度情報テーブル28のリソース識別子301の一つに関する処理を示すが,影響度情報テーブル28のリソース識別子301のすべてに関して,影響度304を格納し終えるまで繰り返す。
It is searched whether the resource type 302 corresponding to the resource identifier 301 of the influence degree information table 28 is in the influence source resource type 401 of the dependency relationship definition table 30 (step 501). The processing flow shows processing related to one of the resource identifiers 301 of the influence degree information table 28, but is repeated until the influence degree 304 is stored for all of the resource identifiers 301 of the influence degree information table 28.
検索の結果,リソース種別がある場合はステップ503を依存関係毎に繰返し,ない場合はステップ505に分岐する(ステップ502)。リソース種別がない場合,影響度情報テーブル28の該当リソースの重要度303を影響度304とする(ステップ505)。たとえば,影響度情報テーブル28のリソース識別子301が“ホスト-A”のリソース種別302である“ホスト”を依存関係定義テーブル30で検索すると,リソース種別“ホスト”は依存関係定義テーブル30の影響元リソース種別401にあるので,ステップ503を実行して依存関係毎の影響度を算出する。
As a result of the search, if there is a resource type, step 503 is repeated for each dependency, and if not, the process branches to step 505 (step 502). If there is no resource type, the importance degree 303 of the resource in the influence degree information table 28 is set as the influence degree 304 (step 505). For example, when “dependence definition table 30 is searched for“ host ”, which is resource type 302 having resource identifier 301 of“ host-A ”in impact information table 28, resource type“ host ”is the influence source of dependency definition table 30. Since the resource type 401 exists, step 503 is executed to calculate the degree of influence for each dependency relationship.
依存関係毎の影響度の算出処理を図13を用いて説明する。依存関係定義テーブル30の影響元リソース種別401の関連種別403が関連元であるかを判定し(ステップ601),関連元である場合は,該当するリソースが関連元であり,依存関係定義テーブル30の影響先リソース種別402に等しい関連先リソース種別の関連をリソース関連情報テーブル27から検索する(ステップ602)。関連元でない場合は,該当するリソースが関連先であり,依存関係定義テーブル30の影響元リソース種別401に等しい関連元リソース種別をリソース関連情報テーブル27から検索する(ステップ605)。たとえば,影響元リソース種別401が“ホスト”の場合には,依存関係定義テーブル30の関連種別に“関連元”と定義してあるので,“ホスト-A”が関連元であり,関連先が依存関係定義テーブル30の影響先リソース種別402のアプリケーションである関連をリソース関連情報テーブル27から検索すると,関連先リソースとして,“アプリケーション-A”と“アプリケーション-B”と“アプリケーション-C”が見つかる。これが,“ホスト-A”が影響を与えるリソースになる。これを影響先リソース305として影響度情報テーブル28に格納する。
The influence degree calculation process for each dependency will be described with reference to FIG. It is determined whether or not the relation type 403 of the influence source resource type 401 in the dependency relation definition table 30 is the relation source (step 601). If the relation type is the relation source, the corresponding resource is the relation source, and the dependency relation definition table 30 The resource relation information table 27 is searched for the relation of the relation destination resource type equal to the influence destination resource type 402 (step 602). If it is not the association source, the relevant resource is the association destination, and the association source resource type equal to the influence source resource type 401 of the dependency relationship definition table 30 is searched from the resource association information table 27 (step 605). For example, when the influence source resource type 401 is “host”, since “related source” is defined as the related type in the dependency definition table 30, “host-A” is the related source, and the related destination is When a relationship that is an application of the affected resource type 402 in the dependency relationship definition table 30 is searched from the resource related information table 27, “application-A”, “application-B”, and “application-C” are found as related resources. . This is the resource that “Host-A” affects. This is stored in the impact information table 28 as the affected resource 305.
次に,関連先リソースとして見つけたリソース毎に,それぞれの影響度を求める(ステップ603)。たとえば,“アプリケーション-A”のリソース種別である“アプリケーション”は依存関係定義テーブル30の影響元リソース種別401にないので,“アプリケーション-A”が影響を与えるリソースは存在しない。これにより,“アプリケーション-A”の(影響を与える全リソースの影響度の和)は0と求まる。また,“アプリケーション-A”の重要度は影響度テーブル28から5と求まる。これにより,“アプリケーション-A”の影響度は0 + 5 = 5と求まり,これを影響度情報テーブル28の“アプリケーション-A”の行の影響度304に格納する。同様に,“アプリケーション-B”と“アプリケーション-C”の影響度はどちらも1と求まる。
Next, for each resource found as a related resource, the degree of influence is obtained (step 603). For example, since “application”, which is the resource type of “application-A”, is not included in the influence source resource type 401 of the dependency definition table 30, there is no resource that is affected by “application-A”. As a result, the “application-A” (the sum of the influence levels of all the affected resources) is 0. Further, the importance level of “application-A” is obtained as 5 from the influence degree table 28. As a result, the influence degree of “application-A” is obtained as 0 + 5 = , 5, and this is stored in the influence degree 304 of the row “application-A” of the influence degree information table 28. Similarly, the degree of influence of “application-B” and “application-C” is both 1.
次に,該当リソースの全ての依存関係の影響度と該当リソースの重要度との和を該当リソースの影響度とする(ステップ504)。該当リソースが“ホスト-A”の場合,“ホスト-A”の(影響を与える全リソースの影響度の和)は(“アプリケーション-A”の影響度) + (“アプリケーション-B”の影響度) + (”アプリケーション-C ”の影響度) = 5 + 1 + 1 = 7 と求まる。また,“ホスト-A”の重要度は影響度情報テーブル28において1であるので,“ホスト-A”の影響度は7 + 1 = 8と求まる。これを影響度情報テーブル28の“ホスト-A”の影響度304に格納する。
Next, the sum of the influence level of all the dependencies of the corresponding resource and the importance level of the corresponding resource is set as the influence level of the corresponding resource (step 504). When the corresponding resource is “Host-A”, the “Sum of the impact of all affected resources” of “Host-A” is (the impact of “Application-A”) + (the impact of “Application-B”) ) + (Influence of “Application-C 度”) = 5 + 1 + 1 = 7. Also, since the importance level of “host-A” is 1 in the impact level information table 28, the impact level of “host-A” is calculated as 7 + 1 = 8. This is stored in the influence degree 304 of “host-A” in the influence degree information table 28.
また,影響度計算部19は,算出した影響度を表す,図14に示す影響度確認画面112を,管理クライアント6のディスプレイに表示する。影響度確認画面112は,図8に示す構成情報確認画面111に,各リソースの影響度を重畳させた画面である。
Further, the influence degree calculation unit 19 displays an influence degree confirmation screen 112 shown in FIG. 14 representing the calculated influence degree on the display of the management client 6. The influence degree confirmation screen 112 is a screen in which the influence degree of each resource is superimposed on the configuration information confirmation screen 111 shown in FIG.
<リソースの多重度算出(ステップ10)>
管理対象装置1のリソースがクラスタ構成やハードウェアの冗長化構成などのように多重化されている場合,そのリソースに障害が発生した場合の管理対象装置1に与える影響は,多重化していないリソースよりも小さい。そこで,リソースの多重度計算部20では,多重化されているリソースを検索し,影響度を修正する。 <Calculation of resource multiplicity (step 10)>
When resources of the manageddevice 1 are multiplexed as in a cluster configuration or a hardware redundant configuration, the influence on the managed device 1 when a failure occurs in the resource is an unmultiplexed resource Smaller than. Therefore, the resource multiplicity calculation unit 20 searches for multiplexed resources and corrects the influence.
管理対象装置1のリソースがクラスタ構成やハードウェアの冗長化構成などのように多重化されている場合,そのリソースに障害が発生した場合の管理対象装置1に与える影響は,多重化していないリソースよりも小さい。そこで,リソースの多重度計算部20では,多重化されているリソースを検索し,影響度を修正する。 <Calculation of resource multiplicity (step 10)>
When resources of the managed
図15は,多重度定義テーブル29の例であり,多重化の対象のリソース種別701と多重化となる条件702が定義されている。リソースの多重度計算部20では,収集したリソース毎に多重度定義テーブル29を検索し,多重化しているリソースの組を発見する。発見したリソースの組を一つのリソースとして影響度情報テーブル28で扱い,その影響度は多重度にあわせて修正する。2重化されているリソースの影響度は1/2のように,影響度を1/(多重度)に修正し,影響度情報テーブル28の影響度304を更新する。
FIG. 15 is an example of the multiplicity definition table 29 in which a resource type 701 to be multiplexed and a condition 702 for multiplexing are defined. The resource multiplicity calculation unit 20 searches the multiplicity definition table 29 for each collected resource to find a set of multiplexed resources. The discovered resource set is handled as one resource in the impact information table 28, and the impact is corrected according to the multiplicity. The influence degree of the duplicated resource is corrected to 1 / (multiplicity) so that the influence degree of the resource is 1/2, and the influence degree 304 of the influence degree information table 28 is updated.
<アラートポリシー判定および発行(ステップ11~13)>
アラート検出部21がアラートポリシー34を参照し,アラートを発行するか判定する。アラートを発行する場合は,アラート出力部23がアラートを発行する。アラート出力部23では,管理クライアント6のディスプレイにGUI表示,メール送信,SNMP(Simple Network Management Protocol)などの少なくとも一つにより,ユーザにアラートを通知する。 <Alert policy judgment and issue (steps 11 to 13)>
Thealert detection unit 21 refers to the alert policy 34 to determine whether to issue an alert. When issuing an alert, the alert output unit 23 issues an alert. The alert output unit 23 notifies the user of an alert by at least one of GUI display, mail transmission, SNMP (Simple Network Management Protocol), etc. on the display of the management client 6.
アラート検出部21がアラートポリシー34を参照し,アラートを発行するか判定する。アラートを発行する場合は,アラート出力部23がアラートを発行する。アラート出力部23では,管理クライアント6のディスプレイにGUI表示,メール送信,SNMP(Simple Network Management Protocol)などの少なくとも一つにより,ユーザにアラートを通知する。 <Alert policy judgment and issue (
The
図16は,アラートポリシーテーブル34の例であり,影響度の上限値(閾値)801と上限値を超えたリソース数の閾値802と除外条件803として除外リソース種別が定義されている。除外条件803に該当せずに,影響度が上限値801を超え,その数(リソースの数)がリソース数の閾値802以上であるリソースを,アラート発行の対象とする。
FIG. 16 is an example of the alert policy table 34, in which an excluded resource type is defined as an upper limit value (threshold value) 801 of the degree of influence, a threshold value 802 of the number of resources exceeding the upper limit value, and an exclusion condition 803. A resource whose impact level exceeds the upper limit value 801 and whose number (the number of resources) is not less than the threshold value 802 for the number of resources is not subject to the exclusion condition 803.
図17に,アラートの判定および発行の処理フローを示す。影響度がユーザが規定した閾値を超えた場合,そのリソースに関してアラートを発行しシステム管理者に通知する。アラート検出部21では,各リソースに関して影響度計算部19(多重度計算部20による修正を含む)により影響度304が求められた影響度情報テーブル28から,アラートポリシーテーブル34の影響度の上限値801を超えたリソース数を検索し,検索したリソース数が,アラートポリシーテーブル34の上限を超えたリソース数の閾値802を超えていた場合(ステップ900),アラート出力部23を通して,アラートをユーザに通知する(ステップ901)。なお,リソース数の閾値802を用いずに,影響度の上限値801を超えたリソースをアラート発行の対象のリソースとする簡易な判定でもよい。図16に示す例では,リソース数の閾値802が1であるので,実質的に簡易な判定と同じになる。
Fig. 17 shows the processing flow for alert determination and issue. When the degree of influence exceeds a threshold specified by the user, an alert is issued regarding the resource and notified to the system administrator. In the alert detection unit 21, the upper limit value of the influence degree of the alert policy table 34 is obtained from the influence degree information table 28 in which the influence degree 304 is obtained by the influence degree calculation part 19 (including correction by the multiplicity calculation part 20) for each resource. When the number of resources exceeding 801 is searched and the number of searched resources exceeds the threshold 802 for the number of resources exceeding the upper limit of the alert policy table 34 (step 900), the alert is sent to the user through the alert output unit 23. Notification is made (step 901). Instead of using the threshold value 802 for the number of resources, a simple determination may be made such that a resource exceeding the upper limit 801 of the influence degree is set as a resource to be alerted. In the example shown in FIG. 16, since the threshold value 802 for the number of resources is 1, this is substantially the same as the simple determination.
図10の影響度情報テーブル28と図16のアラートポリシーテーブル34に示す例では,影響度上限値801の7を超えているリソース数が,除外条件803を満たすネットワークスイッチを除いて4つあり,リソース数閾値802の1も超えているので,アラートを発行する。
In the example shown in the impact information table 28 in FIG. 10 and the alert policy table 34 in FIG. 16, there are four resources that exceed the impact upper limit value 801 of 7 except for the network switch that satisfies the exclusion condition 803. Since 1 of the resource number threshold value 802 is also exceeded, an alert is issued.
<推奨する構成変更案作成(ステップ14)>
影響度が規定した閾値を超えた場合,アラートを発行すると共に,ユーザに対して推奨する構成変更案を提供する。推奨構成生成部22が,推奨する構成変更案を作成し,推奨構成表示部25が,作成した構成変更案を表示する。 <Recommended configuration change proposal creation (step 14)>
When the degree of influence exceeds a specified threshold, an alert is issued and a recommended configuration change proposal is provided to the user. The recommendedconfiguration generation unit 22 creates a recommended configuration change plan, and the recommended configuration display unit 25 displays the created configuration change plan.
影響度が規定した閾値を超えた場合,アラートを発行すると共に,ユーザに対して推奨する構成変更案を提供する。推奨構成生成部22が,推奨する構成変更案を作成し,推奨構成表示部25が,作成した構成変更案を表示する。 <Recommended configuration change proposal creation (step 14)>
When the degree of influence exceeds a specified threshold, an alert is issued and a recommended configuration change proposal is provided to the user. The recommended
図18に,推奨構成生成部22の処理フローを示す。推奨構成生成部22は,分散化構成作成処理(ステップ1002)と多重化構成作成処理(ステップ1004)を実行し,管理対象装置1の新たな構成案として分散化構成と多重化構成の構成変更案を作成する。
FIG. 18 shows a processing flow of the recommended configuration generation unit 22. The recommended configuration generation unit 22 executes the distributed configuration creation processing (step 1002) and the multiplexed configuration creation processing (step 1004), and changes the configuration of the distributed configuration and the multiplexed configuration as a new configuration plan of the management target device 1. Create a draft.
以下,分散化構成作成処理(ステップ1002)と多重化構成作成処理(ステップ1004)について説明する。
Hereinafter, the distributed configuration creation processing (step 1002) and the multiplexed configuration creation processing (step 1004) will be described.
<分散化構成変更案作成(ステップ1002)>
分散化構成作成の処理フローを図19に示す。本処理では,分散化した推奨構成を分散化構成情報テーブル32に格納する。 <Distributed configuration change plan creation (step 1002)>
FIG. 19 shows a processing flow for creating a distributed configuration. In this process, the distributed recommended configuration is stored in the distributed configuration information table 32.
分散化構成作成の処理フローを図19に示す。本処理では,分散化した推奨構成を分散化構成情報テーブル32に格納する。 <Distributed configuration change plan creation (step 1002)>
FIG. 19 shows a processing flow for creating a distributed configuration. In this process, the distributed recommended configuration is stored in the distributed configuration information table 32.
まず該当リソースの影響先リソース305の一覧を影響度情報テーブル28から取得する(ステップ1105)。“ホスト-A”を例にすると,影響度情報テーブル28より,“アプリケーション-A”と“アプリケーション-B”と“アプリケーション-C”を取得する。ここで,該当リソースとは,影響度が規定した閾値を超えているリソースであり,複数ある場合は,それら複数のリソースに関して図19に示す処理を繰り返す。
First, a list of affected resources 305 of the corresponding resource is acquired from the impact information table 28 (step 1105). Taking “host-A” as an example, “application-A”, “application-B”, and “application-C” are acquired from the impact information table 28. Here, the corresponding resource is a resource whose influence level exceeds a prescribed threshold value. When there are a plurality of resources, the processing shown in FIG. 19 is repeated for the plurality of resources.
次に,該当リソースに与える影響度が大きいリソースの順に,割り当て可能なリソースを検索する(ステップ1106)。“ホストA”に影響を与えるリソースを影響度順に並べると,“アプリケーション-A”,“アプリケーション-B” ,“アプリケーション-C”の順になる(影響度が同値の場合は順不同)。この場合,まず“アプリケーションA”を割り当てるリソースを検索する。
Next, the resources that can be allocated are searched in the order of the resources having the greatest influence on the resource (step 1106). When the resources that affect “Host A” are arranged in order of impact, they are in the order of “Application-A”, “Application-B”, and “Application-C” (in the case of the same impact, they are in no particular order). In this case, first, a resource to which “application A” is allocated is searched.
図20に,ステップ1106の割り当て可能なリソース検索の処理フローを示す。リソースの一覧を取得する(ステップ1109)。リソースの一覧は,管理対象装置1のリソースの一覧であり,構成管理サーバ5に格納され管理されている。なお,リソースの一覧には,管理対象装置1を構成するリソースではあるが使用されていないリソースも含んでいる。リソースの一覧の中に追加リソースとしてのホストがない状態では,割り当て可能なリソースは“ホスト-A”しかなく,また,“ホスト-A”には関連が割り当っていない(再割り当てのため,構成変更収集部で収集した関連は考慮せずに,“ホスト-A”には関連を割り当てていない初期状態を想定する)ので,“アプリケーション-A”を“ホスト-A”に割り当てる。これにより,ホストAの影響度は“アプリケーションA”の影響度 + “ホストA”の重要度 = 5 + 1 = 6 となり,アラートの閾値を超えてしまうが,“ホストA”は未割り当てリソースのため,“アプリケーションA”を割り当てることとし,分散化構成テーブル1100に格納する。図22は分散化構成情報テーブル32の例であり,リソース識別子1101が“ホストA”のリソースにリソース識別子1103が“アプリケーション-A”を割り当てることを示している(ステップ1108)。
FIG. 20 shows a process flow for searching for resources that can be allocated in step 1106. A list of resources is acquired (step 1109). The resource list is a list of resources of the management target device 1 and is stored and managed in the configuration management server 5. Note that the resource list includes resources that constitute the management target device 1 but are not used. When there is no host as an additional resource in the resource list, the only resource that can be allocated is “Host-A”, and no association is assigned to “Host-A” (for reassignment, (Assuming an initial state in which no association is assigned to “Host-A” without considering the association collected by the configuration change collection unit), “Application-A” is assigned to “Host-A”. As a result, the impact level of Host A becomes “Application A” impact level + “Host A” severity level = 5 + 1 = 6, which exceeds the alert threshold, but “Host A” is an unallocated resource. Therefore, “application A” is assigned and stored in the distributed configuration table 1100. FIG. 22 is an example of the distributed configuration information table 32, and shows that the resource identifier 1103 assigns “application-A” to the resource with the resource identifier 1101 “host A” (step 1108).
次に,“アプリケーション-B”を割り当てるリソースを検索する。割り当て対象のリソースは“ホスト-A”があるが,“ホスト-A”に割り当てた場合,“ホスト-A”の影響度は“アプリケーション-A”の影響度 + “アプリケーション-B”の影響度 + “ホスト-A”の重要度 = 5 + 1 + 1 = 7となり,アラートポリシーの影響度上限値を超えてしまう。
Next, search for resources to which “Application-B” is assigned. The resource to be assigned is “Host-A”, but when assigned to “Host-A”, the impact of “Host-A” is the impact of “Application-A” + The impact of “Application-B” + The importance of “Host-A” is = 5 + 1 + 1 = 7, which exceeds the upper limit of the impact level of the alert policy.
“ホスト-A”は未割り当てリソースでもない(すでに“アプリケーション-A”を割り当てている)ため,割り当てるリソースが見つからない(ステップ1110)。割り当てるリソースが見つからない場合,新規のリソースを追加する(ステップ1107)。図22の例では,新しいリソース“追加ホスト”を追加し,“アプリケーション-B”を“追加ホスト”に割り当てる。同様に,“アプリケーション-C”は“追加ホスト”に割り当てることになる。以上のように “ホスト-A”に関して作成した分散化テーブル(分散化変更案情報の実現形式の一つ)を図22に示す。また,分散化テーブル1100には,作成した推奨構成の影響度1104を格納する。
Since “Host-A” is not an unassigned resource (“Application-A” has already been assigned), the assigned resource is not found (step 1110). If a resource to be allocated cannot be found, a new resource is added (step 1107). In the example of FIG. 22, a new resource “additional host” is added and “application-B” is assigned to “additional host”. Similarly, “Application-C” is assigned to “Additional Host”. FIG. 22 shows a decentralized table (one of the forms for realizing decentralized change plan information) created for “Host-A” as described above. Also, the degree of influence 1104 of the created recommended configuration is stored in the distributed table 1100.
以上の例は,新しいリソースとして“追加ホスト”がリソースの一覧にある場合,すなわち管理対象装置1を構成するリソース(ホスト)ではあるが使用されていないリソース(ホスト)がある場合であるが,新しいリソースがない場合がある。この場合は,分散化構成をとる必要があるが追加リソースがなく,分散化構成をとることができないことを,管理クライアント6を介してシステム管理者に通知するか,追加リソースがあるとして分散化構成案を作成し,リソースの追加を促すメッセージをシステム管理者に通知する。
The above example is a case where “additional host” is in the resource list as a new resource, that is, there is a resource (host) that is a resource (host) that constitutes the managed device 1 but is not used. There may be no new resources. In this case, it is necessary to adopt a decentralized configuration, but there is no additional resource, and the system administrator is notified via the management client 6 that the decentralized configuration cannot be taken. Create a configuration proposal and notify the system administrator of a message prompting you to add resources.
<多重化構成変更案作成(ステップ1004)>
多重化構成作成の処理フローを図21に示す。本処理では,多重化の推奨構成を多重化構成情報テーブル33に格納する。 <Multiplexing configuration change proposal creation (step 1004)>
FIG. 21 shows a processing flow for creating a multiplexed configuration. In this processing, the recommended multiplexing configuration is stored in the multiplexing configuration information table 33.
多重化構成作成の処理フローを図21に示す。本処理では,多重化の推奨構成を多重化構成情報テーブル33に格納する。 <Multiplexing configuration change proposal creation (step 1004)>
FIG. 21 shows a processing flow for creating a multiplexed configuration. In this processing, the recommended multiplexing configuration is stored in the multiplexing configuration information table 33.
まず現在の影響度と閾値から多重度を以下の計算式より算出する(ステップ1204)。多重度 = リソースの影響度 / リソースの閾値 (但し,小数点以下切り上げ) 以下,リソースとして“ホスト-A”を取り上げて説明するが,影響度が規定した閾値を超えているリソースが複数ある場合は,それら複数のリソースに関して,以下に説明する処理を繰り返す。
First, the multiplicity is calculated from the current influence level and threshold value by the following formula (step 1204). Multiplicity = Resource impact / Resource threshold 但 (however, rounded up after the decimal point) Hereafter, “Host-A” will be taken up as a resource, but if there are multiple resources whose impact exceeds the specified threshold , The processing described below is repeated for the plurality of resources.
図10の影響度テーブル28より “ホスト-A”の影響度は8であり,図16のアラートポリシーテーブル34より影響度上限値は7なので,多重度は[8 / 7 ]= 2と求まる(ステップ1204)。なお,[ ]は,小数点以下を切り上げた整数値を表す。これより,現在の“ホスト-A”に1つ“追加ホスト”を追加し(ステップ1205),ホスト数を2とする。次に,“追加ホスト”と“ホスト-A”に影響を与えているリソース(“アプリケーション-A”と“アプリケーション-B”と“アプリケーションC”)との間の関連を作成する(ステップ1206)。さらに,“ホスト-A”と“追加ホスト”の影響度は多重度2で多重化しているため,影響度を1/(多重度)とし,それぞれ8 / 2 = 4となる。また,作成した多重化構成のリソース識別子1201とリソース種別1202と算出した推奨構成での影響度1203は多重化テーブル1200(多重化変更案情報の実現形式の一つ)に格納する。図23に多重化構成テーブルの例を示す。
Since the influence degree of “Host-A” is 8 from the influence degree table 28 of FIG. 10 and the influence upper limit value is 7 from the alert policy table 34 of FIG. 16, the multiplicity is obtained as [8/7] = 2. Step 1204). [] Represents an integer value rounded up after the decimal point. Thus, one “additional host” is added to the current “host-A” (step 1205), and the number of hosts is set to two. Next, an association is created between “additional host” and resources affecting “host-A” (“application-A”, “application-B”, and “application C”) (step 1206). . Furthermore, since the degree of influence of “host-A” and “additional host” is multiplexed at multiplicity 2, the degree of influence is 1 / (multiplicity), and 8/2 = 4 respectively. The created multiplexing configuration resource identifier 1201 and resource type 1202 and the calculated recommended configuration impact 1203 are stored in the multiplexing table 1200 (one of the implementation forms of multiplexing change plan information). FIG. 23 shows an example of a multiplexing configuration table.
なお,“追加ホスト”に関しては,分散化構成変更案作成の場合と同様に,追加ホストとしてのリソースがない場合,多重化構成をとる必要があるが追加リソースがなく,多重化構成をとることができないことを,管理クライアント6を介してシステム管理者に通知するか,追加リソースがあるとして多重化構成案を作成し,リソースの追加を促すメッセージをシステム管理者に通知する。
As for “additional host”, as in the case of creating a distributed configuration change proposal, if there is no resource as an additional host, it is necessary to adopt a multiplexing configuration, but there is no additional resource and a multiplexing configuration is adopted. The system administrator is notified via the management client 6 that the system cannot perform the operation, or a multiplexing configuration plan is created on the assumption that there are additional resources, and a message prompting the addition of resources is notified to the system administrator.
<推奨する構成変更案を表示(ステップ15)>
推奨構成表示部25は,推奨する構成変更案を管理クライアント6に表示する。図24は推奨構成表示画面1300の例である。また,推奨構成表示画面に必要な情報は分散化構成情報テーブル32と多重化構成情報テーブル33に保存されているため,推奨構成表示画面1300は構成変更後でも表示可能である。 <Display recommended configuration change proposal (step 15)>
The recommendedconfiguration display unit 25 displays a recommended configuration change plan on the management client 6. FIG. 24 shows an example of a recommended configuration display screen 1300. Further, since the information necessary for the recommended configuration display screen is stored in the distributed configuration information table 32 and the multiplexed configuration information table 33, the recommended configuration display screen 1300 can be displayed even after the configuration is changed.
推奨構成表示部25は,推奨する構成変更案を管理クライアント6に表示する。図24は推奨構成表示画面1300の例である。また,推奨構成表示画面に必要な情報は分散化構成情報テーブル32と多重化構成情報テーブル33に保存されているため,推奨構成表示画面1300は構成変更後でも表示可能である。 <Display recommended configuration change proposal (step 15)>
The recommended
そこで,システムの運用管理者は,推奨構成に従い構成変更を実施したあと,影響度確認画面で,構成変更後の影響度を表示し,推奨構成画面1300と比較することで同じ構成に変更ができたことを確認することができる。
Therefore, the system administrator can change the configuration to the same by displaying the impact after the configuration change on the impact confirmation screen after making the configuration change according to the recommended configuration and comparing it with the recommended configuration screen 1300. Can be confirmed.
本実施形態によれば,情報処理システムに障害が発生しにくい,特に業務運用に与える影響が大きい障害が発生しにくいシステム運用管理が可能になる。具体的には,障害が発生した場合に情報システムに重大な影響を及ぼす恐れがあるリソースを事前に検知し,検知内容に対応した構成変更案をシステム管理者に対して提案することが可能になる。また実際の構成変更後に構成変更案どおりに構成変更できたか検証することが可能になる。
According to the present embodiment, it is possible to perform system operation management in which a failure is unlikely to occur in the information processing system, and particularly, a failure that has a large influence on business operations is unlikely to occur. Specifically, it is possible to detect in advance resources that may have a serious impact on the information system in the event of a failure, and propose a configuration change proposal corresponding to the detected content to the system administrator. Become. In addition, it is possible to verify whether the configuration can be changed according to the configuration change plan after the actual configuration change.
1:管理対象装置,2:サーバ装置,4:スイッチ,5:構成管理サーバ,6:管理クライアント,16:構成情報提供部,17:構成情報取得部,18:重要度計算部,19:影響度計算部,20:多重度計算部,21:アラート検出部,22:推奨構成生成部,23:アラート出力部,24:アラートポリシー設定部,25:推奨構成表示部,26:構成情報テーブル,27:リソース関連情報テーブル,28:影響度情報テーブル,29:多重度定義テーブル,30:依存関係定義テーブル,31:重要度定義テーブル,32:分散化構成情報テーブル,33:多重化構成情報テーブル,34:アラート ポリシー,35:構成情報制御部。
1: managed device, 2: server device, 4: switch, 5: configuration management server, 6: management client, 16: configuration information providing unit, 17: configuration information acquisition unit, 18: importance calculation unit, 19: influence Degree calculation unit, 20: multiplicity calculation unit, 21: alert detection unit, 22: recommended configuration generation unit, 23: alert output unit, 24: alert policy setting unit, 25: recommended configuration display unit, 26: configuration information table, 27: Resource related information table, 28: Impact information table, 29: Multiplicity definition table, 30: Dependency definition table, 31: Importance definition table, 32: Distributed configuration information table, 33: Multiplex configuration information table , 34: Alert policy, 35: Configuration information control unit.
Claims (10)
- 構成を管理する対象である情報処理システムと接続する運用管理装置であって,
管理クライアントと接続し,稼動中の前記情報処理システムから,前記情報処理システムの構成情報を取得する構成情報取得部,
取得した前記構成情報から,前記情報処理システムを構成するリソースに障害が発生した場合に,前記情報処理システムの業務遂行に与える影響を示す影響度を各リソースについて算出する影響度計算部,及び,
算出した前記影響度が予め定めた影響度の上限値を超えているリソースがある場合に,前記リソースの影響度が前記上限値を下回る前記情報処理システムの構成案を作成する構成生成部を有することを特徴とする運用管理装置。 An operation management device connected to an information processing system whose configuration is to be managed,
A configuration information acquisition unit that connects to a management client and acquires configuration information of the information processing system from the information processing system in operation;
An influence calculation unit for calculating an influence degree indicating an influence on business execution of the information processing system when a failure occurs in the resource constituting the information processing system from the obtained configuration information; and
A configuration generation unit configured to create a configuration plan of the information processing system in which the influence degree of the resource is lower than the upper limit value when the calculated influence degree exceeds a predetermined upper limit value of the influence degree; An operation management apparatus characterized by that. - 前記情報処理システムの構成案は,前記リソースの影響度が前記上限値を下回る前記情報処理システムの分散化構成と多重化構成の構成変更案であることを特徴とする請求項1記載の運用管理装置。 2. The operation management according to claim 1, wherein the configuration plan of the information processing system is a configuration change plan of a distributed configuration and a multiplexed configuration of the information processing system in which the influence degree of the resource is lower than the upper limit value. apparatus.
- 前記影響度計算部は,前記情報処理システムを構成する前記リソースに障害が発生した場合に,前記リソースが影響を与える他のリソース影響度と前記リソースの重要度の和を前記リソースの影響度として算出することを特徴とする請求項2記載の運用管理装置。 The influence calculation unit, when a failure occurs in the resource constituting the information processing system, uses the sum of the importance of the resource and the other resource influence that the resource affects as the influence degree of the resource The operation management apparatus according to claim 2, wherein the operation management apparatus is calculated.
- 前記影響度計算部が前記影響度を算出した前記各リソースの中で,多重化構成されているリソースに関して,算出した前記影響度を修正する多重度計算部をさらに有することを特徴とする請求項2記載の運用管理装置。 The multiplicity calculation unit for correcting the calculated influence degree with respect to a resource configured to be multiplexed among the resources for which the influence degree calculation unit has calculated the influence degree. 2. The operation management apparatus according to 2.
- 前記管理クライアントから入力される前記予め定めた影響度の上限値を設定するアラートポリシー設定部,前記各リソースについて算出した前記影響度が予め前記定めた影響度の上限値を超えているか否かを判定するアラート検出部,および,算出した前記影響度が予め前記定めた影響度の上限値を超えている場合にアラートを前記管理クライアントに出力するアラート出力部をさらに有することを特徴とする請求項2記載の運用管理装置。 An alert policy setting unit for setting the upper limit value of the predetermined influence level input from the management client, whether the influence level calculated for each resource exceeds the upper limit value of the predetermined influence level An alert detection unit for determining, and an alert output unit for outputting an alert to the management client when the calculated degree of influence exceeds an upper limit value of the predetermined degree of influence. 2. The operation management apparatus according to 2.
- 構成を管理する対象である情報処理システムと接続する運用管理装置による運用管理方法であって,前記運用管理装置は管理クライアントと接続し,前記運用管理装置は,稼動中の前記情報処理システムから,前記情報処理システムの構成情報を取得し,取得した前記構成情報から,前記情報処理システムを構成するリソースに障害が発生した場合に,前記情報処理システムの業務遂行に与える影響を示す影響度を各リソースについて算出し,
算出した前記影響度が予め定めた影響度の上限値を超えているリソースがある場合に,前記リソースの影響度が前記上限値を下回る前記情報処理システムの構成案を作成することを特徴とする運用管理方法。 An operation management method by an operation management apparatus connected to an information processing system whose configuration is to be managed, wherein the operation management apparatus is connected to a management client, and the operation management apparatus is connected to the information processing system in operation, The configuration information of the information processing system is acquired, and the degree of influence indicating the influence on the performance of the information processing system when a failure occurs in a resource configuring the information processing system from each of the acquired configuration information. Calculate resources,
When there is a resource for which the calculated influence degree exceeds a predetermined upper limit value of the influence degree, a configuration plan of the information processing system in which the influence degree of the resource is lower than the upper limit value is created. Operation management method. - 前記情報処理システムの構成案は,前記リソースの影響度が前記上限値を下回る前記情報処理システムの分散化構成と多重化構成の構成変更案であることを特徴とする請求項6記載の運用管理方法。 7. The operation management according to claim 6, wherein the configuration plan of the information processing system is a configuration change plan of a distributed configuration and a multiplexed configuration of the information processing system in which the influence degree of the resource is lower than the upper limit value. Method.
- 前記運用管理装置は,前記情報処理システムを構成する前記リソースに障害が発生した場合に,前記リソースが影響を与える他のリソース影響度と前記リソースの重要度の和を前記リソースの影響度として算出することを特徴とする請求項7記載の運用管理方法。 The operation management device calculates, as a resource influence degree, the sum of importance of the resource and another resource influence degree that the resource influences when a failure occurs in the resource constituting the information processing system The operation management method according to claim 7, wherein:
- 前記運用管理装置は,前記影響度を算出した前記各リソースの中で,多重化構成されているリソースに関して,算出した前記影響度を修正することを特徴とする請求項7記載の運用管理方法。 The operation management method according to claim 7, wherein the operation management apparatus corrects the calculated influence degree with respect to a resource configured to be multiplexed among the resources for which the influence degree is calculated.
- 前記運用管理装置は,前記管理クライアントから入力される前記予め定めた影響度の上限値を設定し,前記各リソースについて算出した前記影響度が予め前記定めた影響度の上限値を超えているか否かを判定し,算出した前記影響度が予め前記定めた影響度の上限値を超えている場合にアラートを前記管理クライアントに出力することを特徴とする請求項7記載の運用管理方法。 The operation management apparatus sets an upper limit value of the predetermined influence degree input from the management client, and whether the influence degree calculated for each resource exceeds the upper limit value of the predetermined influence degree. The operation management method according to claim 7, wherein an alert is output to the management client when the calculated degree of influence exceeds an upper limit value of the predetermined degree of influence.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010106351A JP2013178592A (en) | 2010-05-06 | 2010-05-06 | Operation management device and operation management method of information processing system |
JP2010-106351 | 2010-05-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011138879A1 true WO2011138879A1 (en) | 2011-11-10 |
Family
ID=44903731
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2011/053044 WO2011138879A1 (en) | 2010-05-06 | 2011-02-14 | Operation management device and operation management method of information processing system |
Country Status (2)
Country | Link |
---|---|
JP (1) | JP2013178592A (en) |
WO (1) | WO2011138879A1 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014002557A1 (en) * | 2012-06-29 | 2014-01-03 | 日本電気株式会社 | Shared risk effect evaluation system, shared risk effect evaluation method, and program |
WO2014188638A1 (en) * | 2013-05-22 | 2014-11-27 | 日本電気株式会社 | Shared risk group management system, shared risk group management method, and shared risk group management program |
JPWO2013114911A1 (en) * | 2012-02-01 | 2015-05-11 | 日本電気株式会社 | Risk assessment system, risk assessment method, and program |
CN104679619A (en) * | 2013-11-28 | 2015-06-03 | 英业达科技有限公司 | Server and detection method of server |
WO2015114816A1 (en) * | 2014-01-31 | 2015-08-06 | 株式会社日立製作所 | Management computer, and management program |
WO2015121925A1 (en) * | 2014-02-12 | 2015-08-20 | 株式会社日立製作所 | System managing method |
CN106126389A (en) * | 2016-06-23 | 2016-11-16 | 上海爱数信息技术股份有限公司 | Hardware detection method and system |
JPWO2014115504A1 (en) * | 2013-01-23 | 2017-01-26 | 日本電気株式会社 | Information processing apparatus and influence determination method |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5625621B2 (en) * | 2010-08-25 | 2014-11-19 | 富士通株式会社 | Detection apparatus, method, and program |
CN103744735B (en) * | 2014-01-09 | 2017-07-25 | 福建星网锐捷网络有限公司 | The dispatching method and device of a kind of multi-core resource |
US10693745B2 (en) | 2018-02-27 | 2020-06-23 | Servicenow, Inc. | Defining and enforcing operational associations between configuration item classes in managed networks |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003058520A (en) * | 2001-08-09 | 2003-02-28 | Mitsubishi Heavy Ind Ltd | Computer arrangement method |
JP2005234861A (en) * | 2004-02-19 | 2005-09-02 | Mitsubishi Electric Corp | Management device and management system |
JP2008217285A (en) * | 2007-03-02 | 2008-09-18 | Hitachi Ltd | Operation management apparatus and operation management method for information processing system |
JP2009223497A (en) * | 2008-03-14 | 2009-10-01 | Nec Corp | Management machine, management system, management program, and management method |
JP2009277022A (en) * | 2008-05-15 | 2009-11-26 | Fujitsu Ltd | Information processing system, load control method, and load control program |
-
2010
- 2010-05-06 JP JP2010106351A patent/JP2013178592A/en active Pending
-
2011
- 2011-02-14 WO PCT/JP2011/053044 patent/WO2011138879A1/en active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003058520A (en) * | 2001-08-09 | 2003-02-28 | Mitsubishi Heavy Ind Ltd | Computer arrangement method |
JP2005234861A (en) * | 2004-02-19 | 2005-09-02 | Mitsubishi Electric Corp | Management device and management system |
JP2008217285A (en) * | 2007-03-02 | 2008-09-18 | Hitachi Ltd | Operation management apparatus and operation management method for information processing system |
JP2009223497A (en) * | 2008-03-14 | 2009-10-01 | Nec Corp | Management machine, management system, management program, and management method |
JP2009277022A (en) * | 2008-05-15 | 2009-11-26 | Fujitsu Ltd | Information processing system, load control method, and load control program |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPWO2013114911A1 (en) * | 2012-02-01 | 2015-05-11 | 日本電気株式会社 | Risk assessment system, risk assessment method, and program |
WO2014002557A1 (en) * | 2012-06-29 | 2014-01-03 | 日本電気株式会社 | Shared risk effect evaluation system, shared risk effect evaluation method, and program |
JPWO2014115504A1 (en) * | 2013-01-23 | 2017-01-26 | 日本電気株式会社 | Information processing apparatus and influence determination method |
WO2014188638A1 (en) * | 2013-05-22 | 2014-11-27 | 日本電気株式会社 | Shared risk group management system, shared risk group management method, and shared risk group management program |
CN104679619A (en) * | 2013-11-28 | 2015-06-03 | 英业达科技有限公司 | Server and detection method of server |
WO2015114816A1 (en) * | 2014-01-31 | 2015-08-06 | 株式会社日立製作所 | Management computer, and management program |
US9990258B2 (en) | 2014-01-31 | 2018-06-05 | Hitachi, Ltd. | Management computer and management program |
WO2015121925A1 (en) * | 2014-02-12 | 2015-08-20 | 株式会社日立製作所 | System managing method |
US9852007B2 (en) | 2014-02-12 | 2017-12-26 | Hitachi, Ltd. | System management method, management computer, and non-transitory computer-readable storage medium |
CN106126389A (en) * | 2016-06-23 | 2016-11-16 | 上海爱数信息技术股份有限公司 | Hardware detection method and system |
CN106126389B (en) * | 2016-06-23 | 2019-02-01 | 上海爱数信息技术股份有限公司 | Hardware detection method and system |
Also Published As
Publication number | Publication date |
---|---|
JP2013178592A (en) | 2013-09-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011138879A1 (en) | Operation management device and operation management method of information processing system | |
US8015275B2 (en) | Computer product, method, and apparatus for managing operations of servers | |
US7949882B2 (en) | Storage session management system in storage area network | |
CN108632067B (en) | Disaster recovery deployment method, device and system | |
US9417978B2 (en) | Management system for managing computer system, method for managing computer system, and storage medium | |
US20070234116A1 (en) | Method, apparatus, and computer product for managing operation | |
WO2011101887A1 (en) | Management system and method of controlling management system | |
JP2011237844A (en) | Load balancer and system | |
US7987394B2 (en) | Method and apparatus for expressing high availability cluster demand based on probability of breach | |
JP2004127141A (en) | Method for managing volume and obstruction in network having storage device | |
US20140143418A1 (en) | Management computer, storage system management method, and storage system | |
US11886904B2 (en) | Virtual network function VNF deployment method and apparatus | |
US9881056B2 (en) | Monitor system and monitor program | |
EP3044906A1 (en) | Apparatus and method for monitoring network performance | |
KR101586354B1 (en) | Communication failure recover method of parallel-connecte server system | |
CN108780408B (en) | Identifying implementation status of logical entities based on global implementation number | |
WO2013171865A1 (en) | Management method and management system | |
CN102724104A (en) | Apparatus and method for automatically configuring Java EE application cluster | |
US8489721B1 (en) | Method and apparatus for providing high availabilty to service groups within a datacenter | |
US9317355B2 (en) | Dynamically determining an external systems management application to report system errors | |
JP5549374B2 (en) | Load balancing apparatus and load balancing control method | |
US9575865B2 (en) | Information processing system and monitoring method | |
JP5734421B2 (en) | Management information generation method, management information generation program, and management information generation apparatus | |
US10990429B2 (en) | Rule-based reallocation of hosted compute resources | |
CN102571880B (en) | Service dispatching method and system as well as service dispatching node |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11777398 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11777398 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: JP |