A method, apparatus, device and medium for node service deployment

Abstract

The present application discloses a node service deployment method, apparatus, device and medium, relating to the field of computer technology, including: obtaining a node service deployment request, determining a node to be deployed and deployment information based on the node service deployment request; judging whether the network connectivity between the local device and the node to be deployed is normal, if it is normal, judging whether the disk to which the node belongs in the deployment information exists, if it exists, determining a deployment capacity value; obtaining the local remaining capacity value, judging whether the remaining capacity value is greater than the deployment capacity value, if it is greater, determining a service unique identifier; judging whether there is a historical service unique identifier identical to the service unique identifier locally, if not, formatting the node to be deployed to obtain a formatted node to be deployed; performing a service deployment start operation on the formatted node to be deployed based on the deployment information to obtain a node after service deployment. The present application can improve the service deployment efficiency, increase the service deployment accuracy, and improve the cluster maintenance ability.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly relates to a method, device, equipment and medium for node service deployment. Background Art

[0002] BeeGFS cluster is a parallel file system emerging in recent years, developed by the German Thinkparq team, dedicated to achieving high performance of business applications using scaled hardware, and has wide applications in the fields of HPC, AI, machine learning, life sciences, and resource exploration. The BeeGFS cluster adopts a full command-line deployment method. When the cluster scale is small, the deployment takes less time. However, if the cluster scale is large (such as more than 5 nodes), the native command-line deployment method has the following deficiencies: The time for deploying using the native command line increases linearly with the increase in the number of nodes (N); There are many creation and change steps involved in the deployment process, and it is very easy to have omissions or errors in service types, service parameters or configurations when the node scale is large, which affects the deployment progress; After the deployment is completed, there is no overall view of the service status and configuration of each node in the cluster, which is not conducive to overall inspection and subsequent maintenance.

[0003] As can be seen from the above, how to improve the efficiency of node service deployment, increase the accuracy of node service deployment, and improve the cluster maintenance ability are problems to be solved in this field. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a method, device, equipment and medium for node service deployment, which relates to the field of computer technology, and can improve the efficiency of node service deployment, increase the accuracy of node service deployment, and improve the cluster maintenance ability. The specific solutions are as follows:

[0005] In a first aspect, the present application discloses a method for node service deployment, including:

[0006] Obtain a node service deployment request, and determine the nodes to be deployed and deployment information based on the node service deployment request;

[0007] Judge whether the network connectivity between the local and the nodes to be deployed is normal. If the network connectivity between the local and the nodes to be deployed is normal, then judge whether the disks to which the nodes in the deployment information belong exist. If the disks to which the nodes in the deployment information belong exist, then determine the deployment capacity value in the deployment information;

[0008] Obtain the remaining capacity value of the local, and judge whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, then determine the service unique identifier in the deployment information;

[0009] Determine whether there is a historical service unique identifier in the local that is the same as the service unique identifier in the to-be-deployed node information. If there is no historical service unique identifier in the local that is the same as the service unique identifier in the to-be-deployed node information, format the to-be-deployed node to obtain a formatted to-be-deployed node;

[0010] Based on the deployment information, perform a service deployment start operation on the formatted to-be-deployed node to obtain a node after service deployment.

[0011] Optionally, the determining the to-be-deployed node and deployment information based on the node service deployment request includes:

[0012] Determine the to-be-deployed node based on the node service deployment request;

[0013] Determine the deployment information including the name of the to-be-deployed node, the disk to which the node belongs, the deployment capacity value, the service unique identifier, and the port number.

[0014] Optionally, the obtaining the node service deployment request and determining the to-be-deployed node and deployment information based on the node service deployment request includes:

[0015] Determine the service type to be deployed according to the node service deployment request;

[0016] Based on the service type and the node service deployment request, determine the to-be-deployed node and deployment information.

[0017] Optionally, after determining whether the network connectivity between the local and the to-be-deployed node is normal, it further includes:

[0018] If the network connectivity between the local and the to-be-deployed node is abnormal, generate a network connectivity re-detection request or a node name re-detection request;

