JP2007193696A - Support program, support program generation program, support program generation method, file generation/distribution method and installation server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To create or distribute a file used for a check on whether or not a correct installation state is maintained after installation. <P>SOLUTION: A meta-package generates installation settings for automatically installing a plurality of pieces of software in each of a plurality of clusters, and generates and distributes an IDS setting file for supporting software management after the installation. Specifically, installation settings 61a are generated from a template describing setting information about the plurality of pieces of software and from externally input customization information, an IDS setting file 62a used for a check after the automatic installation of the plurality of pieces of software in computers is generated accordingly, and the IDS setting file 62a is distributed to the installation destination along with an IDS setting file prepared at the generation of the meta-package. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a support program, a file generation / distribution method, a support program generation program, a support program generation method, and a support program for supporting automatic installation of a plurality of software and software management after installation on each of one or a plurality of computers, and The present invention relates to an installation server that performs automatic installation using a support program.

  FIG. 10 shows a configuration of a general clustering system (hereinafter referred to as a cluster). The cluster 100 is a system (calculation) in which a large number of computers (calculation nodes) 102 are connected to one private network 103 and can be used as an execution environment for calculation jobs via representative nodes called head nodes 101a and 101b. Environment). FIG. 10 shows an example having two head nodes 101a and 101b, but the number of head nodes may be one or more. Each of the calculation nodes 102 and the head nodes 101a and 101b is a computer on which an OS and various software are installed, each of which operates independently. In addition, the head nodes 101 a and 101 b are connected to a general network 104. The private network 103 may be connected to other components 105 such as RAID (Redundant Arrays of Inexpensive Disks), a mass storage facility (Parallel file system: PSG), or the like. is there.

  Here, the head nodes 101a and 101b operate as a window to the user. The user accesses the calculation node 102 through the head nodes 101a and 101b. That is, the head nodes 101a and 101b hide the physical and logical details of the computation node 102 from the user. Therefore, when a user submits a job, the user can submit the job through the head nodes 101a and 101b and obtain the result without being aware of the configuration of the computing node 102. The head nodes 101a and 101b have a job scheduler and control access to the calculation node 102 on which the application is executed.

  By the way, recently, due to the advancement of network technology, high-speed network technologies such as Gigabit Ethernet (registered trademark), Myrinet, Infiniband, etc. are spreading. Gigabit Ethernet (registered trademark) is a high-speed Ethernet (registered trademark) standard in which the communication speed is increased to 1 Gbps. Infiniband is a technology for transmitting data at 10 Gbps. With the spread of such network technology, the number of computing nodes constituting one cluster is expanding to a scale of several hundred to several thousand units.

  As a problem associated with such an increase in the number of nodes, there is a sharp rise in cluster installation / management costs. That is, in order to construct a cluster, it is necessary to install an OS and software on all the computation nodes and set them correctly. For this reason, the first problem is that the initial introduction cost for setting up all the nodes is increased (see, for example, Patent Document 1). A second problem is that it is necessary to always check whether the system is broken so that the system continues to operate correctly after installation. The introduction and management costs of these clusters are a serious problem because they are proportional to the increase in the number of computing nodes.

  Among the above two problems, as a system for reducing the initial introduction cost of the cluster, which is the first problem, the cluster automatic system which automatically performs OS and software installation and setting processing which has been performed manually in the past An installer has been proposed. FIG. 11 is a diagram for explaining a general cluster automatic installer.

  The automatic cluster installer is installed on the installation server 202. Then, the automatic cluster installer receives as input the installation setting 201 which is a file describing setting information to be applied to the cluster 203, and automatically sets up each computation node 204 constituting the cluster 203.

  The main processes of the automatic cluster installer are initialization of a hard disk drive mounted on the calculation node 204, creation of a partition, installation of designated software, and setting specific to the software and the calculation node 204. The automatic cluster installer performs automatically without any interactive input (keyboard input or mouse input) by the user. When setting up all of the computing nodes 204 manually, for example, it takes several days to several weeks, but the time required for setup is reduced to several minutes by using the automatic cluster installer, which is dramatically shortened compared to the manual case. Can reduce the initial introduction cost.

  FIG. 12 shows a general software stack (software hierarchical structure) automatically installed on each computation node by the automatic installer. As an example, a case where the OS is Linux will be described.

  On each computation node, a Linux kernel as an OS is used as a base, and a Linux system operates on it. Furthermore, software, job, and cluster state management mechanisms such as job scheduling / startup, cluster software management, and cluster state management operate in the upper layer. Then, an application (message passing) for performing communication between nodes further operates on these upper layers, and a higher-order grid (GRID) application or the like may operate on this.

  Typically, hundreds to thousands of middleware to application layer software packages are installed on a standard compute node. In addition, there is a strict dependency between each layer such that a specific application operates on a specific lower middleware. That is, a complicated dependency relationship is generated between the software. In addition, an appropriate setting file is required for each software to operate correctly.

  Therefore, although the automatic installer can improve the speed of the installation itself, it is the responsibility of the cluster administrator to create a configuration file in advance to resolve these complex dependencies and perform a correct installation. In this case, it is necessary to create not only the dependency relationship between software but also a software setting file in advance. The cost of creating a file defining the dependency between software and the software setting file increases as the number of software installed on each computation node increases.

  That is, the automatic installer can speed up the installation process itself, but the cost for creating a setting file (installation setting) for the automatic installer that solves the dependency problem and the setting file problem still remains high. Further, the stable operation cost after the setup, which is the second problem described above, remains unsolved.

  Therefore, there is a so-called metapackage as an existing study for solving the dependency relationship and the problem of the configuration file. A metapackage is an “automatic cluster installer setting template collection” created by a cluster or system management expert. Metapackages can be freely installed via a metapackage repository published on the Internet.

  Specifically, the meta package can be customized for each site where the meta package has been downloaded by grouping automatic installer settings for realizing functions such as a complete job execution environment and complete monitoring system on the cluster. Packaged as a template.

