Server life cycle information processing method and related device

Abstract

The invention discloses a server life cycle information processing method and a related device, and relates to the technical field of data processing, and the method comprises the steps: for each process node in a target server life cycle, generating a target server life cycle information record corresponding to the process node, the target server life cycle information record of each flow node is stored, and the target server life cycle information corresponding to each flow node is associated through the source identifier, the data space identifier and the father node identifier, so that the method is simple and efficient; the operation and maintenance personnel can obtain the complete and traceable life cycle information of the target server only based on the source identifier, the data space identifier and the father node identifier in the life cycle information of the target server corresponding to each process node, and by adopting the scheme, the server life cycle information can be simply and efficiently processed; and the integrity of the life cycle information of the server is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a server lifecycle information processing method and related devices. Background Art

[0002] In the infrastructure of large data centers, servers are core resources, so server lifecycle management is particularly necessary. Server lifecycle management (SLM) refers to the planning and execution of all links from server planning, procurement, deployment, operation to final retirement and replacement. In order to manage the server lifecycle, it is necessary to obtain server lifecycle information for storage for subsequent use. Server lifecycle information includes application information (applicant, application purpose, project information, etc.), approval information (approver, approval opinion, etc.), procurement information (supplier, purchase price, maintenance date, configuration information, etc.), financial information (settlement party, purchase price, etc.), application operation and maintenance information, etc.

[0003] At present, in the operation process of companies with large data center infrastructure, the effective operation of servers depends on the close cooperation of multiple systems (such as resource application system, approval system, procurement system, financial system, application operation and maintenance system, etc.). This cross-system operation mode leads to the problem of scattered server life cycle information. In this case, when it is necessary to manage the life cycle of the server, the current mainstream approach is to establish an interface to integrate data across multiple systems to obtain the server life cycle information of each system and store it in the data warehouse for subsequent use. However, this approach is complex and inefficient, and it cannot guarantee the integrity of the server life cycle information.

[0004] Therefore, how to provide a simple and efficient server lifecycle information processing solution and improve the integrity of server lifecycle information has become a technical problem that needs to be urgently solved by technical personnel in this field. Summary of the invention

[0005] In view of the above problems, the present application provides a server lifecycle information processing method and related devices to achieve the purpose of simply and efficiently processing server lifecycle information and improving the integrity of server lifecycle information. The specific scheme is as follows:

[0006] The first aspect of the present application provides a method for processing server lifecycle information, comprising:

[0007] For each process node in the life cycle of the target server, a target server life cycle information record corresponding to the process node is generated; the target server life cycle information record corresponding to the process node includes a source identifier, a data space identifier, a parent node identifier, and the target server life cycle information generated by the process node; the source identifiers in the target server life cycle information records corresponding to different process nodes are the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node;

[0008] The target server lifecycle information record of each of the process nodes is stored.

[0009] In a possible implementation, the source identifier in the target server lifecycle information record corresponding to different process nodes is the same preset link tracking identifier.

[0010] In a possible implementation, the method for generating the preset link tracking identifier includes:

[0011] Before generating the target server lifecycle information record corresponding to each process node in the target server lifecycle, when a relevant resource application of the target server occurs at the starting process node in the target server lifecycle, the preset link tracking identifier is generated according to the name of the starting process node and the relevant resource application time of the target server.

[0012] In a possible implementation, for each process node in the life cycle of the target server, a method for generating a data space identifier of the process node includes:

[0013] Obtain the name and generation time of the target server lifecycle information generated by the process node;

[0014] A data space identifier of the process node is generated according to the name and generation time of the target server lifecycle information generated by the process node.

[0015] In a possible implementation, after generating the preset link tracking identifier, the method further includes:

[0016] A target server lifecycle data link is created, wherein the target service lifecycle data link includes header information and data space; the header information of the target server lifecycle data link includes at least a source identifier; and the source identifier is the preset link tracking identifier.

[0017] In a possible implementation, storing the target server lifecycle information record corresponding to each of the process nodes includes:

[0018] Inject the target server lifecycle information records corresponding to each of the process nodes into the data space of the target server lifecycle data chain to generate target server lifecycle chain data;

[0019] The target server lifecycle link data is stored.

[0020] In a possible implementation, storing the target server lifecycle information record corresponding to each of the process nodes includes:

[0021] The target server lifecycle information records corresponding to each of the process nodes are stored in the corresponding process nodes respectively.

[0022] A second aspect of the present application provides a server lifecycle information processing device, including:

[0023] A record generating unit, for generating, for each process node in the life cycle of a target server, a target server life cycle information record corresponding to the process node; the target server life cycle information record corresponding to the process node includes a source identifier, a data space identifier, a parent node identifier, and the target server life cycle information generated by the process node; the source identifiers in the target server life cycle information records corresponding to different process nodes are the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node;

[0024] The record storage unit is used to store the target server life cycle information record of each process node.

[0025] In a possible implementation, the source identifier in the target server lifecycle information record corresponding to different process nodes is the same preset link tracking identifier.

[0026] In a possible implementation, the device further includes: a preset link tracking identifier generating unit;

[0027] The preset link tracking identifier generation unit is used to generate the preset link tracking identifier according to the name of the starting process node and the relevant resource application time of the target server when a relevant resource application of the target server occurs at the starting process node in the target server life cycle, before generating the target server life cycle information record corresponding to the process node for each process node in the target server life cycle.

[0028] In a possible implementation, the apparatus further includes: a data space identifier generating unit;

[0029] The data space identifier generating unit is used to obtain, for each process node in the target server life cycle, the name and generation time of the target server life cycle information generated by the process node;

[0030] A data space identifier of the process node is generated according to the name and generation time of the target server lifecycle information generated by the process node.

[0031] In a possible implementation, the apparatus further includes: a target server lifecycle data link creation unit;

[0032] The target server lifecycle data link creation unit is used to create a target server lifecycle data link after generating the preset link tracking identifier. The target service lifecycle data link includes header information and data space; the header information of the target server lifecycle data link at least includes a source identifier; the source identifier is the preset link tracking identifier.

[0033] In a possible implementation, the record storage unit is specifically used to:

[0034] Inject the target server lifecycle information records corresponding to each of the process nodes into the data space of the target server lifecycle data chain to generate target server lifecycle chain data;

[0035] The target server lifecycle link data is stored.

[0036] In a possible implementation, the record storage unit is specifically used to:

[0037] The target server lifecycle information records corresponding to each of the process nodes are stored in the corresponding process nodes respectively.

[0038] The third aspect of the present application provides a computer program product, including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the server lifecycle information processing method of the above-mentioned first aspect or any implementation method of the first aspect.

[0039] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0040] The memory is used to store computer programs;

[0041] The processor is used to execute the computer program so that the electronic device can implement the server lifecycle information processing method of the above-mentioned first aspect or any implementation manner of the first aspect.

[0042] A fifth aspect of the present application provides a computer-readable storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the server lifecycle information processing method of the above-mentioned first aspect or any implementation of the first aspect.

[0043] By means of the above technical scheme, the present application provides a server lifecycle information processing method and related devices. For each process node in the lifecycle of the target server, a target server lifecycle information record corresponding to the process node is generated; the target server lifecycle information record corresponding to the process node contains a source identifier, a data space identifier, a parent node identifier, and the target server lifecycle information generated by the process node; the source identifier in the target server lifecycle information record corresponding to different process nodes is the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node; the target server lifecycle information record of each process node is stored. In this scheme, the target server lifecycle information corresponding to each process node is associated through the source identifier, the data space identifier, and the parent node identifier, which is simple and efficient. The operation and maintenance personnel can obtain the complete and traceable lifecycle information of the target server based only on the source identifier, the data space identifier, and the parent node identifier in the target server lifecycle information corresponding to each process node. The adoption of this scheme can achieve the purpose of simply and efficiently processing server lifecycle information and improving the integrity of server lifecycle information. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0045] Figure 1 A flowchart of a method for processing server lifecycle information provided in an embodiment of the present application;

