Container migration method and device, electronic equipment, storage medium and computer program product

Abstract

The invention relates to a container migration method and device, electronic equipment, a storage medium and a computer program product. The method comprises the following steps: receiving a migration request for a target container in a source side node from the source side node in a plurality of side nodes; in response to the migration request, sending a migration instruction for the target container and business data of the target container to the target side node; wherein the migration instruction is used for instructing the target side node to create a new container corresponding to the target container based on the container mirror image of the target container, the configuration file and the service data. Therefore, the container mirror image and the configuration file of each side node can be synchronized among the plurality of side nodes in advance through the cloud host, and when the container migration on the source side node is triggered, the target side node can directly use the configuration file and the container mirror image of the to-be-migrated container pulled from the cloud host in advance to execute the container migration. Therefore, the container migration time can be shortened.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and more particularly, to a container migration method, apparatus, electronic device, storage medium, and computer program product. Background Art

[0002] Docker is a lightweight container platform that uses operating system-level virtualization technology to isolate and run applications. There are two main approaches to hot migration of Docker containers: The first solution involves hot migration of containers using container orchestration frameworks such as Kubernetes and KubeEdge. However, adapting and porting the Kubernetes framework to edge devices requires at least four cores and 8GB of memory, which is a waste of resources.

[0003] The second solution primarily analyzes the Docker container configuration based on Docker's operating principles and then reverse-engineers the container on the destination host based on the analyzed configuration to achieve container migration. This solution eliminates the need for the Kubernetes framework, thus conserving hardware resources. However, in this container migration solution, the migration time is primarily determined by the size of the container. Larger containers will take longer to migrate, resulting in inefficient container migration. Summary of the Invention

[0004] The present disclosure provides a container migration method, apparatus, electronic device, storage medium, and computer program product to at least address the problem in the above-mentioned related art that, if the container is large, the container migration will take a long time, which will lead to low container migration efficiency.

[0005] According to a first aspect of an embodiment of the present disclosure, a container migration method is provided, which is applied to a cloud host, and the cloud host communicates with multiple edge nodes. The container migration method includes: receiving a migration request for a target container in the source edge node from a source edge node among the multiple edge nodes; in response to the migration request, sending a migration indication for the target container and the business data of the target container to a target edge node among the multiple edge nodes, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes in advance through the cloud host; wherein the migration indication is used to instruct the target edge node to create a new container corresponding to the target container based on the container image, configuration file and business data of the target container.

[0006] Optionally, it also includes: regularly detecting whether the business data of at least one container installed on each edge node has changed; when it is determined that the business data of a container in a certain edge node has changed, receiving and saving the changed business data of the container in the certain edge node.

[0007] Optionally, it also includes: regularly detecting whether the configuration file of at least one container installed on each edge node has changed; when it is determined that the configuration file of a container in a certain edge node has changed, receiving and saving the changed configuration file of the certain container in the certain edge node, and synchronizing it to other edge nodes.

[0008] Optionally, before responding to the migration request and sending a migration indication for the target container and the business data of the target container to a target edge node among the multiple edge nodes, it also includes: obtaining the load status of each edge node among the multiple edge nodes; and selecting an edge node from the multiple edge nodes as the target edge node based on the load status of each edge node.

[0009] Optionally, the load condition of the edge node includes at least one of the following items: the number of containers currently running on the edge node, the current CPU resource occupancy of the edge node, and the current memory resource occupancy of the edge node.

[0010] According to a second aspect of an embodiment of the present disclosure, a container migration method is provided, which is applied to a target edge node, wherein the target edge node is one of a plurality of edge nodes communicating with a cloud host, and the container migration method comprises: receiving a migration indication for a target container in a source edge node among the plurality of edge nodes and business data of the target container from the cloud host, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the plurality of edge nodes are synchronized to other edge nodes through the cloud host; in response to the migration indication, creating a new container corresponding to the target container based on the container image, configuration file and business data of the target container.

[0011] According to a third aspect of an embodiment of the present disclosure, a container migration method is provided, comprising: sending a migration request for a target container in a source edge node among multiple edge nodes to a cloud host; sending a migration instruction for the target container and the business data of the target container to a target edge node among the multiple edge nodes through the cloud host in response to the migration request, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes in advance through the cloud host; creating a new container corresponding to the target container based on the container image, configuration file and business data of the target container through the target edge node in response to the migration instruction.

[0012] According to the fourth aspect of an embodiment of the present disclosure, there is provided a container migration device, which is applied to a cloud host, and the cloud host communicates with multiple edge nodes. The container migration device includes: a migration request receiving module, configured to receive a migration request for a target container in the source edge node from a source edge node among the multiple edge nodes; a business data sending module, configured to send a migration indication for the target container and the business data of the target container to a target edge node among the multiple edge nodes in response to the migration request, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes in advance through the cloud host; wherein the migration indication is used to instruct the target edge node to create a new container corresponding to the target container based on the container image, configuration file and business data of the target container.

[0013] Optionally, it also includes: a business data change detection module, configured to periodically detect whether the business data of at least one container installed on each edge node has changed; a changed business data receiving module, configured to receive and save the changed business data of a container in a certain edge node when it is determined that the business data of a container in a certain edge node has changed.

[0014] Optionally, it also includes: a configuration file change detection module, configured to periodically detect whether the configuration file of at least one container installed on each edge node has changed; a changed configuration file receiving module, configured to receive and save the changed configuration file of the container in a certain edge node when it is determined that the configuration file of the container in the certain edge node has changed, and synchronize it to other edge nodes.