The cluster administrator selects the required metapackage from the metapackage repository in units of functions and applies it to the automatic cluster installer at the local site. Appropriate dependencies are explicitly defined in advance between the templates, and the dependencies are handled appropriately by the metapackage installation tool. Solved automatically. In addition, since the meta package includes a template for setting files for each software, the initial setting cost of the automatic cluster installer described above is greatly reduced. In other words, when the metapackage is introduced, a correct automatic installer setting can be easily generated, and problems of dependency and setting files can be solved.
JP 2001-159979 A

  However, since the metapackage is simply a template of the setting file that is input to the automatic installer in this way, it is responsible for the installation process, but has nothing to do with it after installation. In other words, after a proper installation using the metapackage, if a user destroys the cluster environment, it will not work correctly.

  That is, it does not include a mechanism for reducing the above-mentioned second problem, “cost for keeping stable operation even after setup”. In other words, the meta package can “install a correct installation setting at a low cost”, but has a problem that it does not know anything after the installation.

  The present invention has been made to solve such a problem, and can create or distribute a file used for checking whether or not a correctly installed state is maintained even after installation. An object of the present invention is to provide an installation server for automatically installing a support program, a file creation / distribution method, a support program creation program for generating a support program, and a support program.

  In order to achieve the above-described object, a support program generation program according to the present invention performs an operation of generating a support program for supporting automatic installation of a plurality of software and software management after installation for each of one or a plurality of computers. A file information extraction step for extracting file information constituting the plurality of software, and an inspection after automatically installing the plurality of software on a computer based on the file information Based on a first inspection information file generation step for generating a first inspection information file in which the first inspection information used in the above is described, a template in which the plurality of software lists and the plurality of software setting information are described, in front A support program generating step of generating a support program, wherein the support program generating step generates the support program having a function of distributing the first inspection information file to a plurality of software installation destinations. Features.

  In the present invention, when creating a support program, file information of software installed by the support program is extracted, and based on this, a first inspection information file including properties and file lists of files constituting the plurality of software is generated. To do. That is, an intrusion detection system or the like can check whether the system is broken by inspecting the file information of the software installed after the installation using the first inspection information file.

  In the file information extraction step, the file information can be extracted by referring to an information database in which software file information is accumulated based on the plurality of software lists, and the software file information database is referred to. Thus, file information can be extracted.

  Further, in the support program generation step, the support program is generated based on a list of the plurality of software, the template, a user interface definition for customizing setting information described in the template, and a predetermined specification definition. For example, the first inspection information file can be generated using a user interface such as GUI (Graphical User Interface) or CUI (Character-based User Interface) simultaneously with the generation of the metapackage.

  A support program according to the present invention is a support program for causing a computer to execute an operation of generating and distributing a file for supporting automatic installation of a plurality of software and software management after the installation for each of one or a plurality of computers. An installation setting generation step for generating an installation setting for automatically installing the plurality of software from a template in which setting information of the plurality of software is described and customization information input from the outside, and the installation setting A second inspection information file for generating a second inspection information file in which second inspection information used for inspection after the plurality of software is automatically installed in the computer is generated based on the installation setting generated in the generation step. Those having a generation step.

  In the present invention, an installation setting is automatically generated, and a second inspection information file for checking whether or not the software has been tampered with after the software is installed is generated based on the installation setting. Can do.

  In the installation setting generation step, a wizard is activated, and the user can generate the installation setting by inputting customization information in an interactive window. The user can easily generate the installation setting.

  Further, in the second inspection information file generation step, the second inspection information file is generated based on the customization information included in the installation setting. Here, the second inspection information may include one or more of user information, serial number, and installation destination directory information. By checking these pieces of information, the software after installation can be managed.

  A support program according to the present invention is a support program for causing a computer to execute an operation of generating and distributing a file for supporting automatic installation of a plurality of software and software management after the installation for each of one or a plurality of computers. An installation setting generation step for generating an installation setting for automatically installing the plurality of software, and first inspection information used for inspection after the plurality of software are automatically installed on the computer are described. A distribution step of distributing the inspection information file to the installation destinations of the plurality of software;

  In the present invention, the first inspection information file in which the first inspection information used for the inspection after the plurality of software is automatically installed in the computer can be distributed to the installation destination.

  In the installation setting generation step, the installation setting can be generated from a template in which setting information of the plurality of software is described and customization information input from the outside, and the installation setting is automatically used. Multiple software can be automatically installed by the installer.

  Furthermore, based on the installation setting generated in the installation setting generation step, file generation for generating a second inspection information file in which second inspection information used for inspection after automatic installation of a plurality of software on a computer is described In the distribution step, the first and second inspection information files can be distributed, and management of software after installation can be executed by using these two inspection information files.

  Furthermore, it is a support program generated based on a template in which a list of the plurality of software and setting information of the plurality of software are described, wherein the first inspection information file is file information constituting the plurality of software The first inspection information file generated simultaneously with the support program that automatically generates the installation setting can be distributed to the installation destination.

  A support program generation method according to the present invention is a support program generation method for generating a support program for supporting automatic installation of a plurality of software and software management after installation for each of one or a plurality of computers, the plurality of software A file information extraction step for extracting file information constituting the first inspection information file in which first inspection information used for inspection after the plurality of software is automatically installed on a computer is described based on the file information A first inspection information file generation step for generating, and a support program generation step for generating the support program based on a template in which a list of the plurality of software and setting information of the plurality of software are described. Program students In the step, characterized in that the support program having the function of distributing the first test information file to the installation of the plurality of software is generated.

  A file generation / distribution method according to the present invention is a file generation / distribution method for generating / distributing a file for supporting automatic installation of a plurality of software and software management after installation for each of one or a plurality of computers. An installation setting generation step for generating an installation setting for automatically installing the plurality of software, and first inspection information describing first inspection information used for inspection after the plurality of software is automatically installed on the computer A distribution step of distributing the file to a plurality of software installation destinations;

  An install server according to the present invention is an install server that automatically installs a plurality of software on each of a plurality of computers, and generates and distributes files for supporting the installation of the plurality of software and management after the installation. A file generation / distribution means; and an automatic installer for automatically installing the plurality of software, wherein the file generation / distribution means is an installation setting generation means for generating an installation setting for automatically installing the plurality of software; Distribution means for distributing to the plurality of computers a first inspection information file in which first inspection information used for inspection after the plurality of software is automatically installed in the computer, and the automatic installer includes: in front For each of said plurality of computers according to the installation setting is for automatic install multiple software.

  In the present invention, the file generation / distribution means is used for the inspection after the software is automatically installed on the computer. For example, the first inspection information including the properties of the files constituting the plurality of software and the first inspection information including the file list is described. Since one inspection information file can be distributed to the installation destination, the installed software can be managed at the installation destination using the file.

  Further, the installation setting generation means can generate an installation setting from a template in which setting information of the plurality of software is described and customization information input from the outside.

  Further, the file generation / distribution means includes second inspection information in which second inspection information used for inspection after automatic installation of a plurality of software on a computer is described based on the installation setting generated by the installation setting generation means. The apparatus further includes file generation means for generating an inspection information file, wherein the distribution means can distribute the first and second inspection information files to the plurality of computers, and generates an installation setting. The second inspection information file can be generated based on the above and distributed to the installation destination together with the first inspection information file, so that system management after installation can be performed more powerfully.

  According to the present invention, it is possible to create or distribute a file used for checking whether or not a correctly installed state is maintained even after installation.

  Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. In this embodiment, a meta package will be described as an example of a support program for supporting automatic installation of a plurality of software and software management after the installation for each of one or a plurality of computers. In other words, in the present embodiment, after installing various software on each computing node of the cluster for this metapackage, after the setup, the intrusion detection system (IDS) is inspected to manage after the software installation. To help. At this time, the IDS uses a test information file (hereinafter referred to as an IDS setting file) generated and distributed by the metapackage to check whether each installed software has been changed or not broken since installation. It is what you use.

  First, prior to the description of the metapackage generation method and the IDS configuration file generation / distribution method using the metapackage in the embodiment of the present invention, a cluster automatic installation system using a metapackage is provided to facilitate understanding of the present invention. I will explain. FIG. 1 is a schematic diagram showing an installation system for automatically installing a cluster.

  As shown in FIG. 1, the installation system 1 includes a metapackage server 2, an installation server 3, and a cluster (also referred to as a calculation node or a cluster node) 4. A meta package created by the meta package developer 6 is uploaded to the meta package server 2. In the installation server 3, an automatic installer 3a for installing the cluster 4 is created.

  In such an installation system 1, the package manager 5 accesses the metapackage server 2, searches for the metapackage, and downloads the metapackage having a desired function. For example, the metapackage server 2 searches for a metapackage having functions of an MPI environment and a Java (registered trademark) environment from an MPI (Message Passing Interface) environment, a Globus, and a Java (registered trademark) environment. . Then, this is downloaded to the installation server 3. When the downloaded metapackage is expanded on the installation server 3, a user interface (UI) such as a GUI for customization or a CUI is displayed on a display unit (not shown). A user who performs automatic installation of the cluster 4 customizes and generates installation settings according to this UI, and inputs them to the automatic installer 3a. The automatic installer 3a executes the automatic installation of the cluster 4 according to the customized installation setting.

  FIG. 2 shows an example of the hardware configuration of the installation server 3. As shown in FIG. 2, the installation server 3 includes a CPU (Central Processing Unit) 1001, a ROM (Read Only Memory) 1002, and a RAM (Random Access Memory) 1003, which are connected to each other via a bus 1004. ing. The above-described cluster 4 also has at least a CPU and a memory.

  An input / output interface 1005 is also connected to the bus 1004. The input / output interface 1005 includes, for example, an input unit 1006 including a keyboard and a mouse, a display including a CRT and an LCD, an output unit 1007 including headphones and speakers, a storage unit 1008 including a hard disk, a modem, A communication unit 1009 composed of a terminal adapter or the like is connected.

  The CPU 1001 executes various processes according to various programs constituting the software module stored in the ROM 1002 or various programs constituting the software module loaded from the storage unit 1008 to the RAM 1003. The RAM 1003 also appropriately stores data necessary for the CPU 1001 to execute various processes.

  The communication unit 1009 performs, for example, communication processing via the Internet (not shown), transmits data provided from the CPU 1001, and outputs data received from the communication partner to the CPU 1001, RAM 1003, and storage unit 1008. To do. The storage unit 1008 exchanges with the CPU 1001 to save and erase information. The communication unit 1009 also performs communication processing of analog signals or digital signals with other devices.

  A drive 1010 is connected to the input / output interface 1005 as necessary. For example, a magnetic disk 1011, an optical disk 1012, a flexibil disk 1013, or a semiconductor memory 1014 is appropriately mounted, and a computer / computer read from them is read. The program is installed in the storage unit 1008 as necessary.

  FIG. 3 is a diagram for explaining the specific contents of the files included in the metapackage and the metapackage generation process by the metapackage developer. The main component file 20 of the meta package includes a package selection 20a, a UI definition 20b, a template definition 20c, and a specification definition 20d. The package selection 20a indicates a set of packages to be installed on the cluster node. The template definition 20c is a template for generating a setting file for the automatic installer, and describes setting information for each software. This template definition 20c is a database (registry) in which setting information of the system and application software is recorded. The UI definition 20b is used to customize the setting information described in the template in the meta package. In the specification definition 20d, specifications used for the metapackage are defined.

  These are given as inputs of the metapackage generation tool 10 as a support program generation program. The software dependency information database 30 is a database in which dependency information of each software included in the metapackage is accumulated. The metapackage generation tool 10 passes the query to the software dependency information database 30 and receives the response. Then, the metapackage generation tool 10 generates a metapackage based on these pieces of information.

  Next, a method for generating a metapackage in the present embodiment will be described in detail. In the present embodiment, a mechanism for detecting whether or not a system constructed using a metapackage is broken is added to the metapackage even after installation in the cluster. Specifically, an IDS setting file that is an input of an external inspection program (hereinafter referred to as an intrusion detection system (IDS)) is generated.

  Here, the IDS setting file according to the present embodiment generates one IDS setting file at a meta package generation stage and an operation stage when the meta package generates an installer installation setting, that is, at each stage. In this specification, the IDS setting file generated in the metapackage generation stage and included in the metapackage is referred to as a first IDS setting file as the first inspection information file, and is generated in the metapackage operation stage. The setting file is referred to as a second IDS setting file as a second inspection information file.

  That is, in the present embodiment, first, the meta package generation tool 10 includes a package group (package selection 20a) to be introduced into the cluster by the meta package among the information (file 20) input for generating the meta package. To automatically generate a first IDS setting file. The IDS can periodically check whether the software itself installed in the cluster is not broken based on the first IDS setting file.

  Next, in the operation of generating an installation setting based on a setting template included in the meta package and a user input, the second IDS setting file is automatically generated using the installation setting. The IDS can periodically check whether the software settings introduced to the cluster by the second IDS setting file are not destroyed after the installation.

  First, a method for generating the first IDS setting file will be described. The first IDS setting file is generated when the meta package is generated. FIG. 4 is a schematic diagram showing details of the metapackage generation tool. The metapackage generation tool 10 includes a package data extraction unit 11, an IDS setting file generation unit 12, and a metapackage generation unit 13. Note that the user (metapackage developer) uses this metapackage generation tool 10 to generate a metapackage.

  Here, in the present embodiment, based on the package selection 20a used for generating the metapackage, it is checked whether or not the selected package (software) has been correctly installed after installation. A definition file (IDS setting file) is generated simultaneously with the meta package by the meta package generation tool 10. The generated first IDS setting file is included in the metapackage by the metapackage generation unit (metapackage build tool) 13. As will be described later, the metapackage according to the present embodiment has a function of generating an installation setting of software to be installed in a cluster and distributing the first IDS setting file to each cluster of installation destinations. In each class, IDS is installed in advance, and the distributed IDS setting file serves as an input for IDS, and detects intrusion into the cluster after package installation.

  The package information database 50 is a database in which a file list 11a of files constituting the software included in the package selection 20a and other software and a property 11b of each file are accumulated.

  The package data extraction unit 11 extracts, from the package information database 50, the file list 11a of the files constituting the software included in the package selection 20a and the property 11b of each file. FIG. 5 is a diagram illustrating an example of package data extraction. FIG. 5 shows an example of package data extraction of the zip software package. The extracted information includes a file list 11a and a property 11b. The property 11b includes protection information 111, a file size 112, and a time stamp 113.

  The IDS setting file generation unit 12 uses a first IDS for checking whether the software itself (package configuration) is broken from the file list 11a extracted by the package data extraction unit 11 and the property 11b of each file. A setting file 12a is generated. That is, the IDS checks, for example, the time stamp 113 of the property 11b described in the first IDS setting file 12a. If the time stamp has been changed, the IDS determines that the file has been illegally accessed. .

  The meta package generation unit 13 includes a package component including a first IDS setting file 12a generated by the IDS setting file generation unit 12, a package selection 20a, a UI definition 20b, a template definition 20c, and a meta package specification definition 20d. The file 20 is supplied, and a metapackage (metapackage main body) 40 is generated from these components.

  Next, the operation of the metapackage generation tool 10 will be described. FIG. 6 is a flowchart showing a metapackage generation method. First, the metapackage developer creates a package selection 20a to be included in the metapackage. For example, in the case of an Office metapackage, this package selection 20a indicates a list of a series of software such as “Word”, “Excel”,.

  Next, the package selection 20a is supplied to the package data extraction unit 11 (step S1). The package data extraction unit 11 refers to the package information database 50 (step S2), and extracts the file list 11a included in the package and the property 11b for each file. These obtained data are supplied to the IDS setting file generation unit 12, and the first IDS setting file 12a is generated based on the file list 11a and the property 11b for each file (step S3).

  As described above, the metapackage generation unit 13 generates the metapackage 40 from the component file 20 having the package selection 20a, the UI definition 20b, the template definition 20c, and the specification definition 20d, and the information from the software dependence information database 30. Is generated (steps S4 and S5). Here, the meta package generation unit 13 is also supplied with the first IDS setting file 12a, and the meta package 40 generated by the meta package generation unit 13 includes the first IDS setting file 12a. In this way, an IDS setting file for checking whether or not the software installed in the cluster has been destroyed is automatically generated together with the metapackage and included in the metapackage.

  The first IDS setting file 12a automatically generated here is for checking whether the file included in the metapackage or the protection information has been changed. That is, only information that can be grasped statically at the time of metapackage development is used.

  Next, a method for generating the second IDS setting file will be described. The first IDS setting file is generated when the installation setting of the meta package is generated. FIG. 7 is a diagram for explaining a part of the processing of the metapackage, and is a diagram for explaining the installation setting and IDS setting file (second IDS setting file) generation function 60. FIG. 8 is a flowchart showing a method for generating the second IDS setting file.

  The metapackage generated as described above includes an installation setting generation unit 61 and an IDS setting file generation unit 62. The installation setting generation unit 61 generates an installation setting 61a from the template definition 20c and the customization information 70. This file is input to the automatic installer 80, and automatic installation is performed according to this installation setting.

  FIG. 9A is a diagram illustrating an example of a template definition, FIG. 9B is a diagram illustrating an example of customization information, and FIG. 9C is a diagram illustrating an example of installation settings. As shown in FIG. 9A, a part of the template definition file is blank 91, and is configured so that a user's desired value or the like (see FIG. 9B) can be set in this part. In this way, the blank 91 of the template definition 20c is filled with the customization information 70, and the installation setting 61a shown in FIG. 9C is generated.

  At this time, the customization information 70 can be input according to the UI displayed by the metapackage (steps S11 and S12). When the user inputs desired setting items through the UI, a user-specific installation setting 61a is generated (step S13). Specific examples of the customization information 70 include user information, serial number, installation destination directory information, and the like.

  This installation setting 61a is not only an input of the automatic installer 80 but also an input of the IDS setting file generation unit 62 in the present embodiment. The IDS setting file generation unit 62 extracts the customization information 70 and the like from the installation setting 61a and generates an IDS setting file (second IDS setting file) 62a (step S14). That is, for example, the customization information 70 that is a user-specific setting included in the installation setting 61a, and the IDS setting file 62a including the installed file size and checksum are generated. The IDS setting file 62a is distributed to each cluster in which the automatic installer 80 performs automatic installation through the transmission means (not shown) together with the first IDS setting file 12a described above. The distributed IDS setting files 12a and 62a are input to the IDS 90 and used for inspection and the like.

  Since the customization information 70 used for the second IDS setting file 62a is user-specific setting information, the IDS 90 can check this information and determine that there has been unauthorized access if it has been changed. The second IDS setting file 62a generated here is for checking whether or not the item customized by the user is broken, and uses information dynamically set at the time of installing the meta package. It has become. That is, it is different from the above-described setting file (first IDS setting file) 12a.

  The IDS 90 can manage the installed files using the IDS setting file 12a and the IDS setting file 62a generated as described above, even after the metapackage is installed. The IDS 90 may be software included in the meta package, or may be installed in each cluster in advance. The IDS setting files 12a and 62a are distributed so that the IDS 90 is input to each cluster when the automatic installer 80 installs the cluster.

  Here, in the present embodiment, two types of IDS setting files 12 a and 62 a are supplied to the IDS 90. The IDS setting file 12a is based on information specific to the metapackage extracted at the time of metapackage development. By checking this, it is possible to check whether the metapackage configuration itself is broken. On the other hand, the IDS setting file 62a is obtained by extracting the customization information 70 input by the user at the time of developing the metapackage. By checking this, it is possible to check whether the user setting has been changed. it can.

  Further, the operation method (detection method) of the IDS 90 may be turned off when it is not necessary to check, for example, when the risk is small or the environment is not likely to be destroyed in order to prevent a decrease in calculation capacity in the cluster. . Further, the IDS monitoring target files may be all software (files) installed in the cluster, or only important files. If the priority of the monitoring operation is lowered, even if the IDS is activated, the operation of the entire cluster is not affected.

  It should be noted that the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the present invention. For example, in the present embodiment, the automatic generation of the IDS setting file for the cluster has been described by taking the meta package as an example, but the present invention is not limited to this. In other words, for example, a setup CD for a notebook PC or software (installer) for setting up a plurality of programs together can be used to automatically generate an IDS setting file as well as a meta package as long as it has package information. It is.

  Further, although an example in which an IDS setting file is automatically generated in both the metapackage development process and the installation process has been described, only one of the IDS setting files may be used as necessary.

  Furthermore, in the above-described embodiment, the process of automatically generating the IDS setting file has been described by causing the CPU to execute the computer program. In this case, the computer program is stored on the recording medium. It can also be provided by recording, or can be provided by transmission via the Internet or other transmission media.

