[
https://issues.apache.org/jira/browse/MESOS-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666477#comment-15666477
]
Qian Zhang commented on MESOS-6567:
-----------------------------------
Yes, NetworkCniIsolatorProcess::create happens at boot, so picking up new CNI
network configuration files requires a reboot of agent. However, the
modification to an existing CNI network configuration file can be picked up at
runtime, because the CNI network configuration file will be read every time
when attaching a new container to a CNI network
(https://github.com/apache/mesos/blob/1.0.1/src/slave/containerizer/mesos/isolators/network/cni/cni.cpp#L969),
so it is possible to launch a container to a CNI network, and then modify the
configuration file of that CNI network and launch another container to that CNI
network with the new configuration.
> 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)
