You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2016/01/25 19:22:39 UTC

[jira] [Issue Comment Deleted] (AURORA-1052) Populate Labels in TaskConfig

     [ https://issues.apache.org/jira/browse/AURORA-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Erb updated AURORA-1052:
--------------------------------
    Comment: was deleted

(was: I'll try to look into that in a couple of days. 

Idea would be to have a command line flag defaulting to `org.apache.aurora.metadata` that will be used as a prefix for any metadata entry mapped to a label. This prefix could be changed globally by the cluster administrator to `com.myorganization` but could also be set to empty if he wants to leave it up to the user to decide.

What do you think?)

> Populate Labels in TaskConfig
> -----------------------------
>
>                 Key: AURORA-1052
>                 URL: https://issues.apache.org/jira/browse/AURORA-1052
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Stephan Erb
>            Priority: Minor
>              Labels: newbie
>
> Mesos has introduced labels on tasks (MESOS-2120). These correspond to what Aurora calls metadata. 
> We should therefore set task labels according to our metadata information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)