Application program deployment method and device based on cloud service platform and storage medium

Abstract

The embodiment of the invention provides an application program deployment method and device based on a cloud service platform and a storage medium, and the method comprises the steps: obtaining a static file data package of a to-be-deployed custom root file system, and enabling the static file data package to be obtained through the construction of a container mirror image by a root file system configuration device and the packaging of the container mirror image; a binary file of the application program is deployed in the container mirror image; decompressing the static file data packet to deploy a custom root file system locally; and starting the application program in the isolated environment of the custom root file system. According to the embodiment of the invention, the physical machine deploys the self-defined root file system through the static file data packet of the self-defined root file system, a lightweight isolation environment independent of a physical machine environment is provided for an isolated application program, and a container mirror image construction tool or a container arrangement system does not need to be deployed in the physical machine; and light weight of isolation environment deployment is realized.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of computer and network communication technology, and in particular, to a method, device, and storage medium for deploying an application based on a cloud service platform. Background Art

[0002] There are two main types of existing solutions for building isolated environments: virtualization technology and containerization technology. Virtualization technology isolates different applications and operating systems by creating virtual machine instances, but due to its heavy resource consumption and long startup time, it may not be efficient enough in some scenarios. In order to overcome some limitations of virtualization technology and provide a lighter isolation mechanism, container technology has become an important solution. Containers are a lightweight virtualization technology that uses the isolation mechanism at the operating system level to package applications and their dependencies into a portable container image.

[0003] Container technology provides a complete isolation solution. However, some applications have only low isolation requirements when deployed. Introducing container technology at this time will occupy physical machine resources and cause additional costs. Therefore, a lightweight isolation environment is needed to isolate the application's operating environment. Summary of the invention

[0004] The embodiments of the present disclosure provide an application deployment method, device, and storage medium based on a cloud service platform to provide a lightweight isolation environment to isolate the operating environment of the application.

[0005] In a first aspect, an embodiment of the present disclosure provides an application deployment method based on a cloud service platform, comprising:

[0006] Obtain a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application;

[0007] Decompressing the static file data packet to locally deploy the custom root file system;

[0008] The application is started in an isolated environment of the custom root file system.

[0009] In a second aspect, an embodiment of the present disclosure provides an application deployment method based on a cloud service platform, comprising:

[0010] Using a container image building tool in a root file system configuration device, building a container image in the root file system configuration device according to a preset container image building file, wherein the container image is deployed with a binary file of an application program;

[0011] Packaging the container image to obtain a static file data packet of the custom root file system;

[0012] The static file data packet is sent to a target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in an isolated environment of the custom root file system.

[0013] In a third aspect, an embodiment of the present disclosure provides an application deployment device based on a cloud service platform, including:

[0014] An acquisition unit is used to acquire a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application;

[0015] A deployment unit, configured to decompress the static file data packet to locally deploy the custom root file system;

[0016] The running unit is used to start the application in the isolated environment of the custom root file system.

[0017] In a fourth aspect, an embodiment of the present disclosure provides an application deployment device based on a cloud service platform, including:

[0018] A construction unit, configured to construct a container image in the root file system configuration device according to a preset container image construction file through a container image construction tool in the root file system configuration device, wherein the container image is deployed with a binary file of an application program;

[0019] A packaging unit, used to package the container image to obtain a static file data packet of a custom root file system;

[0020] The sending unit is used to send the static file data packet to the target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in the isolated environment of the custom root file system.

[0021] In a fifth aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor and a memory;

[0022] The memory stores computer-executable instructions;

[0023] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the application deployment method based on the cloud service platform as described in the first aspect and various possible designs of the first aspect, or the application deployment method based on the cloud service platform as described in the second aspect and various possible designs of the second aspect.

[0024] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer execution instructions. When a processor executes the computer execution instructions, the application deployment method based on the cloud service platform as described in the first aspect and various possible designs of the first aspect, or the application deployment method based on the cloud service platform as described in the second aspect and various possible designs of the second aspect is implemented.

[0025] In the seventh aspect, an embodiment of the present disclosure provides a computer program product, including computer execution instructions. When a processor executes the computer execution instructions, it implements the application deployment method based on the cloud service platform as described in the first aspect and various possible designs of the first aspect, or the application deployment method based on the cloud service platform as described in the second aspect and various possible designs of the second aspect.

[0026] The cloud service platform-based application deployment method, device, and storage medium provided in the embodiments of the present disclosure obtain a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of the application; the static file data packet is decompressed to locally deploy the custom root file system; and the application is started in the isolated environment of the custom root file system. In the embodiments of the present disclosure, a physical machine deploys a custom root file system through a static file data packet of a custom root file system, providing an isolated application with a lightweight isolation environment independent of the physical machine environment, without the need to deploy a container image building tool or a container orchestration system in the physical machine, thereby achieving lightweight deployment of the isolated environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0028] Figure 1 A system diagram of a method for deploying an application based on a cloud service platform provided in an embodiment of the present disclosure;

[0029] Figure 2 A schematic diagram of a process flow of an application deployment method based on a cloud service platform provided in an embodiment of the present disclosure;

