Storage cluster system upgrading method and device, electronic equipment, medium and product

Abstract

The invention relates to the technical field of computers, in particular to a storage cluster system upgrading method and device, electronic equipment, a medium and a product. The method comprises the steps that a current upgrading package is received, and the state of a current rapid upgrading function is obtained; under the condition that the current upgrade package meets the pre-checking condition, decompressing the current upgrade package, and performing pre-upgrading checking on the decompressed upgrade package to obtain a pre-upgrading checking result; and determining a target upgrading mode of the current storage cluster system according to the pre-upgrading check result and the state of the current rapid upgrading function, and performing staged upgrading on the grouped nodes of the storage cluster based on the target upgrading mode so as to complete upgrading of the current storage cluster system. Therefore, the problems of service interruption, long consumed time and reduced reliability caused by forcing the controller to restart in the existing storage cluster upgrade are solved, the non-interruption upgrade of the storage system is realized, the controller restart is avoided while the system consistency is ensured, and the service continuity and the upgrade efficiency are remarkably improved.

Description

Technical Field

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

[0002] With the acceleration of digital transformation in various industries, the demand for data storage is growing. More and more customers are using large amounts of storage as core data storage media. Customers have increasingly stringent requirements on the performance, stability and reliability of storage systems. Its efficient and stable operation has become a prerequisite for the stable operation of customer businesses.

[0003] As a complex distributed software system, storage cluster systems involve not only underlying firmware (such as the BMC (Baseboard Management Controller), BIOS (Basic Input / Output System), and CPLD (Complex Programmable Logic Device)), but also firmware for various add-in cards, driver management, and a variety of upper-layer advanced functions. Therefore, introducing new storage features, fixing bugs, improving performance, and patching security vulnerabilities inevitably trigger system software upgrades. Because storage clusters directly carry critical services, users and system administrators generally expect upgrades to be quick and seamless, with minimal disruption to services and a zero-perception approach.

[0004] However, storage cluster system software, as a cluster system, typically utilizes a dual-controller or multi-controller architecture. To ensure upgrade effectiveness and product consistency, current storage system upgrade mechanisms generally rely on controller restarts. This results in a time-consuming and inefficient upgrade process. Furthermore, only one controller remains operational during the upgrade, reducing controller redundancy and significantly lowering overall system reliability, making it difficult to meet user requirements for high reliability and business continuity. Therefore, shortening upgrade time and minimizing controller restarts have become key technical challenges in this field. Summary of the Invention

[0005] The present application provides a storage cluster system upgrade method, device, electronic device, medium and product to solve the problems of existing storage cluster upgrades such as business interruption, lengthy time consumption and reduced reliability due to forced controller restart. It realizes non-interruption upgrade of the storage system, avoids controller restart while ensuring system consistency, and significantly improves business continuity and upgrade efficiency.

[0006] To achieve the above objectives, a first embodiment of the present application provides a storage cluster system upgrade method, comprising the following steps: Receive the current upgrade package and obtain the status of the current fast upgrade function; If the current upgrade package meets the pre-check condition, decompress the current upgrade package and perform a pre-upgrade check on the decompressed upgrade package to obtain a pre-upgrade check result; The target upgrade mode of the current storage cluster system is determined according to the pre-upgrade check result and the current status of the fast upgrade function, and the group nodes of the storage cluster are upgraded in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system.

[0007] Through the above technical means, the existing storage cluster upgrade caused business interruption, lengthy processing time and reduced reliability due to forced controller restart. The problem of non-disruptive upgrade of the storage system is realized, which avoids controller restart while ensuring system consistency, significantly improving business continuity and upgrade efficiency.

[0008] According to the storage cluster system upgrade method proposed in the embodiment of the present application, if the current upgrade package meets the pre-check conditions, the current upgrade package is decompressed and a pre-upgrade check is performed. Based on the pre-upgrade check results and the current status of the rapid upgrade function, the target upgrade mode of the current storage cluster system is determined, and the grouped nodes of the storage cluster are upgraded in stages to complete the upgrade of the current storage cluster system. This solves the problem of existing storage cluster upgrades causing business interruptions, lengthy processing time, and reduced reliability due to forced controller restarts. It achieves non-disruptive upgrades of the storage system, avoids controller restarts while ensuring system consistency, and significantly improves business continuity and upgrade efficiency.

