A cross-platform service scheduling method and system

Abstract

The application discloses a cross-platform service scheduling method and system, and the method comprises the following steps: S1, configuration instance: matching the same cloud service environment information, the corresponding service information and the entity information to generate an application instance, and distributing the application instance to the corresponding cloud service environment; S2, creating and running the application instance: creating the corresponding service scheduler instance for the application instance respectively, and uniformly scheduling the service scheduler instance to run the service in the application instance; S3, listening to the application instance: the service scheduler listens to the information of the application instance through a heartbeat mechanism; S4, automatic repair: collecting the state of the service scheduler instance and reporting, offline the service scheduler instance with an abnormal running state, and re-creating a new service scheduler instance to repair the fault. The application realizes the centralized management and unified scheduling of cross-platform applications and services, reduces the hardware cost and maintenance complexity, and improves the stability and expansibility of service scheduling.

Description

Technical Field

[0001] The present invention relates to the technical field of service scheduling, and in particular to a cross-platform service scheduling method and system. Background Art

[0002] The continuous emergence of cloud service providers has simplified application deployment, but it has also brought about many new problems. The most significant issue is that services within a single application often need to be deployed across different cloud service platforms due to varying business requirements. The existing solution is to deploy a set of services on each cloud service platform. However, with the increasing number of applications and their services, and the increasing complexity of business, deploying a separate service scheduling system for each application on a cloud service platform is extremely costly. Furthermore, the service capabilities offered by each cloud service platform vary, making it difficult to centrally manage and uniformly schedule these services, making stable operation difficult and increasing the cost and difficulty of deployment and maintenance. Summary of the Invention

[0003] To solve the above problems, the present invention provides a cross-platform service scheduling method and system to solve the problems of the current service scheduling such as lack of centralized management, high maintenance cost and difficulty in maintenance.

[0004] The present invention adopts the following technical solutions:

[0005] A cross-platform service scheduling method, the method comprising the following steps:

[0006] S1. Instance configuration: Match the same cloud service environment information with its corresponding service information and entity information to generate an application instance, and assign the application instance to the corresponding cloud service environment. The service information and entity information in the application instance form a service group and an entity group, respectively.

[0007] S2. Create and run application instances: Create corresponding service scheduler instances for the application instances respectively, and use the service scheduler to uniformly schedule the service scheduler instances to run the services in the corresponding application instances.

[0008] Furthermore, it also includes step S3, monitoring application instances: the service scheduler monitors the information of the application instance through the heartbeat mechanism. When the service group or entity group in the application instance changes, a new service scheduler instance is created for it. When the service group or entity group in the application instance is removed, the corresponding service scheduler instance stops responding.

[0009] Furthermore, it also includes the steps: S4, automatic repair: the service monitor collects the status of the service scheduler instance and reports it to the API interface, the API interface takes the service scheduler instance offline with abnormal running status, and recreates a new service scheduler instance to repair the fault.

[0010] Furthermore, step S1 is specifically as follows:

[0011] S11. The management and operation platform adds basic configuration parameters through the API interface. The basic configuration parameters include cloud service environment information, service information, and entity information.

[0012] S12. Matching the same cloud service environment information and its corresponding service information and entity information to generate an application instance, wherein the service information and entity information form a service group and an entity group, respectively, and the service information and entity information are paired in pairs to generate a service;

[0013] S13. Allocate the application instance to a corresponding cloud service environment under a cloud service platform according to the cloud service environment information.

[0014] Furthermore, step S2 is specifically as follows:

[0015] S21. Create a corresponding service scheduler instance for each application instance in the corresponding cloud service platform;

[0016] S22. The service scheduler obtains the application instance corresponding to the service scheduler instance through the API interface, and runs the service in the application instance, wherein when running the service in the application instance, the entity information is used as the context parameter of the service information.

[0017] A cross-platform service scheduling system, which is used to implement the above-mentioned cross-platform service scheduling method, includes a metadata database, a cloud service platform, an API interface, a service scheduler, a management and operation platform, and a service monitor;

