CN114020301A - System upgrading device and system upgrading method - Google Patents

Abstract

The application discloses a system upgrading device and a system upgrading method, wherein the system upgrading device comprises: an upgrade controller and at least one actuator; the upgrading controller is used for analyzing the dependency relationship of each actuator in the description file to obtain the execution sequence of each actuator, sequentially starting each actuator according to the execution sequence based on the execution state of the actuator started in the previous round, and monitoring the execution state of the started actuator; if the actuators started in the previous round are monitored to be executed successfully, starting the actuators in the next round; if any actuator started in the previous round fails to execute, the upgrading of the new architecture system is stopped; and the executor is used for upgrading the subsystem responsible in the new architecture system and feeding back the execution state. Therefore, an automatic system upgrading method is realized, the upgrading efficiency is improved, and the upgrading failure rate is reduced.

Description

System upgrading device and system upgrading method

Technical Field

The present disclosure relates to the field of system upgrading technologies, and in particular, to a system upgrading apparatus and a system upgrading method.

Background

With increasingly complex and bulky software, industrial internet platforms may consist of tens or even hundreds of microservices and operate in containerized environments.

In the process of continuous iteration of product versions, the technical architecture and data structure of the industrial internet platform system are continuously changed, so that the subsystems providing various services in the system need to be correspondingly upgraded.

Because the technical architecture and data structure of the system may send large changes, and the services are dependent on the requirements of sequential execution, the common software self-upgrading method is difficult to meet the upgrading requirements in such a scenario. Therefore, at present, upgrading operation is performed on each subsystem mainly in a manual mode based on the sequential execution requirements of services.

However, the mode of manually executing the upgrade process has high requirement on the level of the implementation personnel and is very easy to make mistakes, so the upgrade efficiency is relatively slow, and the upgrade failure rate is high.

Disclosure of Invention

Based on the defects of the prior art, the application provides a system upgrading device and a system upgrading method, so as to solve the problems of low efficiency and high recognition rate in the prior art.

In order to achieve the above object, the present application provides the following technical solutions:

a first aspect of the present application provides a system upgrade apparatus, including:

an upgrade controller and at least one actuator;

the upgrading controller is used for analyzing the dependency relationship of each actuator in the description file to obtain the execution sequence of each actuator, sequentially starting each actuator according to the execution sequence based on the execution state of the actuator started in the previous round, and monitoring the execution state of the started actuator; if the actuators started in the previous round are monitored to be executed successfully, starting the actuators in the next round; if any actuator started in the previous round fails to execute, the upgrading of the new architecture system is stopped;

and the executor is used for upgrading the subsystem responsible in the new architecture system and feeding back the execution state.

Optionally, in the system upgrading apparatus provided above, when the executor upgrades a subsystem in charge of the new architecture system and feeds back an execution state, the executor is configured to:

performing data statistics on the responsible subsystem to obtain a first statistical result;

upgrading database data of the responsible subsystem;

carrying out configuration file upgrading and system file upgrading on the responsible subsystem;

performing data statistics on the currently responsible subsystem to obtain a second statistical result;

judging whether the first statistical result is consistent with the second statistical result or not;

if the first statistical result is consistent with the second statistical result, feeding back an execution state of successful execution;

and if the first statistical result is inconsistent with the second statistical result, feeding back an execution state of execution failure.

Optionally, in the system upgrading apparatus provided above, the executor is further configured to:

and monitoring the running data in the upgrading process in real time, and generating a running log based on the running data.

Optionally, in the system upgrading apparatus provided above, the upgrade controller is further configured to:

and collecting the running log generated by the actuator, and displaying the running log.

Optionally, in the system upgrading apparatus provided above, the upgrade controller is further configured to:

and after monitoring that any one started actuator fails to execute, recording the reason of the failure to execute, and feeding back the reason of the failure to execute.

