[
https://issues.apache.org/jira/browse/MESOS-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667560#comment-15667560
]
Dan Osborne commented on MESOS-6567:
------------------------------------
Ah I didn't interpret "existing" correctly in your post. Makes sense.
So since there already is a filescan happening at container runtime, it
hopefully shouldn't be too difficult to expand it to networks that don't
already exist too.
> 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)
