You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dan Osborne (JIRA)" <ji...@apache.org> on 2016/05/18 19:50:13 UTC
[jira] [Updated] (MESOS-5412) Support CNI_ARGS
[ https://issues.apache.org/jira/browse/MESOS-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Osborne updated MESOS-5412:
-------------------------------
Description:
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.
was:
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.
> 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)