Cluster configuration deployment method, device, equipment, storage medium and product

Abstract

The present application discloses a cluster configuration deployment method, device, equipment, storage medium and product, and relates to the field of computer technology. The cluster configuration deployment method includes: receiving configuration feature information and configuration selection information; according to the configuration selection information, confirming the extended component configuration and core component configuration corresponding to the configuration feature information in a preset component configuration library; combining the extended component configuration with the core component configuration to obtain a target cluster configuration; deploying the target cluster configuration to a preset business cluster. The present application selects the extended component configuration and the core component configuration in the component configuration library, combines them into a target cluster configuration, and realizes the package generation of the target cluster configuration, thereby realizing the quick deployment of the target cluster configuration to the business cluster, thereby improving the efficiency of cluster configuration deployment.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a cluster configuration and deployment method, apparatus, device, storage medium and product. Background Art

[0002] With the rapid development of cloud computing, big data, microservice architecture and distributed computing, enterprise-level application systems are increasingly relying on large-scale clusters to provide high-performance, scalable services. As the cluster size gradually becomes bloated, the difficulty of managing cluster configuration increases greatly.

[0003] The current cluster configuration deployment solution is to manually perform cluster configuration maintenance, but as the configuration involved in cluster building grows exponentially, the means of manually deploying cluster configurations are facing increasing challenges. Not only can it not use automation technology to track the entire life cycle of cluster configurations, but it also requires a huge amount of time and manpower costs to maintain increasingly complex configurations of different clusters, different environments, different component combinations, and different iteration versions. It is difficult to meet the complex requirements of cluster configuration generation, iteration, process control, and status tracking, resulting in low efficiency of cluster configuration deployment.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a cluster configuration deployment method, device, equipment, storage medium and product, aiming to solve the technical problem of low efficiency of cluster configuration deployment.

[0006] To achieve the above objectives, the present application proposes a cluster configuration deployment method, the method comprising:

[0007] receiving configuration feature information and configuration selection information;

[0008] According to the configuration selection information, confirming the extended component configuration and the core component configuration corresponding to the configuration feature information in a preset component configuration library;

[0009] Combining the extended component configuration with the core component configuration to obtain a target cluster configuration;

[0010] Deploy the target cluster configuration to a preset business cluster.

[0011] In one embodiment, the step of receiving configuration feature information includes:

[0012] Receiving original configuration files of different configuration feature information;

[0013] Obtaining configuration responsibility information of the original configuration file;

[0014] Classifying the original configuration file into an original extension component configuration and an original core component configuration according to the configuration responsibility information;

[0015] The original extension component configuration and the original core component configuration are saved to a preset component configuration library.

[0016] In one embodiment, the step of saving the original extension component configuration and the original core component configuration to a preset component configuration library includes:

[0017] Performing a deployment test on the extension component configuration or the core component configuration to obtain a first deployment test result;

[0018] If the first deployment test result meets the preset test requirements, the version information of the extension component configuration or the core component configuration is updated to the official version.

[0019] In one embodiment, the step of saving the original extension component configuration and the original core component configuration to a preset component configuration library includes:

[0020] Monitoring the configuration status of all component configurations in the component configuration library;

[0021] When the component configuration changes, update the corresponding configuration status;

[0022] When the component configuration is deployed to the preset component and a correct application signal is received, monitoring of the corresponding component configuration is stopped.

[0023] In one embodiment, the step of combining the extension component configuration with the core component configuration to obtain the target cluster configuration includes:

[0024] Generate an extension component configuration version number and a core component configuration version number based on the extension component configuration and the core component configuration according to a preset component version number generation rule;

[0025] According to a preset cluster version number generation rule, a cluster configuration version number is generated based on the extension component configuration version number and the core component configuration version number.

[0026] In one embodiment, the step of generating a cluster configuration version number includes:

[0027] Performing a deployment test on the target cluster configuration to obtain a second deployment test result;

[0028] If the second deployment test result meets the preset test requirements, the version information of the target cluster configuration is updated to the official version.

[0029] In addition, to achieve the above purpose, the present application also proposes a cluster configuration deployment device, the cluster configuration deployment device comprising:

[0030] A receiving module, used for receiving configuration feature information and configuration selection information;

[0031] A confirmation module, used to confirm the extended component configuration and the core component configuration corresponding to the configuration feature information in a preset component configuration library according to the configuration selection information;

