[
https://issues.apache.org/jira/browse/MESOS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734027#comment-14734027
]
Chad Heuschober commented on MESOS-3372:
----------------------------------------
Hi Klaus,
To me, it's not the question of whether the data is available but making the
functionality available in a reusable fashion that doesn't require forking or
creating frameworks to implement over and over for each framework. It seems to
me that you're suggesting it is the framework's responsibility to do any of
this work even if it's repeated across multiple frameworks. Is that correct to
say? What made the case to me for this to be in mesos directly was because this
has nothing to do with scheduling -- the above implementation is about
injecting slave attributes into tasks so the specific application workloads can
use those attributes appropriately.
> Allow mesos agent attributes to be tokenized in taskInfo
> --------------------------------------------------------
>
> Key: MESOS-3372
> URL: https://issues.apache.org/jira/browse/MESOS-3372
> Project: Mesos
> Issue Type: Improvement
> Reporter: Chad Heuschober
>
> Some applications workloads would benefit from having access to the
> statically defined slave attributes. By processing `taskInfo` on the slave
> such tokens, as defined in `taskInfo` could be replaced with the appropriate
> values to achieve such objectives as rack locality.
> Example:
> Before token replacement:
> {code}
> {
> "discovery": {
> "environment": "RACK_@MESOS.AGENT.ATTRS.RACK_ID@"
> }
> }
> {code}
> After token replacement:
> {code}
> {
> "discovery": {
> "environment": "RACK_DC131R57"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
