Component processing method and device based on cloud environment, electronic equipment and storage medium

Abstract

The invention provides a cloud environment-based component processing method and device, electronic equipment and a storage medium. According to the method and the device, operation and maintenance personnel are supported to provide hot repair for the identified component with the risk, and a flexible mode is provided for developers to expand and / or replace versions of the components on the nodes in the service resource pool, so that the components in the service resource pool are more maintainable, and the user experience is improved. The assembly maintenance efficiency of operation and maintenance personnel can be greatly improved, and time cost is saved. According to the application, the versions of the components in the nodes in the service resource pool are repaired, so that the versions of the same type of components in the nodes in the service resource pool can be kept consistent, or the versions of the various types of components in the same node in the service resource pool can be compatible. According to the invention, the performance of cooperation between various types of components in the same node in the service resource pool can be improved, and efficient and safe operation of the node is maintained.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and in particular to a component processing method, device, electronic device and storage medium based on a cloud environment. Background Art

[0002] With the rapid development and popularization of cloud computing, the number of nodes in cloud clusters of cloud vendors is increasing. In order to ensure the high performance, high availability, security and stability of cloud clusters, cloud vendors establish resource pools of cloud clusters in various places. Resource pools can be regarded as sub-clusters in cloud clusters.

[0003] However, as the number of resource pools in the cloud cluster continues to increase and the number of nodes in each resource pool continues to expand, the version differences of components in different servers in different resource pools are becoming increasingly larger after continuous iteration of versions. Components in nodes include computing components, storage components, and network components, etc. Summary of the invention

[0004] The present application illustrates a component processing method, device, electronic device and storage medium based on a cloud environment.

[0005] In a first aspect, the present application shows a component processing method based on a cloud environment, which is applied to a control node in a central resource pool in a cloud cluster, and the method includes:

[0006] Obtain a hot fix plug-in script submitted by an operation and maintenance personnel, the hot fix plug-in script carrying the identifier of the component to be repaired, the target version of the component to be repaired, the identifier of the resource pool to be repaired in the cloud cluster, and the address of the node to be repaired in the resource pool to be repaired; the node to be repaired has the component to be repaired, and the current version of the component to be repaired in the node to be repaired is different from the target version;

[0007] According to the identifier of the resource pool to be repaired in the hot repair plug-in script, obtain the address of the socks5 server in the resource pool to be repaired;

[0008] According to the address of the socks5 server in the resource pool to be repaired, determine the first communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be repaired;

[0009] According to the address of the node to be repaired, a hot repair plug-in script is sent to the node to be repaired via the first communication connection, the second communication connection and the third communication connection, the second communication connection being the communication connection established between the control node in the central resource pool and the socks5 client in the central resource pool; the third communication connection being the communication connection established between the socks5 server in the resource pool to be repaired and the node to be repaired in the resource pool to be repaired; so that the node to be repaired obtains the target version of the component to be repaired in the component repository according to the identifier of the component to be repaired in the hot repair plug-in script and the target version of the component to be repaired, and upgrades the current version of the component to be repaired in the node to be repaired to the target version of the component to be repaired.

[0010] In a second aspect, the present application shows a component processing method based on a cloud environment, which is applied to a control node in a central resource pool in a cloud cluster, and the method includes:

[0011] Obtain the component version collection instruction submitted by the operation and maintenance personnel. The component version collection instruction carries the identifier of the resource pool to be collected in the cloud cluster and the address of the node to be collected in the resource pool to be collected;

[0012] According to the identifier of the resource pool to be collected in the component version collection instruction, obtain the address of the socks5 server in the resource pool to be collected;

[0013] Determine, according to the address of the socks5 server in the resource pool to be collected, a fourth communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be collected;

[0014] According to the address of the node to be collected, a component version collection instruction is sent to the node to be collected via the fourth communication connection, the second communication connection and the fifth communication connection; so that the node to be collected obtains the identifier of each component in the node to be collected and the current version of each component according to the component version collection instruction; the identifier of each component in the node to be collected and the current version of each component are sent to the management and control node via the fourth communication connection, the second communication connection and the fifth communication connection; the second communication connection is a communication connection established between the management and control node in the central resource pool and the socks5 client in the central resource pool; the fifth communication connection is a communication connection established between the socks5 server in the resource pool to be collected and the node to be collected in the resource pool to be collected;

[0015] The identifiers of the components in the node to be collected and the current versions of the components are received and sent by the node to be collected via the fourth communication connection, the second communication connection and the fifth communication connection.

[0016] In a third aspect, the present application shows a component processing method based on a cloud environment, which is applied to a control node in a central resource pool in a cloud cluster, and the method includes:

[0017] When a new resource pool has been established in the cloud cluster, obtain node information of a new node in the new resource pool;

[0018] Obtaining a stable version of a component baseline applicable to node information of a new node in a new resource pool, wherein the stable version of the component baseline includes identifiers of various components required in the new node in the new resource pool and stable component versions of various components;

[0019] Establishing a sixth communication connection between the socks5 client in the central resource pool and the socks5 server in the new resource pool;

[0020] According to the address of the new node in the new resource pool, the component baseline of the stable version is sent to the new node in the new resource pool via the sixth communication connection, the second communication connection and the seventh communication connection; the second communication connection is the communication connection established between the control node in the central resource pool and the socks5 client in the central resource pool; the seventh communication connection is the communication connection established between the socks5 server in the new resource pool and the new node in the new resource pool;

[0021] So that the new node in the new resource pool can obtain the components corresponding to the stable component versions of the components required in the new node in the component warehouse according to the identifiers of the components required in the new node in the stable version of the component baseline, and deploy the obtained components in the new node in the new resource pool respectively.

[0022] In a fourth aspect, the present application shows a component processing method based on a cloud environment, which is applied to a node to be repaired in a resource pool to be repaired in a cloud cluster, and the method includes:

[0023] A hot repair plug-in script is received, which is sent by the control node in the central resource pool in the cloud cluster to the node to be repaired via the first communication connection, the second communication connection and the third communication connection according to the address of the node to be repaired; the hot repair plug-in script is submitted by the operation and maintenance personnel in the control node, and the hot repair plug-in script carries the identifier of the component to be repaired, the target version of the component to be repaired, the identifier of the resource pool to be repaired and the address of the node to be repaired in the resource pool to be repaired in the cloud cluster; the node to be repaired has the component to be repaired, and the current version of the component to be repaired in the node to be repaired is different from the target version; the first communication connection is the socks5 in the central resource pool. The communication connection established between the client and the socks5 server in the resource pool to be repaired; the second communication connection is the communication connection established between the control node in the central resource pool and the socks5 client in the central resource pool; the third communication connection is the communication connection established between the socks5 server in the resource pool to be repaired and the node to be repaired in the resource pool to be repaired; the first communication connection is determined by the control node according to the address of the socks5 server in the resource pool to be repaired, and the address of the socks5 server in the resource pool to be repaired is obtained by the control node according to the identifier of the resource pool to be repaired in the hot repair plug-in script;

