System deployment method and computing device

Abstract

The embodiment of the invention provides a system deployment method and computing equipment, relates to the technical field of cloud native, and can complete deployment of a cloud native system in an offline environment. The method comprises the following steps: sending a software related package set to a target working node of a cluster through a control node of the cluster; the software related package set comprises software related packages required for deploying the cloud native system. And then, sending a first instruction to the target working node to instruct the target working node to store the software related package set in a first preset working directory of the target working node. And then, sending a second instruction to the target working node to instruct the target working node to create a first offline mirror image source file based on the software related package set under the first preset working directory. Then, the cloud native system can be deployed on the target working node based on the first offline mirror image source file, and the first offline mirror image source file is used for representing a source of a software related package needed for installing the cloud native system.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of cloud native technology, and in particular to a system deployment method and computing device. Background Art

[0002] Cloud-native systems leverage containerization technology to encapsulate applications and their dependencies into independent containers, enabling applications to better adapt to changing business needs and operating environments. Currently, when developers deploy cloud-native systems, they typically download the installation package from the internet. They then use the installation package to complete the deployment of the cloud-native system.

[0003] However, deploying a cloud-native system using the above solution places high demands on the network environment. An unstable network environment may cause the cloud-native system installation to fail. Summary of the Invention

[0004] The present application provides a system deployment method and computing device that can complete the deployment of cloud native systems in an offline environment.

[0005] In the first aspect, the present application provides a system deployment method, which is applied to the control node of a cluster, and the cluster also includes working nodes. A set of software-related packages can be sent to a target working node, which is any working node, and the set of software-related packages includes software-related packages required for deploying a cloud-native system. Afterwards, a first instruction can be sent to the target working node, and the first instruction is used to instruct the target working node to store the set of software-related packages in a first preset working directory of the target working node. Afterwards, a second instruction can be sent to the target working node, and the second instruction is used to instruct the target working node to create a first offline mirror source file based on the set of software-related packages in the first preset working directory. Then, the cloud-native system can be deployed on the target working node based on the first offline mirror source file, and the first offline mirror source file is used to indicate the source of the software-related packages required to install the cloud-native system.

[0006] Based on the above technical solution, the control node can distribute a set of software-related packages to the target working node, and the set of software-related packages includes the software-related packages required for deploying the cloud native system. Afterwards, the control node controls the target working node to store the set of software-related packages in the preset working directory of the target working node, and creates an offline mirror source file based on the set of software-related packages in the preset working directory. The offline mirror source file is used to specify the source of the software-related packages required for the target working node to install the cloud native system. In this way, the target working node can complete the creation of the offline mirror source file in an environment without a network. Then, the control node can control the target working node to install the cloud native system. Compared with conventional technology, in this application, since the control node stores a set of software-related packages, there is no need to download the software packages related to the cloud native system through the network, so that the control node can complete the deployment of the cloud native system in an offline environment. In addition, in this application, there is no need for developers to manually deploy the cloud native system. The control node can complete the deployment of the cloud native system in the cluster, thereby improving the efficiency of system deployment.

[0007] In combination with the first aspect, in a possible implementation, the method may further include: reading a set of software-related packages from a storage device, and writing the set of software-related packages into a local storage space of the control node.

[0008] In conjunction with the first aspect, in another possible implementation, the method may further include: sending a metadata creation tool installation package to a target work node. Thereafter, sending a third instruction to the target work node, the third instruction instructing the target work node to install the metadata creation tool. The second instruction instructs the target work node to create the first offline image source file by running the metadata creation tool.

[0009] In conjunction with the first aspect, in another possible implementation, a package manager is configured on the target work node. Deploying a cloud native system on the target work node based on a first offline image source file includes removing historical image source files from the package manager and clearing cached data of the historical image source files. The cloud native system is installed on the target work node based on the first offline image source file via the package manager.

[0010] In conjunction with the first aspect, in another possible implementation, deploying a cloud-native system includes multiple deployment tasks. Installing the cloud-native system on a target work node based on a first offline image source file using a package manager includes parsing a pre-set task file, the task file including multiple deployment tasks. Each deployment task is executed on the target work node using the package manager.

[0011] In conjunction with the first aspect, in another possible implementation, the method may further include generating a target key pair, the target key pair including a public key and a private key. Establishing a connection with a target work node and sending the public key to the target work node, where the public key is used by the target work node to verify devices accessing the target work node, and the private key is used by the control node to access the target work node.

[0012] In combination with the first aspect, in another possible implementation, the cloud native system includes a client of the cluster backup software, and the client of the cluster backup software is used to send preset instructions to the server of the cluster backup software in the cluster, and the preset instructions are used to instruct the backup or recovery of target data; the target data is the data in the target microservice, target namespace, or target service.

[0013] In combination with the first aspect, in another possible implementation, the cloud native system includes: data storage software, the data storage software is used to join the target working node to the data storage cluster; the data storage cluster is used to store target data.

[0014] In conjunction with the first aspect, in another possible implementation, the method may further include: storing the set of software-related packages in a second preset working directory of the control node; creating a second offline image source file based on the set of software-related packages in the second preset working directory; and installing the cloud native system on the control node based on the second offline image source file.

[0015] In the second aspect, the present application provides a system deployment method, which is applied to a target working node of a cluster, and the cluster includes a control node. In this method, a set of software-related packages sent by the control node can be received, and the set of software-related packages includes software-related packages required for deploying a cloud-native system. Afterwards, a first instruction sent by the control node is received and responded to, and the set of software-related packages is stored in a first preset working directory of the target working node. Then, a second instruction sent by the control node is received and responded to, and a first offline image source file is created based on the set of software-related packages in the first preset working directory. Then, the cloud-native system is deployed based on the first offline image source file, and the first offline image source file is used to represent the source of the software-related packages required to install the cloud-native system.

