Standard inspection method and device for installation configuration, electronic equipment and storage medium

Abstract

The invention discloses an installation configuration specification inspection method and device, electronic equipment and a storage medium, and the method and device are applied to the electronic equipment and are used for inspecting installation configuration specifications of software products of a production system. The method specifically comprises the following steps: creating a standard inspection task based on inspection range characteristics, production version baseline information and VT environment ledger information of a software product of a production system; and executing the specification inspection task, and sending an inspection script generated according to the product specification inspection rule of the software product to the to-be-inspected deployment unit server, so that the to-be-inspected deployment unit server executes the inspection script to generate specification inspection result information. According to the method, a flexible parameterization design mode is used, the automatic inspection function of the installation configuration specification of the software product is achieved, and therefore it can be guaranteed that the inspection efficiency of the product specification is greatly improved, and the inspection quality is greatly improved.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and more specifically, to a method, device, electronic device, and storage medium for verifying the installation and configuration specifications. Background Art

[0002] With the development and wide application of middleware and database software products, more and more production systems are applying these software products. In order to strengthen the standardized management of software products and guide the project team to configure and use software products, the product managers of each software product will summarize the deployment and configuration experience to form a product installation and configuration specification document for the recommended version baseline. And according to the latest official vulnerability situation on a regular basis, notify the project team to perform product upgrades to timely repair security vulnerabilities and product defects.

[0003] Currently, there is a lack of verification of the installation and configuration specifications of application software in the production system. For the latest official vulnerability situation, it cannot be guaranteed that the application system can perform product upgrades in a timely manner to repair security vulnerabilities and product defects. Summary of the Invention

[0004] In view of this, the present application provides a method, device, electronic device, and storage medium for verifying the installation and configuration specifications, which are used to automatically verify the installation and configuration specifications of application software in the production system, so as to ensure that the application system can perform product upgrades in a timely manner to repair security vulnerabilities and product defects.

[0005] In order to achieve the above object, the following solutions are proposed:

[0006] A method for verifying the installation and configuration specifications, which is applied to an electronic device and is used to verify the installation and configuration specifications of software products in the production system. The specification verification method includes the steps of:

[0007] Creating a specification verification task based on the inspection scope characteristics, production version baseline information, and VT environment ledger information of the software products in the production system;

[0008] Executing the specification verification task, and sending the inspection script generated according to the product specification verification rules of the software product to the server of the deployment unit to be inspected, so that the server of the deployment unit to be inspected executes the inspection script to generate specification verification result information.

[0009] Optionally, the step of creating a specification verification task based on the inspection scope characteristics, production version baseline information, and VT environment ledger information of the software products in the production system includes the steps of:

[0010] Extract the inspection scope features and perform parametric configuration, determine the system scope of product inspection according to the inspection scope features, regularly receive the production version baseline information, query the VT environment ledger information according to the system scope, and obtain the system server information in the VT environment ledger information;

[0011] Screen the deployment unit name and deployment unit type information of the software product in the inspection scope features according to the production version baseline information, and create the specification inspection task according to the name of the software product, the deployment unit name and the deployment unit type information.

[0012] Optionally, when executing the specification inspection task, sending the inspection script generated according to the product specification inspection rules of the software product to the to-be-inspected deployment unit server, so that the to-be-inspected deployment unit server executes the inspection script to generate specification inspection result information, including the steps:

[0013] Obtain the installation configuration specification of the software product, and sort out the installation configuration specification to form the product specification inspection rules;

[0014] Regularly start the specification inspection task, send the inspection script to the to-be-inspected deployment unit service request, so that the to-be-inspected deployment unit server executes the inspection script to generate specification inspection result information.

[0015] Optionally, it further includes the steps:

[0016] Display the specification inspection result information, and receive the review information of the reviewer. When the inspection passed information is received, control to stop executing the specification inspection task.

[0017] Optionally, it further includes the steps:

[0018] Update the inspection review status of the software product when the review information of the software product is passed.

[0019] A specification inspection device for installation configuration, which is applied to an electronic device and is used to inspect the installation configuration specification of a software product of a production system. The specification inspection device includes:

[0020] A task creation module, configured to create a specification inspection task based on the inspection scope features, production version baseline information and VT environment ledger information of the software product of the production system;

