Agreed, vMotion always struck me as something for those monolithic apps with a lot of local state.
The industry seems to be moving away from that as fast as its little legs will carry it. On 19 February 2016 at 11:35, Jason Giedymin <[email protected]> wrote: > Food for thought: > > One should refrain from monolithic apps. If they're small and stateless you > should be doing rolling upgrades. > > If you find yourself with one container and you can't easily distribute that > work load by just scaling and load balancing then you have a monolith. Time > to enhance it. > > Containers should not be treated like VMs. > > -Jason > > On Feb 19, 2016, at 6:05 AM, Mike Michel <[email protected]> wrote: > > Question is if you really need this when you are moving in the world of > containers/microservices where it is about building stateless 12factor apps > except databases. Why moving a service when you can just kill it and let the > work be done by 10 other containers doing the same? I remember a talk on > dockercon about containers and live migration. It was like: „And now where > you know how to do it, dont’t do it!“ > > > > Von: Avinash Sridharan [mailto:[email protected]] > Gesendet: Freitag, 19. Februar 2016 05:48 > An: [email protected] > Betreff: Re: Feature request: move in-flight containers w/o stopping them > > > > 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 <[email protected]> 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 <[email protected]> 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
