A system upgrade method and computing device

Abstract

The embodiment of the present application discloses a system upgrade method and a computing device, wherein the method comprises: in response to a system upgrade task for a management system including multiple subsystems, performing a system upgrade on the subsystems in the management system; if an abnormal upgrade event is detected, determining an upgrade rollback order according to the upgrade order of each upgraded subsystem, and performing rollback processing on each upgraded subsystem 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 it is determined that the management system upgrade is successful, running the management system after the successful upgrade; if a system service abnormality occurs in the management system within a preset time period after the operation, rolling back the management system according to the overall rollback order, so that the system version of the management system is restored to the system version before the system upgrade, thereby ensuring the consistency of the system version and the system stability of the management system during the system upgrade, and effectively improving the reliability of the system upgrade.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a system upgrade method and a computing device. Background Art

[0002] System upgrades can provide new functions and improve user experience, and can also fix system vulnerabilities and defects. Therefore, system upgrades are an important feature in the system. For a system that contains multiple subsystems, it is necessary to upgrade each subsystem in the system in sequence. However, uncontrollable factors may usually occur during the subsystem upgrade process, causing the subsystem upgrade to fail. The subsystem upgrade failure may not be handled temporarily, and the subsystem that has completed the upgrade cannot be rolled back, which will result in subsystems with incompatible system versions in the system, and may also cause the system to be unable to be used normally in full, and the reliability of the system upgrade cannot be effectively guaranteed. Summary of the invention

[0003] The embodiments of the present application provide a system upgrade method and a computing device, which can ensure the consistency of the system version and the system stability of the management system during the system upgrade, and effectively improve the reliability of the system upgrade.

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

[0005] In response to a system upgrade task for a management system including a plurality of subsystems, performing a system upgrade on a subsystem in the management system;

[0006] If an abnormal upgrade event is detected, the upgrade rollback sequence is determined according to the upgrade sequence of each upgraded subsystem, and each upgraded subsystem is rolled back according to the upgrade rollback sequence, so that the system version of each upgraded subsystem is restored to the system version before the system upgrade;

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

[0008] If a system service anomaly occurs in the management system within a preset time period after operation, the management system is rolled back in accordance with the overall rollback sequence so that the system version of the management system is restored to the system version before the system upgrade.

[0009] In a second aspect, an embodiment of the present application provides a system upgrade device, which may include:

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

[0011] A rollback unit, configured to, if an abnormal upgrade event is detected, determine an upgrade rollback sequence according to the upgrade sequence of each upgraded subsystem, and perform rollback processing on each upgraded subsystem according to the upgrade rollback sequence, so that the system version of each upgraded subsystem is restored to the system version before the system upgrade;

[0012] An operating unit, configured to operate the upgraded management system if it is determined that the management system is upgraded successfully;

[0013] The rollback unit is also used to roll back the management system in an overall rollback sequence if a system service anomaly occurs in the management system within a preset time period after operation, so as to restore the system version of the management system to the system version before the system upgrade.

[0014] In a third aspect, an embodiment of the present application provides a computing device, wherein the computing device includes a processor, and the processor is configured to support the computing device to implement the functions involved in the first aspect. The computing device may also include a memory, which is coupled to the processor and stores 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 a communication network.

[0015] In a fourth aspect, an embodiment of the present application provides a computer storage medium, which stores a computer program. The computer program includes program instructions, which, when executed by a processor, are used to implement the functions involved in the above-mentioned first aspect.

[0016] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes program instructions. When the computer program product is executed by a computing device, the computing device can implement the functions involved in the first aspect above.

[0017] In a sixth aspect, the present application provides a chip system, which includes a processor for supporting a computing device to implement the functions involved in the first aspect. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0018] The embodiments of the present application can respond to a system upgrade task for a management system including multiple subsystems, and perform a system upgrade on the subsystems in the management system; if an upgrade abnormality event is detected, the upgrade rollback order can be determined according to the upgrade order of each upgraded subsystem, and each upgraded subsystem can be 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 it is determined that the management system upgrade is successful, the management system after the successful upgrade can be run; if a system service abnormality occurs in the management system within a preset time period after the operation, the management system can be rolled back according to the overall rollback order, so that the system version of the management system is restored to the system version before the system upgrade; in this way, the consistency of the system version and the system stability of the management system during the system upgrade can be guaranteed, so as to effectively improve the reliability of the system upgrade. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 It is a schematic diagram of the architecture of an upgrade system provided in an embodiment of the present application;

[0021] Figure 2 It is a flowchart of a system upgrade method provided in an embodiment of the present application;

[0022] Figure 3a It is a schematic diagram of the composition of a management system provided in an embodiment of the present application;

[0023] Figure 3b is a flowchart of responding to a system upgrade task provided by an embodiment of the present application;

[0024] Figure 3c This is a flowchart of an upgrade process of a management system provided by an embodiment of the present application;

[0025] Figure 4 It is a flowchart of another system upgrade method provided in an embodiment of the present application;

[0026] Figure 5a It is a schematic diagram comparing an upgrade process and a rollback process provided in an embodiment of the present application;

[0027] Figure 5b It is a schematic diagram comparing another upgrade process and a rollback process provided in an embodiment of the present application;

[0028] Figure 5c It is a schematic diagram of a system upgrade interface during a management system upgrade process provided by an embodiment of the present application;

[0029] Figure 5d It is a schematic diagram of an interface of an upgrade success interface after a management system is successfully upgraded provided by an embodiment of the present application;

[0030] Figure 5e This is a schematic diagram of an interface of a submission prompt pop-up window provided in an embodiment of the present application;

[0031] Figure 5f It is a schematic diagram of an upgrade details interface of a subsystem provided in an embodiment of the present application;

[0032] Figure 5g This is a flowchart of a rollback process provided by an embodiment of the present application;

[0033] Figure 5h It is a flowchart of another system upgrade method provided in an embodiment of the present application;

[0034] Figure 6 It is a structural schematic diagram of a system upgrade device provided in an embodiment of the present application;

[0035] Figure 7 It is a structural diagram of a computing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0037] An embodiment of the present application provides a system upgrade solution, the principle of which is as follows: if there is a system upgrade task for a management system including multiple subsystems, the subsystems in the management system can be upgraded; if an upgrade abnormality is detected during the system upgrade, the upgrade rollback order can be determined according to the upgrade order of each upgraded subsystem, and each upgraded subsystem can be 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 it is determined that the management system upgrade is successful, the management system after the successful upgrade can be further run; if a system service abnormality occurs in the management system within a preset time period after the run, the rollback can be performed according to the overall rollback order, so that the system version of the management system is restored to the system version before the system upgrade.

[0038] By implementing the above solution, when an exception occurs during the upgrade process of the subsystem of the management system, the upgraded subsystems can be rolled back in sequence according to the upgrade order of the subsystems; and after the overall upgrade of the management system is completed, the successfully upgraded management system can be run to observe whether all the functions of the successfully upgraded management system are available. If it is determined that all functions cannot be used, the overall rollback can be performed in reverse order according to the upgrade order of the subsystems; thereby effectively ensuring the consistency of the system versions and system stability of each subsystem in the management system to ensure that users can continue to use the system normally. In addition, unified monitoring and management of the upgrade and rollback processes of different subsystems in the management system can be achieved, supporting the sequential rollback of multiple subsystems, and effectively reducing operation and maintenance risks.

[0039] In a specific implementation, the execution subject of the above-mentioned system upgrade solution may be a computing device, which includes but is not limited to a terminal or a server. In other words, the computing device may be a server or a terminal, or a system composed of a server and a terminal. Among them, the terminal mentioned above may be an electronic device, including but not limited to mobile phones, tablet computers, desktop computers, laptop computers, PDAs, vehicle-mounted devices, intelligent voice interaction devices, augmented reality / virtual reality (AR / VR) devices and other mobile Internet devices (mobile internet device, MID) with network access capabilities. Among them, the server mentioned above may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, vehicle-road collaboration, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0040] For example, when the computing device is a server, the embodiment of the present application provides an upgrade system, such as Figure 1 As shown, the upgrade system may include at least one terminal and at least one server; the terminal can obtain a system upgrade task for a management system including multiple subsystems, and upload the obtained system upgrade task for the management system including multiple subsystems to a server (i.e., a computing device), so that the server can respond to the system upgrade task for the management system including multiple subsystems, and adopt a system upgrade solution to perform a system upgrade on the management system.

[0041] The implementation details of the technical solution of the embodiment of the present application are described in detail below:

[0042] Based on the system upgrade solution provided above, the present application embodiment provides a system upgrade method. Figure 2 , Figure 2 is a flowchart of a system upgrade method provided in an embodiment of the present application. The embodiment of the present application is mainly described with a computing device as the execution subject; see Figure 2 , the system upgrade method may include the following steps:

[0043] S201 , in response to a system upgrade task for a management system including a plurality of subsystems, performing a system upgrade on a subsystem in the management system.

[0044] The management system may be a Hyper Converged Infrastructure (HCI) system, such as a hyper-converged system or a hyper-converged product, or a system including multiple subsystems, without limitation. Hyper-converged infrastructure means that the same set of unit equipment not only has computing, network, storage, server virtualization and other resources and technologies, but also multiple sets of unit equipment can be aggregated through the network to achieve modular seamless horizontal expansion (scale-out) and form a unified resource pool.

[0045] In this case, the multiple subsystems under the management system may include: a subsystem with a hyper-converged management service (the subsystem may be referred to as the first subsystem), a host and a subsystem composed of a virtual machine with a virtualization management service deployed on the host (the subsystem may be referred to as the second subsystem); the first subsystem may be used to provide management services to the second subsystem. Among them, the host may refer to a physical server running virtualization software, and relevant technicians may create a virtual machine on the host; as for the management system here, a virtual machine with a virtualization management service may be deployed on the host. Among them, the management service may refer to a management module for the server. In the embodiment of the present application, the management service may also be referred to as a management plane service, such as a hyper-converged management service may be referred to as a hyper-converged management plane service, and a virtualization management service may be referred to as a virtualization management plane service.

[0046] It should be noted that the hyper-converged management service and virtualization management service in the management system can be deployed on the host. In a management system, the number of hyper-converged management services can be one or more, and the virtualization management service can have a main service for the virtualization management service and a backup service for the virtualization management service. Among them, different hyper-converged management services can be deployed on different hosts, and the main service and backup service for the virtualization management service are also deployed on different hosts. It should be noted that the number of main services and backup services can be one or more respectively. When the total number of main services and backup services is less than the total number of hosts involved in the management system, some of the second subsystems may only involve hosts, that is, no virtual machines with virtualization management services are deployed on the hosts.

[0047] For example, see Figure 3a As shown, the management system involves three hosts. In this management system, the hyper-converged management service can be deployed on three hosts (such as host 1, host 2, and host 3), and the virtual machines of the main service and backup service of the virtualization management service are deployed on different hosts (such as host 1 deploys the backup service virtual machine, and host 3 deploys the main service virtual machine). Figure 3a The ordinary virtual machines (such as ordinary virtual machine 1, ordinary virtual machine 2, and ordinary virtual machine 3) in the management system shown in the figure may refer to virtual machines that provide other services, which are different from the virtual machines with virtualization management services here. The ordinary virtual machines may also be referred to as target virtual machines.

[0048] against Figure 3a In general, the subsystems in the management system may include: a first subsystem composed of a hyper-converged management service deployed on three hosts, wherein the hyper-converged management service deployed on one host can be understood as a first subsystem; it may also include: a second subsystem composed of host 1 and a virtual machine with a virtualization management service (backup service) deployed on host 1, a second subsystem composed of host 2, and a second subsystem composed of host 3 and a virtual machine with a virtualization management service (main service) deployed on host 3.

[0049] The system upgrade task indicates to perform a system upgrade on the management system, that is, to upgrade the system version of the management system.

[0050] In one implementation, when there is a system upgrade task for a management system including multiple subsystems, the initiator of the task (which may refer to any user) 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. Optionally, the computing device may output a task initiation interface so that the initiator performs relevant operations on the task initiation interface to initiate a system upgrade task for the management system including multiple subsystems. The task initiation interface may be displayed on the terminal screen of the terminal used by the initiator, and the task initiation interface may specifically be an interface in the system upgrade platform. The computing device here may be understood as a background service device of the system upgrade platform.

[0051] For example, when the initiator needs to perform a system upgrade on a management system, the initiator can log in to the system upgrade platform on the terminal used, and perform relevant operations on the task initiation interface in the system upgrade platform to send a system upgrade task for the management system including multiple subsystems to the computing device. Figure 3b As shown, a task initiation interface may be displayed on the terminal screen of the terminal used by the initiating object, and the task initiation interface may at least include a setting area 301 for setting the system identifier of the management system to be upgraded and a confirmation control 302. If the initiating object wants to perform a system upgrade on a management system, the system identifier corresponding to the management system may be set in the setting area 301 first, and 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.

[0052] In one implementation, the rule for upgrading the management system may be: first upgrade the management service, then upgrade the host (such as server software), and each upgrade object (such as management service or host) may be upgraded step by step or node by node according to several upgrade steps. Then, for a management system including a first subsystem and a second subsystem, the first subsystem in the management system may be upgraded first, and after completing the upgrade of the first subsystem, the second subsystem in the management system may be upgraded.

[0053] Based on this, it can be known that the specific implementation of the system upgrade of the subsystems in the management system in step 201 can be: first obtain the software upgrade package corresponding to the first subsystem, and use the software upgrade package corresponding to the first subsystem to perform a system upgrade on the first subsystem; after completing the system upgrade of the first subsystem, you can then obtain the software upgrade package corresponding to the second subsystem, and use the software upgrade package corresponding to the second subsystem to perform a system upgrade on the second subsystem.

[0054] The software upgrade packages of each subsystem can be pre-stored in a storage area, so that when the management system is upgraded, the required software upgrade packages can be directly obtained from the storage area. Optionally, when the system upgrade is performed on the system upgrade platform, the system upgrade platform can include a function for upgrade package management, that is, the upgrade package management can manage the software upgrade packages required by each subsystem in the management system.

[0055] Optionally, before performing a system upgrade on the first subsystem, an inspection operation may be performed on the first subsystem to ensure that the first subsystem can be upgraded normally and reliably. For example, the service status of the first subsystem may be checked to determine whether the hyper-converged management service corresponding to the first subsystem can provide services normally. The configuration and version of the software upgrade package may also be checked to ensure that the software upgrade package is normally available. The first subsystem may also be checked to see if there is a system warning. If there is a system warning, the system warning may be eliminated first to ensure the normal operation of the upgrade. Other inspection operations may also be included, which are not limited. Similarly, before performing a system upgrade on the second subsystem, an inspection operation may be performed on the second subsystem to ensure that the second subsystem can be upgraded normally and reliably.

[0056] For example, the process of upgrading the management system can be found in Figure 3c As shown. Figure 3c As shown, the software upgrade package for the hyper-converged management service (i.e., the first subsystem) can be distributed first, and then the hyper-converged management service can be checked; after the check is passed, the distributed software upgrade package can be used to perform a system upgrade on the hyper-converged management service. After completing the upgrade of the hyper-converged management service, the software upgrade package for the host and virtualization management service (i.e., the second subsystem) can be distributed, and the host and virtualization management service can be checked; after the check is passed, the distributed software upgrade package can be used to perform a system upgrade on the host and virtualization management service, thereby completing the system upgrade of the management system.

[0057] It should be noted that, as mentioned above, a second subsystem may involve a host and a virtual machine with a virtualization management service deployed on the host. Therefore, when performing a system upgrade on the second subsystem, the system upgrade can also be performed on the virtual machine with a virtualization management service on the host first. After completing the system upgrade of the virtual machine with the virtualization management service, the system upgrade of the host can be performed.

[0058] In one implementation, the number of the second subsystems may be one or more. When the number of the second subsystems is multiple, the number of hosts involved in the management system is also multiple, that is, the number of the second subsystems is the number of hosts. For example, if the number of the second subsystems is 3, the number of hosts is also 3. It should be noted that when there are multiple hosts, there is also a corresponding upgrade order (or it can be called a host upgrade order) for system upgrades of multiple hosts.

[0059] Optionally, the host upgrade order for upgrading multiple hosts can be determined based on the backup services and backup services for the virtualization management service deployed in the hosts of the multiple second subsystems; in one embodiment, the host with the backup service deployed can be used as the first host to be upgraded, and the host with the main service deployed can be used as the last host to be upgraded, and the upgrade order of other hosts in the multiple hosts is not limited and can be arranged in any way. In general, the host upgrade order can be determined according to the existence of the management service and the main and backup services of the management service, and it is ensured that the host with the backup service of the virtualization management service is upgraded first, and the host with the main service of the virtualization management service is upgraded last. Through this host upgrade order determination method, it can be effectively guaranteed that the business services provided by the management system are not interrupted when the main and backup switching is performed during 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 backup service, and host 3 is deployed with a main service, then the upgrade order of these 3 hosts (from first to last order) can be: host 1, host 2, host 3.

[0060] It should be noted that when there are multiple virtual machines with virtualization management services or multiple hyper-convergence management services, multiple virtual machines of virtualization management services can be upgraded simultaneously with a corresponding upgrade sequence, and multiple hyper-convergence management services can also be upgraded simultaneously. In the subsequent rollback process, multiple virtual machines of virtualization management services can also be rolled back simultaneously, and multiple hyper-convergence management services can also be rolled back simultaneously.