[0024] According to the identifier of the component to be repaired in the hot repair plug-in script and the target version of the component to be repaired, the component to be repaired of the target version is obtained in the component repository;

[0025] The current version of the component to be repaired in the node to be repaired is upgraded to the component to be repaired of the target version.

[0026] In a fifth aspect, the present application shows a component processing method based on a cloud environment, which is applied to a node to be collected in a resource pool to be collected in a cloud cluster, and the method includes:

[0027] Receive a component version collection instruction sent by the control node in the central resource pool in the cloud cluster via the fourth communication connection, the second communication connection and the fifth communication connection according to the address of the node to be collected; the component version collection instruction is submitted by the operation and maintenance personnel in the control node, and the component version collection instruction carries the identifier of the resource pool to be collected in the cloud cluster and the address of the node to be collected in the resource pool to be collected; the fourth communication connection is an established communication connection between the socks5 client in the central resource pool and the socks5 server in the resource pool to be collected; the second communication connection is an established communication connection between the control node in the central resource pool and the socks5 client in the central resource pool; the fifth communication connection is an established communication connection between the socks5 server in the resource pool to be collected and the node to be collected in the resource pool to be collected; the fourth communication connection is determined by the control node according to the address of the socks5 server in the resource pool to be collected, and the address of the socks5 server in the resource pool to be collected is obtained by the control node according to the identifier of the resource pool to be collected in the component version collection instruction;

[0028] Obtain the identifier of each component in the node to be collected and the current version of each component according to the component version collection instruction;

[0029] The identification of each component in the node to be collected and the current version of each component are sent to the management and control node via the fourth communication connection, the second communication connection and the fifth communication connection, so that the management and control node receives the identification of each component in the node to be collected and the current version of each component.

[0030] In a sixth aspect, the present application shows a component processing method based on a cloud environment, which is applied to a new node in a new resource pool in a cloud cluster, and the method includes:

[0031] Receive a component baseline of a stable version of node information applicable to a new node in a new resource pool, which is sent by the control node in the central resource pool in the cloud cluster via the sixth communication connection, the second communication connection, and the seventh communication connection according to the address of the new node in the new resource pool; the sixth communication connection is a communication connection between the socks5 client in the central resource pool and the socks5 server in the new resource pool established by the control node; the second communication connection is an established communication connection between the control node in the central resource pool and the socks5 client in the central resource pool; the seventh communication connection is an established communication connection between the socks5 server in the new resource pool and the new node in the new resource pool, and the component baseline of the stable version includes the identifiers of each component required in the new node in the new resource pool and the stable component versions of each component; the component baseline of the stable version is obtained by the control node after obtaining the node information of the new node in the new resource pool when a new resource pool has been established in the cloud cluster;

[0032] In the component repository, according to the identifiers of the components required in the new node in the component baseline of the stable version, the components corresponding to the stable component versions of the components required in the new node are obtained;

[0033] Deploy the acquired components in new nodes in the new resource pool.

[0034] In a seventh aspect, the present application illustrates an electronic device, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the method described in any of the above aspects.

[0035] In an eighth aspect, the present application illustrates a non-temporary computer-readable storage medium, which, when instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to execute a method as described in any of the above aspects.

[0036] In a ninth aspect, the present application illustrates a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to execute the method described in any of the above aspects.

[0037] The technical solution provided by this application may have the following beneficial effects:

[0038] This application supports operation and maintenance personnel to provide hot fixes for components that are identified to be at risk, and provides developers with a flexible way to expand and / or replace the versions of components on nodes in the service resource pool, so that the components in the service resource pool are more maintainable, which can greatly improve the efficiency of operation and maintenance personnel in maintaining components and save time costs.

[0039] By repairing the versions of components in nodes in the service resource pool according to the present application, the versions of components of the same type in each node in the service resource pool can be kept consistent, or the versions of components of different types in the same node in the service resource pool can be made compatible.

[0040] Alternatively, the appropriate security version selected for the components in the node can be deployed, updated or upgraded in a timely manner according to actual needs. Known security vulnerabilities can be indirectly repaired by changing the component version, reducing potential security risks, thereby improving the performance of coordination between various types of components in the same node in the service resource pool and maintaining efficient and secure operation of the node.

[0041] Through this application, it is supported to collect the versions of each component in each node in each service resource pool in the cloud cluster through the control node of the central resource pool in the cloud cluster, so that the operation and maintenance personnel can comprehensively analyze the version status of each component on each node in each service resource pool, so that the operation and maintenance personnel can determine whether there are compatibility issues between the versions of each component on any node in any service resource pool, so as to facilitate immediate processing when compatibility issues are found between the versions of each component on the same node, prevent node crashes or failures caused by version incompatibility (mismatch or conflict), thereby ensuring the continuous and stable operation of the service.

[0042] Through this application, when deploying various components for new nodes in a new resource pool, stable versions of components can be deployed for new nodes in the new resource pool. Stable versions of components can be understood as the compatibility and adaptability between the versions of various components in the new node, so that the stability of the cooperation between various components in the new node is strong, and the function of any component will not be affected, thereby improving reliability and reducing the subsequent maintenance costs of the versions of various components deployed for new nodes in the new resource pool. The purpose of quickly building a new resource pool in a cloud cluster is also achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 It is a schematic diagram of a component processing system based on a cloud environment of the present application.

[0044] Figure 2 It is a step flow chart of a component processing method based on a cloud environment of the present application.

[0045] Figure 3 It is a step flow chart of a component processing method based on a cloud environment of the present application.

[0046] Figure 4 It is a step flow chart of a component processing method based on a cloud environment of the present application.

[0047] Figure 5 It is a block diagram of an electronic device of the present application.

[0048] Figure 6 It is a block diagram of an electronic device of the present application. DETAILED DESCRIPTION

[0049] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0050] The versions of IaaS (Infrastructure as a Service) layer components in nodes in different resource pools vary greatly. The versions of network components and storage components in the same node may not be the same, and there may be compatibility issues between network components and storage components of different versions, which may cause instability in the node during operation. For example, a certain version (such as V1.0) of the network component may be incompatible with another version (such as V2.0) of the storage component, resulting in node network failure and affecting the node's data transmission.

[0051] Secondly, different versions of components may differ in performance optimization, resource utilization, etc. If they are mixed, they may restrict each other, resulting in the problem of the short board of the barrel, which in turn leads to poor overall performance of the resource pool.