[0009] To achieve the above objectives, a second embodiment of the present application provides a storage cluster system upgrade device, comprising: The acquisition module is used to receive the current upgrade package and obtain the status of the current fast upgrade function; a processing module, configured to decompress the current upgrade package if the current upgrade package meets the pre-check condition, and perform a pre-upgrade check on the decompressed upgrade package to obtain a pre-upgrade check result; An upgrade module is used to determine the target upgrade mode of the current storage cluster system based on the pre-upgrade check result and the status of the current fast upgrade function, and to upgrade the group nodes of the storage cluster in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system.

[0010] According to the storage cluster system upgrade device proposed in the embodiment of the present application, if the current upgrade package meets the pre-check conditions, the current upgrade package is decompressed and a pre-upgrade check is performed. Based on the pre-upgrade check results and the current status of the rapid upgrade function, the target upgrade mode of the current storage cluster system is determined, and the grouped nodes of the storage cluster are upgraded in stages to complete the upgrade of the current storage cluster system. This solves the problem of existing storage cluster upgrades causing business interruptions, lengthy processing time, and reduced reliability due to forced controller restarts. It achieves non-disruptive upgrades of the storage system, avoids controller restarts while ensuring system consistency, and significantly improves business continuity and upgrade efficiency.

[0011] To achieve the above-mentioned objectives, the third aspect of the present application proposes an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the storage cluster system upgrade method as described in the above-mentioned embodiment.

[0012] To achieve the above objectives, the fourth embodiment of the present application proposes a non-volatile computer-readable storage medium on which a computer program is stored. The program is executed by a processor to implement the storage cluster system upgrade method as described in the above embodiment.

[0013] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. 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 any creative work.

[0015] Figure 1 A flowchart of a storage cluster system upgrade method provided according to an embodiment of the present application; Figure 2 A flowchart of storage system pre-upgrade inspection and configuration decision-making according to one embodiment of the present application; Figure 3 A flowchart of a storage cluster rolling upgrade and controller restart strategy execution according to an embodiment of the present application; Figure 4 A block diagram of a storage cluster system upgrade method and apparatus according to an embodiment of the present application; Figure 5 A schematic diagram of the structure of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0016] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0017] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0018] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0019] Those skilled in the art will understand that although the existing technology takes into account rapid upgrades, from the perspectives of inter-module compatibility, whether patch packages are re-made, and reducing the scope of repeated unloading and reloading, it is impossible to flexibly select the upgrade scope according to actual scenarios for complex storage cluster system software with highly coupled modules, resulting in the need to restart the controller after the upgrade, and unable to effectively solve the problem of long upgrade time caused by controller restart during the upgrade.

[0020] Based on the problems existing in the above-mentioned existing technologies, this application flexibly selects the upgrade scope and upgrade waiting time when upgrading the storage cluster system software according to the usage scenario, shortens the upgrade time to the greatest extent, and flexibly controls whether the controller is restarted during the upgrade process. It not only improves customer satisfaction and product reliability, but also ensures that equipment and services obtain key security protection faster, reducing the risks caused by vulnerability exposure or product defects.

[0021] The following describes the storage cluster system upgrade method, device, electronic device, medium and product proposed according to the embodiments of the present application with reference to the accompanying drawings.

[0022] Specifically, Figure 1 This is a flowchart of a pre-alarm method based on integrated learning according to an embodiment of the present application.

[0023] For example, Figure 1 As shown, the storage cluster system upgrade method includes the following steps: In step S101, the current upgrade package is received and the status of the current fast upgrade function is obtained.

[0024] The current state of the fast upgrade function refers to the flag explicitly set by the user through the configuration interface or API to determine the selection of the current upgrade mode. The current state of the fast upgrade function includes an on state and a off state.

[0025] Specifically, in the embodiment of the present application, the upgrade package file can be uploaded through the configuration node of the storage cluster, and the status of the current fast upgrade function can be obtained through the user configuration interface, which is not specifically limited here.

[0026] For example, the customer chooses whether to upgrade the firmware of BMC, BIOS, CPLD and external cards. If the firmware of BMC, BIOS, CPLD and external cards does not need to be upgraded, the quick upgrade can be enabled, that is, the current status of the fast upgrade function obtained is enabled. If the firmware of BMC, BIOS, CPLD and external cards needs to be upgraded, the quick upgrade is not enabled, that is, the current status of the fast upgrade function obtained is disabled.

