JP2021140372A - Configuration management device, configuration management method, and configuration management program - Google Patents

Abstract

To provide a configuration management device for automatically reflecting a configuration of a construction subject system changed by a user through operating an apparatus installed in the construction subject system, to construction information of the construction subject system.SOLUTION: A configuration management device 100 comprises a construction information management section 110, a construction processing section 120, a setting change detection section 140, a change content extraction section 150, and a change content reflection section 160. The construction information management section receives construction information 111 and manages the construction information. The construction processing section uses the construction information for constructing a construction subject system 90. The setting change detection section detects presence or absence of a setting change for an apparatus installed in the construction subject system equipped with apparatus. The change content extraction section extracts a content of the setting change as a change content when the setting change presents. The change content reflection section reflects the change content into the construction information to be used for constructing the construction subject system.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to a configuration management device, a configuration management method, and a configuration management program.

A method of automatically constructing a system may be used by using construction information. The construction information is information used for constructing a system such as an IT (Information Technology) system.

Patent Document 1 discloses a technique for automatically constructing a system based on construction information.

Japanese Unexamined Patent Publication No. 2019-12185

According to the technique of Patent Document 1, when the configuration of the construction target system is changed by the user operating the device provided in the construction target system without changing the construction information, the configuration of the construction target system and the configuration of the construction target system , There is a problem that inconsistency occurs with the construction information.

This disclosure describes the configuration of the construction target system and the construction information when the configuration of the construction target system is changed by the user operating the device provided in the construction target system without changing the construction information. The purpose is to prevent inconsistencies between them.

The configuration management device according to the present disclosure is
A setting change detection unit that detects the presence or absence of a setting change of the device provided in the system to be built equipped with the device, and a setting change detection unit.
When there is a setting change, a change content extraction unit that extracts the content of the setting change as a change content, and a change content extraction unit.
The construction information used for constructing the construction target system is provided with a change content reflection unit that reflects the change content.

The configuration of the construction target system is changed by the equipment included in the construction target system executing the setting change.
The setting change detection unit includes reference configuration information indicating the configuration of the construction target system before the configuration of the construction target system is changed by the device executing the setting change, and the device changes the setting. When executed, the confirmation configuration information indicating the configuration of the construction target system whose configuration has been changed is generated, and the setting change is detected by using the reference configuration information and the confirmation configuration information. ..

The setting change detection unit generates a setting file table that summarizes the setting files of the construction target system using the construction information, and the reference configuration information and the confirmation configuration information are combined with the setting file table. Is generated using.

The configuration management device according to the present disclosure includes an operation history recording unit that records an operation history indicating a history of operation of the device.
The change content extraction unit extracts the change content using the operation history.

The setting change is executed by changing a setting file containing information indicating the configuration of the system to be built.
The operation history includes device operation information indicating an operation executed when the device included in the construction target system is operated, and time information corresponding to the device operation information.
The setting change detection unit manages information including the time when the setting file is changed as setting file information.
The change content extraction unit identifies the operation executed for the device in the time zone when the setting file is changed by using the setting file information and the operation history, and identifies the specified operation. Extract as the change content.

The change content extraction unit has candidate operation information including information on operations that may change the settings of the device included in the system to be constructed, and compares the device operation information with the candidate operation information. The operation that caused the setting change is specified, and the information corresponding to the specified operation is extracted as the change content.

The change content reflecting unit generates a file corresponding to the specified operation, and reflects the generated file in the construction information.

The configuration management device according to the present disclosure is
The construction processing unit that constructs the construction target system as a test construction target system by using the construction information that reflects the change contents as the change construction information and using the change construction information.
Test configuration information indicating the configuration of the test construction target system is generated, a difference between the confirmation configuration information and the test configuration information is detected as a configuration difference, and the configuration difference is the modified construction information. It is provided with a configuration difference detection unit that reflects the information in.

The configuration management method according to this disclosure is
The setting change detection unit detects whether or not the setting of the device provided in the system to be constructed including the device has been changed.
When the change content extraction unit has the setting change, the change content extraction unit extracts the content of the setting change as the change content.
The changed contents are reflected in the construction information used for constructing the construction target system.

The configuration management program related to this disclosure can be applied to a computer.
Detects the presence or absence of a change in the settings of the device provided in the system to be built equipped with the device.
When there is a setting change, the content of the setting change is extracted as the change content.
The changed contents are reflected in the construction information used for constructing the construction target system.

The configuration management device 100 according to the present disclosure includes a setting change detection unit 140, a change content extraction unit 150, and a change content reflection unit 160. The setting change detection unit 140 detects whether or not the setting of the device included in the construction target system 90 has been changed. The change content extraction unit 150 extracts the content of the setting change as the change content when there is a setting change. The change content reflecting unit 160 is construction information 111 including information indicating the configuration of the construction target system 90, and reflects the change content in the construction information 111 used for constructing the construction target system 90.
Therefore, according to the present disclosure, when the user does not change the construction information 111 and the configuration of the construction target system 90 is changed by the user operating the device included in the construction target system 90, the construction target system 90 It is possible to prevent inconsistency between the configuration of the above and the construction information 111.

A configuration example of the configuration management device 100 according to the first embodiment. A hardware configuration example of the configuration management device 100 according to the first embodiment. The flowchart which shows the operation of the configuration management apparatus 100 which concerns on Embodiment 1. FIG. A hardware configuration example of the configuration management device 100 according to a modification of the first embodiment. A configuration example of the configuration management device 100 according to the second embodiment. An example of the configuration file table 143 according to the second embodiment. An example of a file showing an outline of the system to be built 90. An example of a file that shows user information. An example of retrieving software package information. An example of acquiring information on the software package installed in the system to be built 90. An example of getting file information. The flowchart which shows the operation of the configuration management apparatus 100 which concerns on Embodiment 2. A configuration example of the configuration management device 100 according to the third embodiment. The figure explaining the outline of the operation of the configuration management apparatus 100 which concerns on Embodiment 3. FIG. The flowchart which shows the operation of the configuration management apparatus 100 which concerns on Embodiment 3. The figure explaining the operation of the configuration management apparatus 100 shown in the flowchart of FIG. The flowchart which shows the operation of the configuration management apparatus 100 which concerns on Embodiment 3. The figure explaining the operation of the configuration management apparatus 100 shown in the flowchart of FIG. A table that illustrates an example of direct configuration. The figure explaining the outline of the operation of the configuration management apparatus 100 which concerns on Embodiment 3. FIG. The figure explaining the operation of the change content reflecting part 160 which concerns on Embodiment 3. FIG. The figure explaining the operation of the change content reflecting part 160 which concerns on Embodiment 3. FIG. The figure explaining the operation of the change content reflecting part 160 which concerns on Embodiment 3. FIG. A configuration example of the configuration management device 100 according to the fourth embodiment. The flowchart which shows the operation of the configuration management apparatus 100 which concerns on Embodiment 4.

