A management method, system and device

Abstract

The present invention discloses a management method, system and device, relating to the field of clusters. The execution commands corresponding to each sub-task after division are sequentially sent to non-management nodes to facilitate the execution of sub-tasks by non-management nodes; the first progress of the currently executed sub-task and the second progress of the main task are obtained through a task manager; the first progress and the second progress are displayed through a management page. In this application, the main task is divided into multiple sub-tasks through the task manager, and finally the first progress of the sub-task and the second progress of the main task are simultaneously displayed through the management page. The change speed of the first progress is higher than that of the second progress. Therefore, the displayed first progress can more easily enable users to clearly see the progress of the current task. The task progress display on the management page will not be not updated for a long time, nor will it mislead users into thinking that the task is stuck, enabling users to have a better evaluation of the product quality and improving the user experience.

Description

Technical Field

[0001] The present invention relates to the field of clusters, and in particular to a management method, system and device. Background Art

[0002] When the carrying capacity of storage products in a large-scale cluster is insufficient, it is possible to support expanding new nodes into the original cluster to enhance the carrying capacity. During the execution of the cluster node expansion task, various services need to be configured, and the overall task execution takes a certain amount of time. The interface will display the execution progress of the overall task in real time for the user. Currently, the task progress display is relatively rough, only showing the progress percentage of the overall task. When configuring some services, the configuration time of the overall task is usually long, and the task progress display on the interface will not be updated for a long time, misleading the user to think that the task is stuck, which to a certain extent affects the user's evaluation of the product quality and reduces the user experience. Summary of the Invention

[0003] The purpose of the present invention is to provide a management method, system and device, where the displayed first progress is more likely to enable the user to clearly see the progress of the current task, the task progress display on the management page will not be not updated for a long time, will not mislead the user to think that the task is stuck, enabling the user to have a better evaluation of the product quality and improving the user experience.

[0004] To solve the above technical problems, the present invention provides a management method applied to a processor in a management node. The management method includes:

[0005] When receiving a configuration instruction for a new non-management node, adding the main task corresponding to the configuration instruction to a task manager pre-installed in the management node;

[0006] Dividing the main task into multiple subtasks by the task manager according to a pre-stored task division template;

[0007] Sequentially sending the execution commands corresponding to each of the divided subtasks to the non-management node so that the non-management node can execute the subtasks;

[0008] Obtaining, by the task manager, a first progress of the currently executed subtask and a second progress of the main task;

[0009] Displaying the first progress and the second progress through a management page.

[0010] Preferably, obtaining, by the task manager, a first progress of the currently executed subtask and a second progress of the main task includes:

[0011] Periodically obtaining, by the task manager, a first progress of the currently executed subtask and a second progress of the main task.

[0012] Preferably, obtaining the first progress of the currently executing subtask through the task manager includes:

[0013] Obtaining the steps that have been completed in the currently executing subtask and the first preset percentage corresponding to each of the steps;

[0014] Obtaining the first current progress percentage of the currently executing subtask according to the steps that have been completed in the currently executing subtask and the preset percentage corresponding to each of the steps;

[0015] Taking the first current progress percentage as the first progress.

[0016] Preferably, the process of obtaining the second progress of the main task includes:

[0017] Obtaining the steps that have been completed in the main task and the second preset percentage corresponding to each of the steps;

[0018] Obtaining the second current progress percentage of the main task according to the steps that have been completed in the main task and the second preset percentage corresponding to each of the steps;

[0019] Taking the second current progress percentage as the second progress of the main task.

[0020] Preferably, before adding the main task corresponding to the configuration instruction to the task manager pre-installed on the management node when a new configuration instruction for a non-management node is received, it further includes:

[0021] Determining whether the current management node is faulty;

[0022] If so, taking the standby management node as the new management node and entering the step of adding the main task corresponding to the configuration instruction to the task manager pre-installed on the management node when a new configuration instruction for a non-management node is received.

[0023] Preferably, the management page is a WEB Client.

