When a scheduler registers or re-registers with the master, `MasterInfo` is provided as the callback. This includes the version information which can be used to determine which capabilities a Master has. This is admittedly not great; there is a ticket to introduce Master capabilities and include them in MasterInfo. https://issues.apache.org/jira/browse/MESOS-5675
On Wed, Jul 5, 2017 at 3:58 AM, Tomek Janiszewski <jani...@gmail.com> wrote: > Here is the context of this problem https://github.com/ > mesosphere/marathon/pull/5406#discussion_r125454193 > I want to backport support for Mesos HealthChecks to Marathon 1.3. How can > I ensure that Mesos supports HTTP/TCP healthchecks form Marathon > perspective? > > wt., 4 lip 2017 o 17:56 użytkownik Tomek Janiszewski <jani...@gmail.com> > napisał: > >> Hi >> >> Mesos allows frameworks to declare it's abilities. How can I get Mesos >> capabilities from framework perspective? >> >> For example, I'm developing a framework that would use Mesos >> Healthchecks. How can I determine if Mesos version support it. I think it >> should be a part of subscription response. Currently I need to query Mesos >> API after subscription to get Mesos version and configuration. What is the >> best practice to do this? >> >> Thanks >> Tomek >> >