It is a schematic diagram which shows the installation system for installing a cluster automatically. It is a figure which shows the hardware constitutions of a general installation server. It is a figure explaining the specific content of the file contained in a metapackage, and the production | generation process of the metapackage by a metapackage developer. It is a schematic diagram which shows the detail of the metapackage production | generation tool concerning embodiment of this invention. It is a figure which shows the example of package data extraction concerning embodiment of this invention. It is a flowchart which shows the production | generation method of the metapackage concerning embodiment of this invention. It is a figure explaining a part of meta package process concerning embodiment of this invention, Comprising: It is a figure explaining the installation setting and IDS setting file (2nd IDS setting file) production | generation function 60. FIG. It is a flowchart which shows the production | generation method of the 2nd IDS setting file concerning embodiment of this invention. (A) is a figure which shows an example of a template definition, (b) is a figure which shows an example of customization information, (c) is a figure which shows an example of installation setting. It is a figure which shows the structure of a general clustering system (henceforth a cluster). It is a figure explaining a general cluster automatic installer. It is a figure which shows the general software stack (hierarchical structure of software) automatically installed on each calculation node by an automatic installer.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Installation system 2 Meta package server 3 Installation server 3a Automatic installer 4 Cluster 5 Package manager 6 Meta package developer 10 Meta package generation tool 11 Package data extraction part 11a File list 11b Property 12 Setting file generation part 12a Setting file 13 Meta package generation Unit 20 Component file 20a Package selection 20b UI definition 20c Template definition 20d Specification definition 30 Software dependent information database 40 Meta package 50 Package information database 60 Generation function 61 Installation setting generation unit 61a Installation setting 62 Setting file generation unit 62a Setting file 70 Customization Information 80 Automatic installer 91 Blank 100 Cluster 101a Node 102 Computing node 103 Private network 104 Network 105 Component 111 Protection information 112 File size 113 Time stamp 201 Installation setting 202 Installation server 203 Cluster 204 Computing node 1004 Bus 1005 Input / output interface 1006 Input unit 1007 Output unit 1008 Storage unit 1009 Communication unit 1010 Drive 1011 Magnetic disk 1012 Optical disk 1013 Flexivir disk 1014 Semiconductor memory

