Lans Carstensen created MESOS-2197:
--------------------------------------
Summary: Allow frameworks using Docker containerizer to prioritize
resourceOffers with precached Docker images
Key: MESOS-2197
URL: https://issues.apache.org/jira/browse/MESOS-2197
Project: Mesos
Issue Type: Improvement
Reporter: Lans Carstensen
Docker container / task startup latency is significantly different on slaves
that have already retrieved Docker images vs. those that haven't. It would be
desirable to give a framework the ability to sort/prioritize offers based on
whether or not the Docker image is already present or not.
Ideally this sort of signalling could also be leveraged to allow mesos slaves
to pre-populate Docker images that frameworks are requesting.
Keeping in mind that image tags are mutable. Just because there is an
"ubuntu:latest" image present on a slave doesn't mean that's the image that
will be used (i.e. force_pull_image=true - https://reviews.apache.org/r/28190/
). This is especially true of continuous integration / deployment environments
where "latest" could be changing frequently. The framework may end up having
to resolve an image tag to an image id first and use that for comparison with
the slaves.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