[0016] In conjunction with the first aspect, in one possible implementation, the method further includes: receiving an installation package for a metadata creation tool from a control node. Receiving and, in response to a third instruction from the control node, installing the metadata creation tool. The second instruction instructs the target work node to create a first offline image source file by running the metadata creation tool. In conjunction with the first aspect, in another possible implementation, establishing a connection with the control node and receiving a public key from the control node, the public key being used by the target work node to verify devices accessing the target work node.

[0017] In a third aspect, the present application provides a computing device comprising: a memory and one or more processors, wherein the memory is coupled to the processors; the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the one or more processors, the computing device executes the method described in the first aspect or the second aspect and any possible implementation thereof.

[0018] In a fourth aspect, the present application provides a chip system, which is applied to a computing device. The chip system includes one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via a circuit. The interface circuits are configured to receive a signal from a memory of the computing device and send the signal to the processor, the signal including computer instructions stored in the memory. When the processor executes the computer instructions, the computing device performs the method described in the first aspect or the second aspect, and any possible implementation thereof.

[0019] In a fifth aspect, the present application provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on a computing device, the computing device executes the method described in the first aspect or the second aspect and any possible implementation thereof.

[0020] In a sixth aspect, the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method as described in the first aspect or the second aspect and any possible implementation thereof.

[0021] It can be understood that the beneficial effects that can be achieved by the system deployment method described in the second aspect and any possible implementation thereof, the computing device described in the third aspect and any possible implementation thereof, the chip system described in the fourth aspect, the computer-readable storage medium described in the fifth aspect, and the computer program product described in the sixth aspect can be referred to as the beneficial effects in the first aspect and any possible implementation thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 A flow chart of a system deployment method provided in an embodiment of the present application;

[0023] Figure 2 A flowchart of another system deployment method provided in an embodiment of the present application;

[0024] Figure 3 A flowchart of another system deployment method provided in an embodiment of the present application;

[0025] Figure 4 A flowchart of another system deployment method provided in an embodiment of the present application;

[0026] Figure 5 A flowchart of another system deployment method provided in an embodiment of the present application;

[0027] Figure 6 A schematic diagram of the composition of a business processing system architecture provided in an embodiment of the present application;

[0028] Figure 7 A schematic diagram of another business processing system architecture provided in an embodiment of the present application;

[0029] Figure 8 A schematic diagram of the composition of a system deployment device provided in an embodiment of the present application;

[0030] Figure 9 A schematic diagram of another system deployment device provided in an embodiment of the present application;

[0031] Figure 10 A schematic diagram of the structural composition of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0033] In this application, the character " / " generally indicates that the preceding and following objects are in an "or" relationship. For example, A / B can be understood as A or B.

[0034] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature identified as "first" or "second" may explicitly or implicitly include one or more of such features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0035] Furthermore, the terms "including," "having," and any variations thereof, as used in the description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or modules is not limited to the listed steps or modules, but may optionally include other steps or modules not listed, or may optionally include other steps or modules inherent to the process, method, product, or apparatus.

[0036] Additionally, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present concepts in a concrete manner.

[0037] In order to facilitate understanding of the technical solution of the present application, before introducing the system deployment method of the embodiment of the present application in detail, the professional terms mentioned in the embodiment of the present application are first introduced.

[0038] 1. A cloud-native system is a system architecture that leverages the advantages of cloud computing to build and run applications. Cloud-native systems feature containerization, microservices architecture, service mesh, and automated operations and maintenance. They offer advantages such as high agility, strong scalability, high resource utilization, and excellent reliability. Cloud-native systems can be applied to a variety of scenarios, including internet applications, enterprise applications, big data, and artificial intelligence applications.

[0039] The embodiments of the present application provide a system deployment method that can be applied to scenarios where cloud native systems need to be deployed on computing devices. For example, a cloud native system can be deployed in a cluster to ensure that the business cluster can handle related businesses. For another example, since the business cluster handles a large number of businesses, if a business cluster fails, it will cause business interruption. In order to avoid business interruption caused by business cluster failure, a disaster recovery cluster can be deployed, and the disaster recovery cluster also needs to deploy a cloud native system.

[0040] The system deployment method provided in the embodiment of the present application can be applied to the control node of the cluster. In this method, the control node can distribute a set of software-related packages to the target working node, and the set of software-related packages includes the software-related packages required for deploying the cloud native system. Afterwards, the control node controls the target working node to store the set of software-related packages in the preset working directory of the target working node, and creates an offline mirror source file based on the set of software-related packages in the preset working directory. The offline mirror source file is used to specify the source of the software-related packages required for the target working node to install the cloud native system. Then, the control node can control the target working node to install the cloud native system. Compared with conventional technology, in this application, since the control node stores a set of software-related packages, there is no need to download the software packages related to the cloud native system through the network, so that the control node can complete the deployment of the cloud native system in an offline environment. In addition, in this application, there is no need for developers to manually deploy the cloud native system. The deployment of the cloud native system in the cluster can be completed by the control node, thereby improving the efficiency of system deployment.

[0041] In an embodiment of the present application, before the control node controls the target working node to install the cloud native system, the control node may first obtain a set of software-related packages. The control node may read the set of software-related packages from a storage device and write the set of software-related packages to the local storage space of the control node.

[0042] The software-related package set includes the software-related packages required for deploying a cloud-native system. The software-related packages may include at least one of the following: an image, a dependency package, and an installation package.

[0043] It should be understood that the embodiments of the present application do not limit the storage device. For example, the storage device may be a mobile storage device, such as a mobile hard disk or a USB flash drive (such as a networkable server downloading a set of software-related packages via a network and then copying the set of software-related packages to a USB flash drive). For another example, the storage device may be a terminal, such as a mobile phone or a laptop computer. For another example, the storage device may be a server, and the server and the control node are in the same local area network, and the server shares the set of software-related packages with the control node via the local area network.

[0044] In other words, the control node does not need to download software packages from the network, but instead obtains the software package set from the storage device. This allows the control node to obtain the software package set and complete the deployment of the cloud native system even if it is not connected to the network.

[0045] In an embodiment of the present application, a set of software-related packages is downloaded from a storage device via a network. The set of software-related packages may include: software-related packages of multiple software to be deployed. The multiple software to be deployed may include: automated operation and maintenance software, operating system software, containerization software, and container orchestration software.