[0019] Send the network connectivity re-detection request or the node name re-detection request to the local.

[0020] Optionally, after determining whether there is a historical service unique identifier in the local that is the same as the service unique identifier in the to-be-deployed node information, it further includes:

[0021] If there is a historical service unique identifier in the local that is the same as the service unique identifier in the to-be-deployed node information, create a service directory according to business requirements and generate a configuration file;

[0022] Modify the configuration parameters in the configuration file according to the port number and the service unique identifier in the deployment information.

[0023] Optionally, the operation of starting service deployment for the formatted node to be deployed based on the deployment information includes:

[0024] Execute a preset file system mounting command on the formatted node to be deployed through a security protocol to obtain the node to be deployed after the command is executed;

[0025] Perform a service deployment start operation on the node to be deployed after the command is executed based on the deployment information.

[0026] Optionally, after obtaining the node after service deployment, it further includes:

[0027] Obtain the service status and configuration information of all the nodes after service deployment;

[0028] Generate a service-owned directory based on the service status and the configuration information, and save the service-owned directory locally.

[0029] In a second aspect, the present application discloses a node service deployment device, including:

[0030] A node service deployment request acquisition module, configured to acquire a node service deployment request, and determine a node to be deployed and deployment information based on the node service deployment request;

[0031] A connectivity judgment module, configured to judge whether the network connectivity between the local and the node to be deployed is normal. If the network connectivity between the local and the node to be deployed is normal, judge whether the disk to which the node belongs in the deployment information exists. If the disk to which the node belongs in the deployment information exists, determine the deployment capacity value in the deployment information;

[0032] A capacity value judgment module, configured to acquire the remaining capacity value of the local, and judge whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, determine the service unique identifier in the deployment information;

[0033] A service unique identifier judgment module, configured to judge whether there is a historical service unique identifier in the local that is the same as the service unique identifier in the information of the node to be deployed. If there is no historical service unique identifier in the local that is the same as the service unique identifier in the information of the node to be deployed, format the node to be deployed to obtain a formatted node to be deployed;

[0034] A node service deployment module, configured to perform a service deployment start operation on the formatted node to be deployed based on the deployment information to obtain a node after service deployment.

[0035] In a third aspect, the present application discloses an electronic device, including:

[0036] A memory for storing a computer program;

[0037] A processor for executing the computer program to implement the foregoing node service deployment method.

[0038] In a fourth aspect, the present application discloses a computer storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the foregoing disclosed node service deployment method are implemented.

[0039] It can be seen that the present application provides a node service deployment method, including obtaining a node service deployment request, and determining a node to be deployed and deployment information based on the node service deployment request; determining whether the network connectivity between the local device and the node to be deployed is normal, if the network connectivity between the local device and the node to be deployed is normal, then determining whether the disk to which the node in the deployment information belongs exists, if the disk to which the node in the deployment information belongs exists, then determining the deployment capacity value in the deployment information; obtaining the remaining capacity value of the local device, and determining whether the remaining capacity value is greater than the deployment capacity value, if the remaining capacity value is greater than the deployment capacity value, then determining the service unique identifier in the deployment information; determining whether there is a historical service unique identifier in the local device that is the same as the service unique identifier in the information of the node to be deployed, if there is no historical service unique identifier in the local device that is the same as the service unique identifier in the information of the node to be deployed, then formatting the node to be deployed to obtain a formatted node to be deployed; performing a service deployment start operation on the formatted node to be deployed based on the deployment information to obtain a node after service deployment. The present application realizes the service deployment of all nodes in the cluster by executing a deployment tool on a single node. Each type of service deployment is distinguished by the service type. According to different input parameters, the node to be deployed, the deployed service, and the main parameters are actively identified to realize the full-automatic deployment and start of the service, and the deployment results can be actively collected, which is convenient for inspection after deployment and subsequent maintenance, thereby improving the efficiency of node service deployment, increasing the accuracy of node service deployment, and improving the cluster maintenance ability. Description of the Drawings

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the following drawings are only the embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0041] Figure 1 It is a flowchart of a node service deployment method disclosed in the present application;