[0021] A task execution module, configured to execute the specification inspection task, send the inspection script generated according to the product specification inspection rules of the software product to the to-be-inspected deployment unit server, so that the to-be-inspected deployment unit server executes the inspection script to generate specification inspection result information.

[0022] Optionally, it further includes:

[0023] An appeal review module, configured to display the specification inspection result information and receive the review information of the reviewer, and control to stop executing the specification inspection task when the inspection passed information is received.

[0024] Optionally, it further includes:

[0025] A status update module, configured to update the inspection review status of the software product when the review information of the software product is passed.

[0026] An electronic device, the electronic device includes at least one processor and a memory connected to the processor, wherein:

[0027] The memory is used to store computer programs or instructions;

[0028] The processor is used to execute the computer programs or instructions, so that the electronic device implements the specification inspection method as described above.

[0029] A computer-readable storage medium, applied to an electronic device, the storage medium carries one or more computer programs, and the one or more computer programs can be executed by the electronic device, so that the electronic device can implement the specification inspection method as described above.

[0030] As can be seen from the above technical solutions, the present application discloses a specification inspection method, device, electronic device and storage medium for installation and configuration. The method and device are applied to an electronic device and are used to inspect the installation and configuration specifications of software products in a production system. Specifically, a specification inspection task is created based on the inspection scope characteristics of the software products in the production system, the production version baseline information and the VT environment ledger information; the specification inspection task is executed, and the inspection script generated according to the product specification inspection rules of the software product is sent to the to-be-inspected deployment unit server, so that the to-be-inspected deployment unit server executes the inspection script and generates specification inspection result information. The present application uses a flexible parameterized design pattern to achieve the automated inspection function of the installation and configuration specifications of software products, thereby being able to ensure a great improvement in the product specification inspection efficiency and the inspection quality. Description of the Drawings

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0032] Figure 1 Flow chart of a specification inspection method for installation and configuration of an embodiment of the present application;

[0033] Figure 2 Flow chart of another specification inspection method for installation and configuration of an embodiment of the present application;

[0034] Figure 3 Flow chart of yet another specification inspection method for installation and configuration of an embodiment of the present application;

[0035] Figure 4 Block diagram of a specification inspection device for installation and configuration of an embodiment of the present application;

[0036] Figure 5 Block diagram of another specification inspection device for installation and configuration of an embodiment of the present application;

[0037] Figure 6 Block diagram of yet another specification inspection device for installation and configuration of an embodiment of the present application;

[0038] Figure 7 Block diagram of an electronic device of an embodiment of the present application. Detailed implementation manners

[0039] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0040] The present application realizes the specification inspection of the software products of the production system in the VT environment through automated design. It can maximize the automation of determining the inspection scope, executing the inspection, and recording the inspection results, which can ensure that the software products applied in the production system meet the installation and configuration specifications and version requirements, and complete the work with extremely high inspection efficiency and quality at extremely low labor costs, and the information assets can also be properly preserved. Among them, the VT environment refers to the environment for pre-production inspection and testing of the development and delivery version, and the version of this environment should be consistent with the production environment; the specification inspection refers to the control process of inspecting the implementation of the software product installation and configuration specification requirements in the production system, mainly inspecting whether the software products used in the production system meet the current version requirements, whether the installation and configuration meet the specifications, and whether there are unrectified inspection problems.

[0041] Figure 1 Flow chart of a specification inspection method for installation and configuration of an embodiment of the present application.

[0042] Such as Figure 1As shown in the figure, this embodiment provides a method for verifying the installation and configuration specifications, which is applied to an electronic device and used to verify the installation and configuration specifications of software products in a production system. The electronic device can be understood as a computer, server, or cloud platform with data calculation and information processing capabilities. The specific steps of this specification verification method are as follows:

[0043] S1. Create a specification verification task based on the inspection scope characteristics of the software products in the production system, the production version baseline information, and the VT environment ledger information.

[0044] This operation creates the corresponding specification verification task by obtaining the inspection scope characteristics of the software products in the production system, the production version baseline information, and the VT environment ledger information. The specific process includes the following steps:

[0045] First, extract the inspection scope characteristics of the software products in the production system, and perform parametric configuration on the extracted inspection scope characteristics to obtain parametric inspection scope characteristics. As the specification verification work progresses in depth and the software products of each production system are adjusted and changed, the relevant information of the software products in the production system can be flexibly maintained and updated. And by receiving the audited and released production version baseline information regularly in the background, automatically judge the system scope of software product inspection according to the extracted inspection scope characteristics, and query the VT environment ledger information to obtain the system server information within the inspection scope.

[0046] The above-mentioned extracted inspection scope characteristics include the system English name, deployment unit name, deployment unit type (including AP application server, DB database server, WB website server), the development unit to which the system belongs, and the name of the software product applied. The obtained production version baseline information includes the production date, production type, system English name, and version delivery status. The collected VT environment ledger information includes information such as the system English name, deployment unit name, deployment unit type, server managed IP, server usage status, and version inspection.

[0047] Then, screen the name of the software product applied, the name of the deployment unit where the product is installed, the deployment unit type information, etc. in the inspection scope characteristics according to the system name of the current production version baseline information. If the system does not apply the software products within the specification verification scope, update the software product inspection task status in the version baseline information to not applied. If the system applies the software products, then query the server managed IP in the normal usage status in the VT environment ledger information according to the screened system name, deployment unit name, and deployment unit type. Create a specification verification task according to the screened production date, production system name, deployment unit name, VT environment server managed IP, name of the software product applied, etc. information.

[0048] S2. Execute the specification inspection task and send the inspection script generated according to the product specification inspection rules of the software product to the server of the deployment unit to be inspected.

[0049] After obtaining the specification inspection task created according to the above inspection scope characteristics, production version baseline information, and VT environment ledger information, execute the specification inspection task. By executing this task, send the inspection script generated according to the product specification inspection rules of the software product to the server of the deployment unit to be inspected. So that the server of the deployment unit to be inspected executes this inspection script, thereby generating specification inspection result information. The specific process is as follows:

[0050] First, after the installation and configuration specification of any software product to be inspected is released, obtain the installation and configuration specification of the corresponding software product, and sort out this installation and configuration specification to form product specification inspection rules. The product specification inspection rules are divided into two levels: critical and warning. For inspection problems at the critical level, the project team must rectify them. For inspection problems at the warning level, the project team is required to analyze and confirm them, and rectification is not required.

[0051] Then, develop verification scripts in languages such as Python, Shell, and Perl according to the product specification inspection rules, and perform parametric configuration of the product specification inspection rules and inspection scripts during inspection. With the version upgrade and optimization of the software product and the adjustment of the installation and configuration specification, the inspection rules and scripts can be flexibly updated and maintained. The background of the specification inspection tool judges to start the specification inspection task regularly after the production system version is installed and deployed, automatically send the inspection script to the server of the deployment unit to be inspected, execute the inspection script to collect the software product configuration information, and judge to generate the specification inspection result information corresponding to the rules.

[0052] After the user obtains this specification inspection result information, update the status of the product specification inspection task of the production system according to this information: if all inspection rules of the software product meet the specifications, update the status of the software product specification inspection task of the production system to passed; if only warning-level rules of the software product do not meet the specifications, update the status of the software product specification inspection task of the production system to be confirmed; if any critical-level inspection rule of the software product does not meet the specifications, update the status of the software product inspection task of the production system to be rectified. If the execution of the inspection script fails and no inspection result is generated, update the status of the software product inspection task of the production system to failed.

[0053] As can be seen from the above technical solution, this embodiment provides a method for verifying installation and configuration specifications, which is applied to an electronic device and used to verify the installation and configuration specifications of software products in a production system. Specifically, a specification verification task is created based on the verification scope characteristics of the software products in the production system, the production version baseline information, and the VT environment ledger information; the specification verification task is executed, and the verification script generated according to the product specification verification rules of the software product is sent to the server of the deployment unit to be inspected, so that the server of the deployment unit to be inspected executes the verification script and generates specification verification result information. This application uses a flexible parameterized design pattern to achieve the automated verification function of the installation and configuration specifications of software products, thereby ensuring a significant improvement in the efficiency and quality of product specification verification.

[0054] In another specific implementation manner of this application, the following steps are further included, as Figure 2 shown.

[0055] S3. Display the specification verification result information and receive the review information.

