Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A705D200CED for ; Fri, 18 Aug 2017 19:21:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A56B416B06A; Fri, 18 Aug 2017 17:21:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EB0A8169C4B for ; Fri, 18 Aug 2017 19:21:07 +0200 (CEST) Received: (qmail 96415 invoked by uid 500); 18 Aug 2017 17:21:05 -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 96400 invoked by uid 99); 18 Aug 2017 17:21:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Aug 2017 17:21:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B9E6F180643 for ; Fri, 18 Aug 2017 17:21:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.085 X-Spam-Level: *** X-Spam-Status: No, score=3.085 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Hw24eV3GnpVa for ; Fri, 18 Aug 2017 17:21:03 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 7F18260D02 for ; Fri, 18 Aug 2017 17:21:02 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id EBEB35D53BB1C for ; Fri, 18 Aug 2017 10:21:01 -0700 (MST) Date: Fri, 18 Aug 2017 10:18:51 -0700 (PDT) From: Alexey Dmitriev To: dev@ignite.apache.org Message-ID: <1503076731467-21066.post@n4.nabble.com> In-Reply-To: References: <3B2BD029-1490-4A8C-94F5-EF54FB291E99@apache.org> Subject: Re: Cluster auto activation design proposal MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 18 Aug 2017 17:21:08 -0000 API is proposed in the head of the thread by Sergey, as I understood: ______________________________________________________ API for BaselineTopology manipulation may look like this: *Ignite::activation::establishBaselineTopology();* *Ignite::activation::establishBaselineTopology(BaselineTopology bltTop);* Both methods will establish BT and activate cluster once it is established. The first one allows user to establish BT using current topology. If any changes happen to the topology during establishing process, user will be notified and allowed to proceed or abort the procedure. Second method allows to use some monitoring'n'management tools like WebConsole where user can prepare a list of nodes, using them create a BT and send to the cluster a command to finally establish it. From high level BaselineTopology entity contains only collection of nodes: *BaselineTopology {* * Collection nodes;* *}* *TopologyNode* here contains information about node - its consistent id and set of user attributes used to calculate affinity function. ____________________________________________ -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cluster-auto-activation-design-proposal-tp20295p21066.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.