Hyper-converged software-defined storage deployment method, apparatus, device, and medium

Abstract

The application discloses a hyper-converged software-defined storage deployment method, and relates to the fields of cloud computing and storage virtualization. The method comprises the following steps: reserving target resources for a software-defined storage node in a physical server, so as to ensure normal operation of the software-defined storage node; creating a data network on the physical server based on a selected target pass-through network card, so as to use the data network as a communication network between the software-defined storage nodes in different physical server nodes and as a network for connecting the physical server by the hyper-converged software-defined storage to provide storage services; and constructing a storage space corresponding to the software-defined storage node by using a selected target physical disk. Therefore, the application improves the performance of the hyper-converged software-defined storage.

Description

Technical Field

[0001] This invention relates to the fields of cloud computing and storage virtualization, and in particular to a method, apparatus, device and medium for deploying hyperconverged software-defined storage. Background Technology

[0002] Currently, the traditional deployment method for SDS (software-defined storage) is to use system virtual machines, that is, to build system virtual machines as SDS nodes on physical servers to form a nested system, and to build a hyperconverged environment using system virtual machines as SDS nodes.

[0003] However, because the system virtual machines in ARM (Advanced RISC Machines) servers do not support pass-through of hardware resources such as RAID (Redundant Array of Independent Disks) cards and network cards, servers with this architecture cannot be deployed with hyperconverged SDS in the traditional way. In addition, when deploying using the traditional method, the virtualization system needs to come with its own image, which is used to create the system virtual machines in the nested system. This results in an excessively large image and a complicated process. At the same time, because the traditional deployment method adds a layer of system virtual machines, the performance of hyperconverged SDS will also suffer to some extent.

[0004] In conclusion, improving the performance of hyperconverged software-defined storage has become an urgent problem to be solved. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide a method, apparatus, device, and medium for deploying hyperconverged software-defined storage, which can improve the performance of hyperconverged software-defined storage. The specific solution is as follows:

[0006] In a first aspect, this application discloses a method for deploying hyperconverged software-defined storage, including:

[0007] Reserve target resources in the physical server for the software-defined storage node to ensure the normal operation of the software-defined storage node;

[0008] A data network is created on the physical server based on the selected target pass-through network card, so that the data network can be used as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services.

[0009] The storage space corresponding to the software-defined storage node is constructed using the selected target physical disk.

[0010] Optionally, the step of creating a data network on the physical server based on the selected target pass-through network interface card includes:

[0011] A virtual storage switch is created on the physical server based on the selected target pass-through network card, and a data network is created based on the virtual storage switch.

[0012] Optionally, after creating the data network on the physical server, the process further includes:

[0013] Create network ports for the data network and configure network interconnection protocols for the network ports.

[0014] Optionally, before constructing the storage space corresponding to the software-defined storage node using the selected target physical disk, the method further includes:

[0015] Based on a preset disk ratio, a first preset number of solid-state drives and a second preset number of hard disk drives are selected as the target physical disks corresponding to the software-defined storage nodes.

[0016] Optionally, constructing the storage space corresponding to the software-defined storage node using the selected target physical disk includes:

[0017] The selected solid-state drive is used to construct the cache space corresponding to the software-defined storage node, and the selected hard disk drive is used to construct the data space corresponding to the software-defined storage node.

[0018] Optionally, the hyperconverged software-defined storage deployment method further includes:

[0019] Configure a configuration file for the software-defined storage node in the physical server to monitor the software-defined storage node.

[0020] Optionally, the target physical disk includes several disks in a redundant disk array card and / or a non-volatile memory disk; the target resources include central processing unit resources and memory resources.

[0021] Secondly, this application discloses a hyperconverged software-defined storage deployment device, comprising:

[0022] The resource reservation module is used to reserve target resources for the software-defined storage node in the physical server to ensure the normal operation of the software-defined storage node;

[0023] A network creation module is used to create a data network on the physical server based on a selected target pass-through network card, so that the data network can be used as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services.

[0024] The storage space construction module is used to construct the storage space corresponding to the software-defined storage node using the selected target physical disk.

[0025] Thirdly, this application discloses an electronic device, including a processor and a memory; wherein, when the processor executes a computer program stored in the memory, it implements the aforementioned disclosed hyperconverged software-defined storage deployment method.

