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

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

Sounds good we should chat and try out the Docker API on Windows with Mesos to 
see what we can do.

> 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