[ 
https://issues.apache.org/jira/browse/MESOS-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635413#comment-14635413
 ] 

Timothy Chen commented on MESOS-3098:
-------------------------------------

Is the Windows Container API 100% compatiable with the Docker remote API? 
Docker remote API changes from time to time so not sure what's being supported.
But basically DockerContainerizer goes behind the Dockerd to update cgroup 
limits directly, and we need similiar capability from Windows Container API as 
well.
And I think it's good to map out all the calls we make from Mesos -> Docker and 
make sure they are all there, such as logs, kill, remove, ps -a, ideally also 
labels, etc.

> 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: Alex Clemmer
>              Labels: mesosphere
>
> 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.4#6332)

Reply via email to