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 4F447200C00 for ; Wed, 18 Jan 2017 10:44:47 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4DE26160B53; Wed, 18 Jan 2017 09:44:47 +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 5515A160B3A for ; Wed, 18 Jan 2017 10:44:46 +0100 (CET) Received: (qmail 90148 invoked by uid 500); 18 Jan 2017 09:44:45 -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 90113 invoked by uid 99); 18 Jan 2017 09:44:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2017 09:44:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id DC9B7C00B6 for ; Wed, 18 Jan 2017 09:44:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id izTT5MM55LNJ for ; Wed, 18 Jan 2017 09:44:43 +0000 (UTC) Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 855175FB6A for ; Wed, 18 Jan 2017 09:44:42 +0000 (UTC) Received: by mail-wm0-f54.google.com with SMTP id c85so236795215wmi.1 for ; Wed, 18 Jan 2017 01:44:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=NG4PLGMx5kmDofyN3nI5FmIdYC5IFL6mqCfUYsW6LgA=; b=PGG1CdzudpUgLuwTG65uuzKXocKttzfWeeEmAqeCYt2DfU6JFAbAOUWbdtZvjT64ot JwQVweVPOqdlexQDKmfGmSoyGzjDwCvmfZ+ygwfH6oy76c/SnurO+skNdHpbeuMmEya0 63dq3nouzyi62ya2O+L72rib7RgwddgHsrCf+lIiTOsHo/jGpJdMWjy3apXEXpY51sZj WIsSfq+jswf4l9sUb5fisfp9vTaNpJKINjwNBxrPtuz03mTeiWeOHiSxJl8IQLhgtH/s BREB/nR2uT85yoHjybB2DCxPafpQiP6ioF1JBpZrLIFns6m846bhJd4wCdLPor3bC0/8 ChbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=NG4PLGMx5kmDofyN3nI5FmIdYC5IFL6mqCfUYsW6LgA=; b=HYytab1GE/9tOo4bnVeMKRPf5/7Z5CLgGmv+3t3L4fujw99QpLBkxfRCPqSwywdnnX elaqlkZbnSpiO080PHuVVC/sgjFeEiKSKOHZvIImBP0PvEiwJG5yf8K/yxiXZWsP4RNN wRGQ8I91oIfKDhKgHP/TxikF3wBYLyYxM+gWpWpsQnIINfYh9TE6OMXCm03nElObHZKy Lqg1KZWpr94QRUM+Srj2hiHh9hFxZxu29gi3M6g/8BlRGu1/kSkX6DEFXaubPDkdO5Kk TSbtLXNEzB4IRMfaaI0k2Ch+N0x0iILwQCrYcF88CPdzTDzSfbkigHCU4RU1zYQ6bct0 i/GA== X-Gm-Message-State: AIkVDXJVsK/9zALM61EXIEBDJx4WIN8nUFTNP0ThIUc6eiupLqYJaQne64y/WF2CXqcB5qpgsMbyYdcZE+Uhyw== X-Received: by 10.28.144.66 with SMTP id s63mr20745273wmd.134.1484732681949; Wed, 18 Jan 2017 01:44:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.128.85 with HTTP; Wed, 18 Jan 2017 01:44:41 -0800 (PST) In-Reply-To: References: From: CmingXu Date: Wed, 18 Jan 2017 17:44:41 +0800 Message-ID: Subject: Re: customized IP for health check To: user@mesos.apache.org Content-Type: multipart/alternative; boundary=001a114672d818164105465b44b9 archived-at: Wed, 18 Jan 2017 09:44:47 -0000 --001a114672d818164105465b44b9 Content-Type: text/plain; charset=UTF-8 The framework user have to make sure the IPs assigned unique and accessible within the VLAN. In some cases, framework user want their DB, Cache or Proxy type of apps handled by my framework & mesos, they might also want the app treated as they are deployed as the old way, which have a unique IP for each container. This kind of app is not the only type that my framework support, with BRIDGE driver supported too. On Wed, Jan 18, 2017 at 5:30 PM, Jie Yu wrote: > It's also possible that the IP is not known by the task/framework upfront > (in fact, this is quite common depending on the underlying network driver), > what does your general framework do in this case? > > - Jie > > On Wed, Jan 18, 2017 at 10:26 AM, CmingXu wrote: > >> I am not sure what kind of apps are going to be running on Mesos, what I >> am doing is a general purpose framework kind of like Marathon. >> >> On Wed, Jan 18, 2017 at 5:24 PM, Jie Yu wrote: >> >>> and we don't know if the task listening on all interfaces or not >>> >>> >>> OK, i think that's the reason. Although, i am wondering: the task is >>> already listening on an external IP, why not just listen on 0.0.0.0. Any >>> specific reason this is a concern? Or just because there is no way to >>> configure the listening address of the task? >>> >>> - Jie >>> >>> On Wed, Jan 18, 2017 at 10:17 AM, CmingXu wrote: >>> >>>> To Alex: >>>> Yes, we know the IP upfront, framework user need reserve unique IP for >>>> each task, and we don't know if the task listening on all interfaces or >>>> not, so let the health check on the IP is the best option. >>>> >>>> >>>> >>>> To Jie Yu: >>>> >>>> by DEFAULT_DOMAIN I mean >>>> >>>> *static const string DEFAULT_DOMAIN = "127.0.0.1"* >>>> >>>> in source code src/health-check/health_checker.cpp >>>> >>>> On Wed, Jan 18, 2017 at 4:58 PM, Jie Yu wrote: >>>> >>>>> So you want to use the IP addressed assigned by your macvlan driver to >>>>> do health check? If that's the case, I still don't understand why entering >>>>> the network namespace of the container and use localhost for health check >>>>> does not work (which is what Mesos is doing). >>>>> >>>>> I walked through the Mesos source code and obviously the TCP & HTTP >>>>>> doesn't meet my requirements as DEFAULT_DOMAIN is hard coded >>>>> >>>>> >>>>> What do you mean by DEFAULT_DOMAIN? >>>>> >>>>> - Jie >>>>> >>>>> On Wed, Jan 18, 2017 at 9:54 AM, CmingXu wrote: >>>>> >>>>>> the network I am currently used is USER, and each task was assigned >>>>>> with a unique vLAN IP with the underlaying docker driver is Macvlan. I >>>>>> want my framework user have the ability to define there own >>>>>> HealthChecks with the IP assigned to a specific task. >>>>>> >>>>>> I walked through the Mesos source code and obviously the TCP & HTTP >>>>>> doesn't meet my requirements as DEFAULT_DOMAIN is hard coded, now the >>>>>> only option to be might be health check with COMMAND, but if TCP does >>>>>> support passing IP would be great help. >>>>>> >>>>>> Thanks >>>>>> >>>>>> On Wed, Jan 18, 2017 at 4:40 PM, Jie Yu wrote: >>>>>> > Hi, can you elaborate a bit more on why you need to use an >>>>>> customized IP, >>>>>> > rather than using localhost for health check? >>>>>> > >>>>>> > - Jie >>>>>> > >>>>>> > On Wed, Jan 18, 2017 at 9:19 AM, CmingXu >>>>>> wrote: >>>>>> >> >>>>>> >> Is there any plan we support customized IP when define a health >>>>>> check? >>>>>> >> If true, what's the ETA? >>>>>> >> >>>>>> >> thanks >>>>>> > >>>>>> > >>>>>> >>>>> >>>>> >>>> >>> >> > --001a114672d818164105465b44b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The framework user have to make sure the IPs assigned= unique and accessible within the VLAN.=C2=A0=C2=A0

