You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2015/12/23 10:42:46 UTC

[jira] [Commented] (MESOS-3370) Deprecate the external containerizer

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

Bernd Mathiske commented on MESOS-3370:
---------------------------------------

commit 43420dd0a27cd4adf1b2c929262f96e86d647acf
Author: Joerg Schad <jo...@mesosphere.io>
Date:   Wed Dec 23 10:41:38 2015 +0100

    Added links to individual containerizers in containerizer-internal.md.
    
    Review: https://reviews.apache.org/r/41683/

> Deprecate the external containerizer
> ------------------------------------
>
>                 Key: MESOS-3370
>                 URL: https://issues.apache.org/jira/browse/MESOS-3370
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Niklas Quarfot Nielsen
>
> To our knowledge, no one is using the external containerizer and we could clean up code paths in the slave and containerizer interface (the dual launch() signatures)
> In a deprecation cycle, we can move this code into a module (dependent on containerizer modules landing) and from there, move it into it's own repo



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