[0061] It is understandable that, in addition to the host with the main service and the backup service deployed, one or more hosts may be included. In the case where there are multiple hosts, the upgrade order of these multiple hosts may be determined in a random manner or according to a preset rule. In one embodiment, the preset rule may be a rule about the characteristic parameter of the host; for example, the characteristic parameter may be the importance level of the host, and the importance level may be pre-set. Among them, the upgrade order of the host may be positively correlated 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 higher, and if the importance level of the host is lower, the upgrade order of the host is lower. In this way, it can be ensured that the host with a higher importance level is upgraded first. For example, assuming that the importance levels of the three hosts are in the order of host A, host B, and host C from high to low, the upgrade order of the three hosts is host A, host B, and host C.

[0062] S202: If an abnormal upgrade event is detected, an upgrade rollback sequence is determined according to the upgrade sequence of each upgraded subsystem, and each upgraded subsystem is rolled back according to the upgrade rollback sequence.

[0063] Among them, by performing rollback processing on each upgraded subsystem, the system version of each upgraded subsystem can be restored to the system version before the system upgrade, thereby ensuring the consistency of the system version of each subsystem in the management system.

[0064] It is understandable that in the upgrade process of each subsystem of the management system, there may be some uncontrollable risks (or uncontrollable factors). For example, in the process of upgrading the virtualized server software, there are usually many uncontrollable factors to trigger the generation of upgrade exception events, thereby causing the subsystem upgrade to fail. After a subsystem in the management system fails to upgrade, the subsequent subsystems cannot be upgraded. In this case, the system version of some subsystems in the management system may be the system version after the system upgrade, the system version of some subsystems may be the system version before the system upgrade, and there are subsystems in the state of having an upgrade failure (i.e., the subsystem that failed to upgrade). When an upgrade exception event occurs during the system upgrade, the system versions of the various subsystems in the management system are inconsistent. Due to the inconsistency of the system versions, the instability of the entire management system may be caused, and the management system may not be able to guarantee the availability of all services, thereby affecting the normal use of the management system by users. In order to ensure the consistency of the system version and the stability of the system of the management system, the upgraded subsystems can be rolled back to ensure that users can continue to use the management system normally, and also to buy time for abnormal upgrade situations to eliminate abnormalities.

[0065] Based on this consideration, after detecting an abnormal upgrade event, the management system can be rolled back in time to ensure that the system versions of each subsystem in the management system are restored to the original system versions. Because only some subsystems have been upgraded at this time, only the subsystems that have completed the upgrade and the subsystems corresponding to the abnormal upgrade event can be rolled back. Here, the subsystems that have completed the upgrade and the subsystems corresponding to the abnormal upgrade event are understood as upgraded subsystems.

[0066] The upgrade rollback order for rolling back the upgraded subsystems may be: the reverse order (or inverse order) of the upgrade order of the upgraded subsystems. For example, assuming that the management system has three subsystems, and the upgrade order of the three subsystems is: subsystem 1, subsystem 2, subsystem 3; if an upgrade abnormality event is detected during the system upgrade of subsystem 2, it is necessary to roll back subsystem 1 and subsystem 2, and the upgrade rollback order for rolling back the two subsystems is: subsystem 2, subsystem 1.

[0067] As mentioned above, in the process of performing system upgrades on multiple subsystems of the management system, the first subsystem is upgraded first, and then the second subsystem is upgraded; an upgrade abnormality event can be detected during the upgrade of the first subsystem, or an upgrade abnormality event can be detected during the upgrade of the second subsystem. In the case where an upgrade abnormality event is detected during the upgrade of the first subsystem, only the first subsystem needs to be rolled back; in the case where an upgrade abnormality event is detected during the upgrade of the second subsystem, the second subsystem needs to be rolled back first, and after the rollback of the second subsystem is completed, the first subsystem needs to be rolled back.

[0068] S203: If it is determined that the management system is upgraded successfully, the upgraded management system is run.

[0069] It should be understood that in the process of system upgrade for a management system with multiple subsystems, usually after each subsystem is upgraded, the project will be submitted according to the subsystem, that is, after completing the system upgrade of a subsystem, a submission trigger instruction can be initiated. The submission trigger instruction can be completed by the submission control output by the initiating object trigger on the system upgrade platform. After the submission trigger instruction is completed, it means that the subsystem has been successfully upgraded, and the subsystem can no longer be rolled back or upgraded after the submission trigger instruction is completed. If a subsystem fails to upgrade due to various uncontrollable factors and cannot be processed temporarily, and the subsystem that has completed the upgrade cannot be rolled back, it will cause subsystems with incompatible versions in the management system, or it may also cause the system resources to be unable to be fully used, that is, the object cannot use the management system normally.

[0070] Considering that a subsystem directly initiates a submission trigger instruction after completing the system upgrade, it may result in the inability to roll back the subsystem that has completed the system upgrade after an abnormal upgrade event occurs later, then in the embodiment of the present application, consider delaying the initiation of the submission trigger instruction. That is, in the embodiment of the present application, after each subsystem in the management system completes the upgrade, the upgrade project for the corresponding subsystem will not be submitted in time (or the submission trigger instruction will be initiated), and after the upgrade of a single subsystem is successful, the upgrade data related to the system upgrade will not be temporarily cleared, so as to ensure that when an abnormal upgrade event is detected during the system upgrade process, the subsystem that has completed the upgrade can also roll back. And after all subsystems in the management system have completed the upgrade, that is, after determining that the management system has been successfully upgraded, the upgrade project for this management system will not be submitted in time, and all the upgrade data will not be cleared, but a period of observation will be given before clearing all the upgrade data to observe whether the functions of the management system are fully available after the system upgrade. In other words, during this observation period, the service operation test of the management system after the successful upgrade can be carried out; if the service can run normally during this observation period, it is determined that the management system is functional after the system upgrade, and a submission trigger instruction can be initiated; if the service is abnormal during this observation period, the management system can be rolled back as a whole.

[0071] Based on this, it can be known that after determining that the management system has been successfully upgraded, the upgraded management system can be run to determine whether to execute an operation of submitting a trigger instruction or executing an operation of rolling back the entire management system.

[0072] S204: If a system service abnormality occurs in the management system within a preset time period after operation, the management system is rolled back according to the overall rollback sequence.

[0073] Among them, by performing rollback processing on the management system, the system version of the management system can be restored to the system version before the system upgrade, thereby ensuring the consistency of the system versions of various subsystems in the management system.

[0074] The preset time period can be pre-set, and the preset time period can be understood in the same way as the observation period mentioned above; the length of the preset time period is not specifically limited, for example, the preset time period can be 3 days, 5 days, etc. The preset time period can also be understood as a trial operation period for the management system after the successful upgrade, that is, the management system after the successful upgrade is operated during the trial operation period to determine whether the system service of the management system is normal during the trial operation period.

[0075] It is understandable that if a system service abnormality occurs in the management system within a preset time period after operation, it indicates that certain functions in the successfully upgraded management system are unavailable, resulting in the inability to fully use the resources of the management system. The system version of the management system can be rolled back to the system version before the system upgrade to ensure the normal use of the management system and to ensure that the normal use of users is not affected in the event of an abnormal system upgrade.

[0076] Among them, the overall rollback order is determined based on the upgrade order when the multiple subsystems in the management system are upgraded, and the overall rollback order can be the reverse order of the upgrade order. For example, assuming that there are 3 subsystems in the management system, and the upgrade order of these 3 subsystems is: subsystem 1, subsystem 2, subsystem 3; then the upgrade rollback order for the rollback of these 3 subsystems is: subsystem 3, subsystem 2, subsystem 1. As mentioned above, when performing a system upgrade, the management service in the management system is upgraded first, and then the host in the management system is upgraded. When rolling back, the host in the management system is rolled back first, and then the management service in the management system is rolled back. And the subsystems in the management system involve the first subsystem and the second subsystem. Based on this, it can be seen that the overall rollback order can be the second subsystem first, and then the first subsystem. It can be seen that in the embodiment of the present application, multiple subsystems can be rolled back in the reverse order of the upgrade, reducing the additional risks brought by uncontrollable factors in the upgrade of multiple subsystems, and ensuring the consistency of the system versions of multiple subsystems and system stability.

[0077] Based on this, it can be known that the specific implementation of the rollback processing of the management system in accordance with the overall rollback order in step S204 can be: first, the second subsystem in the management system is rolled back 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, the first subsystem in the management system can be rolled back so that the system version of the first subsystem that has completed the upgrade is restored to the system version before the system upgrade.

[0078] As mentioned above, the second subsystem may involve hosts and virtual machines with virtualized pipeline services deployed on the hosts, and when the management system is upgraded, the virtual machines with virtualized management services in the second subsystem are upgraded first, and after the upgrade of the virtual machines with virtualized pipeline services is completed, the system upgrade is performed on all hosts. Correspondingly, when the second subsystem is rolled back, all hosts are rolled back first, and after the rollback of all hosts is completed, the virtual machines with virtualized management services deployed on the hosts are rolled back.

