[MESOS-3098] Implement WindowsContainerizer and WindowsDockerContainerizer

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Won't Do
• Component/s: containerization
• Labels: mesosphere microsoft
• Epic Link: windows
• Story Points: 13
• Assignee: Joseph Wu
• Reporter: Joseph Wu
• Created: 20/Jul/15 22:44
• Updated: 26/Nov/18 12:54
• Resolved: 26/Nov/18 12:54

Description

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(Alex Clemmer): 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.

Issue Links

• is blocked by: MESOS-898 Introduce CMake as an alternative build system.