A component coordination configuration method, device, terminal device and readable storage medium

Abstract

The present application is applicable to the field of cluster technology, and provides a component coordination configuration method, apparatus, terminal device and readable storage medium, the method comprising: based on the current business scenario of the target type component, determining at least one target coordination strategy that matches the target type component, and then coordinating and configuring the component parameters of the target type components in multiple clusters based on the target coordination strategy. The present application automatically coordinates and configures the target type components in multiple clusters based on the target coordination strategy, which can improve the component coordination efficiency and reduce the coordination operation and maintenance cost and error rate.

Description

Technical Field

[0001] The present application belongs to the field of cluster technology, and in particular, relates to a component coordination configuration method, apparatus, terminal equipment and readable storage medium. Background Art

[0002] With the continuous development of artificial intelligence (AI) technology, AI systems consume more and more resources, such as storage resources and computing resources. These resources are often distributed in different types of clusters, such as container orchestration engine (Kubernetes, K8s) cluster, Yet Another Resource Negotiator (YARN) cluster, etc.

[0003] In some cases, it is necessary to modify the parameters of the same components included in each cluster. As the number of clusters and the number of components within the clusters increase, the modification efficiency becomes lower and lower, and errors become more likely. Summary of the invention

[0004] The embodiments of the present application provide a component coordination configuration method, apparatus, terminal device and readable storage medium, which can improve the coordination efficiency and coordination accuracy of components in a cluster and reduce the coordination operation and maintenance costs.

[0005] In a first aspect, an embodiment of the present application provides a component coordination configuration method, the method comprising:

[0006] Acquire a current business scenario of a target type component, where the target type component is distributed in multiple clusters;

[0007] Based on the current business scenario, determining at least one target coordination strategy matching the target type component;

[0008] Based on the target coordination strategy, component parameters of the target type components in the multiple clusters are coordinated and configured.

[0009] In a second aspect, an embodiment of the present application provides a component coordination configuration device, the device comprising:

[0010] A scenario acquisition module, used to acquire the current business scenario of a target type component, where the target type component is distributed in multiple clusters;

[0011] A strategy determination module, configured to determine at least one target coordination strategy matching the target type component based on the current business scenario;

[0012] A coordination configuration module is used to coordinate and configure component parameters of the target type components in the multiple clusters based on the target coordination strategy.

[0013] In a third aspect, an embodiment of the present application provides a terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements a component coordination configuration method described in the first aspect above.

[0014] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the component coordination configuration method described in the first aspect above is implemented.

[0015] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on a terminal device, the terminal device executes a component coordination configuration method described in the first aspect above.

[0016] Compared with the prior art, the embodiments of the present application have the following beneficial effects: for target type components distributed in multiple clusters, the present application determines at least one target coordination strategy that matches the target type components based on the current business scenario of the target type components, and then automatically coordinates and configures the component parameters of the target type components in the multiple clusters based on the target coordination strategy, which can improve the component coordination efficiency and reduce the coordination operation and maintenance costs and error rates. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 It is a flowchart of a component coordination configuration method provided by an embodiment of the present application;

[0019] Figure 2 is a flowchart of a component coordination configuration method provided by another embodiment of the present application;

[0020] Figure 3 It is a flowchart of a component coordination configuration method provided by another embodiment of the present application;

[0021] Figure 4 It is a schematic structural block diagram of a component coordination configuration device provided by an embodiment of the present application;

[0022] Figure 5 It is a structural diagram of a terminal device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0023] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0024] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0025] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0026] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0027] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0028] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0029] Embodiment 1:

[0030] See also Figure 1 , Figure 1 A schematic flow chart of a component coordination configuration method provided in the present application is shown.

[0031] Step 101, obtaining the current business scenario of the target type component, where the target type component is distributed in multiple clusters.

[0032] Optionally, in order to improve user experience, multiple clusters can cooperate with each other to provide services to users, for example, multiple clusters can provide services to AI systems. The types of clusters in the multiple clusters can be the same or different. As an example but not a limitation, the multiple clusters can include clusters of types such as K8s clusters and YARN clusters.

