[
https://issues.apache.org/jira/browse/MESOS-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768302#comment-15768302
]
Jie Yu commented on MESOS-6567:
-------------------------------
commit 58f180a2059fc7610ee2ff6b3f0991f9d5492212
Author: Avinash sridharan <[email protected]>
Date: Wed Dec 21 11:42:11 2016 -0800
Modified the initialization logic for `network/cni` isolator.
Since the `network/cni` isolator will soon be able to
add/modify/delete CNI configuration files without the need for agent
restart, we are changing the initialization logic to not bail out if
we see errors while reading a CNI configuration file or don't find a
CNI plugin for a given CNI configuration. If either of these errors
occur the `network/cni` isolator would simply skip the specific CNI
network and complete the initialization.
Review: https://reviews.apache.org/r/54716/
> 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
> Assignee: Avinash Sridharan
>
> 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)