[0026] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned disclosed hyperconverged software-defined storage deployment method.

[0027] As can be seen, this application reserves target resources for software-defined storage nodes in the physical server to ensure the normal operation of the software-defined storage nodes; a data network is created on the physical server based on the selected target pass-through network interface card (NIC), so that the data network serves as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services; and the storage space corresponding to the software-defined storage node is constructed using the selected target physical disk. Therefore, this application creates a data network on the physical server based on the selected target pass-through NIC, realizing that the communication network and the network providing storage services are the same network, reducing network complexity and further improving the performance of the hyperconverged software-defined storage. Attached Figure Description

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

[0029] Figure 1 A flowchart of a hyperconverged software-defined storage method provided in this application;

[0030] Figure 2 A flowchart illustrating a specific hyperconverged software-defined storage deployment method provided in this application;

[0031] Figure 3 A flowchart illustrating a specific method for determining the number of hyperconverged software-defined storage users provided in this application;

[0032] Figure 4 A schematic diagram of a hyperconverged software-defined storage deployment method provided in this application;

[0033] Figure 5 A schematic diagram of a traditional hyperconverged software-defined storage deployment method;

[0034] Figure 6 A schematic diagram of a hyperconverged software-defined storage deployment method provided in this application;

[0035] Figure 7 A schematic diagram of a hyperconverged software-defined storage deployment device is provided for this application;

[0036] Figure 8 A schematic diagram of an electronic structure provided for this application. Detailed Implementation

[0037] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0038] Currently, because the system virtual machines in ARM (Advanced RISC Machines) servers do not support pass-through of hardware resources such as RAID (Redundant Array of Independent Disks) cards and network cards, servers with this architecture cannot be deployed with hyperconverged SDS in the traditional way. In addition, when deploying using the traditional method, the virtualization system needs to come with its own image, which is used to create the system virtual machines in the nested system. This results in excessively large images and a complicated process. At the same time, because the traditional deployment method adds a layer of system virtual machines, the performance of hyperconverged SDS will also suffer to some extent.

[0039] To overcome the above problems, this application provides a hyperconverged software-defined storage deployment solution that can improve the performance of hyperconverged software-defined storage.

[0040] See Figure 1 As shown in the figure, this application discloses a hyperconverged software-defined storage deployment method, which includes:

[0041] Step S11: Reserve target resources for the software-defined storage node in the physical server to ensure the normal operation of the software-defined storage node.

[0042] In this embodiment of the application, before reserving target resources for software-defined storage nodes in the physical server, a virtualization system is installed in the physical server, and the deployment installation package is integrated into the virtualization system.

[0043] In this embodiment, the control group function of the Linux kernel is used to reserve target resources for software-defined storage nodes in a physical server. These target resources include central processing unit (CPU) resources and memory resources. The target resources are those necessary to ensure the normal operation of the software-defined storage nodes. Specifically, the target resources are reserved in the physical server according to a preset resource reservation scheme. That is, the control group function of the Linux kernel is used to reserve target resources for the software-defined storage nodes in the physical server based on the amount of resources needed to ensure their normal operation. It should be noted that the control group function of the Linux kernel is used to limit and control the reserved target resources.

[0044] In this embodiment of the application, target resources are reserved in the physical server for the software-defined storage node, and the target resources are isolated to ensure that the target resources are used only for the hyperconverged software-defined storage; that is, a specific size of resources is reserved and isolated. It can be understood that the reserved CPU (central processing unit) resources and memory resources are guaranteed not to be used by other systems, processes or programs, the independence of the central processing unit resources and memory resources is guaranteed, and sufficient resources are guaranteed for the operation of the software-defined storage node.

[0045] In this embodiment of the application, the number of corresponding physical servers in the hyperconverged software-defined storage is several, that is, the number of software-defined storage nodes constituting the hyperconverged software-defined storage is several, which is not specifically limited here; it should be noted that the information stored in the hyperconverged software-defined storage is common to all software-defined storage nodes.

[0046] Step S12: Create a data network on the physical server based on the selected target pass-through network card, so that the data network can serve as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services.

