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

Abstract

The invention provides a container cloud deployment method, device and equipment based on a DPC protocol, and the method comprises the steps: building a single main node cluster and an empty node pool through a container management platform, and bringing a bare metal node into the empty node pool; wherein the bare metal node has a storage access environment supporting a DPC protocol; after a DPC client and a third-party container plug-in are sequentially installed on the bare metal node, a mirror image of the third-party container plug-in is loaded to a local warehouse of the container management platform; creating an instance based on an application template generated by the loaded mirror image, and assigning a unique name for the instance; after a storage docking tool is deployed on the main node and connection parameters are configured, a storage class associated with the instance is created on the container management platform; and based on the storage class, creating a PVC to verify whether the storage link is available, and if the verification is passed, determining that the container cloud deployment is successful. According to the invention, the DPC technology is introduced into the container cloud deployment scheme, so that the access storage efficiency of the container is remarkably improved.

Description

Technical Field

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

[0002] With the deepening of information intensification, the integration of information systems has become a hot topic in the industry. Currently, computer virtualization technology is experiencing diversified development, demonstrating differentiated effectiveness across various industries and application scenarios. Container cloud, as a key branch of virtualization technology, demonstrates significant application value thanks to its lightweight and efficient nature.

[0003] Existing container clouds generally adopt a "physical server + NAS storage" architecture: physical servers are used as the foundation for virtualized computing resources, while NAS storage provides data storage support. However, due to its architectural limitations, NAS storage can only share resources through a single IP address, resulting in significant storage performance bottlenecks. This is particularly difficult to meet the needs of high-concurrency, large-scale data read and write operations in massive data processing scenarios, severely restricting the overall effectiveness of container clouds.

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

[0005] The embodiments of the present invention provide a container cloud deployment method, apparatus, and device based on the DPC protocol, aiming to solve the problem that existing container clouds are unable to meet the high concurrency and large-scale data reading and writing requirements of massive data processing scenarios due to the limitations of the NAS storage architecture.

[0006] In a first aspect, an embodiment of the present invention provides a container cloud deployment method based on the DPC protocol, the method comprising: After creating a single-master node cluster and an empty node pool through the container management platform, the bare metal node is incorporated into the empty node pool; wherein the bare metal node has a storage access environment that supports the DPC protocol; After installing the DPC client and the third-party container plug-in on the bare metal node in sequence, the image of the third-party container plug-in is loaded into the local warehouse of the container management platform; Create an instance based on the application template generated by the loaded image and assign a unique name to the instance; After deploying the storage connection tool on the master node and configuring the connection parameters, create a storage class associated with the instance on the container management platform; A PVC is created based on the storage class to verify whether the storage link is available. If the verification passes, the container cloud deployment is determined to be successful.

[0007] In a second aspect, an embodiment of the present invention further provides a container cloud deployment device based on the DPC protocol, the device comprising: A first creation unit is configured to create a single-master node cluster and an empty node pool through a container management platform, and then incorporate the bare metal node into the empty node pool; wherein the bare metal node has a storage access environment that supports the DPC protocol; An installation loading unit is configured to install the DPC client and the third-party container plug-in on the bare metal node in sequence, and then load the image of the third-party container plug-in into the local warehouse of the container management platform; A second creation unit is configured to create an instance based on the application template generated by the loaded image and assign a unique name to the instance; A deployment creation unit, configured to deploy a storage docking tool on the master node and configure connection parameters, and then create a storage class associated with the instance on the container management platform; The verification and determination unit is configured 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.

[0008] In a third aspect, an embodiment of the present invention further provides an electronic device, which includes a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the method described in the first aspect is implemented.

[0009] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the method described in the first aspect can be implemented.

