Plug-in service deployment method and device, electronic equipment and storage medium

By introducing deployment nodes into the cluster system and receiving client requests through their interfaces, the security problem of illegal client attacks during plug-in service deployment is solved, and the security isolation and improvement of containers and worker nodes is achieved.

CN118945217APending Publication Date: 2024-11-12ZHUHAI KINGSOFT OFFICE SOFTWARE +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310535814.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-11
Publication Date
2024-11-12

Smart Images

  • Figure CN118945217A_ABST
    Figure CN118945217A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a plug-in service deployment method and device, electronic equipment and a storage medium. The plug-in service deployment method comprises the following steps: receiving a deployment request sent by a client based on a service port; wherein the deployment request comprises deployment information of a first plug-in service; generating task information according to the deployment information; wherein after the task information is monitored by the working nodes, the task information is used for at least one target node in the working nodes to deploy the first plug-in service. Therefore, the deployment request is received through the service port of the deployment node, the task information is set to be monitored by the working node, and the deployment request is received by a container port or a port of a physical machine in the non-open working node; the security problem caused by the fact that a working node needs to receive a client deployment request to open a container port or a port of a physical machine is reduced, and the security in the plug-in service deployment process is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of information technology, and in particular to a plug-in service deployment method and device, an electronic device, and a storage medium. Background Art

[0002] Plug-in services are also referred to as plug-in services, and there is no need to stop the operation of basic services and / or deployed plug-in services when deploying plug-in services.

[0003] A service cluster may include multiple nodes deployed in a distributed manner.

[0004] In a service cluster, a service can be grouped into multiple small services, which can also be called microservices. These microservices are a type of plug-in service. These microservices coordinate and cooperate with each other, so as to use different nodes of the service cluster to provide the microservices required by users. Each microservice can run independently in an independent process on different or the same node. Microservices can communicate quickly using lightweight communication mechanisms. Plugin service deployment can be quickly achieved by deploying containers on nodes.

[0005] In the plug-in service deployment process of the related technology, the working nodes or container interfaces in the service cluster need to be exposed to the deployed clients, which allows illegal clients to directly attack the containers or working nodes through the deployment process of the plug-in service, thereby causing security issues for the containers and / or working nodes. Summary of the invention

[0006] The present invention provides a plug-in service deployment method, apparatus, device and storage medium.

[0007] A first aspect of an embodiment of the present disclosure provides a plug-in service deployment method, which is executed by a deployment node and includes:

[0008] Receiving a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service;

[0009] Generate task information based on the deployment information; wherein, the task information is used to deploy the first plug-in service on at least one target node in the working node. After the task information is monitored by the working node, it is used to deploy the first plug-in service on at least one target node in the working node.

[0010] A second aspect of an embodiment of the present disclosure provides a plug-in service deployment method, which is executed by a working node and includes:

[0011] Monitoring task information sent by a deployment node; wherein the task information is generated based on a deployment request received by a service port; the deployment request is used to request deployment of a first plug-in service;

[0012] A first plug-in service is deployed according to the task information.

[0013] According to a third aspect of an embodiment of the present disclosure, a plug-in service deployment device is provided, the device comprising:

[0014] A first receiving module, configured to receive a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service;

[0015] A generation module is used to generate task information based on the deployment information; wherein, the task information is used to deploy the first plug-in service on at least one target node in the working node. After the task information is monitored by the working node, it is used to deploy the first plug-in service on at least one target node in the working node.

[0016] A fourth aspect of an embodiment of the present disclosure provides a plug-in service deployment device, the device comprising:

[0017] A second receiving module is used to monitor the task information sent by the deployment node; wherein the task information is generated based on the deployment request received by the service port; the deployment request is used to request the deployment of the first plug-in service;

[0018] A deployment module is used to deploy the first plug-in service according to the task information.

[0019] A fifth aspect of the embodiments of the present disclosure provides a service cluster, including:

[0020] A deployment node, configured to receive a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service; and generate task information according to the deployment information; wherein after the task information is monitored by a working node, it is used to deploy the first plug-in service to at least one target node in the working node;

[0021] A working node is used to monitor task information of a deployment node; wherein the task information is generated based on a deployment request received by a service port; a deployment request is used to request deployment of a first plug-in service; and the first plug-in service is deployed according to the task information.

[0022] A sixth aspect of the present disclosure provides an electronic device, including:

[0023] processor;

[0024] a memory for storing processor-executable instructions;

[0025] The processor is configured to implement the plug-in service deployment method provided by any one of the technical solutions of the first aspect, the second aspect or the fifth aspect when running the executable instructions.

[0026] A seventh aspect of an embodiment of the present disclosure provides a computer-readable storage medium, wherein the readable storage medium stores an executable program, wherein when the executable program is executed by a processor, the plug-in service deployment method provided by any one of the solutions of the first aspect, the second aspect, or the fifth aspect is implemented.

[0027] The technical solution provided by the embodiments of the present disclosure adds a deployment node in the cluster system, and receives the deployment request sent by the client through the service interface of the deployment node, rather than receiving the deployment request through the container port of the working node, thereby reducing the illegal client directly attacking the working node through the container port when receiving the deployment request, and improving the security of the container and the working node.

[0028] At the same time, in the embodiment of the present disclosure, the deployment node receives a deployment request from the client, and then sends task information to the target node of the first plug-in service to be deployed according to the deployment request. On the one hand, the plug-in service deployment is realized, and on the other hand, the isolation of the working node and the client for deploying the plug-in is realized, thereby improving the security of the working node for deploying the plug-in service.

[0029] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0031] Figure 1 The present invention is a flowchart of a plug-in service deployment method according to an exemplary embodiment.

[0032] Figure 2 The diagram is a schematic diagram of nodes involved in a plug-in service deployment method according to an exemplary embodiment.

[0033] Figure 3 The present invention is a flowchart of a plug-in service deployment method according to an exemplary embodiment.

[0034] Figure 4 The present invention is a flowchart of a plug-in service deployment method according to an exemplary embodiment.

[0035] Figure 5 The present invention is a flowchart of a plug-in service deployment method according to an exemplary embodiment.

[0036] Figure 6 The present invention is a flowchart of a plug-in service deployment method according to an exemplary embodiment.

[0037] Figure 7 The present invention is a flowchart of a plug-in service deployment method according to an exemplary embodiment.

[0038] Figure 8 The diagram is a schematic diagram of a plug-in service deployment method according to an exemplary embodiment.

[0039] Fig. 9 The diagram is a schematic diagram showing a method of creating a transmission according to an exemplary embodiment.

[0040] Fig.10 The figure is a schematic diagram of a configuration file according to an exemplary embodiment.

[0041] Fig.11 It is a schematic diagram showing a routing rule according to an exemplary embodiment.

[0042] Fig.12 is a structural diagram of a plug-in service deployment device according to an exemplary embodiment;

[0043] Fig.13 is a structural diagram of a plug-in service deployment device according to an exemplary embodiment;

[0044] Fig.14 The diagram is a schematic structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

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

[0046] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0047] like Figure 1 As shown, the embodiment of the present disclosure provides a plug-in service deployment method, which is executed by a deployment node and includes:

[0048] S1110: receiving a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service;