[0079] In one implementation, if the management system does not have a system service anomaly within a preset time period after operation, a submission trigger instruction can be initiated, and the submission trigger instruction can be used to trigger the submission of an instruction for indicating the successful completion of the system upgrade task. It can be seen that the embodiment of the present application can ensure that after the management system is upgraded, if a system service anomaly (such as a usage problem) occurs during operation within a preset time period, it can be rolled back in reverse order according to the upgrade sequence of multiple subsystems, ensuring that multiple subsystems can be upgraded sequentially and rolled back in reverse order, and ensuring the consistency of system versions and functional availability of each subsystem in the management system.

[0080] In the embodiment of the present application, when an exception occurs during the upgrade process of the subsystem of the management system, the upgraded subsystems can be rolled back in sequence according to the upgrade order of the subsystems; and after the overall upgrade of the management system is completed, the management system after the successful upgrade is run to observe whether all the functions of the management system after the successful upgrade are available. If it is determined that all functions cannot be used, the overall reverse rollback can be performed according to the upgrade order of the subsystems; thereby effectively ensuring the consistency of the system versions and the system stability of each subsystem in the management system, so as to ensure that users can continue to use the system normally. In addition, unified monitoring and management of the upgrade and rollback processes of different subsystems in the management system can be achieved, supporting the sequential rollback of multiple subsystems, and effectively reducing the operation and maintenance risks.

[0081] See also Figure 4 , is a flowchart of another system upgrade method provided by an embodiment of the present application. The present application embodiment is mainly described with a computing device as the execution subject; see Figure 4 The system upgrade method may include the following steps:

[0082] S401 , in response to a system upgrade task for a management system including a plurality of subsystems, performing system upgrade on subsystems in the management system.

[0083] The specific implementation of step S401 may refer to the description of step S201 above, which will not be repeated here.

[0084] As mentioned above, in the system upgrade of the management system, the system upgrade of the host is involved. The following specifically describes the process of system upgrade of a single host. For the convenience of description, the following description is based on the target host in the management system as an example. The target host can refer to any host included in the management system.

[0085] Specifically, a target check can be performed on the target host first; the target check can include checking the service status of the target host, checking the version and configuration of the software upgrade package, checking the system alarm, etc. In the service status check, the service status can include an unavailable state and an available state. When the service status of the target host is an available state, it is determined that the target host is not abnormal; by checking the version and configuration of the software upgrade package, it can be ensured that the upgraded host is the correct system version and that the software upgrade package is a reliable upgrade package; by checking the system alarm, it can be ensured that the host can operate normally. When the host has a system alarm, subsequent operations can be performed after eliminating the system alarm. The target check can also include other checks, which are not limited to this.

[0086] After completing the target check, it can be further determined whether a hyper-converged management service is deployed on the target host. If it is determined that a hyper-converged management service is deployed on the target host, the hyper-converged management service can be migrated (or expelled) from the target host to ensure that the services provided by the hyper-converged management service are not affected when the host system is upgraded. If the hyper-converged management service is not deployed on the target host, there is no need to perform the migration step. Then, the target host can also be set to an inoperable state, that is, during the system upgrade process, avoid continuing to execute business services on the target host, resulting in abnormal upgrades or abnormal business services. Next, the target virtual machines deployed on the target host can be migrated (such as the ordinary virtual machines mentioned above). These target virtual machines are virtual machines used to provide other business services. Because the upgrade of these virtual machines is not involved in the system upgrade of the management system here, in order to ensure the normal use of these virtual machines, these virtual machines can be migrated out of the target host when the target host is upgraded.

[0087] Furthermore, the target host can be upgraded, such as by using a software upgrade package to upgrade the target host's system version. It can also be determined whether a virtual machine management service is deployed on the target host. If it is determined that a virtual machine management service is deployed on the target host, the virtualization management service can be switched between the primary and secondary modes, and the business services of the target host can be restored. If it is determined that the virtual machine management service is not deployed on the target host, the switching step does not need to be performed, and the business services of the target host can be directly restored.

[0088] For example, see Figure 5a As shown, the upgrade process of the target host can refer to Figure 5a The process on the left side of the middle, combined with the description of the above upgrade process and Figure 5aIt can be seen from the described process that the following steps may be involved in the upgrade process: an inspection step for checking the service status, a migration step for migrating the hyper-converged management service (the host deployed with the hyper-converged management service needs to execute this step), a checking step for the version, system, alarm, etc., a setting step for setting the host to be temporarily inoperable, a migration step for migrating ordinary virtual machines on the host, a host upgrade step for upgrading the host using a software upgrade package, a switching step for switching the virtualization management service between the primary and standby modes (the host deployed with the virtualization management service needs to execute this step), and a recovery step for restoring the business services of the host.

[0089] In summary, the embodiments of the present application can automatically arrange the upgrade steps involved in the upgrade process of the host. In the upgrade process of a single host, the corresponding upgrade steps can be dynamically arranged according to whether the host contains virtualization management services and hyper-converged management services, as well as relevant information of the host, to ensure that the host can be upgraded smoothly, and to ensure that the upgrade of the host does not affect the services provided by the virtualization management service and hyper-converged management service deployed on the host.

[0090] It should be noted that each subsystem in the management system has a corresponding upgrade sequence during the system upgrade. The subsystems are upgraded in sequence according to the corresponding upgrade sequence. Before the upgrade of one subsystem is completed, the next subsystem cannot be upgraded.

[0091] S402: If an abnormal upgrade event is detected, an upgrade rollback sequence is determined according to the upgrade sequence of each upgraded subsystem, and each upgraded subsystem is rolled back according to the upgrade rollback sequence.

[0092] The upgrade rollback order for rolling back the upgraded subsystems may be the reverse order of the upgrade order of the upgraded subsystems. For example, assuming that there are 4 subsystems in the management system, and the upgrade order of the 4 subsystems is: subsystem 1, subsystem 2, subsystem 3, subsystem 4; if an upgrade abnormality event is detected during the system upgrade of subsystem 3, it is necessary to roll back subsystem 1, subsystem 2, and subsystem 3, and the upgrade rollback order for rolling back the two subsystems is: subsystem 3, subsystem 2, subsystem 1.

[0093] As mentioned above, in the process of performing system upgrades on multiple subsystems of the management system, the first subsystem is upgraded first, and then the second subsystem is upgraded; an upgrade abnormality event can be detected during the upgrade of the first subsystem, or an upgrade abnormality event can be detected during the upgrade of the second subsystem. In the case where an upgrade abnormality event is detected during the upgrade of the first subsystem, only the first subsystem needs to be rolled back; in the case where an upgrade abnormality event is detected during the upgrade of the second subsystem, the second subsystem needs to be rolled back first, and after the rollback of the second subsystem is completed, the first subsystem needs to be rolled back.

[0094] Considering that the second subsystem involves a host and a virtual machine with a virtualization management service deployed on the host, the upgrade exception event may be detected during the upgrade process of the host, or may be detected in the virtual machine with the virtualization management service. In the upgrade process, the virtual machine with the virtualization management service is upgraded first, and then the host is upgraded. If the upgrade exception event is detected during the upgrade process of the host, the host needs to be rolled back first, and after the rollback process of the host is completed, the virtual machine with the virtualization management service is rolled back. If the upgrade exception event is detected in the virtual machine with the virtualization management service, only the virtual machine with the virtualization management service needs to be rolled back, because the host has not been upgraded, that is, there is no rollback process for the host.

[0095] The following is a specific description of the implementation of rollback processing for each upgraded subsystem when an upgrade exception event is detected during the upgrade process of the host. Among them, the upgrade exception event can be detected when an exception occurs in the target upgrade step of the system upgrade of the host, and the target upgrade step can be any upgrade step among the upgrade steps included in the system upgrade process of the host. It can be understood that if the upgrade exception event is detected during the upgrade process of the host, there may be two situations for the subsystem that has completed the upgrade: one is that the subsystem that has completed the upgrade includes the first subsystem, and the other is that the subsystem that has completed the upgrade includes the first subsystem and the second subsystem. The rollback processing in these two situations is explained below.

[0096] In the case where the upgraded subsystem includes the first subsystem, the specific implementation of rolling back the upgraded subsystems in the upgrade rollback order may include: 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 step required for rolling back the host in the target second subsystem can be determined based on the target upgrade step, and the host in the target second subsystem can be rolled back based on the rollback step; after the host in the target second subsystem is successfully rolled back, it can be further determined whether a virtual machine with a virtualization management service is deployed in the target second subsystem to determine whether it is necessary to roll back the virtual machine with the virtualization management service. If there is a virtual machine with a virtualization management service in the target second subsystem, the virtual machine with a virtualization management service in the target second subsystem can be rolled back; after the virtual machine with a virtualization management service in the target second subsystem is successfully rolled back, the upgraded first subsystem can be rolled back. If there is no virtual machine with a virtualization management service in the target second subsystem, there is no rollback process for the virtual machine with a virtualization management service, and the upgraded first subsystem is directly rolled back.