[0015] Optionally, it also includes: a load acquisition module, configured to obtain the load status of each edge node among the multiple edge nodes; and an edge node selection module, configured to select an edge node from the multiple edge nodes as the target edge node based on the load status of each edge node.

[0016] Optionally, the load condition of the edge node includes at least one of the following items: the number of containers currently running on the edge node, the current CPU resource occupancy of the edge node, and the current memory resource occupancy of the edge node.

[0017] According to the fifth aspect of an embodiment of the present disclosure, a container migration device is provided, which is applied to a target edge node, wherein the target edge node is one of a plurality of edge nodes communicating with a cloud host, and the container migration device includes: a business data receiving module, configured to receive from the cloud host a migration indication for a target container in a source edge node among the plurality of edge nodes and business data of the target container, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the plurality of edge nodes are synchronized to other edge nodes through the cloud host; a new container creation module, configured to create a new container corresponding to the target container based on the container image, configuration file and business data of the target container in response to the migration indication.

[0018] According to the sixth aspect of an embodiment of the present disclosure, a container migration device is provided, comprising: a migration request sending module, configured to send a migration request for a target container in a source edge node among a plurality of edge nodes to a cloud host through a source edge node among the plurality of edge nodes; a migration indication sending module, configured to send a migration indication for the target container and the business data of the target container to a target edge node among the plurality of edge nodes through the cloud host in response to the migration request, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the plurality of edge nodes are synchronized to other edge nodes in advance through the cloud host; a container creation module, configured to create a new container corresponding to the target container based on the container image, configuration file and business data of the target container through the target edge node in response to the migration indication.

[0019] According to a seventh aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the container migration method according to the present disclosure.

[0020] According to an eighth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the container migration method according to the present disclosure.

[0021] According to a ninth aspect of an embodiment of the present disclosure, a computer program product is provided, including a computer program, which implements the container migration method according to the present disclosure when executed by a processor.

[0022] The technical solutions provided by the embodiments of the present disclosure bring at least the following beneficial effects: In the present disclosure, the container image and configuration file of each edge node can be synchronized in advance among multiple edge nodes through the cloud host. When the container migration on the source edge node is triggered, the target edge node can directly use the configuration file and container image of the container to be migrated that are pre-pulled from the cloud host to perform container migration, avoiding a series of tedious operation steps in the related technology of searching, packaging, synchronizing the configuration file of the container to be migrated and downloading the container image of the container to be migrated when the container migration is triggered, thereby shortening the container migration time.

[0023] In addition, the cloud host can pre-store container business data for each of the multiple edge nodes. When a container migration is triggered on the source edge node, the cloud host can send the business data of the container to be migrated to the target edge node. Because the cloud host provides a greater transmission bandwidth than the edge node, sending the business data of the container to be migrated from the cloud host to the target edge node can achieve a faster data transmission rate than sending it directly from the source edge node to the target edge node, further shortening the container migration time and improving the efficiency of container migration.

[0024] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute an improper limitation of the present disclosure.

[0026] Figure 1 is a schematic diagram illustrating the implementation process of the second container migration solution in the related art; Figure 2 is a schematic diagram illustrating a cloud-edge collaborative online hot migration deployment architecture according to an exemplary embodiment of the present disclosure; Figure 3 is a flowchart illustrating a container migration method according to an exemplary embodiment of the present disclosure; Figure 4 is a flowchart illustrating another container migration method according to an exemplary embodiment of the present disclosure; Figure 5 is a flowchart illustrating another container migration method according to an exemplary embodiment of the present disclosure; Figure 6 is a block diagram illustrating a container migration apparatus according to an exemplary embodiment of the present disclosure; Figure 7 is a block diagram illustrating another container migration apparatus according to an exemplary embodiment of the present disclosure; Figure 8 is a block diagram illustrating another container migration apparatus according to an exemplary embodiment of the present disclosure; Figure 9 is a block diagram illustrating an electronic device according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0028] It should be noted that the terms "first," "second," and the like in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the numbers used in this manner are interchangeable where appropriate so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The implementation methods described in the following examples do not represent all implementation methods consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with certain aspects of the present disclosure as detailed in the appended claims.

[0029] It should be noted that the phrase "at least one of the several items" in this disclosure includes three types of parallel situations: "any one of the several items", "a combination of any multiple of the several items", and "all of the several items". For example, "including at least one of A and B" includes the following three parallel situations: (1) including A; (2) including B; (3) including A and B. For another example, "performing at least one of step 1 and step 2" means the following three parallel situations: (1) performing step 1; (2) performing step 2; and (3) performing both step 1 and step 2.

[0030] Live migration technology refers to the process of migrating virtualized systems or application business systems from one host to another by leveraging a cluster, interrupting business applications as quickly as possible. Live migration technology for traditional KVM-based virtual machines is relatively mature. However, compared to traditional virtual machines, containers are essentially specialized processes with a high dependency on the host. Therefore, the live migration mechanism used in virtual machines cannot be directly applied to Docker containers. In this context, cross-edge node live migration of business applications has become a crucial means of improving system resiliency and reliability.

[0031] As mentioned above, in the relevant technology, there are mainly two solutions for hot migration of Docker containers: the first solution is mainly to use container editing and orchestration frameworks such as Kubernetes and KubeEdge to hot migrate containers; the second solution is mainly to analyze the Docker container configuration based on the working principle of Docker, and then reversely reconstruct a container on the destination host according to the analyzed configuration to achieve container migration.

