[
https://issues.apache.org/jira/browse/AURORA-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381910#comment-15381910
]
Stephan Erb commented on AURORA-1734:
-------------------------------------
There are many potential label sources in Mesos: tasks as submitted by the
user, frameworks, slave hooks or master hooks.
The metadata prefix was introduced to mitigate concerns that a user provided
label could collide with label sources set up by operators. For example, if a
user decides to use {{environment}} or {{role}} as a label, this would prevent
us from doing this directly within Aurora in the future.
> Configurable Metadata prefix
> ----------------------------
>
> Key: AURORA-1734
> URL: https://issues.apache.org/jira/browse/AURORA-1734
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Renan DelValle
> Assignee: Renan DelValle
> Priority: Trivial
>
> Currently, a prefix ("org.apache.aurora.metadata.") is injected into the
> metadata key in the scheduler. It would be beneficial to allow users to set
> their own metadata prefix (including an empty string).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
