A component processing method and device based on a cloud environment, an electronic device, and a storage medium

Abstract

The application provides a cloud environment-based component processing method and device, electronic equipment and storage medium. Through the application, an operation and maintenance personnel can provide hot repair for the identified risky components, and a flexible way is provided for the developer to extend and / or replace the version of the components on the nodes in the service resource pool, so that the components in the service resource pool are more maintainable, the efficiency of the operation and maintenance personnel in maintaining the components can be greatly improved, and the time cost is saved. Through the repair of the version of the components in the nodes in the service resource pool, the versions of the same kind of components in each node in the service resource pool can be consistent, or the versions of each kind of components in the same node in the service resource pool can be compatible. The performance of the cooperation between each kind of components in the same node in the service resource pool can be improved, and the efficient and safe operation of the node is maintained.

Description

Technical Field

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

[0002] With the rapid development and widespread application of cloud computing, the number of nodes in cloud clusters provided by cloud vendors is increasing. To ensure the high performance, high availability, security, and stability of cloud clusters, cloud vendors establish resource pools for cloud clusters in various locations. These resource pools can be viewed as sub-clusters within the cloud cluster.

[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 on different servers in different resource pools become increasingly significant after continuous version iterations. Components in a node include computing components, storage components, and network components, among others. Summary of the Invention

[0004] This application discloses a component processing method, apparatus, electronic device, and storage medium based on a cloud environment.

[0005] Firstly, this application discloses a component processing method based on a cloud environment, applied to a management node in a central resource pool of a cloud cluster, the method comprising:

[0006] Obtain the hotfix plugin script submitted by the operations and maintenance personnel. The hotfix plugin 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. The node to be repaired contains 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] Based on the identifier of the resource pool to be repaired in the hotfix plugin script, obtain the address of the socks5 server in the resource pool to be repaired;

[0008] Based on 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 to-be-repaired node, a hot repair plug-in script is sent to the to-be-repaired node via the first communication connection, the second communication connection, and the third communication connection, the second communication connection being a communication connection established between the management and control node in the central resource pool and the socks5 client in the central resource pool, and the third communication connection being a communication connection established between the socks5 server in the to-be-repaired resource pool and the to-be-repaired node in the to-be-repaired resource pool, so that the to-be-repaired node acquires the to-be-repaired component of the target version from the component warehouse according to the identifier of the to-be-repaired component and the target version of the to-be-repaired component in the hot repair plug-in script, and upgrades the to-be-repaired component of the current version in the to-be-repaired node to the to-be-repaired component of the target version.

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

[0011] Obtaining a component version collection instruction submitted by an operation and maintenance personnel, the component version collection instruction carrying an identifier of a to-be-collected resource pool in the cloud cluster and an address of a to-be-collected node in the to-be-collected resource pool;

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

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

[0014] According to the address of the to-be-collected node, sending a component version collection instruction to the to-be-collected node via the fourth communication connection, the second communication connection, and a fifth communication connection, so that the to-be-collected node acquires identifiers of each component in the to-be-collected node and current versions of each component according to the component version collection instruction, and sends the identifiers of each component in the to-be-collected node and the current versions of each component to the management and control node via the fourth communication connection, the second communication connection, and the fifth communication connection, the second communication connection being a communication connection established between the management and control node in the central resource pool and the socks5 client in the central resource pool, and the fifth communication connection being a communication connection established between the socks5 server in the to-be-collected resource pool and the to-be-collected node in the to-be-collected resource pool;

[0015] Receiving the identifiers of each component in the to-be-collected node and the current versions of each component sent by the to-be-collected node via the fourth communication connection, the second communication connection, and the fifth communication connection.

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

[0017] In the case that a new resource pool has been established in the cloud cluster, node information of a new node in the new resource pool is acquired;

[0018] A stable version of a component baseline applicable to the node information of the new node in the new resource pool is acquired, and the stable version of the component baseline comprises the identification of each component required in the new node in the new resource pool and the stable component version of each component;

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

[0020] According to the address of the new node in the new resource pool, the stable version of the component baseline is sent to the new node in the new resource pool via the sixth communication connection, a second communication connection and a seventh communication connection; the second communication connection is a communication connection already established between the management node in the central resource pool and the socks5 client in the central resource pool; and the seventh communication connection is a communication connection already 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 acquires, in the component warehouse, the components corresponding to the stable component version of each component required in the new node according to the identification of each component required in the new node in the stable version of the component baseline, and respectively deploys each acquired component in the new node in the new resource pool.

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

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

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

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

[0026] In a fifth aspect, a component processing method based on a cloud environment is shown, applied to a to-be-collected node in a to-be-collected resource pool in a cloud cluster, and the method comprises:

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

[0028] According to the component version collection instruction, the identifier of each component in the to-be-collected node and the current version of each component are obtained;

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

[0030] In a sixth aspect, a component processing method based on a cloud environment is shown, applied to a new node in a new resource pool in a cloud cluster, and the method comprises:

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

[0028] According to the component version collection instruction, the identifier of each component in the to-be-collected node and the current version of each component are obtained;

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

[0030] In a sixth aspect, a component processing method based on a cloud environment is shown, applied to a new node in a new resource pool in a cloud cluster, and the method comprises:

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