[0032] A combination module, used to combine the extension component configuration with the core component configuration to obtain a target cluster configuration;

[0033] The deployment module is used to deploy the target cluster configuration to a preset business cluster.

[0034] In addition, to achieve the above objectives, the present application also proposes a cluster configuration deployment device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the cluster configuration deployment method described above.

[0035] In addition, to achieve the above objectives, the present application also proposes a storage medium, which is a computer-readable storage medium, and stores a computer program on the storage medium. When the computer program is executed by a processor, the steps of the cluster configuration deployment method described above are implemented.

[0036] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the cluster configuration deployment method described above are implemented.

[0037] One or more technical solutions proposed in this application have at least the following technical effects:

[0038] Compared with the related art, where manual deployment of cluster configuration consumes a great deal of time and manpower, resulting in low efficiency of cluster configuration deployment, the present application receives configuration feature information and configuration selection information; based on the configuration selection information, confirms the extended component configuration and core component configuration corresponding to the configuration feature information in the preset component configuration library; combines the extended component configuration with the core component configuration to obtain the target cluster configuration; and deploys the target cluster configuration to the preset business cluster. It is understandable that the present application adopts the method of selecting the extended component configuration and the core component configuration in the component configuration library according to the configuration feature information, combining them into the target cluster configuration, and deploying the preset business cluster. By selecting the extended component configuration and the core component configuration in the component configuration library, combining them into the target cluster configuration, the package generation of the target cluster configuration is realized, thereby realizing the quick deployment of the target cluster configuration to the business cluster, thereby improving the efficiency of cluster configuration deployment. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] 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.

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0041] Figure 1 A schematic diagram of a process flow provided for the first embodiment of the cluster configuration and deployment method of the present application;

[0042] Figure 2 A flow chart of the second embodiment of the cluster configuration and deployment method of the present application;

[0043] Figure 3 A brief flowchart of the cluster configuration and deployment method provided in Example 2 of the present application;

[0044] Figure 4 A schematic diagram of the module structure of a cluster configuration deployment device according to an embodiment of the present application;

[0045] Figure 5 A schematic diagram of the device structure of the hardware operating environment involved in the cluster configuration deployment method in the embodiment of the present application.

[0046] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0047] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0048] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0049] The main solutions of the embodiments of this application are:

[0050] receiving configuration feature information and configuration selection information;

[0051] According to the configuration selection information, confirming the extended component configuration and the core component configuration corresponding to the configuration feature information in a preset component configuration library;

[0052] Combining the extended component configuration with the core component configuration to obtain a target cluster configuration;

[0053] Deploy the target cluster configuration to a preset business cluster.

[0054] In this embodiment, the present application uses a cluster configuration deployment device as the execution subject. For ease of description, it is specifically described below as "device".

[0055] The existing technology relies on manual cluster configuration and maintenance, but as the configuration involved in cluster building grows exponentially, the means of manually deploying cluster configurations are facing increasing challenges. Not only can it not use automation technology to track the entire life cycle of cluster configurations, but it also requires a huge amount of time and manpower to maintain increasingly complex configurations of different clusters, different environments, different component combinations, and different iteration versions. It is difficult to meet the complex requirements of cluster configuration generation, iteration, process control, and status tracking, resulting in low efficiency of cluster configuration deployment.

[0056] Based on this, the present application embodiment provides a cluster configuration deployment method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the cluster configuration deployment method of the present application.

[0057] In this embodiment, the cluster configuration deployment method includes steps S10 to S40:

[0058] Step S10, receiving configuration feature information and configuration selection information;

[0059] It should be noted that the configuration feature information is a set of parameters that describe the characteristics and requirements of a component. The configuration selection information is the configuration options selected by the user according to the requirements.

[0060] Step S20, confirming the extended component configuration and the core component configuration corresponding to the configuration feature information in a preset component configuration library according to the configuration selection information;

[0061] It should be noted that the component configuration library is a database that stores multiple component configurations. The extended component configuration represents optional auxiliary components that further enhance the cluster function, including monitoring, logging, machine script automatic deployment and other components. The core component configuration represents the configuration of components required to build a minimum cluster, including necessary components such as container engine, CNI, DNS, etc.

[0062] Step S30, combining the extended component configuration with the core component configuration to obtain a target cluster configuration;

[0063] It should be noted that the target cluster configuration is the final container cluster configuration obtained through combination, which meets specific business needs and performance requirements.

