A patch upgrading method and device, an operation server and a storage medium

Abstract

Embodiments of the present application disclose a patch upgrading method and device, an operation server and a storage medium. The method comprises: in response to a patch upgrading instruction, obtaining a patch upgrading script, wherein the patch upgrading script comprises at least one of a domain control server upgrading script, a management cluster upgrading script, a computing cluster upgrading script and a storage cluster upgrading script; and for at least one intradomain server of a software-defined data center located under the same domain control, performing patch upgrading on the at least one intradomain server by calling and executing the patch upgrading script. The technical solution of the embodiments of the present application can realize integrated upgrading of a Windows server SDDC.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a patch upgrade method, apparatus, operating server and storage medium. Background Technology

[0002] With the rapid development of cloud computing, it has served various fields and achieved remarkable results, with advantages such as high flexibility, dynamic expansion and high resource utilization efficiency.

[0003] For Software Defined Data Centers (SDDCs) that rely on cloud computing technologies, regular patch upgrades are necessary to ensure the secure and stable operation of the data center. However, current patch upgrade solutions are not very effective and need improvement. Summary of the Invention

[0004] This invention provides a patch upgrade method, apparatus, operating server, and storage medium to achieve an integrated patch upgrade effect for Windows Server SDDC.

[0005] According to one aspect of the present invention, a patch upgrade method is provided, applied to an operation server, the method comprising:

[0006] In response to a patch upgrade command, retrieve the patch upgrade script;

[0007] For at least one server in a software-defined data center located under the same domain controller, patch upgrades are performed on at least one server in the domain by calling and executing a patch upgrade script;

[0008] The patch upgrade scripts include at least one of the following: domain controller server upgrade script, management cluster upgrade script, compute cluster upgrade script, and storage cluster upgrade script.

[0009] According to another aspect of the present invention, a patch upgrade apparatus is provided, configured on an operation server, the apparatus comprising:

[0010] The patch upgrade script retrieval module is used to retrieve the patch upgrade script in response to a patch upgrade command.

[0011] The patch upgrade module is used to upgrade at least one domain server in a software-defined data center located under the same domain controller by calling and executing a patch upgrade script.

[0012] The patch upgrade scripts include at least one of the following: domain controller server upgrade script, management cluster upgrade script, compute cluster upgrade script, and storage cluster upgrade script.

[0013] According to another aspect of the present invention, an operation server is provided, which may include:

[0014] At least one processor; and

[0015] A memory that is communicatively connected to at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by at least one processor, such that when the at least one processor executes the program, it implements the patch upgrade method provided in any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided having computer instructions stored thereon for causing a processor to execute and implement the patch upgrade method provided in any embodiment of the present invention.

[0018] The technical solution of this invention, in response to a patch upgrade command, obtains a patch upgrade script, which includes at least one of a domain controller server upgrade script, a management cluster upgrade script, a compute cluster upgrade script, and a storage cluster upgrade script. For at least one domain server located in a software-defined data center under the same domain controller, the patch upgrade script is invoked and executed to perform a patch upgrade on at least one domain server. This technical solution achieves the effect of integrated patch upgrades for Windows Server SDDC, that is, it achieves patch upgrades for the operating system and various hardware and software components of the Windows Server SDDC.

[0019] It should be understood that the description in this section is not intended to identify key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of a patch upgrade method provided by an embodiment of the present invention;

[0022] Figure 2 This is a flowchart of another patch upgrade method provided by an embodiment of the present invention;

[0023] Figure 3 This is a flowchart of an optional example of another patch upgrade method provided according to an embodiment of the present invention;

[0024] Figure 4 This is a flowchart of another patch upgrade method provided by an embodiment of the present invention;

[0025] Figure 5 This is a flowchart of an optional example of another patch upgrade method provided according to an embodiment of the present invention;

[0026] Figure 6 This is a structural block diagram of a patch upgrade device provided according to an embodiment of the present invention;

[0027] Figure 7 This is a schematic diagram of the structure of the operation server that implements the patch upgrade method of this invention. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. The same applies to "target," "original," etc., and will not be repeated here. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] Figure 1This is a flowchart of a patch upgrade method provided in an embodiment of the present invention. This embodiment is applicable to patch upgrades of Windows Server SDDC, and is particularly applicable to patch upgrades of various aspects of Windows Server SDDC. The method can be executed by the patch upgrade device provided in this embodiment of the present invention. This device can be implemented in software and / or hardware, and can be integrated into an operating server, which can also be called an operating machine.

[0031] To better understand the patch upgrade method in the embodiments of the present invention, the operator machine in the embodiments of the present invention will be described by way of example first.

[0032] When performing patch upgrades on a Windows Server SDDC, a Windows Server operator machine (physical or virtual machine) can be created. However, considering that patch upgrades involve a host machine restart, if the host machine and operator machine are deployed in the same Windows Server SDDC environment, the operator machine will be shut down when the host machine restarts, which will directly affect the subsequent patch upgrade process. Therefore, the operator machine is deployed in a domain other than the current Windows Server SDDC, that is, the operator machine and the host machine are deployed in different Windows Server SDDC environments, thereby excluding the operator machine from the patch upgrade sequence.

