Service scheduling method and device, equipment and storage medium

Abstract

The invention provides a service scheduling method and device, equipment and a storage medium. The method comprises the steps that a management end can respond to a first operation of a user to obtain service deployment configuration information, and the service deployment configuration information comprises service starting information, service dependence information and service deployment information; a deployment command message can be issued to a working end according to service deployment information based on a dependency relationship in the service dependency information, and the working end can receive the deployment command message sent by a management end, call an actuator of the working end and deploy the service to a runtime environment according to the deployment command message. According to the method provided by the invention, the service deployment configuration information can be obtained through the unified protocol template, and various service processes are automatically scheduled and executed according to the service deployment configuration information, so that the convenience, the adaptation capability and the automation degree during service deployment are improved, and the service deployment efficiency is improved.

Description

Technical Field

[0001] This application relates to the technical field of service scheduling, and in particular, to a service scheduling method, apparatus, device, and storage medium. Background Art

[0002] With the development of Internet and cloud computing technologies, services can be deployed to runtime environments such as physical machines, virtual machines, and containers to efficiently utilize computing resources.

[0003] With the enrichment of functions of more and more services, the dependency relationships among service processes in a service become more and more complex. The existing technical implementation solutions for deploying services to different runtime environments are based on the scheduling and deployment logic at the service process level, which requires the configuration information to be highly bound to the runtime environment. Users need to provide a series of configuration files for service processes and strictly follow the requirements of the configuration files to sequentially schedule and start service processes. However, in the above process, users need to manually issue configuration information in sequence according to the startup order of each service process, resulting in low service deployment efficiency. Summary of the Invention

[0004] This application provides a service scheduling method, apparatus, device, and storage medium, which can automatically schedule and execute various service processes according to the deployment time sequence of service processes in a service, improving service deployment efficiency.

[0005] In a first aspect, this application provides a service scheduling method, which is applied to a management end. The method includes:

[0006] In response to a first operation of a user, obtain service deployment configuration information, where the service deployment configuration information includes service startup information, service dependency information, and service deployment information;

[0007] Based on the dependency relationships in the service dependency information, send a deployment command message to a working end according to the service deployment information, where the deployment command message carries the service startup information.

[0008] In a possible implementation manner, the obtaining service deployment configuration information in response to the first operation of the user includes:

[0009] Receive the service deployment configuration information input by the user, where the first operation is an input operation;

[0010] Or,

[0011] In response to a selection operation of the user on a preset deployment template, obtain the service deployment configuration information, where the deployment template includes: multiple services, startup information and deployment information of each service, and dependency information between processes; the first operation is a selection operation.

[0012] In a possible implementation, the service startup information includes at least one service, the startup parameters, runtime environment, and configuration file of each service;

[0013] The service dependency information includes the dependency relationships between service processes;

[0014] The service deployment information includes the worker nodes to which each service is deployed and the number of deployment replicas;

[0015] Correspondingly, sending a deployment command message to the worker nodes according to the service deployment information, where the deployment command message carries the service startup information, includes:

[0016] For each service, send a deployment command message to the worker node corresponding to the service in the service deployment message, where the deployment command message includes the startup parameters, runtime environment, and configuration file of the service.

[0017] In a possible implementation, the method further includes:

[0018] In response to a second operation of the user, obtain a service stop command or a service deletion command for the service, where the second operation is a service stop operation or a service deletion operation;

[0019] Send the service stop command or the service deletion command to the worker node corresponding to the service.

[0020] In a second aspect, the present application provides a service scheduling method, which is applied to a worker node, and the method includes:

[0021] Receive a deployment command message sent by a management node, where the deployment command message includes the startup parameters, runtime environment, and configuration file of the service;

[0022] Call the executor of the worker node, and deploy the service to the runtime environment according to the deployment command message; the executor is used to perform initialization, startup operation, and status acquisition operation on the service according to the startup parameters and configuration file.

[0023] In a possible implementation, the method further includes:

[0024] Receive the service stop command or the service deletion command sent by the management node;

[0025] According to the service stop command, call the executor to stop the service, or according to the service deletion command, call the executor to delete the service; the executor is further used to perform stop or deletion operation on the service.

[0026] In a possible implementation manner, after receiving the deployment command message sent by the receiving management end, the method further includes:

[0027] Perform permission verification on the management end and verify the data structure of the deployment command message;

[0028] Correspondingly, calling the executor of the worker end to deploy the service to the runtime environment according to the deployment command message includes:

[0029] After both the permission of the management end and the data structure of the deployment command message pass the verification, call the executor of the worker end to deploy the service to the runtime environment according to the deployment command message.

[0030] In a third aspect, the present application provides a service scheduling device, and the device includes:

[0031] An acquisition module, configured to obtain service deployment configuration information in response to a first operation of a user, where the service deployment configuration information includes service start information, service dependency information, and service deployment information;

[0032] A sending module, configured to send a deployment command message to the worker end according to the service deployment information based on the dependency relationship in the service dependency information, where the service start information is carried in the deployment command message.

[0033] In a possible implementation manner, the acquisition module is specifically configured to:

[0034] Receive the service deployment configuration information input by the user, where the first operation is an input operation;

[0035] Or,

[0036] In response to a selection operation of the user on a preset deployment template, obtain the service deployment configuration information, where the deployment template includes: multiple services, start information and deployment information of each service, and dependency information between processes; the first operation is a selection operation.

[0037] In a possible implementation manner, the service start information includes at least one service, start parameters, runtime environment, and configuration file of each service;

[0038] The service dependency information includes the dependency relationship between service processes;

[0039] The service deployment information includes the worker end where each service is deployed and the number of deployment replicas;

[0040] Correspondingly, the sending module is specifically configured to:

[0041] For each service, a deployment command message is sent to the worker corresponding to the service in the service deployment message, and the deployment command message includes startup parameters, a runtime environment, and a configuration file of the service.

[0042] In a possible implementation manner, the obtaining module is further configured to, in response to a second operation of the user, obtain a service stop command or a service deletion command for the service, where the second operation is a service stop operation or a service deletion operation;

[0043] The sending module is further configured to send the service stop command or the service deletion command to the worker corresponding to the service.

[0044] In a fourth aspect, the present application provides a service scheduling device, where the device includes:

