Server information management method and device

Abstract

The embodiment of the invention provides a server information management method and device, and the method comprises the steps: obtaining the basic information of a target server; based on the basic information, configuring a first node in a version chain, the first node being used for representing a target server of a first version, the first version being obtained based on the basic information; under the condition that the target server is updated, obtaining updating information of the target server; based on the update information, a second node in the version chain is configured, the second node is used for representing a target server of a second version, the second version is obtained based on the update information, and the first node is a father node of the second node. Through the server information management method and device, the problem that the management efficiency of the server information is low is solved, and the effect of improving the management efficiency of the server information is achieved.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of computers, and more particularly, to a method and apparatus for managing server information. Background Art

[0002] In the related art, in the scenario of server management, since server management relies on interface document analysis and manual testing, when the server version is frequently updated, and different customers may have different customization requirements for the same model of server, resulting in a large number of variants in server interfaces and function implementations. When managing these servers, a large amount of interface document analysis and a large amount of manual testing are required, which is time-consuming and laborious, and thus leads to the problem of low management efficiency of server information. Therefore, there is a problem of low management efficiency of server information.

[0003] In response to the above problems, no effective solution has been proposed yet. Summary of the Invention

[0004] Embodiments of the present application provide a method and apparatus for managing server information to at least solve the problem of low management efficiency of server information in the related art.

[0005] According to an embodiment of the present application, a method for managing server information is provided, including: obtaining basic information of a target server; based on the basic information, configuring a first node in a version chain, where the first node is used to represent a target server of a first version, and the first version is obtained based on the basic information; in the case where the target server is updated, obtaining update information of the target server; based on the update information, configuring a second node in the version chain, where the second node is used to represent a target server of a second version, the second version is obtained based on the update information, and the first node is the parent node of the second node.

[0006] According to another embodiment of the present application, a device for managing server information is provided, including: a first obtaining unit, configured to obtain basic information of a target server; a first configuring unit, configured to configure a first node in a version chain based on the basic information, where the first node is used to represent a target server of a first version, and the first version is obtained based on the basic information; a second obtaining unit, configured to obtain update information of the target server in the case where the target server is updated; a second configuring unit, configured to configure a second node in the version chain based on the update information, where the second node is used to represent a target server of a second version, the second version is obtained based on the update information, and the first node is the parent node of the second node.

[0007] As an alternative solution, the above-mentioned first configuration unit includes: a first configuration module, configured to configure a first verification function for the first node when the above-mentioned basic information includes information about the first function of the above-mentioned target server, where the above-mentioned first verification function is used to verify the above-mentioned first function; the above-mentioned second configuration unit includes: a second configuration module, configured to configure a second verification function for the second node when the above-mentioned update information includes information about the newly added second function of the above-mentioned target server, where the above-mentioned second verification function is used to verify the above-mentioned second function.

[0008] As an alternative solution, the above-mentioned second configuration unit includes: an acquisition module, configured to acquire the version basic information corresponding to the above-mentioned customized version when acquiring the customized version that the above-mentioned target server needs to be compatible with; a first verification module, configured to use the above-mentioned first verification function to verify the above-mentioned version basic information to obtain a first verification result, where the above-mentioned first verification result is used to verify the matching degree between the function corresponding to the above-mentioned version basic information and the above-mentioned first function; a determination module, configured to determine that the above-mentioned customized version is incompatible with the above-mentioned version chain when the above-mentioned first verification result indicates that the verification fails; a second verification module, configured to use the above-mentioned second verification function to verify the above-mentioned version basic information to obtain a second verification result when the above-mentioned first verification result indicates that the verification passes, where the above-mentioned second verification result is used to verify the matching degree between the function corresponding to the above-mentioned version basic information and the above-mentioned second function; a third configuration module, configured to configure a third node in the above-mentioned version chain based on the above-mentioned version basic information when the above-mentioned second verification result indicates that the verification fails, where the above-mentioned third node is used to represent the target server of the above-mentioned customized version, and the above-mentioned first node is the parent node of the above-mentioned third node; a fourth configuration module, configured to configure a fourth node in the above-mentioned version chain based on the above-mentioned version basic information when the above-mentioned second verification result indicates that the verification passes, where the above-mentioned fourth node is used to represent the target server of the above-mentioned customized version, and the above-mentioned second node is the parent node of the above-mentioned fourth node.

[0009] As an alternative solution, the above-mentioned first configuration unit includes: a first creation module, configured to create a main version line in the above-mentioned version chain based on the hardware configuration in the above-mentioned basic information before configuring the first node in the above-mentioned version chain based on the above-mentioned basic information, where the above-mentioned main version line is associated with the above-mentioned first node and the above-mentioned second node; a second creation module, configured to create a version branch line in the above-mentioned version chain based on the hardware configuration in the above-mentioned version basic information before configuring the above-mentioned third node in the above-mentioned version chain based on the above-mentioned version basic information, where the above-mentioned version branch line is associated with the above-mentioned third node.

[0010] As an alternative, the above device further includes: a third acquisition unit, configured to acquire a first feature set corresponding to the above version chain when the above version chain has been created, where the first feature set is used to record feature information involved in each node in the above version chain; an update unit, configured to update the first feature set after configuring the first node in the version chain based on the above basic information, so that the first feature set records the feature information involved in the first node.

[0011] As an alternative, the above device further includes: a fourth acquisition unit, configured to acquire a second feature set corresponding to the server to be managed; a comparison unit, configured to compare the first feature set with the second feature set to obtain a comparison result; a management unit, configured to manage the server to be managed using the above version chain when the comparison result indicates that the first feature set and the second feature set meet the similarity condition; a fifth acquisition unit, configured to acquire other version chains except the above version chain to manage the server to be managed when the comparison result indicates that the first feature set and the second feature set do not meet the above similarity condition.