[0030] Figure 3 A schematic diagram of the architecture of a physical machine provided in an embodiment of the present disclosure;

[0031] Figure 4 A schematic diagram of a process flow of an application deployment method based on a cloud service platform provided in another embodiment of the present disclosure;

[0032] Figure 5 A structural block diagram of an application deployment device based on a cloud service platform provided in an embodiment of the present disclosure;

[0033] Figure 6 A structural block diagram of an application deployment device based on a cloud service platform provided in another embodiment of the present disclosure;

[0034] Figure 7 A schematic diagram of the hardware structure of an electronic device provided in one embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0036] Container is a lightweight virtualization technology that uses the isolation mechanism at the operating system level to package applications and their dependencies into a portable container image. This container image contains all the runtime environment, library files and configurations required by the application, so that the application can run in a consistent manner on any host that supports containers. Unlike virtual machine technology, container technology does not start an operating system for each container instance, but shares the same operating system in the same host. In essence, a container is a process running on an operating system, but with the addition of resource isolation and restrictions. The implementation principle of the container is to group related processes in the system that serve the same business goal and put them in the same namespace. Each namespace can have its own independent host name, process ID system, IPC, network, file system, user and other resources, and then use Cgroup technology to limit the CPU, memory and other resources that the process can use. Docker is one of the specific technical implementations of containerization technology, and it also relies on Namespaces and Cgroup to achieve isolation and restriction of container resources.

[0037] In an application scenario, when multiple applications share a server, the server's physical machine configuration, lib library and other operating environments are easily affected by other applications, which may cause application startup failures due to modifications to dependent libraries or dependent configurations. Therefore, there is a certain isolation requirement for applications. Although containers can provide an isolated environment, they have the following problems:

[0038] Container technology has many dependencies. The Linux system provides various isolation capabilities, but it does not provide native container building capabilities. It still needs to rely on third-party components such as Docker to create containers. The use and maintenance of such systems are relatively complex and will also cause a certain amount of physical machine resource occupation. On the other hand, the management capabilities for containers usually rely on third-party container orchestration systems, such as the most widely used Kubernetes. However, while it provides the ability to automatically manage containers, it also affects the stability of containers to a certain extent, such as container expulsion. For some applications with high stability requirements, this situation is intolerable.

[0039] In addition, container management mainly relies on third-party container orchestration systems. If a container orchestration system is not used, there is a lack of automated management of containers, and it is impossible to automatically pull up containers after the physical machine is restarted or retry to build a container environment after a problem occurs. This has a great impact on the stability of application operation.

[0040] Moreover, although container technology can provide a complete isolation solution, some applications have only low isolation requirements when deployed and mainly expect to run in an independent operating environment. They can tolerate using the same process, network and other namespaces as other applications. They do not need the complete isolation solution of container technology, but rather need a lightweight isolation environment to isolate the application's operating environment.

[0041] To solve the above technical problems, the embodiment of the present disclosure provides an application deployment method based on a cloud service platform, which can use the native capability root file system (Rootfs) of the Linux system to provide an operating environment independent of the physical machine for the isolated application, by obtaining a static file data packet of the custom root file system to be deployed, wherein the static file data packet is obtained by configuring the root file system device to build a container image and packaging the container image, and the container image is deployed with the binary file of the application; decompressing the static file data packet to deploy the custom root file system locally; and starting the application in the isolated environment of the custom root file system. In the embodiment of the present disclosure, the physical machine deploys the custom root file system through the static file data packet of the custom root file system, providing an isolated application with a lightweight isolation environment independent of the physical machine environment, which is not affected by the physical machine environment, and does not need to deploy a container image building tool or a container orchestration system in the physical machine, thereby realizing lightweight deployment of the isolated environment.

[0042] The custom root file system in the disclosed embodiment is also a process root file system (Process Root Filesystem, commonly referred to as the root file system in "process isolation" or "process namespace"), which can provide an independent view and environment for each process, so that the process can run in an isolated space to avoid interference with other processes or the system environment. Through this mechanism, the process root file system allows each process to have its own file system structure, for example, it can have different files, directories, and mount points, which will not affect other processes in the system or the entire file system. This isolation is crucial to improving the security, stability and resource management efficiency of the system. The process root file system allows multiple applications to run in parallel on the same host without interfering with each other, while simplifying dependency management and version control.

[0043] The system diagram of the application deployment method based on the cloud service platform provided by the embodiment of the present disclosure is as follows: Figure 1As shown, it includes a target physical machine that needs to deploy a lightweight isolation environment, and a root file system configuration device, wherein a container image building tool (such as Docker) is deployed in the root file system configuration device, and there is no need to deploy a container image building tool in the target physical machine. The root file system configuration device builds a container image through the container image building tool and packages the container image to obtain a static file data packet of the custom root file system, wherein the container image is deployed with the binary file of the application, and then sends it to the target physical machine, and the target physical machine decompresses the static file data packet to locally deploy the custom root file system, and starts the application in the isolated environment of the custom root file system.

[0044] The following will introduce in detail the application deployment method based on the cloud service platform of the present invention in conjunction with specific embodiments.

