A chassis management system control method, device and medium

Abstract

The application relates to the field of computer systems and discloses a chassis management system control method and device and a medium, which comprises the following steps: when a managed chassis meets preset conditions, obtaining equipment information of the managed chassis so as to control the chassis. The chassis type of the managed chassis is determined according to the equipment information; the chassis type comprises a physical chassis and a virtual chassis, and the virtual chassis is generated according to simulation instructions, virtual equipment information and virtual chassis data transmitted by a preset communication link; chassis data of the managed chassis is obtained according to the chassis type, and the managed chassis is controlled, so as to judge whether the performance of the chassis management system meets the demand according to a control result. The virtual equipment information and the virtual chassis data are obtained through the preset communication link, the performance of the chassis management system is tested, and whether the chassis management system meets the demand is judged. Multiple chassis are not needed to be built by using hardware equipment, and the time cost and manpower and material resources consumed in the testing process are reduced.

Description

Technical Field

[0001] This application relates to the field of computer systems, and in particular to a control method, device, and medium for a chassis management system. Background Technology

[0002] In storage device operation scenarios, it is necessary to provide chassis management services for storage devices. Typically, a chassis management system is used to manage chassis peripherals (such as power supplies, fans, temperature, voltage, firmware, VPD, LEDs, etc.) to provide a safe and stable working environment for storage devices.

[0003] With the development of storage services, the types of chassis are becoming increasingly diverse (e.g., chassis that connect to Non-Volatile Memory Host Controller Interface Specification (NVME) protocol disks, chassis that connect to Serial Attached SCSI (SAS) protocol disks, etc.). Figure 1 (This is a chassis structure diagram provided in an embodiment of this application, such as...) Figure 1 As shown, 1 is a SAS interface chassis, and 2 is an NVME interface chassis. Besides the interface type, they also use different data transmission protocols. With business growth, there may be situations where the chassis management system does not support chassis peripherals. Furthermore, when the number of chassis managed by the chassis management system is too large, the system's performance may become insufficient, preventing timely processing of data from each chassis.

[0004] Currently, the only way to determine whether the chassis control system can operate normally is through actual testing. However, this method requires building multiple chassis according to needs, which consumes a lot of time and resources.

[0005] Therefore, how to provide a control method for a chassis management system to accurately determine whether the chassis management system is compatible with the target chassis is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0006] The purpose of this application is to provide a control method, device, and medium for a chassis management system, so as to reduce the hardware cost and improve the testing efficiency during the process of testing the performance of the chassis management system.

[0007] To address the aforementioned technical problems, this application provides a control method for a chassis management system, comprising:

[0008] When the managed chassis is detected to meet the preset conditions, the device information of the managed chassis is obtained;

[0009] The chassis type of the managed chassis is determined based on the device information; wherein, the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated based on the virtual device information and virtual machine chassis data sent by the client and the preset communication link;

[0010] The chassis data of the managed chassis is obtained according to the chassis type, and the managed chassis is controlled to determine whether the performance of the chassis management system meets the requirements based on the control results.

[0011] Preferably, the virtual machine chassis creation process includes:

[0012] Determine whether the virtual machine box registration information sent through the preset communication link has been obtained, wherein the virtual machine box registration information is the information obtained after parsing the simulation command;

[0013] If the virtual machine box registration information is obtained, the virtual registration code and product ID are obtained through the system wristband process;

[0014] The virtual machine box is created based on the virtual registration code and the product ID.

[0015] Preferably, the managed chassis meets the preset conditions including:

[0016] The chassis data of the managed chassis has changed.

[0017] Preferably, the device information includes a registration code and a product ID.

[0018] Preferably, determining the chassis type of the managed chassis based on the device information includes:

[0019] Obtain the maintenance list of the chassis management system and determine the product ID of the managed chassis based on the device information;

[0020] The chassis type of the managed chassis is determined based on the maintenance list and the product ID.

[0021] Preferably, obtaining the chassis data of the managed chassis according to the chassis type includes:

[0022] If the chassis type is a virtual machine chassis, then historical chassis data is obtained through the preset communication link, and the managed chassis is simulated based on the historical chassis data;

[0023] If the chassis type is a physical chassis, then real-time chassis data is obtained through the preset communication link, and the working status of the physical chassis is monitored based on the real-time chassis data.

[0024] Preferably, the step of simulating the managed chassis based on the historical chassis data includes:

[0025] Obtain simulation task requirements;

[0026] Analyze the simulation task requirements to obtain the target chassis type and the number of target chassis;

[0027] A simulation system is generated based on the target chassis type and the number of target chassis;

[0028] The working status information of each virtual machine chassis in the simulation system is obtained to determine the business capabilities of the chassis management system.

[0029] Preferably, obtaining historical chassis data through the preset communication link includes:

[0030] Obtain the protocol type of the managed chassis;

[0031] The historical chassis data corresponding to the protocol type is obtained through the preset communication link.

[0032] Preferably, after the step of obtaining historical chassis data through the preset communication link, the method further includes:

[0033] The historical chassis data is decrypted according to the protocol type.

[0034] Preferably, obtaining the working status information of each virtual machine chassis in the simulation system includes:

[0035] Obtain the temperature information, humidity information, and firmware version number information of each virtual machine box sent by the preset communication link.

[0036] Preferably, before the step of obtaining the working status information of each virtual machine chassis in the simulation system, the method further includes:

[0037] Determine whether the simulation system is compatible with the virtual machine chassis of the target chassis type;

[0038] If incompatible, the test will be terminated.

[0039] Preferably, after the step of obtaining the chassis data of the managed chassis according to the chassis type, the method further includes:

[0040] Obtain access information sent by the client;

[0041] The system displays the operating status of the simulation system to the user based on the access information.

[0042] Preferred options also include:

[0043] The managed chassis are tested according to the maintenance list to determine the performance of the chassis management system.

[0044] Preferably, after the step of monitoring the working status of the physical chassis based on the real-time chassis data, the method further includes:

[0045] When an anomaly is detected in the physical chassis data, an alarm message is sent to the administrator.

[0046] Preferably, the step of obtaining the historical chassis data corresponding to the protocol type through the preset communication link specifically means that the historical chassis data is data injected through an automated script.

[0047] Preferably, the preset communication link is an inter-process communication link.

[0048] Preferably, the protocol type includes SAS protocol and NVME protocol.

[0049] To address the aforementioned technical problems, this application also provides a control device for a chassis management system, comprising:

[0050] The acquisition module is used to acquire the device information of the managed chassis when it is detected that the managed chassis meets the preset conditions;

[0051] The determination module is used to determine the chassis type of the managed chassis based on the device information; wherein, the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated based on the virtual device information and virtual machine chassis data sent by the client and the preset communication link;

[0052] The control module is used to obtain the chassis data of the managed chassis according to the chassis type, and to control the managed chassis, so as to determine whether the performance of the chassis management system meets the requirements based on the control results.

[0053] To address the aforementioned technical problems, this application also provides a chassis management system control device, including a memory for storing computer programs;

[0054] A processor is used to implement the steps of the chassis management system control method when executing the computer program.

[0055] To address the aforementioned technical problems, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the chassis management system control method.

[0056] This application provides a control method for a chassis management system, comprising: when a managed chassis is detected to meet preset conditions, acquiring device information of the managed chassis to facilitate control of the chassis according to its type; determining the chassis type of the managed chassis based on the device information; wherein the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated based on virtual device information and virtual machine chassis data sent according to simulation instructions and a preset communication link; acquiring chassis data of the managed chassis according to the chassis type, and controlling the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control results. Therefore, the technical solution provided by this application acquires virtual device information and virtual machine chassis data through a preset communication link to test the performance of the chassis management system and determine whether the chassis management system meets the requirements. This eliminates the need to use hardware equipment to build multiple chassis, reducing the time and manpower costs consumed in the testing process. Furthermore, the technical solution provided by this application is similar to the control method for physical chassis and can be used to manage both virtual machine chassis and physical chassis simultaneously, without requiring specialized adjustments for different types of chassis, further improving testing efficiency.

[0057] Furthermore, this application also provides a chassis management system control device and medium, comprising: when a managed chassis is detected to meet preset conditions, acquiring device information of the managed chassis to facilitate control of the chassis according to its type; determining the chassis type of the managed chassis based on the device information; wherein the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated according to virtual device information and virtual machine chassis data sent by simulation instructions and a preset communication link; acquiring chassis data of the managed chassis according to the chassis type, and controlling the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control results. Therefore, the technical solution provided by this application acquires virtual device information and virtual machine chassis data through a preset communication link to test the performance of the chassis management system and determine whether the chassis management system meets the requirements. This eliminates the need to use hardware equipment to build multiple chassis, reducing the time and manpower costs consumed in the testing process. Furthermore, the technical solution provided by this application is similar to the control method for physical chassis, and can be used to manage both virtual machine chassis and physical chassis simultaneously, without requiring specialized adjustments for different types of chassis, further improving testing efficiency. Attached Figure Description

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

[0059] Figure 1 A chassis structure diagram provided in an embodiment of this application;

[0060] Figure 2 A flowchart illustrating a chassis management system control method provided in this application embodiment;

[0061] Figure 3 A software architecture diagram of a chassis management system provided in an embodiment of this application;

[0062] Figure 4 This is a structural diagram of a chassis management system control device provided in an embodiment of this application;

[0063] Figure 5 This is a structural diagram of another chassis management system control device provided in an embodiment of this application. Detailed Implementation

[0064] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0065] The core of this application is to provide a control method, device, and medium for a chassis management system, so as to reduce the hardware cost and improve the testing efficiency during the process of testing the performance of the chassis management system.

[0066] In scalable storage device applications, to ensure the proper functioning of the expanded storage devices, a chassis management system (HMS) is needed to provide management services. This management system controls chassis peripherals (such as power supplies, fans, temperature sensors, voltage regulators, firmware, VPDs, and LEDs) to ensure the extended storage devices function correctly. For the HMS to manage the chassis, chassis data must first be registered in the management system. The expanded chassis connects to the HMS via a communication link. For example, when the communication link is a SAS link, the registration process for the expanded chassis includes: when the HMS's SAS driver scans the external chassis device, it reports a login to the driver module. This login contains a product ID. The driver module then reports the login to the Enclosure Management (EN) module. The EN module receives the login information, parses out the specific chassis corresponding to the product ID, and finally builds a model for that type of chassis and adds it to the maintained chassis list. When hardware information (such as temperature, fan speed, firmware version number, etc.) changes, the Expander chip in the operating system's oses (i.e., expander firmware) connects to each sensor via I2C, updating power, fan, temperature, voltage, and other information every 1 second (default). When a disk status update is received, the disk status is also updated immediately (and an indicator light illuminates accordingly). A discovery event is reported. Upon receiving a discovery event, the EN module looks up the maintained chassis list index (index), then sends a SAS protocol message to the specified chassis via the index to retrieve chassis management data. After obtaining the chassis management data, it processes and caches the data for GUI or CLI query and display. The EN module then notifies the start of detection and recovery tasks. When the EN module detects a discovery event, it checks all items in the detection & recovery chain to determine if any anomalies exist in the managed chassis. If anomalies are detected, timely maintenance is performed.

[0067] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0068] Figure 2 A flowchart of a chassis management system control method provided in an embodiment of this application is shown below. Figure 2 As shown, the chassis management system control method provided in this application includes:

[0069] S10: When the managed chassis is detected to meet the preset conditions, obtain the device information of the managed chassis;

[0070] S11: Determine the chassis type of the managed chassis based on the device information; among which, chassis type includes physical chassis and virtual machine chassis, and virtual machine chassis is a chassis generated according to the virtual device information and virtual machine chassis data sent by the simulation command and the preset communication link;

[0071] S12: Obtain chassis data of the managed chassis according to the chassis type, and control the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control results.

[0072] In practice, a chassis management system governs a large number of managed chassis. These managed chassis can be physical chassis or virtual machine chassis, and there is no limitation here.

[0073] When providing storage solutions to users, the variety of scalable storage devices and the varying business and performance requirements of different customers necessitate pre-testing of the storage system based on user needs to ensure a good user experience and prevent situations where the storage solution does not support the user-specified chassis or the maximum number of chassis the solution can handle is lower than the user's specified value. However, this process requires building the corresponding chassis according to user requirements. When the number of chassis required is large, pre-conditions such as cables, power cords, and available space must be prepared. Furthermore, environment setup and equipment debugging require significant manpower and resources, resulting in low operational efficiency.

[0074] To address this problem, this application provides a control method for a chassis management system. Figure 3 A software architecture diagram of a chassis management system provided in this application embodiment is shown below. Figure 3As shown, the software includes an IO process, a daemon process, and an IPC communication link. The IPC communication link, located between the daemon process and the IO process, transmits information related to the virtual machine enclosure. The IO process is the process running within the managed enclosure, while the daemon process is the process running on the client side. The daemon process includes a virtual machine enclosure data monitoring and processing module, which monitors virtual machine enclosure data injected via automated scripts in real time. When a virtual machine enclosure list (a list of product IDs named "virtual_enclosure_list") is injected via automated scripts, this module can capture it in real time and proactively report the discovered virtual machine enclosure information via IPC. Furthermore, a virtual login interface is added to the IO process driver module. This interface is registered in the IPC messages. When the daemon process proactively reports the discovery of a virtual machine enclosure, it will call back this interface to report the virtual login, carrying the product ID. Upon receiving the login, the enclosure module will create a new enclosure model, mapping the product ID to the actual enclosure, and add it to the enclosure linked list maintained by the EN module, facilitating subsequent management of the enclosure through the enclosure management module.

[0075] It is understood that the technical solution provided in this application achieves the exchange of chassis information between the IO process and the daemon process through a preset communication link. This method is similar to the data exchange method currently used in physical chassis. Therefore, in the technical solution provided in this application, the managed host can be either a virtual host or a physical host. When the managed host is a virtual host, a simulation system is constructed using historical host data cached in the system (host data generated during the operation of the physical host) to determine whether the current chassis management system can meet the user's needs. When the managed host is a physical host, the real-time data generated during the operation of the physical host only needs to be sent to the chassis management system through the preset communication link to monitor the operating status of the physical host.

[0076] During system operation, when the chassis management system detects a change in the data of any managed host, it triggers a discovery event to update the data of the managed host in the system. It can be understood that there are two scenarios that trigger a discovery event: either the managed chassis that triggers the event is a newly created virtual machine chassis or a newly connected physical host, which has no historical data; or the managed chassis that triggers the event is a pre-created chassis, and its chassis peripheral data has changed.

[0077] In practice, the device information for the managed chassis includes a registration code and a product ID. The chassis management system can determine the chassis type using the registration code and product ID, thereby creating the corresponding virtual machine chassis in the system. Furthermore, commonly used chassis communication protocols include SAS and NVME protocols, with the default communication link being inter-process communication.

[0078] This embodiment provides a chassis management system control method, including: when a managed chassis is detected to meet preset conditions, acquiring device information of the managed chassis to facilitate chassis control based on the type of the managed chassis. The chassis type is determined based on the device information; wherein, the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated based on virtual device information and virtual machine chassis data sent according to simulation instructions and a preset communication link; chassis data of the managed chassis is acquired based on the chassis type, and the managed chassis is controlled to determine whether the performance of the chassis management system meets the requirements based on the control results. Therefore, the technical solution provided in this application acquires virtual device information and virtual machine chassis data through a preset communication link to test the performance of the chassis management system and determine whether the chassis management system meets the requirements. It eliminates the need to use hardware to build multiple chassis, reducing the time and manpower costs consumed in the testing process. Furthermore, the technical solution provided in this application is similar to the control method for physical chassis and can be used to manage both virtual machine chassis and physical chassis simultaneously, without requiring specialized adjustments for different types of chassis, further improving testing efficiency.

[0079] In practice, the chassis management system processes and analyzes the peripheral data of each managed chassis to determine whether the chassis is operating normally and controls the peripherals accordingly. For example, when the chassis temperature is detected to be higher than a threshold temperature, the chassis management system controls the fans to operate in order to lower the chassis temperature.

[0080] During the operation of a storage system, to ensure the normal functioning of storage devices, it is essential to maintain a stable environment within the chassis as much as possible to minimize environmental interference. Therefore, when a change in the data within any chassis is detected, it is necessary to promptly control the chassis peripherals.

[0081] In a preferred embodiment, the managed chassis must meet the preset conditions, including: the chassis data of any managed chassis changes.

[0082] Understandably, when a new managed chassis is added to the system, the chassis management system needs to control that chassis. However, newly added managed chassis do not have historical data, only current data, and the chassis data may have changed. Therefore, using "changes in the chassis data of any managed chassis" as a filtering condition includes this situation.

[0083] In practical implementation, different types of chassis vary. To ensure system compatibility with different chassis types, when different types of chassis are incorporated into the system, corresponding chassis instances (virtual chassis) need to be created based on the chassis type. In this embodiment, product IDs are used to distinguish different types of chassis. Furthermore, the registration code of the virtual chassis enables the chassis management system to determine the chassis information and processing scheme corresponding to the chassis in the linked list. Therefore, as a preferred embodiment, the device information in the chassis management system control method provided in this application includes registration codes and product IDs.

[0084] In practical implementation, to efficiently and conveniently process the chassis, it is necessary to select the appropriate processing scheme based on the chassis type. For example, if the chassis type is a virtual machine chassis, historical chassis data is obtained through a preset communication link, and the managed chassis is simulated based on the historical chassis data; if the chassis type is a physical chassis, real-time chassis data is obtained through a preset communication link, and the working status of the physical chassis is monitored based on the real-time chassis data. As a preferred embodiment, determining the chassis type of the managed chassis based on the device information includes:

[0085] Obtain the maintenance list of the chassis management system and determine the product ID of the managed chassis based on the device information;

[0086] The chassis type of the managed chassis is determined based on the maintenance list and product ID.

[0087] Table 1 is a schematic diagram of the maintenance list provided in this embodiment. As shown in Table 1, the maintenance list of the chassis management system stores the attribute information and equipment information of each managed chassis. When the chassis management system needs to determine the equipment information of any chassis, it only needs to use the maintenance list and product ID.

[0088] Table 1

[0089] product type Model 1 Model 2 enclosure version 1 1 number of drive slots(number of slots) 0 25 max drivers per slots 0 1 Slot form factor (disk size) 0 25 SAS Drive interface (disk speed) 0 32 Virtual enclosure? (Reserved) 1 1 Disk protocol type SAS NVME product id CXW1010000000000 CXW1011912532000 enclosure model Mid-range / High-end

[0090] In practical implementation, to ensure the availability of the storage system solution provided to users, a simulation system can be created using the chassis management system control method provided in this application to simulate the chassis's operating state. Creating the simulation system requires creating multiple virtual machine chassis for the chassis management system. The virtual machine chassis creation process includes:

[0091] Determine whether the virtual machine box registration information sent by the preset communication link has been obtained; wherein, the virtual machine box registration information is the information obtained after parsing the simulation command sent by the client;

[0092] If the virtual machine box registration information is obtained, the virtual login and product ID are obtained through the system daemon process;

[0093] Generate a virtual machine box based on the virtual login and product ID.

[0094] Specifically, the daemon process includes a virtual machine enclosure data monitoring and processing module. This module monitors virtual machine enclosure data injected via pytest in real time. Once a virtual machine enclosure list (a list table named "virtual_enclosure_list" based on product IDs) is injected via pytest, the module can capture it in real time and proactively report the discovered virtual machine enclosure information via IPC. Next, pytest injects all enclosure management data from the virtual machine enclosure list (files named after product IDs). This module performs periodic tests and then caches the management data for each virtual machine enclosure.

[0095] The IO process driver module includes a virtual login interface, which is registered in the IPC message. When the daemon actively reports the discovery of virtual machine chassis information, it will call back this interface to report the virtual login, carrying the product ID. After receiving the login, the chassis module will establish a new chassis model, associate the product ID with the actual chassis, and add it to the chassis linked list maintained by the EN module, so that the chassis management system can control each virtual machine chassis in the future.

[0096] The technical solution provided in this application achieves the exchange of chassis information between the IO process and the daemon process through a preset communication link. This method is similar to the data exchange method currently used in physical chassis. Therefore, in the technical solution provided in this application, the managed host can be a virtual host or a physical host. As a preferred embodiment, obtaining the chassis data of the managed chassis according to the chassis type includes:

[0097] If the chassis type is a virtual machine chassis, historical chassis data is obtained through a preset communication link, and the managed chassis is simulated based on the historical chassis data;

[0098] If the chassis type is a physical chassis, real-time chassis data is obtained through a preset communication link, and the working status of the physical chassis is monitored based on the real-time chassis data.

[0099] In practical implementation, the chassis management system and the storage system composed of each virtual machine chassis can be used for simulation to help users and R&D personnel determine the system's stability and reliability. In practice, simulating the managed chassis based on historical chassis data includes:

[0100] Obtain simulation task requirements;

[0101] Analyze the simulation task requirements to obtain the target chassis type and the number of target chassis;

[0102] A simulation system is generated based on the target chassis type and the number of target chassis;

[0103] Obtain the working status information of each virtual machine chassis in the simulation system to determine the business capabilities of the chassis management system.

[0104] It is important to note that, to improve simulation testing efficiency, the testing process should be terminated promptly when incompatibility between the simulation system and the target chassis is detected. Specifically, before obtaining the operating status information of each virtual machine chassis in the simulation system, it is also necessary to determine whether the simulation system is compatible with the virtual machine chassis of the target chassis type.

[0105] Understandably, simulation task requirements are based on information determined by user needs or R&D personnel's development needs. They are primarily used to determine whether the current storage system can support the target number of chassis or whether it is compatible with the target type of chassis. After the simulation system is built, the working status information of each virtual machine chassis in the simulation system is obtained to determine the business capabilities of the chassis management system. If the simulation system functions normally, it indicates that the current chassis management system can meet the customer's requirements.

[0106] In specific implementation, in order to ensure the security and reliability of data transmission, as a preferred embodiment, obtaining historical chassis data through a preset communication link includes: obtaining the protocol type of the managed chassis; and obtaining historical chassis data corresponding to the protocol type through the preset communication link.

[0107] Furthermore, data can be injected into a pre-defined communication link using automated scripts to achieve data transmission.

[0108] In a preferred embodiment, after the step of obtaining historical chassis data through a preset communication link, the method further includes: decrypting the historical chassis data according to the protocol type.

[0109] In practice, if the virtual machine chassis management data cached in the daemon process is injected into the product id file by the pytest process in plaintext format via the SAS protocol, the data obtained by the chassis management system is also a ses message. After being parsed and processed by the SAS protocol, the data is placed into the upper-layer application module of the chassis management system.

[0110] As a preferred embodiment, obtaining the working status information of each virtual machine chassis in the simulation system includes: obtaining the temperature information, humidity information, and firmware version number information of each virtual machine chassis sent by the preset communication link.

[0111] Specifically, chassis peripherals include: power supply, fans, temperature, voltage, firmware, and vital product data (VPD). A VPD is a collection of configuration and information data related to a specific set of hardware or software. The storage device chassis VPD stores important device information, such as the product model, product serial number, and other key data. The product model identifies the product category, and the product serial number is a unique identifier for each device.

[0112] As a preferred embodiment, in order to enable customers to more intuitively understand the performance of the storage system composed of the chassis management system and the virtual machine chassis, the working status of the simulation system can also be displayed to users through a web page.

[0113] In practice, after obtaining the chassis data of the managed chassis according to the chassis type, the process also includes: obtaining access information sent by the client; and displaying the working status of the simulation system to the user based on the access information.

[0114] Customers can access the client via either the intranet or the internet; there is no restriction on this. Users can view the number and type of chassis in your simulation system, the operating status of each chassis, etc., to assess the business capabilities of the chassis management system.

[0115] In practical implementation, the chassis management system control method provided in this application can also be used to manage physical chassis. To better understand the working status of the physical chassis and improve the security of the storage system, the processes of each physical chassis can be tested periodically. As a preferred embodiment, the chassis management system control method provided in this application further includes:

[0116] Each managed chassis is tested according to the maintenance list to determine the performance of each managed chassis and the simulation system.

[0117] Furthermore, following the step of monitoring the working status of the physical chassis based on real-time chassis data, the process also includes:

[0118] When an anomaly is detected in the physical chassis data, an alarm message is sent to the administrator.

[0119] Alarm information can be sent to administrators in the form of log messages, or it can be alerted to administrators through physical alarm status such as buzzers or indicator lights; there are no restrictions on which method is used.

[0120] As a preferred embodiment, obtaining historical chassis data corresponding to the protocol type through a preset communication link specifically involves the historical chassis data being data injected via an automated script.

[0121] In practical implementation, the default communication link is inter-process communication (IPC). Inter-process communication refers to the interaction of data between two processes, including: half-duplex Unix pipes, FIFOs (named pipes), message queues, semaphores, shared memory, network sockets, etc.

[0122] In the above embodiments, the control method for the chassis management system has been described in detail. This application also provides embodiments corresponding to the control device for the chassis management system. It should be noted that this application describes the embodiments of the device from two perspectives: one is based on the functional modules, and the other is based on the hardware.

[0123] Figure 4 A structural diagram of a chassis management system control device provided in an embodiment of this application is shown below. Figure 4 As shown, the device includes:

[0124] The acquisition module 10 is used to acquire the device information of the managed chassis when it is detected that the managed chassis meets the preset conditions;

[0125] The determination module 11 is used to determine the chassis type of the managed chassis based on the device information; wherein, the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated based on the virtual device information and virtual machine chassis data sent by the simulation command and the preset communication link;

[0126] The control module 12 is used to obtain the chassis data of the managed chassis according to the chassis type, and to control the managed chassis, so as to determine whether the performance of the chassis management system meets the requirements based on the control results.

[0127] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus, which will not be repeated here.

[0128] This embodiment provides a chassis management system control device, comprising: when a managed chassis is detected to meet preset conditions, acquiring device information of the managed chassis to facilitate control of the chassis according to its type; determining the chassis type of the managed chassis based on the device information; wherein the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated according to virtual device information and virtual machine chassis data sent by simulation instructions and a preset communication link; acquiring chassis data of the managed chassis according to the chassis type, and controlling the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control results. Therefore, the technical solution provided by this application acquires virtual device information and virtual machine chassis data through a preset communication link to test the performance of the chassis management system and determine whether the chassis management system meets the requirements. It eliminates the need to use hardware equipment to build multiple chassis, reducing the time and manpower costs consumed in the testing process. Furthermore, the technical solution provided by this application is similar to the control method for physical chassis, and can be used to manage both virtual machine chassis and physical chassis simultaneously, without requiring specialized adjustments for different types of chassis, further improving testing efficiency.

[0129] Figure 5 A structural diagram of another chassis management system control device provided in an embodiment of this application is shown below. Figure 5 As shown, the chassis management system control device includes: a memory 20 for storing computer programs;

[0130] The processor 21 is used to execute computer programs to implement the steps of the chassis management system control method as described in the above embodiments.

[0131] The chassis management system control device provided in this embodiment may include, but is not limited to, smartphones, tablets, laptops, or desktop computers.

[0132] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one of the following hardware forms: Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as the Central Processing Unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an Artificial Intelligence (AI) processor, which is used to handle computational operations related to machine learning.

[0133] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 20 is used to store at least the following computer program 201, which, after being loaded and executed by the processor 21, is capable of implementing the relevant steps of the chassis management system control method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, and the storage method may be temporary storage or permanent storage. The operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, device information, chassis type, chassis data, etc.

[0134] In some embodiments, the chassis management system control device may further include a display screen 22, an input / output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.

[0135] Those skilled in the art will understand that Figure 5 The structure shown does not constitute a limitation on the control device of the chassis management system and may include more or fewer components than shown.

[0136] The chassis management system control device provided in this application includes a memory and a processor. When the processor executes the program stored in the memory, it can implement the following method:

[0137] When the managed chassis is detected to meet the preset conditions, the device information of the managed chassis is obtained;

[0138] The chassis type of the managed chassis is determined based on the equipment information; among which, chassis types include physical chassis and virtual machine chassis, and virtual machine chassis are chassis generated according to virtual device information and virtual machine chassis data sent by simulation instructions and preset communication links;

[0139] The system obtains the chassis data of the managed chassis based on the chassis type, and controls the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control results.

[0140] This embodiment provides a chassis management system control device, comprising: when a managed chassis is detected to meet preset conditions, acquiring device information of the managed chassis to facilitate control of the chassis according to its type; determining the chassis type of the managed chassis based on the device information; wherein the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated according to virtual device information and virtual machine chassis data sent by simulation instructions and a preset communication link; acquiring chassis data of the managed chassis according to the chassis type, and controlling the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control results. Therefore, the technical solution provided by this application acquires virtual device information and virtual machine chassis data through a preset communication link to test the performance of the chassis management system and determine whether the chassis management system meets the requirements. It eliminates the need to use hardware equipment to build multiple chassis, reducing the time and manpower costs consumed in the testing process. Furthermore, the technical solution provided by this application is similar to the control method for physical chassis, and can be used to manage both virtual machine chassis and physical chassis simultaneously, without requiring specialized adjustments for different types of chassis, further improving testing efficiency.

[0141] Finally, this application also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps described in the above method embodiments. This embodiment provides a chassis management system control device, comprising: when a managed chassis is detected to meet preset conditions, acquiring device information of the managed chassis to facilitate control of the chassis according to its type; determining the chassis type of the managed chassis based on the device information; wherein the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated according to virtual device information and virtual machine chassis data sent by simulation instructions and a preset communication link; acquiring chassis data of the managed chassis according to the chassis type, and controlling the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control result. Therefore, the technical solution provided by this application acquires virtual device information and virtual machine chassis data through a preset communication link, thereby testing the performance of the chassis management system to determine whether the chassis management system meets the requirements. This eliminates the need to use hardware equipment to build multiple chassis, reducing the time and manpower costs consumed in the testing process. Furthermore, the technical solution provided in this application is similar to the control method of physical chassis, and can be used to manage both virtual machine chassis and physical chassis at the same time, without the need for special adjustments for different types of chassis, thereby further improving testing efficiency.

[0142] It is understood that if the methods in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0143] The control method, apparatus, and medium for the chassis management system provided in this application have been described in detail above. The various embodiments in the specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0144] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A control method for a chassis management system, characterized in that, include: When the managed chassis is detected to meet the preset conditions, the device information of the managed chassis is obtained; The chassis type of the managed chassis is determined based on the device information; wherein, the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated based on the virtual device information and virtual machine chassis data sent by the client and the preset communication link; The chassis data of the managed chassis is obtained according to the chassis type, and the managed chassis is controlled to determine whether the performance of the chassis management system meets the requirements based on the control results. The step of determining the chassis type of the managed chassis based on the device information includes: Obtain the maintenance list of the chassis management system and determine the product ID of the managed chassis based on the device information; The chassis type of the managed chassis is determined based on the maintenance list and the product ID; The step of obtaining the chassis data of the managed chassis according to the chassis type includes: If the chassis type is a virtual machine chassis, historical chassis data is obtained through the preset communication link, and the managed chassis is simulated based on the historical chassis data. The simulation of the managed chassis based on the historical chassis data includes: obtaining simulation task requirements; parsing the simulation task requirements to obtain the target chassis type and the number of target chassis; generating a simulation system based on the target chassis type and the number of target chassis; and obtaining the working status information of each virtual machine chassis in the simulation system to determine the business capabilities of the chassis management system. If the chassis type is a physical chassis, then real-time chassis data is obtained through the preset communication link, and the working status of the physical chassis is monitored based on the real-time chassis data.

