I'd recommend also starting a separate thread about how to approach the
problem of quota more generally, we'd love to know more about what you're
looking for!

On Thu, Dec 18, 2014 at 9:20 AM, Sushant Kumar <[email protected]> wrote:
>
> I will create a JIRA ticket. My motivation is to have a simple quota
> system that is plugged in via authorization module. If there is already
> related work planned around this, could you please point me to the ticket?
>
> Sushant
>
>
>   On Wednesday, December 17, 2014 1:33 PM, Niklas Nielsen <
> [email protected]> wrote:
>
>
> Oh - sorry; you are absolutely right. Did the common mistake of misreading
> authentication/authorization.
> It would definitely be a cool use case for modules; let's create a JIRA
> ticket for it until we have resources to work on it.
>
> Niklas
>
> On 17 December 2014 at 13:23, Sushant Kumar <[email protected]> wrote:
>
> isnt authorization done in a separate module than authenticator?
>
> Sushant
>
>
>   On Wednesday, December 17, 2014 12:58 PM, Niklas Nielsen <
> [email protected]> wrote:
>
>
> Pluggable authenticator modules should land in Mesos 0.22:
> https://issues.apache.org/jira/browse/MESOS-1966
>
> Niklas
>
> On 16 December 2014 at 11:19, Benjamin Mahler <[email protected]>
> wrote:
>
> Sorry for the delay, yes it's possible but I don't think anyone has looked
> at modularizing it. Hopefully others will speak up otherwise!
>
> We have only one authorizer implementation in the code (a LocalAuthorizer
> <https://github.com/apache/mesos/blob/0.21.0/src/authorizer/authorizer.hpp#L64>
> that takes everything up front). Other Authorizers can be added, and it
> could be modularized to allow private custom Authorizer implementations.
>
> Hope this helps,
> Ben
>
> On Thu, Dec 11, 2014 at 9:25 PM, Sushant Kumar <[email protected]>
> wrote:
>
> Hi,
>
> I am looking at the authorization feature as documented here:
> https://github.com/apache/mesos/blob/master/docs/authorization.md.
>
> Is it possible to have a custom module to handle authorization?
>
> Sushant
>
>
>
>
>
>
>

Reply via email to