[0027] Furthermore, in some embodiments, after receiving the current upgrade package, it also includes: determining whether the storage cluster is configured with a network attached storage (NAS) service; if the storage cluster is configured with a network attached storage service, configuring the current waiting time to be a first preset time, otherwise, configuring the current waiting time to be a second preset time; wherein the first preset time is greater than the second preset time.

[0028] Optionally, the first preset time length may be 30 minutes, and the second preset time length may be 1 minute, which are not specifically limited here.

[0029] Specifically, after receiving the current upgrade package, this embodiment of the present application detects the storage cluster service type and configures a waiting time. By determining whether the storage cluster is configured for Network Attached Storage (NAS) services, it dynamically adapts differentiated upgrade waiting strategies. If the cluster is detected to be deploying NAS services, the upgrade waiting time is set to a first preset time (30 minutes). If NAS services are not configured, the second preset time (1 minute) is used, thereby shortening the overall upgrade time.

[0030] It's important to note that NAS services place stringent demands on storage system input / output continuity and session persistence. By implementing these differentiated latency strategies, the upgrade process ensures data security while minimizing overall latency to an acceptable level for the business, achieving a balance between storage cluster reliability and timeliness.

[0031] In step S102, if the current upgrade package meets the pre-check condition, the current upgrade package is decompressed, and a pre-upgrade check is performed on the decompressed upgrade package to obtain a pre-upgrade check result.

[0032] Furthermore, in some embodiments, when the current upgrade package meets the pre-check conditions, it also includes: if the current status of the fast upgrade function is on, determining whether the system version of the current storage cluster system supports fast upgrade to the target upgrade version corresponding to the current upgrade package; if the system version of the current storage cluster system does not support fast upgrade to the target upgrade version corresponding to the current upgrade package, generating a reminder message, and issuing a reminder that fast upgrade is not supported based on the reminder message.

[0033] Among them, the pre-check condition of the embodiment of the present application can be to check the current upgrade package to determine whether the current upgrade package meets the integrity and legality requirements.

[0034] Specifically, during the rapid upgrade process, if the user has proactively enabled the rapid upgrade switch before the upgrade, meaning the rapid upgrade feature is currently enabled, the upgrade package is first verified for integrity and legitimacy. A bidirectional compatibility analysis is then performed between the current storage cluster system's running version and the target version carried in the upgrade package to determine whether a technical path exists that allows for a direct rapid upgrade. If the analysis results indicate that there are firmware (including but not limited to BMC, BIOS, CPLD, and add-in card firmware) differences, interface changes, or dependencies between the current system version and the target version that do not meet the rapid upgrade requirements, meaning that the current version does not support rapid upgrades to the target version, a structured reminder message is immediately generated, notifying the user that the current running version does not support rapid upgrades to the target version, and prompting the user to pay attention to the subsequent pre-upgrade check results.

[0035] Furthermore, if the user has not enabled the fast upgrade switch, that is, the current status of the fast upgrade function is off, the above-mentioned adaptability determination step is directly skipped and the subsequent upgrade process is entered.

[0036] Therefore, through the upfront version compatibility verification, the risk of system inconsistency caused by forced rapid upgrades can be effectively avoided, while ensuring the process execution efficiency in non-rapid upgrade scenarios.

[0037] Furthermore, the configuration node decompresses the upgrade package and performs a pre-upgrade check to check whether the cluster meets the upgrade requirements, such as whether the nodes in the cluster are redundant and whether there are serious fault alarms that hinder the upgrade, and obtain the pre-upgrade check results.

[0038] In step S103, the target upgrade mode of the current storage cluster system is determined according to the pre-upgrade check result and the current status of the fast upgrade function, and the grouped nodes of the storage cluster are upgraded in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system.

[0039] Furthermore, in some embodiments, the target upgrade mode of the current storage cluster system is determined based on the pre-upgrade check result and the current status of the fast upgrade function, including: when the current status of the fast upgrade function is on and the pre-upgrade check result is passed, the target upgrade mode is determined to be the preset fast upgrade mode; when the current status of the fast upgrade function is on and the pre-upgrade check result is failed, a user confirmation instruction is obtained, if the user confirmation instruction is to confirm the fast upgrade, the target upgrade mode is determined to be the preset fast upgrade mode, and if the user confirmation instruction is to cancel the fast upgrade, the target upgrade mode is determined to be the preset normal upgrade mode.

