You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2017/01/17 01:04:26 UTC
[jira] [Commented] (MESOS-5931) Support auto backend in Unified
Containerizer.
[ https://issues.apache.org/jira/browse/MESOS-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824798#comment-15824798 ]
Adam B commented on MESOS-5931:
-------------------------------
Ping. Looks like we still need a review from the Shepherd, [~jieyu]
> 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
> Priority: Critical
> 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)