Offline deployment method and computing device

Abstract

The embodiment of the invention provides an offline deployment method and computing equipment, the method is applied to the computing equipment, the method comprises the steps that a deployment request sent by user equipment is received, and the deployment request is used for requesting deployment of a container cluster and a database cluster; determining a first target node for deploying a container cluster and a second target node for deploying a database cluster according to the deployment request; and deploying the container cluster offline at the first target node and deploying the database cluster offline at the second target node through an automatic operation and maintenance tool in the computing device. The method can be used for improving the container deployment efficiency.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of computing devices, and in particular, to an offline deployment method and a computing device. Background Art

[0002] Container clusters can be used for automated deployment, scaling, and management of containerized applications, enabling applications to be quickly deployed to the cloud, thereby accelerating the speed of business moving to the cloud.

[0003] In the related art, technicians can manually deploy container clusters. However, manual deployment of container clusters is time-consuming and laborious, resulting in low deployment efficiency of container clusters. Summary of the Invention

[0004] The embodiments of the present application provide an offline deployment method and a computing device, which are used to solve the technical problem of low deployment efficiency of container clusters.

[0005] In a first aspect, the embodiments of the present application provide an offline deployment method, which is applied to a computing device. The method includes:

[0006] Determine a first target node for deploying a container cluster and a second target node for deploying a database cluster according to the deployment request;

[0007] Deploy the container cluster offline on the first target node and deploy the database cluster offline on the second target node through an automated operation and maintenance tool in the computing device.

[0008] In the above solution, the computing device can receive a deployment request sent by a user device. The deployment request is used to request the deployment of a container cluster and a database cluster. It can determine a first target node for deploying the container cluster and a second target node for deploying the database cluster according to the deployment request. It can deploy the container cluster offline on the first target node and deploy the database cluster offline on the second target node through an automated operation and maintenance tool in the computing device. Through the above solution, the computing device can automatically deploy the container cluster and the database cluster in an offline state, improving the deployment efficiency of the cluster.

[0009] In a possible implementation manner, the determining the first target node for deploying the container cluster includes:

[0010] Obtain a first parameter from the user device;

[0011] Determine a first mode of the container cluster according to the first parameter. The first mode is a high-availability mode, a non-high-availability mode, or a single-machine mode;

[0012] Determine the first target node according to the first mode.

[0013] In the above solution, the computing device can determine the first mode according to the first parameter, and can determine the first target node according to the first mode, achieving the purpose of determining the first target node.

[0014] In one possible implementation, the determining the first target node according to the first mode includes:

[0015] Sending a first field to be configured to the user device according to the first mode;

[0016] Receiving a first field value corresponding to the first field to be configured sent by the user device;

[0017] Determining the first target node according to the first field value.

[0018] In the above solution, the computing device can determine the first target node for deploying the container cluster according to the first field value in the first mode, achieving the purpose of determining the first target node.

[0019] In one possible implementation,

[0020] The first field to be configured includes the address of the first target node;

[0021] Wherein, the first target node includes: the master node of the container cluster, or, the first target node includes: the master node of the container cluster and the worker nodes of the container cluster.

[0022] In the above solution, the first field to be configured can be the address of the first target node, enabling the computing device to determine the first target node according to the address of the first target node.

[0023] In one possible implementation, the determining the second target node for deploying the database cluster includes:

[0024] Obtaining a second parameter from the user device;

[0025] Determining a second mode of the database cluster according to the second parameter, where the second mode is a flexible database mode, a complex database mode, or a relational database mode;

[0026] Determining the second target node according to the second mode.

[0027] In the above solution, the computing device can determine the second mode according to the second parameter, and can determine the second target node according to the second mode, achieving the purpose of determining the second target node.

[0028] In a possible implementation, determining the second target node according to the second mode includes:

[0029] Sending a second field to be configured to the user equipment according to the second mode;

[0030] Receiving a second field value corresponding to the second field to be configured sent by the user equipment;

[0031] Determining the second target node according to the second field value.

[0032] In the above solution, the computing device can determine the second target node for deploying the database cluster in the second mode according to the second field value, achieving the purpose of determining the second target node.

[0033] In a possible implementation,

[0034] The second configuration field includes the address of the second target node;

[0035] Wherein, the number of the second target nodes is multiple.

[0036] In the above solution, the second field to be configured can be the address of the second target node, enabling the computing device to determine the second target node according to the address of the second target node.

[0037] In a possible implementation, the off-line deployment of the container cluster on the first target node and the off-line deployment of the database cluster on the second target node by the automated operation and maintenance tool includes:

[0038] Obtaining an off-line deployment installation package and an installation script;

[0039] Deploying the container cluster on the first target node and deploying the database cluster on the second target node according to the off-line deployment installation package and the installation script.

[0040] In the above solution, the computing device can deploy the container cluster and the database cluster off-line according to the off-line deployment installation package and the installation script, achieving the purpose of off-line automatic deployment of the container cluster and the database cluster and improving the deployment efficiency.

[0041] In a possible implementation, the off-line deployment installation package includes at least one of the following:

[0042] An off-line installation package for the container cluster operating system;

[0043] An off-line installation package for the container;

[0044] An off-line installation package for high-availability components;

[0045] Offline installation package for container image repository images;

[0046] Offline installation package for container orchestration engines;

[0047] Offline installation package for container interfaces;

[0048] Offline installation package for distributed storage systems;

[0049] Offline installation package for distributed file systems;

[0050] Offline installation package for log analysis systems;

[0051] Offline installation package for monitoring and alerting systems;

[0052] Offline installation package for disaster recovery components;

[0053] Offline installation package for microservice registration;

[0054] Offline installation package for multi-cloud management platforms;

[0055] Offline installation package for database systems;

[0056] Offline installation package for databases;

[0057] Offline installation package for database server monitoring systems; or,

[0058] Offline installation package for database monitoring systems.

[0059] In the above solutions, there are many types of offline deployment installation packages, which endow container clusters and database clusters with many functions.

[0060] In a second aspect, an embodiment of the present application provides an offline deployment device. The offline deployment device is applied to a computing device and includes a receiving module, a determining module, and a deployment module. Among them,

[0061] The receiving module is configured to receive a deployment request sent by a user device. The deployment request is used to request the deployment of a container cluster and a database cluster;

[0062] The determining module is configured to determine, according to the deployment request, a first target node for deploying the container cluster and a second target node for deploying the database cluster;

[0063] The deployment module is configured to, through an automated operation and maintenance tool in the computing device, offline deploy the container cluster on the first target node and offline deploy the database cluster on the second target node.

[0064] In the above solution, the offline deployment device can receive a deployment request sent by a user device. The deployment request is used to request the deployment of a container cluster and a database cluster. It can determine a first target node for deploying the container cluster and a second target node for deploying the database cluster according to the deployment request. It can deploy the container cluster on the first target node and the database cluster on the second target node offline through an automated operation and maintenance tool in the computing device. Through the above solution, the container cluster and the database cluster can be automatically deployed offline, improving the deployment efficiency of the cluster.

[0065] In a possible implementation manner, the determining module is specifically configured to,

[0066] Obtain a first parameter from the user device;

[0067] Determine a first mode of the container cluster according to the first parameter. The first mode is a high-availability mode, a non-high-availability mode, or a single-machine mode;

[0068] Determine the first target node according to the first mode.

[0069] In the above solution, the first mode can be determined according to the first parameter, and the first target node can be determined according to the first mode, achieving the purpose of determining the first target node.

[0070] In a possible implementation manner, the determining module is specifically configured to,

[0071] Send a first field to be configured to the user device according to the first mode;

[0072] Receive a first field value corresponding to the first field to be configured sent by the user device;

[0073] Determine the first target node according to the first field value.

[0074] In the above solution, the first target node for deploying the container cluster in the first mode can be determined according to the first field value, achieving the purpose of determining the first target node.

[0075] In a possible implementation manner,

[0076] The first field to be configured includes the address of the first target node;

[0077] Wherein, the first target node includes: the master node of the container cluster, or the first target node includes: the master node of the container cluster and the worker nodes of the container cluster.

[0078] In the above solution, the first field to be configured may be the address of the first target node, so that the computing device can determine the first target node according to the address of the first target node.

[0079] In a possible implementation manner, the determining module is specifically configured to,

[0080] Obtain a second parameter from the user device;

[0081] Determine a second mode of the database cluster according to the second parameter, where the second mode is a flexible database mode, a complex database mode, or a relational database mode;

[0082] Determine the second target node according to the second mode.

[0083] In the above solution, the second mode can be determined according to the second parameter, and the second target node can be determined according to the second mode, achieving the purpose of determining the second target node.

[0084] In a possible implementation manner, the determining module is specifically configured to,

[0085] Send a second field to be configured to the user device according to the second mode;

[0086] Receive a second field value corresponding to the second field to be configured sent by the user device;

[0087] Determine the second target node according to the second field value.

[0088] In the above solution, the second target node for deploying the database cluster in the second mode can be determined according to the second field value, achieving the purpose of determining the second target node.