[0049] S1120: Generate task information according to the deployment information; wherein, after the task information is monitored by the working node, it is used to deploy the first plug-in service in at least one target node in the working node.

[0050] Both the deployment node and the working node can be servers providing services.

[0051] The client can correspond to any terminal device, which can be a fixed terminal or a mobile terminal.

[0052] The client may be a web client or an application client running in a terminal device.

[0053] In an embodiment of the present disclosure, a deployment node has a deployment module. The deployment module of the deployment node may be referred to as a first deployment module. The first deployment module may open a service port to the client, so that the first deployment module may receive a deployment request sent by the client based on the service port. Exemplarily, the first deployment module may be a deployment container running on the deployment node. The deployment node may also include a first execution module (also referred to as the execution module), which may be a part of the resources set on the deployment node other than the first deployment module. For example, the deployment node corresponds to a physical host, which divides the resources into two parts, one part constituting the first deployment module, and the other part constituting the first execution module. For another example, the deployment node corresponds to a virtual host, which divides the resources into two parts, one part constituting the first deployment module, and the other part constituting the first execution module.

[0054] Exemplarily, the deployment node configures one or more service ports of the physical machine running the first deployment module to the first deployment module. At this time, the first deployment module can receive deployment requests from the same or different clients through the one or more service ports.

[0055] The service ports here include but are not limited to:

[0056] Port based on file transfer protocol;

[0057] Port based on telnet;

[0058] Ports based on different service modes. Exemplarily, the service mode may include a port based on the Transmission Control Protocol (TCP) and / or a port based on the User Datagram Protocol (UDP).

[0059] In other embodiments, the deployment node may not configure a dedicated service port for the first deployment module. In other embodiments, the deployment node may also configure all service ports for the first deployment module to use, but the first deployment module may not have a dedicated service port, that is, the first deployment module and other functional modules in the deployment node share the service port of the deployment node.

[0060] Exemplarily, the deployment node is different from the working node. A deployment module for deploying plug-ins is provided in the deployment node. The working node can be used to provide various service nodes.

[0061] In some embodiments, the deployment nodes and the worker nodes may be located in a service cluster.

[0062] In other embodiments, the deployment node and the working node may also be located in different service clusters.

[0063] In some other embodiments, the deployment node may be located in the service cluster, and the working node may be located in the service cluster or outside the service cluster.

[0064] In summary, there are connection ports between the deployment nodes and the worker nodes.

[0065] refer to Figure 2 The service cluster shown includes a deployment node (node1) and a working node (node2). In some embodiments, a service cluster may include more than one working node. Figure 2 The working nodes also include working nodes (node3) outside the service cluster. Deployment modules are set on both the deployment nodes and the working nodes. Figure 2 The "docker" shown in the figure is a container. The container can be used to run codes such as plug-ins, thereby providing plug-in services and / or basic services.

[0066] In some embodiments, the deployment node includes a first execution module in addition to the first deployment module. The first execution module may be one of the aforementioned functional modules. The first execution module and the first deployment module may be functional modules that occupy different resources in the deployment node. The first execution module may also deploy containers required for the service. That is, the container deployed by the deployment node may also provide services. The service may include a plug-in service and a basic service.

[0067] In some embodiments, the deployment node is a node that can be used to deploy services. In other embodiments, the deployment node can also be a composite node that takes into account both deployment functions and execution functions. If the deployment node is a composite node, a security filtering module is deployed between the first deployment module and the first execution module in the deployment node to isolate the first deployment module from the first execution module. Alternatively, the first deployment module and the first execution module are set in different domains that are not nodes, thereby achieving security isolation through domains.

[0068] In the disclosed embodiment, the service port of the deployment node can remotely receive a deployment request sent by a client through a network. The deployment request can request the deployment information of any plug-in service. In the disclosed embodiment, in order to distinguish different plug-in services, the plug-in service to be deployed is referred to as the "first plug-in service". The "first" here is only used to distinguish different plug-in services, not to sort them.

[0069] The deployment information may include but is not limited to at least one of the following:

[0070] Plug-in information of the first plug-in service to be deployed;

[0071] Node information of the first plug-in service to be deployed;

[0072] Environment variables for the first plugin service to be deployed.

[0073] Exemplarily, the plug-in information may include at least one of the following:

[0074] A plug-in identifier of the first plug-in service;

[0075] The version number of the first plugin service;

[0076] The code of the first plugin service.

[0077] The plug-in information of the first plug-in service to be deployed may include, but is not limited to, identification information of the first plug-in service and / or description of the plug-in service. Exemplarily, the plug-in information may include, but is not limited to, container information of a target container providing the first plug-in service. The container information may include a container name and / or a container image, etc.

[0078] The node information of the first plug-in service to be deployed indicates the target node of the first plug-in service to be deployed. The target node may include one or more working nodes.

[0079] The node information may include at least one of the following:

[0080] Node ID;

[0081] Node address;

[0082] Node attributes.

[0083] In some embodiments, the deployment node may provide the client with a node identifier of a candidate node capable of deploying the plug-in service. The candidate node may be any one or more of the aforementioned working nodes.

[0084] The client selects a target node from candidate nodes based on user input or default selection rules, and carries the node identifier of the target node in the deployment request.

[0085] The node address may include, but is not limited to: the node's Internet Protocol (IP) address, the node's Media Access Control (MAC) address, etc., which can uniquely identify the node.

[0086] Exemplarily, the client displays the node addresses of the candidate nodes in advance or based on information provided by the deployment node, selects the target node from the candidate nodes based on user input or default selection rules acting on the client, and carries the node address of the target node in the deployment request.

[0087] In some cases, the deployment request may also carry node attributes. The node attributes may be any information describing the node, such as the node type and / or the resource type of the node.

[0088] In this case, when the deployment node receives a deployment request, it can select an alternative node with corresponding node attributes as the target node based on the node attributes carried in the deployment request. In this way, the deployment node can select a suitable target node for deploying the first plug-in service based on the node's load rate and / or the node's idle resource rate, etc.

[0089] In summary, in some cases, the deployment request can carry any one of the node identifier, node address and node attributes alone. In other cases, the deployment request can also carry node attributes while carrying the node identifier and / or node address. Here, the node attributes can be used to describe the resource type and / or resource quantity that the target node for deploying the first container needs to provide. If the node identifier of a node is carried in the deployment request, but the node resources for deploying the first plug-in service at this node are not idle, at this time, the deployment node can choose to select an alternative node from other alternative nodes that have the resources required to deploy the first plug-in service for smooth and successful deployment.

[0090] In the embodiment of the present disclosure, the deployment node will generate task information according to the deployment request. After generating the task information, the task information will be published to the message channel monitored by the working node. In this way, after the task information is published, the working node can obtain the latest task information in time, so as to determine whether it needs to execute the task pointed to by the task information.

[0091] In some embodiments, the method further comprises:

[0092] Configure the communication mechanism between the working node and the deployment node; the communication mechanism can be used for communication interaction between the working node and the deployment node. The communication mechanism includes but is not limited to the monitoring mechanism involving the aforementioned message channel. Exemplarily, the aforementioned message channel is configured when configuring the communication mechanism between the working node and the deployment node.

