Server management method, electronic device, readable storage medium and program product

Abstract

The application discloses a kind of server management method, electronic equipment, readable storage medium and program product, it is related to computer technical field.Therein, method includes based on user attribute and server attribute, according to the implementation module of each kind of server each kind of business corresponding generation business-implementation corresponding relationship, and determine the implementation logic relationship between the implementation module of adjacent version. To user business implementation request, according to user attribute matched target business-implementation corresponding relationship information, implementation logic relationship and user server attribute, determine the routing relationship of business implementation module and server attribute satisfying user request, finally business implementation data is encrypted and feedback to user.The application can solve the problem that related technology cannot meet the needs of user safe, efficient and effective server management, can accurately update the corresponding relationship of server and function implementation method on the basis of ensuring that customer information is not leaked, realize the efficient management of server.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a server management method, electronic device, readable storage medium, and program product. Background Technology

[0002] When managing servers, related technologies first distinguish server types based on server attributes, and then match different types of servers with corresponding functional implementation methods according to configuration files.

[0003] As the number of servers increases, the relevant technologies can neither guarantee that customer information will not be leaked, nor can they accurately update the correspondence between servers and function implementation methods, nor can they efficiently manage servers. Summary of the Invention

[0004] This invention provides a server management method, electronic device, computer-readable storage medium, and computer program product, which can accurately update the correspondence between the server and the function implementation method while ensuring that user data is not leaked, thereby achieving efficient server management.

[0005] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0006] This invention provides a server management method, comprising:

[0007] Based on user attributes and server attributes, and according to the implementation modules corresponding to various services of various types of servers, the business-implementation correspondence information of each user is generated; based on the business-implementation correspondence information of each user, the implementation logic relationship between each implementation module and the implementation modules of adjacent server software versions is determined.

[0008] When a user's business implementation request is received, the system matches the target business-implementation correspondence information based on the user's attributes. Based on the target business-implementation correspondence information, the implementation logic relationship, and the attributes of the user's server, the system determines the business implementation module that satisfies the user's business implementation request and generates the routing relationship between each business implementation module and the corresponding server attributes.

[0009] The encrypted business implementation modules and the encrypted routing relationships are sent to the user as the request processing result.

[0010] The present invention also provides an electronic device, including a memory and a processor, wherein the processor is configured to implement the steps of any of the above-described server management methods when executing a computer program stored in the memory.

[0011] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the above-described server management methods.

[0012] Finally, the present invention also provides a computer program product, including a computer program / instruction that, when executed by a processor, implements the steps of any of the above-described server management methods.

[0013] The advantages of the technical solution provided by this invention are as follows: During the compatibility management of the server, business-implementation correspondence information is generated for each business, covering all implementation modules that implement that business function. Based on this correspondence information, the direct relationship between different servers can be accurately determined. The implementation logic relationship between adjacent versions of implementation modules can clearly reveal the similarity relationship between different servers. Based on the direct and similar relationships between different servers, the correspondence between servers and function implementation methods can be accurately updated, which is beneficial for improving the reusability of identical code and achieving efficient server management. For user business implementation requests, each business implementation module that meets the implementation requirements is matched. The encrypted business implementation modules and their correspondence with the server are fed back to the user as specific data to meet the user's needs. In this way, users cannot perceive other user data that is not their own, avoiding the leakage of user privacy data. This achieves efficient and effective server management while ensuring that user data is not leaked.

[0014] Furthermore, the present invention also provides corresponding electronic devices, computer-readable storage media, and computer program products for server management methods, further making the method more practical. These electronic devices, computer-readable storage media, and computer program products have corresponding advantages. Attached Figure Description

[0015] To more clearly illustrate the technical solutions of the present invention or related technologies, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 A schematic diagram of the hardware composition framework applicable to the server management method provided by the present invention;

[0017] Figure 2 A flowchart illustrating a server management method provided by the present invention;

[0018] Figure 3This is a schematic diagram of the business module tree provided by the present invention in an exemplary application scenario;

[0019] Figure 4 A schematic diagram of the implementation logic relationship tree provided by the present invention in an exemplary application scenario;

[0020] Figure 5 A schematic diagram of the business module tree provided by the present invention in another exemplary application scenario;

[0021] Figure 6 A schematic diagram illustrating the generation process of the request processing result provided by the present invention in an exemplary application scenario;

[0022] Figure 7 This is a structural framework diagram of an exemplary embodiment of the server management device provided by the present invention;

[0023] Figure 8 This is a structural diagram of an exemplary embodiment of the electronic device provided by the present invention. Detailed Implementation

[0024] To enable those skilled in the art to better understand the technical solutions of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. In this specification and the aforementioned drawings, the terms "first," "second," "third," "fourth," etc., are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. The term "exemplary" means "serving as an example, embodiment, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as superior to or better than other embodiments.

[0025] Server management software identifies server types based on attributes such as machine name, routes server types to the appropriate implementation interfaces via routing files, and finally calls these interfaces to configure and manage the corresponding servers. As business needs grow and the number of compatible server models increases, the number and types of servers that can be managed by the same server management software also rises. This increases the difficulty of server management and raises the risk of unauthorized access to server compatibility information. To protect user privacy and prevent data leaks, the client interface of the server management software needs to be simplified, providing only the basic management functions.

[0026] The relevant technology distinguishes servers by model name and then maps different server models to corresponding functional implementation methods based on configuration files. During server compatibility processing, the configuration file of the server model to be compatible is routed to the corresponding implementation method, thereby enabling server management. As the number of server users and their needs increase, the types and number of server models also increase, leading to a larger scale of servers that the server management software needs to manage. With the increasing number of servers, the configuration files become increasingly large, making it difficult to clearly display the relationships between different server models. When a new server model is added or a server implementation method is updated, previously identical models also need to be modified. However, due to the loss of the mapping between different models, update information may be incomplete. Furthermore, server users may use the server management software to determine other compatible models, potentially leading to the leakage of user information.