[0089] In a possible implementation manner,

[0090] The second configuration field includes the address of the second target node;

[0091] Wherein, the number of the second target nodes is multiple.

[0092] In the above solution, the second field to be configured may be the address of the second target node, so that the computing device can determine the second target node according to the address of the second target node.

[0093] In a possible implementation manner, the deployment module is specifically configured to,

[0094] Obtain an offline deployment installation package and an installation script;

[0095] Deploy the container cluster on the first target node and deploy the database cluster on the second target node according to the offline deployment installation package and the installation script.

[0096] In the above solution, the computing device can deploy the container cluster and the database cluster offline according to the offline deployment installation package and the installation script, achieving the purpose of offline automatic deployment of the container cluster and the database cluster and improving the deployment efficiency.

[0097] In a possible implementation manner, the offline deployment installation package includes at least one of the following:

[0098] Offline installation package of the container cluster operating system;

[0099] Offline installation package of the container;

[0100] Offline installation package of the high-availability component;

[0101] Offline installation package of the container image repository image;

[0102] Offline installation package of the container orchestration engine;

[0103] Offline installation package of the container interface;

[0104] Offline installation package of the distributed storage system;

[0105] Offline installation package of the distributed file system;

[0106] Offline installation package of the log analysis system;

[0107] Offline installation package of the monitoring and alarming system;

[0108] Offline installation package of the disaster recovery component;

[0109] Offline installation package of the microservice registration;

[0110] Offline installation package of the multi-cloud management platform;

[0111] Offline installation package of the database system;

[0112] Offline installation package of the database;

[0113] Offline installation package of the database server monitoring system; or,

[0114] Offline installation package of the database monitoring system.

[0115] In the above solution, the types of the offline deployment installation package are numerous, enabling the container cluster and the database cluster to have more functions.

[0116] In a third aspect, an embodiment of the present application provides a computing device, including: a memory, a processor;

[0117] The memory stores computer-executable instructions;

[0118] The processor executes the computer-executable instructions stored in the memory, such that the processor performs the above first aspect and / or various possible implementation manners of the first aspect.

[0119] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the above first aspect and / or various possible implementation manners of the first aspect.

[0120] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the above first aspect and / or various possible implementation manners of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0121] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0122] Figure 1 It is a schematic flowchart of an offline deployment method provided by an embodiment of the present application;

[0123] Figure 2 It is a schematic flowchart of another offline deployment method provided by an embodiment of the present application;

[0124] Figure 3A It is a schematic flowchart of a determination process of a first target node provided by an embodiment of the present application;

[0125] Figure 3B It is a schematic flowchart of another determination process of a first target node provided by an embodiment of the present application;

[0126] Figure 4 It is a schematic flowchart of yet another offline deployment method provided by an embodiment of the present application;

[0127] Figure 5A It is a schematic flowchart of a determination process of a second target node provided by an embodiment of the present application;

[0128] Figure 5B It is a schematic flowchart of another determination process of a second target node provided by an embodiment of the present application;

[0129] Figure 5CAnother schematic diagram of the determination process of the second target node provided by the embodiment of the present application;

[0130] Figure 6 Another schematic diagram of the process of an offline deployment method provided by the embodiment of the present application;

[0131] Figure 7 A schematic diagram of a container cluster and a database cluster provided by the embodiment of the present application;

[0132] Figure 8 A schematic diagram of the structure of an offline deployment device provided by the embodiment of the present application;

[0133] Figure 9 A schematic diagram of the structure of a computing device provided by the embodiment of the present application. Detailed implementation manners

[0134] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the embodiments of the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the appended claims.

[0135] The technical solution provided by the embodiment of the present application is applicable to the container deployment scenario and is used to improve the container deployment efficiency.

[0136] The technical solution of the embodiment of the present application will be described in detail below with specific embodiments. These several specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0137] Figure 1 A schematic diagram of the process of an offline deployment method provided by the embodiment of the present application. The execution subject of this method can be a computing device or a processor set in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the execution subject is taken as the computing device for illustration. Please refer to Figure 1 , this method may include:

[0138] S101. Receive a deployment request sent by a user device, where the deployment request is used to request the deployment of a container cluster and a database cluster.

[0139] The container cluster can be, for example, a container orchestration engine (Kubernetes, K8S) cluster, etc.

[0140] S102. Determine a first target node for deploying a container cluster and a second target node for deploying a database cluster according to the deployment request.

[0141] The number of the first target node and the second target node can each be one or more, and the embodiments of the present application do not limit this.

[0142] The deployment request can trigger the computing device to determine the first target node and the second target node.

[0143] When determining the first target node, the computing device can first determine the first mode of the container cluster, and then determine the first target node according to the first mode.

[0144] The first mode can be a high-availability mode, a non-high-availability mode, or a single-machine mode.

[0145] The high-availability mode can also be called the CLUSTER mode, the non-high-availability mode can also be called the SINGLE mode, and the single-machine mode can also be called the ONLY mode.

[0146] Specifically, the computing device can obtain a first parameter from the user device and can determine the first mode of the container cluster according to the first parameter. After the computing device determines the first mode, it can obtain the address of the first target node from the user device. The computing device can determine the first target node according to the address of the first target node.

[0147] When determining the second target node, the computing device can first determine the second mode of the database cluster, and then determine the second target node according to the second mode.

[0148] The second mode can be a flexible database mode, a complex database mode, or a relational database mode.

[0149] The flexible database mode can also be called the MongoDB mode, the complex database mode can also be called the PostgreSQL mode, and the relational database mode can also be called the MySQL mode.

[0150] Specifically, the computing device can obtain a second parameter from the user device and can determine the second mode of the database cluster according to the second parameter. After the computing device determines the second mode, it can obtain the address of the second target node from the user device. The computing device can determine the second target node according to the address of the second target node.

[0151] S103. Through the automated operation and maintenance tool in the computing device, deploy the container cluster offline on the first target node and deploy the database cluster offline on the second target node.

[0152] The automated operation and maintenance tool can be, for example, the ansible automation tool.

[0153] Automated operation and maintenance tools can be pre-installed in the computing device; alternatively, the computing device can install the automated operation and maintenance tools before deploying the container cluster and the database cluster. The embodiments of the present application do not limit this.

[0154] In some embodiments, before deploying the container cluster on the first target node and the database cluster on the second target node, the computing device can also perform security authentication processing on the first target node and the second target node.

[0155] The security authentication processing can be, for example, establishing mutual trust. When establishing mutual trust, the computing device can execute a mutual trust script to implement a remote login mutual trust mode between the first target node and the second target node.

[0156] In the offline deployment method provided in this embodiment, the computing device can receive a deployment request sent by the user device, where the deployment request is used to request the deployment of the container cluster and the database cluster; it can determine the first target node for deploying the container cluster and the second target node for deploying the database cluster according to the deployment request; and it can deploy the container cluster offline on the first target node and the database cluster offline on the second target node through the automated operation and maintenance tools in the computing device. Through the above method, the computing device can automatically deploy the container cluster and the database cluster in an offline state, improving the deployment efficiency of the cluster.

[0157] Based on the above embodiments, the following combines Figure 2 , to illustrate the process of the computing device determining the first target node.

[0158] Figure 2 FIG. is a schematic flowchart of another offline deployment method provided in the embodiments of the present application. The execution subject of this method can be a computing device or a processor provided in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the execution subject is taken as the computing device for illustration. Please refer to Figure 2 , this method can include:

[0159] S201. Obtain a first parameter from the user device.

[0160] The user device can be a computer, a mobile phone, a tablet computer, etc.

[0161] In this embodiment, when obtaining the first parameter, the computing device can control the user device to display a first page, and the first page includes a first parameter input control.

[0162] The first parameter input control can be used to receive elements input by the user.

[0163] For example, the first parameter input control can be a text box, which can be used to receive text or numbers input by the user.

[0164] After the user device displays the first page, the user can input the first parameter at the position of the first parameter input control, so that the user device can receive the first parameter.

[0165] After the user device receives the first parameter, it can send the first parameter to the computing device, so that the computing device can obtain the first parameter.

[0166] Optionally, before the computing device controls the user device to display the first page, it can also control the user device to display a confirmation page. The confirmation page is used to prompt the user to confirm whether they have read the instruction manual. If the user has read the instruction manual, the computing device can control the user device to display the first page. If the user has not read the instruction manual, the computing device can exit the offline deployment process.

[0167] For example, the confirmation page can include a preset field, which can be used to ask the user whether they have read the instruction manual. If the user has read the instruction manual, they can enter "YES"; if the user has not read the instruction manual, they can enter "NO".

[0168] S202. Determine the first mode of the container cluster according to the first parameter.

[0169] The first parameter can be used to indicate the first mode.

[0170] The first parameter can be in the form of numbers, letters, or strings, etc. The specific form of the first parameter is not limited in this embodiment. When the first parameter is different, the first mode is also different.

[0171] Optionally, there may be a corresponding relationship between the first parameter and the first mode. The computing device can determine the first mode according to the first parameter and the corresponding relationship between the first parameter and the first mode.

