Desktop cloud lightweight two-copy storage cluster deployment method and system

Abstract

The invention relates to the technical field of cloud information, in particular to a desktop cloud lightweight two-copy storage cluster deployment method and system. According to the desktop cloud lightweight two-copy storage cluster deployment method, single-node disk data forms a two-copy storage cluster by using a DRBD distributed storage system, and real-time cross-node synchronization is performed to ensure high reliability of the data; an additional diskless node is configured in the cluster and serves as a third-party diskless arbitration node in the two-copy cluster, so that the problem of split brain caused by mutual scrambling of resources after the heartbeat connection of the cluster is interrupted is solved. According to the desktop cloud lightweight two-copy storage cluster deployment method and system, the split-brain problem of two nodes of a DRBD distributed storage system is solved, disk resources of all computing nodes can be fully utilized, the utilization rate of node disks is increased, and the overall hardware cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of cloud information technology, and in particular to a desktop cloud lightweight two-copy storage cluster deployment method and system. Background Art

[0002] Currently, desktop cloud vendors mostly use OpenStack components to provide virtual machines and virtual machine disks. For existing desktop clouds that use files as the virtual machine disk storage backend, virtual machine disk data is only stored in a single computing node. If a computing node is shut down or fails, the virtual machine on this computing node will be unusable due to disk damage, resulting in business interruption or even data loss.

[0003] The usual solution is to configure two dedicated storage nodes as a primary and backup storage cluster, or use distributed storage similar to the Ceph distributed storage system.

[0004] If a dedicated storage cluster is used, all disks are generally required to be concentrated in two storage nodes, and the disks of other nodes often cannot be used.

[0005] If a storage cluster similar to the Ceph distributed storage system is used, it will lead to higher computing, storage, and network resource usage, higher management and maintenance complexity, and higher hardware costs.

[0006] DRBD is a distributed storage system in the storage layer of the Linux kernel. The DRBD distributed storage system can be used to share block devices, file systems and data between two Linux servers, which is similar to the function of a network RAID-1 (remote mirroring).

[0007] When the user writes data to the local file system, the data written to the local disk will also be sent to another host in the network. It is recorded in a file system in the same form. The data of the local (primary node) and remote host (standby node) can be synchronized in real time. When the local system fails, a copy of the same data is retained on the remote host and can continue to be used. Using the DRBD distributed storage system function in high availability (HA) can replace the use of a shared disk array. Because the data exists on both the local host and the remote host, when a single node fails and node switching is required, the remote host can continue to provide services by using the backup data on the standby node.

[0008] The process of manually configuring and debugging the DRBD distributed storage system software is usually complicated. In addition, due to the master-slave mode of the two nodes, once the heartbeat network between the two nodes is abnormal, the master and the standby nodes will think that the other node is faulty and force themselves to switch to the master node. This will lead to serious brain split behavior, inconsistent data between the two nodes, loss of synchronous backup function, and inability to provide external disk read and write services.

[0009] Since the installation and configuration process of the DRBD distributed storage system is relatively complicated, and once a cluster split-brain occurs, the fault repair is difficult and complicated, which reduces the popularity of the software and increases the maintenance cost of this software.

[0010] In view of the above problems, the present invention proposes a desktop cloud lightweight two-copy storage cluster deployment method and system. Summary of the invention

[0011] In order to overcome the defects of the prior art, the present invention provides a simple and efficient desktop cloud lightweight two-copy storage cluster deployment method and system.

[0012] The present invention is achieved through the following technical solutions:

[0013] A desktop cloud lightweight two-copy storage cluster deployment method, characterized in that: single-node disk data is formed into a two-copy storage cluster using a DRBD distributed storage system, and real-time cross-node synchronization is performed to ensure high data reliability;

[0014] Configure additional diskless nodes in the cluster as third-party diskless arbitration nodes in the secondary replica cluster to avoid resource contention and split-brain problems after the cluster heartbeat connection is interrupted.

[0015] Better yet, on the same cloud platform, multiple DRBD distributed storage system clusters are configured on all computing nodes, and diskless arbitration nodes are cross-multiplexed to avoid excessive concentration of storage resources and bottlenecks in single-node storage capacity, thereby minimizing waste of storage resources.

[0016] The following steps are involved:

[0017] Step S1, compile a DRBD distributed storage system cluster planning file;

[0018] In the DRBD distributed storage system cluster planning file, configure the following:

[0019] drbd_hosts: the planned host names of the primary and backup DRBD distributed storage system clusters;

[0020] storage_vip: keepalived access cluster VIP;

[0021] arbitration_host: a diskless arbitration node in a cluster that is reused when multiple DRBD distributed storage systems are deployed in a cluster;

[0022] drbd_sync_disk: the name of the physical disk that the DRBD distributed storage system nodes synchronize with;

[0023] Step S2, installing the software package;

[0024] Verify the cluster parameters planned in step S1, including the primary and standby DRBD distributed storage system cluster hosts drbd_hosts and the cluster diskless arbitration node arbitration_host reused when multiple DRBD storage system clusters are deployed; and install the keepalived software package and the DRBD distributed storage system software package;

[0025] Step S3, generate a keepalived random access password and configure the corresponding keepalived access cluster vip;

[0026] Generate a keepalived random access password and unique identifier route_id for each set of nodes in the master and standby DRBD distributed storage system cluster host drbd_host planned above, and add the vrrp_instance configuration corresponding to the keepalived access cluster vip;

[0027] Step S4, configuring a DRBD distributed storage system communication port for the first group of clusters;

[0028] Generate a DRBD distributed storage system virtual machine disk configuration file for the first set of active and standby DRBD distributed storage system cluster hosts drbd_host;

[0029] Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host respectively;

[0030] Step S5, configuring a DRBD distributed storage system communication port for the second group of clusters;

[0031] Generate the DRBD distributed storage system virtual machine disk drbd0 configuration file for the second set of active and standby DRBD distributed storage system cluster hosts drbd_host;

[0032] The second group of active and standby DRBD distributed storage system cluster hosts and the first group of active and standby DRBD distributed storage system cluster hosts drbd_host use the same third-party node as the diskless arbitration node;

[0033] Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host, and the diskless arbitration nodes use new cluster internal communication ports that are different from the first group to avoid conflicts with the first group of cluster communication ports;

[0034] The first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster reuse third-party nodes as diskless arbitration nodes to avoid the arbitration brain split problem common in the two node clusters;

[0035] Add new DRBD distributed storage system configuration groups to the remaining nodes in the cluster to fully utilize the disks of all nodes.

[0036] In the step S1, a network file system service nfs-server is installed for each group of clusters in the planned primary and backup DRBD distributed storage system cluster host drbd_host, so that users can access the disk data in the cluster through each group of dedicated keepalived access cluster vip.

[0037] In step S4, the data nodes k122 / k123 of the DRBD distributed storage system cluster host use the internal communication port 7789; the diskless arbitration node k126 of the DRBD distributed storage system cluster host uses the internal communication port 17789;

[0038] In step S5, the data nodes k124 / k125 of the DRBD distributed storage system cluster host use the internal communication port 7789; the diskless arbitration node k126 of the DRBD distributed storage system cluster host uses the internal communication port 17790;

[0039] The k126 nodes reused by the first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster serve as diskless arbitration nodes.

[0040] A desktop cloud lightweight two-copy storage cluster deployment system, comprising:

[0041] The planning file writing module is responsible for writing the DRBD distributed storage system cluster planning file and configuring the following contents in the DRBD distributed storage system cluster planning file:

[0042] drbd_hosts: the planned host names of the primary and backup DRBD distributed storage system clusters;

[0043] storage_vip: keepalived access cluster VIP;

[0044] arbitration_host: a diskless arbitration node in a cluster that is reused when multiple DRBD distributed storage systems are deployed in a cluster;

[0045] drbd_sync_disk: the name of the physical disk that the DRBD distributed storage system nodes synchronize with;

[0046] The software package installation module is responsible for verifying the cluster parameters planned by the planning file writing module, including the primary and standby DRBD distributed storage system cluster hosts drbd_hosts and the cluster diskless arbitration node arbitration_host reused when multiple DRBD storage system clusters are deployed; and installing the keepalived software package and the DRBD distributed storage system software package;

[0047] The keepalived configuration module is responsible for generating the keepalived random access password and unique identifier route_id for each node in the planned primary and standby DRBD distributed storage system cluster host drbd_host, and adding the vrrp_instance configuration corresponding to the keepalived access cluster vip (storage_vip);

[0048] The communication port configuration module is responsible for configuring the DRBD distributed storage system communication ports for the two clusters respectively, as follows:

