[
https://issues.apache.org/jira/browse/MESOS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962083#comment-14962083
]
Vinod Kone commented on MESOS-3735:
-----------------------------------
We could include the agent binary version in the /slaves endpoint. The endpoint
already has all the pertinent information about a slave, so sticking a version
seems reasonable. Looks like this needs an update to "summarize(const Slave&
slave)" in master/http.cpp. Once the agent speaks HTTP with the master, we
could figure out how to expose the agent's API version as well.
For schedulers, currently master doesn't know the libmesos version used by the
scheduler. Since we are in the process of moving away from libmesos, it makes
sense to only think about exposing the API version used by registered
schedulers. This also needs adding a "/frameworks" endpoint.
> Mesos master should expose the version of registered agents/schedulers
> -----------------------------------------------------------------------
>
> Key: MESOS-3735
> URL: https://issues.apache.org/jira/browse/MESOS-3735
> Project: Mesos
> Issue Type: Improvement
> Reporter: Vinod Kone
> Assignee: Guangya Liu
>
> Currently Mesos master doesn't expose the (release and API) version
> information of clients (agents and schedulers) registered with it. It would
> be useful to have this information in the WebUI and in an HTTP endpoint. The
> latter would be especially useful during deploys/upgrades.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