[0172] For example, the corresponding relationship between the first parameter and the first mode can be shown in Table 1:

[0173] Table 1

[0174] First parameter First mode CLUSTER High-availability mode SINGLE Non-high-availability mode ONLY Single-machine mode

[0175] As shown in Table 1, if the first parameter is "CLUSTER", the first mode is the high-availability mode; if the first parameter is "SINGLE", the first mode is the non-high-availability mode; if the first parameter is "ONLY", the first mode is the single-machine mode.

[0176] S203. Send the first field to be configured to the user device according to the first mode.

[0177] In this embodiment, after the computing device sends the first field to be configured to the user device, the user device can display a second page, and the second page includes the first field to be configured.

[0178] The first field to be configured on the second page is used to indicate that the user inputs a first field value corresponding to the first field to be configured.

[0179] The first field to be configured includes the address of the first target node; wherein, the first target node includes: the master node of the container cluster, or, the first target node includes: the master node of the container cluster and the worker nodes of the container cluster.

[0180] Specifically, if the first mode is the single-machine mode, the container cluster may include only one master node, then the first target node may include the master node of the container cluster. If the first mode is the high-availability mode, the container cluster may include multiple master nodes and multiple worker nodes, then the first target node may include the master node of the container cluster and the worker nodes of the container cluster. If the first mode is the non-high-availability mode, the container cluster may include one master node and multiple worker nodes, then the first target node may include the master node of the container cluster and the worker nodes of the container cluster.

[0181] Specifically, after the computing device determines the first mode, it can send the first field to be configured to the user device. The first field to be configured can trigger the user device to display the second page, so as to indicate the user to input the first field value corresponding to the first field to be configured through the first field to be configured displayed on the second page.

[0182] It should be noted that if the first field to be configured includes the addresses of multiple first target nodes, the user device can display the second page once, and the second page can include the addresses of the multiple first target nodes. Or, if the first field to be configured includes the addresses of multiple first target nodes, the user device can also display the second page multiple times, and the second page can include the address of one first target node each time.

[0183] S204. Receive the first field value corresponding to the first field to be configured sent by the user device.

[0184] The first field value corresponding to the first field to be configured can be the address of the first target node input by the user.

[0185] Specifically, the user can input the first field value on the second page so that the user device can receive the first field value. After the user device receives the first field value, it can send the first field value to the computing device.

[0186] In some embodiments, after the computing device receives the first field value, it can also update the first field value to the first configuration file corresponding to the container cluster.

[0187] In some embodiments, after receiving the first field value, the computing device may further receive the field value corresponding to a preset configuration field input by the user.

[0188] The preset fields to be configured include at least one of the following: Network File System (NFS) node address; container image repository node address; object storage node address; service Classless Inter-Domain Routing (CIDR) address; pod CIDR address; subnet mask address of the computing device; virtual IP address of the master node of the container cluster; network card name of the computing device; Network Time Protocol (NTP) node address; drive letter of the data disk of the distributed storage node; monitoring and alarm parameters; or, the root account password of the computing device.

[0189] Among them, the container image repository node address may also be referred to as the Harbor address. The object storage node address may also be referred to as the MiniO address. The service CIDR address may also be referred to as the SERVICE CIDR address. The pod CIDR address may also be referred to as the POD CIDR address. The drive letter of the data disk of the distributed storage node may also be referred to as the drive letter of the CEPH data disk. The root account password of the computing device may also be referred to as the root account password of the computing device.

[0190] In some embodiments, after the computing device receives the preset field value, it may further update the preset field value to the first configuration file and the first address file corresponding to the container cluster.

[0191] S205. Determine a first target node according to the first field value.

[0192] The first field value may be the address of the first target node input by the user. It should be understood that the computing device may determine the first target node according to the first field value.

[0193] In the offline deployment method provided in this embodiment, the computing device may obtain a first parameter from the user device; may determine a first mode of the container cluster according to the first parameter; may send a first field to be configured to the user device according to the first mode; may receive the first field value corresponding to the first field to be configured sent by the user device; and may determine the first target node according to the first field value. Through the above method, the purpose of determining the first target node can be achieved.

[0194] Based on the above embodiments, the following combines Figure 3A and Figure 3B , and exemplarily describes the process of the computing device determining the first target node.

[0195] First, combineFigure 3A , the determination process of the first target node in the high-availability mode is described.

[0196] Figure 3A This is a schematic diagram of the determination process of a first target node provided by an embodiment of the present application. The execution subject of this method can be a computing device or a processor provided in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the execution subject is taken as an example of a computing device for description. Please refer to Figure 3A , the method may include:

[0197] S3101. Determine whether the user has read the instruction manual.

[0198] If the user has not read the instruction manual, execute S3102;

[0199] If the user has read the instruction manual, execute S3103.

[0200] S3102. Exit the offline deployment process.

[0201] S3103. Obtain a first parameter from the user device.

[0202] S3104. Determine a first mode according to the first parameter.

[0203] It is assumed that the first mode in this embodiment is the high-availability mode.

[0204] S3105. Send a first field to be configured to the user device.

[0205] S3106. Receive a first field value corresponding to the first field to be configured.

[0206] In the high-availability mode, the first field value can be 3 main node addresses and 6 working node addresses input by the user.

[0207] S3107. Update the first field value to the first configuration file.

[0208] S3018. Receive the NFS node address sent by the user device.

[0209] It should be noted that S3108 can be executed after S3107, or S3108 can be executed before S3107, or S3108 can be executed simultaneously with S3107. This embodiment does not make a limitation on this.

[0210] S3109. Update the NFS node address to the first address file.

[0211] S3110. Receive the Harbor address sent by the user device.

[0212] It should be noted that S3110 can be executed after S3109, or S3110 can be executed before S3109, or S3110 can be executed simultaneously with S3109. This embodiment does not limit this.

[0213] S3111. Update the Harbor address to the first configuration file.

[0214] S3112. Receive the MiniO address sent by the user device.

[0215] It should be noted that S3112 can be executed after S3111, or S3112 can be executed before S3111, or S3112 can be executed simultaneously with S3111. This embodiment does not limit this.

[0216] S3113. Update the MiniO address to the first configuration file.

[0217] S3114. Receive the SERVICE CIDR address sent by the user device.

[0218] It should be noted that S3114 can be executed after S3113, or S3114 can be executed before S3113, or S3114 can be executed simultaneously with S3113. This embodiment does not limit this.

[0219] S3115. Update the SERVICE CIDR address to the first configuration file.

[0220] S3116. Receive the POD CIDR address sent by the user device.

[0221] It should be noted that S3116 can be executed after S3115, or S3116 can be executed before S3115, or S3116 can be executed simultaneously with S3115. This embodiment does not limit this.

[0222] S3117. Update the POD CIDR address to the first configuration file.

[0223] S3118. Receive the subnet mask address sent by the user device.

[0224] It should be noted that S3118 can be executed after S3117, or S3118 can be executed before S3117, or S3118 can be executed simultaneously with S3117. This embodiment does not limit this.

[0225] S3119. Update the subnet mask address to the first address file.

[0226] S3120. Receive the virtual IP address of the master node of the container cluster sent by the user device.

[0227] It should be noted that S3120 can be executed after S3119, or S3120 can be executed before S3119, or S3120 can be executed simultaneously with S3119. This embodiment does not make any limitations in this regard.

[0228] S3121. Update the virtual IP address of the master node of the container cluster to the first address file.

[0229] S3122. Receive the network card name of the computing device sent by the user device.

[0230] It should be noted that S3122 can be executed after S3121, or S3122 can be executed before S3121, or S3122 can be executed simultaneously with S3121. This embodiment does not make any limitations in this regard.

[0231] S3123. Update the network card name of the computing device to the first address file.

[0232] S3124. Receive the NTP node address sent by the user device.

[0233] It should be noted that S3124 can be executed after S3123, or S3124 can be executed before S3123, or S3124 can be executed simultaneously with S3123. This embodiment does not make any limitations in this regard.

[0234] S3125. Update the NTP node address to the first address file.

[0235] S3126. Receive the drive letter of the data disk of CEPH sent by the user device.

[0236] It should be noted that S3126 can be executed after S3125, or S3126 can be executed before S3125, or S3126 can be executed simultaneously with S3125. This embodiment does not make any limitations in this regard.

[0237] S3127. Update the drive letter of the data disk of CEPH to the first address file.

[0238] S3128. Receive the monitoring and alarm parameters sent by the user device.

[0239] It should be noted that S3128 can be executed after S3127, or S3128 can be executed before S3127, or S3128 can be executed simultaneously with S3127. This embodiment does not make any limitations in this regard.

[0240] S3129. Update the monitoring and alarm parameters to the first address file.

[0241] S3130. Receive the root account password of the computing device sent by the user device.

[0242] It should be noted that S3130 can be executed after S3129, or S3130 can be executed before S3129, or S3130 can be executed simultaneously with S3129. This embodiment does not make a limitation on this.

[0243] S3131. Update the root account password of the computing device to the first address file.

[0244] Secondly, in combination with Figure 3B , the determination process of the first target node in the non-high-availability mode will be described.

[0245] Figure 3B This is another schematic diagram of the determination process of the first target node provided by the embodiment of the present application. The execution subject of this method can be a computing device or a processor set in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the execution subject is taken as the computing device as an example for description. Please refer to Figure 3B , this method may include:

[0246] S3201. Determine whether the user has read the instruction manual.

[0247] If the user has not read the instruction manual, execute S3201;

[0248] If the user has read the instruction manual, execute S3203.

[0249] S3202. Exit the offline deployment process.

[0250] S3203. Obtain the first parameter from the user device.

[0251] S3204. Determine the first mode according to the first parameter.

[0252] Assume that the first mode in this embodiment is the non-high-availability mode.

[0253] S3205. Send the first to-be-configured field to the user device.

[0254] S3206. Receive the first field value corresponding to the first to-be-configured field.

[0255] In the non-high-availability mode, the first field value can be 1 main node address input by the user and 5 working node addresses.

[0256] S3207. Update the first field value to the first configuration file.

[0257] S3208. Receive the NFS node address sent by the user device.

[0258] It should be noted that S3208 can be executed after S3207, or S3208 can be executed before S3207, or S3208 can be executed simultaneously with S3207. This embodiment does not limit this.

[0259] S3209. Update the NFS node address to the first address file.

[0260] S3210. Receive the Harbor address sent by the user device.

[0261] It should be noted that S3209 can be executed after S3210, or S3209 can be executed before S3210, or S3209 can be executed simultaneously with S3210. This embodiment does not limit this.

[0262] S3211. Update the Harbor address to the first configuration file.

[0263] S3212. Receive the MiniO address sent by the user device.

[0264] It should be noted that S3212 can be executed after S3211, or S3212 can be executed before S3211, or S3212 can be executed simultaneously with S3211. This embodiment does not limit this.

[0265] S3213. Update the MiniO address to the first configuration file.

[0266] S3214. Receive the SERVICE CIDR address sent by the user device.

[0267] It should be noted that S3214 can be executed after S3213, or S3214 can be executed before S3213, or S3214 can be executed simultaneously with S3213. This embodiment does not limit this.

[0268] S3215. Update the SERVICE CIDR address to the first configuration file.

[0269] S3216. Receive the POD CIDR address sent by the user device.

[0270] It should be noted that S3216 can be executed after S3215, or S3216 can be executed before S3215, or S3216 can be executed simultaneously with S3215. This embodiment does not limit this.

[0271] S3217. Update the POD CIDR address to the first configuration file.

[0272] S3218. Receive the subnet mask address sent by the user device.

[0273] It should be noted that S3218 can be executed after S3217, or S3218 can be executed before S3217, or S3218 can be executed simultaneously with S3217. This embodiment does not limit this.

[0274] S3219. Update the subnet mask address to the first address file.

[0275] S3220. Receive the network card name of the computing device sent by the user device.

[0276] It should be noted that S3220 can be executed after S3219, or S3220 can be executed before S3219, or S3220 can be executed simultaneously with S3219. This embodiment does not limit this.

[0277] S3221. Update the network card name of the computing device to the first address file.

[0278] S3222. Receive the NTP node address sent by the user device.

[0279] It should be noted that S3222 can be executed after S3221, or S3222 can be executed before S3221, or S3222 can be executed simultaneously with S3221. This embodiment does not limit this.

[0280] S3223. Update the NTP node address to the first address file.

[0281] S3224. Receive the drive letter of the data disk of CEPH sent by the user device.

[0282] It should be noted that S3224 can be executed after S3223, or S3224 can be executed before S3223, or S3224 can be executed simultaneously with S3223. This embodiment does not limit this.

[0283] S3225. Update the drive letter of the data disk of CEPH to the first address file.

[0284] S3226. Receive the monitoring and alarm parameters sent by the user device.

[0285] It should be noted that S3226 can be executed after S3225, or S3226 can be executed before S3225, or S3226 can be executed simultaneously with S3225. This embodiment does not limit this.

[0286] S3227. Update the monitoring and alarm parameters to the first address file.

[0287] S3228. Receive the root account password of the computing device sent by the user device.

[0288] It should be noted that S3228 can be executed after S3227, or S3228 can be executed before S3227, or S3228 can be executed simultaneously with S3227. This embodiment does not make any limitations in this regard.

[0289] S3229. Update the root account password of the computing device to the first address file.

[0290] It should be noted that in the single-machine mode, the container cluster can include only one master node. That is to say, the value of the first field input by the user can be the address of 1 master node. In addition, other processes are the same as the process for determining the first target node in the non-high-availability mode, and will not be elaborated here.

[0291] Based on any of the above embodiments, the process of determining the second target node by the computing device will be described below in conjunction with Figure 4 , and the process of determining the second target node by the computing device will be described.

[0292] Figure 4 FIG. is a schematic flowchart of another offline deployment method provided by an embodiment of the present application. The execution subject of this method can be a computing device or a processor provided in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the execution subject is taken as an example of the computing device for description. Please refer to Figure 4 , and the method may include:

[0293] S401. Obtain a second parameter from the user device.

[0294] In this embodiment, when obtaining the second parameter, the computing device can control the user device to display a third page, and the third page includes a second parameter input control.

[0295] The second parameter input control can be used to receive elements input by the user.

[0296] For example, the second parameter input control can be a drop-down menu, and the second parameter input control can provide a selectable list, and the user can select an option from it.

[0297] After the user device displays the third page, the user can input the second parameter at the position of the second parameter input control so that the user device can receive the second parameter.

[0298] After receiving the second parameter, the user device may send the second parameter to the computing device so that the computing device can obtain the second parameter.

[0299] S402. Determine the second mode of the database cluster according to the second parameter.

[0300] The second parameter can be used to indicate the second mode.

[0301] The second parameter can be in the form of numbers, letters, or strings, etc. The specific form of the second parameter is not limited in this embodiment. When the second parameter is different, the second mode is also different.

[0302] Optionally, there may be a corresponding relationship between the second parameter and the second mode. The computing device can determine the second mode according to the second parameter and the corresponding relationship between the second parameter and the second mode.

[0303] For example, the corresponding relationship between the second parameter and the second mode can be as shown in Table 2:

[0304] Table 2

[0305] Second parameter Second mode MongoDB Flexible database mode PostgreSQL Complex database mode MySQL Relational database mode

[0306] As shown in Table 2, if the second parameter is "MongoDB", the second mode is the flexible database mode; if the second parameter is "PostgreSQL", the second mode is the complex database mode; if the second parameter is "MySQL", the second mode is the relational database mode.

[0307] In some embodiments, after the computing device determines the second mode, it can also set other modes to the uninstalled state in the second configuration file corresponding to the database cluster; where the other modes are the modes other than the second mode among the flexible database mode, the complex database mode, and the relational database mode.

[0308] S403. Send the second field to be configured to the user device according to the second mode.

[0309] In this embodiment, after the computing device sends the second field to be configured to the user device, the user device can display the fourth page, and the fourth page includes the second field to be configured.

[0310] The second field to be configured on the fourth page is used to indicate that the user inputs the second field value corresponding to the second field to be configured.

[0311] The second configuration field includes the addresses of the second target nodes; where the number of the second target nodes is multiple.

[0312] Specifically, the database cluster may include multiple nodes, that is to say, the number of the second target nodes can be multiple.

[0313] Specifically, after the computing device determines the second mode, it can send a second field to be configured to the user device. The second field to be configured can trigger the user device to display a fourth page, and the second field to be configured displayed on the fourth page can instruct the user to input a second field value corresponding to the second field to be configured.

[0314] It should be noted that the user device can display the fourth page once, and the fourth page can include the addresses of multiple second target nodes. Alternatively, the user device can also display the fourth page multiple times, and each time the fourth page can include the address of one second target node.

[0315] S404. Receive the second field value corresponding to the second field to be configured sent by the user device.

[0316] The second field value corresponding to the second field to be configured can be the address of the second target node input by the user.

[0317] Specifically, the user can input the second field value on the fourth page so that the user device can receive the second field value. After the user device receives the second field value, it can send the second field value to the computing device.

[0318] In some embodiments, after the computing device receives the second field value, it can also update the second field value to the second configuration file corresponding to the database cluster and the second address file corresponding to the database cluster.

[0319] S405. Determine the second target node according to the second field value.

[0320] The second field value can be the address of the second target node input by the user. It should be understood that the computing device can determine the second target node according to the second field value.

[0321] In the offline deployment method provided in this embodiment, the computing device can obtain a second parameter from the user device; can determine the second mode of the database cluster according to the second parameter; can send a second field to be configured to the user device according to the second mode; can receive the second field value corresponding to the second field to be configured sent by the user device; and can determine the second target node according to the second field value. Through the above method, the purpose of determining the second target node can be achieved.

[0322] Based on the above embodiments, the following combines Figures 5A - 5C , and exemplarily describes the process of the computing device determining the second target node.