[0010] The present invention provides a container cloud deployment method, device and equipment based on the DPC protocol. The method includes: after creating a single-master node cluster and an empty node pool through a container management platform, incorporating a bare metal node into the empty node pool; wherein the bare metal node has a storage access environment that supports the DPC protocol; after installing a DPC client and a third-party container plug-in on the bare metal node in sequence, loading the image of the third-party container plug-in into the local warehouse of the container management platform; creating an instance based on an application template generated based on the loaded image, and assigning a unique name to the instance; after deploying a storage docking tool on the master node and configuring connection parameters, 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 determined to be successful. The present invention introduces DPC technology into the container cloud deployment solution, replaces the traditional shared storage NAS protocol with the DPC protocol, and uses the synergy between the DPC client and the third-party container plug-in to implement protocol adaptation and node identification for the third-party distributed storage by the third-party container plug-in. The container host (master node) is used to achieve parallel access to multiple nodes of the third-party distributed storage through the DPC client, effectively breaking through the performance bottleneck of single IP sharing of NAS storage and significantly improving the efficiency of container access to storage. In particular, in massive data processing scenarios, it can meet the needs of high concurrency and large-scale data reading and writing, thereby comprehensively improving the container operation performance and business data processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0012] Figure 1 A schematic diagram of a process for deploying a container cloud based on the DPC protocol provided in an embodiment of the present invention; 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; Figure 3 A schematic block diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0013] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0014] It will be understood that when used in this specification and the appended claims, the terms “comprises” and “comprising” indicate the presence of described features, integers, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0015] 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 present invention. As used in the specification and appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise.

[0016] It should be further understood that the term "and / or" used in the present specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes these combinations. The embodiment of the present invention provides a container cloud deployment method, device and equipment based on the DPC protocol. The container cloud deployment method based on the DPC protocol can be found in Figure 1 , Figure 1 A flowchart of a container cloud deployment method based on the DPC protocol provided in an embodiment of the present invention. The method is applied to the controller of a 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), and the remaining server serves as a bare metal server (bare metal node). Specifically, the present invention creates a single-master node cluster, which consists of a master node and at least one slave node. Both the master node and the slave node serve as the operating carriers of the container management platform. The master node is the main operating carrier of the container management platform. The slave node synchronizes the master node status in real time and automatically takes over its functions when the master node fails, ensuring the continuous operation of the container management platform and avoiding management interruptions. The container management platform uses the master / slave nodes as the operating carriers, manages and schedules the bare metal nodes through the master node, and jointly supports the operation of the container cloud.

[0017] Figure 1 The flowchart of the container cloud deployment method based on the DPC protocol provided by the embodiment of the present invention is as follows. Figure 1 As shown, the method includes the following steps S110-S150.

[0018] S110. After creating a single-master node cluster and an empty node pool through a container management platform, incorporate a bare metal node into the empty node pool; wherein the bare metal node has a storage access environment that supports the DPC protocol.

[0019] In this embodiment, the container management platform is used as the operation entry point. A single-master node cluster and an empty node pool are first constructed, and then the bare metal nodes are incorporated into the empty node pool to achieve full life cycle management and resource scheduling of the bare metal nodes.

[0020] In one embodiment, before 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.

[0021] In this embodiment, before using the container management platform as the operation entry to build a single master node cluster and an empty node pool, 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 main server (master node) and the backup server (slave server), which together constitute the operating carrier of the container management platform, and 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 on the bare metal node.

[0022] S120: After installing the DPC client and the third-party container plug-in on the bare metal node in sequence, load the image of the third-party container plug-in into the local warehouse of the container management platform.

[0023] In this embodiment, an operation instruction is initiated to the bare metal node that has been included in the empty node pool through the container management platform, and the DPC client is installed locally on the bare metal node. The DPC client, as the core component of protocol conversion and parallel access, is responsible for converting storage access requests on the container host (i.e., the bare metal node) into a format that complies with the DPC protocol, and realizes parallel data reading and writing of multiple nodes of third-party distributed storage through high-speed network cards.

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

[0025] In one embodiment, step S120 includes: installing a DPC client on the bare metal node; testing whether the bare metal node can perform parallel reading and writing of distributed storage with the DPC protocol through the DPC client through a mount operation; if the test passes, installing a third-party container plug-in on the bare metal node, and loading the image of the third-party container plug-in into the local warehouse of the container management platform; wherein the third-party container plug-in relies on the protocol communication environment constructed by the DPC client.

