[
https://issues.apache.org/jira/browse/MESOS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051736#comment-15051736
]
Thomas Rampelberg commented on MESOS-4090:
------------------------------------------
I like the idea quite a bit. Leaving `native` as a catch all doesn't make much
sense though. I'd recommend either putting a couple different libs into
`native` (eg. executor, scheduler, ....) or splitting them out into totally
separate python packages named the way they're used (again, executor,
scheduler, ...). As the number of python packages are starting to get a little
ridiculous, my preference would be to put the libs into native.
> 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)