[0046] Automated O&M tools integrate multiple O&M tools, enabling system configuration, program deployment, and command execution. These tools can execute multiple tasks using script files, including software installation and system configuration. A script file is a data-serialized file that defines the tasks to be executed and their order.

[0047] Operating system software is used to upgrade the server's operating system to ensure better performance of the server.

[0048] Containerization software is used to containerize applications. A container is a lightweight, portable, independent runtime environment that contains the application and all its dependencies, such as code, runtime environment, system tools, and system libraries. Containers are isolated from each other and run on the same operating system, enabling efficient sharing of system resources.

[0049] Container orchestration software is used to manage containerized applications across multiple nodes in a cluster. Container orchestration software can provide functions such as application deployment, updating, and maintenance.

[0050] The following uses a storage device as an example of an internet-connected server to describe a method for the storage device to obtain a set of software-related packages via network downloads.

[0051] For example, a cloud image source storing software packages for various software components of a community enterprise operating system can be configured on an internet-connected server, along with an additional software package image source. This allows the server to obtain software packages for various software components of the community enterprise operating system, as well as additional software packages. The server can then create a folder for the automated operation and maintenance software on the root partition. The internet-connected server can then execute a download command. The internet-connected server can then obtain the installation package and dependency packages for the automated operation and maintenance software, namely, the software packages for the automated operation and maintenance software.

[0052] It should be understood that add-on packages are projects that provide additional software packages for the system. Software packages not available in the cloud image repository can be obtained from the add-on package mirror repository. After configuring the add-on package mirror repository, the server can access and download these additional packages, expanding the range of software that can be installed on the server.

[0053] For another example, a kernel upgrade package can be downloaded from a download URL on an internet-connected server. Then, a first directory is created in the root partition, and a download command is executed to store the downloaded software package of the software package management tool in the first directory. Then, the operating system configuration file can be modified in the first directory, and the value of the preset parameter can be changed from 0 to 1. By changing the value of the preset parameter, the internet-connected server can retain the downloaded software package. Then, an installation command can be executed, which is used to upgrade the operating system locally through the kernel upgrade package. In addition, during the upgrade process, the internet-connected server can download the dependent packages of the operating system from the network and save them to the first directory. That is, the software-related packages of the operating system software include: the kernel package and the dependent packages of the operating system.

[0054] For another example, a containerized software image source can be added to an internet-connected server. The server can then clear the containerized software image source cache and then update the containerized software image source cache with the containerized software image source. The server then creates a second directory and executes a search command to locate software packages related to the containerized software. The server can then execute a download command to download the containerized software to the second directory.

[0055] For example, you can download the installation package for container orchestration software. You can then install the container orchestration service on an internet-connected server and start the automated operation and maintenance service. The automated operation and maintenance service then pulls the server image of the container orchestration software and exports it as a compressed image package to complete the generation of the server image. The software-related packages for the container orchestration software include the installation package and the server image.

[0056] It should be understood that downloading the software packages of the automated operation and maintenance software, the operating system software, and the containerized software to the root directory facilitates subsequent packaging and transmission of the software packages. Furthermore, by downloading the software packages of the automated operation and maintenance software, the operating system software, and the containerized software, the cloud native system can be installed in the cluster, enabling the cluster to handle related services.

[0057] Optionally, the software to be deployed in the cloud native system may also include: cluster backup software and data storage software.

[0058] Cluster backup software is a cluster backup and migration tool that can upload backups of container orchestration system resources and data from the original cluster to the data storage software. In the event of a disaster or when data migration is required, the disaster recovery cluster can use the cluster backup software to pull the corresponding backup data from the data storage software to restore cluster resources.

[0059] Data storage software can provide distributed object storage services and store data.

[0060] For example, a server with internet access can download the cluster backup software installation package from a website. Furthermore, the server image of the cluster backup software can be pulled through automated operations and maintenance services and exported as a compressed image package. Specifically, the software-related packages of the cluster backup software include the cluster backup software installation package and the cluster backup software server image.

[0061] For another example, the networkable server may execute a command to download the data storage software to download a software-related package of the data storage software.

[0062] It is understandable that when the cloud-native system includes cluster backup software and data storage software, the cloud-native system can complete data backup and recovery, thereby improving the stability of the system.

[0063] After the storage device downloads the software-related packages of each software to be deployed through the network, the storage device may create a software-related package set.

[0064] For example, after the networkable server has downloaded all the software packages to be deployed, a folder a can be created. Then, the software packages in the automated operation and maintenance software folder (which stores the software packages for the automated operation and maintenance software), the folders in the first directory (which store the software packages for the operating system software), and the folders in the second directory (which store the software packages for the containerized software) are copied to folder a. Afterwards, a search command is used to search for all software packages in the first directory (which stores software packages downloaded from the network, such as software packages for data storage software and cluster backup software), and the found software packages are copied to folder a. Folder a is then compressed to obtain a collection of software packages.

[0065] The above is an introduction to the process of creating a set of software related packages. The following is an introduction to the system deployment method provided in the embodiment of the present application.

[0066] In some embodiments, when deploying a cloud-native system, a control node may obtain system configuration information, including identifiers of nodes in the cluster. The control node may then generate a configuration manifest file for the cloud-native system based on the system configuration information.

[0067] Optionally, the system configuration information may also include configuration information of data storage software.

[0068] For example, the identifier of each node in the cluster may be an Internet Protocol (IP) address. The configuration information of the data storage software may include: an account number and password for logging into the data storage software.

[0069] In one possible implementation, the control node stores system configuration information. The control node may obtain an initial manifest file. Subsequently, when the control node detects a prompt to enter parameters, the control node may input the stored system configuration information to generate a configuration manifest file.

[0070] Optionally, the system configuration information may be input to the control node by a user installing the cloud native system. When the control node detects a prompt to input parameters, the control node may input the system configuration information in response to the user inputting the system configuration information to generate a configuration manifest file.

