Re: "Appropriating" an existing process into mesos task

Hi Guangya: I looked around and didn't find any. We needed something really fast, so i put together something that can work for us. I've already deployed it in production and am actively bug fixing:) Pretty much everything is a hack and there is a long way to go. The code is here -

Re: "Appropriating" an existing process into mesos task

Hi Krishnanarayanan, Can you please share more for how did you use mesos executor to manage VMs? The Mesos also filed a JIRA here https://issues.apache.org/jira/browse/MESOS-2717 which want to introduce Qemu/LVM support, seems you are ahead of community. ;-) Thanks, Guangya On Wed, May 25,

Re: "Appropriating" an existing process into mesos task

Guangya: Thanks for your response. yeah, the VMs are created by the mesos executor. I'll take a look at the checkpointing and see if it works. On Wed, May 25, 2016 at 10:57 AM, Guangya Liu wrote: > Hi Krishnanarayanan, > > How did you create your VM on baremetal servers

Re: "Appropriating" an existing process into mesos task

Hi Krishnanarayanan, How did you create your VM on baremetal servers with Mesos? Are you leveraging mesos executor or some other components? The framework have checkpoint logic which can recover tasks in one framework back to original state, please refer to

Re: "Appropriating" an existing process into mesos task

Hello: We've been using mesos to allocate kvm VMs on our baremetal servers. The high level flow is as below: o user requests a VM with nCpus and mMem. o framework picks up an appropriate offer and spins a new VM o the baremetal on which the VM was spun is noted into a json file. cpu/mem