[0028] According to the component version collection instruction, the identifier of each component in the to-be-collected node and the current version of each component are obtained;

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

[0032] In the component warehouse, according to the identification of each component required in the new node in the component baseline of the stable version, a stable component version corresponding to each component required in the new node is obtained;

[0033] Each component obtained is respectively deployed in the new node in the new resource pool.

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

[0035] In an eighth aspect, the present application shows a non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by the processor of an electronic device, the electronic device can execute the method of any one of the above aspects.

[0036] In a ninth aspect, the present application shows a computer program product, when the instructions in the computer program product are executed by the processor of an electronic device, the electronic device can execute the method of any one of the above aspects.

[0037] The technical scheme provided by the present application can include the following beneficial effects:

[0038] Through the present application, the operation and maintenance personnel can provide hot fixes for the identified components with risks, and provide a flexible way for developers to extend and / or replace the 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 efficiency of the operation and maintenance personnel in maintaining the components can be greatly improved, and the time cost can be saved.

[0039] Through the repair of the versions of the components in the nodes in the service resource pool, the versions of the same kind of components in each node in the service resource pool can be kept consistent, or the versions of each kind of components in the same node in the service resource pool can have compatibility.

[0040] Alternatively, a suitable secure version of the component in the node can be selected and deployed, updated or upgraded in time according to actual needs, known security vulnerabilities can be indirectly repaired by changing the version of the component, potential security risks can be reduced, and the performance of the cooperation between each kind of components in the same node in the service resource pool can be improved, and the efficient and safe operation of the node can be maintained.

[0041] Through the application, the versions of each component in each node in each service resource pool in the cloud cluster are collected by a management node of a central resource pool in the cloud cluster, so that an operation and maintenance personnel can comprehensively analyze the versions of each component on each node in each service resource pool, and determine whether there is a compatibility problem between the versions of each component on any node in any service resource pool, so as to facilitate immediate processing in the case that there is a compatibility problem between the versions of each component on the same node, prevent node crashes or failures due to version incompatibility (mismatch or conflict), and thus ensure the continuous and stable operation of the service.

[0042] Through the application, when deploying each component for a new node in a new resource pool, a stable version of the component can be deployed for the new node in the new resource pool. The stable version of the component can be understood as that the compatibility between the versions of each component in the new node is strong, and the adaptability is strong, so that the stability of the mutual cooperation of each component in the new node is strong, and the function of any component will not be affected, the reliability is improved, and the maintenance cost of the subsequent maintenance of the versions of each component deployed for the new node in the new resource pool is reduced. The purpose of quickly building a new resource pool in the cloud cluster is also achieved. BRIEF DESCRIPTION OF DRAWINGS

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

[0044] Figure 2 is a step flowchart of a component processing method based on a cloud environment according to the application.

[0045] Figure 3 is a step flowchart of a component processing method based on a cloud environment according to the application.

[0046] Figure 4 is a step flowchart of a component processing method based on a cloud environment according to the application.

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

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

[0049] The technical solutions in the embodiments of the application will be described clearly and completely below with reference to the drawings in the embodiments of the application. Obviously, the described embodiments are only some of the embodiments of the application, not all the embodiments. Based on the embodiments in the application, all other embodiments obtained by a person of ordinary skill in the art without creative labor fall within the scope of protection of the application.

[0050] The versions of IaaS (Infrastructure as a Service) layer components in nodes in different resource pools are quite different. The versions of network components and the versions of storage components in the same node can not be the same version, and there can be compatibility problems between different versions of network components and storage components, which can cause instability of the node during operation. For example, a network component of a certain version (for example, V1.0) can be incompatible with a storage component of another version (for example, V2.0), causing network failure of the node and affecting data transmission of the node.

[0051] Secondly, different versions of components can have differences in performance optimization, resource utilization, etc. If mixed use, they can restrict each other, causing the short board problem of the wooden bucket, and further causing the overall performance of the resource pool to be poor.

[0052] If the version of a component of the IaaS layer of the resource pool is lower, the possibility of security vulnerabilities of the low version component is greater, and these vulnerabilities can be exploited by hackers to attack the nodes in the resource pool, causing the security risk to be unable to be effectively controlled.

[0053] The version confusion of the components increases the management complexity of the nodes in the resource pool. In the scenario where the administrator uniformly configures the versions of each component in the resource pool, more versions of components need to be handled at the same time, which can make the configuration task become tedious and prone to errors, and the configuration task becomes more difficult.

[0054] Due to the version confusion of the components, the overall performance of the resource pool can be poor, the security risk is increased, etc. The cloud vendor can need to invest more resources to solve these problems, including purchasing new hardware devices for the resource pool, upgrading the software version, etc., thereby increasing the cost.

[0055] Therefore, the scheme of the present application is proposed.

[0056] Before introducing the scheme of the present application, the technical terms that can be involved in the present application are explained.

[0057] Socks5 is a set of open software standards developed by the Internal project team to handle network security matters. Socks provides traffic and security management between Internet servers and clients for information entering and exiting enterprise networks.