[0032] Figure 1 Schematic diagram showing the implementation process of the second container migration solution in the related art. Figure 1 The second container migration solution can mainly include the following four parts: 1. Migration preparation phase In this phase, the first step is to prepare the environment before migration between the source and destination hosts and synchronize configuration files and other information to the destination host, for example, establishing an SSL connection, copying the configuration file config.v2.json, etc. Then, the container C to be migrated on the source host can be exported and pushed to the private warehouse, and the container C to be migrated can be pulled out from the private warehouse on the destination host. Figure 1 Container C* represents the container being migrated to the destination host. Next, you need to rsync the container data and memory data on the source host to the destination host, and also synchronize any dirty data.

[0033] 2. Migrate container images and synchronize files Reference Figure 1 "Image" represents the image currently running on the host, while "Image*" represents a packaged image used for container live migration. Furthermore, "Image*" is a non-running container image. At this stage, you first need to execute the container creation command on the destination host and modify the container's ID and name to match the container information on the source host. You can then check whether the container data on the source host is consistent with the container data on the destination host.

[0034] 3. Restore application services At this stage, you can freeze the containers on the source and destination hosts, and use the docker start command to start the container on the destination host and configure related information such as the network. At this point, the container on the destination host is officially running and taking over the business.

[0035] 4. Clean up and migrate host resources During this phase, the main task is to clear information related to the migrated container on the source host. This can be divided into two situations. The first situation is that the container migration is successful. At this point, you can clean up and delete the container image on the source host, as well as the temporary files and data generated during the container migration process. The second situation is that the container migration fails. At this point, you need to use the docker start command on the source host to restart the container on the source host and resume services. In addition, you need to clean up and delete the container image on the destination host, as well as the temporary files and data generated during the container migration process. In addition, you need to record the reason for the container migration failure in the system / var / log.

[0036] It should be noted that regardless of the above container migration solution, container services must be temporarily interrupted for container migration. The container service interruption time can be calculated using the following formula: = + in, Indicates the time required to search for the configuration file, business data, container image version number, and other content of the container to be migrated when triggering container migration; Indicates the time it takes to package and export the found content; Indicates the time it takes to synchronize the packaged file from the source edge node to the target edge node; Indicates the time it takes for the target edge node to pull the container image of the container to be migrated from the application store; Indicates the time it takes to create a new container on the target edge node; Indicates the time it takes to start a newly created container on the target edge node.

[0037] In order to ensure the continuity of business services, shortening the interruption time of container business as much as possible has become an urgent problem that needs to be solved.

[0038] In order to solve the above-mentioned problems existing in the related technologies, the present disclosure provides a cloud-edge collaborative online hot migration deployment architecture solution. Figure 2 Schematic diagram showing a cloud-edge collaborative online hot migration deployment architecture according to an exemplary embodiment of the present disclosure. Figure 2The cloud-edge collaborative online hot migration deployment architecture can mainly include a cloud host (also known as: cloud master station, cloud server, etc.), multiple edge nodes (also known as edge nodes) and multiple end-side devices (for example, cameras, temperature sensors, humidity sensors, etc.).

[0039] The "cloud host" is mainly used to coordinate the hot migration process of the containers installed on each edge node; the "edge node" can refer to a physical device set up in a specific area. For example, the "edge node" can be a terminal device set up next to a street; the "end-side device" is mainly used to collect external data and synchronize it to the container it is associated with. It should be noted that the end-side devices associated with different containers may be different from each other, which is related to the type of container itself. For example, assuming that container A is mainly used to provide video surveillance services, the end-side device associated with container A can be a camera; assuming that container B is mainly used to provide weather forecast services, the end-side device associated with container B can be a temperature sensor, humidity sensor, etc.

[0040] It should be noted that each edge node can have at least one container installed. Furthermore, after establishing a connection with the cloud host, each edge node can synchronize the relevant information of each of its installed containers with the cloud host. For example, the edge node can send the container identifier, configuration file, and service data of each installed container to the cloud host.

[0041] The "container identifier" is used to uniquely indicate which container the corresponding container is, that is, the container identifiers corresponding to different containers are different from each other. The "container configuration file" may include but is not limited to the following: the version number of the container, how much CPU resources / memory resources / bandwidth resources the container requires, whether the container is associated with an end-side device, and which end-side devices are specifically associated with it, etc. In addition, the cloud host can also store a large number of container images. The container image can be understood as an installation package, which is mainly used to complete the deployment and installation of the container. Moreover, these container images can be stored in the cloud host after the cloud host is set up, so that each edge node can pull and install them.

[0042] After receiving the container identifier and configuration file of at least one container installed on each of the multiple edge nodes, the cloud host can synchronize the container identifier and configuration file of at least one container installed on each edge node with the other edge nodes. In this way, each edge node can store the configuration files of all containers installed on all other edge nodes.

[0043] Exemplarily, after each edge node obtains the container identifier of the container installed on other edge nodes, it can also use the obtained container identifier to pull down the container image of the corresponding container on the cloud host. In this way, each edge node can also store the container images of all containers installed on all other edge nodes. It should be noted that the container image pulled down from the cloud host can be in the form of a compressed package, and the compressed package will only be decompressed when a new container is created on the target edge node. Therefore, downloading the container images of containers on other edge nodes in advance on each edge node does not take up too much space.

[0044] In this way, in the present disclosure, by using the cloud host to synchronize the configuration files and container images of the containers installed on each edge node to other edge nodes in advance, when the container migration is triggered, the target edge node can directly use the pre-acquired configuration files and container images of the containers to be migrated to perform the container migration, avoiding a series of tedious operation steps in the related technology of searching, packaging, synchronizing the configuration files of the containers to be migrated and downloading the container images of the containers to be migrated only when the container migration is triggered, thereby shortening the container migration time.

