[ https://issues.apache.org/jira/browse/MESOS-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735650#comment-14735650 ]
Connor Doyle commented on MESOS-3013: ------------------------------------- In the design doc we discussed how this new message might need to be added to {{ExecutorInfo}} as well for backwards compatibility, since the Mesos containerizer doesn't support setting {{ContainerInfo}}. Could you update the title and description to capture that? > Extend ContainerInfo to include "NetworkInfo" message > ----------------------------------------------------- > > Key: MESOS-3013 > URL: https://issues.apache.org/jira/browse/MESOS-3013 > Project: Mesos > Issue Type: Task > Reporter: Kapil Arya > Assignee: Kapil Arya > Labels: mesosphere > > As per the [design > doc|https://docs.google.com/document/d/17mXtAmdAXcNBwp_JfrxmZcQrs7EO6ancSbejrqjLQ0g], > we need to enable frameworks to specify network requirements. The proposed > message could be along the lines of: > {code} > message NetworkInfo { > enum Protocol { > IPv4, > IPv6 > } > required Protocol protocol; > // A netgroup is the name given to a set of logically-related IPs that are > // allowed to communicate within themselves. For example, one might want > // to create separate netgroups for dev, testing, qa and prod deployment > // environments. > repeated string netgroups; > // Sticky IPs allow a framwork to re-launch a task with the same IP on a > // different Slave/Node. > optional bool sticky [default = false]; > // A unique id that the framework uses to "tag" the assigned IP. This "tag" > // can be later used to "reclaim" IP while relaunching the task. > optional string id; > }; > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)