mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-5931) Support auto backend in Unified Containerizer.
Date Fri, 18 Nov 2016 05:43:58 GMT

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

Adam B commented on MESOS-5931:
-------------------------------

[~jieyu], [~gilbert], Can we make some progress on this again soon? The copy backend is really
undesirable for large production images.

> Support auto backend in Unified Containerizer.
> ----------------------------------------------
>
>                 Key: MESOS-5931
>                 URL: https://issues.apache.org/jira/browse/MESOS-5931
>             Project: Mesos
>          Issue Type: Improvement
>          Components: containerization
>            Reporter: Gilbert Song
>            Assignee: Gilbert Song
>              Labels: backend, containerizer, mesosphere
>
> Currently in Unified Containerizer, copy backend will be selected by default. This is
not ideal, especially for production environment. It would take a long time to prepare an
huge container image to copy it from the store to provisioner.
> Ideally, we should support `auto backend`, which would automatically/intelligently select
the best/optimal backend for image provisioner if user does not specify one from the agent
flag.
> We should have a logic design first in this ticket, to determine how we want to choose
the right backend (e.g., overlayfs or aufs should be preferred if available from the kernel).



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

Mime
View raw message