[0012] As an alternative, the above first configuration unit includes: an allocation unit, configured to allocate corresponding weights to at least one piece of attribute information involved in the first node, where the weights are used to indicate the importance of the attribute information for the target server.

[0013] According to another embodiment of the present application, there is also provided a computer-readable storage medium, in which a computer program is stored, where the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0014] According to another embodiment of the present application, there is also provided an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0015] Through the present application, the basic information of the target server is acquired; based on the basic information, the first node in the version chain is configured, where the first node is used to represent the target server of the first version, and the first version is obtained based on the basic information; when the target server is updated, the update information of the target server is acquired; based on the update information, the second node in the version chain is configured, where the second node is used to represent the target server of the second version, and the second version is obtained based on the update information, and the first node is the parent node of the second node.

[0016] Specifically, by obtaining the basic information of the target server and configuring the first node in the version chain based on this information, the initial version and characteristics of the target server can be accurately represented. In the case of server updates, further obtain the update information and configure the second node in the version chain based on this information to represent the updated version. Moreover, as a child node of the first node, the second node not only records the characteristics and changes of the new version but also maintains the continuity and difference records between versions, which can clearly display the evolution history of the server version and can quickly locate the differences in the implementation of functions by traversing the version chain during the adaptation process of the new version, improving the efficiency of server information management. Since it is possible to quickly locate the differences in the implementation of functions by traversing the version chain during the adaptation process of the new version, the problem of low management efficiency of server information can be solved, and thus the technical effect of improving the management efficiency of server information is achieved. Brief Description of the Drawings

[0017] Figure 1 is a schematic diagram of the application environment of the server information management method according to an embodiment of the present application;

[0018] Figure 2 is a flowchart of the server information management method according to an embodiment of the present application;

[0019] Figure 3 is a schematic diagram of the server information management method according to an embodiment of the present application;

[0020] Figure 4 is a schematic diagram of the server information management method according to an embodiment of the present application;

[0021] Figure 5 is a structural block diagram of the server information management device according to an embodiment of the present application. Detailed Embodiments

[0022] The embodiments of the present application will be described in detail below with reference to the drawings and in conjunction with the embodiments.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence.

[0024] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 is a hardware structural block diagram of a server device of a server information management method according to an embodiment of the present application. As Figure 1 shown, the server device may include one or more ( Figure 1Only one processor 102 is shown (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a field-programmable gate array FPGA), and a memory 104 for storing data. Among them, the above server device may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that Figure 1 The structure shown is only schematic and does not limit the structure of the above server device. For example, the server device may further include more or fewer components than those shown Figure 1 shown, or have a different configuration from that Figure 1 shown.

[0025] The memory 104 can be used to store computer programs. For example, software programs and modules of application software, such as the computer program corresponding to the management method of server information in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implements the above method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely set relative to the processor 102, and these remote memories can be connected to the server device through a network. Examples of the above network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0026] The transmission device 106 is used to receive or send data via a network. Specific examples of the above network may include a wireless network provided by the communication provider of the server device. In one instance, the transmission device 106 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus communicate with the Internet. In one instance, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0027] In this embodiment, a method for managing server information is provided. Figure 2 is a flowchart of the method for managing server information according to the embodiments of the present application, as shown in Figure 2 shown, and the process includes the following steps:

[0028] Step S202, obtaining the basic information of the target server;

[0029] In an alternative embodiment, the target server may be, but is not limited to, a specific server that needs to be managed or compatibility adapted.

[0030] In an alternative embodiment, the basic information may, but is not limited to, include information such as the model, manufacturer, platform, project, version number, etc. of the server, and may be used, but is not limited to, for initially identifying and classifying the target server.

[0031] Step S204: Configure the first node in the version chain based on the basic information, where the first node is used to represent the target server of the first version, and the first version is obtained based on the basic information.

[0032] In an alternative embodiment, the version chain may, but is not limited to, be a structured data representation for recording the evolution process between different versions of the server, and each node on the chain represents a specific version.

[0033] In an alternative embodiment, the first node may, but is not limited to, be a node on the version chain and may be used, but is not limited to, for representing the target server of the first version.

[0034] Step S206: When the target server is updated, obtain the update information of the target server.

[0035] In an alternative embodiment, the update information may, but is not limited to, be understood as the specific changes after the server is updated.

[0036] Step S208: Configure the second node in the version chain based on the update information, where the second node is used to represent the target server of the second version, the second version is obtained based on the update information, and the first node is the parent node of the second node.

[0037] In an alternative embodiment, the second node may, but is not limited to, be a node on the version chain and may, but is not limited to, be a child node of the first node for indicating the inheritance relationship between versions.

[0038] In an alternative embodiment, obtaining the basic information of the target server may, but is not limited to, be completed by reading the firmware or software metadata of the server. For example, information such as the model, manufacturer, and platform can be obtained through the baseboard management controller.

[0039] In an alternative embodiment, configuring the first node in the version chain based on the basic information creates the first node of the version chain according to the obtained basic information. This is usually an initial version node that contains the basic features and function implementations of the server, such as the model, platform, project, etc., as well as the corresponding management software function implementation methods.

[0040] In an alternative embodiment, when an update occurs on the target server, update information of the target server is obtained. This process can be understood, but is not limited to, that the update information of the server can be obtained by monitoring the version numbers of firmware and software, log files, or directly invoking the management interface of the server. The obtained update information can be used to determine whether the server requires a version update and function adaptation.

[0041] In an alternative embodiment, based on the update information, the second node in the version chain is configured. This process can be understood, but is not limited to, that when the server is updated, according to the update information, a second node is added to the version chain to represent the updated server version. This node not only contains the features of the new version, such as new functions, interface changes, etc., but also inherits the attributes of the first node, forming a continuation between versions.

