[MESOS-6841] Allow Dynamic CNI Configuration

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Component/s: agent
• Assignee: Unassigned
• Reporter: Miguel Bernadin
• Shepherd: Avinash Sridharan
• Created: 27/Dec/16 19:44
• Updated: 27/Dec/16 19:54
• Resolved: 27/Dec/16 19:54

Description

Agents has the ability to set resources dynamically without agent restart. After seeing that CNI is configured at agent startup we could add Dynamic CNI Configuration support in the future. Creating this JIRA is to track this effort.

Note that the network/cni isolator learns all the available networks by looking at the CNI configuration in the --network_cni_config_dir at startup. This implies that if a new CNI network needs to be added after Agent startup, the Agent needs to be restarted. The network/cni isolator has been designed with recover capabilities and hence restarting the Agent (and therefore the network/cni isolator) will not affect container orchestration.

Sourced from http://mesos.apache.org/documentation/latest/cni/

Issue Links

• duplicates: MESOS-6567 Actively Scan for CNI Configurations