[0040] Specifically, the embodiment of the present application determines the target upgrade mode by checking whether the rapid upgrade conditions are met and whether the target version to be upgraded to the current version involves a firmware upgrade.

[0041] When the fast upgrade switch is turned on, the previously completed upgrade package check result is first reused: If the result indicates that there are no firmware-level differences between the current running version and the target version and all dependency conditions are met, the target upgrade mode is directly determined to be the preset fast upgrade mode, and the fast upgrade identifier is written into the decompressed upgrade file set, entering the next stage of the distribution and upgrade process without repeating any additional pre-checks.

[0042] Furthermore, when the fast upgrade switch is on, if the upgrade package inspection results indicate that there are situations that hinder the fast upgrade, such as inconsistent firmware versions, interface changes, or missing key dependencies, that is, the upgrade package inspection fails, a detailed risk report will be immediately generated based on the actual inspection results. The report content lists the firmware that must be upgraded simultaneously with this upgrade and their corresponding version numbers, and quantifies the compatibility, stability, and security risks that may be caused if the firmware upgrade is not performed. This report can be presented synchronously with the log system through the management interface and trigger a second confirmation interaction. If the user explicitly chooses to continue the fast upgrade, the fast upgrade logo will be added to the decompressed upgrade file, and the subsequent steps will still be executed in the fast upgrade mode; if the user chooses to cancel the fast upgrade, the target upgrade mode will be automatically switched to the normal upgrade mode for the next upgrade.

[0043] This ensures upgrade flexibility while ensuring the prudence of key operations through mandatory risk confirmation steps, balancing operational efficiency and system reliability.

[0044] Furthermore, in some embodiments, determining the target upgrade mode of the current storage cluster system based on the pre-upgrade check result and the current status of the fast upgrade function also includes: if the current status of the fast upgrade function is off, determining whether the decompressed upgrade package involves a firmware upgrade based on the pre-upgrade check result; if the decompressed upgrade package does not involve a firmware upgrade, determining the target upgrade mode to be the preset fast upgrade mode; otherwise, determining the target upgrade mode to be the preset normal upgrade mode.

[0045] Specifically, when the express upgrade feature is disabled, a pre-upgrade check is performed immediately after the upgrade package is unpacked to determine whether the changes involve any firmware-level content. If the check indicates that the upgrade package does not contain any version updates for the baseboard management controller (BMC), basic input / output system (BIOS), complex programmable logic device (CPLD), or add-in card firmware, the system reassesses and automatically adjusts the target upgrade mode to the preset express upgrade mode. A express upgrade flag is also added to the unpacked upgrade file, allowing subsequent scripts to use this flag to perform incremental upgrades without restarting the controller.

[0046] On the contrary, if the inspection finds that the upgrade package contains version changes of any of the above firmware, the default decision is maintained, the target upgrade mode is determined to be normal upgrade mode, and a complete upgrade path including firmware burning, full service shutdown, controller restart and integrity verification is entered to ensure the consistency and reliability of the firmware and the upper software stack.

[0047] Therefore, through the above technical means, the user's demand for upgrade flexibility is met, and the system reliability risk caused by improper mode selection is avoided.

[0048] Further, in some embodiments, the grouped nodes of the storage cluster are upgraded in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system, including: dividing the storage cluster nodes into a first group of nodes and a second group of nodes; when performing an upgrade operation on the first group of nodes, if the target upgrade mode is a preset fast upgrade mode, then a restart operation is not performed on the current controller, otherwise, a restart operation is performed on the current controller; when the upgrade operation is completed on the first group of nodes, an upgrade operation is performed on the second group of nodes, if the target upgrade mode is a preset fast upgrade mode, then a restart operation is not performed on the current controller, otherwise, a restart operation is performed on the current controller; when the upgrade operation is completed on the second group of nodes, it is determined that the upgrade of the current storage cluster system is completed.

[0049] Specifically, the configuration node first distributes the upgrade package that has passed the integrity check in parallel to all nodes to be upgraded in the cluster, and divides all nodes into the first group of nodes and the second group of nodes to achieve rolling upgrades and maintain business continuity.

[0050] For the upgrade process of the first group of nodes, the script first reads the quick upgrade flag in the upgrade file. This flag determines the actions to be performed by the upgrade script. If the quick upgrade flag is present and valid, the script only overwrites and replaces service-level files, bypassing firmware upgrade checks and file replacements, and not restarting the controller. If the quick upgrade flag is absent, meaning the upgrade mode is a standard upgrade, the script sequentially stops services, replaces all files, modifies permissions, recreates soft links, restarts services, and restarts the controller. Finally, it starts all relevant services to ensure the new version environment is ready.

