One problem with implementing something like vMotion for Mesos is to address seamless movement of network connectivity as well. This effectively requires moving the IP address of the container across hosts. If the container shares host network stack, this won't be possible since this would imply moving the host IP address from one host to another. When a container has its network namespace, attached to the host, using a bridge, moving across L2 segments might be a possibility. To move across L3 segments you will need some form of overlay (VxLAN maybe ?) .
On Thu, Feb 18, 2016 at 7:34 PM, Jay Taylor <outtat...@gmail.com> wrote: > Is this theoretically feasible with Linux checkpoint and restore, perhaps > via CRIU?http://criu.org/Main_Page > > On Feb 18, 2016, at 4:35 AM, Paul Bell <arach...@gmail.com> wrote: > > Hello All, > > Has there ever been any consideration of the ability to move in-flight > containers from one Mesos host node to another? > > I see this as analogous to VMware's "vMotion" facility wherein VMs can be > moved from one ESXi host to another. > > I suppose something like this could be useful from a load-balancing > perspective. > > Just curious if it's ever been considered and if so - and rejected - why > rejected? > > Thanks. > > -Paul > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245