[0323] First, combine Figure 5A , and describe the process of determining the second target node in the MongoDB mode.

[0324] Figure 5A This is a schematic diagram of the determination process of a second target node provided by an embodiment of the present application. The execution subject of this method can be a computing device or a processor provided in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the execution subject is taken as an example of a computing device for illustration. Please refer to Figure 5A This method may include:

[0325] S5101. Obtain a second parameter from the user device.

[0326] S5102. Determine a second mode according to the second parameter.

[0327] It is assumed that in this embodiment, the second mode is the MongoDB mode.

[0328] S5103. Send a second field to be configured to the user device.

[0329] The second field to be configured is used to request and obtain the address of the second target node.

[0330] S5104. Receive the address of node 01 in the database cluster in the MongoDB mode sent by the user device.

[0331] S5105. Update the address of node 01 in the database cluster to the second configuration file and the second address file.

[0332] S5106. Receive the address of node 02 in the database cluster in the MongoDB mode sent by the user device.

[0333] It should be noted that S5106 can be executed after S5105, or S5106 can be executed before S5105, or S5106 can be executed simultaneously with S5105. This embodiment does not make a limitation on this.

[0334] S5107. Update the address of node 02 in the database cluster to the second configuration file and the second address file.

[0335] S5108. Receive the address of node 03 in the database cluster in the MongoDB mode sent by the user device.

[0336] It should be noted that S5108 can be executed after S5107, or S5108 can be executed before S5107, or S5108 can be executed simultaneously with S5107. This embodiment does not make a limitation on this.

[0337] S5109. Update the address of node 03 in the database cluster to the second configuration file and the second address file.

[0338] It should be noted that the second target nodes include the nodes of database cluster 01, the nodes of database cluster 02, and the nodes of database cluster 03 under the MongoDB mode.

[0339] Secondly, in combination with Figure 5B , the determination process of the second target nodes under the PostgreSQL mode will be described.

[0340] Figure 5B FIG. is a schematic diagram of another determination process of the second target nodes provided by an embodiment of the present application. The execution subject of this method can be a computing device or a processor provided in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the case where the execution subject is a computing device will be taken as an example for description. Please refer to Figure 5B , this method may include:

[0341] S5201. Obtain a second parameter from the user device.

[0342] S5202. Determine a second mode according to the second parameter.

[0343] It is assumed that in this embodiment, the second mode is the PostgreSQL mode.

[0344] S5203. Send a second field to be configured to the user device.

[0345] The second field to be configured is used to request and obtain the address of the second target node.

[0346] S5204. Receive the address of the main node of the database cluster under the PostgreSQL mode sent by the user device.

[0347] S5205. Update the address of the main node of the database cluster to the second configuration file and the second address file.

[0348] S5026. Receive the address of the slave node of the database cluster under the PostgreSQL mode sent by the user device.

[0349] It should be noted that S5206 can be executed after S5205, or S5206 can be executed before S5205, or S5206 can be executed simultaneously with S5205. This embodiment does not make any limitation in this regard.

[0350] S5027. Update the address of the slave node of the database cluster to the second configuration file and the second address file.

[0351] It should be noted that the second target nodes include the main node of the database cluster and the slave node of the database cluster under the PostgreSQL mode.

[0352] Secondly, in combination with Figure 5C , the determination process of the second target node in the MySQL mode will be described.

[0353] Figure 5C It is a schematic diagram of another determination process of the second target node provided by the embodiment of the present application. The execution subject of this method can be a computing device or a processor set in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the case where the execution subject is a computing device will be used as an example for description. Please refer to Figure 5C , this method may include:

[0354] S5301. Obtain a second parameter from the user device.

[0355] S5302. Determine a second mode according to the second parameter.

[0356] It is assumed that the second mode in this embodiment is the MySQL mode.

[0357] S5303. Send a second field to be configured to the user device.

[0358] The third field to be configured is used to request to obtain the address of the second target node.

[0359] S5304. Receive the address of the main node of the database cluster in the MySQL mode sent by the user device.

[0360] S5305. Update the address of the main node of the database cluster to the second configuration file and the second address file.

[0361] S5306. Receive the address of the slave node of the database cluster in the MySQL mode sent by the user device.

[0362] It should be noted that S5306 can be executed after S5305, or S5306 can be executed before S5305, or S5306 can be executed simultaneously with S5305. This embodiment does not make a limitation on this.

[0363] S5307. Update the address of the slave node of the database cluster to the second configuration file and the second address file.

[0364] It should be noted that the second target node includes the main node of the database cluster and the slave node of the database cluster in the MySQL mode.

[0365] Based on any of the above embodiments, after determining the first target node and the second target node, the computing device can deploy a container cluster on the first target node and can deploy a database cluster on the second target node. Next, in combination withFigure 6 , the offline deployment method provided in the embodiments of the present application will be further described.

[0366] Figure 6 It is a schematic flowchart of another offline deployment method provided in the embodiments of the present application. The execution subject of this method can be a computing device or a processor provided in the computing device. The computing device can be, for example, a server. The processor in the computing device can be, for example, the CPU in the server. For ease of understanding, in the following, the case where the execution subject is a computing device will be taken as an example for description. Please refer to Figure 6 , this method may include:

[0367] S601. Receive a deployment request sent by a user device, where the deployment request is used to request the deployment of a container cluster and a database cluster.

[0368] It should be noted that the specific implementation manner of S601 can refer to S101, which will not be elaborated here.

[0369] S602. Obtain a first parameter from the user device.

[0370] S603. Determine a first mode of the container cluster according to the first parameter.

[0371] S604. Send a first field to be configured to the user device according to the first mode.

[0372] S605. Receive a first field value corresponding to the first field to be configured sent by the user device.

[0373] S606. Determine a first target node according to the first field value.

[0374] It should be noted that the specific implementation manners of S602 - S606 can refer to S201 - S205, which will not be elaborated here.

[0375] S607. Obtain a second parameter from the user device.

[0376] S608. Determine a second mode of the database cluster according to the second parameter.

[0377] S609. Send a second field to be configured to the user device according to the second mode.

[0378] S610. Receive a second field value corresponding to the second field to be configured sent by the user device.

[0379] S611. Determine a second target node according to the second field value.

[0380] It should be noted that the specific implementation manners of S607 - S611 can refer to S401 - S405, which will not be elaborated here.

[0381] S612. Obtain the offline deployment installation package and the installation script.

[0382] The offline deployment installation package can be the offline installation packages of the respective components corresponding to the container cluster and the offline installation packages of the respective components of the database cluster.

[0383] The installation script can include: the offline installation scripts of the respective components corresponding to the container cluster and the offline installation scripts of the respective components of the database cluster.

[0384] In this embodiment, the offline deployment installation package includes at least one of the following: the offline installation package of the container cluster operating system (OperatingSystem, OS); the offline installation package of Docker; the offline installation package of the High Availability (HA) component; the offline installation package of the Harbor image of the container image repository; the offline installation package of the Kubernetes (K8S) container orchestration engine; the offline installation package of the Ingress of the container; the offline installation package of the Ceph distributed storage system; the offline installation package of the Network File System (NFS); the offline installation package of the log analysis system; the offline installation package of the monitoring and alerting system; the offline installation package of the disaster recovery component; the offline installation package of the microservice registration; the offline installation package of the multi-cloud management platform; the offline installation package of the database system; the offline installation package of the database; the offline installation package of the database server monitoring system; or, the offline installation package of the database monitoring system.

[0385] In this embodiment, the installation script can at least include the offline installation script corresponding to the above offline deployment installation package.

[0386] In this embodiment, the computing device can obtain the offline deployment installation package and the installation script from the local.

[0387] S613. According to the offline deployment installation package and the installation script, deploy the container cluster offline on the first target node and deploy the database cluster offline on the second target node.

[0388] It should be noted that for any component corresponding to the container cluster or any component corresponding to the database cluster, the computing device deploys the component on the corresponding node in the same way. In this embodiment, taking any component as an example, the method for offline deploying the component will be described.

[0389] For any component corresponding to the container cluster or any component corresponding to the database cluster, the computing device can deploy the component on the corresponding node according to the offline installation package of the component and the offline installation script corresponding to the component.

[0390] Specifically, the computing device can instruct the corresponding node to create an offline installation and deployment working directory through an automated operation and maintenance tool, copy the offline deployment installation package of the component and the offline installation script of the component to the offline installation and deployment working directory, and instruct the corresponding node to execute the offline installation script of the component, thereby completing the offline deployment of the component.

[0391] For example, taking the HA component as an example, the HA component can be deployed on the master node of the container cluster. When deploying the HA component, the computing device can instruct the master node of the container cluster to create an offline installation and deployment working directory through an automated operation and maintenance tool, copy the offline deployment installation package of the HA component and the offline installation script of the HA component to the offline installation and deployment working directory, and instruct the master node of the container cluster to execute the offline installation script of the HA component, thereby completing the offline deployment of the HA component.