[0045] A receiving module, configured to receive a deployment command message sent by a management end, where the deployment command message includes startup parameters, a runtime environment, and a configuration file of a service;

[0046] A processing module, configured to call an executor of a worker to deploy the service to the runtime environment according to the deployment command message; the executor is configured to perform initialization, startup operation, and status obtaining operation on the service according to the startup parameters and the configuration file.

[0047] In a possible implementation manner, the receiving module is further configured to receive the service stop command or the service deletion command sent by the management end;

[0048] The processing module is further configured to call the executor to stop the service according to the service stop command, or call the executor to delete the service according to the service deletion command; the executor is further configured to perform a stop or deletion operation on the service.

[0049] In a possible implementation manner, the receiving module is further configured to perform permission verification on the management end and verify the data structure of the deployment command message;

[0050] Correspondingly, the processing module is specifically configured to:

[0051] After both the permission of the management end and the data structure of the deployment command message pass the verification, call the executor of the worker to deploy the service to the runtime environment according to the deployment command message.

[0052] In a fifth aspect, the present application provides an electronic device, including: a processor, a memory, and a communication interface;

[0053] The memory stores computer-executable instructions;

[0054] The processor executes the computer-executable instructions stored in the memory, such that the processor executes the service scheduling method according to any one of the first aspect or the second aspect.

[0055] In a sixth aspect, the present application provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the service scheduling method according to any one of the first aspect or the second aspect when being executed by a processor.

[0056] In a seventh aspect, the present application provides a computer program product including a computer program, which implements the service scheduling method according to any one of the first aspect or the second aspect when being executed by a processor.

[0057] The service scheduling method, apparatus, device and storage medium provided by the present application can, after responding to the input service deployment configuration information of a user or selecting a preset deployment template, enable a management end to obtain service deployment configuration information, where the service deployment configuration information includes service start information, service dependency information and service deployment information. Based on the dependency relationship in the service dependency information, the service start information corresponding to the service deployment information can be sent to each worker end. After receiving the service start information corresponding to the service deployment information, the worker end can call an executor of the worker end to deploy the service to different runtime environments. By providing a means of a unified specification template to obtain service deployment configuration information, and according to the deployment sequence of each service process in the service deployment configuration information, various service processes can be automatically executed and scheduled, effectively improving the convenience during the initial deployment of services, greatly enhancing the adaptation ability of service deployment, and further improving the service deployment efficiency. Description of the Drawings

[0058] The drawings here are incorporated into the description and form a part of this description, showing embodiments consistent with the present application and used together with the description to explain the principles of the present application.

[0059] Figure 1 It is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0060] Figure 2 It is a schematic flowchart of a first embodiment of a service scheduling method provided by an embodiment of the present application;

[0061] Figure 3 It is a schematic diagram of a dependency relationship provided by an embodiment of the present application;

[0062] Figure 4 It is a schematic diagram of the principle of a customized executor with a unified interface provided by an embodiment of the present application;

[0063] Figure 5 A deployment schematic diagram of the management end and the working end provided by an embodiment of the present application;

[0064] Figure 6 A flowchart of the second embodiment of a service scheduling method provided by an embodiment of the present application;

[0065] Figure 7 A schematic diagram of a service initialization process provided by an embodiment of the present application;

[0066] Figure 8 A schematic diagram of a service startup process provided by an embodiment of the present application;

[0067] Figure 9 A flowchart of the third embodiment of a service scheduling method provided by an embodiment of the present application;

[0068] Figure 10 A schematic diagram of a service stop and deletion process provided by an embodiment of the present application;

[0069] Figure 11 A schematic diagram of a service exception recovery process provided by an embodiment of the present application;

[0070] Figure 12 A schematic structural diagram of the first embodiment of a service scheduling device provided by an embodiment of the present application;

[0071] Figure 13 A schematic structural diagram of the second embodiment of a service scheduling device provided by an embodiment of the present application;

[0072] Figure 14 A schematic structural diagram of an electronic device provided by an embodiment of the present application.

[0073] Through the above-mentioned drawings, the clear embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These drawings and the textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed implementation manners

[0074] Here, the exemplary embodiments will be described in detail, and the examples are shown in the 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 implementation manners described in the following exemplary embodiments do not represent all the implementation manners consistent with the present application. On the contrary, they are only examples of the devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0075] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments of this application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0076] It should be noted that a service scheduling method, device, equipment, and storage medium provided in this application can be used in the technical field of service scheduling, and can also be used in any field other than the technical field of service scheduling. The application fields of the service scheduling method, device, equipment, and storage medium provided in this application are not limited.

[0077] For ease of understanding, below, in conjunction with Figure 1 , the application scenarios applicable to the embodiments of this application will be described.

[0078] Figure 1 is a schematic diagram of the application scenario provided for the embodiments of this application. Please refer to Figure 1 , the management end can, in response to a user's operation, obtain the service deployment configuration information corresponding to the service, and according to the service deployment configuration information, send a deployment command message to the worker end. After receiving the deployment command message, the worker end can call the executor of the worker end to deploy the service to the runtime environment.

[0079] For example, the management end can, in response to a user's operation, obtain the service deployment configuration information 1 corresponding to Service 1, and according to the service deployment configuration information 1, send a deployment command message 1 to the worker end. After receiving the deployment command message 1, the worker end can call the executor of the worker end to deploy Service 1 to the virtual machine.

[0080] As the functions of more and more services become richer, the dependency relationships between the service processes in the services are also becoming more and more complex. The existing technical implementation solutions for deploying services to different runtime environments are based on the scheduling and deployment logic at the service process level, requiring the configuration information to be highly bound to the runtime environment. Users need to provide a series of configuration files for the service processes and strictly follow the requirements of the configuration files to sequentially schedule and start the service processes. However, in the above process, users need to manually send the configuration information in sequence according to the startup order of each service process, resulting in low service deployment efficiency.

[0081] In view of the above problems, the inventors found that during the process of deploying services in different runtime environments. After the user inputs service deployment configuration information or selects a preset deployment template, the management end can obtain the service deployment configuration information, which includes service startup information, service dependency information, and service deployment information. Based on the dependency relationships in the service dependency information, the service startup information corresponding to the service deployment information can be sent to each worker end. After receiving the service startup information corresponding to the service deployment information, the worker end can call the executor of the worker end to deploy the service to different runtime environments. Based on this, this solution proposes a service scheduling method that can adapt to runtime environments such as physical machines, virtual machines, or containers, and can automatically schedule and execute various service processes through service deployment configuration information, improving service deployment efficiency.

