System and method for joining containers running on multiple nodes of a cluster

1. A computer-implemented method for joining containers running on a cluster of hardware nodes, the method comprising:

on a plurality of nodes connected into the cluster, where each node hosts at least one container, executing a plurality of real processes in the containers, where each real process is executed on a single container and other containers execute fake processes corresponding to the real process, and

wherein the fake process includes interfaces identical to interfaces of a corresponding real process;

for at least one container, executing a backup process that represents a state of the corresponding real process on each node, and

wherein the node on which the backup process executes has no other fake processes corresponding to the real process of that backup process;

determining the real process on a source container to be migrated and a target container where the real process is to be migrated;

for the target container, replacing the fake process with the real process and replacing the real process with the fake process on the source container; and

re-launching a process on the same hardware node with settings from another node;

wherein interfaces of real processes are connected to corresponding interfaces of the corresponding fake process to establish data flow of the interfaces of fake processes identical to the data flow outputted by interfaces of a corresponding real process.

2. The method of claim 1 , wherein interfaces of the fake processes are configured to receive data from conjugated interfaces.

3. The method of claim 1 , further comprising disconnecting interfaces of the real processes from corresponding interfaces of the fake processes when the interfaces of real processes are connected to interfaces of other real processes of the same container.

4. The method of claim 1 , further comprising discarding data flows directed from the real processes to the fake processes received at the interfaces of the fake processes connected to interfaces of another program module.

5. The method of claim 1 , further comprising storing data of the real processes.

6. The method of claim 1 , further comprising applying a check point method to distribution of the real processes and the fake processes for minimizing computational losses.

7. The method of claim 6 , wherein the check point method is Checkpoint/currently amended in User space (CRIU) method.

8. The method of claim 6 , wherein the checkpoint method provides for the re-launching of the process.

9. A computer-implemented method for joining containers running on a cluster of hardware nodes, the method comprising:

on a plurality of nodes connected into the cluster, where each node hosts at least one container, executing a plurality of real processes in the containers, where each real process is executed on a single container and other containers execute fake processes corresponding to the real process,

wherein the fake process includes interfaces identical to interfaces of a corresponding real process;

determining the real process on a source container to be migrated and a target container where the real process is to be migrated;

for the target container, replacing the fake process with the real process and replacing the real process with the fake process on the source container; and

re-launching a process on the same hardware node with settings from another node;

wherein interfaces of real processes are connected to corresponding interfaces of the corresponding fake process to establish data flow of the interfaces of fake processes identical to the data flow outputted by interfaces of a corresponding real process, and

wherein interfaces of the fake processes are configured to receive data from conjugated interfaces.

10. The method of claim 9 , wherein at least one container is executing a backup process that represents a state of the corresponding real process on each node, and

wherein the node on which the backup process executes has no other fake processes corresponding to the real process of that backup process.

11. The method of claim 9 , further comprising disconnecting interfaces of the real processes from corresponding interfaces of the fake processes when the interfaces of real processes are connected to interfaces of other real processes of the same container.

12. The method of claim 9 , further comprising discarding data flows directed from the real processes to the fake processes received at the interfaces of the fake processes connected to interfaces of another program module.

13. The method of claim 9 , further comprising storing data of the real processes.

14. The method of claim 9 , further comprising applying a check point method to distribution of the real processes and the fake processes for minimizing computational losses.

15. The method of claim 9 , wherein the check point method is Checkpoint in User space (CRIU) method.

16. A system for joining containers running on a cluster of hardware nodes, the system comprising:

a plurality of nodes connected into a cluster, each node having a processor;

a plurality of containers running on the nodes, wherein each node hosts at least one container;

a plurality of real processes executing in the containers, wherein each real process is executed on a single container and other containers execute fake processes corresponding to the real process on their respective processors;

wherein the system determines the real process on a source container to be migrated and a target container where the real process is to be migrated;

at least one container executing a backup process that represents a state of the corresponding real process on each node, and

wherein the node on which the backup process executes has no other fake processes corresponding to the real process of that backup process;

for the target container, the system replaces the fake process with the real process and replaces the real process with the fake process on the source container; and

the system re-launches a process on the same hardware node with live settings from another node,

wherein the fake process includes interfaces identical to interfaces of a corresponding real process, and

wherein interfaces of real processes are connected to a corresponding interfaces of the corresponding fake processes so as to establish output data flow of the corresponding interfaces of corresponding fake processes identical to the data flow outputted by interfaces of a corresponding real process.

17. The system of claim 16 , wherein, upon failure of a real process, the backup process takes over functions of the real process.