[0027] In view of this, to address the complex interrelationships between different implementation methods for newly added server models, which hinder effective updates and prevent accurate modification of the corresponding implementation method for each model when a new implementation method is introduced, and to avoid user information leakage, this invention constructs a business-implementation correspondence information for each user based on user and server attributes and the implementation modules corresponding to various services on different types of servers. Based on this information, the implementation logic relationship between each implementation module and the implementation modules of adjacent server software versions is determined. This business-implementation correspondence information and implementation logic relationship clearly reveals the relationships between different servers, enabling precise updates to the correspondence between servers and functional implementation methods. Furthermore, based on this information, a combination of implementation modules that meets the specific business needs of each user is determined. The implementation tools provided to users are only for their own servers and are not provided to all users, ensuring user data security.

[0028] This section describes the specific application environment architecture or hardware architecture upon which the server management methods depend. The following section will further elaborate on this. Figure 1 Examples of possible application scenarios related to the technical solutions of this invention are provided below:

[0029] A data center includes servers and management nodes of various models. Users purchase at least one server from the data center to meet their business needs. The management node can be any server in the data center or a high-performance server. The management node runs server management software, which is installed on the management node via a web page or application. The user manages all of their servers through the server management software.

[0030] The management node generates business-implementation mapping information for each user based on user and server attributes, and according to the implementation modules corresponding to various services on different server types (e.g., each server model). Based on this mapping information, it determines the implementation logic relationship between each implementation module and the implementation modules of adjacent server software versions. Users send business implementation requests to the management node through their client. Upon receiving the request, the management node matches the target business-implementation mapping information with the user attributes. Based on the target business-implementation mapping information, the implementation logic relationship, and the user's server attributes, it determines the business implementation modules that satisfy the user's request and generates routing relationships between each business implementation module and its corresponding server attributes. The encrypted business implementation modules and the encrypted routing relationships are then sent to the client as the request processing result. The data center can accurately update the mapping relationship between servers and functional implementation methods while ensuring user data security, achieving efficient server management.

[0031] It should be noted that the above application scenarios are only shown to facilitate understanding of the ideas and principles of the present invention, and the embodiments of the present invention are not limited in any way. On the contrary, the embodiments of the present invention can be applied to any applicable scenario. After introducing the technical solution of the present invention, various non-limiting embodiments of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0032] Please see first. Figure 2 , Figure 2 This is a flowchart illustrating a server management method provided in this embodiment. This embodiment may include the following:

[0033] S201: Based on user attributes and server attributes, generate business-implementation correspondence information for each user according to the implementation modules corresponding to various services of various types of servers; determine the implementation logic relationship between each implementation module and the implementation modules of adjacent server software versions according to the business-implementation correspondence information for each user.

[0034] In this step, user attributes are unique information that distinguishes different users. For example, this could be the user's registered name when purchasing a server, a unique identifier such as an ID assigned by the server management, or a unique username. Server attributes refer to attributes that can be used to classify servers, such as server type. This step distinguishes all servers based on user and server attributes. First, all servers for each user can be obtained based on user attributes. Then, for each user, all servers purchased by that user can be distinguished based on server attributes. For each type of server for that user, the business combinations that that type of server can perform can be obtained. For example, user M owns a set of server types {A, B, ..., N}, where N represents the total number of server types owned by user M. Each server type is further distinguished based on business, such as server type A having a business set {business 1, business 2, ..., business k}, where k represents the business that server type A can perform. This step manages the server according to business functions. Each business function corresponds to at least one implementation module. An implementation module is a set of methods used to implement a business function. For example, if the business function is to obtain central processing unit (CPU) information, the implementation module for this business function is a method that can obtain a specified field through a specified interface. This specified field is the CPU information that the user wants to obtain, and thus the server is managed through this implementation module. As the server version is continuously updated, the implementation modules for the business functions will also be updated accordingly. Therefore, over time, one business function will correspond to multiple implementation modules, that is, different implementation modules for the same business function will correspond to different server upgrade versions. In this way, each business function will correspond to a set of implementation modules. This allows us to determine a set of implementation modules for each business function of each type of server, thus establishing a correspondence between user, server type, business function, and implementation module. In this correspondence, one user corresponds to multiple types of servers, each type of server corresponds to multiple businesses, and each business function corresponds to a set of implementation modules. For ease of description, this is defined as the user's business-implementation correspondence information. In this way, when user M's device A performs business B operation, the implementation modules of business B for device A are determined by the business-implementation correspondence information, and one of these implementation modules is used to support the implementation of business B.

[0035] After generating the corresponding business-implementation mapping information for each user, for each implementation module, since the set of implementation modules for each business in the business-implementation mapping information represents the implementation methods for the corresponding functions of that business supported by different versions of the server, meaning that the business-implementation mapping information has been updated with the implementation modules after the server software version upgrade, considering scenarios where some server A versions have been upgraded but implementation module B has not been updated, or scenarios where a certain business k currently has an unsupported implementation module and requires the use of a future updated version of the implementation module, it is understandable that if implementation module A and implementation module B are implementation modules of adjacent server versions, and implementation module B is a higher-level version of implementation module A, and implementation module A cannot meet the business requirements of a certain user and machine type, implementation module B can meet those requirements. Furthermore, similar servers and / or similar users will also have similar implementation modules. Therefore, implementation module B can be used as the implementation module of the higher-level version of implementation module A in the business-implementation mapping information of other users as the future upgrade version of implementation module B for this user's machine type, or as the implementation module capable of implementing business k. In other words, the higher-level version or upgraded version of each implementation module may solve the problems existing in the above scenarios. Therefore, the adjacent version implementation module referred to in this step refers to the implementation module that is compared with the next higher version or the upgraded version of the existing implementation module. Accordingly, based on the unique identification information of each implementation module, such as the implementation module name + version number, the implementation module can be represented by traversing all the implementation modules in the business-implementation correspondence information of each user, and all the next higher version implementation modules compared with the current server version can be identified. The correspondence between the implementation module and these next higher version implementation modules is defined as the implementation logic relationship. Accordingly, when determining the implementation logic relationship, in order to clearly show the similarity between different servers, the server type and the corresponding user of the next higher version implementation module can also be added.