2. The chassis management system control method according to claim 1, characterized in that, The creation process of the virtual machine box includes: Determine whether virtual machine box registration information sent through the preset communication link has been obtained, wherein the virtual machine box registration information is information obtained after parsing the simulation command; If the virtual machine box registration information is obtained, the virtual registration code and product ID are obtained through the system wristband process; The virtual machine box is created based on the virtual registration code and the product ID.

3. The chassis management system control method according to claim 1, characterized in that, The managed chassis meets the preset conditions including: The chassis data of the managed chassis has changed.

4. The chassis management system control method according to claim 1, characterized in that, The device information includes a registration code and a product ID.

5. The chassis management system control method according to claim 1, characterized in that, The step of obtaining historical chassis data through the preset communication link includes: Obtain the protocol type of the managed chassis; The historical chassis data corresponding to the protocol type is obtained through the preset communication link.

6. The chassis management system control method according to claim 5, characterized in that, After the step of obtaining historical chassis data through the preset communication link, the method further includes: The historical chassis data is decrypted according to the protocol type.

7. The chassis management system control method according to claim 1, characterized in that, The process of obtaining the working status information of each virtual machine chassis in the simulation system includes: Obtain the temperature information, humidity information, and firmware version number information of each virtual machine box sent by the preset communication link.

8. The chassis management system control method according to claim 1, characterized in that, Before the step of obtaining the working status information of each virtual machine chassis in the simulation system, the method further includes: Determine whether the simulation system is compatible with the virtual machine chassis of the target chassis type; If incompatible, the test will be terminated.

9. The chassis management system control method according to claim 8, characterized in that, After the step of obtaining the chassis data of the managed chassis according to the chassis type, the method further includes: Obtain access information sent by the client; The system displays the operating status of the simulation system to the user based on the access information.

10. The chassis management system control method according to claim 1, characterized in that, Also includes: The managed chassis are tested according to the maintenance list to determine the performance of the chassis management system.

11. The chassis management system control method according to claim 1, characterized in that, After the step of monitoring the working status of the physical chassis based on the real-time chassis data, the method further includes: When an anomaly is detected in the physical chassis data, an alarm message is sent to the administrator.

12. The chassis management system control method according to claim 5, characterized in that, The specific steps of obtaining the historical chassis data corresponding to the protocol type through the preset communication link are as follows: the historical chassis data is data injected through an automated script.

13. The chassis management system control method according to claim 1, characterized in that, The preset communication link is an inter-process communication link.

14. The chassis management system control method according to claim 5, characterized in that, The protocol types include SAS protocol and NVME protocol.

15. A control device for a chassis management system, characterized in that, include: The acquisition module is used to acquire the device information of the managed chassis when it is detected that the managed chassis meets the preset conditions; The determination module is used to determine the chassis type of the managed chassis based on the device information; wherein, the chassis type includes physical chassis and virtual machine chassis, and the virtual machine chassis is a chassis generated based on the virtual device information and virtual machine chassis data sent by the client and the preset communication link; The control module is used to obtain the chassis data of the managed chassis according to the chassis type, and control the managed chassis to determine whether the performance of the chassis management system meets the requirements based on the control results. The step of determining the chassis type of the managed chassis based on the device information includes: Obtain the maintenance list of the chassis management system and determine the product ID of the managed chassis based on the device information; The chassis type of the managed chassis is determined based on the maintenance list and the product ID; The step of obtaining the chassis data of the managed chassis according to the chassis type includes: If the chassis type is a virtual machine chassis, historical chassis data is obtained through the preset communication link, and the managed chassis is simulated based on the historical chassis data. The simulation of the managed chassis based on the historical chassis data includes: obtaining simulation task requirements; parsing the simulation task requirements to obtain the target chassis type and the number of target chassis; generating a simulation system based on the target chassis type and the number of target chassis; and obtaining the working status information of each virtual machine chassis in the simulation system to determine the business capabilities of the chassis management system. If the chassis type is a physical chassis, then real-time chassis data is obtained through the preset communication link, and the working status of the physical chassis is monitored based on the real-time chassis data.

16. A control device for a chassis management system, characterized in that, Includes memory used to store computer programs; A processor, configured to implement the steps of the chassis management system control method as described in any one of claims 1 to 14 when executing the computer program.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the chassis management system control method as described in any one of claims 1 to 14.

Images