[0046] Figure 2 A schematic diagram of the structure of a server lifecycle information processing device provided in an embodiment of the present application;

[0047] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] The following describes the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. The terms used in the implementation method section of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application.

[0049] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0050] 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 need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0051] In the infrastructure of large data centers, servers are core resources, so server lifecycle management is particularly necessary. Server lifecycle management (SLM) refers to the planning and execution of all links from server planning, procurement, deployment, operation to final retirement and replacement. In order to manage the server lifecycle, it is necessary to obtain server lifecycle information for storage for subsequent use. Server lifecycle information includes application information (applicant, application purpose, project information, etc.), approval information (approver, approval opinion, etc.), procurement information (supplier, purchase price, maintenance date, configuration information, etc.), financial information (settlement party, purchase price, etc.), application operation and maintenance information, etc.

[0052] At present, in the operation process of companies with large data center infrastructure, the effective operation of servers depends on the close cooperation of multiple systems (such as resource application system, approval system, procurement system, financial system, application operation and maintenance system, etc.). This cross-system operation mode leads to the problem of scattered server life cycle information. In this case, when it is necessary to manage the life cycle of the server, the current mainstream approach is to establish an interface to integrate data across multiple systems to obtain the server life cycle information of each system and store it in the data warehouse for subsequent use.

[0053] However, this approach has the following shortcomings: First, data integration across multiple systems requires a lot of preliminary preparation work and a long implementation cycle; second, when servers change frequently, information updates are often not timely. More importantly, before purchasing a server, only server specification configuration information is required, and there is no server serial number information. Currently, the resource application system, approval system, and procurement system do not manage server serial numbers. Therefore, the server life cycle information is largely missing in integrity. When used later, it is impossible to trace the application source, approval information, and procurement information of a server.

[0054] It can be seen that the existing server lifecycle information processing solutions are complex and inefficient, and cannot guarantee the integrity of server lifecycle information.

[0055] In order to solve the above problems, the embodiment of the present application provides a method for processing server lifecycle information. The method for processing server lifecycle information of the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0056] Reference Figure 1 , Figure 1 A flow chart of a method for processing server lifecycle information provided in an embodiment of the present application is shown as follows: Figure 1 As shown, a server lifecycle information processing method provided in an embodiment of the present application may include steps S101 to S102, and these steps are described in detail below.

[0057] S101: for each process node in the life cycle of a target server, generate a target server life cycle information record corresponding to the process node; the target server life cycle information record corresponding to the process node includes a source identifier, a data space identifier, a parent node identifier, and the target server life cycle information generated by the process node; the source identifiers in the target server life cycle information records corresponding to different process nodes are the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node;

[0058] In the present application, the target server may be any type of server, such as a physical server. Physical server types may be classified into computing type, memory type, etc. according to their usage. The present application does not impose any limitation on this.

[0059] For a server, the server lifecycle refers to the entire process from application to decommissioning, which includes various stages of the server, such as planning, procurement, deployment, operation and maintenance, upgrade, and retirement, etc. Different process nodes are responsible for each stage. Therefore, the service lifecycle includes multiple process nodes, such as resource application system, approval system, procurement system, financial system, application operation and maintenance system, etc.

[0060] Each process node in the target server life cycle can generate its corresponding target server life cycle information record, and the generation methods include but are not limited to custom methods, SDK (Software Development Kit) or interface methods. Among them, the custom method refers to the generation according to the agreed generation time and agreed generation rules. For example, for the process node of the resource application system, the timing for generating its corresponding target server life cycle information record can be "when there is a resource application, the resource application system creates a new record", and the agreed rules can be "source identifier, data space identifier, parent node identifier and the specific implementation method of the target server life cycle information generated by the process node". The SDK or interface method refers to encapsulating the generation time and generation rules inside the SDK or interface, and the process node can generate records by directly calling the SDK or interface.