[0392] It should be noted that before deploying the container cluster on the first target node and deploying the database cluster on the second target node, an automated operation and maintenance tool can also be deployed on the first target node and an automated operation and maintenance tool can be deployed on the second target node. The method of deploying the automated operation and maintenance tool is the same as the method of deploying the component, which will not be elaborated here.

[0393] In the offline deployment method provided in this embodiment, the computing device can receive a deployment request sent by the user device; obtain a first parameter from the user device; determine a first mode of the container cluster according to the first parameter; send a first to-be-configured field to the user device according to the first mode; receive a first field value corresponding to the first to-be-configured field sent by the user device; determine a first target node according to the first field value; obtain a second parameter from the user device; determine a second mode of the database cluster according to the second parameter; send a second to-be-configured field to the user device according to the second mode; receive a second field value corresponding to the second to-be-configured field sent by the user device; determine a second target node according to the second field value; obtain an offline deployment installation package and an installation script; and offline deploy the container cluster on the first target node and offline deploy the database cluster on the second target node according to the offline deployment installation package and the installation script. Through the above method, the computing device can automatically deploy the container cluster and the database cluster in an offline state, improving the deployment efficiency of the cluster. In addition, in the above method, there is no need for technicians to manually deploy, and there is no need for technicians to learn to use the automated operation and maintenance tool, which further improves the deployment efficiency and reduces errors that may be caused by manual operations. In addition, through the above method, the offline deployment of disaster recovery components, microservice registration, and monitoring and alarm system log analysis systems can also be completed, enabling users to quickly complete the deployment of the container cluster and the database cluster, and thus accelerating the cloud migration efficiency of user services.

[0394] Based on any of the above embodiments, before deploying the container cluster and the database cluster, an offline deployment installation package can also be made. Next, the process of making the offline deployment installation package will be described by way of example.

[0395] 1) Making the offline installation package of the ansible automation tool.

[0396] Configure the image source on the computing device and create an ansible folder on the root partition of the computing device. The computing device executes the command: yum -y install ansible --downloadonly --downloaddir= / root / ansible to generate the dependency packages of the ansible automation tool in the / root / ansible directory and complete the source finding of the dependency packages of the ansible automation tool. Among them, the dependency packages of the ansible automation tool can be in the form of rpm packages.

[0397] The computing device switches to the / root / ansible directory and executes the commands: yum -y localisntall. / *.rpm and ansible –version. After successful execution, the offline installation package of the ansible automation tool can be made.

[0398] The computing device switches to the / root / ansible directory, executes the compression command, transfers it to the local personal computer, and marks it as the offline installation package of the ansible automation tool to complete the archiving of the offline installation package of the ansible automation tool.

[0399] 2) Making the offline installation package of the container cluster OS.

[0400] The computing device downloads the kernel upgrade packages kernel-ml-4.19.12-1.el7.elrepo.x86_64.rpm and kernel-ml-devel-4.19.12-1.el7.elrepo.x86_64.rpm. The computing device creates a kernel directory in the root partition and executes the command: yum -y install yum-utils --downloadonly --downloaddir= / root / kernel, switches to the / root / kernel directory, changes the value of the parameter keepcache in the operating system configuration file: / etc / yum.conf from 0 to 1, and then executes the command: yum -y localinstall. / *.rpm. Then it switches to the / var / cache / yum directory, finds all rpm packages, and copies them to the / root / kernel directory to complete the source tracing of the container cluster OS offline installation package. Among them, the container cluster OS offline installation package can be in the form of an rpm package.

[0401] The computing device switches to the / root / kernel directory and executes the command yum -y localinstall. / *.rpm. If no exception occurs after execution, the production of the container cluster OS offline installation package is completed.

[0402] The computing device switches to the / root / kernel directory, executes a compression command, names it as the container cluster OS offline installation package, and transfers it to the local personal computer and marks it as the container cluster OS offline installation package to complete the local archiving of the container cluster OS offline installation package.

[0403] 3) Production of the Docker offline installation package.

[0404] Add the Docker image source on the computing device. The computing device executes to clear the image source cache, update the image source cache, create the directory / root / docker, and then executes the command: yum list docker-ce --showduplicates | sort–r, and then executes the command yum -y install docker-ce-20.10.9-3.el7 --downloadonly --downloaddir= / root / docker to complete the source tracing of the Docker offline installation package. Among them, the Docker offline installation package can be in the form of an rpm.

[0405] The computing device switches to the directory / root / docker and executes the command: yum -y localinstall. / *.rpm, then starts Docker. If no exception occurs, the production of the Docker offline installation package is completed.

[0406] The computing device switches to the directory / root / docker, executes the compression command, transfers it to the local personal computer, and marks it as the Docker offline installation package to complete the local archiving of the Docker offline installation package.

[0407] It should be noted that the method for producing the K8S offline installation package is the same as or similar to that of the Docker offline installation package, and the method for producing the K8S offline installation package will not be elaborated below.

[0408] 4) Production of the HA component offline installation package.

[0409] Create a directory / root / ha on the computing device and execute the command yumdownloader --resolve --destdir= / root / ha keepalived harpoxy to complete the source search for the HA component offline installation package.

[0410] The computing device switches to the / root / ha directory and executes the command yum -y localinstall. / *.rpm to start keepalived and harpoxy. If no exception occurs, the production of the HA component offline installation package is completed.

[0411] The computing device switches to the / root / ha directory, executes the compression command, transfers it to the local personal computer, and marks it as the HA component offline installation package to complete the local archiving of the HA component offline installation package.

[0412] 5) Production of the Harbor image offline installation package.

[0413] Download the installation package harbor-offline-installer-v2.5.3.tgz on the computing device, install docker and docker-compose. Create a directory / root / harbor on the computing device, copy the downloaded harbor installation package and docker-compose to the directory / root / harbor, then start docker, and then install harbor. After the installation is complete, the computing device exports and saves all images to the directory / root / harbor to complete the source search for the Harbor image offline installation package.

[0414] The computing device switches to the / root / harbor directory and executes the image import to complete the production of the Harbor image offline installation package.

[0415] The computing device switches to the / root / harbor directory, executes the compression command, transfers it to the local personal computer, and marks it as the Harbor image offline installation package to complete the local archiving of the Harbor image offline installation package.

[0416] It should be noted that the production methods of the Ingress offline installation package, the CEPH offline installation package, the NFS offline installation package, the log analysis system offline installation package, the monitoring and alerting system offline installation package, the disaster recovery component offline installation package, the microservice registration offline installation package, and the multi-cloud management platform offline installation package are the same as or similar to the production method of the Harbor image offline installation package. The production methods of the Ingress offline installation package, the CEPH offline installation package, the NFS offline installation package, the log analysis system offline installation package, the monitoring and alerting system offline installation package, the disaster recovery component offline installation package, the microservice registration offline installation package, the K8S dashboard (Kubernetes-dashboard) offline installation package, and the multi-cloud management platform offline installation package will not be elaborated below.

[0417] 6) Production of the database system offline installation package.

[0418] Configure the image source on the computing device and configure the mongodb image source for the database. The computing device changes the value of the parameter keepcache in the operating system configuration file: / etc / yum.conf from 0 to 1. The computing device downloads the mongodb database installation method as a binary installation package, uploads it to the specified networked server, then decompresses it, and then starts the database. If there is a prompt to install dependent packages during the startup process, use the yum method to install them. After the dependent packages are installed, start the database again until it starts normally, and the source of the database system offline installation package is completed in the / var / cache / yum directory. Among them, the database system offline installation package can be in rpm format.

[0419] The computing device creates a dependent package directory under the root partition, switches to the / var / cache / yum directory, and copies all rpm packages in the / var / cache / yum directory to the dependent package directory to complete the offline production of the dependent packages for the database system offline installation package.

[0420] The computing device executes a compression command on the dependency package directory containing the dependency packages, transfers it to the local personal computer, and marks it as the offline installation package of the database system to complete the archiving of the offline installation package of the database system.

[0421] 7) Production of the offline installation package of the database.

[0422] The computing device downloads the mongodb database binary file package to complete the source search for the offline installation package of the database. Optionally, the 64-bit, centos system, and tar-type mongodb database binary file package can be downloaded through the wget download method.

[0423] After the download of the mongodb database installation package is completed, the production of the offline installation package of the database is completed. The offline installation package of the database can be in binary form.

[0424] The computing device transfers the offline installation package of the database to the local personal computer and marks it as the offline installation package of the database to complete the local archiving of the offline installation package of the database.

[0425] 8) Production of the offline installation package of the database server monitoring system and the offline installation package of the database monitoring system.

[0426] The computing device uses the wget method to download the offline installation package of the database server monitoring system, uses the wget method to download the mirror of the offline installation package of the database monitoring system, and downloads the offline installation package of the database monitoring system client to complete the source search for the offline installation package of the database server monitoring system and the offline installation package of the database monitoring system.

[0427] The computing device switches to the root partition, creates a monitoring package collection directory, and copies the offline installation package of the database server monitoring system, the offline installation package of the database monitoring system, and the offline installation package of the database monitoring system client to the monitoring package collection directory to complete the production of the offline installation package of the database server monitoring system and the offline installation package of the database monitoring system.