[0093] Exemplarily, configuring a communication mechanism between a working node and a deployment node may include:

[0094] Configure the communication address and / or interface associated with the message channel.

[0095] Exemplarily, a first interface for publishing task information to a message channel is deployed for a deployment node, and / or a listening configuration for listening to task information is configured for a working node, and the listening configuration may include at least a second interface.

[0096] In this way, after the task information is published to the message channel, the working node can access the task information through monitoring.

[0097] In some embodiments, task information may be published to a message channel separately, or may be stored in a configuration file and published to a message channel.

[0098] In the embodiment of the present disclosure, a deployment node is added to the cluster system, and the deployment request sent by the client is received through the service interface of the deployment node, rather than through the container port or the port of the physical machine, thereby reducing the security issues caused by directly opening the working node container port to the client during the process of receiving the deployment request. For example, at least during the plug-in service deployment process, the illegal client can directly attack the container and / or working node through the container port, thereby improving the security of the container and / or working node.

[0099] For example, the container port may be an application program interface (API) port configured for the container. If the client directly sends a deployment request through the container port, it is equivalent to directly exposing the container in the cluster system to the client, which may make it easier for illegal clients to attack the container.

[0100] At the same time, in the embodiment of the present disclosure, the deployment node receives a deployment request from the client, and then generates task information according to the deployment request for the target node to be deployed with the first plug-in service to listen to. On the one hand, the plug-in service deployment is realized, and on the other hand, in the plug-in deployment, the client does not need to communicate directly with the working node or the container in the working node, that is, the isolation of the working node where the plug-in is deployed and the client is realized, thereby improving the security of the working node where the plug-in is deployed.

[0101] In some embodiments, the deployment information includes:

[0102] Configuration information, including at least: node information of the target node;

[0103] The environment variables include at least: a running environment state quantity of the first plug-in service.

[0104] Exemplarily, the node information may refer to any of the aforementioned embodiments.

[0105] The configuration information may also include other information required for the target node to deploy the plug-in service.

[0106] Specifically, the configuration information includes at least one of the following:

[0107] The network protocol IP address of the working node where the first plug-in service is to be deployed;

[0108] The node number of the working node where the first plug-in service is to be deployed;

[0109] The node name of the working node where the first plug-in service is to be deployed;

[0110] Node attribute information of the working node on which the first plug-in service is to be deployed.

[0111] In some embodiments, the environment variable includes at least one of the following:

[0112] Providing image information of a target container of the first plug-in service;

[0113] Database information;

[0114] Store information;

[0115] Log information.

[0116] Providing the target container of the first plug-in service may include: providing container image information of the container required by the plug-in service, etc.

[0117] The database information may include but is not limited to the identification and / or attributes of the database required by the plug-in service. The attributes include but are not limited to database management rules such as database type, data capacity and / or consistency principle followed by the database.

[0118] The storage information may include a global variable that may be involved in running the first plug-in service.

[0119] The log information indicates the log type, log level, log storage, and update rules.

[0120] In some embodiments, task information is generated according to the deployment information, including:

[0121] According to the deployment information,

[0122] Generate or update a configuration file containing the task information; wherein, after the updated configuration file is monitored by the target node, it is used to deploy the first plug-in service.

[0123] In some embodiments, the deployment node can directly generate a configuration file based on the deployment information, and the task information is used as the file content of the configuration file. Alternatively, the deployment node generates the task information based on the deployment information and writes the task information into the generated configuration file.

[0124] After the configuration file is generated or updated, it is published to the message channel for the working nodes to listen to.

[0125] Exemplarily, task information is stored in a configuration file; the working node is configured with relevant information for monitoring a message channel, for example, the working node is configured with an address and / or port for accessing the configuration file, through which the configuration file can be monitored; when it is determined that the content of the configuration file has changed, the latest version of the configuration file is read from the message channel, thereby enabling the deployment node to obtain the task information sent according to the deployment request.

[0126] Exemplarily, a configuration module is configured on the deployment node. The configuration module may be an etcd module, which executes the etcd mechanism. The etcd module maintains various etcd files. The etcd file may include a configuration file for plugin service deployment.

[0127] refer to Figure 2As shown, the deployment information generates task information, and the task information is written to the etcd module, which is used to generate or update the configuration file for storing task information. The task information includes at least a task identifier (ID) relative to the deployment information submitted by the client. The task information may also include deployment information, etc., which comes from the deployment request. After the configuration file is updated, the etcd module broadcasts an update message. The update message will be listened to by the deployment module of the working node, and the subsequent working node will obtain the task information from the etcd module of the deployment node, or, based on the message push of the etcd module in the deployment node, the working node obtains the task information. Exemplarily, the working node obtains the task information from the configuration file in the etcd module of the deployment node.

[0128] like Figure 3 As shown, the embodiment of the present disclosure provides a plug-in service deployment method, which is executed by a deployment node and includes:

[0129] S1210: receiving a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of the first plug-in service;

[0130] S1220: Generate task information according to the deployment information; wherein, after the task information is monitored by the working node, it is used to deploy the first plug-in service in at least one target node in the working node.

[0131] S1230: Acquire deployment status information of the target node;

[0132] S1240: Send a deployment response to the client according to the deployment status information.

[0133] Obtaining the deployment status information of the target node may include: monitoring the deployment status information released by the working node through the etcd module; wherein the deployment status information includes: deployment status variables; and the deployment status variables indicate the deployment result.

[0134] Exemplarily, the target node may be part or all of the working nodes. Therefore, the target node and the deployment node may also communicate through a monitoring mechanism. Exemplarily, the working node will publish the deployment status information to the message channel. When the deployment node monitors the message channel, once a new message is heard, it will read the latest message from the message channel to obtain the deployment status information. Of course, here the deployment node can easily obtain the deployment status information through the monitoring mechanism.

[0135] Exemplarily, the deployment status information is stored in the status "status" in the configuration file. After the deployment node publishes the configuration file, it will monitor the status file in the message channel through the first interface to obtain the deployment status information in a timely manner.

[0136] In some embodiments, the deployment status information is not limited to being obtained through a monitoring mechanism, and the deployment node may also directly request the deployment status information from the target node, or obtain the deployment status information based on a push from the target node.

[0137] The deployment status variable information may record the deployment result and / or deployment progress of the plug-in service on the corresponding working node.

[0138] Exemplarily, the deployment status variable information (Status) may indicate at least one of the following:

[0139] Start the deployment;

[0140] Deployment progress, for example, the deployment of the first plug-in service may be divided into several deployment steps; the deployment progress may be completed steps and / or deployment steps to be completed;

[0141] Deployment is ongoing;

[0142] Deployment is complete;

[0143] Deployment was successful;

[0144] Deployment failure, etc.

[0145] The deployment status variable information may also be referred to as installation status variable information, which may indicate whether the corresponding working node has completed the plug-in installation and / or the installation result.

[0146] By receiving the deployment status information, the deployment progress and / or monitoring result of the first plug-in service can be known, so as to better implement the deployment of the first plug-in service.

[0147] In some embodiments, S1240 may include at least one of the following:

[0148] When the deployment status information of the target nodes to be deployed with the first plug-in service all indicate that the deployment is successful, sending a deployment response indicating that the deployment is successful to the client;

