System installation and deployment method and system based on engineering metadata

Abstract

The invention provides a system installation and deployment method and system based on engineering metadata, and relates to the technical field of software deployment, and the method comprises the steps: determining a software installation mode, and obtaining the engineering metadata; checking an installation environment based on preposition dependency information prompted by the engineering metadata; after the safety of the installation environment is ensured, performing signature verification and integrity verification on the software package based on the engineering metadata abstract and the signature information; after verification and verification are passed, the software package is installed on the basis of the component list of the engineering metadata, and the software package is configured on the basis of the information configuration list of the engineering metadata; and acquiring a security policy of the engineering metadata, activating a security protection function, generating installation engineering metadata after the security policy is completed, and evaluating the installation process based on the security engineering metadata.

Description

Technical Field

[0001] The present disclosure relates to the technical field of software deployment, and in particular to a system installation and deployment method and system based on engineering metadata. Background Art

[0002] The statements in this section merely provide background information related to the present disclosure and do not necessarily constitute prior art.

[0003] In a broad sense, system installation and deployment includes multiple technical fields: such as system packaging, system deployment, system security, and system maintenance. With the rapid development of software technology, the rapid popularization of cloud technology, and the explosive growth of open source code, the complexity of current software systems has greatly increased in terms of function, system architecture, and the degree of interdependence of class libraries compared to software systems 20 years ago, which has brought new challenges to the rapid installation and deployment of systems. In order to solve these problems, a series of solutions have emerged and have been widely used.

[0004] For artifact repositories and project file definitions: For example, solutions like mvn repository. It provides a shared storage repository for multi-party artifact files, describes software projects (such as third-party dependencies, compilation and packaging) through project files, and uses project files to package and deploy software. For container runtimes and their description files: For example, solutions like docker. It describes the build environment on which the software depends, and packages the runtime environment into containers, thereby reducing the system's dependence on external operating systems during deployment and reducing deployment difficulty. Operating environment scanning and protection technology: For example, solutions like trivy. It relies on feature scanning of the development or production environment to quickly identify the third-party dependencies of the software system and the relationships between services.

[0005] The emergence of these technologies undoubtedly brings solutions or technical means to some aspects of installation, deployment, and system analysis. However, they still have some problems:

[0006] 1) No global information is formed. Each technical solution only acts on a certain stage of the software cycle and generates relevant information. However, this information is often discarded, and is not organized to form the global information of the system software, and does not have the information backtracking capability of the entire life cycle of the software.

[0007] 2) When installing, upgrading or renovating the system, due to the lack of effective records and information, it is impossible to automatically recommend and generate effective packaged installation and upgrade solutions. Often a large amount of manpower is required to conduct business analysis and test the system, resulting in high installation and upgrade costs and cumbersome steps.

[0008] 3) In the actual deployment process, especially in offline environments, there is often a lack of effective verification mechanisms and access procedures for system deployment and safe operation. In addition, the scanning and analysis results are often processed passively and analyzed after the fact, lacking initiative. Summary of the invention

[0009] In order to solve the above problems, the present disclosure proposes a system installation and deployment method and system based on engineering metadata, which effectively tracks the entire life cycle of software information, realizes digital twin and visualization of software installation and deployment, and realizes the generation of software packaging and deployment strategies and automation of specific processes through the collection, analysis, extraction and query of engineering metadata.

[0010] According to some embodiments, the present disclosure adopts the following technical solutions:

[0011] The system installation and deployment method based on project metadata includes:

[0012] Determine the software installation method and obtain project metadata;

[0013] Checking the installation environment based on the pre-dependency information indicated by the project metadata;

[0014] After ensuring the safety of the installation environment, perform signature verification and integrity check on the software package based on the project metadata summary and signature information;

[0015] After verification and validation, the software package is installed based on the component list of the project metadata, and the software package is configured based on the information configuration list of the project metadata;

[0016] The security policy of the engineering metadata is obtained, the security protection function is activated, and after completion, the installation engineering metadata is generated, and the installation process is evaluated based on the security engineering metadata.

[0017] According to some embodiments, the present disclosure adopts the following technical solutions:

[0018] System installation and deployment system based on project metadata, including:

[0019] Data acquisition module, determines the software installation method and obtains project metadata;

[0020] A data analysis module is used to check the installation environment based on the pre-dependency information indicated by the project metadata; after ensuring the safety of the installation environment, the software package is signed and verified for integrity based on the project metadata summary and signature information;

[0021] The software deployment module is used to install the software package based on the component list of the engineering metadata after verification and validation, and configure the software package based on the information configuration list of the engineering metadata; obtain the security policy of the engineering metadata, activate the security protection function, generate the installation engineering metadata after completion, and evaluate the installation process based on the security engineering metadata.

[0022] According to some embodiments, the present disclosure adopts the following technical solutions:

[0023] A non-transitory computer-readable storage medium is used to store computer instructions. When the computer instructions are executed by a processor, the system installation and deployment method based on engineering metadata is implemented.

[0024] According to some embodiments, the present disclosure adopts the following technical solutions:

[0025] An electronic device comprises: a processor, a memory and a computer program; wherein the processor is connected to the memory, the computer program is stored in the memory, and when the electronic device is running, the processor executes the computer program stored in the memory so that the electronic device executes the system installation and deployment method based on engineering metadata.

[0026] Compared with the prior art, the present invention has the following beneficial effects:

[0027] The disclosed system installation and deployment method based on engineering metadata realizes the generation of software packaging and deployment strategies and the automation of specific processes through the collection, analysis, extraction and query of engineering metadata, thereby improving the efficiency and success rate of software packaging and deployment.

[0028] The disclosed system installation and deployment method based on engineering metadata improves the integrity, security, and robustness of the installed system and timely discovers system security risks by extracting configuration specification information, system key information, software components, security policy recommendations, necessary verification use cases, etc. from engineering metadata.

[0029] The disclosed system installation and deployment method based on engineering metadata realizes effective tracking of the entire life cycle of software information, and realizes digital twin and visualization of software installation and deployment. It can timely discover problems and errors in the development stage, release stage, installation and configuration stage, and reduce software deployment risks. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings constituting a part of the present disclosure are used to provide a further understanding of the present disclosure. The illustrative embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation on the present disclosure.

[0031] Figure 1 A schematic diagram of the system organization architecture of an embodiment of the present disclosure;

[0032] Figure 2 This is a data acquisition flow chart of an embodiment of the present disclosure;

[0033] Figure 3 A flowchart for packaging software products according to an embodiment of the present disclosure;

[0034] Figure 4 The software deployment and installation flowchart of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] The present disclosure is further described below in conjunction with the accompanying drawings and embodiments.

[0036] It should be noted that the following detailed descriptions are all illustrative and are intended to provide further explanation of the present disclosure. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present disclosure belongs.

[0037] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present disclosure. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprising" and / or "including" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0038] Example 1

[0039] In one embodiment of the present disclosure, a system installation and deployment method based on engineering metadata is provided, comprising:

[0040] Step 1: Determine the software installation method and obtain project metadata;

[0041] Step 2: Check the installation environment based on the pre-dependency information indicated by the project metadata;

[0042] Step 3: After ensuring the safety of the installation environment, perform signature verification and integrity check on the software package based on the project metadata summary and signature information;

[0043] Step 4: After verification and validation, the software package is installed based on the component list of the project metadata, and the software package is configured based on the information configuration list of the project metadata;

[0044] Step 5: Obtain the security policy of the project metadata, activate the security protection function, and after completion, generate the installation project metadata, and evaluate the installation process based on the security project metadata.

[0045] As an embodiment, the specific implementation process of the system installation and deployment method based on engineering metadata disclosed in the present invention requires the implementation of platform tools. The process operation of the platform tools participates in the entire life cycle of the software system and ultimately serves the installation and deployment of the software system. The entire platform tool includes Figure 1 The components shown are a tool for defining project metadata entries and their specifications 1, a project metadata file database 12, a tool for automatically collecting project metadata 13, a project metadata information system 14, a project metadata analysis report 15, a software packaging tool 16, a software installation framework 17, and a signed software release product 18.

[0046] Among them, the engineering metadata entry and specification definition tool 11 defines all metadata entries and specifications generated by the development software according to the development process of each software program, industry characteristics, and development dependent software. The software metadata data and its index maintained by the present disclosure are stored in the engineering metadata file library 12. Finally, the engineering metadata automatic collection tool 13 needs to be integrated with various information systems and development tools of the software engineering to realize the automatic collection and update of engineering metadata.

[0047] The engineering metadata information system 14 is used to maintain the metadata defined by the definition tool 11 and collected by the collection tool 13. The metadata should include (but not limited to) software basic information, software function list, software component data, and software deployment configuration.

[0048] Furthermore, the basic software information should include the software name, software version, release time, etc.

[0049] The software function list should include software function description information, function-related development definition, function-related test definition, and related code submission, etc.

[0050] The software component data should include a list of internal software components, internal component release locations and dependencies, external system dependencies, deployment resource dependencies, etc.

[0051] The software deployment configuration information should include the released or installed software signature information, software authorization information, software configuration parameters, field fault list, and related security policies.