[0428] The computing device switches to the monitoring package collection directory, executes the compression command, transfers the compressed package to the local personal computer, and marks it as the monitoring collection directory to complete the local archiving of the offline installation package of the database server monitoring system and the offline installation package of the database monitoring system.

[0429] Based on any of the above embodiments, before deploying the container cluster and the database cluster, an offline installation script can also be made. Next, the process of making the offline installation script will be described by way of example.

[0430] 1) Production of the mutual trust script.

[0431] The principle of the mutual trust script is as follows: First, install the dependent software, then transfer the public key from the source end to the target end, and generate the mutual trust script according to the input parameters in the control panel. After generating the mutual trust script, the mutual trust script can be executed on two verification devices to determine whether the goal of remotely logging in to the target device (the two verification devices include the target device) without entering the password of the target device can be achieved. If so, transfer the mutual trust script to the local personal computer and mark it as mutual trust to complete the production of the mutual trust script.

[0432] 2) Production of the offline installation script for the container cluster OS.

[0433] Create the offline source working directory / opt / centos_repo, move the directory of the RPM packages that have been decompressed and include server dependencies to the / opt / centos_repo directory, create the / etc / yum.repos.d / centos_bak directory, and move the mirror sources in the / etc / yum.repos.d / directory to the / etc / yum.repos.d / centos_bak directory. Create a custom mirror source file, specify the mirror source source address as / opt / centos_repo / Packages. Use the createrepo command to create a new YUM source, use the ansible automation tool to distribute the mirror source to each server node, and execute clearing the mirror source and updating the mirror source on each node to complete the production of the offline installation script for the container cluster OS.

[0434] 3) Production of the offline installation script for HA components.

[0435] The computing device executes YUM to install and deploy keepalived and haproxy, copies the updated keepliaved configuration file and haproxy configuration file, executes the keepliaved configuration file of the updated node, modifies the firewall VRRP multicast policy, and starts the keeplived and haproxy services to complete the production of the offline installation script for HA components.

[0436] 4) Production of the offline installation script for CEPH.

[0437] The computing device creates a common resource, creates an operator deployment, creates a Cluster Custom Resource Definition (CRD), and creates a cluster file cluster.yaml. After a preset duration (e.g., 200 seconds), it creates a CEPH tool file, creates a block storage object storage class file, creates a file storage file, creates a file storage class file, creates an object file, creates an object storage class file, creates an object storage PVC file, retains the object storage gateway service, and deploys the CEPH monitoring service to complete the production of the CEPH offline installation script.

[0438] It should be noted that the methods for creating the offline installation scripts of the log analysis system, the monitoring and alerting system, the microservice registration system, the disaster recovery component system, and the multi-cloud management platform are the same as or similar to the method for creating the CEPH offline installation script. The methods for creating the offline installation scripts of the log analysis system, the monitoring and alerting system, the microservice registration system, the disaster recovery component system, and the multi-cloud management platform will not be elaborated below.

[0439] 5) Production of the Harbor offline installation script.

[0440] Extract the Harbor image offline installation package, modify the value of "hostname" to the server address of the installation node, and turn off all the parameter items related to the https protocol. At the same time, install the docker service on the installation node, copy the downloaded docker-compose command to the / user / locol / sbin / directory, and grant it executable permission. Import the Harbor image offline installation package to the installation node and start the installation. After the installation is complete, start the service, and at this time, the production of the Harbor offline installation script is completed.

[0441] 6) Production of the database offline installation script.

[0442] The computing device logs in to the installation node of the database, switches to the database installation package directory, creates a database installation script file, extracts the database installation package, creates a database working directory, a data storage directory, a log directory, and a configuration file directory, modifies the database configuration file, and starts the database. Then copy this script to the root partition directory and mark it as the database offline installation script. At this time, the production of the database offline installation script is completed.

[0443] 7) Production of the database monitoring system offline installation script.

[0444] Create a database system monitoring script on the installation node of the database monitoring system. The implementation principle of the offline installation script of the database monitoring system is as follows: Switch to the database collection directory, create the working directory of the database monitoring server, unzip the database server installation package to the working directory of the database monitoring server, configure the configuration file of the data block monitoring system server, and start the service of the database monitoring server. Deploy the client collection service on the database working node, log in to the node where the database works, and perform the following operations: Import the database client collection image, add the database startup configuration file, start the database client image collection service, unzip the database server client collection installation package, and start the database node server client collection service. At this time, the production of the offline installation script of the database monitoring system is completed.

[0445] Based on any of the above embodiments, the container cluster and the database cluster deployed by the solution provided by the embodiments of the present application have many functions. The functions of the container cluster and the database cluster will be described below in conjunction with Figure 7 , and the functions of the container cluster and the database cluster will be described.

[0446] Figure 7 This is a schematic diagram of a container cluster and a database cluster provided by an embodiment of the present application. Please refer to Figure 7 , the container cluster has functions such as microservice registration and CEPH storage function. The container cluster may also include a database server monitoring system, a log analysis system, an HA component, a Kubernetes-dashboard, a multi-cloud management platform, and a disaster recovery component, etc.

[0447] The client can be used to interact with users and can access the HA component. The HA component can forward the services to be migrated to the cloud to the CEPH storage. Microservice registration can be used to manage and track the availability and location of microservice instances. The Kubernetes-dashboard can be used to manage and monitor the container cluster. The multi-cloud management platform can be used to provide a unified interface and tools to manage the resources of multiple cloud service providers. The disaster recovery component can be used to provide functions such as data backup, failover, and automatic recovery to minimize service interruption and data loss. The container image repository can be used to store and distribute the container image repository.

[0448] The database cluster can be any one of a flexible database, a complex database, and a relational database.

[0449] The log analysis system can be used to collect the logs of the database cluster and can send the logs of the database cluster to the database server monitoring system. The database server monitoring system can monitor the database cluster according to the logs of the database cluster.

[0450] Based on any of the above embodiments, taking the disaster recovery component Velero as an example below, the disaster recovery component can have functions such as regular backup, backup and recovery service functions, and inter-cluster migration functions. The usage methods of various functions are described below by way of example.

[0451] 1) Usage of the regular backup function

[0452] The regular backup function can be used to back up the cluster resources of the container cluster.

[0453] The working mode of the disaster recovery component is to back up the data in the container cluster to object storage to achieve high availability and persistence. The default backup retention time is 720 hours, and it can be downloaded and restored when needed.

[0454] For example, assume that the business namespace is "nginx-example", the name of the backup is "nginx-backups", and the regular backup time is once every 1 hour. The regular backup can be completed by executing "velero createschedule nginx-backups--schedule="0* / 1***"--include-namespaces nginx-example--default-volumes-to-restic-n velero".

[0455] Another example, assume that the backup starts at 1 am every day and the data is retained for 24 hours. The regular backup can be completed by executing "velerocreate schedule nginx-backups--schedule="0 1***"--ttl 24h--include-namespaces nginx-example--default-volumes-to-restic-n velero".

[0456] 2) Usage of the backup and recovery service function

[0457] The backup and recovery service function can be used to restore according to the cluster resources of the backed-up container cluster in case of resource loss.

[0458] Exemplarily, assume the business target service is: nginx-app. A backup can be created by executing the command "velero backup create nginx-backups --include-namespaces nginx-example --default-volumes-to-restic -n velero"; the backup location can be viewed by executing the command "velero backup-location get"; the backup files can be viewed by executing the command "kubectl get backups.velero.io -n velero"; the backup test application can be deleted by executing the command "kubectl delete –f with–pv.yaml"; the backup test application can be restored by executing the command "velero restore create --from-backup nginx-backup"; whether the service is normal after recovery can be viewed by executing the command "kubectl get po –n nginx-example"; and the backup can be deleted by executing the command "velero backup delete nginx-backup".

[0459] 3) Usage of the cross-cluster migration function

[0460] The cross-cluster migration function can be used to migrate cluster resources to other clusters or copy a production cluster to development and test clusters.

[0461] Exemplarily, assume the target files of cluster A are backed up and need to be transferred to cluster B. The disaster recovery components can be uninstalled in cluster A by executing the commands "kubectl delete namespace / velero clusterrolebinding / velerokubectl delete crds -l component=velero", the velero.sh file can be modified to re-specify the S3 address to point to the minio object storage of cluster B. The disaster recovery component server and client can be installed in cluster A, a backup can be made in cluster A by executing the command "velero restore create --from-backup nginx-backup", and the restoration can be performed in cluster B by executing the command "velero restore create --from-backup apisix-bacups".

[0462] Figure 8Schematic structural diagram of an offline deployment device provided by an embodiment of the present application. The offline deployment device is applied to a computing device. The offline deployment device 10 includes a receiving module 11, a determining module 12, and a deployment module 13. Among them,

[0463] The receiving module 11 is configured to receive a deployment request sent by a user device. The deployment request is used to request the deployment of a container cluster and a database cluster;

