A method, system and device for unified processing of chassis management data

Abstract

The present invention provides a method, system, storage medium and device for unified processing of chassis management data, and the method includes: data processing steps. The data processing steps include the following steps: enumerating the function points supported in the chassis management program; for each function point, enumerating the data points supported by it to form a processing data table; traversing all the attribute points in each function point to form an attribute table; applying the attribute table to the processing data table, and supplementing the distinguishing mark of each attribute, and adding a mark whether the attribute is supported; for the processing flow of the data point, a function template for the data processing flow related to the mark whether the attribute is supported is made, and the input parameter is the processing data table. According to the present invention, a unified processing framework is established in the unified processing mode of chassis management data, which improves the readability, maintainability, reusability and portability of chassis management data processing.

Description

Technical Field

[0001] The present invention relates to the field of data management, and in particular to a method, system, storage medium and device for unified processing of chassis management data. Background Art

[0002] The storage system requires high reliability and high speed to process the massive data transmitted between servers and hard disks.

[0003] The chassis management module of the prior art is used to detect the operation status of the device in real time, including temperature, voltage, fan, etc.; in order to ensure that the device can operate stably and reliably for a long time, it is necessary to detect the information of these peripheral hardware in real time.

[0004] The chassis management module is divided into two parts: one part is data collection and status reporting based on the SES program or BMC program, and the other part is the EM thread in the storage main program, which is used for data alarm and processing.

[0005] The data processed by BMC is classified into multiple functional points according to function: temperature, voltage, fan, VPD, and other functional points; each functional point has many data points: taking the temperature functional point as an example, there are dozens of temperature points in a chassis; each data point can be divided into multiple attribute points according to its location, sensor type, access link difference, and feature difference.

[0006] In the encoding ideas of the existing technology, each data point is sorted out to see which attribute points are supported, and then the supported attribute points are processed; special cases in the attributes need to be executed separately.

[0007] With this idea, coding is easy to implement and is suitable for functions with fewer data points. However, for the chassis management program, which detects dozens of temperature points and dozens of voltage points at the same time, there are a large number of identical repeated operations, and there will be many special points, which will cause the following problems:

[0008] 1) The code is process-oriented and data-point-oriented;

[0009] 2) Data points have both general and specific attributes. To process specific attributes, you need to add "screening and specific processing of specific data points" separately, which is not universal.

[0010] 3) The coding process is easy to understand, but the code readability and integrity are poor. When maintaining the code, you cannot see all the attributes supported by a data point, which makes maintenance and debugging difficult.

[0011] 4) New version adaptation: When developing a new board, if a temperature point is no longer supported, the attribute needs to be deleted; if a new data point is added, the attributes of the data point need to be sorted out and added one by one within the process-oriented scope.

[0012] Therefore, to address the problem, it is necessary to propose a better unified processing mode for chassis management data to improve the readability, maintainability, reusability and portability of chassis management data processing. Summary of the invention

[0013] In view of this, the purpose of the present invention is to propose an improved method, system, storage medium and device for unified processing of chassis management data, so as to build a unified processing framework and improve the readability, maintainability, reusability and portability of chassis management data processing.

[0014] Based on the above purpose, on one hand, the present invention provides a method for unified processing of chassis management data, wherein the method includes a data processing step, and the data processing step includes the following steps:

[0015] List the functional points supported in the chassis management program;

[0016] For each of the functional points, the data points supported by the functional points are listed to form a processing data table;

[0017] Traversing all the attribute points in each of the function points to form an attribute table;

[0018] Apply the attribute table to the processed data table, and add a distinguishing mark for each attribute, and a mark indicating whether the attribute is supported;

[0019] A function template for the data processing flow related to a flag indicating whether the attribute is supported is created for the processing flow of the data point, and the input parameter is the processing data table.

[0020] In some embodiments of the method for unified processing of chassis management data according to the present invention, the function point includes at least one of temperature, voltage, fan, physical port information, MiniSAS port information, and hard disk information.