[0082] Next, the technical solutions shown in this application will be described in detail through specific embodiments. It should be noted that the following several embodiments can exist independently or be combined with each other. For the same or similar content, it will not be repeated in different embodiments.

[0083] Figure 2 It is a schematic flowchart of the first embodiment of a service scheduling method provided by an embodiment of this application. Please refer to Figure 2 , this method includes:

[0084] S101. In response to a first operation of the user, obtain service deployment configuration information, where the service deployment configuration information includes service startup information, service dependency information, and service deployment information.

[0085] To deploy the services required to support the business to different runtime environments, in response to the first operation of the user, the first operation can be an input operation or a selection operation, and obtain service deployment configuration information, where the service deployment configuration information includes service startup information, service dependency information, and service deployment information. In a specific implementation, the management end can receive the service deployment configuration information input by the user, or, in response to the user's selection operation on the preset deployment template, obtain the service deployment configuration information, and the deployment template includes: multiple services, the startup information and deployment information of each service, and the dependency information between processes.

[0086] In a specific implementation manner, the service startup information includes at least one service, the startup parameters, runtime environment, and configuration files of each service. For example, the service startup information 1 includes: Service 1, and the service name corresponding to Service 1 can be a distributed publish-subscribe messaging system (Kafka); the startup parameters of Service 1 include: Parameter 1 and Parameter 2, where Parameter 1 can be 4 GB (gigabytes) of memory and Parameter 2 can be the operating frequency of the CPU (central processing unit) of 2.5 GHz (gigahertz); the runtime environment can be a virtual machine; the configuration files can include Configuration File 1 and Configuration File 2, where Configuration File 1 can be the storage path of the Kafka runtime log and Configuration File 2 can be the number of threads for processing network requests.

[0087] In a specific implementation manner, the service dependency information includes the dependency relationships between service processes and the sequence of service startup.

[0088] Figure 3 A schematic diagram of the dependency relationship provided by an embodiment of the present application. Please refer to Figure 3 , Service 1 can have four service processes, namely Service Process A, Service Process B, Service Process C, and Service Process D. There are no other dependencies between Service Process A and Service Process B. Service Process C needs to be deployed on the same working node as Service Process B and needs to be started after Service Process B on this node is started. Service Process D needs to be started after Service Process A on Working Node 1, Service Process C on Working Node 2, and Service Process C on Working Node 3 are started.

[0089] Optionally, Working Node 1 where Service Process A is located, Working Node 2 where Service Process B and Service Process C are located, Working Node 3 where Service Process B and Service Process C are located, and Working Node 4 where Service Process D is located can be set on the same working end according to user requirements, or can be set on different working ends. For example, Working Nodes where Service Process A, Service Process B, Service Process C, and Service Process D are located are on the same Working End 1.

[0090] In a specific implementation manner, the service deployment information includes the working end where each service is deployed and the number of deployment replicas. To avoid the impact of single-point failures and single-node crashes, services required to support the business can be deployed with multiple replicas and multiple working ends. For example, Service 1 can be deployed with a number of 3 deployment replicas. Among them, Deployment Replica 1 can be deployed on Working End 1, Deployment Replica 2 can be deployed on Working End 2, and Deployment Replica 3 can be deployed on Working End 3.

[0091] In an alternative embodiment, a configuration preprocessing module and a service status management module can be set up on the management side. The configuration preprocessing module manages the obtained service deployment configuration information. The service status management module stores the current status and expected status of each service process, as well as the dependency relationships between various service processes, and can schedule services in sequence according to the dependency relationships. Optionally, the current status and expected status can include six statuses: uninitialized, initialized, stopped, started, starting, and stopping.

[0092] For example, the management side can, in response to a user's input operation, obtain deployment configuration information 1 corresponding to Service 1. The deployment configuration information 1 includes service startup information 1, service dependency information 1, and service deployment information 1.

[0093] S102. Based on the dependency relationships in the service dependency information, send a deployment command message to the worker side according to the service deployment information.

[0094] During the service deployment process, since a service can include multiple service processes and there can be dependency relationships between service processes, a deployment command message can be sent to the worker side based on the dependency relationships in the service dependency information according to the service deployment information. The deployment command message carries service startup information. In a specific implementation, based on the dependency relationships in the service dependency information, for each service, a deployment command message can be sent to the corresponding worker side in the service deployment message. The deployment command message includes the startup parameters, runtime environment, and configuration file of the service.

[0095] For example, based on the dependency relationships in service dependency information 1, for Service 1, a deployment command message 1 can be sent to worker side 1 corresponding to Service 1 in service deployment message 1.

[0096] S103. Call the executor of the worker side and deploy the service to the runtime environment according to the deployment command message.

[0097] After receiving the deployment command message sent by the management side, the worker side can call the executor of the worker side and deploy the service to the runtime environment according to the startup parameters, runtime environment, and configuration file of the service included in the deployment command message. Among them, the executor is used to perform initialization, startup operation, and status acquisition operation on the service according to the startup parameters and configuration file.

[0098] In an alternative embodiment, a service process management module and an executor may be provided at the working end. The service process management module is responsible for the life cycle management and status reporting of all service processes of the current working node; the executor can be customized according to user requirements to obtain a customized executor, and the customized executor has a set of unified executor interfaces for completing service initialization, running services, stopping services, deleting services, and obtaining status work.

[0099] Figure 4 This is a schematic diagram of the principle of a customized executor with a unified interface provided by an embodiment of the present application. Please refer to Figure 4 , the customized executor can adapt to the executor interface upward and dock with the runtime environment downward for different runtime environments, and provide service process solutions. For example, for a physical machine to dock with the latest initialization system (init) in the Linux system, and for a container to dock with image management and container execution (Containerd) for process management.

[0100] To further illustrate the deployment command message sent by the management end and the process of the working end receiving the deployment command message, in combination with Figure 5 , the deployment of the management end and the working end will be described in detail.