[0045] refer to Figure 2 , Figure 2 A flowchart of a method for deploying an application based on a cloud service platform provided in one embodiment of the present disclosure. The method of this embodiment can be applied to any target physical machine, wherein the target physical machine can be a physical machine in a cloud service platform, and of course it is not limited to a physical machine in a cloud platform. The method for deploying an application based on a cloud service platform includes:

[0046] S201. Obtain a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application.

[0047] In this embodiment, in order to achieve lightweight, there is no need to deploy container image building tools (such as Docker) or container orchestration systems (such as Kubernetes) on the target physical machine. Instead, a static file data packet of a custom root file system (Rootfs) to be deployed is obtained, and then a custom root file system (Rootfs) is deployed on the target physical machine after decompression, so that an operating environment independent of the physical machine, that is, an isolated environment, can be built for the isolated application.

[0048] The static file data packet of the custom root file system to be deployed can be provided by other devices. Optionally, in this embodiment, the static file data packet of the custom root file system to be deployed can be obtained by the root file system configuration device building a container image and packaging the container image.

[0049] Specifically, the root file system configuration device can be any device that can deploy container images, such as a development end device. A container image building tool (such as Docker) can be installed on the root file system configuration device. Furthermore, an image building file (Dockerfile) can be written in the container image building tool, or a pre-written image building file can be imported into the container image building tool, wherein the image building file includes a script consisting of a series of commands and parameters, and the script contains instructions and instructions required for building the image. Specifically, the operating system version that the application needs to run can be specified, and the binary files of the application and the dependent libraries that the application needs to execute can be installed using relevant commands. Some customized operations can also be performed, such as modifying configuration files, configuring environment variables, etc. Then, the container image building tool builds the container image in the root file system configuration device according to the container image building file, wherein the process of building the container image can adopt any known process, which will not be repeated here.

[0050] After completing the container image construction in the root file system configuration device, the container image can be packaged into a folder data package as a static file data package of the custom root file system. The root file system configuration device can then transmit this static file data package to any target physical machine, and the target physical machine deploys the custom root file system based on the static file data package.

[0051] Optionally, since the container image is in the Union File System format (UnionFS), it cannot be directly used by the target physical machine where the container image building tool is not deployed. Therefore, during packaging, the file system content of the container image can be exported as a tar archive through the output command (export command) as a static file data package of the custom root file system, where tar is a file packaging format.

[0052] Optionally, when the root file system configuration device transfers the static file data package of the custom root file system to the target physical machine, the file can be transferred between the root file system configuration device and the target physical machine by executing a file transfer command (scp command, etc.); or the root file system configuration device can upload the static file data package of the custom root file system to an intermediate database, such as a file storage system, etc., and then the target physical machine downloads it from the intermediate database; of course, it can also be transmitted through any other means, which will not be repeated here.

[0053] S202: Decompress the static file data package to locally deploy the custom root file system.

[0054] In this embodiment, after the target physical machine obtains the static file data packet of the custom root file system, it decompresses the static file data packet into the target physical machine, and obtains a root file system, that is, the custom root file system is deployed locally on the target physical machine, and the custom root file system is a process root file system, which can provide an isolated operating environment for the application, so that the application can run in this isolated environment. Compared with the container deployment process, the target physical machine needs to install a container image building tool (such as Docker) to build a container image in the container image building tool or run a container image package packaged by other physical machines. In this embodiment, the target physical machine does not need to deploy a container image building tool, and only needs to complete the decompression of the static file data packet of the custom root file system to obtain a custom root file system, which can provide a lightweight isolation environment.

[0055] S203: Start the application in the isolated environment of the custom root file system.

[0056] In this embodiment, after the local deployment of the custom root file system is completed, the application program can be started and run in the isolated environment of the custom root file system.

[0057] Optionally, the application can be started in at least two of the following ways:

[0058] Method 1: Execute a root file system switching command to switch from the current root file system to the custom root file system, and execute an application startup instruction to execute the binary file of the application in the isolated environment of the custom root file system;

[0059] Method 2: Through the first preset system manager of the physical machine operating system, according to the root file system field in the first preset system manager, execute the binary file of the application in the isolated environment of the custom root file system, wherein the root file system field is pre-configured as the custom root file system.

[0060] In method one, since the physical machine may currently be in the physical machine root file system or other root file systems, if you need to start an application in the root file system automatically, you need to switch from the current root file system to a custom root file system. Optionally, you can switch to a custom root file system by executing a root file system switching command (chroot command); then execute the application startup instruction to start executing the application's binary file in the isolated environment of the custom root file system, thereby starting and running the application.

[0061] In the second method, the application can be started from the isolated environment of the custom root file system in the form of a system manager. The system manager can be systemd, which is an initialization system and service manager in the Linux operating system. It optimizes the system startup speed by starting services in parallel and using dependencies, and can effectively manage system processes, services, mount points and devices, etc.; systemd uses a single configuration file format to define and manage services, and provides a rich command line tool so that users and administrators can easily control the status of services, view logs and troubleshoot; in addition, systemd also introduces many advanced features, such as service monitoring, automatic restart, resource control (through cgroups), target units (targets) and user session management, etc., which significantly improves the flexibility and maintainability of system management. In systemd, the root file system of the service can be specified by setting the root file system field (RootDirectory option) of the service. In this embodiment, the first preset system manager systemd can be pre-built in the target physical machine, and the root file system field (RootDirectory option) can be additionally specified as a custom root file system in its configuration, and then the binary file of the application can be executed in the isolated environment of the custom root file system through the first preset system manager systemd, so as to start and run the application.