[0021] In some embodiments of the method for unified processing of chassis management data according to the present invention, the data processing step further includes determining the operation priority of each attribute when supplementing the distinguishing mark of each attribute.

[0022] In some embodiments of the method for unified processing of chassis management data according to the present invention, data is read only when a high priority attribute is marked as supported.

[0023] In some embodiments of the method for unified processing of chassis management data according to the present invention, the method further comprises a data reporting step, which comprises the following steps:

[0024] Extract the byte position and bit position of padding of a type of data and form a position table as a position template;

[0025] Extract the data to be filled and form a reporting data table as a data template;

[0026] Encapsulates the position filling function, with the input parameters being the data template and the position template.

[0027] In some embodiments of the method for unified processing of chassis management data according to the present invention, when adapting a new board, for data points that can be inherited, directly copy the row in the processing data table or the reporting data table; for data points that are no longer used, directly delete the row in the processing data table or the reporting data table; for newly added data points, add a new row of data points in the processing data table or the reporting data table.

[0028] Another aspect of the present invention further provides a system for unified processing of chassis management data, comprising: a data processing module, which performs data processing and includes the following modules:

[0029] A function point enumeration module, the function point enumeration module enumerating function points supported in the chassis management program;

[0030] A data point enumeration module, which enumerates the data points supported by each function point to form a processing data table;

[0031] An attribute table composition module, which traverses all attribute points in each of the function points to compose an attribute table;

[0032] An attribute marking module, which applies the attribute table to the processed data table, and adds a distinguishing mark for each attribute, and adds a mark indicating whether the attribute is supported;

[0033] A data processing template function encapsulation module is used to create a function template for the data processing flow that is related to a flag indicating whether the attribute is supported according to the processing flow of the data point, and the input parameter is the processing data table.

[0034] In some embodiments of the system for unified processing of chassis management data according to the present invention, the function point includes at least one of temperature, voltage, fan, physical port information, MiniSAS port information, and hard disk information.

[0035] In some embodiments of the system for unified processing of chassis management data according to the present invention, the attribute marking module determines the operation priority of each attribute when supplementing the distinguishing mark of each attribute.

[0036] In some embodiments of the system for unified processing of chassis management data according to the present invention, the data processing module reads data only when a high priority attribute is marked as supported.

[0037] In some embodiments of the system for unified processing of chassis management data according to the present invention, the mode configuration module is further configured to further include a data reporting module, which is used for data reporting and includes the following modules:

[0038] A position table composition module, wherein the position table composition module extracts the byte position and the bit position of the padding of a type of data and composes a position table as a position template;

[0039] A data table composition module, which extracts data to be filled and composes a reporting data table as a data template;

[0040] A position filling function encapsulation module encapsulates the position filling function, and the input parameters are the data template and the position template.

[0041] In some embodiments of the system for unified processing of chassis management data according to the present invention, when adapting a new board, the data processing module or the data reporting module directly copies the row in the processing data table or the reporting data table for data points that can be inherited; directly deletes the row in the processing data table or the reporting data table for data points that are no longer used; and adds a new row of data points in the processing data table or the reporting data table for newly added data points.

[0042] In yet another aspect of the present invention, a computer-readable storage medium is provided, storing computer program instructions, which, when executed, implement any of the above-mentioned methods for unified processing of chassis management data according to the present invention.

[0043] In another aspect of the present invention, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, any one of the above methods for unified processing of chassis management data according to the present invention is executed.

[0044] The present invention has at least the following beneficial technical effects: the present invention proposes a unified processing mode for chassis management data, extracts each type of data, and supports data sets; changes the process- and data point-oriented encoding method to a data table and template-oriented processing method; no longer focuses on the determination of data points, but on the determination of attributes, to achieve high reusability of the processing mechanism; separates data tables and template functions, only needs to focus on data tables, gets rid of cumbersome process processing, focuses on the adaptation of data attributes, improves code development efficiency, and reduces maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0046] In the figure:

[0047] Figure 1 A schematic block diagram showing an embodiment of a method for unified processing of chassis management data according to the present invention;

[0048] Figure 2 A schematic block diagram showing another embodiment of a method for unified processing of chassis management data according to the present invention;

[0049] Figure 3 A schematic block diagram showing an embodiment of a system for unified processing of chassis management data according to the present invention;

[0050] Figure 4 A schematic block diagram showing another embodiment of a system for unified processing of chassis management data according to the present invention;

[0051] Figure 5 A schematic diagram showing an embodiment of a computer-readable storage medium for implementing a method for unified processing of chassis management data according to the present invention;

[0052] Figure 6 A schematic diagram showing the hardware structure of an embodiment of a computer device for realizing a method for unified processing of chassis management data according to the present invention;

[0053] Figure 7 An example diagram showing a situation where there are differences in attributes supported by multiple data;

[0054] Figure 8 The data table formed by the method for unified processing of chassis management data according to the present invention is shown.

[0055] Fig. 9 A schematic diagram showing the data reporting steps in the chassis management data processing method in the prior art is shown. DETAILED DESCRIPTION

[0056] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the embodiments of the present invention are further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0057] It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are intended to distinguish two non-identical entities or non-identical parameters with the same name. It can be seen that "first" and "second" are only for the convenience of expression and should not be understood as limitations on the embodiments of the present invention. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, other steps or units inherent to a process, method, system, product or device that includes a series of steps or units.

[0058] In the traditional chassis management module, the main tasks of the BMC program are as follows:

[0059] 1) Read the peripheral status of the device at a high frequency, such as fan, voltage, fan and other information, and make abnormal judgments; when an abnormal state is determined, report its status and information to the EM thread;

[0060] 2) Receive and execute control instructions sent by the EM thread;

[0061] 3) Some self-control processing can also be performed internally, such as automatically adjusting the fan speed according to the fan speed strategy when detecting the high or low temperature of the chassis.

[0062] As a data processing and collection unit, the BMC program mainly collects various types of data through the i2c link. The i2c link is very busy. The data accessed by i2c include: various sensors, CPLD, PSU, VPD and other data. And each type of data is large, so it is necessary to add an i2c switch to expand the GPIO. That is, one i2c bus may have many access paths.

[0063] The data processed by BMC is classified into multiple functional points according to the functional classification: temperature, voltage, fan, VPD, etc.

[0064] Each function point has many data points: taking the temperature function point as an example, there are dozens of temperature points in a chassis;

[0065] Each data point can be divided into multiple attribute points according to its location, sensor type, access link difference, and feature difference, such as:

[0066] 1) On a pluggable board, it has pluggable properties;

[0067] 2) A certain temperature point supports single-point detection, double-point detection, and multi-point detection;

[0068] 3) The data may be read successfully and the reading value is within the normal range;

[0069] 4) The data may be read successfully, but the reading value exceeds the warning range;

[0070] 5) Data may fail to be read and cannot be recovered;

[0071] 6) Some temperature points support level 2 alarms, and some support level 3 alarms.

[0072] In the traditional chassis management module, the EM thread is part of the storage main program, and its main tasks are as follows:

[0073] 1) Receive data and status from BMC and update internal data;

[0074] 2) When there is an abnormal state, a warning is issued that the user can view intuitively, and the main system is notified whether other processing is required for the abnormality; (for example, when the temperature of certain key components is too high, whether to shut down for protection);

[0075] 3) When the main system controls a certain hardware during program operation, it is sent to the BMC program through the EM thread, and the BMC program actually controls it (such as reading and writing VPD configuration information, turning on a certain abnormal control light)

[0076] According to the traditional coding idea, each data point will be sorted out to see which attribute points are supported, and then the supported attribute points will be processed; for special cases, they need to be executed separately. The following shows an example of the traditional coding idea;

[0077]

[0078] The inventor found that the chassis management program supports the management of multiple function points, and multiple function points manage many data points. These data points have roughly similar attributes and specific attribute points, that is, there are a large number of repeated data processing processes. The use of data point-oriented processing methods leads to a lot of specific processing in the processing process, resulting in poor code versatility and unfavorable data expansion. When new models are adapted, there will also be a large number of different data point configurations, and the development efficiency is relatively low.

[0079] To solve the above problem, a first aspect of the present invention provides a method for unified processing of chassis management data. Figure 1 FIG. 2 is a schematic block diagram showing an embodiment of a method for unified processing of chassis management data according to the present invention. Figure 1In the embodiment shown, the method includes: a data processing step S10, the data processing step S10 includes the following steps

[0080] Step S110: List the function points supported by the chassis management program;

[0081] Step S120: for each of the function points, list the data points it supports to form a processing data table;

[0082] Step S130: traverse all attribute points in each of the function points to form an attribute table;

[0083] Step S140: applying the attribute table to the processed data table, and supplementing the distinguishing mark of each attribute, and adding a mark indicating whether the attribute is supported;

[0084] Step S150: for the processing flow of the data point, a function template for the data processing flow is created which is related to the flag indicating whether the attribute is supported, and the input parameter is the processing data table.

[0085] In some embodiments of the method 100 for unified processing of chassis management data according to the present invention, the function point includes at least one of temperature, voltage, fan, physical port information, MiniSAS port information, hard disk information, and the like.

[0086] Taking the temperature point as one of the functional points as an example, the supported data points may include: air inlet temperature, multiple main chip temperatures, air outlet temperature, various sensor temperatures on the board, PSU temperature, and ambient temperature.

[0087] In some embodiments of the method 100 for unified processing of chassis management data according to the present invention, the data processing step further includes determining the operation priority of each attribute when supplementing the distinguishing mark of each attribute.

[0088] Take the temperature point as one of the function points as an example: its attributes can be as follows and ranked in priority:

[0089] Pluggable attribute: The first priority is to confirm whether the temperature point is in place and whether the chip access link with the program is connected; only when it is "connected" can data be read and processed. For PSU_Temp (the temperature point of the PSU power supply), when the PSU is unplugged, the access link with the program is disconnected and can no longer be accessed; after the PSU is connected, the access link with the program is connected and can be accessed; therefore, it is necessary to distinguish the pluggable attribute. For Inlet_Temp (the temperature point on the motherboard), it is on the same motherboard as the main chip running the chassis management program, and the pluggable attribute is not distinguished, that is, this point is always in place).

[0090] OK and FAIL attributes: second priority. Data read can be initiated only when the bit is in place.

[0091] Over-temperature alarm attributes OverTempWarning, OverTempFault, and SuperCriticalFault: The third priority level. Only when the data value is in place and read successfully, can the data value be determined to determine whether there is an over-temperature alarm. This indicates the third-level over-temperature alarm processing.

[0092] When a data point supports this attribute, it can be used normally; when a temperature point does not distinguish this attribute, it can be set to always be TRUE or always be FALSE; so that a unified calling function can be called later without distinguishing data points, thus achieving universality of data processing.

[0093] Take the pluggable properties of the temperature point as an example:

[0094] PSU_Temp: Because this temperature point is on the pluggable PSU, when the PSU is connected, the temperature point is in place; when the PSU is unplugged, the temperature point is not in place; therefore, it is necessary to determine whether it is in place;

[0095] Inlet_Temp: The air inlet temperature value on the mainboard. Because it is on the same board as the main chip, when the mainboard is unplugged, the main program cannot run. Therefore, it is assumed to be in place; that is, no in-place processing is required, that is, if_presence = TRUE.

[0096] Furthermore, still taking the data reading of the temperature point as an example: first read the whether-in-position flag, and then read the temperature value according to whether it is in-position;

[0097] Encapsulate the check_presence() function:

[0098] For PSU_Temp, read the PSU presence signal to determine whether it is in place; call check_presence() to return the actual presence status;

[0099] For Inlet_Temp, it does not have the pluggable attribute. When check_presence() is called, the return value is always 1.

[0100] Taking the three-level over-temperature alarm attribute of temperature as an example, some temperature points support three-level alarms, some temperature points only support two-level alarms, and some temperatures only support one-level alarms. However, for all temperature points, three-level alarm attributes are set; for supported alarm levels, they need to be obtained through data calculations; for unsupported alarm levels, they are directly set to 0, indicating that no special calculations are required and they will not be triggered. In this way, the same comprehensive alarm status function () can be used to perform comprehensive calculations on the status values ​​and uniformly process them, without having to identify which temperature point supports which level of alarm.

[0101] The following further illustrates the function of the method for unified processing of chassis management data according to the present invention by comparing the specific examples of the present invention with the data processing steps in the prior art.

[0102] In processing Figure 7 When the discrete data attributes shown in the figure are shown (the figure lists the attribute differences supported by each data), the data processing steps in the prior art and the original data point-oriented processing method for determining and processing specific data points are as follows:

[0103]

[0104] The above method can be summarized as the pattern of data table → data flow processing function ().

[0105] In the method 100 for unified processing of chassis management data, the mode of data table + attribute table → data processing template function () is adopted to unify the attributes of the data points into the following attribute table:

[0106]

[0107] The resulting data table is as follows Figure 8 shown.

[0108] The process of whether to support the attribute is as follows:

[0109]

[0110] Therefore, according to the method 100 for unified processing of chassis management data of the present invention, in the data processing step, the processing flow oriented to data points is changed to a processing flow oriented to attribute points, and the method of "attribute table + data table + template function for attribute processing" is used.

[0111] The data processing method according to the above embodiment is universal; the processing function achieves unified data processing, and the attribute distinction of the data is reflected in the data table, which is clear at a glance; subsequent development and maintenance can focus on the data table, without the need to sort out the process of each temperature point one by one. When troubleshooting data errors, the focus is mainly on the numerical differences in the data table, which improves the efficiency of problem location.

[0112] According to the method 100 for unified processing of chassis management data of the present invention, "data points" and "attribute processing" are separated. The attribute processing function processes data points one by one and only determines whether the attribute point is supported, without determining which data point. It has strong versatility. The processing mechanism for the same type of data is unified, and only one processing function needs to be called. The processing function is short and concise, and only focuses on how to process, not on the specific content. It has strong reusability and high code execution efficiency. When encoding, there is no need to pay attention to the processing of the process in the processed data, which reduces the probability of errors and improves coding efficiency and development efficiency. When maintaining the product, you only need to pay attention to the "attributes" and "support flags" of the data to see the overall situation at a glance and improve maintainability. When debugging data points, there is no need to worry about the process.

[0113] Figure 2 A schematic diagram of a preferred embodiment of a method for unified processing of chassis management data according to the present invention is shown. Figure 2 The following examples further illustrate the method according to the present invention.

[0114] Figure 2 The method for unified processing of chassis management data according to the present invention further includes a data reporting step S20, and the data reporting step S20 includes the following steps:

[0115] Step S210: extracting the byte position and bit position of the padding of a type of data, and forming a position table as a position template;

[0116] Step S220: extracting the data to be filled and forming a reporting data table as a data template;

[0117] Step S230: Encapsulate the position filling function, with the input parameters being the data template and the position template.

[0118] A data packet contains hundreds or thousands of data, hundreds of bytes, and many bit operations. Taking temperature points as an example, there are dozens of temperature points, and there are dozens of groups of data arranged in the same format. If we calculate them one by one according to the process and check the offset address and bit position of each data one by one, the calculation is repetitive and tedious, and it is easy to make mistakes, so error correction is a complicated process.

[0119] The following further illustrates the function of the method for unified processing of chassis management data according to the present invention by comparing the specific examples of the present invention with the data reporting steps in the prior art.

[0120] The data reporting steps in the prior art are as follows: Fig. 9 shown. Fig. 9The data format of the communication with the main program is shown. A data packet contains quite complicated function points, data points, attribute points, and corresponding data addresses. The data reporting steps of the prior art include: listing all the data of the data packet, making a data table, and calculating the location one by one. Since the entire reporting process is processing calculations, the calculations are complicated and very prone to errors.

[0121] The data reporting step of the method for unified processing of chassis management data according to the present invention converts data with the same function and the same position format into a data table; together with the position template, it is universally processed through the template function. Similar to the data processing step in the method for unified processing of chassis management data according to the present invention, the data reporting step of the present invention allows subsequent development and maintenance to focus only on the data table, greatly improving efficiency. In the data reporting step, the data-oriented processing flow in the prior art is changed to a template function-oriented processing flow, using the method of "filling the position template + filling the data table + filling the processed template function".

[0122] Because according to Figure 2 The method for unified processing of chassis management data of the present invention shown adopts the method of {template + data} to define the position filling method of each data, so it is called once for each data point in a loop, which is highly reusable and completes the processing of repeated data; simplifies the processing flow; solves the problem of cumbersome and repetitive data processing; and only needs to focus on the processing content of the data.

[0123] In some embodiments of the method 100 for unified processing of chassis management data according to the present invention, when adapting a new board, for data points that can be inherited, directly copy the row in the processing data table or the reporting data table; for data points that are no longer used, directly delete the row in the processing data table or the reporting data table; for newly added data points, add a new row of data points in the processing data table or the reporting data table.

[0124] The chassis management data processing method of the prior art has the following disadvantages when adapting to new boards: in order to process specific attributes, it is necessary to determine the data points, which loses universality and is not conducive to code inheritance and transplantation; when adapting to new boards, changes in data points require adjustment of process codes, and whether adding or deleting codes is relatively complicated; when a specific data point supports multiple attributes and the processing codes are distributed in multiple locations, it is even more difficult to sort out, the maintainability is poor, and it is impossible to see the whole picture at a glance.

[0125] According to the method 100 for unified processing of chassis management data of the present invention, when adapting a new board, for the above-mentioned temperature-related processing, the process function call of the processing almost does not need to be changed. The only change is to adjust the temperature point attributes in the data table according to the temperature point difference of the new board, thereby improving the efficiency of adaptation. Therefore, according to the method 100 for unified processing of chassis management data of the present invention, the code is highly adapted, the template function is short and concise, and highly reusable; it is not easy to make mistakes, and the development efficiency and maintenance efficiency are improved.

[0126] Note that in the background description of this application, BMC is mentioned for chassis management program, but the chassis management program is not limited to BMC, but can be expanded to all embedded programs, targeting application scenarios where there is a large amount of unified processing of data with the same function.

[0127] A second aspect of the present invention also provides a system for unified processing of chassis management data. Figure 3 FIG. 2 is a schematic block diagram showing an embodiment of a system for unified processing of chassis management data according to the present invention. Figure 3 As shown, the system includes: a data processing module 10, which performs data processing and includes the following modules:

[0128] A function point enumeration module 110, which enumerates the function points supported in the chassis management program;

[0129] A data point enumeration module 120, which enumerates the data points supported by each function point to form a processing data table;

[0130] An attribute table forming module 130, which traverses all attribute points in each of the function points to form an attribute table;

[0131] An attribute marking module 140, which applies the attribute table to the processed data table, and adds a distinguishing mark for each attribute, and adds a mark indicating whether the attribute is supported;

[0132] The data processing template function encapsulation module 150 creates a function template for the data processing flow related to a flag indicating whether the attribute is supported according to the processing flow of the data point, and the input parameter is the processing data table.

[0133] In some embodiments of the system 200 for unified processing of chassis management data according to the present invention, the function point includes at least one of temperature, voltage, fan, physical port information, MiniSAS port information, and hard disk information.

[0134] In some embodiments of the system 200 for unified processing of chassis management data according to the present invention, the attribute marking module determines the operation priority of each attribute when supplementing the distinguishing mark of each attribute.

[0135] In some embodiments of the system 200 for unified processing of chassis management data according to the present invention, the data processing module 10 reads data only when the attribute with a high priority is marked as supported.