[0061] In this application, the source identifiers in the target server lifecycle information records corresponding to different process nodes are the same. In a possible implementation, the source identifiers in the target server lifecycle information records corresponding to different process nodes are the same preset link tracking identifier. The preset methods of the link tracking identifier can include multiple methods, such as preset fixed values, or setting based on certain rules, etc. This application does not impose any restrictions on this.

[0062] The target server lifecycle information record corresponding to each process node contains a data space identifier, and the data space identifier is used to indicate the target server lifecycle information generated by the process node, such as the name and generation time of the target server lifecycle information generated by the process node. It should be noted that the data space identifier in the target server lifecycle information record corresponding to each process node will be passed to the next process node as the parent node identifier of the next process node when the target server lifecycle process flows, that is, except for the first process node, the parent node identifier in the target server lifecycle information record corresponding to each process node is the data space identifier of the previous process node adjacent to the process node. The parent node identifier of the first process node is empty.

[0063] For ease of understanding, in this application, sourceId represents the source identifier, spaceId represents the data space identifier, and parentId represents the parent node identifier. Based on this, examples of target server lifecycle information records corresponding to several process nodes are provided in the embodiments of this application, as follows:

[0064] Example 1:

[0065] "souceId": "a00e0f6124f163cdbc445acae1bc14e",

[0066] "spaceId": "13fb978b539fd7168985b4fc5eaf99f2",

[0067] "parentId": "",

[0068] "platformInfo": "Resource Application System",

[0069] "creatTime": "2024-06-11 15:30:45",

[0070] "orderId": "DD202410101234",

[0071] "applyConfig": {

[0072] "cpuModle": "intel Silver 4310",

[0073] "memoryModle": "32G*3200MHZ",

[0074] "quantity": 6

[0075] },

[0076] "applyInfo": {

[0077] "applicant": "Zhang San",

[0078] "applicantDepartment": "Technical Center",

[0079] }

[0080] Example 1 indicates that Zhang San from the technical center department applied for 6 physical servers with a CPU model of Intel Silver 4310 and a memory of 32G*3200MHZ in the resource application system at 15:30:45 on June 11, 2024. The application number is DD202410101234.

[0081] Example 2:

[0082] "souceId": "a00e0f6124f163cdbc445acae1bc14e",

[0083] "spaceId": "ca206e9a06784288bcf4617a4aac2ce3",

[0084] "parentId": "13fb978b539fd7168985b4fc5eaf99f2",

[0085] "platformInfo": "Purchase System",

[0086] "creator": "Zhao Wu",

[0087] "creatTime": "2024-06-12 16:40:45",

[0088] "purchaseOrderId": "CG202406121234",

[0089] "purchaseInfo": {

[0090] "cpuModle": "intel Gold 6330",

[0091] "memoryModle": "32G*3200MHZ",

[0092] "quantity": 6

[0093] },

[0094] "comment": "Configuration changed, original request is out of stock.",

[0095] "supplyInfo": {

[0096] "supplier": "Hefei Taoyun Technology Co., Ltd."

[0097] "linkMan": "Li Si"

[0098] }

[0099] Example 2 indicates that Zhao Wu purchased 6 physical servers with CPU model Intel Gold 6330 and memory of 32G*3200MHZ in the procurement system at 16:40:45 on June 12, 2024. The purchase order number is CG202406121234. The supplier is Hefei Taoyun Technology Co., Ltd. and the supplier contact person is Li Si.

[0100] From the above examples 1 and 2, it can be seen that the resource application system and the procurement system share the same sourceId in the target server lifecycle information record, and generate a unique spaceId. The next process node of the resource application system is the procurement system, and the spaceId in its corresponding target server lifecycle information record is used as the parentId in the target server lifecycle information record corresponding to the procurement system, while the resource application system is the starting process node, and the parentId in its corresponding target server lifecycle information record is empty.

