[
https://issues.apache.org/jira/browse/AURORA-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061167#comment-15061167
]
R.B. Boyer commented on AURORA-687:
-----------------------------------
I was going to try it in my simulated VM environment to see if it all works.
MESOS-703 seems to only apply if you are transitioning a preexisting registered
framework to one that has a principal attached. For our one custom framework
we ran into MESOS-703 when moving from the unauthenticated to authenticated
deployment just after launch. This was solvable by just nuking the world and
starting fresh.
So if the same holds true for Aurora then people who start out completely
authenticated will never see this problem, as the framework will
forever-and-always announce with a fixed principal. The only place that will
require a bit of love is in the documentation hinting that folks should really
not turn on mesos authorization without a cluster rebuild or face the wrath of
MESOS-703
> 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)