[0049] Generate a DRBD distributed storage system virtual machine disk configuration file for the first group of active and standby DRBD distributed storage system cluster hosts drbd_host; configure different internal communication ports for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster hosts respectively;

[0050] Generate a DRBD distributed storage system virtual machine disk drbd0 configuration file for the second group of active and standby DRBD distributed storage system cluster hosts drbd_host; the second group of active and standby DRBD distributed storage system cluster hosts and the first group of active and standby DRBD distributed storage system cluster hosts drbd_host use the same third-party node as the diskless arbitration node;

[0051] Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host, and the diskless arbitration nodes use new cluster internal communication ports that are different from the first group to avoid conflicts with the first group of cluster communication ports;

[0052] The first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster reuse third-party nodes as diskless arbitration nodes to avoid the arbitration brain split problem common in the two node clusters;

[0053] At the same time, add new DRBD distributed storage system configuration groups to the remaining nodes in the cluster to fully utilize the disks of all nodes.

[0054] A desktop cloud lightweight two-copy storage cluster deployment computing device, characterized by: comprising:

[0055] One or more processors, one or more memories, and one or more programs, wherein the one or more programs are stored in the one or more memories and are configured to be executed by the one or more processors, and the one or more programs include instructions for executing any of the above methods.

[0056] A computer-readable storage medium storing one or more programs, characterized in that: the one or more programs include instructions, and when the instructions are executed by a desktop cloud lightweight two-copy storage cluster deployment computing device, the desktop cloud lightweight two-copy storage cluster deployment computing device executes any of the above methods.

[0057] The beneficial effects of the present invention are as follows: the desktop cloud lightweight two-copy storage cluster deployment method and system not only solves the brain split problem existing in two nodes of the DRBD distributed storage system, but also can fully utilize the disk resources of all computing nodes, improve the node disk utilization rate, and reduce the overall hardware cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0059] Attached Figure 1 It is a schematic diagram of the desktop cloud lightweight two-copy storage cluster deployment method of the present invention. DETAILED DESCRIPTION

[0060] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0061] This desktop cloud lightweight two-copy storage cluster deployment method uses the DRBD distributed storage system to form a two-copy storage cluster for single-node disk data, and performs real-time cross-node synchronization to ensure high data reliability.

[0062] Configure additional diskless nodes in the cluster as third-party diskless arbitration nodes in the secondary replica cluster to avoid resource contention and split-brain problems after the cluster heartbeat connection is interrupted.

[0063] Better yet, on the same cloud platform, multiple DRBD distributed storage system clusters are configured on all computing nodes, and diskless arbitration nodes are cross-multiplexed to avoid excessive concentration of storage resources and bottlenecks in single-node storage capacity, thereby minimizing waste of storage resources.

[0064] The following steps are involved:

[0065] Step S1, compile a DRBD distributed storage system cluster planning file;

[0066] {"drbd_hosts":[

[0067] {"hosts":["k122","k123"],"storage_vip":"87.87.87.195"},

[0068] {"hosts":["k124","k125"],"storage_vip":"87.87.87.196"}

[0069] ],"arbitration_host":"k126","drbd_sync_disk":" / dev / sdf"}

[0070] In the DRBD distributed storage system cluster planning file, configure the following:

[0071] drbd_hosts: the planned host names of the primary and backup DRBD distributed storage system clusters;

[0072] storage_vip: keepalived access cluster VIP;

[0073] arbitration_host: a diskless arbitration node in a cluster that is reused when multiple DRBD distributed storage systems are deployed in a cluster;

[0074] drbd_sync_disk: the name of the physical disk that the DRBD distributed storage system nodes synchronize with;

[0075] Step S2, installing the software package;

[0076] Verify the cluster parameters planned in step S1, including the primary and standby DRBD distributed storage system cluster hosts drbd_hosts and the cluster diskless arbitration node arbitration_host reused when multiple DRBD storage system clusters are deployed; and install the keepalived software package and the DRBD distributed storage system software package;

[0077] Step S3, generate a keepalived random access password and configure the corresponding keepalived access cluster vip;

[0078] Generate a keepalived random access password and unique identifier route_id for each set of nodes in the master and standby DRBD distributed storage system cluster host drbd_host planned above, such as k122", "k123", and add the vrrp_instance configuration corresponding to the keepalived access cluster vip (storage_vip);

[0079] Step S4, configuring a DRBD distributed storage system communication port for the first group of clusters;