[0136] In some embodiments of the system 200 for unified processing of chassis management data according to the present invention, the system further comprises a data reporting module 20, which is used for data reporting and comprises the following modules:

[0137] A position table forming module 210, wherein the position table forming module 210 extracts the byte position and the bit position of the padding of a type of data and forms a position table as a position template;

[0138] A data table composition module 220, which extracts data to be filled and composes a reporting data table as a data template;

[0139] The position filling function encapsulation module 230 encapsulates the position filling function, and the input parameters are the data template and the position template.

[0140] In some embodiments of the system 200 for unified processing of chassis management data according to the present invention, when adapting a new board, the data processing module or the data reporting module directly copies the row in the processing data table or the reporting data table for data points that can be inherited; directly deletes the row in the processing data table or the reporting data table for data points that are no longer used; and adds a new row of data points in the processing data table or the reporting data table for newly added data points.

[0141] A third aspect of the embodiments of the present invention further provides a computer-readable storage medium. Figure 5 A schematic diagram of a computer-readable storage medium for a method for unified processing of chassis management data provided by an embodiment of the present invention is shown. Figure 5 As shown, the computer-readable storage medium 300 stores computer program instructions 310, which can be executed by a processor. When the computer program instructions 310 are executed, the method of any of the above embodiments is implemented.

[0142] It should be understood that, without conflict, all embodiments, features and advantages described above for the method for unified processing of chassis management data according to the present invention are also applicable to the system and storage medium for unified processing of chassis management data according to the present invention.

[0143] According to a fourth aspect of the embodiments of the present invention, a computer device 400 is provided, including a memory 420 and a processor 410, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method of any one of the above embodiments is implemented.

[0144] like Figure 6 FIG. 1 is a schematic diagram of the hardware structure of a computer device for executing the unified processing method of chassis management data provided by the present invention. Figure 6 The computer device 400 shown in FIG. 1 is taken as an example, and the computer device includes a processor 410 and a memory 420, and may also include: an input device 430 and an output device 440. The processor 410, the memory 420, the input device 430 and the output device 440 may be connected via a bus or other means. Figure 6 The example of the bus connection is taken as an example. The input device 430 can receive input digital or character information, and generate signal input related to the unified processing of chassis management data. The output device 440 can include display devices such as display screens.

[0145] The memory 420, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions / modules corresponding to the resource monitoring method in the embodiment of the present application. The memory 420 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the use of the resource monitoring method, etc. In addition, the memory 420 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 420 may optionally include a memory remotely arranged relative to the processor 410, and these remote memories may be connected to the local module via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0146] The processor 410 executes various functional applications and data processing of the server by running the non-volatile software programs, instructions and modules stored in the memory 420, that is, implements the resource monitoring method of the above method embodiment.

[0147] It will also be appreciated by those skilled in the art that various exemplary logic blocks, modules, circuits and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, a general description has been given to the functions of various schematic components, blocks, modules, circuits and steps. Whether this function is implemented as software or hardware depends on specific applications and the design constraints imposed on the entire system. Those skilled in the art can implement the function in various ways for each specific application, but this implementation decision should not be interpreted as causing a departure from the disclosed scope of the embodiments of the present invention.

[0148] Finally, it should be noted that the computer-readable storage medium (e.g., memory) herein may be a volatile memory or a nonvolatile memory, or may include both a volatile memory and a nonvolatile memory. As an example and not by way of limitation, a nonvolatile memory may include a read-only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. A volatile memory may include a random access memory (RAM), which may act as an external cache memory. As an example and not by way of limitation, RAM may be obtained in a variety of forms, such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to include, but are not limited to, these and other suitable types of memory.

[0149] The various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or executed using the following components designed to perform the functions herein: a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP, and / or any other such configuration.

