Cloud application configuration parameter verification method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an on-cloud application configuration parameter verification method and device, electronic equipment and a storage medium. The method comprises the following steps: acquiring configuration information of an application component, wherein the configuration information comprises a plurality of configuration parameters and a configuration version corresponding to each configuration parameter; for each configuration parameter, determining a standard value of the configuration parameter according to a configuration version corresponding to the configuration parameter; based on the standard value, determining a parameter verification rule corresponding to the configuration parameter from a configuration rule base, the parameter verification rule comprising at least one of an integrity verification rule, a data type verification rule and a value range verification rule; according to a parameter verification rule, the configuration parameters are verified, a verification result is determined, and the verification result represents whether the configuration parameters meet preset configuration requirements or not; and generating a configuration verification report according to verification results corresponding to all the configuration parameters. The method is used for improving the verification effect of the configuration parameters of the cloud application and guaranteeing the stable operation of the cloud application system.

Description

Technical Field

[0001] The present application relates to the field of cloud application management technology, and in particular to a method, device, electronic device and storage medium for verifying configuration parameters of cloud applications. Background Art

[0002] Cloud native technology is developing rapidly, and a large number of applications are gradually migrating to the cloud. This trend has brought new challenges and opportunities in the field of cloud application management technology. As the scale of applications expands and the complexity increases, ensuring the stable operation of cloud application systems has become a key issue. The management and monitoring of application configuration parameters plays a vital role in system performance and service continuity.

[0003] In the prior art, the DevOps pipeline does not support automatic verification of configuration parameters. If it is to be supported, it needs to be modified. This results in the inability to effectively prevent component configuration parameter confusion when the cloud application is tested and launched using the DevOps pipeline. For the traditional cloud application component parameter configuration check, the unified management platform Agent on the virtual machine is usually used to send the check script to the application instance for execution and obtain the check result.

[0004] It can be seen that the existing technology has the problem of poor verification effect when applying configuration parameters on the cloud. Summary of the invention

[0005] The embodiments of the present application provide a method, device, electronic device and storage medium for verifying the configuration parameters of cloud applications, so as to solve the problem of poor verification effect when configuring the configuration parameters of cloud applications in the prior art, and ensure the stable operation of the cloud application system.

[0006] In a first aspect, an embodiment of the present application provides a method for verifying configuration parameters of an application on a cloud, including:

[0007] Obtain configuration information of application components, including multiple configuration parameters and the configuration version corresponding to each configuration parameter. Application components include single application components in the pipeline and full application components in the cloud environment.

[0008] For each configuration parameter, determine the standard value of the configuration parameter according to the configuration version corresponding to the configuration parameter;

[0009] Based on the standard value, determine a parameter verification rule corresponding to the configuration parameter from a configuration rule library, where the parameter verification rule includes at least one of an integrity verification rule, a data type verification rule, and a value range verification rule;

[0010] According to the parameter verification rules, the configuration parameters are verified to determine the verification results, which indicate whether the configuration parameters meet the preset configuration requirements;

[0011] Generate a configuration verification report based on the verification results corresponding to all configuration parameters.

[0012] In a second aspect, an embodiment of the present application provides a cloud application configuration parameter verification device, including:

[0013] An acquisition module is used to acquire configuration information of application components, where the configuration information includes multiple configuration parameters and a configuration version corresponding to each configuration parameter. Application components include a single application component in a pipeline and a full set of application components in a cloud environment.

[0014] A determination module, used for determining, for each configuration parameter, a standard value of the configuration parameter according to a configuration version corresponding to the configuration parameter;

[0015] A matching module, used to determine a parameter verification rule corresponding to the configuration parameter from a configuration rule library based on a standard value, wherein the parameter verification rule includes at least one of an integrity verification rule, a data type verification rule, and a value range verification rule;

[0016] A verification module is used to verify the configuration parameters according to the parameter verification rules and determine the verification results, which represent whether the configuration parameters meet the preset configuration requirements;

[0017] The generation module is used to generate a configuration verification report based on the verification results corresponding to all configuration parameters.

[0018] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

[0019] Memory stores computer-executable instructions;

[0020] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0021] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0022] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0024] Figure 1 A schematic diagram of the scenario of the cloud application configuration parameter verification method provided in this application;

[0025] Figure 2 A flowchart of the cloud application configuration parameter verification method provided by this application;

[0026] Figure 3 A schematic diagram of the specific process of the cloud application configuration parameter verification method in the pipeline provided by this application;