[0064] Step S40: deploying the target cluster configuration to a preset service cluster.

[0065] It should be noted that the business cluster is a group of physical servers, virtual machines or containers that are configured and optimized to support specific business applications or services, and usually run the same or similar applications to provide high availability and load balancing.

[0066] The present application provides a solution, which selects extended component configuration and core component configuration in the component configuration library according to configuration feature information, combines them into a target cluster configuration, and deploys a preset business cluster. By selecting extended component configuration and core component configuration in the component configuration library and combining them into a target cluster configuration, package generation of the target cluster configuration is achieved, thereby achieving quick deployment of the target cluster configuration to the business cluster, thereby improving the efficiency of cluster configuration deployment.

[0067] In a feasible implementation manner, before step S10, the method further includes:

[0068] Receiving original configuration files of different configuration feature information;

[0069] Obtaining configuration responsibility information of the original configuration file;

[0070] Classifying the original configuration file into an original extension component configuration and an original core component configuration according to the configuration responsibility information;

[0071] The original extension component configuration and the original core component configuration are saved to a preset component configuration library.

[0072] It should be noted that the original configuration file is the initial version of the configuration information, which contains information such as environment variables, dependent services, network configuration, etc. required for the operation of the container. The configuration feature information is a specific attribute or parameter in the configuration file used to identify or distinguish different configuration items, including but not limited to the name, version, service or component of the configuration item, etc., which is used to identify and process in the configuration management process. The configuration responsibility information is the responsibilities and functions of each component configuration defined in the configuration file. The original extended component configuration refers to the configuration file of components that are not required for the core functions of the container cluster but can provide additional functions or services. The original core component configuration refers to the configuration files of those components that are critical to the normal operation of the container cluster. The component configuration library is a database that stores all component configuration files.

[0073] It is understandable that by properly classifying and managing these configuration files, the stability and flexibility of the cluster can be ensured.

[0074] Exemplarily, first, users can flexibly customize according to the different features of component configuration, and upload customized file directories to the platform for hosting. The platform provides the functions of generating, editing, and viewing component configurations. After uploading the file directory, users can edit the original file content directly on the platform according to the version iteration requirements, and the edited and saved files will be synchronized to the uploaded files. After the original file content of the platform meets the user's expectations, the user can organize the original file into a specific cm (an object for storing configuration data) through the generation configuration function and send it to the underlying management cluster, where the user can choose the access method (http interface access form, bestconfig cluster cm object access form), for the platform, version type and version number, the version number user can fill in a 12-digit unique number or generate the latest version number by default. When generating the configuration, the platform will package the original file configuration package based on the underlying kustomize command, that is, generate a version component configuration of the corresponding feature.

[0075] Users can package component configuration files of a certain type of feature on the platform's management page. The packages are divided into core component configuration packages and extended component configuration packages. The approval process allows the reviewer to further confirm the correctness and legality of the configuration. The reviewer can view the currently generated component configuration in the change order. After approval, the relevant changes to the component configuration of this version will initiate a PR review and merge into the git component library, and at the same time be sent to the underlying management cluster for subsequent use.

[0076] In a feasible implementation manner, after the step of saving the original extension component configuration and the original core component configuration to a preset component configuration library, the following steps are included:

[0077] Performing a deployment test on the extension component configuration or the core component configuration to obtain a first deployment test result;

[0078] If the first deployment test result meets the preset test requirements, the version information of the extension component configuration or the core component configuration is updated to the official version.

[0079] It should be noted that the extended component configuration refers to the configuration of components that provide additional functions or services for the container cluster, which is not required for the core functions of the cluster, but can enhance the functions of the cluster. The core component configuration refers to the configuration of components that are critical to the normal operation of the container cluster. The deployment test is a series of tests performed on the configuration in the actual cluster environment to verify the correctness and stability of the configuration. The deployment test may include functional testing, performance testing, security testing, etc. to ensure that the configuration can achieve the expected effect in actual operation. The first deployment test result refers to the result obtained after the deployment test. These results will be used to evaluate whether the component configuration meets the requirements for cluster operation. The preset test requirements are standards or conditions set before the deployment test to determine whether the test results are qualified. These requirements may include specific performance indicators, error rates, resource utilization, etc. The version information is used to identify the update status of the component configuration, which helps to track the change history of the configuration and apply the correct configuration version in the cluster. The official version is when the configuration passes the deployment test and meets the preset test requirements, its version information will be updated to the official version.