[0047] In this embodiment, after the operator selects the target passthrough network interface card (NIC) on the front-end page, a data network is created on the physical server based on the selected NIC. This data network serves as both a communication network between the software-defined storage nodes on different physical server nodes and a network connecting the hyperconverged software-defined storage to the physical server to provide storage services. It should be noted that the communication network and the network providing storage services use the same data network, which reduces network complexity. Essentially, the data network serves as both a communication network between software-defined storage nodes and a network connecting to the storage services provided by the hyperconverged software-defined storage; the creation of network resources is integrated into the deployment process of the hyperconverged software-defined storage, simplifying the operation of the front-end interface.

[0048] In this embodiment of the application, the step of selecting the target pass-through network card can be completed before reserving target resources for the software-defined storage node in the physical server, or before creating a data network on the physical server based on the selected target pass-through network card. No specific limitation is made here.

[0049] In this embodiment, a data network is created instead of adding a system virtual machine to the physical server. This transfers control of the software-defined storage node from the system virtual machine to the physical server, i.e., the host, reducing deployment steps and improving performance. It should be noted that traditional methods add a system virtual machine and use it as the software-defined storage node, while this application does not add a system virtual machine but uses the physical server as the carrier. Furthermore, since there is no system virtual machine, the problem of traditional deployment methods (system virtual machine method) not supporting hardware passthrough (such as network card passthrough) on ARM architecture servers is solved, eliminating dependence on traditional deployment methods, avoiding system nesting, and significantly improving the performance of the hyperconverged software-defined storage node.

[0050] Step S13: Construct the storage space corresponding to the software-defined storage node using the selected target physical disk.

[0051] In this embodiment, the selected target physical disk is used to construct the storage space corresponding to the software-defined storage node, so as to realize the storage service of hyperconverged software-defined storage.

[0052] In this embodiment of the application, the target physical disk is selected before reserving target resources for the software-defined storage node in the physical server, or before constructing the storage space corresponding to the software-defined storage node using the selected target physical disk; no specific limitation is made here.

[0053] In this embodiment of the application, it is necessary to configure configuration files for the software-defined storage nodes in the physical server in order to monitor the software-defined storage nodes. Furthermore, after installing the configuration files and starting the monitoring and other services of the hyperconverged software-defined storage, all configuration files are used to monitor the real-time operating status and resource usage of the hyperconverged software-defined storage.

[0054] In this embodiment of the application, after configuring the configuration file for the software-defined storage node in the physical server, it is also necessary to use hyperconverged software-defined storage. The deployment is completed when all services in the physical servers are normal and the service information is displayed normally.

[0055] As can be seen, this application reserves target resources for software-defined storage nodes in the physical server to ensure the normal operation of the software-defined storage nodes; a data network is created on the physical server based on the selected target pass-through network interface card (NIC), so that the data network serves as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services; and the storage space corresponding to the software-defined storage node is constructed using the selected target physical disk. Therefore, this application creates a data network on the physical server based on the selected target pass-through NIC, realizing that the communication network and the network providing storage services are the same network, reducing network complexity and further improving the performance of the hyperconverged software-defined storage.

[0056] See Figure 2 As shown in the figure, this application discloses a specific hyperconverged software-defined storage method, which includes:

[0057] Step S21: Reserve target resources for the software-defined storage node in the physical server to ensure the normal operation of the software-defined storage node.

[0058] In this embodiment, the control group function of the Linux kernel is used to reserve target resources for software-defined storage nodes in a physical server. These target resources include central processing unit (CPU) resources and memory resources. The target resources are those necessary to ensure the normal operation of the software-defined storage nodes. Specifically, the target resources are reserved in the physical server according to a preset resource reservation scheme. That is, the control group function of the Linux kernel is used to reserve target resources for the software-defined storage nodes in the physical server based on the amount of resources needed to ensure their normal operation. It should be noted that the control group function of the Linux kernel is used to limit and control the reserved target resources.

[0059] In this embodiment, target resources are reserved for the software-defined storage node in the physical server, and the target resources are isolated to ensure that the target resources are used only for the hyperconverged software-defined storage; that is, a specific size of resources is reserved and isolated. It can be understood that the reserved CPU (central processing unit) resources and memory resources are guaranteed not to be used by other systems, processes or programs, ensuring the independence of CPU resources and memory resources, and ensuring sufficient resources for the operation of the software-defined storage node.

