Method and device for rapid orchestration of heterogeneous applications for federated computing
By building a distributed application orchestration support environment in the federated computing cluster, using the collaborative scheduling functions of the main control site and sub-sites, the problem of low orchestration efficiency of the federated computing cluster is solved, rapid orchestration and deployment are achieved, and collaborative operation of multiple sub-sites is supported. , improves orchestration efficiency and fault tolerance.
Patent Information
- Application Number
- CN202210248362.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-14
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-03-14
AI Technical Summary
The lack of fast orchestration support for federated computing clusters has resulted in too long application orchestration processes, reducing the timeliness of testing and deployment, and existing container orchestration clusters cannot support distributed collaborative application running orchestration for multiple subsites.
Build a distributed application orchestration support environment in a federated computing cluster, including main control sites, sub-sites and basic services, generate heterogeneous application orchestration plans through the main control site, and use global task scheduling and local task scheduling functions for asynchronous processing , realize the rapid orchestration and deployment of applications.
It improves application orchestration efficiency, supports the operation of distributed collaborative applications in multiple sub-sites, improves orchestration efficiency and has good fault tolerance.
Smart Images

Figure CN114756339B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network communication technology, and in particular to a method for rapidly arranging heterogeneous applications for federated computing, a computer device, and a storage medium. Background Art
[0002] With the development of network communication technology, federated computing technology has emerged. Federated computing is a distributed computing organization model formed by autonomous and geographically distributed sub-sites. Each sub-site joins the federated computing cluster in an equal and mutually beneficial cooperation manner, providing remote access to virtual computing resources and storage and network resources through standardized API interfaces. Federated computing tasks involve a large number of sub-sites, and there are many types of applications that need to be started. The installation and configuration of each application are complex, and the processing flow of the applications started at each sub-site has a time sequence relationship. However, the federated computing cluster lacks fast orchestration support, requiring users to remotely connect to each node of the cluster one by one, and then upload and install the deployment task program one by one through remote access protocols such as SSH and start the test task, resulting in a long application orchestration process, which reduces the timeliness of testing and deployment.
[0003] However, the current container orchestration cluster is mainly aimed at a single site and cannot support the distributed and collaborative application operation orchestration of multiple sub-sites. The application orchestration process is too long and the orchestration efficiency is low. Summary of the invention
[0004] Based on this, it is necessary to provide a method, computer device and storage medium for fast orchestration of heterogeneous applications for federated computing that can improve the efficiency of application orchestration in order to address the above technical problems.
[0005] A method for fast orchestration of heterogeneous applications for federated computing, which builds a distributed application orchestration support environment in a federated computing cluster; the distributed application orchestration support environment includes a master control site, a sub-site, and basic services; the master control site includes an application orchestration solution generation function, a global task scheduling function, and an application resource management function; the sub-site includes a local task scheduling function, a task execution function, and an application running function; the basic service is used to provide unified identity authentication, access services, and a message bus for the master site and the sub-site;
[0006] The method includes: generating a heterogeneous application program orchestration plan according to an application program orchestration plan generating function in a distributed application program orchestration support environment through a master control site; performing global task scheduling on the heterogeneous application program orchestration plan according to a global task scheduling function in a distributed application program orchestration support environment through a master control site; and starting a local task scheduling function to perform local task scheduling after receiving a plan message from the master control site in a distributed application program orchestration support environment through a sub-site and a basic service, and performing task execution, application program operation function deployment, and application program startup according to a task execution function and an application program operation function.
[0007] In one embodiment, a heterogeneous application program orchestration solution is generated by a master control site according to an application program orchestration solution generation function in a distributed application program orchestration support environment, including:
[0008] The master site uses a directed acyclic graph in the distributed application orchestration support environment to describe the application installation and startup configuration and application runtime sequence that need to be deployed at each sub-site, and generate a heterogeneous application orchestration solution.
[0009] In one embodiment, a heterogeneous application orchestration solution is generated by using a directed acyclic graph to describe the application installation and startup configuration and the application runtime sequence to be deployed at each sub-site in a distributed application orchestration support environment, including:
[0010] The master control site uses a directed acyclic graph to model in a distributed application program orchestration support environment to obtain a workflow structure; the vertices of the directed acyclic graph are the vertices of the workflow structure; the edges of the directed acyclic graph are the edges of the workflow structure;
[0011] Generate heterogeneous application orchestration solutions based on the vertices and edges of the workflow structure; the vertices of the workflow structure include root vertices and non-root vertices; the root vertex represents the process of starting the application orchestration, the non-root vertices of the workflow represent the running instances of the application, and each vertex of the workflow corresponds to a metadata array; the metadata array is used to record the installation directory, running parameter configuration, output result directory, start time, end time and other configuration and running key parameters of the corresponding application; the edges of the workflow structure reflect the order of application running, and a directed edge can be added between any two vertices, and the orchestration order of the source vertex of the edge must precede the orchestration order of the destination vertex; each edge of the workflow structure corresponds to a metadata array, which is used to record the source vertex and destination vertex of the edge of the workflow structure.
[0012] In one of the embodiments, the global task scheduling function includes global task configuration, global task startup, global task monitoring and global task clearing.
[0013] In one embodiment, performing global task scheduling on heterogeneous application program orchestration solutions according to a global task scheduling function in a distributed application program orchestration support environment through a master control site includes:
[0014] The master site configures the application orchestration scheme for each subsite in the distributed application orchestration support environment, and starts the local task scheduling function of each subsite in batches to execute their respective application orchestration schemes. Each subsite periodically reports the vertex completion ratio of local task scheduling. After all subsites complete their respective application orchestrations, the global task scheduling ends and the master site releases the application storage resources of each subsite.
[0015] In one of the embodiments, the local task scheduling function includes scheduler instance generation, scheduler timing calculation and scheduler task execution; scheduler task execution includes task reading, task parsing, task execution and task completion.
[0016] In one of the embodiments, the task execution function includes retrieving application instance metadata and starting to execute the application instance; the application running function includes pulling application executable code and updating the application instance status.
[0017] In one embodiment, the basic service includes a message bus function and a unified registration function; the message bus function is for the main control site and the sub-site to access the same message bus subscription topic through the distributed message middleware, publish messages to the subscribed topic, and asynchronously receive messages.
[0018] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:
[0019] Construct a distributed application orchestration support environment in the federated computing cluster; the distributed application orchestration support environment includes a master site, sub-sites, and basic services; the master site includes application orchestration solution generation functions, global task scheduling functions, and application resource management functions; the sub-sites include local task scheduling, task execution functions, and application running functions; the basic services are used to provide unified identity authentication, access services, and message buses for the master site and sub-sites;
[0020] Generate heterogeneous application orchestration plans in a distributed application orchestration support environment according to the application orchestration plan generation function through the master site; perform global task scheduling on heterogeneous application orchestration plans in a distributed application orchestration support environment according to the global task scheduling function through the master site; after receiving the plan message from the master site in the distributed application orchestration support environment, the sub-sites and basic services start the local task scheduling function to perform local task scheduling and perform task execution, application running function deployment and application startup according to the task execution function and application running function.
[0021] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:
[0022] Construct a distributed application orchestration support environment in the federated computing cluster; the distributed application orchestration support environment includes a master site, sub-sites, and basic services; the master site includes application orchestration solution generation functions, global task scheduling functions, and application resource management functions; the sub-sites include local task scheduling, task execution functions, and application running functions; the basic services are used to provide unified identity authentication, access services, and message buses for the master site and sub-sites;
[0023] Generate heterogeneous application orchestration plans in a distributed application orchestration support environment according to the application orchestration plan generation function through the master site; perform global task scheduling on heterogeneous application orchestration plans in a distributed application orchestration support environment according to the global task scheduling function through the master site; after receiving the plan message from the master site in the distributed application orchestration support environment, the sub-sites and basic services start the local task scheduling function to perform local task scheduling and perform task execution, application running function deployment and application startup according to the task execution function and application running function.
[0024] The above-mentioned method, computer device and storage medium for rapid orchestration of heterogeneous applications for federated computing first build a distributed application orchestration support environment in a federated computing cluster; the distributed application orchestration support environment includes a master control site, a sub-site and basic services; the master control site includes an application orchestration plan generation function, a global task scheduling function and an application resource management function; the sub-site includes a local task scheduling, a task execution function and an application running function; the basic services are used to provide unified identity authentication, access services and message buses for the master site and the sub-sites; a heterogeneous application orchestration plan is generated in the distributed application orchestration support environment according to the application orchestration plan generation function by the master control site; the heterogeneous application orchestration plan is orchestrated in the distributed application orchestration support environment according to the global task scheduling function by the master control site. The present invention constructs a distributed application orchestration support environment, sets a master site, a sub-site and basic services in the distributed application orchestration support environment to perform orchestration and scheduling of heterogeneous applications, improves the response speed of sub-site scheduling through an asynchronous processing flow that separates task scheduling and application deployment, has good fault tolerance for application exceptions, realizes the deployment and startup of distributed collaborative applications of each sub-site, supports the operation orchestration of distributed collaborative applications of multiple sub-sites, and improves the orchestration efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 A flowchart of a method for rapidly arranging heterogeneous applications for federated computing in one embodiment is provided;
[0026] Figure 2 A schematic diagram of the structure of a distributed application program orchestration support environment in one embodiment;
[0027] Figure 3 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0028] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0029] In one embodiment, Figure 1 As shown in the figure, a method for fast orchestration of heterogeneous applications for federated computing is provided. Figure 2As shown, a distributed application orchestration support environment is built in a federated computing cluster; the distributed application orchestration support environment includes a master site, a sub-site, and basic services; the master site includes an application orchestration solution generation function, a global task scheduling function, and an application resource management function; the sub-site includes a local task scheduling, a task execution function, and an application running function; the basic service is used to provide unified identity authentication, access services, and a message bus for the master site and the sub-site, including the following steps:
[0030] Step 102, generating a heterogeneous application program orchestration solution in a distributed application program orchestration support environment according to the application program orchestration solution generation function through the master control site.
[0031] The application orchestration scheme generation function refers to obtaining the workflow structure through directed acyclic graph modeling. An application orchestration scheme corresponds to a workflow structure, and the metadata model is encoded and stored in the JSON message format. The workflow structure includes vertices and edges; the root vertex of the workflow represents the process of starting the application orchestration, and the non-root vertex of the workflow represents the running instance of an application. Each vertex of the workflow corresponds to a metadata array, which records the configuration and running key parameters of the corresponding application, such as the installation directory, running parameter configuration, output result directory, start time, and end time. The edges of the workflow reflect the order of application operation. A directed edge can be added between any two vertices, and the orchestration order of the source vertex of the edge must precede the orchestration order of the destination vertex. A vertex can have any number of directed edges, and these edges can run concurrently. Each edge of the workflow corresponds to a metadata array, which records the source vertex and destination vertex of the edge.
[0032] Step 104 , performing global task scheduling on the heterogeneous application program orchestration solution in the distributed application program orchestration support environment according to the global task scheduling function through the master control site.
[0033] The global task scheduling function refers to the master site configuring the application orchestration plan for each sub-site, batch starting each sub-site to execute their own application orchestration plan through local task scheduling, and each sub-site regularly reporting the vertex completion ratio of local task scheduling. After all sub-sites complete their own application orchestration, the global task scheduling ends and the master site releases the application storage resources of each sub-site.
[0034] Step 106, after receiving the solution message from the master site in the distributed application orchestration support environment through the sub-site and basic services, the local task scheduling function is started to perform local task scheduling and perform task execution, application running function deployment and application startup according to the task execution function and application running function.
[0035] The local task scheduling function refers to scheduling and running application orchestration plans at sub-sites. After receiving the plan message from the main control site through the basic service, the sub-site parses and calls the local task scheduling function and calls the task execution function to execute the task, and calls the application running function to deploy and run the application.
[0036] In the above-mentioned method for rapid orchestration of heterogeneous applications for federated computing, a distributed application orchestration support environment is first constructed in the federated computing cluster; the distributed application orchestration support environment includes a master control site, a sub-site, and basic services; the master control site includes an application orchestration plan generation function, a global task scheduling function, and an application resource management function; the sub-site includes a local task scheduling, a task execution function, and an application running function; the basic services are used to provide unified identity authentication, access services, and message buses for the master site and the sub-site; a heterogeneous application orchestration plan is generated in the distributed application orchestration support environment according to the application orchestration plan generation function through the master control site; and the heterogeneous application orchestration plan is globally orchestrated in the distributed application orchestration support environment according to the global task scheduling function through the master control site. Task scheduling; after receiving the scheme message of the main control site in the distributed application orchestration support environment through the sub-site and basic service, the local task scheduling function is started to perform local task scheduling, and task execution, application running function deployment and application startup are performed according to the task execution function and application running function; the present invention constructs a distributed application orchestration support environment, sets the main control site, sub-site and basic services in the distributed application orchestration support environment to perform orchestration and scheduling of heterogeneous applications, improves the response speed of sub-site scheduling through the asynchronous processing flow that separates task scheduling and application deployment, has good fault tolerance for application exceptions, realizes the deployment and startup of distributed collaborative applications of each sub-site, supports the operation orchestration of distributed collaborative applications of multiple sub-sites, and improves the orchestration efficiency.
[0037] In one embodiment, a heterogeneous application program orchestration solution is generated by a master control site according to an application program orchestration solution generation function in a distributed application program orchestration support environment, including:
[0038] The master site uses a directed acyclic graph in the distributed application orchestration support environment to describe the application installation and startup configuration and application runtime sequence that need to be deployed at each sub-site, and generate a heterogeneous application orchestration solution.
[0039] In one embodiment, a heterogeneous application orchestration solution is generated by using a directed acyclic graph to describe the application installation and startup configuration and the application runtime sequence to be deployed at each sub-site in a distributed application orchestration support environment, including:
[0040] The master control site uses a directed acyclic graph to model in a distributed application program orchestration support environment to obtain a workflow structure; the vertices of the directed acyclic graph are the vertices of the workflow structure; the edges of the directed acyclic graph are the edges of the workflow structure;
[0041] Generate heterogeneous application orchestration solutions based on the vertices and edges of the workflow structure; the vertices of the workflow structure include root vertices and non-root vertices; the root vertex represents the process of starting the application orchestration, the non-root vertices of the workflow represent the running instances of the application, and each vertex of the workflow corresponds to a metadata array; the metadata array is used to record the installation directory, running parameter configuration, output result directory, start time, end time and other configuration and running key parameters of the corresponding application; the edges of the workflow structure reflect the order of application running, and a directed edge can be added between any two vertices, and the orchestration order of the source vertex of the edge must precede the orchestration order of the destination vertex; each edge of the workflow structure corresponds to a metadata array, which is used to record the source vertex and destination vertex of the edge of the workflow structure.
[0042] In one of the embodiments, the global task scheduling function includes global task configuration, global task startup, global task monitoring and global task clearing.
[0043] Global task configuration means that the master site first cleans up the application orchestration schemes previously associated with the subsites to be configured, and then configures the application orchestration schemes that each subsite needs to run. The input is a list of subsites and a list of application orchestration schemes, and the output is a list of application orchestration schemes to be started for each subsite. The application orchestration scheme list for each subsite is defined through the front-end configuration interface and stored in the back-end relational database. One application orchestration scheme can be associated with multiple subsites, and one subsite can also be associated with multiple application orchestration schemes.
[0044] Global task initiation means that the master site encodes the configuration relationship into a JSON message and broadcasts it to all sub-sites through the message bus. After the sub-site subscribes to the configuration relationship JSON message, it parses the application orchestration scheme message and stores it in the local backend relational database, and updates the application orchestration scheme to be executed. The sub-site calls the local task scheduling function to execute the application orchestration scheme.
[0045] Global task monitoring means that the master site subscribes to the running progress of the sub-site through the monitoring topic of the message bus. Each sub-site compiles an running progress message at a certain interval (the default is 1 minute). The message includes the identification number of the sub-site and the proportion (percentage) of the executed vertices to the total number of nodes, and is published to the message bus. All sites that subscribe to the monitoring topic can parse and obtain the running progress of the sub-site.
[0046] Global task clearing means that when the application orchestration plan is completed or needs to be temporarily interrupted, the master site notifies each sub-site to clear the application through the clearing topic of the message bus. Each sub-site subscribes to the clearing topic in advance. After receiving the clearing function of the master site, it clears the storage resources of the executed application, terminates the unfinished application instance, ends the execution of the local scheduler, and clears the resources occupied by the local scheduler.
[0047] In one embodiment, performing global task scheduling on heterogeneous application program orchestration solutions according to a global task scheduling function in a distributed application program orchestration support environment through a master control site includes:
[0048] The master site configures the application orchestration scheme for each subsite in the distributed application orchestration support environment, and starts the local task scheduling function of each subsite in batches to execute their respective application orchestration schemes. Each subsite periodically reports the vertex completion ratio of local task scheduling. After all subsites complete their respective application orchestrations, the global task scheduling ends and the master site releases the application storage resources of each subsite.
[0049] The master site application orchestration solution generation and global orchestration include the master site building heterogeneous application orchestration solutions, describing the application installation and startup configuration that needs to be deployed at each sub-site through a directed acyclic graph architecture, defining the runtime sequence of the application, and then starting the global orchestration, performing full life cycle management of the application orchestration at each sub-site, calling the application resource management function to maintain the application, calling the application orchestration solution generation function to build a new solution, and calling the global task scheduling function to perform automated global orchestration.
[0050] In one of the embodiments, the application resource management function refers to the master site building an object storage service, the key of the object storage is the name of the application, and the value is the executable code of the application, which supports the storage and download functions of the application. The master site provides remote query and download of application resources for the sub-site through the reverse proxy service. When the sub-site is running, it provides local task scheduling, task execution, and application running functions. Each sub-site of the federated computing deploys a sub-site runtime service. The status of each vertex includes four categories: "not executed", "executing", "completed", and "abnormal exit". The status of all vertices that have not been scheduled by the application orchestration scheme is "not executed", and the status of all vertices that have completed the scheduling of the application orchestration scheme is "completed" or "abnormal exit". The local task scheduler supports the isolated execution of multiple concurrent application orchestration schemes. Each application orchestration scheme instance corresponds to an independent local task scheduler, and different application orchestration processes will not interfere with each other. To support the execution of local scheduler tasks under load balancing, each sub-site builds a single App queue to provide unified application execution for multiple local task schedulers.
[0051] In one of the embodiments, the local task scheduling function includes scheduler instance generation, scheduler timing calculation and scheduler task execution; scheduler task execution includes task reading, task parsing, task execution and task completion.
[0052] Scheduler instance generation refers to the running requirements of multi-user and multi-concurrency applications. When an application orchestration solution is executed, a scheduler instance is built separately. This scheduler instance is responsible for the entire life cycle of application orchestration. The scheduler automatically exits after the application orchestration is completed. A separate workflow queue structure is built. The elements of the queue are key-value pairs. The key is the name of the vertex application, and the value is the metadata required for the application to run.
[0053] Scheduler timing calculation refers to the scheduler inputting the JSON file of the application orchestration plan. First, the directed acyclic graph structure encoded in the JSON file is traversed through the graph breadth-first algorithm to obtain the topological sorting of the vertices of the directed acyclic graph. The topological sorting is written into the metadata field of the vertex in ascending order with positive integer values, and then the topological sorting values of the vertices are inserted into the workflow queue in ascending order. The sorting values of all vertices that can be started concurrently are the same, and are written into the execution order field of the workflow queue in an arbitrary order.
[0054] Scheduler task execution refers to reading the execution order field of the workflow queue and scheduling the execution of each vertex according to the topological sorting. The applications associated with the vertices are executed in the order from small to large. Scheduler task execution includes task reading, task parsing, task execution, and task completion.
[0055] Task reading means reading the vertices of the workflow queue in ascending order according to the topological sorting. Each time, only the application with the smallest topological sorting among the unfinished application instances is read.
[0056] Task parsing refers to parsing the metadata of the application corresponding to the vertex and constructing the application instance metadata. An application instance is identified by a random string. The same application code can be started and executed concurrently by multiple local task schedulers through different application instance identifiers.
[0057] Task execution means writing the metadata of the application instance into the App queue, asynchronously reading the tasks in the App queue through the task execution function, and executing the application instance. Vertices with the same timing value are put into the App queue concurrently.
[0058] Task completion means that after the application currently executing the vertex has finished executing, that is, after the vertex status is "completed" or "abnormal exit", the subsequent unfinished vertices are read in a loop and transferred to steps 1.2.1.3.1 for execution in sequence. If all vertices have been completed, the local scheduler is terminated and the storage resources occupied by the current local scheduler are destroyed.
[0059] In one of the embodiments, the task execution function includes retrieving application instance metadata and starting to execute the application instance; the application running function includes pulling application executable code and updating the application instance status.
[0060] The task execution function refers to taking out and executing application instance records from the App queue in a first-in-first-out order.
[0061] Retrieving application instance metadata means that the subsite pre-sets the upper limit of the number of application instances that can be executed concurrently. If the currently running but unfinished application instances have not reached the upper limit, you can continue to read and start application instances from the App queue. Otherwise, you must wait until the running application ends and releases resources before you can start a new application instance.
[0062] Starting and executing an application instance means calling the application running function according to the retrieved application instance record to execute the corresponding application. The number of concurrently running application instances is updated according to the number of newly started applications, and the vertex state associated with the application instance in the workflow queue of the local task scheduler is marked from "not executed" to "executing".
[0063] The application running function means that the sub-site parses the metadata of the application instance, starts the application, and updates the running status of the application instance in the workflow queue.
[0064] Pulling the application executable code means querying the executable code of the application instance locally. If it does not exist locally, querying and downloading the application executable code from the master control site, and then starting the corresponding application.
[0065] Update the application instance status to point to the App queue to indicate that the application has been started and set the status to "Executing"; after the application ends normal execution, indicate to the App queue that the application has exited and set the status to "Completed". If the application exits abnormally, set the status to "Exit Abnormally", and reduce the number of concurrently running application instances based on the number of completed and abnormally exited applications. Synchronously update the corresponding application status in the workflow queue.
[0066] In one embodiment, the basic service includes a message bus function and a unified registration function; the message bus function is for the main control site and the sub-site to access the same message bus subscription topic through the distributed message middleware, publish messages to the subscribed topic, and asynchronously receive messages.
[0067] The unified registration function means that the master site provides a registration topic through the message bus; each sub-site publishes an access request message to the master site through the registration topic when it starts. After the master site receives the access message, it manually reviews the identity of the sub-site and registers the sub-site as a sub-site after confirming that it is a federated computing member. Otherwise, the registration request of the corresponding site will be rejected.
[0068] It should be understood that although Figure 1 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.
[0069] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 3As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for rapid orchestration of heterogeneous applications for federated computing is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a key, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.
[0070] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0071] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method in the above embodiment when executing the computer program.
[0072] In one embodiment, a computer storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method in the above embodiment are implemented.
[0073] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
[0074] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, 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, they should be considered to be within the scope of this specification.
[0075] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.
Claims
1. A method for rapid orchestration of heterogeneous applications for federated computing, characterized in that: Constructing a distributed application orchestration support environment in a federated computing cluster; the distributed application orchestration support environment includes a master control site, sub-sites, and basic services; the master control site includes an application orchestration solution generation function, a global task scheduling function, and an application resource management function; the sub-sites include a local task scheduling, a task execution function, and an application running function; The basic service is used to provide unified identity authentication, access services and message bus for the main site and sub-sites; The method includes: generating a heterogeneous application orchestration scheme according to the application orchestration scheme generation function in the distributed application orchestration support environment by the master site; performing global task scheduling on the heterogeneous application orchestration scheme according to the global task scheduling function in the distributed application orchestration support environment by the master site; and starting the local task scheduling function to perform local task scheduling after receiving the scheme message of the master site in the distributed application orchestration support environment by the sub-site and the basic service, and performing task execution, application running function deployment and application startup according to the task execution function and application running function.
2. The method according to claim 1, characterized in that: Generate a heterogeneous application program orchestration scheme in the distributed application program orchestration support environment through the master control site according to the application program orchestration scheme generation function, including: The master control site uses a directed acyclic graph in the distributed application orchestration support environment to describe the application installation and startup configuration and the application runtime sequence that need to be deployed at each sub-site, thereby generating a heterogeneous application orchestration solution.
3. The method according to claim 2, characterized in that The master control site uses a directed acyclic graph in the distributed application program orchestration support environment to describe the application program installation and startup configuration and the application program runtime sequence to be deployed at each sub-site, thereby generating a heterogeneous application program orchestration solution, including: The master control site uses a directed acyclic graph to model in the distributed application program orchestration support environment to obtain a workflow structure; the vertices of the directed acyclic graph are the vertices of the workflow structure; the edges of the directed acyclic graph are the edges of the workflow structure; A heterogeneous application orchestration scheme is generated according to the vertices of the workflow structure and the edges of the workflow structure; the vertices of the workflow structure include root vertices and non-root vertices; the root vertex represents the process of starting the application orchestration, the non-root vertices of the workflow represent the running instances of the application, and each vertex of the workflow corresponds to a metadata array; the metadata array is used to record the installation directory, running parameter configuration, output result directory, start time, end time configuration and key running parameters of the corresponding application; the edges of the workflow structure reflect the order of application running, and a directed edge can be added between any two vertices, and the orchestration order of the source vertex of the edge must be prior to the orchestration order of the destination vertex; each edge of the workflow structure corresponds to a metadata array, which is used to record the source vertex and destination vertex of the edge of the workflow structure.
4. The method according to claim 1, characterized in that: The global task scheduling function includes global task configuration, global task startup, global task monitoring and global task clearing.
5. The method according to claim 4, characterized in that Performing global task scheduling on the heterogeneous application program orchestration solution in the distributed application program orchestration support environment according to the global task scheduling function by the master control site includes: The master control site configures the application orchestration scheme of each subsite in the distributed application orchestration support environment, and starts the local task scheduling function of each subsite in batches to execute their respective application orchestration schemes. Each subsite periodically reports the vertex completion ratio of local task scheduling. After all subsites complete their respective application orchestrations, the global task scheduling ends and the master control site releases the application storage resources of each subsite.
6. The method according to claim 5, characterized in that The local task scheduling function includes scheduler instance generation, scheduler timing calculation and scheduler task execution; the scheduler task execution includes task reading, task parsing, task execution and task completion.
7. The method according to claim 1, characterized in that The task execution function includes retrieving application instance metadata and starting to execute the application instance; the application running function includes pulling application executable code and updating application instance status.
8. The method according to claim 1, characterized in that The basic service includes a message bus function and a unified registration function; the message bus function enables the master site and the sub-site to access the same message bus subscription topic through a distributed message middleware, publish messages to the subscribed topic, and asynchronously receive messages.
9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.