[0080] It is understandable that when a component is deployed or changed, it must be associated with a certain version of the component configuration. Only after the process approval, the specific version of the component configuration can be applied to the component. The component configuration can be divided into test version and official version. The test version is used for verification, and the official version is used for production.

[0081] For example, before the official production is put into use, the user can issue and verify the component configuration of the test version, that is, select the test component configuration of a specific version for deployment and issuance, and convert the test version configuration to the official version according to whether the component deployment status meets expectations. The component configuration converted to the official version can be put into production and use. Among them, whether it is a test version or a formal version of the component configuration, when the configuration is issued, it will go through a process-based approval and be confirmed by relevant personnel, and it will be issued to the component after confirmation.

[0082] In a feasible implementation manner, after the step of saving the original extension component configuration and the original core component configuration to a preset component configuration library, the following steps are included:

[0083] Monitoring the configuration status of all component configurations in the component configuration library;

[0084] When the component configuration changes, update the corresponding configuration status;

[0085] When the component configuration is deployed to the preset component and a correct application signal is received, monitoring of the corresponding component configuration is stopped.

[0086] It should be noted that the component configuration library is a database or file system that stores all component configurations. The component configuration library is responsible for centrally managing the configuration information of all components in the cluster to facilitate unified configuration management and distribution. The component configuration refers to the configuration information of each component (such as services, applications, containers, etc.) in the cluster, which usually includes necessary parameters, environment variables, dependencies, etc., which are used to define the behavior and operating environment of the component. The configuration status refers to the current status of the component configuration, such as whether it has been deployed, whether it is being updated, whether it is in an error state, etc. The configuration status helps to monitor and manage the configuration of each component in the system. The monitoring refers to continuously observing and checking the status of component configurations to ensure that they run as expected. The monitoring process may involve automated tools for real-time detection of configuration changes and application status. The change refers to any modification or update of the component configuration. The change may include adding new configuration items, modifying the value of existing configurations, deleting outdated configurations, etc. The update configuration status means that when the component configuration changes, the corresponding configuration status needs to be updated in the component configuration library to reflect the latest configuration information. This helps to maintain configuration version control and track change history. The deployment refers to applying the component configuration to the preset component to make it effective. The deployment process may involve pushing configurations to specific nodes or containers in the cluster.

[0087] In addition, it should be noted that the preset component refers to a component that is pre-defined in the cluster and is used to test the component configuration. The correct application signal refers to the confirmation signal received from the preset component after the component configuration is deployed, indicating that the configuration has been successfully applied and the component is running normally. Stop monitoring means that once the component configuration is successfully deployed and the correct application signal is received, it is no longer necessary to monitor the component configuration. This means that the configuration has been running stably and can be temporarily removed from the monitoring list until new changes occur.

[0088] Exemplarily, after a component configuration is applied by a certain change, the background program will continue to track the configuration status until the configuration is correctly applied by the component. Among them, for a certain change in the component configuration, the configuration status of the change can be divided into waiting for approval, approved, waiting for distribution, executing, completed or not meeting expectations. Waiting for approval is a state that is not determined by the relevant approver, and it will be blocked until timeout; after approval, it will enter the waiting for distribution state, at which time the device will obtain the corresponding version configuration and generate a component deployment object and then distribute it; after the distribution is completed, it will enter the executing state, at which time the device will try to deploy according to the selected component configuration. If the deployment is successful, the change task status will be displayed as completed, otherwise it will change to not meeting expectations after a certain period of time, indicating that the current version of the component configuration cannot be deployed normally.

[0089] In a feasible implementation manner, before step S40, the following steps are included:

[0090] Generate an extension component configuration version number and a core component configuration version number based on the extension component configuration and the core component configuration according to a preset component version number generation rule;

[0091] According to a preset cluster version number generation rule, a cluster configuration version number is generated based on the extension component configuration version number and the core component configuration version number.

