You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2016/03/30 01:14:25 UTC
[jira] [Updated] (MESOS-4090) Create light-weight executor only and
scheduler only mesos eggs
[ https://issues.apache.org/jira/browse/MESOS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-4090:
------------------------------
Story Points: 5
Summary: Create light-weight executor only and scheduler only mesos eggs (was: Create a light-weight, executor only mesos egg)
commit da1dc09cf647c905fa47ac6ab8c04aeab5047c8b
Author: Steve Niemitz <sn...@twitter.com>
Date: Tue Mar 29 16:12:19 2016 -0700
Added CHANGELOG for python module changes.
Review: https://reviews.apache.org/r/45398/
> Create light-weight executor only and scheduler only mesos eggs
> ---------------------------------------------------------------
>
> 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
> Fix For: 0.29.0
>
>
> 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)