[
https://issues.apache.org/jira/browse/MESOS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507931#comment-14507931
]
Cody Maloney commented on MESOS-2644:
-------------------------------------
We may also want to think about exposing 'feature' flags which schedulers can
depend upon rather than hard version requirements. Could be useful for when a
feature needs to be hot-patched in (Or when working off a fork for testing out
a feature), then lands in a later release.
> AS a framework developer I WANT to check and depend on a Mesos 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
>
> 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)