[0051] After the upgrade of the first group of nodes is complete, status stability monitoring is performed based on a preconfigured wait time. Once the upgraded nodes have stabilized, the second group of nodes is upgraded using the same strategy. In the fast upgrade mode, no controller restart is performed, while in the standard upgrade mode, a full restart process is performed. Once the second group of nodes has also completed the upgrade and passed status verification, and all nodes in the cluster are running the new version, the cluster-level components of each node begin a consistent switchover, marking the end of the upgrade process for the entire storage cluster system.

[0052] Therefore, through the above technical solution, it is possible to flexibly choose whether the storage cluster system upgrade requires restarting the controller, thereby achieving rapid upgrade, shortening the upgrade time, and improving user satisfaction.

[0053] In order to facilitate those skilled in the art to more clearly understand the implementation process of the storage cluster system software rapid upgrade method of the embodiment of the present application, the following is combined with Figure 2 and Figure 3 Provide detailed explanation.

[0054] The fast upgrade solution in this embodiment involves seven stages: uploading the upgrade package and selecting whether to quickly upgrade and waiting time, upgrade package inspection, upgrade package distribution, first group node upgrade, waiting for upgraded node inspection, second group node upgrade, and cluster system upgrade.

[0055] To facilitate understanding, the rapid upgrade solution is divided into the storage system pre-upgrade inspection and configuration decision process and the storage cluster rolling upgrade and controller restart policy execution process.

[0056] First, combine Figure 2 This section describes the storage system pre-upgrade inspection and configuration decision-making process.

[0057] Specifically, if Figure 2As shown, the upgrade package is first uploaded and a wait time is configured. This wait time is set by the user or the system. Furthermore, whether to enable a fast upgrade is configured to determine whether to subsequently enable the fast upgrade policy. After configuration, the upgrade package integrity and validity check is performed. If the check fails, the process terminates. If the check passes, the process continues to determine whether to configure the fast upgrade node.

[0058] In the "Determine whether to configure fast upgrade" node, the system checks whether fast upgrade is enabled based on the user's previous selection. If it is, the system further checks whether fast upgrade is supported from the current version to the target version. If not, a warning is generated indicating that fast upgrade is not supported, and the user is prompted to pay attention to the subsequent pre-upgrade check results. Regardless of support, the system proceeds to the stage of extracting the upgrade package. If fast upgrade is not previously configured, the system skips the support check and proceeds directly to extracting the upgrade package.

[0059] After decompression is complete, determine whether the stacking cluster environment supports the upgrade and verify the feasibility of the upgrade for the entire cluster environment. If the verification result is not supported, the process ends; if supported, determine whether to configure quick upgrade. If quick upgrade is not configured at this time, continue to determine whether it involves a firmware upgrade. If quick upgrade is configured, determine whether the upgrade package check passes. If the upgrade package check fails, check the firmware upgrade status involved in the upgrade package, report the firmware that needs to be upgraded and the main risks of not upgrading, and determine whether the user confirms the quick upgrade. If the quick upgrade is confirmed, add the quick upgrade mark and continue with the subsequent upgrade package distribution. Otherwise, directly distribute the upgrade package.

[0060] In addition, after determining whether a firmware upgrade is involved, the method further includes: if a firmware upgrade is involved, directly distributing the upgrade package; if a firmware upgrade is not involved, adding a quick upgrade flag and continuing with subsequent upgrade package distribution.

[0061] Secondly, combined Figure 3 This section describes the storage cluster rolling upgrade and controller restart policy execution process.

[0062] First, the upgrade package is distributed. After configuring the node to push the upgrade package to all nodes in the cluster in parallel, the nodes are divided into the first and second groups, and the rolling upgrade is performed sequentially. During the upgrade phase for the first group of nodes, the upgrade script first reads the fast upgrade flag in the upgrade file. If the flag is present, the script only performs service-level file replacement and hot reload, exempting the controller from restarting. If the flag is not present, the script performs a full restart process.

[0063] After the upgrade of the first set of nodes is complete, the system waits for the upgraded nodes to stabilize and monitors their status until they have fully joined the cluster and are providing services. The upgrade is then performed on the second set of nodes using the same decision logic. If a fast upgrade flag is present, a controller restart is skipped; otherwise, a restart is performed. Once the second set of nodes has also completed the upgrade and passed the stability check, the cluster component upgrade step is triggered, and the new version of the cluster module on each node is consistently switched, completing the upgrade process.

[0064] In order to help those skilled in the art understand the storage cluster system software rapid upgrade method in the embodiment of the present application more clearly and intuitively, a detailed description is given below with reference to specific examples.

[0065] In this example, the dual-controller cluster system software is upgraded from version 1 to version 2. This does not involve upgrading the BMC, BIOS, CPLD, or other firmware. However, because the upgrade package contents are unpredictable before the upgrade, the fast upgrade parameter is not selected for caution. The specific implementation process is as follows: Step 1: Log in to the storage cluster system. On the system update page, upload the upgrade check file (update_check) and the version 2 upgrade file through the device graphical interface. Since the customer environment does not have NAS services configured, select a 1-minute wait time for the upgrade. Do not select fast upgrade, and then start the upgrade.

[0066] Step 2: After the upgrade package is uploaded, the upgrade package check will automatically start and the upgrade package check will pass.

[0067] Step 3: Configure the node to decompress the upgrade package, perform the upgrade environment test, and ensure that the test passes. Since the target version supports fast upgrade, a fast upgrade flag is added here.

[0068] Step 4: Configure the node to start distributing the upgrade package to other nodes.

[0069] Step 5: The first group of nodes starts upgrading. In this example, non-configuration nodes are upgraded. The upgrade script stops services, replaces files, modifies permissions, rebuilds soft links, restarts services, and starts all related services. The controller is not restarted.

[0070] Step 6: Wait for the first group of nodes to be upgraded, join the cluster, and become stable.

[0071] Step 7: Start upgrading the second group of nodes. The upgrade process is the same as step 5, without restarting the controller.

[0072] Step 8: Wait for the node to join the cluster and become stable.

[0073] Step 9: Cluster components begin upgrading.

[0074] Therefore, according to the present invention, a method for quickly upgrading storage cluster system software is proposed. Users can flexibly choose whether to quickly upgrade and the waiting time after the upgrade between nodes based on their own business conditions and the actual changes in the upgrade package. The upgrade program flexibly controls whether to quickly upgrade based on customer configuration and the actual change scope of the upgrade package, which greatly improves the flexibility of storage cluster system software upgrades. According to actual conditions, the upgrade can be quickly completed without restarting the controller, which greatly shortens the upgrade time and improves customer satisfaction.

[0075] According to the storage cluster system upgrade method proposed in the embodiment of the present application, if the current upgrade package meets the pre-check conditions, the current upgrade package is decompressed and a pre-upgrade check is performed. The target upgrade mode of the current storage cluster system is determined based on the pre-upgrade check results and the current status of the rapid upgrade function, and the grouped nodes of the storage cluster are upgraded in stages to complete the upgrade of the current storage cluster system. This solves the problem that the existing storage cluster upgrade caused by forced controller restart leads to business interruption, lengthy time consumption, and reduced reliability. Customers can customize the upgrade method according to the actual scenario. At the same time, it also integrates the ability to independently judge whether a rapid upgrade is possible. Even if the user uses the default upgrade policy, the optimal upgrade solution can be achieved. It realizes a comprehensive judgment of whether a rapid upgrade is possible based on the actual upgrade scenario, greatly optimizes the upgrade process, and improves the flexibility of storage cluster upgrades.

[0076] Next, a storage cluster system upgrade device according to an embodiment of the present application will be described with reference to the accompanying drawings.

[0077] Figure 4 It is a block diagram of a storage cluster system upgrade device according to an embodiment of the present application.

[0078] like Figure 4 As shown, the storage cluster system upgrade 10 includes: an acquisition module 100 , a processing module 200 , and an upgrade module 300 .

[0079] Among them, the acquisition module 100 is used to receive the current upgrade package and obtain the status of the current fast upgrade function; the processing module 200 is used to decompress the current upgrade package when the current upgrade package meets the pre-check conditions, and perform a pre-upgrade check on the decompressed upgrade package to obtain the pre-upgrade check result; the upgrade module 300 is used to determine the target upgrade mode of the current storage cluster system based on the pre-upgrade check result and the status of the current fast upgrade function, and upgrade the grouped nodes of the storage cluster in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system.