[0071] As you can see, generating a configuration manifest file for a cloud-native system facilitates the control node to distribute the software to be deployed according to the identifiers of each node in the cluster, thereby ensuring that the cloud-native system can be deployed. Furthermore, the data storage cluster can be deployed using the data storage software configuration information.

[0072] After introducing the process of the control node obtaining the software-related package set and generating the configuration manifest file, the following describes the process of the control node deploying the cloud native system based on the software-related package set.

[0073] In some embodiments, before the control node deploys the cloud native system based on the set of software-related packages, the control node may establish a mutual trust connection with the target working node.

[0074] In one possible implementation, the control node can generate a target key pair consisting of a public key and a private key. The control node can then establish a connection with a target worker node and send the public key to the target worker node. The public key is used by the target worker node to verify access to the device, while the private key is used by the control node to access the target worker node.

[0075] In an embodiment of the present application, when a control node sends a public key to a target working node, the control node may generate a connection prompt message that instructs the device establishing a connection with the working node to authenticate. Upon detecting the connection prompt message, the control node obtains connection configuration information for the target working node, including connection instructions and an access password. The connection instructions are used to confirm the establishment of a connection with the target working node. The control node may then establish a connection with the target working node based on the connection configuration information.

[0076] Exemplarily, the configuration list file includes the IP address of the target working node. Afterwards, the control node generates a key pair (i.e., the target key pair) using a key generation tool and copies the generated public key to the target working node. During the copying process, the connection prompt message may include a prompt message of "Confirm whether to connect" and a prompt message of "Please enter the password." When the control node issues a prompt message of "Confirm whether to connect," the control node may enter "Yes" (i.e., a connection instruction). When the control node issues a prompt message of "Please enter the password," the control node may enter the access password of the target working node.

[0077] In this way, the control node can establish a mutually trusted connection by generating a target key pair and sending the public key to the target working node. When the control node subsequently accesses the target working node, the target working node can verify the control node using the public key, thus simplifying the subsequent access process.

[0078] In an embodiment of the present application, after the control node establishes a mutual trust connection with the target working node, the control node can install the cloud native system based on a set of software-related packages.

[0079] The present application embodiment provides a system deployment method, such as Figure 1 As shown, the system deployment method may include:

[0080] S101: The control node sends a set of software-related packages to a target working node.

[0081] The target working node is any working node. The software-related package set includes one or more software-related packages of the software to be deployed.

[0082] In a possible implementation, the software-related package set may include all software-related packages of the software to be deployed. The control node may send all software-related packages of the software to be deployed to the target working node.

[0083] In another possible implementation, the control node stores the software to be deployed required by each target work node. Based on the software to be deployed required by each target work node, the control node may send a locally stored set of software-related packages to the target work node. The set of software-related packages sent to each target work node includes the software-related packages of the software to be deployed required by the target work node.

[0084] For example, if worker node a requires cluster backup software, the set of software-related packages distributed to worker node a includes the software-related packages of the cluster backup software. The control node can send the software-related packages of the cluster backup software to worker node a through an automated operation and maintenance tool.

[0085] It should be understood that the automated operation and maintenance tool can communicate with the target work node using the secure shell protocol (SSH). When the control node runs the automated operation and maintenance tool and the target work node has the SSH service enabled, the control node can send the software-related packages to the target work node.

[0086] S102: The target working node receives a set of software-related packages sent by the control node.

[0087] In a possible implementation, the target working node may store the set of software-related packages in a default storage directory of the target working node. The default storage directory is used to store data received from other devices.

[0088] S103: The control node sends a first instruction to the target working node.

[0089] The first instruction is used to instruct the target working node to store the software-related package set in a first preset working directory of the target working node.

[0090] Exemplarily, the control node may issue the first instruction through an automated operation and maintenance tool.

[0091] S104: The target working node receives and responds to the first instruction sent by the control node, and stores the software-related package set in a first preset working directory of the target working node.

[0092] The first instruction includes a first preset working directory.

[0093] In a possible implementation, after receiving the first instruction, the target working node may copy the software-related package set to a first preset working directory.

[0094] In another possible implementation, the software-related package set is a compressed package. After receiving the first instruction, the target working node may decompress the compressed package of the software-related package set to a first preset working directory.

[0095] S105. The control node sends a second instruction to the target working node.

[0096] The second instruction is used to instruct the target working node to create a first offline image source file based on the set of software-related packages in the first preset working directory. The first offline image source file is used to represent the source of the software-related packages required for installing the cloud native system.

[0097] S106: The target working node receives and responds to the second instruction sent by the control node, and creates a first offline image source file based on the software-related package set in the first preset working directory.

[0098] The first image source file includes metadata of a set of software-related packages, and the metadata includes: a first preset working directory, description information of the software-related packages, version information of the software-related packages, and dependency relationships of the software-related packages.

[0099] In a possible implementation, the control node may create an initial image source file in a first preset working directory. Thereafter, the control node may configure the first preset working directory in the initial image source file to obtain a first offline image source file.

[0100] S107: The control node controls deployment of the cloud native system on the target working node based on the first offline image source file.

[0101] In a possible implementation, a package manager is configured on the target working node, and the control node can remove the historical image source files of the package manager and clear the cached data of the historical image source files.

[0102] For example, a directory a may be created, and all historical image source files stored in directory b may be moved to directory a. Furthermore, cached data of the historical image source files may be cleared.

[0103] The control node then installs the cloud native system on the target worker node based on the first offline image source file using a package manager, which is used to install, uninstall, update, and manage software packages on the operating system.

[0104] For example, the control node can execute an installation command using a software package management tool to install the cloud-native system on the target worker node. For example, the address of the first offline image source file can be specified in the software package management tool. The software package management tool can then locate the software-related package set on the target worker node based on the first offline image source file specified in the configuration file and install the cloud-native system.

[0105] It is understandable that by removing the historical image source files of the package manager and clearing the cached data of the historical image source files, conflicts between the historical image source files and the offline image source files can be avoided, thereby increasing the probability of successfully deploying the cloud native system.

