[
https://issues.apache.org/jira/browse/AIRFLOW-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370384#comment-16370384
]
Agraj Mangal commented on AIRFLOW-2068:
---------------------------------------
Hi [~bolke] I've updated the PR with the test case. The reason it's skipped for
you is that it requires Mesos Python bindings/eggs to run and the test is
skipped if it does not find those bindings.
The problem with not having those python bindings in airflow is that they are
currently not downloadable or installable via pip
(https://issues.apache.org/jira/browse/MESOS-8597)
Having said that I've build mesos locally and installed the python bindings and
ran the test successfully. I've updated the PR with the test output. Please let
me know if something else is required
> Mesos Executor should allow specifying optional Docker image before running
> command
> -----------------------------------------------------------------------------------
>
> Key: AIRFLOW-2068
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2068
> Project: Apache Airflow
> Issue Type: Improvement
> Components: executor
> Affects Versions: Airflow 1.8
> Reporter: Agraj Mangal
> Assignee: Agraj Mangal
> Priority: Major
>
> In its current form, MesosExecutor schedules tasks on mesos slaves which just
> contain airflow commands assuming that the mesos slaves already have airflow
> installed and configured on them. This assumption goes against the Mesos
> philosophy of having a heterogeneous cluster.
> Since mesos provides an option to pull a docker image before actually running
> the actual task/command so this improvement changes the mesos_executor.py to
> specify an optional docker image containing airflow which can be pulled on
> slaves before running the actual airflow command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
