Configuration change support device and configuration change support method

Abstract

To provide a technology which can support a configuration change of an IT infrastructure.SOLUTION: A configuration integration management server 40 comprises a storage device and a processing device. The storage device stores: IT infrastructure configuration information indicating physical connection of an IT infrastructure, logical connection, and arrangement information on a resource which configures the IT infrastructure; and application dependence information indicating dependence information to the IT infrastructure of an application 52 executed by a host 50. The processing device is configured to: acquire configuration change information on the IT infrastructure; create addition configuration change information for minimizing the impact on the application 52 in performing configuration change of the configuration change information on the basis of the configuration change information, the IT infrastructure configuration information, and the application dependence information; create an application impact element indicating the impact on the application 52 in performing configuration change of the configuration change information and the addition configuration change information; and notify a configuration change performer of the application impact element and the addition configuration change information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a configuration change support device and a configuration change support method. [Background technology]

[0002] Today's IT infrastructure consists of a stack of multiple virtualization technologies, including the storage layer, VM (Virtual Machine) layer, and container layer, and infrastructure administrators at each layer are generally unaware of the configuration of layers other than those they are responsible for. However, for storage plugins for containers, the storage configuration information must be entered as application configuration information provided by the storage administrator. Performing configuration changes such as VM migration without being aware of this configuration information can result in problems such as system environment destruction, even if VM resources are migrated appropriately.

[0003] In the method described in Patent Document 1, configuration information is automatically discovered, and for the migration of one or more components, a portion of the configuration information indicating the connection relationships that should be maintained for the components to be migrated is passed to a migration service provider, which then carries out the migration of each component. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Special Publication No. 2019-525302 Summary of the Invention [Problem to be solved by the invention]

[0005] In Patent Document 1, configuration information indicating the connection relationships that should be maintained in the infrastructure when migrating components is provided, but application setting information is not referenced. In other words, Patent Document 1 does not provide a method for dealing with the need to change application setting information due to a configuration change in the infrastructure layer (VM layer, storage layer).

[0006] Therefore, an object of the present invention is to provide a technique that can support changes to the configuration of an IT infrastructure. [Means for solving the problem]

[0007] In order to solve the above problem, one representative configuration change support device of the present invention is a configuration change support device that supports configuration changes to the IT infrastructure of one or more storage devices and one or more hosts connected to the storage devices, and is equipped with a storage device and a processing device. The storage device stores IT infrastructure configuration information that indicates the physical connections, logical connections, and placement information of the resources that make up the IT infrastructure of the IT infrastructure, and application dependency information that indicates the dependency of applications executed by the hosts on the IT infrastructure. The processing device acquires the configuration change information of the IT infrastructure, and based on the configuration change information, IT infrastructure configuration information, and application dependency information, creates additional configuration change information that minimizes the impact on applications when a configuration change based on the configuration change information is implemented, creates application impact elements that indicate the impact on applications when a configuration change based on the configuration change information and the additional configuration change information is implemented, and notifies the configuration change implementer of the application impact elements and the additional configuration change information. [Effects of the Invention]

[0008] According to the present invention, it is possible to support changes to the configuration of an IT infrastructure.

[0009] Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of a schematic configuration of a system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of hardware and functions of a configuration integration management server. [Figure 3] FIG. 10 illustrates an example of a physical connection information management table. [Figure 4]FIG. 10 is a diagram illustrating an example of a volume connection information management table. [Figure 5] FIG. 10 illustrates an example of a VM placement information management table. [Figure 6] FIG. 10 illustrates an example of an application configuration information management table. [Figure 7] FIG. 10 is a diagram illustrating an example of a conversion table for converting application setting files into configuration-dependent information. [Figure 8] FIG. 10 illustrates an example of a configuration dependency information management table for an application setting file. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of a configuration change process. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of an application setting change process. [Figure 11] 10 is a flowchart showing an example of a configuration change impact calculation and additional configuration creation process. [Figure 12] 10 is a flowchart illustrating an example of an application setting change recording process. [Figure 13] FIG. 10 is a diagram illustrating an example of an alert screen for a configuration change implementer. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment will be described with reference to the drawings.

[0012] In the following, when necessary for convenience, the description will be divided into multiple sections or embodiments, but unless otherwise specified, they are not unrelated to each other, and one is related to the other as a partial or complete modification, detail, supplementary explanation, etc. Furthermore, in the following, when the number of elements, etc. (including the number, numerical value, amount, range, etc.) is mentioned, it is not limited to that specific number, and may be more or less than the specific number, unless otherwise specified or when it is clearly limited in principle to a specific number, etc.