[0024] Preferably, dividing the main task into multiple subtasks by the task manager according to a pre-stored task division template includes:

[0025] Obtaining the identification information of the main task;

[0026] Determining the type of the main task according to the identification information;

[0027] Through the task manager, dividing the main task into multiple subtasks based on the type of the main task according to the task division template.

[0028] Preferably, the identification information is a name and / or a number.

[0029] To solve the above technical problems, the present invention also provides a management system, including:

[0030] A processing unit, configured to add the main task corresponding to the configuration instruction to a task manager pre-installed on the management node when receiving a configuration instruction for a new non-management node;

[0031] A partitioning unit, configured to partition the main task into multiple subtasks by the task manager according to a pre-stored task partitioning template;

[0032] An execution command sending unit, configured to sequentially send the execution commands corresponding to each of the partitioned subtasks to the non-management node so that the non-management node can execute the subtasks;

[0033] A first progress and second progress obtaining unit, configured to obtain a first progress of the currently executed subtask and a second progress of the main task by the task manager;

[0034] Display the first progress and the second progress through a management page.

[0035] To solve the above technical problems, the present invention also provides a management device, including:

[0036] A memory, configured to store a computer program;

[0037] A processor, configured to execute the computer program to implement the steps of the above-mentioned management method.

[0038] The present application provides a management method, system and device. When receiving a configuration instruction for a new non-management node, add the main task corresponding to the configuration instruction to a task manager pre-installed on the management node; partition the main task into multiple subtasks by the task manager according to a pre-stored task partitioning template; sequentially send the execution commands corresponding to each of the partitioned subtasks to the non-management node so that the non-management node can execute the subtasks; obtain a first progress of the currently executed subtask and a second progress of the main task by the task manager; display the first progress and the second progress through a management page. By partitioning the main task into multiple subtasks through the task manager and finally simultaneously displaying the first progress of the subtask and the second progress of the main task through the management page, and the change speed of the first progress is higher than that of the second progress, so the displayed first progress is easier for the user to clearly see the progress of the current task, and the task progress display on the management page will not be updated for a long time, and will not mislead the user to think that the task is stuck, enabling the user to have a better evaluation of the product quality and improving the user experience. Description of the Drawings

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the attached drawings required in the prior art and the embodiments. Obviously, the attached drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other attached drawings can also be obtained based on these attached drawings.

[0040] Figure 1 It is a flowchart of a management method provided by the present invention;

[0041] Figure 2 It is a schematic structural diagram of a management device provided by the present invention. Specific embodiments

[0042] The core of the present invention is to provide a management method, system and device. The displayed first progress makes it easier for users to clearly see the progress of the current task. The task progress display on the management page will not be updated for a long time, and will not mislead users into thinking that the task is stuck, enabling users to have a good evaluation of the product quality and improving the user experience.

[0043] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the attached drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts fall within the scope of protection of the present invention.

[0044] Please refer to Figure 1 , Figure 1 It is a flowchart of a management method provided by the present invention. Applied to the processor in the management node, the method includes:

[0045] S11: When receiving a configuration instruction for a new non - management node, add the main task corresponding to the configuration instruction to the task manager pre - installed in the management node;

[0046] During the continuous operation of a large-scale cluster, as the production data increases day by day, the existing cluster may be restricted by various factors such as node scale and storage space. The operating load of the cluster becomes heavier and heavier, and it is unable to continue to provide stable and sustainable services. Therefore, the service capacity of the cluster can be improved by further expanding the cluster scale. Taking the storage product AS13000 as an example, it supports expanding new nodes into the original cluster and configuring corresponding services on the new nodes to enhance the overall service carrying capacity of the cluster. During the execution of the cluster node expansion task, various services need to be configured, and the overall task execution takes a certain amount of time. The interface will display the execution progress of the overall task for the user in real time. Currently, the task progress display is relatively rough, and the progress display jumps rather abruptly. When configuring some services, if the configuration takes a long time, the task progress display on the interface will not be updated for a long time, which will mislead customers into thinking that the task has frozen. This problem will affect the usability of the product and, to a certain extent, the overall evaluation of the product quality by users.