[0033] Multiple clusters include target type components, for example, multiple clusters include storage components, network components and other types of components. There are certain dependencies between the target type components in multiple clusters. For example, when the component parameters of the target type components in a cluster are changed, the component parameters of the target type components in other clusters also need to be changed.

[0034] Optionally, obtaining the current business scenario of the target type component includes: obtaining the current business scenario of the target type component input by a user. As an example, before multiple clusters start to provide services, the user may input the business scenario currently corresponding to the target type component in the cluster.

[0035] As an example but not a limitation, target type components in multiple clusters can be applied to business scenarios such as ticket grabbing and video playback.

[0036] Step 102: Based on the current business scenario, determine at least one target coordination strategy that matches the target type component.

[0037] The target type component has different component parameters that need to be coordinated and configured in different business scenarios. For example, in business scenario A, the target type component has component parameters m that need to be coordinated and configured, and in business scenario B, the target type component has component parameters m and n that need to be coordinated and configured.

[0038] Different component parameters that need to be coordinated and configured have different corresponding coordination strategies. As an example, in a business scenario, a component parameter of a target type component can correspond to one or more coordination strategies.

[0039] Optionally, before determining at least one target coordination strategy that matches the target type component based on the current business scenario, the method also includes: based on component parameters required for the same type of components in different clusters in multiple business scenarios, constructing at least one coordination strategy corresponding to each business scenario to obtain a coordination strategy set.

[0040] For components of the same type in different clusters, at least one coordination strategy corresponding to the component of the same type is constructed in different business scenarios. The coordination strategy can be constructed by the user, or a strategy construction algorithm can be set and the coordination strategy can be constructed by the strategy construction algorithm.

[0041] In the above construction mode, different types of components correspond to a coordination strategy set, and the coordination strategy set includes coordination strategies corresponding to component parameters required by different types of components in different business scenarios.

[0042] In an optional embodiment, a coordination strategy may be constructed for each type of component to obtain a corresponding coordination strategy set, that is, for each type of component, a corresponding coordination strategy is constructed based on the component parameters required by the type of component in multiple business scenarios to obtain a coordination strategy set. In this construction method, one type of component corresponds to one coordination strategy set.

[0043] Optionally, based on the current business scenario, at least one target coordination strategy that matches the target type component is determined, including: based on the business scenario identifier, selecting at least one coordination strategy that matches the current business scenario from a coordination strategy set as the target coordination strategy; the coordination strategy set includes multiple coordination strategies, each coordination strategy corresponds to a preset business scenario identifier.

[0044] Optionally, a corresponding business scenario identifier may be added after each coordination strategy is constructed, or corresponding business scenario identifiers may be added to the coordination strategies in the coordination strategy set after the coordination strategy set is obtained.

[0045] After the current business scenario is acquired, the current business scenario may be compared with the business scenario identifier corresponding to the coordination strategy, and the coordination strategy having the same business scenario identifier as the current business scenario may be determined as the target coordination strategy.

[0046] Step 103: Coordinate and configure component parameters of target type components in multiple clusters based on the target coordination strategy.

[0047] Optionally, component parameters of target type components in multiple clusters can be monitored. When component parameters of target type components in multiple clusters need to be coordinated and configured, coordinated configuration can be performed based on the target coordination strategy. Coordinated configuration can also be performed based on the target coordination strategy when component parameters of target type components in one or more clusters change.

[0048] In an optional implementation, the component parameters of the target type components in each cluster can be directly monitored through the long connection channel between each cluster. In another optional implementation, the component parameters can be stored in middleware such as the relational database MySQL and the distributed application coordination service ZooKeeper, and then the component parameters of the target type components in multiple clusters can be monitored through the middleware.

[0049] The target coordination strategy can be understood as an abstraction of the coordination method. The target coordination strategy can include the effective range of characteristic parameters, component parameter configuration rules, and resource configuration rules. The effective range of characteristic parameters can be used to indicate that a certain characteristic parameter is enabled in certain clusters and disabled in other clusters. The component parameter configuration rules can be used to indicate the parameter type of the component parameters of the target type component in each cluster. For example, a certain webhook parameter is configured for the target type component in the k8s cluster, and another webhook parameter is configured for the target type component in the yarn cluster. The resource configuration rules can be used to indicate the allocation of physical machine resources according to the available physical machine resources of the target type component in each cluster.

