[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-dev
Subject:    Re: Setting up virtual machine isolation container
From:       Benjamin Hindman <benh () eecs ! berkeley ! edu>
Date:       2012-01-30 17:30:09
Message-ID: CAFeOQnWP1yQRyu4dv4ifVn7Dfp50bbCjikLRc3M67c-do8sAqQ () mail ! gmail ! com
[Download RAW message or body]


Hi Charles,

A 'dispatch' can currently only be done from within the same OS process as
the receiver (in this case, the slave). So you'll want your isolation
module to do this.

Provided your VM's networking stack gets set up correctly, the executor
should have no problem connecting back to the slave (since it does so via a
network socket).

Ben.



On Mon, Jan 30, 2012 at 7:41 AM, Charles Earl <charles.cearl@gmail.com>wrote:

> Hi,
> I am completing a virtual machine isolation container for mesos based upon
> the lxc container.
> Using LxcIsolationModule as a model, I launch vm (using virsh), start
> mesos-launcher on the vm
> I believe that I need to run something like
>  dispatch(slave, &Slave::executorStarted, frameworkId, executorId, pid);
> inside of the vm image to report the executor process to the slave.
> I believe the best way to accomplish this to create a simple fork/exec
> wrapper around
>  ExecutorLauncher::run()
> to do this, assuming that the environment variables are configured
> correctly on the virtual machine.
> Is this sensible?
> Charles


[prev in list] [next in list] [prev in thread] [next in thread]