[0026] In this embodiment, a DPC client is installed on a bare metal node. Its core function is to build a parsing and execution environment for the DPC protocol at the operating system level of the bare metal node. By performing a mount operation on the bare metal node, it is tested whether the bare metal node can simultaneously establish connections with multiple nodes of distributed storage and complete data reading and writing with the help of the DPC client. If the test passes, it means that the DPC client has been working normally and the bare metal node has efficient storage access capabilities based on the DPC protocol. At this time, the next step is executed (installing a third-party container plug-in on the bare metal node and loading the image of the third-party container plug-in into the local warehouse of the container management platform); if the test fails, it is necessary to start the troubleshooting and repair process.

[0027] In one embodiment, installing a third-party container plug-in on the bare metal node includes: obtaining an installation package of the third-party container plug-in, and decompressing 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 plug-in, thereby completing the third-party container plug-in installation operation.

[0028] In this embodiment, obtaining the installation package of the third-party container plug-in may be performed as follows: AAcop_Storage_Kubernetes_CSI_Plugins_V4.6.0.tar; Decompress the installation package on the bare metal node to obtain three sub-compressed packages: AAcop_Storage_Kubernetes_CSI_plugin_dependency.tar; AAcop_Storage_Kubernetes_Csl_Plugin_V4.3.0_X86_64.tar; cop-4.3.0.tgz; After all the sub-compressed packages are decompressed into the same target directory, the target directory is configured as the root directory of the third-party container plug-in to complete the third-party container plug-in installation operation.

[0029] 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 plug-in, 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 image programs and second image programs to the local warehouse to complete the image upload and loading operation.

[0030] In this embodiment, the container management platform is logged in, the "local warehouse" function interface is entered, and an image upload and loading operation is initiated. Specifically, seven first image programs located in a first specified directory are selected from the root directory; three second image programs located in a second specified directory are selected from the root directory; all the selected first image programs and second image programs are uploaded to the local warehouse, completing the image upload and loading operation.

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

[0032] 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 configuration page that pops up, 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.

[0033] This step modifies the image repository address parameter to ensure that the instance can correctly pull the image of the third-party container plug-in loaded in the local repository, avoiding instance creation failure due to inaccessible default address. At the same time, the unique name facilitates subsequent management and operation of the instance.

[0034] In one embodiment, step S130 includes: associating 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, creating an instance on the application template; specifying a unique name for the instance, and configuring the name and related parameters of the container contained in the instance.

[0035] In this embodiment, the local repository of the image is associated with a target deployment project (such as a meteorological data processing project) so that the target deployment project obtains image access rights to the local repository; subsequently, after importing an application template generated based on the image into the target deployment project (after modification of application template parameters), an instance is created on the application template; a unique name is assigned to the instance, and the name and related parameters of the container contained in the instance are configured, wherein the related parameters include but are not limited to the memory resource parameters and network configuration parameters of the container.

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

[0037] In this embodiment, log in to any node in a 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 in the target docking directory to the / home / Gandalf directory of the target master node. The target docking directory is as follows: AAcop_Storage_Kubernetes_CSI_Plugin_V4.3.0_X86_64\AAcop_Storage_Kubernetes_CSI_Plugin_V4.3.0_X86_64\bin\oceanctl; After the file is uploaded, create the 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 links (used to limit users' brute force access to storage). Connection parameters are key configurations for the container management platform to identify and connect to backend storage, ensuring that containers can access storage resources through the correct path and protocol.

[0038] Next, enter the storage class page of the container management platform and enter the storage class configuration parameters in the pop-up edit page to complete the storage class creation. The storage class configuration parameters must be linked to the connection parameters. The storage class configuration parameters are as follows: kind:

StorageClass

sc-system-manage

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

[0040] 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 front-end, where the storage front-end refers to the entry layer for the container management platform to interact with the distributed storage. During the execution of the docking command, the third-party container plug-in 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 prompt (that is, the connection feasibility result is feasible), indicating that the container management platform has formed an effective link with the distributed storage through the third-party container plug-in, and the step of creating a storage class associated with the instance on the container management platform can continue.

[0041] If an error message is returned, it means that the connection feasibility result is not feasible and you need to recheck the correctness of the account password and the accuracy of the connection parameters.

[0042] S150: Create a PVC based on the storage class to verify whether the storage link is available. If the verification passes, it is determined that the container cloud deployment is successful.

[0043] In this embodiment, after the storage class is created, a PVC (Persistent Volume Claim) is created through the container management platform to verify the availability of the storage link. The steps are as follows: On the container management platform, click the "Storage" page and select "PVC" from the submenu to enter the PVC management page. On this PVC management page, click the "Create" button to trigger the PVC configuration process. After entering the PVC configuration information (such as basic identification information, storage class association information, storage resource requirements, etc.), click the "OK" button. The container management platform will call the third-party container plug-in based on the storage class to request storage resources from the third-party distributed storage. 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 Plug-in → DPC Protocol → Distributed Storage) is available, indicating that the container cloud deployment is successful. If an error status is displayed, troubleshooting is required.