In the description and drawings of the embodiments, the same elements and the corresponding elements are designated by the same reference numerals. The description of the elements with the same reference numerals will be omitted or simplified as appropriate. The arrows in the figure mainly indicate the flow of data or the flow of processing.

Embodiment 1.
Hereinafter, the present embodiment will be described in detail with reference to the drawings.
*** Explanation of configuration ***

First, the configuration management device 100 will be briefly described. The configuration management device 100 manages the configuration of the system to be constructed 90. The configuration of the construction target system 90 refers to at least a part of the configuration of the construction target system 90. The configurations of the systems 90 to be constructed may be different from each other. The configuration management device 100 may manage the configurations of a plurality of systems 90 to be constructed.

The system to be constructed 90 is typically a system that can be operated based on IaC (Infrastructure as Code). The system to be constructed 90 is typically a system including a device such as a computer. Unless otherwise specified, the device refers to the device included in the system to be constructed 90. As a specific example, the system to be constructed 90 is a system composed of a server, a storage, and a network. The system to be built 90 may be an IT (Information Technology) system, a server owned by a data center, or a system including hardware and a virtualization platform. The virtualization platform is, as a specific example, VMware (registered trademark). The virtualization platform may be a virtualization environment corresponding to hardware. When referring to hardware, unless otherwise specified, it refers to the hardware included in the system to be built 90.
The construction target system 90 can construct the construction target system 90 by using the construction information 111. As a specific example, the construction information 111 is information on software installed in the device, information on a user registered in the device, or information on the directory structure of the device. The software includes an OS (Operating System), a device driver, firmware, middleware, and an application program. There is idempotency in constructing the construction target system 90 using the construction information 111.
The construction information 111 includes information instructing the construction of the construction target system 90, and is used for constructing the construction target system 90. The construction information 111 may include information indicating the configuration of the construction target system 90. As a specific example, the construction information 111 is a parameter file or an Ansible (registered trademark) Playbook. The construction information 111 may consist of a plurality of files.
The user can also change the settings of the device by operating the device. Unless otherwise specified, the user is a user of the system to be built 90. Users include system builders and system operators. The user may be a robot or a computer.
The setting change is to change the settings of at least a part of the devices included in the system to be constructed 90. The setting may be changed by changing the construction information 111 or by directly executing the setting. The direct setting is to change the device setting by operating the device included in the construction target system 90 without changing the construction information 111. When the user directly executes the setting, the setting change of the device of the system to be constructed 90 is realized. When the user operates the system to be constructed 90 and does not execute the setting change, the configuration management device 100 may determine that the user has not executed the setting change.
In the direct setting, the user does not change the construction information 111, and the user operates the equipment or the like included in the construction target system 90. In the direct setting, the user may input the file into the device included in the system 90 to be constructed. Specific examples of setting changes include executing a command to install or update software, changing the configuration file by the user, changing the user registered in the device, or changing the directory structure. It is up to the user to change.
When the device executes the setting change, the configuration of the system to be built 90 is changed. The setting change may correspond to the change of the configuration of the system to be constructed 90. When a device executes a setting change, the device typically changes the device configuration according to a user's instruction.

FIG. 1 shows a configuration example of the configuration management device 100 according to the present embodiment. As shown in this figure, the configuration management device 100 includes a construction information management unit 110, a construction processing unit 120, a setting change detection unit 140, a change content extraction unit 150, and a change content reflection unit 160.

The construction information management unit 110 receives the construction information 111 and manages the construction information 111. The construction information management unit 110 has a version control tool as a specific example. The version control tool is, as a specific example, Subversion or Git.

The construction processing unit 120 constructs the construction target system 90 using the construction information 111. The construction processing unit 120 may instruct to construct the construction target system 90.

The setting change detection unit 140 detects whether or not the setting of the device included in the construction target system 90 has been changed.

The change content extraction unit 150 extracts the content of the setting change as the change content when there is a setting change. The content of the change is the difference between the configuration of the change construction target system 90 before the configuration is changed by executing the setting change and the configuration of the construction target system 90 corresponding to the setting change. The construction target system 90 corresponding to the setting change is the construction target system 90 after the device executes the setting change. The configuration of the system to be constructed 90 is changed when the device executes a setting change.

The change content reflection unit 160 reflects the change content in the construction information 111. Reflecting the changed contents includes adding a command corresponding to the setting change to the construction information 111.

FIG. 2 shows a hardware configuration example of the configuration management device 100 according to the present embodiment. The configuration management device 100 includes a computer 10. The configuration management device 100 may be composed of a plurality of computers 10.

As shown in this figure, the computer 10 is a computer including hardware such as a processor 11, a memory 12, an auxiliary storage device 13, an input / output IF (Interface) 14, and a communication device 15. These hardware are connected to each other via a signal line 19.

The processor 11 is an IC (Integrated Circuit) that performs arithmetic processing, and controls the hardware included in the computer. As a specific example, the processor 11 is a CPU (Central Processing Unit), a DSP (Digital Signal Processor), or a GPU (Graphics Processing Unit).
The configuration management device 100 may include a plurality of processors that replace the processor 11. The plurality of processors share the role of the processor 11.

