[jira] [Updated] (MESOS-5310) Enable `network/cni` isolator to allow modifications and deletion of CNI config
[ https://issues.apache.org/jira/browse/MESOS-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-5310: -- Fix Version/s: (was: 1.0.0) > 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)
[jira] [Updated] (MESOS-5310) Enable `network/cni` isolator to allow modifications and deletion of CNI config
[ https://issues.apache.org/jira/browse/MESOS-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-5310: -- Story Points: 5 (was: 1) > 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)
[jira] [Updated] (MESOS-5310) Enable `network/cni` isolator to allow modifications and deletion of CNI config
[ https://issues.apache.org/jira/browse/MESOS-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avinash Sridharan updated MESOS-5310: - Summary: Enable `network/cni` isolator to allow modifications and deletion of CNI config (was: Enable `network/cni` isolator to load CNI config at runtime. ) > 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)