[0027] Figure 4 A schematic diagram of the specific process of the cloud application configuration parameter verification method in the cloud environment provided by this application;

[0028] Figure 5 A schematic diagram of the structure of the cloud application configuration parameter verification device provided by this application;

[0029] Figure 6 A schematic diagram of the structure of the electronic device provided in this application.

[0030] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0031] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0032] First, the terms involved in this application are explained:

[0033] Cloud computing environment: that is, the cloud environment, including each cluster and multiple cloud applications that have been tested and launched in the cluster, can obtain the required resources (such as network, server, storage and application services) from the configurable computing resource sharing pool anytime, anywhere, conveniently and on demand, and resources can also be quickly supplied and released.

[0034] Kubernetes: An open source system for automating the deployment, scaling, and management of containerized applications. It groups application containers into logical units for easy management and service discovery.

[0035] Workload: An application running on Kubernetes. Kubernetes uses workload resources to manage a group of Pod applications, such as scaling, starting, and destroying.

[0036] Pod: In Kubernetes, a pod is the smallest deployment unit that can be created, scheduled, and managed. It is a collection of containers rather than a single application container. Containers in the same Pod share the same network namespace, IP address, and port space.

[0037] System component configuration: A component is described as "a program that performs a specific function and is designed to facilitate the operation of other components and applications together". Optionally, the component configuration includes application configuration files and middleware layer configuration files.

[0038] DevOps pipeline: An automated, integrated workflow that connects software development, testing, and deployment to achieve the goals of continuous integration, continuous delivery, and continuous deployment.

[0039] In the prior art, the DevOps pipeline does not support automatic verification of configuration parameters. If it is to be supported, it needs to be modified. This results in the inability to effectively prevent the confusion of component configuration parameters when the cloud application is put online using the DevOps pipeline test. For the traditional cloud application component parameter configuration check, it is usually through the unified management platform Agent on the virtual machine to send the check script to the application instance for execution and obtain the check results. It can be seen that the cloud application cannot accurately know the standard values ​​of the configuration parameters of each application system before it goes into production, and there are many errors in manual inspection, which leads to performance degradation, security vulnerabilities and even service interruptions after the application system goes online.

[0040] The cloud application configuration parameter verification method provided in this application establishes an accurate data foundation to support the subsequent verification process by systematically acquiring and managing the configuration information of application components; by determining the standard value for each configuration parameter and applying multi-dimensional verification rules (including integrity, data type, and value range, etc.) from the configuration rule library, a comprehensive and accurate parameter verification is achieved. This automated verification process not only improves the efficiency and consistency of the verification, but also reduces human intervention and errors; by generating a configuration verification report, a clear configuration status view is provided for operation and maintenance and developers, supporting them to quickly locate and solve configuration problems. Therefore, the problem of poor verification effect caused by single rules or unclear standards in traditional verification can be solved, and configuration errors can be discovered and corrected in a timely manner, thereby ensuring the stable operation of the cloud application system and improving operation and maintenance efficiency.

[0041] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0042] Figure 1 A schematic diagram of a scenario for the cloud application configuration parameter verification method provided in this application, such as Figure 1 As shown, the specific application scenario of this application can be a configuration parameter verification system, which can be directly deployed in the workflow of the assembly line, or after the application is put into production on the cloud, it can be connected to the cloud platform through a preset interface in the cloud environment to obtain the configuration information of the application component. The configuration parameter verification system includes a configuration information collection module, a configuration rule base, a configuration monitoring module, and a result display module.

[0043] Among them, the configuration information collection module is used to obtain the middleware version information, configuration files, environment variables and other configuration information of the cloud application in the DevOps pipeline or specific interfaces, such as API (Application Programming Interface), CLI (Command-Line Interface) or SDK (Software Development Kit), and parse and standardize the collected configuration information for subsequent verification.

[0044] The configuration rule library is used to store the verification rules of various component configuration parameters, including mandatory items, data types, value ranges, etc. The rule library can support custom rules, allowing users to add or modify configuration parameter verification rules according to actual needs after review.

[0045] The configuration monitoring module is used to intelligently match and compare the configuration information processed by the configuration information collection module with the rules in the configuration rule base. It verifies the collected configuration parameter items one by one through various combined verification methods such as integrity verification, data type verification, and value range verification, and records the verification results and error information.

[0046] The result display module is used to display the verification results of all configuration parameters in the form of reports or platform modules, which more intuitively displays the configuration information and inspection results of the application middleware, facilitates quick positioning, understanding of configuration parameters and adjustments, and realizes unified configuration management and monitoring of each component.

