CN113342520B

CN113342520B - Cross-cluster remote continuous release method and system based on federal implementation

Info

Publication number: CN113342520B
Application number: CN202110603473.0A
Authority: CN
Inventors: 满欣; 吴仲阳; 许广洋; 陈彦锦
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-05-31
Filing date: 2021-05-31
Publication date: 2024-03-08
Anticipated expiration: 2041-05-31
Also published as: CN113342520A

Abstract

The method and the system for cross-cluster remote continuous release based on federal implementation can be used in the financial field or other fields, and the method comprises the following steps: the method comprises the steps that a main cluster receives at least one piece of application development requirement information and workload condition information transmitted by all business clusters, and schedules all the business clusters according to all the workload condition information; the service cluster receives a service cluster scheduling instruction and application development requirement information sent by a main cluster, and develops a corresponding application; through the mode of multi-cluster management, the main cluster decides how to distribute the workload in different clusters according to the workload condition of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; the workload of each cluster is maximized.

Description

Cross-cluster remote continuous release method and system based on federal implementation

Technical Field

The application relates to the financial field, in particular to a cross-cluster remote continuous release method and system based on federal implementation.

Background

In order to ensure the safety of the software development process, different types of business works are mutually isolated, so that each branch office can deploy business clusters such as a research and development cluster, a test cluster, a production cluster and the like. The resource scheduling platform provides a corresponding cluster environment according to specific work demands of users, supports continuous integrated release across clusters, and can deploy release in each cluster according to different stages of a software life cycle.

Disclosure of Invention

Aiming at the problems in the prior art, the application provides a cross-cluster remote continuous release method and system based on federation, which can provide corresponding cluster environments according to specific work demands of users, support continuous integrated release of cross clusters, and can be deployed and released in each cluster according to different stages of a software life cycle.

In order to solve the technical problems, the application provides the following technical scheme:

in a first aspect, the present application provides a federally implemented cross-cluster remote persistent publishing method, performed by a primary cluster, comprising:

receiving at least one piece of application development requirement information and workload condition information transmitted by all business clusters;

and scheduling each service cluster according to the workload status information transmitted by all the service clusters, so that each service cluster processes the application development requirement information and further develops corresponding application.

Further, the application development requirement information includes a plurality of function requirement information, and the cross-cluster remote continuous publishing method further includes:

generating a function release sequence according to the plurality of function requirement information;

the scheduling each service cluster according to the workload status information transmitted by all the service clusters includes:

And dispatching the service clusters in the idle state one by one according to the function release sequence so as to process the requirement information of each function and further develop the corresponding application module.

Further, the service clusters in the idle state develop loaded service clusters for releasing all functional requirements, and schedule the service clusters in the idle state one by one according to the functional release sequence, including:

aiming at the function demand information at the first place, scheduling one of the service clusters currently in the idle state, and transmitting the application development demand information to the service cluster so that the service cluster processes the function demand information to generate an intermediate product;

and executing iterative operation, scheduling another service cluster in an idle state, and instructing the other service cluster in the idle state to receive the intermediate product so that the other service cluster processes the adjacent next function requirement information, and generating an integrated intermediate product until all the function requirements are processed.

In a second aspect, the present application provides a federally implemented cross-cluster remote persistent publishing method, performed by a service cluster in an idle state, including:

Receiving a service cluster scheduling instruction sent by a main cluster and application development requirement information;

processing the application development requirement information and developing a corresponding application;

the main cluster receives at least one application development requirement information and workload status information transmitted by all service clusters, and then schedules each service cluster according to the workload status information transmitted by all service clusters.

Further, the application development requirement information includes a plurality of function requirement information, the service cluster is a first scheduled service cluster, the main cluster generates a function release sequence according to the plurality of function requirement information, and the processing the application development requirement information and developing a corresponding application includes:

processing the first function demand information in the function release sequence to generate an intermediate product;

and sending the intermediate product to a designated service cluster according to an intermediate product transmission instruction sent by the main cluster, so that the designated service cluster processes the next adjacent function requirement information in the function release sequence.

Further, the service cluster is a service cluster which is not scheduled first, the processing the application development requirement information and developing a corresponding application includes:

Receiving an intermediate product sent by a last designated service cluster, and an intermediate product transmission instruction and a function release sequence sent by a main cluster;

processing the current function demand information to be processed in the function release sequence, and generating an integrated intermediate product on the basis of the intermediate product sent by the last service cluster;

transmitting the integrated intermediate product to a next designated service cluster based on the intermediate product transmission instruction; and if the next appointed service cluster is the last scheduled service cluster, outputting the final application by the next appointed service cluster.

In a third aspect, the present application provides a federally implemented cross-cluster remote persistent publishing method, including:

the method comprises the steps that a main cluster receives at least one piece of application development requirement information and workload status information transmitted by all business clusters;

the service cluster receives a service cluster scheduling instruction sent by a main cluster and application development requirement information;

and the service cluster processes the application development requirement information and develops corresponding applications.

In a fourth aspect, the present application provides a primary cluster comprising:

an information receiving module: receiving at least one piece of application development requirement information and workload condition information transmitted by all business clusters;

And a cluster scheduling module: and scheduling each service cluster according to the workload status information transmitted by all the service clusters, so that each service cluster processes the application development requirement information and further develops corresponding application.

Further, the application development requirement information includes a plurality of function requirement information, and the main cluster further includes:

functional sequence module: generating a function release sequence according to the plurality of function requirement information;