[0052] If the version of a component in the IaaS layer of the resource pool is low, the low-version component is more likely to have security vulnerabilities, which may be exploited by hackers to attack the nodes in the resource pool, resulting in the inability to effectively control security risks.

[0053] Component version confusion increases the management complexity of nodes in the resource pool. When administrators configure the versions of various components in the resource pool in a unified manner, they need to handle more versions of components at the same time, which may make the configuration task cumbersome and error-prone, making the configuration task more difficult.

[0054] Since component version confusion may lead to problems such as poor overall performance of the resource pool and increased security risks, cloud vendors may need to invest more resources to solve these problems, including purchasing new hardware equipment for the resource pool, upgrading software versions, etc., thereby increasing costs.

[0055] To this end, the solution of this application is proposed.

[0056] Before introducing the solution of the present application, the technical terms that may be involved in the present application are first explained.

[0057] Socks5 is a set of open software standards developed by the Internet project team to handle network security issues. Socks provides traffic and security management for information entering and leaving the corporate network between the Internet server and the client.

[0058] Socks is a security standard related to the Socket port of TCP / IP (Transmission Control Protocol / Internet Protocol). Generally, firewall systems act on the seventh layer of the OSI (Open System Interconnect) model, which is the application layer, like gateways, to regulate the high-level protocols of TCP / IP. Socks acts on the fifth layer of the OSI model, which is the session layer. Socks5 supports peer connections, so that two peers can establish a connection directly without going through other proxy servers, which improves the efficiency of network transmission. It is a solution that provides security services from session layer to session layer and is not affected by changes in high-level applications.

[0059] Reference Figure 1 , shows a structural block diagram of a component processing system based on a cloud environment of the present application, wherein the system includes:

[0060] Central resource pool and multiple service resource pools.

[0061] A service resource pool has multiple nodes, which can be physical servers or virtual machines installed on servers in the service.

[0062] The service resource pool is used to provide cloud services externally. For example, the service resource pool can provide cloud services externally based on the nodes therein.

[0063] The central resource pool is used to manage and control each service resource pool. For example, it is used to collect the versions of components in the nodes in the service resource pool, to deploy the required versions of components in the nodes in the service resource pool, to update or unify the versions of components in the nodes in the service resource pool, etc.

[0064] There are multiple nodes in the central resource pool, and one of the nodes has a socks5 client.

[0065] Any node in a service resource pool has a socks5 server.

[0066] The socks5 clients in the central resource pool establish communication connections with the socks5 servers in each service resource pool.

[0067] Communication connections are established between the socks5 client in the central resource pool and other nodes in the central resource pool (other nodes are nodes where the socks5 client is not located).

[0068] A communication connection is established between the socks5 server in any service resource pool and other nodes in the service resource pool (other nodes are nodes where the socks5 server is not located).

[0069] The socks5 client in the central resource pool and the socks5 server in any service resource pool achieve secure communication by establishing connection, performing identity authentication, forwarding data and closing connection.

[0070] The socks5 client in the central resource pool in the cloud cluster can send the public key of the socks5 client to each service resource pool in the cloud cluster to achieve mutual trust access.

[0071] In this way, any node in the central resource pool and any node in any service resource pool can exchange data with each other through the three established communication connections mentioned above.

[0072] In this way, the network interconnection of nodes in different resource pools is achieved, which can reduce the network transmission cost; under limited network connection resources, a single connection is reused to complete the network interconnection of nodes in different resource pools.

[0073] There is no need to establish direct communication connections between nodes in different resource pools, which can save network resources.

[0074] The interconnection between a Socks5 server in a service resource pool and the node where a non-Socks5 server is located in the service resource pool is a natural interconnection between intranet machines. Network transmission through the internal network card does not consume bandwidth, thereby saving bandwidth.

[0075] The socks5 client in the central resource pool can also be dynamically destroyed according to actual needs, and then dynamically created according to actual needs, and then establish a communication connection between the dynamically created socks5 client and the socks5 server in the service resource pool that needs to be connected, so as to improve flexibility and avoid waste of resources.

[0076] In the present application, components or other applications on each node in each resource pool in the cloud cluster may adopt a microservice architecture to improve overall scalability and high availability.

[0077] The nodes in the resource pool can be Kubernetes-based nodes.

[0078] Reference Figure 2 , showing a step flow chart of a component processing method based on a cloud environment of the present application.

[0079] Applicable to the management and control nodes in the central resource pool in the cloud cluster and the nodes to be repaired in the resource pool to be repaired in the cloud cluster.

[0080] The control node in the central resource pool is one of the multiple nodes in the central resource pool except the node where the socks5 client is located.

[0081] The resource pool to be repaired is one of the service resource pools in the cloud cluster.

[0082] The node to be repaired in the resource pool to be repaired is at least one node among the multiple nodes in the resource pool to be repaired except the node where the socks5 server is located.

[0083] Among them, the method includes:

[0084] In step S101, the control node obtains a hot fix plug-in script submitted by an operation and maintenance personnel, and the hot fix plug-in script carries the identifier of the component to be repaired, the target version of the component to be repaired, the identifier of the resource pool to be repaired in the cloud cluster, and the address of the node to be repaired in the resource pool to be repaired. The node to be repaired has a component to be repaired, and the current version of the component to be repaired in the node to be repaired is different from the target version.

[0085] A node can have multiple types of components, such as storage components, network components, and computing components. Each component has its own version. Different types of components have different identifiers.

[0086] The component to be repaired may be a component of at least one type among a plurality of types in the node to be repaired. For example, the component to be repaired may be at least one of a storage component, a network component, and a computing component.

[0087] Different nodes have different addresses, and the address of a node may be an IP (Internet Protocol) address of the node. Different resource pools have different identifiers.

[0088] Operation and maintenance personnel can obtain the versions of each component in each node in each service resource pool through the management and control node, and evaluate whether the versions of each component in the same node are compatible.

[0089] If the operation and maintenance personnel believe that the current version of a component (a component may be one or two of the storage component, network component, and computing component) in a node in a service resource pool is incompatible with the current versions of other components in the node, and believe that after the current version of the component in the node is upgraded to the target version, the target version of the component is compatible with the current versions of other components in the node, then it means that the version of the component in the node in the service resource pool needs to be upgraded from the current version to the target version.

[0090] At this time, the service resource pool is a resource pool to be repaired, the node is a node to be repaired, and the component is a component to be repaired.

[0091] The operation and maintenance personnel can create a hot fix plug-in script through their client, and submit the hot fix plug-in script to the control node in the central resource pool through their client. In this way, the control node can obtain the hot fix plug-in script submitted by the operation and maintenance personnel through their client.

[0092] The versions of each component in the node to be repaired in the resource pool to be repaired are the current versions.

[0093] The way in which the control node obtains the version of each component in each node in each service resource pool can be seen later. Figure 3 The illustrated embodiment will not be described in detail here.

