[
https://issues.apache.org/jira/browse/MESOS-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265093#comment-15265093
]
Guangya Liu commented on MESOS-5310:
------------------------------------
Does it make sense to make this a common endpoint can work for different
isolators, such as network, volume etc? I think that there will also be same
requirement for docker/volume isolator.
> Enable `network/cni` isolator to load CNI config at runtime.
> -------------------------------------------------------------
>
> Key: MESOS-5310
> URL: https://issues.apache.org/jira/browse/MESOS-5310
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Environment: linux
> Reporter: Avinash Sridharan
> Assignee: Avinash Sridharan
>
> Currently the `network/cni` isolator can only load the CNI configs at
> startup. This makes the CNI networks immutable. From an operational
> standpoint this can make deployments painful for operators.
> To make CNI more flexible the `network/cni` isolator should be able to load
> configs at run time.
> The proposal is to add an endpoint to the `network/cni` isolator, to which
> when the operator sends a PUT request the `network/cni` isolator will reload
> CNI configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