the cluster scheduling module comprises: cluster scheduling unit: and dispatching the service clusters in the idle state one by one according to the function release sequence so as to process the requirement information of each function one by one and further develop corresponding application modules one by one.

In a fifth aspect, the present application provides a service cluster, the service cluster comprising:

the demand receiving module: receiving a service cluster scheduling instruction sent by a main cluster and application development requirement information;

and an application development module: processing the application development requirement information and developing a corresponding application;

Further, the application development requirement information includes a plurality of function requirement information, the service cluster is a first scheduled service cluster, the main cluster generates a function release sequence according to the plurality of function requirement information, and the application development module includes:

a first development unit: processing the first function demand information in the function release sequence to generate an intermediate product;

a first transmission unit: and sending the intermediate product to a designated service cluster according to an intermediate product transmission instruction sent by the main cluster, so that the designated service cluster processes the next adjacent function requirement information in the function release sequence.

Further, the service cluster is a non-first scheduled service cluster, and the application development module includes:

a receiving unit: receiving an intermediate product sent by a last designated service cluster, and an intermediate product transmission instruction and a function release sequence sent by a main cluster;

a second development unit: processing the current function demand information to be processed in the function release sequence, and generating an integrated intermediate product on the basis of the intermediate product sent by the last service cluster;

A second transmission unit: transmitting the integrated intermediate product to a next designated service cluster based on the intermediate product transmission instruction; and if the next appointed service cluster is the last scheduled service cluster, outputting the final application by the next appointed service cluster.

In a sixth aspect, the present application provides a federally-implemented cross-cluster remote persistent publication system, comprising:

a master cluster: receiving at least one application development requirement information and workload condition information transmitted by all service clusters, and scheduling each service cluster according to the workload condition information transmitted by all service clusters;

service cluster: and receiving a service cluster scheduling instruction and application development requirement information sent by a main cluster, processing the application development requirement information, and developing a corresponding application.

In a seventh aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the cross-cluster remote persistent distribution method when the processor executes the program.

In an eighth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the cross-cluster remote persistent release method.

According to the technical scheme, the method and the system for remote continuous release of the cross-cluster based on the federal implementation provided by the application comprise the following steps: the method comprises the steps that a main cluster receives at least one piece of application development requirement information and workload condition information transmitted by all business clusters, and schedules all the business clusters according to the workload condition information transmitted by all the business clusters; the service cluster receives a service cluster scheduling instruction and application development requirement information sent by a main cluster, processes the application development requirement information and develops a corresponding application; through the mode of multi-cluster management, the main cluster decides how to distribute the workload in different clusters according to the workload condition of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a main cluster execution operation flow of a federally implemented cross-cluster remote persistent publishing method in an embodiment of the present application.

Fig. 2 is a flowchart illustrating specific operations between steps 100 to 110 in a federally implemented cross-cluster remote persistent distribution method according to an embodiment of the present application.

Fig. 3 is a schematic flow chart of step 002 in a federally implemented cross-cluster remote persistent publishing method in an embodiment of the present application.

Fig. 4 is a schematic flow chart of a service cluster execution operation of the federally implemented cross-cluster remote persistent publishing method in an embodiment of the present application.

Fig. 5 is a flowchart illustrating step 201 in a federally implemented cross-cluster remote persistent publishing method in an embodiment of the present application.

Fig. 6 is a flow diagram of a federally implemented cross-cluster remote persistent publishing method in an embodiment of the present application.

Fig. 7 is a schematic structural diagram of a primary cluster in an embodiment of the present application.

Fig. 8 is a schematic structural diagram of a service cluster in an embodiment of the present application.

Fig. 9 is a schematic structural diagram of an application development module of a first scheduled service cluster in an embodiment of the present application.

Fig. 10 is a schematic structural diagram of an application development module of a service cluster that is not scheduled first in the embodiment of the present application.

Fig. 11 is a schematic structural diagram of a federally implemented cross-cluster remote persistent publishing device provided by an application example of the present application.

Fig. 12 is a schematic working diagram of a Master node processor in a cross-cluster remote persistent publishing device based on federal implementation provided by an application example of the present application.

Fig. 13 is a schematic structural diagram of an electronic device in an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

It should be noted that, the cross-cluster remote continuous release method and system based on federation disclosed in the present application can be used in the financial field, and also can be used in any field other than the financial field, and the application field of the cross-cluster remote continuous release method and system based on federation disclosed in the present application is not limited.

In one or more embodiments of the present application, a service cluster in an idle state refers to a service cluster after all functional requirement development loads are released, and all workloads do not need to be released.

In order to ensure the safety of a software development process, different types of business works are mutually isolated, the application provides a cross-cluster remote continuous release method, a cross-cluster remote continuous release device, electronic equipment and a computer readable storage medium based on federal realization, and a main cluster decides how to distribute the work load in different clusters according to the work load condition of each business cluster through a multi-cluster management mode, so that different tasks are assigned to different clusters.

Based on the foregoing, the present application further provides a cross-cluster remote persistent publishing device for implementing the cross-cluster remote persistent publishing method provided in one or more embodiments of the present application, where the cross-cluster remote persistent publishing device may be in communication connection with a client device, and the client terminal device may be provided with a plurality of cross-cluster remote persistent publishing devices, and specifically may access the client terminal device through an application server.

