[
https://issues.apache.org/jira/browse/MESOS-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046150#comment-15046150
]
Yong Qiao Wang commented on MESOS-3944:
---------------------------------------
Good points! I have the same concern before designing the DR(Dynamic Roles),
but currently, in DR, we need to persist RoleInfo, so it is needed now. For
ACLs, role is just one of objects of ACLs, and ACLs can also be configured for
user and framework_principle, so I think it does not make sence to include it
into RoleInfo. For Quota, Can you have a talk with Alexander(Owner of quota
support)? I think like quota and resource reservation, they are heavy
configuration for role, they can be managed by a separated project, but like
weight and grace period, they are light configuration for role, it is no need
to add a separated endpoints for their management, we can add them into
RoleInfo, and manage them with /roles endpoint.
> Move RoleInfo message out of allocator.proto
> ---------------------------------------------
>
> Key: MESOS-3944
> URL: https://issues.apache.org/jira/browse/MESOS-3944
> Project: Mesos
> Issue Type: Task
> Reporter: Yong Qiao Wang
> Assignee: Yong Qiao Wang
>
> Currently role protobuf is defined in allocator.proto, we will move it out
> and define role protobuf in a separated package, and this protobuf message
> will as internal representation for role related information (e.g. for
> persisting role).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