[0058] Socks is a security standard related to the Socket port of TCP / IP (Transmission Control Protocol / Internet Protocol), and a general firewall system usually functions as a gateway on the seventh layer of the OSI (Open System Interconnect) model, that is, the application layer, and controls the high-level protocol of TCP / IP, while Socks functions on the fifth layer of the OSI model, that is, the session layer, Socks 5 supports peer-to-peer connection, so that two peers can directly establish a connection without passing through other proxy servers, thereby improving the efficiency of network transmission, and is a scheme for providing security services between the session layer and the session layer, and is not affected by changes in high-level application programs.

[0059] Referring to Figure 1 , a structural block diagram of a component processing system based on a cloud environment is shown, wherein the system comprises:

[0060] a central resource pool and a plurality of service resource pools.

[0061] Each service resource pool has a plurality of nodes, and the nodes can be physical servers or virtual machines built on the servers.

[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, to collect the versions of components in the nodes in the service resource pool, to deploy the required version of the component in the nodes in the service resource pool, to update or adapt the versions of the components in the nodes in the service resource pool, etc.

[0064] The central resource pool has a plurality of nodes, and one of the nodes has a socks5 client.

[0065] One of the nodes in any service resource pool has a socks5 server.

[0066] The socks5 client in the central resource pool and the socks5 server in each service resource pool are respectively connected in communication.

[0067] The socks5 client in the central resource pool and each node (other nodes are nodes where the socks5 client is not located) in the central resource pool are respectively connected in communication.

[0068] The socks5 server in any one service resource pool and each node (other nodes are nodes where non-socks5 servers are located) in the service resource pool have respectively established a communication connection.

[0069] The socks5 client in the center resource pool and the socks5 server in any one service resource pool realize secure communication through connection establishment, identity authentication, data forwarding, and connection closing.

[0070] The socks5 client in the center resource pool in the cloud cluster can issue the public key of the socks5 client to each service resource pool in the cloud cluster to realize mutual trust access.

[0071] In this way, any node in the center resource pool and any node in any service resource pool can interact 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 realized, which can reduce network transmission costs; 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 separately establish direct communication connections between nodes in different resource pools, which can save network resources.

[0074] The intercommunication between the Socks5 server in a service resource pool and the node where the non-Socks5 server is located in the service resource pool belongs to the natural intercommunication of the intranet machine, and the network transmission goes through the internal network card without consuming bandwidth, thereby saving bandwidth.

[0075] The socks5 client in the center resource pool can also be dynamically destroyed according to actual needs, and the socks5 client is dynamically created again according to actual needs, and the communication connection between the dynamically created socks5 client and the socks5 server in the service resource pool that needs to be connected is established again, which improves flexibility and avoids resource waste.

[0076] In this application, the components or other application programs on each node in each resource pool in the cloud cluster can adopt a micro-service architecture to improve overall scalability and high availability.

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

[0078] Referring to Figure 2 , a step flowchart of a component processing method based on a cloud environment is shown.

[0079] The management and control node is applied to a central resource pool in a cloud cluster, and the to-be-repaired node is in a to-be-repaired resource pool in the cloud cluster.

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

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

[0082] The to-be-repaired node in the to-be-repaired resource pool is at least one of the plurality of nodes in the to-be-repaired resource pool except for the node where the socks5 server is located.

[0083] The method comprises the following steps.

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

[0085] The node can have a plurality of types of components, such as a storage component, a network component, and a computing component, etc. Each component has a respective version. The identifiers of different types of components are different.

[0086] The to-be-repaired component can be at least one of a plurality of types of components in the to-be-repaired node, such as at least one of a storage component, a network component, and a computing component, etc.

[0087] The addresses of different nodes are different, and the address of the node can be an IP (Internet Protocol) address of the node. The identifiers of different resource pools are different.

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

[0089] If the operation and maintenance personnel consider that the current version of a component (the component can be one of a storage component, a network component, and a computing component, or two of them) in a node in a service resource pool is incompatible with the current versions of other components in the node, and consider that after upgrading the current version of the component in the node to a target version, the target version of the component is compatible with the current versions of other components in the node, it is indicated 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 to-be-repaired resource pool, the node is a to-be-repaired node, and the component is a to-be-repaired component.

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

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

[0093] The management and control node can obtain the versions of each component in each node in each service resource pool in the manner shown in the embodiment described below, which will not be described in detail here. Figure 3

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

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

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

[0097] The address of the socks5 client in the center resource pool can be the IP address of the socks5 client in the center resource pool.

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

[0099] ​The management and control node can correspond the identifier of the service resource pool with the address of the socks5 service end in the service resource pool to form a corresponding table item, and store the corresponding relationship between the identifier of the service resource pool and the address of the socks5 service end in the service resource pool. The corresponding relationship can be located in the management and control node.

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

[0101] In this way, in the present step, the management and control node can extract the identifier of the to-be-repaired resource pool in the hot repair plug-in script, and then find the address of the socks5 service end corresponding to the identifier of the to-be-repaired resource pool in the corresponding relationship between the identifier of the service resource pool and the address of the socks5 service end in the service resource pool, that is, the address of the socks5 service end in the to-be-repaired resource pool.

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

[0103] As mentioned earlier, the communication connection between the socks5 client in the center resource pool and the socks5 service end in any one service resource pool is established in advance, and the communication connection between the socks5 client in the center resource pool and the socks5 service end in any one service resource pool is bound to the address of the socks5 client in the center resource pool and the address of the socks5 service end in the service resource pool.

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

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

[0106] On the logical side, the management and control node and the to-be-repaired node have: the socks5 client in the center resource pool and the socks5 service end in the to-be-repaired resource pool.

[0107] The socks5 client in the central resource pool has an established first communication connection with the socks5 server in the to-be-repaired resource pool. The management node in the central resource pool has an established second communication connection with the socks5 client in the central resource pool. The socks5 server in the to-be-repaired resource pool has an established third communication connection with the to-be-repaired node in the to-be-repaired resource pool. 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 directly used.

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

[0109] The addresses of different nodes are different.

[0110] In step S105, the to-be-repaired node receives the hot repair plug-in script sent by the management 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 to-be-repaired node.

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

[0112] The component warehouse stores components of various versions required by each node in each resource pool in the cloud cluster developed in the history process. The component warehouse stores entities (implementations) of the components, application programs of the components, and the like.

[0113] Each component in the component warehouse is marked by its identifier and version. For example, in an embodiment, the component warehouse stores a correspondence relationship among the components, the identifiers of the components, and the versions of the components.

[0114] In this way, in this step, the component that corresponds to both the identifier of the to-be-repaired component and the target version of the to-be-repaired component in the hot repair plug-in script can be found in the correspondence relationship among the components, the identifiers of the components, and the versions of the components, and used as the to-be-repaired component of the target version.

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

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

[0117] Through the present application, the operation and maintenance personnel can provide hot repair for the identified components with risks, and a flexible way is provided for the developer to extend and / or replace the version of the component on the node in the service resource pool, so that the components in the service resource pool are more maintainable, the efficiency of the operation and maintenance personnel in maintaining the components can be greatly improved, and the time cost can be saved.

[0118] Through the repair of the version of the component in the node in the service resource pool, the versions of the same kind of components in each node in the service resource pool can be kept consistent, or the versions of each kind of components in the same node in the service resource pool can have compatibility.

[0119] Alternatively, the appropriate safe version of the component in the node can be selected and deployed, updated or upgraded in time according to actual needs, the known security vulnerabilities can be indirectly repaired by changing the version of the component, potential security risks can be reduced, and thus the performance of cooperation between each kind of components in the same node in the service resource pool can be improved, and the efficient and safe operation of the node can be maintained.

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

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

[0122] The to-be-repaired node upgrades the current version of the to-be-repaired component in the to-be-repaired node to the target version of the to-be-repaired component, and the to-be-repaired node obtains a version upgrade result of the to-be-repaired component in the to-be-repaired node. 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 the version upgrade result of the to-be-repaired component in the to-be-repaired node sent by the to-be-repaired node 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 for the client of the operation and maintenance personnel to display the version upgrade result, so that the operation and maintenance personnel can view the version upgrade result.

[0125] If the operation and maintenance personnel considers that the version upgrade result is correct, the operation and maintenance personnel can input a confirmation operation on the version upgrade result displayed by the client of the operation and maintenance personnel. The client of the operation and maintenance personnel generates a confirmation instruction on the version upgrade result according to the confirmation operation and sends the confirmation instruction on the version upgrade result to the management and control node.

[0126] The management and control node can receive the confirmation instruction on the version upgrade result, and then obtain the repaired version of each component in the to-be-repaired node according to the confirmation instruction on the version upgrade result. The management and control node generates a component baseline according to the repaired version of each component in the to-be-repaired node, so as to realize the version upgrade / optimization / repair of each component in the to-be-repaired node based on the component baseline.

[0127] The component baseline can include the identification of each component in the to-be-repaired node and the version of each component. The component baseline can also include the address of the to-be-repaired node, and further include the identification of the to-be-repaired resource pool. The addresses of different nodes are different, and the identifications of different resource pools are different.

[0128] Referring to Figure 3 , a step flowchart of a component processing method based on a cloud environment is shown. The method is applied to a management and control node in a center resource pool in a cloud cluster and a to-be-collected node in a to-be-collected resource pool in the cloud cluster.

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

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

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

[0132] The method comprises:

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

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

[0135] The to-be-collected resource pool can be at least one service resource pool of a plurality of service resource pools in the cloud cluster, and the to-be-collected node in the to-be-collected resource pool can be at least one node of a plurality of nodes in the to-be-collected resource pool.

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

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

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

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

[0140] The management node can form a corresponding table item of the identifier of the service resource pool and the address of the socks5 server in the service resource pool, and store the corresponding table item in a 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 node.

[0141] The same is true for each of the other service resource pools in the cloud cluster.

[0142] Thus, in this step, the management and control node can extract the identifier of the to-be-collected resource pool in the component version collection instruction, and then find the address of the socks5 server corresponding to the identifier of the to-be-collected resource pool in the correspondence between the identifier of the service resource pool and the address of the socks5 server in the service resource pool, that is, the address of the socks5 server in the to-be-collected resource pool.

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

[0144] As mentioned earlier, the communication connection between the socks5 client in the center resource pool and the socks5 server in any one of the service resource pools is established in advance, and the communication connection between the socks5 client in the center resource pool and the socks5 server in any one of the service resource pools is bound to the address of the socks5 client in the center resource pool and the address of the socks5 server in the service resource pool.

[0145] Thus, the address of the socks5 server in the to-be-collected resource pool bound to the communication connection can be determined in the communication connection between the socks5 client in the center resource pool and the socks5 server in each of the service resource pools in the cloud cluster, that is, the fourth communication connection established between the socks5 client in the center resource pool and the socks5 server in the to-be-collected resource pool.

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

[0147] On the logical plane, the management and control node and the to-be-collected node have: the socks5 client in the center resource pool and the socks5 server in the to-be-collected resource pool.

[0148] The socks5 client in the center resource pool has an established fourth communication connection with the socks5 server in the to-be-collected resource pool. The management node in the center resource pool has an established second communication connection with the socks5 client in the center resource pool. The socks5 server in the to-be-collected resource pool has an established fifth communication connection with the to-be-collected node in the to-be-collected resource pool. 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 directly used.

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

[0150] The addresses of different nodes are different.

[0151] In step S205, the to-be-collected node receives the component version collection instruction sent by the management node in the center 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 to-be-collected node.

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

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

[0154] For any one component in the to-be-collected node, the identification of the component and the current version of the component have a binding relationship, for example, a key-value form binding relationship, and the same is true for each of the other components in the to-be-collected node, so as to be distinguished.

[0155] In step S208, the management node receives the identification of each component in the to-be-collected node and the current version of each component sent by the to-be-collected node via the fourth communication connection, the second communication connection, and the fifth communication connection.

[0156] Further, the management node can store the identification of each component in the to-be-collected node and the current version of each component. For example, for any one component in the to-be-collected node, the management node can form a corresponding table item with the identification of the to-be-collected resource pool, the address of the to-be-collected node in the to-be-collected resource pool, the identification of the component in the to-be-collected node in the to-be-collected resource pool, and the current version of the component in the to-be-collected node in the to-be-collected resource pool, and store the corresponding relationship among the identification of the to-be-collected resource pool, the address of the to-be-collected node, the identification of the component, and the current version of the component. The same is true for each other component in the to-be-collected node.

[0157] Alternatively, the management node can also send the identification of each component in the to-be-collected node 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 displays the identification of each component in the to-be-collected node and the current version of each component for the operation and maintenance personnel to view.

[0158] Through the present application, the version of each component in each node in each service resource pool in the cloud cluster is collected by the management node of the central resource pool in the cloud cluster, so that the operation and maintenance personnel can analyze the version of each component on each node in each service resource pool, determine whether there is a compatibility problem between the versions of each component on any one node in any one service resource pool, and facilitate immediate processing in the case of discovering that there is a compatibility problem between the versions of each component on the same node, preventing node crashes or failures due to version incompatibility (mismatch or conflict), thereby ensuring the continuous and stable operation of the service.

[0159] Referring to Figure 4 , a step flowchart of a component processing method based on a cloud environment is shown. The method is applied to a management node in a central resource pool in a cloud cluster and a new node in a new resource pool created in the cloud cluster.

[0160] The management 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 resource pool newly established in the cloud cluster, which can be one or multiple. The new resource pool is a service resource pool.

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

[0163] The method comprises:

[0164] In step S301, in a case where a new resource pool has been established in the cloud cluster, the management and control node acquires 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 can include a type of system included in the node, a model of processor in the node, a type of architecture of processor in the node, a space of memory in the node, a model of memory in the node, a model of network card in the node, a bandwidth of the node, and the like.

[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 acquire the node information of the new node in the new resource pool locally.

[0169] In step S302, the management and control node acquires a component baseline of a stable version suitable for the node information of the new node in the new resource pool, the component baseline of the stable version including the identification of each component required in the new node in the new resource pool and the stable component version of each component.

[0170] In the present application, the cloud cluster has a plurality of service resource pools, each service resource pool has a plurality of nodes, and the node information of different nodes is not the same, for example, the node information of nodes in different service resource pools is different, 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 components required by itself, such as storage components, computing components, network components, and the like, each type of component has a plurality of versions, and the versions of the same type of component in each node in each service resource pool are not the same.

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

[0173] Through statistics, the component version combinations suitable for nodes with different node information are not the same.

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

[0175] In this way, 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 corresponding relationship between the node information and the stable stable component version suitable for the node information of the node.

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

[0177] The communication connection between the socks5 client in the center resource pool in the cloud cluster and the socks5 service end in the new resource pool can be established, and the communication connection is bound to the address of the socks5 client in the center resource pool and the address of the socks5 service end in the service resource pool.

[0178] The address of the socks5 client in the center resource pool can be the IP address of the socks5 client in the center resource pool.

[0179] The address of the socks5 service end in the new resource pool can be the IP address of the socks5 service end in the new resource pool.

[0180] The management node can form a corresponding table item of the identifier of the new resource pool and the address of the socks5 service end 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 service end in the service resource pool. The corresponding relationship can be located in the management node, which is convenient for subsequent 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 plane, the management and control node and the new node have a socks5 client in the central resource pool and a socks5 server in the new resource pool.

[0183] The socks5 client in the central resource pool and the socks5 server in the new resource pool have an established sixth communication connection. The management and control node in the central resource pool and the socks5 client in the central resource pool have an established second communication connection. The socks5 server in the new resource pool and the new node in the new resource pool have an established seventh communication connection. The second communication connection and the seventh communication connection are 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 hotfix 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] The addresses of different nodes are different.

[0186] In step S305, the new node in the new resource pool receives the stable version of the component baseline of the node information suitable for the new node in the new resource pool 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 acquires the stable component version corresponding to each component required by the new node in the component warehouse according to the identifier of each component required by the new node in the stable version of the component baseline.

[0188] The component warehouse stores each version of each component required by each node in each resource pool in the cloud cluster developed in the historical process. The entity (implementation) of the component stored in the component warehouse is an application program of the component, etc.

[0189] Each component in the component warehouse is marked by its identifier and version. For example, in an embodiment, the component warehouse stores the correspondence among the component, the identifier of the component and the version of the component.

[0190] Thus, in this step, for the identification of any one component in the component baseline and the version of the component, the component corresponding to the identification of the component and the version of the component can be found in the correspondence among the component, the identification of the component, and the version of the component. The same is true for the identification of each component in the component baseline and the version thereof.

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

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

[0193] Through the present application, when deploying components for the new nodes in the new resource pool, stable version components can be deployed for the new nodes in the new resource pool. The stable version components can be understood as components with strong compatibility and adaptability between versions of components in the new nodes, so that the stability of the components in the new nodes is strong, and the functionality of any one component is not affected, the reliability is improved, and the maintenance cost of the versions of the components deployed for the new nodes in the new resource pool is reduced. The purpose of quickly building a new resource pool in a cloud cluster is also achieved.

[0194] In the present application, through the unified version naming rule and version release process, the administrator can more conveniently track and manage the versions of the components, reduce the difficulty of troubleshooting and upgrade maintenance caused by version problems, and thus improve the management efficiency. At the same time, it is helpful to quickly locate the source of the problem when a security problem occurs, and take appropriate measures to respond.

[0195] In another embodiment of the present application, each version of each kind of component in the component warehouse is a legal component. Generally, the components deployed on each node in each service resource pool are components in the component warehouse.

[0196] However, sometimes illegal components may be illegally deployed on any node in any service resource pool by illegal persons to engage in illegal activities, thereby causing security risks to the cloud cluster.

[0197] Therefore, the management and control node can obtain the digital digest information of each version of each kind of component in the component warehouse in advance, and store the digital digest information of each version of each kind of component.

[0198] Afterwards, the digital digest information of each component on any node in any service resource pool can be acquired periodically or in real time, and the digital digest information of any component on the node is compared with the digital digest information corresponding to the "type and version of the component" stored in advance. If they are the same, it is determined that the component on the node is a legal component, or if they are different, it is determined that the component on the node is an illegal component. A prompt information is sent to the client of the operation and maintenance personnel to prompt the operation and maintenance personnel to intervene as soon as possible, so as to improve the security.

[0199] The digital digest information can include MD5 (Message-Digest Algorithm) or SHA256 (Secure Hash Algorithm 256).

[0200] It should be noted that, for the method embodiments, in order to simply describe, they are all described as a series of action combinations, but those skilled in the art should know that the present application is not limited to the order of the actions described, because according to the present application, certain steps can be performed in other order or at the same time. Secondly, those skilled in the art should know 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, the present application also provides an electronic device, which includes 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, it implements each process of the above method embodiments and achieves the same technical effects. To avoid repetition, it will not be described here.

[0202] The present application also provides a computer readable storage medium, which stores a computer program. When the computer program is executed by the processor, it implements each process of the above method embodiments and achieves the same technical effects. To avoid repetition, it will not be described here. The computer readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0203] Figure 5 is a block diagram of an electronic device 800 according to an embodiment of the present application. For example, the electronic device 800 can 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] Referring to Figure 5The electronic device 800 can include one or more of the following components: a processing component 802, a memory 804, a power supply 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 usually controls overall operations of the electronic device 800, such as operations associated with displaying, making phone calls, data communications, camera operations, and recording operations. The processing component 802 can include one or more processors 820 to execute instructions to complete all or part of steps of the above methods. In addition, the processing component 802 can include one or more modules to facilitate