[0036] S202: When a user's business implementation request is received, match the target business-implementation relationship information according to the user attributes.

[0037] Among them, the user business implementation request is the request instruction of the business that the user wants to implement. The user business implementation request includes at least user attributes and the business that the user wants to implement. By parsing the user business implementation request, user attributes such as user name and the business that the user wants to implement such as business name are obtained. After generating business-implementation correspondence information for each user in step S201, the corresponding business-implementation correspondence information can be matched for the parsed user attributes, which is the target business-implementation correspondence information of this step.

[0038] S203: Based on the target business-implementation correspondence information, implementation logic relationship and user server attributes, determine the business implementation modules that meet the user business implementation request, and generate the routing relationship between each business implementation module and the corresponding server attributes.

[0039] After the previous step determined the target business-implementation mapping information and parsed the business the user wanted to implement, a set of implementation modules corresponding to that business can be identified in the target business-implementation mapping information based on the business's identifier information. This set of existing implementation modules is the business implementation module that satisfies the user's business implementation request. Since the implementation logic relationship can determine which existing implementation modules in the business-implementation mapping information cannot meet the user's business needs, and which may support the business, implementation modules that might be used can also be identified for these existing implementation modules in the implementation logic relationship. This set of implementation modules is also considered as business implementation modules. After determining the business implementation modules, a mapping relationship needs to be established between each business implementation module and its corresponding server type. For ease of description, this is defined as a routing relationship. For example, the routing relationship can be identified through server attribute identifier information: implementation module identifier information, such as machine type: module name.

[0040] S204: Send the encrypted business implementation modules and the encrypted routing relationships to the user as the request processing result.

[0041] To protect user privacy and prevent other users from learning about the user's server compatibility information, after determining the routing information that satisfies the user's business implementation request in the above steps, this routing information, together with the business implementation module, can be encrypted. The encrypted data can then be used as the request processing result and fed back to the user. Any encryption method can be used to encrypt the business implementation module and the routing relationship together or separately, without affecting the implementation of this invention.

[0042] In the technical solution provided in this embodiment, during the compatibility management of the server, business-implementation correspondence information is generated for each service, covering all implementation modules that implement the service function. This correspondence information accurately determines the direct relationships between different servers. Based on the implementation logic relationships between adjacent versions of implementation modules, the similarity relationships between different servers can be clearly obtained. Furthermore, based on the direct and similar relationships between different servers, the correspondence between servers and function implementation methods can be accurately updated, which helps improve the reusability of identical code and achieves efficient server management. For user service implementation requests, each business implementation module that meets the implementation requirements is matched. The encrypted business implementation modules and their correspondence with the server are then fed back to the user as specific data to meet the user's needs. This prevents users from perceiving other user data that is not their own, avoiding the leakage of user privacy data. This ensures efficient and effective server management while guaranteeing that user data is not leaked.

[0043] In the above embodiments, no limitation is made on how to determine the business implementation module that satisfies the user's business implementation request. The present invention provides a variety of methods for determining the business implementation module according to different application scenarios, which may include the following:

[0044] In an exemplary application scenario, a user's business implementation request includes multiple pending business requirements, and the user's request includes a requirement to increase server compatibility. This requirement refers to the user's request to enhance server compatibility. The process of determining the business implementation module to satisfy the user's business implementation request includes: In the target business-implementation correspondence information, sequentially determine the implementation modules for each pending business requirement; for ease of description, these are defined as known implementation modules. If no implementation module for a pending business requirement exists in the target business-implementation correspondence information, for ease of description, it is defined as a target pending business requirement and a target business implementation module. If the user's business implementation request includes a requirement to increase server compatibility, then determine the highest version of the implementation module corresponding to the target pending business requirement based on the target business-implementation correspondence information; for ease of description, this is defined as a bridge implementation module. In the implementation logic relationship, determine the implementation modules of the next higher version of the bridge implementation module; for ease of description, these are defined as candidate implementation modules. Based on the differences between different users and / or different servers, determine the probability that each candidate implementation module can implement the target business requirement, and select the candidate implementation module with the highest probability as the target business implementation module; use each known implementation module and the target business implementation module as the business implementation module that satisfies the user's business implementation request.

[0045] In another exemplary application scenario, the user's business implementation request also includes multiple pending business requirements. The user has not explicitly stated a need for increased server compatibility. The process of determining the business implementation module to satisfy the user's business implementation request includes: First, identifying known implementation modules for each pending business requirement from the target business-implementation correspondence information. Second, if no implementation module exists in the target business-implementation correspondence information, an implementation module is needed to satisfy the user's business requirements. Therefore, the highest-version bridge implementation module corresponding to the target pending business can be determined based on the target business-implementation correspondence information. Third, identifying candidate implementation modules for the next higher version of the bridge implementation module in the implementation logic relationship, and determining the probability of each candidate implementation module implementing the target pending business based on different user differences and / or different server differences. Fourth, using the known implementation modules and the candidate implementation modules carrying probabilities as the business implementation modules to satisfy the user's business implementation request. Alternatively, several candidate implementation modules with high probabilities can be directly sent to the business implementation module. When providing feedback to the user, it should be clearly stated that each candidate implementation module may support the pending business, allowing the user to try using each candidate implementation module to implement the pending business according to their actual needs.

[0046] In another exemplary application scenario, the user's business implementation request also includes multiple pending business requirements. The user also explicitly states a need to increase server compatibility. The process of determining the business implementation module that satisfies the user's business implementation request includes: in the target business-implementation correspondence information, sequentially determining the known implementation modules that implement each pending business requirement in the user's business implementation request; if the user's business implementation request also includes a need to increase server compatibility, then in the implementation logic relationship, determining each candidate implementation module of the next higher level of the known implementation module; based on different user differences and / or different server differences, determining the probability of each candidate implementation module implementing the corresponding pending business requirement, and selecting the candidate implementation module with the highest probability as the implementation module of the known implementation module. For ease of description, this is defined as a compatible implementation module; and using each known implementation module and its corresponding compatible implementation module as the business implementation module that satisfies the user's business implementation request.