[0013] The system or device in this specification may be a physical computer system (one or more physical computers), or a system built on a group of computing resources (multiple computing resources) such as a cloud platform. The computer system or group of computing resources may include one or more interface devices (including, for example, a communication device and an input / output device), one or more storage devices (including, for example, a memory (main memory) and an auxiliary storage device), and one or more processing devices.

[0014] When a function is realized by executing a program on a computing device, the defined processing is performed using a storage device and / or an interface device, etc., as appropriate, and therefore the function may be considered to be at least a part of one or more computing devices. Processing described using a function as the subject may also be processing performed by a system including one or more computing devices.

[0015] The program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable storage medium (e.g., a computer-readable non-transitory storage medium). The description of each function is an example, and multiple functions may be combined into one function or one function may be divided into multiple functions.

[0016] In one embodiment of this specification, application impact factors and proposed additional configuration changes are created for a configuration change implemented by an IT infrastructure administrator, and are presented to the user. The application impact factors indicate zero or more application names, the operating status of the application after the configuration change, and setting information that needs to be changed before and after the configuration change for the application. The proposed additional configuration changes indicate changes to the placement and settings of zero or more elements that make up the IT infrastructure.

[0017] FIG. 1 is a diagram showing an example of a schematic configuration of a system according to this embodiment.

[0018] The system includes one or more hosts 50 and one or more storage devices 60 , some of which are connected via one or more storage area networks (SANs) 70 .

[0019] The host 50 has one or more virtual machines (VMs) 51 and one or more applications 52 running on the VMs. These applications 52 include applications running on a container orchestration tool or the like running on the VMs 51.

[0020] The storage device 60 has a resource pool 63 and a logical volume 62 extracted from the resource pool 63. Access from the host 50 to the logical volume 62 is performed using a method such as FC / iSCSI, and the port 61 that allows access and the access source are written as settings within the storage device.

[0021] The storage administrator 12 uses the storage administrator terminal 11 to access storage management software running on the storage management server 10 and operates the storage device 60 (monitoring, configuration changes, etc.).

[0022] The VM administrator 22 uses the VM administrator terminal 21 to access the VM management software running on the VM management server 20 and operates (monitors, changes configuration, etc.) the hypervisor on the host 50 and the VMs 51 running on the hypervisor.

[0023] The application administrator 32 uses the application administrator terminal 31 to access application management software running on the application management server 30 and operates (monitors, changes settings, etc.) the application 52. The application management server may be one of the VMs 51.

[0024] The configuration integration management server 40 (configuration change support device) communicates with the storage management server 10, VM management server 20, and application management server 30 to obtain IT infrastructure configuration information and application setting information, obtain configuration change information, issue alerts, request additional configuration changes, and request setting changes.

[0025] FIG. 2 is a diagram illustrating an example of the hardware and functions of the configuration integration management server 40. As shown in FIG.

[0026] The configuration integration management server 40 includes a processing device 41 , a memory 42 , an auxiliary storage device 43 , and a communication device 44 .

[0027] The processing device 41 includes processors such as a CPU (Central Processing Unit), a DSP (Digital Signal Processor), a GPU (Graphics Processing Unit), and an FPGA (Field-Programmable Gate Array), and implements the IT infrastructure construction plan creation method according to this embodiment by executing various programs stored in the auxiliary storage device 43.

[0028] The memory 42 is called a main storage device and is composed of a ROM (Read Only Memory), a RAM (Random Access Memory), etc. The auxiliary storage device 43 is an auxiliary storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The communication device 44 is composed of a known network interface such as a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, or a serial communication module.

[0029] These components of the configuration integrated management server 40 can communicate with each other via an internal bus. The configuration integrated management server 40 may further include input devices such as a keyboard, mouse, or touch panel that accept input operations from the user, and output devices such as a display that shows processing results to the user.

[0030] The auxiliary storage device 43 of the configuration integrated management server 40 stores a configuration change impact calculation / additional configuration creation program 45, a configuration change recording program 46, and an application setting change recording program 47. In addition to the programs shown here, other programs are also stored in the auxiliary storage device 43.

[0031] The auxiliary storage device 43 also stores a physical connection information management table 100, a volume connection information management table 200, a VM placement information management table 300, an application configuration information management table 400, an application setting file to configuration dependent information conversion table 500, and an application setting file configuration dependent information management table 600. These tables are referenced and updated by each program executed by the processing device 41.

[0032] Next, we will explain the details of each table stored in the auxiliary storage device 43 of the configuration integration management server 40. In each table described below, some items may be omitted and other items may be added.