The second aspect of the present application provides a system upgrading method, which is applied to a system upgrading device, where the upgrading system includes an upgrading controller and at least one actuator, and the system upgrading method includes:

the upgrading controller obtains the execution sequence of each actuator by analyzing the dependency relationship of each actuator in the description file;

the upgrading controller starts a current target actuator and monitors the execution state of the current target actuator; wherein the current target actuator is the actuator of which the execution sequence is first in each actuator which is not started currently;

the current target executor updates the subsystem responsible in the new architecture system;

if the upgrading controller monitors that the target actuator fails to execute, the upgrading of the new architecture system is stopped;

and if the upgrading controller monitors that the target actuator is successfully executed, the upgrading controller returns to execute the current target actuator and monitors the execution state of the current target actuator until the actuator which is not started does not exist any more.

Optionally, in the above method for upgrading a system, the upgrading a subsystem in charge of a new architecture system by the current target executor includes:

the current target actuator carries out data statistics on the responsible subsystem to obtain a first statistical result;

the current target executor upgrades the database data of the responsible subsystem;

the current target executor carries out configuration file upgrading and system file upgrading on the responsible subsystem;

the current target actuator carries out data statistics on the current responsible subsystem to obtain a second statistical result;

the current target actuator judges whether the first statistical result is consistent with the second statistical result;

if the first statistical result is consistent with the second statistical result, the current target actuator feeds back an execution state of successful execution;

and if the first statistical result is inconsistent with the second statistical result, the current target actuator feeds back an execution state of execution failure.

Optionally, in the above method for upgrading a system, the obtaining, by the upgrade controller, an execution sequence of each actuator by analyzing a dependency relationship of each actuator in the description file includes:

the upgrading controller analyzes the dependency relationship of each actuator in the description file;

the upgrading controller generates a directed acyclic graph formed by the actuators based on the dependency relationship of the actuators;

and the upgrading controller determines the sequence of each actuator in the directed acyclic graph as the execution sequence of each actuator.

Optionally, in the method for upgrading a system described above, the method further includes:

the current target actuator monitors the operation data in the upgrading process in real time and generates an operation log based on the operation data.

Optionally, in the upgrade method of the above system, after the upgrade controller starts a current target actuator and monitors an execution state of the current target actuator, the method further includes:

and the upgrading controller collects the running log generated by the current target actuator and displays the running log.

The application provides a system upgrading device, which comprises an upgrading controller and at least one actuator. The upgrading controller is used for analyzing the dependency relationship of each actuator in the description file to obtain the execution sequence of each actuator, sequentially starting each actuator according to the execution sequence based on the execution state of the actuator started in the previous round, and monitoring the execution state of the started actuator. If the actuators started in the previous round are monitored to be executed successfully, starting the actuators in the next round; if any actuator started in the previous round fails to execute, the upgrading actuator of the new framework system is stopped to be used for upgrading the subsystem in charge in the new framework system, and the execution state is fed back, so that the system is automatically upgraded in sequence through the upgrading controller, the actuator and the description file, manual operation is not needed, one-key upgrading is achieved, the upgrading efficiency is effectively improved, and the upgrading failure rate is reduced.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a system upgrading apparatus according to an embodiment of the present disclosure;

fig. 2 is a flowchart of a method for upgrading a system according to an embodiment of the present application;

fig. 3 is a schematic diagram of a system upgrade stage according to an embodiment of the present application;

FIG. 4 is a flowchart of a method for obtaining an execution sequence of an actuator according to an embodiment of the present disclosure;

fig. 5 is a flowchart of a method for upgrading a subsystem according to an embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In this application, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

An embodiment of the present application provides a system upgrade apparatus, as shown in fig. 1, including:

an upgrade controller and at least one actuator.

It should be noted that the system upgrading apparatus provided in the embodiment of the present application further includes an important component: a file is described.

