JP7107546B2 - Inspection system, inspection method and program - Google Patents

Description

The present invention relates to an inspection system, inspection method and program.

Several techniques have been proposed in connection with computer inspection.
For example, Patent Literature 1 describes an inspection method that simplifies the hardware configuration by virtualizing a server that provides an inspection program to a device to be inspected. The inspection method described in Patent Literature 1 uses a hardware configuration in which a device to be inspected and an operation terminal device for operating the device to be inspected are connected. A virtual server operates on the operation terminal device, and the device to be inspected connects to the virtual server and reads and executes the inspection program.

Further, Patent Literature 2 describes a virtual system control program for testing a virtual system configured using a plurality of virtual machines. The virtual system control program described in Patent Literature 2 configures an active virtual system and a test virtual system using the same physical server pool. The test virtual system is configured by adding a virtual machine for a test client to the virtual machine configuration of the operational virtual system.

JP 2013-020282 A JP 2010-113381 A

When the inspection target includes new hardware, the device driver corresponding to the inspection of the new hardware is a new OS (Operating System) kernel or a new OS distribution (OS distribution). ). In this case, it is necessary to perform inspection using a new OS.
The inspection program includes hardware-related or specialized processing, and is closely related to the kernel and device drivers. For this reason, porting the inspection program to the new OS in order to perform inspection using the new OS requires a large amount of man-hours and places a heavy burden on the operator. It is preferable that such a burden on the operator can be reduced.

An object of the present invention is to provide an inspection system, an inspection method, and a program that can solve the above-described problems.

According to a first aspect of the present invention, an inspection system includes an inspection program providing unit that provides, to each of a plurality of versions of an operating system, an inspection program that runs on that version of the operating system; and an inspection execution control unit that switches the version of the operating system applied to the machine to be inspected and causes the machine to be inspected to execute the inspection program that runs on the version of the operating system.

According to a second aspect of the present invention, an inspection method includes the steps of: providing an inspection program that runs on each of a plurality of versions of an operating system to each of a plurality of versions of the operating system; switching a version of an operating system to be applied to a target device and causing the target device to execute the inspection program that operates on the version of the operating system.

According to a third aspect of the present invention, the program includes a step of providing the computer with an inspection program that operates on each of a plurality of versions of the operating system, and each time the machine to be inspected is restarted, a step of switching the version of the operating system to be applied to the machine to be inspected and causing the machine to be inspected to execute the inspection program that runs on the version of the operating system.

According to this invention, the burden on the operator who builds or updates the inspection system can be made relatively small.

1 is a schematic block diagram showing the functional configuration of an inspection system according to an embodiment; FIG. It is a figure which shows the structural example in the case of comprising the inspection system which concerns on embodiment using a virtual machine. 3 is a schematic block diagram showing the functional configuration of a management server according to the embodiment; FIG. FIG. 4 is a diagram illustrating an example of processing procedures of an inspection system and an inspection target machine when a management server according to the embodiment acquires hardware configuration information of the inspection target machine and selects an OS and an inspection tool; FIG. 4 is a diagram showing an example of a processing procedure when the inspection system according to the embodiment prepares a kernel and an inspection program for causing an inspection target machine to perform inspection; FIG. 2 is a diagram showing an example of a processing procedure of an inspection system and a machine to be inspected when the machine to be inspected according to the embodiment performs inspection; It is a figure showing an example of the minimum composition of an inspection system concerning the present invention.

Embodiments of the present invention will be described below, but the following embodiments do not limit the invention according to the claims. Also, not all combinations of features described in the embodiments are essential for the solution of the invention.
FIG. 1 is a schematic block diagram showing the functional configuration of the inspection system according to the embodiment. With the configuration shown in FIG. 1 , the inspection environment 1 includes an inspection system 100 and an inspection target machine 900 . The inspection system 100 includes a communication section 110 , a display section 120 , an operation input section 130 , a storage section 180 and a control section 190 . The control unit 190 includes a configuration information acquisition unit 191 , a selection unit 192 , an inspection program providing unit 193 and an inspection execution control unit 194 .

