[
https://issues.apache.org/jira/browse/MESOS-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665861#comment-15665861
]
Dan Osborne commented on MESOS-6567:
------------------------------------
I've reproed this on 1.0.1 and can confirm it is not scanned and picked up at
runtime, but instead requires a reboot of the slave process.
I think it's because scanning of CNI networks happens in
NetworkCniIsolatorProcess::create which I believe happens at boot, not during
NetworkCniIsolatorProcess::Isolate, which happens at container runtime?
> 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)