The method comprises the steps that a main cluster in the cross-cluster remote continuous release device can receive application development requirement information from client terminal equipment, acquire a plurality of function requirement information in the application development requirement information from the application development requirement information, generate a function release sequence according to the plurality of function requirement information, transmit the application development requirement information and the function release sequence to a service cluster in an idle state, and process the function requirement information at the first position of the function release sequence according to the application development requirement information and the function release sequence to generate a product; and then, transmitting the intermediate product to a next service cluster designated by the main cluster, processing the function requirement information positioned next adjacent to the function release sequence on the basis of the intermediate product by the service cluster, generating an integrated intermediate product, executing iteration Cao Zu until all the function requirement information is processed, generating a final application product, and transmitting the final application product to the client device.

It is understood that the client devices may include smartphones, tablet electronic device portable computers, desktop computers, personal Digital Assistants (PDAs), and the like.

The client device may have a communication module (i.e. a communication unit) and may be connected to a remote server in a communication manner, so as to implement data transmission with the server. For example, the communication unit may send the user demand information to the server so that the master cluster generates the function release sequence according to the user demand information. The communication unit may also receive the recognition result returned by the server. The server may include a server on the side of the task scheduling center, and in other implementations may include a server of an intermediate platform, such as a server of a third party server platform having a communication link with the task scheduling center server. The server may include a single computer device, a server cluster formed by a plurality of servers, or a server structure of a distributed device.

Any suitable network protocol may be used for communication between the server and the client device, including those not yet developed at the filing date of this application. The network protocols may include, for example, TCP/IP protocol, UDP/IP protocol, HTTP protocol, HTTPS protocol, etc. Of course, the network protocol may also include, for example, RPC protocol (Remote Procedure Call Protocol ), REST protocol (Representational State Transfer, representational state transfer protocol), etc. used above the above-described protocol.

According to the federal-based remote continuous issuing method, the cross-cluster remote continuous issuing device, the electronic equipment and the computer readable storage medium, through a multi-cluster management mode, a main cluster decides how to distribute workload in different clusters according to workload conditions of each service cluster, and different tasks are assigned to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved.

The following embodiments and application examples are described in detail.

In order to ensure the safety of the software development process, different types of business work are mutually isolated, the application provides an embodiment of a cross-cluster remote continuous release method based on federal implementation, and referring to fig. 1, the cross-cluster remote continuous release method specifically comprises the following contents, which are executed by a main cluster:

Step 100: at least one application development requirement information and workload condition information transmitted by all service clusters are received.

It can be understood that a user submits application development requirement information to a main cluster through a client device, one main cluster configures a plurality of service clusters, and the main cluster can acquire the workload condition of the service clusters in real time, find the service clusters in an idle state and perform work task distribution.

Step 110: and scheduling each service cluster according to the workload status information transmitted by all the service clusters, so that each service cluster processes the application development requirement information and further develops corresponding application.

It can be understood that the main cluster can locate the service cluster in the idle state according to the workload status information transmitted by all the service clusters, send the application development requirement information to the service cluster in the idle state, and develop the corresponding application according to the application development requirement information.

As can be seen from the above description, according to the federal implementation-based cross-cluster remote persistent publishing method provided by the embodiments of the present application, through a multi-cluster management mode, a main cluster decides how to distribute workload among different clusters according to workload conditions of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved. The main clusters can be deployed in a cross-cluster redundancy mode, and when a certain cluster area fails, the whole service is not affected. The cluster federation can detect whether a cluster is in an unavailable state, and if a certain cluster is found to be in the unavailable state, the failed task can be reassigned to the clusters in other available states in the cluster federation. The master cluster may automatically advance the indifferent publishing of applications in the environment stack. Baseline management is applied, and one of the management is an environment stack baseline, and aims at the management of on-line release versions, so that the quick rollback to the last stable version when faults occur on the line is ensured. The other is a small baseline, and in other specific scenes, different strategies can be adopted to clearly manage the promotion of the application in development, test and production business.

In order to further improve the development efficiency of the whole service cluster and overall workload of the service clusters, in one embodiment of the federally implemented cross-cluster remote persistent publishing method provided in the present application, a preferred manner of scheduling the service clusters is provided, and referring to fig. 2, the following specifically includes the following contents between step 100 and step 110 in the cross-cluster remote persistent publishing method:

step 001: and generating a function release sequence according to the plurality of function requirement information.

It may be understood that the application development requirement information includes a plurality of function requirement information, the main cluster orders the plurality of function requirement information to generate a function release sequence, each service cluster develops one by one according to the function release sequence, for example, it is to be set that a certain application development requirement information includes A, B, C, D four function requirement information, the main cluster orders the four function requirement information to generate a function release sequence A, C, B, D, and the service clusters develop one by one according to the function release sequence.

In step 110, scheduling each service cluster according to the workload status information transmitted by all service clusters includes:

step 002: and dispatching the service clusters in the idle state one by one according to the function release sequence so as to process the requirement information of each function and further develop the corresponding application module.

In step 002, the main cluster schedules service clusters in idle state according to the function publishing sequence, and each service cluster processes one piece of function requirement information, thereby developing a corresponding application module. The main cluster schedules the service clusters in the idle state according to the function issuing sequence in two scheduling modes, for example, certain application development requirement information comprises A, B, C, D four pieces of function requirement information, the function issuing sequence is A, C, B, D, the first type of the main cluster can schedule four service clusters in the idle state, respectively develop A, B, C, D four functions, and finally integrate the four developed intermediate products to form a final application. Secondly, the main cluster can schedule one of the service clusters in an idle state, schedule the rest required service clusters one by one according to the workload conditions of other service clusters, develop each service cluster on an intermediate product developed by the last service cluster, and finally form a final application. The second scheduling mode is adopted, and the one-by-one scheduling mode is adopted, so that the service clusters can be utilized to the maximum extent, and the whole service clusters can process a plurality of application development requirement information simultaneously.