[0101] In the above examples, Example 1 and Example 2 are target server lifecycle information records generated by two independent business systems. They are independent events, and the requested server information is inconsistent with the actually purchased server information. It is difficult to realize that the two are related. However, the parentId of Example 2 is the spaceId of Example 1, so the purchased server can be traced back to the requested server information, and it can be known that the original requested model is out of stock and the configuration has been changed.

[0102] It can be seen that in the present application, the target server lifecycle information of each process node is associated through the source identifier, data space identifier and parent node identifier, which is simple and efficient.

[0103] S102: storing target server lifecycle information records corresponding to each of the process nodes.

[0104] In the present application, the target server lifecycle information records corresponding to each of the process nodes can be stored in a dispersed manner in each of the process nodes, or can be stored in a centralized location. In this way, the operation and maintenance personnel can obtain the complete and traceable lifecycle information of the target server based on the source identifier, data space identifier, and parent node identifier in the target server lifecycle information records stored in each of the process nodes.

[0105] This embodiment provides a method for processing server lifecycle information. For each process node in the life cycle of the target server, a target server lifecycle information record corresponding to the process node is generated; the target server lifecycle information record corresponding to the process node contains a source identifier, a data space identifier, a parent node identifier, and the target server lifecycle information generated by the process node; the source identifier in the target server lifecycle information record corresponding to different process nodes is the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node; the target server lifecycle information record of each process node is stored. In this solution, the target server lifecycle information corresponding to each process node is associated through the source identifier, the data space identifier, and the parent node identifier, which is simple and efficient. The operation and maintenance personnel can obtain the complete and traceable lifecycle information of the target server based only on the source identifier, the data space identifier, and the parent node identifier in the target server lifecycle information corresponding to each process node. The use of this solution can achieve the purpose of simply and efficiently processing server lifecycle information and improving the integrity of server lifecycle information.

[0106] In another embodiment of the present application, a method for generating the preset link tracking identifier is introduced. Specifically, the method for generating the preset link tracking identifier includes:

[0107] Before generating the target server lifecycle information record corresponding to each process node in the target server lifecycle, when a relevant resource application of the target server occurs at the starting process node in the target server lifecycle, the preset link tracking identifier is generated according to the name of the starting process node and the relevant resource application time of the target server.

[0108] In a possible implementation, when a target server-related resource application occurs at a starting process node in the target server life cycle, an encrypted value (such as an MD5 value) of a string consisting of the name of the starting process node and the target server-related resource application time can be calculated as the preset link tracking identifier.

[0109] For ease of understanding, assuming that the name of the starting process node is "resource application system" and the relevant resource application time of the target server is "2024-06-10 05:30:17", the corresponding preset link tracking identifier can be "a00e0f6124f163cdbc445acae1bc14e".

[0110] In another embodiment of the present application, a method for generating a data space identifier of the process node is introduced. Specifically, the method for generating a data space identifier of the process node includes:

[0111] The name and generation time of the target server life cycle information generated by the process node are obtained; and a data space identifier of the process node is generated according to the name and generation time of the target server life cycle information generated by the process node.

[0112] In a possible implementation, an encrypted value (such as an MD5 value) of a character string of the name of the target server lifecycle information generated by the process node and the generation time combination may be calculated as a data space identifier of the process node.

[0113] For ease of understanding, assuming that the name of the target server lifecycle information generated by the process node is "resource application information" and the generation time is "2024-06-11 15:30:45", the corresponding data space identifier can be "13fb978b539fd7168985b4fc5eaf99f2".

[0114] In another embodiment of the present application, a specific implementation method for storing target server lifecycle information records corresponding to each of the process nodes is described.

[0115] In a possible implementation, after generating the preset link tracking identifier, a target server lifecycle data link may also be created, wherein the target service lifecycle data link includes header information and data space; the header information of the target server lifecycle data link includes at least a source identifier; and the source identifier is the preset link tracking identifier.

[0116] In a possible implementation, the header information of the target server lifecycle data link further includes creation time, target server type, and header information creation platform.