[0044] In summary, the present invention introduces DPC technology into the container cloud deployment solution, replaces the traditional shared storage NAS protocol with the DPC protocol, and uses the synergy between the DPC client and the third-party container plug-in to implement protocol adaptation and node identification for the third-party distributed storage by the third-party container plug-in. The DPC client enables the container host (master node) to access multiple nodes of the third-party distributed storage in parallel, effectively breaking through the performance bottleneck of single IP sharing of NAS storage and significantly improving the efficiency of container access to storage. In particular, in massive data processing scenarios, it can meet the needs of high concurrency and large-scale data reading and writing, thereby comprehensively improving the container operation performance and business data processing efficiency.

[0045] Figure 2 Schematic block diagram of a container cloud deployment device based on the DPC protocol provided in an embodiment of the present invention. Figure 2 As shown, corresponding to the above container cloud deployment method based on the DPC protocol, the present 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, and 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), and the remaining one serves as a bare metal server (bare metal node); specifically, the present invention creates a single master node cluster, which consists of a master node and at least one slave node. The master node and the slave node both serve as the running carriers of the container management platform, wherein the master node is the main running carrier of the container management platform, and the slave node synchronizes the master node status in real time, and automatically takes over its functions when the master node fails, to ensure the continuous operation of the container management platform and avoid management interruption; the container management platform uses the master / slave node as the running carrier, manages and schedules the bare metal nodes through the master node, and jointly supports the operation of the container cloud. Specifically, please refer to Figure 2, the container cloud deployment device 700 based on the DPC protocol includes: The first creation unit 701 is configured to create a single-master node cluster and an empty node pool through a container management platform, and then incorporate a bare metal node into the empty node pool; wherein the bare metal node has a storage access environment that supports the DPC protocol; An installation and loading unit 702 is configured to install the DPC client and the third-party container plug-in on the bare metal node in sequence, and then load the image of the third-party container plug-in into the local repository of the container management platform; The second creation unit 703 is configured to create an instance based on the application template generated by the loaded image and assign a unique name to the instance; A deployment creation unit 704 is configured to deploy a storage connection tool on the master node and configure connection parameters, and then create a storage class associated with the instance on the container management platform; The verification and determination unit 705 is configured 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.

[0046] In some embodiments, after executing the step of creating a single-master node cluster and an empty node pool through the container management platform and before adding the bare metal node to the empty node pool, the first creation unit 701 is further configured to: After creating a single-master node cluster and an empty node pool through the container management platform, incorporate the bare metal node into the empty node pool.

[0047] In some embodiments, after sequentially installing the DPC client and the third-party container plug-in on the bare metal node, the installation and loading unit 702 loads the image of the third-party container plug-in into the local repository of the container management platform, specifically for: Install a DPC client on the bare metal node; test whether the bare metal node can perform parallel reading and writing of distributed storage with the DPC protocol through the DPC client through a mount operation; if the test passes, install a third-party container plug-in on the bare metal node, and load the image of the third-party container plug-in to the local warehouse of the container management platform; wherein, the third-party container plug-in relies on the protocol communication environment constructed by the DPC client.

[0048] In some embodiments, when executing the step of installing a third-party container plug-in on the bare metal node, the installation and loading unit 702 is specifically configured to: Obtain the installation package of the third-party container plug-in and decompress 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 plug-in to complete the third-party container plug-in installation operation.

[0049] 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 plug-in, the installation and loading unit 702 is further configured to: Select multiple first image programs located in a first specified directory from the root directory; select multiple second image programs located in a second specified directory from the root directory; upload all the selected first image programs and second image programs to the local warehouse to complete the image upload and loading operation.