[0047] This embodiment does not impose any special restrictions on the selection type of the cloud application configuration parameter verification system, as long as the configuration information of the application component can be obtained, the configuration information includes multiple configuration parameters and the configuration version corresponding to each configuration parameter, and the application component includes a single application component in the pipeline and the full application component in the cloud environment; for each configuration parameter, determine the standard value of the configuration parameter according to the configuration version corresponding to the configuration parameter; based on the standard value, determine the parameter verification rule corresponding to the configuration parameter from the configuration rule library, the parameter verification rule includes at least one of the integrity verification rule, the data type verification rule, and the value range verification rule; according to the parameter verification rule, verify the configuration parameter to determine the verification result, and the verification result indicates whether the configuration parameter meets the preset configuration requirements; according to the verification results corresponding to all configuration parameters, generate a configuration verification report.

[0048] Figure 2 The flowchart of the cloud application configuration parameter verification method provided by this application is as follows: Figure 2 As shown, the method includes:

[0049] S201. Obtain configuration information of an application component, where the configuration information includes multiple configuration parameters and a configuration version corresponding to each configuration parameter. The application component includes a single application component in a pipeline and a full application component in a cloud environment.

[0050] Application components can include independent components that make up the application, or middleware components. In a cloud computing environment, middleware components are located between the application and the underlying system, providing functions such as communication and data management. A single application component can refer to a middleware component used to build a complete application in a pipeline. A full application component can refer to the collection of all application modules or services deployed or running in a cloud environment.

[0051] Optionally, the configuration information can be parsed from the application configuration file and the middleware layer configuration file, or obtained from the cloud platform through a specific interface.

[0052] Configuration parameters can refer to specific settings of application components, such as database connection strings, API keys, etc.

[0053] The configuration version may refer to the version information of the configuration parameters, which is used to track the historical changes of the configuration to determine different verification rules.

[0054] S202: For each configuration parameter, determine a standard value of the configuration parameter according to a configuration version corresponding to the configuration parameter.

[0055] In this step, the standard value can be the expected value or default value of the configuration parameter, which is used to match the verification rule to ensure the correctness and rationality of the configuration parameter. Furthermore, the standard value can be extracted from the version control system according to the configuration version, or the existing configuration management database can be queried to obtain the standard value of each configuration parameter.

[0056] S203. Based on the standard value, determine a parameter verification rule corresponding to the configuration parameter from a configuration rule library, where the parameter verification rule includes at least one of an integrity verification rule, a data type verification rule, and a value range verification rule.

[0057] The configuration rule base is a database for storing various parameter validation rules. These rules define the conditions that each configuration parameter should meet, such as data type, value range, whether it is required, etc. For example, the rules in the configuration rule base can be matched according to the name and standard value of the configuration parameter. For example, if the rule requires that a parameter must be an integer and have a specific range, the system will check whether the standard value meets these conditions. Optionally, based on the configuration rule base, a machine learning algorithm is used to predict applicable validation rules.

[0058] S204: Verify the configuration parameters according to the parameter verification rule and determine the verification result, which indicates whether the configuration parameters meet the preset configuration requirements.

[0059] In this step, once the standard value matches the rule, the system will perform verification on the configuration parameters, and the verification results will be recorded, including which parameters passed the verification, which parameters did not pass the verification, and error messages.

[0060] Integrity check can refer to whether all necessary parameters are set, data type check can refer to whether the parameter value is of the correct data type, and value range check can refer to whether the parameter value is within the allowed range.

[0061] It should be noted that different types of rules can be used to check the configuration parameters one by one in a combined checking manner.

[0062] S205. Generate a configuration verification report according to the verification results corresponding to all configuration parameters.

[0063] The configuration verification report may refer to a report summarizing the verification results corresponding to all configuration parameters of this verification, and the report may be pushed to the verification personnel for review in the form of a report or platform module.

[0064] In one example, a report in PDF or HTML format is generated for manual review; the report is pushed to the user terminal device corresponding to the result display module, automatically triggering an alarm or notification. The configuration information and verification results of the application components can be intuitively displayed, which facilitates quick positioning, understanding of configuration parameters and adjustment, and realizes unified configuration management and monitoring of each component.