[0042] It should be noted that the embodiments of the present application provide an efficient and systematic method for managing and identifying different versions and customized branches of a server. In a scenario where server management software is compatible with multiple servers, by constructing a version chain, each node not only records the version information of the target server but also includes a description of the differences between versions, such as function changes, interface changes, hardware configuration adjustments, etc. In addition, the relationship between nodes clearly represents the iteration path of the version, facilitating the quick identification and positioning of the specific version features of the server. Thus, when a new server is adapted or a version is updated, targeted differential analysis and function implementation selection can be carried out, thereby improving the management efficiency of the server.

[0043] Through the above steps, first, the basic information of the target server is obtained, and based on this information, the first node in the version chain is configured, which can accurately represent the initial version and features of the target server. When an update occurs on the server, the update information is further obtained, and based on this information, the second node is configured in the version chain to represent the updated version. And as a child node of the first node, the second node not only records the features and changes of the new version but also maintains the continuity and difference records between versions, which can clearly display the evolution history of the server version and can quickly locate the differences in function implementation by traversing the version chain during the adaptation process of the new version, improving the management efficiency of server information. Since the differences in function implementation can be quickly located by traversing the version chain during the adaptation process of the new version, the problem of low management efficiency of server information can be solved, thereby achieving the technical purpose of making full use of the multi-core processor and parallel computing capabilities of the server, and further achieving the technical effect of improving the management efficiency of server information.

[0044] Among them, the execution subject of the above steps can be a server, a terminal, etc., but is not limited thereto.

[0045] As an alternative solution, in the case where the basic information includes information about the first function of the target server, during the process of configuring the first node in the version chain based on the basic information, the method further includes:

[0046] S1-1, configure a first verification function for the first node, where the first verification function is used to verify the first function;

[0047] In the case where the update information includes information about the newly added second function of the target server, during the process of configuring the second node in the version chain based on the update information, the method further includes:

[0048] S1-2, configure a second verification function for the second node, where the second verification function is used to verify the second function.

[0049] In an alternative embodiment, the first function and the second function may but are not limited to refer to the functions included in a specific version of the server.

[0050] For further illustration, the first function may be a function determined based on the basic information of the target server, and the second function may be a function newly added or changed based on the server update information.

[0051] In an alternative embodiment, the first verification function and the second verification function may but are not limited to be understood as functions used to verify whether a specific function can be reused in the server management software. Each verification function corresponds to a function and is designed according to the implementation differences of the function in different versions or models, so that during the adaptation process of a new model or version, it can quickly determine whether the function is applicable.

[0052] As an alternative solution, configuring the first verification function for the first node, where the first verification function is used to verify the first function, this process may but is not limited to be understood as when creating the initial node of the version chain, in addition to recording the basic information, it is also necessary to define a verification function for subsequent verification in the management software whether the function can be reused.

[0053] As an alternative solution, configuring the second verification function for the second node, where the second verification function is used to verify the second function, this process may but is not limited to be understood as that with the update of the server version, in addition to recording the changes in the version information and the feature set, a verification function should also be configured for the nodes of the new version, which will help the management software quickly determine whether the function can be directly reused or additional development work is required through the verification function when adapting to a new model or version.

[0054] It should be noted that the design of the verification function is based on the specific implementation of the server functions and can accurately reflect the differences in functions among different versions or models. For the first function included in the basic information, the first verification function can ensure that the compatibility and applicability of the function are verified during the initial configuration stage of the server management software. When the server is updated and a second function is added, the second verification function can ensure that the management software can quickly identify and adapt to the new function, avoiding unnecessary testing and development work, and thus improving the management efficiency of the server.

[0055] Through the embodiments of the present application, a first verification function is configured for the first node, where the first verification function is used to verify the first function; a second verification function is configured for the second node, where the second verification function is used to verify the second function. By configuring the verification function for the node, the technical purpose of avoiding unnecessary testing and development work is achieved, and thus the technical effect of improving the management efficiency of the server is realized.

[0056] As an optional solution, after configuring the second node in the version chain based on the update information, the method further includes:

[0057] S2-1, when obtaining the customized version that the target server needs to be compatible with, obtaining the version basic information corresponding to the customized version;

[0058] S2-2, using the first verification function to verify the version basic information to obtain a first verification result, where the first verification result is used to verify the matching degree between the function corresponding to the version basic information and the first function;

[0059] S2-3, when the first verification result indicates that the verification fails, determining that the customized version is incompatible with the version chain;

[0060] S2-4, when the first verification result indicates that the verification passes, using the second verification function to verify the version basic information to obtain a second verification result, where the second verification result is used to verify the matching degree between the function corresponding to the version basic information and the second function;

[0061] S2-5, when the second verification result indicates that the verification fails, configuring a third node in the version chain based on the version basic information, where the third node is used to represent the target server of the customized version, and the first node is the parent node of the third node;

[0062] S2-6, when the second verification result indicates that the verification passes, configuring a fourth node in the version chain based on the version basic information, where the fourth node is used to represent the target server of the customized version, and the second node is the parent node of the fourth node.

[0063] As an alternative, the customized version can, but is not limited to, be a hardware or software customization based on the basic server model according to the specific customer or project requirements, forming a server version with differentiated features.

[0064] In an alternative embodiment, the version basic information can, but is not limited to, include information such as the model, manufacturer, platform, project, and hardware configuration of the customized version server, which is used to identify the specific features of the customized version.

[0065] In an alternative embodiment, the third node and the fourth node can, but are not limited to, be understood as newly added nodes in the version chain, which are used to represent the customized version of the server. According to the verification result, a parent-child node relationship is formed with the existing nodes. Among them, the first node is the parent node of the third node, and the second node is the parent node of the fourth node.

[0066] In an alternative embodiment, the first verification result can, but is not limited to, be the result after the execution of the first verification function. Passing the verification indicates that the customized version is compatible with the version chain. Failing the verification indicates that the customized version is not compatible with the version chain, and it is necessary to determine that the customized version requires new function implementation instead of reusing the functions on the existing version chain.