[0033] Windows Server SDDC patch upgrades can be understood as patch upgrades targeting the Windows Server SDDC Fabirc server. This Fabirc server includes domain controllers (Active Directory, AD), management virtual machines / physical machines, compute / storage physical machines, and Software Defined Network (SDN) virtual machines / physical machines, among other domain servers. To control these domain servers via an operator, the operator can be added to the domain controller of the target Windows Server SDDC environment being upgraded. This means adding the operator to the domain controller where the target server resides. Then, the operator can directly send commands to the corresponding domain server via ICM (In-Process Communication) to achieve control over the domain server. It's worth noting that this operator can also handle patch upgrades for multiple Windows Server SDDC environments. Simply remove the operator from the domain and rejoin it to the new Windows Server SDDC domain controller, thus improving operator reuse and offering state-of-the-art advantages.

[0034] In addition, a Domain User account with Admin and NCAdmin privileges can be provided for the operator machine to issue commands for Windows Server SDDC patch upgrades. In practice, optionally, SQL Server Express 2016 / 2019 is used as the database to record every command issued by the operator machine. Since the operator machine cannot access the internet in a closed environment, the root certificate online verification function can be disabled in the operator machine group policy to improve user experience. Furthermore, to directly view the status of the upgrade cluster nodes on the operator machine during patch upgrades, the RSAT-ADDS, RAST-Hyper-V-Tools, RAST-Clustering, RAST-Storage-Replica, and RSAT-NLB functional roles can be configured.

[0035] See Figure 1 The method of this invention specifically includes the following steps:

[0036] S110. In response to a patch upgrade command, obtain a patch upgrade script, wherein the patch upgrade script includes at least one of a domain controller server upgrade script, a management cluster upgrade script, a compute cluster upgrade script, and a storage cluster upgrade script.

[0037] The patch upgrade script can be a script already deployed on the operating machine for implementing patch upgrades of Windows Server SDDC. In practical applications, optionally, this patch upgrade script includes at least one of the following: a domain controller upgrade script, a management cluster upgrade script, a compute cluster upgrade script, and a storage cluster upgrade script. The domain controller upgrade script can be used to implement AD patch upgrades on at least one domain server of Windows Server SDDC; the management cluster upgrade script can be used to implement patch upgrades on management virtual machines and management hosts on the at least one domain server; the compute cluster upgrade script can be used to implement patch upgrades on compute hosts on the at least one domain server; and the storage cluster upgrade script can be used to implement patch upgrades on storage hosts. In other words, these patch upgrade scripts cover all aspects of Windows Server SDDC, specifically the operating system and hardware / software. Optionally, this patch upgrade script can be written using PowerShell commands.

[0038] Alternatively, after writing at least one patch upgrade script, the process designer (i.e., process orchestration tool) can be used to orchestrate the at least one patch upgrade script. For example, the at least one patch upgrade script can be loaded into the process designer, and then the process designer can select the required patch upgrade scripts under the current Windows server SDDC from the at least one patch upgrade script, thereby determining the execution flow of these required patch upgrade scripts and adding the corresponding parameters, thus achieving the effect of patch upgrade process orchestration.

[0039] Based on this, the operator receives the patch upgrade script in response to a patch upgrade command that can be used to instruct the Windows server SDDC to perform a patch upgrade.

[0040] S120. For at least one domain server in a software-defined data center located under the same domain controller, perform a patch upgrade on at least one domain server by calling and executing a patch upgrade script.

[0041] Specifically, for at least one domain server of the Windows Server SDDC located under the same domain controller as the operator machine, that is, at least one domain server that can be controlled by the operator machine, the patch upgrade script is called and executed to upgrade the at least one domain server, thereby realizing the integrated upgrade of the Windows Server SDDC.

[0042] The technical solution of this invention, in response to a patch upgrade command, obtains a patch upgrade script, which includes at least one of a domain controller server upgrade script, a management cluster upgrade script, a compute cluster upgrade script, and a storage cluster upgrade script. For at least one domain server located in a software-defined data center under the same domain controller, the patch upgrade script is invoked and executed to perform a patch upgrade on at least one domain server. This technical solution achieves the effect of integrated patch upgrades for Windows Server SDDC, that is, it achieves patch upgrades for the operating system and various hardware and software components of the Windows Server SDDC.

[0043] An optional technical solution, before performing a patch upgrade on at least one server within the domain by calling and executing the patch upgrade script, the patch upgrade method further includes: obtaining an environment pre-check script, and performing an environment pre-check on the software-defined data center by calling and executing the environment pre-check script; wherein the environment pre-check script is used to export basic information of the software-defined data center, view the exported basic information, and distribute at least one of the patch files.

[0044] To ensure the smooth implementation of Windows Server SDDC patch upgrades, an environment pre-check can be performed on the Windows Server SDDC before the upgrade. This environment pre-check can include exporting and viewing basic Windows Server SDDC information and distributing patch files. To this end, an environment pre-check script can be pre-written to implement the above-mentioned environment pre-check functions, and the Windows Server SDDC environment pre-check can be achieved by calling and executing this script. In practical applications, optionally, the exported basic information can cover information such as cluster nodes, servers, MGMT virtual machines, SDN virtual machines, COMP cluster virtual machines, and cluster fileshares. A fileshare can be understood as a logical volume added to the storage cluster within the compute cluster. Optionally, the viewing function can be used to observe the health status of each cluster node, such as VMM, MGMT, and SQL, before the Windows Server SDDC upgrade, as well as whether clock synchronization is working properly. The above technical solution can resolve known risks associated with Windows Server SDDC before patch upgrades, thereby improving the smoothness of the Windows Server SDDC patch upgrade process.