[0065] The cloud application configuration parameter verification method provided in the embodiment of the present application, by obtaining the configuration information of the application component, including multiple configuration parameters and corresponding configuration versions, forms a systematic configuration management foundation, and provides an accurate data source for subsequent verification; for each configuration parameter, the standard value is determined according to its configuration version, which can ensure that the benchmark for parameter verification is accurate and consistent, and avoid verification errors caused by version differences; parameter verification rules are determined from the configuration rule library, including multiple dimensions such as integrity, data type and value range, which can comprehensively cover all aspects of configuration parameters and improve the accuracy of verification; verification steps are automatically executed according to the parameter verification rules to generate verification results, which reduces human intervention and improves verification efficiency and consistency; the verification results of all configuration parameters are summarized to generate a configuration verification report, providing a clear configuration status view for operation and maintenance and developers. Through a systematic and automated verification process, configuration errors or inconsistencies can be discovered in a timely manner to prevent system failures caused by configuration problems, thereby ensuring the stable operation of the cloud application system.

[0066] Based on the above embodiments, when the application component is a single application component in a pipeline, the method for obtaining configuration information of the application component described in S201 may include: in response to the operation of uploading an application image and a configuration file of a single application component in the pipeline, obtaining initial configuration information of the single application component from the application image; and standardizing the initial configuration information to obtain configuration information of the single application component.

[0067] The pipeline can refer to an environment that uses DevOps pipelines to build and deploy applications. Triggers can be set in the pipeline to automatically execute scripts to extract configuration information when developers upload new application images and configuration files. Webhooks can also be used to listen to upload events and trigger backend services to process images and configuration files.

[0068] The initial configuration information can be obtained by starting the application image using a container tool and extracting it from a running container through an API interface or command line. It can also be obtained by parsing the metadata layer of the application image and directly reading configuration files or environment variables.

[0069] In this step, standardization can refer to converting the initial configuration information into a unified format or structure for subsequent processing and verification. For example, configuration management tools (such as Ansible, Chef) are used to convert configuration files in different formats into a unified JSON format, or custom scripts are written to format and clean up configuration data according to predefined templates and rules.

[0070] By responding to upload operations in the pipeline, automatically obtaining initial configuration information from the application image and performing standardized processing, the automation and standardization of configuration management is achieved. First, this automated process reduces manual intervention, reduces the phenomenon of human errors, and improves processing efficiency; second, through standardized processing, the consistency and readability of configuration information are ensured, providing a reliable data foundation for subsequent verification steps, which not only speeds up the deployment and update process of application components, but also improves the accuracy and consistency of configuration management, thereby enhancing the stability and maintainability of the system.

[0071] Based on the above embodiment, when the application component is a single application component in the pipeline, after generating a configuration verification report based on the verification results corresponding to all configuration parameters, the method may further include: if there are configuration parameters in the configuration verification report that do not meet the preset configuration requirements, terminating the construction and deployment process of the single application component in the pipeline; and sending the configuration parameters that do not meet the preset configuration requirements and the corresponding verification results to the terminal server for early warning.

[0072] The preset configuration requirement may refer to the standard or expected value of the configuration parameter of the system or application. The terminal server may refer to the user's terminal device, which is a server used to receive and process warning information, and is usually responsible for notifying relevant personnel or cloud systems. Warning may refer to reminding or warning relevant personnel to pay attention to configuration problems so that timely measures can be taken.

[0073] The method to terminate the pipeline is to configure a conditional step in the pipeline to automatically interrupt the pipeline when a verification failure is detected; or to manually stop the execution of the pipeline through an API call or command line tool.

[0074] The early warning method may be to use a message queue (such as RabbitMQ, Kafka) to send the verification result to the terminal server. It should be noted that the early warning may be sent to the terminal server together with the error information of the failed verification. The error information may be the information directly generated when the verification result is generated, or the information may be found from the error information database according to the failed verification type.

[0075] By detecting configuration parameters that do not meet preset requirements in the configuration verification report and terminating the pipeline, unqualified application components are effectively prevented from entering the production environment, ensuring the stability and security of the system. First, the automated termination process reduces human intervention, ensuring that problems can be discovered and handled at an early stage, avoiding potential system failures or security vulnerabilities; second, unqualified configuration parameters and verification results are sent to the terminal server for early warning, so that relevant personnel can receive timely notifications and take corrective measures. This early warning mechanism not only improves the response speed to problems, but also enhances the team's collaboration and problem-solving efficiency.

[0076] Based on the above embodiments, when the application component is a full application component in a cloud environment, the method for obtaining configuration information of the application component described in S201 may include: obtaining full cluster information based on a preset interface of the cloud environment, the full cluster information including cluster configuration information of multiple clusters and full application components under each cluster; for each cluster, obtaining workload information of the full application components under the cluster based on the preset interface of the cloud environment; determining the configuration information of the full application components under the cluster based on the cluster configuration information and workload information of the cluster.