[0149] When the deployment status information of at least one target node of the plurality of first plug-in services to be deployed indicates a deployment failure, sending a deployment failure indicating a deployment success to the client;

[0150] When the deployment status information of at least one target node of the plurality of to-be-deployed first plug-in services indicates that deployment is in progress, sending a deployment response to the client is temporarily suspended, or a deployment response indicating that deployment is in progress is sent to the client.

[0151] In some embodiments, the method further comprises:

[0152] In the case of receiving the deployment status information sent by the target node indicating that the deployment has failed, detecting the task information;

[0153] In the case where the task information is incorrect, the corrected task information is resent, and the corrected task information is used for the target node where the historical deployment failed to redeploy the first plug-in service.

[0154] In other embodiments, the deployment failure may not be caused by incorrect task information, but by system fluctuations. In this case, the deployment node can send a redeployment instruction.

[0155] In some embodiments, the method further comprises:

[0156] When receiving the deployment status information sent by the target node indicating that the deployment has failed, directly enter the redeployment step; when redeploying, the deployment environment and / or routing information and other legacy files and / or information generated by the failed deployment will be cleaned up to reduce the next deployment failure caused by the legacy files and / or information of the failed deployment, thereby improving the success rate of the next deployment;

[0157] When the number of deployment failures received from the target node reaches a threshold, a deployment response indicating deployment failure is sent to the client.

[0158] Of course, the above is only an example of the deployment node monitoring the deployment status of the first plug-in service of the working node and how to provide a deployment response to the client, but the specific implementation is not limited to the above example.

[0159] like Figure 4 As shown, the embodiment of the present disclosure provides a plug-in service deployment method, which is executed by a working node and includes:

[0160] S2110: monitoring the task information of the deployment node; wherein the task information is generated based on the deployment request received by the service port; the deployment request is used to request the deployment of the first plug-in service;

[0161] S2120: Deploy the first plug-in service according to the task information.

[0162] The working node may be a different node in the same cluster system as the deployment node, or may be a node outside the cluster system where the deployment node is located.

[0163] In short, a connection is established between the working node and the deployment node, and the working node will monitor the task information through the connection. Exemplarily, the task information can be included in a configuration file, and the working node can monitor the configuration file to achieve the monitoring of the task information.

[0164] In some embodiments, the deployment information includes at least configuration information, including node information and environment variables; the node information indicates the target node to be deployed with the first plug-in service; the environment variables include at least the running environment state of the first plug-in service.

[0165] A working node may be composed of one or more physical machines, one or more virtual machines, or a mixture of one or more physical machines and one or more virtual machines.

[0166] In the disclosed embodiment, the working node may monitor the task information sent by the deployment node in various ways, for example, monitoring the task information broadcasted by the deployment node. The working node may monitor the configuration file exposed to the working node by the deployment node, and the configuration file stores the task information. The task information may indicate the deployment task of any first plug-in service. If the deployment task of the plug-in service to be executed by the working node is monitored, the first plug-in service will be deployed on the node according to the task information.

[0167] Thus, in the disclosed embodiment, the container port of the working node is exposed to the deployment node rather than directly to the client, thereby improving the deployment security of the plug-in service.

[0168] In the disclosed embodiment, the deployment node receives the deployment information to generate task information, and generates or updates the configuration file according to the task information; after the configuration file is distributed to the working node, the working node deploys the first plug-in service. The distribution method may be to send the configuration file to the working node, or to expose the channel for accessing the configuration file to the working node, and the working node accesses the configuration file through the channel. Fig.10 Shown is a schematic diagram of a configuration file.

[0169] In some embodiments, deploying the plug-in according to the task information includes:

[0170] According to the task information, determine whether the working node is the target node;

[0171] When the working node is the target node, the input parameter information is generated according to the task information;

[0172] Deploy the first plug-in service based on the creation input information.

[0173] In the disclosed embodiment, the task information may carry any information indicating the target node. In this way, after receiving the task information, the working node will determine whether it is the target node for the first plug-in service to be deployed based on the task information. If the current working node is the target node for the first plug-in service to be deployed indicated by the deployment node, the deployment of the first plug-in service will be started based on the task information. If the current working node is not the target node for the first plug-in service to be deployed indicated by the deployment node, the received task information may be discarded or ignored.

[0174] If the current working node is the target node, creation input parameter information is generated according to the task information. The creation input parameter information can also be called deployment parameters, which can be any parameters for deploying the first plug-in service.

[0175] Exemplarily, the creation input parameter information may include: resource parameters for deploying the first plug-in service, environment parameters for deploying the first plug-in service, and / or deployment mode for deploying the first plug-in service. In summary, in the disclosed embodiment, the working node listens to the task information from the deployment node, and then generates the creation input parameter information for deploying the first plug-in service according to the task information, so as to achieve safe and easy deployment of the first plug-in service.

[0176] like Fig. 9 As shown, this is a kind of creation input parameter information.

[0177] In some embodiments, creating the input parameter information includes at least one of the following:

[0178] Image information, including image name and / or image tag;

[0179] Container information, describing the target container running the first plug-in service;

[0180] Explore live information;

[0181] Deployment status quantity;

[0182] Node ID;

[0183] Create information.

[0184] The image information includes an image name and / or an image tag, which facilitates the working node to read the content required for deploying the first plug-in service from the local database of the working node, the database of the deployment node, or the database of the cluster system when deploying the first plug-in service.

[0185] In some embodiments, the container information may include a container image for running the first plug-in service, etc. In this way, after the current working node obtains the task information, it can create a container on the current working node when deploying the first plug-in service by setting the container information. The container may be a container that provides the first plug-in service, which may be referred to as a target container in the disclosed embodiment.

[0186] In other embodiments, the container information may include a container identifier, a container version, a validity mark of a container resource, a container image identifier and / or a storage location of a container image, etc.

[0187] The detection information may include at least one of the following:

[0188] Activity detection mode information, indicating the activity detection mode; typical activity detection modes may include but are not limited to: an activity detection mode based on the Transmission Control Protocol (TCP) and an activity detection mode based on the Hyper Text Transfer Protocol (HTTP);

[0189] Probe cycle information, indicating the probe cycle;

[0190] Deployment status quantity, which can be used to record deployment status information and / or status code, etc.

[0191] Figure 2 As shown in the figure, keepalived has a liveness detection module deployed on both the deployment node and the working node; the liveness detection module can be used to detect the liveness of the corresponding plug-in service.

[0192] like Figure 5 As shown, the embodiment of the present disclosure provides a plug-in service deployment method, which is executed by a working node and includes:

[0193] S2210: monitoring the task information of the deployment node; wherein the task information is generated based on the deployment request received by the service port; the deployment request is used to request the deployment of the first plug-in service;

[0194] S2220: Deploy the first plug-in service according to the task information.

[0195] S2230: Generate routing rules for the first plug-in service.

[0196] The routing rule can be used to provide the first plug-in service based on a load balancing mechanism. Exemplarily, when a target container of the first plug-in service is deployed on multiple working nodes and / or multiple physical machines, when responding to a service request, the load balancing of the node where the service container is located is taken into consideration, and a service container is selected to provide the first plug-in service.