[0018] The metadata database is used to provide basic configuration parameters and application examples;

[0019] The cloud service platform provides a cloud service environment and creates and executes corresponding service scheduler instances according to the application instances;

[0020] The API interface serves as a communication management interface between the management and operation platform and the metadata database and cloud service platform;

[0021] The service scheduler is used to schedule the service scheduler instance and trigger the addition and termination of the service scheduler instance;

[0022] The management and operation platform is used to visually manage the metadata database and view the status of the service scheduler instance;

[0023] The service monitor is used to collect the status of the corresponding service scheduler instance under the current cloud service platform and report it to the management and operation platform.

[0024] Furthermore, the basic configuration parameters include cloud service environment information, service information, and entity information; wherein, the same cloud service environment information and its corresponding service information and entity information are matched to generate an application instance, and the service information and entity information in the application instance constitute a service group and an entity group respectively.

[0025] Furthermore, a metadata management module and an application instance management module are set up in the management and operation platform, wherein the metadata management module manages the basic configuration parameters, service groups and entity groups in the metadata database through the API interface, and the application instance management module manages the service scheduler instance under the cloud service platform through the API interface.

[0026] Furthermore, the service monitor reports the status of the service scheduler instance through the API interface.

[0027] Furthermore, the service scheduler schedules the service scheduler instance and triggers the addition and termination of the service scheduler instance through the API interface.

[0028] After adopting the above technical solution, the present invention has the following advantages compared with the background technology:

[0029] 1. The present invention provides a cross-platform service scheduling method that can achieve unified scheduling of application services on different cloud service platforms, thereby realizing centralized management of cross-platform applications and their services. This eliminates the need to deploy separate service schedulers on each cloud service platform, reducing hardware costs and maintenance complexity.

[0030] 2. The present invention uniformly schedules application instances through a service scheduler, and monitors and provides feedback on the status of service scheduler instances through a service monitor, which helps relevant personnel to discover and solve problems in a timely manner. Services can be added or stopped at runtime without restarting the application to avoid service interruption, thereby improving the stability and scalability of service scheduling. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 Flow chart of the method of the present invention;

[0032] Figure 2 It is a configuration flow chart of an application example of the present invention;

[0033] Figure 3A schematic diagram is provided for the application example of the present invention;

[0034] Figure 4 Schematic diagram of the system structure of the present invention. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0036] Example

[0037] like Figure 1 As shown, a cross-platform service scheduling method includes the following steps:

[0038] S1. Instance configuration: Match the same cloud service environment information with its corresponding service information and entity information to generate an application instance, and assign the application instance to the corresponding cloud service environment. The service information and entity information in the application instance form a service group and an entity group, respectively.

[0039] Step S1 is specifically as follows:

[0040] S11. The management and operation platform adds basic configuration parameters through the API interface. The basic configuration parameters include cloud service environment information, service information, and entity information.

[0041] S12. Matching the same cloud service environment information and its corresponding service information and entity information to generate an application instance, wherein the service information and entity information form a service group and an entity group, respectively, and the service information and entity information are paired in pairs to generate a service;

[0042] S13. Allocate the application instance to a corresponding cloud service environment under a cloud service platform according to the cloud service environment information.

[0043] like Figure 2 As shown, service information A and service information B constitute service group A, entity A and entity B constitute entity group A, service group A, entity group A and cloud service environment information A constitute application instance A, then application instance A includes cloud service environment information A, service information A, service information B, entity A and entity B, and the service information and entity information in application instance A are paired and combined to form four services, namely service A-entity A, service A-entity B, service B-entity A and service B-entity B. These four services all correspond to the same cloud service environment information A, so application instance A is assigned to the corresponding cloud service environment A under the cloud service platform.