[0094] The hot fix plug-in script may be generated based on an extension mechanism of SPI (Service Provider Interface).

[0095] In step S102, the management and control node obtains the address of the socks5 server in the resource pool to be repaired according to the identifier of the resource pool to be repaired in the hot repair plug-in script.

[0096] In this application, for any service resource pool in the cloud cluster, a communication connection between the socks5 client in the central resource pool in the cloud cluster and the socks5 server in the service resource pool will be established in advance. The communication connection is bound to the address of the socks5 client in the central resource pool and the address of the socks5 server in the service resource pool.

[0097] The address of the socks5 client in the central resource pool may be the IP address of the socks5 client in the central resource pool.

[0098] The address of the socks5 server in the service resource pool may be the IP address of the socks5 server in the service resource pool.

[0099] The management and control node can form a corresponding table entry with the identifier of the service resource pool and the address of the socks5 server in the service resource pool, and store it in the corresponding relationship between the identifier of the service resource pool and the address of the socks5 server in the service resource pool. The corresponding relationship can be located in the management and control node.

[0100] The same is true for every other service resource pool in the cloud cluster.

[0101] In this way, in this step, the management and control node can extract the identifier of the resource pool to be repaired in the hot repair plug-in script, and then search for the address of the socks5 server corresponding to the identifier of the resource pool to be repaired in the correspondence between the identifier of the service resource pool and the address of the socks5 server in the service resource pool, which is the address of the socks5 server in the resource pool to be repaired.

[0102] In step S103, the management and control node determines the first communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be repaired according to the address of the socks5 server in the resource pool to be repaired.

[0103] As mentioned above, the "communication connection between the socks5 client in the central resource pool and the socks5 server in any service resource pool" has been established in advance, and the "communication connection between the socks5 client in the central resource pool and the socks5 server in any service resource pool" is bound to the address of the socks5 client in the central resource pool and the address of the socks5 server in the service resource pool.

[0104] In this way, the communication connection bound to the address of the socks5 server in the resource pool to be repaired can be determined in the communication connections between the socks5 client in the central resource pool and the socks5 server in each service resource pool in the cloud cluster, that is, the first communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be repaired.

[0105] In step S104, the management and control node sends a hot repair plug-in script to the node to be repaired via the first communication connection, the second communication connection, and the third communication connection according to the address of the node to be repaired.

[0106] On the logical side, there are: a socks5 client in the central resource pool and a socks5 server in the resource pool to be repaired between the control node and the node to be repaired.

[0107] A first communication connection has been established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be repaired. A second communication connection has been established between the control node in the central resource pool and the socks5 client in the central resource pool. A third communication connection has been established between the socks5 server in the resource pool to be repaired and the node to be repaired in the resource pool to be repaired. The first communication connection, the second communication connection and the third communication connection are all communication connections that have been successfully established in advance and can be used directly.

[0108] In this way, the management and control node can send the hot repair plug-in script to the node to be repaired via the first communication connection, the second communication connection, and the third communication connection according to the address of the node to be repaired.

[0109] Different nodes have different addresses.

[0110] In step S105, the node to be repaired receives a hot repair plug-in script sent by the management and control node in the central resource pool in the cloud cluster via the first communication connection, the second communication connection and the third communication connection according to the address of the node to be repaired.

[0111] In step S106, the node to be repaired obtains the target version of the component to be repaired from the component repository according to the identifier of the component to be repaired in the hot repair plug-in script and the target version of the component to be repaired.

[0112] The component warehouse stores various versions of components that need to be used by various nodes in various resource pools in the cloud cluster developed in the historical process. The component warehouse stores component entities (implementations), component applications, etc.

[0113] Each component in the component warehouse is marked by its identification and version. For example, in one embodiment, the component warehouse stores: the corresponding relationship between the component, the identification of the component and the version of the component.

[0114] Thus, in this step, the component that corresponds to both the identifier of the component to be repaired in the hot fix plug-in script and the target version of the component to be repaired can be searched in the correspondence between the component, the identifier of the component and the version of the component, and used as the component to be repaired of the target version.

[0115] In step S107, the node to be repaired upgrades the component to be repaired of the current version in the node to be repaired to the component to be repaired of the target version.

[0116] For example, according to the identifier of the component to be repaired in the hot repair plug-in script, the current version of the component to be repaired is searched in the node to be repaired, and the current version of the component to be repaired is uninstalled in the node to be repaired, and then the target version of the component to be repaired is installed in the node to be repaired, so as to upgrade the current version of the component to be repaired in the node to be repaired to the target version of the component to be repaired.

[0117] This application supports operation and maintenance personnel to provide hot fixes for components that are identified to be at risk, and provides developers with a flexible way to expand and / or replace the versions of components on nodes in the service resource pool, so that the components in the service resource pool are more maintainable, which can greatly improve the efficiency of operation and maintenance personnel in maintaining components and save time costs.

[0118] By repairing the versions of components in nodes in the service resource pool according to the present application, the versions of components of the same type in each node in the service resource pool can be kept consistent, or the versions of components of different types in the same node in the service resource pool can be made compatible.

[0119] Alternatively, the appropriate security version selected for the components in the node can be deployed, updated or upgraded in a timely manner according to actual needs. Known security vulnerabilities can be indirectly repaired by changing the component version, reducing potential security risks, thereby improving the performance of coordination between various types of components in the same node in the service resource pool and maintaining efficient and secure operation of the node.

[0120] In another embodiment of the present application, the hot repair plug-in script also carries the time to be repaired. In this way, before the node to be repaired upgrades the current version of the component to be repaired in the node to be repaired to the component to be repaired of the target version, it is determined whether the current moment of the resource pool to be repaired has reached the time to be repaired. In the case where the current moment of the resource pool to be repaired reaches the time to be repaired, the node to be repaired executes step S107 again: upgrading the current version of the component to be repaired in the node to be repaired to the component to be repaired of the target version. Through this embodiment, the current version of the component to be repaired in the node to be repaired can be upgraded to the component to be repaired of the target version at a specific moment, which improves the flexibility of the upgrade and improves the maintainability of the component.

[0121] In another embodiment of the present application, after the control node sends the hot repair plug-in script to the node to be repaired via the first communication connection, the second communication connection, and the third communication connection according to the address of the node to be repaired, the method further includes:

[0122] The node to be repaired upgrades the current version of the component to be repaired in the node to be repaired to the target version of the component to be repaired, and the node to be repaired obtains the version upgrade result of the component to be repaired in the node to be repaired. The version upgrade result is sent to the management and control node via the first communication connection, the second communication connection, and the third communication connection.

[0123] The management and control node receives a version upgrade result of a component to be repaired in the node to be repaired, which is sent by the node to be repaired via the first communication connection, the second communication connection, and the third communication connection.