[0077] In this step, the preset interface of the cloud environment may refer to an API or other interface provided by the cloud service provider, such as a CLI or SDK, for accessing and managing cloud resources.

[0078] Full cluster information may include configuration information of all clusters or predefined clusters in the cloud environment and information about all application components under each cluster. Cluster configuration information may refer to detailed information describing cluster settings, including network configuration, node specifications, storage configuration, etc. Workload information may be information used to describe the running status of application components in the cluster.

[0079] You can obtain the resource usage and running status of application components in each cluster by calling the cloud API; you can also use monitoring tools to collect and analyze workload data to obtain workload information. The configuration information can be determined by integrating and cleaning the data obtained from the API and monitoring tools to generate complete configuration information for each application component.

[0080] In one example, an API, CLI or SDK provided by a cloud service provider is used to obtain a list of all cloud clusters, for example, including basic information such as the cluster identifier, name, and region; for each cluster, detailed information is obtained using an API or other interface, for example, including a list of nodes, network configuration, storage configuration, etc.; in each cluster, a list of all namespaces is obtained, which is a logical partition used to isolate resources in a container orchestration platform such as Kubernetes; for each namespace, information about all workloads running therein is obtained, for example, including deployments, stateful sets, daemon sets, jobs, etc.; for each workload, relevant application information is collected, such as container images, environment variables, configuration files, resource requests and restrictions (CPU, memory, etc.), number of replicas, etc.; a management platform agent running on a cluster node can help collect more detailed workload information, where the agent can execute scripts or commands to obtain real-time performance indicators, log information, health status, etc.; the collected workload information is integrated into a unified database or data warehouse for further analysis.

[0081] By obtaining full cluster information and workload information through a preset interface based on the cloud environment, comprehensive configuration management of all application components in the cloud environment is achieved. By using the API and tools of the cloud service provider, cluster and application component information is automatically collected and integrated, reducing the complexity and errors of manual operations; by analyzing cluster configuration information and workload information, the configuration of application components can be dynamically adjusted and optimized to meet actual operation requirements, which not only improves the efficiency and accuracy of configuration management, but also enhances the elasticity and scalability of the system.

[0082] Based on the above embodiments, when the application component is a full application component in a cloud environment, after generating a configuration verification report based on the verification results corresponding to all configuration parameters, the method may further include: for each cluster, determining a set of configuration verification reports corresponding to all full application components under the cluster; and sending the set of configuration verification reports to the terminal server for visual display.

[0083] Furthermore, the configuration verification report set may be a collection of configuration verification reports of all application components in a cluster. Visual display may refer to presenting data through a graphical interface so that users can intuitively understand and analyze information.

[0084] In one example, a method for determining a configuration verification report set may be to, after generating a configuration verification report for each application component, use a script to aggregate these reports into a cluster-level report set; or a method for determining a configuration verification report set may be to use a database or data warehouse to store the verification results of each application component and index and classify them by cluster.

[0085] By determining the configuration verification report set of all application components under each cluster and sending it to the terminal server for visual display, the configuration management information is centralized and intuitive. First, the cluster-level report set provides a comprehensive perspective, allowing operation and maintenance personnel to quickly understand the configuration status and potential problems of application components in each cluster; second, through visual display, complex verification data is converted into easy-to-understand graphics and charts, which improves the readability and analysis efficiency of information and speeds up problem detection and response.

[0086] Based on the above embodiment, before sending the configuration verification report set to the terminal server for visual display, the method may also include: determining an abnormal verification report in the configuration verification report set, the abnormal verification report being a configuration verification report corresponding to a configuration parameter that does not meet the preset configuration requirements; generating a predefined tag for the abnormal verification report, the predefined tag being used to search for configuration parameters that do not meet the preset configuration requirements in the configuration verification report set.

[0087] The predefined tags may refer to tags or keywords used to identify and quickly find specific problems in the abnormality verification report.

[0088] Optionally, a script or tool is used to scan the configuration verification report collection, identify the configuration parameters marked as unqualified in the report, and classify these reports as abnormal verification reports. Alternatively, when generating configuration verification reports, reports that do not meet preset requirements are automatically marked and screened and classified in subsequent steps.

[0089] The method of generating predefined labels for anomaly verification reports may include generating labels including problem type, severity, and impact scope for each anomaly verification report so as to quickly filter and locate in a visual interface. It may also include using a machine learning algorithm to analyze the content of the anomaly report and automatically generate descriptive labels to help users understand and handle the problem.

