[
https://issues.apache.org/jira/browse/MESOS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585758#comment-14585758
]
Adam B edited comment on MESOS-2157 at 6/15/15 10:32 AM:
---------------------------------------------------------
[~jdef] Just beware that the initial DisableEndpoints FirewallRule does not
handle nested paths or wildcards, so each endpoint to be disabled must be
explicitly specified, including any with a frameworkId or taskId. So even if
you disable {{/master/frameworks}} those that know a frameworkId can still
access {{/master/frameworks/<frameworkId>}} unless you explicitly disable it.
was (Author: adam-mesos):
[~jdef] Just beware that the initial DisableEndpoints FirewallRule does not
handle nested paths or wildcards, so each endpoint to be disabled must be
explicitly specified, including any with a frameworkId or taskId. So even if
you disable `/master/frameworks` those that know a frameworkId can still access
`/master/frameworks/{frameworkId}` unless you explicitly disable it.
> Add /master/slaves and /master/frameworks/{framework}/tasks/{task} endpoints
> ----------------------------------------------------------------------------
>
> Key: MESOS-2157
> URL: https://issues.apache.org/jira/browse/MESOS-2157
> Project: Mesos
> Issue Type: Task
> Components: master
> Reporter: Niklas Quarfot Nielsen
> Assignee: Alexander Rojas
> Priority: Trivial
> Labels: mesosphere, newbie
>
> master/state.json exports the entire state of the cluster and can, for large
> clusters, become massive (tens of megabytes of JSON).
> Often, a client only need information about subsets of the entire state, for
> example all connected slaves, or information (registration info, tasks, etc)
> belonging to a particular framework.
> We can partition state.json into many smaller endpoints, but for starters,
> being able to get slave information and tasks information per framework would
> be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