[0062] Of course, the present embodiment is not limited to the above two startup methods, and other startup methods that can realize starting the application in the isolated environment of the custom root file system are also possible, and there is no limitation here.

[0063] Optionally, multiple applications can also be run in the isolated environment of the same custom root file system. That is, when the root file system configuration device builds a container image, the binary files of multiple applications can be deployed in the container image. Correspondingly, the static file data package of the custom root file system includes the binary files of multiple applications.

[0064] Optionally, multiple applications may have a certain execution order or dependency relationship, so multiple applications need to be started in sequence according to the execution order or dependency relationship during startup; in method one, each application startup instruction can be triggered in sequence according to the execution order or dependency relationship, so as to realize the sequential startup of multiple applications; and in method two, the execution order and / or dependency information of multiple applications can be preset in the first preset system manager, for example, the Before field and the Requires field are configured to determine the startup order of the applications, and then through the first preset system manager, according to the root file system field in the first preset system manager, and the execution order and / or dependency information, the multiple applications are started in sequence in the isolated environment of the custom root file system.

[0065] Of course, the above-mentioned multiple application programs are not limited to the application programs in the same custom root file system, and may also be application programs in different custom root file systems.

[0066] The application deployment method based on the cloud service platform provided in this embodiment obtains a static file data packet of the custom root file system to be deployed, wherein the static file data packet is obtained by configuring the root file system device to build a container image and packaging the container image, and the container image is deployed with the binary file of the application; decompresses the static file data packet to locally deploy the custom root file system; and starts the application in the isolated environment of the custom root file system. In this embodiment, the physical machine deploys the custom root file system through the static file data packet of the custom root file system, providing a lightweight isolation environment independent of the physical machine environment for the isolated application, without the need to deploy a container image building tool or a container orchestration system in the physical machine, thereby realizing lightweight deployment of the isolated environment.

[0067] Based on any of the above embodiments, after decompressing the static file data package to locally deploy the custom root file system in S202, the method may further include:

[0068] receiving a capability mount instruction, wherein the capability mount instruction is used to indicate a target system capability and / or a target mount point of a target hardware in the custom root file system that the application needs to use;

[0069] The capability mounting instruction is executed to mount the target system capability or the system path corresponding to the target hardware to the target mounting point.

[0070] In this embodiment, the directory structure of the custom root file system is basically the same as the directory structure of the physical machine root file system, but the system capabilities or hardware have not been used yet, that is, the custom root file system is a static folder at this time, lacking the system path of the process running, such as the system path of some system capabilities and / or the system path of the hardware, and needs to be mounted to the custom root file system to use these system capabilities and / or hardware. For example, if the application needs to use system capabilities such as process management and cgroup management, it is necessary to mount the system path (sys path) from the kernel to the target mount point specified in the custom root file system. If the application needs to use certain hardware, the device path (dev path) of the hardware device file is mounted to the target mount point specified in the custom root file system, so that the custom root file system realizes the system capabilities and hardware usage capabilities that are completely consistent with the physical machine. In the specific implementation, the mount operation can be implemented using the capability mount instruction (mount command), and the file type, the target system capability and / or target hardware to be mounted, and the target mount point can be specified in the mount operation, so that the corresponding system file can be mounted at the target mount point of the custom root file system, wherein the target mount point is the path of the mount position in the custom root file system.

[0071] Optionally, the above-mentioned mounting process may also be implemented in the form of a system manager, wherein the system manager may be systemd. Specifically, a second preset system manager systemd may be pre-built in the target physical machine, and the target system capabilities and / or target hardware required by the application, as well as the target mount point of the target system capabilities or target hardware in the custom root file system may be pre-configured, and then the system path corresponding to the target system capabilities or target hardware may be mounted to the target mount point through the second preset system manager systemd.

[0072] Based on any of the above embodiments, some configurations of the custom root file system can be configured when the root file system configuration device builds a container image, but there are some configurations that cannot be configured when the root file system configuration device builds a container image, such as some configurations that need to be dynamically loaded, which need to be dynamically loaded from a dynamic library, so the configuration needs to be performed at runtime. This embodiment also provides at least two ways to configure the custom root file system on the target physical machine:

[0073] Method 1: receiving a configuration instruction of a custom root file system, executing a root file system switching command, switching from a current root file system to the custom root file system, and executing the configuration instruction to configure the environment parameters of the custom root file system;

[0074] Method 2: using a second preset service manager of the physical machine operating system and configuring the environment parameters of the custom root file system according to preset configuration information in the second preset service manager.