[0047] Therefore, this application proposes a management method that effectively solves the above problems. First, the nodes inside the cluster are divided into management nodes and non-management nodes. The number of management nodes is usually less than that of non-management nodes. When the processor of the management node receives a configuration instruction, it implements the configuration of the non-management nodes according to this instruction. First, when receiving a configuration instruction for a new non-management node, the main task corresponding to the configuration instruction is added to the task manager pre-installed on the management node. That is, when new expansion nodes are added to the cluster to expand the capacity or increase the carrying capacity, or to implement other new functions, that is, when new non-management nodes are added, when the processor of the management node receives this configuration instruction, it adds the main task corresponding to this configuration instruction to the task manager pre-installed on the management node so that the task manager can subsequently issue and execute this main task. The whole process is automated, improving the automation degree and feasibility of the solution.

[0048] It should be noted that the task manager only needs to be installed on the management nodes and does not need to be installed on the non-management nodes. The task manager is actually a software application. After installation, it can issue tasks or execute main tasks for other non-management nodes. The whole process is automated, improving the automation degree and feasibility of the solution.

[0049] The construction of the task manager uniformly manages and maintains the execution progress of each task in the cluster. At the same time, an automatic cleaning function for completed tasks is configured for the task manager to recycle the resources occupied by the completed tasks, which can save resources while executing the corresponding tasks and improve the feasibility of the solution, providing more space for other tasks or services to be executed.

[0050] S12: Divide the main task into multiple subtasks through the task manager according to the pre-stored task division template;

[0051] After the user issues a task through the management interface and adds it to the task manager. The task manager splits it according to the actual operation of the task, splits out independent subtasks, precisely divides each step of the task, and defines a progress percentage for each step to facilitate recording the actual progress of task execution. The process of dividing the main task into multiple subtasks through the task manager according to the pre-stored task division template is also automated. The pre-stored task division template here is not unique. According to the execution steps of the actual task, the corresponding task division template can be selected, that is, each type of main task may correspond to a way of dividing into subtasks, and this division method is pre-stored inside the task manager. That is, when installing this task manager, its internal already contains the task division template. Divide the main task according to the task division template to obtain the subtasks required by this solution. The whole process is automated, improving the efficiency and enhancing the reliability and feasibility of the solution.

[0052] It should be noted that the task division template is pre-stored inside the task manager, and there is no need to perform additional operation steps again when actually using this solution, improving the efficiency of the solution. According to the different main tasks, multiple different task division templates can be stored inside the processor of the management node, and then divide the task according to the task division template. At the same time, more task division templates can be obtained through real-time feedback according to the different main tasks, and then store more task division templates pre-stored inside the task manager, enabling this solution to continuously learn during actual use, so as to divide more main tasks and improve the flexibility and reliability of the solution.

[0053] S13: Send the execution commands corresponding to each divided subtask to the non-management nodes in sequence for the non-management nodes to execute the subtasks;

[0054] After splitting out independent subtasks, send the execution commands corresponding to each divided subtask to the non-management nodes in sequence for the non-management nodes to execute the subtasks. This process is the execution process of the subtasks, and the execution commands are sent to the non-management nodes in sequence so that the non-management nodes can execute the subtasks corresponding to the execution commands in sequence, facilitating the subsequent steps to obtain the current execution progress. The whole process is automated, improving the processing efficiency and automation degree of the solution.

[0055] In this solution, the task is first sent to the task manager of the management node. After the task is divided, the divided subtasks are sent to the non-management nodes. This allocation method of setting the management node and the non-management nodes makes the controllability of the solution better, and also facilitates management and task allocation, preventing the task allocation from becoming chaotic and disorderly, and improving the reliability of the solution.

[0056] S14: Obtain the first progress of the currently executing subtask and the second progress of the main task through the task manager;

[0057] After sending the execution instruction of the subtask to the non-management node, the subtask will start to execute, and there is a process during the execution. There is a current execution progress during the execution of each subtask, and there is also an execution progress for the main task. When the execution progress reaches 100%, it means that the task is completed at this time. The task manager will delete the completed task to reduce the resource occupancy of the task, improving the reliability and feasibility of the task.

[0058] The user issues a task through the management interface and adds it to the task manager. It needs to be split according to the actual operation of the task, splitting out independent subtasks, accurately dividing each step of the task, and defining the progress percentage for each step to facilitate recording the actual progress of the task execution. In addition, when obtaining the progress of a certain subtask, if it reaches 100%, it means that the progress of the task has been obtained at this time. Then the first progress obtained at this time is the progress of the next subtask. Since each subtask is executed by the non-management nodes in sequence, the task manager also obtains the first progress of each current subtask until all the subtasks to be executed in the solution are completed. After that, the acquisition of the first progress of the subtasks stops. At the same time, when all the subtasks are completed, the main task is also completed as a whole, so the acquisition of the progress of the main task also stops, improving the reliability of the solution. The whole process is automated, improving the reliability and feasibility of the solution.

[0059] S15: Display the first progress and the second progress through the management page.

[0060] Obtain the first progress of the currently executing subtask and the second progress of the main task through the task manager, that is, the main task added to the task manager, iteratively query the execution progress of the subtask, and update the execution progress of the overall task. Finally, from the user's perspective, it still needs to be implemented that the user can view the execution progress of the current main task and subtask. The user can view the specific execution progress of the task in real time through the management interface. The progress display on the management page includes the first progress of the currently executing subtask and the second progress of the main task. The prior art only displays the progress of the main task, does not divide the subtasks, and it is impossible to display the subtasks in real time. Therefore, this application adds the display of subtasks. On the one hand, the user can more carefully see the progress of the main task and subtasks. On the other hand, the user can also compare the main task and subtasks, and can see the task execution speeds of the main task and subtasks at the same time, which is better in the overall experience, improves the reliability and feasibility of the solution, and enhances the user experience.

[0061] The key point is that since the subtask is part of the main task, the speed of progress change of the subtask must be faster than that of the main task. Therefore, the user will no longer think that the progress of the subtask has stopped executing, and will no longer mislead the user into thinking that the current task has not been executed, improving the reliability of the solution and the user experience.

[0062] In addition, in order to further optimize the user experience, this application can also add a prompt module to prompt the user about the execution status of the current task. For example, it can prompt the user that a certain subtask has been completed or the main task has been completed. It can also give a prompt when the main task has completed a preset percentage. The preset percentage can be set according to the user's needs and actual situation. For example, when the execution progress of the main task reaches 50%, it prompts the user that the task has been completed halfway, etc., improving the feasibility of the solution and the user experience.

[0063] The prompt module can be but is not limited to a voice prompt module, a light prompt module, or a display module, etc., as long as it is reasonable and can give the user a prompt, increasing the flexibility of the solution, enhancing the user experience, and enabling the user to give a better usage evaluation.

[0064] Generally speaking, the present application provides a management method. When a configuration instruction for a new non-management node is received, the main task corresponding to the configuration instruction is added to the task manager pre-installed on the management node; the main task is divided into multiple sub-tasks by the task manager according to a pre-stored task division template; the execution commands corresponding to each divided sub-task are sequentially sent to the non-management node to facilitate the non-management node to execute the sub-task; the task manager obtains the first progress of the currently executed sub-task and the second progress of the main task; the first progress and the second progress are displayed through the management page. In the present application, the main task is divided into multiple sub-tasks by the task manager, and finally the first progress of the sub-task and the second progress of the main task are simultaneously displayed through the management page. The change speed of the first progress is higher than that of the second progress, so the displayed first progress is more likely to enable the user to clearly see the progress of the current task. The task progress display on the management page will not be updated for a long time and will not mislead the user into thinking that the task is stuck, enabling the user to have a good evaluation of the product quality and improving the user experience.

[0065] Based on the above embodiments:

[0066] As a preferred embodiment, obtaining the first progress of the currently executed sub-task and the second progress of the main task by the task manager includes:

[0067] The task manager periodically obtains the first progress of the currently executed sub-task and the second progress of the main task.

[0068] The manner of obtaining the first progress of the currently executed sub-task and the second progress of the main task by the task manager is specifically to periodically obtain the first progress of the currently executed sub-task and the second progress of the main task, that is, to update the first progress of the current sub-task and the second progress of the main task in real time. The obtained period can be changed according to the user's needs and actual usage conditions, improving the flexibility of the solution and the user experience.

[0069] Periodic obtaining is convenient to implement from the perspective of the processor, that is, to obtain in real time, so that the obtained progress is the real-time updated progress, improving the accuracy of the obtained progress.

[0070] As a preferred embodiment, obtaining the first progress of the currently executed sub-task by the task manager includes:

[0071] Obtain the currently executed steps of the currently executed sub-task and the first preset percentage corresponding to each step;

[0072] Obtain the first current progress percentage of the currently executed sub-task according to the currently executed steps and the preset percentage corresponding to each step.

[0073] Take the first current progress percentage as the first progress.

[0074] When obtaining the first progress of the currently executing subtask through the task manager, it can be obtained according to the specific execution situation of the current subtask. The execution of each subtask has multiple steps. A weight ratio for each step is set in advance. Since there may be relatively simple steps and relatively complex steps, a higher weight, that is, the first preset percentage, can be set for the complex steps, and a lower weight can be set for the relatively simple steps. Finally, after each step is completed, the percentage weight of this weight is accumulated with the weights of the previously completed steps, and finally the first current progress percentage of the currently executing subtask is obtained. Just take the first current progress percentage as the first progress. The whole process is automated, improving the automation level of the solution.

[0075] It should be noted that the weight division of this solution is very fine, specifically different steps have different weights, rather than directly dividing all steps with the same weight. And when dealing with complex steps, it takes longer time, so the method provided by this solution is more reasonable, improving the reliability of the solution.

[0076] As a preferred embodiment, the process of obtaining the second progress of the main task includes:

[0077] Obtain the currently completed steps of the main task and the corresponding second preset percentage for each step;

[0078] Obtain the second current progress percentage of the main task according to the currently completed steps and the corresponding second preset percentage for each step;

[0079] Take the second current progress percentage as the second progress of the main task.

[0080] When obtaining the second progress of the currently executing main task through the task manager, it can be obtained according to the specific execution situation of the current main task. The execution of each main task has multiple steps. A weight ratio for each step is set in advance. Since there may be relatively simple steps and relatively complex steps, a higher weight, that is, the second preset percentage, can be set for the complex steps, and a lower weight can be set for the relatively simple steps. Finally, after each step is completed, the percentage weight of this weight is accumulated with the weights of the previously completed steps, and finally the second current progress percentage of the currently executing main task is obtained. Just take the second current progress percentage as the second progress. The whole process is automated, improving the automation level of the solution.

[0081] As a preferred embodiment, before adding the main task corresponding to the configuration instruction to the task manager pre-installed on the management node when receiving the configuration instruction for the new non-management node, it further includes:

[0082] Determine whether the current management node is faulty;

[0083] If so, use the standby management node as the new management node and enter the step of adding the main task corresponding to the configuration instruction to the task manager pre-installed on the management node when receiving the configuration instruction for the new non-management node.

[0084] Deploy the task manager service on each management node in the cluster, which is responsible for uniformly managing various tasks added to the task manager, maintaining the basic information and execution progress of each task. Using the primary and standby disaster tolerance mechanism, the task information in each node's task manager is kept synchronized. When the primary node fails abnormally and the task fails and aborts, after the cluster primary node switches, it can replace the original primary node and continue to manage and maintain the tasks in the manager. During the task execution process, it can be determined in real time whether the current management node is faulty. If so, use the standby management node as the new management node. Usually, only one management node is actually used, but a standby management node can also be set. Once the management node in use has problems such as a fault, it is necessary to switch to the standby node in time for control to continue to complete the task execution of this solution. When a management node fault is found, the standby management node is automatically switched, and the whole process is automated, improving the reliability and feasibility of the solution.