[0206] The memory 804 is configured to store various types of data to support operations of the electronic device 800. Examples of these data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, images, videos, and the like. The memory 804 can be implemented by any type of volatile or non-volatile storage devices 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 storage, flash memory, magnetic or optical disk.

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

[0208] The multimedia component 808 includes a screen to provide an output interface between the electronic device 800 and a user. In some embodiments, the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense a touch, a slide, and a gesture on the touch panel. The touch sensor can not only sense a boundary of a touching or a sliding action, but also detect duration and intensity of the touching or sliding action. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. The front camera and / or the rear camera can receive external multimedia data when the electronic device 800 is in an operating mode, such as a shooting mode or a video mode. Each of the front and rear camera can be a fixed optical lens system or have a focal length and optical zooming capability.

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

[0210] The I / O interface 812 provides an interface for the processing component 802 and peripheral interface modules, such as a keypad, a click wheel, buttons, and the like. The buttons can include, but are not limited to, a home button, a volume button, a start button, and a lock button.

[0211] The sensor component 814 includes one or more sensors to provide various state assessments for the electronic device 800. For example, the sensor component 814 can monitor an open / closed state of the electronic device 800, relative positioning of components, such as a display and a keypad of the electronic device 800, a change in position of the electronic device 800 or a component of the electronic device 800, presence or absence of user contact with the electronic device 800, orientation or acceleration / deceleration of the electronic device 800, and a temperature change of the electronic device 800. The sensor component 814 can include a proximity sensor to detect presence of an object within a proximity range of the electronic device 800 without any physical touch. The sensor component 814 can further include a light sensor, such as a CMOS or CCD image sensor, to use in an imaging application. In some embodiments, the sensor component 814 can further 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 cellular network standard (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an example embodiment, the communication component 816 receives broadcast signals or broadcast operation information from external broadcast management systems via a broadcast channel. In an example embodiment, the communication component 816 can further include 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) techniques, infrared data association (IrDA) techniques, ultra-wideband (UWB) techniques, Bluetooth (BT) techniques, and other techniques.