[0101] Figure 5 This is a schematic diagram of the deployment of the management end and the working end provided by an embodiment of the present application. Please refer to Figure 5 , the management end can receive the service deployment configuration information input by the user, or obtain the service deployment configuration information in response to the user's selection of a preset deployment template. The configuration preprocessing module can preprocess the obtained service deployment configuration information, save the service dependency information in the service deployment configuration information to the service status management module, and send the corresponding service start information to each working end according to the service deployment information in the service deployment configuration information. Subsequently, the service status management module can monitor the current status of each service of the working end and schedule the corresponding service processes in sequence according to the service dependency information; the service process management module of the working end can receive the service start information, call the interface of the customized executor to perform the initialization work of the service and be responsible for the life cycle management work of the service.

[0102] For example, after receiving the deployment command message 1 sent by the management end, working end 1 can call the executor of working end 1 and deploy service 1 to the virtual machine according to parameter 1, parameter 2, virtual machine, configuration file 1, and configuration file 2 included in the deployment command message 1.

[0103] In an embodiment of the present application, the management terminal may, in response to a first operation of a user, obtain service deployment configuration information, which includes service startup information, service dependency information, and service deployment information. Moreover, the management terminal may, based on the dependency relationships in the service dependency information, send a deployment command message to the worker terminal according to the service deployment information. After receiving the deployment command message sent by the management terminal, the worker terminal may invoke an executor of the worker terminal to deploy the service into the runtime environment according to the deployment command message. In the above process, various service processes can be automatically scheduled and executed through the service deployment configuration information, improving the service deployment efficiency.

[0104] Next, based on the Figure 2 embodiment shown, in combination with Figure 6 , the above service scheduling method will be further described.

[0105] Figure 6 FIG. is a schematic flowchart of a second embodiment of a service scheduling method provided by an embodiment of the present application. Please refer to Figure 6 , the method includes:

[0106] S201. Receive service deployment configuration information input by a user, or obtain service deployment configuration information in response to a user's selection operation on a preset deployment template. The service deployment configuration information includes service startup information, service dependency information, and service deployment information.

[0107] During continuous business development, the user can deploy services required to support the business into different runtime environments to provide corresponding functions for the business. The user can define a unified specification template on the management terminal, input the service deployment configuration information into the specification template to obtain the service deployment configuration information, or obtain the service deployment configuration information by responding to the user's selection of a preset deployment template on the management terminal.

[0108] Optionally, the service deployment information may further include the deployment working nodes of the service processes owned by each service. For example, Service 2 may have four service processes, namely Service Process A, Service Process B, Service Process C, and Service Process D. Service Process A can be deployed on Working Node 1 of Worker Terminal 2, Service Process B and Service Process C can be deployed on Working Nodes 2 and 3 of Worker Terminal 2, and Service Process D can be deployed on Working Node 4 of Worker Terminal 2.

[0109] In a specific implementation, a specification template refers to a service deployment configuration information template that complies with regulations, is pre-designed, and can be reused, and can be customized by users; a preset deployment template may refer to a template provided by the service and pre-stored by the management end. For example, a distributed publish-subscribe messaging system can provide a preset deployment template, and the service deployment configuration information 2 corresponding to Service 2 can be obtained through the preset deployment template.

[0110] Optionally, the management end obtains the service deployment configuration information, which can also be obtained by comprehensively combining the specification template input by the user on the basis of selecting a preset deployment template.

[0111] For example, the management end can respond to the user's selection operation of the preset deployment template, obtain the deployment configuration information 2 corresponding to Service 2, and the service deployment configuration information 2 includes service startup information 2, service dependency information 2, and service deployment information 2.

[0112] S202. Based on the dependency relationships in the service dependency information, for each service, send a deployment command message to the worker corresponding to the service in the service deployment message.

[0113] Since the deployment configuration information includes service dependency information, and the service dependency information determines the startup sequence of the service processes included in the service, it is possible to send a deployment command message to the worker corresponding to the service in the service deployment message based on the dependency relationships in the service dependency information. The deployment command message includes the startup parameters, runtime environment, and configuration file of the service; optionally, the deployment command message can also include the working nodes where the service processes are arranged on the worker.

[0114] For example, based on the dependency relationships in the service dependency information 2, for Service 2, send a deployment command message 2 to the worker 2 corresponding to Service 2 in the service deployment message 2. The deployment command message 2 includes the startup parameters, runtime environment, and configuration file of Service 2; optionally, the deployment command message 2 also includes deploying the A service process of Service 2 on the working node 1 of the worker 2, deploying the B service process and the C service process on the working nodes 2 and 3 of the worker 2, and deploying the D service process on the working node 4 of the worker 2.

[0115] S203. Perform permission verification on the management end and verify the data structure of the deployment command message.

[0116] In order to accurately execute the deployment command message sent by the management end, the worker needs to perform permission verification on the management end and verify the data structure of the deployment command message, so as to ensure that the received deployment command message has an accurate source and the data structure meets the data structure requirements of the worker.

[0117] In a specific implementation, permission verification of the management end can be performed by verifying the management end identifier carried in the deployment command message sent by the management end. For example, if the management end identifier 0 is stored in the worker 2 and the deployment command message 2 received by the worker 2 carries the management end identifier 0, it can be considered that the management end has the permission to issue the deployment command message 2.

[0118] In a specific implementation, verification of the data structure of the deployment command message can be performed by verifying whether the number, order, and type of the fields included in the deployment command message sent by the management end conform to the number, order, and type of the fields recognizable by the worker. For example, for the deployment command message 2 received by the worker 2, the deployment command message 2 has 3 fields, with the order being field A, field B, and field C respectively, and the type of the fields can be floating-point type, which conforms to the number, order, and type of the fields recognizable by the worker 2. Then it can be considered that the data structure of the deployment command message 2 issued by the management end conforms to the data structure requirements of the worker 2.

[0119] For example, the worker 2 can perform identity verification on the management end and verify the data structure of the deployment command message 2.

[0120] S204. After both the permission of the management end and the data structure of the deployment command message pass the verification, call the executor of the worker, and deploy the service to the runtime environment according to the deployment command message.