[0067] In an alternative embodiment, the second verification result can, but is not limited to, be the result after the execution of the second verification function. Passing the verification indicates that the customized version is fully compatible with the existing functions. Then, a fourth node is created based on the second node in the version chain, which indicates that the customized version can fully reuse the existing functions without additional development work, improving the code reuse rate and management efficiency, and then the fourth node is created. If the verification fails, that is, there are differences between the customized version and the existing functions, then a third node is created in the version chain to represent the server of the customized version, and this node directly inherits from the node that passes the first function verification, indicating that it has basic compatibility with the initial version of the server management software but is different in subsequent functions.

[0068] It should be noted that by using the first verification function and the second verification function, the basic information of the customized version can be tested at multiple levels to determine its matching degree with the existing functions, so as to decide whether to directly reuse the functions, whether new function implementation is required, or only fine-tuning on the basis of the existing functions is needed, avoiding blind development and a large number of repeated tests when compatible with the customized version server, and significantly improving the management efficiency of the server.

[0069] Through the embodiments of the present application, when obtaining the customized version that the target server needs to be compatible with, obtain the version basic information corresponding to the customized version; use the first verification function to verify the version basic information to obtain a first verification result, where the first verification result is used to verify the matching degree between the function corresponding to the version basic information and the first function; when the first verification result indicates that the verification fails, determine that the customized version is incompatible with the version chain; when the first verification result indicates that the verification passes, use the second verification function to verify the version basic information to obtain a second verification result, where the second verification result is used to verify the matching degree between the function corresponding to the version basic information and the second function; when the second verification result indicates that the verification fails, configure a third node in the version chain based on the version basic information, where the third node is used to represent the target server of the customized version, and the first node is the parent node of the third node; when the second verification result indicates that the verification passes, configure a fourth node in the version chain based on the version basic information, where the fourth node is used to represent the target server of the customized version, and the second node is the parent node of the fourth node. By using the first verification function and the second verification function to verify the customized server, the technical purpose of avoiding blind development and a large number of repeated tests when compatible with the customized version server is achieved, and further the technical effect of improving the management efficiency of the server is realized.

[0070] As an optional solution, before configuring the first node in the version chain based on the basic information, the method further includes:

[0071] S3-1, create a main version line in the version chain based on the hardware configuration in the basic information, where the main version line is associated with the first node and the second node;

[0072] Before configuring the third node in the version chain based on the version basic information, the method further includes:

[0073] S3-2, create a version branch line in the version chain based on the hardware configuration in the version basic information, where the version branch line is associated with the third node.

[0074] In an optional embodiment, the main version line can be but is not limited to understood as the main line in the version chain, and can be but is not limited to representing the direct iteration path of the server from the basic version to the latest version, covering the version update history of the server without special customization requirements.

[0075] In an optional embodiment, the version branch line can be but is not limited to understood as the line branched out in the version chain, representing the version path of the server under specific hardware configurations or customization requirements, reflecting the functional changes and differences in function implementation of the server under different environments or requirements.

[0076] In an optional embodiment, based on the hardware configuration in the basic information, the main version line in the version chain is created. This process can be understood, but is not limited to, that before creating the first node of the server management software version chain, it is first necessary to construct the main version line according to the basic information of the target server, especially the details of the hardware configuration.

[0077] Based on the hardware configuration in the version basic information, the version branch line in the version chain is created. This process can be understood, but is not limited to, that before creating the third node of the customized version server, according to the basic information of the customized version, especially the differences in its specific hardware configuration, the version branch line is created.

[0078] In addition, the version branch line will be directly associated with the third node, reflecting the function implementation and version history of the customized version under specific hardware configurations, forming a contrast with the main version line and showing the customization path.

[0079] It should be noted that the main version line provides a stable basic version iteration path for the server management software, ensuring comprehensive support and efficient management of servers with standard hardware configurations. The introduction of the version branch line, on the other hand, provides a dedicated path for handling server versions under specific hardware configurations or customization requirements, enabling the management software to provide more accurate and personalized function implementations for different environments and requirements, improving the code reusability and system adaptability. Through the construction of the main version line and the version branch line, systematic management of different server versions and customization requirements is achieved, improving the efficiency in server management.

[0080] Through the embodiments of the present application, based on the hardware configuration in the basic information, the main version line in the version chain is created, where the main version line is associated with the first node and the second node; based on the hardware configuration in the version basic information, the version branch line in the version chain is created, where the version branch line is associated with the third node. Through the construction of the main version line and the version branch line, the technical purpose of systematic management of different server versions and customization requirements is achieved, and further the efficiency in server management is improved.

[0081] As an optional solution, in the case where the version chain has been created, the method further includes:

[0082] S4-1, obtaining a first feature set corresponding to the version chain, where the first feature set is used to record the feature information involved in each node in the version chain;

[0083] After configuring the first node in the version chain based on the basic information, the method further includes:

[0084] S4-2, updating the first feature set so that the first feature set records the feature information involved in the first node.

[0085] In an alternative embodiment, the first feature set may, but is not limited to, be understood as a set of nodes in a version chain, and the characteristics of the server version are recorded through a series of attributes and feature information, which may, but is not limited to, be used for the feature information involved in each node in the version chain.

[0086] In an alternative embodiment, the feature information may, but is not limited to, be information used to describe the characteristics of the service version, such as model number, project name, CPU type, function list, interface description, and other information.

[0087] In an alternative embodiment, obtaining the first feature set corresponding to the version chain may, but is not limited to, be understood as that after the version chain is constructed, the system will automatically generate or update a first feature set, which contains the feature information of all nodes in the version chain and is used for the identification and adaptation of subsequent new version servers.

