You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Alexander Rojas <al...@mesosphere.io> on 2015/12/11 10:16:01 UTC
[proposal] Generalized Authorizer Interface
Hi Everyone,
After looking at your comments and doing some extra design we have updated the proposal for the Authorized Interface. Among the main changes is to remove the attributes of all the parameters and making the actions an enum. The full text can be found here:
https://docs.google.com/document/d/1-XARWJFUq0r_TgRHz_472NvLZNjbqE4G8c2JL44OSMQ/edit#heading=h.o4fbpp2hx411 <https://docs.google.com/document/d/1-XARWJFUq0r_TgRHz_472NvLZNjbqE4G8c2JL44OSMQ/edit#heading=h.o4fbpp2hx411>
Among the most recurrent question is how the change will be experience by users (operators and framework developers). So from their perspective, things won’t change unless using custom authorizers, and then only operators will notify one change: the load of the plugin for the custom authorizer.
I would like to listen from you guys on the proposal for recommendations in case we missed something.
Thanks,
Alexander Rojas
Re: [proposal] Generalized Authorizer Interface
Posted by Vinod Kone <vi...@apache.org>.
+modules
On Fri, Dec 11, 2015 at 1:16 AM, Alexander Rojas <al...@mesosphere.io>
wrote:
> Hi Everyone,
>
> After looking at your comments and doing some extra design we have updated
> the proposal for the Authorized Interface. Among the main changes is to
> remove the attributes of all the parameters and making the actions an enum.
> The full text can be found here:
>
>
> https://docs.google.com/document/d/1-XARWJFUq0r_TgRHz_472NvLZNjbqE4G8c2JL44OSMQ/edit#heading=h.o4fbpp2hx411
> <
> https://docs.google.com/document/d/1-XARWJFUq0r_TgRHz_472NvLZNjbqE4G8c2JL44OSMQ/edit#heading=h.o4fbpp2hx411
> >
>
> Among the most recurrent question is how the change will be experience by
> users (operators and framework developers). So from their perspective,
> things won’t change unless using custom authorizers, and then only
> operators will notify one change: the load of the plugin for the custom
> authorizer.
>
> I would like to listen from you guys on the proposal for recommendations
> in case we missed something.
>
> Thanks,
>
> Alexander Rojas
Re: [proposal] Generalized Authorizer Interface
Posted by Vinod Kone <vi...@apache.org>.
+modules
On Fri, Dec 11, 2015 at 1:16 AM, Alexander Rojas <al...@mesosphere.io>
wrote:
> Hi Everyone,
>
> After looking at your comments and doing some extra design we have updated
> the proposal for the Authorized Interface. Among the main changes is to
> remove the attributes of all the parameters and making the actions an enum.
> The full text can be found here:
>
>
> https://docs.google.com/document/d/1-XARWJFUq0r_TgRHz_472NvLZNjbqE4G8c2JL44OSMQ/edit#heading=h.o4fbpp2hx411
> <
> https://docs.google.com/document/d/1-XARWJFUq0r_TgRHz_472NvLZNjbqE4G8c2JL44OSMQ/edit#heading=h.o4fbpp2hx411
> >
>
> Among the most recurrent question is how the change will be experience by
> users (operators and framework developers). So from their perspective,
> things won’t change unless using custom authorizers, and then only
> operators will notify one change: the load of the plugin for the custom
> authorizer.
>
> I would like to listen from you guys on the proposal for recommendations
> in case we missed something.
>
> Thanks,
>
> Alexander Rojas