[0097] The target second subsystem here refers to any second subsystem included in the management system.

[0098] In the case that the subsystems that have completed the upgrade include the first subsystem and the second subsystem, the specific implementation of rolling back the upgraded subsystems in accordance with the upgrade rollback order may include: 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 rolling back the host in the target second subsystem can be determined based on the target upgrade step, and the rollback steps required for rolling back the host in the second subsystem that has completed the upgrade can be determined; it should be noted that, for the host that has only completed a portion of the upgrade (that is, only completed a portion of the steps during the host upgrade process, such as detecting an abnormal upgrade event during the host upgrade process), and the host has completed the upgrade, the rollback steps required for rolling back the host in these two cases are different, and it is necessary to separately determine the rollback steps required for rolling back the host in the target second subsystem and the rollback steps required for rolling back the host in the second subsystem that has completed the upgrade.

[0099] After determining the fallback steps of the host in these two cases, the corresponding hosts can be rolled back based on the fallback steps of the hosts in these two cases. Here, when rolling back multiple hosts, there is also a corresponding rollback order. For example, the hosts in the target second subsystem and the second subsystem that has been upgraded can be rolled back in the reverse order of the upgrade order of the system upgrade of the target second subsystem and the second subsystem that has been upgraded, and based on the rollback steps required for rolling back the hosts in the target second subsystem and the second subsystem that has been upgraded.

[0100] After the host in the target second subsystem and the upgraded second subsystem is successfully rolled back, the target second subsystem and the upgraded second subsystem may further determine whether the virtual machines with virtualization management services need to be rolled back. If the target second subsystem and the upgraded second subsystem have virtual machines with virtualization management services, the virtual machines with virtualization management services in the target second subsystem and the upgraded second subsystem may be rolled back; and after the virtual machines with virtualization management services in the target second subsystem and the upgraded second subsystem are successfully rolled back, the upgraded first subsystem may be rolled back. If the target second subsystem and the upgraded second subsystem do not have virtual machines with virtualization management services, the upgraded first subsystem may be directly rolled back.

[0101] The following specifically describes the rollback steps required for the host to perform rollback processing in the two cases where the host has only partially completed the upgrade and the host has completed the upgrade. In the case where the host has only partially completed the upgrade, the required rollback steps can be dynamically determined based on the upgrade steps where an abnormality occurs during the host upgrade process (such as the target upgrade steps mentioned above), that is, the rollback steps required for the host to perform rollback processing may be different depending on the upgrade steps where an abnormality occurs. In the case where the host has completed the upgrade, the rollback steps required for the host to perform rollback processing are the same, and the host can be rolled back step by step according to the upgrade steps in the upgrade process. The following first describes the complete rollback steps involved in the rollback processing of the host when the host has completed the upgrade.

[0102] As mentioned above, the multiple hosts may include hosts with virtual machines deployed for the primary service of the virtualization management service, and may include hosts with virtual machines deployed for the backup service of the virtualization management service; the multiple hosts may include one or more hosts with hyper-converged management services deployed. Depending on the management services deployed on the host, the fallback steps required for the fallback processing of the host will also be different. In the fallback processing of a single host, the system will be able to dynamically arrange the corresponding fallback steps based on whether the host contains virtualization management services and hyper-converged management services, as well as the upgrade information of the host.

[0103] Optionally, the idea of ​​automatically arranging the rollback steps of the host can be: judging the basic steps to be performed for the rollback according to the upgrade information of the host, and arranging the corresponding processing steps according to whether there is a virtualization management service on the host, and arranging the corresponding processing steps according to whether there is a hyper-convergence management service on the host. The upgrade information of the host may include the service status of the host, etc.

[0104] Based on this, it can be known that the specific implementation of determining the fallback steps required for the fallback processing of each host among the multiple hosts can be described as follows. Considering that the principle of determining the fallback steps of any host among the multiple hosts is consistent, the following takes the target host as an example to specifically explain the determination of the fallback steps. First, the reference fallback steps required for the fallback processing of the target host among the multiple hosts can be determined. The reference fallback steps here can be the basic steps mentioned above; and further determine whether a hyper-converged management service is deployed on the target host. If a hyper-converged management service is deployed on the target host, the first processing step of executing the migration hyper-converged management service can be added to the reference fallback step to obtain the fallback steps required for the fallback processing of the target host; it can also be determined whether a virtualization management service is deployed on the target host. If a virtualization management service is deployed on the target host, the second processing step of executing the master-slave switching processing of the virtualization management service can be added to the reference fallback step to obtain the fallback steps required for the fallback processing of the target host.

[0105] Among them, the reference rollback step may include: a checking step of checking the service status of the target host; a setting step of setting the target host to be temporarily inoperable to set the business service of the target host to an unavailable state; a migration step of the target virtual machine (ordinary virtual machine) on the migration host; a rollback host step of restoring the system version of the target host to the system version before the system upgrade; and a recovery step of restoring the business service of the target host.

[0106] Based on the above description of the rollback steps of the target host, it can be known that in one implementation method, the specific implementation of the rollback processing using the corresponding rollback steps when performing the rollback processing on the target host can be: first check the service status of the target host; after checking that the service status is the target service status (that is, the available status), further determine whether a hyper-converged management service is deployed on the target host. If a hyper-converged management service is deployed on the target host, migrate the hyper-converged management service on the target host; then, the business service of the target host can be set to an unavailable state, and the virtual machines deployed on the target host for providing business services can be migrated, and the system version of the target host can be restored to the system version before the system upgrade; then, it can be determined whether a virtualization management service is deployed on the target host. If a virtualization management service is deployed on the target host, the virtualization management service can be switched between the primary and secondary modes; finally, the business service of the target host can be restored.

[0107] For example, see Figure 5a As shown, the upgrade steps for a single host can be as follows Figure 5a As shown in the process on the left, the rollback of a single host can be as follows Figure 5a If the host is rolled back after the system upgrade is completed, the corresponding rollback process of the host can be found in Figure 5a As shown in the process on the right, you can gradually roll back according to the upgrade steps of the host during the system upgrade process.

[0108] For example, see Figure 5b As shown, the upgrade steps for a single host can be as follows Figure 5b As shown in the process on the left, the rollback of a single host can be as follows Figure 5b In the process on the right side of the host upgrade process, if an upgrade step is abnormal, when the host is rolled back, the rollback steps involved are not rolled back step by step according to the upgrade steps in the upgrade process, but the upgrade step where the abnormality occurs is identified, and the specific rollback operation that needs to be completed for the rollback process is dynamically determined according to the upgrade step. For example, suppose Figure 5b If an exception (error) occurs in the upgrade step of "Upgrade Host" in the process on the left, the corresponding rollback operation only needs to execute the steps of "Roll Back Host", "Master / Slave Switch of Virtualization Management Service (Hosts with Virtualization Management Service)", and "Restore Host Services", and other steps do not need to be executed. In other words, in the rollback process of a single host, the corresponding rollback steps can be dynamically arranged according to whether the host contains virtualization management services and hyper-converged management services, as well as the upgrade information.

[0109] In summary, in the embodiment of the present application, if an abnormality caused by uncontrollable factors occurs at any step in the subsystem upgrade process of the management system, the entire management system can be rolled back in reverse order to ensure the consistency of the system versions of each subsystem in the management system and the system stability. In addition, the rollback sequence of the host can be automatically arranged, and the technician does not need to manually intervene in the rollback sequence after selecting the host. The system can automatically arrange the sequence to achieve automation and intelligence of the rollback process. In addition, the rollback steps of the host can be automatically arranged to effectively improve the stability and automation of the rollback process.

[0110] In one implementation, the system upgrade platform can be called to implement the system upgrade of the management system, and the system upgrade process can be displayed on the relevant interface of the system upgrade platform. Optionally, after initiating the system upgrade task through the task initiation interface of the system upgrade platform, the upgrade process of each subsystem in the management system can be displayed on the system upgrade interface of the system upgrade platform. For example, see Figure 5c The interface shown may be a system upgrade interface, which may include subsystem display areas corresponding to system upgrades of various subsystems, for example, area 51 is the subsystem display area corresponding to subsystem 1, and area 52 is the subsystem display area corresponding to subsystem 2.

[0111] Among them, the subsystem display area of ​​the target subsystem (the target subsystem may refer to any subsystem among multiple subsystems) may include: a situation display area for displaying the upgrade status of the target subsystem during the system upgrade process, an upgrade control (such as control 502) for controlling the upgrade processing of the target subsystem, and a rollback control (such as control 503) for controlling the rollback processing of the target subsystem.