[0044] Similarly, service information C and service information D constitute service group B, entity C and entity D constitute entity group B, service group B, entity group B and cloud service environment information B constitute application instance B, then application instance B includes cloud service environment information B, service information C, service information D, entity C and entity D. By pairing the service information and entity information in application instance B, four services are formed, namely service C-entity C, service C-entity D, service D-entity C and service D-entity D. These four services correspond to the same cloud service environment information B, so the application instance B is assigned to the corresponding cloud service environment B under the cloud service platform.

[0045] Through step S1, different application instances of the same application can be deployed to different cloud service platforms according to different business requirements.

[0046] S2. Create and run application instances: Create corresponding service scheduler instances for the application instances respectively, and use the service scheduler to uniformly schedule the service scheduler instances to run the services in the corresponding application instances;

[0047] Step S2 is specifically as follows:

[0048] S21. Create a corresponding service scheduler instance for each application instance in the corresponding cloud service platform;

[0049] S22. The service scheduler obtains the application instance corresponding to the service scheduler instance through the API interface, and runs the service in the application instance, wherein when running the service in the application instance, the entity information is used as the context parameter of the service information.

[0050] like Figure 3 As shown, for the above-mentioned application instances A and B, service scheduler instances A and B are created for them respectively in the cloud service platform. Then the service scheduler obtains the application instance corresponding to the service scheduler instance A or B through the API interface and runs the service of the application instance.

[0051] Through step S2, the service scheduler can be used to uniformly schedule application instances in different cloud service platforms, thereby running corresponding services and realizing cross-platform service scheduling.

[0052] S3. Monitor application instances: The service scheduler monitors the information of the application instance through the heartbeat mechanism. When the service group or entity group in the application instance changes, a new service scheduler instance is created for it. When the service group or entity group in the application instance is removed, the corresponding service scheduler instance stops responding.

[0053] Specifically, it may include the change, addition or deletion of service information. For example: when the service information A in the service group A changes, it will affect the service corresponding to the service information A, that is, the application instance A has changed, then it is necessary to create a new service scheduler instance for the application instance. When service information E is added to the service group A, the corresponding service will be added (i.e., new service E-entity A and service E-entity B are added), and at this time it is necessary to create a new service scheduler for the application instance A. When the service group or entity group in the application instance is removed, the components of the application instance are incomplete, and it is necessary to stop responding to the corresponding service scheduler instance to prevent errors and interruptions. This step S3 implements the function of adding or stopping services at runtime. When a service is changed, added or deleted, the corresponding application will be automatically expanded or reduced, so there is no need to restart the application to avoid service interruption, so as to meet the needs of the service, improve the availability of the system, and improve the stability and scalability of service scheduling.

[0054] S4. Automatic Repair: The service monitor collects the status of the service scheduler instance and reports it to the API. The API takes down any abnormally running service scheduler instance and creates a new one to repair the problem. This step, through the service monitor's status monitoring and feedback, helps relevant personnel identify and resolve problems in a timely manner.

[0055] The second object of the present invention is to provide a cross-platform service scheduling system, which is used for the above-mentioned cross-platform service scheduling method, such as Figure 4 As shown, the system includes a metadata database, a cloud service platform, an API interface, a service scheduler, a management and operation platform, and a service monitor;

[0056] The metadata database is used to provide basic configuration parameters and application examples;

[0057] The cloud service platform provides a cloud service environment and creates and executes corresponding service scheduler instances according to the application instances;

[0058] The API interface serves as a communication management interface between the management and operation platform and the metadata database and cloud service platform;

[0059] The service scheduler is used to schedule the service scheduler instance and trigger the addition and termination of the service scheduler instance;

[0060] The management and operation platform is used to visually manage the metadata database and view the status of the service scheduler instance;

[0061] The service monitor is used to collect the status of the corresponding service scheduler instance under the current cloud service platform and report it to the management and operation platform.

[0062] The basic configuration parameters include cloud service environment information, service information, and entity information; wherein the same cloud service environment information and its corresponding service information and entity information are matched to generate an application instance, and the service information and entity information in the application instance constitute a service group and an entity group respectively.