[0106] Based on the above technical solution, the control node can distribute a set of software-related packages to the target working node, and the set of software-related packages includes the software-related packages required for deploying the cloud native system. Afterwards, the control node controls the target working node to store the set of software-related packages in the preset working directory of the target working node, and creates an offline mirror source file based on the set of software-related packages in the preset working directory. The offline mirror source file is used to specify the source of the software-related packages required for the target working node to install the cloud native system. In this way, the target working node can complete the creation of the offline mirror source file in an environment without a network. Then, the control node can control the target working node to install the cloud native system. Compared with conventional technology, in this application, since the control node stores a set of software-related packages, there is no need to download the software packages related to the cloud native system through the network, so that the control node can complete the deployment of the cloud native system in an offline environment. In addition, in this application, there is no need for developers to manually deploy the cloud native system. The control node can complete the deployment of the cloud native system in the cluster, thereby improving the efficiency of system deployment.

[0107] In some embodiments, an offline mirror source file may be created by a metadata creation tool.

[0108] The present application embodiment provides a system deployment method, such as Figure 2 As shown, before S105, the system deployment method may include:

[0109] S201: The control node sends the installation package of the metadata creation tool to the target working node.

[0110] It should be understood that metadata creation tools are used to generate metadata for image source files. This metadata contains various information about software packages, such as name, version, dependencies, and description. Through this metadata, package management tools can understand the software packages available in the image source file and their related information, thereby enabling operations such as searching, installing, and updating software packages.

[0111] S202: The target working node receives the installation package of the metadata creation tool sent by the control node.

[0112] S203: The control node sends a third instruction to the target working node.

[0113] The third instruction is used to instruct the target working node to install the metadata creation tool.

[0114] S204: The target working node receives and responds to the third instruction, and installs a metadata creation tool.

[0115] In an embodiment of the present application, the second instruction is specifically used to instruct the target working node to create a first offline image source file by running a metadata creation tool.

[0116] In a possible implementation, the target working node may create the first offline mirror source file by running a metadata creation tool in response to the second instruction.

[0117] Exemplarily, a first offline image source file is created by using a metadata creation tool, a source address of the first image source file is specified, that is, a first preset working directory, and metadata is added to the first image source file.

[0118] Based on the above technical solution, after sending the metadata creation tool installation package to the target work node, a third instruction is sent to the target work node to cause the target work node to create the first offline image source file by running the metadata creation tool. This ensures that the target work node completes the installation of the offline image source file and then deploys the cloud native system.

[0119] In some embodiments, deploying a cloud-native system includes multiple deployment tasks. The control node, using a package manager, installs the cloud-native system on a target worker node based on a first offline image source file. This may include: the control node parsing a pre-configured task file, the task file including multiple deployment tasks. Thereafter, the control node executes each deployment task on the target worker node using the package manager.

[0120] Exemplarily, the task file may be a script file that defines the tasks to be executed and their order.

[0121] In one possible implementation, the control node can parse a pre-configured task file and create multiple module roles, each corresponding to a deployment task. The control node can then call the multiple module roles and execute each deployment task on the target worker node through the package manager.

[0122] Exemplarily, the multiple module roles may include at least one of the following: a module role for deploying an offline image source, a module role for system initialization, a module role for installing a time management server for implementing a network time protocol, a module role for installing a time management client that interacts with a time management server, a module role for deploying containerized software, a module role for importing images, a module role for deploying lifecycle components, a module role for deploying a high-availability cluster control node, a module role for deploying a control node, a module role for deploying a working node, a module role for deploying data storage software, a module role for node labeling, a module role for copying files of automated operation and maintenance software, a module role for transmitting files of automated operation and maintenance software, and a module role for deploying a cluster backup service.

[0123] For example, a module role that deploys an offline image source can be used to deploy an offline image source file on a target worker node. A module role that deploys containerized software can be used to deploy containerized software on a target worker node.

[0124] In a possible implementation, a deployment task corresponds to at least one target working node. The control node can call the module role to execute the deployment task on the corresponding target working node through the package manager.

[0125] In a possible implementation, the task file further includes a preset execution order of the plurality of deployment tasks, and the control node executes each deployment task according to the preset execution order in the task file.

[0126] Exemplarily, the preset execution order can be determined by the order of multiple module roles in the execution file. For example, the preset execution order can be: creating an offline image source file - establishing mutual trust with the target working node - generating a configuration manifest file - initializing the system installation - installing the containerized service - importing the image - installing the container orchestration software - installing the cluster backup service - installing the data storage cluster.

[0127] As you can understand, deploying a cloud-native system involves multiple deployment tasks. The control node parses pre-configured task files and executes each deployment task on the target worker nodes through the package manager. This automates the deployment of the cloud-native system and improves deployment efficiency.

[0128] The present application embodiment provides a system deployment method, such as Figure 3 As shown, the system deployment method may include:

[0129] S301: The control node sends a set of software-related packages to a target working node.

[0130] S302: The control node sends a first instruction to the target working node.

[0131] S303: The control node sends a second instruction to the target working node.

[0132] S304. The control node deploys the cloud native system on the target working node based on the first offline image source file.

[0133] It should be noted that, for the specific introduction of S301-S304, reference may be made to the introduction of S101-S107 in the above embodiment, which will not be repeated here.

[0134] The present application embodiment provides a system deployment method, such as Figure 4 As shown, the system deployment method may include:

[0135] S401: A target working node receives a set of software-related packages sent by a control node.

[0136] S402: The target working node receives and responds to the first instruction sent by the control node, and stores the software-related package set in a first preset working directory of the target working node.

[0137] S403: The target working node receives and responds to the second instruction sent by the control node, and creates a first offline image source file based on the software-related package set in the first preset working directory.

[0138] S404: The target working node deploys the cloud native system based on the first offline image source file.

[0139] In one possible implementation, the control node sends an installation instruction to a target worker node. The installation instruction instructs the target worker node to install the cloud-native system based on the first offline image source file. The installation instruction also includes an automated installation script that instructs the target worker node to perform steps for installing the cloud-native system based on the first offline image source file. The target worker node may receive the installation instruction and then install the cloud-native system based on the automated installation script and the first offline image source file.

