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 https://github.com/apache/mesos/blob/ma

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 resource

Re: Question About Upgrading Mesos

On 2016年05月25日 10:11, haosdent wrote: > but come to step 3, why the running containers become KILLED or LOST ? If you removed the work_dir of slave, or some break changes make slave could not recover those containers successfully, they would be killed. we executed "rm -f /data/mesos/meta/sla

Re: Framework Scheduling on Slave Question

Hi, @Kent. > I’m trying to run a framework scheduler on a Mesos slave node. > Does one have to have mesos-master running on slave nodes to do this? If you mean run it manually, your could start your scheduler in any machine, just make sure the network connection works between framework and Mesos m

Framework Scheduling on Slave Question

Pardon me if this is a newbie question. I’m trying to port an existing simulation system that is comprised of many processes. The master process is executed by a user (on a Mesos master node) and it has a custom Framework that simply launches a process, call it the “root” process”, via a Comma

0.28.2

Hi folks, According to our release schedule, we should be cutting point release for 0.28.x. I volunteer to be the release manager. Vinod and Ben already started a branch (0.28.x) in the repo, so it's just a matter of cutting it. If you have any patch that you want to backport into 0.28.2, please l

Re: Persistent Volume API Change

I'd vote for fixing the bug directly w/o a deprecation period, because a framework is always supposed to registered with proper principal to perform various operations. As long as we clearly document this in upgrade.md, operators should be able to properly fix their framework usage and ACL, before