[0045] In addition, the cloud host can pre-store container business data for each of the multiple edge nodes. When a container migration is triggered on the source edge node, the cloud host can send the business data of the container to be migrated to the target edge node. Because the cloud host provides a greater transmission bandwidth than the edge node, sending the business data of the container to be migrated from the cloud host to the target edge node can achieve a faster data transmission rate than sending it directly from the source edge node to the target edge node, further shortening the container migration time and improving the efficiency of container migration.

[0046] Figure 3 It is a flowchart showing a container migration method according to an exemplary embodiment of the present disclosure, which is applied to a cloud host that can communicate with multiple edge nodes. For example, one or more cloud hosts in a cloud master station can establish associations and network communications with multiple edge nodes, so that subsequent cloud hosts can regularly obtain container configuration information and business data from the edge nodes. The "cloud master station" can be a service cluster, which can include multiple cloud hosts, each of which is mainly used to coordinate the hot migration process of the containers installed on each edge node connected to it.

[0047] Reference Figure 3In step 301, a migration request for a target container in a source edge node may be received from a source edge node among multiple edge nodes. For example, when the source edge node receives a migration instruction from a user for a target container installed on it, it may send a migration request for the target container to the cloud host. Exemplarily, the migration request may include a container identifier of the target container, so that the cloud host can promptly identify which container needs to be migrated.

[0048] According to an exemplary embodiment of the present disclosure, after receiving the migration request, the cloud host can also obtain the load status of each of the multiple edge nodes. For example, the load status may include, but is not limited to, the number of containers currently running on the edge node, the current CPU resource occupancy of the edge node, the current memory resource occupancy of the edge node, and the like. The cloud host can select an edge node from the multiple edge nodes as the target edge node based on the load status of each edge node, wherein the lighter the load of the edge node, the greater the probability that the edge node is selected as the target edge node.

[0049] For example, the cloud host can use at least one parameter of each edge node, including the number of currently running containers, the current CPU resource usage, and the current memory resource usage, to calculate a load index according to preset calculation rules. The target edge node can then be selected based on this load index. Furthermore, different parameters can be assigned corresponding weights to calculate the load index.

[0050] Alternatively, the fewer the number of containers currently running on the edge node, the less the current CPU resources of the edge node are occupied, and the less the current memory resources of the edge node are occupied, the lighter the load on the edge node can be considered, and in this case, the edge node can be tended to be used as the target edge node; if the more the number of containers currently running on the edge node, the more the current CPU resources of the edge node are occupied, and the more the current memory resources of the edge node are occupied, the heavier the load on the edge node can be considered, and in this case, the edge node can be tended not to be used as the target edge node.

[0051] It should be noted that the present disclosure does not limit the specific method of determining the load condition of the edge node, and the above implementation is only an exemplary description.

[0052] This way, when migrating a container, the cloud host can select a single edge node from multiple edge nodes based on their load to host the migrated container. This ensures load balancing across multiple edge nodes, preventing overloaded edge nodes from crashing or underloaded edge nodes from wasting resources. Furthermore, since the cloud host can select a target edge node based on actual conditions, it has a wider range of options to choose from, thereby improving the success rate of container migration.

[0053] In step 302, in response to the migration request, the cloud host may send a migration instruction for the target container and the business data of the target container to the target side node among the multiple side nodes, wherein the business data of the target container may be synchronized to the cloud host by the source side node after establishing a connection with the cloud host. The container image and corresponding configuration file of each container in each side node among the multiple side nodes may be synchronized to other side nodes in advance through the cloud host. The above-mentioned migration instruction can be used to instruct the target side node to create a new container corresponding to the target container based on the container image, configuration file and business data of the target container to migrate the target container.

[0054] It should be noted that when creating a new container corresponding to the target container on the target edge node, the target container on the source edge node needs to be frozen. For example, the target container on the source edge node needs to be "locked." Furthermore, if the target container is associated with an edge device, the connection between the target container and the associated edge device also needs to be disconnected. Correspondingly, the target edge node also needs to establish new connections with these edge devices based on the information about the edge devices associated with the target container contained in the target container's configuration file.

[0055] Furthermore, a frozen container cannot send or receive data. Therefore, to avoid data loss, the service data generated after the target container is frozen can be stored in the memory of the source edge node. This data can then be synchronized to the target edge node when the container service is restored. A new container created on the target edge node can then officially run and take over the services of the target container.

[0056] According to an exemplary embodiment of the present disclosure, the cloud host can also regularly detect whether the business data of at least one container installed on each edge node has changed. When it is determined that the business data of a container in a certain edge node has changed, the cloud host can receive and save the changed business data of the container in the edge node. Moreover, when triggering container migration, the cloud host can send the changed business data of the container to be migrated to the target edge node.

[0057] In this way, the cloud host can use a fixed frequency to check whether the business data of the container has changed on each edge node, and if there are changes, the cloud host can be synchronized in an incremental manner. Since the cloud host can provide a larger transmission bandwidth than the edge node, sending the business data of the container to be migrated from the cloud host to the target edge node can achieve a faster data transmission rate than directly transmitting data between the source edge node and the target edge node, thereby further shortening the container migration time and improving the container migration efficiency. In addition, compared to the method of synchronizing all the business data that has changed and has not changed, synchronizing data in an "incremental" manner can save bandwidth and avoid excessive occupation of storage resources.

[0058] According to an exemplary embodiment of the present disclosure, the cloud host may also periodically detect whether a configuration file of at least one container installed on each edge node has changed. When it is determined that a configuration file of a container in a certain edge node has changed, the cloud host may receive and save the changed configuration file of the container in the edge node, and may synchronize the changed configuration file to other edge nodes, so that the other edge nodes replace the original configuration file of the container with the changed configuration file.