[0140] For example, taking the installation of the cluster backup service on the working node 01 as an example, the working node 01 receives the software-related package of the cluster backup software (including the installation package of the cluster backup software and the server-side image of the cluster backup software) sent by the control node. The automated installation script for installing the cluster backup service may include: decompressing the software-related package of the cluster backup software, and installing the client of the cluster backup software through the installation package of the cluster backup software. Afterwards, a key file for accessing the data storage software (such as the data storage software) can be created. The data storage software account in the key file is the data storage software, and the data storage software password is 123. Then, the server of the cluster backup software can be deployed through the server-side image of the cluster backup software, and the key file can be configured on the server of the cluster backup software, so that the server of the cluster backup software can access the data storage software cluster.

[0141] For another example, consider installing data storage software on worker node 02. Worker node 02 receives the data storage software's software-related packages (including the data storage software installation package) from the control node. The automated installation script for installing the data storage software may include: decompressing the data storage software's software-related packages. Afterwards, a data storage software user may be created on worker node 02. A mount disk path may then be created, and the disk may be mounted. Finally, the data storage software account and password may be declared.

[0142] It should be noted that, for the specific introduction of S401-S404, reference may be made to the introduction of S101-S107 in the above embodiment, which will not be repeated here.

[0143] The above describes the process of deploying a cloud-native system on a target worker node using a collection of software-related packages. The following describes the process of deploying a cloud-native system locally on a control node.

[0144] In some embodiments, the control node may store the set of software-related packages in a second preset working directory of the control node. The control node may then create a second offline image source file based on the set of software-related packages in the second preset working directory. The control node may then install the cloud-native system on the control node based on the second offline image source file.

[0145] It should be noted that for the specific introduction to the process of installing the cloud native system on the control node, please refer to the introduction to installing the cloud native system on the target working node in the above embodiment, which will not be repeated here.

[0146] It is understandable that after the control node stores the software-related package set in the second preset working directory, it can create a second offline image source file based on the software-related package set, and then install the cloud native system on the control node based on the second offline image source file. In this way, there is no need for developers to manually deploy the cloud native system. The control node can complete the deployment of the cloud native system in the cluster, thereby improving the efficiency of system deployment. In addition, since the control node stores the software-related package set, there is no need to download the cloud native system-related software package through the network, so that the control node can complete the deployment of the cloud native system in an offline environment.

[0147] The following describes the embodiments of the present application with reference to specific examples. Figure 5 As shown, the control node receives a control command, which is used to instruct the cluster whether to perform the target task, which is a cluster migration task or a new cluster task. When the cluster performs the target task, the control node determines whether a set of software-related packages is stored. If the control node does not store a set of software-related packages, the target task is exited. If the control node stores a set of software-related packages, the cloud native system is installed. Afterwards, the control node enters the system configuration information according to the prompts and modifies the configuration file list according to the system configuration information. The control node then starts installing the automated operation and maintenance software and executes the mutual trust script to complete the establishment of a mutual trust connection with the target working node. The control node then starts installing the container orchestration software and data storage software. The control node can then call the service installation script of the cluster backup software to complete the installation of the cluster backup service. When the cluster does not perform the target task, the control node does not perform the target task.

[0148] In an embodiment of the present application, after the cloud-native system is installed, the cloud-native system may include a cluster backup software client, which is configured to send preset instructions to the cluster backup software server in the cluster, the preset instructions being configured to instruct the backup or restore of target data. The target data is data in a target microservice, a target namespace, or a target service.

[0149] For example, the cluster can send preset instruction 1 for restoring data in namespace 1 through the client of the cluster backup software. Afterwards, the server of the cluster backup software can send preset instruction 1 to namespace 1, so that the data storage software cluster sends the data in namespace 1 to the cluster.

[0150] It's understandable that cloud-native systems include cluster backup software clients, enabling cluster backup capabilities. Furthermore, the target data is the data within the target microservice, target namespace, or target service, facilitating refined data management and reducing cluster processing load.

[0151] In an embodiment of the present application, the cloud native system may further include: data storage software, the data storage software is used to join the target working node to the data storage cluster; the data storage cluster is used to store target data.

[0152] For example, the data storage cluster can store data in namespace 1 and data in microservice 1.

[0153] It is understandable that the cloud-native system includes data storage software, which can complete the deployment of data storage clusters, so that the data storage clusters store target data, thereby completing the refined management of data.

[0154] The following describes how to install a cloud-native system cluster using specific examples.

[0155] like Figure 6 FIG. 6 shows a business processing system provided by an embodiment of the present application, which may include: a computing device cluster 601 , a load balancing cluster 602 , a data storage cluster 603 , and a terminal device 604 .

[0156] Among them, the computing device cluster 601 may include a business cluster, and the computing device cluster 601 may receive a business processing request sent by the terminal device 604 and send the processing result to the terminal device 604. In addition, the computing device cluster 601 is deployed with a cloud native system (such as automated operation and maintenance software, cluster backup software, etc.). For example, the computing device cluster 601 can manage containerized applications in the cluster through container orchestration software. For another example, the computing device cluster 601 is deployed with a client of cluster backup software and a server of cluster backup software, and data backup or data recovery can be completed through the cluster backup software. Among them, the business cluster may include: cluster backup software, container orchestration software, containerization software, and operating system software.

[0157] The load balancing cluster 602 includes a load balancer and can distribute business processing requests to different working nodes in the computing device cluster 601 based on the load of the computing device cluster 601 .

[0158] Among them, the load balancer can be used for load balancing and proxy services of Transmission Control Protocol (TCP) and Hypertext Transfer Protocol (HTTP) applications.

[0159] In some embodiments, the business processing system may further include a data storage cluster 603. The data storage cluster 603 is used to store data in the business cluster. The data storage cluster may include: data storage software.