[0042] Figure 2Flowchart of a node service deployment method disclosed in this application;

[0043] Figure 3 Schematic structural diagram of a node service deployment device disclosed in this application;

[0044] Figure 4 Structural diagram of an electronic device provided by this application. Detailed implementation manners

[0045] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0046] The BeeGFS cluster is a parallel file system that has emerged in recent years and is developed by the German Thinkparq team. It is committed to using large-scale hardware to achieve high performance of business applications and has a wide range of applications in the fields of HPC, AI, machine learning, life sciences, and resource exploration. The BeeGFS cluster adopts a full command-line deployment method. When the cluster scale is small, the deployment takes less time. However, if the cluster scale is large (such as more than 5 nodes), the native command-line deployment method has the following deficiencies: the time for deploying using the native command line increases linearly with the increase in the number of nodes (N); there are many creation and change steps involved in the deployment process, and it is very easy to have omissions or errors in service types, service parameters, or configurations when the node scale is large, affecting the deployment progress; after the deployment is completed, there is no overall view of the service status and configuration of each node in the cluster, which is not conducive to overall inspection and subsequent maintenance. As can be seen from the above, how to improve the efficiency of node service deployment, increase the accuracy of node service deployment, and improve the cluster maintenance ability is a problem to be solved in this field.

[0047] Refer to Figure 1 As shown, the embodiments of the present invention disclose a node service deployment method, which may specifically include:

[0048] Step S11: Obtain a node service deployment request, and determine the nodes to be deployed and deployment information based on the node service deployment request.

[0049] In this embodiment, a node service deployment request is obtained, the service type to be deployed is determined according to the node service deployment request, and then the nodes to be deployed and deployment information are determined based on the service type and the node service deployment request; wherein, the deployment information includes the name of the node to be deployed, the disk to which the node belongs, the deployment capacity value, the unique service identifier, and the port number.

[0050] This application is applied to the deployment tool in any node within the cluster. By setting the service type and passing different custom parameters for different service types, the inspection, deployment, and startup of services are realized. Taking the deployment of the META service as an example: Obtain the node service deployment request, and then confirm the node name, the disk / partition to which the node belongs, the deployment capacity value, the service ID (Identity document, unique identifier), and the port number of the META service to be deployed. For different service types, automatic configuration of specific type parameters can be achieved, such as whether the MGMTD service uses the system disk partition and whether to format the partition; whether the META and STORAGE services use the multi-process mode and the port settings for different processes.

[0051] Step S12: Determine whether the network connectivity between the local machine and the node to be deployed is normal. If the network connectivity between the local machine and the node to be deployed is normal, then determine whether the disk to which the node belongs in the deployment information exists. If the disk to which the node belongs in the deployment information exists, then determine the deployment capacity value in the deployment information.

[0052] In this embodiment, after determining whether the network connectivity between the local machine and the node to be deployed is normal, it further includes: If the network connectivity between the local machine and the node to be deployed is abnormal, then generate a network connectivity re-detection request or a node name re-detection request; send the network connectivity re-detection request or the node name re-detection request to the local machine.

[0053] In this embodiment, check whether the corresponding node between the local machine and the node to be deployed is connectable. If it is not connectable, then throw an exception and require checking the connectivity or the node name to generate a network connectivity re-detection request or a node name re-detection request, and then send the network connectivity re-detection request or the node name re-detection request to the local machine.

[0054] In this embodiment, check whether the set disk exists. If it does not exist, then throw an exception; if it exists, then check whether the remaining capacity meets the set capacity requirement. If it does not meet the requirement, then throw an exception.

[0055] Step S13: Obtain the remaining capacity value of the local machine, and determine whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, then determine the service unique identifier in the deployment information.

[0056] Step S14: Determine whether there is a historical service unique identifier on the local machine that is the same as the service unique identifier in the information of the node to be deployed. If there is no historical service unique identifier on the local machine that is the same as the service unique identifier in the information of the node to be deployed, then format the node to be deployed to obtain a formatted node to be deployed.