[0464] The determining module 12 is configured to determine a first target node for deploying the container cluster and a second target node for deploying the database cluster according to the deployment request;

[0465] The deployment module 13 is configured to offline deploy the container cluster on the first target node and offline deploy the database cluster on the second target node through an automated operation and maintenance tool in the computing device.

[0466] The offline deployment device provided in this embodiment can execute the method shown in any of the above method embodiments. The implementation principle and technical effects are similar, and will not be elaborated here in this embodiment.

[0467] In a possible implementation manner, the determining module 12 is specifically configured to,

[0468] Obtain a first parameter from the user device;

[0469] Determine a first mode of the container cluster according to the first parameter. The first mode is a high-availability mode, a non-high-availability mode, or a single-machine mode;

[0470] Determine the first target node according to the first mode.

[0471] In a possible implementation manner, the determining module 12 is specifically configured to,

[0472] Send a first field to be configured to the user device according to the first mode;

[0473] Receive a first field value corresponding to the first field to be configured sent by the user device;

[0474] Determine the first target node according to the first field value.

[0475] In a possible implementation manner,

[0476] The first field to be configured includes the address of the first target node;

[0477] Among them, the first target node includes: the master node of the container cluster, or, the first target node includes: the master node of the container cluster and the worker nodes of the container cluster.

[0478] In a possible implementation manner, the determining module 12 is specifically configured to,

[0479] Obtain a second parameter from the user device;

[0480] Determine a second mode of the database cluster according to the second parameter, where the second mode is a flexible database mode, a complex database mode, or a relational database mode;

[0481] Determine the second target node according to the second mode.

[0482] In a possible implementation manner, the determining module 12 is specifically configured to,

[0483] Send a second field to be configured to the user device according to the second mode;

[0484] Receive a second field value corresponding to the second field to be configured sent by the user device;

[0485] Determine the second target node according to the second field value.

[0486] In a possible implementation manner,

[0487] The second configuration field includes the address of the second target node;

[0488] Among them, the number of the second target nodes is multiple.

[0489] In a possible implementation manner, the deployment module 13 is specifically configured to,

[0490] Obtain an offline deployment installation package and an installation script;

[0491] Deploy the container cluster on the first target node and deploy the database cluster on the second target node according to the offline deployment installation package and the installation script.

[0492] In a possible implementation manner, the offline deployment installation package includes at least one of the following:

[0493] Offline installation package of the container cluster operating system;

[0494] Offline installation package of the container;

[0495] Offline installation package of the high-availability component;

[0496] Offline installation package of the container image repository image;

[0497] Offline installation package of container orchestration engine;

[0498] Offline installation package of container interface;

[0499] Offline installation package of distributed storage system;

[0500] Offline installation package of distributed file system;

[0501] Offline installation package of log analysis system;

[0502] Offline installation package of monitoring and alarming system;

[0503] Offline installation package of disaster recovery component;

[0504] Offline installation package of microservice registration;

[0505] Offline installation package of multi-cloud management platform;

[0506] Offline installation package of database system;

[0507] Offline installation package of database;

[0508] Offline installation package of database server monitoring system; or,

[0509] Offline installation package of database monitoring system.

[0510] The offline deployment device provided in this embodiment can execute the method shown in any of the above method embodiments, and its implementation principle and technical effects are similar, which will not be elaborated here in this embodiment.

[0511] Figure 9 It is a schematic structural diagram of a computing device provided in an embodiment of the present application. As Figure 9 shown, the computing device 20 may include: a processor 21 and a memory 22. Among them, the processor 21 and the memory 22 can communicate; exemplarily, the processor 21 and the memory 22 communicate through a communication bus 23. The memory 22 is used to store computer execution instructions, and the processor 21 is used to call the computer execution instructions in the memory to execute the offline deployment method shown in any of the above method embodiments.

[0512] Optionally, the computing device 20 may further include a communication interface, and the communication interface may include a transmitter and / or a receiver.

[0513] The computing device 20 may be the computing device shown in any of the above method embodiments and may execute the offline deployment method shown in any of the above method embodiments.

[0514] Optionally, the above-mentioned processor may be a CPU, or may also be a GPU, a Baseboard Management Controller (BMC), other general-purpose processors, a Digital Signal Processor (DSP), or an Application Specific Integrated Circuit (ASIC), etc. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0515] An embodiment of the present application provides a computer-readable storage medium, on which computer-executable instructions are stored; the computer-executable instructions are used to implement the offline deployment method as described in any of the above embodiments.

[0516] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed, the computer is enabled to execute the above-mentioned offline deployment method.

[0517] All or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program may be stored in a readable memory. When the program is executed, it executes the steps including the above method embodiments; and the foregoing memory (storage medium) includes: read-only memory (abbreviation: ROM), RAM, flash memory, hard disk, solid state drive, magnetic tape, floppy disk, optical disc, and any combination thereof.

[0518] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processing machine, or other programmable terminal devices to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable terminal devices generate a device for implementing the specified functions in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or a device for implementing the specified functions in multiple blocks.

[0519] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable terminal device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufacture including an instruction device that implements the functions specified in one or more processes and / or blocks Figure 1 in one or more processes and / or blocks Figure 1 specified in one or more blocks.

[0520] These computer program instructions can also be loaded onto a computer or other programmable terminal device, such that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes and / or blocks Figure 1 in one or more processes and / or blocks Figure 1 specified in one or more blocks.

[0521] Obviously, those skilled in the art can make various modifications and variations to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalent technologies, the embodiments of the present application are also intended to include these modifications and variations.

[0522] In the embodiments of the present application, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device including a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the presence of additional identical elements in the process, method, article or device including such element. The term "or" and its variants may refer to "and / or". In the embodiments of the present application, terms such as "first", "second", etc. are used to distinguish similar objects and do not necessarily have to be used to describe a specific order or sequence. In the embodiments of the present application, "a plurality of" means two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0523] Other embodiments of the present application will be readily contemplated by those skilled in the art after considering the specification and the invention disclosed in practice. The embodiments of the present application are intended to cover any variations, uses, or adaptations of the embodiments of the present application, which follow the general principles of the embodiments of the present application and include the common general knowledge or conventional technical means in the technical field not disclosed in the embodiments of the present application.

Claims

1. An offline deployment method, characterized in that: Applied to a computing device, the method comprises: Receive a deployment request sent by a user device, where the deployment request is used to request deployment of a container cluster and a database cluster; Determine, according to the deployment request, a first target node for deploying a container cluster and a second target node for deploying a database cluster; The container cluster is deployed offline at the first target node, and the database cluster is deployed offline at the second target node, through an automated operation and maintenance tool in the computing device.

2. The method according to claim 1, characterized in that The determining of a first target node for deploying the container cluster includes: Acquire a first parameter from the user equipment; Determine a first mode of the container cluster according to the first parameter, where the first mode is a high availability mode, a non-high availability mode, or a stand-alone mode; According to the first mode, the first target node is determined.

3. The method according to claim 2, characterized in that The determining the first target node according to the first mode includes: According to the first mode, sending a first to-be-configured field to the user equipment; receiving a first field value corresponding to the first to-be-configured field and sent by the user equipment; The first target node is determined according to the first field value.

4. The method according to claim 3, characterized in that The first to-be-configured field includes an address of the first target node; The first target node includes: a master node of the container cluster, or the first target node includes: a master node of the container cluster and a working node of the container cluster.

5. The method according to any one of claims 1 to 4, characterized in that: The determining of the second target node for deploying the database cluster includes: Acquire a second parameter from the user equipment; Determining a second mode of the database cluster according to the second parameter, the second mode being a flexible database mode, a complex database mode, or a relational database mode; According to the second mode, the second target node is determined.

6. The method according to claim 5, characterized in that The determining the second target node according to the second mode includes: According to the second mode, sending a second to-be-configured field to the user equipment; receiving a second field value corresponding to the second to-be-configured field and sent by a user equipment; A second target node is determined according to the second field value.

7. The method according to claim 6, characterized in that The second configuration field includes an address of the second target node; There are multiple second target nodes.

8. The method according to any one of claims 1 to 7, characterized in that: The offline deployment of the container cluster on the first target node by using the automated operation and maintenance tool, and the offline deployment of the database cluster on the second target node, includes: Obtain the offline deployment installation package and installation script; According to the offline deployment installation package and the installation script, the container cluster is deployed on the first target node, and the database cluster is deployed on the second target node.

9. The method according to claim 8, characterized in that The offline deployment installation package includes at least one of the following: Container cluster operating system offline installation package; Container offline installation package; Offline installation package for high-availability components; Container image repository image offline installation package; Offline installation package of container orchestration engine; Container interface offline installation package; Distributed storage system offline installation package; Distributed file system offline installation package; Offline installation package of log analysis system; Offline installation package of monitoring and alarm system; Offline installation package of disaster recovery components; Microservice registration offline installation package; Multi-cloud management platform offline installation package; Database system offline installation package; Database offline installation package; Database server monitoring system offline installation package; or, Offline installation package of the database monitoring system.

10. A computing device, characterized in that: include: Memory and processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 9.

Images