[0050] In some embodiments, when executing the step of creating an instance based on the application template generated by the loaded image and assigning a unique name to the instance, the second creating unit 703 is specifically configured to: Associating 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, creating an instance based 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.

[0051] In some embodiments, after executing the steps of deploying the storage docking tool on the master node and configuring connection parameters, the deployment creation unit 704 is further configured to: Verify the connection feasibility between the container management platform and the third-party distributed storage according to the input docking command, and obtain a connection feasibility result; wherein the third-party container plug-in points to the third-party distributed storage; if the connection feasibility result is feasible, execute the step of creating a storage class associated with the instance on the container management platform.

[0052] It should be noted that technical personnel in the relevant field can clearly understand that the specific implementation process of the above-mentioned container cloud deployment device based on the DPC protocol and each unit can refer to the corresponding description in the aforementioned method embodiment. For the convenience and conciseness of the description, it will not be repeated here.

[0053] The above-mentioned container cloud deployment device based on the DPC protocol can be implemented in the form of a computer program. The computer program can be used in Figure 3 Runs on the computer equipment shown.

[0054] See also Figure 3 , Figure 38 is a schematic block diagram of an electronic device provided by 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 a communication function.

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

[0056] The non-volatile storage medium 803 can store an operating system 8031 ​​and a computer program 8032. The computer program 8032 includes program instructions, which, when executed, can enable the processor 802 to execute a container cloud deployment method based on the DPC protocol.

[0057] The processor 802 is used to provide computing and control capabilities to support the operation of the entire electronic device 800.

[0058] The internal memory 804 provides an environment for the operation 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.

[0059] The network interface 805 is used to communicate with other devices over the network. Figure 3 The structure shown in the figure is merely a block diagram of a portion of the structure related to the solution of the present invention, and does not constitute a limitation on the electronic device 800 to which the solution of 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 a different component arrangement.

[0060] The processor 802 is configured to execute a computer program 8032 stored in the memory to implement the following steps: After creating a single-master node cluster and an empty node pool through the container management platform, the bare metal node is included in the empty node pool; wherein, the bare metal node has a storage access environment that supports the DPC protocol; after installing the DPC client and the third-party container plug-in on the bare metal node in sequence, the image of the third-party container plug-in is loaded into the local warehouse of the container management platform; an instance is created based on the application template generated based on the loaded image, and a unique name is assigned to the instance; after deploying the storage docking tool on the master node and configuring the connection parameters, a storage class associated with the instance is created on the container management platform; based on the storage class, a PVC is created to verify whether the storage link is available. If the verification passes, the container cloud deployment is determined to be successful.

[0061] In some embodiments, after creating a single-master node cluster and an empty node pool through the container management platform, the processor 802 further implements the following steps before incorporating the bare metal node into the empty node pool: After creating a single-master node cluster and an empty node pool through the container management platform, incorporate the bare metal node into the empty node pool.

[0062] In some embodiments, after sequentially installing the DPC client and the third-party container plug-in on the bare metal node, the processor 802 loads the image of the third-party container plug-in to the local repository of the container management platform, specifically implementing the following steps: Install a DPC client on the bare metal node; test whether the bare metal node can perform parallel reading and writing of distributed storage with the DPC protocol through the DPC client through a mount operation; if the test passes, install a third-party container plug-in on the bare metal node, and load the image of the third-party container plug-in to the local warehouse of the container management platform; wherein, the third-party container plug-in relies on the protocol communication environment constructed by the DPC client.

[0063] In some embodiments, when implementing the step of installing a third-party container plug-in on the bare metal node, the processor 802 specifically implements the following steps: Obtain the installation package of the third-party container plug-in and decompress 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 plug-in to complete the third-party container plug-in installation operation.

[0064] In some embodiments, after decompressing all the sub-compressed packages into the same target directory and configuring the target directory as the root directory of the third-party container plug-in, the processor 802 further implements the following steps: Select multiple first image programs located in a first specified directory from the root directory; select multiple second image programs located in a second specified directory from the root directory; upload all the selected first image programs and second image programs to the local warehouse to complete the image upload and loading operation.