The memory 12 is typically a volatile storage device. The memory 12 is also called a main storage device or a main memory. The memory 12 is, as a specific example, a RAM (Random Access Memory). The data stored in the memory 12 is stored in the auxiliary storage device 13 as needed.

The auxiliary storage device 13 is typically a non-volatile storage device. As a specific example, the auxiliary storage device 13 is a ROM (Read Only Memory), an HDD (Hard Disk Drive), or a flash memory. The data stored in the auxiliary storage device 13 is loaded into the memory 12 as needed.

The input / output IF14 is a port to which the input device and the output device are connected. The input / output IF14 is, as a specific example, a USB (Universal Serial Bus) terminal. The input device is, as a specific example, a keyboard and a mouse. The output device is, as a specific example, a display.

The communication device 15 is a receiver and a transmitter. As a specific example, the communication device 15 is a communication chip or a NIC (Network Interface Card).

The auxiliary storage device 13 stores the configuration management program. The configuration management program is a program that allows a computer to realize the functions of each part included in the configuration management device 100. The configuration management program is loaded into the memory 12 and executed by the processor 11. Each part of the configuration management device 100 is realized by software.
The auxiliary storage device 13 stores an OS (Operating System). At least part of the OS is loaded into memory 12 and executed by processor 11. That is, the processor 11 executes the configuration management program while executing the OS.

The data used when executing the configuration management program and the data obtained by executing the configuration management program are the memory 12, the auxiliary storage device 13, the register in the processor 11, the cache memory in the processor 11, and the like. It is appropriately stored in the storage device.

When each part of the configuration management device 100 receives the data, the data may be received via the input / output IF 14 or the data may be received via the communication device 15.

The configuration management program may be recorded on a non-volatile recording medium that can be read by a computer. The non-volatile recording medium is, for example, an optical disk or a flash memory. The configuration management program may be provided as a program product.

*** Explanation of operation ***
The operation procedure of the configuration management device 100 corresponds to the configuration management method. Further, the program that realizes the operation of the configuration management device 100 corresponds to the configuration management program.

FIG. 3 is a flowchart showing an example of the operation of the configuration management device 100 according to the first embodiment. The operation of the configuration management device 100 will be described with reference to this figure.
As a specific example, the configuration management device 100 starts the processing of this flowchart when the user inputs the construction information 111 to the configuration management device 100.

(Step S101: Construction information reception process)
The construction information management unit 110 receives the construction information 111.

(Step S102: Construction information management process)
The construction information management unit 110 manages the construction information 111. As a specific example, the construction information management unit 110 updates the construction information 111 stored in the storage device, or registers the construction information 111 in the version control tool.

(Step S103: Construction process)
The construction processing unit 120 constructs the construction target system 90 using the construction information 111 managed by the construction information management unit 110. The construction processing unit 120 may transmit the construction information 111 to the construction target system 90, and may instruct the construction target system 90 to construct the construction target system 90 using the construction information 111.
The construction processing unit 120 may use only a part of the construction information 111. As a specific example, the construction processing unit 120 constructs the construction target system 90 using only the difference between the latest construction information 111 and the construction information 111 of the previous version.
The construction processing unit 120 may construct the construction target system 90 at any timing. As a specific example, the construction processing unit 120 does not have to construct the construction target system 90 every time the construction information 111 is changed.
Further, the configuration management device 100 may proceed to the next step without constructing the construction target system 90.

(Step S104: Standby process)
The setting change detection unit 140 waits until the setting is directly detected. When the direct setting is executed, the configuration management device 100 proceeds to step S105.
The setting change detection unit 140 may directly detect the setting by any method.

(Step S105: Setting change detection process)
The setting change detection unit 140 detects the presence or absence of a setting change. The setting change detection unit 140 may specify the device operated by the user or the file changed by the user.
When the setting change detection unit 140 detects the setting change, the configuration management device 100 proceeds to step S106. Otherwise, the configuration management device 100 proceeds to step S104.

(Step S106: Change content extraction process)
The change content extraction unit 150 extracts the change content. The changed content extraction unit 150 may detect the changed content by any method.
The change content extraction unit 150 may extract only the difference.

(Step S107: Change content reflection process)
The change content reflection unit 160 reflects the content extracted by the change content extraction unit 150 in the construction information 111.
The configuration management device 100 proceeds to step S102.

*** Explanation of the effect of Embodiment 1 ***
As described above, according to the present embodiment, when the setting change is executed by the user operating the device included in the construction target system 90, the change content corresponding to the setting change is automatically added to the construction information 111. Can be reflected. Therefore, according to the present embodiment, the configuration of the construction target system 90 and the construction information 111 can be automatically matched. Therefore, according to the present embodiment, it is possible to reduce the cost of operating the system to be constructed 90.
In addition, the configuration management device 100 can assist the system 90 to be constructed to realize CI (Continuous Integration) or CD (Continuous Delivery).

*** Other configurations ***
<Modification example 1>
FIG. 4 shows a hardware configuration example of the configuration management device 100 according to this modification.
As shown in this figure, the configuration management device 100 includes a processing circuit 18 instead of at least one of the processor 11, the memory 12, and the auxiliary storage device 13.
The processing circuit 18 is hardware that realizes at least a part of each part included in the configuration management device 100.
The processing circuit 18 may be dedicated hardware, or may be a processor 11 that executes a program stored in the memory 12.

When the processing circuit 18 is dedicated hardware, the processing circuit 18 is, as a specific example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (ASIC is an Application Specific Integrated Circuit), an FPGA. (Field Programmable Gate Array) or a combination thereof.
The configuration management device 100 may include a plurality of processing circuits that replace the processing circuit 18. The plurality of processing circuits share the role of the processing circuit 18.

In the configuration management device 100, some functions may be realized by dedicated hardware, and the remaining functions may be realized by software or firmware.

As a specific example, the processing circuit 18 is realized by hardware, software, firmware, or a combination thereof.
The processor 11, the memory 12, the auxiliary storage device 13, and the processing circuit 18 are collectively referred to as a "processing circuit Lee". That is, the functions of each functional component of the configuration management device 100 are realized by the processing circuit.

The same applies to the configuration management device 100 according to the other embodiment as in the present modification.