[0088] In an alternative embodiment, updating the first feature set so that the feature information involved in the first node is recorded in the first feature set may, but is not limited to, be understood as that after the first node of the version chain is created, the feature information of the first node needs to be added to the first feature set. This includes information such as the hardware configuration and basic functions of the server, providing a basis for the creation of subsequent nodes and the update of the feature set. By updating the first feature set, it is convenient for the management and compatibility verification of subsequent server versions, so as to improve the efficiency of server management.

[0089] Through the embodiments of the present application, the first feature set corresponding to the version chain is obtained, wherein the first feature set is used to record the feature information involved in each node in the version chain; the first feature set is updated so that the feature information involved in the first node is recorded in the first feature set. By updating the first feature set, the technical purpose of facilitating the management and compatibility verification of subsequent server versions is achieved, and thus the technical effect of improving the efficiency of server management is realized.

[0090] As an alternative solution, when a server to be managed is obtained, the method further includes:

[0091] S5-1, obtaining a second feature set corresponding to the server to be managed;

[0092] S5-2, comparing the first feature set with the second feature set to obtain a comparison result;

[0093] S5-3, when the comparison result indicates that the first feature set and the second feature set meet the similarity condition, managing the server to be managed using the version chain;

[0094] S5-4. When the comparison result indicates that the first feature set and the second feature set do not meet the similarity condition, obtain other version chains except the version chain to manage the server to be managed.

[0095] In an alternative embodiment, the second feature set can be, but is not limited to, understood as a set of feature information representing the server to be managed, including its hardware configuration, function implementation, interface description, etc., which can be, but is not limited to, used for subsequent comparison with the existing first feature set to determine the compatible version chain or customization path of the server to be managed.

[0096] In an alternative embodiment, the similarity condition can be, but is not limited to, understood as a standard used in server version management to determine whether two servers are similar enough to decide whether the existing function implementations in the version chain can be reused.

[0097] In an alternative embodiment, obtaining the second feature set corresponding to the server to be managed can be, but is not limited to, understood as that when a new server is incorporated into the compatible range of the management software, it is first necessary to collect and organize the feature information of the server to form a second feature set for subsequent comparison with the first feature set.

[0098] In an alternative embodiment, comparing the first feature set with the second feature set to obtain a comparison result can be, but is not limited to, understood as that after collecting the second feature set of the server to be managed, the next step is to compare it with the first feature set corresponding to the existing version chain. The comparison result will reflect the degree of difference in features between the two servers and be used to decide whether the existing version chain can be directly used for management.

[0099] In an alternative embodiment, when the comparison result indicates that the first feature set and the second feature set meet the similarity condition, use the version chain to manage the server to be managed. This process can be, but is not limited to, understood as that if the comparison result indicates that the first feature set and the second feature set meet the preset similarity condition, then it can be considered that the server to be managed can directly reuse the function implementations of the existing version chain without additional development, and the server to be managed can be managed using the existing version chain.

[0100] In an alternative embodiment, when the comparison result indicates that the first feature set and the second feature set do not meet the similarity condition, obtain other version chains except the version chain to manage the server to be managed. This process can be, but is not limited to, understood as that if the comparison result shows that the server to be managed has significant differences in features from the servers in the existing version chain and does not meet the similarity condition, then the system will automatically search for other version chains in the database to find a version chain that better matches the features of the server to be managed to improve the efficiency of server management.

[0101] It should be noted that by obtaining the second feature set of the server to be managed and comparing it with the existing first feature set, it is possible to accurately determine whether the server to be managed can directly reuse the function implementation in the existing version chain or needs to find a more matching version chain. This not only reduces the workload of compatibility analysis and function adaptation, improves the management efficiency, but also enables flexible adoption of the most suitable version chain for management according to the diversity of the server environment when performing server management.

[0102] Through the embodiments of the present application, obtain the second feature set corresponding to the server to be managed; compare the first feature set with the second feature set to obtain a comparison result; when the comparison result indicates that the first feature set and the second feature set meet the similarity condition, manage the server to be managed using the version chain; when the comparison result indicates that the first feature set and the second feature set do not meet the similarity condition, obtain other version chains except the version chain to manage the server to be managed. By obtaining the second feature set of the server to be managed and comparing it with the existing first feature set, the technical purpose of accurately determining whether the server to be managed can directly reuse the function implementation in the existing version chain or needs to find a more matching version chain is achieved, and thus the technical effect of improving the server management efficiency is realized.

[0103] As an optional solution, in the process of configuring the first node in the version chain based on the basic information, the method further includes:

[0104] Assign corresponding weights to at least one piece of attribute information involved in the first node, where the weight is used to represent the importance of the attribute information to the target server.

[0105] In an optional embodiment, the attribute information can be, but is not limited to, various features with distinctiveness and descriptiveness in the server version, including but not limited to hardware configurations (such as processor type, memory size), software environments (such as operating system version, firmware type), functional modules (such as remote management, performance monitoring), etc., and can be used to construct, but is not limited to, the feature set of the server.

[0106] In an optional embodiment, the process of assigning corresponding weights to at least one piece of attribute information involved in the first node can be understood, but is not limited to, that when creating the first node of the server version chain, the collected and sorted attribute information is assigned weights, and the setting of the weights reflects the importance of these attributes in server management and compatibility judgment.

[0107] It should be noted that by assigning weights to the attribute information of the first node, a more accurate feature set can be constructed when performing server management, thereby improving the efficiency of server management.

[0108] In the embodiments of the present application, corresponding weights are respectively assigned to at least one piece of attribute information related to the first node, where the weights are used to represent the importance of the attribute information to the target server. By assigning weights to the attribute information of the first node, the technical purpose of being able to construct a more accurate feature set during server management is achieved, and thus the technical effect of improving the efficiency of server management is realized.

[0109] As an alternative solution, for the convenience of understanding, the above server information management method is applied to the scenario of server management using server management software.

