[
https://issues.apache.org/jira/browse/MESOS-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Klues updated MESOS-7577:
-------------------------------
Target Version/s: 2.1.0
Description:
Once we reach Mesos 2.0, we should completely remove the GPU_RESOURCES
capability and the corresponding {{--filter-gpu-resources}} that controls
whether the allocator honors this capability or not.
It will have been deprecated once support for {{dynamic reservations}},
{{hierarchical roles}}, and {{support for reservations to multiple roles}} has
landed. The JIRA tracking these features as blockers to this ticket are linked
below.
was:
This flag was added as a temporary way to to enable / disable honoring the
GPU_RESOURCES framework capability. We should remove it once we have better
support for achieving the same functionality that the GPU_RESOURCES capability
gives you.
This support relies on dynamic reservations, hierarchical roles, and support
for reservations to multiple roles (an unyet implemented feature). The JIRA
tracking these features as blockers to this ticket are linked below.
> Remove GPU_RESOURCES capability and master flag
> `--filter-gpu-resources={true|false}`
> -------------------------------------------------------------------------------------
>
> Key: MESOS-7577
> URL: https://issues.apache.org/jira/browse/MESOS-7577
> Project: Mesos
> Issue Type: Task
> Components: allocation, gpu
> Reporter: Kevin Klues
>
> Once we reach Mesos 2.0, we should completely remove the GPU_RESOURCES
> capability and the corresponding {{--filter-gpu-resources}} that controls
> whether the allocator honors this capability or not.
> It will have been deprecated once support for {{dynamic reservations}},
> {{hierarchical roles}}, and {{support for reservations to multiple roles}}
> has landed. The JIRA tracking these features as blockers to this ticket are
> linked below.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
