Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-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 2DC6D102C3 for ; Tue, 5 May 2015 14:01:12 +0000 (UTC) Received: (qmail 62682 invoked by uid 500); 5 May 2015 14:01:12 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 62634 invoked by uid 500); 5 May 2015 14:01:12 -0000 Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.incubator.apache.org Delivered-To: mailing list dev@ignite.incubator.apache.org Received: (qmail 62623 invoked by uid 99); 5 May 2015 14:01:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 14:01:11 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [54.76.25.247] (HELO mx1-eu-west.apache.org) (54.76.25.247) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 14:00:43 +0000 Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id AA32624E9D for ; Tue, 5 May 2015 14:00:41 +0000 (UTC) Received: (qmail 60989 invoked by uid 99); 5 May 2015 14:00:40 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 14:00:40 +0000 Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5EA2D1A01AB for ; Tue, 5 May 2015 14:00:40 +0000 (UTC) Received: by lbbuc2 with SMTP id uc2so128985857lbb.2 for ; Tue, 05 May 2015 07:00:38 -0700 (PDT) X-Gm-Message-State: ALoCoQnie2EdWCDiRt3mMReTHMlFW2aWnHNopZTAtwlP1KLZ839oUpz/4inJz8RWlrKMWBbft413 MIME-Version: 1.0 X-Received: by 10.152.207.41 with SMTP id lt9mr23787801lac.52.1430834438720; Tue, 05 May 2015 07:00:38 -0700 (PDT) Received: by 10.114.172.174 with HTTP; Tue, 5 May 2015 07:00:38 -0700 (PDT) In-Reply-To: <20150505054709.GA14430@tpx> References: <20150505054709.GA14430@tpx> Date: Tue, 5 May 2015 17:00:38 +0300 Message-ID: Subject: Re: Ignite and Mesos Integration From: Yakov Zhdanov To: dev@ignite.incubator.apache.org Content-Type: multipart/alternative; boundary=001a11345a2873e4310515561a4b X-Virus-Checked: Checked by ClamAV on apache.org --001a11345a2873e4310515561a4b Content-Type: text/plain; charset=UTF-8 Cool idea! --Yakov 2015-05-05 8:47 GMT+03:00 Konstantin Boudnik : > I like the idea. Mesos is real solid hardware resource scheduler, which can > complement Ignite abilities to dynamically scale up and down. > > Having Ignite in a container'ized form should help as well by simplifying > the > deployment of the bits even further. Also, I believe the basic integration > should be simple enough (request more nodes with certain properties) and > go a > long way. > > Here you can see what one can do with Apache Mesos > https://www.youtube.com/watch?v=UgJMlHdZEx4 > > Regards, > Cos > > On Mon, May 04, 2015 at 05:19PM, Dmitriy Setrakyan wrote: > > Igniters, > > > > Does anyone in the community have experience with Apache Mesos? > > > > I have been reading on Mesos architecture and I think Ignite should > > integrate with Mesos. This will add very cool datacenter management > > capabilities to Ignite which will make it easier to manage and maintain. > > > > There are many videos on Mesos available here: > > http://mesos.apache.org/documentation/latest/mesos-presentations/ > > > > Nice architecture description here: > > http://mesos.apache.org/documentation/latest/mesos-architecture/ > > > > Thoughts? > > > > D. > --001a11345a2873e4310515561a4b--