[0057] In this embodiment, after determining whether there is a historical service unique identifier in the local area that is the same as the service unique identifier in the to-be-deployed node information, the following steps are further included: If there is a historical service unique identifier in the local area that is the same as the service unique identifier in the to-be-deployed node information, a service directory is created according to the service requirements, and a configuration file is generated; the configuration parameters in the configuration file are modified according to the port number in the deployment information and the service unique identifier.

[0058] In this embodiment, it is checked whether the service ID already exists in the set node. If it exists, an exception is thrown. If it does not exist, a service directory is created as needed, a configuration file is generated, and the configuration parameters are modified according to the port number and the service ID.

[0059] Step S15: Perform a service deployment start operation on the formatted to-be-deployed node based on the deployment information to obtain a node after service deployment.

[0060] In this embodiment, a node service deployment request is obtained, and the to-be-deployed node and deployment information are determined based on the node service deployment request; it is judged whether the network connectivity between the local area and the to-be-deployed node is normal. If the network connectivity between the local area and the to-be-deployed node is normal, it is judged whether the disk to which the node in the deployment information belongs exists. If the disk to which the node in the deployment information belongs exists, the deployment capacity value in the deployment information is determined; the remaining capacity value of the local area is obtained, and it is judged whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, the service unique identifier in the deployment information is determined; it is judged whether there is a historical service unique identifier in the local area that is the same as the service unique identifier in the to-be-deployed node information. If there is no historical service unique identifier in the local area that is the same as the service unique identifier in the to-be-deployed node information, the to-be-deployed node is formatted to obtain a formatted to-be-deployed node; a service deployment start operation is performed on the formatted to-be-deployed node based on the deployment information to obtain a node after service deployment. In this application, by executing the deployment tool on a single node, the service deployment of all nodes in the cluster is realized. Each type of service deployment is distinguished by the service type. According to different input parameters, the to-be-deployed node, the deployed service, and the main parameters are actively identified, realizing the full-automatic deployment and start of the service. The deployment results can be actively collected, which is convenient for post-deployment inspection and subsequent maintenance, thereby improving the efficiency of node service deployment, increasing the accuracy of node service deployment, and improving the cluster maintenance ability.

[0061] See Figure 2 As shown, an embodiment of the present invention discloses a node service deployment method, which may specifically include:

[0062] Step S21: Obtain a node service deployment request, and determine the node to be deployed and deployment information based on the node service deployment request.

[0063] Step S22: Determine whether the network connectivity between the local device and the node to be deployed is normal. If the network connectivity between the local device and the node to be deployed is normal, then determine whether the disk to which the node belongs in the deployment information exists. If the disk to which the node belongs in the deployment information exists, then determine the deployment capacity value in the deployment information.

[0064] Step S23: Obtain the remaining capacity value of the local device, and determine whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, then determine the service unique identifier in the deployment information.

[0065] Step S24: Determine whether there is a historical service unique identifier in the local device that is the same as the service unique identifier in the information of the node to be deployed. If there is no historical service unique identifier in the local device that is the same as the service unique identifier in the information of the node to be deployed, then format the node to be deployed to obtain a formatted node to be deployed.

[0066] Step S25: Execute a preset file system mounting command on the formatted node to be deployed through a security protocol to obtain the node to be deployed after the command is executed, and perform a service deployment start operation on the node to be deployed after the command is executed based on the deployment information to obtain a node after service deployment.

[0067] In this embodiment, on the premise that passwordless access is completed for each node in the cluster, commands are distributed to other nodes through SSH (security protocol) on a single node to implement service deployment for all nodes in the cluster.

[0068] Step S26: Obtain the service status and configuration information of all the nodes after service deployment, generate a service belonging directory based on the service status and the configuration information, and save the service belonging directory to the local device.

[0069] In this embodiment, if there is no historical service unique identifier in the local device that is the same as the service unique identifier in the information of the node to be deployed, then disk / partition formatting, file system mounting, service deployment and startup are performed according to the existing information. When all nodes are deployed, the service status and configuration information are collected by traversing all nodes, a service belonging directory is generated based on the service status and the configuration information, and the service belonging directory is saved to the local device.