[0045] In practical applications, in addition to exporting basic information via the environment pre-check script, NC information can also be exported. This allows users to view both the exported basic information and the exported NC information. The exported NC information records virtual machine PIP, Vet, and other information. If a virtual machine is restored and PIP is lost, it can be recovered using the exported NC information. Furthermore, it's necessary to check the X722 onboard network card information. The X722 is the onboard network card on the motherboard. This step checks the storage involved in the management cluster, storage cluster, and SDN cluster. Therefore, it's necessary to check if the X722 on the cluster host is disabled. If it is not disabled, it will cause anomalies in the providers listed in Virtual Machine Manager (VMM). It should be noted that VMM is the management tool for Windows Server SDDC, which can be used to create virtual machines, etc.

[0046] Alternatively, before patching, you can check if the NCHost agent and SLBHost agent services on the host machine are functioning correctly. If these two services are not running, it may affect PIP communication and Software Load Balance (SLB). Also, you can check very large virtual machines, because in practice, it has been found that virtual machines with >= 256GB of memory are shut down during the save process; therefore, this should be checked before patching.

[0047] Another optional technical solution, after patching at least one domain server by calling and executing the patch upgrade script, further includes: upon detecting a patch rollback event, in response to the patch rollback event, performing a patch upgrade on at least one domain server that rolled back the patch. Considering the possibility of patch rollback during Windows Server SDDC patch upgrades, the rolled-back domain server can be upgraded individually. This rolled-back domain server can be at least one of MGMTVM, SDNVM, and the host machine. This technical solution achieves the effect of individually upgrading a specified domain server in the event of patch rollback, thereby improving the robustness and reliability of Windows Server SDDC and reducing the risk of occasional patch installation instability.

[0048] Figure 2This is a flowchart of another patch upgrade method provided in this embodiment of the invention. This embodiment is based on the above-mentioned technical solutions and optimized. In this embodiment, optionally, the patch upgrade script includes a domain controller server upgrade script. By calling and executing the patch upgrade script, at least one domain server is patched and upgraded, including: for a first domain controller server and a second domain controller server among at least one domain server, by calling and executing the domain controller server upgrade script, the first domain controller server and the second domain controller server are patched and upgraded in batches; further optionally, the patch upgrade script also includes a management cluster upgrade script, which includes a management virtual machine upgrade script and a management host upgrade script. By calling and executing the patch upgrade script, at least one domain server is patched and upgraded. This includes: controlling the shutdown of the Virtual Machine Manager Cluster Service and Structured Query Language Cluster Service deployed on at least one management virtual machine in a domain server; performing patch upgrades on the management virtual machine after the service shutdown by calling and executing a management virtual machine upgrade script; controlling the management virtual machine to a maintenance state and shutting down the management cluster storage resources and cluster services deployed on at least one management host machine in a domain server that hosts the management virtual machine; and performing patch upgrades on the management host machine after the service shutdown by calling and executing a management host machine upgrade script. The explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0049] See Figure 2 The method in this embodiment may specifically include the following steps:

[0050] S210. In response to the patch upgrade command, obtain the patch upgrade script, wherein the patch upgrade script includes the domain controller server upgrade script, the management virtual machine upgrade script, and the management host machine upgrade script.

[0051] Among them, the management virtual machine upgrade script can be used to implement patch upgrades for management virtual machines in at least one domain server, and the management host upgrade script can be used to implement patch upgrades for management host machines in the at least one domain server.

[0052] S220. Identify at least one intradomain server in a software-defined data center located under the same domain controller.

[0053] S230. For at least one domain controller server and a second domain controller server in a domain, patch upgrades are performed on the first domain controller server and the second domain controller server in batches by calling and executing the domain controller server upgrade script.

[0054] In practical applications, at least one domain server includes a first domain controller (i.e., the first Active Directory) and a second domain controller (i.e., the second Active Directory). When patching and upgrading these two Active Directory servers, to ensure that at least one of them can operate normally, a batch online upgrade approach can be adopted. Specifically, by calling and executing the domain controller server upgrade script, the active-active first and second Active Directory servers are upgraded online in batches (i.e., rolling upgrades), thus not affecting the normal operation of services on the Active Directory servers.

[0055] S240. For at least one management virtual machine in a domain server, control the shutdown of the Virtual Machine Manager Cluster Service and the Structured Query Language Cluster Service deployed on the management virtual machine.

[0056] When patching and upgrading the management cluster, a method can be adopted: first managing the virtual machine class (MGMTVM), then managing the host machine. Specifically, before upgrading MGMTVM, the operator can control the VMM cluster service and the Structured Query Language (SQL) cluster service deployed on MGMTVM to stop running. This can be done by sending a command to MGMTVM to stop the two cluster services deployed on it. This is to prevent unknown factors from interfering with the patch upgrade.

[0057] S250. By calling and executing the management virtual machine upgrade script, patch upgrades are performed on the management virtual machine after the service stops running.

[0058] Since both cluster services deployed on MGMTVM have stopped running, all unknown factors that could interfere with the patch upgrade process have been eliminated. At this point, the management virtual machine can be patched and upgraded by calling and executing the management virtual machine upgrade script after the service stops running, thus ensuring the effective upgrade of the management virtual machine.

[0059] S260. For at least one management host machine in a domain server that hosts management virtual machines, control the management virtual machines to be in maintenance state, and stop the operation of management cluster storage resources and cluster services deployed on the management host machine.

