[
https://issues.apache.org/jira/browse/MESOS-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083219#comment-14083219
]
Jay Buffington commented on MESOS-1593:
---------------------------------------
[~tnachen] I think you're missing my point. My premise is that changing
default behavior between releases is a bad thing which should be avoided
whenever possible.
My concern is that schedulers that do not specify a network will get host
networking when using the code that includes this change. Once that's shipped,
you should not change the default because it will break schedulers that rely on
it. Instead, make networking required in this change and once we have bridged
you can make it optional with bridged being the default.
> Add DockerInfo Configuration
> ----------------------------
>
> Key: MESOS-1593
> URL: https://issues.apache.org/jira/browse/MESOS-1593
> Project: Mesos
> Issue Type: Task
> Reporter: Timothy Chen
> Assignee: Timothy Chen
>
> We want to add a new proto message to encapsulate all Docker related
> configurations into DockerInfo.
> Here is the document that describes the design for DockerInfo:
> https://github.com/tnachen/mesos/wiki/DockerInfo-design
--
This message was sent by Atlassian JIRA
(v6.2#6252)