[0047] Of course, in a simpler application scenario, where the user does not increase the compatibility requirements, and the known implementation modules that implement each required business can be identified sequentially based on the target business-implementation correspondence information, then these known implementation modules can be directly used as the business implementation modules that meet the user's business implementation requests, without the need to determine compatible implementation modules.

[0048] For the above application scenarios, when calculating the probability that each candidate implementation module will achieve the target business requirement, the user difference information and server difference information between each candidate implementation module / candidate implementation module and the known implementation module can be quantified. For example, if the candidate implementation module / candidate implementation module and the known implementation module belong to the same user, the user difference information is 1. If the candidate implementation module / candidate implementation module and the known implementation module belong to the same server model, the server difference information is 1. The greater the difference between the users of the candidate implementation module / candidate implementation module and the known implementation module, the smaller the quantified value of the user difference information. The greater the difference between the servers of the candidate implementation module / candidate implementation module and the known implementation module, the smaller the quantified value of the server difference information.

[0049] As can be seen from the above, this embodiment calculates the probability of a higher-level implementation module based on the logical relationship between implementation modules and the degree of difference between the user and / or server. When the current business does not support it, the implementation module with the highest probability is used to attempt compatibility. This effectively solves the problem that the server is updated ahead of time but the management software has not yet updated the corresponding data, resulting in the inability to find an effective implementation module to meet the business needs. By providing a compatible implementation module, the user's business needs can be responded to quickly, the user experience can be improved, and the reuse rate of the same code can be increased.

[0050] The above embodiments do not limit how to generate the business-implementation correspondence information for each user. Based on the above embodiments, the present invention also provides an exemplary method for generating business-implementation correspondence information, which may include the following:

[0051] Obtain all servers to be managed for the current user and classify them according to their attributes; count the services of each type of server to be managed, obtain the implementation modules of each service, and form an implementation linked list for each implementation module of the same service; generate the service-implementation correspondence information for each user according to the following: the same user includes multiple types of servers to be managed, the same type of server to be managed includes multiple services, and each service has a unique corresponding implementation linked list.

[0052] The above embodiments can directly use textual or array forms to represent a group of implementation modules. For example, to facilitate the display of relationships between different implementation modules and the determination of implementation logic, a group of implementation modules for each business can be represented in table form, or for example, in linked list form: For each business, obtain all implementation modules of the current business; sort the implementation modules of the current business according to their version number or update time, and generate an implementation linked list for the current business according to the sorted implementation modules. After these implementation modules are grouped into an implementation linked list, each business actually corresponds to one implementation linked list. When managing the server, the implementation module linked list is traversed according to the server version to find the corresponding implementation module.

[0053] For example, a tree structure can be used to represent the business-implementation correspondence information for each user. Each subtree corresponds to the implementation modules of all services for a certain type of server. Based on the root node representing user attributes, each child node of the root node representing the attributes of the server to be managed, each child node's child nodes representing services, and leaf nodes representing implementation lists, a corresponding business module tree is generated for each user to represent the business-implementation correspondence information. For ease of description, the business-implementation correspondence information for each user can be defined as a business module tree. For example, in a scenario where the user name is used as a user attribute and the server model is used for classification, the user's business module tree can be generated based on the user's server model. Figure 3 As shown.

[0054] As can be seen from the above, this embodiment uses a tree structure to store business-to-business relationship information. Each business corresponds to a linked list of implementation modules, which can more clearly show the relationship between different servers and improve server management efficiency.

[0055] The above embodiments do not limit how to generate the implementation logic relationship between implementation modules. Based on the above embodiments, the present invention also provides an exemplary method for generating the implementation logic relationship, which may include the following:

[0056] The business-implementation mapping information for each user is traversed to determine the next-level implementation module for each implementation module. For ease of description, this is defined as the target implementation module. The target user and target server model corresponding to each target implementation module are obtained. Based on the following scenarios: multiple users corresponding to the same implementation module, multiple server models corresponding to each user, and one target implementation module corresponding to each server model, the implementation logic relationships between each implementation module and other implementation modules are generated respectively.

[0057] For example, such as Figure 4As shown, a tree structure can be used to store logical relationships. The root node represents the implementation module, each child node of the root node represents the user attribute, each child node's child node represents the server model, and the leaf nodes represent the target implementation module. A corresponding implementation logic relationship tree is generated for each implementation module to represent the implementation logic relationship between the current implementation module and other implementation modules.

[0058] Based on the business-implementation correspondence information in the tree structure described above, for each implementation module, find its next implementation module in each implementation linked list as the target implementation module. Each implementation module is taken as the root node, and its next implementation module in each implementation linked list is taken as the leaf node. The device model and user corresponding to the leaf node are added to the intermediate paths to generate a tree-structured representation of the implementation logic relationship.

[0059] As can be seen from the above, this embodiment uses a tree structure to store logical relationships, which can more clearly display the relationships between different servers and improve server management efficiency.

[0060] Furthermore, based on the above embodiment, in implementing the logical relationship, for each user's business-implementation correspondence information, the implementation modules for each next-level upgrade are determined. For ease of description and to avoid ambiguity, this embodiment defines them as upgrade candidate modules. Based on the differences between different users and / or different servers, the probability that each upgrade candidate module is an upgrade version of the corresponding implementation module is determined, and the upgrade candidate module with the highest probability is selected as the probability implementation module; the corresponding business-implementation correspondence information is updated according to the probability implementation module corresponding to each implementation module.