[0033] FIG. 3 is a diagram showing an example of the physical connection information management table 100. As shown in FIG.

[0034] The physical connection information management table 100 consists of one record consisting of a storage device ID 101 that identifies a storage device 60, a port ID 102 that identifies a port 61 of the storage device 60, and a host ID 103 that identifies a host 50 connected to the storage device 60.

[0035] Each record indicates that a host 50 identified by a host ID 103 is connected to a storage device 60 identified by a storage device ID 101 via a port 61 identified by a port ID 102 .

[0036] This information is set by the storage administrator 12 and the VM administrator 22 .

[0037] FIG. 4 is a diagram showing an example of the volume connection information management table 200. As shown in FIG.

[0038] Each record in the volume connection information management table 200 is composed of a storage device ID 201 that identifies a storage device 60, a pool ID 202 that identifies a resource pool 63 that the storage device 60 has, a volume ID 203 that identifies a logical volume 62 extracted from the resource pool 63, a port ID 204 that identifies a port 61 that the storage device 60 has, and a volume connection destination VM ID 205 that identifies a virtual machine (VM) 51 to which the logical volume 62 is connected.

[0039] Each record indicates that a VM 51 with a volume destination VM ID 205 is connected to a logical volume 62 identified by a volume ID 203, which is extracted from a resource pool 63 identified by a pool ID 202 on a storage device 60 identified by a storage device ID 201, via a port 61 identified by a port ID 204.

[0040] These pieces of information are set in S7 of the configuration change recording process in FIG. 9, which will be described later.

[0041] FIG. 5 is a diagram illustrating an example of the VM placement information management table 300. As shown in FIG.

[0042] In the VM placement information management table 300, one record is configured by a VM ID 301 that identifies a virtual machine (VM) 51, and a host ID 302 that identifies the host 50 on which the VM 51 is placed.

[0043] These pieces of information are set in S7 of the configuration change recording process in FIG. 9, which will be described later.

[0044] FIG. 6 is a diagram illustrating an example of the application configuration information management table 400. As shown in FIG.

[0045] In the application configuration information management table 400, one record is configured by an application ID 401 that identifies an application 52 running on a virtual machine (VM) 51, and a VM ID 402 that identifies the VM 51 on which the application 52 is deployed. These pieces of information are set in S7 of the configuration change recording process in FIG. 9, which will be described later.

[0046] FIG. 7 is a diagram showing an example of a conversion table 500 for converting application setting files into configuration-dependent information.

[0047] A conversion table 500 for converting application setting files into configuration dependency information has one record consisting of an application ID 501 that identifies an application 52, a setting file name 502 of the setting file for the application 52, a target parameter path 503 that indicates the parameter path of the component referenced by the setting file, a configuration dependency 504 that indicates which component of the IT infrastructure the value of the parameter path refers to accessing, and an impact 505 that indicates the impact on the application 52 due to the inability to maintain the access.

[0048] These records are common regardless of the specific environment, and may be provided by the distributor of the application 52, the distributor of the application management software, the distributor of the integrated configuration management software, etc. Alternatively, they may be set by the application administrator 32.

[0049] FIG. 8 is a diagram showing an example of a configuration-dependent information management table 600 for application setting files.

[0050] The configuration dependency information management table 600 for the application setting file comprises one record consisting of an application ID 601 that identifies the application 52, a VM ID 602 ​​that identifies the VM 51 on which the application 52 is deployed, a setting file name 603 of the setting file for the application 52, a target parameter path 604 that indicates the parameter path of the component referenced by the setting file, a target storage device ID 605 that identifies the storage device that needs to be accessed by the application 52, a target port ID 606 that identifies the port 61 of the storage device 60 that needs to be accessed by the application 52, a target volume ID 607 that identifies the logical volume 62 of the storage device 60 that needs to be accessed by the application 52, a target pool ID 608 that identifies the resource pool 63 of the storage device 60 that needs to be accessed by the application 52, and an impact 609 that indicates the impact on the application due to the inability to maintain the access.

[0051] Null may be entered for the target storage device ID 605, target port ID 606, target volume ID 607, and target pool ID 608, but it is guaranteed that one or more columns are not null.

[0052] This information is set in S9 of the application setting change recording process in FIG. 10, which will be described later.

[0053] Of the information held by the above-mentioned configuration integrated management server 40, the information on the physical connection information management table 100, the volume connection information management table 200, the VM placement information management table 300, and the application configuration information management table 400, which relate to the configuration information of the IT infrastructure, will be referred to as "IT infrastructure configuration information," and the information on the application setting file configuration dependency information management table 600, which relates to the dependency information of the application 52 on the IT infrastructure, will be referred to as "application dependency information." This information may be held in a format different from the format described in this embodiment, such as a different table configuration, and equivalent information may be held in a format different from that described in this embodiment.

