[
https://issues.apache.org/jira/browse/MESOS-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871098#comment-15871098
]
Joseph Wu commented on MESOS-3098:
----------------------------------
{code}
commit 7a6b7c69560178a22be7a6f0990b27556fca2c59
Author: Daniel Pravat <[email protected]>
Date: Wed Feb 15 16:21:39 2017 -0800
Added Windows support for Docker executor.
This commit will introduce the changes to the Mesos Docker interfaces
required to use the Docker executor to run Windows Containers in the
Mesos agent. In particular, since Windows Containers use named pipes to
connect do the Docker host, rather than a socket, we introduce the
plumbing to default to a named pipe connection when invoking the
`docker` command.
This work constitutes the beginning of the end of the work that will
eventually result in Mesos support of Windows Containers.
This review is partially based on r/52364, which was the work of Daniel
Pravat.
Review: https://reviews.apache.org/r/56505/
{code}
> Implement WindowsContainerizer and WindowsDockerContainerizer
> -------------------------------------------------------------
>
> Key: MESOS-3098
> URL: https://issues.apache.org/jira/browse/MESOS-3098
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Reporter: Joseph Wu
> Assignee: Daniel Pravat
> Labels: mesosphere, microsoft
>
> The MVP for Windows support is a containerizer that (1) runs on Windows, and
> (2) runs and passes all the tests that are relevant to the Windows platform
> (_e.g._, not the tests that involve cgroups). To do this we require at least
> a `WindowsContainerizer` (to be implemented alongside the
> `MesosContainerizer`), which provides no meaningful (_e.g._) process
> namespacing (much like the default unix containerizer). In the long term
> (hopefully before MesosCon) we want to support also the Windows container
> API. This will require implementing a separate containerizer, maybe called
> `WindowsDockerContainerizer`.
> Since the Windows container API is actually officially supported through the
> Docker interface (_i.e._, MSFT actually ported the Docker engine to Windows,
> and that is the official API), the interfaces (like the fetcher) shouldn't
> change much. The tests probably will have to change, as we don't have access
> to any isolation primitives like cgroups for those tests.
> Outstanding TODO([~hausdorff]): Flesh out this description when more details
> are available, regarding:
> * The container API for Windows (when we know them)
> * The nuances of Windows vs Linux (when we know them)
> * etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