[0197] In some embodiments, after the first plug-in service is deployed, second domain name information is generated, and the second domain name information can be used for domain name resolution of the domain name carried in the service request. In view of this, the working node can generate a routing rule for the first plug-in service according to the second domain name information of the first plug-in service.

[0198] In the embodiment of the present disclosure, if the target container is deployed on multiple physical machines or multiple working nodes, a routing rule will be generated. In the embodiment of the present disclosure, the routing rule may include: the IP address of each physical machine where the target container is deployed, the IP address of the working node and / or the IP address of the target container. In order to reduce the load imbalance of multiple physical machines in the distributed cluster system, a routing rule that takes load balancing into consideration will be generated. In this way, by responding to service requests according to the routing rule, load balancing between different physical machines and / or working nodes can be achieved as much as possible.

[0199] Exemplarily, the routing rule may include but is not limited to a Linux Virtual Server (lvs) rule. Figure 2 The lvs rule in is the aforementioned routing rule. Fig.11 A schematic diagram of a routing rule.

[0200] In some embodiments, the working node includes a deployment module and an execution module. Figure 6 As shown, the method also includes:

[0201] S2310: Acquire first domain name resolution information maintained by the execution module; wherein the first domain name resolution information at least includes: domain name resolution information of a basic service;

[0202] S2320: The deployment module determines the second domain name resolution information of the first plug-in service according to the task information;

[0203] S2330: The deployment module receives the first domain name resolution information from the execution module, and merges the received first domain name resolution information with the second domain name resolution information to obtain third domain name resolution information;

[0204] The third domain name resolution information is used to respond to a service request, wherein the service request includes a domain name for the requested service.

[0205] The deployment module in the working node may also be referred to as a second deployment module. The "second" in the second deployment module is used to distinguish the "first deployment module" in the deployment node and has no special meaning.

[0206] The execution module in the working node may also be referred to as the second execution module. The "second" in the second execution module is used to distinguish the "first execution module" in the deployment node and has no special meaning.

[0207] In some embodiments, at least the deployment module and the execution module may be functional modules that occupy different resources in the working node. The computing resources and / or storage resources occupied by each other are different, and the processes used are also different, so they do not interfere with each other.

[0208] In an embodiment of the present disclosure, the second execution module may locally maintain first domain name resolution information of the deployed second plug-in. Exemplarily, the first domain name resolution information may be included in the first file.

[0209] At the same time, the second deployment module maintains second domain name resolution information, which may be domain name resolution information generated by the second deployment module when deploying the first plug-in service. The second domain name resolution information may be maintained in a second file maintained by the second deployment module.

[0210] After the second deployment module completes the update of the first domain name resolution information, that is, the received first domain name resolution information is merged with the second domain name resolution information to obtain the third domain name resolution information, all the domain name resolution information in the working node will be obtained, so that after the second execution module receives the service request, it will query the third domain name resolution information according to the service request, thereby obtaining the IP address providing the basic service and / or the plug-in service. That is, the third domain name resolution information may include the domain name resolution information of the basic service and the domain name resolution information of the plug-in service.

[0211] In some embodiments, routing rules are also stored in the deployment node. When responding to a service request, the IP address of the container that responds to the service request is determined based on the domain name resolution information and the routing rules.

[0212] Exemplarily, when the second execution module is dormant or closed, the first domain name resolution information and / or routing rules are stored in one or more first files. When the second execution module is activated or started, the information content in the first file is mounted to the second deployment module, so that the second deployment module can locally maintain the complete domain name resolution information.

[0213] In some embodiments, the method further comprises:

[0214] Generate deployment status information according to the deployment status of the first plug-in service;

[0215] sending the deployment status information,

[0216] The deployment status information includes: a deployment status variable; the deployment status variable indicates a deployment result.

[0217] Exemplarily, the deployment state variable information may record the deployment result and / or deployment progress of the plug-in service on the corresponding working node.

[0218] Exemplarily, the deployment status variable information (Status) may indicate at least one of the following:

[0219] Start the deployment;

[0220] Deployment is ongoing;

[0221] Deployment progress, for example, the deployment of the first plug-in service may be divided into several deployment steps; the deployment progress may be completed steps and / or deployment steps to be completed;

[0222] Deployment is complete;

[0223] Deployment was successful;

[0224] Deployment failure, etc.

[0225] The deployment status variable information may also be referred to as installation status variable information, which may indicate whether the corresponding working node has completed the plug-in installation and / or the installation result.

[0226] Exemplarily, the working node may send deployment status information to the deployment node, so that the deployment node will know the deployment progress of the first plug-in service. Exemplarily, the working node may periodically send deployment status information to the deployment node, or the working node may send deployment status information when the first plug-in service is deployed to any key deployment step that specifies reporting deployment status information. In some other embodiments, a reporting instruction of the deployment node is received during the deployment process, and deployment status variable information is sent to the deployment node according to the reporting instruction.

[0227] like Figure 7 As shown, the embodiment of the present disclosure provides a plug-in service deployment method, which can be executed by a client, and the method includes:

[0228] S3110: Detect deployment operation;

[0229] S3120: When a deployment operation is detected, sending a deployment request to the deployment node through the service port, wherein the deployment request includes deployment information of the first plug-in service;

[0230] The deployment information may be used by the deployment node to generate task information for deploying the first plug-in service by at least one working node.

[0231] In the disclosed embodiment, the client sends a deployment request to the deployment node of the cluster system through the service port, rather than directly sending the deployment request to the container port in the cluster system, thereby achieving isolation between the container and the client, thereby improving the security of the plug-in service deployment.

[0232] In some embodiments, the deployment information includes:

[0233] Configuration information, including at least: node information of the target node;

[0234] The environment variables include at least: a running environment state quantity of the first plug-in service.

[0235] The deployment information may include but is not limited to at least one of the following:

[0236] Plug-in information of the first plug-in service to be deployed;

[0237] Node information of the first plug-in service to be deployed;

[0238] Environment variables for the first plugin service to be deployed.

[0239] Exemplarily, the plug-in information may include at least one of the following:

[0240] A plug-in identifier of the first plug-in service;

[0241] The version number of the first plugin service;

[0242] The code of the first plugin service.

[0243] The node information of the first plug-in service to be deployed indicates the target node of the first plug-in service to be deployed. The target node may include one or more working nodes.

[0244] The node information may include at least one of the following:

[0245] Node ID;

[0246] Node address;

[0247] Node attributes.

[0248] In some embodiments, the deployment node may provide the client with a node identifier of a candidate node capable of deploying the plug-in. The candidate node may be any one or more of the aforementioned working nodes.

[0249] The client selects a target node from candidate nodes based on user input or default selection rules, and carries the node identifier of the target node in the deployment request.

[0250] The node address may include, but is not limited to: the node's Internet Protocol (IP) address, the node's Media Access Control (MAC) address, etc., which can uniquely identify the node.

[0251] In some embodiments, the method further comprises:

[0252] Receive node information of candidate nodes sent by the deployment node;

[0253] Display node information of candidate nodes;

[0254] Based on the selection operation acting on the node information, the node information carried in the deployment request is determined.