[0121] After both the permission of the management end and the data structure of the deployment command message pass the verification, the worker can call the executor of the worker, and deploy the service to the runtime environment according to the startup parameters, runtime environment, and configuration file of the service included in the deployment command message; optionally, it can also deploy the service processes included in the service to different worker nodes in the runtime environment according to the worker nodes where the service processes are arranged in the worker as included in the deployment command message. Among them, the executor is used to perform initialization, startup, and status acquisition operations on the service according to the startup parameters and configuration file.

[0122] For example, the worker 2 can perform identity verification on the management end and verify the data structure of the deployment command message 2, and the verification results can both pass. Then the executor of the worker 2 can be called to deploy the service 2 to the runtime environment according to the startup parameters, runtime environment, and configuration file of the service 2 included in the deployment command message 2; optionally, the service process A owned by the service 2 can be deployed on the worker node 1 in the runtime environment, the B service process and the C service process can be deployed on the worker nodes 2 and 3 in the runtime environment, and the D service process can be deployed on the worker node 4 in the runtime environment.

[0123] In the embodiments of the present application, the management end may receive service deployment configuration information input by a user, or obtain service deployment configuration information in response to a user's selection operation on a preset deployment template. The service deployment configuration information includes service startup information, service dependency information, and service deployment information. Based on the dependency relationships in the service dependency information, for each service, a deployment command message is sent to the corresponding worker end in the service deployment message. After receiving the deployment command message sent by the management end, the worker end may perform permission verification on the management end and verify the data structure of the deployment command message. After both the permission of the management end and the data structure of the deployment command message pass the verification, the executor of the worker end may be called to deploy the service to the runtime environment according to the deployment command message. In the above process, through the service deployment configuration information, services and service processes can be deployed, and various service processes can be automatically scheduled and executed, improving the service deployment efficiency.

[0124] In a specific implementation manner, when a service is created or updated, a service initialization process and a startup process of the service process may be executed.

[0125] Figure 7 It is a schematic diagram of a service initialization process provided by the embodiments of the present application. Please refer to Figure 7 , and this process includes:

[0126] S301. Send down user configuration.

[0127] In this step, the user may create directories, files required for the operation of the service process, or configure necessary environment variables, kernel parameters, etc., to obtain a service deployment configuration information template. The management end may obtain the service deployment configuration information in response to the user's input operation. The service deployment configuration information includes service startup information, service dependency information, and service deployment information.

[0128] S302. Transmit the service dependency information to the service status management module.

[0129] The configuration preprocessing module may analyze and split the service deployment configuration information, and save the service dependency information in the service deployment configuration information to the service status management module.

[0130] S303. Send down the configuration to the worker end including the corresponding runtime environment.

[0131] The configuration preprocessing module may send the service startup information to the service process management module of the worker end according to the service deployment information.

[0132] S304. Determine whether the configuration has changed.

[0133] After receiving the service startup information, the service process management module can determine whether the service startup information is the same as the existing service process information. If not, it can further determine whether the service process is running. If it is running, the service process can be stopped first.

[0134] S305. If it is a new creation or configuration change, call the initialization interface and return the initialization result.

[0135] If it is a new service and the existing service configuration is updated, the service process management module can call the service initialization interface of the customized executor of the current worker and return the initialization result. The initialization result can be: Initialized.

[0136] S306. Set the status of the corresponding service to Initialized.

[0137] After the service process management module completes the service initialization by calling the customized executor of the current worker, it can set the status of the current service to Initialized and send it to the service status management module.

[0138] In the embodiment of the present application, when initializing the service, the management end can obtain the service deployment configuration information in response to the user's input operation. The configuration preprocessing module of the management end can analyze and split the service deployment configuration information, transfer the service dependency information included in the service deployment configuration information to the service status management module, and distribute the service startup information included in the service deployment configuration information to the service process management module of the worker according to the service deployment information. The service process management module can judge the received service startup information. If it is a new service or service configuration update, it can call the service initialization interface of the customized executor of the current worker, set the status of the current service to Initialized and send it to the service status management module. During the process of initializing the service, the service deployment configuration information can be obtained according to the unified specification template, adapting to the runtime environment such as physical machines, virtual machines or containers, improving the convenience during the initial deployment of the service, greatly enhancing the adaptation ability of the service deployment, and improving the service deployment efficiency.

[0139] In a specific implementation manner, after the service initialization is completed, the service can be started. Specifically, the specific execution process of the service startup can be described by the startup of the service process included in the service.

[0140] Figure 8 It is a schematic diagram of a service startup process provided by the embodiment of the present application. Please refer to Figure 8 , and the process includes:

[0141] S401. Calculate the service processes to be started by calculating the status of various service processes managed.

[0142] Since the service status management module can obtain the dependency information of the service process during the service initialization phase and can also manage the current status information of all service processes reported by all worker service process management modules, the service status management module can adjust the expected status of the service process based on the dependency relationships in the service dependency information.

[0143] For example, if the dependent B service process of the C service process has not been started, the expected status of the C service process can be modified to stopped until the B service process on which the C service process depends is successfully started.

[0144] S402. Start the service process.

[0145] When the service status management module adjusts the expected status of the service process, it can also tune the status of various service processes it manages in real time. If the current status of a service process does not match its expected status, it can enter the service process startup process and send a request to start the service process to the service process management module.

[0146] For example, if the current status of the B service process is stopped, which does not match its expected status of started, it can enter the service process startup process and send a request to start the service process to the service process management module.

[0147] S403. Call the running interface and call the status acquisition interface to monitor the service process status.

[0148] After receiving the request to start the service process, the service process management module can call the running interface of the customized executor to start the service process and can also call the status acquisition interface to monitor the service process status.

[0149] For example, after receiving the request to start the service, the service process management module can call the running interface of the customized executor to start the B service process and can also call the status acquisition interface to monitor the status of the B service process.

[0150] S404. After successful startup, set the status of the corresponding service process to started.

[0151] After the service process is successfully started, the service process management module can set the status of the current service process to started and send it to the service status management module, and trigger the service process dependency monitoring of the service status management module again, then it can monitor that the service process it depends on has been started.

[0152] For example, after the B service process is successfully started, the service process management module can set the status of the current B service process to started and send it to the service status management module, and trigger the service process dependency monitoring of the service status management module again, then it can monitor that the B service process on which the C service process depends has been successfully started.

[0153] S405. When there is a change in the status of a service process, repeat steps S401 - S404 until all service processes are in the expected status.