[0110] In an alternative embodiment, the servers are classified by the basic attributes of the servers, such as hardware configuration information such as model, manufacturer, platform, project, etc., and combined with the model to form a new server model A. These attributes become the initial feature set of model A. The feature set has a feature weight vector representing the weight of the feature, which is initially 1. During the growth of the tree, the feature set and the weight vector of model A will be updated.

[0111] It should be noted that as the general server iterates with the main version, its functions will change and the interfaces will also change. The management software needs to be compatible according to the changes in the main version. When the version is updated and the functions of the management software change, a node is formed, which includes: version number, release time, verification method, and modified interfaces.

[0112] For further illustration by way of example, optionally Figure 3 As shown, there are version 1.1 and version 1.3 under the main version of model A. Among them, the creation date of version 1.1 is October 15, and there are n functions. Each function has a verification method and an implementation interface, that is, functions 1 to n modified in version 1.1, representing the functions of the management software. Each function includes a verification method and the corresponding affected implementation interface. The creation date of version 1.3 is November 15, and there is function 1, which has a verification method and an implementation interface.

[0113] In an alternative embodiment, as the version is updated, a version chain will be generated for compatible servers. As the version increases, the length of the chain increases. Through this chain, the implementation changes of the management software caused by version changes can be analyzed. As the chain increases, the features involved in the chain nodes are updated. The initial feature set plus the features of each node are combined into the feature set PA of this version chain.

[0114] When it is necessary to be compatible with the customized version of server A or other models, it is judged by traversing the version chain of A. If the verification methods of all version nodes of A pass the verification, continue to verify the next node until the verification fails or there is no next node. If the verification of the customized version passes, it means that the customized version can directly reuse the main version of A for management, and the customized version can also be classified into the main version of A without distinction. At this time, by comparing the characteristics of the two servers, the overlapping characteristics are retained. If the node fails to pass the verification, it means that the customized version generates a new branch on the parent node of this node. Test the customized version, test all management functions, and generate a new node. This node also includes the version number, release time, verification method, and modified interface.

[0115] To further illustrate with an example, finally, according to this method, a tree structure such as Figure 4 can be generated. Under the main version of model A, there are versions 1.1, 1.3, 1.6, and 1.9. Among them, in version 1.3, there is branch b of model A. In branch b of model A, there are hardware configurations 1 and 2, and under branch b of model A, there are also versions 2.1 and 2.3. Under version 1.6, there is branch c of model A. In branch c of model A, there are hardware configurations 3 and attribute 4, and branch c of model A also has version 3.1.

[0116] It should be noted that if the customized version requires a new branch, in addition to generating nodes and version chains, it is also necessary to judge the differences between branch b and the main version, including model, manufacturer, platform, project, and other hardware configurations. That is, through the changes in this configuration, branch b of the model can be distinguished from the main version. Generate a set of attribute characteristics.

[0117] Furthermore, using the same method, branch c can be further expanded, and finally a feature set PA = {P1, P2,..., Pn} of model A, as well as attribute sets PA1 and PA2 of each branch can be generated. Among them, P1 in PA may be that the number of CPUs of the model is 2, and the corresponding branch attribute may be 2 or 4 or others. The corresponding feature set is paired with a feature weight vector. At this time, a branch tree of model A and the version chain corresponding to each node on the tree are generated.

[0118] Finally, when managing a new version of a compatible model, if it is found that a certain command reports an error and cannot be adapted to this model, then adaptation is required. By comparing the attribute vectors of this model with those of other models, if a certain model is more similar to it, then traverse its version chain to judge whether there is a node for the error reporting function. If there is, verify it through the verification method. If the verification is successful, use the implementation method of this function; otherwise, continue to traverse the version chain. If this chain does not have an implementation, then look for the next chain.

[0119] In an alternative embodiment, when managing compatibility for a new model, the characteristic set attributes between models are compared to determine similar models, and then their version chains are traversed.

[0120] In an alternative embodiment, the compatibility of the model is tested according to the corresponding version. If it can be managed, the model is classified into model A. If there are differences in implementation, it can be processed according to the branch.

[0121] In an alternative embodiment, before initial compatibility of model A, a version chain of A needs to be created:

[0122] (1) Record the configuration information of model A, including information such as platform, manufacturer, project, CPU type, etc., and summarize it as the main version of model A. These attributes are the characteristic set PA of A, and the characteristic weight vector WA. Each value of the initial WA is 1.

[0123] (2) When the server management tool manages server A, it first performs compatibility adaptation on the server to form the initial version and the initial function implementation;

[0124] (3) If the server version is updated, check whether all tool functions are satisfied. If satisfied, no update is required. If a certain function a reports an error or exception, this function needs to be developed for this version. At the same time, add a chain node, which includes the release time and version number of this version, function a, verification method, and implementation method. In addition, if new attributes are added to the new version node, modify the characteristic set of A and add the corresponding attribute values of the node.

[0125] (3) The verification method is the flag bit for the change of this function interface. It may be a modification of a certain hardware configuration or a change in the return field of another interface. Through this method, it can be determined whether to use this implementation method.

[0126] (4) As the version increases, the version chain gradually increases. At this time, the version chain of model A, the characteristic set PA, and the characteristic weight vector WA are completed.

[0127] In an alternative embodiment, if there is compatibility for a certain branch B of model A, then:

[0128] (1) For the customized version B of A, it is necessary to confirm from which node on the version chain of A to start branch modification at this time.

[0129] (2) Start verification from the root node of A, and judge whether it is satisfied through the verification function of each node. If node 1 is satisfied, then search for the next node 2 along the linked list until a certain node n fails the verification.

[0130] (3) If the node n fails the verification, it can be considered that B branches from the node n - 1, and the initial node of B is the node n - 1.

[0131] (4) After determining the initial node, start the full - scale test for B.

[0132] (5) If all functions pass the test, then B directly re - uses the node n - 1. Since B cannot continue to be compatible along the version chain of A, a version chain for B (with only one node) needs to be created.

