Re: [VOTE] Release Apache Mesos 0.27.1 (rc1)

+1 (binding) Tested on ASF CI. Project Mesos-Release Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl [image: Success]

Re: AW: Feature request: move in-flight containers w/o stopping them

Mesos is not only about running stateless microservices to handle http requests. There are long duration workloads that would benefit from being rescheduled to a different host and not being interrupted; i.e. to implement dynamic bin packing in the cluster. The networking issues has been proved

Re: AW: Feature request: move in-flight containers w/o stopping them

Moving stateless services can be trivial or a non problem, as others have suggested. Migrating state full services becomes a function of migrating the state, including any network conx, etc. To think aloud, from a bit of past considerations in hpc like systems, some systems relied upon the

Re: AW: Feature request: move in-flight containers w/o stopping them

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 wrote: > Food for thought: > > One

Re: AW: Feature request: move in-flight containers w/o stopping them

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

AW: Feature request: move in-flight containers w/o stopping them

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