[0117] For ease of understanding, an example of a target server lifecycle data link is provided in an embodiment of the present application, as follows:

[0118] "creatTime":"2024-06-10 05:30:17",

[0119] "souceId": "a00e0f6124f163cdbc445acae1bc14e",

[0120] "type": "Physical Server",

[0121] "creatInfo": {

[0122] "platformInfo": "Resource Application System"

[0123] }

[0124] "spaceInfo": []

[0125] The example indicates that at 5:30:17 on June 10, 2024, a link with source ID a00e0f6124f163cdbc445acae1bc14e is created in the resource application system, and the asset type is a physical server.

[0126] The target server lifecycle information record storing each of the process nodes includes:

[0127] The target server lifecycle information record of each process node is injected into the data space of the target server lifecycle data chain to generate target server lifecycle chain data; and the target server lifecycle chain data is stored.

[0128] For ease of understanding, an example of target server lifecycle link data is provided in an embodiment of the present application, as follows:

[0129] "creatTime": "2024-06-10 05:30:17",

[0130] "souceId": "a00e0f6124f163cdbc445acae1bc14e",

[0131] "type": "Physical Server",

[0132] "creatInfo": {

[0133] "platformInfo": "Resource Application System"

[0134] },

[0135] "spaceInfo": [

[0136] {

[0137] "spaceId": "13fb978b539fd7168985b4fc5eaf99f2",

[0138] "parentId": "",

[0139] "platformInfo": "Resource Application System",

[0140] "creatTime": "2024-06-11 15:30:45",

[0141] "orderId": "202410101234",

[0142] "applyConfig": {

[0143] "cpuModle": "intel Silver 4310",

[0144] "memoryModle": "32G*3200MHZ",

[0145] "quantity": 6

[0146] },

[0147] "applyInfo": {

[0148] "applicant": "Zhang San",

[0149] "applicantDepartment": "Technical Center"

[0150] }

[0151] },

[0152] {

[0153] "spaceId": "ca206e9a06784288bcf4617a4aac2ce3",

[0154] "parentId": "13fb978b539fd7168985b4fc5eaf99f2",

[0155] "platformInfo": "Purchase System",

[0156] "creator": "Zhao Wu",

[0157] "creatTime": "2024-06-12 16:40:45",

[0158] "purchaseOrderId": "CG202406121234",

[0159] "purchaseInfo": {

[0160] "cpuModle": "intel Gold 6330",

[0161] "memoryModle": "32G*3200MHZ",

[0162] "quantity": 6

[0163] },

[0164] "comment": "Configuration change, out of stock for the original requirement.",

[0165] "supplyInfo": {

[0166] "supplier": "Hefei Taoyun Technology Co., Ltd.",

[0167] "linkMan": "Li Si"

[0168] }

[0169] },

[0170] {

[0171] "spaceId": "086c3d1737fd4d80ab5b34eed9b1bce5",

[0172] "parentId": "ca206e9a06784288bcf4617a4aac2ce3",

[0173] "platformInfo": "Inventory management system",

[0174] "creator": "Wang Liu",

[0175] "creatTime": "2024-07-12 13:40:45",

[0176] "entryOrderId": "RK202407121234",

[0177] "entryInfo":

[0178] {

[0179] "cpuModle": "intel Gold 6330",

[0180] "mermoryModle": "32G*3200MHZ",

[0181] "SN": 9800203208498669

[0182] },

[0183] {

[0184] "cpuModle": "intel Gold 6330",

[0185] "memoryModle": "16G*3200MHZ",

[0186] "SN": 6101437101961066

[0187] }

[0188] ],

[0189] "comment": "2 units in stock"

[0190] } ]

[0192] It can be seen from the above example that the target server lifecycle information records corresponding to each process node are connected in series through the same source identifier to form the target server lifecycle link data.

[0193] The purpose of this implementation is to aggregate the target server lifecycle information records corresponding to each of the process nodes to generate a target server lifecycle data chain, and to persistently store the target server lifecycle data chain for subsequent retrieval and analysis by operation and maintenance personnel. Generally speaking, each process node shares a copy of data, and each process node can directly obtain it from the storage when it needs to be retrieved or updated.