As can be seen from the foregoing description, in the cross-cluster remote continuous publishing method based on federal implementation provided in the embodiments of the present application, a main cluster sorts a plurality of function requirement information in application development requirement information to obtain a function publishing sequence, and service clusters are scheduled one by one according to the function publishing sequence, so that the service clusters can be utilized to the maximum extent, and the whole service clusters can process a plurality of application development requirement information simultaneously.

In order to further improve the development efficiency of the whole service cluster and overall workload of the service clusters, in one embodiment of the federally implemented cross-cluster remote persistent publishing method provided in the present application, an iterative development manner is provided, and referring to fig. 3, step 002 in the cross-cluster remote persistent publishing method specifically includes the following contents:

step 021: and aiming at the function requirement information at the first position, scheduling one of the service clusters currently in the idle state, and transmitting the application development requirement information to the service cluster so that the service cluster processes the function requirement information to generate an intermediate product.

It can be understood that the main cluster schedules the first service cluster in an idle state, transmits application development requirement information to the service cluster, and the service cluster processes the function requirement information at the first position of the function release sequence to generate a first intermediate product.

Step 022: and executing iterative operation, scheduling another service cluster in an idle state, and instructing the other service cluster in the idle state to receive the intermediate product so that the other service cluster processes the adjacent next function requirement information, and generating an integrated intermediate product until all the function requirements are processed.

It can be understood that, after the processing of the functional requirement information at the first position of the functional release sequence is completed, the main cluster schedules the second service cluster in an idle state, the service cluster receives the first intermediate product transmitted by the first service cluster, processes the functional requirement information at the second position of the functional release sequence on the basis of the first intermediate product to generate the second intermediate product, and simultaneously, the main cluster schedules the third service cluster in an idle state, the service cluster receives the second intermediate product transmitted by the second service cluster, processes the functional requirement information at the third position of the functional release sequence on the basis of the second intermediate product, generates the third intermediate product, and circulates in this way until all the functional requirement processing is completed, thereby obtaining the final application product.

In a second aspect, in order to further improve application accuracy of feature information corresponding to an API call log, the present application provides an embodiment of a federally implemented cross-cluster remote persistent publishing method, referring to fig. 4, where the cross-cluster remote persistent publishing method specifically includes the following content, which is executed by a service cluster in an idle state:

step 200: and receiving a service cluster scheduling instruction sent by the main cluster and application development requirement information.

Step 201: and processing the application development requirement information to develop a corresponding application.

It can be understood that a user submits application development requirement information to a main cluster through a client device, one main cluster configures a plurality of service clusters, and the main cluster can acquire the workload condition of the service clusters in real time, find the service clusters in an idle state and perform work task distribution. The service clusters receive the scheduling instruction and the application development requirement information from the service clusters, and develop corresponding application products according to the application development requirement information, and in some other embodiments, when one of the service clusters fails, the service clusters report the failure to the main clusters, and the main clusters redistribute the tasks which fail in the service cluster development to other available service clusters without affecting the whole service.

As can be seen from the above description, according to the federal implementation-based cross-cluster remote persistent publishing method provided by the embodiments of the present application, through a multi-cluster management mode, a main cluster decides how to distribute workload among different clusters according to workload conditions of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved.

In order to further improve the development efficiency of the whole service cluster and overall workload of the service clusters, in an embodiment of the federally implemented cross-cluster remote persistent publishing method provided in the present application, a manner of iterative development of application requirements is provided, and referring to fig. 5, step 201 in the cross-cluster remote persistent publishing method specifically includes the following contents:

Step 030: and processing the function demand information positioned at the first position in the function release sequence to generate an intermediate product.

It can be understood that the service cluster processing the function requirement information located at the first position in the function release sequence is the first scheduled service cluster, the main cluster sends a scheduling instruction and application development requirement information to the service cluster in the idle state according to the function release sequence, and the service cluster processes the function requirement information located at the first position in the function release sequence to generate a first intermediate product.

Step 031: and sending the intermediate product to a designated service cluster according to an intermediate product transmission instruction sent by the main cluster, so that the designated service cluster processes the next adjacent function requirement information in the function release sequence.

It may be appreciated that, when the first intermediate product in step 031 is developed, the service cluster receives an intermediate product transmission instruction from the main cluster, and sends the first intermediate product and the application development requirement information to a designated service cluster, and the designated service cluster processes the function requirement information located at the second position in the function release sequence on the basis of the first intermediate product, so as to generate a second intermediate product.

step 032: and receiving the intermediate product sent by the last designated service cluster, and an intermediate product transmission instruction and a function issuing sequence sent by the main cluster.

Step 033: and processing the function requirement information to be processed currently in the function release sequence, and generating an integrated intermediate product on the basis of the intermediate product sent by the last service cluster.

Step 034: transmitting the integrated intermediate product to a next designated service cluster based on the intermediate product transmission instruction; and if the next appointed service cluster is the last scheduled service cluster, outputting the final application by the next appointed service cluster.

