[
https://issues.apache.org/jira/browse/MESOS-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avinash Sridharan updated MESOS-5310:
-------------------------------------
Comment: was deleted
(was: I am not sure a single end point serve any purpose here. The endpoints
need to be canonical since the operator would want to rebootstrap each of these
entities (isolators) individually (there is no dependency between them. This
implies that if we have a single end point something will have route the
requests to right isolator (probably the `MesosContainerizer`), which will
automatically happen if at the `libprocess` level if we separate end points for
each 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
> 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)