[0112] When the target subsystem needs to be upgraded, the object can trigger the upgrade control corresponding to the target subsystem. For example, assuming that the target subsystem is subsystem 1, the upgrade control is control 502; and when it is detected that the upgrade control in the subsystem display area of ​​the target subsystem is triggered, the target subsystem can be upgraded, that is, the background service device (i.e., the computing device) of the system upgrade platform can execute the upgrade process of the target subsystem; and the upgrade status of the target subsystem during the system upgrade process can be displayed in the subsystem display area of ​​the target subsystem.

[0113] When it is necessary to roll back the target subsystem, the object can 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 it is detected that the rollback control in the subsystem display area of ​​the target subsystem is triggered, the target subsystem can be rolled back, that is, the background service device (i.e., the computing device) of the system upgrade platform can execute the rollback process for the target subsystem.

[0114] Among them, the target subsystem can also include system upgrades of each node, and the situation display area can include a node situation display area for each node (such as a node situation display area 501 for the upgrade status of node (Node) 2), and the nodes included in the target subsystem can be understood as components that need to be upgraded in the target subsystem. It should be noted that when there are multiple nodes in the target subsystem, the multiple nodes can be upgraded in sequence according to the upgrade order for the multiple nodes.

[0115] The node status display area of ​​a node may include a first area for displaying the basic information of the node and a second area for upgrade progress information. The basic information may include the node name, node IP, a status indicating whether the node upgrade is successful (such as the status may be not started, upgrading, failed, upgraded), the progress of the node upgrade, the current version corresponding to the node (the system version before the system upgrade) and the target version (the system version after the system upgrade), the start time of the system upgrade, the time taken for the system upgrade, and the like. For example, area 504 is the first area of ​​Node2, and area 505 is the second area of ​​Node2. The upgrade progress information can be used to display the execution status of the node at each upgrade step, such as the detection of passing the upgrade configuration and the warning of failing the system check displayed in area 505.

[0116] Among them, if the node is not successfully upgraded, the status in the basic information can show "failed". In this case, the object can trigger the fallback control (such as control 506) used to control the fallback processing of the node, and when it is detected that the fallback control for the node is triggered, the node can be rolled back, that is, the background service device (i.e., the computing device) of the system upgrade platform can execute the rollback process for the node. In the case of a single node upgrade failure, during the process of rolling back the node separately, the rollback steps can be assembled according to the management service status of the host where the node is located and the upgrade steps that have abnormalities during the upgrade to determine the rollback steps required for the host rollback processing.

[0117] It can be seen that through the design of the system upgrade platform, the management system can be upgraded with one click. This one-click upgrade feature can provide objects with page-based wizard-style whole-system upgrade capabilities. Compared with manual upgrades, one-click upgrades standardize the upgrade process and upgrade constraints, and have greatly improved automation, stability, and security. It can provide objects with a faster, more efficient, safer, and more reliable upgrade experience, and can also effectively reduce the learning costs and manpower investment of customers and implementation personnel.

[0118] S403: If it is determined that the management system is upgraded successfully, the upgraded management system is run.

[0119] In one implementation, after each subsystem in the management system is successfully upgraded, the system upgrade interface can jump to an upgrade success interface for the successful system upgrade. For example, the upgrade success interface here can be found in Figure 5d As shown. The upgrade success interface can display the upgrade status information of each subsystem in the management system. For example, the upgrade status information of a subsystem may include the name of the subsystem, upgrade status, upgrade start time, upgrade time, etc. Considering that there is a trial operation period for the management system after a successful upgrade in the embodiment of the present application, after each subsystem completes the upgrade, the upgrade status in the upgrade status information of a subsystem displayed in the upgrade success interface can be "Submit after verification" to remind the object that the subsystem is still in the trial operation period. If there is no system service abnormality in the trial operation period, the subsystem will initiate the submission task instruction.

[0120] The upgrade success interface can display the upgrade status information of each subsystem in the management system at multiple time points. Figure 5d As shown, area 507 displays the upgrade status information of each subsystem in the management system when the management system is upgraded at a certain time point. Area 507 may also include a first submission control (such as control 508) for submitting the system upgrade task for the management system. If the management system does not have a system service abnormality during the trial operation period, the object may trigger the first submission control; or, if the management system has a system service abnormality within a preset time period after operation, and after the rollback processing of the management system is completed, the object may also trigger the first submission control.

[0121] In one implementation, when it is detected that the first submission control (such as control 508) for the management system is triggered in the upgrade success interface, a submission prompt pop-up window may be displayed on the upgrade success interface. For example, the submission prompt pop-up window may be as follows: Figure 5eAs shown. The submission prompt pop-up window may include an input area (such as area 509) for inputting the account information of the initiating object that initiates the system upgrade task and a second submission control (such as control 510). The account information may include the object name and the 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. When the initiating object determines to submit the system upgrade task, the second submission control can be triggered. 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 submission control is triggered, it can be determined that the system upgrade task is completed.

[0122] In one implementation, after each subsystem in the management system is successfully upgraded, a corresponding upgrade details interface can be displayed based on the specific subsystem, such as object click Figure 5d Neutron system 1, then Figure 5d The system upgrade interface shown can jump to Figure 5f The upgrade details page for subsystem 1 is shown.

[0123] It is understandable that after the management system is successfully upgraded, there will be a trial operation period (i.e. a preset period of time). If there are system service anomalies caused by uncontrollable factors during the trial operation, you can Figure 5f In the interface shown in the figure, each subsystem is rolled back in the reverse order of its upgrade sequence. If the system service does not show any abnormality after the trial operation period, the system upgrade platform system can give a submission prompt (such as Figure 5e The interface shown in the figure) is used to guide the object to complete the submission operation.

[0124] From the description of the above interface, it can be seen that in the system upgrade of the management system, if all subsequent subsystems are upgraded and uncontrollable risks are encountered during the observation period, it can also support rolling back the subsystem upgrade process in reverse order directly on the interface to ensure that the upgrade abnormality does not affect user services. In addition, by providing a Web page (such as the various interfaces mentioned above), the entire rollback process can be visually monitored and operated to ensure that the entire upgrade process is manageable and controllable, eliminating the risks caused by uncontrollable factors. In addition, the features of each subsystem in the management system (such as a hyper-converged system) that supports single-node upgrades, rollbacks, and submissions can be used to orchestrate the node upgrade steps or rollback steps, and the algorithm can be used to maximize the automation and stability of system upgrades and rollbacks.

[0125] S404: If a system service abnormality occurs in the management system within a preset time period after operation, a rollback process is performed on the second subsystem in the management system.

[0126] It is understandable that if a system service anomaly occurs during operation of a successfully upgraded management system, it can be determined that there is a problem with the management system after the system upgrade, or that 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, that is, the system version of the management system after the system upgrade can be restored to the system version before the system upgrade.

[0127] Based on this, if a system service anomaly occurs in the management system within a preset time period after operation, the management system can be rolled back. During the rollback process, the second subsystem in the management system can be rolled back first so that the system version of the upgraded second subsystem can be restored to the system version before the system upgrade.

[0128] As mentioned above, in addition to the host, the second subsystem may also include a virtual machine with a virtualization management service; when the second subsystem includes a host and a virtual machine with a virtualization management service, the host may be rolled back first, and then the virtual machine with the virtualization management service may be rolled back.

[0129] The number of the second subsystems may be one or more. In one implementation, when the number of the second subsystems is one and the second subsystem includes a host and a virtual machine with a virtualization management service, the host in the second subsystem may be directly rolled back first, and then the virtual machine with a virtualization management service in the second subsystem may be rolled back. In another implementation, when the number of the second subsystems is one and the second subsystem includes a host, the host in the second subsystem may be directly rolled back.

[0130] In one implementation, when there are multiple second subsystems, there are also multiple hosts involved. In this case, multiple hosts need to be rolled back; after multiple hosts are successfully rolled back, multiple virtual machines with virtualization management services in the second subsystems can be rolled back. When rolling back multiple hosts, there can be a corresponding rollback sequence for these multiple hosts, so that the multiple hosts can be rolled back in sequence according to this rollback sequence; for the convenience of description, the rollback sequence here can be referred to as the host rollback sequence.

[0131] Optionally, similar to the principle of determining the host upgrade order of multiple hosts, the host fallback order of multiple hosts can also be determined based on the standby service and standby service for the virtualization management service deployed in the hosts of the multiple second subsystems. In one embodiment, the host with the standby service deployed can be used as the first host to fall back, and the host with the main service deployed can be used as the last host to fall back, while the fallback order of other hosts in the multiple hosts is not limited and can be arranged in any way. In general, the host fallback order can be determined according to the existence of the management service and the main and standby services of the management service, and it is ensured that the host with the standby service of the virtualization management service is first rolled back, and the host with the main service of the virtualization management service is rolled back last. Through this host fallback order determination method, it can be effectively guaranteed that the business services provided by the management system are not interrupted when the main and standby switching is performed during the system fallback process. 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 main service, then the fallback order of these 3 hosts (from first to last order) can be: host 2, host 1, host 3.