[0213] In an example embodiment, the electronic device 800 can be implemented with 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, micro-controllers, microprocessors, or other electronic elements, for performing the above-described methods.

[0214] In an example embodiment, a non-transitory computer-readable storage medium including instructions, such as the memory 804 including instructions, is also provided, which can be executed by the processor 820 of the electronic device 800 to complete the above-described methods. 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 disc, and an optical data storage device, etc.

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

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

[0217] The electronic device 1900 can further 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 can 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 the terms "comprising", "including", or any other variant are intended to cover a non-exclusive inclusion, such that processes, methods, articles, or apparatuses that comprise a list of elements are not required to include only those elements in the list, but can include other elements not expressly listed or inherent to such processes, methods, articles, or apparatuses. Without further limitation, an element preceded by "comprises... a" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0219] Those skilled in the art can clearly understand that the above-mentioned embodiment method can be realized by means of software and necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the methods described in various embodiments 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 embodiments, which are only illustrative and not restrictive. Those skilled in the art can make many forms without departing from the purpose of the present application and the scope protected by the claims under the inspiration of the present application, which all belong to the protection of the present application.

[0221] Those skilled in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of the present application can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are executed in hardware or software depends on the specific application and design constraints of the technical solutions. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0222] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0223] In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented by other manners. For example, the apparatus embodiments described above are only schematic, for example, the division of the units is only a logical function division, and another division manner can be used in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0224] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

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

