[MESOS-7576] Add master flag `--filter-gpu-resources={true|false}`

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Done
• Affects Version/s: 1.2.0
• Fix Version/s: 1.4.0
• Component/s: gpu
• Target Version/s: 1.4.0
• Assignee: Kevin Klues
• Reporter: Kevin Klues
• Shepherd: Benjamin Mahler
• Created: 26/May/17 21:14
• Updated: 31/May/17 23:24
• Resolved: 31/May/17 23:24

Description

Per the email thread below, we are adding a new flag on the master called --filter-gpu-resources to enable / disable honoring the GPU_RESOURCES framework capability.

https://www.mail-archive.com/[e-mail]/msg37571.html

When set to true, this flag will cause the mesos master to continue to
function as it does today. That is, it will filter offers containing GPU
resources and only send them to frameworks that opt into the GPU_RESOURCES framework capability. When set to false, this flag will cause the master to not filter offers containing GPU resources, and indiscriminately send them to all frameworks whether they set the GPU_RESOURCES capability or not.

This is a temporary flag that will eventually be removed. We will remove it once we have better support for achieving the same functionality that the GPU_RESOURCES capability gives you.

As described in the email, this support relies on dynamic reservations, hierarchical roles, and support for reservations to multiple roles (an unyet implemented feature). The JIRA tracking these features are linked below.

Issue Links

• is related to: MESOS-2018 Dynamic Reservation
• is related to: MESOS-6375 Support hierarchical resource allocation roles.
• is related to: MESOS-7574 Allow reservations to multiple roles.
• relates to: MESOS-7577 Remove GPU_RESOURCES capability and master flag `--filter-gpu-resources={true|false}`
• relates to: MESOS-7579 Deprecate GPU_RESOURCES capability and master flag `--filter-gpu-resources={true|false}`