[0194] This implementation method can facilitate each process node to obtain full data.

[0195] In actual operation, it can be combined with a QR code management system or CMDB (Configuration Management Database) system to generate a QR code based on source ID and affix it to the server body. When operation and maintenance personnel perform operation and maintenance management (such as removing and retrieving servers, changing configurations) and query server information, they can scan the QR code and complete the acquisition of data for the entire life cycle of the server without logging into a specific system, which is convenient and fast.

[0196] In another possible implementation, the target server lifecycle information records corresponding to each of the process nodes may be stored in the corresponding process nodes respectively.

[0197] The target server lifecycle information records corresponding to each of the process nodes are stored in the corresponding process nodes respectively. The operation and maintenance personnel can obtain the records of the corresponding process nodes through souceId and spaceId. At this time, there is no need to obtain the full amount of data, so it is more lightweight.

[0198] To summarize, the solution of the present application is to efficiently obtain the full life cycle management information of the server, so that the production data of each server can be traced and quickly queried. By assigning a globally unique link tracking identifier to each type of server in the source process node (generally the resource application system), which serves as a globally unique identifier and is passed to each link along the process, and the information of each link is recorded, a complete data chain can be formed.

[0199] Compared with the existing technology, this application solution does not require cross-system development and docking, and can automatically realize the assembly of full-link data with lightweight access. It is highly scalable and can be easily combined with third-party manufacturers (such as server manufacturers and operation and maintenance management manufacturers), greatly reducing the workload of operation and maintenance. Moreover, compared with the existing technology, the target server life cycle link data generated by this application solution has fast traceability query, convenient update, and high data integrity.

[0200] A server lifecycle information processing method provided in an embodiment of the present application is introduced above, and a device for executing the above server lifecycle information processing method will be introduced below.

[0201] See also Figure 2 , Figure 2 This is a schematic diagram of the structure of a server lifecycle information processing device provided in an embodiment of the present application. Figure 2 As shown, the server lifecycle information processing device includes:

[0202] The record generating unit 11 is used to generate a target server life cycle information record corresponding to each process node in the target server life cycle; the target server life cycle information record corresponding to the process node includes a source identifier, a data space identifier, a parent node identifier, and the target server life cycle information generated by the process node; the source identifiers in the target server life cycle information records corresponding to different process nodes are the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node;

[0203] The record storage unit 12 is used to store the target server lifecycle information record of each process node.

[0204] In a possible implementation, the source identifier in the target server lifecycle information record corresponding to different process nodes is the same preset link tracking identifier.

[0205] In a possible implementation, the device further includes: a preset link tracking identifier generating unit;

[0206] The preset link tracking identifier generation unit is used to generate the preset link tracking identifier according to the name of the starting process node and the relevant resource application time of the target server when a relevant resource application of the target server occurs at the starting process node in the target server life cycle, before generating the target server life cycle information record corresponding to the process node for each process node in the target server life cycle.

[0207] In a possible implementation, the apparatus further includes: a data space identifier generating unit;

[0208] The data space identifier generating unit is used to obtain, for each process node in the target server life cycle, the name and generation time of the target server life cycle information generated by the process node;

[0209] A data space identifier of the process node is generated according to the name and generation time of the target server lifecycle information generated by the process node.

[0210] In a possible implementation, the apparatus further includes: a target server lifecycle data link creation unit;

[0211] The target server lifecycle data link creation unit is used to create a target server lifecycle data link after generating the preset link tracking identifier. The target service lifecycle data link includes header information and data space; the header information of the target server lifecycle data link at least includes a source identifier; the source identifier is the preset link tracking identifier.

[0212] In a possible implementation, the record storage unit is specifically used to:

[0213] Inject the target server lifecycle information records corresponding to each of the process nodes into the data space of the target server lifecycle data chain to generate target server lifecycle chain data;