[0075] In method one, when receiving a configuration instruction, you can first switch from the current root file system to the custom root file system before executing the configuration instruction on the custom root file system. The root file system can also be switched by executing the root file system switching command (chroot command), switching to the custom root file system path, and then executing the configuration operation of the environment parameters corresponding to the configuration instruction in the directory of the custom root file system, and then the configuration can be read after the application is started.

[0076] In the second method, the configuration of the custom root file system on the target physical machine can also be implemented in the form of a system manager, wherein the system manager can be systemd. Specifically, a second preset system manager systemd can be pre-built in the target physical machine, preset configuration information can be pre-set, and then the second preset system manager systemd can configure the environment parameters of the custom root file system according to the preset configuration information in the second preset service manager.

[0077] Another advantage of using the second configuration method is that it can avoid configuration failure when the physical machine is restarted. When the physical machine is restarted, the second preset service manager can automatically reconfigure the custom root file system according to the preset configuration information; similarly, the second preset system manager is used to implement the above-mentioned mounting of the target system capability or target hardware, which can also avoid the loss of mounting when the physical machine is restarted. When the physical machine is restarted, the second preset service manager can automatically remount the files corresponding to the target system capability or target hardware to the target mount point. The second preset service manager can realize the remounting and reconfiguration of the target system capability or target hardware of the custom root file system after the physical machine is restarted without manual execution, which improves automation and convenience.

[0078] It should be noted that in the above embodiment, before starting an application in an isolated environment that defines a root file system, the custom root file system must be mounted to the target system capabilities or target hardware and the custom root file system must be configured to prevent the application from being started before the isolated environment is built and its configuration does not meet expectations.

[0079] Based on the above embodiment, the specific architecture of the target physical machine can be as follows: Figure 3As shown, the left side is the architecture of the application deployed in the root file system of the physical machine above the operating system kernel and the computer hardware. The binary files (Bin) and dependent libraries (lib libraries) of these physical machine applications are deployed on the root file system of the physical machine, and can be managed and deployed by a system manager systemd; and the right side is the method provided by this embodiment, that is, a custom root file system independent of the physical machine root file system is deployed, on which the binary files (Bin) and dependent libraries (lib libraries) of isolated applications are deployed, and the environment and configuration of the custom root file system can be managed and deployed by one or more system managers systemd, and the startup control of the application can also be performed.

[0080] In an optional embodiment, after the target physical machine obtains the static file data packet of the custom root file system, the static file data packet can be decompressed; the target system capabilities required by the application or the system path corresponding to the target hardware are mounted to the target mount point in the custom root file system; the custom root file system is switched to and the environmental parameters of the custom root file system are configured; and then the application is started in the isolated environment of the custom root file system. Specifically, a first preset system manager can be configured first, and the root file system field in the first preset system manager is configured as the custom root file system, that is, the application is specified to be executed in the custom root file system. If multiple applications are involved, the startup order of multiple applications can also be configured. Furthermore, the first preset system manager executes the binary file of the application in the isolated environment of the custom root file system according to the root file system field to realize the startup of the application.

[0081] refer to Figure 4 , Figure 4 A flowchart of a method for deploying an application based on a cloud service platform provided in an embodiment of the present disclosure. The method of this embodiment can be applied to a root file system configuration device, wherein the root file system configuration device can be any device such as a physical machine that can deploy a container image building tool. The method for deploying an application based on a cloud service platform includes:

[0082] S401, using a container image building tool in a root file system configuration device, building a container image in the root file system configuration device according to a preset container image building file, wherein the container image is deployed with a binary file of an application;

[0083] S402, packaging the container image to obtain a static file data packet of the custom root file system;

[0084] S403: Send the static file data packet to the target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in the isolated environment of the custom root file system.

[0085] This embodiment is a method embodiment of the root file system configuration device side. Its specific principles and technical effects can be found in the method embodiment of the target physical machine side, which will not be repeated here.

[0086] The method for configuring the root file system device side provided in this embodiment can provide static file data packets of a custom root file system for one or more target physical machines, thereby eliminating the need to deploy container image building tools or container orchestration systems on the target physical machines. The target physical machines only need to deploy the custom root file system through the static file data packets of the custom root file system to provide an isolated application with a lightweight isolation environment independent of the physical machine environment, thereby achieving lightweight deployment of the isolation environment.

[0087] Corresponding to the application deployment method based on the cloud service platform on the target physical machine side of the above embodiment, Figure 5 A structural block diagram of an application deployment device based on a cloud service platform provided in an embodiment of the present disclosure. For ease of explanation, only the parts related to the embodiment of the present disclosure are shown. Figure 5 The application deployment device 500 based on the cloud service platform includes: an acquisition unit 501, a deployment unit 502, and an operation unit 503.

[0088] The acquisition unit 501 is used to acquire a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application;

[0089] A deployment unit 502, configured to decompress the static file data packet to locally deploy the custom root file system;

[0090] The running unit 503 is used to start the application in the isolated environment of the custom root file system.

[0091] In one or more embodiments of the present disclosure, when the running unit 503 starts the application in the isolated environment of the custom root file system, it is used to:

[0092] Execute a root file system switching command to switch from the current root file system to the custom root file system, and execute an application startup instruction to execute the binary file of the application in the isolated environment of the custom root file system; or

[0093] The binary file of the application is executed in the isolated environment of the custom root file system through a first preset system manager of the physical machine operating system according to a root file system field in the first preset system manager, wherein the root file system field is preconfigured as the custom root file system.

[0094] In one or more embodiments of the present disclosure, the application program includes a plurality of applications; and the first preset system manager is preset with the execution order and / or dependency information of the plurality of applications;

[0095] Correspondingly, the running unit 503, when starting the application in the isolated environment of the custom root file system through the first preset system manager of the physical machine operating system and according to the root file system field in the first preset system manager, is used to:

[0096] The plurality of applications are started sequentially in the isolated environment of the custom root file system through the first preset system manager according to the root file system field in the first preset system manager and the execution order and / or dependency information.

[0097] In one or more embodiments of the present disclosure, after decompressing the static file data packet to locally deploy the custom root file system, the deployment unit 502 is further configured to:

[0098] Receiving a capability mount instruction, wherein the capability mount instruction is used to indicate a target system capability and / or a target mount point of a target hardware in the custom root file system that the application needs to use; executing the capability mount instruction to mount a system path corresponding to the target system capability or the target hardware to the target mount point; or

[0099] Through the second preset service manager of the physical machine operating system, according to the target system capabilities and / or the target mount point of the target hardware in the custom root file system required by the application program preset in the second preset service manager, the system path corresponding to the target system capabilities or the target hardware is mounted to the target mount point.

[0100] In one or more embodiments of the present disclosure, before starting the application in the isolated environment of the custom root file system, the deployment unit 502 is further configured to:

[0101] Receiving a configuration instruction of a custom root file system, executing a root file system switching command, switching from a current root file system to the custom root file system, and executing the configuration instruction to configure environment parameters of the custom root file system; or

[0102] The environment parameters of the custom root file system are configured through the second preset service manager of the physical machine operating system according to the preset configuration information in the second preset service manager.

[0103] In one or more embodiments of the present disclosure, the deployment unit 502 is further configured to:

[0104] After the physical machine is restarted, the environment parameters of the custom root file system are reconfigured through the second preset service manager according to the preset configuration information in the second preset service manager.

[0105] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0106] Corresponding to the root file system configuration device side of the above embodiment, the application deployment method based on the cloud service platform, Figure 6 A structural block diagram of an application deployment device based on a cloud service platform provided in an embodiment of the present disclosure. For ease of explanation, only the parts related to the embodiment of the present disclosure are shown. Figure 6 The application deployment device 600 based on the cloud service platform includes: a construction unit 601, a packaging unit 602, and a sending unit 603.

[0107] Among them, the construction unit 601 is used to build a container image in the root file system configuration device according to a preset container image construction file through a container image construction tool in the root file system configuration device, wherein the container image is deployed with a binary file of an application;

[0108] A packaging unit 602 is used to package the container image to obtain a static file data packet of a custom root file system;

[0109] The sending unit 603 is used to send the static file data packet to the target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in the isolated environment of the custom root file system.

[0110] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0111] refer to Figure 7, which shows a schematic diagram of the structure of an electronic device 700 suitable for implementing the embodiment of the present disclosure, and the electronic device 700 may be a terminal device or a server. The terminal device may include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers, portable multimedia players (PMPs), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0112] like Figure 7 As shown, the electronic device 700 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 to a random access memory (RAM) 703. Various programs and data required for the operation of the electronic device 700 are also stored in the RAM 703. The processing device 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0113] Typically, the following devices may be connected to the I / O interface 705: input devices 706 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 707 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 708 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 709. The communication devices 709 may allow the electronic device 700 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 7 The electronic device 700 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0114] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 709, or installed from a storage device 708, or installed from a ROM 702. When the computer program is executed by the processing device 701, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0115] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0116] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0117] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the method shown in the above embodiment.

[0118] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0119] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0120] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".

[0121] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0122] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0123] In a first aspect, according to one or more embodiments of the present disclosure, a method for deploying an application based on a cloud service platform is provided, comprising:

[0124] Obtain a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application;

[0125] Decompressing the static file data packet to locally deploy the custom root file system;

[0126] The application is started in an isolated environment of the custom root file system.

[0127] According to one or more embodiments of the present disclosure, starting the application in the isolated environment of the custom root file system includes:

[0128] Execute a root file system switching command to switch from the current root file system to the custom root file system, and execute an application startup instruction to execute the binary file of the application in the isolated environment of the custom root file system; or

[0129] The binary file of the application is executed in the isolated environment of the custom root file system through a first preset system manager of the physical machine operating system according to a root file system field in the first preset system manager, wherein the root file system field is preconfigured as the custom root file system.

[0130] According to one or more embodiments of the present disclosure, the application program includes a plurality of applications; and the first preset system manager is preset with the execution order and / or dependency information of the plurality of applications;

[0131] Accordingly, starting the application in the isolated environment of the custom root file system according to the root file system field in the first preset system manager through the first preset system manager of the physical machine operating system includes:

[0132] The plurality of applications are started sequentially in the isolated environment of the custom root file system through the first preset system manager according to the root file system field in the first preset system manager and the execution order and / or dependency information.

