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

Posted to issues@mesos.apache.org by "Gilbert Song (JIRA)" <ji...@apache.org> on 2015/12/23 00:03:46 UTC

[jira] [Assigned] (MESOS-4240) Pull provisioner from linux filesystem isolator to Mesos containerizer.

     [ https://issues.apache.org/jira/browse/MESOS-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilbert Song reassigned MESOS-4240:
-----------------------------------

    Assignee: Gilbert Song

> Pull provisioner from linux filesystem isolator to Mesos containerizer.
> -----------------------------------------------------------------------
>
>                 Key: MESOS-4240
>                 URL: https://issues.apache.org/jira/browse/MESOS-4240
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Jie Yu
>            Assignee: Gilbert Song
>
> The rationale behind this change is that many of the image specifications (e.g., Docker/Appc) are not just for filesystems. They also specify runtime configurations (e.g., environment variables, volumes, etc) for the container.
> Provisioner should return those runtime configurations to the Mesos containerizer and Mesos containerizer will delegate the isolation of those runtime configurations to the relevant isolator.
> Provisioner will return a ProvisionInfo (a protobuf) which will be passed to isolators (the 'prepare' interface). ProvisionInfo includes an optional 'rootfs' and image specific runtime configurations (could be the Docker/Appc manifest).



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