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 17C42200D54 for ; Fri, 8 Dec 2017 15:19:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 160B3160C0D; Fri, 8 Dec 2017 14:19:31 +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 344F8160BF2 for ; Fri, 8 Dec 2017 15:19:30 +0100 (CET) Received: (qmail 22545 invoked by uid 500); 8 Dec 2017 14:19:29 -0000 Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list dev@nifi.apache.org Received: (qmail 22506 invoked by uid 99); 8 Dec 2017 14:19:28 -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, 08 Dec 2017 14:19:28 +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 865981806C0 for ; Fri, 8 Dec 2017 14:19:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.901 X-Spam-Level: X-Spam-Status: No, score=-2.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eby6baaKfM8K for ; Fri, 8 Dec 2017 14:19:26 +0000 (UTC) Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com [209.85.128.182]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6BCC55F2AB for ; Fri, 8 Dec 2017 14:19:25 +0000 (UTC) Received: by mail-wr0-f182.google.com with SMTP id v22so10978001wrb.0 for ; Fri, 08 Dec 2017 06:19:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=yvHESTOcc5hfoUnZQsYfz3932C7j+zk7nTVDRaLfris=; b=MpZb3G9bGStNQfhPh6wMNua63UcBtW4nlptBZjoN5PIfZN/qAafD/6u2OPfvs2hXXA I2rtw4W/qnfx1a86cz6Bd6iMXFuEhVY2IZchifT3d/5nhHDVWKo0k1nFkdl92RxxOe6D e4qfx49Nvp6RuuvwnSLCAUEOxkGRvKHXm49w94lKg1S0eBimDpR+vlZzLjiCFKpC49Cd 492UVB3PpQJtdUgbpBBipCU6auS6nHaEnCciY2OHcQN0Bba4DFHiS3yh40MQFX07Y3Ri y0qFfp7PrnYkbhzj0wUbSLO/sENheJxUVke+ASKm74CcZpPc7+6QKyhcvgf7jPqeargl Nafw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=yvHESTOcc5hfoUnZQsYfz3932C7j+zk7nTVDRaLfris=; b=KO0l4C4lYR8shDYbicuDjISK+uiiz3E+ybeWL2U8Bh/UNcpjLY2AIrCTQIvPU5OO62 SaEtVYZ2DNAU3teT+mArd1esNwN8bXM21KF92gPiM5njv1F0+b/o2mwI1KTSs9ZByI5Y D2l01YFhi/tjb5eHxG9euN7SpwTEVDkc6MMIkfpEKaUpUlC6++dc4pXD13bGXMEAFvIx dEqPlPo8ZzTJQIn094pyx1CkRz9qF/nk26maQMiUbk2pavoK+1iIR/kFyQndxdw1z1iG iEdWA6Pbd4zJhwbeHg94kVAYPAJp0lb00vJ4c9Dr+KY28eb2cMsHY5KoBKnYNklQkJMH wmWQ== X-Gm-Message-State: AKGB3mJJxwsbxy/G2DM/gVzN0H6us4RjLjYDkmVw8Ci6ckGA/VpjBi1T vch5xxsAPiLSGYxtbjfOpJk95nTee9Avnzql9DAKt2gX X-Google-Smtp-Source: AGs4zMZKKKjMn3ToayZ1R7DfliPbpfjpU6FORybPuGkF23Z68exg91VOvQ9htP0Ks1BGkxytY5ne6Ff+yrT0sEhm0qY= X-Received: by 10.223.168.23 with SMTP id l23mr3537301wrc.15.1512742764714; Fri, 08 Dec 2017 06:19:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.163.70 with HTTP; Fri, 8 Dec 2017 06:19:24 -0800 (PST) In-Reply-To: References: From: Bryan Bende Date: Fri, 8 Dec 2017 09:19:24 -0500 Message-ID: Subject: Re: [DISCUSS] First Release of NiFi Registry To: dev@nifi.apache.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable archived-at: Fri, 08 Dec 2017 14:19:31 -0000 Mike, You brought up a good point... documentation is one of the things that still needs to be done. There is some information that might be helpful though... I would suggest reading this Wiki page for the feature proposal of "Configuration Management of Flows" [1]. There is also a JIRA from a few months ago with initial mock ups for the registry UI [2]. As part of the RC I can provide some instructions on how it can be tested with NiFi using PR 2219. Thanks, Bryan [1] https://cwiki.apache.org/confluence/display/NIFI/Configuration+Manageme= nt+of+Flows [2] https://issues.apache.org/jira/browse/NIFIREG-3 On Thu, Dec 7, 2017 at 8:21 PM, Mike Thomsen wrote= : > Is there a good description/detail page somewhere going over the registry= ? > > On Thu, Dec 7, 2017 at 2:06 PM, Pierre Villard > wrote: > >> Strong +1!! >> >> Really impressed by all the work you guys did on the registry stuff. Ver= y >> impatient to use it in official releases! >> >> Le 7 d=C3=A9c. 2017 18:52, "Jeff" a =C3=A9crit : >> >> Bryan, >> >> +1 to getting an initial release of NiFi Registry out to the community. >> Definitely a huge step in the evolution of NiFi! >> >> On Thu, Dec 7, 2017 at 11:29 AM Russell Bateman >> wrote: >> >> > Our down-stream users are excited at the prospect of using this regist= ry >> > capability for their flows. So, we're eager to see it integrated into >> > the earliest NiFi version you can choose (1.5.0?). >> > >> > Russ >> > >> > On 12/07/2017 08:49 AM, Kevin Doran wrote: >> > > Thanks for kicking off this discussion thread, Bryan. >> > > >> > > I support prepping a release of NiFi Registry and making it version >> > 0.1.0 as you propose. >> > > >> > > Thanks! >> > > Kevin >> > > >> > > On 12/7/17, 10:45, "Joe Witt" wrote: >> > > >> > > Bryan - very exciting and awesome. Having experimented with th= e >> > > registry on the JIRAs/PRs you mention I must say this is going = to >> > be a >> > > huge step forward for NiFi! >> > > >> > > Since we'll also be doing a NiFi release soon (1.5.0?) I am hap= py >> to >> > > volunteer to RM that as well if needed. >> > > >> > > Thanks >> > > >> > > On Thu, Dec 7, 2017 at 10:39 AM, Bryan Bende >> > wrote: >> > > > Hey folks, >> > > > >> > > > There has been a lot of great work done on the NiFi Registry = [1] >> > and I >> > > > think we are probably very close to an initial release focuse= d >> on >> > > > storing "versioned flows". >> > > > >> > > > Since NiFi will have a dependency on client code provided by = the >> > > > registry, the first release of the registry would need to occ= ur >> > before >> > > > the first release of NiFi that integrates with it. The work o= n >> the >> > > > NiFi side is being done as part of NIFI-4436, which can be >> > followed >> > > > along on PR 2219 [2]. >> > > > >> > > > Currently nifi-registry master is set to 0.0.1-SNAPSHOT, but = I >> > would >> > > > propose the first release should be 0.1.0. >> > > > >> > > > Let me know if anyone has any thoughts or comments. I'm happ= y >> to >> > act >> > > > as RM if no one else is interested in doing so, and we can st= art >> > the >> > > > process of going through JIRA to see what is left. >> > > > >> > > > Thanks, >> > > > >> > > > Bryan >> > > > >> > > > [1] https://nifi.apache.org/registry.html >> > > > [2] https://github.com/apache/nifi/pull/2219 >> > > >> > > >> > > >> > >> > >>