You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Andrew Schwartzmeyer (JIRA)" <ji...@apache.org> on 2018/02/10 00:10:00 UTC
[jira] [Assigned] (MESOS-3094) Mesos on Windows
[ https://issues.apache.org/jira/browse/MESOS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Schwartzmeyer reassigned MESOS-3094:
-------------------------------------------
Resolution: Fixed
Assignee: Andrew Schwartzmeyer (was: Li Li)
This epic got out of hand. It was originally meant to cover porting the Mesos containerizer to Windows, but ended up being used like a "windows" label.
We've triaged all remaining unresolved issues, and either moved them to a more appropriate epic, or left them without an epic but labeled appropriately.
> Mesos on Windows
> ----------------
>
> Key: MESOS-3094
> URL: https://issues.apache.org/jira/browse/MESOS-3094
> Project: Mesos
> Issue Type: Epic
> Components: containerization, libprocess, stout
> Reporter: Joseph Wu
> Assignee: Andrew Schwartzmeyer
> Priority: Major
> Labels: mesosphere
>
> The ultimate goal of this is to have all containerizer tests running and passing on Windows Server.
> # It must build (see MESOS-898).
> # All OS-specific code (that is touched by the containerizer) must be ported to Windows.
> # The containizer itself must be ported to Windows, alongside the MesosContainerizer.
> Note: Isolation (cgroups) will probably not exist on Windows.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)