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 <[email protected]> wrote: > 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 > https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L233-L237 > , does this help? > > Thanks, > > Guangya > > On Wed, May 25, 2016 at 12:25 PM, Krishnanarayanan VR < > [email protected]> wrote: > >> >> 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 resources are also noted in the same file. >> o In the event that the framework dies and restarts, the file is >> processed first and a VM needs to be created iff the VM does not exist ( >> for whatever reason ). data for each VM is stored in a file likewise. >> >> My question/requirement is: >> >> The framework restart does not have any impact on the individual kvm VMs >> on the mesos slave baremetal servers. when the framework restarts, if the >> VM is already present, I'd just like to add it to the TASK_RUNNING status >> with the noted resources, without having to go through the actual executor. >> >> Any pointers on how this can be achieved ? >> >> Thanks >> > >
