Return-Path: X-Original-To: apmail-incubator-giraph-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-giraph-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 1875898B6 for ; Thu, 5 Apr 2012 04:52:14 +0000 (UTC) Received: (qmail 43653 invoked by uid 500); 5 Apr 2012 04:52:13 -0000 Delivered-To: apmail-incubator-giraph-dev-archive@incubator.apache.org Received: (qmail 43616 invoked by uid 500); 5 Apr 2012 04:52:13 -0000 Mailing-List: contact giraph-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: giraph-dev@incubator.apache.org Delivered-To: mailing list giraph-dev@incubator.apache.org Received: (qmail 43604 invoked by uid 99); 5 Apr 2012 04:52:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 04:52:13 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jghoman@gmail.com designates 209.85.212.177 as permitted sender) Received: from [209.85.212.177] (HELO mail-wi0-f177.google.com) (209.85.212.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 04:52:05 +0000 Received: by wibhj13 with SMTP id hj13so713311wib.0 for ; Wed, 04 Apr 2012 21:51:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=SGG0H1KSq/aO/vxwsITF9cQXmQ4QfVdL2TeZJCsbXH0=; b=h1Uyr8fzYfoalDxcCP2AEEIHZzSKqbvFL/cURsZlGCFCm5FUhrxmsC65yqkLIZWMMi bX4fP25PNFnGjD8FCgenP/tRPztsdX+G2ni4elUid7HEV71AQRPkTa8FTQ/qDh3ci+Ba S5NGsp1H3VOf+yikjLRm5eiwDpsGxqLbK+zpp3P9lcXhJgWOgx5TQcTPhXNt5bvLRRzY CKxcU2O916WZt+msIHyjsgaJND/FNZBVOe/wAPmc3VMzXmmMq4Vpm6x/6idrE4H9Dh36 zO0aoV1SbabFuLITkKKaWK4etR6TWA64GDZgShqemP7Y67RK5t73RvwCb4O5GJgHNKTL AyJQ== Received: by 10.216.131.34 with SMTP id l34mr741688wei.54.1333601505521; Wed, 04 Apr 2012 21:51:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.94.163 with HTTP; Wed, 4 Apr 2012 21:51:15 -0700 (PDT) In-Reply-To: <4F7D2306.6020600@apache.org> References: <4F7D1FE8.6050708@googlemail.com> <4F7D2306.6020600@apache.org> From: Jakob Homan Date: Wed, 4 Apr 2012 21:51:15 -0700 Message-ID: Subject: Re: Giraph as Whirr service, see WHIRR-530 To: giraph-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This is interesting. Whirr can already spin up Hadoop MR clusters, which can then run the Giraph jobs. Once Giraph is bootstrapped onto YARN, this will make more sense as a Whirr service. On Wed, Apr 4, 2012 at 9:43 PM, Avery Ching wrote: > I don't use Whirr...I haven't heard it mentioned on this forum yet. =A0An= yone? > > Avery > > > On 4/4/12 9:30 PM, Paolo Castagna wrote: >> >> Hi, >> seen this? >> >> =A0 WHIRR-530 - Add Giraph as a service >> =A0 https://issues.apache.org/jira/browse/WHIRR-530 >> >> This could be quite useful for users who want to give Giraph a spin on >> cloud >> infrastructure, just for testing or to run a few small experiments. >> My experience with Whirr an small 10-20 nodes clusters has be quite >> positive. >> Less so for larger clusters, but it more a problem/limit with the cloud >> provider rather than Whirr itself. I think. >> >> Whirr makes extremely easy and pleasant deploy stuff on-demand. >> >> ... and Whirr already supports YARN: >> https://issues.apache.org/jira/browse/WHIRR-391 >> >> Is any Giraph developers/users here also a Whirr user? >> >> Paolo > >