The description file at least includes the identifier of each actuator and the dependency relationship of each actuator, that is, information about which actuators and versions are formulated through the description file, and also records the dependency relationship among the actuators, that is, the serial or parallel execution relationship among the actuators. It should be further noted that the description file is also configured with execution parameters of each actuator, so as to configure the actuators.

The upgrade controller is essentially a pipeline coordinator and does not need to be changed frequently after the development is completed.

The upgrading controller is mainly used for analyzing the dependency relationship of each actuator in the description file to obtain the execution sequence of each actuator, sequentially starting each actuator according to the execution sequence based on the execution state of the actuator started in the previous round, and monitoring the execution state of the started actuator.

It should be noted that, since the actuators can be activated in parallel, a plurality of actuators may correspond to the same execution sequence, and each execution sequence corresponds to at least one actuator. After the upgrading controller starts the actuator, whether the execution state of the actuator is execution success or execution failure is mainly concerned, and details of operation are not concerned.

Specifically, if it is monitored that the actuators started in the previous round are executed successfully, the actuators in the next round are started. If any actuator started in the previous round fails to execute, the upgrading of the new architecture system is stopped, namely the whole upgrading process is finished.

It should be further noted that, when the upgrading controller starts the actuator, the upgrading controller starts the actuator according to the configuration information of the actuator in the description file.

Optionally, in order to quickly find the reason for the failure when the upgrade fails and adjust accordingly, in another embodiment of the present application, the upgrade controller is further configured to:

and after monitoring that any one started actuator fails to execute, recording the reason of the failure of the execution, and feeding back the reason of the failure of the execution.

The executor is mainly used for upgrading the subsystem responsible in the new architecture system and feeding back the execution state. Moreover, because the actuators are associated with each other, the resulting output value is assigned to a position according to convention so as to be used as an input of another actuator. Of course, the actuators that are butted against each other may be configured in advance in a butting manner.

Optionally, the executor includes a data statistics tool, a database data upgrade tool, a configuration file upgrade tool, a file upgrade tool, and a data integrity check tool.

The executor, when upgrading the subsystem in charge in the new architecture system, is used to: and carrying out data statistics on the responsible subsystems to obtain a first statistical result. And then, upgrading the database data of the responsible subsystem, and upgrading the configuration file and the system file of the responsible subsystem. And then, performing data statistics on the currently responsible subsystem again to obtain a second statistical result, and judging whether the first statistical result is consistent with the second statistical result so as to check the data integrity.

And if the first statistical result is consistent with the second statistical result, feeding back an execution state of successful execution. And if the first statistical result is inconsistent with the second statistical result, feeding back an execution state of the execution failure.

Optionally, in another embodiment of the present application, the actuator is further configured to:

and monitoring the running data in the upgrading process in real time, and generating a running log based on the running data.

Accordingly, in this embodiment of the present application, the upgrade controller is further configured to: and acquiring the running log generated by the actuator, and displaying the running log.

The system upgrading device provided by the embodiment of the application comprises an upgrading controller and at least one actuator. The upgrading controller is used for analyzing the dependency relationship of each actuator in the description file to obtain the execution sequence of each actuator, sequentially starting each actuator according to the execution sequence based on the execution state of the actuator started in the previous round, and monitoring the execution state of the started actuator. If the actuators started in the previous round are monitored to be executed successfully, starting the actuators in the next round; if any actuator started in the previous round fails to execute, the upgrading actuator of the new framework system is stopped to be used for upgrading the subsystem in charge in the new framework system, and the execution state is fed back, so that the system is automatically upgraded in sequence through the upgrading controller, the actuator and the description file, manual operation is not needed, one-key upgrading is achieved, the upgrading efficiency is effectively improved, and the upgrading failure rate is reduced.

Based on the system upgrading device provided above, an embodiment of the present application provides a system upgrading method, that is, the system upgrading method provided in the embodiment of the present application is applied to the system device described above, and the system device includes the audit controller and at least one actuator as described above, so as shown in fig. 2, the system upgrading method provided in the embodiment of the present application includes the following steps:

s201, the upgrading controller obtains the execution sequence of each actuator by analyzing the dependency relationship of each actuator in the description file.

When the system upgrade is started in step S201, the preparation work of the previous stage is also required.

The original system is stopped first and data backup is performed. Specifically, all external requests are intercepted at an entrance of the original system, timing tasks inside the system are stopped, and whether the original system has unprocessed data or not is detected. After determining that no unprocessed data exists, stopping the main business service, and only retaining data services, such as database services, file systems, configuration centers and the like.

Then, the system data of the original system is backed up, which may specifically include configuration files, database files, system files, configuration items, and the like. Then, installing and deploying a new architecture system, downloading a system upgrade device of a corresponding version and data into a network of the new architecture system, and executing step S201 when a user triggers a key to start upgrading.

Since there may be dependency between services of the system, there is a precedence relationship in the execution, so that the system upgrade may be divided into multiple stages as shown in fig. 3, for services that need to be executed successively, two stages that are executed successively are divided, and for services that can be executed simultaneously, the same stage may be performed simultaneously. Subsystems providing different services can be upgraded by different actuators, so that serial or parallel dependency exists among the actuators.

It should be noted that there may be multiple executors for one execution order, that is, multiple parallel executors correspond to the same execution order.

Optionally, in another embodiment of the present application, as shown in fig. 4, a specific implementation manner of step S201 includes the following steps:

s401, the upgrading controller analyzes the dependency relationship of each actuator in the description file.

It should be noted that, the analysis description file includes the dependency relationship of the executor, and also includes other information such as the version of the executor, so that the dependency relationship between the executors in the analysis description file needs to be analyzed.

S402, the upgrading controller generates a directed acyclic graph formed by the actuators based on the dependency relationship of the actuators.

Specifically, each actuator is taken as a node, nodes corresponding to actuators having dependency relationships are connected, and a connection line between two actuators having direct dependency relationships can be directed to a dependent actuator by the dependent actuator.

And S403, the upgrading controller determines the sequence of each actuator in the directed acyclic graph as the execution sequence of each actuator.

The order of each actuator in the directed acyclic graph represents the dependency relationship between the actuators, so the order of each actuator in the directed acyclic graph is the execution order of each actuator.

S202, starting the current target actuator by the upgrading controller, and monitoring the execution state of the current target actuator.

The current target actuator is the actuator which is arranged in the first execution sequence in the various actuators which are not started currently. The current target actuators are the respective actuators that need to be activated for the current round.

Since one execution order may correspond to a plurality of executors, the current target executor may include a plurality. And when a plurality of current target actuators exist, respectively starting each current target actuator, and detecting the execution state of each target actuator.

Wherein the execution state of the target executor includes an execution success and an execution failure.

Optionally, the description file may further include configuration information of the actuator, and at this time, the upgrade controller may perform parameter configuration on the current target actuator based on the configuration information of the actuator in the description file, and start the current target actuator.

And S203, the current target executor updates the subsystem responsible in the new architecture system.

Specifically, the current target executor updates the subsystem in charge of the new architecture system, and feeds back the execution state according to the execution condition.

It should be noted that, if there are a plurality of current target actuators, step S203 specifically updates the subsystem in charge of the architecture system for each current target actuator. Alternatively, the corresponding relationship between the actuator and the subsystem may be determined by the description file, or may be determined by the logic of the actuator itself or other means.

Optionally, the current target actuator may also output the execution result to the designated location so as to take its execution result as an input to the next actuator relied upon.

Optionally, in another embodiment of the present application, a specific implementation manner of step S203, as shown in fig. 5, includes the following steps:

s501, the current target actuator performs data statistics on the responsible subsystem to obtain a first statistical result.

And S502, the database data of the responsible subsystem is upgraded by the current target actuator.

And S503, the current target executor performs configuration file upgrading and system file upgrading on the responsible subsystem.