[0080] Generate a DRBD distributed storage system virtual machine disk configuration file for the first set of active and standby DRBD distributed storage system cluster hosts drbd_host;

[0081] Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host respectively;

[0082] Step S5, configuring a DRBD distributed storage system communication port for the second group of clusters;

[0083] Generate the DRBD distributed storage system virtual machine disk drbd0 configuration file for the second set of active and standby DRBD distributed storage system cluster hosts drbd_host;

[0084] The second group of active and standby DRBD distributed storage system cluster hosts and the first group of active and standby DRBD distributed storage system cluster hosts drbd_host use the same third-party node as the diskless arbitration node;

[0085] Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host, and the diskless arbitration nodes use new cluster internal communication ports that are different from the first group to avoid conflicts with the first group of cluster communication ports;

[0086] The first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster reuse third-party nodes as diskless arbitration nodes to avoid the arbitration brain split problem common in the two node clusters;

[0087] Add new DRBD distributed storage system configuration groups to the remaining nodes in the cluster to fully utilize the disks of all nodes.

[0088] In the step S1, a network file system service nfs-server is installed for each group of clusters in the planned primary and backup DRBD distributed storage system cluster host drbd_host, so that users can access the disk data in the cluster through each group of dedicated keepalived access cluster vip.

[0089] In step S4, the data nodes k122 / k123 of the DRBD distributed storage system cluster host use the internal communication port 7789; the diskless arbitration node k126 of the DRBD distributed storage system cluster host uses the internal communication port 17789;

[0090] resource drbd0{

[0091] on k122

[0092] device / dev / drbd0;

[0093] disk / dev / sdf;

[0094] meta-disk internal;

[0095] address 87.87.87.122:7789;

[0096] node-id 0;

[0097] }

[0098] on k123

[0099] device / dev / drbd0;

[0100] disk / dev / sdf;

[0101] meta-disk internal;

[0102] address 87.87.87.123:7789;

[0103] node-id 1;

[0104] }

[0105] on k126

[0106] device / dev / drbd0;

[0107] disk none;

[0108] meta-disk internal;

[0109] address 87.87.87.126:17789;

[0110] node-id 2;

[0111] }

[0112] connection-mesh

[0113] hosts k122 k123 k126;

[0114] net{

[0115] use-rle no;

[0116] }

[0117] }

[0118] }

[0119] In step S5, the data nodes k124 / k125 of the DRBD distributed storage system cluster host use the internal communication port 7789; the diskless arbitration node k126 of the DRBD distributed storage system cluster host uses the internal communication port 17790;

[0120] The k126 nodes reused by the first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster serve as diskless arbitration nodes.

[0121]

[0122]

[0123] The desktop cloud lightweight two-copy storage cluster deployment system includes:

[0124] The planning file writing module is responsible for writing the DRBD distributed storage system cluster planning file and configuring the following contents in the DRBD distributed storage system cluster planning file:

[0125] drbd_hosts: the planned host names of the primary and backup DRBD distributed storage system clusters;

[0126] storage_vip: keepalived access cluster VIP;

[0127] arbitration_host: a diskless arbitration node in a cluster that is reused when multiple DRBD distributed storage systems are deployed in a cluster;

[0128] drbd_sync_disk: the name of the physical disk that the DRBD distributed storage system nodes synchronize with;

[0129] The software package installation module is responsible for verifying the cluster parameters planned by the planning file writing module, including the primary and standby DRBD distributed storage system cluster hosts drbd_hosts and the cluster diskless arbitration node arbitration_host reused when multiple DRBD storage system clusters are deployed; and installing the keepalived software package and the DRBD distributed storage system software package;

[0130] The keepalived configuration module is responsible for generating the keepalived random access password and unique identifier route_id for each node in the planned primary and standby DRBD distributed storage system cluster host drbd_host, and adding the vrrp_instance configuration corresponding to the keepalived access cluster vip (storage_vip);

[0131] The communication port configuration module is responsible for configuring the DRBD distributed storage system communication ports for the two clusters respectively, as follows:

[0132] Generate a DRBD distributed storage system virtual machine disk configuration file for the first group of active and standby DRBD distributed storage system cluster hosts drbd_host; configure different internal communication ports for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster hosts respectively;