[0061] For ease of description, Figure 3 The business module tree shown and Figure 4 Taking the implementation logic tree as an example, for Figure 3 The last implementation module in the implementation linked list is matched with the corresponding implementation logic tree. Based on the user information and server attributes of the implementation module, the probability between it and each leaf node of the implementation logic tree is calculated, and the modules are sorted according to probability. The module with the highest probability is selected as the most likely to be compatible with the implementation. Figure 3 Update and get Figure 5 The diagram shows a business module tree. When a user requests increased compatibility, in addition to the known implementation modules, the implementation module with the highest conditional probability added to each linked list can be fed back to the user. This way, when none of the implementation modules in the original implementation list can meet the user's business needs, the implementation module with the highest probability of compatibility can be used for adaptation.

[0062] As can be seen from the above, this embodiment adds the implementation module of the most likely future update version to the user's business-implementation correspondence. This not only solves the problem that the server is updated ahead of time but the management software has not yet updated the corresponding data, resulting in the inability to find an effective implementation module to meet business needs, but also improves code reusability and achieves efficient server management.

[0063] As an efficient implementation method, the probability of each upgrade candidate module can be calculated as follows: The probability of an upgrade candidate module being a one-level upgrade version of the corresponding implementation module is calculated using the probability calculation formula, which can be expressed as follows: ,in, This indicates the probability that the candidate module x1 is an upgraded version of the corresponding implementation module A. Am represents the server attribute information of implementation module A, x1m represents the server attribute information of candidate module x1, Au represents the user attribute information of implementation module A, and x1u represents the user attribute information of candidate module x1. This represents the server attribute weight value. This represents the user attribute weight value. Initial values ​​can be set for both server attribute weight values ​​and user attribute weight values, and these values ​​can be dynamically adjusted based on the similarity trends between different users and between different types of servers.

[0064] If there are multiple identical target upgrade candidate modules, the probability of each target upgrade candidate module being an upgraded version of the corresponding implementation module is first calculated by calling the probability calculation formula. Then, the sum of the probabilities of all target upgrade candidate modules being upgraded versions of the corresponding implementation module is taken as the probability of the target upgrade candidate module being an upgraded version of the corresponding implementation module.

[0065] As can be seen from the above, this embodiment calculates the probability of upgrading the candidate module to an upgraded version of the corresponding implementation module by dynamically adjusting the server attribute weight value and the user attribute weight value. By merging the probabilities of the same candidate module, it can effectively improve the accuracy and efficiency of the calculation of the logical relationship between different implementation modules, and improve the effectiveness and efficiency of server management.

[0066] The above embodiments do not limit the encryption method of the request processing result. The present invention also provides an exemplary implementation method, which may include the following:

[0067] The system concatenates the user's encrypted information with the user server's model name, and uses the hashed encrypted data of the user-model concatenation as the user server's dedicated server information; it also concatenates the user's encrypted information with the module names of each business implementation module, and uses the hashed encrypted data of each user-module concatenation as the dedicated implementation information of each business implementation module; based on each business implementation module and its corresponding user server, it generates a routing table that maps each dedicated implementation information to its dedicated server; and finally, it packages the user's encrypted information, the routing table, and each dedicated implementation information to generate the request processing result.

[0068] In this embodiment, a dynamic salt value is used as an example for encryption. Of course, other encryption methods can also be used, such as digital signatures or dynamic cryptography. This invention does not limit these methods. Figure 6 As shown, a dynamic salt value can be pre-generated for each user. The salt value is then concatenated with the server model names purchased by the user, followed by hash encryption to obtain the unique server model names for each user's servers. This prevents unauthorized data sharing between users, such as preventing user A from directly operating user B's machine with their tools, and also preventing A from recognizing user B's server data. Once the business implementation module is determined, a new implementation module name can be generated by concatenating it with the salt value and using hash encryption. Even if two servers use implementation module A, knowing one server allows inference of the other server based on implementation module A, protecting user privacy. Finally, the salt value, the encrypted business implementation module, and the route are packaged and provided to the user, ensuring that the tools sent to the user can only manage the servers purchased by that user and cannot access other users' server data, thus improving user data security.

[0069] To further improve server management efficiency and effectiveness, based on the above embodiments, the present invention can also perform update operations according to user feedback information, which may include the following:

[0070] Receive user compatibility feedback; if the target probability implementation module is determined to be an upgraded version of the corresponding implementation module based on the compatibility feedback, increase the corresponding target user difference weight and target device difference weight, and update the corresponding business-implementation correspondence information and implementation logic relationship; if the candidate implementation module implements the function of the target business to be required based on the compatibility feedback, increase the corresponding target user difference weight and target device difference weight, and update the corresponding business-implementation correspondence information and implementation logic relationship; if the candidate implementation module implements the function of the target business to be required based on the compatibility feedback, increase the corresponding target user difference weight and target device difference weight, and update the corresponding business-implementation correspondence information and implementation logic relationship.

[0071] In this embodiment, when the provided non-known implementation module implements the corresponding business function during the user's use, the user difference weight and the model difference weight of the module are increased, and the user's business module tree diagram and the corresponding logical relationship diagram are updated.

[0072] To make the technical solution of the present invention clearer and more understandable to those skilled in the art, the present invention also provides an exemplary server management implementation method, which may include the following:

[0073] A1: Count all servers and divide the servers among users according to the user names.

[0074] A2: Select one user name, distinguish the servers under this user according to the server model name, and distinguish each model according to the business, to obtain a business set {Business 1, Business 2,..., Business k}. Each business corresponds to an implementation list of business implementation modules, and the implementation list sequentially includes multiple implementation modules according to different version numbers.

[0075] A3: Based on that the root node represents the user name, each sub-node of the root node represents the server model name, each sub-node of each sub-node represents the business, and the leaf node represents the implementation list, generate a corresponding business module tree for the user.

[0076] A4: For all users, repeat steps A2 - A3 to generate the business module trees of all users.