[0065] In some embodiments, when implementing the steps of creating an instance based on the application template generated by the loaded image and assigning a unique name to the instance, the processor 802 specifically implements the following steps: Associating 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, creating an instance based 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.

[0066] In some embodiments, after implementing the steps of deploying the storage docking tool on the master node and configuring connection parameters, the processor 802 further implements the following steps: Verify the connection feasibility between the container management platform and the third-party distributed storage according to the input docking command, and obtain a connection feasibility result; wherein the third-party container plug-in points to the third-party distributed storage; if the connection feasibility result is feasible, execute the step of creating a storage class associated with the instance on the container management platform.

[0067] It should be understood that in the embodiment of the present invention, the processor 802 may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), 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.

[0068] Those skilled in the art will appreciate that all or part of the steps in the method of the above-described embodiment can be implemented by instructing the relevant hardware through a computer program. The computer program includes program instructions, which can be stored in a storage medium that is computer-readable. The program instructions are executed by at least one processor in the computer system to implement the steps in the method of the above-described embodiment.

[0069] Therefore, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions. When the program instructions are executed by a processor, the processor performs the following steps: After creating a single-master node cluster and an empty node pool through the container management platform, the bare metal node is included in the empty node pool; wherein, the bare metal node has a storage access environment that supports the DPC protocol; after installing the DPC client and the third-party container plug-in on the bare metal node in sequence, the image of the third-party container plug-in is loaded into the local warehouse of the container management platform; an instance is created based on the application template generated based on the loaded image, and a unique name is assigned to the instance; after deploying the storage docking tool on the master node and configuring the connection parameters, a storage class associated with the instance is created on the container management platform; based on the storage class, a PVC is created to verify whether the storage link is available. If the verification passes, the container cloud deployment is determined to be successful.

[0070] In one embodiment, after executing the program instructions to create a single-master node cluster and an empty node pool through the container management platform, the processor further implements the following steps before incorporating the bare metal node into the empty node pool: After creating a single-master node cluster and an empty node pool through the container management platform, incorporate the bare metal node into the empty node pool.

[0071] In one embodiment, after the processor executes the program instructions to sequentially install the DPC client and the third-party container plug-in on the bare metal node, the processor loads the image of the third-party container plug-in to the local repository of the container management platform, specifically implementing the following steps: Install a DPC client on the bare metal node; test whether the bare metal node can perform parallel reading and writing of distributed storage with the DPC protocol through the DPC client through a mount operation; if the test passes, install a third-party container plug-in on the bare metal node, and load the image of the third-party container plug-in to the local warehouse of the container management platform; wherein, the third-party container plug-in relies on the protocol communication environment constructed by the DPC client.

[0072] In one embodiment, when the processor executes the program instructions to implement the step of installing a third-party container plug-in on the bare metal node, the processor specifically implements the following steps: Obtain the installation package of the third-party container plug-in and decompress 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 plug-in to complete the third-party container plug-in installation operation.

[0073] In one embodiment, after executing the program instructions to decompress all the sub-compressed packages into the same target directory and configuring the target directory as the root directory of the third-party container plug-in, the processor further implements the following steps: Select multiple first image programs located in a first specified directory from the root directory; select multiple second image programs located in a second specified directory from the root directory; upload all the selected first image programs and second image programs to the local warehouse to complete the image upload and loading operation.

[0074] In one embodiment, when the processor executes the program instructions to implement the steps of creating an instance based on the application template generated by the loaded image and assigning a unique name to the instance, the processor specifically implements the following steps: Associating 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, creating an instance based 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.

[0075] In one embodiment, after executing the program instructions to implement the steps of deploying the storage docking tool on the master node and configuring connection parameters, the processor further implements the following steps: Verify the connection feasibility between the container management platform and the third-party distributed storage according to the input docking command, and obtain a connection feasibility result; wherein the third-party container plug-in points to the third-party distributed storage; if the connection feasibility result is feasible, execute the step of creating a storage class associated with the instance on the container management platform.

[0076] The storage medium may be any computer-readable storage medium that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk.

[0077] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the composition and steps of each example according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0078] In the several embodiments provided herein, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the various units is merely a logical functional division, and actual implementation may employ other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0079] The steps in the methods of the embodiments of the present invention may be adjusted in order, combined, or deleted as needed. The units in the devices of the embodiments of the present invention may be combined, divided, or deleted as needed. Furthermore, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit.