It can be understood that, after the last specified service cluster processes the current function requirement information, the service cluster receives a product transmission instruction sent by the main cluster, and transmits the developed intermediate product to the next specified service cluster, and the next specified service cluster processes the function requirement information to be processed currently in the function release sequence on the basis of the intermediate product developed by the last service cluster, generates an integrated intermediate product, and sends the integrated intermediate product to the next specified service cluster until all the function requirement information is processed, so as to generate a final application product.

In the following, steps 021 to 025 will be described in connection with the specific embodiment, for example, a certain application development requirement information includes A, B, C three function requirement information, and the master cluster generates a function issuing sequence with the sequence A, B, C according to the application development requirement information. The method comprises the steps that a first service cluster in an idle state receives a scheduling instruction, application development requirement information and a function release sequence sent by a main cluster, the function requirement information A at the first position of the function release sequence is processed to generate a first intermediate product a, meanwhile, the first service cluster receives a product transmission instruction sent by the main cluster, the first intermediate product a is transmitted to a specified second service cluster, the second service cluster receives the first intermediate product a and the function release sequence, the second service cluster processes function requirement information B at the second position of the function release sequence on the basis of the first intermediate product a to generate a second intermediate product B, the second service cluster receives a product transmission instruction sent by the main cluster, the second intermediate product B is transmitted to a specified third service cluster, the third service cluster receives the second intermediate product B and the function release sequence, the function requirement information C at the last position of the function release sequence on the basis of the second intermediate product B is processed to generate a third intermediate product C, and the third intermediate product C is a final application product after development is completed.

In order to ensure the safety of the software development process, the service works of different categories are isolated from each other, and the application provides an embodiment of a cross-cluster remote continuous release method based on federal implementation, referring to fig. 6, wherein the cross-cluster remote continuous release method specifically comprises the following contents:

step 300: the master cluster receives at least one application development requirement information and workload condition information transmitted by all the service clusters.

It can be understood that the main cluster can locate the service cluster in the idle state according to the workload status information transmitted by all the service clusters, send the received application development requirement information to the service cluster in the idle state, and develop the corresponding application according to the application development requirement information.

Step 301: and the service cluster receives the service cluster scheduling instruction and the application development requirement information sent by the main cluster.

It can be understood that the service clusters receive the scheduling instruction from the service clusters and the application development requirement information, and develop the corresponding application products according to the application development requirement information, and in some other embodiments, when one of the service clusters fails, the service clusters report the failure to the main cluster, and the main cluster redistributes the task that fails in the service cluster development to other available service clusters, so that the whole service is not affected.

Step 302: and the service cluster processes the application development requirement information and develops corresponding applications.

In order to ensure the security of the software development process, the business works of different categories are isolated from each other, and the application provides an embodiment of a main cluster, referring to fig. 7, wherein the main cluster specifically includes the following contents:

the information receiving module 10: at least one application development requirement information and workload condition information transmitted by all service clusters are received.

It can be understood that, the information receiving module 10 receives application development requirement information submitted by a user through a client device, one main cluster configures a plurality of service clusters, and the main cluster can acquire the workload condition of the service clusters in real time, find the service clusters in an idle state, and perform work task allocation.

Cluster scheduling module 11: and scheduling each service cluster according to the workload status information transmitted by all the service clusters, so that each service cluster processes the application development requirement information and further develops corresponding application.

It can be understood that the cluster scheduling module 11 collects the workload information of each service cluster, positions the service clusters in the idle state according to the workload status information transmitted by all the service clusters, and sends the application development requirement information to the service clusters in the idle state, and the service clusters develop corresponding applications according to the application development requirement information. In some other embodiments, the cluster scheduling module 11 may further detect the working state of each service cluster according to the workload status information transmitted by all service clusters, and when one of the service clusters fails, the task that fails in the service cluster development may be reassigned to other available service clusters, without affecting the whole service.

The main cluster supports multi-cluster management, and the core processor of the main cluster is used for solving the problems of automatic deployment and recovery of the application, so that a user only needs to submit the configuration requirement of an application instance, the core processor can finish the initialization of the application instance, and when a certain module of the application fails, the core processor has an automatic recovery function. The core processor comprises a Master node processor and a workbench node processor.

The Master cluster comprises a Master node and a Worker node, and a Master node processor is deployed for managing Master components required by all service clusters (clusters which are constructed according to user requirements and process specific tasks); and deploying a Waker node processor for managing the upper line and the lower line of the Woker node, wherein the Woker node of the main cluster is a Master node of each service cluster.

As shown in fig. 12, the Master node processor is configured to monitor the state change of the service cluster (the service cluster state is automatically generated by the Master node processor), so that all Master components of the service cluster reach the target state.

Besides the Master component, the Master node processor can also maintain the expansion component, and resources can be deployed to a target state only by providing an expansion component deployment template for a user.

The workbench node processor is used for monitoring the state change of the machine in the service cluster, and finally enabling the workbench node to reach the ready state; some component gray scale release may be controlled to some nodes. The user only needs to submit the user-defined resource description describing the gray release, and the gray release can be executed.

As can be seen from the above description, in the primary cluster provided in the embodiments of the present application, through a multi-cluster management mode, the primary cluster determines how to allocate workloads in different clusters according to workload conditions of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved. The main clusters can be deployed in a cross-cluster redundancy mode, and when a certain cluster area fails, the whole service is not affected. The cluster federation can detect whether a cluster is in an unavailable state, and if a certain cluster is found to be in the unavailable state, the failed task can be reassigned to the clusters in other available states in the cluster federation. The master cluster may automatically advance the indifferent publishing of applications in the environment stack. Baseline management is applied, and one of the management is an environment stack baseline, and aims at the management of on-line release versions, so that the quick rollback to the last stable version when faults occur on the line is ensured. The other is a small baseline, and in other specific scenes, different strategies can be adopted to clearly manage the promotion of the application in development, test and production business.