[0077] A5: For the implementation list of the business module tree diagram, if there is a logical relationship from implementation module x to implementation module y, generate a logical structure of <x, user M, model A, module y> according to the user M and model A corresponding to implementation module y, and obtain all the logical structures of implementation module x to form an implementation logical relationship tree of implementation module x.

[0078] A6: Repeat the execution of A5 to generate a corresponding implementation logical relationship tree for the last implementation module of the implementation list of each business module tree. During the repeated execution, if a corresponding implementation logical relationship tree has already been generated for the same implementation module, there is no need to generate it repeatedly.

[0079] A7: According to the implementation logical relationship trees of each implementation module, calculate the probability of the upgraded implementation module corresponding to each leaf node of the implementation logical relationship tree for the implementation module by calling the probability calculation formula.

[0080] A8: Obtain the probabilities corresponding to all the upgraded modules of each implementation module, and use the upgraded module with the highest probability as the next upgraded module of the implementation module, and update the business module tree corresponding to A3.

[0081] A9: For the service of user M2-model A2, if the last implementation module x in the implementation chain of the user service module tree cannot be implemented, determine the probability of all upgrade modules of implementation module x according to the method of A6, and take the target upgrade module with the higher probability as the implementation module that supports the service.

[0082] A10: When the target upgrade module implements the service for user M2-model A2, the user difference weight and model difference weight are increased accordingly, and the service module tree and implementation logic relationship tree for that user are updated.

[0083] As can be seen from the above, this embodiment can more clearly obtain the relationship between different servers, realize the control and management of multiple branch server versions, and achieve a higher reuse rate of the same code.

[0084] It should be noted that there is no strict order of execution between the steps in this invention. As long as they conform to the logical order, these steps can be executed simultaneously or in a certain preset order. Figure 2 This is just an illustrative example and does not mean that this is the only possible execution order.

[0085] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0086] This invention also provides a corresponding apparatus for the server management method, further enhancing the method's practicality. The apparatus can be described from both a functional module perspective and a hardware perspective. The server management apparatus provided by this invention is described below. This apparatus is used to implement the server management method provided by this invention. In this embodiment, the server management apparatus may include or be divided into one or more program modules. These program modules are stored in a storage medium and executed by one or more processors to complete the server management method disclosed in Embodiment 1. The program module referred to in this embodiment is a series of computer program instruction segments capable of performing a specific function, which is more suitable than the program itself for describing the execution process of the server management apparatus in the storage medium. The following description will specifically introduce the functions of each program module in this embodiment. The server management apparatus described below and the server management method described above can be referred to in correspondence.

[0087] From the perspective of functional modules, see Figure 7 , Figure 7 This is a structural diagram of the server management device provided in this embodiment under one specific implementation. The device may include:

[0088] The relationship building module 701 is used to generate business-implementation correspondence information for each user based on user attributes and server attributes, according to the implementation modules corresponding to various services of various types of servers; and to determine the implementation logic relationship between each implementation module and the implementation modules of adjacent server software versions based on the business-implementation correspondence information for each user.

[0089] The request implementation determination module 702 is used to, upon receiving a user's business implementation request, match the target business-implementation correspondence information according to the user attributes; determine the business implementation module that satisfies the user's business implementation request based on the target business-implementation correspondence information, the implementation logic relationship and the attributes of the user server, and generate the routing relationship between each business implementation module and the corresponding server attributes.

[0090] The encrypted sending module 703 is used to send the encrypted business implementation modules and the encrypted routing relationship to the user as the request processing result.

[0091] For example, in some embodiments of this example, the request implementation determination module 702 can also be used to: sequentially determine known implementation modules that implement each requested service in the target service-implementation correspondence information; when there is no target service implementation module that implements the target requested service in the target service-implementation correspondence information, if the user service implementation request includes a requirement to increase server compatibility, determine the highest version of the bridge implementation module corresponding to the target requested service based on the target service-implementation correspondence information; in the implementation logic relationship, determine each candidate implementation module of the next higher version of the bridge implementation module, determine the probability of each candidate implementation module implementing the target requested service based on different user difference information and / or different server difference information, and select the candidate implementation module with the highest probability as the target service implementation module; and use each known implementation module and the target service implementation module as the service implementation module that satisfies the user service implementation request.

[0092] For example, in some other embodiments of this embodiment, the above-mentioned request implementation determination module 702 can also be used to: sequentially determine known implementation modules that implement each requested service in the target service-implementation correspondence information; when there is no implementation module that implements the target requested service in the target service-implementation correspondence information, if the user service implementation request does not include the requirement to increase server compatibility, then determine the highest version of the bridge implementation module corresponding to the target requested service according to the target service-implementation correspondence information; in the implementation logic relationship, determine each candidate implementation module of the next higher version of the bridge implementation module, and determine the probability of each candidate implementation module implementing the target requested service based on different user difference information and / or different server difference information; and use each known implementation module and each candidate implementation module carrying the probability as the service implementation module that satisfies the user service implementation request.

[0093] For example, in some other embodiments of this embodiment, the request implementation determination module 702 can also be used to: sequentially determine the known implementation modules for each service to be required in the user service implementation request in the target service-implementation correspondence information; if the user service implementation request also includes a requirement for increased server compatibility, then determine each candidate implementation module of the next higher version of the known implementation module in the implementation logic relationship; determine the probability of each candidate implementation module implementing the corresponding service to be required based on different user difference information and / or different server difference information, and select the candidate implementation module with the highest probability as the compatible implementation module of the known implementation module; and use each known implementation module and its corresponding compatible implementation module as the service implementation module that satisfies the user service implementation request.

[0094] For example, in some other embodiments of this embodiment, the relationship construction module 701 can also be used to: obtain each server to be managed by the current user, classify each server to be managed according to server attributes; count the services of each type of server to be managed, obtain the implementation modules of each service, and form an implementation linked list of each implementation module of the same service; generate service-implementation correspondence information for each user according to the following: the same user includes multiple types of servers to be managed, the same type of server to be managed includes multiple services, and each service has a unique corresponding implementation linked list.