[0054] Next, the processing executed by the configuration integration management server 40 will be described.

[0055] FIG. 9 is a sequence diagram illustrating an example of a configuration change process.

[0056] Here, we will use a configuration change in the VM layer as an example, but when making a configuration change in the storage layer, the VM administrator terminal 21 and VM management server 20 can be read as the storage administrator terminal 11 and storage management server 10, respectively, and the storage management server 10 can be read as the VM management server 20.

[0057] Furthermore, when changing settings at the application layer, the VM administrator terminal 21 and the VM management server 20 should be read as the application administrator terminal 31 and the application management server 30, respectively.

[0058] First, the VM administrator terminal 21 passes configuration change information to the VM management server 20 to request a configuration change for the VM 51. Here, the configuration change information is information equivalent to updating one or more records in the volume connection information management table 200, the VM placement information management table 300, or the application configuration information management table 400.

[0059] The VM management server 20 transfers the received configuration change request to the configuration integration management server 40, and requests a configuration change impact determination.

[0060] The configuration integrated management server 40 receives the configuration change information and executes the configuration change impact calculation and additional configuration creation process S1. Details of the configuration change impact calculation and additional configuration creation process S1 will be described later, so here only the purpose of the process and inputs and outputs will be explained.

[0061] The configuration change impact calculation and additional configuration creation process creates additional configuration change information for the received configuration change information in a way that maintains as much as possible the dependency information in the configuration dependency information management table 600 of the application setting file, and calculates the impact on the application side, if any.

[0062] The configuration change impact calculation / additional configuration creation process S1 outputs additional configuration change information and application impact factors. Like the configuration change information, the additional configuration change information is information equivalent to updating one or more records in the volume connection information management table 200, VM placement information management table 300, or application configuration information management table 400, and indicates configuration change information that should be added to the configuration change information.

[0063] The application impact factors indicate, for each application for which the constraints of the configuration dependency information management table 600 of the application setting file can no longer be maintained due to the configuration change, the impact on the application, such as stopping the application or requiring a change to the setting file, and, if a change to the setting file is required, the revised setting file.

[0064] Next, it is determined whether there are any application-affecting factors or additional configuration change information (S2), and if there are neither application-affecting factors nor additional configuration change information (NO in S2), the process proceeds to S6, where the configuration integration management server 40 requests a configuration change to the VM management server 20 and executes the configuration change processing.

[0065] On the other hand, if there is at least one of the application-affecting factors and additional configuration change information (YES in S2), the configuration integration management server 40 notifies the VM administrator terminal 21 of the application-affecting factors and additional configuration change information.

[0066] The VM administrator terminal 21 displays this information and performs the processes of S3, S4, and S5. This display method may be a GUI (Graphical User Interface) such as a pop-up on the management software as will be described later with reference to FIG. 13, or may be an email, a push notification, or the like.

[0067] By receiving an input from the VM administrator 22 on the VM administrator terminal 21, it is determined whether to continue the configuration change (S3), and if the configuration change is not to be continued (NO in S3), the process ends.

[0068] On the other hand, if the configuration change is to be continued (YES in S3), the process proceeds to S4 and subsequent steps.

[0069] Next, it is determined whether there are any application-affecting factors notified by the configuration integration management server 40 (S4). If there are any application-affecting factors notified by the configuration integration management server 40 (YES in S4), the process proceeds to S5. On the other hand, if there are no application-affecting factors notified from the configuration integration management server 40 (NO in S4), the process of S5 is skipped and the subsequent processes are carried out.

[0070] Next, a response request is made to the application administrator 32 (S5). This can take the form of a manual response such as communication between administrators, or an automatic update of a setting file. The sequence for changing the application configuration will be described later.

[0071] Next, the VM administrator terminal 21 issues a configuration change continuation request to the configuration integration management server 40 .

[0072] Next, the configuration integration management server 40 implements configuration changes corresponding to the information described in the configuration change information and additional configuration change information. The configuration integration management server 40 passes the configuration change information and additional configuration change information to the VM management server 20 and the storage management server 10, and requests them to make configuration changes.

[0073] The VM management server 20 and the storage management server 10 respectively implement configuration changes corresponding to the configuration change information and the additional configuration change information (S6).

[0074] These configuration changes are achieved by the VM management software on the VM management server 20 and the storage management software on the storage management server 10, and the procedure is not important.

[0075] Thereafter, the VM management server 20 and the storage management server 10 issue a configuration change recording request to the configuration integration management server 40. The configuration integration management server 40 executes a configuration change recording process to update the volume connection information management table 200, the VM placement information management table 300, and the application configuration information management table 400 based on the configuration change information and the additional configuration change information (S7). A program corresponding to this process is stored in a configuration change recording program 46 stored in the auxiliary storage device 43 of the configuration integration management server 40.

[0076] As a result, when the VM administrator 22 makes a configuration change, the setting information of the application 52 that references the infrastructure configuration is taken into consideration, and the additional configuration changes required to minimize the response on the application 52 side, and if response on the application 52 side is necessary, the response measures are calculated, and this information is presented to the infrastructure administrator along with an alert.

[0077] An example of a configuration change made by the VM administrator 22 is when the virtual machine 51 is migrated between physical servers. In this case, an event may occur in which the storage resource of the configuration information included in the setting information of the application 52 on the virtual machine 51 cannot be accessed from the migration destination physical server. This is envisioned as a use case in which the VM administrator 22 migrates the virtual machine 51 on the host 50 to another host 50 for maintenance or troubleshooting of the host 50 without understanding the configuration of the storage device 60.

[0078] An example of a change in the settings of an application 52 is when a virtual machine 51 is created and the setting information of an existing application 52 is applied. An event may occur in which the new virtual machine 51 cannot access a storage resource included in the setting information of the existing application 52. This is likely to occur in a use case in which a virtual machine 51 is created when scaling out the application 52 and the setting of the existing application 52 is used as is.

[0079] FIG. 10 is a sequence diagram illustrating an example of the application setting change process.

[0080] The application administrator terminal 31 issues an application setting change request to the application management server 30. Here, the application setting change information indicates the target application ID, the setting file name, and the difference between the setting files.

[0081] The application management server 30 executes an application setting change process S8 for changing the setting file of the application, and then passes the application setting change information to the configuration integration management server, and executes a request to record the application setting change.

[0082] The configuration integrated management server 40 receives application setting change information as input and executes application setting change recording process S9. The application setting change recording process S9 is a process for updating the application setting file configuration dependency information management table 600 by referencing the application setting change information and the application setting file configuration dependency information conversion table 500. Details will be described later.

[0083] In this way, recording and tracking of the setting information of an application that references the infrastructure configuration is achieved.

[0084] FIG. 11 is a flowchart showing an example of the configuration change effect calculation and additional configuration creation process S1 of FIG.

[0085] A program corresponding to this process is stored in the configuration change impact calculation / additional configuration creation program 45 stored in the auxiliary storage device 43 of the configuration integration management server 40. This process is started by a configuration change impact judgment request.

[0086] In the configuration change impact calculation and additional configuration creation process S1, the configuration integrated management server 40 first receives configuration change information as input (S101).

[0087] As described above, the configuration change information is information equivalent to updating one or more records in any of the volume connection information management table 200, the VM placement information management table 300, and the application configuration information management table 400.

[0088] Next, the configuration integrated management server 40 acquires records (application-dependent information) related to the configuration change that have a common portion of any of the configuration change information for the VM ID 602, the target storage device ID 605, the target port ID 606, the target volume ID 607, and the target pool ID 608 from among all the records in the configuration-dependent information management table 600 of the application setting file, and repeats the series of processes from S103 to S110 for that application-dependent information. For simplicity of explanation, when referencing the table in the following processes, if there is information corresponding to an update of a record that corresponds to the configuration change information and the additional configuration change information at that time, that information is treated as having priority.

[0089] Next, the configuration integration management server 40 determines whether, based on the configuration change information and the current additional configuration change information, the application 52 can still physically access the storage device 60 with the target storage device ID 605 of the record (application-dependent information) using the access method set in the application 52 after the configuration change (S103). As a specific example, the configuration integration management server 40 refers to the VM placement information management table 300 for the VM ID 602 ​​of the record, acquires the host ID 302 where the VM 51 matching the VM ID 602 ​​is placed, and refers to the physical connection information management table 100 to determine whether the host ID 101 matching the target storage device ID 605 of the record is connected to the host ID 103 matching the host ID 302.

[0090] If the application 52 cannot physically access the storage device 60 with the target storage device ID 605 using the access method set in the application 52 after the configuration change (NO in S103), the process proceeds to S104.

[0091] On the other hand, if the application 52 can still physically access the storage device 60 with the target storage device ID 605 using the access method set in the application 52 after the configuration change (YES in S103), the process proceeds to S108.