In order to further improve the development efficiency of the whole service cluster and overall workload of the service clusters, in an embodiment of the cross-cluster remote persistent publishing device based on federal implementation provided in the present application, a preferred manner of scheduling the service clusters is provided, see fig. 7, where the main cluster further includes:

functional sequence module 12: and generating a function release sequence according to the plurality of function requirement information.

It may be understood that the application development requirement information includes a plurality of function requirement information, the function sequence module 12 orders the plurality of function requirement information to generate a function release sequence, each service cluster develops one by one according to the function release sequence, for example, it is to be set that a certain application development requirement information includes A, B, C, D four function requirement information, the function sequence module 12 orders the four function requirement information to generate a function release sequence A, C, B, D, and the service clusters develop one by one according to the function release sequence.

The cluster scheduling module 11 includes: cluster scheduling unit: and dispatching the service clusters in the idle state one by one according to the function release sequence so as to process the requirement information of each function one by one and further develop corresponding application modules one by one.

It can be understood that the cluster scheduling unit schedules service clusters in an idle state according to the function release sequence, and each service cluster processes one piece of function requirement information so as to develop a corresponding application module. The cluster scheduling unit schedules the service clusters in the idle state according to the function issuing sequence in two scheduling modes, for example, certain application development requirement information comprises A, B, C, D four pieces of function requirement information, the function issuing sequence of the cluster scheduling unit is A, C, B, D, the first type of the cluster scheduling unit can schedule the four service clusters in the idle state to develop A, B, C, D four functions respectively, and finally the developed four intermediate products are integrated to form a final application. Secondly, the cluster scheduling unit may schedule one of the service clusters in an idle state, schedule the remaining service clusters one by one according to workload conditions of other service clusters, develop each service cluster on an intermediate product developed by the last service cluster, and finally form a final application. The second scheduling mode is adopted, and the one-by-one scheduling mode is adopted, so that the service clusters can be utilized to the maximum extent, and the whole service clusters can process a plurality of application development requirement information simultaneously.

As can be seen from the above description, in the main cluster provided in the embodiments of the present application, the main cluster sorts a plurality of function requirement information in application development requirement information to obtain a function release sequence, and according to the function release sequence, service clusters are scheduled one by one, so that the service clusters can be utilized to the maximum extent, and the whole service cluster can process a plurality of application development requirement information simultaneously.

In order to ensure the security of the software development process, the business works of different categories are isolated from each other, and the application provides an embodiment of a business cluster, referring to fig. 8, where the business cluster specifically includes the following contents:

the demand receiving module 20: and receiving a service cluster scheduling instruction sent by the main cluster and application development requirement information.

The application development module 21: and processing the application development requirement information to develop a corresponding application.

It can be understood that one main cluster configures a plurality of service clusters, and the main cluster can acquire the workload condition of the service clusters in real time, find the service clusters in an idle state, and perform work task allocation. The demand receiving module 20 receives a scheduling instruction from a cluster and application development demand information, and the application development module 21 develops a corresponding application product according to the application development demand information, and in some other embodiments, when one of the service clusters fails, the service cluster detects the failure through workload information of the service cluster, reports the failure to the main cluster, and the main cluster redistributes a task failing in the service cluster development to other available service clusters without affecting the whole service.

As can be seen from the above description, in the service cluster provided in the embodiments of the present application, through a multi-cluster management mode, a main cluster determines how to distribute workload among different clusters according to workload conditions of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved. The main clusters can be deployed in a cross-cluster redundancy mode, and when a certain cluster area fails, the whole service is not affected. The cluster federation can detect whether a cluster is in an unavailable state, and if a certain cluster is found to be in the unavailable state, the failed task can be reassigned to the clusters in other available states in the cluster federation.

In order to further improve the development efficiency of the whole service cluster and overall workload of the service clusters, in an embodiment of a service cluster provided in the present application, a manner of iterative development of application requirements is provided, and referring to fig. 9, an application development module 21 of a first scheduled service cluster specifically includes the following contents:

First development unit 001: and processing the function demand information positioned at the first position in the function release sequence to generate an intermediate product.

It can be understood that, the service cluster that processes the function requirement information located at the first position in the function release sequence is the first scheduled service cluster, the main cluster sends a scheduling instruction and application development requirement information to the service cluster that is in the idle state according to the function release sequence, and the first development unit 001 of the service cluster processes the function requirement information located at the first position in the function release sequence to generate the first intermediate product.

The first transmission unit 002: and sending the intermediate product to a designated service cluster according to an intermediate product transmission instruction sent by the main cluster, so that the designated service cluster processes the next adjacent function requirement information in the function release sequence.

It can be understood that, when the first intermediate product in the first development unit 001 is developed, the service cluster receives an intermediate product transmission instruction from the first development unit, and the first transmission unit 002 sends the first intermediate product and the application development requirement information to a designated service cluster, and the designated service cluster processes the function requirement information located at the second position in the function release sequence on the basis of the first intermediate product, so as to generate a second intermediate product.

As can be seen from the above description, in the service cluster provided in the embodiment of the present application, the main cluster sequences a plurality of function requirement information in application development requirement information to obtain a function release sequence, and schedules the service clusters one by one according to the function release sequence, so that the service clusters can be utilized to the maximum extent, and the whole service cluster can process a plurality of application development requirement information simultaneously.

