[
https://issues.apache.org/jira/browse/MESOS-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599202#comment-14599202
]
Adam B commented on MESOS-2884:
-------------------------------
[~karya] These RRs have been committed. Is there anything else left to do for
this ticket?
commit 1a82a3fb2bc717c468218384190a115b770f88c3
Author: Kapil Arya <ka...@mesosphere.io>
Date: Tue Jun 23 12:33:41 2015 -0700
Updated LinuxLauncher to receive list of namespaces.
MesosContainerizer looks up the list of required namespaces by calling
Isolator::namespaces() for all enabled isolators and passes on this
value to LinuxLauncher.
Review: https://reviews.apache.org/r/35586
commit 2143ae0315990ed663bf5810a801adeacff3a986
Author: Kapil Arya <ka...@mesosphere.io>
Date: Tue Jun 23 12:32:32 2015 -0700
Updated Isolator to return required namespaces.
This would enable the MesosContainerizer to pass on a list of namespaces
to LinuxLauncher instead of having LinuxLauncher guess it from the
isolation flags.
Review: https://reviews.apache.org/r/35585
> Allow isolators to specify required namespaces
> ----------------------------------------------
>
> Key: MESOS-2884
> URL: https://issues.apache.org/jira/browse/MESOS-2884
> Project: Mesos
> Issue Type: Task
> Components: isolation
> Reporter: Kapil Arya
> Assignee: Kapil Arya
> Labels: mesosphere
>
> Currently, the LinuxLauncher looks into SlaveFlags to compute the namespaces
> that should be enabled when launching the executor. This means that a custom
> Isolator module doesn't have any way to specify dependency on a set of
> namespaces.
> The proposed solution is to extend the Isolator interface to also export the
> namespaces dependency. This way the MesosContainerizer can directly query all
> loaded Isolators (inbuilt and custom modules) to compute the set of
> namespaces required by the executor. This set of namespaces is then passed on
> to the LinuxLauncher.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
