CN119988385A - A server life cycle information processing method and related device - Google Patents
A server life cycle information processing method and related device Download PDFInfo
- Publication number
- CN119988385A CN119988385A CN202510209354.5A CN202510209354A CN119988385A CN 119988385 A CN119988385 A CN 119988385A CN 202510209354 A CN202510209354 A CN 202510209354A CN 119988385 A CN119988385 A CN 119988385A
- Authority
- CN
- China
- Prior art keywords
- target server
- life cycle
- identifier
- lifecycle
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Computer And Data Communications (AREA)
Abstract
本申请公开了一种服务器生命周期信息处理方法及相关装置，涉及数据处理技术领域，包括：针对位于目标服务器生命周期的每一流程节点，生成流程节点对应的目标服务器生命周期信息记录，并存储各个流程节点的目标服务器生命周期信息记录，各个流程节点对应的目标服务器生命周期信息之间通过源标识、数据空间标识以及父节点标识进行关联，简单高效，运维人员仅仅基于各个流程节点对应的目标服务器生命周期信息中的源标识、数据空间标识以及父节点标识即可获取目标服务器完整的可追溯的生命周期信息，采用本方案可以实现简单高效的处理服务器生命周期信息，并提升服务器生命周期信息的完整性的目的。
The present application discloses a server lifecycle information processing method and related devices, which relate to the field of data processing technology, including: for each process node in the target server lifecycle, generating a target server lifecycle information record corresponding to the process node, and storing the target server lifecycle information record of each process node, the target server lifecycle information corresponding to each process node is associated through a source identifier, a data space identifier and a 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 only based 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 realize the purpose of simply and efficiently processing the server lifecycle information and improving the integrity of the server lifecycle information.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing life cycle information of a server.
Background
In the infrastructure of large data centers, servers are core resources, and therefore server lifecycle management is particularly necessary. Server lifecycle management (SLM, server Lifecycle Management) refers to the planning and execution of all links from the planning, procurement, deployment, operation of the server to the final retirement and replacement process. In order to manage the server lifecycle, the server lifecycle information needs to be acquired for storage for later use. Server life cycle information such as application information (application party, application purpose, project information, etc.), approval information (approver, approval opinion, etc.), purchase information (supplier, purchase price, maintenance date, configuration information, etc.), financial information (settlement party, purchase price, etc.), application operation and maintenance information, etc.
Currently, in the operation process of companies holding the infrastructure of large data centers, the effective operation of servers depends on close collaboration of multiple systems (such as resource application systems, approval systems, purchasing systems, financial systems, application operation and maintenance systems, etc.), and this operation mode across multiple systems causes the problem of server lifecycle information dispersion. In this case, when lifecycle management needs to be performed on the server, it is currently the mainstream practice to perform data integration across multiple systems by establishing an interface to obtain the lifecycle information of the server of each system, and store the lifecycle information in a data repository in a centralized manner for later use. However, this method is complex and inefficient to operate, and cannot guarantee the integrity of the life cycle information of the server.
Therefore, how to provide a simple and efficient server lifecycle information processing scheme and improve the integrity of the server lifecycle information is a technical problem to be solved by those skilled in the art.
Disclosure of Invention
In view of the above problems, the present application provides a method and related apparatus for processing server lifecycle information, so as to achieve the purposes of simply and efficiently processing the server lifecycle information and improving the integrity of the server lifecycle information. The specific scheme is as follows:
the first aspect of the present application provides a server life cycle information processing method, including:
Generating a target server life cycle information record corresponding to each flow node in the life cycle of the target server, wherein the target server life cycle information record corresponding to the flow node comprises a source identifier, a data space identifier, a father node identifier and target server life cycle information generated by the flow node;
and storing the life cycle information record of the target server of each flow node.
In one possible implementation, the source identifiers in the target server lifecycle information records corresponding to different process nodes are the same preset link tracking identifier.
In one possible implementation, the generating manner of the preset link tracking identifier includes:
And generating the preset link tracking identification according to the name of the initial flow node and the related resource application time of the target server when the related resource application of the target server occurs to the initial flow node in the life cycle of the target server before generating the life cycle information record of the target server corresponding to the flow node for each flow node in the life cycle of the target server.
In one possible implementation, for each process node located in the life cycle of the target server, the generating manner of the data space identifier of the process node includes:
Acquiring the name and the generation time of the life cycle information of the target server generated by the flow node;
and generating a data space identifier of the flow node according to the name and the generation time of the life cycle information of the target server generated by the flow node.
In one possible implementation, after the generating the preset link tracking identifier, the method further includes:
and creating a target server life cycle data chain, wherein the target service life cycle data chain comprises head information and a data space, the head information of the target server life cycle data chain at least comprises a source identifier, and the source identifier is the preset link tracking identifier.
In one possible implementation, the storing the target server life cycle information record corresponding to each flow node includes:
Injecting the target server life cycle information records corresponding to the flow nodes into a data space of a target server life cycle data chain to generate target server life cycle link data;
And storing the life cycle link data of the target server.
In one possible implementation, the storing the target server life cycle information record corresponding to each flow node includes:
And storing the life cycle information records of the target servers corresponding to the flow nodes in the corresponding flow nodes respectively.
A second aspect of the present application provides a server life cycle information processing apparatus including:
The system comprises a record generation unit, a record generation unit and a processing unit, wherein the record generation unit is used for generating a target server life cycle information record corresponding to each flow node in the life cycle of the target server, the target server life cycle information record corresponding to the flow node comprises a source identifier, a data space identifier, a father node identifier and target server life cycle information generated by the flow node, the source identifiers in the target server life cycle information records corresponding to different flow nodes are the same, and the father node identifier is the data space identifier of the last flow node adjacent to the flow node;
and the record storage unit is used for storing the life cycle information records of the target servers of the flow nodes.
In one possible implementation, the source identifiers in the target server lifecycle information records corresponding to different process nodes are the same preset link tracking identifier.
In one possible implementation, the device further comprises a preset link tracking identifier generating unit;
The preset link tracking identifier generating unit is configured to generate, before the target server lifecycle information record corresponding to each process node located in the target server lifecycle is generated, the preset link tracking identifier according to the name of the initial process node and the related resource application time of the target server when the related resource application of the target server occurs at the initial process node located in the target server lifecycle.
In one possible implementation, the apparatus further comprises a data space identification generation unit;
The data space identifier generating unit is used for acquiring the name and the generation time of the life cycle information of the target server generated by each flow node in the life cycle of the target server;
and generating a data space identifier of the flow node according to the name and the generation time of the life cycle information of the target server generated by the flow node.
In one possible implementation, the apparatus further comprises a target server lifecycle data chain creation unit;
The target server life cycle data link creation unit is used for creating a target server life cycle data link after the preset link tracking identification is generated, wherein the target server life cycle data link comprises head information and a data space, the head information of the target server life cycle data link at least comprises a source identification, and the source identification is the preset link tracking identification.
In a possible implementation, the record storage unit is specifically configured to:
Injecting the target server life cycle information records corresponding to the flow nodes into a data space of a target server life cycle data chain to generate target server life cycle link data;
And storing the life cycle link data of the target server.
In a possible implementation, the record storage unit is specifically configured to:
And storing the life cycle information records of the target servers corresponding to the flow nodes in the corresponding flow nodes respectively.
A third aspect of the present application provides a computer program product comprising computer readable instructions which, when run on an electronic device, cause the electronic device to implement the server lifecycle information processing method of the above-described first aspect or any implementation of the first aspect.
A fourth aspect of the application provides an electronic device comprising at least one processor and a memory coupled to the processor, wherein:
the memory is used for storing a computer program;
the processor is configured to execute the computer program to enable the electronic device to implement the server lifecycle information processing method of the first aspect or any implementation manner of the first aspect.
A fifth aspect of the present application provides a computer readable storage medium carrying one or more computer programs which, when executed by an electronic device, enable the electronic device to implement the server lifecycle information processing method of the above first aspect or any implementation manner of the first aspect.
By means of the technical scheme, the server life cycle information processing method and the related device are provided. The method comprises the steps of generating a target server life cycle information record corresponding to a flow node aiming at each flow node in the life cycle of the target server, wherein the target server life cycle information record corresponding to the flow node comprises a source identifier, a data space identifier, a father node identifier and target server life cycle information generated by the flow node, the source identifiers in the target server life cycle information records corresponding to different flow nodes are identical, the father node identifier is the data space identifier of the last flow node adjacent to the flow node, and the target server life cycle information record of each flow node is stored. In the scheme, 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 operation and maintenance personnel can acquire the complete 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 target server life cycle information corresponding to each flow node. By adopting the scheme, the purposes of simply and efficiently processing the service life information of the server and improving the integrity of the service life information of the server can be realized.
Drawings
The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.
Fig. 1 is a schematic flow chart of a server life cycle information processing method according to an embodiment of the present application;
Fig. 2 is a schematic structural diagram of a server life cycle information processing device according to an embodiment of the present application;
Fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. The terminology used in the description of the embodiments of the application herein is for the purpose of describing particular embodiments of the application only and is not intended to be limiting of the application.
Embodiments of the present application are described below with reference to the accompanying drawings. As one of ordinary skill in the art can know, with the development of technology and the appearance of new scenes, the technical scheme provided by the embodiment of the application is also applicable to similar technical problems.
The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and are merely illustrative of the manner in which embodiments of the application have been described in connection with the description of the objects having the same attributes. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
In the infrastructure of large data centers, servers are core resources, and therefore server lifecycle management is particularly necessary. Server lifecycle management (SLM, server Lifecycle Management) refers to the planning and execution of all links from the planning, procurement, deployment, operation of the server to the final retirement and replacement process. In order to manage the server lifecycle, the server lifecycle information needs to be acquired for storage for later use. Server life cycle information such as application information (application party, application purpose, project information, etc.), approval information (approver, approval opinion, etc.), purchase information (supplier, purchase price, maintenance date, configuration information, etc.), financial information (settlement party, purchase price, etc.), application operation and maintenance information, etc.
Currently, in the operation process of companies holding the infrastructure of large data centers, the effective operation of servers depends on close collaboration of multiple systems (such as resource application systems, approval systems, purchasing systems, financial systems, application operation and maintenance systems, etc.), and this operation mode across multiple systems causes the problem of server lifecycle information dispersion. In this case, when lifecycle management needs to be performed on the server, it is currently the mainstream practice to perform data integration across multiple systems by establishing an interface to obtain the lifecycle information of the server of each system, and store the lifecycle information in a data repository in a centralized manner for later use.
However, this approach has the disadvantages that, firstly, data integration across multiple systems requires a large amount of preliminary preparation work, the implementation period is long, and secondly, when the server is changed frequently, information update is often not timely. More importantly, only server specification configuration information is needed before server purchase, no server serial number information exists, and the current resource application system, the approval system and the purchase system do not manage the server serial number, so that the service life cycle information of the server is greatly lost in integrity, and the application source, approval information and purchase information of a certain server cannot be traced back when the server is used later.
Therefore, the existing server life cycle information processing scheme is complex in operation and low in efficiency, and the integrity of the server life cycle information cannot be guaranteed.
In order to solve the above problems, the embodiment of the application provides a server life cycle information processing method. The following describes a server life cycle information processing method according to an embodiment of the present application in detail with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a flowchart of a server life cycle information processing method according to an embodiment of the present application, and as shown in fig. 1, the server life cycle information processing method according to an embodiment of the present application may include steps S101 to S102, and the steps are described in detail below.
S101, generating a target server life cycle information record corresponding to each flow node in a target server life cycle, wherein the target server life cycle information record corresponding to the flow node comprises a source identifier, a data space identifier, a father node identifier and target server life cycle information generated by the flow node;
In the present application, the target server may be any type of server, for example, a physical server, and the types of physical servers may be classified into a computing type, a memory type, and the like according to the use purpose, and the present application is not limited in any way.
For a server, the service life cycle refers to the whole process from the start of application to the end of deactivation of the server, and includes various stages of the server, such as planning, purchasing, deploying, operating and maintaining, upgrading, retirement and the like, wherein each stage is responsible for different process nodes. Thus, the service lifecycle includes a plurality of process nodes, such as resource application systems, approval systems, purchasing systems, financial systems, application operation and maintenance systems, and the like.
Each process node in the target server lifecycle may generate a corresponding target server lifecycle information record, where the generation method includes, but is not limited to, a custom method, an SDK (Software Development Kit, a software development kit), or an interface method. The custom mode refers to generation according to the contracted generation time and the contracted generation rule. For example, the process node of the resource application system may generate the corresponding target server life cycle information record at the time of resource application, the resource application system creates a new record, and the agreed rule may be "specific implementation manner of source identifier, data space identifier, father node identifier and the target server life cycle information generated by the process node". The SDK or interface mode refers to that generating time and generating rules are packaged in the SDK or interface, and the flow node directly calls the SDK or interface to generate records.
In the application, the source identifiers in the life cycle information records of the target servers corresponding to different flow nodes are the same, and in one possible implementation, the source identifiers in the life cycle information records of the target servers corresponding to different flow nodes are the same preset link tracking identifier. The preset manner of the link tracking identifier may include various manners, such as preset fixed values, or setting based on a certain rule, which is not limited in any way.
The target server life cycle information record corresponding to each flow node comprises a data space identifier, wherein the data space identifier is used for indicating the target server life cycle information generated by the flow node, such as the name and the generation time of the target server life cycle information generated by the flow node. It should be noted that, when the target server lifecycle flows, the data space identifier in the target server lifecycle information record corresponding to each flow node is transferred to the next flow node as the parent node identifier of the next flow node, that is, except the first flow node, the parent node identifier in the target server lifecycle information record corresponding to each flow node is the data space identifier of the last flow node adjacent to the flow node. The parent node of the first flow node is identified as null.
For easy understanding, in the present application, a source identifier is represented by souceId, a data space identifier is represented by spaceId, and a parent node identifier is represented by parentId, and based on this, in the embodiment of the present application, several examples of target server lifecycle information records corresponding to flow nodes are provided, which are specifically as follows:
Example one:
"souceId": "a00e0f6124f163cdbc445acae1bc14e",
"spaceId": "13fb978b539fd7168985b4fc5eaf99f2",
"parentId": "",
"platformInfo" resource application System ",
"creatTime": "2024-06-11 15:30:45",
"orderId": "DD202410101234",
"applyConfig ": {
"cpuModle": "intel Silver 4310",
"mermoryModle": "32G*3200MHZ",
"quantity": 6
},
"applyInfo": {
"Applicant": "Zhang san",
"APPLICANTDEPARTMENT": technical center ",
}
Example one shows that the Zhang Sanyu, 2024, 11, 15, 30 minutes and 45 seconds of technical center department applies for 6 physical servers with the cpu model number INTEL SILVER, 4310, the memory 32G x 3200MHz and the application number DD202410101234 in the resource application system.
Example two:
"souceId": "a00e0f6124f163cdbc445acae1bc14e",
"spaceId": "ca206e9a06784288bcf4617a4aac2ce3",
"parentId": "13fb978b539fd7168985b4fc5eaf99f2",
"platformInfo" purchasing system ",
"Creator": "Zhao Wu",
"creatTime": "2024-06-12 16:40:45",
"purchaseOrderId": "CG202406121234",
"purchaseInfo": {
"cpuModle": "intel Gold 6330",
"mermoryModle": "32G*3200MHZ",
"quantity": 6
},
"Comment" is a configuration change, the original request is no longer freighted. ",
"supplyInfo": {
"Supplier": "Hefei nao science and technology Co., ltd",
LinkMan: "Lifour"
}
Example two shows that Zhao Wu is purchased in a purchasing system at 40 minutes and 45 seconds at 12 days of 06 months of 2024 in 6 cpu models of intel Gold 6330, a physical server with memory of 32G x 3200MHz, a purchasing list number of CG202406121234, a supplier of a fertilizer and cloud technology Co-efficient, and a supplier contact of Li IV.
As can be seen from the above example one and example two, the resource application system and the purchasing system share the same souceId in the target server life cycle information record, and generate a unique spaceId. The next flow node of the resource application system is a purchasing system, spaceId in the corresponding target server life cycle information record is taken as parentId in the corresponding target server life cycle information record of the purchasing system, the resource application system is a starting flow node, and parentId in the corresponding target server life cycle information record is null.
In the foregoing examples, the first example and the second example are target server lifecycle information records generated by two independent service systems, which are independent events, and the applied server information and the actually purchased server information are not consistent, so that it is difficult to realize that the two have relevance conventionally. However, parentId of example two is spaceId of example one, so the purchased server can be traced back to the server information of the application, and the configuration change can be made knowing that the original application model was empty.
Therefore, in the application, the life cycle information of the target servers of the flow nodes are related through the source identifier, the data space identifier and the father node identifier, so that the method is simple and efficient.
S102, storing the life cycle information records of the target servers corresponding to the flow nodes.
In the application, the life cycle information records of the target servers corresponding to the flow nodes can be stored in the flow nodes in a scattered way or in a centralized way, so that the operation and maintenance personnel can acquire the complete traceable life cycle information of the target servers according to the source identification, the data space identification and the father node identification in the stored life cycle information records of the target servers of the flow nodes.
The embodiment provides a server life cycle information processing method. The method comprises the steps of generating a target server life cycle information record corresponding to a flow node aiming at each flow node in the life cycle of the target server, wherein the target server life cycle information record corresponding to the flow node comprises a source identifier, a data space identifier, a father node identifier and target server life cycle information generated by the flow node, the source identifiers in the target server life cycle information records corresponding to different flow nodes are identical, the father node identifier is the data space identifier of the last flow node adjacent to the flow node, and the target server life cycle information record of each flow node is stored. In the scheme, 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 operation and maintenance personnel can acquire the complete 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 target server life cycle information corresponding to each flow node. By adopting the scheme, the purposes of simply and efficiently processing the service life information of the server and improving the integrity of the service life information of the server can be realized.
In another embodiment of the present application, a method for generating the preset link tracking identifier is described, and specifically, the method for generating the preset link tracking identifier includes:
And generating the preset link tracking identification according to the name of the initial flow node and the related resource application time of the target server when the related resource application of the target server occurs to the initial flow node in the life cycle of the target server before generating the life cycle information record of the target server corresponding to the flow node for each flow node in the life cycle of the target server.
In one possible implementation, when the related resource application of the target server occurs at the start flow node in the life cycle of the target server, an encrypted value (such as MD5 value) of a character string formed by combining the name of the start flow node and the related resource application time of the target server may be calculated as the preset link tracking identifier.
For ease of understanding, assuming that the name of the initial flow node is "resource application system", and the related resource application time of the target server is "2024-06-10:05:30:17", the corresponding preset link tracking identifier may be "a00e0f6124f163cdbc445acae bc14e".
In another embodiment of the present application, a method for generating a data space identifier of the flow node is described, and specifically, the method for generating the data space identifier of the flow node includes:
And generating a data space identifier of the flow node according to the name and the generation time of the life cycle information of the target server generated by the flow node.
In one possible implementation, the name of the target server lifecycle information generated by the flow node and the encrypted value (e.g., MD5 value) of the generated time-combined string may be calculated as the data space identification of the flow node.
For ease of understanding, assuming that the name of the target server lifecycle information generated by the flow node is "resource application information" and the generation time is "2024-06-11 15:30:45", the corresponding data space identifier may be "13fb978b539fd7168985b4fc5eaf f2".
In another embodiment of the present application, a specific implementation manner of storing the life cycle information record of the target server corresponding to each flow node is described.
In one possible implementation, after the generating the preset link tracking identifier, a target server lifecycle data chain may also be created, where the target service lifecycle data chain includes header information and a data space, where the header information of the target server lifecycle data chain includes at least a source identifier, and the source identifier is the preset link tracking identifier.
In one possible implementation, the header information of the target server lifecycle data chain further includes a creation time, a target server type, and a header information creation platform.
For easy understanding, in the embodiment of the present application, a target server lifecycle data chain example is provided, which is specifically as follows:
"creatTime":"2024-06-10 05:30:17",
"souceId": "a00e0f6124f163cdbc445acae1bc14e",
"type": physical server ",
"creatInfo": {
"PlatformInfo": resource application System "
}
"spaceInfo": []
An example shows that 2024, month 06, day 10, 5, 30 minutes 17 seconds creates a link in the resource application system with source Id of a00e0f6124f163cdbc445acae bc14e, asset type of physical server.
The storing of the target server life cycle information record of each flow node includes:
and injecting the target server life cycle information record of each flow node into a data space of the target server life cycle data chain to generate target server life cycle link data, and storing the target server life cycle link data.
For easy understanding, in the embodiment of the present application, a target server lifecycle link data example is provided, which is specifically as follows:
"creatTime": "2024-06-10 05:30:17",
"souceId": "a00e0f6124f163cdbc445acae1bc14e",
"type": physical server ",
"creatInfo": {
"PlatformInfo": resource application System "
},
"spaceInfo": [
{
"spaceId": "13fb978b539fd7168985b4fc5eaf99f2",
"parentId": "",
"PlatformInfo" resource application System ",
"creatTime": "2024-06-11 15:30:45",
"orderId": "202410101234",
"applyConfig ": {
"cpuModle": "intel Silver 4310",
"mermoryModle": "32G*3200MHZ",
"quantity": 6
},
"applyInfo": {
"Applicant": "Zhang san",
APPLICANTDEPARTMENT "technical center"
}
},
{
"spaceId": "ca206e9a06784288bcf4617a4aac2ce3",
"parentId": "13fb978b539fd7168985b4fc5eaf99f2",
"PlatformInfo" purchasing system ",
"Creator": "Zhao Wu",
"creatTime": "2024-06-12 16:40:45",
"purchaseOrderId": "CG202406121234",
"purchaseInfo": {
"cpuModle": "intel Gold 6330",
"mermoryModle": "32G*3200MHZ",
"quantity": 6
},
"Comment" is a configuration change, the original request is no longer freighted. ",
"supplyInfo": {
"Supplier": "Hefei nao science and technology Co., ltd",
LinkMan: "Lifour"
}
},
{
"spaceId": "086c3d1737fd4d80ab5b34eed9b1bce5",
"parentId": "ca206e9a06784288bcf4617a4aac2ce3",
"PlatformInfo" inventory management system ",
"Creator": "Wang Liu",
"creatTime": "2024-07-12 13:40:45",
"entryOrderId": "RK202407121234",
"entryInfo": [
{
"cpuModle": "intel Gold 6330",
"mermoryModle": "32G*3200MHZ",
"SN": 9800203208498669
},
{
"cpuModle": "intel Gold 6330",
"mermoryModle": "16G*3200MHZ",
"SN": 6101437101961066
}
],
"Comment" 2 "warehouses"
}
]
As can be seen from the above examples, the target server lifecycle information records corresponding to the flow nodes are connected in series by the same source identifier to form the target server lifecycle link data.
The aim of the implementation mode is to aggregate the target server life cycle information records corresponding to the flow nodes to generate a target server life cycle data chain, and to store the target server life cycle data chain in a lasting manner for subsequent retrieval and analysis by operation and maintenance personnel. In general, each flow node shares a piece of data, and each flow node can directly obtain from the storage when needing to be searched or updated.
The implementation mode can facilitate each flow node to acquire the full data.
In actual operation, the two-dimensional code can be generated according to souceId and attached to a server body by combining with a two-dimensional code management system or a CMDB (Configuration Management Database ) system. When operation and maintenance personnel perform operation and maintenance management (such as server loading and unloading, configuration changing) and query server information, two-dimension codes can be scanned, and data acquisition of the whole life cycle of the server can be completed without logging in a specific system, so that the method is convenient and quick.
In another possible implementation, the target server life cycle information record corresponding to each flow node may be stored in the corresponding flow node.
And storing the life cycle information records of the target servers corresponding to the flow nodes in the corresponding flow nodes respectively, and enabling operation and maintenance personnel to acquire the records of the corresponding flow nodes through souceId and spaceId, so that full data are not required to be acquired, and the weight is lighter.
In summary, in the scheme of the application, in order to efficiently obtain the full life cycle management information of the server, the production data of each server can be traced, and the server can be queried rapidly, and a complete data chain can be formed by distributing a globally unique link tracking identifier to each type of server in a source flow node (generally a resource application system) as a globally unique identifier, transmitting the globally unique identifier to each link along with the flow, and recording the information of each link.
Compared with the prior art, the scheme of the application can automatically realize the assembly of the full-link data without cross-system development and docking and has high expansibility, and can be easily combined with third-party manufacturers (such as server manufacturers and operation and maintenance management manufacturers), thereby greatly reducing the operation and maintenance workload. Compared with the prior art, the target server life cycle link data generated by the scheme of the application has the advantages of quick tracing inquiry, convenient updating and high data integrity.
The method for processing the life cycle information of the server provided by the embodiment of the application is introduced above, and a device for executing the method for processing the life cycle information of the server is introduced below.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a server life cycle information processing device according to an embodiment of the application. As shown in fig. 2, the server life cycle information processing apparatus includes:
a record generating unit 11, configured to generate, for each process node located in a target server lifecycle, a target server lifecycle information record corresponding to the process node, where the target server lifecycle information record corresponding to the process node includes a source identifier, a data space identifier, a parent node identifier, and target server lifecycle information generated by the process node;
A record storage unit 12, configured to store a target server life cycle information record of each of the flow nodes.
In one possible implementation, the source identifiers in the target server lifecycle information records corresponding to different process nodes are the same preset link tracking identifier.
In one possible implementation, the device further comprises a preset link tracking identifier generating unit;
The preset link tracking identifier generating unit is configured to generate, before the target server lifecycle information record corresponding to each process node located in the target server lifecycle is generated, the preset link tracking identifier according to the name of the initial process node and the related resource application time of the target server when the related resource application of the target server occurs at the initial process node located in the target server lifecycle.
In one possible implementation, the apparatus further comprises a data space identification generation unit;
The data space identifier generating unit is used for acquiring the name and the generation time of the life cycle information of the target server generated by each flow node in the life cycle of the target server;
and generating a data space identifier of the flow node according to the name and the generation time of the life cycle information of the target server generated by the flow node.
In one possible implementation, the apparatus further comprises a target server lifecycle data chain creation unit;
The target server life cycle data link creation unit is used for creating a target server life cycle data link after the preset link tracking identification is generated, wherein the target server life cycle data link comprises head information and a data space, the head information of the target server life cycle data link at least comprises a source identification, and the source identification is the preset link tracking identification.
In a possible implementation, the record storage unit is specifically configured to:
Injecting the target server life cycle information records corresponding to the flow nodes into a data space of a target server life cycle data chain to generate target server life cycle link data;
And storing the life cycle link data of the target server.
In a possible implementation, the record storage unit is specifically configured to:
And storing the life cycle information records of the target servers corresponding to the flow nodes in the corresponding flow nodes respectively.
The embodiment of the application also provides electronic equipment. Referring to fig. 3, a schematic diagram of an electronic device suitable for use in implementing embodiments of the present application is shown. The electronic device in the embodiment of the present application may include, but is not limited to, a fixed terminal such as a mobile phone, a notebook computer, a PDA (personal digital assistant), a PAD (tablet computer), a desktop computer, and the like. The electronic device shown in fig. 3 is only an example and should not be construed as limiting the functionality and scope of use of the embodiments of the application.
As shown in fig. 3, the electronic device may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601, which may 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 means 608 into a Random Access Memory (RAM) 603. In the state where the electronic device is powered on, various programs and data necessary 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 through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
In general, devices may be connected to I/O interface 605 including input devices 606, including for example, touch screens, touch pads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc., output devices 607, including for example, liquid Crystal Displays (LCDs), speakers, vibrators, etc., storage devices 608, including for example, memory cards, hard disks, etc., and communication devices 609. The communication means 609 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. While fig. 3 shows an electronic device having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.
Embodiments of the present application also provide a computer program product including computer readable instructions, which when executed on an electronic device, cause the electronic device to implement any of the server lifecycle information processing methods provided by the embodiments of the present application.
The embodiment of the application also provides a computer readable storage medium, which carries one or more computer programs, and when the one or more computer programs are executed by the electronic device, the electronic device can realize any server life cycle information processing method provided by the embodiment of the application.
It should be further noted that the above-described apparatus embodiments are merely illustrative, and that the units described as separate units may or may not be physically separate, and that units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, in the drawings of the embodiment of the device provided by the application, the connection relation between the modules represents that the modules have communication connection, and can be specifically implemented as one or more communication buses or signal lines.
From the above description of the embodiments, it will be apparent to those skilled in the art that the present application may be implemented by means of software plus necessary general purpose hardware, or of course by means of special purpose hardware including application specific integrated circuits, special purpose CPUs, special purpose memories, special purpose components, etc. Generally, functions performed by computer programs can be easily implemented by corresponding hardware, and specific hardware structures for implementing the same functions can be varied, such as analog circuits, digital circuits, or dedicated circuits. But a software program implementation is a preferred embodiment for many more of the cases of the present application. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a readable storage medium, such as a floppy disk, a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk or an optical disk of a computer, etc., comprising several instructions for causing a computer device (which may be a personal computer, a training device, a network device, etc.) to perform the method according to the embodiments of the present application.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. 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 one website, computer, training device, or data center to another website, computer, training device, or data center via a wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a training device, a data center, or the like that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (Solid STATE DISK, SSD)), etc.
Claims (11)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510209354.5A CN119988385A (en) | 2025-02-25 | 2025-02-25 | A server life cycle information processing method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510209354.5A CN119988385A (en) | 2025-02-25 | 2025-02-25 | A server life cycle information processing method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN119988385A true CN119988385A (en) | 2025-05-13 |
Family
ID=95626082
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202510209354.5A Pending CN119988385A (en) | 2025-02-25 | 2025-02-25 | A server life cycle information processing method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119988385A (en) |
-
2025
- 2025-02-25 CN CN202510209354.5A patent/CN119988385A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101978366B (en) | Application management within deployable object hierarchy | |
| US20140040182A1 (en) | Systems and methods for collection and consolidation of heterogeneous remote business data using dynamic data handling | |
| US20110264636A1 (en) | Updating a data warehouse schema based on changes in an observation model | |
| US20060241997A1 (en) | System and method for integrating workflow processes with a project management system | |
| CN107102848A (en) | Provide user interface element | |
| CN105793874B (en) | Method and system for managing group information | |
| EP2610762A1 (en) | Database version management system | |
| CN114282078A (en) | Project data processing method, device, electronic device and storage medium | |
| US10572247B2 (en) | Prototype management system | |
| CN114444712A (en) | Management method and device of machine learning model, computer equipment and storage medium | |
| US20080114627A1 (en) | System and Method for Capturing Process Instance Information in Complex or Distributed Systems | |
| CN105677427A (en) | Module upgrading method and device | |
| CN115080540A (en) | Data migration method and device, computer equipment and storage medium | |
| CN113253991A (en) | Task visualization processing method and device, electronic equipment and storage medium | |
| US8260782B2 (en) | Data element categorization in a service-oriented architecture | |
| CN108595488B (en) | Data migration method and apparatus | |
| CN119988385A (en) | A server life cycle information processing method and related device | |
| CN104572145B (en) | File edition management method and system | |
| WO2024114340A1 (en) | Method and apparatus for constructing digital twin model in plurality of logistics scenarios, and device and medium | |
| US20080183537A1 (en) | Approach to comprehensive requirements specifications for complex workflows | |
| CN112597121A (en) | Logic script processing method and device, electronic equipment and storage medium | |
| CN114528198A (en) | Software automation test method and device, electronic equipment and storage medium | |
| Shrivastava et al. | Hadoop blueprints | |
| TWI894029B (en) | Data providing method and apparatus for the same | |
| CN117687608B (en) | Method, device, equipment and storage medium for generating orchestration stream |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |