Container cloud deployment method, apparatus and equipment based on DPC protocol

Abstract

This invention provides a container cloud deployment method, apparatus, and device based on the DPC protocol. The method includes: creating a single master node cluster and an empty node pool through a container management platform, and then including bare metal nodes in the empty node pool; wherein the bare metal nodes have a storage access environment that supports the DPC protocol; sequentially installing a DPC client and a third-party container plugin on the bare metal nodes, and then loading the image of the third-party container plugin into the local repository of the container management platform; creating an instance based on an application template generated from the loaded image, and assigning a unique name to the instance; deploying a storage interface tool on the master node and configuring connection parameters, and then creating a storage class associated with the instance on the container management platform; creating a PVC based on the storage class to verify whether the storage link is available; if the verification is successful, the container cloud deployment is considered successful. This invention significantly improves the efficiency of container access to storage by introducing DPC technology into the container cloud deployment scheme.

Description

Technical Field

[0001] This invention relates to the field of computer virtualization technology, and in particular to a container cloud deployment method, apparatus, and equipment based on the DPC protocol. Background Technology

[0002] With the deepening of information integration, information system integration has become a hot topic in the industry. Currently, computer virtualization technology is showing a diversified development trend, playing a differentiated role in various industries and application scenarios. Among them, container cloud, as an important branch of virtualization technology, has demonstrated significant application value due to its lightweight and efficient characteristics.

[0003] Current container clouds generally adopt a "physical server + NAS storage" architecture: virtualized computing resources are built on the basis of physical servers, and data storage support is provided by NAS storage. However, due to its architectural characteristics, NAS storage can only achieve resource sharing through a single IP address, resulting in a significant bottleneck in storage performance. Especially in massive data processing scenarios, it is difficult to meet the needs of high concurrency and large-scale data read and write, which seriously restricts the overall performance of container clouds.

[0004] Therefore, due to the limitations of the NAS storage architecture, existing container clouds have difficulty meeting the high concurrency and large-scale data read and write requirements of massive data processing scenarios. Summary of the Invention

[0005] This invention provides a container cloud deployment method, apparatus, and device based on the DPC protocol, aiming to address the limitations of existing container clouds due to their NAS storage architecture, which makes it difficult to meet the high-concurrency and large-scale data read / write requirements of massive data processing scenarios.

[0006] In a first aspect, embodiments of the present invention provide a container cloud deployment method based on the DPC protocol, the method comprising:

[0007] After creating a single master node cluster and an empty node pool through the container management platform, the bare metal nodes are included in the empty node pool; wherein, the bare metal nodes have a storage access environment that supports the DPC protocol;

[0008] After installing the DPC client and the third-party container plugin on the bare metal node in sequence, the image of the third-party container plugin is loaded into the local repository of the container management platform.

[0009] Create an instance based on the application template generated from the loaded image, and assign a unique name to the instance;

[0010] After deploying the storage integration tool and configuring the connection parameters on the master node, create a storage class associated with the instance in the container management platform;

[0011] A PVC is created based on the storage class to verify whether the storage link is available. If the verification is successful, the container cloud deployment is considered successful.

[0012] Secondly, embodiments of the present invention also provide a container cloud deployment device based on the DPC protocol, the device comprising:

[0013] The first creation unit is used to create a single master node cluster and an empty node pool through the container management platform, and then include bare metal nodes into the empty node pool; wherein, the bare metal nodes have a storage access environment that supports the DPC protocol;

[0014] The installation and loading unit is used to install the DPC client and the third-party container plugin sequentially on the bare metal node, and then load the image of the third-party container plugin into the local repository of the container management platform.

[0015] The second creation unit is used to create an instance based on the application template generated from the loaded image, and to assign a unique name to the instance;

[0016] The deployment creation unit is used to deploy the storage docking tool on the master node and configure the connection parameters, and then create a storage class associated with the instance on the container management platform;

[0017] The verification and determination unit is used to create a PVC based on the storage class to verify whether the storage link is available. If the verification is successful, the container cloud deployment is determined to be successful.

[0018] Thirdly, embodiments of the present invention also provide an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method described in the first aspect above.

[0019] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a processor, can implement the method described in the first aspect.

[0020] This invention provides a container cloud deployment method, apparatus, and device based on the DPC protocol. The method includes: creating a single master node cluster and an empty node pool through a container management platform, and then including bare metal nodes in the empty node pool; wherein the bare metal nodes have a storage access environment that supports the DPC protocol; sequentially installing a DPC client and a third-party container plugin on the bare metal nodes, and then loading the image of the third-party container plugin into the local repository of the container management platform; creating an instance based on an application template generated from the loaded image, and assigning a unique name to the instance; deploying a storage docking tool on the master node and configuring connection parameters, and then creating a storage class associated with the instance on the container management platform; creating a PVC based on the storage class to verify whether the storage link is available, and if the verification is successful, the container cloud deployment is considered successful. This invention introduces DPC technology into container cloud deployment solutions, replacing the traditional NAS protocol for shared storage with the DPC protocol. Through the synergy of the DPC client and third-party container plugins, the third-party container plugins achieve protocol adaptation and node identification for third-party distributed storage. The DPC client enables the container host (master node) to access multiple nodes of the third-party distributed storage in parallel, effectively overcoming the performance bottleneck of NAS storage's single IP sharing and significantly improving the efficiency of container access to storage. Especially in massive data processing scenarios, it can meet the needs of high concurrency and large-scale data read / write, thereby comprehensively improving container operating performance and business data processing efficiency. Attached Figure Description

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

[0022] Figure 1 A flowchart illustrating the container cloud deployment method based on the DPC protocol provided in this embodiment of the invention;

[0023] Figure 2 A schematic block diagram of a container cloud deployment device based on the DPC protocol provided in an embodiment of the present invention;

[0024] Figure 3 A schematic block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0025] 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, not all, of the embodiments of the present invention. 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.

[0026] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0027] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0028] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations. Embodiments of this invention provide a container cloud deployment method, apparatus, and device based on the DPC protocol. For details on the container cloud deployment method based on the DPC protocol, please refer to... Figure 1 , Figure 1 This is a flowchart illustrating the container cloud deployment method based on the DPC protocol provided in this embodiment of the invention. The method is applied to the controller of a container management platform. Container cloud deployment requires at least three servers: two as the master server (master node) and one as the backup server (slave server), and the remaining one as a bare metal server (bare metal node). Specifically, this invention creates a single master node cluster, consisting of one master node and at least one slave node. Both the master node and slave nodes serve as the operating carriers of the container management platform. The master node is the primary operating carrier of the container management platform, and the slave nodes synchronize the master node's status in real time and automatically take over its functions when the master node fails, ensuring continuous operation of the container management platform and avoiding management interruptions. The container management platform uses the master / slave nodes as operating carriers, managing and scheduling the bare metal nodes through the master node to jointly support the operation of the container cloud.

[0029] Figure 1 This is a flowchart illustrating the container cloud deployment method based on the DPC protocol provided in an embodiment of the present invention. Figure 1 As shown, the method includes the following steps S110-S150.

[0030] S110. After creating a single master node cluster and an empty node pool through the container management platform, the bare metal nodes are included in the empty node pool; wherein, the bare metal nodes have a storage access environment that supports the DPC protocol.

[0031] In this embodiment, the container management platform is used as the operation entry point. First, a single master node cluster and an empty node pool are built. Then, the bare metal nodes are included in the empty node pool to realize the full life cycle management and resource scheduling of the bare metal nodes.

[0032] In one embodiment, prior to step S110, the method further includes: installing a DPC protocol-compatible operating system and a high-speed network card on the bare metal node to build a storage access environment supporting the DPC protocol on the bare metal node.

[0033] In this embodiment, before building a single master node cluster and an empty node pool using the container management platform as the operation entry point, it is also necessary to complete the deployment of a conventional container cloud. Specifically, the container cloud deployment requires at least three servers, two of which serve as the master server (master node) and the backup server (slave server), respectively, which together constitute the operating platform of the container management platform. The remaining one serves as a bare metal server (bare metal node). A DPC protocol-compatible operating system and a high-speed network card are installed on the bare metal node to build a storage access environment that supports the DPC protocol.

[0034] S120. After installing the DPC client and the third-party container plugin on the bare metal node in sequence, the image of the third-party container plugin is loaded into the local repository of the container management platform.

[0035] In this embodiment, the container management platform initiates operation commands to the bare metal nodes that have been included in the empty node pool. The DPC client is installed locally on the bare metal node. As a core component for protocol conversion and parallel access, the DPC client is responsible for converting storage access requests on the container host (i.e., the bare metal node) into a format that conforms to the DPC protocol, and realizing parallel data reading and writing to multiple nodes of third-party distributed storage through a high-speed network card.

[0036] After the DPC client is installed, a third-party container plugin is deployed on the bare metal node. The third-party container plugin serves as an adaptation interface between the container cloud (a management platform consisting of a master node and at least one slave node, i.e., a container management platform) and the storage resources of the bare metal node. In other words, after the third-party container plugin is installed, the container management platform can access the storage resources of the bare metal node.

[0037] In one embodiment, step S120 includes: installing a DPC client on the bare metal node; testing whether the bare metal node can perform parallel read and write operations on distributed storage with the DPC protocol through the DPC client via a mount operation; if the test is successful, installing a third-party container plugin on the bare metal node and loading the image of the third-party container plugin into the local repository of the container management platform; wherein the third-party container plugin depends on the protocol communication environment built by the DPC client.

[0038] In this embodiment, a DPC client is installed on the bare metal node. Its core function is to build a DPC protocol parsing and execution environment at the operating system level of the bare metal node. By performing a mounting operation on the bare metal node, it is tested whether the bare metal node can establish connections with multiple nodes of distributed storage simultaneously and complete data read and write operations using the DPC client. If the test passes, it indicates that the DPC client is working normally and the bare metal node has efficient storage access capabilities based on the DPC protocol. At this point, the next step is executed (installing a third-party container plugin on the bare metal node and loading the image of the third-party container plugin into the local repository of the container management platform). If the test fails, a troubleshooting and repair process needs to be initiated.

[0039] In one embodiment, installing a third-party container plugin on the bare metal node includes: obtaining an installation package of the third-party container plugin, and performing a decompression operation on the installation package on the bare metal node to obtain at least one sub-compressed package; after decompressing all the sub-compressed packages to the same target directory, configuring the target directory as the root directory of the third-party container plugin, thereby completing the installation operation of the third-party container plugin.

[0040] In this embodiment, obtaining the installation package of the third-party container plugin can specifically be as follows:

[0041] AAcop_Storage_Kubernetes_CSI_Plugins_V4.6.0.tar;

[0042] On the bare metal node, the installation package is decompressed to obtain three sub-compressed packages, which are as follows:

[0043] AAcop_Storage_Kubernetes_CSI_plugin_dependency.tar;

[0044] AAcop_Storage_Kubernetes_Csl_Plugin_V4.3.0_X86_64.tar;

[0045] cop-4.3.0.tgz;

[0046] After extracting all the sub-compressed packages to the same target directory, configure the target directory as the root directory of the third-party container plugin to complete the installation of the third-party container plugin.

[0047] In one embodiment, after decompressing all the sub-compressed packages to the same target directory and configuring the target directory as the root directory of the third-party container plugin, the method further includes: selecting multiple first image programs located in a first specified directory from the root directory; selecting multiple second image programs located in a second specified directory from the root directory; and uploading all the selected first and second image programs to the local repository to complete the image upload and loading operation.

[0048] In this embodiment, log in to the container management platform, enter the "Local Repository" function interface, and initiate an image upload and loading operation. Specifically, select seven first image programs located in the first specified directory from the root directory; select three second image programs located in the second specified directory from the root directory; upload all the selected first and second image programs to the local repository to complete the image upload and loading operation.

[0049] S130. Create an instance based on the application template generated from the loaded image, and assign a unique name to the instance.

[0050] In this embodiment, enter the application template interface of the container management platform, select the application template generated based on the loaded image, click "Create Instance", and in the pop-up configuration page, switch to the "Parameters" tab, find the configuration item involving the image repository address (the default value is "k8s.gcr.io / sig-storage"), and modify it in the edit box to the actual image repository address of the environment. Specifically, the user needs to modify it according to the floating IP address in their actual network environment; after completing the parameter modification, specify a unique name for the instance.

[0051] This step ensures that the instance can correctly pull the images of the third-party container plugins already loaded in the local repository by modifying the image repository address parameter, avoiding instance creation failure due to the default address being inaccessible. At the same time, the unique name facilitates subsequent management and maintenance of the instance.

[0052] In one embodiment, step S130 includes: associating the local repository of the image with the target deployment project; importing an application template generated based on the image into the target deployment project, and creating an instance on the application template; assigning a unique name to the instance, and configuring the name and related parameters of the container contained in the instance.

[0053] In this embodiment, the local repository of the image is associated with the target deployment project (such as a meteorological data processing project), enabling the target deployment project to obtain image access permissions from the local repository. Subsequently, after importing the application template generated based on the image (with the application template parameters already modified) into the target deployment project, an instance is created on the application template. A unique name is assigned to the instance, and the name and related parameters of the containers contained in the instance are configured. The related parameters include, but are not limited to, the container's memory resource parameters and network configuration parameters.

[0054] S140. After deploying the storage docking tool and configuring the connection parameters on the master node, create a storage class associated with the instance in the container management platform.

[0055] In this embodiment, log in to any node in the single-master node cluster (including the currently active master node or a slave node in standby state, collectively referred to as the "target master node"), and upload all files under the target docking directory to the / home / Gandalf directory of the target master node; wherein, the target docking directory is specifically as follows:

[0056] AAcop_Storage_Kubernetes_CSI_Plugin_V4.3.0_X86_64\AAcop_Storage_Kubernetes_CSI_Plugin_V4.3.0_X86_64\bin\oceanctl;

[0057] After the file upload is complete, create a csi.yaml file on the master node and write the connection parameters. The connection parameters include storage type, storage name, namespace, access address, storage address, storage pool, protocol type, logical port, and number of connections (used to restrict users from brute-forcing access to storage). The connection parameters are the key configuration for the container management platform to identify and connect to the backend storage, ensuring that the container can access storage resources through the correct path and protocol.

[0058] Next, after entering the storage class page of the container management platform, enter the storage class configuration parameters in the pop-up editing page to complete the storage class creation; the storage class configuration parameters must be linked with the connection parameters; the storage class configuration parameters are as follows:

[0059] kind: [StorageClass] type name

[0060] apiVersion:

storage.k8s.io / v1

[0061] metadata: metadata information

[0062] name:

sc-system-manage

[0063] Provisioner:

csi.AA.com

[0064] allowVolumeExpansion: [true] Whether to support dynamic expansion.

[0065] parameters: parameter information

[0066] backend:

"nfs-155"

[0067] pool:

"StoragePool004"

[0068] volumeType:

fs

[0069] allocType: [thin] The allocation model (default: minimum).

[0070] authClient: ["*"] User information (default is empty).

[0071] In one embodiment, after step S140, the method further includes: verifying the connection feasibility between the container management platform and the third-party distributed storage based on the input docking command, and obtaining a connection feasibility result; wherein the third-party container plugin points to the third-party distributed storage; if the connection feasibility result is feasible, then the step of creating a storage class associated with the instance in the container management platform is executed.

[0072] In this embodiment, the docking command is `. / oceanctl create backend -f csi.yaml -i yaml`. After executing the docking command, enter the administrator account and corresponding password of the storage frontend. Here, the storage frontend refers to the entry layer for interaction between the container management platform and the distributed storage. During the execution of the docking command, the third-party container plugin will establish communication with the third-party distributed storage through the DPC protocol based on the connection parameters configured in the csi.yaml file. If the authentication is successful and the connection parameters match, the terminal interface of the target master node will return a success message (i.e., the connection feasibility result is feasible). At this time, it indicates that the container management platform has formed an effective link with the distributed storage through the third-party container plugin, and the step of creating a storage class associated with the instance on the container management platform can continue.

[0073] If an error message is returned, it means that the connection is not feasible and you need to re-check the correctness of the account password, the accuracy of the connection parameters, etc.

[0074] S150. Create a PVC based on the storage class to verify whether the storage link is available. If the verification is successful, the container cloud deployment is determined to be successful.

[0075] In this embodiment, after the storage class is created, a PVC (Persistent Volume Declaration) is created through the container management platform to verify the availability of the storage link. The operation steps are as follows: On the container management platform, click the "Storage" page, select the sub-menu "PVC" to enter the PVC management page. On the PVC management page, click the "Create" button to trigger the PVC configuration process. Enter the relevant configuration content of the PVC (such as basic identification information, storage class association information, storage resource requirements, etc.), and then click the "OK" button. The container management platform will call the third-party container plugin to apply for storage resources from the third-party distributed storage based on the storage class. Return to the PVC management page and check the "Status" column. If it shows "Bound", it means that the PVC has been successfully bound to the storage resource and the storage link (container management platform → storage class → third-party container plugin → DPC protocol → distributed storage) is available, and the container cloud deployment can be determined to be successful. If an error status is displayed, error troubleshooting is required.

[0076] In summary, this invention introduces DPC technology into container cloud deployment solutions, replacing the traditional NAS protocol of shared storage with the DPC protocol. Through the synergy of the DPC client and third-party container plugins, the third-party container plugins achieve protocol adaptation and node identification for third-party distributed storage, while the DPC client enables the container host (master node) to access multiple nodes of the third-party distributed storage in parallel. This effectively overcomes the performance bottleneck of NAS storage's single IP sharing, significantly improving the efficiency of container access to storage. Especially in massive data processing scenarios, it can meet the needs of high concurrency and large-scale data read / write, thereby comprehensively improving container operating performance and business data processing efficiency.

[0077] Figure 2 This is a schematic block diagram of a container cloud deployment device based on the DPC protocol provided in an embodiment of the present invention. Figure 2As shown, corresponding to the above-described container cloud deployment method based on the DPC protocol, this invention also provides a container cloud deployment device based on the DPC protocol. The device is configured in the controller of the container management platform. Container cloud deployment requires at least three servers, two of which serve as the master server (master node) and the backup server (slave server), respectively, and the remaining one as a bare metal server (bare metal node). Specifically, this invention creates a single master node cluster, which consists of one master node and at least one slave node. Both the master node and slave nodes serve as the operating carriers of the container management platform. The master node is the primary operating carrier of the container management platform, and the slave nodes synchronize the master node's status in real time and automatically take over its functions when the master node fails, ensuring continuous operation of the container management platform and avoiding management interruptions. The container management platform uses the master / slave nodes as operating carriers, and manages and schedules the bare metal nodes through the master node, jointly supporting the operation of the container cloud. For details, please refer to... Figure 2 The container cloud deployment appliance 700 based on the DPC protocol includes:

[0078] The first creation unit 701 is used to create a single master node cluster and an empty node pool through the container management platform, and then include bare metal nodes into the empty node pool; wherein, the bare metal nodes have a storage access environment that supports the DPC protocol.

[0079] The installation and loading unit 702 is used to install the DPC client and the third-party container plugin sequentially on the bare metal node, and then load the image of the third-party container plugin into the local repository of the container management platform.

[0080] The second creation unit 703 is used to create an instance based on the application template generated from the loaded image, and to assign a unique name to the instance;

[0081] Deployment creation unit 704 is used to deploy storage docking tools on the master node and configure connection parameters, and then create a storage class associated with the instance on the container management platform;

[0082] The verification and determination unit 705 is used to create a PVC based on the storage class to verify whether the storage link is available. If the verification is successful, the container cloud deployment is determined to be successful.

[0083] In some embodiments, before the first creation unit 701 performs the step of adding bare metal nodes to the empty node pool after creating a single master node cluster and an empty node pool through a container management platform, it is further configured to:

[0084] After creating a single master node cluster and an empty node pool through the container management platform, the bare metal nodes are included in the empty node pool.

[0085] In some embodiments, when the installation and loading unit 702 loads the image of the third-party container plugin into the local repository of the container management platform after sequentially installing the DPC client and the third-party container plugin on the bare metal node, it is specifically used for:

[0086] Install a DPC client on the bare metal node; test whether the bare metal node can perform parallel read and write operations on the distributed storage with the DPC protocol through the DPC client by mounting operations; if the test is successful, install a third-party container plugin on the bare metal node and load the image of the third-party container plugin into the local repository of the container management platform; wherein, the third-party container plugin depends on the protocol communication environment built by the DPC client.

[0087] In some embodiments, when the installation and loading unit 702 performs the step of installing a third-party container plugin on the bare metal node, it is specifically used for:

[0088] Obtain the installation package of the third-party container plugin, and perform a decompression operation on the installation package on the bare metal node to obtain at least one sub-compressed package; after decompressing all the sub-compressed packages to the same target directory, configure the target directory as the root directory of the third-party container plugin to complete the installation operation of the third-party container plugin.

[0089] In some embodiments, after performing the step of decompressing all the sub-compressed packages to the same target directory and configuring the target directory as the root directory of the third-party container plugin, the installation loading unit 702 is further configured to:

[0090] Select multiple first image programs located in the first specified directory from the root directory; select multiple second image programs located in the second specified directory from the root directory; upload all selected first and second image programs to the local repository to complete the image upload and loading operation.

[0091] In some embodiments, when the second creation unit 703 performs the step of creating an application template instance based on the loaded image and assigning a unique name to the instance, it is specifically used for:

[0092] Associate the local repository of the image with the target deployment project; after importing the application template generated based on the image into the target deployment project, create an instance on the application template; assign a unique name to the instance, and configure the name and related parameters of the container contained in the instance.

[0093] In some embodiments, after performing the steps of deploying the storage docking tool on the master node and configuring the connection parameters, the deployment creation unit 704 is further configured to:

[0094] The connection feasibility between the container management platform and the third-party distributed storage is verified based on the input docking command, and a connection feasibility result is obtained; wherein, the third-party container plugin points to the third-party distributed storage; if the connection feasibility result is feasible, then the step of creating a storage class associated with the instance in the container management platform is executed.

[0095] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the container cloud deployment device and its units based on the DPC protocol can be found in the corresponding descriptions in the foregoing method embodiments. For the sake of convenience and brevity, these details will not be repeated here.

[0096] The aforementioned container cloud deployment device based on the DPC protocol can be implemented as a computer program, which can be used in, for example... Figure 3 It runs on the computer device shown.

[0097] Please see Figure 3 , Figure 3 This is a schematic block diagram of an electronic device provided in an embodiment of the present invention. The computer device 800 can be a terminal or a server, wherein the terminal can be an electronic device with communication functions.

[0098] See Figure 3 The electronic device 800 includes a processor 802, a memory, and a network interface 805 connected via a system bus 801. The memory may include a non-volatile storage medium 803 and internal memory 804.

[0099] The non-volatile storage medium 803 may store an operating system 8031 ​​and a computer program 8032. The computer program 8032 includes program instructions that, when executed, cause the processor 802 to perform a container cloud deployment method based on the DPC protocol.

[0100] The processor 802 provides computing and control capabilities to support the operation of the entire electronic device 800.

[0101] The internal memory 804 provides an environment for the execution of the computer program 8032 in the non-volatile storage medium 803. When the computer program 8032 is executed by the processor 802, the processor 802 can execute a container cloud deployment method based on the DPC protocol.

[0102] This network interface 805 is used for network communication with other devices. Those skilled in the art will understand that... Figure 3The structure shown is merely a block diagram of a portion of the structure related to the present invention and does not constitute a limitation on the electronic device 800 to which the present invention is applied. The specific electronic device 800 may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0103] The processor 802 is used to run a computer program 8032 stored in the memory to perform the following steps:

[0104] After creating a single master node cluster and an empty node pool through the container management platform, bare metal nodes are included in the empty node pool. Each bare metal node has a storage access environment that supports the DPC protocol. After installing a DPC client and a third-party container plugin on the bare metal node, the image of the third-party container plugin is loaded into the local repository of the container management platform. An instance is created based on the application template generated from the loaded image, and a unique name is assigned to the instance. After deploying a storage integration tool and configuring connection parameters on the master node, a storage class associated with the instance is created on the container management platform. A PVC is created based on the storage class to verify the availability of the storage link. If the verification passes, the container cloud deployment is considered successful.

[0105] In some embodiments, before the processor 802 incorporates bare metal nodes into the empty node pool after creating a single master node cluster and an empty node pool through a container management platform, the processor 802 also performs the following steps:

[0106] After creating a single master node cluster and an empty node pool through the container management platform, the bare metal nodes are included in the empty node pool.

[0107] In some embodiments, when the processor 802 loads the image of the third-party container plugin into the local repository of the container management platform after sequentially installing the DPC client and the third-party container plugin on the bare metal node, the specific steps are as follows:

[0108] Install a DPC client on the bare metal node; test whether the bare metal node can perform parallel read and write operations on the distributed storage with the DPC protocol through the DPC client by mounting operations; if the test is successful, install a third-party container plugin on the bare metal node and load the image of the third-party container plugin into the local repository of the container management platform; wherein, the third-party container plugin depends on the protocol communication environment built by the DPC client.

[0109] In some embodiments, when implementing the step of installing a third-party container plugin on the bare metal node, the processor 802 specifically implements the following steps:

[0110] Obtain the installation package of the third-party container plugin, and perform a decompression operation on the installation package on the bare metal node to obtain at least one sub-compressed package; after decompressing all the sub-compressed packages to the same target directory, configure the target directory as the root directory of the third-party container plugin to complete the installation operation of the third-party container plugin.

[0111] In some embodiments, after decompressing all the sub-compressed packages to the same target directory and configuring the target directory as the root directory of the third-party container plugin, the processor 802 further implements the following steps:

[0112] Select multiple first image programs located in the first specified directory from the root directory; select multiple second image programs located in the second specified directory from the root directory; upload all selected first and second image programs to the local repository to complete the image upload and loading operation.

[0113] In some embodiments, when implementing the step of creating an instance of an application template generated based on a loaded image and assigning a unique name to the instance, the processor 802 specifically implements the following steps:

[0114] Associate the local repository of the image with the target deployment project; after importing the application template generated based on the image into the target deployment project, create an instance on the application template; assign a unique name to the instance, and configure the name and related parameters of the container contained in the instance.

[0115] In some embodiments, after implementing the steps of deploying the storage docking tool on the master node and configuring the connection parameters, the processor 802 also implements the following steps:

[0116] The connection feasibility between the container management platform and the third-party distributed storage is verified based on the input docking command, and a connection feasibility result is obtained; wherein, the third-party container plugin points to the third-party distributed storage; if the connection feasibility result is feasible, then the step of creating a storage class associated with the instance in the container management platform is executed.

[0117] It should be understood that, in this embodiment of the invention, the processor 802 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0118] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0119] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions. When executed by a processor, the program instructions cause the processor to perform the following steps:

[0120] After creating a single master node cluster and an empty node pool through the container management platform, bare metal nodes are included in the empty node pool. Each bare metal node has a storage access environment that supports the DPC protocol. After installing a DPC client and a third-party container plugin on the bare metal node, the image of the third-party container plugin is loaded into the local repository of the container management platform. An instance is created based on the application template generated from the loaded image, and a unique name is assigned to the instance. After deploying a storage integration tool and configuring connection parameters on the master node, a storage class associated with the instance is created on the container management platform. A PVC is created based on the storage class to verify the availability of the storage link. If the verification passes, the container cloud deployment is considered successful.

[0121] In one embodiment, before the step of adding bare metal nodes to the empty node pool after the processor executes the program instructions to create a single master node cluster and an empty node pool through the container management platform, the processor further performs the following steps:

[0122] After creating a single master node cluster and an empty node pool through the container management platform, the bare metal nodes are included in the empty node pool.

[0123] In one embodiment, when the processor executes the program instructions to sequentially install the DPC client and the third-party container plugin on the bare metal node, and then loads the image of the third-party container plugin into the local repository of the container management platform, the specific steps are as follows:

[0124] Install a DPC client on the bare metal node; test whether the bare metal node can perform parallel read and write operations on the distributed storage with the DPC protocol through the DPC client by mounting operations; if the test is successful, install a third-party container plugin on the bare metal node and load the image of the third-party container plugin into the local repository of the container management platform; wherein, the third-party container plugin depends on the protocol communication environment built by the DPC client.

[0125] In one embodiment, when the processor executes the program instructions to install a third-party container plugin on the bare metal node, it specifically implements the following steps:

[0126] Obtain the installation package of the third-party container plugin, and perform a decompression operation on the installation package on the bare metal node to obtain at least one sub-compressed package; after decompressing all the sub-compressed packages to the same target directory, configure the target directory as the root directory of the third-party container plugin to complete the installation operation of the third-party container plugin.

[0127] In one embodiment, after the processor executes the program instructions to decompress all the sub-compressed packages to the same target directory and configures the target directory as the root directory of the third-party container plugin, it further performs the following steps:

[0128] Select multiple first image programs located in the first specified directory from the root directory; select multiple second image programs located in the second specified directory from the root directory; upload all selected first and second image programs to the local repository to complete the image upload and loading operation.

[0129] In one embodiment, when the processor executes the program instructions to create an application template instance based on the loaded image and assign a unique name to the instance, it specifically implements the following steps:

[0130] Associate the local repository of the image with the target deployment project; after importing the application template generated based on the image into the target deployment project, create an instance on the application template; assign a unique name to the instance, and configure the name and related parameters of the container contained in the instance.

[0131] In one embodiment, after executing the program instructions to deploy the storage docking tool and configure the connection parameters on the master node, the processor further performs the following steps:

[0132] The connection feasibility between the container management platform and the third-party distributed storage is verified based on the input docking command, and a connection feasibility result is obtained; wherein, the third-party container plugin points to the third-party distributed storage; if the connection feasibility result is feasible, then the step of creating a storage class associated with the instance in the container management platform is executed.

[0133] The storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0134] Those skilled in the art will 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 implementations should not be considered beyond the scope of this invention.

[0135] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0136] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0137] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0138] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and such modifications or substitutions are intended to be within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be subject to the scope of protection of the claims.

Claims

