[
https://issues.apache.org/jira/browse/MESOS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507947#comment-14507947
]
Adam B commented on MESOS-2644:
-------------------------------
Note that the Mesos master may have a different Mesos version than its slaves
(some could be +1, some -1), and also different than the libmesos used by
individual schedulers and executors. This ticket is just about the Mesos master
version, since that's what the framework scheduler will be communicating with.
However, the 0.23 Mesos master might support persistent volumes, while some
0.22 slaves still do not. It would be difficult to convey to the framework that
offers from some slaves can be used to create persistent volumes while others
cannot.
At least having a /master/version (and /slave/version ?) endpoint would help.
Another near-term alternative would be to embed the version in the
FrameworkRe[re]gisteredMessage, which would be superceded by embedding the
sender's version in all messages.
> AS a framework developer I WANT to check and depend on a Mesos (master)
> version
> -------------------------------------------------------------------------------
>
> Key: MESOS-2644
> URL: https://issues.apache.org/jira/browse/MESOS-2644
> Project: Mesos
> Issue Type: Story
> Components: framework
> Affects Versions: 0.22.0
> Reporter: Aaron Bell
> Labels: mesosphere
>
> Example: I'm developing a framework that makes use of persistent volumes,
> MESOS-1554. At startup I want my scheduler to verify the Mesos master's
> version and abort if it's less than e.g. {{0.23.0}}, which I know is the
> minimum version for that feature.
> I've looked at MESOS-753 and MESOS-986 and they don't seem to address this
> cleanly.
> Version may be available in {{state.json}}, but this is an unboundedly large
> value to parse. It would seem sensible to have an HTTP endpoint {{/version}}
> or similar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