[0060] After the MGMTVM upgrade check is complete, the management host machine hosting the MGMTVM can be patched. Specifically, this includes patching the operating system, network card driver firmware, and RAID card. Before upgrading the management host machine, all MGMTVMs should be put into maintenance mode. This is because without this operation, if the host machine restarts, the MGMTVMs hosted on it will perceive a sudden power outage, potentially causing some data to be missed and affecting the operation of the virtual machines. In addition, before upgrading the management host machine, the management cluster storage resources and cluster services deployed on it can be stopped. In fact, management clusters, storage clusters, and SDN clusters all involve storage; therefore, when shutting down services, storage can be shut down first, in the order (MGMTFS) - POOLS - DISKS. Storage clusters and SDN clusters only have POOLS and DISKS. The startup order is the reverse. Alternatively, since the management host machine also requires patch upgrades and involves a restart, all MGMTVMs hosted on it can be saved / stopped before upgrading the management host machine. Furthermore, to prevent MGMTVM from starting automatically, you can configure Hyper-V to disable automatic startup for MGMTVM.

[0061] S270. By calling and executing the management host upgrade script, patch upgrades are performed on the management host after the service stops running.

[0062] Specifically, the management host machine upgrade script is used to patch and upgrade the management host machine after the service has stopped running. In practical applications, optionally, after the management host machine upgrade check is complete, the cluster service, cluster storage resources, and all management virtual machines except for the VMM can be started and the VMM SQL cluster restored. However, the VMM is not restored immediately because the storage cluster volumes have already been added to the VMM. If the VMM is restored, it will lose these added volumes if all hosts in the storage cluster are restarted; therefore, the VMM needs to be shut down.

[0063] The technical solution of this invention upgrades the first and second Active Directory (AD) in batches online by calling and executing the domain controller server upgrade script, thereby achieving effective AD upgrades without affecting the normal operation of ADs. Furthermore, by sequentially upgrading the management virtual machine and the management host, effective upgrades of the management cluster are achieved. The above technical solution has low coupling; by splitting the Windows Server SDDC patch upgrade, independent upgrades of ADs and the management cluster are achieved.

[0064] To better understand the patch upgrade process for AD and managed clusters as described in the embodiments of the present invention, the following illustrative examples are provided. For example, see [link to example]. Figure 3 The patch upgrade process for AD and the management cluster is divided into four stages: preparation, AD restart, management upgrade, and cleanup. The specific operations for each stage are described below:

[0065] Preparations in advance: preparation of the operator machine, media distribution, and environment check (Windows server SDDC environment and hardware);

[0066] AD Restart: Perform restart and check on Windows server SDDC-AD01 and Windows server SDDC-AD02 in sequence;

[0067] Management Upgrade: After restarting and checking Windows server SDDC-AD02, perform the following steps in sequence: shut down Windows server SDDC environment VMM and SQL, shut down Windows server SDDC environment management VM, check running VM, shut down management cluster, upgrade management node SAS card driver to the corresponding vendor, restart node, upgrade management node RAID card driver to the corresponding vendor, start management cluster (including S2D), start management VM, and restore VMM.

[0068] Final step: Manage VM status checks and hardware and node memory checks.

[0069] Figure 4This is a flowchart of another patch upgrade method provided in this embodiment of the invention. This embodiment is based on and optimized from the above-described technical solutions. In this embodiment, optionally, the patch upgrade script includes a compute cluster upgrade script and a storage cluster upgrade script; by calling and executing the patch upgrade script, patch upgrades are performed on at least one domain server, including: for the compute host and storage host in at least one domain server, after controlling the shutdown of the compute cluster service deployed on the compute host, controlling the shutdown of the storage resources and services of the storage cluster deployed on the storage host; by calling and executing the compute cluster upgrade script, patch upgrades are performed on the compute host after the service has stopped running, and by calling and executing the storage cluster upgrade script, patch upgrades are performed on the storage host after the service has stopped running; the above patch upgrade method further includes: after controlling the recovery of the storage resources and services of the storage cluster, controlling the recovery of the compute cluster service; optionally, the above patch upgrade method may further include: obtaining a post-upgrade check script; by calling and executing the post-upgrade check script, checking the memory status of the recovered compute cluster service and the health status of the storage resources of the storage cluster. The explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0070] See Figure 4 The method in this embodiment may specifically include the following steps:

[0071] S310. In response to the patch upgrade command, obtain the patch upgrade script, wherein the patch upgrade script includes the compute cluster upgrade script and the storage cluster upgrade script.

[0072] S320. Identify at least one intradomain server in a software-defined data center located under the same domain controller.

[0073] S330. For at least one compute host and storage host in a domain server, after controlling the shutdown of the compute cluster service deployed on the compute host, control the shutdown of the storage cluster storage resources and services deployed on the storage host.

[0074] For patch upgrades targeting compute and storage clusters, it is necessary to first stop the compute cluster services deployed on the compute host, then stop the storage resources and services deployed on the storage host, and finally perform a synchronous upgrade of the compute and storage hosts.

[0075] S340. By calling and executing the computing cluster upgrade script, patch the computing host machine after the service stops running; and by calling and executing the storage cluster upgrade script, patch the storage host machine after the service stops running.

[0076] In practical applications, upgrading a compute cluster may optionally involve steps such as saving tenant virtual machines, shutting down tenant virtual machines, checking the running virtual machine _COMP cluster, and preventing virtual machines from starting the _COMP cluster. After completing these steps, a separate upgrade of the SDN cluster can be performed, breaking the dependency between compute and storage.

[0077] S350. After controlling the recovery of storage resources and services in the storage cluster, control the recovery of computing cluster services.

