Return-Path: X-Original-To: apmail-reef-dev-archive@minotaur.apache.org Delivered-To: apmail-reef-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84E7C182A7 for ; Thu, 7 Jan 2016 09:14:10 +0000 (UTC) Received: (qmail 6464 invoked by uid 500); 7 Jan 2016 09:14:10 -0000 Delivered-To: apmail-reef-dev-archive@reef.apache.org Received: (qmail 6428 invoked by uid 500); 7 Jan 2016 09:14:10 -0000 Mailing-List: contact dev-help@reef.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@reef.apache.org Delivered-To: mailing list dev@reef.apache.org Received: (qmail 6409 invoked by uid 99); 7 Jan 2016 09:14:10 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jan 2016 09:14:10 +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 B6990C0D31 for ; Thu, 7 Jan 2016 09:14:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id MGgivun0XmlJ for ; Thu, 7 Jan 2016 09:14:03 +0000 (UTC) Received: from mail-yk0-f178.google.com (mail-yk0-f178.google.com [209.85.160.178]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 447292314A for ; Thu, 7 Jan 2016 09:14:02 +0000 (UTC) Received: by mail-yk0-f178.google.com with SMTP id v14so240007604ykd.3 for ; Thu, 07 Jan 2016 01:14:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3b19KQht81rHUg0ZmSkY0gji1s7cbXHWo8wib4/6NEQ=; b=h6CLcOTd3AwaAZidvC65XFja4G2xtdGJda2lIHigWpooElSfdPDUovrHRJdlNMJz7i L+Oc53XXGl2c7Amh/NhX/jA3ALfhVaNkH83bYGz4NUA7myfyGI9uaeeJ2dIuHQMCA/Ia 9Co67SngExLNXICZABHEXuGIVZa+lCcSF1ksH0lA9SuRhfp3eJUwNa8h8sxocGUxYVAc sx+W5TJIHQ36mJ7FOW8A2hNpMSymaFN2XtPGTR+ItRJ/jBvjXKPkW+af3n/6RacErK2u lNgEN+7Gjw6GgW50V2hkWzMhGxHpPsGQ/m3QoP1U0/wA2ZMoEU/KkZ75G8YD+GKeaL4x mrTQ== MIME-Version: 1.0 X-Received: by 10.13.235.82 with SMTP id u79mr85242591ywe.225.1452158041233; Thu, 07 Jan 2016 01:14:01 -0800 (PST) Received: by 10.37.207.201 with HTTP; Thu, 7 Jan 2016 01:14:01 -0800 (PST) In-Reply-To: References: <567D71A9.9020804@weimo.de> <5684DF0D.6090800@weimo.de> <56856560.2000803@weimo.de> Date: Thu, 7 Jan 2016 18:14:01 +0900 Message-ID: Subject: Re: new runtime: stand-alone distributed runtime? From: Byung-Gon Chun To: dev@reef.apache.org Content-Type: multipart/alternative; boundary=94eb2c086ea034a4600528bae43b --94eb2c086ea034a4600528bae43b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks, John. I will assign it to Dongjin, our new intern. -Gon On Mon, Jan 4, 2016 at 1:50 PM, John Yang wrote: > I opened a JIRA: > https://issues.apache.org/jira/browse/REEF-1123 > > Thanks, > John > > On Fri, Jan 1, 2016 at 4:48 PM, Byung-Gon Chun wrote: > > > Thanks for the input, Markus! > > John, can you create an issue regarding the stand-alone distributed > runtime > > and assign it to DongJin? > > > > -Gon > > > > On Fri, Jan 1, 2016 at 4:26 PM, Markus Weimer wrote: > > > > > Great! I think it is time to move the remainder of the design and > > > implementation discussions onto a JIRA? > > > > > > Markus > > > > > > On Thu, Dec 31, 2015 at 4:53 PM, John Yang > wrote: > > > > Cool! Your suggestions sound great. I'll help the intern in > > implementing > > > it. > > > > > > > > Thanks, > > > > John > > > > 2016. 1. 1. =EC=98=A4=EC=A0=84 2:27=EC=97=90 "Markus Weimer" =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1: > > > > > > > >> On 2015-12-31 00:14, John Yang wrote: > > > >> > > > >>> So please allow me to ask some more questions. > > > >>> > > > >> > > > >> Go ahead. But understand that I've not given this nearly as much > > thought > > > >> as you :-) > > > >> > > > >> - In which directory to scp the jars/resources? - /tmp comes to my > > > >>> mind > > > >>> > > > >> > > > >> We could make that configurable, and default to something like > > > >> `./REEF_SSH/` with the same naming scheme as for the local runtime= . > > > >> Using a relative path puts it into the user's $HOME directory for > easy > > > >> access. And using the local runtime's file system layout ensures > that > > in > > > >> the (common) case of NFS-mounted $HOME, we don't produce name > clashes. > > > >> > > > >> Actually, for NFS mounted $HOME, we could even optimize the `scp` > > round > > > >> away. But that is for later stages :) > > > >> > > > >> - How shall we retrieve the Evaluator logs? - Somehow redirect > > > >>> stdout/stderr through the SSH connection to the Driver to be stor= ed > > > >>> on its node > > > >>> > > > >> > > > >> That would put a lot of load on the Driver machine's network > > connection. > > > >> On the plus side, it makes the logs instantly available. > > > >> > > > >> Another alternative, that reverses these benefits, would be to wri= te > > the > > > >> logs local on the Evaluator side, and then scp them to the Driver = at > > the > > > >> end. And from there, we could scp them to the Client after the > Driver > > > >> exits. This has longer waits for the logs to be available, but is > > likely > > > >> more robust and efficient. > > > >> > > > >> - How shall we teach the SSH runtime the available hosts? - Maybe = we > > > >>> allow Tang configuration of List that represent a list of > ip > > > >>> addresses > > > >>> > > > >> > > > >> I'd use a `Set`, as the order likely doesn't matter. We also need = a > > > >> username for the ssh connections. For a first cut, I believe it is > OK > > > >> for us to assume that public keys have been set up for > authentication. > > > >> > > > >> Markus > > > >> > > > > > > > > > > > -- > > Byung-Gon Chun > > > --=20 Byung-Gon Chun --94eb2c086ea034a4600528bae43b--