[0133] (6) If the function x of the B node reports an error, it means that the current node n - 1 cannot meet the requirements of B and functions need to be developed. For the function x, in order to increase code re - use, check whether there is a ready - made implementation method in other branches. Therefore, it is necessary to traverse the entire tree to check whether there is a node that is compatible with the function x.

[0134] (7) If the function of a certain node is also applicable to the branch B, the corresponding feature weight of that node is increased by 10%, indicating the universality of the feature.

[0135] (8) After completing the compatibility of the customized version B of A, B also has its own version chain and feature set.

[0136] In an alternative embodiment, if it is necessary to be compatible with another server C, first, it is necessary to determine which current version chain has a higher similarity with C. The calculation method is as follows, where α i is whether the attributes of the model to be compatible and the model corresponding to the branch are the same. If they are the same, it is 1; if they are different, it is 0. ri is its weight, and the calculated r is the similarity between the server and the branch:

[0137]

[0138] Then, according to the similarity, sort each branch. The higher the similarity, the greater the probability of function re - use. According to the sorting, select the version chain with the highest similarity for comparison, and the comparison method can be processed similarly to the branches in Example 2.

[0139] Finally, if the final model C can be classified as a branch of the model A, the corresponding feature weights of the same features between A and C are increased, and the features that are different between A and C are deleted from A and used as the features of the nodes of C.

[0140] In addition, when managing the server, if a function reports an error, a preliminary screening can be performed by traversing the tree, so as to quickly locate the function implementation method that may have an error.

[0141] Through the embodiments of the present application, the similarity relationship between servers can be obtained more clearly; in addition, the version control management of multi - branch servers can be performed. The connection between each server is clearer, and the same - code re - use rate is higher.

[0142] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of various embodiments of the present application.

[0143] In this embodiment, a management device for server information is also provided. This device is used to implement the above embodiments and preferred implementation methods, and those that have been described will not be repeated. As used hereinafter, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0144] Figure 5 is a structural block diagram of a management device for server information according to an embodiment of the present application, as Figure 5 shown, the device includes:

[0145] A first acquisition unit 502, configured to acquire basic information of a target server;

[0146] A first configuration unit 504, configured to configure a first node in a version chain based on the basic information, where the first node is used to represent the target server of the first version, and the first version is obtained based on the basic information;

[0147] A second acquisition unit 506, configured to acquire update information of the target server when the target server is updated;

[0148] A second configuration unit 508, configured to configure a second node in the version chain based on the update information, where the second node is used to represent the target server of the second version, the second version is obtained based on the update information, and the first node is the parent node of the second node.

[0149] For specific embodiments, reference can be made to the examples shown in the above management method of server information, and details will not be repeated here.

[0150] As an alternative, the first configuration unit 504 includes: a first configuration module, configured to configure a first verification function for the first node when the basic information includes information about the first function of the target server, where the first verification function is used to verify the first function; a second configuration unit 508 includes: a second configuration module, configured to configure a second verification function for the second node when the update information includes information about the newly added second function of the target server, where the second verification function is used to verify the second function.

[0151] For specific embodiments, reference may be made to the examples shown in the above server information management method, and details are not described herein again in this example.

[0152] As an alternative, the second configuration unit 508 includes: an acquisition module, configured to acquire version basic information corresponding to a customized version when the customized version that the target server needs to be compatible with is acquired; a first verification module, configured to use the first verification function to verify the version basic information to obtain a first verification result, where the first verification result is used to verify the matching degree between the function corresponding to the version basic information and the first function; a determination module, configured to determine that the customized version is incompatible with the version chain when the first verification result indicates that the verification fails; a second verification module, configured to use the second verification function to verify the version basic information to obtain a second verification result when the first verification result indicates that the verification passes, where the second verification result is used to verify the matching degree between the function corresponding to the version basic information and the second function; a third configuration module, configured to configure a third node in the version chain based on the version basic information when the second verification result indicates that the verification fails, where the third node is used to represent the target server of the customized version, and the first node is the parent node of the third node; a fourth configuration module, configured to configure a fourth node in the version chain based on the version basic information when the second verification result indicates that the verification passes, where the fourth node is used to represent the target server of the customized version, and the second node is the parent node of the fourth node.

[0153] For specific embodiments, reference may be made to the examples shown in the above server information management method, and details are not described herein again in this example.

[0154] As an alternative, the first configuration unit 504 includes: a first creation module, configured to create a main version line in the version chain based on the hardware configuration in the basic information before configuring the first node in the version chain based on the basic information, where the main version line is associated with the first node and the second node; a second creation module, configured to create a version branch line in the version chain based on the hardware configuration in the version basic information before configuring the third node in the version chain based on the version basic information, where the version branch line is associated with the third node.

[0155] For specific embodiments, reference may be made to the examples shown in the above-mentioned method for managing server information, and details thereof will not be elaborated herein.

[0156] As an alternative solution, the apparatus further includes: a third acquisition unit, configured to acquire a first feature set corresponding to the version chain when the version chain has been created, where the first feature set is used to record the feature information involved in each node in the version chain; and an update unit, configured to update the first feature set after configuring the first node in the version chain based on the basic information, so that the first feature set records the feature information involved in the first node.

[0157] For specific embodiments, reference may be made to the examples shown in the above-mentioned method for managing server information, and details thereof will not be elaborated herein.

[0158] As an alternative solution, the apparatus further includes: a fourth acquisition unit, configured to acquire a second feature set corresponding to the server to be managed; a comparison unit, configured to compare the first feature set with the second feature set to obtain a comparison result; a management unit, configured to manage the server to be managed by using the version chain when the comparison result indicates that the first feature set and the second feature set meet the similarity condition; and a fifth acquisition unit, configured to acquire other version chains except the version chain to manage the server to be managed when the comparison result indicates that the first feature set and the second feature set do not meet the similarity condition.