1. A container cloud deployment method based on the DPC protocol, characterized in that, The method includes: After creating a single master node cluster and an empty node pool through the container management platform, the bare metal nodes are included in the empty node pool; wherein, the bare metal nodes have a storage access environment that supports the DPC protocol; After installing the DPC client and the third-party container plugin on the bare metal node in sequence, the image of the third-party container plugin is loaded into the local repository of the container management platform. Create an instance based on the application template generated from the loaded image, and assign a unique name to the instance; After deploying the storage integration tool and configuring the connection parameters on the master node, create a storage class associated with the instance in the container management platform; A PVC is created based on the storage class to verify whether the storage link is available. If the verification is successful, the container cloud deployment is considered successful. After creating a single master node cluster and an empty node pool through the container management platform, and before including the bare metal nodes in the empty node pool, the process also includes: A DPC protocol-compatible operating system and a high-speed network card are installed on the bare metal node to build a storage access environment that supports the DPC protocol on the bare metal node. After deploying the storage integration tool and configuring the connection parameters on the master node, the process also includes: The connection feasibility between the container management platform and the third-party distributed storage is verified based on the input docking command, and the connection feasibility result is obtained; wherein, the third-party container plugin points to the third-party distributed storage; If the connection feasibility result is feasible, then the step of creating a storage class associated with the instance in the container management platform is executed.

2. The container cloud deployment method based on the DPC protocol according to claim 1, characterized in that, After sequentially installing the DPC client and the third-party container plugin on the bare metal node, the image of the third-party container plugin is loaded into the local repository of the container management platform, including: Install the DPC client on the bare metal node; The mounting operation was used to test whether the bare metal node could perform parallel read and write operations on the distributed storage with the DPC protocol through the DPC client. If the test passes, a third-party container plugin is installed on the bare metal node, and the image of the third-party container plugin is loaded into the local repository of the container management platform; wherein, the third-party container plugin depends on the protocol communication environment built by the DPC client.

3. The container cloud deployment method based on the DPC protocol according to claim 2, characterized in that, The installation of a third-party container plugin on the bare metal node includes: Obtain the installation package of the third-party container plugin, and perform a decompression operation on the installation package on the bare metal node to obtain at least one sub-compressed package; After extracting all the sub-compressed packages to the same target directory, configure the target directory as the root directory of the third-party container plugin to complete the installation of the third-party container plugin.

4. The container cloud deployment method based on the DPC protocol according to claim 3, characterized in that, After decompressing all the sub-compressed packages to the same target directory and configuring the target directory as the root directory of the third-party container plugin, the method further includes: Select multiple first image programs located in the first specified directory from the root directory; Select multiple second image programs located in the second specified directory from the root directory; Upload both the selected first and second image programs to the local repository to complete the image upload and loading operation.

5. The container cloud deployment method based on the DPC protocol according to claim 1, characterized in that, The application template generated based on the loaded image creates an instance, and a unique name is assigned to the instance, including: Associate the local repository of the image with the target deployment project; After importing the application template generated based on the image into the target deployment project, an instance is created on the application template; Assign a unique name to the instance and configure the name and related parameters of the container contained in the instance.

6. A container cloud deployment device based on the DPC protocol, characterized in that, The device includes: The first creation unit is used to create a single master node cluster and an empty node pool through the container management platform, and then include bare metal nodes into the empty node pool; wherein, the bare metal nodes have a storage access environment that supports the DPC protocol; The installation and loading unit is used to install the DPC client and the third-party container plugin sequentially on the bare metal node, and then load the image of the third-party container plugin into the local repository of the container management platform. The second creation unit is used to create an instance based on the application template generated from the loaded image, and to assign a unique name to the instance; The deployment creation unit is used to deploy the storage docking tool on the master node and configure the connection parameters, and then create a storage class associated with the instance on the container management platform; The verification and determination unit is used to create a PVC based on the storage class to verify whether the storage link is available. If the verification is successful, the container cloud deployment is determined to be successful. The first creation unit is further configured to install a DPC protocol-compatible operating system and a high-speed network card on the bare metal node to build a storage access environment that supports the DPC protocol on the bare metal node. The deployment creation unit is further configured to verify the feasibility of connecting the container management platform and the third-party distributed storage based on the input docking command, and obtain a connection feasibility result; wherein the third-party container plugin points to the third-party distributed storage; if the connection feasibility result is feasible, then the step of creating a storage class associated with the instance in the container management platform is executed.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the container cloud deployment method based on the DPC protocol as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which includes program instructions that, when executed by a processor, cause the processor to perform the container cloud deployment method based on the DPC protocol as described in any one of claims 1-5.

Images