The inspection target machine 900 is an inspection target. The machine 900 to be inspected is configured by combining a computer such as a workstation or a personal computer (PC) and peripheral devices.
The inspection system 100 controls inspection of the machine 900 to be inspected. Specifically, the inspection system 100 controls the machine 900 to be inspected to execute the inspection program. The inspection system 100 also functions as a user interface in the inspection environment 1 .
The inspection system 100 is configured using a computer such as a workstation or a personal computer, for example. The inspection system 100 may be configured using one computer, or may be configured using a plurality of computers. Moreover, as will be described later, the inspection system 100 may be configured using a virtual machine.

The communication unit 110 communicates with other devices. In particular, the communication unit 110 communicates with the machine 900 to be inspected, transmits the inspection program to the machine 900 to be inspected, and receives execution result information of the inspection program from the machine 900 to be inspected.
The display unit 120 has a display screen such as a liquid crystal panel or an LED (Light Emitting Diode) panel, and displays various images. For example, the display unit 120 displays the inspection result of the machine 900 to be inspected.
The operation input unit 130 includes input devices such as a keyboard and a mouse, and receives user operations. For example, the operation input unit 130 receives a user operation instructing the start of inspection of the machine 900 to be inspected.

The storage unit 180 stores various information. In particular, the storage unit 180 stores an inspection tool for causing the inspection target machine 900 to perform an inspection, and an OS (Operating System) to be executed by the inspection target machine 900 during inspection. In order to cope with the case where the device driver corresponding to new hardware inspection is only in the new OS kernel or the new OS distribution (OS distribution), the storage unit 180 has a plurality of Store version of OS.

The OS stored in the storage unit 180 is not limited to a specific type of OS. For example, the OS stored in the storage unit 180 may be Linux (registered trademark), but is not limited to this.
A case where the storage unit 180 stores two versions of the OS, new and old, will be described below as an example, but the number of OS versions stored in the storage unit 180 may be two or more. The storage unit 180 may store three or more versions of the OS.

The control unit 190 controls each unit of the inspection system 100 to perform various processes. The control unit 190 is configured by the CPU included in the inspection system 100 reading a program from the storage unit 180 and executing the program.
The configuration information acquisition unit 191 acquires hardware configuration information of the inspection target machine 900 . For example, the configuration information acquisition unit 191 controls the device to be inspected 900 to execute a hardware configuration investigation program, and acquires hardware configuration information as an execution result.

The selection unit 192 selects the OS version to be applied to the inspection target machine 900 based on the hardware configuration information acquired by the configuration information acquisition unit 191 . The selection unit 192 selects an OS for each piece of hardware that constitutes the device to be inspected 900, and selects an old version OS for hardware compatible with an old version OS. On the other hand, the selection unit 192 selects the new version of the OS for hardware that only the new version of the OS supports.

Further, the selection unit 192 selects an inspection tool to be used for inspection of the inspection target machine 900 for each version of the selected OS. Since the selection unit 192 selects the old version OS for the hardware supported by the old version OS, the inspection tool that operates on the old version OS can be used without porting to the new version OS. be able to. In this respect, the burden on the operator who constructs or updates the inspection system 100 can be reduced.

The inspection program providing unit 193 provides the inspection target machine 900 with an inspection program that operates on each of a plurality of versions of the OS. Specifically, the inspection program providing unit 193 uses the inspection tool selected by the selection unit 192 to generate, for each OS version, an inspection program for causing the inspection target machine 900 to execute the inspection tool.

