mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Clemmer (JIRA)" <>
Subject [jira] [Updated] (MESOS-3098) Implement WindowsContainerizer and WindowsDockerContainerizer
Date Sun, 04 Dec 2016 21:41:58 GMT


Alex Clemmer updated MESOS-3098:
    Labels: mesosphere microsoft  (was: mesosphere)

> Implement WindowsContainerizer and WindowsDockerContainerizer
> -------------------------------------------------------------
>                 Key: MESOS-3098
>                 URL:
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>            Reporter: Joseph Wu
>            Assignee: Alex Clemmer
>              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,
> * 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

View raw message