[
https://issues.apache.org/jira/browse/MESOS-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343925#comment-15343925
]
Qian Zhang commented on MESOS-5310:
-----------------------------------
The above patches are to introduce 'cni/config' endpoint in agent to support
dynamically adding a new CNI network configuration. However, based on the
discussion with Jie and Avinash, that is not in the scope of MVP, so we will
hold on and may iterate on it later.
As MVP, we'd like to checkpoint CNI network configuration in container dir when
launching the container, and also use it when detaching container, this will
make the container life cycle consistent. Here is the review chain:
https://reviews.apache.org/r/49069/
> Enable `network/cni` isolator to allow modifications and deletion of CNI
> config
> -------------------------------------------------------------------------------
>
> 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: Qian Zhang
> Labels: mesosphere
>
> 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)
