[
https://issues.apache.org/jira/browse/MESOS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongqiao Wang updated MESOS-4213:
---------------------------------
Description:
Currently, Mesos uses the following ways to configure role-related objects:
1. For dynamic reserve resources for a role, /reserve endpoint is used to
reserve, another /unreserve endpoint is used to unreserve, maybe the third
endpoint should be added to show resource reservation of a role later due to
someone has issue a requirement of this.
2. For configuring quota for a role, only one endpoint /quota is provided to
set/remove/show quota information.
3. For dynamic weights, only one endpoint /weights will be provided to update
weight;
4. For role information, /roles endpoint is only provided to show role
information contains role name, non-default weight and the registered
frameworks and their allocated resources, and any role will be allowed, subject
to the ACL/authorization system.
We can find that the design between above endpoints are different, so in the
long-run, we like the idea of consistency among these types of endpoints, for
example:
1. Add a new endpoint /reservations to follow the same PUT+DELETE pattern for
reserve+unreserve.
2. Add a new endpoint /volumes to follow the same PUT+DELETE pattern for
create+desgroy.
3. Improve /roles endpoints
4. etc.
> Define a proper RESTful API to keep consistency among role-related
> configuration endpoints
> ------------------------------------------------------------------------------------------
>
> Key: MESOS-4213
> URL: https://issues.apache.org/jira/browse/MESOS-4213
> Project: Mesos
> Issue Type: Epic
> Reporter: Yongqiao Wang
> Assignee: Yongqiao Wang
> Priority: Minor
>
> Currently, Mesos uses the following ways to configure role-related objects:
> 1. For dynamic reserve resources for a role, /reserve endpoint is used to
> reserve, another /unreserve endpoint is used to unreserve, maybe the third
> endpoint should be added to show resource reservation of a role later due to
> someone has issue a requirement of this.
> 2. For configuring quota for a role, only one endpoint /quota is provided to
> set/remove/show quota information.
> 3. For dynamic weights, only one endpoint /weights will be provided to update
> weight;
> 4. For role information, /roles endpoint is only provided to show role
> information contains role name, non-default weight and the registered
> frameworks and their allocated resources, and any role will be allowed,
> subject to the ACL/authorization system.
> We can find that the design between above endpoints are different, so in the
> long-run, we like the idea of consistency among these types of endpoints, for
> example:
> 1. Add a new endpoint /reservations to follow the same PUT+DELETE pattern for
> reserve+unreserve.
> 2. Add a new endpoint /volumes to follow the same PUT+DELETE pattern for
> create+desgroy.
> 3. Improve /roles endpoints
> 4. etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
