[jira] [Commented] (MESOS-5412) Support CNI_ARGS
[ https://issues.apache.org/jira/browse/MESOS-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334603#comment-15334603 ] Jie Yu commented on MESOS-5412: --- CNI spec just merged the 'args' support https://github.com/containernetworking/cni/pull/247 We should passing in NetworkInfo to the plugin using 'args' field. > Support CNI_ARGS > > > Key: MESOS-5412 > URL: https://issues.apache.org/jira/browse/MESOS-5412 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Dan Osborne > > Mesos-CNI should support the > [CNI_ARGS|https://github.com/containernetworking/cni/blob/master/SPEC.md#parameters] > field. > This would allow CNI plugins to be able to implement advanced networking > capabilities without needing modifications to Mesos. Current use case I am > facing: Allowing users to specify policy for their CNI plugin. > I'm proposing the following implementation: Pass a task's [NetworkInfo > Labels|https://github.com/apache/mesos/blob/b7e50fe8b20c96cda5546db5f2c2f47bee461edb/include/mesos/mesos.proto#L1732] > to the CNI plugin as CNI_ARGS. CNI args are simply key-value pairs split by > a '=', e.g. "FOO=BAR;ABC=123", which could be easily generated from the > NetworkInfo's key-value labels. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5412) Support CNI_ARGS
[ https://issues.apache.org/jira/browse/MESOS-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304992#comment-15304992 ] Dan Osborne commented on MESOS-5412: [~hartem] Not planning on submitting a patch by then, so feel free to bump this out. I'm no longer convinced that CNI args would be the right place to inject network policy definitions for a Task. Shall we leave this issue open as a backlog item until a more pressing need / more defined use case for CNI_ARGS arises? > Support CNI_ARGS > > > Key: MESOS-5412 > URL: https://issues.apache.org/jira/browse/MESOS-5412 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Dan Osborne > > Mesos-CNI should support the > [CNI_ARGS|https://github.com/containernetworking/cni/blob/master/SPEC.md#parameters] > field. > This would allow CNI plugins to be able to implement advanced networking > capabilities without needing modifications to Mesos. Current use case I am > facing: Allowing users to specify policy for their CNI plugin. > I'm proposing the following implementation: Pass a task's [NetworkInfo > Labels|https://github.com/apache/mesos/blob/b7e50fe8b20c96cda5546db5f2c2f47bee461edb/include/mesos/mesos.proto#L1732] > to the CNI plugin as CNI_ARGS. CNI args are simply key-value pairs split by > a '=', e.g. "FOO=BAR;ABC=123", which could be easily generated from the > NetworkInfo's key-value labels. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5412) Support CNI_ARGS
[ https://issues.apache.org/jira/browse/MESOS-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304855#comment-15304855 ] Artem Harutyunyan commented on MESOS-5412: -- Hey [~djosborne], we will be cutting a release next Monday (05.30.2016). Are you planning on submitting a patch for this? > Support CNI_ARGS > > > Key: MESOS-5412 > URL: https://issues.apache.org/jira/browse/MESOS-5412 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Dan Osborne > > Mesos-CNI should support the > [CNI_ARGS|https://github.com/containernetworking/cni/blob/master/SPEC.md#parameters] > field. > This would allow CNI plugins to be able to implement advanced networking > capabilities without needing modifications to Mesos. Current use case I am > facing: Allowing users to specify policy for their CNI plugin. > I'm proposing the following implementation: Pass a task's [NetworkInfo > Labels|https://github.com/apache/mesos/blob/b7e50fe8b20c96cda5546db5f2c2f47bee461edb/include/mesos/mesos.proto#L1732] > to the CNI plugin as CNI_ARGS. CNI args are simply key-value pairs split by > a '=', e.g. "FOO=BAR;ABC=123", which could be easily generated from the > NetworkInfo's key-value labels. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5412) Support CNI_ARGS
[ https://issues.apache.org/jira/browse/MESOS-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290167#comment-15290167 ] Qian Zhang commented on MESOS-5412: --- [~djosborne], Can you please elaborate what kind of policy you want to specify for the CNI plugin? > Support CNI_ARGS > > > Key: MESOS-5412 > URL: https://issues.apache.org/jira/browse/MESOS-5412 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Dan Osborne > Fix For: 0.29.0 > > > Mesos-CNI should support the > [CNI_ARGS|https://github.com/containernetworking/cni/blob/master/SPEC.md#parameters] > field. > This would allow CNI plugins to be able to implement advanced networking > capabilities without needing modifications to Mesos. Current use case I am > facing: Allowing users to specify policy for their CNI plugin. > I'm proposing the following implementation: Pass a task's [NetworkInfo > Labels|https://github.com/apache/mesos/blob/b7e50fe8b20c96cda5546db5f2c2f47bee461edb/include/mesos/mesos.proto#L1732] > to the CNI plugin as CNI_ARGS. CNI args are simply key-value pairs split by > a '=', e.g. "FOO=BAR;ABC=123", which could be easily generated from the > NetworkInfo's key-value labels. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