[0124] The version upgrade result is sent to the client of the operation and maintenance personnel, so that the client of the operation and maintenance personnel can display the version upgrade result and the operation and maintenance personnel can view the version upgrade result.

[0125] If the operation and maintenance personnel believe that there are no errors in the version upgrade result, they can enter a confirmation operation for the version upgrade result displayed on the operation and maintenance personnel's client. The operation and maintenance personnel's client generates a confirmation instruction for the version upgrade result based on the confirmation operation and sends a confirmation instruction for the version upgrade result to the management and control node.

[0126] The management and control node can receive a confirmation instruction for the version upgrade result, and then obtain the repaired version of each component in the node to be repaired according to the confirmation instruction for the version upgrade result; generate a component baseline according to the repaired version of each component in the node to be repaired to achieve the sealing of the repaired version of each component in the node to be repaired, and then the version upgrade / optimization / repair of each component in the node to be repaired is upgraded / optimized / repaired based on the component baseline.

[0127] The component baseline may include: the identifiers and versions of each component in the node to be repaired, and may also include the address of the node to be repaired. Further, it may also include the identifier of the resource pool to be repaired. Different nodes have different addresses, and different resource pools have different identifiers.

[0128] Reference Figure 3 , shows a flow chart of the steps of a component processing method based on a cloud environment of the present application. Applied to the control nodes in the central resource pool in the cloud cluster and the nodes to be collected in the resource pool to be collected in the cloud cluster.

[0129] The control node in the central resource pool is one of the multiple nodes in the central resource pool except the node where the socks5 client is located.

[0130] The resource pool to be collected is one of the service resource pools in the cloud cluster.

[0131] The node to be collected in the resource pool to be collected is at least one node among the multiple nodes in the resource pool to be collected except the node where the socks5 server is located.

[0132] Among them, the method includes:

[0133] In step S201, the control node obtains a component version collection instruction submitted by an operation and maintenance personnel, where the component version collection instruction carries an identifier of a resource pool to be collected in the cloud cluster and an address of a node to be collected in the resource pool to be collected.

[0134] When the operation and maintenance personnel need to obtain the versions of each component in each node in each service resource pool through the control node and evaluate whether the versions of each component in the same node are compatible, the operation and maintenance personnel can make a component version collection instruction through their client and submit the component version collection instruction to the control node in the central resource pool through their client. In this way, the control node can obtain the component version collection instruction submitted by the operation and maintenance personnel through their client.

[0135] The resource pool to be collected may be at least one service resource pool among multiple service resource pools in the cloud cluster, and the node to be collected in the resource pool to be collected may be at least one node among multiple nodes in the resource pool to be collected.

[0136] In step S202, the management and control node obtains the address of the socks5 server in the resource pool to be collected according to the identifier of the resource pool to be collected in the component version collection instruction.

[0137] In this application, for any service resource pool in the cloud cluster, a communication connection between the socks5 client in the central resource pool in the cloud cluster and the socks5 server in the service resource pool will be established in advance. The communication connection is bound to the address of the socks5 client in the central resource pool and the address of the socks5 server in the service resource pool.

[0138] The address of the socks5 client in the central resource pool may be the IP address of the socks5 client in the central resource pool.

[0139] The address of the socks5 server in the service resource pool may be the IP address of the socks5 server in the service resource pool.

[0140] The management and control node can form a corresponding table entry with the identifier of the service resource pool and the address of the socks5 server in the service resource pool, and store it in the corresponding relationship between the identifier of the service resource pool and the address of the socks5 server in the service resource pool. The corresponding relationship can be located in the management and control node.

[0141] The same is true for every other service resource pool in the cloud cluster.

[0142] In this way, in this step, the management and control node can extract the identifier of the resource pool to be collected in the component version collection instruction, and then search for the address of the socks5 server corresponding to the identifier of the resource pool to be collected in the correspondence between the identifier of the service resource pool and the address of the socks5 server in the service resource pool, which is the address of the socks5 server in the resource pool to be collected.

[0143] In step S203, the management and control node determines the fourth communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be collected according to the address of the socks5 server in the resource pool to be collected.

[0144] As mentioned above, the "communication connection between the socks5 client in the central resource pool and the socks5 server in any service resource pool" has been established in advance, and the "communication connection between the socks5 client in the central resource pool and the socks5 server in any service resource pool" is bound to the address of the socks5 client in the central resource pool and the address of the socks5 server in the service resource pool.

[0145] In this way, the communication connection bound to the address of the socks5 server in the resource pool to be collected can be determined in the communication connections between the socks5 client in the central resource pool and the socks5 server in each service resource pool in the cloud cluster, that is, the fourth communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be collected.

[0146] In step S204, the management and control node sends a component version collection instruction to the node to be collected via the fourth communication connection, the second communication connection, and the fifth communication connection according to the address of the node to be collected.

[0147] On the logical side, there are: socks5 client in the central resource pool and socks5 server in the resource pool to be collected between the management and control node and the node to be collected.

[0148] A fourth communication connection has been established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be collected. A second communication connection has been established between the control node in the central resource pool and the socks5 client in the central resource pool. A fifth communication connection has been established between the socks5 server in the resource pool to be collected and the node to be collected in the resource pool to be collected. The fourth communication connection, the second communication connection and the fifth communication connection are all communication connections that have been successfully established in advance and can be used directly.

[0149] In this way, the management and control node can send a component version collection instruction to the node to be collected via the fourth communication connection, the second communication connection, and the fifth communication connection according to the address of the node to be collected.

[0150] Different nodes have different addresses.

[0151] In step S205, the node to be collected receives a component version collection instruction sent by the management and control node in the central resource pool in the cloud cluster via the fourth communication connection, the second communication connection and the fifth communication connection according to the address of the node to be collected.

[0152] In step S206, the node to be collected obtains the current version of each component in the node to be collected according to the component version collection instruction.

[0153] In step S207, the node to be collected sends the identifier of each component in the node to be collected and the current version of each component to the management and control node via the fourth communication connection, the second communication connection and the fifth communication connection.

[0154] For any component in the node to be collected, there is a binding relationship between the identifier of the component and the current version of the component, for example, a binding relationship in the form of key-value. The same is true for each other component in the node to be collected, so as to facilitate distinction.

[0155] In step S208, the management and control node receives the identifiers of the components in the node to be collected and the current versions of the components, which are sent by the node to be collected via the fourth communication connection, the second communication connection and the fifth communication connection.