[0056] Users can view the specification verification result information through the corresponding problem appeal interface. For example, the verification information that does not conform to the specification verification rules included in the product specification verification tasks in the to-be-rectified status includes information such as production date, software product name, verification unit name, affiliated rules, rule level, problem content, discovery time, problem status, appeal record, etc. The project team can analyze the cause of the problem based on information such as the problem content and the affiliated rules, determine a solution, and carry out rectification or submit an appeal for the cause of the problem. For the problems of product specification verification rules that have been rectified, there is no need to submit an appeal; the record status of the rule problems submitted for appeal becomes pending review (appealing).

[0057] Through the regularly executed specification verification task, the verification script can be reissued to the problem verification unit to conduct product specification verification again. If the verification problems that do not conform to the rules do not reappear, the status of the rule problems is automatically updated to rectified; if the verification problems reappear, the latest occurrence time of the rule problems is updated to the current execution date, and the problem status remains unchanged, still being to-be-rectified. For the verification problems submitted for appeal by the project team, the personnel in the product specification review position will manually confirm and review the cause of the problem. If the review is passed, the status of the verification problem becomes false alarm (review passed); otherwise, if the review fails, the status of the verification problem becomes to-be-rectified (appeal rejected).

[0058] When all the rule verification results included in the software product specification verification task are passed, false alarm (review passed), or rectified, the status of the software product specification verification task is passed. The automatic verification module of the specification verification tool stops regularly executing the software product specification verification task.

[0059] In another specific embodiment of the present application, the following steps may further be included, as Figure 3 shown.

[0060] S4. When the audit information of the software product is passed, update the inspection and audit status of the software product.

[0061] By periodically executing the specification inspection task of the software product, when the specification inspection task status of all software products applied in the production system is passed, update the software product specification inspection and audit status of the production system to passed. Otherwise, the software product specification inspection and audit of the production system fails. The update system audit status module will periodically execute the verification of the specification inspection task status of all software products applied in the production system before the production conclusion is issued. When the status of all software product specification inspection tasks is passed, update the software product specification inspection and audit status of the production system to passed.

[0062] At the time point when the production inspection conclusion is required to be issued according to the inspection specification, automatically synchronize the software product specification inspection and audit conclusion of the production system to the production version baseline of the production version console.

[0063] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and computer instructions.

[0064] Although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous.

[0065] It should be understood that the various steps recorded in the method embodiments of the present disclosure may be executed in a different order and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.

[0066] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or combinations thereof. Such programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the C language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, execute as a stand-alone software package, execute partially on the user's computer and partially on a remote computer, or execute entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer.

[0067] Figure 4 The block diagram of a specification inspection device for an installation and configuration according to an embodiment of the present application. As Figure 4 shown, an embodiment provides a specification inspection device for an installation and configuration. The device is applied to an electronic device and is used to inspect the installation and configuration specifications of software products of a production system. The electronic device can be understood as a computer, a server, or a cloud platform with data calculation and information processing capabilities. The specification inspection device specifically includes a task creation module 10 and a task execution module 20.

[0068] The task creation module is used to create a specification inspection task based on the inspection scope characteristics of the software product of the production system, the production version baseline information, and the VT environment ledger information.

[0069] This operation realizes the creation of a corresponding specification inspection task by obtaining the inspection scope characteristics of the software product of the production system, the production version baseline information, and the VT environment ledger information. The specific process includes the following steps:

[0070] First, in the identification and determination of the inspection scope module, the inspection scope characteristics of the software product of the production system are extracted, and the extracted software product inspection scope characteristics are parametrically configured to obtain parametric inspection scope characteristics. With the in-depth development of the specification inspection work and the adjustment and change of application software products of each production system, the relevant information of the application software products of the production system can be flexibly maintained and updated. Regularly receive the audited and released production version baseline information through the inspection tool system background to automatically determine the system scope of software product inspection according to the extracted inspection scope characteristics, and query the VT environment ledger information to obtain the system server information within the inspection scope.

[0071] The extracted inspection scope features above include: the English name of the system, the name of the deployment unit, the type of the deployment unit (including AP application server, DB database server, WB website server), the development unit to which the system belongs, and the name of the software product applied. The obtained production version baseline information includes: the production date, the production type, the English name of the system, and the version delivery status. The collected VT environment ledger information includes: the English name of the system, the name of the deployment unit, the type of the deployment unit, the IP of the server under custody, the usage status of the server, and information such as whether it is used for version inspection, etc.

