[
https://issues.apache.org/jira/browse/MESOS-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000203#comment-14000203
]
Vinod Kone commented on MESOS-1335:
-----------------------------------
+1 a static environment.json sounds like a great idea.
> Make state.json information partially accessible as well as via "text"
> ----------------------------------------------------------------------
>
> Key: MESOS-1335
> URL: https://issues.apache.org/jira/browse/MESOS-1335
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Reporter: Tobias Weingartner
> Priority: Minor
>
> The information returned by {{http://localhost:5051/slave(1)/state.json}} is
> rather volumous, especially if you're trying to do certain simple things like
> knowing which version of a slave happens to be running.
> Possible improvement, allow to address portions of the endpoint:
> {noformat}
> curl -s 'localhost:5051/slave(1)/state/version.json'
> curl -s 'localhost:5051/slave(1)/state/attributes.txt'
> {noformat}
> The above would return something like:
> {noformat}
> {"version": "0.18.0"}
> {noformat}
> {noformat}
> /attributes/host some-hostname
> /attributes/rack some-other-rack
> /attributes/attr-name attr-value
> {noformat}
> Possibly an interim solution to the volume of data would be pull out certain
> information into another endpoint (something like stats.json, maybe
> version.json or environment.json?). In particular, the keys I'd be looking
> for would be:
> {noformat}
> attributes
> flags
> build_*
> hostname
> id
> log_dir
> master_hostname
> pid
> resources
> start_time
> version
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