[0090] By identifying abnormal verification reports and generating predefined tags before sending the configuration verification report collection to the terminal server for visual display, the efficiency of problem detection and handling is improved. By identifying abnormal verification reports, operation and maintenance personnel can quickly focus on the problems that need to be solved first, avoiding the tedious process of manually searching in large amounts of data; by generating predefined tags, a structured description is provided for abnormal reports, making the classification, sorting and priority management of problems more intuitive and efficient, which improves the accuracy of anomaly detection. By integrating these tags in the visual display, operation and maintenance personnel can more easily navigate and analyze configuration problems, supporting faster decision-making and more effective resource allocation.

[0091] Based on the above embodiments, the method described in S205 for generating a configuration verification report based on the verification results corresponding to all configuration parameters may include: determining a first configuration parameter that does not meet the preset configuration requirements based on the verification results corresponding to all configuration parameters; obtaining the reason for the verification failure of the first configuration parameter; and generating a configuration verification report based on the first configuration parameter, the verification failure reason and the second configuration parameter that meets the preset configuration requirements.

[0092] The verification failure reason may refer to a reason or error information that specifically describes why the first configuration parameter does not meet the preset configuration requirement.

[0093] For example, detailed error information is extracted from the verification result to describe the specific reasons why the parameters are unqualified. Alternatively, the verification rules and parameter values ​​are analyzed through the error information to generate explanatory text to help understand the reasons for the failure.

[0094] By identifying the first configuration parameter that does not meet the preset requirements and obtaining the reason for its verification failure, the root cause of the problem can be clearly presented, which is convenient for quick location and repair; by simultaneously displaying the second configuration parameter that meets the requirements, the report provides a complete view of the configuration health status, helping users to identify overall trends and patterns, improving the accuracy of problem diagnosis, and enhancing the transparency and operability of configuration management. By generating detailed and structured configuration verification reports, users can more effectively optimize configurations and manage resources, supporting more efficient system maintenance and improvement.

[0095] Figure 3 The specific flow chart of the cloud application configuration parameter verification method in the pipeline provided by this application is as follows: Figure 3 As shown, in this embodiment Figure 2On the basis of the implementation example, the method for verifying the configuration parameters of cloud applications in the pipeline is explained in detail. For the scenario where an application image needs to be created and uploaded to the product library before the cloud application is released, and various component parameters need to be configured, a configuration parameter verification system is added to the pipeline. If the component configuration parameter verification fails, the image file is prevented from being uploaded to the product library, which is equivalent to setting a production access control check before the image is constructed. The following mainly introduces the process that is different from the traditional pipeline working mode after adding the configuration parameter verification system, including: (1) After uploading the application image and configuration file in the pipeline, start the configuration information collection module, obtain the upper-level component information from the application image on the cloud, and pass it to the configuration monitoring module; (2) The configuration monitoring module now determines the standard value of the component parameter to ensure the correctness of the parameters at the production application system layer, and then intelligently matches and compares the collected component configuration parameters with the pre-defined rules of the configuration rule library to obtain the verification results; (3) The configuration monitoring module generates a configuration verification report based on the verification results, including the configuration items that passed the verification, the configuration items that failed the verification and the reasons, etc., and displays the configuration verification report to the user through the DevOps pipeline, so that the user can quickly locate the problem and make repairs and adjustments.

[0096] Figure 4 The specific flow chart of the method for verifying the configuration parameters of cloud applications in the cloud environment provided by this application is as follows: Figure 4 As shown, in this embodiment Figure 2Based on the implementation examples, a method for verifying the configuration parameters of cloud applications in a cloud environment is described in detail. Applications will have different component configurations when facing different cloud environments. As a large number of cloud applications are put into production, the number of component configuration parameter monitoring increases dramatically. For the scenario of massive application component configuration monitoring after production, this method is adapted to different cloud environments to ensure that after the application is upgraded and changed, the new configuration parameters can be correctly verified to be valid and compliant in different cloud environments. The method includes: (1) firstly obtaining the full cloud cluster information of the cloud environment through a standard interface (such as API, CLI or SDK), and collecting the workload information of each cloud application, and using the unified management platform Agent on the cluster node to transmit the inspection script to each workload of the cluster; (2) intelligently matching the collected configuration information of each component with the rules in the configuration rule library, performing configuration verification, and generating a configuration verification report, including configuration items that passed the verification, configuration items that failed the verification and the reasons, etc. For example, the inspection script is sent to any node of each cluster through the API, and the workloads of all namespaces under the current cluster are queried in turn, and then the configuration of each component of the workload is checked to obtain the inspection results of non-compliant parameters; (3) after traversing all clusters, the parameter inspection results of all workloads under all clusters are returned and integrated, and finally integrated into the report module of the unified management platform, and the results are displayed through email and platform modules to inform the responding personnel to ensure the validity and compliance of the parameters.