[0080] Further, in some embodiments, the upgrade module 300 is used to: when the current state of the fast upgrade function is on and the pre-upgrade check result is passed, determine that the target upgrade mode is the preset fast upgrade mode; when the current state of the fast upgrade function is on and the pre-upgrade check result is failed, obtain a user confirmation instruction, if the user confirmation instruction is to confirm the fast upgrade, determine the target upgrade mode to be the preset fast upgrade mode, if the user confirmation instruction is to cancel the fast upgrade, determine the target upgrade mode to be the preset normal upgrade mode.

[0081] Furthermore, in some embodiments, the upgrade module 300 is also used to: if the current status of the fast upgrade function is off, determine whether the decompressed upgrade package involves a firmware upgrade based on the pre-upgrade check result; if the decompressed upgrade package does not involve a firmware upgrade, determine the target upgrade mode to be the preset fast upgrade mode; otherwise, determine the target upgrade mode to be the preset normal upgrade mode.

[0082] Further, in some embodiments, the upgrade module 300 is used to: divide the storage cluster nodes into a first group of nodes and a second group of nodes; when performing an upgrade operation on the first group of nodes, if the target upgrade mode is a preset fast upgrade mode, then the restart operation is not performed on the current controller, otherwise, the restart operation is performed on the current controller; when the upgrade operation is completed on the first group of nodes, the upgrade operation is performed on the second group of nodes, if the target upgrade mode is the preset fast upgrade mode, then the restart operation is not performed on the current controller, otherwise, the restart operation is performed on the current controller; when the upgrade operation is completed on the second group of nodes, it is determined that the upgrade of the current storage cluster system is completed.

[0083] Furthermore, in some embodiments, after receiving the current upgrade package, the acquisition module 100 is also used to: determine whether the storage cluster is configured with a network attached storage service; if the storage cluster is configured with a network attached storage service, configure the current waiting time to be a first preset time; otherwise, configure the current waiting time to be a second preset time; wherein the first preset time is greater than the second preset time.

[0084] Furthermore, in some embodiments, when the current upgrade package meets the pre-check conditions, the processing module 200 is also used to: if the current status of the fast upgrade function is on, determine whether the system version of the current storage cluster system supports fast upgrade to the target upgrade version corresponding to the current upgrade package; if the system version of the current storage cluster system does not support fast upgrade to the target upgrade version corresponding to the current upgrade package, generate a reminder message, and issue a reminder that fast upgrade is not supported based on the reminder message.

[0085] It should be noted that the above explanations of the storage cluster system upgrade method embodiment are also applicable to the storage cluster system upgrade device of this embodiment, and will not be repeated here.

[0086] According to the storage cluster system upgrade device proposed in the embodiment of the present application, if the current upgrade package meets the pre-check conditions, the current upgrade package is decompressed and a pre-upgrade check is performed. Based on the pre-upgrade check results and the current status of the rapid upgrade function, the target upgrade mode of the current storage cluster system is determined, and the grouped nodes of the storage cluster are upgraded in stages to complete the upgrade of the current storage cluster system. This solves the problem of existing storage cluster upgrades causing business interruptions, lengthy processing time, and reduced reliability due to forced controller restarts. It achieves non-disruptive upgrades of the storage system, avoids controller restarts while ensuring system consistency, and significantly improves business continuity and upgrade efficiency.

[0087] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device may include: Memory 501 , processor 502 , and computer programs stored in the memory 501 and executable on the processor 502 .

[0088] When the processor 502 executes the program, the server security authentication method provided in the above embodiment is implemented.

[0089] Furthermore, the electronic device further includes: The communication interface 503 is used for communication between the memory 501 and the processor 502 .

[0090] The memory 501 is used to store computer programs that can be run on the processor 502 .

[0091] The memory 501 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0092] If the memory 501, processor 502, and communication interface 503 are implemented independently, the communication interface 503, memory 501, and processor 502 can be connected to each other via a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus. Buses can be divided into address buses, data buses, control buses, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0093] Optionally, in a specific implementation, if the memory 501, the processor 502 and the communication interface 503 are integrated on a chip, the memory 501, the processor 502 and the communication interface 503 can communicate with each other through an internal interface.

[0094] The processor 502 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0095] An embodiment of the present application also provides a non-volatile computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the server security authentication method as described above is implemented.