[0159] For specific embodiments, reference may be made to the examples shown in the above-mentioned method for managing server information, and details thereof will not be elaborated herein.

[0160] As an alternative solution, the first configuration unit 504 includes: an allocation unit, configured to allocate corresponding weights to at least one piece of attribute information involved in the first node, where the weight is used to indicate the importance of the attribute information to the target server.

[0161] For specific embodiments, reference may be made to the examples shown in the above-mentioned method for managing server information, and details thereof will not be elaborated herein.

[0162] It should be noted that the above-mentioned various virtual devices (modules, units, sub-modules, sub-units, components, etc.) can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited thereto: the above-mentioned virtual devices are all located in the same processor; or, the above-mentioned various virtual devices are respectively located in different processors in any combination form.

[0163] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0164] In an exemplary embodiment, the above-mentioned computer-readable storage medium may include, but is not limited to: various media such as USB flash drives, read-only memory (ROM for short), random access memory (RAM for short), external hard drives, magnetic disks, or optical discs that can store computer programs.

[0165] An embodiment of the present application further provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0166] In an exemplary embodiment, the above-mentioned electronic device may further include a transmission device and an input / output device. Among them, the transmission device is connected to the above-mentioned processor, and the input / output device is connected to the above-mentioned processor.

[0167] Specific examples in this embodiment may refer to the examples described in the above embodiments and exemplary embodiments, and will not be repeated here.

[0168] Obviously, those skilled in the art should understand that the above-mentioned virtual devices or steps of the present application can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. They can be implemented by program codes executable by the computing device. Thus, they can be stored in a storage device and executed by the computing device. And in some cases, the steps shown or described can be executed in a different order than here, or they can be separately made into individual integrated circuit modules, or multiple modules or steps among them can be made into a single integrated circuit module to implement. In this way, the present application is not limited to any specific combination of hardware and software.

[0169] The above are only the preferred embodiments of the present application and are not used to limit the present application. For those skilled in the art, the present application can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for managing server information, characterized in that: include: Get the basic information of the target server; Based on the basic information, configure a first node in the version chain, wherein the first node is used to represent a target server of a first version, and the first version is obtained based on the basic information; When the target server is updated, obtaining update information of the target server; Based on the update information, a second node in the version chain is configured, wherein the second node is used to represent a target server of a second version, the second version is obtained based on the update information, and the first node is a parent node of the second node.

2. The method according to claim 1, characterized in that In a case where the basic information includes information about a first function of the target server, in the process of configuring a first node in the version chain based on the basic information, the method further includes: configuring a first verification function for the first node, wherein the first verification function is used to verify the first function; In a case where the update information includes information about a second function newly added by the target server, in the process of configuring a second node in the version chain based on the update information, the method further includes: configuring a second verification function for the second node, wherein the second verification function is used to verify the second function.

3. The method according to claim 2, characterized in that After configuring the second node in the version chain based on the update information, the method further includes: When the customized version that the target server needs to be compatible with is obtained, basic version information corresponding to the customized version is obtained; Using the first verification function, verifying the version basic information to obtain a first verification result, wherein the first verification result is used to verify the matching degree between the function corresponding to the version basic information and the first function; If the first verification result indicates that the verification fails, determining that the customized version is incompatible with the version chain; When the first verification result indicates that the verification is passed, the second verification function is used to verify the version basic information to obtain a second verification result, wherein the second verification result is used to verify the matching degree between the function corresponding to the version basic information and the second function; When the second verification result indicates that the verification fails, configuring a third node in the version chain based on the version basic information, wherein the third node is used to represent the target server of the customized version, and the first node is the parent node of the third node; When the second verification result indicates that the verification is passed, the fourth node in the version chain is configured based on the version basic information, wherein the fourth node is used to represent the target server of the customized version, and the second node is the parent node of the fourth node.

4. The method according to claim 3, characterized in that: Before configuring the first node in the version chain based on the basic information, the method further includes: creating a main version line in the version chain based on the hardware configuration in the basic information, wherein the main version line is associated with the first node and the second node; Before configuring the third node in the version chain based on the version base information, the method further includes: creating a version branch in the version chain based on the hardware configuration in the version base information, wherein the version branch is associated with the third node.

5. The method according to claim 1, characterized in that In the case where the version chain has been created, the method further includes: obtaining a first feature set corresponding to the version chain, wherein the first feature set is used to record feature information related to each node in the version chain; After configuring the first node in the version chain based on the basic information, the method further includes: updating the first feature set so that the first feature set records feature information related to the first node.

6. The method according to claim 5, characterized in that In the case where the server to be managed is obtained, the method further includes: Acquire a second feature set corresponding to the server to be managed; Comparing the first feature set with the second feature set to obtain a comparison result; When the comparison result indicates that the first feature set and the second feature set meet a similarity condition, managing the server to be managed by using the version chain; When the comparison result indicates that the first feature set and the second feature set do not satisfy the similarity condition, other version chains except the version chain are obtained to manage the server to be managed.

7. The method according to any one of claims 1 to 6, characterized in that In the process of configuring the first node in the version chain based on the basic information, the method further includes: A corresponding weight is assigned to each of the at least one attribute information involved in the first node, wherein the weight is used to indicate the importance of the attribute information to the target server.

8. A server information management device, characterized in that: include: A first acquisition unit, used to acquire basic information of a target server; A first configuration unit is configured to configure a first node in the version chain based on the basic information, wherein the first node is used to represent a target server of a first version, and the first version is obtained based on the basic information; A second acquisition unit is used to acquire update information of the target server when the target server is updated; The second configuration unit is used to configure the second node in the version chain based on the update information, wherein the second node is used to represent the target server of the second version, the second version is obtained based on the update information, and the first node is the parent node of the second node.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.

Images