[0078] When restoring compute and storage clusters, the storage cluster's storage resources and services can be restored first, followed by the compute cluster's services. It's important to note that SDN cluster upgrades are similar to management cluster upgrades; both SDN virtual machines and SDN host machines can be upgraded. NCVM is the SDN control layer, while GWVM and MUXVM are SDN data layer components. The data layer depends on the control layer; if the control layer services are not running, the entire SDN will malfunction. Therefore, after patching and upgrading SDNVM, NCVM should be started first, followed by GWVM and MUXVM. Compared to management virtual machines, after patching and upgrading NCVM, the NC version can be updated.

[0079] S360: Obtain the post-upgrade check script. By calling and executing the post-upgrade check script, check the memory status of the restored computing cluster service and the health status of the storage resources of the storage cluster.

[0080] The upgrade completion check is a crucial part of the Windows Server SDDC patch upgrade process. After the compute-storage SDN cluster recovers, its status can be checked, including the memory status of the compute cluster services, the health of the storage resources in the storage cluster, and the NCHost agent and SLBHost agent services. NC controls the entire Windows Server SDDC network, and its performance directly impacts virtual machine communication. NC checks may include: NC replication status, NC certificates, NC version, NC node status, NCPlugin version, and NC TCP 6640 connections. After the check passes, VMM virtual machines and VMM cluster services can be restored, and finally, tenant virtual machines can be restored.

[0081] The technical solution of this invention achieves an effective upgrade of the compute-storage SDN by successively stopping the compute cluster service and the storage resources and services of the storage cluster; after the upgrade, the health status of the Windows server SDDC is further ensured by checking the memory status of the compute cluster service and the storage resources of the storage cluster.

[0082] To better understand the upgrade process and post-upgrade inspection process of the compute-storage SDN described in the embodiments of the present invention, specific examples are provided below for illustrative purposes. For example, Figure 5 As shown, the upgrade process and post-upgrade inspection process of Compute Storage SDN are divided into six stages: preliminary preparation, VM pause, patch upgrade, VMM upgrade, virtual machine recovery and individual recovery, and finalization. The specific operations of each stage are described below:

[0083] Preparations in advance: Environment check (Windows server SDDC environment, hardware), data backup and job pause, NC backup, VMM snapshot and SQL backup, SCOM alarm pause, and Windows server SDDC environment information acquisition;

[0084] VM pause: The Windows server SDDC compute cluster VM shutdown / save and the Windows server SDDC compute cluster VM disable virtual machine auto-start are executed sequentially;

[0085] Patch upgrade: After disabling virtual machine auto-start in the Windows Server SDDC computer cluster, a running VM check is performed, and the VMM process is shut down. After this process, the upgrade proceeds in three branches:

[0086] Branch 1: The following steps are executed sequentially: SDN VM patch upgrade and restart, NC upgrade and check, SDN VM shutdown, SDN cluster stop, SDN host patch upgrade, SAS card driver upgrade, node restart, SAS card fixed upgrade, node restart and check, SDN cluster recovery (including S2D status check and host memory check), SDN VM startup and check, node memory check, and hardware master status check.

[0087] Branch 2: The following steps are executed sequentially: storage cluster shutdown, storage node patch upgrade, vendor SAS card driver upgrade, node restart (restart before upgrade), SAS card fixed upgrade, node restart and check, start storage cluster and S2D and node memory check, and hardware master status check.

[0088] Branch 3: Compute cluster shutdown, compute node patch upgrade, restart and check (node ​​memory check, restart before upgrade), compute cluster recovery and node memory check, hardware master status check;

[0089] VMM upgrade: After memory checks and hardware master status checks at the common step nodes of the three branches, VMMServer & Console upgrade (including VMM recovery) and VMM Agent upgrade are executed sequentially.

[0090] Virtual machine recovery and single-item recovery: After the VMM Agent is upgraded, the recovery of virtual machines on the compute nodes of the Windows server SDDC environment is performed in sequence, and the VM status is checked and compared, and the host memory usage is checked.

[0091] Final steps: Storage FileShare & Provider check, backup job recovery, SCOM detection recovery, PIP check, GW to VPN subnet route connectivity verification, NC 6640 connection check, NC & SLB check, and VMM snapshot deletion.

[0092] To better understand the overall patching and upgrade process for Windows Server SDDC, a specific example is provided below. For instance, this integrated patching and upgrade process for Windows Server SDDC involves the following seventeen parts, each based on at least one step, and each step based on its own script. As mentioned above, the execution order of these scripts can be orchestrated using a process designer, and then the process executor can be used to call and execute these orchestrated scripts. The following examples illustrate these seventeen parts and the steps involved in each part:

[0093] I. Preparation: Check the upgrade configuration.

[0094] II. Exporting Basic Information: Exporting cluster node information, exporting server basic information, exporting server network card driver information, exporting MGMT cluster virtual machine information, exporting cluster FileShare information, and exporting COMP cluster virtual machine information.

[0095] III. Exporting NC Information: Exporting NC information, obtaining virtual machine (vnet) information, and exporting Virtual Network Peering information.

[0096] IV. Viewing Exported Information: View the VMM compute cluster list, view the exported COMP cluster list, view the exported MGMT cluster list, view the exported SDN cluster list, view the exported STOR cluster list, view the exported NAS cluster list, view the exported VMM cluster list, view the exported SQL cluster list, view exported FileShare information, view exported COMP node information, view exported MGMT node information, view exported SDN node information, view exported STOR node information, view exported VMM node information, view exported SQL node information, view exported COMP virtual machines, view exported GPU virtual machines, query cluster node timezones, view MGMT cluster virtual machines, view SDN cluster virtual machines, and view X722 onboard network card information.