[0050] For example, if the target coordination strategy includes the effective range of characteristic parameters, and the effective range of characteristic parameters stipulates that the component parameter m of the target type component can only be enabled in one cluster, and there are three clusters A, B, and C, and the component parameter m of the target type component has been enabled in cluster B, the coordination configuration process is as follows:

[0051] After detecting that the component parameter m of the target type component in cluster A is enabled or after detecting an instruction to enable the component parameter m of the target type component in cluster A, the component parameter m of the target type component in cluster A can be turned on and the enabled component parameter m in cluster B can be turned off according to the target coordination strategy.

[0052] For target type components distributed in multiple clusters, the present application determines at least one target coordination strategy that matches the target type components based on the current business scenario of the target type components, and then automatically coordinates and configures the component parameters of the target type components in the multiple clusters based on the target coordination strategy, which can improve the component coordination efficiency and reduce the coordination operation and maintenance costs and error rates.

[0053] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0054] Embodiment 2:

[0055] See also Figure 2, Figure 2 A schematic flow chart of a component coordination configuration method provided in the present application is shown.

[0056] Step 201, obtaining the current business scenario of the target type component, where the target type component is distributed in multiple clusters.

[0057] Step 202: Based on the current business scenario, determine at least one target coordination strategy that matches the target type component.

[0058] For the relevant contents in step 201-step 202, reference can be made to the relevant description in step 101-step 102, which will not be repeated here.

[0059] Step 203: Coordinate and configure component parameters of target type components in multiple clusters based on the target coordination strategy.

[0060] In order to improve the efficiency of coordination configuration, coordination configuration instructions corresponding to target type components in multiple clusters may be determined based on the target coordination strategy.

[0061] Optionally, based on the target coordination strategy, component parameters of target type components in multiple clusters are coordinated and configured, including: based on the target coordination strategy, determining expected component parameters of target type components in multiple clusters; generating coordination configuration instructions based on the expected component parameters of target type components in multiple clusters; and sending coordination configuration instructions to multiple clusters so that the multiple clusters respectively coordinate and configure the component parameters of the target type components included therein.

[0062] For example, if the target coordination strategy includes the effective range of characteristic parameters, and the effective range of characteristic parameters stipulates that the component parameter m of the target type component can only be enabled in one cluster, and there are three clusters A, B, and C, and the component parameter m of the target type component has been enabled in cluster B, the coordination configuration process is as follows:

[0063] After detecting that the component parameter m of the target type component in cluster A is enabled or after detecting an instruction to enable the component parameter m of the target type component in cluster A, based on the effective range of the characteristic parameters, it can be determined that the coordination configuration instruction of the target type component in cluster A is to enable component parameter m, and the coordination configuration instruction of the target type component in cluster B is to disable component parameter m; the coordination configuration instruction to enable component parameter m is sent to cluster A, and the coordination configuration instruction to disable component parameter m is sent to cluster B, so that cluster A and cluster B respectively configure the component parameters of the target type components contained therein based on the corresponding coordination configuration instructions.

[0064] As an example but not limitation, the target type component may be a storage component, which is used to store cluster data or component data. The content in a target coordination policy corresponding to the storage component may be the effective scope of the s3 gateway, for example, the s3 gateway of the storage component is configured only in one cluster. Based on this, after monitoring that a user configures the s3 gateway of the storage component in a cluster or after monitoring the instruction to configure the s3 gateway in a cluster, the coordination configuration instructions corresponding to each cluster can be determined based on the target coordination policy, so that each cluster can configure the s3 gateway based on the coordination configuration instructions.

[0065] As an example but not limitation, the target type component can also be a network component. The content in a target coordination strategy corresponding to a network component can be a resource configuration rule. For example, when the bandwidth pressure of a network component in a cluster is large, the physical machine resources corresponding to the network components with less bandwidth pressure in other clusters are called to balance the physical machine resources. Among them, the number of physical machines corresponding to multiple clusters is fixed. When scheduling physical machine resources, the scheduling of physical machine resources can be achieved by increasing or decreasing the number of physical machines corresponding to the network components.

