You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Qian Zhang (JIRA)" <ji...@apache.org> on 2016/11/10 00:26:59 UTC

[jira] [Commented] (MESOS-6567) Actively Scan for CNI Configurations

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

Qian Zhang commented on MESOS-6567:
-----------------------------------

Currently, the modification to an existing CNI network configuration file under {{--network_cni_config_dir}} will be automatically picked up by Mesos agent when it attaches a container to the CNI network.

> Actively Scan for CNI Configurations
> ------------------------------------
>
>                 Key: MESOS-6567
>                 URL: https://issues.apache.org/jira/browse/MESOS-6567
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Dan Osborne
>
> Mesos-Agent currently loads the CNI configs into memory at startup. After this point, new configurations that are added will remain unknown to the Mesos Agent process until it is restarted.
> This ticket is to request that the Mesos Agent process can the CNI config directory each time it is networking a task, so that modifying, adding, and removing networks will not require a slave reboot.



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