[
https://issues.apache.org/jira/browse/MESOS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104941#comment-15104941
]
chenqiang edited comment on MESOS-4213 at 1/18/16 9:05 AM:
-----------------------------------------------------------
Suggest to add another additional RestAPI /framework to get framework info.
In the response payload should contain the resources of
allocated/available/totals for certain type framework.
There another case that one certain framework may have some roles. e.g,
marathon would work as marathon_role1, marathon_role2 as long as user set
different roles for them. So, if we want to get resource metrics for marathon,
it should accumulate all kinds of roles.
was (Author: chenqiang):
Suggest to add another additional RestAPI /framework to get framework info.
In the response payload should contain the resources of
allocated/available/totals for certain type framework.
> 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)