[0097] The cloud application configuration parameter verification method provided in the embodiment of the present application sets up a production access control verification before the cloud application is deployed before production, performs intelligent detection and early warning of parameters, and forcibly terminates the DevOps pipeline release of the application when the configuration parameters are not compliant, prevents the image file from being uploaded to the product library, and pushes the detection results to the platform to promote the subsequent optimization and improvement of the configuration parameters of each component. At the same time, intelligent detection can be performed adaptively to achieve regular inspections after the massive cloud applications are put into production. By combining the collected cloud service component configuration information with the rule base rules, the correctness of the configuration parameters of each component after the application is upgraded and changed is ensured, ensuring the robustness and stability of the system.

[0098] Figure 5 The schematic diagram of the structure of the cloud application configuration parameter verification device provided by this application is as follows: Figure 5 As shown, the cloud application configuration parameter verification device 50 provided in this embodiment includes:

[0099] An acquisition module 501 is used to acquire configuration information of an application component, where the configuration information includes multiple configuration parameters and a configuration version corresponding to each configuration parameter. The application component includes a single application component in a pipeline and a full application component in a cloud environment.

[0100] A determination module 502, configured to determine, for each configuration parameter, a standard value of the configuration parameter according to a configuration version corresponding to the configuration parameter;

[0101] A matching module 503 is used to determine a parameter verification rule corresponding to the configuration parameter from a configuration rule library based on the standard value, wherein the parameter verification rule includes at least one of an integrity verification rule, a data type verification rule, and a value range verification rule;

[0102] The verification module 504 is used to verify the configuration parameters according to the parameter verification rules and determine the verification results, which represent whether the configuration parameters meet the preset configuration requirements;

[0103] The generating module 505 is used to generate a configuration verification report according to the verification results corresponding to all configuration parameters.

[0104] In a possible implementation, when the application component is a single application component in a pipeline, the acquisition module 501 may also be used to:

[0105] In response to an operation of uploading an application image and a configuration file of a single application component in the pipeline, initial configuration information of the single application component is obtained from the application image;

[0106] The initial configuration information is standardized to obtain the configuration information of a single application component.

[0107] In a possible implementation, when the application component is a full application component in a cloud environment, the acquisition module 501 may also be used to:

[0108] Based on the preset interface of the cloud environment, obtain the full cluster information, which includes the cluster configuration information of multiple clusters and the full application components under each cluster;

[0109] For each cluster, based on the preset interface of the cloud environment, obtain the workload information of all application components in the cluster;

[0110] Determine the configuration information of all application components in the cluster based on the cluster configuration information and workload information of the cluster.

[0111] In a possible implementation, the generating module 505 may also be used to:

[0112] If there are configuration parameters in the configuration verification report that do not meet the preset configuration requirements, the construction and deployment process of a single application component in the pipeline will be terminated;

[0113] The configuration parameters that do not meet the preset configuration requirements and the corresponding verification results are sent to the terminal server for early warning.

[0114] In a possible implementation, the generating module 505 may also be used to:

[0115] For each cluster, determine the configuration verification report set corresponding to all full-scale application components in the cluster;

[0116] Send the configuration verification report set to the terminal server for visual display.

[0117] In a possible implementation, the generating module 505 may also be used to:

[0118] Determine an abnormal verification report in the configuration verification report set, where the abnormal verification report is a configuration verification report corresponding to a configuration parameter that does not meet a preset configuration requirement;

[0119] Generates a predefined tag for an abnormal verification report. The predefined tag is used to find configuration parameters that do not meet the preset configuration requirements in the configuration verification report collection.

[0120] In a possible implementation, the generating module 505 may also be used to:

[0121] Determine, according to the verification results corresponding to all configuration parameters, a first configuration parameter that does not meet the preset configuration requirement;

[0122] Obtaining the reason for the verification failure of the first configuration parameter;

[0123] A configuration verification report is generated according to the first configuration parameter, the verification failure reason, and the second configuration parameter that meets the preset configuration requirement.

[0124] The cloud application configuration parameter verification device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0125] Figure 6 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 6 As shown, the electronic device 60 provided in this embodiment includes: at least one processor 601 and a memory 602. Optionally, the device 60 also includes a communication component 603. The processor 601, the memory 602 and the communication component 603 are connected via a bus 604.