The inspection execution control unit 194 controls the inspection target machine 900 to switch the OS version of the inspection target machine 900 and execute an inspection program according to the OS version. Specifically, the inspection execution control unit 194 reboots the inspection target machine 900 and switches the version of the operating system applied to the inspection target machine 900 each time the inspection target machine 900 is rebooted. Then, the inspection execution control unit 194 causes the inspection target machine 900 to execute an inspection program that operates on the switched version of the operating system.

Next, the inspection system will be further described with reference to FIGS. 2 to 6, taking as an example the case of configuring the inspection system using a virtual machine.
FIG. 2 is a diagram illustrating a configuration example when the inspection system according to the embodiment is configured using virtual machines. With the configuration shown in FIG. 2 , the inspection environment 2 includes an inspection system 200 and an inspection target machine 900 . The inspection system 200 includes hardware 211 , a hypervisor 213 , a management server 220 , an old version OS machine 230 , a new version OS machine 240 , a tool database 250 and a network boot server 260 . Hardware 211 includes a network port 212 . The management server 220, the old version OS machine 230, the new version OS machine 240, the tool database 250, and the network boot server 260 are configured as virtual machines.
The machines to be inspected in FIG. 2 are the same as those in FIG. 1, and are denoted by the same reference numerals (900), and the description thereof will be omitted.

Inspection system 200 corresponds to an example of inspection system 100 . The virtual machines that make up the inspection system 200 may be executed on one physical server or may be executed on multiple physical servers.
Hardware 211 is the hardware layer of a physical server used in inspection system 200 . Each of the virtual machines constituting the inspection system 200 is connected to the network port 212 of the hardware 211 for communication. The test target device 900 is also connected to the network port 212 , and communication is performed between the virtual machines and between the virtual machine and the test target device 900 .
A hypervisor 213 is a hypervisor that operates on a physical server used in the inspection system 200 and provides a virtual machine execution environment.

The management server 220 corresponds to an example of the configuration information acquisition unit 191 in FIG. 1 and acquires hardware configuration information of the inspection target machine 900 . The management server 220 corresponds to an example of the selection unit 192 in FIG. 1, selects an OS version to be applied to the inspection target machine 900 based on the hardware configuration information, and performs inspection for each selected OS version. An inspection tool to be used for inspection of the target machine 900 is selected.

FIG. 3 is a schematic block diagram showing the functional configuration of the management server 220. As shown in FIG. With the configuration shown in FIG. 3 , the management server 220 includes a storage section 221 and a control section 222 . The control unit 222 executes an inspection control program for controlling cooperation of virtual machines. Then, the control unit 222 stores the hardware configuration information of the inspection target device 900 acquired from the inspection target device 900 and the inspection result of the inspection target device 900 in the storage unit 221 . Further, when selecting an inspection tool, the control unit 222 refers to information on inspection items for hardware, which is stored in advance in the storage unit 221 .

The old-version OS machine 230 executes an old-version OS and generates an inspection program that operates on the old-version OS.
The new-version OS machine 240 executes the new-version OS and generates inspection programs that operate on the new-version OS.
A combination of the old version OS machine 230 and the new version OS machine 240 corresponds to an example of the inspection program providing unit 193 in FIG. By combining the old-version OS machine 230 and the new-version OS machine 240, for each OS version, a virtual machine to which the OS of the version is applied is used to generate an inspection program that operates on the OS of the version.

The tool database 250 stores inspection tools and provides the old version OS machine 230 and the new version OS machine 240 with the inspection tools.
The network boot server 260 provides an OS and a test program when the machine 900 to be tested is booted. Each time the device under test 900 reboots under the control of the management server 220, the network boot server 260 provides the device under test 900 with a different version of the OS (especially kernel) and a test program that runs on that version of the OS.
A combination of the management server 220 and the network boot server 260 corresponds to an example of the test execution control unit 194 in FIG.