[0156] Furthermore, the management and control node can store the identification of each component in the node to be collected and the current version of each component. For example, for any component in the node to be collected, the management and control node can form a corresponding table item consisting of the identification of the resource pool to be collected, the address of the node to be collected in the resource pool to be collected, the identification of the component in the node to be collected in the resource pool to be collected, and the current version of the component in the node to be collected in the resource pool to be collected, and store it in the correspondence between the identification of the resource pool to be collected, the address of the node to be collected, the identification of the component and the current version of the component. The same is true for each other component in the node to be collected.

[0157] Alternatively, the management and control node can also send the identification of each component in the node to be collected and the current version of each component to the client of the operation and maintenance personnel, so that the client of the operation and maintenance personnel can display the identification of each component in the node to be collected and the current version of each component for the operation and maintenance personnel to view.

[0158] Through this application, it is supported to collect the versions of each component in each node in each service resource pool in the cloud cluster through the control node of the central resource pool in the cloud cluster, so that the operation and maintenance personnel can comprehensively analyze the version status of each component on each node in each service resource pool, so that the operation and maintenance personnel can determine whether there are compatibility issues between the versions of each component on any node in any service resource pool, so as to facilitate immediate processing when compatibility issues are found between the versions of each component on the same node, prevent node crashes or failures caused by version incompatibility (mismatch or conflict), thereby ensuring the continuous and stable operation of the service.

[0159] Reference Figure 4 , shows a flow chart of the steps of a component processing method based on a cloud environment of the present application. Applied to the management and control nodes in the central resource pool in the cloud cluster and the new nodes in the new resource pool created in the cloud cluster.

[0160] The control node in the central resource pool is one of the multiple nodes in the central resource pool except the node where the socks5 client is located.

[0161] The new resource pool is a newly created resource pool in the cloud cluster, which can be one or more. The new resource pool is a service resource pool.

[0162] The new node in the new resource pool is at least one node among the multiple nodes in the new resource pool except the node where the socks5 server is located.

[0163] Among them, the method includes:

[0164] In step S301, when a new resource pool has been established in the cloud cluster, the management and control node obtains node information of a new node in the new resource pool.

[0165] The new node can be a virtual machine or a physical machine.

[0166] The node information of the node may include: the type of system in the node, the model of the processor in the node, the type of architecture of the processor in the node, the memory space in the node, the model of the memory in the node, the model of the network card in the node, the bandwidth of the node, etc.

[0167] In the present application, after a new resource pool has been established in the cloud cluster, the node information of each new node in the new resource pool can be manually stored in the management and control node in the central resource pool.

[0168] In this way, the management and control node can obtain the node information of the new node in the new resource pool locally at the management and control node.

[0169] In step S302, the management and control node obtains a component baseline of a stable version of node information applicable to a new node in a new resource pool, wherein the component baseline of the stable version includes identifiers of various components required in the new node in the new resource pool and stable component versions of various components.

[0170] In the present application, there are multiple service resource pools in the cloud cluster, each service resource pool has multiple nodes, and the node information of different nodes is also different. For example, the node information of nodes in different service resource pools is different, and the node information of nodes in the same service resource pool is the same. Or, for another example, the node information of nodes in different service resource pools is different, and the node information of nodes in the same service resource pool is different.

[0171] Each node has the components it needs, such as storage components, computing components, and network components. Each component has multiple versions, and the versions of the same component in each node in each service resource pool are not the same.

[0172] In this way, if the versions of components of various types in a node are combined together to obtain a component version combination of a node, then there are many component version combinations of each node in each service resource pool (as long as the versions of one component of the same type in two component version combinations are different, the two component version combinations are different).

[0173] According to statistics, different combinations of component versions are applicable to nodes with different node information.

[0174] For example, for any node of node information that has appeared in the cloud cluster in the past, various component version combinations of components used on the node of the node information can be counted, and the component version combination of components used on the node of the node information for the longest time is used as the component version combination of components applicable to the node of the node information. The component version combination of components used on the node of the node information for the longest time indicates that the component version combination is stable for the node of the node information, and the component version combination can become the component baseline of the stable version of the node of the node information, that is, as the stable component version of the node of the node information. Then, the node information and the stable component version of the node of the node information are formed into corresponding table items, and stored in the corresponding relationship between the node information and the stable component version of the node applicable to the node information. The same is true for each other node of node information that has appeared in the cloud cluster in the past.

[0175] Thus, in this step, the stable component version corresponding to the node information of the new node in the new resource pool can be found in the correspondence between the node information and the stable component version of the node applicable to the node information.

[0176] In step S303, the management and control node establishes a sixth communication connection between the socks5 client in the central resource pool and the socks5 server in the new resource pool.

[0177] A communication connection can be established between a socks5 client in a central resource pool in a cloud cluster and a socks5 server in a new resource pool, and the communication connection is bound to the address of the socks5 client in the central resource pool and the address of the socks5 server in the service resource pool.

[0178] The address of the socks5 client in the central resource pool may be the IP address of the socks5 client in the central resource pool.

[0179] The address of the socks5 server in the new resource pool may be the IP address of the socks5 server in the new resource pool.

[0180] The control node can form a corresponding table entry with the identifier of the new resource pool and the address of the socks5 server in the new resource pool, and store it in the corresponding relationship between the identifier of the service resource pool and the address of the socks5 server in the service resource pool. The corresponding relationship can be located in the control node for subsequent search and use.

[0181] In step S304, the management and control node sends the stable version of the component baseline to the new node in the new resource pool via the sixth communication connection, the second communication connection, and the seventh communication connection according to the address of the new node in the new resource pool.

[0182] On the logical side, there are: socks5 client in the central resource pool and socks5 server in the new resource pool between the management and control node and the new node.

[0183] There is an established sixth communication connection between the socks5 client in the central resource pool and the socks5 server in the new resource pool. There is an established second communication connection between the control node in the central resource pool and the socks5 client in the central resource pool. There is an established seventh communication connection between the socks5 server in the new resource pool and the new node in the new resource pool. The second communication connection and the seventh communication connection are both communication connections that have been successfully established in advance and can be used directly.

[0184] In this way, the management and control node can send the hot fix plug-in script to the new node via the sixth communication connection, the second communication connection, and the seventh communication connection according to the address of the new node.

[0185] Different nodes have different addresses.

[0186] In step S305, the new node in the new resource pool receives a component baseline of a stable version of node information applicable to the new node in the new resource pool, which is sent by the management and control node in the central resource pool in the cloud cluster via the sixth communication connection, the second communication connection, and the seventh communication connection according to the address of the new node in the new resource pool.

[0187] In step S306, the new node in the new resource pool obtains components corresponding to the stable component versions of the components required in the new node in the component repository according to the identifiers of the components required in the new node in the stable version of the component baseline.

[0188] The component repository stores various versions of components that need to be used by various nodes in various resource pools in the cloud cluster developed in the historical process, the entities (implementations) of the components stored in the component repository, and the applications of the components.