[0080] If this 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, or the portion 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, stored in a storage medium, includes instructions for enabling a computer device (such as a personal computer, terminal, or network device) to execute all or part of the steps of the method described in various embodiments of the present invention.

[0081] 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 comprises: After creating a single-master node cluster and an empty node pool through the container management platform, the bare metal node is incorporated into the empty node pool; wherein the bare metal node has a storage access environment that supports the DPC protocol; After installing the DPC client and the third-party container plug-in on the bare metal node in sequence, the image of the third-party container plug-in is loaded into the local warehouse of the container management platform; Create an instance based on the application template generated by the loaded image and assign a unique name to the instance; After deploying the storage connection tool on the master node and configuring the connection parameters, create a storage class associated with the instance on the container management platform; A PVC is created based on the storage class to verify whether the storage link is available. If the verification passes, the container cloud deployment is determined to be successful.

2. The container cloud deployment method based on the DPC protocol according to claim 1, characterized in that: After creating a single-master node cluster and an empty node pool through the container management platform, and before incorporating the bare metal node into the empty node pool, the method further 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 supporting the DPC protocol on the bare metal node.

3. The container cloud deployment method based on the DPC protocol according to claim 1, characterized in that: After the DPC client and the third-party container plug-in are installed on the bare metal node in sequence, the image of the third-party container plug-in is loaded into the local warehouse of the container management platform, including: Installing the DPC client on the bare metal node; Test whether the bare metal node can perform parallel reading and writing of distributed storage with the DPC protocol through the DPC client through the mount operation; If the test passes, a third-party container plug-in is installed on the bare metal node, and the image of the third-party container plug-in is loaded into the local warehouse of the container management platform; wherein, the third-party container plug-in relies on the protocol communication environment constructed by the DPC client.

4. The container cloud deployment method based on the DPC protocol according to claim 3 is characterized in that: The step of installing a third-party container plug-in on the bare metal node includes: Obtain an installation package of a third-party container plug-in, and decompress the installation package on the bare metal node to obtain at least one sub-compressed package; After all the sub-compressed packages are decompressed into the same target directory, the target directory is configured as the root directory of the third-party container plug-in to complete the third-party container plug-in installation operation.

5. The container cloud deployment method based on the DPC protocol according to claim 4 is 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 plug-in, the method further includes: Selecting a plurality of first image programs located in a first designated directory from the root directory; Selecting a plurality of second image programs located in a second designated directory from the root directory; Upload the selected first image program and second image program to the local warehouse to complete the image upload and loading operation.

6. 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 assigns a unique name to the instance, including: Associating 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, creating an instance based on the application template; Specify a unique name for the instance and configure the name and related parameters of the container contained in the instance.

7. The container cloud deployment method based on the DPC protocol according to claim 1, characterized in that: After deploying the storage interconnection tool on the master node and configuring the connection parameters, the following steps are also included: Verify the feasibility of the connection between the container management platform and the third-party distributed storage according to the input docking command, and obtain a connection feasibility result; wherein the third-party container plug-in points to the third-party distributed storage; If the connection feasibility result is feasible, a step of creating a storage class associated with the instance on the container management platform is executed.

8. A container cloud deployment device based on the DPC protocol, characterized in that: The device comprises: A first creation unit is configured to create a single-master node cluster and an empty node pool through a container management platform, and then incorporate a bare metal node into the empty node pool; wherein the bare metal node has a storage access environment that supports the DPC protocol; An installation loading unit is configured to install the DPC client and the third-party container plug-in on the bare metal node in sequence, and then load the image of the third-party container plug-in into the local warehouse of the container management platform; A second creation unit is configured to create an instance based on the application template generated by the loaded image and assign a unique name to the instance; A deployment creation unit, configured to deploy a storage docking tool on the master node and configure connection parameters, and then create a storage class associated with the instance on the container management platform; The verification and determination unit is configured 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.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the container cloud deployment method based on the DPC protocol according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which includes program instructions. When the program instructions are executed by the processor, the processor executes the container cloud deployment method based on the DPC protocol as described in any one of claims 1 to 7.

Images