Service deployment method and device, electronic equipment and storage medium

Abstract

The invention provides a service deployment method and device, electronic equipment and a storage medium, and relates to the technical field of computers. In the application, after at least one node cluster for deploying the instance corresponding to the target service is determined, the instance can be deployed on a plurality of working nodes included in the at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance is completed on the plurality of working nodes, the instance can be deployed on the at least one node cluster. And sending the target configuration information to the plurality of working nodes respectively, thereby receiving configuration information comparison results reported by the plurality of working nodes respectively. Therefore, whether the instance corresponding to the target service is deployed on the plurality of working nodes or not can be effectively monitored through the comparison result of the plurality of pieces of received configuration information, so that the stability of service deployment is ensured.

Description

Technical Field

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

[0002] Service deployment plays an important role in network services. Stable service deployment can ensure high availability and security of network services, thereby better meeting the service needs of target objects. Currently, service deployment mainly relies on update and release tools. Although it can improve the efficiency of service deployment, it is obviously insufficient in ensuring the stability of service deployment.

[0003] In view of this, how to improve the stability of service deployment is an issue that needs to be addressed urgently. Summary of the invention

[0004] Embodiments of the present application provide a service deployment method, device, electronic device, and storage medium to improve the stability of service deployment.

[0005] In a first aspect, an embodiment of the present application provides a service deployment method, the method comprising:

[0006] In response to a deployment request for a target service, determining at least one node cluster for deploying an instance corresponding to the target service;

[0007] Based on the target configuration information of the instance, deploy the instance on multiple working nodes included in at least one node cluster, and when it is determined that the deployment of the instance on the multiple working nodes is completed, send the target configuration information to the multiple working nodes respectively;

[0008] Receive configuration information comparison results reported by multiple working nodes respectively; wherein each configuration information comparison result represents whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information.

[0009] In an optional embodiment, determining at least one node cluster for deploying an instance corresponding to a target service includes:

[0010] Determine the number of worker nodes for the deployment instance based on the service requirements for the target service;

[0011] Based on the number of working nodes, at least one node cluster is selected from the preset multiple node clusters.

[0012] In an optional embodiment, deploying the instance on multiple working nodes included in at least one node cluster based on target configuration information of the instance includes:

[0013] A hierarchical release strategy for an instance is set for at least one node cluster; the hierarchical release strategy is used to indicate multiple deployment stages for deploying the instance in at least one node cluster;

[0014] Deploy instances on multiple working nodes based on the hierarchical release strategy and target configuration information.

[0015] In an optional embodiment, based on the hierarchical release strategy and target configuration information, instances are deployed on multiple working nodes, including:

[0016] For the multiple deployment stages included in the staged release strategy, perform the following operations respectively:

[0017] Deploy the instance on at least one node corresponding to a deployment phase based on the target configuration information;

[0018] When it is determined that at least one node has completed the deployment of the instance, an instance operation result corresponding to the at least one node is obtained; wherein each instance operation result represents whether the instance deployed on the corresponding node can provide the target service;

[0019] If at least one instance running result is a target instance running result indicating that the instance deployed on the corresponding node can provide the target service, then the instance deployment of the next deployment phase begins.

[0020] In an optional embodiment, after deploying the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, the method further includes:

[0021] Perform instance deployment detection on multiple working nodes to obtain corresponding instance deployment detection results;

[0022] If the instance deployment detection result indicates that the instance deployment on the multiple working nodes does not meet the preset instance deployment requirements, an instance deployment rollback operation is performed on the multiple working nodes.

[0023] In an optional embodiment, performing an instance deployment rollback operation on multiple working nodes includes:

[0024] Determine first concurrencies corresponding to multiple deployment phases when deploying instances on multiple working nodes, and perform instance deployment rollback operations on multiple working nodes based on the multiple first concurrencies and their corresponding rollback phases;

[0025] Based on a preset accelerated rollback rule, determine the second concurrency of the rollback phase corresponding to the multiple deployment phases respectively, and perform instance deployment rollback operations on the multiple working nodes based on the multiple second concurrencies; or,

[0026] Based on the current maximum concurrency, perform instance deployment rollback operations on multiple working nodes.

[0027] In an optional embodiment, the method further includes:

[0028] In response to an abnormal event occurring during instance deployment for a target service, determining an instance deployment termination mode set for the target service;

[0029] Stop instance deployment for the target service based on instance deployment termination mode.

[0030] In a second aspect, an embodiment of the present application further provides a service deployment device, the device comprising:

[0031] A request response module, configured to determine at least one node cluster for deploying an instance corresponding to the target service in response to a deployment request of the target service;

[0032] An instance deployment module, configured to deploy the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance is completed on the multiple working nodes, send the target configuration information to the multiple working nodes respectively;

[0033] The information receiving module is used to receive configuration information comparison results reported by multiple working nodes respectively; wherein each configuration information comparison result represents whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information.

[0034] In an optional embodiment, when determining at least one node cluster for deploying an instance corresponding to a target service, the request response module is specifically configured to:

[0035] Determine the number of worker nodes for the deployment instance based on the service requirements for the target service;

[0036] Based on the number of working nodes, at least one node cluster is selected from the preset multiple node clusters.

[0037] In an optional embodiment, when deploying an instance on multiple working nodes included in at least one node cluster based on target configuration information of the instance, the instance deployment module is specifically used to:

[0038] A hierarchical release strategy for an instance is set for at least one node cluster; the hierarchical release strategy is used to indicate multiple deployment stages for deploying the instance in at least one node cluster;

[0039] Deploy instances on multiple working nodes based on the hierarchical release strategy and target configuration information.

[0040] In an optional embodiment, when deploying instances on multiple working nodes based on the hierarchical release strategy and target configuration information, the instance deployment module is specifically used to:

[0041] For the multiple deployment stages included in the staged release strategy, perform the following operations respectively:

[0042] Deploy the instance on at least one node corresponding to a deployment phase based on the target configuration information;

[0043] When it is determined that at least one node has completed the deployment of the instance, an instance operation result corresponding to the at least one node is obtained; wherein each instance operation result represents whether the instance deployed on the corresponding node can provide the target service;

[0044] If at least one instance running result is a target instance running result indicating that the instance deployed on the corresponding node can provide the target service, then the instance deployment of the next deployment phase begins.

[0045] In an optional embodiment, after deploying the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, the instance deployment module is further used to:

[0046] Perform instance deployment detection on multiple working nodes to obtain corresponding instance deployment detection results;

[0047] If the instance deployment detection result indicates that the instance deployment on the multiple working nodes does not meet the preset instance deployment requirements, an instance deployment rollback operation is performed on the multiple working nodes.

[0048] In an optional embodiment, when performing an instance deployment rollback operation on multiple working nodes, the instance deployment module is specifically used to:

[0049] Determine first concurrencies corresponding to multiple deployment phases when deploying instances on multiple working nodes, and perform instance deployment rollback operations on multiple working nodes based on the multiple first concurrencies and their corresponding rollback phases;

[0050] Based on a preset accelerated rollback rule, determine the second concurrency of the rollback phase corresponding to the multiple deployment phases respectively, and perform instance deployment rollback operations on the multiple working nodes based on the multiple second concurrencies; or,

[0051] Based on the current maximum concurrency, perform instance deployment rollback operations on multiple working nodes.

[0052] In an optional embodiment, the instance deployment module is further used to:

[0053] In response to an abnormal event occurring during instance deployment for a target service, determining an instance deployment termination mode set for the target service;

[0054] Stop instance deployment for the target service based on instance deployment termination mode.

[0055] In a third aspect, an embodiment of the present application further provides an electronic device, including:

[0056] Processor; and

[0057] Memory for storing programs,

[0058] The program includes instructions, which, when executed by a processor, cause the processor to execute the service deployment method as described in the first aspect.

[0059] In a fourth aspect, an embodiment of the present application further provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the service deployment method as described in the first aspect.

[0060] In a fifth aspect, the present application provides a computer program product, which, when called by a computer, enables the computer to execute the steps of the service deployment method as described in the first aspect.

[0061] The beneficial effects of this application are as follows:

[0062] In the service deployment method provided in the embodiment of the present application, after determining at least one node cluster of the instance corresponding to the deployment target service, the instance can be deployed on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance is completed on multiple working nodes, the target configuration information is sent to the multiple working nodes respectively, thereby receiving the configuration information comparison results reported by the multiple working nodes respectively; wherein each configuration information comparison result represents whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information. In this way, it is possible to effectively monitor whether the instance corresponding to the target service is deployed on multiple working nodes through the comparison results of the received multiple configuration information, thereby ensuring the stability of the service deployment.

[0063] In addition, other features and advantages of the present application will be described in the subsequent description, and partly become apparent from the description, or be understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described here are used to provide a further understanding of the present application, constitute a part of the present application, and do not constitute an improper limitation on the present application. In the drawings:

[0065] Figure 1 A schematic diagram of an optional system architecture applicable to the embodiments of the present application;

[0066] Figure 2 A schematic diagram of an implementation flow of a service deployment method provided in an embodiment of the present application;

[0067] Figure 3 A logical schematic diagram of service deployment based on a hierarchical publishing strategy provided in an embodiment of the present application;

[0068] Figure 4 A logical diagram of a refined rollback provided in an embodiment of the present application;

[0069] Figure 5 A logical schematic diagram based on configuration information comparison results provided in an embodiment of the present application;

[0070] Figure 6 A schematic diagram of a specific application scenario of a service deployment provided in an embodiment of the present application;

[0071] Figure 7 A schematic diagram of the structure of a service deployment device provided in an embodiment of the present application;

[0072] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as being limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not intended to limit the scope of protection of the present application.

[0074] It should be understood that the various steps described in the method implementation of the present application can be performed in different orders and / or performed in parallel. In addition, the method implementation may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this respect.

[0075] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below. It should be noted that the concepts of "first", "second", etc. mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0076] It should be noted that the modifications of "one" and "plurality" mentioned in the present application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0077] The names of the messages or information exchanged between multiple devices in the embodiments of the present application are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0078] Some of the terms used in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

[0079] (1) Tiered release: This refers to the process in which information technology (IT) systems that have already provided services to users are grouped according to a fixed logical division strategy and gradually implemented in order to reduce the impact of deployment operations and program processing problems on users.