Claims (20)

A support program generation program for causing a computer to execute an operation of generating a support program that supports automatic installation of a plurality of software and software management after installation for each of one or a plurality of computers,
A file information extraction step for extracting file information constituting the plurality of software;
Based on the file information, a first inspection information file generating step for generating a first inspection information file in which first inspection information used for inspection after the plurality of software is automatically installed in a computer is described;
A support program generating step for generating the support program based on a template in which a list of the plurality of software and setting information of the plurality of software is described;
In the support program generation step, the support program having a function of distributing the first inspection information file to installation destinations of the plurality of software is generated. 2. The support program generation according to claim 1, wherein in the file information extraction step, the file information is extracted based on a list of the plurality of software with reference to an information database in which file information of the software is stored. program. In the support program generation step, the support program is generated based on a list of the plurality of software, the template, a user interface definition for customizing setting information described in the template, and a predetermined specification definition. The support program generation program according to claim 1 or 2, characterized in that The support program generation program according to any one of claims 1 to 3, wherein the first inspection information includes properties and / or a file list of files constituting the plurality of software. A support program for causing a computer to execute an operation of generating and distributing a file for supporting automatic installation of a plurality of software and software management after the installation for each of one or a plurality of computers,
An installation setting generation step for generating an installation setting for automatically installing the plurality of software from a template in which setting information of the plurality of software is described and customization information input from the outside;
A second inspection for generating a second inspection information file in which second inspection information used for inspection after the plurality of software is automatically installed on the computer is generated based on the installation setting generated in the installation setting generation step. A support program having an information file generation step. 6. The support program according to claim 5, wherein, in the installation setting generation step, a wizard is activated and the installation setting is generated by a user inputting customization information in an interactive window. The support program according to claim 6, wherein, in the second inspection information file generation step, the second inspection information file is generated based on customization information included in the installation setting. The support program according to claim 6 or 7, wherein the second inspection information includes at least one of user information, serial number, and installation destination directory information. A support program for causing a computer to execute an operation of generating and distributing a file for supporting automatic installation of a plurality of software and software management after the installation for each of one or a plurality of computers,
An installation setting generation step for generating an installation setting for automatically installing the plurality of software;
A support program comprising a distribution step of distributing a first inspection information file in which first inspection information used for inspection after the plurality of software is automatically installed in a computer is distributed to installation destinations of the plurality of software. The support program according to claim 9, wherein in the installation setting generation step, the installation setting is generated from a template in which setting information of the plurality of software is described and customization information input from the outside. A file generation step of generating a second inspection information file in which second inspection information used for inspection after automatically installing a plurality of software on a computer is generated based on the installation setting generated in the installation setting generation step; In addition,
The support program according to claim 9 or 10, wherein in the distribution step, the first and second inspection information files are distributed. A support program generated based on a template in which a list of the plurality of software and setting information of the plurality of software is described,
The support program according to any one of claims 9 to 11, wherein the first examination information file is generated simultaneously with the support program based on file information constituting the plurality of software. The support program according to any one of claims 9 to 12, wherein the first inspection information includes a property and / or a file list of files constituting the plurality of software. The support program according to any one of claims 11 to 13, wherein the second inspection information includes at least one of user information, serial number, and directory information of an installation destination. A support program generation method for generating a support program for supporting automatic installation of a plurality of software and software management after the installation on each of one or a plurality of computers,
A file information extraction step for extracting file information constituting the plurality of software;
Based on the file information, a first inspection information file generating step for generating a first inspection information file in which first inspection information used for inspection after the plurality of software is automatically installed in a computer is described;
A support program generating step for generating the support program based on a template in which a list of the plurality of software and setting information of the plurality of software is described;
In the support program generation step, the support program having a function of distributing the first inspection information file to installation destinations of the plurality of software is generated. A file generation / distribution method for generating / distributing a file for supporting automatic installation of a plurality of software and management of software after installation for each of one or a plurality of computers,
An installation setting generation step for generating an installation setting for automatically installing the plurality of software;
A file generation / distribution method comprising a distribution step of distributing a first inspection information file in which first inspection information used for inspection after the plurality of software is automatically installed on a computer is distributed to installation destinations of the plurality of software. A file generation / distribution method for generating / distributing a file for supporting automatic installation of a plurality of software and management of software after installation for each of one or a plurality of computers,
An installation setting generation step for generating an installation setting for automatically installing the plurality of software from a template in which setting information of the plurality of software is described and customization information input from the outside;
A file generation step for generating a second inspection information file in which second inspection information used for inspection after the plurality of softwares are automatically installed on the computer based on the installation setting generated in the installation setting generation step A file generation / distribution method. An installation server for automatically installing a plurality of software on each of a plurality of computers,
File generation / distribution means for generating / distributing a file for supporting the installation of the plurality of software and management after the installation;
An automatic installer for automatically installing the plurality of software,
The file generation / distribution means includes:
Installation setting generation means for generating an installation setting for automatically installing the plurality of software;
Distribution means for distributing a first inspection information file in which first inspection information used for inspection after the plurality of software is automatically installed in the computer is described to the plurality of computers;
The automatic installer is an installation server for automatically installing a plurality of software on each of the plurality of computers according to the installation setting. The installation server according to claim 18, wherein the installation setting generation unit generates an installation setting from a template in which setting information of the plurality of software is described and customization information input from the outside. The file generation / distribution means includes:
File generation means for generating a second inspection information file in which second inspection information used for inspection after automatic installation of a plurality of software on a computer is based on the installation setting generated by the installation setting generation means In addition,
The installation server according to claim 18 or 19, wherein the distribution unit distributes the first and second inspection information files to the plurality of computers.

Images