[
https://issues.apache.org/jira/browse/MESOS-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062535#comment-14062535
]
Benjamin Hindman commented on MESOS-1593:
-----------------------------------------
Thanks for posting the document [~tnachen]!
I'd love to get some feedback from folks about how we might capture multiple
Docker containers for the same task or executor. For example, we could easily
make a task or executor be represented by a 'repeated DockerInfo' field, with
the contract being that each of the Docker containers represented by each
DockerInfo will be started, killed, and cleaned up as a single "atomic" unit
for that task/executor! (We should also consider the semantics if just one of
those Docker containers exits, i.e., restart it? kill everything? etc.)
I think this is worth a discussion up front (even if we don't implement
anything now, it would be nice to be prepared to do something like that in the
future). There might be a more generic "pod" like abstraction that we want to
introduce for DockerInfo or CommandInfo, but motivating it from the Docker
perspective seems valuable since this seems to be a theme for deploying Docker
containers.
> 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)