[0080] (2) Service: is an abstract concept, usually referring to the functions or capabilities provided through the network. Service is the basic object of deployment. There can be multiple services, and the smallest deployment unit is a service.

[0081] (3) Instance: refers to the specific program or process of a service running on a specific server, which can realize the specific functions of the service. A service can contain one or more instances, that is, a service can be provided by one or more instances.

[0082] (4) Rollback: refers to the act of restoring a program or data to its previous state, or it can refer to the act of restoring a system to its previous version. Rollback includes program rollback and data rollback.

[0083] Based on the above-mentioned nouns and related terminology explanations, the design concept of the embodiments of the present application is briefly introduced below:

[0084] The automated deployment of services mainly relies on update and release tools. Although these tools can improve the efficiency of service deployment, they are obviously insufficient in terms of the stability of service deployment. For example, in the scenario of high-availability deployment of instances, the aforementioned tools cannot effectively monitor the coverage of the new version on all servers, which may easily lead to some instances not being updated.

[0085] Therefore, in order to solve or improve the above-mentioned problems, an embodiment of the present application proposes a service deployment method, which may specifically include: in response to a deployment request of a target service, determining at least one node cluster for deploying an instance corresponding to the target service; based on the target configuration information of the instance, deploying the instance on multiple working nodes included in at least one node cluster, and when it is determined that the deployment of the instance is completed on multiple working nodes, sending the target configuration information to the multiple working nodes respectively; receiving configuration information comparison results reported by multiple working nodes respectively; wherein each configuration information comparison result represents whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information.

[0086] By adopting the above method, by comparing the received multiple configuration information results, it is possible to effectively monitor whether the instance corresponding to the target service is deployed on multiple working nodes, thereby ensuring the stability of service deployment.

[0087] In particular, the preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application, and the embodiments of the present application and the features in the embodiments may be combined with each other if there is no conflict.

[0088] See also Figure 1 As shown, it is a schematic diagram of the system architecture of a service deployment system applicable to an embodiment of the present application, and the system architecture may include: at least one control node 101 and multiple worker nodes 102. Among them, the control node 101 can also be called a master node, and the worker node 102 can also be called a slave node. The control node 101 can manage the worker node 102. For example, the control node 101 can create, schedule or delete an instance deployed on the worker node 102. After the worker node 102 deploys the instance, it can provide the service corresponding to the instance.

[0089] The control node 101 and the working node 102 can exchange information through a communication network, wherein the communication mode adopted by the communication network may include: wireless communication mode and wired communication mode. Exemplarily, the control node 101 can access the network through cellular mobile communication technology to communicate with the working node 102. The cellular mobile communication technology, for example, includes the fifth generation mobile communication (5th generation mobile networks, 5G) technology or the next generation mobile communication technology. Optionally, the control node 101 can access the network through a short-range wireless communication mode to communicate with the working node 102. The short-range wireless communication mode, for example, includes wireless fidelity (wireless fidelity, Wi-Fi) technology.

[0090] In an embodiment of the present application, the working node 101 can determine at least one node cluster for deploying an instance corresponding to the target service in response to a deployment request of the target service; deploy the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance is completed on multiple working nodes, send the target configuration information to the multiple working nodes respectively; receive the configuration information comparison results reported by the multiple working nodes respectively. Among them, each configuration information comparison result can represent whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information. Therefore, it is possible to effectively monitor whether the instance corresponding to the target service is deployed on multiple working nodes.

[0091] The following describes a service deployment method provided by an exemplary embodiment of the present application in combination with the above-mentioned system architecture and with reference to the accompanying drawings. It should be noted that the above-mentioned system architecture is only shown to facilitate understanding of the spirit and principles of the present application, and the implementation of the present application is not limited in this regard.

[0092] See also Figure 2 As shown, it is a schematic diagram of an implementation process of a service deployment method provided in an embodiment of the present application. The execution subject takes the control node in the service deployment system as an example. The specific implementation process of the method is as follows:

[0093] S201: In response to a deployment request of a target service, determine at least one node cluster for deploying an instance corresponding to the target service.

[0094] Before executing step S201, the user or application developer may pre-create a target service. For example, the user or application developer may pre-create a target service with a service name of "hello world". The target service may provide a user with specific network services or capabilities to meet the user's network usage needs.

[0095] Since the target service is ultimately to be run on a working node (e.g., a hardware server), in order to ensure the high availability of the target service, the target service needs to be deployed on multiple working nodes at the same time, and each working node can provide the same function to the outside, that is, the network service or capability corresponding to the target service. Therefore, after receiving the deployment request of the target service, the control node needs to quickly determine at least one node cluster for deploying the instance corresponding to the target service. Optionally, for a system architecture with multiple computer rooms, the node cluster can be a computer room, and the working node can be a server in the computer room.

[0096] Therefore, in an optional implementation, the control node can determine the number of working nodes of the deployment instance based on the service demand for the target service, and thus select at least one node cluster from the preset multiple node clusters based on the number of working nodes. In this way, the number of working nodes of the deployment instance is determined according to the service demand for the target service, which not only meets the maximum service demand for the target service, but also reduces the waste of excessive node resources.

