[
https://issues.apache.org/jira/browse/MESOS-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745493#comment-16745493
]
Benjamin Bannier commented on MESOS-9523:
-----------------------------------------
Linked MESOS-9314 which aims to introduce some primitives we should probably
reuse when implementing the improivement here. See in particular the design doc
linked there.
For this ticket, we wouldn't need all set operations outlined there, but just
enough to implement alternatives like {{cpus:2;mem:512|disk:0.1}}. For that we
would also require a type to express a collection of {{Resource}}s (e.g.,
{{cpus:2;mem:512}}). This currently doesn't exist in the proto level.
[~mzhu] and [~bbannier] will sync next week to figure out the next steps.
> Add per-framework allocatable resources matcher/filter.
> -------------------------------------------------------
>
> Key: MESOS-9523
> URL: https://issues.apache.org/jira/browse/MESOS-9523
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
> Reporter: Meng Zhu
> Assignee: Benjamin Bannier
> Priority: Major
> Labels: mesosphere, storage
>
> Currently, Mesos has a single global flag `min_allocatable_resources` that
> provides some control over the shape of the offer. But, being a global flag,
> finding a one-size-fits-all shape is hard and less than ideal. It will be
> great if frameworks can specify different shapes based on their needs.
> In addition to extending this flag to be per-framework. It is also a good
> opportunity to see if it can be more than `min_alloctable` e.g. providing
> more predicates such as max, (not) contain and etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