[0072] After obtaining and updating the production version baseline information with the completed version baseline status as reviewed and released, the module for identifying and determining the inspection scope is triggered. Then, according to the system name in the current production version baseline information, the name of the software product applied and the name of the deployment unit where the product is installed, the type information of the deployment unit, etc. are screened from the inspection scope feature information. If the system does not apply the software products within the specified inspection scope, the software product inspection task status in the version baseline information is updated to not applied. If the system applies software products, then according to the screened system name, deployment unit name, and deployment unit type, the IP of the server under custody in the normal usage status is queried from the VT environment ledger information. According to the screened production date, production system name, deployment unit name, VT environment server IP under custody, the name of the software product applied, etc., a specification inspection task is automatically created.

[0073] The task execution module is used to execute the specification inspection task and send the inspection script generated according to the product specification inspection rules of the software product to the server of the deployment unit to be inspected.

[0074] After obtaining the specification inspection task created based on the above inspection scope features, production version baseline information, and VT environment ledger information, the specification inspection task is executed. By executing this task, the inspection script generated according to the product specification inspection rules of the software product is sent to the server of the deployment unit to be inspected. So that the server of the deployment unit to be inspected can execute this inspection script, thereby generating specification inspection result information. The specific process is described as follows:

[0075] First, after the installation and configuration specification of any software product to be inspected is released, the installation and configuration specification of the corresponding software product is obtained and sorted out to form product specification inspection rules. The product specification inspection rules are divided into two levels: critical and warning. For the inspection problems at the critical level, the project team must make rectifications. For the inspection problems at the warning level, the project team is required to analyze and confirm, and rectification is not required necessarily.

[0076] Then, according to the product specification inspection rules, check scripts in languages such as Python, Shell, and Perl are developed. During inspection, the product specification inspection rules and the inspection scripts are parametrically configured. With the version upgrade and optimization of software products and the adjustment of installation and configuration specifications, the inspection rules and scripts can be flexibly updated and maintained. The specification inspection tool's background determines to start the specification inspection task regularly after the production system version is installed and deployed, automatically sends the inspection script to the server of the deployment unit to be inspected, executes the inspection script to collect the software product configuration information, and determines and generates the specification inspection result information corresponding to the rules.

[0077] After the user obtains the specification inspection result information, the status of the product specification inspection task of the production system is updated according to this information: if all inspection rules of the software product meet the specifications, the status of the software product specification inspection task of the production system is updated to passed; if only warning-level rules of the software product do not meet the specifications, the status of the software product specification inspection task of the production system is updated to be confirmed; if any severe-level inspection rule of the software product does not meet the specifications, the status of the software product inspection task of the production system is updated to be rectified. If the execution of the inspection script fails and no inspection result is generated, the status of the software product inspection task of the production system is updated to failed.

[0078] As can be seen from the above technical solution, this embodiment provides a specification inspection device for installation and configuration, which is applied to an electronic device and is used to inspect the installation and configuration specifications of software products in the production system. Specifically, a specification inspection task is created based on the inspection scope characteristics of the software products in the production system, the production version baseline information, and the VT environment ledger information; the specification inspection task is executed, and the inspection script generated according to the product specification inspection rules of the software product is sent to the server of the deployment unit to be inspected, so that the server of the deployment unit to be inspected executes the inspection script and generates the specification inspection result information. This application uses a flexible parametric design pattern to realize the automatic inspection function of the installation and configuration specifications of software products, thereby ensuring a significant improvement in the product specification inspection efficiency and the inspection quality.

[0079] In another specific implementation manner of this application, an appeal review module 30 is further included, as Figure 5 shown.

[0080] The appeal review module is used to display the specification inspection result information and receive the review information.

[0081] Users can view the specification inspection result information through the corresponding problem appeal interface. For example, the inspection information that does not conform to the specification inspection rules included in the product specification inspection tasks in the to-be-rectified status includes information such as production date, software product name, inspection unit name, affiliated rules, rule level, problem content, discovery time, problem status, appeal records, etc. The project team can analyze the cause of the problem based on information such as the problem content and the affiliated rules, determine the solution, and carry out rectification or submit an appeal for the cause of the problem. For the problems of product specification inspection rules that have been rectified, there is no need to submit an appeal; the record status of the rule problems submitted for appeal becomes pending review (appealing).