[0060] Step S22: Create a virtual storage switch on the physical server based on the selected target pass-through network card, and create a data network based on the virtual storage switch, so that the data network can be used as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services.

[0061] In this embodiment, after the operator selects the target passthrough network interface card (NIC) on the front-end page, a data network is created on the physical server based on the selected NIC. This data network serves as both a communication network between the software-defined storage nodes on different physical server nodes and a network connecting the hyperconverged software-defined storage to the physical server to provide storage services. It should be noted that the communication network and the network providing storage services use the same data network, which reduces network complexity. Essentially, the data network serves as both a communication network between software-defined storage nodes and a network connecting to the storage services provided by the hyperconverged software-defined storage—a unified network. The creation of network resources is integrated into the hyperconverged software-defined storage deployment process, simplifying the front-end interface operation. It is understood that using the data network creation method for hyperconverged software-defined storage deployment effectively expands the applicability of hyperconverged systems and increases their deployment forms.

[0062] In this embodiment, a virtual storage switch is created on the physical server based on the selected target pass-through network card. After a data network is created based on the virtual storage switch, network ports are created for the data network, and network interconnection protocols are configured for the network ports; the network interconnection protocol is specifically IP (Internet Protocol) information. It should be noted that the creation of the data network must be based on the virtual storage switch.

[0063] In this embodiment, a system virtual machine is no longer added to the physical server. Instead, a data network is created, transferring control of the software-defined storage node from the system virtual machine to the physical server, i.e., the host. This reduces the deployment process and improves performance. It should be noted that traditional methods add a system virtual machine and use it as the software-defined storage node. This application does not add a system virtual machine but uses the physical server as the carrier for the software-defined storage node. It should also be noted that since there is no system virtual machine, the problem of traditional deployment methods (system virtual machine method) not supporting hardware passthrough (such as network card passthrough) on ARM architecture servers is solved. This eliminates the dependence on traditional deployment methods, avoids system nesting, and also greatly improves the performance of the hyperconverged software-defined storage node.

[0064] Step S23: Construct the storage space corresponding to the software-defined storage node using the selected target physical disk.

[0065] In this embodiment, a configuration file needs to be configured for the software-defined storage node in the physical server in order to monitor the software-defined storage node; furthermore, after installing the configuration file and starting the monitoring and other services of the hyperconverged software-defined storage, all configuration files are used to monitor the real-time operating status and resource usage of the hyperconverged software-defined storage.

[0066] In this embodiment of the application, after configuring the configuration file for the software-defined storage node in the physical server, it is also necessary to use hyperconverged software-defined storage. The deployment is completed when all services in the physical servers are normal and the service information is displayed normally.

[0067] As can be seen, this application reserves target resources for software-defined storage nodes in the physical server to ensure the normal operation of the software-defined storage nodes; it creates a virtual storage switch on the physical server based on the selected target pass-through network interface card (NIC), and creates a data network based on the virtual storage switch, so that the data network can serve as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services; and it uses the selected target physical disk to construct the storage space corresponding to the software-defined storage node. Therefore, this application creates a data network on the physical server based on the selected target pass-through network interface card, realizing that the communication network and the network providing storage services are the same network, reducing network complexity and further improving the performance of the hyperconverged software-defined storage.

[0068] See Figure 3 As shown in the figure, this application discloses a specific method for deploying hyperconverged software-defined storage, the method including:

[0069] Step S31: Reserve target resources for the software-defined storage node in the physical server to ensure the normal operation of the software-defined storage node.

[0070] In this embodiment, the control group function of the Linux kernel is used to reserve target resources for software-defined storage nodes in a physical server. These target resources include central processing unit (CPU) resources and memory resources. The target resources are those necessary to ensure the normal operation of the software-defined storage nodes. Specifically, the target resources are reserved in the physical server according to a preset resource reservation scheme. That is, the control group function of the Linux kernel is used to reserve target resources for the software-defined storage nodes in the physical server based on the amount of resources needed to ensure their normal operation. It should be noted that the control group function of the Linux kernel is used to limit and control the reserved target resources.