[0092] It should be noted that the component version number generation rule is a set of predefined rules or standards for determining how to generate version numbers for component configurations in a cluster, and may be based on specific naming conventions, dates, timestamps, change content or other logic to generate version numbers. The extended component configuration is an optional auxiliary component that represents further enhancement of cluster functions, including components such as monitoring, logging, and machine script automated deployment. The core component configuration is a configuration of components that represent the necessary requirements for building a minimum cluster, including necessary components such as container engine, CNI, and DNS. The extended component configuration version number is a unique identifier generated for the extended component configuration according to the preset component version number generation rule. The core component configuration version number is a unique identifier generated for the core component configuration according to the preset component version number generation rule. The cluster version number generation rule is a set of predefined rules or standards for determining how to generate a version number for the configuration of the entire cluster. By combining the extended component configuration version number and the core component configuration version number, a version number representing the configuration status of the entire cluster is generated. The cluster configuration version number is a unique identifier generated according to the preset cluster version number generation rule, combining the extended component configuration version number and the core component configuration version number. The cluster configuration version number reflects the current status of all component configurations in the cluster and is a key part of cluster configuration management.

[0093] For example, refer to Figure 2When generating a cluster configuration version, the components configured by the extension components and the components configured by the core components will generate their own version numbers according to the preset rules, and the two will generate the corresponding cluster configuration version numbers according to certain rules.

[0094] It is understandable that cluster configuration can be divided into extension component combination and core component combination. The combination of the two will be associated with a new cluster configuration version, which will be saved in the database after approval for subsequent cluster construction. Among them, the cluster version can be divided into 5 stages according to different life cycles, including:

[0095] Test version: a version used to test the correctness and reliability of cluster configuration, mainly used to build a test cluster.

[0096] Official version: After the test version passes the test and the bill of lading is approved, it will be upgraded to the official version.

[0097] Compatible version: When a new official version is generated and a cluster is still using the old official version, the old official version becomes a compatible version. If no cluster is using it, it becomes a historical version.

[0098] Historical versions: unused old official versions, unused compatible versions.

[0099] Abandoned version: After the test version is terminated, it will become an abandoned version.

[0100] Furthermore, when generating a cluster configuration version, the extension component combination and the core component combination components will generate their own group version numbers according to the above rules, and the two will generate corresponding cluster configuration version numbers according to certain rules. After the cluster configuration is generated, it is a test version by default, and it must be verified and tested before it can be turned into a formal version for production. Among them, except for the test version that does not require approval, the version status flow starting from the test version must be approved and confirmed by relevant personnel to ensure that the currently effective cluster configuration will not be arbitrarily destroyed.

[0101] In a feasible implementation manner, the step of generating a cluster configuration version number includes:

[0102] Performing a deployment test on the target cluster configuration to obtain a second deployment test result;

[0103] If the second deployment test result meets the preset test requirements, the version information of the target cluster configuration is updated to the official version.

[0104] It should be noted that the second deployment test result refers to the result obtained after performing a cluster configuration deployment test, which is used to evaluate whether the target cluster configuration meets the requirements for cluster operation.

[0105] It is understandable that after the cluster configuration is generated, it is a test version by default and must be verified and tested before it can be turned into a formal version for production. Among them, except for the test version that does not require approval, the version status flow starting from the test version must be approved and confirmed by relevant personnel to ensure that the currently effective cluster configuration will not be arbitrarily destroyed. At the same time, the status of the cluster configuration is also divided into waiting for approval, approved, waiting for issuance, executing, completed or not meeting expectations. The meaning of each stage is analogous to the component configuration.

[0106] This embodiment provides a cluster configuration deployment method, which adopts the method of selecting extended component configuration and core component configuration in the component configuration library according to configuration feature information, combining them into a target cluster configuration, and deploying a preset business cluster. By selecting extended component configuration and core component configuration in the component configuration library, combining them into a target cluster configuration, package generation of the target cluster configuration is realized, thereby realizing quick deployment of the target cluster configuration to the business cluster, thereby improving the efficiency of cluster configuration deployment.

[0107] For example, to help understand the implementation process of the cluster configuration deployment method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 3 , Figure 3 A brief flow chart of a cluster configuration and deployment method is provided, specifically:

[0108] The user first creates multiple component configurations in the management system. These configurations are various parameters and settings required for the cluster to run. The created configurations are versioned, which means that each configuration has a unique version number for easy management and tracking. The versioned configurations are integrated into the cluster configuration, which is a collection of configurations for the entire cluster. The cluster configuration is written or read into the database for easy storage and subsequent access. The user can view the details of the cluster configuration in the management system. The user uses the configuration through the management system, which may involve editing the configuration or applying it to a specific task. Before the configuration is applied, it may be necessary to go through the task approval process to ensure that the configuration change is authorized. The RuNiu system is an approval process system. Once the configuration is approved, the management system will track the configuration status to ensure that the configuration changes are correctly applied to the cluster. The configuration status will be synchronized with the business cluster at a regular interval to ensure that the configuration in the cluster is up to date. The management system is responsible for managing the cluster, including the distribution of configurations and monitoring of cluster status. Finally, the configuration will be distributed to the business cluster, completing the entire configuration deployment process.

