You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Avinash Sridharan (JIRA)" <ji...@apache.org> on 2016/12/07 18:13:58 UTC

[jira] [Updated] (MESOS-6679) Allow `network/cni` isolator to dynamically load CNI configuration

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

Avinash Sridharan updated MESOS-6679:
-------------------------------------
    Summary: Allow `network/cni` isolator to dynamically load CNI configuration  (was: All `network/cni` isolator to dynamically load CNI configuration)

> Allow `network/cni` isolator to dynamically load CNI configuration
> ------------------------------------------------------------------
>
>                 Key: MESOS-6679
>                 URL: https://issues.apache.org/jira/browse/MESOS-6679
>             Project: Mesos
>          Issue Type: Improvement
>          Components: containerization
>            Reporter: Avinash Sridharan
>            Assignee: Avinash Sridharan
>              Labels: mesosphere
>
> Currently the `network/cni` isolator learns the CNI config at startup. In case the CNI config changes after the agent has started, the agent needs to be restarted in order to learn any modifications to the CNI config.
> We would like the `network/cni` isolator to be able to load CNI config on the fly without a restart. To achieve this we plan to introduce a new endpoint on the `network/cni` isolator that would allow the operator to explicitly ask the `network/cni` isolator to reload the configuration.



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