[0255] In this way, the client can independently select the node information for deploying the first plug-in service according to user instructions and other circumstances.

[0256] In some other embodiments, detecting the deployment operation may include:

[0257] Displays deployment operations that are applied on the Deployments page.

[0258] Before a deployment operation is detected, the client displays the deployment page.

[0259] The deployment page may also include one or more input controls, which may be used to input one or more types of information required to be carried in the deployment request.

[0260] The input control may include but is not limited to a text input box, or a file import box, etc.

[0261] The one or more information received via the input control may include configuration information and / or environment variables.

[0262] The disclosed embodiments provide a service cluster. The service cluster may be a microservice cluster. The service cluster may include one or more cloud platforms. One or more cloud platforms may include one or more nodes. The node may include at least one deployment node and at least one working node. In some cases, the service cluster is provided with multiple deployment nodes, which are independently provided, and can support different deployment nodes to respond to deployment requests from different clients in parallel. When the cloud platform and basic services are stable, plug-ins need to be deployed. However, when the cloud platform does not open the remote port of the container, it is necessary to support the deployment of specified nodes and send additional actions such as access routing to avoid affecting the basic services, which makes deployment more difficult.

[0263] Aiming at the problem that the cloud platform needs to support the deployment of designated nodes when the remote port of the container is not opened, and issue additional actions such as access routing to avoid affecting the basic services, a micro-plug-in deployment method is invented.

[0264] refer to Figure 2 As shown, the entire deployment task is initiated by a web page (Web), and the Web first performs pre-configuration filling. The pre-configuration includes deployment configuration and environment variables, where the deployment configuration is to select the node IP address to be installed. The web page can be run in the client.

[0265] Environment variables refer to the variables required for the operation of the plug-in service, such as image information, database information, storage information, log level, etc. When the Web selects the node to be deployed, it can obtain all the node information of the cluster by calling the interface of the deployment module and select the node to be deployed. Then upload the installation package of the plug-in service to the deployment module of the deployment node (the deployment node here is node1, which is not the node selected by the Web. The node selected by the Web is passed to the deployment module as a parameter). The deployment module is responsible for deploying the plug-in service (also called microservice or microplug-in) to the node specified by the Web; the Web queries the task progress. If it fails, subsequent processing is required to clean up the plug-in service and routing information that failed to be deployed in the environment. If the deployment is successful, it will display the deployment success. Reference Figure 2 As shown in the figure, the entire service cluster is divided into nodes in the cluster (node1, node2) and nodes outside the cluster (node3).

[0266] The disclosed embodiment adopts etcd's watch mechanism for message monitoring. Each basic service. Plugin services can be deployed on any node and need to be specified by the Web. For example, a certain plugin service requires a graphics processing unit (GPU). However, the GPU only exists on node3, so node3 can be selected for deployment. All deployment modules, keepalived, and etcd are containerized deployment modules on the deployment platform node, which are responsible for monitoring the message changes of etcd on the deployment node (node1).

[0267] When the Web sends a deployment request to the deployment module of the deployment node, the deployment module will write the deployment information into the configuration file of the etcd module. After the deployment modules on all nodes listen to the etcd message broadcast by the etcd module of the deployment node, they will perform subsequent deployment work according to the configuration file updated by the deployment node. The ports exposed by the etcd module are encrypted with a self-signed certificate to protect the open ports. The container API port is not directly exposed here to avoid the cloud platform environment being widely controlled by the open container remote port, thereby causing network security issues.

[0268] Web initiates a deployment request to the deployment node.

[0269] Web requests are all initiated to the deployment module of the deployment node (node1). After receiving the uploaded package, the deployment module will perform the image upload operation.

[0270] After the deployment module of the deployment node receives the deployment request, it writes the deployment request into the etcd file.

[0271] This etcd file is a stand-alone etcd file on the deployment node. The deployment node writes the deployment information to the etcd file as follows:

[0272] The creation input information is roughly as follows:

[0273]

[0274]

[0275] The logic of the deployment module is as follows: after receiving a deployment request, it is written to the etcd file, and success is returned, and then the installation status is asynchronously queried. The status here is roughly divided into four stages.

[0276] Wait Process

[0277] Initialization process (Init Process);

[0278] Initialization process (Init Process), and the container runs successfully (docker run Success);

[0279] The initialization process (Init Process), the container runs successfully (docker run Success), and the installation is completed (finished).

[0280] The deployment modules of all nodes discover new tasks / deployment modules / taskid / ip by watching etcd.

[0281] All deployment modules will watch the etcd change messages.

[0282] Container running (docker run).

[0283] After the deployment module listens (watches) to the message, the message contains the deployment node information; for example, node_ip is node1, node2.

[0284] When node1 listens to the message and determines that node1 belongs to node_ip (node1, nod2), it will render the container (docker) template to generate a container assembly file (for example, the container assembly file includes but is not limited to a docker-compose file) and create a docker service.

[0285] When node3 listens to the message, since node3 does not belong to node_ip (node1, nod2), node3 will automatically skip the generation process of the docker-compose file and will not create a container service.

[0286] The docker service is mainly created by docker-compose. When the message changes are monitored, the deployment operation begins. The key information contained in the message will render the container (such as docker) template (container template docker_template) file in the deployment module to generate a container assembly file, which can be used to generate a docker service.

[0287] All nodes will generate lvs routing rules. The key information contained in the message will render the keepalived configuration template (lvs_template) in the deployment module, generate the keepalived.conf file and mount it into the keepalived path. When the deployment module restarts keepalived, new routing rules will be generated. The routing rules can facilitate access to plug-ins.

[0288] The execution result is updated in the "status":"", [Installation status information] in the etcd file for progress query. If it fails, follow-up processing is required to clean up the microservices and routing information that failed to be deployed in the environment. If the deployment is successful, it will display deployment success.

[0289] In addition, it is important to note that when deploying, nodes must be specified;

[0290] The creation input contains node information (node_ip). During installation, the monitored messages will be used to determine whether the node needs plug-in services. If the node information in the input is empty, an error will be reported directly.

[0291] Considering that the deployment module of the working node (also called the execution node) is restarted and causes the deployment to fail halfway through the installation, the deployment status information will generate deployment status information indicating that the deployment failed.

[0292] Load balancing mainly generates LVS rules based on the existing keepalived configuration files. Based on the installation information, the deployment module will generate the keepalived configuration file, for example, Fig.10 shown.

[0293] The LVS rules produced on each node are as follows Fig.11 shown.

[0294] Further information on how to access plugins:

[0295] Physical hosts and containers access other services mainly through / etc / hosts for domain name resolution. In order to reduce the mutual influence between the hosts file of the physical host and the hosts file of the container host, the following can be done: Figure 8 shown.

[0296] / data / kube / deployment module / hosts is mounted to the host by / etc / hosts of the deployment module. / data / kube / deployment module / hosts contains the host's / etc / hosts and the domain name resolution of all plugins. The implementation method is: the host's / etc / hosts is mounted to the deployment module's / data / hosts. Each time the program is started, the / data / hosts file is updated to the deployment module's / etc / hosts. Each time a plugin is deployed, the domain name resolution is written to the deployment module's / etc / hosts. Therefore, / data / kube / deployment module / hosts contains the host's / etc / hosts and the domain name resolution of all plugins.

