[
https://issues.apache.org/jira/browse/MESOS-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744338#comment-16744338
]
Meng Zhu commented on MESOS-9523:
---------------------------------
[~jdef] we do not have a design doc. But there has bee some discussion. For
example, you can find this mailing list discussion from [~bmahler] regarding
"matcher" (the second point):
https://lists.apache.org/thread.html/93bd3bf4000d606f88d5c4f390ab628764399007186c025eccd39880@%3Cdev.mesos.apache.org%3E
While I mentioned the potential of doing more than `min`, I agree that we
should be mindful of the complexities (both for Mesos as well as for the user
mental model). Maybe we can implement min only but keep the API extensible?
Just want to make sure we consider these aspects.
> 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)