[0150] The above are exemplary embodiments disclosed in the present invention, but it should be noted that various changes and modifications may be made without departing from the scope disclosed in the embodiments of the present invention as defined in the claims. The functions, steps and / or actions of the method claims according to the disclosed embodiments described herein do not need to be performed in any particular order. In addition, although the elements disclosed in the embodiments of the present invention may be described or required in individual form, they may also be understood as multiple unless explicitly limited to the singular.

[0151] It should be understood that, as used herein, the singular form "a" or "an" is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations of one or more of the items listed in association. The serial numbers of the embodiments disclosed in the above embodiments of the present invention are for description only and do not represent the advantages and disadvantages of the embodiments.

[0152] A person skilled in the art should understand that the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the disclosure of the embodiments of the present invention (including the claims) is limited to these examples; under the concept of the embodiments of the present invention, the technical features in the above embodiments or different embodiments can also be combined, and there are many other changes in different aspects of the embodiments of the present invention as above, which are not provided in detail for the sake of simplicity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present invention should be included in the protection scope of the embodiments of the present invention.

Claims

1. A method for unified processing of chassis management data, It is characterized in that The method comprises a data processing step, wherein the data processing step comprises the following steps: List the functional points supported in the chassis management program; For each of the functional points, the data points supported by the functional points are listed to form a processing data table; Traversing all the attribute points in each of the function points to form an attribute table; Apply the attribute table to the processed data table, and add a distinguishing mark for each attribute, and a mark indicating whether the attribute is supported; A function template for the data processing flow related to a flag indicating whether the attribute is supported is produced for the processing flow of the data point, and the input parameter is the processing data table; The method further comprises a data reporting step, which comprises the following steps: Extract the byte position and bit position of padding of a type of data and form a position table as a position template; Extract the data to be filled and form a reporting data table as a data template; Encapsulates the position filling function, with the input parameters being the data template and the position template.

2. The method according to claim 1, It is characterized in that The function point includes at least one of temperature, voltage, fan, physical port information, MiniSAS port information, and hard disk information.

3. The method according to claim 1, It is characterized in that The data processing step also includes determining the operation priority of each attribute when supplementing the distinguishing mark of each attribute.

4. The method according to claim 3, It is characterized in that Data is read only if the higher priority attribute is flagged as supported.

5. The method according to any one of claims 1 to 4, It is characterized in that When adapting a new board, for data points that can be inherited, directly copy the row in the processing data table or the reporting data table; for data points that are no longer used, directly delete the row in the processing data table or the reporting data table; for newly added data points, add a new row of data points in the processing data table or the reporting data table.

6. A system for unified processing of chassis management data, It is characterized in that include: The data processing module performs data processing and includes the following modules: A function point enumeration module, the function point enumeration module enumerating function points supported in the chassis management program; A data point enumeration module, which enumerates the data points supported by each function point to form a processing data table; An attribute table composition module, which traverses all attribute points in each of the function points to compose an attribute table; An attribute marking module, which applies the attribute table to the processed data table, and adds a distinguishing mark for each attribute, and adds a mark indicating whether the attribute is supported; A data processing template function encapsulation module, which makes a function template for the data processing flow related to a flag indicating whether the attribute is supported according to the processing flow of the data point, and the input parameter is the processing data table; The system further includes a data reporting module, which is used for data reporting and includes the following modules: A position table composition module, wherein the position table composition module extracts the byte position and the bit position of the padding of a type of data and composes a position table as a position template; A data table composition module, which extracts data to be filled and composes a reporting data table as a data template; A position filling function encapsulation module encapsulates the position filling function, and the input parameters are the data template and the position template.

7. The system according to claim 6, It is characterized in that When adapting to a new board, the data processing module or the data reporting module directly copies the row in the processing data table or the reporting data table for data points that can be inherited; directly deletes the row in the processing data table or the reporting data table for data points that are no longer used; and adds a new row of data points in the processing data table or the reporting data table for newly added data points.

8. A computer device comprising a memory and a processor, It is characterized in that The memory stores a computer program, and when the computer program is executed by the processor, the method for unified processing of chassis management data as described in any one of claims 1 to 5 is performed.

Images