[0160] For example, a data storage cluster can receive data backup requests from a business cluster via cluster backup software and store the data in the business cluster. Another example is a data storage cluster can receive data recovery requests from a business cluster and restore the data in the business cluster. Alternatively, a load balancing cluster can distribute data to different working nodes within the data storage cluster based on the cluster's load.

[0161] Optionally, the data storage cluster 603 can store / restore part of the data in the service cluster. For example, the data storage cluster 603 can store / restore the data of a namespace or a service in the service cluster.

[0162] In some embodiments, the computing device cluster 601 is a business cluster, and the business processing system may further include: a data storage cluster.

[0163] In the embodiment of the present application, the computing device cluster 601 may include at least one computing device. Different computing devices in the at least one computing device may communicate with each other. The computing device may be a single physical or logical server, or may be two or more physical or logical servers sharing different responsibilities and collaborating to implement various server functions.

[0164] Illustratively, the server may be a blade server, a high-density server, a rack server, a tower server, or the like.

[0165] The terminal device 604 may send a service processing request to the computing device cluster 601. For example, the terminal device 604 may send a service processing request to the computing device cluster 601 via a domain name system (DNS).

[0166] Exemplarily, the terminal device may include a mobile phone, a tablet computer, a handheld computer, a personal computer (PC), a cellular phone, a personal digital assistant (PDA), a wearable device (such as a smart watch, a smart bracelet, etc.), a smart home device (such as a television, etc.), a car computer (such as a car computer, etc.), a smart screen, a game console, a headset, an AI speaker, an augmented reality (AR) / virtual reality (VR) device, an ultra-mobile personal computer (UMPC), a laptop computer, a netbook, a desktop computer or an all-in-one computer, etc.

[0167] Combine Figure 6 ,like Figure 7As shown, the business processing system may further include: a computing device cluster 701, a load balancing cluster 702, and a terminal device 703. The computing device cluster 701 is deployed with a cloud native system.

[0168] If computing device cluster 601 fails and the data storage cluster stores data from computing device cluster 601, computing device cluster 701 can obtain the data from the data storage cluster. Furthermore, computing device cluster 701 can receive service processing requests from terminal device 604 and send the processing results to terminal device 703. Furthermore, computing device cluster 701 is deployed with container orchestration software.

[0169] For example, the computing device cluster 701 includes a business cluster. The computing device cluster 701 is deployed with a client of cluster backup software and a server of cluster backup software, and data recovery can be completed through the cluster backup software.

[0170] It should be noted that, for a specific introduction to the computing device cluster 701 , reference may be made to the description of the computing device cluster 601 , which will not be repeated here.

[0171] The load balancing cluster 702 can distribute business processing requests to different working nodes in the computing device cluster 701 based on the load of the computing device cluster 701. In addition, the computing device cluster 701 can access the data storage cluster 603 through the load balancing cluster 702.

[0172] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of a computing device. It is understandable that, in order to implement the above functions, the computing device includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the system deployment method steps of each example described in the embodiment disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computing device software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0173] The embodiment of the present application can divide the system deployment device into functional modules or functional units according to the above method example. For example, each functional module or functional unit can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules or functional units. Among them, the division of modules or units in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0174] Please refer to Figure 8 , which shows a schematic diagram of a system deployment device provided by an embodiment of the present application. The system deployment device can be a functional module in the above-mentioned computing device for implementing the method of the embodiment of the present application. Figure 8 As shown, the system deployment device may include: a sending module 801 and a processing module 802.

[0175] The sending module 801 is used to send the software-related package set to the target working node; the target working node is any working node, and the software-related package set includes the software-related packages required for deploying the cloud-native system. The sending module 801 is used to send a first instruction to the target working node, and the first instruction is used to instruct the target working node to store the software-related package set in the first preset working directory of the target working node. The sending module 801 is used to send a second instruction to the target working node, and the second instruction is used to instruct the target working node to create a first offline mirror source file based on the software-related package set in the first preset working directory. The processing module 802 is used to deploy the cloud-native system on the target working node based on the first offline mirror source file, and the first offline mirror source file is used to represent the source of the software-related packages required to install the cloud-native system.

[0176] In a possible implementation, the processing module 802 is configured to read the software-related package set from a storage device and write the software-related package set into a local storage space of the control node.

[0177] In another possible implementation, sending module 801 is configured to send the metadata creation tool installation package to the target work node. Sending module 801 is configured to send a third instruction to the target work node, the third instruction instructing the target work node to install the metadata creation tool. A second instruction instructs the target work node to create the first offline image source file by running the metadata creation tool.

[0178] In another possible implementation, a package manager is configured on the target worker node. Processing module 802 is configured to remove the package manager's historical image source files and clear cached data for the historical image source files. Processing module 802 is configured to install the cloud-native system on the target worker node based on the first offline image source file using the package manager.

[0179] In another possible implementation, deploying a cloud-native system includes multiple deployment tasks. Processing module 802 is configured to parse a pre-set task file, which includes multiple deployment tasks. Processing module 803 is configured to execute each deployment task on a target worker node via a package manager.

[0180] In another possible implementation, processing module 802 is configured to generate a target key pair, which includes a public key and a private key. Processing module 802 is configured to establish a connection with a target work node and send the public key to the target work node. The public key is used by the target work node to verify devices accessing the target work node, and the private key is used by the control node to access the target work node.

[0181] In another possible implementation, the cloud-native system includes a client of the cluster backup software, which is used to send preset instructions to the server of the cluster backup software in the cluster, and the preset instructions are used to instruct the backup or recovery of target data; the target data is the data in the target microservice, target namespace, or target service.

[0182] In another possible implementation, the cloud native system includes: data storage software, where the data storage software is used to add a target working node to a data storage cluster; and the data storage cluster is used to store target data.

[0183] In another possible implementation, processing module 802 is configured to store the set of software-related packages in a second preset working directory of the control node. Processing module 802 is configured to create a second offline image source file based on the set of software-related packages in the second preset working directory. Processing module 802 is configured to install the cloud-native system on the control node based on the second offline image source file.