[0066] Optionally, the number of physical machines to be increased or decreased may be set in advance in the resource configuration rules, or a scheduling algorithm may be set in the resource configuration rules, and the number of physical machines to be increased or decreased may be determined by the scheduling algorithm. The scheduling algorithm may determine the number of physical machines that need to be increased or decreased for the network components according to the bandwidth pressure of the network components in each cluster.

[0067] Optionally, generating the coordination configuration instruction includes: obtaining the priority of the target type component; determining a target number of coordination operation units based on the priority of the target type component; and generating the coordination configuration instruction through the target number of coordination operation units.

[0068] Optionally, generating the coordination configuration instruction includes: obtaining the priority of the current business scenario; determining a target number of coordination operation units based on the priority of the current business scenario; and generating the coordination configuration instruction through the target number of coordination operation units.

[0069] The priority of the target type component or the priority of the current business scenario may be predetermined by the user, and the higher the priority, the greater the number of coordinated computing units allocated.

[0070] By allocating a corresponding number of coordination computing units to different types of components or different business scenarios, it is possible to achieve a reasonable allocation of coordination computing resources, improve coordination speed, and ensure coordination efficiency.

[0071] The communication protocols corresponding to different clusters may be different. Therefore, in order to enable each cluster to receive the coordination configuration instruction, the coordination configuration instruction may be converted into a protocol.

[0072] Optionally, sending the coordination configuration instruction to the multiple clusters includes: performing protocol conversion on the coordination configuration instruction based on the communication protocol of each cluster to obtain a corresponding target configuration instruction; and sending the target configuration instruction to the multiple clusters.

[0073] Step 204 , obtaining current component parameters of target type components in multiple clusters after coordination configuration, and detecting whether the current component parameters meet expected component parameters corresponding to the target coordination strategy.

[0074] After the coordination configuration is completed, the current component parameters of the target type components in multiple clusters are obtained through the long connection channel, and compared with the expected component parameters corresponding to the target coordination strategy to determine whether the current component parameters are the same as the expected component parameters.

[0075] Optionally, if the target type component is a storage component, the corresponding component parameter may be the on / off state of the s3 gateway; if the target type component is a network component, the corresponding component parameter may be the number of physical machines.

[0076] The purpose of detecting whether the current component parameters meet the expected component parameters corresponding to the target coordination strategy is to detect whether the coordination configuration result reaches the expected result, thereby ensuring the accuracy of the coordination configuration.

[0077] Step 205 , when the current component parameters do not meet the expected component parameters, based on the target coordination strategy, the component parameters of the target type components in the multiple clusters are coordinated and configured again until the component parameters of the target type components in the multiple clusters meet the expected component parameters.

[0078] If the current component parameters do not meet the expected component parameters, it means that the current coordination was not successful. At this time, one or more coordination configurations need to be performed again until the component parameters of the target type components in multiple clusters meet the expected component parameters.

[0079] The process of performing the coordination configuration again one or more times is the same as the coordination configuration process in step 203, and will not be described again here.

[0080] After coordinating and configuring the component parameters of target type components in multiple clusters based on the target coordination strategy, the present application detects whether the current component parameters of the target type components in multiple clusters after the coordinated configuration meet the expected component parameters corresponding to the target coordination strategy, and if the current component parameters do not meet the expected component parameters, the component parameters of the target type components in multiple clusters are coordinated and configured again based on the target coordination strategy until the component parameters of the target type components in multiple clusters meet the expected component parameters. The present application determines whether the coordinated configuration achieves the expected coordination effect by comparing the current component parameters with the expected component parameters, thereby ensuring the accuracy of the coordinated configuration and the correct operation of the AI ​​system.

[0081] Embodiment three:

[0082] See also Figure 3 , Figure 3 A schematic flow chart of a component coordination configuration method provided in the present application is shown.