[0071] In this embodiment, target resources are reserved for the software-defined storage node in the physical server, and the target resources are isolated to ensure that the target resources are used only for the hyperconverged software-defined storage; that is, a specific size of resources is reserved and isolated. It can be understood that the reserved CPU (central processing unit) resources and memory resources are guaranteed not to be used by other systems, processes or programs, ensuring the independence of CPU resources and memory resources, and ensuring sufficient resources for the operation of the software-defined storage node.

[0072] Step S32: Create a data network on the physical server based on the selected target pass-through network card, so that the data network can serve as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services.

[0073] In this embodiment, the specific process of step S32 can be referred to the corresponding content disclosed in the previous embodiments, and will not be repeated here.

[0074] Step S33: Based on the preset disk ratio, select a first preset number of solid-state drives and a second preset number of hard disk drives as the target physical disks corresponding to the software-defined storage nodes.

[0075] In this embodiment, solid-state drives (SSDs) and hard disk drives (HDDs) are selected as the target physical disks corresponding to the software-defined storage node. Specifically, based on a preset disk configuration ratio, a first preset number of SSDs and a second preset number of HDDs are selected as the target physical disks corresponding to the software-defined storage node. It should be noted that the selection of disks must meet the preset disk configuration ratio.

[0076] In this embodiment, the target physical disk includes several disks in a Redundant Array of Independent Disks (RAID) card and / or non-volatile memory (NVMe) disks. It should be noted that in traditional methods, only one entire RAID card can be selected. However, in this application, the selection of physical disks is not limited by RAID cards, allowing for more flexible disk configuration. One or more disks from a RAID card can be freely selected, or NVMe disks from the server configuration can be chosen, as long as the disk type (i.e., solid-state drives and hard disk drives) matches the preset disk ratio for deployment. It is understood that freely selecting disks can effectively improve the applicability of hyperconverged infrastructure, increase the deployment forms of hyperconverged infrastructure, fully utilize the hardware resource performance of hyperconverged infrastructure, improve product diversity, and facilitate the widespread promotion and application of hyperconverged virtualization systems.

[0077] Step S34: Construct the cache space corresponding to the software-defined storage node using the selected solid-state drive and construct the data space corresponding to the software-defined storage node using the selected hard disk drive, thereby constructing the storage space corresponding to the software-defined storage node.

[0078] In this embodiment, a configuration file needs to be configured for the software-defined storage node in the physical server in order to monitor the software-defined storage node; furthermore, after installing the configuration file and starting the monitoring and other services of the hyperconverged software-defined storage, all configuration files are used to monitor the real-time operating status and resource usage of the hyperconverged software-defined storage.

[0079] In this embodiment of the application, after configuring the configuration file for the software-defined storage node in the physical server, it is also necessary to use hyperconverged software-defined storage. The deployment is completed when all services in the physical servers are normal and the service information is displayed normally.

[0080] As can be seen, this application reserves target resources for software-defined storage nodes in the physical server to ensure the normal operation of the software-defined storage nodes; a data network is created on the physical server based on the selected target pass-through network interface card (NIC) so that the data network can serve as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services; based on a preset disk configuration, a first preset number of solid-state drives (SSDs) and a second preset number of hard disk drives (HDDs) are selected as the target physical disks corresponding to the software-defined storage nodes; the selected SSDs are used to construct the cache space corresponding to the software-defined storage nodes, and the selected HDDs are used to construct the data space corresponding to the software-defined storage nodes, thereby constructing the storage space corresponding to the software-defined storage nodes. Therefore, this application creates a data network on the physical server based on the selected target pass-through NIC, realizing that the communication network and the network providing storage services are the same network, reducing network complexity and further improving the performance of the hyperconverged software-defined storage; this application selects SSDs and HDDs based on a preset disk configuration to construct the storage space corresponding to the software-defined storage nodes, making disk configuration more flexible.

[0081] See Figure 4The diagram shows the hyperconverged software-defined storage deployment scheme of this application, which is a host-based hyperconverged software-defined storage deployment scheme. This scheme installs a virtualization system on a physical server and uses a resource reservation scheme to reserve the CPU and memory required for the normal operation of the software-defined storage node. The reserved resources are exclusively used by the software-defined storage node. At the same time, network cards and disks are configured. The disks can be selected from all disks associated with a Redundant Array of Independent Disks (RAID) card, or some physical disks (NVMe, non-volatile memory) can be selected. It is not limited by the RAID card, so as to achieve the disk ratio required for hyperconverged software-defined storage deployment and directly deploy hyperconverged software-defined storage using the hardware resources on the physical server. It should be noted that the specific process of a hyperconverged software-defined storage deployment solution based on host deployment is as follows: Initiating the deployment process; resource reservation; creating a virtual storage switch; creating a data network; building storage space; configuring configuration files, etc. The steps according to the diagram are as follows: Step 1: After the hardware resources are configured, start the deployment process. Use the Linux kernel's control group function to limit and control resources, reserving CPU and memory resources to ensure the necessary resources for the normal operation of the software-defined storage nodes; Step 2: Select the passthrough network interface card (NIC) on each server and create a virtual storage switch. The uplink of the switch is the NIC of each server; Step 3: Create a data network on the storage switch and configure it with IP (Internet Protocol). This data network is the communication network between software-defined storage nodes and also the data network connecting the storage resources provided by the software-defined storage; Step 4: Build storage space using the selected physical disks, including SSDs (Solid State Disks) and HDDs (Hard Disks). The disks (hard disk drives) meet the preset disk ratio. Solid-state drives are used to build cache space, and hard disk drives are used to build data space as storage space for software-defined storage nodes. Step 5: Configure the configuration files of each node and start monitoring and other services on each node to monitor the real-time running status and resource usage of each software-defined storage node in the hyperconverged software-defined storage. Finally, the deployment of hyperconverged software-defined storage is completed.

[0082] See Figure 5The diagram illustrates a traditional deployment method for hyperconverged software-defined storage (HDS) based on system virtual machines. A virtualization system is installed on the physical server, and system virtual machines are created within this system using an image. The CPU and memory resources of the virtual machine can be configured during the virtual machine creation process. Simultaneously, RAID cards (including all physical disks associated with the RAID card), NVMe disks, and network interface cards (NICs) are directly connected to the system virtual machine. The system virtual machine then serves as the software-defined storage node for HDS deployment. However, in this traditional deployment method, the virtualization system needs to come with its own image, which is used to create the system virtual machine within the nested system. This results in excessively large images and a complex process. Furthermore, the addition of the system virtual machine layer in the traditional deployment method leads to some performance degradation for the HDS.

[0083] See Figure 6 As shown, taking three physical servers as an example, this illustrates a hyperconverged software-defined storage deployment scheme based on host deployment. The process is as follows:

[0084] Step 1: Using the Linux kernel's control group function, reserve 16C and 16GB of memory and CPU resources on physical servers 1, 2, and 3 for the deployment of hyperconverged software-defined storage on these three physical servers;

[0085] Step 2: Use the pass-through network cards on physical servers 1, 2, and 3 to create a virtual storage switch. The uplink of the switch is the network cards of servers 1, 2, and 3.

[0086] Step 3: Create a data network on the storage switch. Data network ports are created on all three servers (1, 2, and 3), and IP information is configured for the three data network ports.

[0087] Step 4: Build storage space using the selected physical disks. Taking one 1TB SSD and two 4TB HDDs on physical servers 1, 2, and 3 as an example, the SSD is used to build cache space with a capacity of 3TB; the HDDs are used to build data space with a capacity of 24TB, which means the total capacity of the hyperconverged SDS is 24TB. It should be noted that the SSD and HDD disks are selected according to the preset disk configuration.

[0088] Step 5: Configure the configuration files for servers 1, 2, and 3, and start monitoring services for the hyperconverged software-defined storage on servers 1, 2, and 3 to monitor the real-time running status and resource usage of the hyperconverged software-defined storage.

[0089] Step Six: Once the services on servers 1, 2, and 3 are all running normally and the information is displayed correctly, the deployment is complete.

[0090] It should be noted that designing reasonable resource reservation schemes, optimized network configuration schemes, and flexible disk selection schemes simplifies the deployment process of hyperconverged infrastructure. To fully leverage the performance of hyperconverged hardware and overcome hardware pass-through limitations, resource reservations for server CPUs and memory ensure the normal operation of software-defined storage nodes on the server. An optimized network resource creation method ensures that communication between software-defined storage nodes and the provision of external storage services use the same network, reducing network complexity. Simultaneously, the flexible physical disk selection scheme simplifies the software-defined storage deployment process, resulting in stronger performance of deployed hyperconverged software-defined storage and increasing the product's deployment options. This makes it suitable for installation and deployment across various architectures, expanding the applicability of hyperconverged virtualization and facilitating its widespread adoption.

[0091] It should be noted that the deployment process of this application does not require a system virtual machine. The installation package required for deployment is directly integrated into the virtualization system. The deployment process only requires configuring a data network, which is automatically created during the deployment process. After meeting the preset disk allocation, hyperconverged software-defined storage can be deployed based on host deployment, allowing the performance of hyperconverged hardware resources to be fully utilized. It should also be noted that because this application does not have a system virtual machine, it solves the problem of traditional deployment methods (system virtual machine method) not supporting hardware passthrough (such as network card passthrough) on ARM architecture servers, eliminating dependence on traditional deployment methods, avoiding system nesting, and significantly improving the performance of hyperconverged software-defined storage nodes. Furthermore, the use of this application in hyperconverged virtualization systems can effectively improve the applicability of hyperconvergence, increase the deployment forms of hyperconvergence, fully utilize the performance of hyperconverged hardware resources, increase product diversity, and facilitate the widespread promotion and application of hyperconverged virtualization systems.

[0092] See Figure 7 As shown in the figure, this application discloses a hyperconverged software-defined storage deployment device, including:

[0093] The resource reservation module 11 is used to reserve target resources for the software-defined storage node in the physical server to ensure the normal operation of the software-defined storage node;

[0094] Network creation module 12 is used to create a data network on the physical server based on the selected target pass-through network card, so that the data network can be used as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services.

[0095] Storage space construction module 13 is used to construct the storage space corresponding to the software-defined storage node using the selected target physical disk.

[0096] As can be seen, this application reserves target resources for software-defined storage nodes in the physical server to ensure the normal operation of the software-defined storage nodes; a data network is created on the physical server based on the selected target pass-through network interface card (NIC), so that the data network serves as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services; and the storage space corresponding to the software-defined storage node is constructed using the selected target physical disk. Therefore, this application creates a data network on the physical server based on the selected target pass-through NIC, realizing that the communication network and the network providing storage services are the same network, reducing network complexity and further improving the performance of the hyperconverged software-defined storage.

[0097] In some embodiments, the network creation module 12 may specifically include:

[0098] The network creation unit is used to create a virtual storage switch on the physical server based on the selected target pass-through network card, and to create a data network based on the virtual storage switch;

[0099] In some embodiments, the hyperconverged software-defined storage deployment apparatus further includes:

[0100] The port creation and protocol configuration unit is used to create network ports for the data network and configure network interconnection protocols for the network ports;

[0101] In some embodiments, the hyperconverged software-defined storage deployment apparatus further includes:

[0102] The selection unit selects a first preset number of solid-state drives and a second preset number of hard disk drives as the target physical disks corresponding to the software-defined storage node, based on a preset disk ratio.

[0103] In some embodiments, the storage space construction module 13 may specifically include:

[0104] The selected solid-state drive is used to construct the cache space corresponding to the software-defined storage node, and the selected hard disk drive is used to construct the data space corresponding to the software-defined storage node.

[0105] In some embodiments, the hyperconverged software-defined storage deployment apparatus further includes:

[0106] Configure a configuration file for the software-defined storage node in the physical server to monitor the software-defined storage node.

[0107] Furthermore, embodiments of this application also provide an electronic device. Figure 8 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0108] Figure 8 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, an input / output interface 24, a communication interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps of the hyperconverged software-defined storage deployment method disclosed in any of the foregoing embodiments.

[0109] 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 25 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 24 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0110] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The memory 22 can be a random access memory that can be used as running memory and a non-volatile memory used for external memory storage. The storage resources on it include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0111] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 on the source host and the computer program 222. The operating system 221 can be Windows, Unix, Linux, etc. In addition to including a computer program capable of performing the hyperconverged software-defined storage deployment method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program capable of performing other specific tasks.

[0112] In this embodiment, the input / output interface 24 may include, but is not limited to, a USB interface, a hard disk read interface, a serial interface, a voice input interface, a fingerprint input interface, etc.