[0133] According to one or more embodiments of the present disclosure, after decompressing the static file data package to locally deploy the custom root file system, the method further includes:

[0134] Receiving a capability mount instruction, wherein the capability mount instruction is used to indicate a target system capability and / or a target mount point of a target hardware in the custom root file system that the application needs to use; executing the capability mount instruction to mount a system path corresponding to the target system capability or the target hardware to the target mount point; or

[0135] Through the second preset service manager of the physical machine operating system, according to the target system capabilities and / or the target mount point of the target hardware in the custom root file system required by the application program preset in the second preset service manager, the system path corresponding to the target system capabilities or the target hardware is mounted to the target mount point.

[0136] According to one or more embodiments of the present disclosure, before starting the application in the isolated environment of the custom root file system, the method further includes:

[0137] Receiving a configuration instruction of a custom root file system, executing a root file system switching command, switching from a current root file system to the custom root file system, and executing the configuration instruction to configure environment parameters of the custom root file system; or

[0138] The environment parameters of the custom root file system are configured through the second preset service manager of the physical machine operating system according to the preset configuration information in the second preset service manager.

[0139] According to one or more embodiments of the present disclosure, the method further includes:

[0140] After the physical machine is restarted, the environment parameters of the custom root file system are reconfigured through the second preset service manager according to the preset configuration information in the second preset service manager.

[0141] In a second aspect, according to one or more embodiments of the present disclosure, a method for deploying an application based on a cloud service platform is provided, comprising:

[0142] Using a container image building tool in a root file system configuration device, building a container image in the root file system configuration device according to a preset container image building file, wherein the container image is deployed with a binary file of an application program;

[0143] Packaging the container image to obtain a static file data packet of the custom root file system;

[0144] The static file data packet is sent to a target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in an isolated environment of the custom root file system.

[0145] In a third aspect, according to one or more embodiments of the present disclosure, there is provided an application deployment device based on a cloud service platform, including:

[0146] An acquisition unit is used to acquire a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application;

[0147] A deployment unit, configured to decompress the static file data packet to locally deploy the custom root file system;

[0148] The running unit is used to start the application in the isolated environment of the custom root file system.

[0149] According to one or more embodiments of the present disclosure, when the running unit starts the application in the isolated environment of the custom root file system, it is used to:

[0150] Execute a root file system switching command to switch from the current root file system to the custom root file system, and execute an application startup instruction to execute the binary file of the application in the isolated environment of the custom root file system; or

[0151] The binary file of the application is executed in the isolated environment of the custom root file system through a first preset system manager of the physical machine operating system according to a root file system field in the first preset system manager, wherein the root file system field is preconfigured as the custom root file system.

[0152] According to one or more embodiments of the present disclosure, the application program includes a plurality of applications; and the first preset system manager is preset with the execution order and / or dependency information of the plurality of applications;

[0153] Accordingly, when the running unit starts the application in the isolated environment of the custom root file system through the first preset system manager of the physical machine operating system and according to the root file system field in the first preset system manager, it is used to:

[0154] The plurality of applications are started sequentially in the isolated environment of the custom root file system through the first preset system manager according to the root file system field in the first preset system manager and the execution order and / or dependency information.

[0155] According to one or more embodiments of the present disclosure, after decompressing the static file data packet to locally deploy the custom root file system, the deployment unit is further configured to:

[0156] Receiving a capability mount instruction, wherein the capability mount instruction is used to indicate a target system capability and / or a target mount point of a target hardware in the custom root file system that the application needs to use; executing the capability mount instruction to mount a system path corresponding to the target system capability or the target hardware to the target mount point; or

[0157] Through the second preset service manager of the physical machine operating system, according to the target system capabilities and / or the target mount point of the target hardware in the custom root file system required by the application program preset in the second preset service manager, the system path corresponding to the target system capabilities or the target hardware is mounted to the target mount point.

[0158] According to one or more embodiments of the present disclosure, before starting the application in the isolated environment of the custom root file system, the deployment unit is further used to:

[0159] Receiving a configuration instruction of a custom root file system, executing a root file system switching command, switching from a current root file system to the custom root file system, and executing the configuration instruction to configure environment parameters of the custom root file system; or

[0160] The environment parameters of the custom root file system are configured through the second preset service manager of the physical machine operating system according to the preset configuration information in the second preset service manager.

[0161] According to one or more embodiments of the present disclosure, the deployment unit is further configured to:

[0162] After the physical machine is restarted, the environment parameters of the custom root file system are reconfigured through the second preset service manager according to the preset configuration information in the second preset service manager.

[0163] In a fourth aspect, according to one or more embodiments of the present disclosure, there is provided an application deployment device based on a cloud service platform, including:

[0164] A construction unit, configured to construct a container image in the root file system configuration device according to a preset container image construction file through a container image construction tool in the root file system configuration device, wherein the container image is deployed with a binary file of an application program;

[0165] A packaging unit, used to package the container image to obtain a static file data packet of a custom root file system;

[0166] The sending unit is used to send the static file data packet to the target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in the isolated environment of the custom root file system.

