Return-Path: X-Original-To: apmail-mesos-dev-archive@www.apache.org Delivered-To: apmail-mesos-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 601DF10A0A for ; Wed, 25 Feb 2015 05:35:06 +0000 (UTC) Received: (qmail 2904 invoked by uid 500); 25 Feb 2015 05:35:06 -0000 Delivered-To: apmail-mesos-dev-archive@mesos.apache.org Received: (qmail 2841 invoked by uid 500); 25 Feb 2015 05:35:06 -0000 Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list dev@mesos.apache.org Received: (qmail 2825 invoked by uid 99); 25 Feb 2015 05:35:05 -0000 Received: from reviews-vm.apache.org (HELO reviews.apache.org) (140.211.11.40) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2015 05:35:05 +0000 Received: from reviews.apache.org (localhost [127.0.0.1]) by reviews.apache.org (Postfix) with ESMTP id 87F7A1D3194; Wed, 25 Feb 2015 05:35:03 +0000 (UTC) Content-Type: multipart/alternative; boundary="===============8072889406956649887==" MIME-Version: 1.0 Subject: Re: Review Request 31390: Added discovery info documentation. From: "Christos Kozyrakis" To: "Niklas Nielsen" , "Connor Doyle" Cc: "Christos Kozyrakis" , "mesos" Date: Wed, 25 Feb 2015 05:35:03 -0000 Message-ID: <20150225053503.4174.48420@reviews.apache.org> X-ReviewBoard-URL: https://reviews.apache.org/ Auto-Submitted: auto-generated Sender: "Christos Kozyrakis" X-ReviewGroup: mesos X-ReviewRequest-URL: https://reviews.apache.org/r/31390/ X-Sender: "Christos Kozyrakis" References: <20150225031810.4174.45250@reviews.apache.org> In-Reply-To: <20150225031810.4174.45250@reviews.apache.org> Reply-To: "Christos Kozyrakis" X-ReviewRequest-Repository: mesos --===============8072889406956649887== MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit > On Feb. 24, 2015, 7:18 p.m., Connor Doyle wrote: > > docs/app-framework-development-guide.md, line 270 > > > > > > Would you like to expand on the meaning of discoverability here? For example, does this mean that other tasks started by the same scheduler should be able to discover this task? > > > > Similarly, since Mesos doesn't enforce any of the discoverability, should `is not` instead read `should not be`? It will be very difficult to address this issue convincingly because it depends on the service discovery system, the networking setup, and whether Mesos allows you to inspect all running tasks through some endpoints etc. All we are doing here is providing info. What the service discovery system does with this info is largely undefined and out of scope. So for now I will change "is not" to "should not be". - Christos ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/31390/#review73969 ----------------------------------------------------------- On Feb. 24, 2015, 4:22 p.m., Christos Kozyrakis wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/31390/ > ----------------------------------------------------------- > > (Updated Feb. 24, 2015, 4:22 p.m.) > > > Review request for mesos, Connor Doyle and Niklas Nielsen. > > > Bugs: MESOS-2396 > https://issues.apache.org/jira/browse/MESOS-2396 > > > Repository: mesos > > > Description > ------- > > Added discovery info documentation. > > > Diffs > ----- > > docs/app-framework-development-guide.md dd7603d099f7582fa8fe93a4c3daa521b23f6223 > > Diff: https://reviews.apache.org/r/31390/diff/ > > > Testing > ------- > > > Thanks, > > Christos Kozyrakis > > --===============8072889406956649887==--