[0059] This way, the cloud host can check each edge node for changes in the container's configuration file at a fixed frequency, and if there are changes, it can synchronize the cloud host incrementally. This ensures that the container configuration files stored on each edge node are up to date, and further ensures that available configuration files can be found immediately when a container migration occurs, thereby ensuring the success rate and efficiency of container migration. In addition, compared to synchronizing all changed and unchanged configuration files, synchronizing configuration files incrementally saves bandwidth and avoids excessive use of storage resources.

[0060] In this disclosure, a cloud-edge collaborative online hot migration optimization strategy is proposed, which can quickly skip the migration preparation stage and the migration container image and file synchronization stage when performing docker hot migration. That is, it can save the process of generating temporary image files on the source edge node, thereby shortening the migration process, that is, shortening the time of performing docker hot migration, and achieving business container cloning and recovery in seconds.

[0061] Figure 4 1 is a flowchart illustrating another container migration method according to an exemplary embodiment of the present disclosure, which is applied to a target edge node, which may be one of multiple edge nodes communicating with a cloud host.

[0062] Reference Figure 4In step 401, the target edge node may receive a migration instruction for a target container in a source edge node among the multiple edge nodes, as well as the service data of the target container, from the cloud host. The service data of the target container may be synchronized to the cloud host by the source edge node after establishing a connection with the cloud host. The container image and corresponding configuration file of each container in each of the multiple edge nodes may be synchronized to other edge nodes via the cloud host.

[0063] It should be noted that the source edge node can receive the user's migration instructions for the target container installed thereon. Then, in response to the received migration instructions, the source edge node can send a migration request for the target container to the cloud host. Exemplarily, the migration request can include the container identifier of the target container, so that the cloud host can know in a timely manner which container needs to be migrated. Then, the cloud host can search for the business data of the target container on it based on the container identifier of the target container included in the migration request, and then send the business data of the found target container to the target edge node.

[0064] In step 402 , the target edge node, in response to the migration instruction issued by the cloud host, may create a new container corresponding to the target container based on the container image, configuration file, and business data of the target container.

[0065] It should be noted that the configuration file of the target container can be synchronized to the cloud host by the source edge node after establishing a connection with the cloud host and sent to the target edge node by the cloud host; and the container image of the target container can be pulled down from the cloud host by the target edge node based on the container identifier of the target container after the source edge node synchronizes the container identifier of the target container to the cloud host after establishing a connection with the cloud host and the cloud host sends the container identifier of the target container to the target edge node.

[0066] In this way, when container migration occurs, since the configuration files and container images of the container to be migrated are pre-downloaded, the target side node can directly use the ready-made configuration files and container images to perform container migration, avoiding a series of tedious operation steps in related technologies such as searching, packaging, and synchronizing the configuration files of the container to be migrated and downloading the container images of the container to be migrated when the container migration is triggered, thereby shortening the container migration time.

[0067] In addition, the cloud host can pre-store container business data for each of the multiple edge nodes. When a container migration is triggered on the source edge node, the cloud host can send the business data of the container to be migrated to the target edge node. Because the cloud host provides a greater transmission bandwidth than the edge node, sending the business data of the container to be migrated from the cloud host to the target edge node can achieve a faster data transmission rate than sending it directly from the source edge node to the target edge node, further shortening the container migration time and improving the efficiency of container migration.

[0068] Figure 5 is a flowchart illustrating another container migration method according to an exemplary embodiment of the present disclosure.

[0069] Reference Figure 5 In step 501, a migration request for a target container in a source edge node can be sent to a cloud host through a source edge node among multiple edge nodes. Specifically, the source edge node can receive a migration instruction from a user for a target container installed thereon. Then, in response to the received migration instruction, the source edge node can send a migration request for the target container to the cloud host. Exemplarily, the migration request can include a container identifier of the target container, so that the cloud host can know in a timely manner which container needs to be migrated.

[0070] In step 502, the cloud host can send a migration instruction for the target container and the business data of the target container to a target edge node among the multiple edge nodes in response to the received migration request. The business data of the target container can be synchronized to the cloud host by the source edge node after establishing a connection with the cloud host. The container image and corresponding configuration file of each container in each edge node among the multiple edge nodes can be synchronized to other edge nodes in advance through the cloud host.

[0071] It should be noted that, as previously mentioned, after each edge node establishes a connection with the cloud host, it can synchronize the relevant information of each of the multiple containers installed on it with the cloud host. For example, the edge node can send the container identifier, configuration file, and business data of each container installed on it to the cloud host.

[0072] After the cloud host receives the container identifier and configuration file of at least one container installed on each of the multiple edge nodes, it can synchronize the container identifier and configuration file of at least one container installed on each edge node to other edge nodes. In this way, each edge node can store the configuration files of all containers installed on all other edge nodes. Exemplarily, after each edge node obtains the container identifier of the container installed on other edge nodes, it can also use the obtained container identifier to pull down the container image of the corresponding container on the cloud host. In this way, each edge node can also store the container image of all containers installed on all other edge nodes.

[0073] In step 503 , the target edge node may create a new container corresponding to the target container based on the container image, configuration file, and service data of the target container in response to the received migration instruction.

[0074] Figure 6 is a block diagram illustrating a container migration apparatus 600 according to an exemplary embodiment of the present disclosure, which is applied to a cloud host that can communicate with multiple edge nodes.

[0075] Reference Figure 6 The container migration device 600 may include a migration request receiving module 601 and a service data sending module 602.

[0076] The migration request receiving module 601 may receive, from a source edge node among multiple edge nodes, a migration request for a target container in the source edge node.

[0077] According to an exemplary embodiment of the present disclosure, the container migration device 600 may further include a load acquisition module and an edge node selection module.