In some cases, = framework user want their DB, Cache or Proxy type of apps handled by my fra= mework & mesos, they might also want the app treated as they are deploy= ed=C2=A0 as the old way, which have a unique IP for each container.

=
This kind of app is not the only type that my framework support, with= =C2=A0 BRIDGE driver supported too.
On Wed, Jan 18, 2017 at 5:30 PM, Jie Yu <yu= jie.jay@gmail.com> wrote:
<= div dir=3D"ltr">It's also possible that the IP is not known by the task= /framework upfront (in fact, this is quite common depending on the underlyi= ng network driver), what does your general framework do in this case?

- Jie

On Wed, Jan 18, 2017 at 10:26 AM, C= mingXu <cming.xu@gmail.com> wrote:
I am not sure what kind of apps are going to= be running on Mesos, what I am doing is a general purpose framework kind o= f like Marathon.

On Wed, Jan 18, 2017 at 5:24 PM, Jie Yu = <yujie.jay@gmai= l.com> wrote:
and we don't know if the task listening on all interf= aces or not

OK, i think that&= #39;s the reason. Although, i am wondering: the task is already listening o= n an external IP, why not just listen on 0.0.0.0. Any specific reason this = is a concern? Or just because there is no way to configure the listening ad= dress of the task?

- Jie

On Wed, Jan 18, 2017 at 10:= 17 AM, CmingXu <cming.xu@gmail.com> wrote:
To Alex:
Yes, we know the IP upfront,= framework user need reserve unique IP for each task, and we don't know= if the task listening on all interfaces or not, so let the health check on= the IP is the best option.



To Jie Yu:

by DEFAULT_DOM= AIN I mean

static const string DEFAULT_DOMAIN =3D "127.0.0.1= "

in source code src/health-check/health_checker.cpp

On Wed, Jan 18, 2017 at 4:58 PM, Jie Yu <yujie.jay@gmail.com&= gt; wrote:
So you= want to use the IP addressed assigned by your macvlan driver to do health = check? If that's the case, I still don't understand why entering th= e network namespace of the container and use localhost for health check doe= s not work (which is what Mesos is doing).

I wa= lked through the Mesos source code and obviously the TCP & HTTP
doesn't meet my requirements as DEF= AULT_DOMAIN is hard coded

Wha= t do you mean by DEFAULT_DOMAIN?

- Jie=C2=A0

On Wed, J= an 18, 2017 at 9:54 AM, CmingXu <cming.xu@gmail.com> wrote:=
= the network I am currently used is USER, and each task was assigned
with a unique vLAN IP with the underlaying docker driver is Macvlan. I
want my framework user have the ability to define there own
HealthChecks with the IP assigned to a specific task.

I walked through the Mesos source code and obviously the TCP & HTTP
doesn't meet my requirements as DEFAULT_DOMAIN is hard coded, now the only option to be might be health check with COMMAND, but if TCP does
support passing IP would be great help.

Thanks

On Wed, Jan 18, 2017 at 4:40 PM, Jie Yu <yujie.jay@gmail.com> wrote:
> Hi, can you elaborate a bit more on why you need to use an customized = IP,
> rather than using localhost for health check?
>
> - Jie
>
> On Wed, Jan 18, 2017 at 9:19 AM, CmingXu <cming.xu@gmail.com> wrote:
>>
>> Is there any plan we support customized IP when define a health ch= eck?
>> If true, what's the ETA?
>>
>> thanks
>
>






--001a114672d818164105465b44b9--