[0132] It is understandable that, in addition to the host with the primary service and the backup service deployed, one or more hosts may also be included. In the case where there are multiple hosts, the fallback order of these multiple hosts may be determined randomly or according to a preset rule. The principle is consistent with the principle of determining the upgrade order of these multiple hosts mentioned above, and will not be repeated here.

[0133] Optionally, each host has a corresponding rollback step when performing the rollback process. The specific implementation of performing the rollback process on multiple hosts in sequence according to the host rollback order can be: first determine the rollback steps required for performing the rollback process on each of the multiple hosts; then perform the rollback process on the multiple hosts in sequence according to the host rollback order, and perform the rollback process on each host using the corresponding rollback steps. The specific description of using the corresponding rollback steps when performing the rollback process on each host can refer to the relevant description in the above step S402, which will not be repeated here; for example, the specific description of using the corresponding rollback steps when performing the rollback process on each host can refer to Figure 5a The fallback process shown on the right side of the Figure 5b The fallback process is shown on the right side of the figure.

[0134] For example, assuming that the management system includes three hosts: host 1, host 2, host 3, and the host rollback order of these three hosts is: host 3, host 2, host 1, then when the rollback process is performed on these three hosts, host 3 is firstly rolled back according to the rollback steps required for the rollback process of host 3, and after the rollback process of host 3 is completed, host 2 is rolled back according to the rollback steps required for the rollback process of host 2, and after the rollback process of host 2 is completed, host 1 is rolled back according to the rollback steps required for the rollback process of host 1. It can be understood that the rollback steps required for the rollback process of host 1, host 2, and host 3 are consistent.

[0135] S405: After the second subsystem is successfully rolled back, the first subsystem in the management system is rolled back.

[0136] As mentioned above, the first subsystem corresponds to the hyper-converged management service. After completing the rollback of the second subsystem, the first subsystem in the management system can be rolled back. By rolling back 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 to ensure the consistency of the system versions of each subsystem in the management system.

[0137] It is understandable that in the system upgrade of the management system, the upgrade of the host, virtual machine management service and hyper-converged management service is involved. If an abnormal upgrade event is detected, or after the upgraded management system is successfully run, a system service abnormality occurs in the management system within a preset time period, a rollback process is required; the rule for the rollback process is that multiple subsystems are rolled back in the reverse order of the upgrade order.

[0138] In addition, the principle of overall rollback is to roll back the host first, then the virtual machine management service, and finally the hyper-converged management service. Figure 5g As shown, assuming that the management system includes three hosts: host 1, host 2 and host 3, when the management service is rolled back, host 1, host 2 and host 3 are rolled back first, and then the virtual machines of the virtualization management service on host 1 and the virtual machines of the virtualization management service on host 3 are rolled back, and finally the hyper-converged management service on host 1, host 2 and host 3 is rolled back.

[0139] It can be seen that in the embodiments of the present application, a reliable overall rollback solution can be provided for the uncontrollable risks that may occur during the system upgrade of the management system. The rollback processing can be integrated and arranged by integrating and arranging the characteristics of each subsystem supporting the individual rollback of a single host. After the upgrade of a single subsystem is successful, the upgrade data can be temporarily not cleared, and after all subsystems are upgraded, a period of observation period is given before clearing all upgrade data to observe whether all functions of the management system are available after the system upgrade, so as to support the rollback of the integrated system before the upgrade, and ensure that the normal use of the management system by the object is not affected in the abnormal upgrade scenario. In a specific application scenario, the management system can be a hyper-converged system (or a hyper-converged product). In the system upgrade of the hyper-converged system, the system upgrade method proposed in the embodiments of the present application can ensure that the customer business is not interrupted during the upgrade of the hyper-converged system, and the upgrade window period can be minimized.

[0140] To better understand the system upgrade method proposed in the embodiment of the present application, the following combination Figure 5h For further explanation, see, for example, Figure 5h As shown, when the computing device responds to a system upgrade task for a management system including multiple subsystems, the subsystems in the management system may be upgraded first. In the system upgrade process, the first subsystem in the management system (i.e., the subsystem for the hyper-converged management service) may be upgraded first, and then the second subsystem (i.e., the subsystem consisting of the host and the virtual machines with virtualization management services deployed on the host) may be upgraded. Specifically, the software upgrade package for the hyper-converged management service may be distributed first, and then the hyper-converged management service may be checked. After the check is passed, the hyper-converged management service may be upgraded using the software upgrade package; after the upgrade of the hyper-converged management service is completed, the software upgrade package for the host and the virtualization management service may be distributed again, and then the host and the virtualization management service may be checked. After the check is passed, the host and the virtualization management service may be upgraded using the software upgrade package; thereby completing the upgrade of the management system.

[0141] After confirming that the management system has been successfully upgraded, the upgraded management system can be run, that is, the system service operation test of the management system can be performed to determine whether the system service can operate normally. If the system service can operate normally within the preset time period after the operation (such as the system service can operate normally within the trial operation period of more than 3 days), that is, the management system has no system service abnormalities, then a submission trigger instruction can be initiated. The submission trigger instruction can be used to trigger the submission of an instruction indicating the successful completion of the system upgrade task. Through the submission trigger instruction, the object can be prompted to submit an instruction indicating the successful completion of the system upgrade task. If the system service is abnormal within the preset time period after the operation, that is, the management system has a system service abnormality, the management system can be rolled back in the overall rollback order to restore the system version of the management system to the system version before the system upgrade. The process of rolling back the management system can first roll back the second subsystem in the management system, and then roll back the first subsystem.

[0142] Specifically, the process of rolling back the management system according to the overall rollback order may be: the rollback order of the host and virtual machine management services corresponding to the second subsystem may be dynamically arranged first, and then the rollback steps for the host in the second subsystem to roll back may be dynamically arranged, so as to roll back the host and virtual machine management services corresponding to the second subsystem in combination with the rollback order and the rollback steps. After completing the rollback processing of the second subsystem, the rollback order of the hyper-converged management service corresponding to the first subsystem may be arranged, and the rollback steps for the hyper-converged management service to roll back may be dynamically arranged, so as to roll back the hyper-converged management service corresponding to the first subsystem in combination with the rollback order and the rollback steps. After completing the rollback processing of the management system, a submit trigger instruction may be initiated to complete the system upgrade of the management system.

[0143] In the embodiment of the present application, when an exception occurs during the upgrade process of the subsystem of the management system, the upgraded subsystems can be rolled back in sequence according to the upgrade order of the subsystems; and after the overall upgrade of the management system is completed, the management system after the successful upgrade is run to observe whether all the functions of the management system after the successful upgrade are available. If it is determined that all functions cannot be used, the overall reverse rollback can be performed according to the upgrade order of the subsystems; thereby effectively ensuring the consistency of the system versions and the system stability of each subsystem in the management system, so as to ensure that users can continue to use the system normally. In addition, unified monitoring and management of the upgrade and rollback processes of different subsystems in the management system can be achieved, supporting the sequential rollback of multiple subsystems, and effectively reducing the operation and maintenance risks.

[0144] See also Figure 6 , Figure 6: is a schematic diagram of a system upgrade device provided in an embodiment of the present application. The system upgrade device described in this embodiment includes:

[0145] An upgrading unit 601 is used for performing a system upgrade on a subsystem in the management system in response to a system upgrade task for the management system including multiple subsystems;

[0146] The rollback unit 602 is used to determine the upgrade rollback sequence according to the upgrade sequence of each upgraded subsystem if an upgrade abnormality event is detected, and perform rollback processing on each upgraded subsystem according to the upgrade rollback sequence to restore the system version of each upgraded subsystem to the system version before the system upgrade;

[0147] The running unit 603 is used to run the successfully upgraded management system if it is determined that the management system is successfully upgraded;

[0148] The rollback unit 602 is also used to roll back the management system according to the overall rollback sequence if a system service anomaly occurs in the management system within a preset time period after operation, so as to restore the system version of the management system to the system version before the system upgrade.

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

[0150] 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.

[0151] In one implementation, the multiple subsystems include: a first subsystem with a hyper-converged management service, a host, and a second subsystem consisting of a virtual machine with a virtualization management service deployed on the host, wherein the first subsystem is used to provide management services to the second subsystem; the rollback unit 602 is specifically used to:

[0152] Performing rollback processing on the second subsystem in the management system so that the system version of the upgraded second subsystem is restored to the system version before the system upgrade;