[0095] As an exemplary implementation of the above embodiments, the relationship construction module 701 can be further used to: generate a corresponding business module tree for each user based on the root node representing user attributes, each child node of the root node representing the attributes of the server to be managed, each child node representing a business, and the leaf node representing an implementation list, so as to represent the business-implementation correspondence information.

[0096] As another exemplary implementation of the above embodiments, the relationship construction module 701 can be further used to: obtain all implementation modules of the current business for each business; sort the implementation modules of the current business according to the version number or update time of each implementation module, and generate the implementation list of the current business according to the sorted implementation modules.

[0097] For example, in some other embodiments of this embodiment, the relationship construction module 701 can also be used to: traverse the business-implementation correspondence information of each user respectively, determine the target implementation module of the next-level version for each implementation module; obtain the target user and target server model corresponding to each target implementation module; and generate the implementation logic relationship between each implementation module and other implementation modules according to the following: the same implementation module corresponds to multiple users, each user corresponds to multiple server models, and each server model corresponds to one target implementation module.

[0098] As an exemplary implementation of the above embodiments, the relationship construction module 701 can be further used to: generate a corresponding implementation logic relationship tree for each implementation module based on the root node representing the implementation module, each child node of the root node representing user attributes, each child node representing the server model, and the leaf node representing the target implementation module, so as to represent the implementation logic relationship between the current implementation module and other implementation modules.

[0099] For example, in some other embodiments of this example, the encrypted sending module 703 can also be used to: concatenate the user's encrypted information with the user server's model name, and use the hash encrypted data of the user-model concatenation information as the user server's dedicated server information; concatenate the user's encrypted information with the module names of each service implementation module, and use the hash encrypted data of each user-module concatenation information as the dedicated implementation information of each service implementation module; generate a routing table that corresponds to each dedicated implementation information and each dedicated server based on each service implementation module and the corresponding user server; and package the user's encrypted information, the routing table, and each dedicated implementation information to generate a request processing result.

[0100] For example, in some other embodiments of this example, the request implementation determination module 702 may also be used to: in the implementation logic relationship, determine each upgrade candidate module for each implementation module of the business-implementation correspondence information for each user; based on the difference information of different users and / or the difference information of different servers, determine the probability that each upgrade candidate module is an upgrade version of the corresponding implementation module, and select the upgrade candidate module with the highest probability as the probability implementation module; update the corresponding business-implementation correspondence information according to the probability implementation module corresponding to each implementation module.

[0101] As an exemplary implementation of the above embodiments, the request implementation determination module 702 can also be used to: receive user compatibility feedback information; determine, based on the compatibility feedback information, that the target probability implementation module is an upgraded version of the corresponding implementation module, then increase the values ​​of the corresponding target user difference weight and target device difference weight, and simultaneously update the corresponding business-implementation correspondence information and implementation logic relationship; when it is determined, based on the compatibility feedback information, that the candidate implementation module implements the function of the target service to be requested, then increase the values ​​of the corresponding target user difference weight and target device difference weight, and simultaneously update the corresponding business-implementation correspondence information and implementation logic relationship; when it is determined, based on the compatibility feedback information, that the candidate implementation module implements the function of the target service to be requested, then increase the values ​​of the corresponding target user difference weight and target device difference weight, and simultaneously update the corresponding business-implementation correspondence information and implementation logic relationship.

[0102] The server management device mentioned above is described from the perspective of functional modules. Furthermore, the present invention also provides an electronic device, which is described from the perspective of hardware. Figure 8 This is a schematic diagram of the structure of an electronic device provided in one embodiment of the present invention. The electronic device includes a memory 801 and a processor 802. The memory 801 stores a computer program, and the processor 802 is configured to run the computer program to perform the steps in any of the above-described server management method embodiments.

[0103] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described server management method embodiments when it runs.

[0104] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0105] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described server management method embodiments.

[0106] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described server management method embodiments.

[0107] The foregoing has provided a detailed description of a server management method, electronic device, computer-readable storage medium, and computer program product provided by the present invention. The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. Whether the units and algorithm steps of the various examples described in the disclosed embodiments are executed in electronic hardware or computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, and such implementations should not be considered beyond the scope of the present invention. Several improvements and modifications can be made to the present invention without departing from its principles, and these improvements and modifications also fall within the protection scope of the present invention.

Claims

1. A server management method, characterized in that, include: Based on user attributes and server attributes, and according to the implementation modules corresponding to various services of various types of servers, the business-implementation correspondence information of each user is generated; based on the business-implementation correspondence information of each user, the implementation logic relationship between each implementation module and the implementation modules of adjacent server software versions is determined; When a user's business implementation request is received, the target business-implementation correspondence information is matched based on the user's attributes. Based on the target business-implementation correspondence information, the implementation logic relationship, and the attributes of the user server, determine the business implementation module that satisfies the user business implementation request, and generate the routing relationship between each business implementation module and the corresponding server attribute; The encrypted business implementation modules and the encrypted routing relationships are sent to the user as the request processing result.

2. The server management method according to claim 1, characterized in that, The user service implementation request includes multiple pending services. Based on the target service-implementation correspondence information, the implementation logic relationship, and the attributes of the user server, a service implementation module that satisfies the user service implementation request is determined, including: In the target service-implementation correspondence information, the known implementation modules that implement each service to be required are determined in sequence; If the target business implementation module for implementing the target business to be requested does not exist in the target business-implementation correspondence information, and if the user business implementation request includes a requirement to increase server compatibility, then the highest version of the bridge implementation module corresponding to the target business to be requested is determined according to the target business-implementation correspondence information. In the implementation logic relationship, each candidate implementation module of the next-level version of the bridge implementation module is determined. Based on different user difference information and / or different server difference information, the probability of each candidate implementation module implementing the target service to be requested is determined, and the candidate implementation module with the highest probability is selected as the target service implementation module. Each known implementation module and the target business implementation module are used as the business implementation module to satisfy the user's business implementation request.