[0085] As a preferred embodiment, the management page is a WEB Client.

[0086] The management page can be but is not limited to WEB Client. WEB Client is a relatively commonly used web page for users. This web page can implement the functions of the task manager based on the user's operations, can obtain and divide tasks, and send subtasks to non-management nodes to enable non-management nodes to execute subtasks. It can also be used as the display module of the user to display the second progress of the current main task and the first progress of the subtasks. This kind of WEB Client is convenient for user operation and data display, improving the reliability of the solution and the user experience.

[0087] As a preferred embodiment, the task manager divides the main task into multiple subtasks according to the pre-stored task division template, including:

[0088] Obtain the identification information of the main task;

[0089] Determine the type of the main task according to the identification information;

[0090] Through the task manager, the main task is divided into multiple subtasks according to the task division template based on the type of the main task.

[0091] It should be noted that dividing the main task into multiple subtasks through the task manager according to the pre-stored task division template specifically means that first, the identification information of the main task can be obtained, and then it is determined which type of task the main task belongs to according to the identification information. The task division template of the task manager can divide the task into subtasks based on the category of the task, that is, specifically what the task is, and the whole process is automated, improving the reliability of the solution.

[0092] As a preferred embodiment, the identification information is the name and / or number.

[0093] The identification information can be but is not limited to the name and / or number. The name or number usually has high reliability as the commonly used information characterizing the main task and can uniquely represent which main task it belongs to. Of course, other information that can uniquely represent the main task can also be selected as long as it is reasonable, improving the flexibility and reliability of the solution.

[0094] To solve the above technical problems, the present invention also provides a management system, including:

[0095] A processing unit, configured to, when receiving a configuration instruction of a new non-management node, add the main task corresponding to the configuration instruction to the task manager pre-installed on the management node;

[0096] A division unit, configured to divide the main task into multiple subtasks through the task manager according to the pre-stored task division template;

[0097] An execution command sending unit, configured to sequentially send the execution commands corresponding to each of the divided subtasks to the non-management node so that the non-management node can execute the subtasks;

[0098] A first progress and second progress acquisition unit, configured to acquire the first progress of the currently executed subtask and the second progress of the main task through the task manager;

[0099] The first progress and the second progress are displayed through the management page.

[0100] Among them, the first progress and second progress acquisition unit includes:

[0101] Periodically acquire the first progress of the currently executed subtask and the second progress of the main task through the task manager.

[0102] Among them, the first progress and second progress acquisition unit includes:

[0103] A first preset percentage acquisition unit, configured to acquire the currently executed steps of the subtask and the first preset percentage corresponding to each of the steps;

[0104] A first current progress percentage acquisition unit, configured to acquire a first current progress percentage of the currently executed subtask according to the currently executed steps and the preset percentage corresponding to each of the steps;

[0105] A first progress determination unit, configured to use the first current progress percentage as the first progress.

[0106] Among them, the first progress and second progress acquisition unit includes:

[0107] A second preset percentage acquisition unit, configured to acquire the currently executed steps of the main task and the second preset percentage corresponding to each of the steps;

[0108] A second current progress percentage acquisition unit, configured to acquire a second current progress percentage of the main task according to the currently executed steps and the second preset percentage corresponding to each of the steps;

[0109] A second progress determination unit, configured to use the second current progress percentage as the second progress of the main task.

[0110] Among them, before the processing unit, there is also:

[0111] A judgment unit, configured to judge whether the current management node fails, and if so, trigger a standby unit;

[0112] A standby unit, configured to use the standby management node as the new management node and, when receiving a configuration instruction for a new non-management node, add the main task corresponding to the configuration instruction to the steps of the task manager pre-installed on the management node.

[0113] Among them, the management page is a WEB Client.

[0114] Among them, the division unit includes:

[0115] An identification information acquisition unit, configured to acquire the identification information of the main task;

[0116] A main task type determination unit, configured to determine the type of the main task according to the identification information;

[0117] A subtask division unit, configured to divide the main task into multiple subtasks through the task manager according to the task division template based on the type of the main task.

[0118] Wherein, the identification information is a name and / or a number.

[0119] Please refer to Figure 2 , Figure 2 , which is a schematic structural diagram of a management device provided by the present invention.

[0120] To solve the above technical problems, the present invention also provides a management device, including:

[0121] A memory 1 for storing a computer program;

[0122] A processor 2 for executing the computer program to implement the steps of the above-mentioned management method.

[0123] For the introduction of the management device provided by this solution, please refer to the embodiments of the above management method, which will not be elaborated here.

[0124] It should also be noted that in this specification, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0125] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0126] The foregoing description of the disclosed embodiments enables those skilled in the art to practice or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A management method, characterized in that, Applied to the processor in the management node, the management method includes: When receiving a configuration instruction for a new non - management node, adding the main task corresponding to the configuration instruction to the task manager pre - installed in the management node; Dividing the main task into multiple subtasks by the task manager according to a pre - stored task division template; Sequentially sending the execution commands corresponding to each of the divided subtasks to the non - management node so that the non - management node can execute the subtasks; Obtaining the first progress of the currently executed subtask and the second progress of the main task through the task manager; Displaying the first progress and the second progress through the management page.

2. The management method according to claim 1, characterized in that, Obtaining the first progress of the currently executed subtask and the second progress of the main task through the task manager includes: Periodically obtaining the first progress of the currently executed subtask and the second progress of the main task through the task manager.

3. The management method according to claim 1, characterized in that, Obtaining the first progress of the currently executed subtask through the task manager includes: Obtaining the currently completed steps of the currently executed subtask and the first preset percentage corresponding to each step; Obtaining the first current progress percentage of the currently executed subtask according to the currently completed steps and the preset percentage corresponding to each step; Taking the first current progress percentage as the first progress.

4. The management method according to claim 1, characterized in that, The process of obtaining the second progress of the main task includes: Obtaining the currently completed steps of the main task and the second preset percentage corresponding to each step; Obtaining the second current progress percentage of the main task according to the currently completed steps and the second preset percentage corresponding to each step; Taking the second current progress percentage as the second progress of the main task.

5. The management method according to claim 1, characterized in that, Before adding the main task corresponding to the configuration instruction to the task manager pre - installed in the management node when receiving a configuration instruction for a new non - management node, it further includes: Judging whether the current management node is faulty; If so, taking the standby management node as the new management node and entering the step of adding the main task corresponding to the configuration instruction to the task manager pre - installed in the management node when receiving a configuration instruction for a new non - management node.

6. The management method according to claim 1, characterized in that, The management page is a WEB Client.

7. The management method according to any one of claims 1 to 6, characterized in that, Dividing the main task into multiple subtasks by the task manager according to a pre - stored task division template includes: Obtaining the identification information of the main task; Determining the type of the main task according to the identification information; Through the task manager, dividing the main task into multiple subtasks based on the type of the main task according to the task division template.

8. The management method according to claim 7, characterized in that, The identification information is a name and / or a number.

9. A management system, characterized in that, Includes: A processing unit, used for adding the main task corresponding to the configuration instruction to the task manager pre - installed in the management node when receiving a configuration instruction for a new non - management node; A dividing unit, used for dividing the main task into multiple subtasks by the task manager according to a pre - stored task division template; An execution command sending unit, configured to sequentially send execution commands corresponding to each of the divided subtasks to the non-management nodes so that the non-management nodes execute the subtasks; A first progress and second progress obtaining unit, configured to obtain a first progress of the currently executed subtask and a second progress of the main task through the task manager; The first progress and the second progress are displayed through a management page.

10. A management device, characterized in that, Comprising: A memory, configured to store a computer program; A processor, configured to execute the computer program to implement the steps of the management method according to any one of claims 1 to 8.

Images