[0097] V. Distribute Patch Files: Distribute Patch File_ADDC, Distribute Network Card Driver_ADDC, Distribute Patch to MGMTVM, Distribute Patch to SDNVM, Distribute Patch File to Cluster Node, Distribute Network Card Driver to Cluster Node, Check Patch File_Specified Cluster, Check Driver File_Specified Cluster, Check Driver File_ADDC, and Check Patch File_ADDC.

[0098] VI. Pre-installation checks: Check server system disk space, check cluster node status, check NCHost agent and SLBHost agent, check failed VMM jobs, and check oversized virtual machines.

[0099] VII. Cessation of Testing Agency Services: Cessation of testing agency services.

[0100] 8. AD & Management Cluster Upgrade: AD01 upgrade patch, AD01 network card upgrade, AD01 restart, AD01 patch check, AD01 network card check, AD02 upgrade patch, AD02 network card upgrade, AD02 restart, AD02 patch check, AD02 network card check, stop VMM cluster service, stop SQL cluster service, install patch_MGMTVM, restart computer_MGMTVM, check patch_MGMTVM, stop large memory virtual machines_MGMT cluster, stop virtual machines_MGMT cluster, disable virtual machine auto-start_MGMT cluster, check running virtual machines_MGMT cluster, check network card driver_MGMT cluster, check patches _MGMT cluster, stop cluster storage resources_MGMT cluster, stop cluster service_MGMT cluster, (S2D best practice), restart computer cluster node_MGMT cluster, install patch cluster node_MGMT cluster, install network card driver cluster node_MGMT cluster, restart computer cluster node_MGMT cluster, check server startup time_MGMT cluster, check patches_MGMT cluster, check Windows UBR information_MGMT cluster, check network card driver_MGMT cluster, start cluster service_MGMT cluster, start cluster storage resources_MGMT cluster, start virtual machine management cluster (VMM exception), and start SQL cluster.

[0101] 9. Compute Cluster Upgrade: Tenant virtual machine Save, Tenant virtual machine Shutdown, Check Running Virtual Machines (COMP Cluster), Disable Automatic Startup of Virtual Machines (COMP Cluster), Check Network Adapter Drivers (COMP Cluster), Check Patches (COMP Cluster), Stop Cluster Service (COMP Cluster), Restart Computer (COMP Cluster), Install Network Adapter Drivers (COMP Cluster), Install Patches (COMP Cluster), Restart Computer (COMP Cluster), Check Server Startup Time (COMP Cluster), Check Patches (COMP Cluster), Check Windows UBR Information (COMP Cluster), Check Network Adapter Drivers (COMP Cluster), Check Storage Cluster Status, Check Server Memory Changes, Start Cluster Service (COMP Cluster), and Check VMM & SQL Cluster Status.

[0102] 10. Storage Cluster Upgrade: Before stopping storage cluster resources, check the VMM, running virtual machines (COMP cluster), network card drivers (STOR cluster), patches (STOR cluster), VMSTOR, SOFS, Pools Offline, stop cluster storage resources (STOR cluster), stop cluster services (STOR cluster), (S2D best practices), restart the computer (STOR cluster), install patches (STOR cluster), install network card drivers (STOR cluster), restart the computer (STOR cluster), check server startup time (STOR cluster), check patches (STOR cluster), check Windows UBR information (STOR cluster), check network card drivers (STOR cluster), start cluster services (STOR cluster), and start cluster storage resources (STOR cluster).

[0103] XI. SDN Cluster Upgrade: Install Patches_SDNVM, Restart Computer_GW_MUX, Restart Computer_SDN_NC, Check Patches_SDNVM, Check Server Startup Time_SDNVM, Stop Large Memory SDN Virtual Machines, Shut Down SDN Virtual Machines Except NC, Shut Down SDN-NC Virtual Machine, Shut Down Other SDN Virtual Machines, Disable SDN Virtual Machine Auto-Start_SDN Cluster, Check Running Virtual Machines_SDN Cluster, Check Network Card Drivers_SDN Cluster, Check Patches_SDN Cluster, Stop Cluster Storage Resources SDN Cluster, Stop Cluster Services SDN Cluster (S2D Best Practices), Restart Computer_SDN Cluster, Install Patches_SDN Cluster, Install Network Card Drivers_SDN Cluster, Restart Computer_SDN Cluster, Check Server Startup Time_SDN Cluster, Check Patches_SDN Cluster, Check Windows UBR Information_SDN Cluster, Check Network Card Drivers_SDN Cluster, Start Cluster Services_SDN Cluster, Start Cluster Storage Resources_SDN Cluster, Start SDN_NC Virtual Machine, Start SDN_MUX&GW Virtual Machine and Start Other SDN Virtual Machines.

[0104] 12. Post-upgrade checks: Check server memory changes, check NCHost agent and SLBHost agent, and check cluster node status.

[0105] 13. Post-upgrade cleanup: Clean up the installation folder.

[0106] 14. NC Check: Compare VirtualNetworkPeering information, check NC replication status, check NC certificate, check NC node version, check NC node status, check VMM and NCPlugin versions, and check NC connection_TCP6640.

[0107] 15. Restore virtual machines in the compute cluster: Check node status_COMP&STOR cluster, start virtual machine_VMM, start VMM cluster, start tenant virtual machine, check unrecovered virtual machine, check virtual machine status_COMP cluster, compare virtual machine VNET changes, and check cluster host memory usage.

[0108] XVI. Start the testing agency service: Start the testing agency service.