Operations of the inspection system 200 and the machine 900 to be inspected will be described with reference to FIGS. 4 to 6. FIG.
FIG. 4 is a diagram showing an example of processing procedures of the inspection system 200 and the inspection target machine 900 when the management server 220 acquires hardware configuration information of the inspection target machine 900 and selects an OS and an inspection tool.
In the processing of FIG. 4, when the device under test 900 itself is powered on and starts booting (sequence S11 1 ), the kernel and program prepared in advance for investigating the hardware configuration are transferred to the network. A request is made to the boot server 260 (sequence S112).

The network boot server 260 provides the hardware configuration investigation kernel and the hardware configuration investigation program to the inspection target device 900 in response to the request from the inspection target device 900 (sequence S113). The machine 900 to be tested examines its own hardware configuration using the provided kernel and program, and transmits the obtained hardware configuration information to the management server 220 (sequence S114).

The management server 220 selects an OS version to be applied to the inspection target machine 900 based on the hardware configuration information received from the inspection target machine 900, and uses each selected OS version for inspection of the inspection target machine 900. An inspection tool is selected (sequence S121). In the examples of FIGS. 4 to 6, the hardware of the device to be inspected 900 includes hardware compatible with the old version OS and hardware compatible only with the new version OS. Therefore, the management server 220 selects both the old version OS and the new version OS.

Then, the management server 220 notifies the old-version OS machine 230 and the new-version OS machine 240 of the selected inspection tool for each OS version, and instructs generation of an inspection program (sequence S122). Specifically, the management server 220 notifies the old-version OS machine 230 of the inspection tool selected for the old-version OS, and instructs the machine 900 to be inspected to generate an inspection program for executing the inspection tool. In addition, the management server 220 notifies the new-version OS machine 240 of the inspection tool selected for the new-version OS, and instructs the inspection target machine 900 to generate an inspection program for executing the inspection tool.

The inspection system 200 and the machine 900 to be inspected perform the process of FIG. 5 following the process of FIG.
FIG. 5 is a diagram showing an example of a processing procedure when the inspection system 200 prepares a kernel and an inspection program for causing the machine 900 to be inspected to perform inspection.
In the process of FIG. 5, the old version OS machine 230 requests the tool database 250 for the inspection tool notified from the management server 220 in sequence S122 of FIG. 4 (sequence S131). The tool database 250 provides the inspection tool requested by the old version OS machine 230 (sequence S132).

The old version OS machine 230 uses the inspection tool provided from the tool database 250 to generate an inspection program for causing the machine 900 to be inspected to execute the inspection tool (sequence S133). The old-version OS machine 230 then transmits the kernel of the old-version OS and the generated inspection program to the network boot server 260 (sequence S134). The network boot server 260 stores the kernel and inspection program received from the old version OS machine 230 in its own storage area.
When the old version OS machine 230 completes the transmission of the kernel and the inspection program, it transmits a completion notification to the management server 220 (sequence S135).

Also, the new version OS machine 240 requests the tool database 250 for the inspection tool notified from the management server 220 in sequence S122 of FIG. 4 (sequence S141). The tool database 250 provides the inspection tools requested by the new version OS machine 240 (sequence S142).

The new version OS machine 240 uses the inspection tool provided from the tool database 250 to generate an inspection program for causing the machine 900 to be inspected to execute the inspection tool (sequence S143). The new version OS machine 240 then transmits the new version OS kernel and the generated inspection program to the network boot server 260 (sequence S144). The network boot server 260 stores the kernel and inspection program received from the new version OS machine 240 in its own storage area.
After completing the transmission of the kernel and the inspection program, the new version OS machine 240 transmits a completion notification to the management server 220 (sequence S145).

The inspection system 200 and the machine to be inspected 900 perform the process of FIG. 6 following the process of FIG.
FIG. 6 is a diagram showing an example of a processing procedure of the inspection system 200 and the inspection target machine 900 when the inspection target machine 900 performs inspection.
In the process of FIG. 6, the management server 220 instructs the machine 900 to be inspected to reboot (sequence S151). The management server 220 receives completion notifications from all virtual machines (the old version OS machine 230 and the new version OS machine 240) corresponding to the OS selected in sequence S121 in FIG. 4 in sequences S135 and S145 in FIG. ing. In this way, the management server 220 instructs the inspection target machine 900 to restart, triggered by receiving completion notifications from all the virtual machines corresponding to the selected OS.