[0184] Please refer to Figure 9 , which shows a schematic diagram of a system deployment device provided by an embodiment of the present application. The system deployment device can be a functional module in the above-mentioned computing device for implementing the method of the embodiment of the present application. Figure 9 As shown, the system deployment device may include: a receiving module 901 and a processing module 902.

[0185] The receiving module 901 is used to receive a set of software-related packages sent by the control node, where the set of software-related packages includes the software-related packages required for deploying the cloud-native system. The receiving module 901 is used to receive and, in response to a first instruction sent by the control node, store the set of software-related packages in a first preset working directory of the target working node. The receiving module 901 is also used to receive and, in response to a second instruction sent by the control node, create a first offline image source file based on the set of software-related packages in the first preset working directory. The processing module 902 is used to deploy the cloud-native system based on the first offline image source file, where the first offline image source file is used to represent the source of the software-related packages required for installing the cloud-native system.

[0186] In one possible implementation, receiving module 901 is configured to receive a metadata creation tool installation package sent by a control node. Receiving module 901 is configured to receive and, in response to a third instruction sent by the control node, install the metadata creation tool. The second instruction instructs a target working node to create a first offline image source file by running the metadata creation tool.

[0187] In another possible implementation, the receiving module 901 is configured to establish a connection with the control node and receive a public key sent by the control node. The public key is used by the target working node to verify a device accessing the target working node.

[0188] Other embodiments of the present application provide a computing device. The computing device may include a memory and one or more processors. The memory and processors are coupled. The memory is configured to store computer program code, which includes computer instructions. When the processors execute the computer instructions, the computing device may perform the functions or steps described in the method embodiments described above.

[0189] The present application also provides a chip system. Figure 10 As shown, the chip system includes at least one processor 1001 and at least one interface circuit 1002. The processor 1001 and the interface circuit 1002 can be interconnected via lines. For example, the interface circuit 1002 can be used to receive signals from other devices (such as the memory of a computing device). For another example, the interface circuit 1002 can be used to send signals to other devices (such as the processor 1001). Exemplarily, the interface circuit 1002 can read instructions stored in the memory and send the instructions to the processor 1001. When the instructions are executed by the processor 1001, the computing device can execute the various steps in the above embodiments. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiments of the present application.

[0190] An embodiment of the present application also provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on the above-mentioned computing device, the computing device executes each function or step in the above-mentioned method embodiment.

[0191] The embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute each function or step in the above method embodiment.

[0192] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0193] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0194] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0195] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0196] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0197] The above content is only a specific embodiment of this application, but the scope of protection of this application is not limited to this. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A system deployment method, characterized in that: Applied to a control node of a cluster, the method includes: Sending a set of software-related packages to a target working node; the target working node is any working node in the cluster, and the set of software-related packages includes software-related packages required for deploying a cloud-native system; Sending a first instruction to the target working node, wherein the first instruction is used to instruct the target working node to store the set of software-related packages in a first preset working directory of the target working node; Sending a second instruction to the target working node, wherein the second instruction is used to instruct the target working node to create a first offline image source file based on the software-related package set in the first preset working directory; The cloud native system is deployed on the target working node based on the first offline image source file, where the first offline image source file is used to represent the source of software-related packages required to install the cloud native system.

2. The system deployment method according to claim 1, characterized in that: Before sending the software-related package set to the target working node, the method further includes: The software-related package set is read from a storage device, and the software-related package set is written into the local storage space of the control node.

3. The system deployment method according to claim 1 or 2, characterized in that: Before sending the second instruction to the target working node, the method further includes: Sending the installation package of the metadata creation tool to the target working node; Sending a third instruction to the target working node, where the third instruction is used to instruct the target working node to install the metadata creation tool; The second instruction is used to instruct the target working node to create the first offline image source file by running the metadata creation tool.

4. The system deployment method according to any one of claims 1 to 3, characterized in that: The target working node is configured with a software package manager, and the cloud native system is deployed on the target working node based on the first offline image source file, including: Remove the historical image source files of the software package manager and clear the cached data of the historical image source files; The cloud native system is installed on the target working node based on the first offline image source file through the software package manager.

5. The system deployment method according to claim 4, characterized in that: Deploying the cloud native system includes multiple deployment tasks; installing the cloud native system on the target working node based on the first offline image source file through the package manager includes: Parsing a preset task file, wherein the task file includes the multiple deployment tasks; Each deployment task is executed on the target working node through the software package manager.

6. The system deployment method according to any one of claims 1 to 5, characterized in that: The method further comprises: Storing the software-related package set in a second preset working directory of the control node; Creating a second offline image source file based on the software-related package set in the second preset working directory; The cloud native system is installed on the control node based on the second offline image source file.

7. A system deployment method, characterized in that: Applied to a target working node of a cluster, the method includes: Receiving a set of software-related packages sent by a control node of the cluster, where the set of software-related packages includes software-related packages required for deploying a cloud-native system; receiving and responding to a first instruction sent by the control node, storing the set of software-related packages in a first preset working directory of the target working node; receiving and responding to a second instruction sent by the control node, creating a first offline image source file based on the set of software-related packages in the first preset working directory; The cloud-native system is deployed based on the first offline image source file, where the first offline image source file is used to indicate a source of software-related packages required to install the cloud-native system.

8. The system deployment method according to claim 7, characterized in that: After receiving and responding to the second instruction sent by the control node, creating a first offline image source file based on the set of software-related packages in the first preset working directory, the method further includes: Receiving an installation package of a metadata creation tool sent by the control node; receiving and installing the metadata creation tool in response to a third instruction sent by the control node; The second instruction is used to instruct the target working node to create the first offline image source file by running the metadata creation tool.

9. The system deployment method according to claim 7 or 8, characterized in that: The method further comprises: Establish a connection with the control node and receive a public key sent by the control node, where the public key is used by the target working node to verify a device accessing the target working node.

10. A computing device, characterized in that The computing device includes a memory and a processor; the memory and the processor are electrically connected; the memory is used to store program instructions, and the processor is used to execute the program instructions, so that the computing device implements the method according to any one of claims 1 to 9.

Images