[0133] Generate a DRBD distributed storage system virtual machine disk drbd0 configuration file for the second group of active and standby DRBD distributed storage system cluster hosts drbd_host; the second group of active and standby DRBD distributed storage system cluster hosts and the first group of active and standby DRBD distributed storage system cluster hosts drbd_host use the same third-party node as the diskless arbitration node;

[0134] Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host, and the diskless arbitration nodes use new cluster internal communication ports that are different from the first group to avoid conflicts with the first group of cluster communication ports;

[0135] The first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster reuse third-party nodes as diskless arbitration nodes to avoid the arbitration brain split problem common in the two node clusters;

[0136] At the same time, add new DRBD distributed storage system configuration groups to the remaining nodes in the cluster to fully utilize the disks of all nodes.

[0137] The desktop cloud lightweight two-copy storage cluster deploys computing devices, including:

[0138] One or more processors, one or more memories, and one or more programs, wherein the one or more programs are stored in the one or more memories and are configured to be executed by the one or more processors, and the one or more programs include instructions for executing any of the above methods.

[0139] The computer-readable storage medium stores one or more programs, wherein the one or more programs include instructions, and when the instructions are executed by a desktop cloud lightweight two-copy storage cluster deployment computing device, the desktop cloud lightweight two-copy storage cluster deployment computing device executes any one of the above methods.

[0140] The desktop cloud lightweight two-copy storage cluster deployment method and system solves the problem of resource competition and brain split that is prone to occur after the cluster heartbeat connection is interrupted by introducing a third-party arbitration node in the two-copy cluster; at the same time, it supports the configuration of multiple DRBD distributed storage system clusters on all computing nodes on the same cloud platform, avoiding excessive concentration of storage resources and bottlenecks of single-node storage capacity, and minimizing storage resource waste; it has the advantages of saving resources, unified and standardized configuration, and both high performance and high reliability.

[0141] The embodiment described above is only one specific implementation of the present invention. Common changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included in the protection scope of the present invention.

Claims

1. A desktop cloud lightweight two-copy storage cluster deployment method, characterized by: The single-node disk data is organized into two-copy storage clusters using the DRBD distributed storage system, and real-time cross-node synchronization is performed to ensure high data reliability. Configure additional diskless nodes in the cluster as third-party diskless arbitration nodes in the secondary replica cluster to avoid resource contention and split-brain problems after the cluster heartbeat connection is interrupted.

2. The method for deploying a lightweight two-copy storage cluster for a desktop cloud according to claim 1, characterized in that: On the same cloud platform, multiple DRBD distributed storage system clusters are configured on all computing nodes, and diskless arbitration nodes are cross-multiplexed to avoid excessive concentration of storage resources and bottlenecks of single-node storage capacity, thereby minimizing waste of storage resources.

3. The method for deploying a lightweight two-copy storage cluster for a desktop cloud according to claim 2, characterized in that: The following steps are involved: Step S1, compile a DRBD distributed storage system cluster planning file; In the DRBD distributed storage system cluster planning file, configure the following: drbd_hosts: the planned host names of the primary and backup DRBD distributed storage system clusters; storage_vip: keepalived access cluster VIP; arbitration_host: a diskless arbitration node in a cluster that is reused when multiple DRBD distributed storage systems are deployed in a cluster; drbd_sync_disk: the name of the physical disk that the DRBD distributed storage system nodes synchronize with; Step S2, installing the software package; Verify the cluster parameters planned in step S1, including the primary and standby DRBD distributed storage system cluster hosts drbd_hosts and the cluster diskless arbitration node arbitration_host reused when multiple DRBD storage system clusters are deployed; Install the keepalived package and the DRBD distributed storage system package; Step S3, generate a keepalived random access password and configure the corresponding keepalived access cluster vip; Generate a keepalived random access password and unique identifier route_id for each set of nodes in the master and standby DRBD distributed storage system cluster host drbd_host planned above, and add the vrrp_instance configuration corresponding to the keepalived access cluster vip; Step S4, configuring a DRBD distributed storage system communication port for the first group of clusters; Generate a DRBD distributed storage system virtual machine disk configuration file for the first set of active and standby DRBD distributed storage system cluster hosts drbd_host; Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host respectively; Step S5, configuring a DRBD distributed storage system communication port for the second group of clusters; Generate the DRBD distributed storage system virtual machine disk drbd0 configuration file for the second set of active and standby DRBD distributed storage system cluster hosts drbd_host; The second group of active and standby DRBD distributed storage system cluster hosts and the first group of active and standby DRBD distributed storage system cluster hosts drbd_host use the same third-party node as the diskless arbitration node; Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host, and the diskless arbitration nodes use new cluster internal communication ports that are different from the first group to avoid conflicts with the first group of cluster communication ports; The first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster reuse third-party nodes as diskless arbitration nodes to avoid the arbitration brain split problem common in the two node clusters; Add new DRBD distributed storage system configuration groups to the remaining nodes in the cluster to fully utilize the disks of all nodes.