And S504, performing data statistics on the currently responsible subsystem by the current target actuator to obtain a second statistical result.

After each item of the subsystem is upgraded, data statistics is carried out on the upgraded subsystem again so as to check the integrity of the upgraded data.

And S505, judging whether the first statistical result is consistent with the second statistical result by the current target executor.

If the first statistical result is consistent with the second statistical result, it indicates that the upgrade is successful, so step S506 is executed at this time. If the first statistical result is inconsistent with the second statistical result, it indicates that the upgrade has failed and the data before and after the upgrade is not uniform, so step S507 is executed at this time.

Optionally, in another embodiment of the present application, when the front target executor updates a subsystem in charge of the new architecture system, the method further includes:

the current target executor monitors the running data in the upgrading process in real time and generates a running log based on the running data.

Accordingly, in another embodiment of the present application, after the upgrading controller starts the current target actuator and monitors the execution state of the current target actuator, the method further includes:

the upgrading controller collects the running logs generated by the current target actuator and displays the running logs so that a user can know the specific running process of the actuator.

And S506, feeding back an execution state of successful execution by the current target actuator.

And S507, feeding back an execution state of the execution failure by the current target actuator.

And S204, whether the upgrade controller monitors the successful execution of the current target actuator.

It should be noted that, in the implementation of the present application, the upgrade controller determines whether to activate the actuator of the next round according to the execution state of the actuator of the previous round, that is, whether to execute successfully.

Therefore, if the upgrade controller monitors the execution state of the current target actuator in real time, and thus monitors that the current target actuator is successfully executed, it indicates that the actuator in the next execution sequence can be started, so step S206 is executed at this time.

If the upgrade controller monitors that the current target actuator fails to execute by monitoring the execution state of the target actuator in real time, since there is a dependency relationship between the actuators, the subsequent predecessor cannot be normally executed at this time, and thus the inter-system upgrade cannot be performed, so that step S205 is executed at this time.

It should be noted that if there are multiple current target actuators, step S206 may be executed only if it is monitored that each current target actuator is executed successfully, and step S205 is executed if it is monitored that any one current target actuator is executed unsuccessfully.

And S205, stopping upgrading the new architecture system.

Because each actuator has a dependency relationship, the upgrading of the new architecture system cannot be completed only if any actuator fails to execute in the system upgrading process, so that the upgrading of the new architecture system can be stopped at the moment.

S206, the upgrading controller judges whether an actuator which is not started exists.

Since the current target actuator of the previous round is successfully executed, the next sequential actuator can be executed according to the execution sequence until no more unactuated actuators exist, and therefore whether the unactuated actuators exist is judged first.

If the upgrade controller determines that there is an unactivated actuator, the process returns to step S202. If it is determined that there are no more actuators that are not activated, all the actuators are executed, and the system is upgraded, so step S207 is executed.

And S207, determining to finish upgrading the new architecture system.

The embodiment of the application provides a system upgrading method which is applied to a system upgrading device. Then, the upgrade controller starts the current target actuator and monitors the execution state of the current target actuator. The current target actuator is the actuator which is arranged in the first execution sequence in the various actuators which are not started currently. And the started current target executor updates the subsystem responsible in the new architecture system. If the target actuator is monitored to be failed to execute, the upgrading controller stops upgrading the new architecture system, if the target actuator is monitored to be successfully executed, the current target actuator is returned to be started, the execution state of the current target actuator is monitored until the actuator which is not started does not exist any more, and therefore the automatic upgrading method is achieved based on the execution result of the last actuator according to the execution sequence, the upgrading efficiency is effectively improved, and the upgrading failure rate is reduced.

It is to be noted that the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus and methods according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the 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 (10)

1. A system upgrade apparatus, comprising:

an upgrade controller and at least one actuator;