[0052] The engineering metadata analysis report 15 is generated by the engineering metadata information system 14 and is used to refer to the metadata information for the installation and deployment of the software. Based on the metadata, the report defines the packaging content and installation process, recommends installation and deployment parameters, and prompts the deployment pre-conditions and post-operations. Based on the process and information prompts defined in the engineering metadata analysis report 15, the software packaging tool 16 is responsible for pipeline packaging, software signing, and automatic testing of the software products, and generates and publishes the signed software release products 18 in the relevant software warehouse, and reports the results of the relevant packaging activities to the engineering metadata information system 14. Based on the engineering metadata analysis report 15 and the signed software release products 18, the software installation framework 17 will install the software based on the process and deployment parameters prompted by the engineering metadata analysis report 15, and will verify the installation environment of the installed software and the security of the software itself, and collect and report the deployment information to the above-mentioned engineering metadata information system 14.

[0053] As an embodiment, the installation and deployment method based on engineering metadata includes three basic processes: information collection of engineering metadata A, software product packaging based on engineering metadata B, and finally software deployment, installation and maintenance based on engineering metadata based on the collected engineering metadata and software product package C. The specific process is described as follows:

[0054] First, if Figure 2 As shown, information collection A, i.e., the steps of obtaining engineering metadata, include:

[0055] Step 0: Define new software or change software functions.

[0056] Step 1: Automatically define and manually revise the metadata list and collection method required by the new software.

[0057] Step 2: Adapt, install, and activate the metadata collection tool agent to continuously monitor and collect metadata generated by various software engineering system activities.

[0058] Step 3: Save the collected metadata based on the metadata item list and create an index for subsequent maintenance and query.

[0059] Furthermore, if Figure 3 As shown, the process of packaging software product B is as follows:

[0060] Step 0: The pipeline automatically or manually triggers the release process of a software product.

[0061] Step 1: Query the engineering metadata analysis report of the software through the basic information of the software product and the parameters of this release.

[0062] The release parameters this time include full release, incremental release, etc.

[0063] Step 2: Based on the engineering metadata information, such as component dependencies and system environment dependencies, pull the components required for the product from each dependency library, perform integrity verification on the components, sign the software release package, and assemble it into a software release package. Necessary engineering metadata analysis reports and installation verification use cases are also packaged in the software release package.

[0064] Step 3: Perform regression testing on the released software based on the test elements installed in the project metadata.

[0065] Step 4: Push the software release package to the product warehouse and report the metadata of this release project.

[0066] Furthermore, if Figure 4 As shown, the steps of deployment, installation and maintenance process C based on project metadata and software packages are as follows:

[0067] Step 0: Install the software by pushing automatic installation or manually installing the software.

[0068] Step 1: Extract project metadata from the software package (offline installation) or query project metadata (online installation).

[0069] The difference between online and offline depends on whether the user deployment environment is connected to the Internet and whether a correct query connection can be established with the metadata information system.

[0070] In an offline environment, since a link cannot be established, the relevant metadata will be published as part of the package release and extracted from the release during installation.

[0071] With the online method, there is no need to put all the information into the release package, but updates can be obtained through queries.

[0072] Step 2: Perform an installation check on the installation environment based on the pre-dependency information (such as external system requirements, environment installation requirements, safety checks, etc.) indicated by the project metadata. If the check passes, proceed to the next step of installation. Otherwise, go to step 7.

[0073] Step 3: Based on the project metadata summary and signature information, perform signature verification and integrity check on the software package. If the verification is successful, proceed to the next step; otherwise, proceed to step 7.

[0074] Step 4: Install the software based on the component list of the project metadata. Configure the software based on the information configuration list of the project metadata. Activate relevant security measures based on the security policy of the project metadata.

[0075] The security policy includes but is not limited to the following aspects:

[0076] 1) Firewall settings and selinux settings of the host where the software or system is located.

[0077] 2) When the software or system is started, the trust chain construction method and verification method and information.

[0078] 3) Startup and registration of security services of software or system.

[0079] 4) Software or system access identity and permission settings.

[0080] Security policy refers to a consideration and abstraction of security measures under the premise of the normal operation of an application or software. It templates and scripts a set of steps to be implemented by a software or system, and can be parameterized according to environmental factors and deployment forms. It presents a security setting standard at a relatively abstract level to the user installation. By setting the security setting standard, the user completes the entire process from policy definition to the final security effectiveness.

[0081] Step 5: After the installation is completed, the metadata of this installation project is generated. The data is collected by automatic reporting (online) or subsequent collection (offline). Based on the installation metadata, the installation project is evaluated.

[0082] The metadata of this installation project includes: installation version, installation environment, startup status and log path.

[0083] Step 6: Start the software. During the startup process, the software startup environment, software summary, software authorization, etc. will be checked based on the project metadata to decide whether to start or terminate the software.

[0084] Step 7: End.

[0085] Example 2

[0086] In one embodiment of the present disclosure, a system installation and deployment system based on engineering metadata is provided, including:

[0087] Data acquisition module, determines the software installation method and obtains project metadata;