[0153] After the second subsystem is successfully rolled back, the first subsystem in the management system is rolled back so that the system version of the upgraded first subsystem is restored to the system version before the system upgrade.

[0154] In one implementation, the number of the second subsystems is multiple, and the hosts corresponding to the multiple second subsystems include a host on which a virtual machine of a primary service for a virtualization management service is deployed, and a host on which a virtual machine of a backup service for a virtualization management service is deployed; the rollback unit 602 is specifically used to:

[0155] Determine a host rollback order for rolling back the multiple hosts based on the standby services and the standby services for the virtualization management service deployed in the hosts of the multiple second subsystems;

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

[0157] 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.

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

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

[0160] 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.

[0161] In one implementation, the multiple hosts include a host on which a virtual machine of a primary service for a virtualization management service is deployed, and include a host on which a virtual machine of a backup service for a virtualization management service is deployed; the rollback unit 602 is specifically configured to:

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

[0163] 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 rollback processing on the target host;

[0164] 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.

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

[0166] Checking the service status of the target host;

[0167] 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;

[0168] 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;

[0169] 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.

[0170] In one implementation, 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; the rollback unit 602 is specifically used to:

[0171] 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 performing a rollback process on the host in the target second subsystem is determined based on the target upgrade step, and a rollback process is performed on the host in the target second subsystem based on the rollback step;

[0172] 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, a rollback process is performed on the virtual machine with a virtualization management service in the target second subsystem;

[0173] 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.

[0174] In one implementation, 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 to the second subsystem; the upgraded subsystem includes the first subsystem and the second subsystem; the rollback unit 602 is specifically used to:

[0175] 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;

[0176] 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;

[0177] 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;

[0178] 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.

[0179] In one implementation, the multiple subsystems include: a first subsystem with a hyper-converged management service, a host, and a second subsystem consisting of a virtual machine with a virtualization management service deployed on the host, wherein the first subsystem is used to provide management services to the second subsystem; the upgrade unit 601 is specifically used to:

[0180] 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;

[0181] 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.

[0182] In one implementation, the upgrading unit 601 is further configured to:

[0183] 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;

[0184] 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.

[0185] In one implementation, the subsystem display area of ​​the target subsystem further includes a rollback control for controlling the target subsystem to perform rollback processing; the rollback unit 602 is further used to:

[0186] 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.

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

[0188] 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;

[0189] 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;

[0190] 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.

[0191] See also Figure 7 , Figure 7 701, memory 702, and network interface 703. The processor 701, memory 702, and network interface 703 can exchange data.

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

[0193] The memory 702 may include a read-only memory and a random access memory, and provide program instructions and data to the processor 701. A portion of the memory 702 may also include a non-volatile random access memory. When the processor 701 calls the program instructions, it is used to execute:

[0194] In response to a system upgrade task for a management system including a plurality of subsystems, performing a system upgrade on a subsystem in the management system;

[0195] If an abnormal upgrade event is detected, the upgrade rollback sequence is determined according to the upgrade sequence of each upgraded subsystem, and each upgraded subsystem is rolled back according to the upgrade rollback sequence, so that the system version of each upgraded subsystem is restored to the system version before the system upgrade;

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

[0197] If a system service anomaly occurs in the management system within a preset time period after operation, the management system is rolled back in accordance with the overall rollback sequence so that the system version of the management system is restored to the system version before the system upgrade.

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

[0199] 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.

[0200] In one implementation, the multiple subsystems include: a first subsystem with a hyper-converged management service, a host, and a second subsystem consisting of a virtual machine with a virtualization management service deployed on the host, wherein the first subsystem is used to provide management services to the second subsystem; the processor 701 is specifically used to:

[0201] Performing rollback processing on the second subsystem in the management system so that the system version of the upgraded second subsystem is restored to the system version before the system upgrade;

[0202] After the second subsystem is successfully rolled back, the first subsystem in the management system is rolled back so that the system version of the upgraded first subsystem is restored to the system version before the system upgrade.

[0203] In one implementation, the number of the second subsystems is multiple, and the hosts corresponding to the multiple second subsystems include a host on which a virtual machine of a primary service for a virtualization management service is deployed, and a host on which a virtual machine of a backup service for a virtualization management service is deployed; the processor 701 is specifically configured to:

[0204] Determine a host rollback order for rolling back the multiple hosts based on the standby services and the standby services for the virtualization management service deployed in the hosts of the multiple second subsystems;

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

[0206] 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.

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

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

[0209] 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.

[0210] In one implementation, the multiple hosts include a host on which a virtual machine of a primary service for a virtualization management service is deployed, and include a host on which a virtual machine of a backup service for the virtualization management service is deployed; the processor 701 is specifically configured to:

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

[0212] 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 rollback processing on the target host;

[0213] 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.

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

[0215] Checking the service status of the target host;

[0216] 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;

[0217] 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;

[0218] 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.

[0219] In one implementation, 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, wherein the first subsystem is used to provide management services to the second subsystem; the upgraded subsystem includes the first subsystem; the processor 701 is specifically used to:

[0220] 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 performing a rollback process on the host in the target second subsystem is determined based on the target upgrade step, and a rollback process is performed on the host in the target second subsystem based on the rollback step;

[0221] 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, a rollback process is performed on the virtual machine with a virtualization management service in the target second subsystem;

[0222] 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.

[0223] In one implementation, 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, wherein the first subsystem is used to provide management services to the second subsystem; the upgraded subsystem includes the first subsystem and the second subsystem; the processor 701 is specifically used to:

[0224] 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;

[0225] 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;

[0226] 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;

[0227] 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.

[0228] In one implementation, the multiple subsystems include: a first subsystem with a hyper-converged management service, a host, and a second subsystem consisting of a virtual machine with a virtualization management service deployed on the host, wherein the first subsystem is used to provide management services to the second subsystem; the processor 701 is specifically used to:

[0229] 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;

[0230] 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.

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

[0232] 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;

[0233] 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.

[0234] In one implementation, the subsystem display area of ​​the target subsystem further includes a rollback control for controlling the target subsystem to perform rollback processing; the processor 701 is further configured to:

[0235] 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.

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

[0237] 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;

[0238] 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;

[0239] 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.

[0240] The embodiment of the present application also provides a chip, which is set in a computing device and is used to execute the method described in the above corresponding embodiment, which will not be described in detail here. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0241] Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

[0242] The present application also provides a computer storage medium on which a computer program is stored. The computer program includes program instructions. When the program instructions are executed by a computing device, the functions of any of the above method embodiments are implemented.

[0243] The above-mentioned computer storage media include but are not limited to flash memory, hard disk, and solid state drive.

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

[0245] The scheme described in the present application can be implemented in various ways. For example, these technologies can be implemented in hardware, software or a combination of hardware. For hardware implementation, the processing unit of the related technology of executing the above method can be implemented in one or more general-purpose processors, digital signal processors (digital signal processor, DSP), digital signal processing devices, application specific integrated circuits (application specific integrated circuit, ASIC), programmable logic devices, field programmable gate arrays (field programmable gate array, FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or any combination of the above. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any traditional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0246] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented 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, all or part of the processes or functions described in the embodiments of the present application are generated. The computer instructions may be stored in a computer storage medium or transmitted from one computer storage medium to another computer storage medium.

[0247] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0248] The preset (such as preset period) in the present application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, curing, or pre-burning.

[0249] Those skilled in the art may understand that, for the convenience and brevity of description, the specific working processes of the computing devices and units described above may refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0250] The same or similar parts between the various embodiments in this application can refer to each other. In the various embodiments in this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of this application do not constitute a limitation on the scope of protection of this 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, the upgrade rollback order is determined according to the upgrade order of each upgraded subsystem, and the upgraded subsystems are 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, characterized in that: Also includes: 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, characterized in that The number of the second subsystems is multiple, and the hosts corresponding to the multiple second subsystems include a host on which a virtual machine of a primary service for a virtualization management service is deployed, and a host on which a virtual machine of a backup service for a virtualization management service is deployed; the rollback processing of the second subsystem in the management system includes: 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, characterized in that: The step of sequentially performing rollback processing on the multiple hosts according to the host rollback order includes: 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, characterized in that The multiple hosts include a host on which a virtual machine of a primary service for the virtualization management service is deployed, and a host on which a virtual machine of a backup service for the virtualization management service is deployed; The step of determining the rollback steps required for performing rollback processing on each of the plurality of hosts includes: 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 the rollback process on each host using corresponding rollback steps includes: 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, characterized in that 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 rollback processing of 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, characterized in that 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, wherein the first subsystem is used to provide management services for the second subsystem; and the system upgrade of the subsystems in the management system includes: 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, characterized in that: Also includes: 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 includes a rollback control for controlling the target subsystem to perform rollback processing; and further includes: 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, characterized in that: Also includes: 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, characterized in that: The method comprises 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.

Images