The device to be inspected 900 reboots according to the instruction from the management server 220, and requests the kernel and inspection program from the network boot server 260 at the time of rebooting (sequence S152). In response to a request from the device 900 to be tested, the network boot server 260 provides the device 900 to be tested with the kernel of the old version OS and the test program that runs on the kernel (sequence S153). That is, the device under test 900 transmits to the device under test 900 the kernel and the test program received from the old version OS machine 230 in sequence S134 of FIG.

The device to be tested 900 executes the kernel received from the network boot server 260 and executes the test program on the kernel to perform the test (sequence S154). Then, the inspection target device 900 transmits the obtained inspection result to the management server 220 (sequence S155).
The management server 220 that has received the inspection result from the inspection target device 900 instructs the inspection target device 900 to restart (sequence S161). The management server 220 instructs the devices to be inspected 900 to reboot as many times as the number of selected OS versions. In the examples of FIGS. 4 to 6, the management server 220 selects two OS versions (old version and new version) in sequence S121 of FIG. Therefore, the management server 220 instructs the machine 900 to be inspected to reboot twice in sequences S151 and S161.

The device to be inspected 900 reboots according to the instruction from the management server 220, and requests the network boot server 260 for the kernel and the inspection program at the time of rebooting (sequence S162). The network boot server 260, in response to a request from the device 900 to be tested, provides the device 900 to be tested with the kernel of the new version of the OS and the test program that runs on the kernel (sequence S163). That is, the device 900 to be tested transmits the kernel and the test program received from the new version OS machine 240 in sequence S144 of FIG.

The network boot server 260 transmits to the device 900 to be inspected the OS kernel of a version that has not yet been transmitted, and the inspection program that runs on the kernel. In the examples of FIGS. 4 to 6, the network boot server 260 has already sent the old version OS kernel and the inspection program running on the kernel to the inspection target device 900 in sequence S153. Therefore, in sequence S<b>163 , the network boot server 260 transmits the kernel of the new version of the OS and the inspection program running on the kernel to the inspection target machine 900 .

The device under test 900 executes the kernel received from the network boot server 260, and executes the test program on the kernel to perform the test (sequence S164). Then, the inspection target device 900 transmits the obtained inspection result to the management server 220 (sequence S165).
The management server 220 acquires the inspection results corresponding to all the selected OS versions, thereby acquiring the inspection results of all the hardware of the inspection target machine 900 . Therefore, the management server 220 does not issue a new restart instruction to the inspection target device 900 . As a result, the inspection system 200 and the machine 900 to be inspected complete the inspection (sequence S171).

As described above, the inspection program providing unit 193 provides each of a plurality of versions of the OS with the inspection program that operates on the version of the OS. The inspection execution control unit 194 switches the version of the OS to be applied to the inspection target machine 900 each time the inspection target machine 900 is restarted, and causes the inspection target machine 900 to execute an inspection program that runs on the OS of the version.
As a result, the inspection program operable on the OS of the old version can be executed by the machine 900 to be inspected without being ported to the OS of the new version. In this respect, the burden on the operator who constructs or updates the inspection system 100 can be reduced.

Also, the configuration information acquisition unit 191 acquires hardware configuration information of the inspection target machine 900 . The selection unit 192 selects the version of the operating system to be applied to the inspection target machine 900 based on the hardware configuration information.
In this way, the selection unit 192 selects the version of the operating system based on the hardware configuration information of the device 900 to be inspected, so that the inspection system 100 can handle various devices 900 to be inspected. inspection can be performed.