[0070] The key points of this application are as follows: The deployment tool applied in any node within the cluster, that is, a method for realizing cluster deployment through single-node operation; a method for quickly deploying corresponding services to specified nodes according to the service type and parameters to be deployed; actively collecting deployment results for convenient subsequent maintenance.

[0071] In this embodiment, a node service deployment request is obtained, and based on the node service deployment request, the node to be deployed and deployment information are determined; it is judged whether the network connectivity between the local and the node to be deployed is normal. If the network connectivity between the local and the node to be deployed is normal, it is judged whether the disk to which the node in the deployment information belongs exists. If the disk to which the node in the deployment information belongs exists, the deployment capacity value in the deployment information is determined; the remaining capacity value of the local is obtained, and it is judged whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, the service unique identifier in the deployment information is determined; it is judged whether there is a historical service unique identifier in the local that is the same as the service unique identifier in the node to be deployed information. If there is no historical service unique identifier in the local that is the same as the service unique identifier in the node to be deployed information, the node to be deployed is formatted to obtain a formatted node to be deployed; based on the deployment information, a service deployment start operation is performed on the formatted node to be deployed to obtain a node after service deployment. This application realizes the service deployment of all nodes within the cluster by executing the deployment tool on a single node. Each type of service deployment is distinguished by the service type. According to different input parameters, the node to be deployed, the deployed service, and the main parameters are actively identified to realize the full-automatic deployment and start of the service, and the deployment results can be actively collected for convenient inspection after deployment and subsequent maintenance, thereby being able to improve the efficiency of node service deployment, increase the accuracy of node service deployment, and improve the cluster maintenance ability.

[0072] See Figure 3 As shown, an embodiment of the present invention discloses a node service deployment device, which may specifically include:

[0073] A node service deployment request acquisition module 11, configured to obtain a node service deployment request, and based on the node service deployment request, determine the node to be deployed and deployment information;

[0074] A connectivity judgment module 12, configured to judge whether the network connectivity between the local and the node to be deployed is normal. If the network connectivity between the local and the node to be deployed is normal, judge whether the disk to which the node in the deployment information belongs exists. If the disk to which the node in the deployment information belongs exists, determine the deployment capacity value in the deployment information;

[0075] A capacity value judgment module 13 is configured to obtain the remaining capacity value of the local device and determine whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, the service unique identifier in the deployment information is determined.

[0076] A service unique identifier judgment module 14 is configured to determine whether there is a historical service unique identifier in the local device that is the same as the service unique identifier in the to-be-deployed node information. If there is no historical service unique identifier in the local device that is the same as the service unique identifier in the to-be-deployed node information, the to-be-deployed node is formatted to obtain a formatted to-be-deployed node.

[0077] A node service deployment module 15 is configured to perform a service deployment start operation on the formatted to-be-deployed node based on the deployment information to obtain a node after service deployment.

[0078] In this embodiment, a node service deployment request is obtained, and based on the node service deployment request, a to-be-deployed node and deployment information are determined; it is determined whether the network connectivity between the local device and the to-be-deployed node is normal. If the network connectivity between the local device and the to-be-deployed node is normal, it is determined whether the disk to which the node in the deployment information belongs exists. If the disk to which the node in the deployment information belongs exists, the deployment capacity value in the deployment information is determined; the remaining capacity value of the local device is obtained, and it is determined whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, the service unique identifier in the deployment information is determined; it is determined whether there is a historical service unique identifier in the local device that is the same as the service unique identifier in the to-be-deployed node information. If there is no historical service unique identifier in the local device that is the same as the service unique identifier in the to-be-deployed node information, the to-be-deployed node is formatted to obtain a formatted to-be-deployed node; a service deployment start operation is performed on the formatted to-be-deployed node based on the deployment information to obtain a node after service deployment. In this application, by executing the deployment tool on a single node, the service deployment of all nodes in the cluster is realized. Each type of service deployment is distinguished by the service type. According to different input parameters, the to-be-deployed node, the deployed service, and the main parameters are actively identified, realizing the full-automatic deployment and start of the service. The deployment results can be actively collected, which is convenient for inspection after deployment and subsequent maintenance, thereby improving the efficiency of node service deployment, increasing the accuracy of node service deployment, and improving the cluster maintenance ability.