Embodiment 2.
Hereinafter, points different from the above-described embodiment will be described with reference to the drawings.

*** Explanation of configuration ***
FIG. 5 shows a configuration example of the configuration management device 100 according to the present embodiment. The basic configuration of the configuration management device 100 is the same as the configuration of the configuration management device 100 according to the first embodiment.

As shown in this figure, the setting change detection unit 140 has reference configuration information 141, confirmation configuration information 142, and setting file table 143.
The setting change detection unit 140 detects the setting change by using the reference configuration information 141 and the confirmation configuration information 142. The setting change detection unit 140 generates the reference configuration information 141 and the confirmation configuration information 142 by using the information indicating the configuration of the construction target system 90.

The reference configuration information 141 indicates the configuration of the construction target system 90 before the configuration of the construction target system 90 is changed by the device executing the setting change. The reference configuration information 141 is typically information generated using the configuration file table 143. The reference configuration information 141 is used to confirm whether or not the setting of the system to be constructed 90 has been changed.

The confirmation configuration information 142 indicates the configuration of the construction target system 90 after the setting change when the device included in the construction target system 90 executes the setting change. When the construction target system 90 is constructed using the construction information 111, the configuration of the constructed construction target system 90 is typically indicated by the confirmation configuration information 142. The confirmation configuration information 142 is typically information generated using the configuration file table 143. The confirmation configuration information 142 is used to confirm the difference from the reference configuration information 141.

The configuration file table 143 is a collection of configuration files 112. A file name and a file location are typically registered in the configuration file table 143. The setting file 112 is a file that includes information indicating the configuration of the construction target system 90 and includes information indicating the configuration of the construction target system 90. The configuration of the device may be changed by the device changing or executing the setting file 112. The configuration change is typically performed by modifying the configuration file 112. The setting file 112 shows the settings of the system to be built 90. The construction target system 90 has a setting file 112. The setting file 112 may consist of a plurality of files.
The configuration file table 143 does not have to contain information about files that the user may not change. The configuration file table 143 does not have to be table format data.
The setting change detection unit 140 registers information for registration in the setting file table 143.

FIG. 6 shows an example of the configuration file table 143. Hereinafter, this figure will be specifically described.
The "system name" column indicates the name of the system to be constructed 90.
The "device name" column indicates the name of the device included in the system to be constructed 90.
The "storage location" column indicates the location where the setting file 112 is stored. The storage location is typically a directory. The storage location is "/ etc /" or "/ usr /" as a specific example when the OS included in the construction target system 90 is Linux (registered trademark).
The "File name" column indicates the name of the file in the storage location. The storage location file is a file stored in the storage location and the hierarchy below the storage location. The setting change detection unit 140 generates the reference configuration information 141 and the confirmation configuration information 142 by using the file corresponding to the file name.

The setting change detection unit 140 does not have to register the file information unrelated to the settings of the construction target system 90 in the confirmation configuration information 142. The "Comparison Exclusion" column indicates the storage location of such files. In this example, the setting change detection unit 140 does not include the information of all the files of "/ usr / tpp /" in the reference configuration information 141 and the confirmation configuration information 142.

The "Version" column indicates software version information. When the file is a software package or the like, the setting change detection unit 140 may include the file version information or the like in the reference configuration information 141 and the confirmation configuration information 142.

The "Timestamp" column indicates the time when the file was last updated.
The "permission" column indicates information corresponding to the user who can modify the file, execute the file, and the like. The display in the "authority" column of this figure follows the display in the Linux (registered trademark) system.
The "hash value" column indicates the hash value of the file. The hash value is a concrete example of the contents of the file.
The setting change detection unit 140 may register the attribute information of the setting file 112 or the contents of the file in the reference configuration information 141 and the confirmation configuration information 142. The attribute information is, as a specific example, a time stamp or an authority.

FIG. 7 shows an example of a file showing an outline of the system to be constructed 90. In this example, information on the name of the system and the name of the device provided in each system is included in the file. systemA and systemB are the names of the system to be constructed 90, respectively. Web01 and web02 are the names of the devices included in the systemA, respectively. "app01" and "appp02" are the names of the devices included in the systemB.
As a specific example, the setting change detection unit 140 acquires the system name and the device name by referring to such a file.
The file showing the outline of the system to be constructed 90 is, as a specific example, an inventory file of Ansible (registered trademark).