[0083] As an optional embodiment, in this embodiment, component parameters of target type components in each cluster stored in middleware such as MySQL and ZooKeeper are monitored, and the target number of coordination operation units is determined based on the priority of the current business scenario. Through the target number of coordination operation units, coordination configuration instructions are generated based on at least one target coordination strategy and then converted through protocol. The configuration instructions after coordination conversion are sent to N clusters respectively to coordinate and configure the N clusters.

[0084] After a coordinated configuration, component parameters fed back by N clusters can be obtained to confirm whether the coordinated configuration is effective. If not, coordination is continued based on at least one target coordination strategy until the component parameters fed back by the N clusters are the same as the expected component parameters.

[0085] The present application determines the number of coordinated computing units to achieve reasonable allocation of coordinated computing resources. Based on the component parameters fed back by N clusters, it can be confirmed whether the component parameters of the N clusters after coordinated configuration are the same as the expected component parameters, so as to ensure the successful coordination configuration of the target type components in the N clusters.

[0086] Embodiment 4:

[0087] See also Figure 4 , Figure 4 The schematic structure of a component coordination configuration device provided by the present application is shown. For the convenience of explanation, only the parts related to the embodiment of the present application are shown in the figure.

[0088] Reference Figure 4 The device includes a scene acquisition module 41, a strategy determination module 42 and a coordination configuration module 43; wherein the specific functions of each module are as follows:

[0089] A scenario acquisition module 41 is used to acquire the current business scenario of a target type component, where the target type component is distributed in multiple clusters;

[0090] A strategy determination module 42, configured to determine at least one target coordination strategy matching the target type component based on the current business scenario;

[0091] The coordination configuration module 43 is used to coordinate and configure component parameters of target type components in multiple clusters based on the target coordination strategy.

[0092] Optionally, the device also includes a set acquisition module, which is used to: before determining at least one target coordination strategy that matches the target type component based on the current business scenario, construct at least one coordination strategy corresponding to each business scenario based on component parameters required for the same type of components in different clusters in multiple business scenarios to obtain a coordination strategy set.

[0093] Optionally, the policy determination module 42 is specifically configured to:

[0094] Based on the business scenario identifier, at least one coordination strategy matching the current business scenario is selected from the coordination strategy set as the target coordination strategy; the coordination strategy set includes multiple coordination strategies, and each coordination strategy corresponds to a preset business scenario identifier.

[0095] Optionally, the coordination configuration module 43 is specifically used for:

[0096] Determine expected component parameters of target type components in multiple clusters based on the target coordination strategy;

[0097] generating coordination configuration instructions based on expected component parameters of target type components in the plurality of clusters;

[0098] A coordination configuration instruction is sent to the multiple clusters, so that the multiple clusters respectively coordinate and configure the component parameters of the target type components included therein.

[0099] Optionally, the coordination configuration module 43 is specifically used for:

[0100] Get the priority of the target type component;

[0101] Based on the priority, determine the target number of coordination operation units;

[0102] Generate coordination configuration instructions through the target number of coordination operation units.

[0103] Optionally, the coordination configuration module 43 is specifically used for:

[0104] Based on the communication protocol of each cluster, the coordination configuration instructions are converted into protocols to obtain the corresponding target configuration instructions;

[0105] Send targeted configuration instructions to multiple clusters.

[0106] Optionally, the device also includes a coordination detection module, which is used to: after coordinating and configuring the component parameters of the target type components in the multiple clusters based on the target coordination strategy, obtain current component parameters of the target type components in the multiple clusters after the coordinated configuration; detect whether the current component parameters meet the expected component parameters corresponding to the target coordination strategy; if the current component parameters do not meet the expected component parameters, based on the target coordination strategy, coordinate and configure the component parameters of the target type components in the multiple clusters again until the component parameters of the target type components in the multiple clusters meet the expected component parameters.

[0107] The above-mentioned component coordination configuration device provided in the embodiment of the present application can be applied in the aforementioned method embodiments 1 and 2. For details, please refer to the description of the above-mentioned method embodiments 1 and 2, which will not be repeated here.

[0108] Embodiment five:

[0109] See also Figure 5 , Figure 5 FIG. 5 shows a schematic structure of a terminal device provided by an embodiment of the present application. The terminal device 5 of this embodiment includes: at least one processor 50 ( Figure 5 Only one is shown), a memory 51, and a computer program 52 stored in the memory 51 and executable on the at least one processor 50, wherein the processor 50 implements the steps of a component coordination configuration method in the above-mentioned embodiments 1 and 2 when executing the computer program 52.

[0110] The terminal device 5 may be a computing device such as a computer, a physical server, or a cloud server. The terminal device 5 may include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art will appreciate that Figure 5 It is only an example of the terminal device 5 and does not constitute a limitation on the terminal device 5. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0111] The processor 50 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0112] In some embodiments, the memory 51 may be an internal storage unit of the terminal device 5, such as a hard disk or memory of the terminal device 5. In other embodiments, the memory 51 may also be an external storage device of the terminal device 5, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device 5. Further, the memory 51 may also include both an internal storage unit and an external storage device of the terminal device 5. The memory 51 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory 51 may also be used to temporarily store data that has been output or is to be output.

[0113] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0114] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0115] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0116] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device capable of carrying the computer program code to the terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electric carrier signal, a telecommunication signal and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0117] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0118] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0119] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0120] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0121] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A component coordination configuration method, characterized in that: The method comprises: Acquire a current business scenario of a target type component, where the target type component is distributed in multiple clusters; Based on the current business scenario, determining at least one target coordination strategy matching the target type component; Based on the target coordination strategy, component parameters of the target type components in the multiple clusters are coordinated and configured.

2. The method according to claim 1, characterized in that Before determining at least one target coordination strategy matching the target type component based on the current business scenario, the method further includes: Based on component parameters required by components of the same type in different clusters under multiple business scenarios, at least one coordination strategy corresponding to each of the business scenarios is constructed to obtain a coordination strategy set.

3. The method according to claim 1, characterized in that The determining, based on the current business scenario, at least one target coordination strategy matching the target type component comprises: Based on the business scenario identifier, at least one coordination strategy matching the current business scenario is selected from a coordination strategy set as the target coordination strategy; the coordination strategy set includes multiple coordination strategies, each of which corresponds to a preset business scenario identifier.

4. The method according to claim 1, characterized in that The step of coordinating and configuring component parameters of the target type components in the multiple clusters based on the target coordination strategy includes: Determining expected component parameters of the target type components in the plurality of clusters based on the target coordination strategy; generating coordination configuration instructions based on expected component parameters of the target type components in the plurality of clusters; The coordination configuration instruction is sent to the multiple clusters, so that the multiple clusters respectively perform coordination configuration on the component parameters of the target type components included therein.

5. The method according to claim 4, characterized in that The generating of the coordination configuration instruction comprises: Obtaining the priority of the target type component; Based on the priorities, determining a target number of coordination computing units; The coordination configuration instruction is generated by the target number of coordination operation units.

6. The method according to claim 4, characterized in that The sending the coordination configuration instruction to the multiple clusters includes: Based on the communication protocol of each of the clusters, performing protocol conversion on the coordination configuration instruction to obtain a corresponding target configuration instruction; The target configuration instruction is sent to the plurality of clusters.

7. The method according to any one of claims 1 to 6, characterized in that: After coordinating and configuring the component parameters of the target type components in the multiple clusters based on the target coordination strategy, the method further includes: Obtaining current component parameters of the target type components in the multiple clusters after coordinated configuration; detecting whether the current component parameters conform to the expected component parameters corresponding to the target coordination strategy; In the case that the current component parameters do not meet the expected component parameters, based on the target coordination strategy, the component parameters of the target type components in the multiple clusters are coordinated and configured again until the component parameters of the target type components in the multiple clusters meet the expected component parameters.

8. A component coordination configuration device, characterized in that: The device comprises: A scenario acquisition module, used to acquire the current business scenario of a target type component, where the target type component is distributed in multiple clusters; A strategy determination module, configured to determine at least one target coordination strategy matching the target type component based on the current business scenario; A coordination configuration module is used to coordinate and configure component parameters of the target type components in the multiple clusters based on the target coordination strategy.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images