[0092] From here, a series of processes from S104 to S107 will be explained.

[0093] Next, the configuration integration management server 40 determines whether there is another storage device 60 that can be accessed after the configuration change (S104). As a specific example, the configuration integration management server 40 refers to the VM placement information management table 300 for the VM 51 of the VM ID 602 ​​of the record, acquires the host ID 302 of the host 50 on which the VM 51 is placed, and refers to the physical connection information management table 100 to determine whether any storage device 60 is connected to the host 50.

[0094] If there is no other storage device 60 that can be accessed after the configuration change (NO in S104), it is determined that additional configuration changes or application setting changes are not possible, and the process proceeds to S105.

[0095] Next, the configuration integration management server 40 adds the combination of the application ID 601 and the impact 609 of the record to the application impact elements (S105), and proceeds to S110.

[0096] On the other hand, if there is another storage device 60 that can be accessed after the configuration change (YES in S104), it is assumed that the application can continue to run by copying data and changing the application settings, and the process proceeds to S106.

[0097] Next, the configuration integration management server 40 adds information corresponding to copying data to the other storage device 60 discovered in S104 to the additional configuration change information (S106).

[0098] As a specific example, for the logical volume 62 of the target volume ID 607 of the record, the volume connection information management table 200 is referenced to obtain the storage device ID 201, pool ID 202, and port ID 204 of the logical volume 62, and these are changed to the storage device ID of the other storage device 60 that has been discovered, the pool ID of an appropriate resource pool 63 on the other storage device 60, and the port ID of the port 61. Then, the process proceeds to S107.

[0099] Next, the combination of the setting file name 603 of the application ID 601 of the record and the difference of the setting file after the change is added to the application influence elements (S107). The difference of the setting file after the change is created by replacing the target storage device ID 605, target port ID 606, target volume ID 607, and target pool ID 608 of the target parameter path 604 of the record with appropriate ones on the discovered storage device 60. Then, proceed to S110.

[0100] Next, a series of processes from S108 to S109 will be explained.

[0101] First, it is determined whether the port 61 of the target port ID 606 and the logical volume 62 of the target volume ID 607 of the record in question are accessible after the configuration change information and the current additional configuration change information (S108).

[0102] As a specific example, the volume connection information management table 200 is referenced to obtain a list of port IDs 204 used to connect to the logical volume 62 of the target volume ID 607 of the record for the VM ID 602 ​​of the record. The VM placement information management table 300 is referenced to obtain the host ID 302 of the host 50 on which the VM 51 of the VM ID 602 ​​of the record is placed, and the physical connection information management table 100 is referenced to determine whether the port ID 102 used to connect to the logical volume 62 and the port 61 of the target port ID 606 are connected to the host 50.

[0103] If the port 61 of the target port ID 606 and the logical volume 62 of the target volume ID 607 of the record are not accessible after the configuration change (NO in S108), it is assumed that changing the access settings to the logical volume 62 will not affect the application 52, and the process proceeds to S109.

[0104] Next, information corresponding to the volume access setting change is added to the additional configuration change information (S109). As a specific example, in the volume connection information management table 200, the target volume ID 607 of the record, the volume ID 203 that matches the VM ID 602, and the port ID 204 of the record corresponding to the volume connection destination VM ID 205 are changed to the port ID of the storage device 60 in which the logical volume 62 that can be accessed after the configuration change is located.

[0105] On the other hand, if the port 61 of the target port ID 606 and the logical volume 62 of the target volume ID 607 of the record are still accessible after the configuration change (YES in S108), the constraints of the record are deemed to be satisfied and nothing is added, and the process proceeds to S110.

[0106] Subsequently, if there are any unprocessed records among the records (application-dependent information) related to the configuration change acquired in S102, the process returns to S102 (S110).

[0107] Next, the application-affecting factors and additional configuration change information added by the repeated processing from S102 to S110 are output (S111), and the configuration change effect calculation and additional configuration creation processing S1 is terminated.

[0108] As a result of the above, the additional configuration change information required to minimize the response on the application 52 side for the configuration change information given as input and the impact factors on the application 52 side when the additional configuration change is implemented are calculated.

[0109] FIG. 12 is a flowchart showing an example of the application setting change recording process S9 of FIG.

[0110] A program corresponding to this process is stored in the application setting change recording program 47 stored in the auxiliary storage device 43 of the configuration integration management server 40. This process is started by a request to record application setting changes.

[0111] The application setting change recording process S9 first receives as input the target application ID of application setting change information, the setting file name, and the difference of the changed setting file (S901).