[0078] After the cloud host receives the migration request, the load acquisition module can also obtain the load status of each of the multiple edge nodes. For example, the load status may include, but is not limited to, the number of containers currently running on the edge node, the current CPU resource occupancy of the edge node, the current memory resource occupancy of the edge node, etc. The edge node selection module can select an edge node from the multiple edge nodes as the target edge node based on the load status of each edge node, wherein the lighter the load of the edge node, the greater the probability that the edge node is selected as the target edge node.

[0079] This way, when migrating a container, the cloud host can select a single edge node from multiple edge nodes based on their load to host the migrated container. This ensures load balancing across multiple edge nodes, preventing overloaded edge nodes from crashing or underloaded edge nodes from wasting resources. Furthermore, since the cloud host can select a target edge node based on actual conditions, it has a wider range of options to choose from, thereby improving the success rate of container migration.

[0080] In response to the migration request, the business data sending module 602 can send a migration instruction for the target container and the business data of the target container to the target side node among the multiple side nodes, wherein the business data of the target container can be synchronized to the cloud host by the source side node after establishing a connection with the cloud host. The container image and corresponding configuration file of each container in each side node among the multiple side nodes can be synchronized to other side nodes in advance through the cloud host. The above-mentioned migration instruction can be used to instruct the target side node to create a new container corresponding to the target container based on the container image, configuration file and business data of the target container to migrate the target container.

[0081] According to an exemplary embodiment of the present disclosure, the container migration apparatus 600 may further include a service data change detection module and a changed service data receiving module.

[0082] The business data change detection module can periodically detect changes to the business data of at least one container installed on each edge node. If the business data of a container on an edge node is determined to have changed, the changed business data receiving module can receive and save the changed business data of the container on the edge node. Furthermore, when a container migration is triggered, the cloud host can send the changed business data of the container to be migrated to the target edge node.

[0083] In this way, the cloud host can use a fixed frequency to check whether the business data of the container has changed on each edge node, and if there are changes, the cloud host can be synchronized in an incremental manner. Since the cloud host can provide a larger transmission bandwidth than the edge node, sending the business data of the container to be migrated from the cloud host to the target edge node can achieve a faster data transmission rate than directly transmitting data between the source edge node and the target edge node, thereby further shortening the container migration time and improving the container migration efficiency. In addition, compared to the method of synchronizing all the business data that has changed and has not changed, synchronizing data in an "incremental" manner can save bandwidth and avoid excessive occupation of storage resources.

[0084] According to an exemplary embodiment of the present disclosure, the container migration apparatus 600 may further include a configuration file change detection module and a changed configuration file receiving module.

[0085] The configuration file change detection module can periodically detect whether the configuration file of at least one container installed on each edge node has changed. If it is determined that the configuration file of a container on a certain edge node has changed, the changed configuration file receiving module can receive and save the changed configuration file of the container on the edge node, and can synchronize the changed configuration file to other edge nodes, so that other edge nodes use the changed configuration file to replace the original configuration file of the container.

[0086] This way, the cloud host can check each edge node for changes in the container's configuration file at a fixed frequency, and if there are changes, it can synchronize the cloud host incrementally. This ensures that the container configuration files stored on each edge node are up to date, and further ensures that available configuration files can be found immediately when a container migration occurs, thereby ensuring the success rate and efficiency of container migration. In addition, compared to synchronizing all changed and unchanged configuration files, synchronizing configuration files incrementally saves bandwidth and avoids excessive use of storage resources.

[0087] Figure 7 7 is a block diagram illustrating another container migration apparatus 700 according to an exemplary embodiment of the present disclosure, which is applied to a target edge node, which may be one of multiple edge nodes communicating with a cloud host.

[0088] Reference Figure 7 The container migration device 700 may include a business data receiving module 701 and a new container creating module 702 .

[0089] The service data receiving module 701 can receive, from the cloud host, a migration instruction for a target container in a source edge node among multiple edge nodes and the service data of the target container, wherein the service data of the target container can be synchronized to the cloud host by the source edge node after establishing a connection with the cloud host. The container image and corresponding configuration file of each container in each edge node among the multiple edge nodes can be synchronized to other edge nodes through the cloud host.

[0090] In response to the migration instruction issued by the cloud host, the new container creation module 702 can create a new container corresponding to the target container based on the container image, configuration file and business data of the target container.

[0091] Figure 8 FIG. 8 is a block diagram illustrating another container migration apparatus 800 according to an exemplary embodiment of the present disclosure.

[0092] Reference Figure 8 The container migration device 800 may include a migration request sending module 801 , a migration instruction sending module 802 and a container creating module 803 .

[0093] The migration request sending module 801 can send a migration request for the target container in the source edge node to the cloud host. Specifically, the source edge node can receive a migration instruction from the user for the target container installed thereon. Then, in response to the received migration instruction, the source edge node can send a migration request for the target container to the cloud host. Exemplarily, the migration request can include a container identifier of the target container, so that the cloud host can know in a timely manner which container needs to be migrated.

[0094] In response to the received migration request, the migration instruction sending module 802 can send a migration instruction for the target container and the business data of the target container to the target edge node among the multiple edge nodes, wherein the business data of the target container can be synchronized to the cloud host by the source edge node after establishing a connection with the cloud host. The container image and corresponding configuration file of each container in each edge node among the multiple edge nodes can be synchronized to other edge nodes in advance through the cloud host.

[0095] In response to the received migration instruction, the container creation module 803 may create a new container corresponding to the target container based on the container image, configuration file, and service data of the target container.

[0096] Figure 9 is a block diagram illustrating an electronic device 900 according to an exemplary embodiment of the present disclosure.

