From dev-return-43200-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Dec 10 10:59:08 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A819B180627 for ; Mon, 10 Dec 2018 10:59:07 +0100 (CET) Received: (qmail 73692 invoked by uid 500); 10 Dec 2018 09:59:06 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 73680 invoked by uid 99); 10 Dec 2018 09:59:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2018 09:59:06 +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 92A11C035A for ; Mon, 10 Dec 2018 09:59:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.202 X-Spam-Level: X-Spam-Status: No, score=-0.202 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Ulra8rqSYugC for ; Mon, 10 Dec 2018 09:59:04 +0000 (UTC) Received: from mail-pg1-f175.google.com (mail-pg1-f175.google.com [209.85.215.175]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3D40C61110 for ; Mon, 10 Dec 2018 09:59:03 +0000 (UTC) Received: by mail-pg1-f175.google.com with SMTP id w6so4727044pgl.6 for ; Mon, 10 Dec 2018 01:59:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=f0KZHHj4Zq10uybjvdNnh9zjbu56ndeCsQagDSGb5/4=; b=pnJhmt9iSsSyXbFBP2of3JR+RC5CaFHWOJdUoiQxQxTy0oyhzlzhwwNLf5uH/PTNPr GSRvRrb0UpcZz5stPHEpUpbwFJmkPehBKNo0GHpxOOShHloDqolIsB1716sjV/6X59jR +3J/Bi4KozNJ4q4pceJXpeEu0GoeyFqQLoWFoPrJ4PPmO5kpOOq7Nst/xIN4a4b6ykXG QCl11l4CYtrlhV+A6AkUly6z1F6eOs3csGaRi+5rBJ+JnpiZy8WKpDAp+eDxUdv66OMM 7r1JlkF5XpMyM7dBfhyC4AoCugSBD651yKhzXB2Xef5//i15j8nQulnvjGz3weUO14+X M1RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=f0KZHHj4Zq10uybjvdNnh9zjbu56ndeCsQagDSGb5/4=; b=Ivynnv0aomrml730sGLeX2QDDB3A6JokcGI+5XH19YPZPNhzhgVD+DZyuHUn3sN1Ke sY7GXwqntL9Y9edtuhoMJU0q3LVFjCvVvPFFBMDWWrom1UBF9tboGul8o4OH+RqNhgNu ctgGnJzFaZtM4y/9z45izICGlI+muokuk+9IZEhyaZ93ZcwzlhSfjy4TJ29w8UGVgxsI Fwks1FqatAaZyjniSmTKxKYmUw2hY0x1hTRWAonVqU+8SnMYfrgGuJHI9HAEctIT1DmB 5DPZQiZNWUvdP+3YHwUe6q9bfA8mq05V+O1WsXXonaSC0xL+35YfdxdKqY8DJKP9/XLU BBvg== X-Gm-Message-State: AA+aEWaFl0UOaxLlBWF9fKPedy+NA/kar5ieeYXzPcCm2ocFQUVVOuS6 uRdsvGCYxJnarAeDxt+gzUqav1wGy03S4IempOskcwbMbA92ag== X-Google-Smtp-Source: AFSGD/WvKun5Zu2iogonIeCOvGQSmhsEoUYz6FOw5qBH4YJ+buvRMWtu0uRAAs030yi0r9bKj6Ws+9CBm5KJvAaqjYU= X-Received: by 2002:a63:2507:: with SMTP id l7mr9916540pgl.22.1544435941301; Mon, 10 Dec 2018 01:59:01 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Vyacheslav Daradur Date: Mon, 10 Dec 2018 12:58:48 +0300 Message-ID: Subject: Re: Ignite cloud readiness and as a managed service To: dev@ignite.apache.org Content-Type: text/plain; charset="UTF-8" From my point of view, it's important to further develop the thin client. Users should be able to use most of Ignite's components via thin client, as far as possible, just for example: * transactional CRUD operations over data in the cluster; * deploy/undeploy and monitor services in the Service Grid; * run and manage the compute tasks; * work with ML component; * data streaming and so on... The thin client allows end-user to place application and Ignite cluster in a different environment and avoid impact on cluster's topology. On Fri, Dec 7, 2018 at 11:24 PM Denis Magda wrote: > > Igniters, > > Presently, there are no any doubts that the private/public cloud > deployments would be dominating soon. Personally, I already see even > conservative companies moving from on-prem to clouds. That migration is > impossible w/o essential support and integrations with tools/environments > like Kubernetes, Docker, AWS, Azure, OpenShift, VMWare to name few. > > Luckily, Ignite is pretty well-equipped at the moment. However, there are > some gaps which I would encourage us to highlight. What should the > community do to make Ignite 100% ready for cloud deployments the next year? > For instance, that's my list of gaps: > > - Pivotal Cloud Foundry support > - Helm integration - https://helm.sh > - Prometheus integration - https://prometheus.io > > Moreover, some of the companies moved forward and began using Ignite as a > managed service. There is nothing we can do on the community side except > for listing where Ignite users can get the service, which might be helpful. > I'm thinking to create a webpage that would list all the known solutions > like 2 below. Any recommendations on this? > > - https://www.nexaops.com/managed-services/managed-services-apache-ignite > - https://gridgain.cloud > > -- > Denis -- Best Regards, Vyacheslav D.