[0097] It should be understood that the total number of nodes corresponding to at least one node cluster mentioned above for the working node may be greater than the number of working nodes required for the deployment instance, but the total number of nodes corresponding to other node clusters except any one node cluster in the at least one node cluster mentioned above should be less than the number of working nodes required for the deployment instance.

[0098] S202: deploying the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance on the multiple working nodes is completed, sending the target configuration information to the multiple working nodes respectively.

[0099] The target configuration information may be information such as the application (e.g., code) and version corresponding to the instance selected by the user or application developer. For example, the control node may filter out target configuration information that meets the user's needs from a preset configuration information set. The preset configuration information set may include multiple candidate configuration information.

[0100] In an optional implementation, when the control node deploys the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, the control node may set a hierarchical release strategy for the instance for the at least one node cluster, thereby deploying the instance on the multiple working nodes based on the hierarchical release strategy and the target configuration information. The hierarchical release strategy may be used to indicate multiple deployment stages for deploying the instance in the at least one node cluster.

[0101] Taking two node clusters (for example, node cluster A and node cluster B) as an example, the control node can set a hierarchical release strategy including four deployment stages for the two node clusters, that is, the multiple working nodes included in the two node clusters are distributed according to four levels. For example, the four deployment stages included in the hierarchical release strategy are as follows:

[0102] The first deployment stage: hbas, that is, launching or deploying an instance in a working node in node cluster A. The second deployment stage: hbao, that is, launching or deploying an instance in all other working nodes in node cluster A. The third deployment stage: hbas, that is, launching or deploying an instance in a working node in node cluster B. The fourth deployment stage: hbao, that is, launching or deploying an instance in all other working nodes in node cluster B.

[0103] It should be understood that the above-mentioned hierarchical publishing strategy, that is, the specific rules of hierarchical publishing, can be obtained by defining and using a formulation template of the hierarchical publishing strategy, and the embodiment of the present application does not limit the formulation template of the hierarchical publishing strategy.

[0104] After each deployment phase is released (i.e., instance deployment is completed), the working node of the deployed instance can be verified to determine whether the working node of the deployed instance can provide the target service. If the working node can provide the target service after the instance is deployed, it can be determined that the instance deployed on the working node meets expectations (i.e., meets the service requirements), which means that the current deployment phase meets the deployment requirements of the instance, thereby ensuring the reliability of the instance deployment.

[0105] Therefore, in an optional implementation, the control node can perform the following operations for any one of the multiple deployment stages included in the hierarchical release strategy: deploy an instance on at least one node corresponding to a deployment stage based on the target configuration information; then, when it is determined that the aforementioned at least one node has completed the deployment of the instance, obtain the instance operation results corresponding to the aforementioned at least one node; finally, if at least one instance operation result is a target instance operation result that indicates that the instance deployed on the corresponding node can provide the target service, the instance deployment of the next deployment stage can be started. Each instance operation result indicates whether the instance deployed on the corresponding node can provide the target service.

[0106] Based on the service deployment method based on the hierarchical release strategy described in the above steps, refer to Figure 3As shown, after the user or application developer creates a target service (e.g., a service named "helloworld"), the master server (i.e., control node) can allocate servers (i.e., working nodes) to the instances corresponding to the target service. For example, the six servers included in the server room A in the server room can be used as multiple working nodes included in one node cluster, and the six servers included in the server room B in the server room can be used as multiple working nodes included in another node cluster.

[0107] Next, the master control server may define a hierarchical publishing template (i.e., a hierarchical publishing strategy), which may specifically include: the first deployment stage (i.e., Stage 1): hbas, i.e., a server (e.g., server A3) in the A computer room assigned to the target service is launched or an instance corresponding to the target service is deployed. The second deployment stage (i.e., Stage 2): hbao, i.e., five servers (i.e., server A1, server A2, server A4, server A5, and server A6) other than server A3 in the A computer room assigned to the target service are launched or an instance corresponding to the target service is deployed. The third deployment stage (i.e., Stage 3): hbas, i.e., a server (e.g., server B3) in the B computer room assigned to the target service is launched or an instance corresponding to the target service is deployed. The fourth deployment stage (i.e., Stage 4): hbao, i.e., five servers (i.e., server B1, server B2, server B4, server B5, and server B6) other than server B3 in the B computer room assigned to the target service are launched or an instance corresponding to the target service is deployed.

[0108] After the release or deployment of the instance is completed in each deployment stage, the target service can be verified or tested by multiple servers in the deployment stage. If the multiple servers in the deployment stage can provide the service functions corresponding to the target service well, it can be determined that the instance deployment in the deployment stage meets expectations, and then the instance release or deployment of the next deployment stage can be started.

[0109] Before deploying the instance according to the above four deployment stages, the master server needs to select the corresponding module and its version to be deployed. Among them, the module is a piece of code (i.e., the target configuration information) selected from the code base (i.e., the preset configuration information set) to provide the target service. It should be understood that the code base will be repeatedly iterated during development, and each iteration will generate a version number. When deploying the module, the corresponding version can be selected for instance deployment.

[0110] Exemplarily, the above code base may include at least one version corresponding to different codes. For example, the code base may include 4 codes, specifically including: Code 1: nignx, code version: 1.0.1, 1.0.2, 1.0.3; Code 2: mysql, code version: 1.0.1, 1.0.2, 1.0.3, 1.0.4; Code 3: redis, code version: 1.0.1, 1.0.2, 1.0.3, 1.0.4; Code 4: helloword, code version: 1.0.1, 1.0.2.

