[
https://issues.apache.org/jira/browse/AURORA-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061190#comment-15061190
]
Zameer Manji commented on AURORA-687:
-------------------------------------
I'm a little conflicted here. I think enabling it by default and avoiding
MESOS-703 is a good new user experience. As an operator of an existing cluster
and user of Aurora, I would be displeased if an upgrade just caused the
scheduler to fail because the default was not maintained between releases.
Perhaps the next release should maintain the default and WARN if it is unset
and the release after that should make the flag mandatory?
> Aurora should set FrameworkInfo.principal
> -----------------------------------------
>
> Key: AURORA-687
> URL: https://issues.apache.org/jira/browse/AURORA-687
> Project: Aurora
> Issue Type: Task
> Reporter: Zameer Manji
> Priority: Minor
>
> The principal field has been in FrameworkInfo since 0.19. In 0.20 it will be
> used for authorization and rate limiting. We should set this field so we can
> use those features.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