[0126] In a specific implementation process, at least one processor 601 executes the computer execution instructions stored in the memory 602, so that at least one processor 601 executes the above method.

[0127] The specific implementation process of the processor 601 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0128] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0129] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0130] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0131] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0132] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0133] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0134] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0135] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0136] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0137] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0138] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0139] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0140] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A method for verifying configuration parameters of cloud applications, characterized in that: Applied to configuration parameter verification system, including: Obtaining configuration information of an application component, the configuration information including multiple configuration parameters and a configuration version corresponding to each configuration parameter, the application component including a single application component in a pipeline and a full application component in a cloud environment; For each configuration parameter, determine a standard value of the configuration parameter according to the configuration version corresponding to the configuration parameter; Based on the standard value, determining a parameter verification rule corresponding to the configuration parameter from a configuration rule library, the parameter verification rule comprising at least one of an integrity verification rule, a data type verification rule, and a value range verification rule; Verifying the configuration parameters according to the parameter verification rule and determining a verification result, wherein the verification result indicates whether the configuration parameters meet the preset configuration requirements; Generate a configuration verification report based on the verification results corresponding to all configuration parameters.

2. The method according to claim 1, characterized in that When the application component is a single application component in a pipeline, The obtaining of configuration information of the application component includes: In response to the operation of uploading the application image and configuration file of the single application component in the pipeline, obtaining initial configuration information of the single application component from the application image; The initial configuration information is standardized to obtain the configuration information of the single application component.

3. The method according to claim 2, characterized in that After generating a configuration verification report according to the verification results corresponding to all configuration parameters, the method further includes: If there are configuration parameters in the configuration verification report that do not meet the preset configuration requirements, then terminating the construction and deployment process of the single application component in the pipeline; The configuration parameters that do not meet the preset configuration requirements and the corresponding verification results are sent to the terminal server for early warning.

4. The method according to claim 1, characterized in that: When the application component is a full-scale application component in the cloud environment, The obtaining of configuration information of the application component includes: Based on a preset interface of the cloud environment, obtain full cluster information, wherein the full cluster information includes cluster configuration information of multiple clusters and full application components under each cluster; For each cluster, based on a preset interface of the cloud environment, obtain workload information of all application components in the cluster; According to the cluster configuration information of the cluster and the workload information, configuration information of all application components in the cluster is determined.

5. The method according to claim 4, characterized in that After generating a configuration verification report according to the verification results corresponding to all configuration parameters, the method further includes: For each cluster, determine a set of configuration verification reports corresponding to all full-scale application components in the cluster; The configuration verification report set is sent to the terminal server for visual display.

6. The method according to claim 5, characterized in that Before sending the configuration verification report set to the terminal server for visual display, the method further includes: Determine an abnormal verification report in the configuration verification report set, where the abnormal verification report is a configuration verification report corresponding to a configuration parameter that does not meet a preset configuration requirement; A predefined tag for the abnormal verification report is generated, and the predefined tag is used to search the configuration parameters that do not meet the preset configuration requirements in the configuration verification report set.

7. The method according to claim 1, characterized in that The configuration verification report is generated according to the verification results corresponding to all configuration parameters, including: Determine, according to the verification results corresponding to all configuration parameters, a first configuration parameter that does not meet the preset configuration requirement; Obtaining a reason for a verification failure of the first configuration parameter; A configuration verification report is generated according to the first configuration parameter, the verification failure reason and the second configuration parameter that meets the preset configuration requirement.

8. A cloud application configuration parameter verification device, characterized in that: include: An acquisition module, used to acquire configuration information of an application component, wherein the configuration information includes multiple configuration parameters and a configuration version corresponding to each configuration parameter, and the application component includes a single application component in a pipeline and a full application component in a cloud environment; A determination module, configured to determine, for each configuration parameter, a standard value of the configuration parameter according to a configuration version corresponding to the configuration parameter; A matching module, configured to determine, based on the standard value, a parameter verification rule corresponding to the configuration parameter from a configuration rule library, wherein the parameter verification rule includes at least one of an integrity verification rule, a data type verification rule, and a value range verification rule; A verification module, used to verify the configuration parameters according to the parameter verification rules and determine a verification result, wherein the verification result indicates whether the configuration parameters meet the preset configuration requirements; The generation module is used to generate a configuration verification report based on the verification results corresponding to all configuration parameters.

9. An electronic device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images