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 5E45D178B6 for ; Sun, 26 Apr 2015 01:36:02 +0000 (UTC) Received: (qmail 33182 invoked by uid 500); 26 Apr 2015 01:36:02 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 33139 invoked by uid 500); 26 Apr 2015 01:36:02 -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 33128 invoked by uid 99); 26 Apr 2015 01:36:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Apr 2015 01:36:02 +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 (athena.apache.org: local policy) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Apr 2015 01:35:54 +0000 Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id AE78043E31 for ; Sun, 26 Apr 2015 01:35:33 +0000 (UTC) Received: (qmail 33099 invoked by uid 99); 26 Apr 2015 01:35:33 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Apr 2015 01:35:33 +0000 Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id CDCF61A0477 for ; Sun, 26 Apr 2015 01:35:32 +0000 (UTC) Received: by oiko83 with SMTP id o83so66352108oik.1 for ; Sat, 25 Apr 2015 18:35:32 -0700 (PDT) X-Gm-Message-State: ALoCoQkhj96dxTU+6X/1BvvEyA8Qtv6vEWwcptyxOTVvqf7YUI3B12VcrVXRbqlb0BceVHTe7Zdb X-Received: by 10.182.29.101 with SMTP id j5mr4605935obh.0.1430012132059; Sat, 25 Apr 2015 18:35:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.190.70 with HTTP; Sat, 25 Apr 2015 18:34:51 -0700 (PDT) In-Reply-To: <20150425195350.GE2826@tpx> References: <20150425025615.GB2826@tpx> <20150425195350.GE2826@tpx> From: Dmitriy Setrakyan Date: Sat, 25 Apr 2015 20:34:51 -0500 Message-ID: Subject: Re: [DISCUSS] Ignite configuration wizards To: "dev@ignite.incubator.apache.org" Content-Type: multipart/alternative; boundary=001a11c200ca280373051496a517 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c200ca280373051496a517 Content-Type: text/plain; charset=UTF-8 On Sat, Apr 25, 2015 at 2:53 PM, Konstantin Boudnik wrote: > On Sat, Apr 25, 2015 at 08:18AM, Dmitriy Setrakyan wrote: > > On Fri, Apr 24, 2015 at 9:56 PM, Konstantin Boudnik > wrote: > > > > > Sounds real good! A question though: when you say 'several docker > files' do > > > you refer to Dockerfile(s) or actual images? As for AIM configuration: > all > > > required in this case is essentially an Ignite configuration file, > right? > > > > > > > I thought that Docker files would be sufficient to deploy in any cloud > > environment. We can also generate configuration files in addition to the > > docker files as well. > > Yeah, docker should work as a deployment media. But I am still unclear: are > you proposing to generate Dockerfiles or the container images? The later > might > be time consuming and tricky in terms of management, etc. Perhaps just > giving > the Dockerfiles would suffice, don't you think? > Yeah, agree. I was thinking docker files and configuration files. Users can take them and deploy them in any environment. > > Cos > > > > On Fri, Apr 24, 2015 at 05:52PM, Nikita Ivanov wrote: > > > > 100% great idea. Additionally to docker files, how about > auto-configuring > > > > AIMs with these settings? > > > > > > > > -- > > > > Nikita Ivanov > > > > > > > > > > > > On Fri, Apr 24, 2015 at 4:34 PM, Dmitriy Setrakyan < > > > dsetrakyan@apache.org> > > > > wrote: > > > > > > > > > Hello everyone, > > > > > > > > > > I have an idea to simplify Ignite configuration via several > web-based > > > > > wizards which will allow to configure Ignite with a few button > clicks. > > > > > > > > > > For example, you should be able to specify all cache configuration > > > > > properties, all persistence properties, streaming, etc. through a > very > > > > > intuitive UI interface. At the end of the process, we could provide > > > several > > > > > docker files which can be easily deployed in any environment. > > > > > > > > > > These wizards can reside as a separate web module under Ignite > repo. > > > > > > > > > > Let this thread be the start of the discussion. > > > > > > > > > > Thoughts? > > > > > > > > > > D. > > > > > > > > > --001a11c200ca280373051496a517--