CN117130629B

CN117130629B - A system upgrade method and computing device

Info

Publication number: CN117130629B
Application number: CN202310954144.XA
Authority: CN
Inventors: 郭健; 林培淳
Original assignee: XFusion Digital Technologies Co Ltd
Current assignee: XFusion Digital Technologies Co Ltd
Priority date: 2023-07-28
Filing date: 2023-07-28
Publication date: 2025-01-17
Anticipated expiration: 2043-07-28
Also published as: CN117130629A

Abstract

The embodiment of the application discloses a system upgrading method and computing equipment, wherein the method comprises the steps of responding to a system upgrading task of a management system comprising a plurality of subsystems, carrying out system upgrading on the subsystems in the management system, determining upgrading backspacing sequence according to upgrading sequence of each upgraded subsystem if an upgrading abnormal event is detected, carrying out backspacing processing on each upgraded subsystem according to the upgrading backspacing sequence, enabling system versions of each upgraded subsystem to be restored to system versions before system upgrading, operating the management system after successful upgrading if successful upgrading is determined, carrying out backspacing processing on the management system according to the whole backspacing sequence if abnormal system service occurs in the management system within a preset time period after operation, enabling the system versions of the management system to be restored to system versions before system upgrading, and guaranteeing consistency and system stability of the system versions of the management system in system upgrading.

Description

System upgrading method and computing device

Technical Field

The present application relates to the field of computer technologies, and in particular, to a system upgrade method and a computing device.

Background

System upgrades of the system can provide new functionality to the system and improve the user experience, while also repairing vulnerabilities and defects of the system, and thus are an important feature in the system. For a system including multiple subsystems, each subsystem included in the system needs to be upgraded in turn, but uncontrollable factors may generally occur in the upgrading process of the subsystem, so that the subsystem upgrade failure may not be processed temporarily, and the subsystem whose upgrade has been completed cannot be rolled back, so that a subsystem whose system version is not matched exists in the system, and the system cannot be used normally in full quantity, so that the reliability of the system upgrade cannot be guaranteed effectively.

Disclosure of Invention

The embodiment of the application provides a system upgrading method and computing equipment, which can ensure the consistency of system versions and the system stability of a management system in system upgrading and effectively improve the reliability of system upgrading.

In a first aspect, an embodiment of the present application provides a system upgrade method, which may include:

In response to a system upgrade task for a management system comprising a plurality of subsystems, performing a system upgrade on subsystems in the management system;

If an upgrade abnormal event is detected, determining an upgrade backspacing sequence according to the upgrade sequence of each upgraded subsystem, and carrying out backspacing processing on each upgraded subsystem according to the upgrade backspacing sequence so as to restore the system version of each upgraded subsystem to the system version before system upgrade;

If the management system is successfully upgraded, the management system after the upgrade is successfully operated;

If the management system has abnormal system service in a preset time period after operation, carrying out rollback processing on the management system according to the whole rollback sequence so as to restore the system version of the management system to the system version before system upgrading.

In a second aspect, an embodiment of the present application provides a system upgrade apparatus, which may include:

An upgrade unit for performing a system upgrade for a subsystem in a management system including a plurality of subsystems in response to a system upgrade task for the management system;

The system comprises a rollback unit, a system version updating unit and a system version updating unit, wherein the rollback unit is used for determining an upgrade rollback sequence according to the upgrade sequence of each upgraded subsystem if an upgrade abnormal event is detected, and rollback processing is carried out on each upgraded subsystem according to the upgrade rollback sequence so as to restore the system version of each upgraded subsystem to the system version before the system upgrade;

The operation unit is used for operating the management system after the successful upgrade if the management system is determined to be successful in the upgrade;

and the rollback unit is further configured to, if the management system has a system service abnormality in a preset time period after operation, rollback the management system according to an overall rollback sequence, so that a system version of the management system is restored to a system version before system upgrade.

In a third aspect, embodiments of the present application provide a computing device comprising a processor configured to support the computing device to implement the functions referred to in the first aspect above. The computing device may also include a memory for coupling with the processor that holds the program instructions and data necessary for the computing device. The computing device may also include a network interface for the computing device to communicate with other devices or communication networks.

In a fourth aspect, embodiments of the present application provide a computer storage medium storing a computer program comprising program instructions for implementing the functions of the first aspect described above when executed by a processor.

In a fifth aspect, embodiments of the present application provide a computer program product comprising program instructions which, when executed by a computing device, enable the computing device to carry out the functions referred to in the first aspect above.

In a sixth aspect, the present application provides a chip system comprising a processor for supporting a computing device to implement the functions referred to in the first aspect above. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

The embodiment of the application can respond to the system upgrading task of the management system comprising a plurality of subsystems and carry out system upgrading on the subsystems in the management system, if an upgrading abnormal event is detected, the upgrading backspacing sequence can be determined according to the upgrading sequence of each upgraded subsystem, and backspacing processing is carried out on each upgraded subsystem according to the upgrading backspacing sequence, so that the system version of each upgraded subsystem is restored to the system version before the system upgrading, if the management system is successfully upgraded, the management system after the upgrading is successfully operated, if the management system is in a preset period after the operation, the management system can be backspacing processed according to the whole backspacing sequence, so that the system version of the management system is restored to the system version before the system upgrading, and in this way, the consistency of the system version and the system stability of the management system in the system upgrading can be ensured, so that the reliability of the system upgrading is effectively improved.

Drawings

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

FIG. 1 is a schematic diagram of an upgrade system according to an embodiment of the present application;

FIG. 2 is a schematic flow chart of a system upgrade method according to an embodiment of the present application;

FIG. 3a is a schematic diagram of a management system according to an embodiment of the present application;

FIG. 3b is a flow chart of a response to a system upgrade task provided by an embodiment of the present application;

FIG. 3c is a schematic flow chart of an upgrade process performed by a management system according to an embodiment of the present application;

FIG. 4 is a flowchart of another system upgrade method according to an embodiment of the present application;

FIG. 5a is a schematic diagram illustrating a comparison between an upgrade procedure and a rollback procedure according to an embodiment of the present application;

FIG. 5b is a schematic diagram illustrating a comparison between an upgrade procedure and a rollback procedure according to an embodiment of the present application;

FIG. 5c is an interface diagram of a system upgrade interface in a management system upgrade process according to an embodiment of the present application;

FIG. 5d is an interface diagram of an upgrade success interface after a management system is successfully upgraded according to an embodiment of the present application;

FIG. 5e is a schematic diagram of an interface of a submit prompt pop-up according to an embodiment of the application;

FIG. 5f is an interface schematic diagram of an upgrade details interface of a subsystem according to an embodiment of the present application;

fig. 5g is a schematic flow chart of a rollback process according to an embodiment of the present application;

FIG. 5h is a flowchart illustrating another system upgrade method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a system upgrade apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.

The embodiment of the application provides a system upgrading scheme, which has the following principles that if a system upgrading task aiming at a management system comprising a plurality of subsystems exists, the system can be upgraded for the subsystems in the management system, if an upgrading abnormal event is detected in the system upgrading, an upgrading backspacing sequence can be determined according to the upgrading sequence of each upgraded subsystem, and backspacing processing is carried out on each upgraded subsystem according to the upgrading backspacing sequence so as to restore the system version of each upgraded subsystem to the system version before the system upgrading, if the management system is successfully upgraded, the management system can be further operated after the upgrading is successfully upgraded, and if the management system is abnormal in system service in a preset time period after the operation, the backspacing processing can be carried out according to the whole backspacing sequence so as to restore the system version of the management system to the system version before the system upgrading.

By implementing the scheme, when the subsystem of the management system is abnormal in the upgrading process, the upgraded subsystem can be sequentially retracted according to the upgrading sequence of the subsystem, after the management system is integrally upgraded, whether the functions of the management system after the upgrading is successful are all available or not is observed through running the management system after the upgrading is successful, and under the condition that the functions are determined to be not fully available, the integral reverse sequence retraction can be performed according to the upgrading sequence of the subsystem, so that the consistency and the system stability of the system version of each subsystem in the management system are effectively ensured, and the user can continue to normally use the system. In addition, unified monitoring and management of upgrading and rollback processes of different subsystems in the management system can be realized, sequential rollback of multiple subsystems is supported, and operation and maintenance risks are effectively reduced.

