Re:Data migration with Kubernetes and Flocker
by lewq on Friday April 24, 2015 @01:53PM
(#9434917)
I believe it is possible to do container live migration -- and for certain stateful services in particular, may make more sense than "add some nodes, remove some others" as you describe. In a previous product, we built seamless container migration of FreeBSD jails based on a network proxy. It did shut down and start up the process, but as long as the process can be gracefully restarted (which most can!) from the user's perspective it just increases latency slightly.
[ Parent
| on HN ]
Re:Data migration with Kubernetes and Flocker
by mbreese on Friday April 24, 2015 @01:59PM
(#9434964)
Oh yeah, if you can survive stopping/starting the process, it should be easily do-able. You just have to manage migrating any stateful data (which you already do!).
But, I wouldn't call that a "live migration" in the VM live migration sense.
However, I wouldn't worry too much about it, since you're absolutely right that most processes can restart gracefully.