[0109] 17. Unconventional Operations: Shutting down the computer, shutting down the computer_specified cluster, shutting down the computer_MGMTVM, shutting down the computer_SDNVM, enabling the virtual machine time synchronization service, upgrading the NC version, upgrading VMMAgent, and checking the VMMAgent version.

[0110] The aforementioned integrated patching and upgrade solution for Windows Server SDDC utilizes PowerShell commands to write Action instructions for relevant upgrade items. These Action instructions are then issued from the operator machine within the Windows Server SDDC domain, enabling upgrades to any specified cluster node or virtual machine. Furthermore, the combination of a Windows operator machine and PowerShell allows for patching and upgrading Windows Server SDDC in different environments simply by switching the operator machine's domain, thus improving operator machine reusability. In addition, all the scripts described are logically related yet independent, and newly added scripts can be seamlessly integrated into the patching and upgrade process, demonstrating strong scalability.

[0111] The above technical solution enables the rapid patching and upgrading of the operating system and diverse hardware and software of the Windows Server SDDC Fabirc layer server.

[0112] Figure 6 This is a structural block diagram of a patch upgrade apparatus provided in an embodiment of the present invention. This apparatus is used to execute the patch upgrade method provided in any of the above embodiments. This apparatus and the patch upgrade methods of the above embodiments belong to the same inventive concept. Details not described in detail in the embodiments of the patch upgrade apparatus can be found in the embodiments of the patch upgrade methods described above. See also... Figure 6 The device can be configured on an operating server and may specifically include: a patch upgrade script acquisition module 410 and a patch upgrade module 420.

[0113] The patch upgrade script acquisition module 410 is used to acquire the patch upgrade script in response to the patch upgrade command. The patch upgrade script includes at least one of the following: domain controller server upgrade script, management cluster upgrade script, compute cluster upgrade script, and storage cluster upgrade script.

[0114] The patch upgrade module 420 is used to perform patch upgrades on at least one domain server in a software-defined data center located under the same domain controller by calling and executing a patch upgrade script.

[0115] Optionally, the patch upgrade script includes a domain controller server upgrade script. The patch upgrade module 420 may include:

[0116] The first patch upgrade unit is used to perform patch upgrades on the first and second domain controllers in batches by calling and executing the domain controller upgrade scripts.

[0117] Optionally, the patch upgrade script includes a management cluster upgrade script, which includes management virtual machine upgrade scripts and management host upgrade scripts. The patch upgrade module 420 may include:

[0118] The first service shutdown unit is used to control the shutdown of the Virtual Machine Manager Cluster Service and the Structured Query Language Cluster Service deployed on at least one management virtual machine in a domain server.

[0119] The second patch upgrade unit is used to perform patch upgrades on the managed virtual machines after the service has stopped running by calling and executing the upgrade script of the managed virtual machine.

[0120] The second service shutdown unit is used to control the management virtual machines in maintenance state and to stop the management cluster storage resources and cluster services deployed on the management virtual machines in at least one management host machine that hosts management virtual machines in at least one domain server.

[0121] The third patch upgrade unit is used to perform patch upgrades on management host machines after the service has stopped running by calling and executing the upgrade script of the management host machine.

[0122] Optionally, the patch upgrade scripts include compute cluster upgrade scripts and storage cluster upgrade scripts. The patch upgrade module 420 may include:

[0123] The third service shutdown unit is used to control the shutdown of storage cluster storage resources and services deployed on storage hosts after controlling the shutdown of computing cluster services deployed on computing hosts in at least one server within the domain.

[0124] The fourth patch upgrade unit is used to perform patch upgrades on the computing host machine after the service stops running by calling and executing the computing cluster upgrade script, and to perform patch upgrades on the storage host machine after the service stops running by calling and executing the storage cluster upgrade script.

[0125] The aforementioned patch upgrade device may further include:

[0126] The service recovery module is used to control the recovery of computing cluster services after the storage resources and services of the storage cluster have been restored.

[0127] Optionally, based on the above-described apparatus, the apparatus may further include:

[0128] The upgrade check script acquisition module is used to obtain the upgrade check script;

[0129] The post-upgrade check module is used to check the memory status of the restored computing cluster services and the health status of the storage resources of the storage cluster by calling and executing the post-upgrade check script.

[0130] Optionally, the above-mentioned patch upgrade device may further include:

[0131] The environment pre-inspection module is used to obtain the environment pre-inspection script before patching at least one server in the domain by calling and executing the patch upgrade script, and to perform an environment pre-inspection on the software-defined data center by calling and executing the environment pre-inspection script.

[0132] The environment pre-inspection script is used to export basic information about the software-defined data center, view the exported basic information, and distribute at least one of the patch files.

[0133] Optionally, the above-mentioned patch upgrade device may further include:

[0134] The patch rollback processing module is used to perform patch upgrades on at least one domain server that rolled back the patch in response to a patch rollback event after patch upgrades are performed on at least one domain server by calling and executing a patch upgrade script.

[0135] The patch upgrade apparatus provided in this embodiment of the invention, in response to a patch upgrade command, acquires a patch upgrade script through a patch upgrade script acquisition module. This patch upgrade script includes at least one of a domain controller server upgrade script, a management cluster upgrade script, a compute cluster upgrade script, and a storage cluster upgrade script. The patch upgrade module then performs patch upgrades on at least one domain server located in a software-defined data center under the same domain controller by calling and executing the patch upgrade script. This apparatus achieves integrated patch upgrades for Windows Server SDDC; in other words, it achieves patch upgrades for the operating system and various hardware and software components of the Windows Server SDDC.