[0111] Since the code in the code base is usually static, it needs to execute commands to run. Therefore, the master server can create a special startup instruction for the target service (or instance) and bind it to the module corresponding to the target service.

[0112] Furthermore, the master server can deploy instances in the above four deployment stages based on the hierarchical release template. That is, the first deployment stage is released first, and after verification, the second deployment stage is released, and so on, until the release is completed (i.e., the deployment is completed). Optionally, each server can record the version number of the deployment instance under the server's deployment path.

[0113] In an optional implementation, after the control node deploys the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, the control node can also perform instance deployment detection on the multiple working nodes to obtain corresponding instance deployment detection results; if the instance deployment detection results indicate that the instance deployment on the multiple working nodes does not meet the preset instance deployment requirements, the instance deployment rollback operation can be performed on the multiple working nodes.

[0114] The preset instance deployment requirement may be a service requirement set for the plurality of working nodes when providing a target service. The embodiment of the present application does not specifically limit the preset instance deployment requirement.

[0115] The instance deployment rollback operation of the above instance can roll back the instances deployed on the above multiple working nodes from the current configuration information to the historical configuration information when it is determined that the instance deployment on the above multiple working nodes does not meet the preset instance deployment requirements, so as to subsequently re-deploy the instances corresponding to the target configuration information on the above multiple working nodes. It should be understood that the aforementioned historical configuration information is the configuration information that meets the preset instance deployment requirements during the previous instance deployment process.

[0116] When the control node needs to perform an instance deployment rollback operation on the above-mentioned multiple working nodes, it can use any of the following three methods to perform an instance deployment rollback operation on the multiple working nodes:

[0117] Method 1: Determine first concurrency corresponding to multiple deployment phases when deploying instances on multiple working nodes, and perform instance deployment rollback operations on multiple working nodes based on the multiple first concurrencies and their corresponding rollback phases.

[0118] By adopting the above-mentioned method 1, the control node can perform instance deployment rollback operations on multiple working nodes according to the concurrency in the hierarchical publishing process (i.e., the first concurrency). That is, when the instance deployment is rolled back, the control node directly reuses the concurrency configuration in the distributed publishing. Specifically, in each deployment stage of the hierarchical publishing, the control node will gradually deploy the instances corresponding to the target service to each server according to the set concurrency (i.e., the first concurrency). Therefore, when the instance deployment is rolled back, the control node can perform the instance deployment rollback from the first concurrency corresponding to each of the multiple deployment stages determined in the hierarchical publishing strategy, thereby ensuring that each rollback stage is consistent with the corresponding deployment stage.

[0119] Method 2: Based on a preset accelerated rollback rule, the second concurrency of the rollback phase corresponding to the multiple deployment phases is determined, and based on the multiple second concurrencies, the instance deployment rollback operation of the instance is performed on the multiple working nodes.

[0120] Still taking the above-mentioned hierarchical release strategy including four deployment stages as an example, the aforementioned preset accelerated rollback rules can specifically be: the second concurrency of the first rollback stage corresponding to the fourth deployment stage is 20%, the second concurrency of the second rollback stage corresponding to the third deployment stage is 30%, the second concurrency of the third rollback stage corresponding to the second deployment stage is 50%, and the second concurrency of the fourth rollback stage corresponding to the first deployment stage is 80%.

[0121] By adopting the above-mentioned method 2, in the scenario where the instance deployment rollback needs to be accelerated, the control node can perform instance deployment rollback operations on multiple working nodes according to the preset accelerated rollback rules, thereby significantly shortening the rollback time of the instance deployment. That is, the control node can control the number of working nodes that simultaneously perform instance deployment rollback in each rollback phase based on dynamically adjustable concurrency control parameters and through corresponding scripts or application programming interfaces (application programming interfaces, APIs), thereby gradually increasing the concurrency. Optionally, the control node can use a thread pool or an asynchronous task queue to set the second rollback degree corresponding to each rollback phase.

[0122] Method 3: Based on the current maximum concurrency, perform instance deployment rollback operations on multiple working nodes.

[0123] By adopting the above-mentioned method 3, in an emergency, the control node can select full concurrency rollback (ie, the current maximum concurrency) to perform instance deployment rollback operations on multiple working nodes.

[0124] At this point, the control node can cancel the release strategy of any deployment stage and complete the instance deployment rollback in the shortest time by maximizing concurrency. For example, the control node can set the upper limit of concurrency control (i.e. the current maximum concurrency) to allow all working nodes to perform instance deployment rollbacks (e.g., version switching) at the same time. Optionally, the control node can automatically detect the completion status of the deployment rollback and generate detailed logs to ensure that all working nodes complete the rollback smoothly.