[0154] When it is detected that the status of the service processes included in the service has changed, steps S401 - S404 can be repeated until all service processes are in the expected status, which indicates that the service has been started.

[0155] For example, if the service status management module detects that the B service process on which the C service process depends has been started, the expected status of the C service process can be modified to started, and steps S401 - S404 can be repeated to complete the start of the C service process.

[0156] In the embodiment of the present application, the service status management module can calculate the service processes that should be started based on the status of various service processes it manages. If the current status of a service process does not match its expected status, the service process startup process can be entered, and a request to start the service process can be sent to the service process management module. After receiving the request to start the service process, the service process management module can call the running interface of the customized executor to start the service process. At the same time, it can also call the status acquisition interface to monitor the status of the service process. When the service process is successfully started, the status of the corresponding service process can be set to started and sent to the service status management module until all service processes are in the expected status, completing the service startup process. During the process of starting the service, based on the service dependency information included in the service deployment configuration information, the startup of service processes can be completed in sequence, automatically scheduling and executing various service processes, and improving the service deployment efficiency.

[0157] Figure 9 This is a schematic flowchart of Embodiment 3 of a service scheduling method provided by the embodiment of the present application. Based on any of the above embodiments, after performing initialization, startup operation, and status acquisition operation on the service, the service can also be stopped or deleted. Please refer to Figure 9 , the method includes:

[0158] S501. In response to the user's second operation, obtain a service stop command or a service deletion command for the service.

[0159] Based on business requirements, when it is necessary to maintain or take offline the service deployed in the runtime environment, the user can perform a stop or delete operation on the service. The management end can obtain a service stop command for the service in response to the user's service stop operation, or can obtain a service deletion command for the service in response to the user's deletion operation.

[0160] For example, the management terminal can obtain the service stop command 1 for Service 1 in response to the user's service stop operation.

[0161] S502. Send the service stop command or the service deletion command to the working terminal corresponding to the service.

[0162] After obtaining the service stop command or the service deletion command of the service, the management terminal can send the obtained service stop command or service deletion command to the corresponding working terminal.

[0163] For example, after obtaining the service stop command 1 for Service 1, the management terminal can send the obtained service stop command 1 to the corresponding working terminal 1.

[0164] S503. Call the executor to stop the service according to the service stop command, or call the executor to delete the service according to the service deletion command.

[0165] After receiving the service stop command or the service deletion command sent by the management terminal, the working terminal can call the executor of the working terminal to stop the service according to the service stop command, or call the executor of the working terminal to delete the service according to the service deletion command. The executor is also used to perform the stop or deletion operation on the service.

[0166] For example, after receiving the service stop command 1 sent by the management terminal, working terminal 1 can call the executor of the working terminal to stop Service 1 according to the service stop command 1.

[0167] In the embodiment of the present application, the management terminal obtains the service stop command or the service deletion command of the service in response to the user's second operation, and sends the service stop command or the service deletion command to the working terminal corresponding to the service. After receiving the service stop command or the service deletion command sent by the management terminal, the working terminal can call the executor to stop the service according to the service stop command, or call the executor to delete the service according to the service deletion command. During the process of stopping or deleting the service, different runtime environments can complete the stop or deletion of the service through the service stop command or the service deletion command obtained from the management terminal, without the user having to master the information of the runtime environment in advance, greatly improving the automation degree of the service during operation.

[0168] In a specific implementation manner, when the user needs to maintain or take offline the service, the service can be stopped or deleted. Specifically, the specific execution process of the service stop or deletion can be described by stopping or deleting the service process included in the service.

[0169] Figure 10 It is a schematic diagram of a service stop and deletion process provided by the embodiment of the present application. Please refer to Figure 10 , and this process includes:

[0170] S601. Send a service stop or deletion command.

[0171] S602. Set the desired state of the service in the configuration to stopped.

[0172] After the management terminal receives the service stop or deletion command issued by the user, the configuration preprocessing module can set the desired state of the corresponding service process in the service status management module to stopped.

[0173] S6021. If it is a deletion command, also send a service deletion command.

[0174] After the management terminal receives the deletion command issued by the user, the configuration preprocessing module can set the desired state of the corresponding service process in the service status management module to stopped and also send a service deletion command.

[0175] S603. Monitor that the service process status does not meet the expectation.

[0176] When it is monitored during the service process status tuning of the service status management module that a service process expected to be stopped is still in the started state, then S604 can be executed.

[0177] S604. Stop the service process.

[0178] The service status management module can send a service process stop command to the service process management module.

[0179] S605. Call the stop interface to stop the service process.

[0180] After the service process management module receives the service process stop command issued by the service status management module, it can call the service stop interface of the customized executor to stop the service process and can also call the status acquisition interface to monitor the service process status.

[0181] S606. Monitor that the service process has stopped.

[0182] After the service process stops, the service process management module can monitor that the service process has stopped.

[0183] S607. Monitor that the service process has stopped and set the status of the corresponding service process to stopped.

[0184] After the service process management module monitors that the service process has stopped, it can send the status of the stopped service process to the service status management module.

[0185] S608. When there is a change in the service process status, repeat steps S603 - S607 until all service processes are in the expected state.

[0186] By repeatedly executing steps S603 to S607 for the service processes included in the service until all service processes meet the expected status, that is, all service processes that should be stopped have stopped, the service stop process ends. If it is necessary to start the service processes again later, the expected status of all service processes can be restored, and the service processes can be gradually restored according to the service process start process.

[0187] S609. All service processes have stopped, and a command to delete the service processes is issued.

[0188] If the service deletion command is issued in step S601, step S6021 can be executed while executing step S602. In addition, after all stop processes are completed, that is, after the status of the corresponding service processes managed is set to stopped, the service status management module can issue a command to delete the service processes to the service process management module.

[0189] S610. Call the deletion interface to delete the service processes.

[0190] After receiving the command to delete the service processes issued by the service status management module, the service process management module can call the service deletion interface of the customized executor to delete the service processes.

[0191] S611. Monitor that the service processes have been deleted and delete the configuration information.

[0192] When the service process management module monitors that the service processes have been deleted, it can delete all files and parameters generated during initialization.

[0193] S612. The deletion of the service processes is completed.

[0194] After the service process management module deletes all files and parameters generated during initialization, it can report the status that the service processes have been deleted to the service status management module.