[0297] Mount / data / kube / deployment module / hosts into / etc / hosts in the container service that needs to access the plug-in. The container service that needs to access the plug-in resolves the container name through / etc / hosts to obtain the IP address (domain name resolution is written to / etc / hosts when deploying the plug-in). All plug-ins can be accessed through lvs. Thus, load balancing is achieved through domain name-ip-lvs-container.

[0298] Figure 8 The following figure shows the module division of the deployment node. Figure 8 The deployment module in the middle is the first deployment module of the deployment node. The host represents the first execution module of the deployment node.

[0299] exist Figure 8In the example, the deployment module maintains a file located in the directory / data / hosts, and the host representing the first execution module also maintains a file located in the directory / etc / hosts. The / data / hosts file can be used to store the first domain name resolution information of the basic service from the host. The files under the directory / etc / hosts of the first deployment module maintain the first domain name resolution information from the directory / data / hosts, and include the second domain name resolution information generated by the deployment plug-in service. That is, the files in the directory etc / hosts of the first deployment module maintain the third domain name resolution information. The directory / data / kube / deployment module / hosts of the first execution module can maintain the domain name resolution information of the second plug-in service and the basic service that have been deployed. For example, after the first deployment module merges the first domain name resolution information and the second domain name resolution information to obtain the third domain name resolution information, the third domain name resolution information can be backed up and stored in the directory / data / kube / deployment module / hosts of the first execution module. Subsequently, when the working node updates or upgrades the basic service and / or the deployment module, it can mount the domain name resolution information under the directory / data / kube / deploymentmodule / hosts to etc / hosts of the first deployment module after completing the update or upgrade. Figure 8 The "mount" in the command represents the mount operation.

[0300] The plug-in service deployment solution provided by the disclosed embodiment has flexible deployment, supports concurrent deployment of a large number of plug-ins, and does not affect the basic service deployment framework; on the other hand, it does not require the opening of container remote ports to ensure the network security of the environment. Moreover, in the host, / etc / hosts and / data / kube / deployment module / hosts are isolated, which can prevent the basic services represented in / etc / hosts from being affected by the second domain name resolution information corresponding to the newly deployed plug-in service, causing the basic service to fail during the plug-in service deployment process.

[0301] The present disclosure provides a service cluster, including:

[0302] A deployment node, configured to receive a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service; and generate task information according to the deployment information; wherein after the task information is monitored by a working node, it is used to deploy the first plug-in service to at least one target node in the working node;

[0303] A working node is used to monitor task information of a deployment node; wherein the task information is generated based on a deployment request received by a service port; a deployment request is used to request deployment of a first plug-in service; and the first plug-in service is deployed according to the task information.

[0304] In the embodiment of the present disclosure, the deployment node may be different from the working node, and the deployment node may execute any of the aforementioned plug-in service deployment methods executed by the deployment node. The working node may execute any of the aforementioned plug-in deployment methods executed by the working node.

[0305] like Fig.12 As shown, the embodiment of the present disclosure provides a plug-in service deployment device, the device comprising:

[0306] The first receiving module 110 is used to receive a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of the first plug-in service;

[0307] The generation module 120 is used to generate task information according to the deployment information; wherein, after the task information is monitored by the working node, it is used to deploy the first plug-in service in at least one target node in the working node.

[0308] The plug-in service deployment device may correspond to a deployment node.

[0309] In some embodiments, the first receiving module 110 and the generating module 120 may include a program module; after the program module is executed by the processor, the above operations can be performed.

[0310] In some other embodiments, the first receiving module 110 and the generating module 120 may include a soft-hard combination module; the soft-hard combination module may include a programmable array, which includes but is not limited to a field programmable array and / or a replica programmable array.

[0311] In some other embodiments, the first receiving module 110 and the generating module 120 may include pure hardware modules; the pure hardware modules include but are not limited to application specific integrated circuits.

[0312] Understandably, deployment information includes:

[0313] Configuration information, including at least: node information of the target node;

[0314] The environment variables include at least: a running environment state quantity of the first plug-in service.

[0315] It can be understood that the configuration information includes at least one of the following:

[0316] The network protocol IP address of the working node where the first plug-in service is to be deployed;

[0317] The node number of the working node where the first plug-in service is to be deployed;

[0318] The node name of the working node where the first plug-in service is to be deployed;

[0319] Node attribute information of the working node on which the first plug-in service is to be deployed.

[0320] It can be understood that the environment variables include at least one of the following:

[0321] Providing image information of a target container of the first plug-in service;

[0322] Database information;

[0323] Store information;

[0324] Log information.

[0325] It can be understood that, according to the deployment information, sending task information to at least one working node includes:

[0326] Update shared configuration and service function files according to deployment information;

[0327] Distribute task information to worker nodes based on shared configuration and service capability files.

[0328] It can be understood that the device also includes:

[0329] A status monitoring module, used to obtain the deployment status information of the target node;

[0330] The generating module 120 is used to send a deployment response to the client according to the deployment status information.

[0331] It can be understood that the status monitoring module is also used to monitor the deployment status information of the working node through the shared configuration and service function monitoring mechanism; wherein the deployment status information includes: deployment status variables; the deployment status variables indicate the deployment results.

[0332] like Fig.13 As shown, the embodiment of the present disclosure provides a plug-in service deployment device, the device comprising:

[0333] The second receiving module 210 is used to monitor the task information of the deployment node; wherein the task information is generated based on the deployment request received by the service port; the deployment request is used to request the deployment of the first plug-in service;

[0334] The deployment module 220 is used to deploy the first plug-in service according to the task information.

[0335] The plug-in service deployment device may correspond to a working node.

[0336] In some embodiments, the second receiving module 210 and the deployment module 220 may include a program module; after the program module is executed by the processor, the above operations can be performed.

[0337] In some other embodiments, the second receiving module 210 and the deployment module 220 may include a software-hard combination module; the software-hard combination module may include a programmable array, which includes but is not limited to a field programmable array and / or a replica programmable array.

[0338] In some other embodiments, the second receiving module 210 and the deploying module 220 may include pure hardware modules; the pure hardware modules include but are not limited to application specific integrated circuits.

[0339] It can be understood that the deployment information at least includes: configuration information, including: node information and environment variables; the node information indicates the target node to be deployed with the first plug-in service; the environment variables at least include: the running environment state of the first plug-in service.

[0340] It can be understood that the deployment module 220 is specifically used to determine whether the working node is a target node based on the task information; if the working node is a target node, generate creation input parameter information based on the task information; and deploy the first plug-in service based on the creation input parameter information.

[0341] It can be understood that creating input parameter information includes at least one of the following:

[0342] Image information, including image name and / or image tag;

[0343] Container information, describing the target container running the first plug-in service;

[0344] Explore live information;

[0345] Deployment status quantity;

[0346] Node ID;

[0347] Create information.

[0348] It can be understood that the deployment module 220 is used to generate routing rules for the first plug-in service.

[0349] Exemplarily, the deployment module 220 may generate a routing rule for the first plug-in service according to the second domain name resolution information of the first plug-in service.