[0167] In a fifth aspect, according to one or more embodiments of the present disclosure, there is provided an electronic device, comprising: at least one processor and a memory;

[0168] The memory stores computer-executable instructions;

[0169] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the application deployment method based on the cloud service platform as described in the first aspect and various possible designs of the first aspect, or the application deployment method based on the cloud service platform as described in the second aspect and various possible designs of the second aspect.

[0170] In a sixth aspect, according to one or more embodiments of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer execution instructions. When a processor executes the computer execution instructions, the application deployment method based on the cloud service platform as described in the first aspect and various possible designs of the first aspect, or the application deployment method based on the cloud service platform as described in the second aspect and various possible designs of the second aspect is implemented.

[0171] In the seventh aspect, according to one or more embodiments of the present disclosure, a computer program product is provided, including computer execution instructions. When a processor executes the computer execution instructions, it implements the application deployment method based on the cloud service platform as described in the first aspect and various possible designs of the first aspect, or the application deployment method based on the cloud service platform as described in the second aspect and various possible designs of the second aspect.

[0172] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

[0173] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0174] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. A method for deploying an application based on a cloud service platform, characterized in that: include: Obtain a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application; Decompressing the static file data packet to locally deploy the custom root file system; The application is started in an isolated environment of the custom root file system.

2. The method according to claim 1, characterized in that The starting the application in the isolated environment of the custom root file system includes: Execute a root file system switching command to switch from the current root file system to the custom root file system, and execute an application startup instruction to execute the binary file of the application in the isolated environment of the custom root file system; or The binary file of the application is executed in the isolated environment of the custom root file system through a first preset system manager of the physical machine operating system according to a root file system field in the first preset system manager, wherein the root file system field is preconfigured as the custom root file system.

3. The method according to claim 2, characterized in that The application program includes a plurality of applications; and the first preset system manager presets the execution order and / or dependency information of the plurality of application programs; Accordingly, starting the application in the isolated environment of the custom root file system according to the root file system field in the first preset system manager through the first preset system manager of the physical machine operating system includes: The plurality of applications are started sequentially in the isolated environment of the custom root file system through the first preset system manager according to the root file system field in the first preset system manager and the execution order and / or dependency information.

4. The method according to claim 1, characterized in that After decompressing the static file data packet to locally deploy the custom root file system, the method further includes: Receiving a capability mount instruction, wherein the capability mount instruction is used to indicate a target system capability and / or a target mount point of a target hardware in the custom root file system that the application needs to use; executing the capability mount instruction to mount a system path corresponding to the target system capability or the target hardware to the target mount point; or Through the second preset service manager of the physical machine operating system, according to the target system capabilities and / or the target mount point of the target hardware in the custom root file system required by the application program preset in the second preset service manager, the system path corresponding to the target system capabilities or the target hardware is mounted to the target mount point.

5. The method according to claim 1, characterized in that Before starting the application in the isolated environment of the custom root file system, the method further includes: Receiving a configuration instruction of a custom root file system, executing a root file system switching command, switching from a current root file system to the custom root file system, and executing the configuration instruction to configure environment parameters of the custom root file system; or The environment parameters of the custom root file system are configured through the second preset service manager of the physical machine operating system according to the preset configuration information in the second preset service manager.

6. The method according to claim 5, characterized in that The method further comprises: After the physical machine is restarted, the environment parameters of the custom root file system are reconfigured through the second preset service manager according to the preset configuration information in the second preset service manager.

7. A method for deploying an application based on a cloud service platform, characterized in that: include: Using a container image building tool in a root file system configuration device, building a container image in the root file system configuration device according to a preset container image building file, wherein the container image is deployed with a binary file of an application program; Packaging the container image to obtain a static file data packet of the custom root file system; The static file data packet is sent to a target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in an isolated environment of the custom root file system.

8. An application deployment device based on a cloud service platform, characterized in that: include: An acquisition unit is used to acquire a static file data packet of a custom root file system to be deployed, wherein the static file data packet is obtained by configuring a root file system device to build a container image and packaging the container image, and the container image is deployed with a binary file of an application; A deployment unit, configured to decompress the static file data packet to locally deploy the custom root file system; The running unit is used to start the application in the isolated environment of the custom root file system.

9. An application deployment device based on a cloud service platform, characterized in that: include: A construction unit, configured to construct a container image in the root file system configuration device according to a preset container image construction file through a container image construction tool in the root file system configuration device, wherein the container image is deployed with a binary file of an application program; A packaging unit, used to package the container image to obtain a static file data packet of a custom root file system; The sending unit is used to send the static file data packet to the target physical machine, so that the target physical machine decompresses the static file data packet to deploy the custom root file system, and starts the application in the isolated environment of the custom root file system.

10. An electronic device, characterized in that: include: at least one processor and memory; The memory stores computer-executable instructions; The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor performs the method according to any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the processor executes the computer-executable instructions, the method according to any one of claims 1 to 7 is implemented.

12. A computer program product, characterized in that The method comprises computer-executable instructions, and when a processor executes the computer-executable instructions, the method according to any one of claims 1 to 7 is implemented.

Images