3. The server management method according to claim 1, characterized in that, The user service implementation request includes multiple pending services. Based on the target service-implementation correspondence information, the implementation logic relationship, and the attributes of the user server, a service implementation module that satisfies the user service implementation request is determined, including: In the target service-implementation correspondence information, the known implementation modules that implement each service to be required are determined in sequence; If there is no implementation module for the target service to be requested in the target service-implementation correspondence information, and if the user service implementation request does not include the requirement to increase server compatibility, then the highest version of the bridge implementation module corresponding to the target service to be requested is determined according to the target service-implementation correspondence information. In the implementation logic relationship, each candidate implementation module of the next-level upgrade of the bridge implementation module is determined, and based on different user difference information and / or different server difference information, the probability of each candidate implementation module implementing the target demand service is determined; Each known implementation module and each candidate implementation module carrying a probability are used as the business implementation module to satisfy the user's business implementation request.

4. The server management method according to claim 1, characterized in that, Based on the target service-implementation correspondence information, the implementation logic relationship, and the attributes of the user server, determine the service implementation module that satisfies the user service implementation request, including: In the target service-implementation correspondence information, the known implementation modules for each service to be required in the user service implementation request are determined sequentially; If the user service implementation request also includes a requirement to increase server compatibility, then in the implementation logic relationship, each candidate implementation module for the next higher version of the known implementation module is determined; Based on the differences between different users and / or different servers, determine the probability that each candidate implementation module will implement the corresponding business requirement, and select the candidate implementation module with the highest probability as the compatible implementation module of the known implementation module. Each known implementation module and its corresponding compatible implementation module are used as the business implementation module to satisfy the user's business implementation request.

5. The server management method according to claim 1, characterized in that, Based on user attributes and server attributes, and according to the implementation modules corresponding to various services on various types of servers, business-implementation mapping information is generated for each user, including: Retrieve all servers to be managed for the current user, and categorize them according to their attributes; The business of each type of server to be managed is counted separately, the implementation modules of each business are obtained, and the implementation modules of the same business are combined into an implementation linked list. Based on the premise that a single user includes multiple types of servers to be managed, a single type of server to be managed includes multiple services, and each service has a unique corresponding implementation linked list, generate the service-implementation correspondence information for each user.

6. The server management method according to claim 5, characterized in that, Generate business-implementation relationship information for each user, including: Based on the root node representing user attributes, each child node of the root node representing the attributes of the server to be managed, each child node's child node representing a business, and the leaf nodes representing an implementation linked list, a corresponding business module tree is generated for each user to represent the business-implementation correspondence information.

7. The server management method according to claim 5, characterized in that, The implementation modules for the same business are grouped into an implementation linked list, including: For each business, obtain all implementation modules of the current business; Based on the version number or update time of each implementation module, the implementation modules of the current service are sorted, and an implementation linked list of the current service is generated according to the sorted implementation modules.

8. The server management method according to claim 1, characterized in that, Based on the business-implementation correspondence information of each user, determine the implementation logic relationship between each implementation module and the implementation modules of adjacent server software versions, including: Iterate through the business-implementation relationship information of each user to determine the target implementation module for each implementation module to be upgraded to the next level. Obtain the target user and target server model corresponding to each target implementation module; Based on the principle that the same implementation module corresponds to multiple users, each user corresponds to multiple server models, and each server model corresponds to one target implementation module, the implementation logic relationship between each implementation module and other implementation modules is generated respectively.

9. The server management method according to claim 8, characterized in that, Generate the implementation logic relationships between each implementation module and other implementation modules, including: Based on the root node representing the implementation module, each child node of the root node representing user attributes, each child node's child node representing the server model, and the leaf nodes representing the target implementation module, a corresponding implementation logic relationship tree is generated for each implementation module to represent the implementation logic relationship between the current implementation module and other implementation modules.

10. The server management method according to claim 1, characterized in that, The encrypted service implementation modules and the encrypted routing relationships include: The encrypted information of the user is concatenated with the model name of the user server, and the hashed encrypted data of the user-model concatenation information is used as the exclusive server information of the user server. The encrypted information of the user is concatenated with the module name of each business implementation module, and the hash encrypted data of each user-module concatenation information is used as the exclusive implementation information of each business implementation module; Based on each business implementation module and its corresponding user server, a routing table is generated to show the correspondence between each dedicated implementation information and each dedicated server. The encrypted information of the user, the routing table, and the specific implementation information are packaged to generate a request processing result.

11. The server management method according to any one of claims 1 to 10, characterized in that, Also includes: In the implementation logic relationship, each implementation module is assigned to a business-implementation correspondence information for each user, and each upgrade candidate module for the next-level version is determined. Based on the differences between different users and / or different servers, determine the probability that each upgrade candidate module is an upgraded version of the corresponding implementation module, and select the upgrade candidate module with the highest probability as the probability implementation module; Based on the probability of each implementation module, the corresponding business-implementation relationship information is updated.

12. The server management method according to claim 11, characterized in that, The user difference information is a user difference weight, the server difference information is a machine model difference weight, and it also includes: Receive compatibility feedback from users; When the target probability implementation module is determined to be an upgraded version of the corresponding implementation module based on the compatibility feedback information, the values ​​of the corresponding target user difference weight and target device difference weight are increased, and the corresponding business-implementation correspondence information and implementation logic relationship are updated. When it is determined from the compatibility feedback information that the candidate implementation module has implemented the function of the target service to be requested, the values ​​of the corresponding target user difference weight and target device difference weight are increased, and the corresponding service-implementation correspondence information and implementation logic relationship are updated. When it is determined from the compatibility feedback information that the candidate implementation module has implemented the function of the target service, the values ​​of the corresponding target user difference weight and target device difference weight are increased, and the corresponding service-implementation correspondence information and implementation logic relationship are updated.

13. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the server management method as described in any one of claims 1 to 12.

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

15. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the server management method according to any one of claims 1 to 12.

Images