4. The method for deploying a lightweight two-copy storage cluster for a desktop cloud according to claim 3 is characterized in that: In the step S1, a network file system service nfs-server is installed for each group of clusters in the planned primary and backup DRBD distributed storage system cluster host drbd_host, so that users can access the disk data in the cluster through each group of dedicated keepalived access cluster vip.

5. The method for deploying a lightweight two-copy storage cluster for a desktop cloud according to claim 3, characterized in that: In step S4, the data nodes k122 / k123 of the DRBD distributed storage system cluster host use the internal communication port 7789; the diskless arbitration node k126 of the DRBD distributed storage system cluster host uses the internal communication port 17789; In step S5, the data nodes k124 / k125 of the DRBD distributed storage system cluster host use the internal communication port 7789; the diskless arbitration node k126 of the DRBD distributed storage system cluster host uses the internal communication port 17790; The k126 nodes reused by the first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster serve as diskless arbitration nodes.

6. A desktop cloud lightweight two-copy storage cluster deployment system, characterized by: include: The planning file writing module is responsible for writing the DRBD distributed storage system cluster planning file and configuring the following contents in the DRBD distributed storage system cluster planning file: drbd_hosts: the planned host names of the primary and backup DRBD distributed storage system clusters; storage_vip: keepalived access cluster VIP; arbitration_host: a diskless arbitration node in a cluster that is reused when multiple DRBD distributed storage systems are deployed in a cluster; drbd_sync_disk: the name of the physical disk that the DRBD distributed storage system nodes synchronize with; The software package installation module is responsible for verifying the cluster parameters planned by the planning file writing module, including the primary and standby DRBD distributed storage system cluster hosts drbd_hosts and the cluster diskless arbitration node arbitration_host reused when multiple DRBD storage system clusters are deployed; and installing the keepalived software package and the DRBD distributed storage system software package; The keepalived configuration module is responsible for generating the keepalived random access password and unique identifier route_id for each node in the planned primary and standby DRBD distributed storage system cluster host drbd_host, and adding the vrrp_instance configuration corresponding to the keepalived access cluster vip; The communication port configuration module is responsible for configuring the DRBD distributed storage system communication ports for the two clusters respectively, as follows: Generate a DRBD distributed storage system virtual machine disk configuration file for the first set of active and standby DRBD distributed storage system cluster hosts drbd_host; Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host respectively; Generate the DRBD distributed storage system virtual machine disk drbd0 configuration file for the second set of active and standby DRBD distributed storage system cluster hosts drbd_host; The second group of active and standby DRBD distributed storage system cluster hosts and the first group of active and standby DRBD distributed storage system cluster hosts drbd_host use the same third-party node as the diskless arbitration node; Different internal communication ports are configured for the data nodes and diskless arbitration nodes of the DRBD distributed storage system cluster host, and the diskless arbitration nodes use new cluster internal communication ports that are different from the first group to avoid conflicts with the first group of cluster communication ports; The first DRBD distributed storage system cluster and the second DRBD distributed storage system cluster reuse third-party nodes as diskless arbitration nodes to avoid the arbitration brain split problem common in the two node clusters; At the same time, add new DRBD distributed storage system configuration groups to the remaining nodes in the cluster to fully utilize the disks of all nodes.

7. A desktop cloud lightweight two-copy storage cluster deployment computing device, characterized by: include: One or more processors, one or more memories, and one or more programs, wherein the one or more programs are stored in the one or more memories and are configured to be executed by the one or more processors, and the one or more programs include instructions for executing any of the methods according to claims 1 to 5.

8. A computer-readable storage medium storing one or more programs, characterized in that: The one or more programs include instructions, which, when executed by a desktop cloud lightweight two-copy storage cluster deployment computing device, enable the desktop cloud lightweight two-copy storage cluster deployment computing device to execute any one of the methods according to claims 1 to 5.

Images