[0226] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that make contributions to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage medium includes: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, and various program code storage media.

[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 can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A cloud environment-based component processing method, characterized by, A method applied to a management and control node in a central resource pool in a cloud cluster, the method comprising: Obtaining a hot repair plug-in script submitted by an operation and maintenance personnel, the hot repair plug-in script carrying an identifier of a to-be-repaired component, a target version of the to-be-repaired component, an identifier of a to-be-repaired resource pool in the cloud cluster, and an address of a to-be-repaired node in the to-be-repaired resource pool; the to-be-repaired node having the to-be-repaired component, and a current version of the to-be-repaired component in the to-be-repaired node being different from the target version; According to the identifier of the to-be-repaired resource pool in the hot repair plug-in script, obtaining an address of a socks5 server in the to-be-repaired resource pool; According to the address of the socks5 server in the to-be-repaired resource pool, determining that a first communication connection has been established between a socks5 client in the central resource pool and the socks5 server in the to-be-repaired resource pool; According to the address of the to-be-repaired node, sending the hot repair plug-in script to the to-be-repaired node via the first communication connection, a second communication connection, and a third communication connection; the second communication connection being a communication connection that has been established between the management and control node in the central resource pool and the socks5 client in the central resource pool; and the third communication connection being a communication connection that has been established between the socks5 server in the to-be-repaired resource pool and the to-be-repaired node in the to-be-repaired resource pool; so that the to-be-repaired node obtains the to-be-repaired component of the target version from a component warehouse according to the identifier of the to-be-repaired component and the target version of the to-be-repaired component in the hot repair plug-in script, and upgrades the to-be-repaired component of the current version in the to-be-repaired node to the to-be-repaired component of the target version.

2. The method of claim 1, wherein, The hot repair plug-in script also carries a to-be-repaired time; so that the to-be-repaired node determines whether the current time of the to-be-repaired resource pool reaches the to-be-repaired time before upgrading the to-be-repaired component of the current version in the to-be-repaired node to the to-be-repaired component of the target version; and in the case that the current time of the to-be-repaired resource pool reaches the to-be-repaired time, the to-be-repaired component of the current version in the to-be-repaired node is further upgraded to the to-be-repaired component of the target version.

3. A cloud environment-based component processing method, characterized by, A method applied to a management and control node in a central resource pool in a cloud cluster, the method comprising: Obtaining a component version collection instruction submitted by an operation and maintenance personnel, the component version collection instruction carrying an identifier of a to-be-collected resource pool in the cloud cluster and an address of a to-be-collected node in the to-be-collected resource pool; According to the identifier of the to-be-collected resource pool in the component version collection instruction, obtaining an address of a socks5 server in the to-be-collected resource pool; According to the address of the socks5 server in the to-be-collected resource pool, determining that a fourth communication connection has been established between a socks5 client in the central resource pool and the socks5 server in the to-be-collected resource pool; According to the address of the to-be-collected node, component version collection instructions are sent to the to-be-collected node via the fourth communication connection, the second communication connection, and the fifth communication connection, so that the to-be-collected node obtains the identities of the components in the to-be-collected node and the current versions of the components according to the component version collection instructions; the identities of the components in the to-be-collected node and the current versions of the components 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 that has been established between the management and control node in the central resource pool and the socks5 client in the central resource pool; and the fifth communication connection is a communication connection that has been established between the socks5 server in the to-be-collected resource pool and the to-be-collected node in the to-be-collected resource pool. The identities of the components in the to-be-collected node and the current versions of the components sent by the to-be-collected node via the fourth communication connection, the second communication connection, and the fifth communication connection are received.

4. A cloud environment-based component processing method, characterized by, The method applied to the management and control node in the central resource pool in the cloud cluster comprises: In the case that a new resource pool has been established in the cloud cluster, node information of a new node in the new resource pool is obtained; A stable version of a component baseline suitable for the node information of the new node in the new resource pool is obtained, the stable version of the component baseline comprising the identities of the components required in the new node in the new resource pool and stable component versions of the components; A sixth communication connection between a socks5 client in the central resource pool and a socks5 server in the new resource pool is established; According to the address of the new node in the new resource pool, the stable version of the component baseline is sent to the new node in the new resource pool via the sixth communication connection, the second communication connection, and a seventh communication connection; the second communication connection is a communication connection that has been established between the management and control node in the central resource pool and the socks5 client in the central resource pool; and the seventh communication connection is a communication connection that has been 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 obtains, in the component warehouse, components corresponding to the stable component versions of the components required in the new node according to the identities of the components required in the new node in the stable version of the component baseline, and respectively deploys the obtained components in the new node in the new resource pool.

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

6. The method of claim 5, wherein, The hot repair plug-in script also carries a to-be-repaired time point; Before the current version of the to-be-repaired component in the to-be-repaired node is upgraded to the target version of the to-be-repaired component, the method further includes: Determining whether a current time point of the to-be-repaired resource pool reaches the to-be-repaired time point; In the case where the current time point of the to-be-repaired resource pool reaches the to-be-repaired time point, the step of upgrading the current version of the to-be-repaired component in the to-be-repaired node to the target version of the to-be-repaired component is performed again.

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

8. A cloud environment-based component processing method, characterized by, The method applied to a new node in a new resource pool in a cloud cluster, the method comprising: The management node in the center resource pool in the cloud cluster sends a component version collection instruction according to the address of the to-be-collected node via a fourth communication connection, a second communication connection and a fifth communication connection; the component version collection instruction is submitted by an operation and maintenance personnel in the management node, and carries the identifier of the to-be-collected resource pool in the cloud cluster and the address of the to-be-collected node in the to-be-collected resource pool; the fourth communication connection is a communication connection established between a socks5 client in the center resource pool and a socks5 server in the to-be-collected resource pool; the second communication connection is a communication connection established between the management node in the center resource pool and the socks5 client in the center resource pool; the fifth communication connection is a communication connection established between the socks5 server in the to-be-collected resource pool and the to-be-collected node in the to-be-collected resource pool; the fourth communication connection is determined by the management node according to the address of the socks5 server in the to-be-collected resource pool, and the address of the socks5 server in the to-be-collected resource pool is obtained by the management node according to the identifier of the to-be-collected resource pool in the component version collection instruction; According to the component version collection instruction, the identifier of each component in the to-be-collected node and the current version of each component are obtained; Via the fourth communication connection, the second communication connection and the fifth communication connection, the identifier of each component in the to-be-collected node and the current version of each component are sent to the management node, so that the management node receives the identifier of each component in the to-be-collected node and the current version of each component.

9. An electronic device, comprising: The method applied to a new node in a new resource pool in a cloud cluster, the method comprising: The management node in the center resource pool in the cloud cluster sends a component version collection instruction according to the address of the to-be-collected node via a fourth communication connection, a second communication connection and a fifth communication connection; the component version collection instruction is submitted by an operation and maintenance personnel in the management node, and carries the identifier of the to-be-collected resource pool in the cloud cluster and the address of the to-be-collected node in the to-be-collected resource pool; the fourth communication connection is a communication connection established between a socks5 client in the center resource pool and a socks5 server in the to-be-collected resource pool; the second communication connection is a communication connection established between the management node in the center resource pool and the socks5 client in the center resource pool; the fifth communication connection is a communication connection established between the socks5 server in the to-be-collected resource pool and the to-be-collected node in the to-be-collected resource pool; the fourth communication connection is determined by the management node according to the address of the socks5 server in the to-be-collected resource pool, and the address of the socks5 server in the to-be-collected resource pool is obtained by the management node according to the identifier of the to-be-collected resource pool in the component version collection instruction; According to the component version collection instruction, the identifier of each component in the to-be-collected node and the current version of each component are obtained; Via the fourth communication connection, the second communication connection and the fifth communication connection, the identifier of each component in the to-be-collected node and the current version of each component are sent to the management node, so that the management node receives the identifier of each component in the to-be-collected node and the current version of each component. The method applied to a new node in a new resource pool in a cloud cluster, the method comprising: The processor, the memory, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor to implement the cloud environment-based component processing method according to any one of claims 1 to 8.

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

Images