[0195] S613. Delete the information related to the service processes, stop monitoring the status of the service processes, and the service deletion is completed.

[0196] After all service processes included in the service are deleted, the service status management module can stop all monitoring and tuning processes related to the service and delete the stored service-related information, and the service deletion is completed.

[0197] It should be noted that steps S601 to S608 are the service process stop process. After all service processes included in the service stop, the service stops; steps S601 to S613, as well as step S6021, are the service process deletion process. After all service processes included in the service are deleted, the service is deleted.

[0198] In an embodiment of the present application, the management terminal can obtain a service stop or deletion command issued by a user, and send the service stop command or the service deletion command to the corresponding worker terminal of the service. After receiving the service stop command or the service deletion command sent by the management terminal, the worker terminal can call an executor to stop the service according to the service stop command, or call an executor to delete the service according to the service deletion command. During the process of stopping or deleting the service, different runtime environments can obtain the service stop command from the management terminal, and complete the service stop by sequentially stopping all service processes included in the service; they can obtain the service deletion command from the management terminal, and after the stop processes of all service processes are completed, delete all service processes included in the service to complete the service deletion. This enables automated scheduling and execution of the stop or deletion of various service processes according to the deployment sequence of the service processes in the service, greatly improving the automation level of the service during operation.

[0199] In an alternative embodiment, when the service exits abnormally due to its own reasons or external reasons, service exception recovery can also be performed. Specifically, the specific execution process of service exception recovery can be described through the exception recovery of the service processes included in the service.

[0200] Figure 11 It is a schematic diagram of a service exception recovery process provided by an embodiment of the present application. Please refer to Figure 11 and this process includes:

[0201] S701. Detect that a service process has an exception.

[0202] When the service has an exception, the service process management module can detect the event of abnormal stop of the service process through the interface for obtaining the status of the customized executor.

[0203] S702. Update the service process status to stopped.

[0204] The service process management module can set the current service process status to stopped and send the stopped service status to the service status management module.

[0205] S703. The service process status changes, and it is detected that the status of the abnormal service process does not meet the expectation.

[0206] When the service status management module detects that the status of the service process sent by the service process management module does not meet the expected status, it can execute step S704.

[0207] S704. Issue a command to start the service process.

[0208] S705. Call the running interface to start the service process.

[0209] After receiving the command to start the service process, the service process management module can restart the abnormal service process through a customized executor.

[0210] S706. When it is detected that the service process has started, set the corresponding service process status to started.

[0211] When the restart of the abnormal service process is completed, the service process management module can detect that the service process has started and can set the status of the corresponding service process under management to started.

[0212] S707. When there is a change in the service process status, repeat steps S701 to S706 until all service processes are in the expected status.

[0213] When it is detected that there is a change in the service process status included in the service, steps S701 to S706 can be repeated until all abnormal service processes have met the expected status, which means that the abnormal service has been restored.

[0214] In the embodiment of the present application, when the service process management module detects that the service process is abnormal, it can update the service process status to stopped and send the stopped service status to the service status management module; when the service status management module detects that the status of the abnormal service process does not meet the expected status, it issues a command to start the service process; after receiving the command to start the service process, the service process management module can restart the abnormal service process through a customized executor until all service processes are in the expected status. In the above process, if the service is abnormal, the abnormal situation can be automatically handled to ensure that the service running status meets the expectation, improve the adaptability and automation degree of service deployment, and improve the service deployment efficiency.

[0215] Figure 12 This is a schematic structural diagram of Embodiment 1 of a service scheduling device provided by an embodiment of the present application. Please refer to Figure 12 , the service scheduling device 10 includes:

[0216] An acquisition module 11, configured to acquire service deployment configuration information in response to a first operation of a user, where the service deployment configuration information includes service start information, service dependency information, and service deployment information;

[0217] A sending module 12, configured to send a deployment command message to a working end based on the dependency relationship in the service dependency information, where the service start information is carried in the deployment command message.

[0218] The service scheduling device provided by the embodiment of the present application can execute the technical solutions shown in the above embodiments, and its implementation principles and beneficial effects are similar and will not be elaborated here.

[0219] In a possible implementation manner, the obtaining module 11 is specifically configured to:

[0220] Receive the service deployment configuration information input by the user, where the first operation is an input operation;

[0221] Or,

[0222] In response to the user's selection operation on a preset deployment template, obtain the service deployment configuration information, where the deployment template includes: multiple services, the startup information and deployment information of each service, and the dependency information between processes; the first operation is a selection operation.

[0223] In a possible implementation manner, the service startup information includes at least one service, the startup parameters, runtime environment, and configuration file of each service;

[0224] The service dependency information includes the dependency relationship between service processes;

[0225] The service deployment information includes the working end and the number of deployment replicas for each service deployment;

[0226] Correspondingly, the sending module 12 is specifically configured to:

[0227] For each service, send a deployment command message to the working end corresponding to the service in the service deployment message, where the deployment command message includes the startup parameters, runtime environment, and configuration file of the service.

[0228] In a possible implementation manner, the obtaining module 11 is further configured to, in response to the user's second operation, obtain a service stop command or a service deletion command for the service, where the second operation is a service stop operation or a service deletion operation;

[0229] The sending module 12 is further configured to send the service stop command or the service deletion command to the working end corresponding to the service.

[0230] The service scheduling device provided in the embodiments of the present application can execute the technical solutions shown in the above embodiments, and its implementation principles and beneficial effects are similar and will not be elaborated here.

[0231] Figure 13 It is a schematic structural diagram of the second embodiment of a service scheduling device provided in the embodiments of the present application. Please refer to Figure 13 The service scheduling device 20 includes:

[0232] A receiving module 21, configured to receive a deployment command message sent by a management end, where the deployment command message includes the startup parameters, runtime environment, and configuration file of a service;

[0233] A processing module 22, configured to call an actuator at the working end, and deploy the service to the runtime environment according to the deployment command message; the actuator is configured to perform initialization, start-up operation, and status acquisition operation on the service according to the start parameters and the configuration file.

[0234] The service scheduling device provided by the embodiment of the present application can execute the technical solutions shown in the above embodiments, and the implementation principles and beneficial effects are similar and will not be elaborated here.

[0235] In a possible implementation manner, the receiving module 21 is further configured to receive the service stop command or the service deletion command sent by the management end;

[0236] The processing module 22 is further configured to call the actuator to stop the service according to the service stop command, or call the actuator to delete the service according to the service deletion command; the actuator is further configured to perform stop or deletion operation on the service.

[0237] In a possible implementation manner, the receiving module 21 is further configured to perform permission verification on the management end and verify the data structure of the deployment command message;

[0238] Correspondingly, the processing module 22 is specifically configured to:

[0239] After both the permission of the management end and the data structure of the deployment command message pass the verification, call the actuator at the working end, and deploy the service to the runtime environment according to the deployment command message.

[0240] The service scheduling device provided by the embodiment of the present application can execute the technical solutions shown in the above embodiments, and the implementation principles and beneficial effects are similar and will not be elaborated here.

[0241] Figure 14 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Please refer to Figure 14 , the electronic device 30 may include a processor 31, a memory 32, and a communication interface 34. Exemplarily, the processor 31, the memory 32, and the communication interface 34 are interconnected through a bus 33.

[0242] The memory 32 stores computer execution instructions;

[0243] The processor 31 executes the computer execution instructions stored in the memory 32, so that the processor 31 executes the service scheduling method provided in the above method embodiment.

[0244] The electronic device provided in the embodiments of the present application can be the management terminal or the working terminal described in the above embodiments, and can execute the technical solutions shown in the above method embodiments. The implementation principles and beneficial effects are similar, and will not be elaborated here.

[0245] Correspondingly, the embodiments of the present application provide a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the service scheduling method provided in any of the above method embodiments.

[0246] Correspondingly, the embodiments of the present application can also provide a computer program product, including a computer program. When the computer program is executed by a processor, the service scheduling method provided in any of the above method embodiments can be implemented.

[0247] All or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a readable memory. When the program is executed, it executes the steps including the above method embodiments; and the foregoing memory (storage medium) includes: read-only memory (abbreviation: ROM), random access memory (abbreviation: RAM), flash memory, hard disk, solid state drive, magnetic tape, floppy disk, optical disc, and any combination thereof.

[0248] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processing unit, or other programmable data processing devices to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing devices generate a device for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0249] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions in the process Figure 1 one process or multiple processes and / or blocks Figure 1The functions specified in one or more boxes.

[0250] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide for implementing the steps of the functions specified in one Figure 1 process or multiple processes and / or boxes Figure 1 or more boxes.

[0251] In the above embodiments, the descriptions of the various embodiments have their own emphases. For parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as falling within the scope described in this specification.

[0252] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include known common knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0253] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A service scheduling method, characterized in that, Applied to the management side, the method includes: In response to a first operation of the user, obtain service deployment configuration information, which includes service startup information, service dependency information, and service deployment information; Based on the dependency relationships in the service dependency information, send a deployment command message to the worker side according to the service deployment information, and the service startup information is carried in the deployment command message.

2. The method according to claim 1, characterized in that, The obtaining service deployment configuration information in response to the first operation of the user includes: Receive the service deployment configuration information input by the user, and the first operation is an input operation; Or, In response to a selection operation of the user on a preset deployment template, obtain the service deployment configuration information, and the deployment template includes: multiple services, startup information and deployment information of each service, and dependency information between processes; the first operation is a selection operation.

3. The method according to claim 1 or 2, characterized in that, The service startup information includes at least one service, startup parameters, runtime environment, and configuration file of each service; The service dependency information includes dependency relationships between service processes; The service deployment information includes the worker side to which each service is deployed and the number of deployment replicas; Correspondingly, the sending a deployment command message to the worker side according to the service deployment information, and the service startup information is carried in the deployment command message, includes: For each service, send a deployment command message to the worker side corresponding to the service in the service deployment message, and the deployment command message includes the startup parameters, runtime environment, and configuration file of the service.

4. The method according to claim 3, characterized in that, The method further includes: In response to a second operation of the user, obtain a service stop command or a service deletion command for the service, and the second operation is a service stop operation or a service deletion operation; Send the service stop command or the service deletion command to the worker side corresponding to the service.

5. A service scheduling method, characterized in that, Applied to the worker side, the method includes: Receive a deployment command message sent by the management side, and the deployment command message includes the startup parameters, runtime environment, and configuration file of the service; Call the executor of the worker side, and deploy the service to the runtime environment according to the deployment command message; the executor is used to perform initialization, startup operation, and status acquisition operation on the service according to the startup parameters and configuration file.

6. The method according to claim 5, characterized in that, The method further includes: Receive the service stop command or the service deletion command sent by the management side; According to the service stop command, call the executor to stop the service, or according to the service deletion command, call the executor to delete the service; the executor is also used to perform stop or deletion operation on the service.

7. The method according to claim 5 or 6, characterized in that, After receiving the deployment command message sent by the management side, the method further includes: Perform permission verification on the management side and verify the data structure of the deployment command message; Correspondingly, the calling the executor of the worker side and deploying the service to the runtime environment according to the deployment command message includes: After passing the verification of both the permissions of the management terminal and the data structure of the deployment command message, call the executor of the worker terminal, and deploy the service to the runtime environment according to the deployment command message.

8. A service scheduling device, characterized in that, The device includes: An acquisition module, configured to acquire service deployment configuration information in response to a first operation of a user, where the service deployment configuration information includes service startup information, service dependency information, and service deployment information; A sending module, configured to send a deployment command message to the worker terminal based on the dependency relationship in the service dependency information, where the deployment command message carries the service startup information.

9. A service scheduling device, characterized in that, The device includes: A receiving module, configured to receive a deployment command message sent by the management terminal, where the deployment command message includes startup parameters of the service, a runtime environment, and a configuration file; A processing module, configured to call the executor of the worker terminal and deploy the service to the runtime environment according to the deployment command message; the executor is configured to perform initialization, startup operation, and status acquisition operation on the service according to the startup parameters and the configuration file.

10. An electronic device, characterized in that,Includes: A processor, a memory, and a communication interface; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory, so that the processor executes the service scheduling method according to any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that, Computer execution instructions are stored in the computer-readable storage medium, and when the computer execution instructions are executed by the processor, they are used to implement the service scheduling method according to any one of claims 1 to 7.

Images