FIG. 8 shows an example of a file showing user information. "/ Home / xxx /" is the location of user xxx's home directory.
As a specific example, the setting change detection unit 140 acquires a storage location from such a file.
As a specific example, the file showing the user information is a YAML (YAML Ain't Markup Language) file such as Ansible (registered trademark) Playbook.

FIG. 9 shows an example of acquiring software package information. "Ypkg-3.2.1.rpm" is the name of the software package. "/Etc/ypkg/ypkg.conf" and "/usr/lib/ypkg/ypkg.so" are storage locations and file names of files related to software package settings.
As a specific example, the setting change detection unit 140 acquires the attribute information of the software package by using the package management tool. As a specific example, the package management tool is RPMM (RPM Package Manager).
The setting change detection unit 140 may use software update information or difference (patch) information instead of the software package information.

As a specific example, the setting change detection unit 140 acquires a list of software packages introduced by the system to be built 90, and the location and name of the files of each software package. When the construction target system 90 is not started, the setting change detection unit 140 starts the construction target system 90 or the system that is a copy of the construction target system 90.
FIG. 10 shows an example of acquiring information on a list of software packages introduced by the system to be built 90. This figure shows the display when the software package list is acquired by RPM. "/Etc/ypkg.conf" and "/usr/lib/ypkg/ypkg.so" are storage locations and names of files related to software package settings. The example also includes version information, permissions, and time stamps for each software package.
As a specific example, the setting change detection unit 140 acquires the storage location, the file name, and the attribute information in this way.

FIG. 11 shows an example of acquisition including storage location information. "/ Etc /" is a storage location. passwd, shadow, and ypkg. The conf is the file name of the file in the storage location. In addition, this example includes the authority, time stamp, and hash value of the file in each storage location.
As a specific example, the setting change detection unit 140 acquires the attribute information and the contents from such a file, and registers the attribute information and the contents in the setting file table 143.

*** Explanation of operation ***
FIG. 12 is a flowchart showing an example of the operation of the configuration management device 100. Differences between the present embodiment and the first embodiment will be mainly described.

(Step S201: Setting file table reception process)
The setting change detection unit 140 receives the setting file table 143.
The setting change detection unit 140 may specify a file in which information indicating the configuration of the construction target system 90 is recorded, and may generate a setting file table 143 using the specified file. The setting change detection unit 140 may generate the setting file table 143 using the information acquired from the construction information 111.

(Step S202: Reference configuration information generation process)
The setting change detection unit 140 generates the reference configuration information 141 by using the construction target system 90 and the setting file table 143. As a specific example, the setting change detection unit 140 may generate the reference configuration information 141 by copying the file shown in the setting file table 143 from the construction target system 90, and is also shown in the setting file table 143. The reference configuration information 141 may be generated by acquiring the version, the time stamp, the authority, and the hash value in the same manner. The reference configuration information 141 may consist of a plurality of files.
When the reference configuration information 141 has already been generated, the setting change detection unit 140 may update the reference configuration information 141 by using the difference between the reference configuration information 141 and the confirmation configuration information 142. The setting change detection unit 140 may use the confirmation configuration information 142 as the reference configuration information 141.
The setting change detection unit 140 may generate the reference configuration information 141 by using only a part of the setting file table 143.

(Step S203: Confirmation configuration information generation process)
The setting change detection unit 140 uses the setting file table 143 to generate confirmation configuration information 142. The setting change detection unit 140 may generate confirmation configuration information 142 by copying the file shown in the setting file table 143 from the system to be constructed 90, and the version and time shown in the setting file table 143. It may be acquired in the same manner as the stamp, authority, and hash value to generate confirmation configuration information 142. The setting change detection unit 140 may generate the confirmation configuration information 142 by using only a part of the setting file table 143.
The setting change detection unit 140 may execute the above-mentioned processing after the construction target system 90 has executed all the processing corresponding to the direct setting. The setting change detection unit 140 may execute the above-mentioned process at any timing. As a specific example, the setting change detection unit 140 does not have to execute the process of this step every time the setting is directly executed. The configuration management device 100 may return to step S104 without the setting change detection unit 140 executing the above-described processing.

(Step S204: Setting change detection process)
The setting change detection unit 140 detects the presence or absence of a setting change of the device by using the reference configuration information 141 and the confirmation configuration information 142. The setting change detection unit 140 may detect a file changed by the user.
If the setting change detection unit 140 cannot detect the setting change, the configuration management device 100 proceeds to step S104. In this case, as a specific example, when the user operates a file that is not registered in the setting file table 143, or when the user changes the setting file 112 and then the setting file 112 changed by the user is changed to the state before the change. When it is returned to. Otherwise, the configuration management device 100 proceeds to step S205.

(Step S205: Change content extraction process)
The change content extraction unit 150 extracts the change content corresponding to the setting change detected in step S204. As a specific example, the change content extraction unit 150 extracts the difference between the reference configuration information 141 and the confirmation configuration information 142.

(Step S206: Change content reflection process)
The change content reflecting unit 160 reflects the change content extracted in step S205 in the construction information 111.
The configuration management device 100 proceeds to step S102 and step S202.

When the configuration management device 100 receives the setting file table 143 during the execution of the processing of this flowchart, the configuration management device 100 may interrupt the processing being executed and execute the processing of this flowchart from the beginning.

*** Explanation of the effect of Embodiment 2 ***
As described above, the configuration management device 100 according to the present embodiment detects the setting change by using the reference configuration information 141, the confirmation configuration information 142, and the setting file table 143. Therefore, according to the present embodiment, it is difficult to fail to reflect the setting change in the construction information 111.

*** Other configurations ***
<Modification 2>
Even if the user directly executes the setting in step S104, the configuration management device 100 does not have to proceed to the next step if the file included in the setting file table 143 has not been updated.
In this modification, as a specific example, in step S104, the setting change detection unit 140 determines whether or not to proceed to the next step by referring to the time stamp shown in the setting file table 143.

Embodiment 3.
Hereinafter, the points different from those of the second embodiment will be mainly described with reference to the drawings.

*** Explanation of configuration ***
FIG. 13 shows a configuration example of the configuration management device 100 according to the present embodiment. As shown in this figure, the configuration management device 100 includes an operation history recording unit 170.

The setting change detection unit 140 manages the setting file information. The setting file information is information including the time when the setting file is changed.

The change content extraction unit 150 may extract the change content using the operation history. The operation history is recorded by the operation history recording unit 170.
The change content extraction unit 150 may have candidate operation information. Candidate operation information includes information on operations that may change device settings. The operation information table 151 is a specific example of candidate operation information.
The change content extraction unit 150 identifies the operation that caused the setting change by comparing the device operation information with the candidate operation information, and extracts the information corresponding to the specified operation as the change content. The device operation information is information indicating the operation performed when the device is operated.
The change content extraction unit 150 identifies the operation executed for the device in the time zone when the setting file is changed by using the setting file information and the operation history, and extracts the specified operation as the change content. You may.

The operation information table 151 shows the correspondence between the setting file 112 and the operation of updating each setting file 112. In the operation information table 151, operations that may change any of the setting files 112 are registered.
An example of the operation information table 151 is shown in FIG. This example is for the case where the OS of each device included in the system to be constructed 90 is Linux (registered trademark).

The change content reflection unit 160 may generate a file corresponding to the operation specified by the change content extraction unit 150, and reflect the generated file in the construction information 111. The change content reflecting unit 160 may copy the file corresponding to the operation.

The operation history recording unit 170 records an operation history indicating a history in which each device included in the construction target system 90 is operated. The operation history shows the history of operations performed by the user for each device included in the system to be constructed 90. The operation history is sometimes called an operation log. The operation history recording unit 170 may manage only the operation history indicating the operation corresponding to the direct setting. The operation corresponding to the direct setting is an operation performed by the user in the direct setting. When referring to the operation history, unless otherwise specified, it refers to the operation history managed by the operation history recording unit 170.
The operation history may include device operation information and time information corresponding to the device operation information.

*** Explanation of operation ***
FIG. 14 is a diagram illustrating an outline of the operation of the configuration management device 100. The outline of the operation of the configuration management device 100 will be described with reference to this figure.

The configuration management device 100 detects that the setting file 112 has been changed. Next, the configuration management device 100 extracts the contents changed by the user using the detected setting file 112 and the operation history. Next, the configuration management device 100 reflects the extracted contents in the construction information 111.

FIG. 15 is a flowchart showing an example of the operation of the configuration management device 100. The operation of the configuration management device 100 will be described with reference to this figure.
The configuration management device 100 executes the process of this flowchart instead of step S205 in the second embodiment.

(Step S301: Change time identification process)
The change content extraction unit 150 specifies the setting change time of the setting file 112. As a specific example, the setting change time is a time stamp of the file detected in step S204.

(Step S302: Operation history search process)
The change content extraction unit 150 identifies the operation executed by the user at the setting change time by searching the operation history using the setting change time as a key.
The change content extraction unit 150 may extract the content of the setting changed by the operation specified in step S302. The content of the setting to be changed is the setting of the device changed by executing the specified operation.

FIG. 16 is a diagram for specifically explaining an example of the processing of this flowchart. This process will be specifically described with reference to this figure.
In step S301, the change content extraction unit 150 specifies that the setting change time of "/ etc / shadow" is 12:00 on November 1, 2019. “/ Etc / shadow” is a file detected in step S204.
Next, in step S302, the change content extraction unit 150 searches the operation history recording unit 170 and identifies the operation executed at 12:00 on November 1, 2019. In this figure, the operation executed at 12:00 on November 1, 2019 is "echo" xxx: ABC "| chpasswd".

FIG. 17 is a flowchart showing another example of the operation of the configuration management device 100. The operation of the configuration management device 100 will be described with reference to this figure. In this example, the change content extraction unit 150 uses the operation information table 151.

(Step S311: Operation information table generation process)
The change content extraction unit 150 registers in the operation information table 151 the operations that may update the setting file 112.
The change content extraction unit 150 may periodically update the file registered in the operation information table 151. At this time, the change content extraction unit 150 may use machine learning.
The change content extraction unit 150 may not generate the operation information table 151 and may accept the operation information table 151 input by the user.

(Step S312: Operation candidate list generation process)
The change content extraction unit 150 searches the operation information table 151 using the file detected in step S204 as a key, and generates an operation candidate list 152 using the search result. The operation candidate list 152 is a list showing a list of operations that may update the file detected in step S204.
If the change content extraction unit 150 cannot generate the operation candidate list 152, the configuration management device 100 returns to step S104.

(Step S313: Operation history search process)
The change content extraction unit 150 searches the operation history using each operation included in the operation candidate list 152 as a key, and identifies the operation corresponding to the setting directly using the search result. The change content extraction unit 150 may use at least one of the time stamp of the file detected in step S204 and the time stamp of the operation history in order to improve the accuracy of extracting the operation corresponding to the direct setting.
As a specific example, the change content extraction unit 150 may utilize information indicating operation candidates corresponding to the direct setting. The change content extraction unit 150 may extract the content of the setting changed by the specified operation.
The change content extraction unit 150 may extract the operation corresponding to the setting directly from the operation history or the like by a method based on the pattern check as shown in Patent Document 2.

FIG. 18 is a diagram for specifically explaining an example of the processing of this flowchart. This process will be specifically described with reference to this figure.

In step S312, the change content extraction unit 150 searches the operation information table 151 using "/ etc / shadow" as a key. “/ Etc / shadow” is a file detected in step S204. The change content extraction unit 150 sets "chpasswd, newusers, passwd, useradd, userdel, usermod, ...", Which is an operation corresponding to "/ etc / shadow", as the operation candidate list 152.
Next, in step S313, the change content extraction unit 150 searches the operation history using each operation included in the operation candidate list 152 as a key. The operation history is managed by the operation history recording unit 170. In this example, the change content extraction unit 150 identifies "chpasswd" from the operation history. “Chpasswd” is included in the operation candidate list 152.
When the time stamp of "/ etc / shadow" and the time stamp of the operation in the operation history match, the operation history recording unit 170 determines that the operation in the operation history is an operation corresponding to the setting directly. You may.

The operation history recording unit 170 may always execute a process of managing the operation history. As a specific example, the operation history recording unit 170 adds the user's operation to the operation history when the user operates the device of the construction target system 90.

As described above, the configuration management device 100 may be able to handle a case where the user changes the configuration of the system to be constructed 90 by a CLI (Command line interface) operation. Further, the configuration management device 100 may be able to cope with a case where the user changes the setting of the construction target system 90 by changing the GUI (Graphical User Interface) operation, the software package, or the setting file. The configuration management device 100 may be able to handle a case where the user changes the configuration of the construction target system 90 by combining these.

FIG. 19 is a table illustrating an example of direct configuration for a Linux® system.
The "direct setting" column indicates a file or the like to be input to the construction target system 90 in the operation corresponding to the direct setting or the direct setting.
The "construction process" column indicates a specific means to be adopted when the user directly executes the setting.
The "operation history" column indicates the type of operation history corresponding to the direct setting.
The "File format / Tool example" column indicates the file format or tool corresponding to the direct setting. As a specific example, the construction processing unit 120 constructs the construction target system 90 using the files or tools described in this column.
The construction information management unit 110 may manage the information shown in this table as construction information 111. By managing the information shown in this table by the construction information management unit 110, the configuration management device 100 can handle various devices, changes, input files, user operations, and the like. be able to.
The change content reflecting unit 160 may execute the process described below in step S206.

FIG. 20 is a diagram illustrating an outline of the operation of the configuration management device 100. The outline of the operation of the configuration management device 100 will be described with reference to this figure.
The CLI operation or GUI operation shown on the left side of this figure is an example of an operation corresponding to the direct setting. When the user executes the setting change by executing such a direct setting, it is reflected in the construction information 111 managed by the construction information management unit 110.
Next, the construction processing unit 120 constructs the construction target system 90 using the changed construction information 111.

FIG. 21 is a diagram illustrating an example in which the change content reflecting unit 160 generates the construction information 111 when the user directly executes the setting by using the CLI operation or the GUI operation. The operation of the change content reflecting unit 160 will be described with reference to this figure. In this example, the construction information management unit 110 classifies and manages the construction information 111 according to the type of operation. In addition, in FIGS. 21 to 23, the same system name and device name as in FIG. 6 and the like are used.
“Echo“ xxx: ABC ”| chpasswd” is a direct setting executed by the user for web01 of systemA by CLI operation. The change content reflecting unit 160 incorporates this operation into the construction information 111 corresponding to web01 of systemA.
"Button.click" is a direct setting executed by the user for web02 of systemA by GUI operation. The change content reflecting unit 160 incorporates this operation into the construction information 111 corresponding to web02 of systemA. The change content reflecting unit 160 may incorporate the configuration of the construction target system 90 changed by this operation into the construction information 111.

FIG. 22 is a diagram illustrating an example in which the change content reflecting unit 160 generates the construction information 111 when the user directly changes the setting file or the software package in the setting. The operation of the change content reflecting unit 160 will be described with reference to this figure. In this example, the construction information management unit 110 classifies and manages the construction information 111 into a setting file and a software package. In addition, changing the setting file or software package includes introducing the setting file or software package and deleting the setting file or software package.
In this example, it is assumed that the user has changed the user password managed by web01 of systemA. The change content reflecting unit 160 takes in the information of the "/ etc / passwd" file and the information of the "/ etc / shadow" file into the construction information 111 corresponding to the web01 of systemA. These files are files that have been modified by the user directly performing the configuration. The change content reflection unit 160 typically incorporates copies of these files into the construction information 111.
Further, in this example, it is assumed that the user has installed the software package "ypkg-3.2.1.rpm" on web02 of systemA. The change content reflection unit 160 converts the "ypkg-3.2.1.rpm" file, or the "/etc/ypkg/ypkg.conf" file and the "/usr/lib/ypkg/ypkg.so" file. It is taken into the construction information 111 corresponding to web02 of systemA. These files are files generated by the user installing "ypkg-3.2.1.rpm" on web02 of systemA. The change content reflection unit 160 may incorporate the version information or build number of the software package into the construction information 111.

FIG. 23 shows an example in which the change content reflecting unit 160 generates the construction information 111 by converting the operation corresponding to the setting directly into the setting script or the construction description. The operation of the change content reflecting unit 160 will be described with reference to this figure. In this example, the construction information management unit 110 classifies and manages the construction information 111 into a setting script and a construction description. The setting script is information of a script file used for constructing the construction target system 90. The configuration management device 100 can construct the construction target system 90 by executing the setting script. The construction description is information instructing the construction of the construction target system 90. The construction description may be put together in a file.
In this example, it is assumed that the user executes the process "echo" xxx: ABC "| chpasswd" on the web01 of systemA. The change content reflection unit 160 generates a shell script file corresponding to this processing, and incorporates the generated file into the construction information 111 corresponding to web01 of systemA. The change content reflection unit 160 may add a description corresponding to this process to the existing shell script file.
Further, in this example, it is assumed that the user also executes this process on web02 of systemA. The change content reflection unit 160 generates an Ansible (registered trademark) Playbook file corresponding to this processing, and incorporates the generated file into the construction information 111 corresponding to web02 of systemA.

*** Explanation of the effect of Embodiment 3 ***
As described above, according to the present embodiment, the setting is directly detected by using the operation information table 151. The change content extraction unit 150 may update the operation information table 151 as appropriate.
Therefore, according to the present embodiment, it is difficult to fail to detect or extract the operation corresponding to the setting change.

*** Other configurations ***
<Modification example 3>
The configuration management device 100 may not include the operation history recording unit 170 and may use the operation history managed by each device included in the system to be constructed 90.

<Modification example 4>
When the user directly executes the setting by inputting a file, the change content extraction unit 150 may analyze the input file and extract the change content.
In this modification, as a specific example, the change content extraction unit 150 specifies an operation for inputting a file in step S302 or step S313, and the change content reflection unit 160 constructs a command described in the input file. It is reflected in 111.

<Modification 5>
The configuration management device 100 may be able to cope with the case where the setting change is executed and the setting change previously executed is canceled by the subsequent setting change.
In this modification, as a specific example, the change content extraction unit 150 may be regarded as having not performed the above-mentioned two operations, and the change content reflection unit 160 may perform the above-mentioned two operations by analyzing the operations. It is not necessary to specify and reflect the setting change corresponding to the two operations in the construction information 111.

Embodiment 4.
Hereinafter, the points different from those of the second embodiment will be mainly described with reference to the drawings.

*** Explanation of configuration ***
FIG. 24 shows a configuration example of the configuration management device 100 according to the present embodiment. The configuration management device 100 includes a configuration difference detection unit 180.

The construction processing unit 120 constructs the construction target system 90 as a test construction target system by using the construction information 111 reflecting the changed contents. The test construction target system may be a construction target system 90 different from the construction target system 90 whose settings have been changed.

As shown in this figure, the configuration difference detection unit 180 has confirmation configuration information 142 and test configuration information 145. The configuration difference detection unit 180 receives the confirmation configuration information 142 from the setting change detection unit 140. The test configuration information 145 indicates the configuration of the test construction target system.
The configuration difference detection unit 180 generates the test configuration information 145, detects the difference between the confirmation configuration information 142 and the test configuration information 145 as the configuration difference, and reflects the configuration difference in the change construction information. The change construction information is the construction information 111 that reflects the changed contents.

*** Explanation of operation ***
FIG. 25 is a flowchart showing an example of the operation of the configuration management device 100. The operation of the configuration management device 100 will be described with reference to this figure.

(Step S401: Test construction process)
The construction processing unit 120 constructs the construction target system 90 using the construction information 111. The construction target system 90 constructed in this step is referred to as a test construction target system. The construction information 111 reflects the changed contents. Hereinafter, the same applies to the description of this flowchart unless otherwise specified.
The construction processing unit 120 may construct a construction target system 90 different from the construction target system 90 for which the direct setting is executed.
When the construction processing unit 120 completes the construction of the construction target system 90, the configuration management device 100 proceeds to the next step.

(Step S402: Test configuration information generation process)
The configuration difference detection unit 180 generates test configuration information 145 with reference to the test construction target system.
The configuration difference detection unit 180 executes the same process as in step S203.

(Step S403: Configuration difference detection process)
The configuration difference detection unit 180 detects the configuration difference by comparing the confirmation configuration information 142 with the test configuration information 145. The configuration difference is a difference between the confirmation configuration information 142 and the test configuration information 145.
When the configuration difference detection unit 180 detects the configuration difference, the configuration management device 100 proceeds to step S404. Otherwise, the configuration management device 100 proceeds to step S406.
The configuration difference detection unit 180 uses the confirmation configuration information 142 generated by the setting change detection unit 140.

(Step S404: Configuration difference extraction process)
The configuration difference detection unit 180 extracts the content of the configuration difference detected in step S403. The configuration difference detection unit 180 executes the same process as in step S205.

(Step S405: Configuration difference reflection process)
The configuration difference detection unit 180 reflects the content of the configuration difference extracted in step S404 in the construction information 111. As a specific example, the configuration difference detection unit 180 executes the same processing as the change content reflection unit 160 according to the third embodiment.

(Step S406: Construction information management process)
The construction information management unit 110 executes the same process as in step S102.

*** Explanation of the effect of Embodiment 4 ***
As described above, according to the present embodiment, the configuration difference detection unit 180 detects the configuration difference by comparing the confirmation configuration information 142 and the test configuration information 145, and the content of the configuration difference. Is reflected in the construction information 111.
Therefore, according to the present embodiment, there is an inconsistency between the construction information 111 generated by the configuration management device 100 according to any one of the first to third embodiments and the construction target system 90 to which the changed contents are reflected. When the above occurs, the inconsistency can be resolved.

*** Other embodiments ***
It is possible to freely combine the above-described embodiments, modify any component of each embodiment, or omit any component in each embodiment.

Further, the embodiment is not limited to the one shown in the first to fourth embodiments, and various changes can be made as needed. The procedure described using the flowchart or the like may be changed as appropriate.

10 computer, 11 processor, 12 memory, 13 auxiliary storage device, 14 input / output IF, 15 communication device, 18 processing circuit, 19 signal line, 90 construction target system, 100 configuration management device, 110 construction information management unit, 111 construction information , 112 Setting file, 120 Construction processing unit, 140 Setting change detection unit, 141 Reference configuration information, 142 Confirmation configuration information, 143 Setting file table, 145 Test configuration information, 150 Change content extraction unit, 151 Operation information table, 152 Operation candidate list, 160 change content reflection unit, 170 operation history recording unit, 180 configuration difference detection unit.

Claims (10)

A setting change detection unit that detects the presence or absence of a setting change of the device provided in the system to be built equipped with the device, and a setting change detection unit.
When there is a setting change, a change content extraction unit that extracts the content of the setting change as a change content, and a change content extraction unit.
A configuration management device including a change content reflection unit that reflects the change content in the construction information used for constructing the construction target system. The configuration of the construction target system is changed by the equipment included in the construction target system executing the setting change.
The setting change detection unit includes reference configuration information indicating the configuration of the construction target system before the configuration of the construction target system is changed by the device executing the setting change, and the device changes the setting. When executed, the confirmation configuration information indicating the configuration of the construction target system whose configuration has been changed is generated, and the setting change is detected by using the reference configuration information and the confirmation configuration information. The configuration management device according to claim 1. The setting change detection unit generates a setting file table that summarizes the setting files of the construction target system using the construction information, and the reference configuration information and the confirmation configuration information are combined with the setting file table. The configuration management device according to claim 2, which is generated by using the above. It is provided with an operation history recording unit that records an operation history indicating a history of operation of the device.
The configuration management device according to claim 3, wherein the change content extraction unit extracts the change content using the operation history. The setting change is executed by changing a setting file containing information indicating the configuration of the system to be built.
The operation history includes device operation information indicating an operation executed when the device included in the construction target system is operated, and time information corresponding to the device operation information.
The setting change detection unit manages information including the time when the setting file is changed as setting file information.
The change content extraction unit identifies the operation executed for the device in the time zone when the setting file is changed by using the setting file information and the operation history, and identifies the specified operation. The configuration management device according to claim 4, which is extracted as the content of the change. The change content extraction unit has candidate operation information including information on operations that may change the settings of the device included in the system to be constructed, and compares the device operation information with the candidate operation information. The configuration management device according to claim 5, wherein the operation that caused the setting change is specified, and the information corresponding to the specified operation is extracted as the change content. The configuration management device according to claim 5 or 6, wherein the change content reflecting unit generates a file corresponding to the specified operation, and reflects the generated file in the construction information. The construction processing unit that constructs the construction target system as a test construction target system by using the construction information that reflects the change contents as the change construction information and using the change construction information.
Test configuration information indicating the configuration of the test construction target system is generated, a difference between the confirmation configuration information and the test configuration information is detected as a configuration difference, and the configuration difference is the modified construction information. The configuration management device according to any one of claims 2 to 7, further comprising a configuration difference detection unit that reflects the above. The setting change detection unit detects whether or not the setting of the device provided in the system to be constructed including the device has been changed.
When the change content extraction unit has the setting change, the change content extraction unit extracts the content of the setting change as the change content.
A configuration management method in which the change content reflection unit reflects the change content in the construction information used to construct the construction target system. On the computer
Detects the presence or absence of a change in the settings of the device provided in the system to be built equipped with the device.
When there is a setting change, the content of the setting change is extracted as the change content.
A configuration management program that reflects the changes in the construction information used to construct the system to be constructed.

Images