[0097] Reference Figure 9 The electronic device 900 includes at least one memory 901 and at least one processor 902. The at least one memory 901 stores instructions. When the instructions are executed by the at least one processor 902, the container migration method according to the exemplary embodiment of the present disclosure is executed.

[0098] As an example, electronic device 900 may be a PC, tablet device, personal digital assistant, smartphone, or other device capable of executing the aforementioned instructions. Here, electronic device 900 is not necessarily a single electronic device, but may also be any collection of devices or circuits capable of executing the aforementioned instructions (or instruction sets) individually or in combination. Electronic device 900 may also be part of an integrated control system or system manager, or may be configured as a portable electronic device that interfaces with local or remote devices (e.g., via wireless transmission).

[0099] In electronic device 900, processor 902 may include a central processing unit (CPU), a graphics processing unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller, or a microprocessor. By way of example and not limitation, the processor may also include an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, a network processor, and the like.

[0100] The processor 902 can execute instructions or codes stored in the memory 901, wherein the memory 901 can also store data. Instructions and data can also be sent and received over a network via a network interface device, wherein the network interface device can use any known transmission protocol.

[0101] The memory 901 may be integrated with the processor 902, for example, by placing RAM or flash memory within an integrated circuit microprocessor or the like. Furthermore, the memory 901 may comprise a separate device, such as an external disk drive, a storage array, or any other storage device usable by a database system. The memory 901 and the processor 902 may be operatively coupled or may communicate with each other, for example, via an I / O port, a network connection, or the like, such that the processor 902 can access files stored in the memory.

[0102] In addition, the electronic device 900 may further include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, a mouse, a touch input device, etc.) All components of the electronic device 900 may be connected to each other via a bus and / or a network.

[0103] According to an exemplary embodiment of the present disclosure, a computer-readable storage medium may also be provided, which, when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform the above-mentioned container migration method. Examples of computer-readable storage media include: read-only memory (ROM), random access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), flash memory, non-volatile memory, CD-ROM, CD-R, CD+R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, Blu-ray or optical disk storage, hard disk drive (HDD), solid state drive (SSD), card storage (such as a multimedia card, secure digital (SD) card or extreme digital (XD) card), magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid state disk and any other device configured to store a computer program and any associated data, data files and data structures in a non-transitory manner and provide the computer program and any associated data, data files and data structures to a processor or computer so that the processor or computer can execute the computer program. The computer program in the above-mentioned computer-readable storage medium can be executed in an environment deployed in a computer device such as a client, a host, an agent device, a server, etc. In addition, in one example, the computer program and any associated data, data files and data structures are distributed on a networked computer system so that the computer program and any associated data, data files and data structures are stored, accessed and executed in a distributed manner by one or more processors or computers.

[0104] According to exemplary embodiments of the present disclosure, a computer program product may also be provided, including a computer program, which implements the container migration method according to the present disclosure when executed by a processor.

[0105] According to the container migration method, device, electronic device, storage medium and computer program product disclosed in the present invention, the container image and configuration file of each edge node can be synchronized in advance among multiple edge nodes through the cloud host. When the container migration on the source edge node is triggered, the target edge node can directly use the configuration file and container image of the container to be migrated that were pre-pulled from the cloud host to perform container migration, avoiding a series of tedious operation steps in the related art such as searching, packaging, synchronizing the configuration file of the container to be migrated and downloading the container image of the container to be migrated when the container migration is triggered, thereby shortening the container migration time.

[0106] In addition, the cloud host can pre-store container business data for each of the multiple edge nodes. When a container migration is triggered on the source edge node, the cloud host can send the business data of the container to be migrated to the target edge node. Because the cloud host provides a greater transmission bandwidth than the edge node, sending the business data of the container to be migrated from the cloud host to the target edge node can achieve a faster data transmission rate than sending it directly from the source edge node to the target edge node, further shortening the container migration time and improving the efficiency of container migration.

[0107] According to an exemplary embodiment of the present disclosure, when performing container migration, the cloud host can select a side node from multiple side nodes based on the load of each side node to undertake the migration container. This can ensure load balancing among multiple side nodes and avoid the situation where some side nodes crash due to excessive load or some side nodes are underloaded, resulting in resource waste. At the same time, since the cloud host is allowed to select the target side node from multiple side nodes based on actual conditions, there is a greater room for selection, thereby also improving the success rate of container migration.

[0108] According to an exemplary embodiment of the present disclosure, the cloud host can use a fixed frequency to check whether the business data of the container has changed on each edge node, and if there is a change, the cloud host can be synchronized in an incremental form. Since the cloud host can provide a larger transmission bandwidth than the edge node, sending the business data of the container to be migrated to the target edge node through the cloud host can obtain a faster data transmission rate than directly transmitting data between the source edge node and the target edge node, thereby further shortening the container migration time and improving the container migration efficiency. In addition, compared to the method of synchronizing all the business data that has changed and has not changed, synchronizing data in an "incremental" manner can save bandwidth and avoid excessive occupation of storage resources.

[0109] According to an exemplary embodiment of the present disclosure, the cloud host can use a fixed frequency to check whether the configuration file of the container on each edge node has changed, and if there is a change, the cloud host can be synchronized in an incremental manner, which can ensure that the configuration file of the container stored on each edge node is the latest, and further ensure that the available configuration file can be found immediately when the container migration occurs, thereby ensuring the success rate and migration efficiency of the container migration. In addition, compared to the method of synchronizing all the changed and unchanged configuration files, synchronizing the configuration files in an "incremental" manner can save bandwidth and avoid excessive occupation of storage resources.