[0189] Each component in the component warehouse is marked by its identification and version. For example, in one embodiment, the component warehouse stores: the corresponding relationship between the component, the identification of the component and the version of the component.

[0190] Thus, in this step, for the identifier of any component in the component baseline and the version of the component, the component that corresponds to the identifier of the component and the version of the component can be searched in the correspondence between the component, the identifier of the component and the version of the component. The same is true for the identifier of each other component in the component baseline and its version.

[0191] In step S307, the new nodes in the new resource pool respectively deploy the acquired components in the new nodes in the new resource pool.

[0192] For example, for any obtained component, the component can be installed in the new node, and the same is true for each other obtained component, so as to respectively deploy the obtained components in the new nodes in the new resource pool.

[0193] Through this application, when deploying various components for new nodes in a new resource pool, stable versions of components can be deployed for new nodes in the new resource pool. Stable versions of components can be understood as the compatibility and adaptability between the versions of various components in the new node, so that the stability of the cooperation between various components in the new node is strong, and the function of any component will not be affected, thereby improving reliability and reducing the subsequent maintenance costs of the versions of various components deployed for new nodes in the new resource pool. The purpose of quickly building a new resource pool in a cloud cluster is also achieved.

[0194] In this application, through the unified version naming rules and version release process, administrators can more easily track and manage the versions of various components, reduce the difficulty of troubleshooting and upgrade maintenance caused by version issues, and thus improve management efficiency. At the same time, it helps to quickly locate the source of security issues when they occur and take corresponding measures to deal with them.

[0195] In another embodiment of the present application, all types and versions of components in the component warehouse are legal components. Generally, all components deployed on each node in each service resource pool are components in the component warehouse.

[0196] However, sometimes criminals may illegally deploy illegal components on any node in any service resource pool to engage in illegal activities, which may bring security risks to the cloud cluster.

[0197] To this end, the management and control node may obtain in advance the digital summary information of the components of each version of each category in the component warehouse, and store the digital summary information of the components of each version of each category.

[0198] Afterwards, the digital summary information of each component on any node in any service resource pool can be obtained regularly or in real time, and the digital summary information of any component on the node can be compared with the pre-stored digital summary information corresponding to the "type and version of the component" to see if they are the same. If they are the same, the component on the node is determined to be a legal component. Or, if they are different, the component on the node is determined to be an illegal component, and a prompt message is sent to the client of the operation and maintenance personnel to prompt the operation and maintenance personnel to intervene as soon as possible to improve security.

[0199] The digital summary information may include: MD5 (Message-Digest Algor ithm, message digest algorithm) or SHA256 (Secure Hash Algor ithm 256, secure hash algorithm 256).

[0200] It should be noted that, for the method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions involved are not necessarily required by the present application.

[0201] Optionally, an embodiment of the present application further provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0202] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, each process of the above method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0203] Figure 5 800 is a block diagram of an electronic device 800 shown in the present application. For example, the electronic device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0204] Reference Figure 5, the electronic device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0205] The processing component 802 generally controls the overall operation of the electronic device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0206] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phone book data, messages, images, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0207] The power supply component 806 provides power to the various components of the electronic device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 800.

[0208] The multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also monitor the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and the rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0209] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the electronic device 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0210] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0211] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the electronic device 800. For example, the sensor assembly 814 can monitor the open / closed state of the device 800, the relative positioning of the components, such as the display and keypad of the electronic device 800, and the sensor assembly 814 can also monitor the position change of the electronic device 800 or a component of the electronic device 800, the presence or absence of contact between the user and the electronic device 800, the orientation or acceleration / deceleration of the electronic device 800, and the temperature change of the electronic device 800. The sensor assembly 814 may include a proximity sensor configured to monitor the presence of nearby objects without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0212] The communication component 816 is configured to facilitate wired or wireless communication between the electronic device 800 and other devices. The electronic device 800 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast operation information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (I rDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0213] In an exemplary embodiment, the electronic device 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

[0214] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by a processor 820 of an electronic device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0215] Figure 6 1 is a block diagram of an electronic device 1900 shown in the present application. For example, the electronic device 1900 may be provided as a server.

[0216] Reference Figure 6 , the electronic device 1900 includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions executable by the processing component 1922, such as an application. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute instructions to perform the above method.

[0217] The electronic device 1900 may also include a power supply component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input / output (I / O) interface 1958. The electronic device 1900 may operate based on an operating system stored in the memory 1932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

[0218] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

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

[0220] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0221] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the present application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0222] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0223] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0224] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0225] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0226] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0227] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A component processing method based on a cloud environment, characterized in that: Applied to a management and control node in a central resource pool in a cloud cluster, the method comprises: Obtain a hot fix plug-in script submitted by an operation and maintenance personnel, the hot fix plug-in script carrying the identifier of the component to be repaired, the target version of the component to be repaired, the identifier of the resource pool to be repaired in the cloud cluster, and the address of the node to be repaired in the resource pool to be repaired; the node to be repaired has the component to be repaired, and the current version of the component to be repaired in the node to be repaired is different from the target version; According to the identifier of the resource pool to be repaired in the hot repair plug-in script, obtain the address of the socks5 server in the resource pool to be repaired; According to the address of the socks5 server in the resource pool to be repaired, determine the first communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be repaired; According to the address of the node to be repaired, a hot repair plug-in script is sent to the node to be repaired via the first communication connection, the second communication connection and the third communication connection, the second communication connection being the communication connection established between the control node in the central resource pool and the socks5 client in the central resource pool; the third communication connection being the communication connection established between the socks5 server in the resource pool to be repaired and the node to be repaired in the resource pool to be repaired; so that the node to be repaired obtains the target version of the component to be repaired in the component repository according to the identifier of the component to be repaired in the hot repair plug-in script and the target version of the component to be repaired, and upgrades the current version of the component to be repaired in the node to be repaired to the target version of the component to be repaired.

2. The method according to claim 1, characterized in that The hot repair plug-in script also carries the time to be repaired; before the node to be repaired upgrades the current version of the component to be repaired in the node to be repaired to the component to be repaired of the target version, it is determined whether the current time of the resource pool to be repaired reaches the time to be repaired; when the current time of the resource pool to be repaired reaches the time to be repaired, the current version of the component to be repaired in the node to be repaired is upgraded to the component to be repaired of the target version.