[0063] A metadata management module and an application instance management module are set up in the management and operation platform, wherein the metadata management module manages the basic configuration parameters, service groups and entity groups in the metadata database through the API interface, and the application instance management module manages the service scheduler instance under the cloud service platform through the API interface.

[0064] The service monitor reports the status of the service scheduler instance through the API interface.

[0065] The service scheduler schedules the service scheduler instance and triggers the addition and termination of the service scheduler instance through the API interface.

[0066] The specific operation process of the above-mentioned cross-platform service scheduling system has been described in detail in the above-mentioned method and will not be repeated here.

[0067] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A cross-platform service scheduling method, characterized by: The method comprises the following steps: S1. Instance configuration: Match the same cloud service environment information with its corresponding service information and entity information to generate an application instance, and assign the application instance to the corresponding cloud service environment. The service information and entity information in the application instance form a service group and an entity group, respectively. S2. Create and run application instances: Create corresponding service scheduler instances for the application instances respectively, and use the service scheduler to uniformly schedule the service scheduler instances to run the services in the corresponding application instances; S3. Monitoring application instances: The service scheduler monitors the information of the application instance through the heartbeat mechanism. When the service group or entity group in the application instance changes, a new service scheduler instance is created for it. When the service group or entity group in the application instance is removed, the corresponding service scheduler instance stops responding. S4. Automatic repair: The service monitor collects the status of the service scheduler instance and reports it to the API interface. The API interface takes the service scheduler instance offline if it is in an abnormal state and creates a new service. Step S1 is specifically as follows: S11. The management and operation platform adds basic configuration parameters through the API interface. The basic configuration parameters include cloud service environment information, service information, and entity information. S12. Matching the same cloud service environment information and its corresponding service information and entity information to generate an application instance, wherein the service information and entity information form a service group and an entity group, respectively, and the service information and entity information are paired in pairs to generate a service; S13. Allocating the application instance to a corresponding cloud service environment under the cloud service platform according to the cloud service environment information; Step S2 is specifically as follows: S21. Create a corresponding service scheduler instance for each application instance in the corresponding cloud service platform; S22. The service scheduler obtains the application instance corresponding to the service scheduler instance through the API interface, and runs the service in the application instance, wherein when running the service in the application instance, the entity information is used as the context parameter of the service information.

2. A cross-platform service scheduling system, characterized by: The system is used to implement the cross-platform service scheduling method according to claim 1, and the system includes a metadata database, a cloud service platform, an API interface, a service scheduler, a management and operation platform, and a service monitor; The metadata database is used to provide basic configuration parameters and application examples; The cloud service platform provides a cloud service environment and creates and executes corresponding service scheduler instances according to the application instances; The API interface serves as a communication management interface between the management and operation platform and the metadata database and cloud service platform; The service scheduler is used to schedule the service scheduler instance and trigger the addition and termination of the service scheduler instance; The management and operation platform is used to visually manage the metadata database and view the status of the service scheduler instance; The service monitor is used to collect the status of the corresponding service scheduler instance under the current cloud service platform and report it to the management and operation platform.

3. A cross-platform service scheduling system according to claim 2, characterized in that: The basic configuration parameters include cloud service environment information, service information, and entity information; wherein the same cloud service environment information and its corresponding service information and entity information are matched to generate an application instance, and the service information and entity information in the application instance constitute a service group and an entity group respectively.

4. A cross-platform service scheduling system according to claim 3, characterized in that: A metadata management module and an application instance management module are set up in the management and operation platform, wherein the metadata management module manages the basic configuration parameters, service groups and entity groups in the metadata database through the API interface, and the application instance management module manages the service scheduler instance under the cloud service platform through the API interface.

5. A cross-platform service scheduling system according to claim 4, characterized in that: The service monitor reports the status of the service scheduler instance through the API interface.

6. A cross-platform service scheduling system according to claim 5, characterized in that: The service scheduler schedules the service scheduler instance and triggers the addition and termination of the service scheduler instance through the API interface.

Images