[0125] Based on the above three instance deployment rollback methods, the control node can achieve Figure 4 The refined rollback shown. Still taking the hierarchical release strategy including 4 deployment stages and the node cluster including computer room A and computer room B as an example, for the above-mentioned method 1 (i.e. normal rollback). The first rollback stage is the fourth deployment stage (i.e. Stage 4): hbao, that is, the five servers (i.e. server B1, server B2, server B4, server B5 and server B6) in computer room B except server B3 are deployed and rolled back one by one. The second rollback stage is the third deployment stage (i.e. Stage 3): hbas, that is, the instance deployment is rolled back on server B3 in computer room B. The third rollback stage is the second deployment stage (i.e. Stage 2): hbao, that is, the five servers (i.e. server A1, server A2, server A4, server A5 and server A6) in computer room A except server A3 are deployed and rolled back one by one. The fourth rollback stage is the first deployment stage (i.e. Stage 1): hbas, that is, the instance deployment is rolled back on server A3 in computer room A.

[0126] For the above-mentioned method 2 (accelerated concurrent rollback). The first rollback stage (i.e. Stage 4): hbao, concurrent rollback of instance deployment is performed on the 5 servers in the B computer room except server B3 with a concurrency of 20%. The second rollback stage is (i.e. Stage 3): hbas, instance deployment rollback is performed on server B3 in the B computer room with a concurrency of 30%. The third rollback stage (i.e. Stage 2): hbao, concurrent rollback of instance deployment is performed on the 5 servers in the A computer room except server A3 with a concurrency of 50%. The fourth rollback stage (i.e. Stage 1): hbas, instance deployment rollback is performed on server A3 in the A computer room with a concurrency of 80%. For the above-mentioned method 3 (full concurrent rollback), instance deployment rollback is performed on all servers included in the A computer room and the B computer room at the same time with the current maximum concurrency.

[0127] It can be seen that based on the above-mentioned refined rollback, the problem of making decisions in real time according to the situation of the business or service deployment system in the related technology and the high stability risk during the rollback process can be improved, that is, the stability of service deployment is further improved.

[0128] S203: Receive configuration information comparison results reported by multiple working nodes respectively.

[0129] Among them, each configuration information comparison result can represent whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information of the instance. In this way, after receiving the configuration information comparison results reported by the above-mentioned multiple working nodes, the control node can determine whether the actual configuration information of the instance deployed on the above-mentioned multiple working nodes is the target configuration information of the instance determined by the control node. Once it is found that the actual configuration information of the instance deployed on a certain working node is different from the target configuration information, the control node can promptly adjust (e.g., roll back) the instance deployment on the working node to ensure that the working node can better provide the target service.

[0130] For example, see Figure 5 As shown, when executing step S203, the control node can set a scheduled task (e.g., a Cron scheduled task, etc.) for the above-mentioned multiple working nodes. For example, the scheduled task can be executed every set time (e.g., 1 hour or 5 minutes, etc.). The aforementioned scheduled task can specifically include the following steps:

[0131] 1) Obtaining actual configuration information: Each working node can read the actual configuration information of the instance by calling a script, where the actual configuration information is stored in a specific file of the working node (e.g., / etc / module_version).

[0132] 2) Obtain target configuration information: Each working node can obtain the target configuration information corresponding to the target service (i.e., the configuration information of the instance selected by the user) from the control node through API requests or remote calls. In other words, the control node can send the stored target configuration information to multiple working nodes.

[0133] 3) Configuration information difference comparison: Each working node compares the actual configuration information read locally by the scheduled task script with the target configuration information obtained from the control node (i.e., diff comparison). During this process, after the control node receives the comparison results reported by each working node, it can automatically process them through the scheduled task script. If the configuration information is inconsistent, an alarm is triggered or a log file is generated to record the working nodes whose actual configuration information is inconsistent with the target configuration information.

[0134] 4) Notification and alarm: Once the control node finds a working node whose actual configuration information is inconsistent with the target configuration information, it can use a variety of methods to notify and alarm. For example, the aforementioned methods may include but are not limited to sending email notifications or pushing to monitoring systems (such as Prometheus, Zabbix), etc. In addition, users or application developers can also further locate problems based on log files and manually or automatically trigger repair mechanisms.

[0135] In an optional implementation, the control node may also determine the instance deployment termination mode set for the target service in response to an abnormal event occurring during the instance deployment process for the target service, thereby stopping the instance deployment for the target service based on the aforementioned instance deployment termination mode. Figure 6 As shown, the aforementioned abnormal events may be special time events (such as holidays, etc.) or events in which some target services fail. The aforementioned instance deployment termination method may be a lock restriction, which may specifically include two lock types: soft lock and hard lock. If it is a soft lock, a prompt may be given to the user, and the user may continue to make changes. For example, you may still not choose to stop the instance deployment for the target service. If it is a hard lock, no changes will be made, that is, the instance deployment for the target service will be stopped.

[0136] Optionally, if the target service corresponds to multiple instance deployment termination methods, the instance deployment termination method with the highest level can be used as the final instance deployment method of the target service. For example, if the target service supports the existence of multiple locks at the same time, then the final lock state of the target service can be the lock state with the highest lock level.

[0137] Based on the above method, abnormal events occurring during instance deployment can be automatically detected, and instance deployment for the target service can be stopped in time to improve the stability of the service deployment system.