[0110] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0111] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A container migration method, characterized in that: Applied to a cloud host that communicates with multiple edge nodes, the container migration method includes: Receiving, from a source edge node among the plurality of edge nodes, a migration request for a target container in the source edge node; In response to the migration request, sending a migration instruction for the target container and the business data of the target container to a target edge node among the multiple edge nodes, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes in advance through the cloud host; The migration instruction is used to instruct the target edge node to create a new container corresponding to the target container based on the container image, configuration file, and service data of the target container.

2. The container migration method according to claim 1, wherein: Also includes: Regularly detecting whether business data of at least one container installed on each edge node has changed; When it is determined that business data of a container in a certain edge node is changed, the changed business data of the container in the certain edge node is received and saved.

3. The container migration method according to claim 1, wherein: Also includes: Regularly checking whether a configuration file of at least one container installed on each edge node has changed; When it is determined that a configuration file of a container in a certain edge node is changed, the changed configuration file of the container in the certain edge node is received and saved, and synchronized to other edge nodes.

4. The container migration method according to claim 1, wherein: Before sending, in response to the migration request, a migration instruction for the target container and the service data of the target container to a target edge node among the multiple edge nodes, the method further includes: Obtaining a load condition of each edge node among the plurality of edge nodes; Based on the load condition of each edge node, an edge node is selected from the multiple edge nodes as the target edge node.

5. The container migration method according to claim 4, wherein: The load condition of the edge node includes at least one of the following items: The number of containers currently running on the edge node, the current CPU resource usage of the edge node, and the current memory resource usage of the edge node.

6. A container migration method, characterized in that: Applied to a target edge node, where the target edge node is one of multiple edge nodes communicating with a cloud host, the container migration method includes: Receiving, from the cloud host, a migration instruction for a target container in a source edge node among the multiple edge nodes and business data of the target container, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes through the cloud host; In response to the migration instruction, a new container corresponding to the target container is created based on the container image, configuration file, and service data of the target container.

7. A container migration method, characterized in that: include: Sending a migration request for a target container in a source edge node to a cloud host through a source edge node among the multiple edge nodes; Sending, via the cloud host, a migration instruction for the target container and the business data of the target container to a target edge node among the multiple edge nodes in response to the migration request, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes in advance through the cloud host; In response to the migration instruction, the target edge node creates a new container corresponding to the target container based on the container image, configuration file, and service data of the target container.

8. A container migration device, characterized in that: Applied to a cloud host, the cloud host communicates with multiple edge nodes, and the container migration device includes: A migration request receiving module is configured to receive, from a source edge node among the plurality of edge nodes, a migration request for a target container in the source edge node; a business data sending module, configured to, in response to the migration request, send a migration instruction for the target container and the business data of the target container to a target edge node among the multiple edge nodes, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes in advance through the cloud host; The migration instruction is used to instruct the target edge node to create a new container corresponding to the target container based on the container image, configuration file, and service data of the target container.

9. The container migration device according to claim 8, characterized in that Also includes: a business data change detection module, configured to periodically detect whether business data of at least one container installed on each edge node has changed; The changed business data receiving module is configured to receive and save the changed business data of a container in a certain edge node when it is determined that the business data of the container in the certain edge node is changed.

10. The container migration device according to claim 8, characterized in that: Also includes: a configuration file change detection module, configured to periodically detect whether a configuration file of at least one container installed on each edge node has changed; The changed configuration file receiving module is configured to receive and save the changed configuration file of a container in a certain edge node when it is determined that the configuration file of the container in the certain edge node has been changed, and synchronize it to other edge nodes.

11. The container migration device according to claim 8, wherein: Also includes: A load acquisition module is configured to acquire a load condition of each edge node among the plurality of edge nodes; The edge node selection module is configured to select an edge node from the multiple edge nodes as the target edge node based on the load condition of each edge node.

12. The container migration device according to claim 11, wherein: The load condition of the edge node includes at least one of the following items: The number of containers currently running on the edge node, the current CPU resource usage of the edge node, and the current memory resource usage of the edge node.

13. A container migration device, characterized in that: Applied to a target edge node, where the target edge node is one of multiple edge nodes communicating with a cloud host, the container migration apparatus includes: a business data receiving module configured to receive, from the cloud host, a migration instruction for a target container in a source edge node among the multiple edge nodes and business data of the target container, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes through the cloud host; The new container creation module is configured to create a new container corresponding to the target container based on the container image, configuration file, and business data of the target container in response to the migration instruction.

14. A container migration device, characterized in that: include: A migration request sending module is configured to send a migration request for a target container in a source edge node to a cloud host through a source edge node among the multiple edge nodes; a migration instruction sending module, configured to send, through the cloud host, a migration instruction for the target container and the business data of the target container to a target edge node among the multiple edge nodes in response to the migration request, wherein the business data of the target container is synchronized to the cloud host by the source edge node after establishing a connection with the cloud host, and the container image and corresponding configuration file of each container in each edge node among the multiple edge nodes are synchronized to other edge nodes in advance through the cloud host; The container creation module is configured to create, through the target edge node, a new container corresponding to the target container based on the container image, configuration file, and business data of the target container in response to the migration instruction.

15. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the container migration method according to any one of claims 1 to 5, and / or to implement the container migration method according to claim 6, and / or to implement the container migration method according to claim 7.

16. A computer-readable storage medium, characterized in that When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the container migration method as described in any one of claims 1 to 5, and / or execute the container migration method as described in claim 6, and / or execute the container migration method as described in claim 7.

17. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, it implements the container migration method according to any one of claims 1 to 5, and / or implements the container migration method according to claim 6, and / or implements the container migration method according to claim 7.

Images