In a specific implementation, the subject of execution of the system upgrade scheme mentioned above may be a computing device, including but not limited to a terminal or server. In other words, the computing device may be a server or a terminal, or may be a system formed by a server and a terminal. The above-mentioned terminal may be an electronic device, including, but not limited to, a mobile phone, a tablet computer, a desktop computer, a notebook computer, a palm computer, a vehicle-mounted device, an intelligent voice interaction device, an augmented Reality/Virtual Reality (AR/VR) device, and other mobile internet devices (mobile INTERNET DEVICE, MID) with network access capability, etc. The servers mentioned above may be independent physical servers, or may be server clusters or distributed systems formed by a plurality of physical servers, or may be cloud servers that provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, vehicle-road collaboration, content distribution networks (Content Delivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms.

When the computing device is a server, the embodiment of the application provides an upgrade system, as shown in fig. 1, the upgrade system may include at least one terminal and at least one server, the terminal may acquire a system upgrade task for a management system including a plurality of subsystems, and upload the acquired system upgrade task for the management system including the plurality of subsystems to the server (i.e., the computing device), so that the server may respond to the system upgrade task for the management system including the plurality of subsystems, and perform a system upgrade on the management system using a system upgrade scheme.

The implementation details of the technical scheme of the embodiment of the application are described in detail below:

based on the system upgrading scheme provided by the application, the embodiment of the application provides a system upgrading method. Referring to fig. 2, fig. 2 is a flow chart of a system upgrade method provided by an embodiment of the present application, which mainly uses a computing device as an execution body, where the system upgrade method may include the following steps:

S201, in response to a system upgrade task for a management system including a plurality of subsystems, performing a system upgrade for the subsystems in the management system.

The management system may be a system of a super fusion infrastructure (Hyper Converged Infrastructure, or simply referred to as "HCI"), for example, the management system may also be referred to as a super fusion system or a super fusion product, or the management system may also be another system including multiple subsystems, which is not limited thereto. The super fusion infrastructure refers to resources and technologies such as computation, network, storage, server virtualization and the like in the same set of unit equipment, and multiple sets of unit equipment can be aggregated through the network to realize modularized seamless lateral expansion (scale-out) so as to form a uniform resource pool.

In this case, the plurality of subsystems under the management system may include a subsystem (which may be referred to as a first subsystem) having a super-converged management service, a subsystem (which may be referred to as a second subsystem) composed of a host and a virtual machine having a virtualized management service deployed on the host, and the first subsystem may be used to provide the management service to the second subsystem. The host may refer to a physical server running virtualization software, and related technicians may create virtual machines on the host, where as for the management system, virtual machines with virtualization management services may be deployed on the host. In the embodiment of the present application, the management service may also be referred to as a management plane service, for example, the super fusion management service may be referred to as a super fusion management plane service, and the virtualized management service may be referred to as a virtualized management plane service.

It should be noted that, the super convergence management service and the virtualization management service in the management system may be deployed on the host, in one management system, the number of the super convergence management services may be one or more, and the virtualization management service may have a main service for the virtualization management service and a standby service for the virtualization management service. Different hyperfusion management services can be deployed on different hosts, and main services and standby services for the virtualization management services are also deployed on different hosts. It should be noted that the number of the main service and the standby service may be one or more, and when the total number of the main service and the standby service is smaller than the total number of the hosts involved in the management system, only the host may be involved in part of the second subsystem, that is, the virtual machine with the virtualized management service is not deployed on the host.

For example, referring to fig. 3a, if 3 hosts are involved in the management system, the super fusion management service may be deployed on 3 hosts (such as host 1, host 2, and host 3), respectively, and virtual machines for the main service and the standby service of the virtualization management service are deployed on different hosts (such as host 1 deploys a virtual machine for the standby service, and host 3 deploys a virtual machine for the main service). In the management system illustrated in fig. 3a, the general virtual machines (such as the general virtual machine 1, the general virtual machine 2, and the general virtual machine 3) may refer to virtual machines that provide other services, and unlike the virtual machine having the virtualization management service herein, the general virtual machine may also be referred to as a target virtual machine.

For fig. 3a, the subsystems in the management system may include a first subsystem composed of a super-converged management service deployed on 3 hosts, wherein the super-converged management service deployed on one host may be understood as a first subsystem, and may further include a second subsystem composed of a host 1 and a virtual machine with a virtualized management service (standby service) deployed on the host 1, a second subsystem composed of a host 2, and a second subsystem composed of a host 3 and a virtual machine with a virtualized management service (main service) deployed on the host 3.

The system upgrading task indicates to upgrade the management system, i.e. upgrade the system version of the management system.

In one implementation, when there is a system upgrade task for a management system including multiple subsystems, an initiating object (which may refer to any user) of the task initiation may initiate the system upgrade task through a computing device, so that the computing device may respond to the system upgrade task for the management system including multiple subsystems and perform subsequent operations. Alternatively, the computing device may output a task initiation interface to facilitate initiation of a system upgrade task for a management system comprising a plurality of subsystems by an initiating object performing a related operation at the task initiation interface. The task initiation interface may be displayed on a terminal screen of a terminal used by the initiation object, and the task initiation interface may specifically be an interface in a system upgrade platform. The computing device may be understood herein as a background service device of a system upgrade platform.

If the initiating object needs to upgrade a management system, a system upgrade platform on the used terminal can be logged in, and related operations can be executed on a task initiation interface in the system upgrade platform to send a system upgrade task for the management system comprising a plurality of subsystems to the computing device. For example, referring to fig. 3b, a task initiation interface may be displayed on a terminal screen of a terminal used to initiate an object, where the task initiation interface may include at least a setting area 301 for setting a system identifier of a management system to be upgraded and a confirmation control 302. If the initiating object wants to upgrade a management system, a system identifier corresponding to the management system may be set in the setting area 301, where the system identifier may be used to uniquely indicate a management system, then a trigger operation (such as clicking, pressing, etc.) may be performed on the confirmation control 302, after the terminal detects that the confirmation control 302 is triggered, a system upgrade task may be generated based on the information in the setting area 301, and the system upgrade task may be sent to the computing device, so that the computing device may respond to the system upgrade task for the management system including multiple subsystems.

In one implementation, the rules for system upgrades to the management system may be to upgrade the management service first, then upgrade the host (e.g., server software), and upgrade each upgrade object (e.g., management service or host) step-by-step or node-by-node in several upgrade steps. Then, for the management system including the first subsystem and the second subsystem, the first subsystem in the management system may be upgraded first, and after the upgrade of the first subsystem is completed, the second subsystem in the management system may be upgraded.

Based on this, the specific implementation of the system upgrade for the subsystem in the management system in step 201 may be that the software upgrade package corresponding to the first subsystem is obtained first to upgrade the system for the first subsystem by using the software upgrade package corresponding to the first subsystem, and after the system upgrade for the first subsystem is completed, the software upgrade package corresponding to the second subsystem may be obtained again to upgrade the system for the second subsystem by using the software upgrade package corresponding to the second subsystem.

The software upgrade package of each subsystem can be pre-stored in a storage area, so that when the management system is upgraded, the required software upgrade package can be directly obtained from the storage area. Alternatively, for a system upgrade performed by the system upgrade platform, the system upgrade platform may include a function related to upgrade package management, i.e., the upgrade package management may manage a software upgrade package required for managing each subsystem in the system.

Optionally, before the system upgrade is performed on the first subsystem, an inspection operation may be performed on the first subsystem, so as to ensure that the first subsystem may perform an upgrade process normally and reliably. If the service state of the first subsystem can be checked to determine that the super fusion management service corresponding to the first subsystem can normally provide services, for example, the configuration and version of the software upgrade package can be checked to ensure that the software upgrade package is normally available, if the first subsystem has a system warning, the system warning can be eliminated first to ensure normal operation of the upgrade, and other checking operations can be included, which are not limited. Similarly, before the second subsystem is upgraded, the second subsystem can be checked to ensure that the second subsystem can be upgraded normally and reliably.

For example, the flow of system upgrade to the management system may be seen in fig. 3 c. As shown in fig. 3c, a software upgrade package for the super fusion management service (i.e., the first subsystem) may be distributed first, and then the super fusion management service may be checked, and after the check is passed, a system upgrade may be performed on the super fusion management service using the distributed software upgrade package. After the super fusion management service is upgraded, a software upgrade package of the host and the virtualization management service (namely, the second subsystem) can be distributed, and the host and the virtualization management service can be checked; after the inspection is passed, the distributed software upgrade package can be used for carrying out system upgrade on the host and the virtualized management service, thereby completing the system upgrade of the management system.

It should be noted that, as described above, the host and the virtual machine with the virtualization management service deployed on the host may be involved in one second subsystem, and when the system upgrade is performed on the second subsystem, the system upgrade may be performed on the virtual machine with the virtualization management service on the host first, and after the system upgrade of the virtual machine with the virtualization management service is completed, the system upgrade may be performed on the host.

In one implementation, the number of the second subsystems may be one or more, where the number of the second subsystems is a plurality, and in a case where the number of the second subsystems is a plurality, the number of hosts involved in the management system is also a plurality, that is, the number of the second subsystems is the number of hosts, and if the number of the second subsystems is 3, the number of hosts is also 3. It should be noted that, when the number of hosts is plural, there is a corresponding upgrade order (or may be referred to as a host upgrade order) for performing a system upgrade on the plural hosts.

Alternatively, the host upgrade order of the plurality of hosts may be determined based on the backup service and the backup service for the virtualized management service deployed in the hosts of the plurality of second subsystems, in an embodiment, the host deployed with the backup service may be the first host to be upgraded, the host deployed with the main service may be the last host to be upgraded, and the upgrade order of the other hosts in the plurality of hosts is not limited and may be arranged in any manner. In general, the host upgrade order can be determined according to the existence of the management service and the main and standby services of the management service, and the host where the standby service with the virtualized management service is located is ensured to be upgraded first, and finally, the host where the main service with the virtualized management service is located is upgraded, and by the determination mode of the host upgrade order, the business service provided by the management system can be effectively ensured not to be interrupted in the process of main and standby switching in the system upgrade process. For example, assuming that the management system involves 3 hosts, host 1, host 2, host 3, and host 1 is deployed with a standby service and host 3 is deployed with a primary service, the upgrade order (from first to last order) of these 3 hosts may be host 1, host 2, host 3.

When the number of virtual machines having the virtualized management service is plural or when the number of the super fusion management service is plural, the virtual machines having the virtualized management service may be updated in the same order according to the existence of the simultaneous update, and the super fusion management service may be updated simultaneously. In the subsequent rollback process, virtual machines for a plurality of virtualized management services may also be rolled back simultaneously, and virtual machines for a plurality of superset management services may also be rolled back simultaneously.

It will be appreciated that for hosts that deploy both primary and backup services, one or more hosts may be included, and where multiple hosts are also present, the order of upgrades for the multiple hosts may be determined in a random manner or according to preset rules. In one embodiment, the preset rule may be a rule regarding a characteristic parameter of the host, for example, the characteristic parameter may be an importance level of the host, and the importance level may be preset. The upgrade order of the host may be in positive correlation with the importance level of the host, that is, if the importance level of the host is higher, the upgrade order of the host is more forward, and if the importance level of the host is lower, the upgrade order of the host is more backward. In this way, priority upgrade of the host with higher importance level can be ensured. For example, assuming that the order of importance levels of 3 hosts is host a, host B, and host C in order from high to low, the upgrade order of the 3 hosts is host a, host B, and host C in order.

S202, if an upgrade abnormal event is detected, an upgrade backspacing sequence is determined according to the upgrade sequence of each upgraded subsystem, and backspacing processing is carried out on each upgraded subsystem according to the upgrade backspacing sequence.

And the rollback processing is carried out on each updated subsystem so that the system version of each updated subsystem can be restored to the system version before the system is updated, thereby ensuring the consistency of the system version of each subsystem in the management system.

It will be appreciated that during an upgrade of each subsystem of the management system, there may be some risk of uncontrollability (or uncontrollability factor), such as during the upgrade of virtualized server software, there are often many uncontrollability factors to trigger the generation of upgrade exception events, which may result in a failure of a subsystem upgrade, while after a failure of one subsystem of the management system, a subsequent subsystem may not be able to perform a system upgrade, which may result in a system version of a portion of the subsystems of the management system being a system version after a system upgrade, a system version of a portion of the subsystems being a system version before a system upgrade, and a subsystem in a failure state (i.e., a subsystem that has failed upgrade). When an upgrade abnormal event occurs in the system upgrade, system versions of all subsystems in the management system are inconsistent, and due to the inconsistent system versions, instability of the whole management system can be caused, and the management system can not guarantee that a full amount of services are available, so that normal use of the management system by a user is affected. In order to ensure the consistency and the system stability of the system version of the management system, the updated subsystem can be rolled back, so that the user can continue to normally use the management system, and the time is strived for the abnormal upgrading condition to perform the abnormal elimination treatment.

Based on the consideration, after the upgrade abnormal event is detected, rollback processing can be performed on the management system in time so as to ensure that the system version of each subsystem in the management system is restored to the original system version. Because only part of the subsystems are upgraded at this time, rollback processing can be performed on only the subsystem which has completed the upgrade and the subsystem corresponding to the detected upgrade abnormal event, and the subsystem which has completed the upgrade and the subsystem corresponding to the detected upgrade abnormal event are understood as upgraded subsystems herein.

The upgrade rollback sequence for rollback processing the upgraded subsystems may be a reverse sequence (or a reverse sequence) of the upgrade sequence of the upgraded subsystems. For example, assuming that there are 3 subsystems in the management system, and the upgrade order of the 3 subsystems is subsystem 1, subsystem 2, and subsystem 3, if an upgrade abnormality event is detected in the system upgrade of subsystem 2, the subsystem 1 and subsystem 2 need to be rollback, and the upgrade rollback order of the two subsystems is subsystem 2 and subsystem 1.

As described above, in the process of upgrading the multiple subsystems of the management system, the first subsystem is upgraded and then the second subsystem is upgraded, so that an upgrade abnormal event can be detected in the process of upgrading the first subsystem or in the process of upgrading the second subsystem. When an upgrade abnormal event is detected in the upgrade process of the first subsystem, the first subsystem is required to be subjected to rollback processing, and when an upgrade abnormal event is detected in the upgrade process of the second subsystem, the second subsystem is required to be subjected to rollback processing, and after the second subsystem is subjected to rollback processing, the first subsystem is subjected to rollback processing.

And S203, if the management system is successfully upgraded, the management system after the upgrade is successfully operated.

It should be understood that in the process of upgrading a system of a management system for multiple subsystems, each subsystem will generally submit a project according to the subsystem, that is, after the system of one subsystem is upgraded, a commit triggering instruction may be initiated, where the commit triggering instruction may be completed by an initiating object triggering a commit control output on a system upgrade platform, after the commit triggering instruction is completed, it indicates that the subsystem is successfully upgraded, and after the commit triggering instruction is completed, a rollback or an upgrade cannot be performed on the subsystem. If a subsystem fails to upgrade and cannot be processed temporarily due to various uncontrollable factors, but the subsystem that has completed the upgrade cannot be rolled back again, there is a subsystem that is not matched with the version in the management system, or the system resources may not be fully used, i.e. the object cannot normally use the management system.

Considering that a subsystem directly initiates a commit triggering instruction after completing system upgrade, which may cause that after an upgrade exception event occurs subsequently, a rollback cannot be performed on a subsystem which has completed system upgrade, in the embodiment of the present application, delay is considered to initiate the commit triggering instruction. In the embodiment of the application, after each subsystem in the management system finishes upgrading, the upgrading project (or the initiation of the submitting trigger instruction) for the corresponding subsystem is not submitted in time, and after the upgrading of the single subsystem is successful, the upgrading data related to the system upgrading is not emptied temporarily, so that the subsystem which finishes upgrading in advance can be retracted when an abnormal upgrading event is detected in the process of upgrading the system. After all subsystems in the management system are upgraded, namely after the management system is successfully upgraded, the upgrade engineering for the management system is not submitted in time, and all upgrade data cannot be emptied, but a period of observation is given before all upgrade data are emptied, so that whether the functions of the management system are all available after the system is upgraded is observed. In other words, service operation test can be performed on the management system after the upgrade is successful in the observation period, if the service can be normally operated in the observation period, the function of the management system after the upgrade is determined to be available, the submission triggering instruction can be initiated, and if the service is abnormal in the observation period, the whole rollback can be performed on the management system.

Based on the above, after the management system is determined to be upgraded successfully, the management system after the upgrade is successfully run to determine whether to execute the operation of submitting the trigger instruction or execute the operation of rolling back the management system as a whole.

S204, if the management system has abnormal system service in the preset time period after operation, carrying out rollback processing on the management system according to the whole rollback sequence.

The rollback processing is performed on the management system, so that the system version of the management system can be restored to the system version before the system is upgraded, and the consistency of the system version of each subsystem in the management system is ensured.

The duration of the preset time period is not particularly limited, and may be, for example, 3 days, 5 days, or the like. The preset time period can also be understood as a commissioning period for the management system after the upgrade is successful, that is, the management system after the upgrade is run in the commissioning period, so as to determine whether the system service of the management system is normal in the commissioning period.

It can be understood that if the management system is abnormal in system service in the preset time period after operation, it indicates that some functions in the management system which is successfully upgraded are unavailable, so that resources of the management system cannot be fully used, and the system version of the management system can be returned to the system version before the system is upgraded, so that normal use of the management system is ensured, and normal use of users is not affected under the abnormal scene of the system upgrade.

Wherein the overall backoff sequence is determined based on an upgrade sequence when performing a system upgrade to a plurality of subsystems in the management system, and the overall backoff sequence may be a reverse sequence of the upgrade sequence. For example, assuming that there are 3 subsystems in the management system, and the upgrade order of the 3 subsystems is subsystem 1, subsystem 2, and subsystem 3, the upgrade and rollback order of the 3 subsystems for rollback processing is subsystem 3, subsystem 2, and subsystem 1. As described above, when the system is upgraded, the management service in the management system is upgraded first, and then the host in the management system is upgraded, and when the system is retracted, the host in the management system is retracted first, and then the management service in the management system is retracted. The subsystems in the management system relate to the first subsystem and the second subsystem, and based on the first subsystem and the second subsystem, the whole rollback sequence can be the first subsystem and the second subsystem. Therefore, in the embodiment of the application, the multi-subsystem can be backed back according to the reverse order of upgrading, so that the extra risk brought by uncontrollable factors of the multi-subsystem upgrading is reduced, and the consistency of the system version and the system stability of the multi-subsystem are ensured.

Based on this, the implementation of the rollback processing for the management system according to the overall rollback sequence in step S204 may be that the rollback processing is performed on the second subsystem in the management system to restore the system version of the second subsystem that has completed the upgrade to the system version before the system upgrade, and the rollback processing may be performed on the first subsystem in the management system after the second subsystem is successfully backed back to restore the system version of the first subsystem that has completed the upgrade to the system version before the system upgrade.

As described above, the second subsystem may relate to a host and a virtual machine deployed on the host and having a virtualized pipeline service, and when the management system is upgraded, the system upgrade is performed on the virtual machine having the virtualized pipeline service in the second subsystem, and after the upgrade is completed on the virtual machine having the virtualized pipeline service, the system upgrade is performed on all the hosts. Correspondingly, when the second subsystem is rolled back, rolling back is firstly carried out on all the hosts, and after the rolling back is completed on all the hosts, rolling back is carried out on the virtual machines with the virtualized management service deployed on the hosts.

In one implementation, if a system service exception does not occur in the management system within a preset period of time after operation, a commit trigger instruction may be initiated, which may be used to trigger a commit of an instruction indicating successful completion of a system upgrade task. Therefore, the embodiment of the application can ensure that after the management system is upgraded, if the system service abnormality (such as use problem) occurs in the operation within a preset time period, the system can be rolled back according to the upgrading sequence of the subsystems, the subsystems can be sequentially upgraded and rolled back in the reverse sequence, and the system version consistency and the function availability of each subsystem in the management system are ensured.

In the embodiment of the application, when the subsystem of the management system is abnormal in the upgrading process, the upgraded subsystem can be sequentially retracted according to the upgrading sequence of the subsystem, after the management system is integrally upgraded, whether the functions of the management system after the upgrading is successful are all available or not is observed by running the management system after the upgrading is successful, and under the condition that the functions are determined to be not fully usable, the integral reverse sequence retraction can be performed according to the upgrading sequence of the subsystem, thereby effectively ensuring the consistency and the system stability of the system version of each subsystem in the management system and ensuring that a user can continuously and normally use the system. In addition, unified monitoring and management of upgrading and rollback processes of different subsystems in the management system can be realized, sequential rollback of multiple subsystems is supported, and operation and maintenance risks are effectively reduced.

Fig. 4 is a flow chart of another system upgrade method according to an embodiment of the present application. The embodiment of the application mainly uses the computing equipment as an execution main body, and referring to fig. 4, the system upgrading method can comprise the following steps:

S401, in response to a system upgrade task for a management system comprising a plurality of subsystems, performing system upgrade on the subsystems in the management system.

The specific implementation of step S401 may refer to the description in step S201, which is not repeated here.

As described above, in the system upgrade of the management system, the system upgrade of the host is referred to, and the following description will specifically explain the flow of the system upgrade of the single host. For convenience of description, the following description will be made with reference to a target host in the management system, where the target host may refer to any host in the hosts included in the management system.

Specifically, a target check may be performed on the target host first, which may include a check of service status of the target host, a check of version and configuration of the software upgrade package, a check of system alarms, and the like. In the checking of the service state, the service state can comprise an unavailable state and an available state, the target host is determined to be not abnormal under the condition that the service state of the target host is the available state, the updated host is ensured to be a correct system version through the checking of the version and the configuration of the software upgrade package, the software upgrade package is a reliable upgrade package, the host can be ensured to be normally operated through the checking of a system alarm, and when the system alarm exists in the host, the subsequent operation can be executed after the system alarm is eliminated. The target inspection may also include other inspections, which are not limited.

After the target inspection is completed, whether the target host is deployed with the super fusion management service can be further determined, and under the condition that the target host is determined to be deployed with the super fusion management service, the super fusion management service can be migrated (or evicted) from the target host, so that when the system is upgraded, the service provided by the super fusion management service is not affected, and if the target host is not deployed with the super fusion management service, the migration step is not required to be executed. Then, the target host can be set to be in a state of being inoperable, namely, in the process of upgrading the system, the situation that the service is continuously executed on the target host, the upgrading is abnormal or the service is abnormal is avoided. Then, the target virtual machines (such as the above-mentioned common virtual machines) deployed on the target host can be migrated, and the target virtual machines are virtual machines for providing other business services, because in the system upgrade of the management system, the upgrade of the virtual machines is not involved, so as to ensure the normal use of the virtual machines, and when the target host is upgraded, the virtual machines can be migrated out of the target host.

Further, the target host may be upgraded, for example, the software upgrade package may be used to upgrade the system version of the target host. The method can also determine whether the virtual machine management service is deployed on the target host, and can perform active-standby switching processing on the virtual machine management service and restore the service of the target host under the condition that the virtual machine management service is deployed on the target host, and can directly restore the service of the target host without executing the switching step under the condition that the virtual machine management service is not deployed on the target host.

For example, referring to fig. 5a, the upgrade process of the target host may refer to the left process in fig. 5a, and as can be seen from the description of the upgrade process and the process described in fig. 5a, the upgrade process may involve a checking step of checking a service state, a migration step of migrating the super fusion management service (the host deployed with the super fusion management service needs to execute the step), a checking step of setting the host to be temporarily inoperable, a migration step of migrating a normal virtual machine on the host, an upgrade host step of upgrading the host with a software upgrade package, a switching step of performing active/standby switching on the virtualization management service (the host deployed with the virtualization management service needs to execute the step), and a restoration step of restoring the service of the host.

In summary, the embodiment of the application can automatically arrange the upgrade steps related to the upgrade process of the host, and in the upgrade process of a single host, the corresponding upgrade steps can be dynamically arranged according to whether the host contains the virtualized management service and the super-fusion management service and the related information of the host, so that the host can be upgraded smoothly, and the virtualized management service and the service provided by the super-fusion management service deployed on the host are not influenced in the process of ensuring the upgrade of the host.

It should be noted that, in the system upgrade of each subsystem in the management system, there is a corresponding upgrade order, and each subsystem is sequentially upgraded according to the corresponding upgrade order, and before one subsystem does not complete the upgrade, the next subsystem cannot be upgraded.

S402, if an upgrade abnormal event is detected, determining an upgrade backspacing sequence according to the upgrade sequence of each upgraded subsystem, and carrying out backspacing processing on each upgraded subsystem according to the upgrade backspacing sequence.

The upgrade rollback sequence for rollback processing the upgraded subsystems may be a reverse sequence of the upgrade sequence of the upgraded subsystems. For example, assuming that there are 4 subsystems in the management system, the upgrade order of the 4 subsystems is subsystem 1, subsystem 2, subsystem 3, and subsystem 4, and if an upgrade abnormality event is detected in the system upgrade of subsystem 3, the subsystem 1, subsystem 2, and subsystem 3 need to be rollback, and the upgrade rollback order of the two subsystems is subsystem 3, subsystem 2, and subsystem 1.

In view of the involvement of the host in the second subsystem and the deployment of virtual machines with virtualization management services on the host, an upgrade exception event may be detected during an upgrade of the host or at a virtual machine with virtualization management services. In the upgrading process, the virtual machine with the virtualization management service is upgraded firstly, then the host is upgraded, if an upgrading abnormal event is detected in the upgrading process of the host, the host needs to be rollback, and after the rollback of the host is completed, the virtual machine with the virtualization management service is rollback. However, if the upgrade anomaly event is detected in the virtual machine having the virtualization management service, only the rollback processing is required for the virtual machine having the virtualization management service, because the upgrade processing is not performed for the host, that is, there is no rollback processing for the host.

The following implementation of rollback processing for each subsystem that has been upgraded is specifically described in the case where an upgrade exception event is detected during an upgrade process for a host. The upgrade exception event may be detected by an exception occurring in a target upgrade step of a system upgrade to the host, which may be any upgrade step of upgrade steps included in the system upgrade process of the host. It will be appreciated that if an upgrade anomaly event is detected during an upgrade of a host, then there may be two cases where the currently upgraded subsystem includes a first subsystem, and where the upgraded subsystem includes the first subsystem and a second subsystem, rollback processing is described below.

In the case that the upgraded subsystem includes the first subsystem, the specific implementation of performing rollback processing on each upgraded subsystem according to the upgrade rollback sequence may include determining, based on the target upgrade step, a rollback step required for performing rollback processing on the host in the target second subsystem, and performing rollback processing on the host in the target second subsystem, if an upgrade exception event is detected in the target upgrade step of system upgrade on the host in the target second subsystem, and further determining, after the host in the target second subsystem successfully backs, whether a virtual machine with a virtualization management service is deployed in the target second subsystem, so as to determine whether the virtual machine with the virtualization management service needs to be rollback processed. And if the virtual machine with the virtualization management service in the target second subsystem is successfully returned, the virtual machine with the virtualization management service in the target second subsystem can be returned, and the updated first subsystem can be returned. If the target second subsystem does not have the virtual machine with the virtualized management service, the rollback processing of the virtual machine with the virtualized management service does not exist, and the rollback processing is directly carried out on the first subsystem which is completed with the upgrade.

Wherein the target second subsystem herein refers to any one of the second subsystems included in the management system.

In the case that the upgraded subsystem includes the first subsystem and the second subsystem, the implementation of performing rollback processing on each upgraded subsystem according to the upgrade rollback sequence may include determining, based on the target upgrade step, a rollback step required for performing rollback processing on the host in the target second subsystem and determining a rollback step required for performing rollback processing on the host in the upgraded second subsystem, if the upgrade exception event is detected in the target upgrade step of system upgrade on the host in the target second subsystem, and determining that only part of the upgrade is performed on the host (i.e., only part of the steps are performed during upgrade of the host, such as an exception upgrade event is detected during upgrade of the host), and that the host has completed the upgrade, determining that the rollback step required for performing rollback processing on the host in the target second subsystem and the rollback step required for performing processing on the host in the upgraded second subsystem are required, respectively.

After determining the rollback steps of the hosts in the two cases, rollback processing can be performed on the corresponding hosts based on the rollback steps of the hosts in the two cases respectively. Here, when performing rollback processing on the plurality of hosts, there is a corresponding rollback sequence, for example, the rollback processing may be performed on the hosts in the target second subsystem and the second subsystem that have completed upgrading, based on rollback steps required for performing rollback processing on the hosts in the target second subsystem and the second subsystem that have completed upgrading, in reverse order of the upgrade sequence of performing system upgrade on the target second subsystem and the second subsystem that has completed upgrading.

After the host in the target second subsystem and the updated second subsystem successfully backs, the virtual machine with the virtualized management service in the target second subsystem and the updated second subsystem can be further judged to determine whether the virtual machine with the virtualized management service needs to be backed up. If the target second subsystem and the virtual machine with the virtualized management service in the updated second subsystem are successfully returned, the virtual machine with the virtualized management service in the target second subsystem and the updated second subsystem can be returned, and the virtual machine with the virtualized management service in the updated second subsystem can be returned to the updated first subsystem. If the target second subsystem and the updated second subsystem do not have the virtual machine with the virtualized management service, the rollback processing can be directly performed on the updated first subsystem.

The rollback steps required for rollback processing of the host are specifically described below for both cases where the host has only completed a partial upgrade and where the host has completed an upgrade. In the case where the host completes only a partial upgrade, the required rollback step may be dynamically determined based on the upgrade step (e.g., the target upgrade step described above) in which an abnormality occurs during the upgrade of the host, i.e., the host may differ in the rollback step required to perform the rollback process. In the case that the host has completed the upgrade, the rollback steps required by the host to perform the rollback process are the same, and the stepwise rollback may be performed according to the upgrade steps of the host in the upgrade process. The following first describes the complete rollback steps involved in rollback processing by a host in the event that the host has completed an upgrade.

As previously described, the plurality of hosts may include hosts that deploy virtual machines for the primary service of the virtualization management service and hosts that deploy virtual machines for the backup service of the virtualization management service, and one or more hosts that deploy the superset management service. The host computer is provided with different management services, the host computer can also be distinguished in the rollback steps required by rollback processing, and in the rollback processing of a single host computer, the system can dynamically arrange the corresponding rollback steps according to whether the host computer contains the virtualized management service and the super fusion management service or not and the upgrade information of the host computer.

Optionally, the idea of automatically arranging the rollback step of the host may be to judge the basic step to be performed for rollback according to the upgrade information of the host, and arrange the corresponding processing step according to whether the host has the virtualized management service, and arrange the corresponding processing step according to whether the host has the superset management service. Wherein the upgrade information of the host may include a service status of the host, etc.

Based on this, the specific implementation of determining the rollback step required for performing the rollback processing on each of the plurality of hosts may be described as follows, and in consideration of the fact that the principle of determining the rollback step of any of the plurality of hosts is consistent, the following description will specifically discuss the determination of the rollback step by taking the target host as an example. Firstly, a reference rollback step required by rollback processing of a target host in a plurality of hosts can be determined, wherein the reference rollback step can be the basic step mentioned above, whether the target host is provided with a super fusion management service or not is further judged, if the target host is provided with the super fusion management service, a first processing step for executing migration of the super fusion management service can be added to the reference rollback step to obtain a rollback step required by rollback processing of the target host, whether the target host is provided with a virtualization management service or not can be judged, and if the target host is provided with the virtualization management service, a second processing step for executing main-standby switching processing of the virtualization management service can be added to the reference rollback step to obtain a rollback step required by rollback processing of the target host.

The reference rollback step may include a checking step of checking a service state of the target host, a setting step of setting the target host to be temporarily inoperable to set a service of the target host to be in an unavailable state, a migration step of migrating a target virtual machine (a general virtual machine) on the host, a rollback host step of restoring a system version of the target host to a system version before system upgrade, and a restoration step of restoring the service of the target host.

Based on the above description of the rollback procedure of the target host, in one implementation manner, the rollback procedure may be implemented by first checking the service state of the target host, further determining whether the target host is deployed with the superstration management service after checking that the service state is the target service state (i.e., the available state), if the target host is deployed with the superstration management service, migrating the superstration management service on the target host, then, may take the service of the target host as an unavailable state, migrate the virtual machine deployed on the target host for providing the service, and restore the system version of the target host to the system version before the system upgrade, then, may determine whether the target host is deployed with the virtualization management service, if the target host is deployed with the virtualization management service, may perform the active-standby switching processing on the virtualization management service, and finally, may restore the service of the target host.

For example, referring to FIG. 5a, the upgrade procedure for a single host may be as shown in the left flow in FIG. 5a, and the rollback for a single host may be as shown in the right flow in FIG. 5 a. If the host performs the rollback processing on the host after the system upgrade is completed, the flow of the rollback processing corresponding to the host may be shown by referring to the flow on the right side in fig. 5a, that is, the host may rollback step by step according to the upgrade step of the host in the system upgrade process.

As another example, referring to fig. 5b, the upgrade procedure for a single host may be as shown in the left flow in fig. 5b, and the rollback for a single host may be as shown in the right flow in fig. 5 b. In the upgrading process of the host, if an abnormality occurs in a certain upgrading step, when the host is in rollback processing, the rollback step involved does not stepwise rollback according to the upgrading step in the upgrading processing, but identifies the upgrading step in which the abnormality occurs, and dynamically judges the specific rollback operation to be completed when the rollback processing is performed according to the upgrading step. For example, assuming that an exception (error) occurs in the upgrade step of the "upgrade host" in the left flow in fig. 5b, the rollback operation corresponding to the rollback process only needs to execute the steps of "rollback host", "active-standby switch of the virtualization management service (host including the virtualization management service)", "resume host service", and other steps need not be executed. That is, in the rollback procedure of a single host, the corresponding rollback steps can be dynamically arranged according to whether the host contains the virtualized management service and the super fusion management service, and the upgrade information.

In summary, in the embodiment of the present application, in any step in the process of upgrading the subsystems of the management system, if an abnormality caused by an uncontrollable factor occurs, the whole management system may be rolled back in reverse order, so as to ensure the consistency and system stability of the system version of each subsystem in the management system. Moreover, the backspacing sequence of the host can be automatically arranged, a technician does not need to manually intervene in the backspacing sequence after selecting the host, and the system can automatically arrange the sequence, so that the automation and the intellectualization of the backspacing process are realized. In addition, the rollback step of the host computer can be automatically arranged, so that the stability and automation of the rollback process are effectively improved.

In one implementation, a system upgrade platform may be invoked to implement a system upgrade to a management system, and a process flow of the system upgrade may be presented on a related interface on the system upgrade platform. Optionally, after the system upgrade task is initiated through the task initiation interface of the system upgrade platform, an upgrade process of each subsystem in the management system may be displayed on the system upgrade interface of the system upgrade platform. For example, referring to fig. 5c, the interface may be a system upgrade interface, where the system upgrade interface may include a subsystem display area for displaying each subsystem for system upgrade, for example, area 51 is a subsystem display area corresponding to subsystem 1, and area 52 is a subsystem display area corresponding to subsystem 2.

The subsystem display area of the target subsystem (the target subsystem may refer to any subsystem of a plurality of subsystems) may include a situation display area for displaying an upgrade situation of the target subsystem in a system upgrade process, an upgrade control (such as control 502) for controlling upgrade processing of the target subsystem, and a rollback control (such as control 503) for controlling rollback processing of the target subsystem.

When the upgrading process is required to be performed on the target subsystem, the object can trigger the upgrading control corresponding to the target subsystem, for example, if the target subsystem is the subsystem 1, the upgrading control is the control 502, and when the upgrading control in the subsystem display area of the target subsystem is detected to be triggered, the system upgrading can be performed on the target subsystem, namely, a background service device (namely, a computing device) of the system upgrading platform can execute the upgrading process of the target subsystem, and the upgrading condition of the target subsystem in the process of system upgrading can be displayed in the subsystem display area of the target subsystem.

When the rollback processing is required to be performed on the target subsystem, the object may trigger the rollback control corresponding to the target subsystem, for example, assuming that the target subsystem is subsystem 1, the rollback control is control 503, and when the rollback control in the subsystem display area of the target subsystem is detected to be triggered, the rollback processing is performed on the target subsystem, that is, the background service device (i.e., the computing device) of the system upgrading platform may execute the rollback flow on the target subsystem.

The target subsystem may further include a system upgrade of each Node, and then the situation display area may include a Node situation display area for each Node (such as a Node situation display area 501 for an upgrade situation of the Node (Node) 2), where a Node included in the target subsystem may be understood as a component that needs to perform a system upgrade under the target subsystem. When there are multiple nodes in the target subsystem, the multiple nodes may be upgraded sequentially according to the upgrade order for the multiple nodes.

The node condition display area of a node may include a first area displaying basic information of the node and a second area displaying upgrade progress information. The basic information may include, among others, a node name, a node IP, a status indicating whether the node upgrade was successful (e.g., the status may be not started, in-upgrade, failed, upgraded), a progress of the node upgrade, a current version corresponding to the node (a system version before the system upgrade), and a target version (a system version after the system upgrade), a start time of the system upgrade, a time consumption of the system upgrade, and the like. For example, region 504 is a first region of Node2 and region 505 is a second region of Node 2. The upgrade progress information may be used to show how the node performs on each upgrade step, such as a warning displayed in area 505 that the upgrade configuration was detected and did not pass the system check.

In this case, the object may trigger a rollback control (e.g., control 506) for controlling the node to perform rollback processing, and when it is detected that the rollback control for the node is triggered, the rollback processing may be performed on the node, that is, the background service device (i.e., the computing device) of the system upgrade platform may execute a rollback procedure for the node. In the case that the upgrade of a single node fails, during the process of independently backing up the node, the rollback step can be assembled according to the management service condition on the host where the node is located and the upgrade step with an abnormality in the upgrade, so as to determine the rollback step required for backing up the host.

It can be seen that by the design of the system upgrade platform, one-key upgrade of the management system can be realized, and the one-key upgrade feature can provide page-guided whole system upgrade capability for the object. Compared with manual upgrading, one-key upgrading standardizes upgrading flow and upgrading constraint, has great promotion in the aspects of automation, stability, safety and the like, can provide more rapid, efficient, safe and reliable upgrading experience for objects, and can also effectively reduce learning cost and manpower input of clients and implementation personnel.

S403, if the management system is successfully updated, the management system after the successful updating is operated.

In one implementation, after each subsystem upgrade in the management system is successful, the system upgrade interface may jump to an upgrade success interface for system upgrade success, e.g., where the upgrade success interface may be as shown in FIG. 5 d. The upgrade success interface may display upgrade status information of each subsystem in the management system, for example, upgrade status information of one subsystem may include a name of a subsystem, an upgrade status, an upgrade start time, upgrade time consumption, and the like. Considering that in the embodiment of the application, the test operation period of the management system after the successful upgrading exists, after each subsystem finishes the upgrading, the upgrading state in the upgrading condition information of one subsystem displayed in the upgrading success interface can be 'submitted after verification', so as to remind an object that the subsystem is still in the test operation period, and the subsystem initiates a task submitting instruction when the system service abnormality does not occur in the test operation period.

The upgrade success interface may display upgrade condition information of each subsystem in the management system at a plurality of time points. For example, referring to fig. 5d, when a system upgrade is performed on a management system at a time point shown in a region 507, upgrade condition information of each subsystem in the management system is displayed. A first submit control (e.g., control 508) may also be included in region 507 for submitting a system upgrade task for the management system. The object can trigger the first submitting control if the management system does not have the system service abnormality in the test operation period, or trigger the first submitting control if the management system has the system service abnormality in the preset period after the operation and the rollback processing of the management system is completed.

In one implementation, upon detecting that a first submit control for the management system (e.g., control 508) is triggered in an upgrade success interface, a submit prompt bullet may be displayed on the upgrade success interface, e.g., as shown in FIG. 5 e. An input area (e.g., area 509) for entering account information for initiating an initiating object that initiates a system upgrade task and a second submit control (e.g., control 510) may be included in the submit prompt pop. The account information may include an object name and a password for logging into the system upgrade platform, so as to determine that the initiating object is a legal object based on the account information. A second submit control may be triggered when the initiating object determines to submit the system upgrade task. When the account information of the initiating object is input in the input area and the triggering of the second submitting control is detected, the completion of the system upgrading task can be determined.

In one implementation, after each subsystem in the management system is successfully upgraded, a corresponding upgrade detail interface may be performed based on a specific subsystem, for example, if the object clicks on subsystem 1 in fig. 5d, the system upgrade interface shown in fig. 5d may jump to the upgrade detail page for subsystem 1 shown in fig. 5 f.

It can be understood that after the management system is successfully upgraded, there is a commissioning period (i.e. a preset period of time), and if an abnormal system service caused by uncontrollable factors is encountered during the commissioning, each subsystem can be rolled back in the upgrade detail page (such as the interface shown in fig. 5 f) according to the reverse order of the upgrade order of each subsystem. If no exception occurs to the system service beyond the commissioning period, the system upgrade platform system may give a commit prompt (such as the interface shown in FIG. 5 e) to direct the object to complete the commit operation.

According to the explanation of the interface, in the system upgrading of the management system, if the uncontrollable risk is encountered during the observation after all subsequent subsystems are upgraded, the system can also support to directly fall back on the interface according to the reverse order of the upgrading process of the subsystems so as to ensure that the user service is not influenced by the upgrading abnormality. And by providing the Web page (such as various interfaces mentioned above), the visual monitoring and operation of the rollback whole flow can be performed, the whole upgrading process is ensured to be controllable, and the risks caused by uncontrollable factors are eliminated. In addition, the characteristics that each subsystem in the management system (such as a super fusion system) supports single node upgrading, rollback and submitting can be utilized, the upgrading step or rollback step of the node can be arranged, and the automation and the stability of the system upgrading and rollback are ensured to the greatest extent through an algorithm.

S404, if the management system has abnormal system service in the preset time period after operation, carrying out rollback processing on a second subsystem in the management system.

It can be understood that if the system service abnormality occurs in the management system after the upgrade is successful, it can be determined that the management system after the system upgrade has a problem, or the management system cannot be used normally by the user, in this case, in order to ensure that the management system can be used normally, the management system can be rolled back, i.e. the system version of the management system after the system upgrade is restored to the system version before the system upgrade.

Based on the above, if the management system has abnormal system service in the preset period after operation, the management system may perform rollback processing, where the rollback processing may be performed on the second subsystem in the management system first, so that the system version of the upgraded second subsystem is restored to the system version before the system upgrade.

As described above, the second subsystem may include a virtual machine with a virtualization management service in addition to the host, and in the case that the second subsystem includes the host and the virtual machine with the virtualization management service, the rollback processing may be performed on the host first and then on the virtual machine with the virtualization management service.

Wherein the number of second subsystems may be one or more. In one implementation manner, in the case that the number of the second subsystems is one, and the second subsystems include the host and the virtual machine with the virtualization management service, the rollback processing may be directly performed on the host in the one second subsystem, and then the rollback processing may be performed on the virtual machine with the virtualization management service in the one second subsystem. In another implementation manner, in the case that the number of the second subsystems is one and the second subsystems include the host, the rollback processing may be directly performed on the host in the one second subsystem.

In one implementation, when the number of the second subsystems is plural, the number of the involved hosts is plural, in which case a rollback process is required for the plural hosts, and after the plural hosts are successfully backed, a rollback process may be performed for the virtual machines having the virtualized management service in the plural second subsystems. When the plurality of hosts are rollback, the plurality of hosts may have a corresponding rollback order, so that the plurality of hosts are sequentially rollback according to the rollback order.

Alternatively, similar to the principle of determining the host upgrade order of the plurality of hosts, the host rollback order of the plurality of hosts may also be determined based on the backup service and the backup service for the virtualization management service deployed in the hosts of the plurality of second subsystems. In one embodiment, the host deployed with the backup service may be used as the first host to be rolled back, the host deployed with the primary service may be used as the last host to be rolled back, and the rolling back sequence of other hosts in the plurality of hosts is not limited, and may be arranged in any manner. In general, the host rollback sequence can be determined according to the existence of the management service and the active/standby service of the management service, and the host where the standby service with the virtualized management service is located is guaranteed to be rolled back first, and finally the host where the active service with the virtualized management service is located is rolled back. For example, assuming that the management system involves 3 hosts, host 1, host 2, host 3, and host 2 is deployed with a standby service and host 3 is deployed with a primary service, the rollback order (from first to last order) of these 3 hosts may be host 2, host 1, host 3.

It will be appreciated that for hosts that deploy both primary and backup services, one or more hosts may be included, and where there are multiple hosts, the rollback order of the multiple hosts may be determined in a random manner or may be determined according to a preset rule. The principle is consistent with the principle of determining the upgrade order of the plurality of hosts, and will not be described herein.

Optionally, each host has a corresponding rollback step when performing rollback processing, and the specific implementation of sequentially performing rollback processing on the multiple hosts according to the rollback sequence of the hosts may be that the rollback step required by performing rollback processing on each host in the multiple hosts is determined first, then sequentially performing rollback processing on the multiple hosts according to the rollback sequence of the hosts, and performing rollback processing on each host by using the corresponding rollback step when performing rollback processing on each host. The specific description of the corresponding rollback step when each host performs rollback processing may be referred to the related description in step S402, which is not described herein, for example, the rollback flow shown on the right side in fig. 5a or the rollback flow shown on the right side in fig. 5b may be referred to by the corresponding rollback step when each host performs rollback processing.

For example, assume that the management system includes 3 hosts, host 1, host 2, and host 3, and the host rollback order of the 3 hosts is that host 3, host 2, and host 1, when rollback processing is performed on the 3 hosts, rollback processing is performed on host 3 according to rollback steps required by rollback processing performed on host 3, after rollback processing is performed on host 3, rollback processing is performed on host 2 according to rollback steps required by rollback processing performed on host 2, and after rollback processing is performed on host 2, rollback processing is performed on host 1 according to rollback steps required by rollback processing performed on host 1. It will be appreciated that the rollback steps required for the rollback processing by the hosts 1, 2, 3 are consistent.

S405, after the second subsystem successfully backs off, the first subsystem in the management system is backed off.

As described above, the first subsystem corresponds to the super-converged management service, after the rollback of the second subsystem is completed, the rollback processing can be performed on the first subsystem in the management system, and by performing the rollback processing on the first subsystem in the management system, the system version of the upgraded first subsystem can be restored to the system version before the system upgrade, so as to ensure the consistency of the system versions of the subsystems in the management system.

It can be understood that in the system upgrade of the management system, the upgrade of the host, the virtual machine management service and the super fusion management service is related, and after an upgrade abnormal event is detected or the management system is operated after the upgrade is successful, the management system has abnormal system service in a preset time period, and the rollback processing is required, wherein the rule of the rollback processing is that a plurality of subsystems rollback according to the reverse order of the upgrade order.

The principle of the whole rollback is that the host is rollback firstly, then the virtual machine management service is rollback, and finally the hyper-integration management service is rollback. For example, as shown in fig. 5g, assuming that the management system includes 3 hosts, host 1, host 2 and host 3, when performing rollback processing on the management service, rollback processing is performed on host 1, host 2 and host 3, then rollback processing is performed on the virtual machine of the virtualized management service on host 1 and the virtual machine of the virtualized management service on host 3, and finally rollback processing is performed on the superset management service on host 1, host 2 and host 3.

It can be seen that, in the embodiment of the present application, for the uncontrollable risk that may occur in the system upgrade process of the management system, a trusted overall rollback scheme may be provided, where the rollback processing may be integrated and arranged by supporting the individual rollback feature of a single host for each subsystem, after the upgrade of the single subsystem is successful, upgrade data may be temporarily not emptied, and after the upgrade of all subsystems is completed, a period of observation is given before all upgrade data is emptied, and whether all functions of the management system are available after the upgrade of the observed system is ensured, so that the normal use of the management system by the object is not affected under the abnormal upgrade scenario before supporting the rollback of the integrated system until the upgrade. In a specific application scenario, the management system may be a super fusion system (or super fusion product), so that in the system upgrading of the super fusion system, the system upgrading mode provided by the embodiment of the application can ensure that the client service is maintained uninterrupted in the upgrading process of the super fusion system, and the upgrading window period can be reduced as much as possible.

For a better understanding of the system upgrade method according to the embodiment of the present application, the following is further described with reference to fig. 5 h. For example, referring to fig. 5h, when a computing device responds to a system upgrade task for a management system including multiple subsystems, the subsystem in the management system may be upgraded first, and an upgrade procedure in the system upgrade may upgrade a first subsystem in the management system (i.e., a subsystem for a super-converged management service) first, and upgrade a second subsystem (i.e., a subsystem composed of a host and a virtual machine with a virtualized management service deployed on the host). The method comprises the steps of distributing a software upgrade package of the super fusion management service, checking the super fusion management service, upgrading the super fusion management service by using the software upgrade package after checking, re-distributing the software upgrade package of the host and the virtualization management service after finishing upgrading the super fusion management service, checking the host and the virtualization management service, and upgrading the host and the virtualization management service by using the software upgrade package after checking, thereby finishing upgrading the management system.

After the management system is successfully upgraded, the management system after the upgrade is successfully upgraded can be operated, namely, an operation test of system service is carried out on the management system, so as to determine whether the system service can be operated normally, if the system service can be operated normally within a preset period of time after the operation (for example, the system service can be operated normally within a test operation period exceeding 3 days), namely, the management system does not have abnormal system service, a submission triggering instruction can be initiated, the submission triggering instruction can be used for triggering and submitting an instruction for indicating that the system upgrade task is successfully completed, and an object can be prompted to submit an instruction for indicating that the system upgrade task is successfully completed through the submission triggering instruction. If the system service is abnormal in the preset time period after the operation, namely, the system service is abnormal in the management system, the management system can be rollback according to the whole rollback sequence, so that the system version of the management system is restored to the system version before the system upgrade. The process of rollback processing for the management system may first rollback the second subsystem in the management system, and then rollback the first subsystem.

The process of performing the rollback processing on the management system according to the overall rollback sequence may be that the rollback sequence of the host corresponding to the second subsystem and the virtual machine management service is dynamically arranged first, and then the rollback step of the host in the second subsystem is dynamically arranged, so that the host corresponding to the second subsystem and the virtual machine management service are rollback by combining the rollback sequence and the rollback step. After the rollback processing of the second subsystem is completed, the rollback sequence of the super-fusion management service corresponding to the first subsystem can be arranged, and the rollback step of the super-fusion management service for rollback can be dynamically arranged, so that the super-fusion management service corresponding to the first subsystem is rolled back by combining the rollback sequence and the rollback step. After the rollback processing of the management system is completed, a commit triggering instruction may be initiated to complete a system upgrade of the management system.

Referring to fig. 6, fig. 6 is a schematic structural diagram of a system upgrade apparatus according to an embodiment of the present application. The system upgrade apparatus described in the present embodiment includes:

An upgrade unit 601, configured to perform a system upgrade on a subsystem in a management system including a plurality of subsystems in response to a system upgrade task for the management system;

A rollback unit 602, configured to determine an upgrade rollback sequence according to an upgrade sequence of each upgraded subsystem if an upgrade abnormal event is detected, and rollback each upgraded subsystem according to the upgrade rollback sequence, so that a system version of each upgraded subsystem is restored to a system version before system upgrade;

an operation unit 603, configured to operate the management system after the upgrade is successful if it is determined that the upgrade of the management system is successful;

The rollback unit 602 is further configured to, if a system service abnormality occurs in the management system within a preset period of time after operation, rollback the management system according to an overall rollback sequence, so that a system version of the management system is restored to a system version before system upgrade.

In one implementation, the rollback unit 602 is further configured to:

if the management system does not have the system service abnormality in the preset time period after operation, initiating a submission triggering instruction, wherein the submission triggering instruction is used for triggering submission of an instruction for indicating successful completion of the system upgrading task.

In one implementation, the multiple subsystems include a first subsystem with a super fusion management service, a second subsystem composed of a host and a virtual machine deployed on the host with a virtualization management service, wherein the first subsystem is used for providing management service for the second subsystem, and the rollback unit 602 is specifically configured to:

Performing rollback processing on a second subsystem in the management system to restore the system version of the updated second subsystem to the system version before the system update;

And after the second subsystem is successfully backed up, carrying out rollback processing on the first subsystem in the management system, so that the system version of the upgraded first subsystem is restored to the system version before the system upgrade.

In one implementation manner, the number of the second subsystems is a plurality, and hosts corresponding to the plurality of second subsystems include a host in which a virtual machine for a main service of the virtualization management service is deployed and a host in which a virtual machine for a backup service of the virtualization management service is deployed, where the rollback unit 602 is specifically configured to:

Determining a host rollback order for rollback to the plurality of hosts based on backup services and backup services for the virtualization management service deployed in the hosts of the plurality of second subsystems;

Sequentially carrying out rollback processing on the plurality of hosts according to the host rollback sequence;

and after the hosts are successfully backed up, carrying out rollback processing on the virtual machines with the virtualized management service in the second subsystems.

In one implementation, the rollback unit 602 is specifically configured to:

determining a rollback step required for rollback processing for each of the plurality of hosts;

And sequentially carrying out rollback processing on the plurality of hosts according to the host rollback sequence, and carrying out rollback processing by utilizing corresponding rollback steps when each host is subjected to rollback processing.

In one implementation, the plurality of hosts includes a host with a virtual machine of a main service for a virtualization management service deployed therein and a host with a virtual machine of a standby service for the virtualization management service, and the rollback unit 602 is specifically configured to:

Determining a reference rollback step required by a target host in the plurality of hosts to perform rollback processing;

If the target host is deployed with the hyper-fusion management service, adding a first processing step for executing migration of the hyper-fusion management service to the reference rollback step to obtain a rollback step required for rollback processing of the target host;

if the target host is deployed with the virtualized management service, adding a second processing step of executing the active-standby switching processing of the virtualized management service to the reference rollback step to obtain a rollback step required by rollback processing of the target host.

In one implementation, the rollback unit 602 is specifically configured to:

Checking the service state of the target host;

After the service state is detected to be the target service state, if the super fusion management service is detected to be deployed on the target host, migrating the super fusion management service on the target host;

setting the target host to a state of inoperable, migrating a target virtual machine deployed on the target host, and restoring a system version of the target host to a system version before system upgrade, wherein the target virtual machine is different from a virtual machine with a virtualization management service;

If the virtualized management service is detected to be deployed on the target host, performing active-standby switching processing on the virtualized management service, and recovering the business service of the target host.

In one implementation, the multiple subsystems include a first subsystem with a super fusion management service, a second subsystem composed of a host and a virtual machine deployed on the host with a virtualization management service, wherein the first subsystem is used for providing management services for the second subsystem, the upgraded subsystem includes the first subsystem, and the rollback unit 602 is specifically configured to:

If the upgrade abnormal event is detected in the target upgrade step of the system upgrade of the host in the target second subsystem, determining a rollback step required by rollback processing of the host in the target second subsystem based on the target upgrade step, and performing rollback processing of the host in the target second subsystem based on the rollback step;

After the host in the target second subsystem successfully backs up, if the virtual machine with the virtualization management service in the target second subsystem, carrying out rollback processing on the virtual machine with the virtualization management service in the target second subsystem;

and after the virtual machine with the virtualization management service in the target second subsystem is successfully returned, carrying out rollback processing on the upgraded first subsystem.

In one implementation, the multiple subsystems include a first subsystem with a super fusion management service, a second subsystem composed of a host and a virtual machine deployed on the host with a virtualization management service, wherein the first subsystem is used for providing management services for the second subsystem, the upgraded subsystem includes the first subsystem and the second subsystem, and the rollback unit 602 is specifically used for:

If the upgrade abnormal event is detected in the target upgrade step of the system upgrade of the host in the target second subsystem, determining a rollback step required for rollback processing of the host in the target second subsystem based on the target upgrade step, and determining a rollback step required for rollback processing of the host in the upgraded second subsystem;

According to the reverse order of the upgrading sequence of the system upgrading of the target second subsystem and the upgraded second subsystem, and based on the rollback steps required by rollback processing of the target second subsystem and the host in the upgraded second subsystem, rollback processing is performed on the target second subsystem and the host in the upgraded second subsystem;

After the host in the target second subsystem and the updated second subsystem is successfully returned, if the virtual machines with the virtualization management service in the target second subsystem and the updated second subsystem are returned, the virtual machines with the virtualization management service in the target second subsystem and the updated second subsystem are returned;

And after the virtual machines with the virtualized management service in the target second subsystem and the updated second subsystem are successfully backed up, carrying out rollback processing on the updated first subsystem.

In one implementation, the multiple subsystems include a first subsystem with a super fusion management service, a second subsystem composed of a host and a virtual machine deployed on the host with a virtualization management service, wherein the first subsystem is used for providing management services for the second subsystem, and the upgrading unit 601 is specifically configured to:

Acquiring a software upgrading packet corresponding to the first subsystem, and performing system upgrading on the first subsystem by utilizing the software upgrading packet corresponding to the first subsystem;

after the system upgrading of the first subsystem is completed, a software upgrading package corresponding to the second subsystem is obtained, and the system upgrading of the second subsystem is carried out by utilizing the software upgrading package corresponding to the second subsystem.

In one implementation, the upgrade unit 601 is further configured to:

Displaying a system upgrading interface on a system upgrading platform, wherein the system upgrading interface displays a subsystem display area which is used for displaying the upgrading condition of each subsystem in the management system;

When the upgrading control in the subsystem display area of the target subsystem is detected to be triggered, carrying out system upgrading on the target subsystem, and displaying the upgrading condition of the target subsystem in the subsystem display area of the target subsystem in the process of system upgrading.

In one implementation manner, the subsystem display area of the target subsystem further includes a rollback control for controlling the target subsystem to rollback, and the rollback unit 602 is further configured to:

and when detecting that the rollback control in the subsystem display area of the target subsystem is triggered, performing rollback processing on the target subsystem.

In one implementation, the rollback unit 602 is further configured to:

Displaying an upgrade success interface for displaying that the management system is successfully upgraded on a system upgrade platform, wherein the upgrade success interface comprises a first submission control for submitting a system upgrade task for the management system;

When the first submission control is detected to be triggered, a submission prompt popup window is displayed on the upgrade success interface, wherein the submission prompt popup window comprises an input area for inputting account information of an initiating object initiating the system upgrade task and a second submission control;

and when the account information of the initiating object is input in the input area and the second submission control is triggered, determining that the system upgrading task is completed.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a computing device according to an embodiment of the application. The computing device described in this embodiment includes a processor 701, a memory 702, and a network interface 703. Data may be interacted between the processor 701, the memory 702, and the network interface 703.

The Processor 701 may be a central processing unit (Central Processing Unit, CPU), which may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), off-the-shelf Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 702 may include read only memory and random access memory and provides program instructions and data to the processor 701. A portion of the memory 702 may also include non-volatile random access memory. Wherein the processor 701, when calling the program instructions, is configured to execute:

In one implementation, the processor 701 is further configured to:

In one implementation, the multiple subsystems include a first subsystem with a super fusion management service, a second subsystem composed of a host and a virtual machine deployed on the host with a virtualization management service, wherein the first subsystem is used for providing management services for the second subsystem, and the processor 701 is specifically configured to:

In one implementation manner, the number of the second subsystems is a plurality, and the hosts corresponding to the plurality of second subsystems include a host in which a virtual machine for a main service of the virtualization management service is deployed and a host in which a virtual machine for a backup service of the virtualization management service is deployed, where the processor 701 is specifically configured to:

In one implementation, the processor 701 is specifically configured to:

In one implementation, the plurality of hosts includes a host with a virtual machine of a main service for a virtualization management service deployed therein and a host with a virtual machine of a standby service for the virtualization management service, and the processor 701 is specifically configured to:

In one implementation, the processor 701 is specifically configured to:

Checking the service state of the target host;

In one implementation, the multiple subsystems include a first subsystem with a super fusion management service, a second subsystem composed of a host and a virtual machine deployed on the host with a virtualization management service, wherein the first subsystem is used for providing management services for the second subsystem, the upgraded subsystem includes the first subsystem, and the processor 701 is specifically configured to:

In one implementation, the multiple subsystems include a first subsystem with a super fusion management service, a second subsystem composed of a host and a virtual machine deployed on the host with a virtualization management service, wherein the first subsystem is used for providing management services for the second subsystem, the upgraded subsystem includes the first subsystem and the second subsystem, and the processor 701 is specifically configured to:

In one implementation, the processor 701 is further configured to:

In one implementation, the subsystem display area of the target subsystem further includes a rollback control for controlling the target subsystem to rollback, and the processor 701 is further configured to:

In one implementation, the processor 701 is further configured to:

The embodiment of the present application further provides a chip, where the chip is disposed in the computing device, and the chip is used to perform the method described in the corresponding embodiment, which is not described herein again. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

Those of skill in the art will further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments of the application may be implemented by electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present application.

The present application also provides a computer storage medium having stored thereon a computer program comprising program instructions which when executed by a computing device perform the functions of any of the method embodiments described above.

The computer storage media include, but are not limited to, flash memory, hard disk, and solid state disk.

The application also provides a computer program product which, when executed by a computer device, implements the functions of any of the method embodiments described above.

The described aspects of the application may be implemented in various ways. For example, these techniques may be implemented in hardware, software, or a combination of hardware. For a hardware implementation, the processing units of the related art that perform the methods described above may be implemented in one or more general purpose processors, digital Signal Processors (DSPs), digital signal processing devices, application Specific Integrated Circuits (ASICs), programmable logic devices, field programmable gate arrays (field programmable GATE ARRAY, FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combinations thereof. A general purpose processor may be a microprocessor, but in the alternative, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer instructions may be stored in a computer storage medium or transmitted from one computer storage medium to another.

It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "and/or" is used to describe an association relationship of an associated object, and indicates that three relationships may exist, for example, "a and/or B" may indicate that only a exists, only B exists, and three cases of a and B exist simultaneously, where a and B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one of a, b or c may represent a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

The preset (e.g., preset period) in the present application may be understood as defining, predefining, storing, pre-negotiating, pre-configuring, curing, or pre-firing.

Those skilled in the art will understand that, for convenience and brevity, the specific working process of the computing device and unit described above may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

The same or similar parts may be referred to each other in the various embodiments of the application. In the embodiments of the present application, and the respective implementation/implementation methods in the embodiments, if there is no specific description and logic conflict, terms and/or descriptions between different embodiments, and between the respective implementation/implementation methods in the embodiments, may be consistent and may refer to each other, and technical features in the different embodiments, and the respective implementation/implementation methods in the embodiments, may be combined to form a new embodiment, implementation, or implementation method according to their inherent logic relationship. The embodiments of the present application described above do not limit the scope of the present application.

Claims

1. A system upgrade method, characterized in that the method comprises:

In response to a system upgrade task for a management system including multiple subsystems, a subsystem in the management system is upgraded; the multiple subsystems include: a first subsystem with a hyper-converged management service, a host and a second subsystem composed of a virtual machine with a virtualization management service deployed on the host, the first subsystem being used to provide management services for the second subsystem;

If an upgrade abnormality event is detected, an upgrade rollback order is determined according to the upgrade order of each upgraded subsystem, and each upgraded subsystem is rolled back according to the upgrade rollback order, so that the system version of each upgraded subsystem is restored to the system version before the system upgrade; if the upgraded subsystem includes the first subsystem; the rollback of each upgraded subsystem according to the upgrade rollback order includes: if the upgrade abnormality event is detected by an abnormality in the target upgrade step of the system upgrade of the host in the target second subsystem, the rollback steps required for the rollback of the host in the target second subsystem are determined based on the target upgrade step, and the host in the target second subsystem is rolled back based on the rollback steps; after the host in the target second subsystem is successfully rolled back, if there is a virtual machine with a virtualization management service in the target second subsystem, the virtual machine with the virtualization management service in the target second subsystem is rolled back; after the virtual machine with the virtualization management service in the target second subsystem is successfully rolled back, the upgraded first subsystem is rolled back;

If it is determined that the management system is successfully upgraded, running the successfully upgraded management system;

If a system service anomaly occurs in the management system within a preset time period after operation, the management system is rolled back in an overall rollback order so that the system version of the management system is restored to the system version before the system upgrade; the rollback of the management system in an overall rollback order includes: rolling back the second subsystem in the management system so that the system version of the second subsystem that has completed the upgrade is restored to the system version before the system upgrade; after the second subsystem is successfully rolled back, rolling back the first subsystem in the management system so that the system version of the first subsystem that has completed the upgrade is restored to the system version before the system upgrade.

2. The method according to claim 1, further comprising:

If no system service anomaly occurs in the management system within a preset time period after operation, a submit trigger instruction is initiated, and the submit trigger instruction is used to trigger submission of an instruction indicating successful completion of the system upgrade task.

3. The method according to claim 1 is characterized in that the number of the second subsystems is multiple, and the hosts corresponding to the multiple second subsystems include hosts on which virtual machines for a primary service of a virtualization management service are deployed, and hosts on which virtual machines for a backup service of a virtualization management service are deployed; the rollback processing of the second subsystem in the management system comprises:

Determine a host rollback order for rolling back the multiple hosts based on the primary service and the backup service for the virtualization management service deployed in the hosts of the multiple second subsystems;

Performing rollback processing on the multiple hosts in sequence according to the host rollback order;

After the multiple hosts are successfully rolled back, a rollback process is performed on the virtual machines with virtualization management services in the multiple second subsystems.

4. The method according to claim 3, wherein the step of performing rollback processing on the multiple hosts in sequence according to the host rollback order comprises:

Determining a rollback step required to perform a rollback process on each of the plurality of hosts;

The plurality of hosts are sequentially subjected to rollback processing according to the host rollback sequence, and corresponding rollback steps are used to perform rollback processing on each host when the rollback processing is performed.

5. The method according to claim 4, wherein the plurality of hosts include hosts on which virtual machines for a primary service of a virtualization management service are deployed, and hosts on which virtual machines for a backup service of a virtualization management service are deployed; and the step of determining the rollback steps required for rollback processing of each of the plurality of hosts comprises:

Determine reference rollback steps required for a target host among the multiple hosts to perform rollback processing;

If a hyper-converged management service is deployed on the target host, the first processing step of executing the migration of the hyper-converged management service is added to the reference rollback step to obtain the rollback step required for performing the rollback process on the target host;

If a virtualization management service is deployed on the target host, the second processing step of executing the active/standby switching processing of the virtualization management service is added to the reference rollback step to obtain the rollback step required for performing the rollback processing on the target host.

6. The method according to claim 5, characterized in that the step of performing rollback processing on each host using corresponding rollback steps comprises:

Checking the service status of the target host;

After checking that the service state is the target service state, if it is detected that a hyper-converged management service is deployed on the target host, migrating the hyper-converged management service on the target host;

Setting the target host to an inoperable state, migrating the target virtual machine deployed on the target host, and restoring the system version of the target host to the system version before the system upgrade; the target virtual machine is different from the virtual machine with the virtualization management service;

If it is detected that a virtualization management service is deployed on the target host, the virtualization management service is switched between active and standby modes, and the business service of the target host is restored.

7. The method according to claim 1, wherein the multiple subsystems include: a first subsystem with a hyper-converged management service, a host and a second subsystem composed of a virtual machine with a virtualization management service deployed on the host, the first subsystem is used to provide management services for the second subsystem; the upgraded subsystem includes the first subsystem and the second subsystem; the step of rolling back each upgraded subsystem according to the upgrade rollback order includes:

If the upgrade abnormality event is detected by an abnormality occurring in a target upgrade step of a system upgrade of a host in the target second subsystem, a rollback step required for rollback processing of the host in the target second subsystem is determined based on the target upgrade step, and a rollback step required for rollback processing of the host in the upgraded second subsystem is determined;

According to the reverse order of the upgrade sequence of performing system upgrade on the target second subsystem and the upgraded second subsystem, and based on the rollback steps required for the hosts in the target second subsystem and the upgraded second subsystem to perform rollback processing, the hosts in the target second subsystem and the upgraded second subsystem are rolled back;

After the host in the target second subsystem and the upgraded second subsystem is successfully rolled back, if the target second subsystem and the upgraded second subsystem have virtual machines with virtualization management services, rollback processing is performed on the virtual machines with virtualization management services in the target second subsystem and the upgraded second subsystem;

After the virtual machines with the virtualization management service in the target second subsystem and the upgraded second subsystem are successfully rolled back, the upgraded first subsystem is rolled back.

8. The method according to claim 1, wherein the plurality of subsystems include: a first subsystem with a hyper-converged management service, a host and a second subsystem composed of a virtual machine with a virtualization management service deployed on the host, the first subsystem being used to provide management services for the second subsystem; the system upgrade of the subsystems in the management system comprises:

Obtaining a software upgrade package corresponding to the first subsystem, and performing a system upgrade on the first subsystem using the software upgrade package corresponding to the first subsystem;

After completing the system upgrade of the first subsystem, a software upgrade package corresponding to the second subsystem is obtained, and the system upgrade of the second subsystem is performed using the software upgrade package corresponding to the second subsystem.

9. The method according to claim 1, further comprising:

Displaying a system upgrade interface on the system upgrade platform, wherein the system upgrade interface displays a subsystem display area for displaying the upgrade status of each subsystem in the management system; the subsystem display area of the target subsystem in each subsystem includes an upgrade control for controlling the target subsystem to perform system upgrade;

When it is detected that the upgrade control in the subsystem display area of the target subsystem is triggered, the target subsystem is upgraded, and the upgrade status of the target subsystem during the system upgrade is displayed in the subsystem display area of the target subsystem.

10. The method according to claim 9, characterized in that the subsystem display area of the target subsystem further comprises a rollback control for controlling the target subsystem to perform rollback processing; and further comprises:

When it is detected that the rollback control in the subsystem display area of the target subsystem is triggered, a rollback process is performed on the target subsystem.

11. The method according to claim 1, further comprising:

Displaying, on the system upgrade platform, an upgrade success interface for showing that the management system has been successfully upgraded, wherein the upgrade success interface includes a first submission control for submitting a system upgrade task for the management system;

When it is detected that the first submission control is triggered, a submission prompt pop-up window is displayed on the upgrade success interface, wherein the submission prompt pop-up window includes an input area for inputting account information of an initiator of the system upgrade task and a second submission control;

When it is detected that the account information of the initiating object is input in the input area and it is detected that the second submit control is triggered, it is determined that the system upgrade task is completed.

12. A computing device, comprising a processor and a memory, wherein the memory is used to store a computer program, the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1 to 11.