In order to further improve the development efficiency of the whole service cluster and overall workload of the service clusters, in an embodiment of a service cluster provided in the present application, a manner of iterative development of application requirements is provided, and referring to fig. 10, an application development module 21 of a service cluster that is not the first scheduled service cluster specifically includes the following contents:

receiving unit 003: and receiving the intermediate product sent by the last designated service cluster, and an intermediate product transmission instruction and a function issuing sequence sent by the main cluster.

Second development unit 004: and processing the function requirement information to be processed currently in the function release sequence, and generating an integrated intermediate product on the basis of the intermediate product sent by the last service cluster.

The second transmission unit 005: transmitting the integrated intermediate product to a next designated service cluster based on the intermediate product transmission instruction; and if the next appointed service cluster is the last scheduled service cluster, outputting the final application by the next appointed service cluster.

In some specific embodiments, a service cluster provided in the present application, an application development module of the service cluster includes: a receiving unit, a development unit and a transmission unit. The receiving unit of the first scheduled service cluster is used for receiving the application demand development information and the function development sequence transmitted by the main cluster, and the receiving units of other scheduled service clusters are used for receiving the intermediate products and the function development sequences transmitted by the last service cluster; the transmission unit of the last scheduled service cluster transmits the developed end-use product to the client device, whereas the transmission unit of the non-tail scheduled service clusters transmits the developed intermediate product to the next service cluster.

In order to ensure the safety of the software development process, the business works of different categories are isolated from each other, the application provides an embodiment of a cross-cluster remote continuous release device based on federal implementation, and referring to fig. 11, the cross-cluster remote continuous release device specifically includes the following contents:

A master cluster: and receiving at least one piece of application development requirement information and the workload condition information transmitted by all the service clusters, and scheduling each service cluster according to the workload condition information transmitted by all the service clusters.

The user submits the configuration requirement for describing the service cluster to the main cluster, and the Master node processor provides the operable service cluster, and the Master component of the service cluster is complete, and only the capacity-expanding workbench node is needed in the follow-up.

A Waker node processor is deployed in the service cluster and is responsible for managing the lifecycle of the Woker node. When a certain workbench node needs to be expanded, only the configuration requirement of the workbench node needs to be submitted, and the workbench node processor initializes the workbench node and adds the workbench node to the service cluster.

The Master node processor is configured to monitor a state change of the service cluster (the service cluster state is automatically generated by the Master node processor), so that all Master components of the service cluster reach a target state.

As can be seen from the above description, the cross-cluster remote persistent publishing device based on federal implementation provided in the embodiments of the present application determines how to distribute workload among different clusters according to workload conditions of each service cluster by using a multi-cluster management mode, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved. As can be seen from the above description, according to the federal implementation-based cross-cluster remote persistent publishing method provided by the embodiments of the present application, through a multi-cluster management mode, a main cluster decides how to distribute workload among different clusters according to workload conditions of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved.

In order to ensure the safety of the software development process in terms of hardware, the business works of different categories are mutually isolated, and the application provides an embodiment of an electronic device for realizing all or part of contents in the cross-cluster remote continuous release method, wherein the electronic device specifically comprises the following contents:

fig. 13 is a schematic block diagram of a system configuration of an electronic device 9600 of an embodiment of the present application. As shown in fig. 13, the electronic device 9600 may include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 13 is exemplary; other types of structures may also be used in addition to or in place of the structures to implement telecommunications functions or other functions.

In an embodiment, the cross-cluster remote persistent release function may be integrated into the central processor. Wherein the central processor may be configured to control:

As can be seen from the above description, in the electronic device provided in the embodiment of the present application, through a multi-cluster management mode, a main cluster determines how to allocate workloads in different clusters according to workload conditions of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved.

In another embodiment, the cross-cluster remote persistent publishing device may be configured separately from the central processor 9100, for example, the cross-cluster remote persistent publishing device may be configured as a chip connected to the central processor 9100, and the cross-cluster remote persistent publishing function is implemented under the control of the central processor.

As shown in fig. 13, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 need not include all of the components shown in fig. 13; in addition, the electronic device 9600 may further include components not shown in fig. 13, and reference may be made to the related art.

As shown in fig. 13, the central processor 9100, sometimes referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device, which central processor 9100 receives inputs and controls the operation of the various components of the electronic device 9600.

The memory 9140 may be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information about failure may be stored, and a program for executing the information may be stored. And the central processor 9100 can execute the program stored in the memory 9140 to realize information storage or processing, and the like.

The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. The power supply 9170 is used to provide power to the electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, but not limited to, an LCD display.

The memory 9140 may be a solid state memory such as Read Only Memory (ROM), random Access Memory (RAM), SIM card, etc. But also a memory which holds information even when powered down, can be selectively erased and provided with further data, an example of which is sometimes referred to as EPROM or the like. The memory 9140 may also be some other type of device. The memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 storing application programs and function programs or a flow for executing operations of the electronic device 9600 by the central processor 9100.

The memory 9140 may also include a data store 9143, the data store 9143 for storing data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers of the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, address book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. A communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, as in the case of conventional mobile communication terminals.

Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, etc., may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and to receive audio input from the microphone 9132 to implement usual telecommunications functions. The audio processor 9130 can include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100 so that sound can be recorded locally through the microphone 9132 and sound stored locally can be played through the speaker 9131.

