[jira] [Commented] (MESOS-2824) Support pre-fetching default container image on slave startup

["Timothy Chen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576113#comment-14576113 ] 

Timothy Chen commented on MESOS-2824:
-------------------------------------

This is a great idea! 
However I'm thinking that image management is going to be evolving and growing feature as a whole , just fetching the default container info image seems pretty limited to me since you can only specify one image.
Do you think we should make this a bit more flexible by specifying a list of default images to prefetch?
Longer term I can foresee we have a lot more image specific configurations, and I was thinking might as well start somewhere.
Let me know what you think.


> Support pre-fetching default container image on slave startup
> -------------------------------------------------------------
>
>                 Key: MESOS-2824
>                 URL: https://issues.apache.org/jira/browse/MESOS-2824
>             Project: Mesos
>          Issue Type: Improvement
>          Components: isolation
>    Affects Versions: 0.23.0
>            Reporter: Ian Downes
>            Priority: Minor
>
> Default container images can be specified with the --default_container_info flag to the slave. This may be a large image that will take a long time to initially fetch/hash/extract when the first container is provisioned. Add optional support to start fetching the image when the slave starts and consider not registering until the fetch is complete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)