[
https://issues.apache.org/jira/browse/MESOS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051766#comment-15051766
]
Steve Niemitz commented on MESOS-4090:
--------------------------------------
I like splitting them into multiple packages, since it allows greater isolation
between the two different libraries. It's pretty unlikely (imo) that someone
would ever want to use both the scheduler and executor driver in the same
package, and splitting them also makes the executor driver much smaller.
My plan for this that I spoke with Vinod about offline was to keep the native
package around, but deprecate it, and then replace it with a scheduler package
for the next release.
> Create a light-weight, executor only mesos egg
> ----------------------------------------------
>
> Key: MESOS-4090
> URL: https://issues.apache.org/jira/browse/MESOS-4090
> Project: Mesos
> Issue Type: Improvement
> Components: build
> Reporter: Steve Niemitz
> Assignee: Steve Niemitz
>
> Currently, when running tasks in docker containers, if the executor uses the
> mesos.native python library, the execution environment inside the container
> (OS, native libs, etc) must match the execution environment outside the
> container fairly closely in order to load the mesos.so library.
> The solution here can be to introduce a much lighter weight python egg,
> mesos.executor, which only includes code (and dependencies) needed to create
> and run an MesosExecutorDriver. Executors can then use this native library
> instead of mesos.native.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