[0138] In summary, in the service deployment method provided in the embodiment of the present application, after determining at least one node cluster of the instance corresponding to the target service to be deployed, the instance can be deployed on multiple working nodes included in the at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance is completed on multiple working nodes, the target configuration information is sent to the multiple working nodes respectively, thereby receiving the configuration information comparison results reported by the multiple working nodes respectively; wherein each configuration information comparison result can characterize whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information. In this way, the received multiple configuration information comparison results can be used to effectively monitor whether the instance corresponding to the target service is deployed on multiple working nodes, thereby ensuring the stability of the service deployment.

[0139] In addition, the issuance of instance deployment rollback tasks is managed in a refined manner. Each instance deployment rollback task will be sent to the corresponding working node to ensure that the instance deployment rollback operation is executed in a refined manner according to the set concurrency; and the preset instance deployment termination method (such as a combination of soft and hard locks) is used to flexibly control whether the instance deployment continues.

[0140] Further, based on the same technical concept, the embodiment of the present application provides a service deployment device, which is used to implement the above method flow of the embodiment of the present application. Figure 7 As shown, the service deployment device 700 may include: a request response module 701, an instance deployment module 702 and a signal receiving module 703, wherein:

[0141] The request response module 701 is used to determine at least one node cluster for deploying an instance corresponding to the target service in response to a deployment request of the target service;

[0142] The instance deployment module 702 is used to deploy the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance is completed on the multiple working nodes, send the target configuration information to the multiple working nodes respectively;

[0143] The information receiving module 703 is used to receive configuration information comparison results reported by multiple working nodes respectively; wherein each configuration information comparison result represents whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information.

[0144] In an optional embodiment, when determining at least one node cluster for deploying an instance corresponding to a target service, the request response module 701 is specifically configured to:

[0145] Determine the number of worker nodes for the deployment instance based on the service requirements for the target service;

[0146] Based on the number of working nodes, at least one node cluster is selected from the preset multiple node clusters.

[0147] In an optional embodiment, when deploying an instance on multiple working nodes included in at least one node cluster based on target configuration information of the instance, the instance deployment module 702 is specifically used to:

[0148] A hierarchical release strategy for an instance is set for at least one node cluster; the hierarchical release strategy is used to indicate multiple deployment stages for deploying the instance in at least one node cluster;

[0149] Deploy instances on multiple working nodes based on the hierarchical release strategy and target configuration information.

[0150] In an optional embodiment, when deploying instances on multiple working nodes based on the hierarchical publishing strategy and target configuration information, the instance deployment module 702 is specifically used to:

[0151] For the multiple deployment stages included in the staged release strategy, perform the following operations respectively:

[0152] Deploy the instance on at least one node corresponding to a deployment phase based on the target configuration information;

[0153] When it is determined that at least one node has completed the deployment of the instance, an instance operation result corresponding to the at least one node is obtained; wherein each instance operation result represents whether the instance deployed on the corresponding node can provide the target service;

[0154] If at least one instance running result is a target instance running result indicating that the instance deployed on the corresponding node can provide the target service, then the instance deployment of the next deployment phase begins.

[0155] In an optional embodiment, after deploying the instance on multiple working nodes included in at least one node cluster based on the target configuration information of the instance, the instance deployment module 702 is further used to:

[0156] Perform instance deployment detection on multiple working nodes to obtain corresponding instance deployment detection results;

[0157] If the instance deployment detection result indicates that the instance deployment on the multiple working nodes does not meet the preset instance deployment requirements, an instance deployment rollback operation is performed on the multiple working nodes.

[0158] In an optional embodiment, when performing an instance deployment rollback operation on multiple working nodes, the instance deployment module 702 is specifically used to:

[0159] Determine first concurrencies corresponding to multiple deployment phases when deploying instances on multiple working nodes, and perform instance deployment rollback operations on multiple working nodes based on the multiple first concurrencies and their corresponding rollback phases;

[0160] Based on a preset accelerated rollback rule, determine the second concurrency of the rollback phase corresponding to the multiple deployment phases respectively, and perform instance deployment rollback operations on the multiple working nodes based on the multiple second concurrencies; or,

[0161] Based on the current maximum concurrency, perform instance deployment rollback operations on multiple working nodes.

[0162] In an optional embodiment, the instance deployment module 702 is further configured to:

[0163] In response to an abnormal event occurring during instance deployment for a target service, determining an instance deployment termination mode set for the target service;

[0164] Stop instance deployment for the target service based on instance deployment termination mode.

[0165] Based on the description of the above method embodiment and device embodiment, the exemplary embodiment of the present invention further provides an electronic device, including: at least one processor; and a memory connected to the at least one processor in communication. The memory stores a computer program that can be executed by the at least one processor, and the computer program is used to enable the electronic device to perform the method according to the embodiment of the present invention when executed by the at least one processor.

[0166] An embodiment of the present application also provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute a method according to an embodiment of the present application.

[0167] An embodiment of the present application also provides a computer program product, including a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute a method according to an embodiment of the present application.

[0168] See also Figure 8 As shown, the structured block diagram of the electronic device 800 that can be used as the server or client of the present application will now be described, which is an example of the hardware device that can be applied to various aspects of the present application. The electronic device is intended to represent the computer device of various forms of digital electronics, such as, laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only used as examples, and are not intended to limit the implementation of the present application described herein and / or required.

