You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "brian wickman (JIRA)" <ji...@apache.org> on 2014/06/04 19:09:01 UTC
[jira] [Commented] (AURORA-84) Deprecate the Identity struct
[ https://issues.apache.org/jira/browse/AURORA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017869#comment-14017869 ]
brian wickman commented on AURORA-84:
-------------------------------------
I've thought about this a bit more and I think the right approach here is exactly what Bill suggests, but do the following:
* Remove Identity from JobConfiguration and TaskConfig
* Remove environment/name from TaskConfig and replace with JobKey
* Create a new structure called Principal
* Add optional Principal field to TaskEvent to indicate who initiated the event (empty if it was a transition coordinated by mesos/scheduler.)
This separation would also help with AURORA-506
> Deprecate the Identity struct
> -----------------------------
>
> Key: AURORA-84
> URL: https://issues.apache.org/jira/browse/AURORA-84
> Project: Aurora
> Issue Type: Task
> Components: Client, Scheduler
> Reporter: Bill Farner
>
> The Identity field is nested in several structs, and the {{role}} field it contains is ~always redundant to a field in {{JobKey}}. Consider removing Identity and using (or adding) a non-user-bearing field like JobKey.
> An open question is whether whether {{Identity.user}} should be retained. Most likely yes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)