[jira] [Updated] (MESOS-6348) Allow `network/cni` isolator unit-tests to run with CNI plugins

["Artem Harutyunyan (JIRA)" <ji...@apache.org>]

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

Artem Harutyunyan updated MESOS-6348:
-------------------------------------
    Sprint: Mesosphere Sprint 44, Mesosphere Sprint 45, Mesosphere Sprint 46, Mesosphere Sprint 47  (was: Mesosphere Sprint 44, Mesosphere Sprint 45, Mesosphere Sprint 46)

> Allow `network/cni` isolator unit-tests to run with CNI plugins 
> ----------------------------------------------------------------
>
>                 Key: MESOS-6348
>                 URL: https://issues.apache.org/jira/browse/MESOS-6348
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Avinash Sridharan
>            Assignee: Avinash Sridharan
>              Labels: mesosphere
>
> Currently, we don't have any infrastructure to allow for CNI plugins to be used in `network/cni` isolator unit-tests. This forces us to mock CNI plugins that don't use new network namespaces leading to very restricting form of unit-tests. 
> Especially for port-mapper plugin, in order to test its DNAT functionality it will be very useful if we run the containers in separate network namespace requiring an actual CNI plugin.
> The proposal is there to introduce a test filter called CNIPLUGIN, that gets set when CNI_PATH env var is set. Tests using the CNIPLUGIN filter can then use actual CNI plugins in their tests.



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