[0082] Through the regularly executed specification inspection tasks, the inspection script can be reissued to the problem inspection unit to conduct product specification inspection again. If the inspection problems that do not conform to the rules do not reappear, the status of the rule problems will be automatically updated to rectified; if the inspection problems reappear, the latest occurrence time of the rule problems will be updated to the current execution date, and the problem status remains unchanged, still being to-be-rectified. For the inspection problems submitted for appeal by the project team, the personnel in the product specification review position will manually confirm and review the cause of the problem. If the review is passed, the status of the inspection problem becomes misreported (review passed); otherwise, if the review fails, the status of the inspection problem becomes to-be-rectified (appeal rejected).

[0083] When all the rule inspection results included in the software product specification inspection tasks are passed, misreported (review passed), or rectified, the status of the software product specification inspection task is passed. The automatic inspection module of the specification inspection tool will stop regularly executing the software product specification inspection task.

[0084] In another specific implementation manner of the present application, a status update module 40 may also be included, as Figure 6 shown.

[0085] The status update module is used to update the inspection review status of the software product when the review information of the software product is passed.

[0086] By regularly executing the verification of the software product specification inspection tasks, when the statuses of the specification inspection tasks of all software products applied in the production system are passed, the software product specification inspection review status of the production system is updated to passed. Otherwise, the software product specification inspection review of the production system fails. The update system review status module will regularly execute the verification of the statuses of the specification inspection tasks of all software products applied in the production system before the production conclusion point is issued. When the statuses of all software product specification inspection tasks are passed, the software product specification inspection review status of the production system is updated to passed.

[0087] At the time point when the production inspection conclusion is required to be issued according to the inspection specification, the software product specification inspection review conclusion of the production system is automatically synchronized to the production version baseline of the production version console.

[0088] The units involved in the embodiments of the present disclosure can be implemented in software or in hardware. Among them, the name of the unit does not constitute a limitation on the unit itself in some cases. For example, the first acquisition unit can also be described as "the unit for acquiring at least two Internet protocol addresses".

[0089] The functions described above in this article can be performed at least in part by one or more hardware logic components. For example, without limitation, the exemplary types of hardware logic components that can be used include: field programmable gate array (FPGA), application specific integrated circuit (ASIC), application specific standard product (ASSP), system on chip (SOC), complex programmable logic device (CPLD), and so on.

[0090] Figure 7 It is a block diagram of an electronic device according to an embodiment of the present application.

[0091] Refer to the following Figure 7 As shown, it shows a structural schematic diagram suitable for implementing the electronic device in the embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. This electronic device is only an example and should not impose any limitations on the functions and usage scope of the embodiments of the present disclosure.

[0092] The electronic device may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes according to the program stored in the read-only memory ROM 702 or the program loaded from the input device 706 into the random access memory RAM 703. In the RAM, various programs and data required for the operation of the electronic device are also stored. The processing device, the ROM, and the RAM are connected to each other through the bus 704. The input / output (I / O) interface 705 is also connected to the bus 704.

[0093] Generally, the following devices can be connected to the I / O interface: input devices including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc. 707; storage devices including, for example, a magnetic tape, a hard disk, etc. 708; and a communication device 709. The communication device 709 can allow the electronic device to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows an electronic device having various devices, it should be understood that it is not required to implement or have all the shown devices. Instead, more or fewer devices can be implemented or had.

[0094] The present application also provides an embodiment of a computer-readable storage medium.

[0095] The above computer-readable storage medium is applied to an electronic device and carries one or more computer programs. When the one or more computer programs are executed by the electronic device, the electronic device checks the installation configuration specifications of the software products of the production system. Specifically, a specification check task is created based on the check scope characteristics of the software products of the production system, the production version baseline information, and the VT environment ledger information; the specification check task is executed, and a check script generated according to the product specification check rules of the software products is sent to the deployment unit server to be checked, so that the deployment unit server to be checked executes the check script to generate specification check result information. The present application uses a flexible parameterized design mode to realize the automatic check function of the installation configuration specifications of software products, so as to ensure that the product specification check efficiency and the check quality are greatly improved. It should be noted that the above computer-readable medium in the present disclosure can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium can include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0096] In the present disclosure, a computer-readable storage medium can be any tangible medium that contains or stores a program, which can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0097] Each embodiment in this specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. For the same or similar parts among the embodiments, reference can be made to each other.

[0098] Although the preferred embodiments of the embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications once they know the basic creative concept. Therefore, the appended claims are intended to be construed as including the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present invention.

[0099] Finally, it should also be noted that in this text, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including", or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article, or terminal device comprising a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such a process, method, article, or terminal device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of additional identical elements in the process, method, article, or terminal device comprising the said element.

[0100] The above has introduced the technical solution provided by the present invention in detail. Specific examples are used in this article to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A method for verifying the installation and configuration specifications of an electronic device for verifying the installation and configuration specifications of a software product in a production system, characterized in that: The specification inspection method includes the steps of: Creating a specification inspection task based on the inspection scope characteristics of the software product of the production system, the production version baseline information, and the VT environment ledger information; Executing the specification inspection task, and sending the inspection script generated according to the product specification inspection rules of the software product to the server of the deployment unit to be inspected, so that the server of the deployment unit to be inspected executes the inspection script to generate specification inspection result information.

2. The standard inspection method according to claim 1, characterized in that: The step of creating a specification inspection task based on the inspection scope characteristics of the software product of the production system, the production version baseline information, and the VT environment ledger information includes the steps of: Extracting the inspection scope characteristics and performing parametric configuration, judging the system scope of product inspection according to the inspection scope characteristics, regularly receiving the production version baseline information, querying the VT environment ledger information according to the system scope, and obtaining the system server information in the VT environment ledger information; Screening the deployment unit name and deployment unit type information of the software product in the inspection scope characteristics according to the production version baseline information, and creating the specification inspection task according to the name of the software product, the deployment unit name, and the deployment unit type information.

3. The specification inspection method according to claim 1, wherein The step of executing the specification inspection task, sending the inspection script generated according to the product specification inspection rules of the software product to the server of the deployment unit to be inspected, so that the server of the deployment unit to be inspected executes the inspection script to generate specification inspection result information includes the steps of: Obtaining the installation and configuration specifications of the software product, and sorting out the installation and configuration specifications to form the product specification inspection rules; Regularly starting the specification inspection task, and sending the inspection script to the service request of the deployment unit to be inspected, so that the server of the deployment unit to be inspected executes the inspection script to generate specification inspection result information.

4. The specification inspection method according to any one of claims 1 to 3, characterized in that It further includes the steps of: Displaying the specification inspection result information, and receiving the review information of the reviewer. When the inspection passed information is received, controlling to stop executing the specification inspection task.

5. The standard inspection method according to claim 4, characterized in that: It further includes the steps of: Updating the inspection review status of the software product when the review information of the software product is passed.

6. A specification inspection device for installation and configuration, which is applied to an electronic device and used to inspect the installation and configuration specifications of software products in a production system, is characterized in that The specification inspection device includes: A task creation module configured to create a specification inspection task based on the inspection scope characteristics of the software product of the production system, the production version baseline information, and the VT environment ledger information; A task execution module configured to execute the specification inspection task, and send the inspection script generated according to the product specification inspection rules of the software product to the server of the deployment unit to be inspected, so that the server of the deployment unit to be inspected executes the inspection script to generate specification inspection result information.

7. The specification inspection device according to claim 6, characterized in that, It further includes: An appeal review module configured to display the specification inspection result information, and receive the review information of the reviewer. When the inspection passed information is received, controlling to stop executing the specification inspection task.

8. The specification inspection device according to claim 8, characterized in that, It further includes: A status update module configured to update the inspection review status of the software product when the review information of the software product is passed.

9. An electronic device, characterized in that: The electronic device includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs or instructions; The processor is configured to execute the computer program or instruction so as to enable the electronic device to implement the specification inspection method according to any one of claims 1 to 5.

10. A computer-readable storage medium, applied to an electronic device, characterized in that, The storage medium carries one or more computer programs, and the one or more computer programs can be executed by the electronic device, so that the electronic device can implement the specification inspection method according to any one of claims 1 to 5.

Images