[0214] The target server lifecycle link data is stored.

[0215] In a possible implementation, the record storage unit is specifically used to:

[0216] The target server lifecycle information records corresponding to each of the process nodes are stored in the corresponding process nodes respectively.

[0217] The present application also provides an electronic device in an embodiment. Figure 3As shown, it shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiment of the present application. The electronic device in the embodiment of the present application may include but is not limited to fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 3 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0218] like Figure 3 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 to a random access memory (RAM) 603. When the electronic device is powered on, various programs and data required for the operation of the electronic device are also stored in the RAM 603. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0219] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a memory card, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 3 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0220] An embodiment of the present application also provides a computer program product including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements any server lifecycle information processing method provided in the embodiment of the present application.

[0221] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When one or more computer programs are executed by an electronic device, the electronic device can implement any server lifecycle information processing method provided in an embodiment of the present application.

[0222] It should also be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

[0223] Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0224] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0225] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a training device, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, training device, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

Claims

1. A method for processing server lifecycle information, characterized in that: include: For each process node in the life cycle of the target server, generate a target server life cycle information record corresponding to the process node; The target server lifecycle information record corresponding to the process node includes a source identifier, a data space identifier, a parent node identifier, and the target server lifecycle information generated by the process node; The source identifiers in the target server lifecycle information records corresponding to different process nodes are the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node; The target server lifecycle information record corresponding to each of the process nodes is stored.

2. The method according to claim 1, characterized in that The source identifier in the target server lifecycle information record corresponding to different process nodes is the same preset link tracking identifier.

3. The method according to claim 2, characterized in that The method for generating the preset link tracking identifier includes: Before generating the target server lifecycle information record corresponding to each process node in the target server lifecycle, when a relevant resource application of the target server occurs at the starting process node in the target server lifecycle, the preset link tracking identifier is generated according to the name of the starting process node and the relevant resource application time of the target server.

4. The method according to claim 1, characterized in that: For each process node in the life cycle of the target server, the method for generating the data space identifier of the process node includes: Obtain the name and generation time of the target server lifecycle information generated by the process node; A data space identifier of the process node is generated according to the name and generation time of the target server lifecycle information generated by the process node.

5. The method according to claim 3, characterized in that: After generating the preset link tracking identifier, the method further includes: A target server lifecycle data link is created, wherein the target service lifecycle data link includes header information and data space; the header information of the target server lifecycle data link includes at least a source identifier; and the source identifier is the preset link tracking identifier.

6. The method according to claim 5, characterized in that The target server lifecycle information record corresponding to each process node is stored, including: Inject the target server lifecycle information records corresponding to each of the process nodes into the data space of the target server lifecycle data chain to generate target server lifecycle chain data; The target server lifecycle link data is stored.

7. The method according to any one of claims 1 to 4, characterized in that The target server lifecycle information record corresponding to each process node is stored, including: The target server lifecycle information records corresponding to each of the process nodes are stored in the corresponding process nodes respectively.

8. A server lifecycle information processing device, characterized in that: include: A record generating unit, for generating, for each process node in the life cycle of the target server, a target server life cycle information record corresponding to the process node; The target server lifecycle information record corresponding to the process node includes a source identifier, a data space identifier, a parent node identifier, and the target server lifecycle information generated by the process node; The source identifiers in the target server lifecycle information records corresponding to different process nodes are the same; the parent node identifier is the data space identifier of the previous process node adjacent to the process node; The record storage unit is used to store the target server life cycle information record of each process node.

9. A computer program product, characterized in that It includes computer-readable instructions, and when the computer-readable instructions are executed on an electronic device, the electronic device implements the server lifecycle information processing method as described in any one of claims 1 to 7.

10. An electronic device, characterized in that: The method comprises at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the server lifecycle information processing method as described in any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that: The storage medium carries one or more computer programs, and when the one or more computer programs are executed by an electronic device, the electronic device can implement the server lifecycle information processing method as described in any one of claims 1 to 7.

Images