[0112] Thereafter, the process of S903 is repeated for each parameter path of the difference in the changed configuration file (S902).

[0113] Next, the configuration dependency information management table 600 for the application setting file is updated based on the dependency information on the IT infrastructure by the parameter path of the setting file (S903).

[0114] As a specific example, the conversion table 500 for application setting file configuration-dependent information is referenced, and if there is no record in which information corresponding to the application ID, the setting file name, and the parameter path is written in the application ID 501, the setting file name 502, and the target parameter path 503, the application setting file configuration-dependent information management table 600 is not updated.

[0115] If there is a record in which information corresponding to the application ID, the setting file name, and the parameter path is written in the application ID 501, the setting file name 502, and the target parameter path 503, the application configuration information management table 400 is referenced to obtain the VM ID 402 of the VM 51 on which the application 52 of the application ID is deployed, and the target storage device ID 605, the target port ID 606, the target volume ID 607, and the target pool ID 608 are obtained from the values ​​set in the configuration dependency destination 504 and the target parameter path 503, and a new record is added to the configuration dependency information management table 600 for the application setting file (or the record is deleted if the difference in the setting file indicates deletion).

[0116] Subsequently, if there is an unprocessed parameter path in the parameter path of the difference of the changed setting file, the process returns to S902 (S904), and if there is no unprocessed parameter path, the application setting change recording process S9 ends.

[0117] FIG. 13 is a diagram showing an example of an alert screen 1000 for a configuration change implementer that is displayed on the terminal (VM administrator terminal 21 or storage administrator terminal 11) of the configuration change implementer (VM administrator 22 or storage administrator 12).

[0118] The alert screen 1000 for the configuration change implementer includes an additional configuration change display field 1010 that displays additional configuration change information created in the configuration change impact calculation / additional configuration creation process S1, an application impact element display field 1020 that displays application impact elements created in the configuration change impact calculation / additional configuration creation process S1, and a confirmation field 1030 where the user can input whether or not to implement the displayed additional configuration changes and application setting changes and continue with the configuration change.

[0119] This allows the person who implements the configuration change (the VM administrator 22 or the storage administrator 12) to check the impact of the configuration change on the application and the additional configuration changes that are required to minimize the impact on the application.

[0120] Note that some of the information shown in FIG. 13 may be omitted, and other information not shown in FIG. 13 may be presented.

[0121] The content of the additional configuration change information is displayed in the additional configuration change display field 1010. The displayed content may be in a table format as shown in the figure, or may be output as a file, etc.

[0122] The contents of the application-affecting factors are displayed in the application-affecting factor display field 1020. The displayed contents may be in a table format as shown in the figure, or may be output as a file, etc. Furthermore, changes to the configuration file may be output as a file as shown in the figure, or may be entered as text in the field.

[0123] A confirmation field 1030 accepts a user input as to whether to continue the configuration change. This input corresponds to the process S3 in FIG. 9 for confirming whether to continue the configuration change.

[0124] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and are not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0125] Furthermore, the above-mentioned components, functions, processing units, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. Furthermore, the above-mentioned components, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the programs, tables, and files that realize each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card or SD card.

[0126] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0127] 1 : Host 10: Storage management server 11: Storage administrator terminal 12: Storage Administrator 20: VM management server 21: VM administrator terminal 22 :VM administrator 30: Application management server 31: Application administrator terminal 32: App Administrator 40: Integrated configuration management server 41: Processing equipment 42: Memory 43: Auxiliary storage device 44: Communication equipment 45: Additional configuration creation program 46: Configuration change recording program 47: App setting change recording program 50: Host 51: Virtual Machine 52: Application 60: Storage device 61: Port 62: Logical volume 63: Resource pool

Claims

1. A configuration change support device that supports a configuration change of an IT infrastructure of one or more storage devices and one or more hosts connected to the storage devices, a storage device and a processing device, The storage device includes: IT infrastructure configuration information indicating physical connections, logical connections, and allocation information of resources constituting the IT infrastructure; application dependency information indicating dependency information of an application executed by the host on the IT infrastructure; The processing device includes: Acquire configuration change information of the IT infrastructure; creating additional configuration change information based on the configuration change information, the IT infrastructure configuration information, and the application dependency information, which minimizes the impact on the application when a configuration change of the configuration change information is implemented; creating an application impact element indicating an impact on the application when the configuration change information and the additional configuration change information are implemented; a configuration change support device that notifies a configuration change implementer of the application-affecting factors and the additional configuration change information;