[0136] The patch upgrade device provided in this embodiment of the invention can execute the patch upgrade method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0137] It is worth noting that in the embodiments of the patch upgrade device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0138] Figure 7 A schematic diagram of an operation server 10, which can be used to implement embodiments of the present invention, is shown. The operation server is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The operation server can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0139] like Figure 7As shown, the operation server 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the operation server 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0140] Multiple components in the operation server 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, optical disk, etc.; and a communication unit 19, such as a network card, modem, wireless transceiver, etc. The communication unit 19 allows the operation server 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0141] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as patch upgrade methods.

[0142] In some embodiments, the patch upgrade method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the operation server 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the patch upgrade method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the patch upgrade method by any other suitable means (e.g., by means of firmware).

[0143] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0144] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0145] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0146] To provide user interaction, the systems and techniques described herein can be implemented on an operating server having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the operating server. Other types of devices can also be used to provide user interaction; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0147] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0148] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0149] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0150] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A patch upgrade method characterized by, The method applied to an operation server comprises: in response to a patch upgrade instruction, obtaining a patch upgrade script; for at least one intradomain server of a software-defined data center under the same domain control, performing patch upgrade on the at least one intradomain server by calling and executing the patch upgrade script; wherein the patch upgrade script comprises at least one of a domain control server upgrade script, a management cluster upgrade script, a computing cluster upgrade script and a storage cluster upgrade script; wherein the patch upgrade script comprises the management cluster upgrade script, the management cluster upgrade script comprises a management class virtual machine upgrade script and a management class host upgrade script, and the patch upgrade on the at least one intradomain server by calling and executing the patch upgrade script comprises: for a management class virtual machine in the at least one intradomain server, controlling the stop running of a virtual machine manager cluster service and a structured query language cluster service deployed on the management class virtual machine, and performing patch upgrade on the management class virtual machine after the stop running by calling and executing the management class virtual machine upgrade script; for a management class host in the at least one intradomain server carrying the management class virtual machine, controlling the management class virtual machine to be in a maintenance state, and controlling the stop running of a management cluster storage resource and a cluster service deployed on the management class host, and performing patch upgrade on the management class host after the stop running by calling and executing the management class host upgrade script.

2. The method of claim 1, wherein, the patch upgrade script comprises the domain control server upgrade script; the patch upgrade on the at least one intradomain server by calling and executing the patch upgrade script further comprises: for a first domain control server and a second domain control server in the at least one intradomain server, performing patch upgrade on the first domain control server and the second domain control server in batches by calling and executing the domain control server upgrade script.

3. The method of claim 1, wherein, the patch upgrade script comprises the computing cluster upgrade script and the storage cluster upgrade script; the patch upgrade on the at least one intradomain server by calling and executing the patch upgrade script further comprises: for a computing host and a storage host in the at least one intradomain server, after controlling the stop running of a computing cluster service deployed on the computing host, controlling the stop running of a storage cluster storage resource and a service deployed on the storage host; performing patch upgrade on the computing host after the stop running by calling and executing the computing cluster upgrade script, and performing patch upgrade on the storage host after the stop running by calling and executing the storage cluster upgrade script; the method further comprises: after controlling the recovery running of the storage cluster storage resource and the service, controlling the recovery running of the computing cluster service.

4. The method of claim 3, wherein, further comprising: obtaining a post-upgrade check script; The memory state of the computing cluster service and the health state of the storage cluster storage resource that have been restored to run are checked by calling and executing the post-upgrade check script.

5. The method of claim 1, wherein, Before the patch upgrade of the at least one intradomain server by calling and executing the patch upgrade script, further comprising: An environment pre-check script is acquired, and an environment pre-check of the software-defined data center is performed by calling and executing the environment pre-check script. The environment pre-check script is used for at least one of exporting the basic information of the software-defined data center, checking the exported basic information, and distributing a patch file.

6. The method of claim 1, wherein, After the patch upgrade of the at least one intradomain server by calling and executing the patch upgrade script, further comprising: In the case of detecting a patch rollback event, the intradomain server that has rolled back the patch is upgraded in response to the patch rollback event.

7. A patch upgrading apparatus characterized by comprising: The device is configured to operate a server, and the device comprises: A patch upgrade script acquisition module is configured to acquire a patch upgrade script in response to a patch upgrade instruction. A patch upgrade module is configured to upgrade the at least one intradomain server of the software-defined data center under the same domain control by calling and executing the patch upgrade script. The patch upgrade script comprises at least one of a domain control server upgrade script, a management cluster upgrade script, a computing cluster upgrade script, and a storage cluster upgrade script. The patch upgrade script comprises the management cluster upgrade script, the management cluster upgrade script comprises a management class virtual machine upgrade script and a management class host upgrade script, and the patch upgrade module comprises: A service first stop running unit is configured to control the stop running of a virtual machine manager cluster service and a structured query language cluster service deployed on the management class virtual machine for the management class virtual machine in the at least one intradomain server. A patch second upgrade unit is configured to upgrade the management class virtual machine after the stop running by calling and executing the management class virtual machine upgrade script. A service second stop running unit is configured to control the stop running of a management cluster storage resource and a cluster service deployed on the management class host for the management class host carrying the management class virtual machine in the at least one intradomain server. A patch third upgrade unit is configured to upgrade the management class host after the stop running by calling and executing the management class host upgrade script.

8. A server, operating as characterized by, At least one processor; and A memory connected in communication with the at least one processor; wherein The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the patch upgrade method in any one of claims 1-6. ​ 9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for causing the processor to implement the patch upgrading method according to any one of claims 1-6 when executed.

Images