3. A component processing method based on a cloud environment, characterized in that: Applied to a management and control node in a central resource pool in a cloud cluster, the method comprises: Obtain the component version collection instruction submitted by the operation and maintenance personnel. The component version collection instruction carries the identifier of the resource pool to be collected in the cloud cluster and the address of the node to be collected in the resource pool to be collected; According to the identifier of the resource pool to be collected in the component version collection instruction, obtain the address of the socks5 server in the resource pool to be collected; Determine, according to the address of the socks5 server in the resource pool to be collected, a fourth communication connection established between the socks5 client in the central resource pool and the socks5 server in the resource pool to be collected; According to the address of the node to be collected, a component version collection instruction is sent to the node to be collected via the fourth communication connection, the second communication connection and the fifth communication connection; so that the node to be collected obtains the identifier of each component in the node to be collected and the current version of each component according to the component version collection instruction; the identifier of each component in the node to be collected and the current version of each component are sent to the management and control node via the fourth communication connection, the second communication connection and the fifth communication connection; the second communication connection is a communication connection established between the management and control node in the central resource pool and the socks5 client in the central resource pool; the fifth communication connection is a communication connection established between the socks5 server in the resource pool to be collected and the node to be collected in the resource pool to be collected; The identifiers of the components in the node to be collected and the current versions of the components are received and sent by the node to be collected via the fourth communication connection, the second communication connection and the fifth communication connection.

4. A component processing method based on a cloud environment, characterized in that: Applied to a management and control node in a central resource pool in a cloud cluster, the method comprises: When a new resource pool has been established in the cloud cluster, obtain node information of a new node in the new resource pool; Obtaining a stable version of a component baseline applicable to node information of a new node in a new resource pool, wherein the stable version of the component baseline includes identifiers of various components required in the new node in the new resource pool and stable component versions of various components; Establishing a sixth communication connection between the socks5 client in the central resource pool and the socks5 server in the new resource pool; According to the address of the new node in the new resource pool, the component baseline of the stable version is sent to the new node in the new resource pool via the sixth communication connection, the second communication connection and the seventh communication connection; the second communication connection is the communication connection established between the control node in the central resource pool and the socks5 client in the central resource pool; the seventh communication connection is the communication connection established between the socks5 server in the new resource pool and the new node in the new resource pool; So that the new node in the new resource pool can obtain the components corresponding to the stable component versions of the components required in the new node in the component warehouse according to the identifiers of the components required in the new node in the stable version of the component baseline, and deploy the obtained components in the new node in the new resource pool respectively.

5. A component processing method based on a cloud environment, characterized in that: Applied to a node to be repaired in a resource pool to be repaired in a cloud cluster, the method comprises: A hot repair plug-in script is received, which is sent by the control node in the central resource pool in the cloud cluster to the node to be repaired via the first communication connection, the second communication connection and the third communication connection according to the address of the node to be repaired; the hot repair plug-in script is submitted by the operation and maintenance personnel in the control node, and the hot repair plug-in script carries the identifier of the component to be repaired, the target version of the component to be repaired, the identifier of the resource pool to be repaired and the address of the node to be repaired in the resource pool to be repaired in the cloud cluster; the node to be repaired has the component to be repaired, and the current version of the component to be repaired in the node to be repaired is different from the target version; the first communication connection is the socks5 in the central resource pool. The communication connection established between the client and the socks5 server in the resource pool to be repaired; the second communication connection is the communication connection established between the control node in the central resource pool and the socks5 client in the central resource pool; the third communication connection is the communication connection established between the socks5 server in the resource pool to be repaired and the node to be repaired in the resource pool to be repaired; the first communication connection is determined by the control node according to the address of the socks5 server in the resource pool to be repaired, and the address of the socks5 server in the resource pool to be repaired is obtained by the control node according to the identifier of the resource pool to be repaired in the hot repair plug-in script; According to the identifier of the component to be repaired in the hot repair plug-in script and the target version of the component to be repaired, the component to be repaired of the target version is obtained in the component repository; The current version of the component to be repaired in the node to be repaired is upgraded to the component to be repaired of the target version.

6. The method according to claim 5, characterized in that The hot fix plug-in script also carries the time to be fixed; Before the component to be repaired of the current version in the node to be repaired is upgraded to the component to be repaired of the target version, the method further includes: Determine whether the current time of the resource pool to be repaired reaches the time to be repaired; When the current time of the resource pool to be repaired reaches the time to be repaired, the step of upgrading the current version of the component to be repaired in the node to be repaired to the component to be repaired of the target version is performed.

7. A component processing method based on a cloud environment, characterized in that: Applied to a node to be collected in a resource pool to be collected in a cloud cluster, the method comprises: Receive a component version collection instruction sent by the control node in the central resource pool in the cloud cluster via the fourth communication connection, the second communication connection and the fifth communication connection according to the address of the node to be collected; the component version collection instruction is submitted by the operation and maintenance personnel in the control node, and the component version collection instruction carries the identifier of the resource pool to be collected in the cloud cluster and the address of the node to be collected in the resource pool to be collected; the fourth communication connection is an established communication connection between the socks5 client in the central resource pool and the socks5 server in the resource pool to be collected; the second communication connection is an established communication connection between the control node in the central resource pool and the socks5 client in the central resource pool; the fifth communication connection is an established communication connection between the socks5 server in the resource pool to be collected and the node to be collected in the resource pool to be collected; the fourth communication connection is determined by the control node according to the address of the socks5 server in the resource pool to be collected, and the address of the socks5 server in the resource pool to be collected is obtained by the control node according to the identifier of the resource pool to be collected in the component version collection instruction; Obtain the identifier of each component in the node to be collected and the current version of each component according to the component version collection instruction; The identification of each component in the node to be collected and the current version of each component are sent to the management and control node via the fourth communication connection, the second communication connection and the fifth communication connection, so that the management and control node receives the identification of each component in the node to be collected and the current version of each component.

8. A component processing method based on a cloud environment, characterized in that: Applied to a new node in a new resource pool in a cloud cluster, the method comprises: Receive a component baseline of a stable version of node information applicable to a new node in a new resource pool, which is sent by the control node in the central resource pool in the cloud cluster via the sixth communication connection, the second communication connection, and the seventh communication connection according to the address of the new node in the new resource pool; the sixth communication connection is a communication connection between the socks5 client in the central resource pool and the socks5 server in the new resource pool established by the control node; the second communication connection is an established communication connection between the control node in the central resource pool and the socks5 client in the central resource pool; the seventh communication connection is an established communication connection between the socks5 server in the new resource pool and the new node in the new resource pool, and the component baseline of the stable version includes the identifiers of each component required in the new node in the new resource pool and the stable component versions of each component; the component baseline of the stable version is obtained by the control node after obtaining the node information of the new node in the new resource pool when a new resource pool has been established in the cloud cluster; In the component repository, according to the identifiers of the components required in the new node in the component baseline of the stable version, the components corresponding to the stable component versions of the components required in the new node are obtained; Deploy the acquired components in new nodes in the new resource pool.

9. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the component processing method based on a cloud environment as claimed in any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the component processing method based on a cloud environment according to any one of claims 1 to 8 is implemented.

Images