the upgrading controller is used for analyzing the dependency relationship of each actuator in the description file to obtain the execution sequence of each actuator, sequentially starting each actuator according to the execution sequence based on the execution state of the actuator started in the previous round, and monitoring the execution state of the started actuator; if the actuators started in the previous round are monitored to be executed successfully, starting the actuators in the next round; if any actuator started in the previous round fails to execute, the upgrading of the new architecture system is stopped;

and the executor is used for upgrading the subsystem responsible in the new architecture system and feeding back the execution state.

2. The system upgrading device according to claim 1, wherein the executor is configured to upgrade a subsystem in charge of the new architecture system and feed back an execution status, and is configured to:

performing data statistics on the responsible subsystem to obtain a first statistical result;

upgrading database data of the responsible subsystem;

carrying out configuration file upgrading and system file upgrading on the responsible subsystem;

performing data statistics on the currently responsible subsystem to obtain a second statistical result;

judging whether the first statistical result is consistent with the second statistical result or not;

if the first statistical result is consistent with the second statistical result, feeding back an execution state of successful execution;

and if the first statistical result is inconsistent with the second statistical result, feeding back an execution state of execution failure.

3. The system upgrade apparatus according to claim 1, wherein the executor is further configured to:

and monitoring the running data in the upgrading process in real time, and generating a running log based on the running data.

4. The system upgrade apparatus according to claim 3, wherein the upgrade controller is further configured to:

and collecting the running log generated by the actuator, and displaying the running log.

5. The system upgrade apparatus according to claim 1, wherein the upgrade controller is further configured to:

and after monitoring that any one started actuator fails to execute, recording the reason of the failure to execute, and feeding back the reason of the failure to execute.

6. A system upgrading method is applied to a system upgrading device, the upgrading system comprises an upgrading controller and at least one actuator, and the system upgrading method comprises the following steps:

the upgrading controller obtains the execution sequence of each actuator by analyzing the dependency relationship of each actuator in the description file;

the upgrading controller starts a current target actuator and monitors the execution state of the current target actuator; wherein the current target actuator is the actuator of which the execution sequence is first in each actuator which is not started currently;

the current target executor updates the subsystem responsible in the new architecture system;

if the upgrading controller monitors that the target actuator fails to execute, the upgrading of the new architecture system is stopped;

and if the upgrading controller monitors that the target actuator is successfully executed, the upgrading controller returns to execute the current target actuator and monitors the execution state of the current target actuator until the actuator which is not started does not exist any more.

7. The method of claim 6, wherein the current target executor upgrades a subsystem responsible for in the new architecture system, comprising:

the current target actuator carries out data statistics on the responsible subsystem to obtain a first statistical result;

the current target executor upgrades the database data of the responsible subsystem;

the current target executor carries out configuration file upgrading and system file upgrading on the responsible subsystem;

the current target actuator carries out data statistics on the current responsible subsystem to obtain a second statistical result;

the current target actuator judges whether the first statistical result is consistent with the second statistical result;

if the first statistical result is consistent with the second statistical result, the current target actuator feeds back an execution state of successful execution;

and if the first statistical result is inconsistent with the second statistical result, the current target actuator feeds back an execution state of execution failure.

8. The method according to claim 6, wherein the obtaining, by the upgrade controller, the execution sequence of each actuator by parsing the dependency relationship of each actuator in the description file comprises:

the upgrading controller analyzes the dependency relationship of each actuator in the description file;

the upgrading controller generates a directed acyclic graph formed by the actuators based on the dependency relationship of the actuators;

and the upgrading controller determines the sequence of each actuator in the directed acyclic graph as the execution sequence of each actuator.

9. The method of claim 6, further comprising:

the current target actuator monitors the operation data in the upgrading process in real time and generates an operation log based on the operation data.

10. The method of claim 9, wherein after the upgrade controller activates a current target actuator and monitors an execution state of the current target actuator, further comprising:

and the upgrading controller collects the running log generated by the current target actuator and displays the running log.

Images