[0109] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the cluster configuration and deployment method of the present application. More simple transformations based on this technical concept are all within the protection scope of the present application.

[0110] It is understandable that the standardized generation strategy and automated version iteration mechanism of this application greatly reduce the time cost of manual maintenance and configuration fault tolerance, ensure the consistency and stability of configuration, and reduce cluster construction failures caused by human operation. At the same time, through the overall configuration version maintenance outside the cluster and the component configuration version maintenance inside the cluster, the isolation and diversity of different cluster configuration applications are guaranteed. At the same time, based on the state perception and tracking of cluster configuration, the process control of cluster life cycle management is realized, thereby realizing efficient, flexible and reliable cluster configuration management.

[0111] This application also provides a cluster configuration deployment device, please refer to Figure 4 , the cluster configuration deployment device includes:

[0112] A receiving module 10, used to receive configuration feature information and configuration selection information;

[0113] A confirmation module 20, configured to confirm, in a preset component configuration library, the extended component configuration and the core component configuration corresponding to the configuration feature information according to the configuration selection information;

[0114] A combination module 30, used to combine the extended component configuration with the core component configuration to obtain a target cluster configuration;

[0115] The deployment module 40 is used to deploy the target cluster configuration to a preset service cluster.

[0116] And / or, the cluster configuration deployment device includes:

[0117] A first receiving module, used for receiving original configuration files with different configuration feature information;

[0118] A first acquisition module, used to acquire configuration responsibility information of the original configuration file;

[0119] A first classification module, configured to classify the original configuration file into an original extension component configuration and an original core component configuration according to the configuration responsibility information;

[0120] The first saving module is used to save the original extension component configuration and the original core component configuration to a preset component configuration library.

[0121] And / or, the cluster configuration deployment device includes:

[0122] A first test module is used to perform a deployment test on the extension component configuration or the core component configuration to obtain a first deployment test result;

[0123] The first updating module is used to update the version information of the extension component configuration or the core component configuration to a formal version if the first deployment test result meets a preset test requirement.

[0124] And / or, the cluster configuration deployment device includes:

[0125] A first monitoring module, used to monitor the configuration status of all component configurations in the component configuration library;

[0126] A second updating module, used for updating the corresponding configuration state when the component configuration changes;

[0127] The first stopping module is used to stop monitoring the corresponding component configuration when the component configuration is deployed to the preset component and a correct application signal is received.

[0128] And / or, the cluster configuration deployment device includes:

[0129] A first generating module, configured to generate an extension component configuration version number and a core component configuration version number based on the extension component configuration and the core component configuration according to a preset component version number generating rule;

[0130] The second generating module is used to generate a cluster configuration version number based on the extension component configuration version number and the core component configuration version number according to a preset cluster version number generating rule.

[0131] And / or, the cluster configuration deployment device includes:

[0132] A second test module is used to perform a deployment test on the target cluster configuration to obtain a second deployment test result;

[0133] The third updating module is used to update the version information of the target cluster configuration to the official version if the second deployment test result meets the preset test requirements.

[0134] The cluster configuration deployment device provided by the present application adopts the cluster configuration deployment method in the above embodiment, which can solve the technical problem of low efficiency of cluster configuration deployment. Compared with the prior art, the beneficial effects of the cluster configuration deployment device provided by the present application are the same as the beneficial effects of the cluster configuration deployment method provided by the above embodiment, and other technical features in the cluster configuration deployment device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0135] The present application provides a cluster configuration deployment device, which includes: at least one processor; and a memory that is communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the cluster configuration deployment method in the above-mentioned embodiment one.