[0079] In some specific embodiments, the node service deployment request acquisition module 11 may specifically include:

[0080] A to-be-deployed node determination module is configured to determine a to-be-deployed node based on the node service deployment request.

[0081] A deployment information determination module, configured to determine deployment information including the name of the node to be deployed, the disk to which the node belongs, the deployment capacity value, the service unique identifier, and the port number.

[0082] In some specific embodiments, the node service deployment request acquisition module 11 may specifically include:

[0083] A service type determination module, configured to determine the service type to be deployed according to the node service deployment request;

[0084] A deployment information determination module, configured to determine the node to be deployed and the deployment information based on the service type and the node service deployment request.

[0085] In some specific embodiments, the connectivity judgment module 12 may specifically include:

[0086] A connectivity judgment module, configured to generate a network connectivity re-detection request or a node name re-detection request if the network connectivity between the local device and the node to be deployed is abnormal;

[0087] A re-detection request sending module, configured to send the network connectivity re-detection request or the node name re-detection request to the local device.

[0088] In some specific embodiments, the service unique identifier judgment module 14 may specifically include:

[0089] A configuration file generation module, configured to create a service directory and generate a configuration file according to business requirements if there is a historical service unique identifier in the local device that is the same as the service unique identifier in the information of the node to be deployed;

[0090] A configuration parameter modification module, configured to modify the configuration parameters in the configuration file according to the port number in the deployment information and the service unique identifier.

[0091] In some specific embodiments, the node service deployment module 15 may specifically include:

[0092] A determined node to be deployed after executing the command module, configured to execute a preset file system mounting command on the formatted node to be deployed through a security protocol to obtain the node to be deployed after executing the command;

[0093] A service deployment start module, configured to perform a service deployment start operation on the node to be deployed after executing the command based on the deployment information.

[0094] In some specific embodiments, the node service deployment module 15 may specifically include:

[0095] All configuration information acquisition modules are used to acquire the service status and configuration information of all nodes after the service is deployed;

[0096] The service directory generation module is used to generate a service directory based on the service status and the configuration information, and save the service directory locally.

[0097] Figure 4 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. Among them, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the node service deployment method executed by the electronic device disclosed in any of the foregoing embodiments.

[0098] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows is any communication protocol applicable to the technical solution of the present application, and no specific limitation is imposed here; the input / output interface 25 is used to acquire external input data or output data to the outside, and its specific interface type can be selected according to specific application requirements, and no specific limitation is made here.

[0099] In addition, as a carrier for resource storage, the memory 22 can be a read-only memory, a random access memory, a magnetic disk, an optical disk, etc. The resources stored thereon include an operating system 221, a computer program 222, and data 223, etc., and the storage method can be short-term storage or permanent storage.

[0100] Among them, the operating system 221 is used to manage and control each hardware device on the electronic device 20 and the computer program 222 to realize the operation and processing of the data 223 in the memory 22 by the processor 21, and it can be Windows, Unix, Linux, etc. In addition to the computer program that can be used to complete the node service deployment method executed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program that can be used to complete other specific tasks. In addition to the data transmitted from external devices received by the node service deployment device, the data 223 may also include data collected by its own input / output interface 25, etc.

[0101] The steps of the methods or algorithms described in combination with the embodiments disclosed in this article can be implemented directly by hardware, software modules executed by a processor, or a combination of both. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium well-known in the technical field.

[0102] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium storing a computer program, which, when loaded and executed by a processor, implements the steps of the node service deployment method disclosed in any of the foregoing embodiments.

[0103] Finally, it should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the existence of additional identical elements in the process, method, article or device comprising the element.