2. 2. The configuration change support device according to claim 1, The storage device includes: a conversion table for converting the setting file of the application into configuration-dependent information; The processing device includes: a configuration change support device that updates the application-dependent information based on the conversion table when a change is made to the setting file of the application;

3. 3. The configuration change support device according to claim 2, The processing device includes: a configuration change support device that, when a configuration change is made to the IT infrastructure, records the configuration change in the IT infrastructure configuration information;

4. 3. The configuration change support device according to claim 2, The processing device includes: If a change in the configuration of the IT infrastructure makes it impossible to physically connect to the storage device to which the virtual machine on which the application runs and the host are connected, creating additional configuration change information for performing data copying to another storage device connectable to the application when a configuration change is made to the IT infrastructure; A configuration change support device creates an application influence element indicating a difference in the setting file of the application when changing the application so that it accesses the other storage device.

5. 3. The configuration change support device according to claim 2, The processing device includes: When a change in the configuration of the IT infrastructure is made, if the application is unable to access the storage device that it has been accessing by the access method set in the application, A configuration change support device that creates additional configuration change information for changing the settings of the storage device so as to permit access using the access method.

6. 3. The configuration change support device according to claim 2, The processing device includes: When a change in the configuration of the IT infrastructure is made, it becomes impossible to physically connect to the storage device to which the virtual machine on which the application runs and the host are connected, When the configuration of the IT infrastructure is changed and there is no other storage device to which the application can be connected, A configuration change support device that creates an application impact element that indicates the impact on the operation of the application.

7. 3. The configuration change support device according to claim 2, The processing device includes: notifying the configuration change implementer of the application-affected factors and the additional configuration change information, and then receiving an input from the configuration change implementer as to whether or not to continue the configuration change of the IT infrastructure; When a selection to continue the configuration change is input, the configuration change support device requests a configuration change of the configuration change information and the additional configuration change information from a management server of the IT infrastructure.

8. 1. A configuration change support method for a configuration change support device that supports a configuration change of an IT infrastructure of one or more storage devices and one or more hosts connected to the storage devices, comprising: the configuration change support device includes a storage device and a processing device; The storage device includes: IT infrastructure configuration information indicating physical connections, logical connections, and allocation information of resources constituting the IT infrastructure; application dependency information indicating dependency information of an application executed by the host on the IT infrastructure; The processing device includes: Acquire configuration change information of the IT infrastructure; creating additional configuration change information based on the configuration change information, the IT infrastructure configuration information, and the application dependency information, which minimizes the impact on the application when a configuration change of the configuration change information is implemented; creating an application impact element indicating an impact on the application when the configuration change information and the additional configuration change information are implemented; A configuration change support method for notifying a configuration change implementer of the application-affecting factors and the additional configuration change information.

9. 9. The configuration change support method according to claim 8, The storage device includes: a conversion table for converting the setting file of the application into configuration-dependent information; The processing device includes: A configuration change support method for updating the application-dependent information based on the conversion table when a change is made to the setting file of the application.

10. 10. The configuration change support method according to claim 9, The processing device includes: A configuration change support method for recording a configuration change in the IT infrastructure configuration information when the configuration change is implemented in the IT infrastructure.

11. 10. The configuration change support method according to claim 9, The processing device includes: If a change in the configuration of the IT infrastructure makes it impossible to physically connect to the storage device to which the virtual machine on which the application runs and the host are connected, creating additional configuration change information for performing data copying to another storage device connectable to the application when a configuration change is made to the IT infrastructure; A configuration change support method for creating an application influence element that indicates a difference in the setting file of the application when changing the application so that it accesses the other storage device.

12. 10. The configuration change support method according to claim 9, The processing device includes: When a change in the configuration of the IT infrastructure is made, if the application is unable to access the storage device that it has been accessing by the access method set in the application, A configuration change support method for creating additional configuration change information for changing the settings of the storage device so as to permit access using the access method.

13. 10. The configuration change support method according to claim 9, The processing device includes: When a change in the configuration of the IT infrastructure is made, it becomes impossible to physically connect to the storage device to which the virtual machine on which the application runs and the host are connected, When the configuration of the IT infrastructure is changed and there is no other storage device to which the application can be connected, A configuration change support method for creating an application impact element that indicates the impact on the operation of the application.

14. 10. The configuration change support method according to claim 9, The processing device includes: notifying the configuration change implementer of the application-affected factors and the additional configuration change information, and then receiving an input from the configuration change implementer as to whether or not to continue the configuration change of the IT infrastructure; When a selection to continue the configuration change is input, a configuration change request is made to a management server of the IT infrastructure to make the configuration change of the configuration change information and the additional configuration change information.

Images