Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0EBA5200CC2 for ; Wed, 5 Jul 2017 16:47:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0D2031637C0; Wed, 5 Jul 2017 14:47:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 52B741637BD for ; Wed, 5 Jul 2017 16:47:08 +0200 (CEST) Received: (qmail 66821 invoked by uid 500); 5 Jul 2017 14:47:07 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 66812 invoked by uid 99); 5 Jul 2017 14:47:07 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jul 2017 14:47:07 +0000 Received: from mail-yw0-f179.google.com (mail-yw0-f179.google.com [209.85.161.179]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id F041F1A0029 for ; Wed, 5 Jul 2017 14:47:06 +0000 (UTC) Received: by mail-yw0-f179.google.com with SMTP id x125so2673714ywa.0 for ; Wed, 05 Jul 2017 07:47:06 -0700 (PDT) X-Gm-Message-State: AKS2vOzEko31CghJa8Or3agAuPCVKv+gv2wd+mqBygHUM8sXay67soYE Sn0Fd4CB444AtX1rJq6KoXc49gudaToF X-Received: by 10.13.234.143 with SMTP id t137mr35119541ywe.180.1499266026198; Wed, 05 Jul 2017 07:47:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.177.144 with HTTP; Wed, 5 Jul 2017 07:46:35 -0700 (PDT) In-Reply-To: References: From: Vinod Kone Date: Wed, 5 Jul 2017 07:46:35 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: How to detemine Mesos Capabilities? To: user Content-Type: multipart/alternative; boundary="94eb2c0882b0ea73c505539312ed" archived-at: Wed, 05 Jul 2017 14:47:09 -0000 --94eb2c0882b0ea73c505539312ed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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 ca= n > I ensure that Mesos supports HTTP/TCP healthchecks form Marathon > perspective? > > wt., 4 lip 2017 o 17:56 u=C5=BCytkownik Tomek Janiszewski > napisa=C5=82: > >> 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 i= t >> should be a part of subscription response. Currently I need to query Mes= os >> API after subscription to get Mesos version and configuration. What is t= he >> best practice to do this? >> >> Thanks >> Tomek >> > --94eb2c0882b0ea73c505539312ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
When a scheduler registers or re-registers with the master= , `MasterInfo` is provided as the callback. This includes the version infor= mation which can be used to determine which capabilities a Master has. This= is admittedly not great; there is a ticket to introduce Master capabilitie= s and include them in MasterInfo.=C2=A0https://issues.apache.org/jira/browse/MESOS-5675

On Wed, J= ul 5, 2017 at 3:58 AM, Tomek Janiszewski <janiszt@gmail.com>= wrote:
Here is the cont= ext of this problem=C2=A0https://github.com/= mesosphere/marathon/pull/5406#discussion_r125454193
I want to = backport support for Mesos HealthChecks to Marathon 1.3. How can I ensure t= hat Mesos supports HTTP/TCP healthchecks form Marathon perspective?

=
wt., 4 lip 2017 o 17:56=C2=A0u=C5=BCytkownik Tomek Janisze= wski <janiszt@gma= il.com> napisa=C5=82:
Hi

Mesos allows frameworks to declare it'= s abilities. How can I get Mesos capabilities from framework perspective?= =C2=A0

For example, I'm developing a framework= that would use Mesos Healthchecks. How can I determine if Mesos version su= pport 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 config= uration. What is the best practice to do this?

Tha= nks
Tomek

--94eb2c0882b0ea73c505539312ed--