[0096] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0097] The above is a detailed introduction to a server security authentication method provided by this application. Specific examples are used herein to illustrate the principles and implementation methods of this application. The description of the above embodiments is only intended to help understand the method and core ideas of this application. It should be noted that, for those skilled in the art, without departing from the principles of this application, several improvements and modifications can be made to this application, and these improvements and modifications also fall within the scope of protection of the claims of this application.

Claims

1. A storage cluster system upgrade method, characterized in that: The following steps are involved: Receive the current upgrade package and obtain the status of the current fast upgrade function; If the current upgrade package meets the pre-check condition, decompress the current upgrade package and perform a pre-upgrade check on the decompressed upgrade package to obtain a pre-upgrade check result; The target upgrade mode of the current storage cluster system is determined according to the pre-upgrade check result and the current status of the fast upgrade function, and the group nodes of the storage cluster are upgraded in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system.

2. The method according to claim 1, characterized in that The determining the target upgrade mode of the current storage cluster system according to the pre-upgrade check result and the current status of the fast upgrade function includes: If the current state of the fast upgrade function is enabled and the pre-upgrade check result is passed, determining that the target upgrade mode is a preset fast upgrade mode; When the current status of the fast upgrade function is on and the pre-upgrade check result is failure, a user confirmation instruction is obtained. If the user confirmation instruction is to confirm the fast upgrade, the target upgrade mode is determined to be the preset fast upgrade mode. If the user confirmation instruction is to cancel the fast upgrade, the target upgrade mode is determined to be the preset normal upgrade mode.

3. The method according to claim 1, characterized in that The determining of the target upgrade mode of the current storage cluster system according to the pre-upgrade check result and the current status of the fast upgrade function further includes: If the current state of the fast upgrade function is off, determining whether the decompressed upgrade package involves a firmware upgrade based on the pre-upgrade check result; If the decompressed upgrade package does not involve firmware upgrade, the target upgrade mode is determined to be the preset fast upgrade mode; otherwise, the target upgrade mode is determined to be the preset normal upgrade mode.

4. The method according to claim 1, wherein The step of upgrading the group nodes of the storage cluster in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system includes: Divide the storage cluster nodes into a first group of nodes and a second group of nodes; In the case of performing an upgrade operation on the first group of nodes, if the target upgrade mode is a preset fast upgrade mode, then no restart operation is performed on the current controller; otherwise, a restart operation is performed on the current controller; When the upgrade operation of the first group of nodes is completed, performing the upgrade operation on the second group of nodes, if the target upgrade mode is the preset fast upgrade mode, not performing the restart operation on the current controller, otherwise, performing the restart operation on the current controller; When the upgrade operation of the second group of nodes is completed, it is determined that the upgrade of the current storage cluster system is completed.

5. The method according to claim 1, characterized in that After receiving the current upgrade package, it also includes: Determine whether the storage cluster is configured with network attached storage services; If the storage cluster is configured with the network attached storage service, the current waiting time is configured to be a first preset time; otherwise, the current waiting time is configured to be a second preset time; The first preset duration is greater than the second preset duration.

6. The method according to claim 1, characterized in that If the current upgrade package meets the pre-check conditions, the following steps are also included: If the current state of the fast upgrade function is enabled, determining whether the system version of the current storage cluster system supports fast upgrade to the target upgrade version corresponding to the current upgrade package; If the system version of the current storage cluster system does not support rapid upgrade to the target upgrade version corresponding to the current upgrade package, a reminder message is generated, and a reminder of non-support for rapid upgrade is issued based on the reminder message.

7. A storage cluster system upgrade device, characterized in that: include: The acquisition module is used to receive the current upgrade package and obtain the status of the current fast upgrade function; a processing module, configured to decompress the current upgrade package if the current upgrade package meets the pre-check condition, and perform a pre-upgrade check on the decompressed upgrade package to obtain a pre-upgrade check result; An upgrade module is used to determine the target upgrade mode of the current storage cluster system based on the pre-upgrade check result and the status of the current fast upgrade function, and to upgrade the group nodes of the storage cluster in stages based on the target upgrade mode to complete the upgrade of the current storage cluster system.

8. An electronic device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the storage cluster system upgrade method according to any one of claims 1 to 6.

9. A non-volatile computer-readable storage medium having a computer program stored thereon, characterized in that: The computer program is executed by a processor to implement the storage cluster system upgrade method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the storage cluster system upgrade method according to any one of claims 1 to 6 is implemented.

Images