[0104] The above has introduced in detail a node service deployment method, device, equipment and storage medium provided by the present invention. Specific examples are used in this article to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A node service deployment method, characterized in that, Including: Obtain a node service deployment request, and determine a node to be deployed and deployment information based on the node service deployment request; Judge whether the network connectivity between the local and the node to be deployed is normal. If the network connectivity between the local and the node to be deployed is normal, then judge whether the disk to which the node in the deployment information belongs exists. If the disk to which the node in the deployment information belongs exists, then determine the deployment capacity value in the deployment information; Obtain the remaining capacity value of the local, and judge whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, then determine the service unique identifier in the deployment information; Judge whether there is a historical service unique identifier in the local that is the same as the service unique identifier in the information of the node to be deployed. If there is no historical service unique identifier in the local that is the same as the service unique identifier in the information of the node to be deployed, then format the node to be deployed to obtain a formatted node to be deployed; Perform a service deployment start operation on the formatted node to be deployed based on the deployment information to obtain a node after service deployment.

2. The node service deployment method according to claim 1, wherein The determining the node to be deployed and the deployment information based on the node service deployment request includes: Determine the node to be deployed based on the node service deployment request; Determine the deployment information including the name of the node to be deployed, the disk to which the node belongs, the deployment capacity value, the service unique identifier, and the port number.

3. The node service deployment method according to claim 1, wherein The obtaining the node service deployment request and determining the node to be deployed and the deployment information based on the node service deployment request includes: Determine the service type to be deployed according to the node service deployment request; Determine the node to be deployed and the deployment information based on the service type and the node service deployment request.

4. The node service deployment method according to claim 1, characterized in that After judging whether the network connectivity between the local and the node to be deployed is normal, it further includes: If the network connectivity between the local and the node to be deployed is abnormal, then generate a network connectivity re-detection request or a node name re-detection request; Send the network connectivity re-detection request or the node name re-detection request to the local.

5. The node service deployment method according to claim 1, wherein After judging whether there is a historical service unique identifier in the local that is the same as the service unique identifier in the information of the node to be deployed, it further includes: If there is a historical service unique identifier in the local that is the same as the service unique identifier in the information of the node to be deployed, then create a service directory according to business requirements and generate a configuration file; Modify the configuration parameters in the configuration file according to the port number and the service unique identifier in the deployment information.

6. The node service deployment method according to claim 1, characterized in that The performing the service deployment start operation on the formatted node to be deployed based on the deployment information includes: Execute a preset file system mounting command on the formatted node to be deployed through a security protocol to obtain the node to be deployed after the command is executed; Perform a service deployment start operation on the node to be deployed after the command is executed based on the deployment information.

7. The node service deployment method according to any one of claims 1 to 6, characterized in that After obtaining the node after service deployment, it further includes: Obtain the service status and configuration information of all the nodes after service deployment; Generate the directory to which the service belongs based on the service status and the configuration information, and save the directory to which the service belongs locally.

8. A node service deployment device, characterized in that, Including: A node service deployment request acquisition module, configured to acquire a node service deployment request, and determine a node to be deployed and deployment information based on the node service deployment request; A connectivity judgment module, configured to judge whether the network connectivity between the local device and the node to be deployed is normal. If the network connectivity between the local device and the node to be deployed is normal, then judge whether the disk to which the node in the deployment information belongs exists. If the disk to which the node in the deployment information belongs exists, then determine the deployment capacity value in the deployment information; A capacity value judgment module, configured to acquire the remaining capacity value of the local device, and judge whether the remaining capacity value is greater than the deployment capacity value. If the remaining capacity value is greater than the deployment capacity value, then determine the service unique identifier in the deployment information; A service unique identifier judgment module, configured to judge whether there is a historical service unique identifier identical to the service unique identifier in the information of the node to be deployed locally. If there is no historical service unique identifier identical to the service unique identifier in the information of the node to be deployed locally, then format the node to be deployed to obtain a formatted node to be deployed; A node service deployment module, configured to perform a service deployment start operation on the formatted node to be deployed based on the deployment information to obtain a node after service deployment.

9. An electronic device, characterized in that, Including: A memory, configured to save a computer program; A processor, configured to execute the computer program to implement the node service deployment method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, For saving a computer program; wherein, when the computer program is executed by the processor, the node service deployment method according to any one of claims 1 to 7 is implemented.

Images