[0088] A data analysis module is used to check the installation environment based on the pre-dependency information indicated by the project metadata; after ensuring the safety of the installation environment, the software package is signed and verified for integrity based on the project metadata summary and signature information;

[0089] The software deployment module is used to install the software package based on the component list of the engineering metadata after verification and validation, and configure the software package based on the information configuration list of the engineering metadata; obtain the security policy of the engineering metadata, activate the security protection function, generate the installation engineering metadata after completion, and evaluate the installation process based on the security engineering metadata.

[0090] Example 3

[0091] In one embodiment of the present disclosure, a non-transitory computer-readable storage medium is provided, wherein the non-transitory computer-readable storage medium is used to store computer instructions, and when the computer instructions are executed by a processor, the system installation and deployment method based on engineering metadata is implemented.

[0092] Example 4

[0093] In one embodiment of the present disclosure, an electronic device is provided, including: a processor, a memory, and a computer program; wherein the processor is connected to the memory, the computer program is stored in the memory, and when the electronic device is running, the processor executes the computer program stored in the memory, so that the electronic device executes the system installation and deployment method based on engineering metadata.

[0094] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0095] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0096] Although the above describes the specific implementation methods of the present disclosure in conjunction with the accompanying drawings, it is not intended to limit the scope of protection of the present disclosure. Technical personnel in the relevant field should understand that on the basis of the technical solution of the present disclosure, various modifications or variations that can be made by those skilled in the art without creative work are still within the scope of protection of the present disclosure.

Claims

1. A system installation and deployment method based on engineering metadata, characterized in that: include: Determine the software installation method and obtain project metadata; Checking the installation environment based on the pre-dependency information indicated by the project metadata; After ensuring the safety of the installation environment, perform signature verification and integrity check on the software package based on the project metadata summary and signature information; After verification and validation, the software package is installed based on the component list of the engineering metadata, and the software package is configured based on the information configuration list of the engineering metadata; The security policy of the engineering metadata is obtained, the security protection function is activated, and after completion, the installation engineering metadata is generated, and the installation process is evaluated based on the security engineering metadata.

2. The system installation and deployment method based on engineering metadata according to claim 1, characterized in that: The software installation method includes offline installation and online installation. In the offline installation method, it is necessary to extract the project metadata, while in the online installation method, the project metadata is directly queried.

3. The system installation and deployment method based on engineering metadata according to claim 1, characterized in that: The acquisition of engineering metadata includes: defining new software or changing software functions, automatically defining and manually revising the engineering metadata list and collection method required for the new software, adapting, installing and activating the engineering metadata collection tool agent, continuously monitoring and collecting metadata generated by various software engineering system activities, saving the collected metadata based on the metadata item list, and establishing an index.

4. The system installation and deployment method based on engineering metadata according to claim 1, characterized in that: The process of forming a software package includes: the pipeline automatically or manually triggers the release process of the software product, queries the engineering metadata analysis report of the software through the basic information of the software product and the parameters of this release, obtains the components required for the software product from each dependent library based on the engineering metadata information and dependencies, and performs integrity verification on the components, signs the software release package, and assembles it into a software release package; performs regression testing on the released software based on the engineering metadata, pushes the software release package to the product warehouse, and reports the engineering metadata of this release.

5. The system installation and deployment method based on engineering metadata according to claim 4, characterized in that: Release parameters include full release and enhanced release.

6. The system installation and deployment method based on engineering metadata according to claim 1, characterized in that: The pre-dependency information includes external system requirements, environmental safety requirements, and safety checks.

7. The system installation and deployment method based on engineering metadata according to claim 1, characterized in that: The generated metadata for this installation project includes the installation version, installation environment, startup status, and log path.

8. A system installation and deployment system based on engineering metadata, characterized in that: include: Data acquisition module, determines the software installation method and obtains project metadata; A data analysis module, used for checking the installation environment based on the pre-dependency information suggested by the project metadata; After ensuring the safety of the installation environment, perform signature verification and integrity check on the software package based on the project metadata summary and signature information; The software deployment module is used to install the software package based on the component list of the engineering metadata after verification and validation, and configure the software package based on the information configuration list of the engineering metadata; obtain the security policy of the engineering metadata, activate the security protection function, generate the installation engineering metadata after completion, and evaluate the installation process based on the security engineering metadata.

9. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium is used to store computer instructions, and when the computer instructions are executed by the processor, the system installation and deployment method based on engineering metadata as described in any one of claims 1-7 is implemented.

10. An electronic device, characterized in that: include: A processor, a memory and a computer program; wherein the processor is connected to the memory, the computer program is stored in the memory, and when the electronic device is running, the processor executes the computer program stored in the memory to enable the electronic device to implement the system installation and deployment method based on engineering metadata as described in any one of claims 1-7.

Images