[0113] Furthermore, embodiments of this application also disclose a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned disclosed hyperconverged software-defined storage deployment method.

[0114] For the specific steps of this method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0115] The computer-readable storage medium referred to herein includes random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, magnetic disks, optical disks, or any other form of storage medium known in the art. When the computer program is executed by a processor, it implements the aforementioned hyperconverged software-defined storage deployment method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0116] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. The apparatus disclosed in the embodiments is described simply because it corresponds to the hyperconverged software-defined storage deployment method disclosed in the embodiments; relevant parts can be referred to the method section.

[0117] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0118] The steps of the algorithm described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main 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 known in the art.

[0119] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0120] The above provides a detailed description of a hyperconverged software-defined storage deployment method, apparatus, device, and medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for deploying hyperconverged software-defined storage, characterized in that, include: Without adding system virtual machines to the physical server, target resources are reserved in the physical server for the software-defined storage node to ensure the normal operation of the software-defined storage node; the number of corresponding physical servers in the hyperconverged software-defined storage is several, and the physical server is used as the carrier for the software-defined storage node. Accordingly, the number of each software-defined storage node constituting the hyperconverged software-defined storage is the same as the number of physical servers. A data network is created on the physical server based on the selected target pass-through network card, so that the data network can be used as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services. The storage space corresponding to the software-defined storage node is constructed using the selected target physical disk; Before constructing the storage space corresponding to the software-defined storage node using the selected target physical disk, the method further includes: Based on a preset disk ratio, a first preset number of solid-state drives and a second preset number of hard disk drives are selected as the target physical disks corresponding to the software-defined storage nodes; The step of constructing the storage space corresponding to the software-defined storage node using the selected target physical disk includes: The selected solid-state drive is used to construct the cache space corresponding to the software-defined storage node, and the selected hard disk drive is used to construct the data space corresponding to the software-defined storage node.

2. The hyperconverged software-defined storage deployment method according to claim 1, characterized in that, The process of creating a data network on the physical server based on the selected target pass-through network interface card includes: A virtual storage switch is created on the physical server based on the selected target pass-through network card, and a data network is created based on the virtual storage switch.

3. The hyperconverged software-defined storage deployment method according to claim 1, characterized in that, After creating the data network on the physical server, the process also includes: Create a network port for the data network and configure a network interconnection protocol for the network port.

4. The hyperconverged software-defined storage deployment method according to claim 1, characterized in that, Also includes: Configure a configuration file for the software-defined storage node in the physical server to monitor the software-defined storage node.

5. The hyperconverged software-defined storage deployment method according to any one of claims 1 to 4, characterized in that, The target physical disk includes several disks in a redundant disk array card and / or a non-volatile memory disk; the target resources include central processing unit resources and memory resources.

6. A hyperconverged software-defined storage deployment device, characterized in that, include: The resource reservation module is used to reserve target resources for software-defined storage nodes in physical servers without adding system virtual machines, so as to ensure the normal operation of the software-defined storage nodes. The number of physical servers in the hyperconverged software-defined storage is several, and the physical servers are used as carriers for the software-defined storage nodes. Accordingly, the number of each software-defined storage node constituting the hyperconverged software-defined storage is the same as the number of physical servers. A network creation module is used to create a data network on the physical server based on a selected target pass-through network card, so that the data network can be used as a communication network between the software-defined storage nodes in different physical server nodes and as a network for the hyperconverged software-defined storage to connect to the physical server to provide storage services. A storage space construction module is used to construct the storage space corresponding to the software-defined storage node using the selected target physical disk; The hyperconverged software-defined storage deployment device is further configured to: select a first preset number of solid-state drives and a second preset number of hard disk drives as the target physical disks corresponding to the software-defined storage nodes based on a preset disk ratio; The storage space construction module is configured to: construct a cache space corresponding to the software-defined storage node using the selected solid-state drive, and construct a data space corresponding to the software-defined storage node using the selected hard disk drive.

7. An electronic device, characterized in that, It includes a processor and a memory; wherein, when the processor executes a computer program stored in the memory, it implements the hyperconverged software-defined storage deployment method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, Used for storing computer programs; wherein, when the computer programs are executed by a processor, they implement the hyperconverged software-defined storage deployment method as described in any one of claims 1 to 5.

Images