[0169] like Figure 8As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 to a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0170] A plurality of components in the electronic device 800 are connected to the I / O interface 805, including: an input unit 806, an output unit 807, a storage unit 808, and a communication unit 809. The input unit 806 may be any type of device capable of inputting information to the electronic device 800, and the input unit 806 may receive input digital or character information, and generate key signal inputs related to user settings and / or function control of the electronic device. The output unit 807 may be any type of device capable of presenting information, and may include but is not limited to a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 808 may include but is not limited to a disk, an optical disk. The communication unit 809 allows the electronic device 800 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks, and may include but is not limited to a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, such as a Bluetooth device, a WiFi device, a worldwide interoperability for microwave access (WiMax) device, a cellular communication device, and / or the like.

[0171] The computing unit 801 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSP), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 801 performs the various methods and processes described above. For example, in some embodiments, the above-mentioned service deployment method may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 800 via the ROM 802 and / or the communication unit 809. In some embodiments, the computing unit 801 may be configured to perform the above-mentioned service deployment method by any other appropriate means (e.g., by means of firmware).

[0172] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0173] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a RAM, a ROM, an erasable programmable read-only memory (EPROM) or a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0174] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0175] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a cathode ray tub (CRT) or a liquid crystal display (LCD) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0176] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0177] A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

[0178] Furthermore, it should be understood that what is disclosed above is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope covered by the present application.

Claims

1. A service deployment method, characterized in that: include: In response to a deployment request of a target service, determining at least one node cluster for deploying an instance corresponding to the target service; Based on the target configuration information of the instance, deploy the instance on multiple working nodes included in the at least one node cluster, and when it is determined that the deployment of the instance on the multiple working nodes is completed, send the target configuration information to the multiple working nodes respectively; Receive configuration information comparison results reported by the multiple working nodes respectively; wherein each configuration information comparison result represents whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information.

2. The method according to claim 1, characterized in that The determining of at least one node cluster for deploying an instance corresponding to the target service includes: Determine the number of working nodes for deploying the instance based on the service demand for the target service; Based on the number of working nodes, the at least one node cluster is selected from a plurality of preset node clusters.

3. The method according to claim 1, characterized in that The deploying the instance on a plurality of working nodes included in the at least one node cluster based on the target configuration information of the instance includes: Setting a hierarchical release strategy for the instance for the at least one node cluster; the hierarchical release strategy is used to indicate multiple deployment stages for deploying the instance in the at least one node cluster; Based on the hierarchical publishing strategy and the target configuration information, the instance is deployed on the multiple working nodes.

4. The method according to claim 3, characterized in that The deploying the instance on the multiple working nodes based on the hierarchical publishing strategy and the target configuration information includes: For the multiple deployment stages included in the hierarchical release strategy, perform the following operations respectively: Deploy the instance on at least one node corresponding to a deployment phase based on the target configuration information; When determining that the at least one node completes the deployment of the instance, obtaining the instance running results corresponding to the at least one node respectively; wherein each instance running result represents: whether the instance deployed on the corresponding node can provide the target service; If at least one instance running result is a target instance running result indicating that the instance deployed on the corresponding node can provide the target service, then instance deployment in the next deployment phase is started.

5. The method according to any one of claims 1 to 4, characterized in that After deploying the instance on a plurality of working nodes included in the at least one node cluster based on the target configuration information of the instance, the method further includes: Performing instance deployment detection of the instance on the multiple working nodes to obtain corresponding instance deployment detection results; If the instance deployment detection result indicates that the instance deployment on the multiple working nodes does not meet the preset instance deployment requirement, an instance deployment rollback operation of the instance is performed on the multiple working nodes.

6. The method according to claim 5, characterized in that The performing the instance deployment rollback operation of the instance on the multiple working nodes includes: Determine first concurrencies corresponding to multiple deployment phases when deploying the instance on the multiple working nodes, and perform instance deployment rollback operations on the multiple working nodes based on the multiple first concurrencies and their corresponding rollback phases; Based on a preset accelerated rollback rule, determine the second concurrency of the rollback phase corresponding to the multiple deployment phases respectively, and perform the instance deployment rollback operation of the instance on the multiple working nodes based on the multiple second concurrencies; or, Based on the current maximum concurrency, an instance deployment rollback operation of the instance is performed on the multiple working nodes.

7. The method according to any one of claims 1 to 4, characterized in that The method further comprises: In response to an abnormal event occurring during instance deployment for the target service, determining an instance deployment termination mode set for the target service; The instance deployment for the target service is stopped based on the instance deployment termination mode.

8. A service deployment device, characterized in that: include: A request response module, configured to determine, in response to a deployment request of a target service, at least one node cluster for deploying an instance corresponding to the target service; An instance deployment module, configured to deploy the instance on multiple working nodes included in the at least one node cluster based on the target configuration information of the instance, and when it is determined that the deployment of the instance is completed on the multiple working nodes, send the target configuration information to the multiple working nodes respectively; The information receiving module is used to receive the configuration information comparison results reported by the multiple working nodes respectively; wherein each configuration information comparison result represents whether the actual configuration information of the instance deployed on the corresponding working node is the same as the target configuration information.

9. An electronic device, comprising: processor; as well as Memory for storing programs, The program includes instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 7.

Images