[0350] It can be understood that the working node includes a deployment module 220 and an execution module; the first domain name resolution information maintained by the execution module is obtained; wherein the first domain name resolution information at least includes the domain name resolution information of the basic service; the deployment module determines the second domain name resolution information of the first plug-in service according to the task information; the deployment module receives the first domain resolution information from the execution module, and merges the received first domain name resolution information with the second domain name resolution information to obtain the third domain name resolution information; wherein the third domain name resolution information is used to respond to the service request, wherein the service request includes the domain name of the requested service.

[0351] An embodiment of the present disclosure further provides an electronic device, including:

[0352] processor;

[0353] a memory for storing processor-executable instructions;

[0354] The processor is configured to implement the plug-in service deployment method of any embodiment of the present disclosure when running the executable instructions.

[0355] The electronic device may at least be the aforementioned server, the first terminal and / or the second terminal.

[0356] The memory may include various types of storage media, which are non-transitory computer storage media that can continue to remember information stored thereon after the communication device loses power.

[0357] The processor can be connected to the memory through a bus or the like to read the executable program stored in the memory, for example, to implement the following Figures 1 to 7 The plug-in service deployment method shown.

[0358] The embodiments of the present disclosure also provide a computer-readable storage medium, which stores an executable program, wherein when the executable program is executed by a processor, the plug-in service deployment method of any embodiment of the present disclosure is implemented. Figures 1 to 7 The plug-in service deployment method shown.

[0359] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0360] The embodiment of the present disclosure provides an electronic device, comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: when running the executable instructions, implement the plug-in service deployment method provided by any of the above technical solutions, for example, Figures 1 to 7 The plug-in service deployment method shown.

[0361] like Fig.14 As shown, an embodiment of the present disclosure shows a structure of an electronic device. For example, the electronic device 900 can be provided as a network side device. Fig.14The electronic device 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions executable by the processing component 922, such as an application. The application stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 922 is configured as an executable program to perform any of the aforementioned methods for applying to the access device, such as Figures 1 to 7 The plug-in service deployment method shown.

[0362] The electronic device 900 may also include a power supply component 926 configured to perform power management of the electronic device 900, a wired or wireless network interface 950 configured to connect the electronic device 900 to a network, and an input / output (I / O) interface 958. The electronic device 900 may operate based on an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

[0363] In an exemplary embodiment, an embodiment of the present disclosure provides a computer-readable storage medium, which stores an executable program, wherein the executable program, when executed by a processor, implements the plug-in service deployment method provided by any of the aforementioned technical solutions.

[0364] The computer-readable storage medium may specifically be: a non-temporary computer-readable storage medium.

[0365] Exemplarily, for example, the memory 932 includes an executable program, and the above instructions can be executed by the processing component 922 of the electronic device 900 to complete the above method.

[0366] The non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

[0367] Those skilled in the art will readily appreciate other implementations of the disclosed embodiments after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosed embodiments, which follow the general principles of the disclosed embodiments and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and examples are to be considered as exemplary only, and the true scope and spirit of the disclosed embodiments are indicated by the following claims.

[0368] It should be understood that the embodiments of the present disclosure are not limited to the precise structures described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the embodiments of the present disclosure is limited only by the appended claims.

Claims

1. A plug-in service deployment method, characterized in that: Executed by the deployment node, including: Receiving a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service; Generate task information based on the deployment information; wherein, after the task information is monitored by the working node, it is used to deploy the first plug-in service on at least one target node in the working node.

2. The method according to claim 1, characterized in that The deployment information includes: Configuration information, including at least: node information of the target node; The environment variables include at least: the running environment state of the first plug-in service.

3. The method according to claim 1 or 2, wherein: The step of generating task information according to the deployment information includes: According to the deployment information; Generate or update a configuration file containing the task information; wherein, after the updated configuration file is monitored by the target node, it is used to deploy the first plug-in service.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Obtaining deployment status information of the target node; Sending a deployment response to the client according to the deployment status information.

5. The method according to claim 4, characterized in that The deployment status information includes: a deployment status variable; the deployment status variable indicates a deployment result.

6. A plug-in service deployment method, characterized in that: Executed by worker nodes, including: Monitoring the task information of the deployment node; wherein the task information is generated based on the deployment request received by the service port; the deployment request is used to request the deployment of the first plug-in service; A first plug-in service is deployed according to the task information.

7. The method according to claim 6, characterized in that The deployment information at least includes: configuration information, including: node information and environment variables; the node information indicates the target node to be deployed with the first plug-in service; the environment variables at least include: the running environment state of the first plug-in service.

8. The method according to claim 6 or 7, characterized in that: The step of deploying the plug-in according to the task information includes: Determine whether the working node is the target node according to the task information; In the case where the working node is the target node, generating creation input parameter information according to the task information; Deploy the first plug-in service according to the creation input parameter information.

9. The method according to any one of claims 6 to 8, characterized in that: The working node includes a deployment module and an execution module; the method further includes: Acquire the first domain name resolution information maintained by the execution module; wherein the first domain name resolution information at least includes: the domain name resolution information of the basic service; the deployment module determines the second domain name resolution information of the first plug-in service according to the task information; The deployment module receives the first domain resolution information from the execution module, and combines the received first domain name resolution information with the second domain name resolution information to obtain third domain name resolution information; The third domain name resolution information is used to respond to a service request, wherein the service request includes a domain name for the requested service.

10. The method according to any one of claims 6 to 9, characterized in that: The deploying the first plug-in service according to the creation input parameter information further includes: A routing rule for the first plug-in service is generated according to the second domain name information of the first plug-in service.

11. The method according to any one of claims 6 to 10, characterized in that: The method further comprises: Generate deployment status information according to the deployment status of the first plug-in service; The deployment status information is sent.

12. A plug-in service deployment device, characterized in that: The device comprises: A first receiving module, configured to receive a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service; A generation module is used to generate task information based on the deployment information; wherein, the task information is used to deploy the first plug-in service on at least one target node in the working node. After the task information is monitored by the working node, it is used to deploy the first plug-in service on at least one target node in the working node.

13. A plug-in service deployment device, characterized in that: The device comprises: A second receiving module is used to monitor the task information sent by the deployment node; wherein the task information is generated based on the deployment request received by the service port; the deployment request is used to request the deployment of the first plug-in service; A deployment module is used to deploy the first plug-in service according to the task information.

14. A service cluster, characterized in that: include: A deployment node, configured to receive a deployment request sent by a client based on a service port; wherein the deployment request includes deployment information of a first plug-in service; and generate task information according to the deployment information; wherein after the task information is monitored by a working node, it is used to deploy the first plug-in service to at least one target node in the working node; A working node is used to monitor the task information of the deployment node; wherein the task information is generated based on a deployment request received by a service port; the deployment request is used to request the deployment of a first plug-in service; and the first plug-in service is deployed according to the task information.

15. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to implement the plug-in service deployment method according to any one of claims 1 to 5 or 6 to 11 when running the executable instructions.

16. A computer-readable storage medium, characterized in that: The readable storage medium stores an executable program, wherein the executable program, when executed by a processor, implements the plug-in service deployment method according to any one of claims 1 to 5 or 6 to 11.