The embodiments of the present application further provide a computer readable storage medium capable of implementing all the steps in the cross-cluster remote persistent distribution method in the foregoing embodiments, where the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program implements all the steps in the cross-cluster remote persistent distribution method in which an execution subject in the foregoing embodiments is a server or a client, for example, the processor implements the following steps when executing the computer program:

As can be seen from the above description, in the computer readable storage medium provided in the embodiments of the present application, through a multi-cluster management mode, a main cluster decides how to allocate workloads in different clusters according to workload conditions of each service cluster, and assigns different tasks to different clusters. Task loads can be uniformly scheduled across clusters through cross-cluster scheduling; maximizing the workload of each cluster, and if the current cluster exceeds the bearing capacity, then the additional workload is routed to another more idle cluster; according to different application requirements, the workload is scheduled to different clusters to meet specific requirements of different end users. By cross-cluster scheduling, the resource availability of multiple clusters and platform resource management capability are improved.

It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principles and embodiments of the present invention have been described in detail with reference to specific examples, which are provided to facilitate understanding of the method and core ideas of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.

Claims

1. A federally implemented cross-cluster remote persistent distribution method, performed by a master cluster, comprising:

receiving at least one piece of application development requirement information and workload condition information transmitted by all business clusters, wherein the application development requirement information comprises a plurality of pieces of function requirement information;

according to the function release sequence, service clusters in an idle state are scheduled one by one to process each function requirement information one by one, and corresponding application modules are developed one by one, so that each service cluster processes the application development requirement information, and corresponding applications are developed;

the service clusters in the idle state are service clusters after the development load of all the functional requirements is released, and the service clusters in the idle state are scheduled one by one according to the functional release sequence, and the method comprises the following steps:

and executing iterative operation, scheduling another service cluster in an idle state, and instructing the other service cluster in the idle state to receive the intermediate product so that the other service cluster in the idle state processes the adjacent next function requirement information, and generating an integrated intermediate product until all the function requirements are processed.

2. A federally implemented cross-cluster remote persistent distribution method, performed by a service cluster in an idle state, comprising:

the main cluster receives at least one piece of application development requirement information and workload condition information transmitted by all business clusters, and then schedules each business cluster according to the workload condition information transmitted by all business clusters;

the application development requirement information comprises a plurality of pieces of function requirement information, the service cluster is a first scheduled service cluster, the main cluster generates a function release sequence according to the plurality of pieces of function requirement information, the application development requirement information is processed, and corresponding applications are developed, and the method comprises the following steps:

3. The cross-cluster remote persistent publishing method of claim 2, wherein the service cluster is a non-first scheduled service cluster, the processing the application development requirement information, developing a corresponding application, comprises:

4. A cross-cluster remote continuous release method based on federal implementation is characterized by comprising the following steps:

the method comprises the steps that a main cluster receives at least one piece of application development requirement information and workload condition information transmitted by all business clusters, wherein the application development requirement information comprises a plurality of pieces of function requirement information;

The main cluster generates a function release sequence according to the plurality of function requirement information, schedules one of the service clusters currently in an idle state according to the function requirement information positioned at the first position in the function release sequence, and transmits the function requirement information positioned at the first position to the service cluster in the idle state;

the service cluster in the idle state processes the function requirement information in the first position to generate an intermediate product;

the main cluster executes iterative operation, schedules another service cluster in an idle state, and instructs the other service cluster in the idle state to receive the intermediate product;

the other service cluster in the idle state processes the next adjacent function requirement information and generates an integrated intermediate product until all the function requirement processing is completed.

5. A primary cluster, the primary cluster comprising:

an information receiving module: receiving at least one piece of application development requirement information and workload condition information transmitted by all business clusters, wherein the application development requirement information comprises a plurality of pieces of function requirement information;

And a cluster scheduling module: scheduling each service cluster according to the workload status information transmitted by all the service clusters, so that each service cluster processes the application development demand information and further develops corresponding applications;

the cluster scheduling module comprises: cluster scheduling unit: according to the function release sequence, dispatching the service clusters in an idle state one by one to process the requirement information of each function one by one, and further developing corresponding application modules one by one;

the service clusters in the idle state are service clusters after the development load of all the functional demands is released, and the cluster scheduling unit schedules the service clusters in the idle state one by one according to the functional release sequence, and the method comprises the following steps:

6. A service cluster, the service cluster comprising:

the application development requirement information comprises a plurality of function requirement information, the service cluster is a first scheduled service cluster, the main cluster generates a function release sequence according to the plurality of function requirement information, and the application development module comprises:

7. The service cluster of claim 6, wherein the service cluster is a non-first scheduled service cluster, and wherein the application development module comprises:

8. A federally implemented cross-cluster remote persistent distribution system, comprising:

a master cluster: receiving at least one piece of application development requirement information and workload condition information transmitted by all business clusters, wherein the application development requirement information comprises a plurality of pieces of function requirement information;

performing iterative operation, scheduling another service cluster in an idle state, and instructing the other service cluster in the idle state to receive the intermediate product, so that the other service cluster in the idle state processes the next adjacent function requirement information, and generates an integrated intermediate product until all the function requirements are processed;

Service cluster: receiving a service cluster scheduling instruction sent by a main cluster and application development requirement information;

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the cross-cluster remote persistent distribution method of any of claims 1 to 4 when the program is executed by the processor.

10. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the cross-cluster remote persistent distribution method according to any of claims 1 to 4.