The selection unit 192 also selects an inspection tool to be used for inspection of the inspection target machine 900 for each version of the selected OS. The inspection program providing unit 193 uses the inspection tool selected by the selection unit 192 to generate an inspection program for each OS version.
As a result, the inspection program providing unit 193 can generate an inspection program by making adjustments for causing the inspection target machine 900 to execute the inspection tool. In this respect, the inspection program providing unit 193 can generate the inspection program relatively easily, and the load on the inspection program providing unit 193 can be relatively small.

In addition, for each OS version, the inspection program providing unit 193 uses a virtual machine to which the OS of the version is applied to generate an inspection program that operates on the OS of the version.
In this manner, the inspection program providing unit 193 generates the inspection program in an environment in which the inspection program can be executed, so that the user can check the operation of the inspection program using the environment. In this respect, the user can relatively easily check the operation of the inspection program.

Next, the minimum configuration of the present invention will be described with reference to FIG.
FIG. 7 is a diagram showing an example of the minimum configuration of an inspection system according to the present invention. An inspection system 10 shown in FIG. 7 includes an inspection program providing unit 11 and an inspection execution control unit 12 .
With such a configuration, the inspection program providing unit 11 provides each of a plurality of versions of the operating system with an inspection program that operates on the version of the operating system. The inspection execution control unit 12 switches the version of the operating system applied to the inspection target machine each time the inspection target machine is restarted, and causes the inspection target machine to execute the inspection program that operates on the operating system of the version.

As a result, the inspection program operable on the old version of the operating system can be executed by the inspection target machine 900 without being ported to the new version of the operating system. In this respect, the burden on the operator who constructs or updates the inspection system 10 can be reduced.

A program for realizing all or part of the functions of the inspection systems 10, 100 and 200 is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read and executed by the computer system. You may process each part by doing. It should be noted that the "computer system" referred to here includes hardware such as an OS and peripheral devices.
The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. Further, the program may be for realizing part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design and the like are included within the scope of the gist of the present invention.

Reference Signs List 1, 2 inspection environment 10, 100, 200 inspection system 11, 193 inspection program providing unit 12, 194 inspection execution control unit 110 communication unit 120 display unit 130 operation input unit 180 storage unit 190 control unit 191 configuration information acquisition unit 192 selection unit 211 hardware 212 network port 213 hypervisor 220 management server 221 storage unit 222 control unit 230 old version OS machine 240 new version OS machine 250 tool database 260 network boot server

Claims (5)

A test program providing unit that generates a test program that operates on a plurality of versions of an operating system using a virtual machine to which the operating system of the version is applied, and that runs on the operating system of the version;
an inspection execution control unit that switches the version of an operating system applied to the inspection target machine each time the inspection target machine is restarted and causes the inspection target machine to execute the inspection program that runs on the version of the operating system;
inspection system. a configuration information acquisition unit that acquires hardware configuration information of the inspection target machine;
a selection unit that selects an operating system version to be applied to the inspection target machine based on the hardware configuration information;
The inspection system of claim 1, comprising: The selection unit selects an inspection tool to be used for inspection of the inspection target machine for each version of the selected operating system,
The inspection program providing unit generates the inspection program for each version of the operating system using the inspection tool selected by the selection unit.
The inspection system according to claim 2. A step of generating an inspection program that runs on each of a plurality of versions of an operating system using a virtual machine to which the operating system of that version is applied ;
a step of switching the version of an operating system applied to the machine to be inspected each time the machine to be inspected is restarted, and causing the machine to be inspected to execute the inspection program that runs on the version of the operating system;
inspection methods including; to the computer,
A step of generating an inspection program that runs on each of a plurality of versions of an operating system using a virtual machine to which the operating system of that version is applied ;
a step of switching the version of an operating system applied to the machine to be inspected each time the machine to be inspected is restarted, and causing the machine to be inspected to execute the inspection program that runs on the version of the operating system;
program to run the

Images