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

Till Toenshoff commented on MESOS-6344:
---------------------------------------

from [~avin...@mesosphere.io] via slack:

@till  @alexr we are still reviewing MESOS-6344 and MESOS-6023 . Jie has done 
one pass and we need to re-factor some code to get it right. My estimate is by 
EOD tomorrow (Friday). MESOS-6014 is just the epic, so will close it out once 
we are done with MESOS-6344 and MESOS-6023. MESOS-6040 is just enabling the 
port-mapper plugin in the CMake build. Should be accomplished by EOD tomorrow 
as well.

> Allow `network/cni` isolator to take a search path for CNI plugins instead of 
> single directory
> ----------------------------------------------------------------------------------------------
>
>                 Key: MESOS-6344
>                 URL: https://issues.apache.org/jira/browse/MESOS-6344
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>            Reporter: Avinash Sridharan
>            Assignee: Avinash Sridharan
>            Priority: Blocker
>              Labels: mesosphere
>
> Currently the `network/cni` isolator expects a single directory with the 
> `--network_cni_plugins_dir` . This is very limiting because this forces the 
> operator to put all the CNI plugins in the same directory. 
> With Mesos port-mapper CNI plugin this would also imply that the operator 
> would have to move this plugin from the Mesos installation directory to a 
> directory specified in the `--network_cni_plugins_dir`. 
> To simplify the operators experience it would make sense for the 
> `--network_cni_plugins_dir` flag to take in set of directories instead of 
> single directory. The `network/cni` isolator can then search this set of 
> directories to find the CNI plugin.



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

Reply via email to