CN115801564A - Service deployment method, service deployment device, equipment and medium - Google Patents
Service deployment method, service deployment device, equipment and medium Download PDFInfo
- Publication number
- CN115801564A CN115801564A CN202211242179.2A CN202211242179A CN115801564A CN 115801564 A CN115801564 A CN 115801564A CN 202211242179 A CN202211242179 A CN 202211242179A CN 115801564 A CN115801564 A CN 115801564A
- Authority
- CN
- China
- Prior art keywords
- target
- service
- node
- deployment
- system version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a service deployment method, a service deployment device, equipment and a medium. The service deployment method comprises the following steps: receiving a service deployment request, wherein the service deployment request carries at least one target service to be deployed. And determining a target node meeting the service information corresponding to the target service from the plurality of nodes, and deploying the target service on the target node. And if the prompt information of the target service deployment completion is received, updating the target node to activate the target service. And if the abnormal alarm information is not received in the updating process, determining that the deployment is successful. By the method and the device, automatic deployment of the target service can be realized, so that the service deployment process is quicker and more convenient, the deployment efficiency is improved, and time cost and labor cost can be saved.
Description
Technical Field
The invention relates to the field of cloud computing, in particular to a service deployment method, a service deployment device, equipment and a medium.
Background
A Service (Service) is a component deployed in an operating system for performing tasks that do not require interaction with a user and that need to run for long periods of time.
In the related art, when a target service is deployed, a target node of the target service to be deployed is determined from a plurality of nodes of a distributed system by adopting a manual screening mode, and then the target service is deployed on the target node.
If the number of nodes in the distributed system is large, if the target node is still determined by adopting the method, a large amount of time cost and time cost are consumed, and the deployment efficiency is low. Therefore, how to improve the deployment efficiency of services in a distributed system becomes a problem to be solved urgently.
Disclosure of Invention
Therefore, the technical problem to be solved by the present invention is to overcome the defect of low service deployment efficiency in the prior art, and provide a service deployment method, a service deployment apparatus, a device, and a medium.
According to a first aspect, the present invention provides a service deployment method, the method comprising:
receiving a service deployment request, wherein the service deployment request carries at least one target service to be deployed;
determining a target node which meets service information corresponding to the target service from a plurality of nodes, and deploying the target service on the target node;
if receiving prompt information of the target service deployment completion, updating the target node to activate the target service;
and if the abnormal alarm information is not received in the updating process, determining that the deployment is successful.
In the mode, automatic deployment of the target service can be realized, and further the service deployment process is quicker and more convenient, so that the deployment efficiency is improved, and time cost and labor cost can be saved.
With reference to the first aspect, in a first embodiment of the first aspect, the determining, from among a plurality of nodes, a target node that satisfies service information corresponding to the target service includes:
respectively acquiring node attribute information corresponding to each node, and taking the node with the node attribute information matched with the service information as a candidate node;
determining a node load state corresponding to the candidate node;
and if the node load state meets a preset state, taking the candidate node as a target node.
With reference to the first aspect, in a second embodiment of the first aspect, the method further comprises:
acquiring running data of the target service in the target node within preset time;
detecting whether the target node fails or not under the condition that the operating data are abnormal;
and if the target node is determined to have a fault, migrating the target service to a next target node.
In this way, the running state of the target service can be monitored according to the running data of the target service in the target node within the preset time, so that the abnormality of the target service can be found in time. When the reason that the target service is abnormal is determined that the target node fails, the target service is timely migrated to the next target node to ensure that the target system can continue to provide the target service, and further loss caused by the current target node failure is reduced.
With reference to the second embodiment of the first aspect, in a third embodiment of the first aspect, the method further comprises:
generating a repair request based on the operation data, and sending the repair request to a target terminal sending the service deployment request;
receiving a patch file fed back by the target terminal based on the repair request;
and repairing the target service by using the patch file.
In combination with the first aspect, in a fourth embodiment of the first aspect, the method further includes:
caching the current system version information of the target node;
and the current system version corresponding to the current system version information provides the system version of the target service for the target node.
With reference to the fourth embodiment of the first aspect, in a fifth embodiment of the first aspect, the method further comprises:
if the abnormal alarm information is received in the updating process, deleting the current system version information of the target node;
determining a target system version from at least one historical system version based on log information that the target node runs under the at least one historical system version;
and controlling the target node to operate according to the target system version.
With reference to the fifth embodiment of the first aspect, in a sixth embodiment of the first aspect, the determining a target system version from the at least one historical system version based on log information of the target node operating under the at least one historical system version includes:
determining the last adopted historical system version of the target node before the target service is deployed from log information of the target node running under at least one historical system version by adopting an information rollback mode;
and determining the last adopted historical system version as a target system version.
According to a second aspect, the invention also provides a service deployment apparatus, the apparatus comprising:
a first receiving unit, configured to receive a service deployment request, where the service deployment request carries at least one target service to be deployed;
the deployment unit is used for determining a target node which meets service information corresponding to the target service from a plurality of nodes and deploying the target service on the target node;
the updating unit is used for updating the target node to activate the target service if the prompt message of finishing the target service deployment is received;
and the first detection unit is used for determining that the deployment is successful if the abnormal alarm information is not received in the updating process.
According to a third aspect, the present invention further provides a computer device, which includes a memory and a processor, where the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the service deployment method according to any one of the first aspect and the optional embodiments thereof.
According to a fourth aspect, the present invention further provides a computer-readable storage medium, which stores computer instructions for causing a computer to execute the service deployment method of the first aspect and any one of the optional implementation manners thereof.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flow chart of a proposed service deployment method according to an example embodiment.
Fig. 2 is a flow chart of another proposed service deployment method in accordance with an example embodiment.
Fig. 3 is a flow chart of yet another proposed service deployment method in accordance with an example embodiment.
Fig. 4 is a flow chart of yet another proposed service deployment method in accordance with an example embodiment.
Fig. 5 is a block diagram of a service deployment apparatus according to an exemplary embodiment.
Fig. 6 is a schematic diagram of a hardware structure of a computer device according to an exemplary embodiment.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it is to be understood that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
In the related art, when a target service is deployed, a target node of the target service to be deployed is determined from a plurality of nodes of a distributed system by adopting a manual screening mode, and then the target service is deployed on the target node.
The above approach is for a distributed system with a small number of nodes. If the number of nodes in the distributed system is large, if the target node is still determined by adopting the method, a large amount of time cost and time cost are consumed, and the deployment efficiency is low.
In order to solve the foregoing problems, an embodiment of the present invention provides a service deployment method, which is used in a distributed system, where an execution subject of the service deployment method may be any node deployed in the distributed system, and the node may be implemented as part or all of a computer device in a software, hardware, or a combination of software and hardware. In the following method embodiments, the execution subject is one of the nodes in the distributed system as an example.
In the distributed system in the embodiment of the invention, the node cluster is deployed. By the service deployment method provided by the invention, the target node capable of deploying the target service can be determined from the plurality of nodes after the service deployment request of the target service to be deployed is received. And the target node can meet the service information corresponding to the target service. And if the prompt information of the target service deployment completion is received, updating the target node to activate the target service, so that the target node can provide the target service in the running process. If the abnormal alarm information is not received in the updating process, the target service is represented to be successfully deployed on the target node, the target node can provide the target service in the operation process, and the successful deployment can be determined, so that the efficiency of service deployment is improved, the service deployment mode is more convenient and faster, and the labor cost is saved.
Fig. 1 is a flow chart of a proposed service deployment method according to an example embodiment. As shown in fig. 1, the service deployment method includes the following steps S101 to S104.
In step S101, a service deployment request is received.
In the embodiment of the invention, the service deployment request carries at least one target service to be deployed. The target service may include a cache service, a state service, a deployment service, a scheduling service interface management service, or an event rollback service, and may be set according to an actual requirement, which is not limited in the present invention.
In step S102, a target node satisfying the service information corresponding to the target service is determined from the plurality of nodes, and the target service is deployed on the target node.
In an embodiment of the invention, the target service may be deployed on at least one target node. That is, different nodes may provide different services, or two or more nodes may provide the same service, among the nodes in the distributed system. The target node may be determined according to the service information corresponding to the target service. That is, a node that can satisfy the service information corresponding to the target service among the plurality of nodes is determined as the target node. The service information may be understood as a usage environment of the target service. The usage environment may include a local area network environment, a wide area network environment, or an internet environment, and may be set according to actual requirements, which is not limited in the present invention.
In one example, the number of target nodes may be determined based on the service information. For example: if the service information corresponding to the target service is that the target service needs to be deployed in the wide area network environment, 1 node may be selected from the plurality of nodes as the target node. If the service information corresponding to the target service is that the target service needs to be deployed in the local area network environment, k nodes can be selected from the plurality of nodes as target nodes. Wherein k is more than or equal to 2, and k is a positive integer.
In step S103, if the prompt message indicating that the target service deployment is completed is received, the target node is updated to activate the target service.
In the embodiment of the invention, if the prompt message of the target service deployment completion is received, the target service is deployed on the target node by representing, and the target node is further updated to activate the target service, so that the target node can provide the target service in the running process.
In step S104, if the abnormal alarm information is not received in the updating process, it is determined that the deployment is successful.
In the embodiment of the invention, whether the information of each link is abnormal when the target node plans to run the target service in the updating process can be detected through an autonomous learning mode and a machine learning mode. If the abnormal alarm information is not received in the updating process, the representation target node can normally provide the target service, and further the successful deployment can be determined.
Through the embodiment, automatic deployment of the target service can be realized, and the service deployment process is quicker and more convenient, so that the deployment efficiency is improved, and time cost and labor cost can be saved.
In an embodiment, the target node may be determined based on node attribute information of the node. The node attribute information may include the working time, the working period, and the working state of the node. Specifically, node attribute information corresponding to each node is respectively obtained, and a node with the node attribute information matched with the service information is taken as a candidate node. And determining the node load state corresponding to the candidate node so as to determine the resource calling condition of the candidate node. If the node load state meets the preset state, the candidate node can be used as the target node.
In one example, the preset state can be understood as a node resource invokable state. If the node load state corresponding to the candidate node meets the preset state, the characteristic candidate node can be normally used, and further the characteristic candidate node can be determined as a target node, and the target service is deployed on the candidate node.
In another example, the preset state may be understood as a state in which the node resource call is not saturated and the remaining resources are sufficient to support the target service call while not affecting the resource calls of other existing services. If the node load state corresponding to the candidate node meets the preset state, the node resources representing the candidate node are sufficient, and the target service is deployed on the candidate node, so that the resource utilization rate of the candidate node can be improved, meanwhile, the risk that the load balance of the distributed system is damaged is favorably reduced, and the stability of the distributed system is favorably ensured. Thus, the candidate node may be considered a target node and the target service may be deployed on the candidate node.
Fig. 2 is a flow chart of another proposed service deployment method in accordance with an example embodiment. As shown in fig. 2, the service deployment method includes the following steps.
In step S201, a service deployment request is received.
In step S202, a target node satisfying the service information corresponding to the target service is determined from the plurality of nodes, and the target service is deployed on the target node.
In step S203, if the prompt message indicating that the target service deployment is completed is received, the target node is updated to activate the target service.
In step S204, if the abnormal alarm information is not received in the updating process, it is determined that the deployment is successful.
In step S205, operation data of the target node of the target service within a preset time is obtained.
In the embodiment of the present invention, the operation data may include data such as throughput, response time, resource utilization rate, and the like. In order to monitor the running condition of the target service, the running data of the target service in the target node within the preset time is acquired, so that the target service can be found to have a fault in time.
In step S206, in the case of an abnormal operation data, it is detected whether the target node has failed.
In the embodiment of the present invention, whether the operation parameter is abnormal may be determined based on the comparison result of the operation data and the standard data. And if the operation data is far deviated from the standard data, determining that the operation parameters are abnormal, and further detecting whether the target node has a fault so as to determine the reason of the abnormal operation parameters.
In step S207, if it is determined that the target node fails, the target service is migrated to the next target node.
In the embodiment of the invention, if the target node is determined to be in fault, the reason for representing the abnormal operation parameters is that the target node is in fault, so that the target service cannot normally operate.
Therefore, in order to ensure that the distribution system can continue to provide the target service, the next target node capable of deploying the target service is determined again from other nodes of the distribution system, and the target service is migrated to the next target node to provide the target service through the next target node, so that the situation that the use of a user is influenced because the current target node cannot normally provide the target service is avoided or reduced, and the loss caused by the fault of the current target node is reduced. The process of determining the next target node is the same as the process of determining the target node, and is not described herein again.
Through the embodiment, the running state of the target service can be monitored according to the running data of the target service in the target node within the preset time, so that the abnormity of the target service can be found in time. And when the reason that the target service is abnormal is determined to be that the target node fails, the target service is timely migrated to the next target node so as to ensure that the target system can continuously provide the target service, and further, the loss caused by the current target node failure is reduced.
In an embodiment, when a repair request generated based on the running data of the target service is received during the target node providing the target service, it is characterized that the target service has a fault (bug) to be repaired in actual running. Therefore, in order to ensure that the target service can normally run on the target node, the generated repair request is sent to the target terminal to inform the target terminal that the running of the target service is abnormal. The target terminal is a terminal sending a service deployment request. And receiving a patch file fed back by the target terminal based on the repair request, and repairing the target service by using the patch file. In one example, after the target service is repaired by the patch file, the patch file is stored so as to be repaired in time when the target service fails again.
In another embodiment, the current system version information of the target node is cached so that when the system of the target node fails, the target node can be quickly restored according to the cached current system version information. And the current system version corresponding to the current system version information provides the system version of the target service for the target node.
Fig. 3 is a flow chart of yet another proposed service deployment method in accordance with an example embodiment. As shown in fig. 3, the service deployment method includes the following steps.
In step S301, a service deployment request is received.
In step S302, a target node satisfying the service information corresponding to the target service is determined from the plurality of nodes, and the target service is deployed on the target node.
In step S303, if the prompt message indicating that the target service deployment is completed is received, the target node is updated to activate the target service.
In step S304, if the abnormal alarm information is not received in the updating process, it is determined that the deployment is successful.
In step S305, if the abnormal alarm information is received during the updating process, the current system version information of the target node is deleted.
In the embodiment of the invention, if the abnormal alarm information is received in the updating process, the target node is represented to be incapable of normally providing the target service, and the current system version information of the target node is deleted so as to cancel the deployment of the target service on the target node.
In step S306, a target system version is determined from the at least one historical system version based on log information that the target node operates under the at least one historical system version.
In the embodiment of the invention, at least one historical system version adopted by the target node in the operation process can be determined based on the log information of the target node in the operation of at least one historical system version. And in order to ensure the normal operation state of the target node, determining the target system version from at least one historical system version so as to control the target node to operate according to the target system version.
In an embodiment, a last-adopted historical system version of the target node before the target service is deployed may be determined from log information of the target node running under at least one historical system version in an information rollback manner, and the last-adopted historical system version may be determined as the target system version.
In step S307, the control target node operates according to the target system version.
By the embodiment, when the target service deployment fails, the target system version to be driven to operate by the target node can be determined from at least one historical system version adopted by the target node, and the target node is controlled to operate by the target system version, so that the safety influence on the distributed system caused by the failure of updating is avoided.
In an implementation scenario, in order to enable each node in the distributed system to implement the service deployment method provided by the present invention, the following services may be deployed in each node in advance: and the caching service is used for caching the historical system version information of the corresponding node so that when the system of the node fails, the node can be quickly restored to the previous version. And the proxy service is used for realizing network proxy on the node so as to maintain the node, maintain the network rule and balance the load of the node. The interface management service is used for unifying interface entries of the nodes, serving as coordinators of all components in the node system, providing interface services by RESTful API (design specification of Internet software architecture), and notifying upper-layer state services after processing the operations of adding, deleting, modifying, checking and monitoring all object resources. And the state service manages the state data set of the node by using the distributed key value pair. And the scheduling/deploying service is used for selecting the node information to be deployed for the newly created service according to a scheduling algorithm so as to determine the target nodes for deploying the service and the number of the target nodes. And the event rollback service is used for recording the log information of each system version of the node, and then when the system of the node breaks down, rolling back the current nearest version to determine the target system version adopted by the node to be operated, thereby avoiding the safety influence on the distributed system caused by the failure of updating.
In another implementation scenario, each node is also pre-deployed with: and the controller is used for monitoring the overall operation condition of the corresponding node. And the automatic test module is used for updating the nodes according to the prompt information of the completion of deployment, checking information of each link when the nodes operate the target service through autonomous learning and machine learning, representing that the updating is successful if no abnormal information or hang-up phenomenon occurs, otherwise generating a repair request to inform the controller, feeding the repair request back to the proxy service, transferring the repair request to the cache service, deleting the current system version information by the cache service, and returning the target system version information through event rollback service so as to control the target nodes to operate according to the target system version corresponding to the target system version information.
In yet another implementation scenario, the process of service deployment may be as shown in FIG. 4. Caching, by a caching service, at least one historical system version information for a node. And judging whether the caching is finished. And if the caching is determined to be completed, realizing the network proxy of the node in the distributed system by the proxy service. And if the cache is determined not to be finished, continuing to cache. The controller monitors the overall operating state of the node based on the communication interaction with the proxy service. If the interface management service detects a service deployment request sent by a target terminal, judging whether the node load state meets a preset state through the state service, and further determining whether the node is used as a target node. If the node is determined to meet the preset state, the target service is deployed on the target node through the scheduling/deploying service, and whether the deployment is completed is determined through whether prompt information of the completion of the deployment of the target service is received. And if the node is determined not to meet the preset state, the controller continuously monitors the overall operation state of the node. And if the deployment is determined to be completed, updating the target node to activate the target service. If not, the controller detects whether the target node fails. And detecting whether the information of each link is abnormal when the target node plans to run the target service in the updating process through an automatic test. And if the abnormal alarm information is not received in the updating process, determining that the deployment is successful. And if the abnormal alarm information is received in the updating process, informing the controller, feeding back to the proxy service, transferring to the cache service, deleting the current system version information by the cache service, and returning to the target system version information through the event rollback service so as to control the target node to operate according to the target system version corresponding to the target system version information.
Based on the same inventive concept, the invention also provides a service deployment device.
Fig. 5 is a block diagram of a service deployment apparatus according to an exemplary embodiment. As shown in fig. 5, the service deployment apparatus includes a first receiving unit 501, a deployment unit 502, an update unit 503, and a first detection unit 504.
A first receiving unit 501, configured to receive a service deployment request, where the service deployment request carries at least one target service to be deployed.
A deployment unit 502, configured to determine, from the multiple nodes, a target node that satisfies the service information corresponding to the target service, and deploy the target service on the target node.
An updating unit 503, configured to update the target node to activate the target service if the prompt information indicating that the target service is deployed is received.
The first detecting unit 504 is configured to determine that the deployment is successful if the abnormal alarm information is not received in the updating process.
In one embodiment, deployment unit 502 comprises: and the first acquisition unit is used for respectively acquiring the node attribute information corresponding to each node so as to take the node with the node attribute information matched with the service information as a candidate node. And the first determining unit is used for determining the node load state corresponding to the candidate node. And the screening unit is used for taking the candidate node as the target node if the node load state meets the preset state.
In another embodiment, the apparatus further comprises: and the second acquisition unit is used for acquiring the running data of the target service in the target node within the preset time. And the second detection unit is used for detecting whether the target node fails or not under the condition that the operation data is abnormal. And the migration unit is used for migrating the target service to the next target node if the target node is determined to have a fault.
In yet another embodiment, the apparatus further comprises: and the request sending unit is used for generating a repair request based on the running data and sending the repair request to the target terminal sending the service deployment request. And the second receiving unit is used for receiving the patch file fed back by the target terminal based on the repair request. And the first repairing unit is used for repairing the target service by using the patch file.
In yet another embodiment, the apparatus further comprises: and the cache unit is used for caching the current system version information of the target node. And the current system version corresponding to the current system version information provides the system version of the target service for the target node.
In yet another embodiment, the apparatus further comprises: and the execution unit is used for deleting the current system version information of the target node if the abnormal alarm information is received in the updating process. And the second determining unit is used for determining the target system version from the at least one historical system version based on the log information of the target node running under the at least one historical system version. And the control unit is used for controlling the target node to operate according to the target system version.
In still another embodiment, the second determination unit includes: and the second determining subunit is used for determining the last adopted historical system version of the target node before the target service is deployed from the log information of the target node running under at least one historical system version in an information rollback mode. And determining the last adopted historical system version as the target system version.
For specific limitations and beneficial effects of the service deployment apparatus, reference may be made to the above limitations on the service deployment method, which is not described herein again. The various modules described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
Fig. 6 is a schematic diagram of a hardware structure of a computer device according to an exemplary embodiment. As shown in fig. 6, the apparatus includes one or more processors 610 and a storage 620, where the storage 620 includes a persistent memory, a volatile memory, and a hard disk, and one processor 610 is taken as an example in fig. 6. The apparatus may further include: an input device 630 and an output device 640.
The processor 610, the memory 620, the input device 630, and the output device 640 may be connected by a bus or other means, such as the bus connection in fig. 6.
The memory 620, serving as a non-transitory computer-readable storage medium, includes a persistent memory, a volatile memory, and a hard disk, and may be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as program instructions/modules corresponding to the service management method in the embodiments of the present application. The processor 610 executes various functional applications of the server and data processing by executing non-transitory software programs, instructions, and modules stored in the memory 620, that is, implements any one of the service deployment methods described above.
The memory 620 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data used as needed or desired, and the like. Further, the memory 620 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 620 optionally includes memory located remotely from the processor 610, which may be connected to a data processing device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 630 may receive input numeric or character information and generate key signal inputs related to user settings and function control. The output device 640 may include a display device such as a display screen.
One or more modules are stored in the memory 620 and, when executed by the one or more processors 610, perform the methods illustrated in fig. 1-4.
The product can execute the method provided by the embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. Details of the technique not described in detail in the present embodiment may be specifically referred to the related description in the embodiments shown in fig. 1 to fig. 4.
Embodiments of the present invention further provide a non-transitory computer storage medium, where a computer-executable instruction is stored in the computer storage medium, and the computer-executable instruction may execute the authentication method in any of the above method embodiments. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk Drive (Hard Disk Drive, abbreviated as HDD), or a Solid State Drive (SSD); the storage medium may also comprise a combination of memories of the kind described above.
It should be understood that the above examples are only for clarity of illustration and are not intended to limit the embodiments. Other variations and modifications will be apparent to persons skilled in the art in light of the above description. And are neither required nor exhaustive of all embodiments. And obvious variations or modifications derived therefrom are intended to be within the scope of the invention.
Claims (10)
1. A method for service deployment, the method comprising:
receiving a service deployment request, wherein the service deployment request carries at least one target service to be deployed;
determining a target node which meets service information corresponding to the target service from a plurality of nodes, and deploying the target service on the target node;
if receiving prompt information of the target service deployment completion, updating the target node to activate the target service;
and if the abnormal alarm information is not received in the updating process, determining that the deployment is successful.
2. The method of claim 1, wherein the determining a target node from a plurality of nodes that satisfies the service information corresponding to the target service comprises:
respectively acquiring node attribute information corresponding to each node, and taking the node with the node attribute information matched with the service information as a candidate node;
determining a node load state corresponding to the candidate node;
and if the node load state meets a preset state, taking the candidate node as a target node.
3. The method of claim 1, further comprising:
acquiring running data of the target service in the target node within preset time;
detecting whether the target node fails or not under the condition that the operating data are abnormal;
and if the target node is determined to have a fault, migrating the target service to a next target node.
4. The method of claim 3, further comprising:
generating a repair request based on the running data, and sending the repair request to a target terminal sending the service deployment request;
receiving a patch file fed back by the target terminal based on the repair request;
and repairing the target service by using the patch file.
5. The method of claim 1, further comprising:
caching the current system version information of the target node;
and the current system version corresponding to the current system version information provides the system version of the target service for the target node.
6. The method of claim 5, further comprising:
if the abnormal alarm information is received in the updating process, deleting the current system version information of the target node;
determining a target system version from at least one historical system version based on log information that the target node runs under the at least one historical system version;
and controlling the target node to operate according to the target system version.
7. The method of claim 6, wherein determining a target system version from the at least one historical system version based on log information that the target node is operating under the at least one historical system version comprises:
determining a last adopted historical system version of the target node before the target service is deployed from log information of the target node running under at least one historical system version by adopting an information rollback mode;
and determining the last adopted historical system version as a target system version.
8. A service deployment apparatus, characterized in that the apparatus comprises:
a first receiving unit, configured to receive a service deployment request, where the service deployment request carries at least one target service to be deployed;
the deployment unit is used for determining a target node which meets the service information corresponding to the target service from a plurality of nodes and deploying the target service on the target node;
the updating unit is used for updating the target node to activate the target service if the prompt message of finishing the target service deployment is received;
and the first detection unit is used for determining that the deployment is successful if the abnormal alarm information is not received in the updating process.
9. A computer device comprising a memory and a processor, wherein the memory and the processor are communicatively connected, the memory stores computer instructions, and the processor executes the computer instructions to perform the service deployment method according to any one of claims 1 to 7.
10. A computer-readable storage medium storing computer instructions for causing a computer to perform the service deployment method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211242179.2A CN115801564A (en) | 2022-10-11 | 2022-10-11 | Service deployment method, service deployment device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211242179.2A CN115801564A (en) | 2022-10-11 | 2022-10-11 | Service deployment method, service deployment device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115801564A true CN115801564A (en) | 2023-03-14 |
Family
ID=85432770
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211242179.2A Pending CN115801564A (en) | 2022-10-11 | 2022-10-11 | Service deployment method, service deployment device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115801564A (en) |
-
2022
- 2022-10-11 CN CN202211242179.2A patent/CN115801564A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11108859B2 (en) | Intelligent backup and recovery of cloud computing environment | |
| CN110162382B (en) | Container-based gray level publishing method, device, computer equipment and storage medium | |
| CN111209110B (en) | Task scheduling management method, system and storage medium for realizing load balancing | |
| US11438249B2 (en) | Cluster management method, apparatus and system | |
| EP3591530B1 (en) | Intelligent backup and recovery of cloud computing environment | |
| CN111538585A (en) | Js-based server process scheduling method, system and device | |
| CN114531373A (en) | Node state detection method, node state detection device, equipment and medium | |
| CN114064438A (en) | Database fault processing method and device | |
| CN106897128B (en) | Distributed application quitting method, system and server | |
| CN112269693B (en) | Node self-coordination method, device and computer readable storage medium | |
| CN115801564A (en) | Service deployment method, service deployment device, equipment and medium | |
| CN115686831A (en) | Task processing method and device based on distributed system, equipment and medium | |
| CN115543393A (en) | Upgrading method, electronic device and storage medium | |
| CN115712521A (en) | Cluster node fault processing method, system and medium | |
| CN114942859A (en) | Method, device, equipment, medium and program product for processing node failure | |
| US9880855B2 (en) | Start-up control program, device, and method | |
| CN114816866A (en) | Fault processing method and device, electronic equipment and storage medium | |
| CN113987065A (en) | Database drifting method, system, electronic device and storage medium | |
| CN109510867B (en) | Data request processing method and device, storage medium and electronic equipment | |
| CN107783855B (en) | Fault self-healing control device and method for virtual network element | |
| CN111858234A (en) | Task execution method, device, equipment and medium | |
| CN110955647A (en) | Database assistance method, database assistance device, computer equipment and storage medium | |
| CN113872808B (en) | Application processing method and device | |
| CN111338647A (en) | Big data cluster management method and device | |
| CN112822257B (en) | Web service management system, method and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |