[
https://issues.apache.org/jira/browse/MESOS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507937#comment-14507937
]
Ben Whitehead commented on MESOS-2644:
--------------------------------------
To extend it a bit further:
As a framework developer I WANT Mesos to enforce version compatibility at
framework registration/reregistration time.
This is something I would love to have that mimics the Android and iOS app
stores where I can't even install something that is incompatible with my
device's software version. In Mesos it'd be great if my framework was prevented
from registering if it wasn't compatible with the version of Mesos running.
This will be very helpful for new frameworks that are being developer against
the forthcoming Persistent Volumes and Dynamic Reservation features.
> 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)