[0136] Reference below Figure 5 , which shows a schematic diagram of the structure of a cluster configuration deployment device suitable for implementing an embodiment of the present application. The cluster configuration deployment device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, tablet computers, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PMPs (Portable Media Players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The cluster configuration deployment device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0137] like Figure 5 As shown, the cluster configuration deployment device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the cluster configuration deployment device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the cluster configuration deployment device to communicate with other devices wirelessly or wired to exchange data. Although the cluster configuration deployment device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0138] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0139] The cluster configuration deployment device provided by the present application adopts the cluster configuration deployment method in the above embodiment, which can solve the technical problem of low efficiency of cluster configuration deployment. Compared with the prior art, the beneficial effects of the cluster configuration deployment device provided by the present application are the same as the beneficial effects of the cluster configuration deployment method provided by the above embodiment, and other technical features in the cluster configuration deployment device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0140] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0141] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0142] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the cluster configuration deployment method in the above-mentioned embodiment.

[0143] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0144] The computer-readable storage medium may be included in the cluster configuration deployment device; or may exist independently without being assembled into the cluster configuration deployment device.

[0145] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the cluster configuration deployment device, the cluster configuration deployment device: receives configuration feature information and configuration selection information;

[0146] According to the configuration selection information, confirming the extended component configuration and the core component configuration corresponding to the configuration feature information in a preset component configuration library;

[0147] Combining the extended component configuration with the core component configuration to obtain a target cluster configuration;

[0148] Deploy the target cluster configuration to a preset business cluster.

[0149] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0150] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0151] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0152] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned cluster configuration deployment method, and can solve the technical problem of low efficiency of cluster configuration deployment. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the cluster configuration deployment method provided in the above-mentioned embodiment, and will not be repeated here.

[0153] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned cluster configuration deployment method when executed by a processor.

[0154] The computer program product provided by this application can solve the technical problem of low efficiency of cluster configuration and deployment. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the cluster configuration and deployment method provided by the above embodiment, which will not be repeated here.

[0155] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A cluster configuration deployment method, characterized in that: The method includes: receiving configuration feature information and configuration selection information; According to the configuration selection information, confirming the extended component configuration and the core component configuration corresponding to the configuration feature information in a preset component configuration library; Combining the extended component configuration with the core component configuration to obtain a target cluster configuration; Deploy the target cluster configuration to a preset business cluster.

2. The method according to claim 1, characterized in that The step of receiving configuration feature information includes: Receiving original configuration files of different configuration feature information; Obtaining configuration responsibility information of the original configuration file; Classifying the original configuration file into an original extension component configuration and an original core component configuration according to the configuration responsibility information; The original extension component configuration and the original core component configuration are saved to a preset component configuration library.

3. The method according to claim 2, characterized in that After the step of saving the original extension component configuration and the original core component configuration to a preset component configuration library, the method further comprises: Performing a deployment test on the extension component configuration or the core component configuration to obtain a first deployment test result; If the first deployment test result meets the preset test requirements, the version information of the extension component configuration or the core component configuration is updated to the official version.

4. The method according to claim 2, characterized in that After the step of saving the original extension component configuration and the original core component configuration to a preset component configuration library, the method further comprises: Monitoring the configuration status of all component configurations in the component configuration library; When the component configuration changes, update the corresponding configuration status; When the component configuration is deployed to the preset component and a correct application signal is received, monitoring of the corresponding component configuration is stopped.

5. The method according to claim 1, characterized in that The step of combining the extension component configuration with the core component configuration to obtain the target cluster configuration includes: Generate an extension component configuration version number and a core component configuration version number based on the extension component configuration and the core component configuration according to a preset component version number generation rule; According to a preset cluster version number generation rule, a cluster configuration version number is generated based on the extension component configuration version number and the core component configuration version number.

6. The method according to claim 5, characterized in that The step of generating a cluster configuration version number includes: Performing a deployment test on the target cluster configuration to obtain a second deployment test result; If the second deployment test result meets the preset test requirements, the version information of the target cluster configuration is updated to the official version.

7. A cluster configuration deployment device, characterized in that: The device comprises: A receiving module, used for receiving configuration feature information and configuration selection information; A confirmation module, used to confirm the extended component configuration and the core component configuration corresponding to the configuration feature information in a preset component configuration library according to the configuration selection information; A combination module, used to combine the extension component configuration with the core component configuration to obtain a target cluster configuration; The deployment module is used to deploy the target cluster configuration to a preset business cluster.

8. A cluster configuration deployment device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the cluster configuration deployment method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the cluster configuration and deployment method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the cluster configuration deployment method according to any one of claims 1 to 6 are implemented.

Images