[VOTE] Release Apache NiFi Registry 0.1.0

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release Apache NiFi Registry 0.1.0

Bryan Bende-2
Hello,

I am pleased to be calling this vote for the source release of Apache
NiFi Registry 0.1.0.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1115/

The Git tag is nifi-registry-0.1.0-RC1
The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca

Checksums of nifi-registry-0.1.0-source-release.zip:
MD5: 56244c3c296cdc9c3fcc6d22590b80d1
SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/bbende.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

65 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12340217

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiRegistry0.1.0

The vote will be open for 96 hours.

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.

The please vote:

[ ] +1 Release this package as nifi-registry-0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Joe Witt
+1 (binding) Release this package as nifi-registry-0.1.0

Release verification process
-pull source artifacts
-verify sigs
-verify commit id
-verify commit history reflects latest changes (based off commit id/history)
-verify source README
-verify source L&N and that it is consistent with the work done in
   https://issues.apache.org/jira/browse/NIFIREG-66
-verify build w/contrib check
-verify binary/assembly README
-verify binary/assembly L&N and that it is consistent with work done in
   https://issues.apache.org/jira/browse/NIFIREG-66
-test registry on its own (manual/user testing)
-review registry docs
-setup certificate based secure reg setup/test
- build nifi with registry integration PR
- verify interaction with secure (certs based) nifi/secure registry

Tests
- create empty group
- make local changes / view diffs / go to
- make sure nifi cannot do anything with the registry when its cert
lacks proxy auth
- once proxy auth added all options available
- verify can publish new versions/comments/ensure input is escaped
- change versions on a live flow with and without enqueued data

Observations
- Having a default URL handler to show the 'you may have mistyped'
type page from nifi would be nice
- We should improve the logic of when components are started/stopped
to make version changes.  For position changes only components should
not start/stop
- There are a lot of very cool features to add from here but this is a
pretty awesome first version with a range of excellent security
options/polish.


This is going to be a huge step forward for the community!

Thanks
Joe

On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende <[hidden email]> wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry 0.1.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1115/
>
> The Git tag is nifi-registry-0.1.0-RC1
> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca
>
> Checksums of nifi-registry-0.1.0-source-release.zip:
> MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 65 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12340217
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
>
> The vote will be open for 96 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
>
> The please vote:
>
> [ ] +1 Release this package as nifi-registry-0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Marc Parisi
+1 binding  to release this package as nifi-registry-0.1.0

  verified sigs, commits, readme.

  Ran some basic tests, including validating creating groups, committing
versions, verifying that there was a way to identify that uncommitted
changes existed.

  Ensured that my bucket's flow's change log matched what I actually did in
the NiFi PR.

  Comments:

    Really enjoyed testing this. In my console I saw a 409 ( which I think
Chrome incorrectly identified from the 405 being returned on
http://localhost:18080/nifi-registry-api/access/token/kerberos )

    The only option defined for Kerberos was the expiration. I thought
about creating a minor ticket as I didn't see one in JIRA,  but I assume
that was intended.

    After creating my bucket through settings an encountered
https://issues.apache.org/jira/browse/NIFIREG-88 .

    The issue is likely client side ( hence why I made a minor ticket ) as
I can switch tabs to show settings; however, until I realized this I waited
nearly 2 minutes for settings to show.

    I'm willing to chalk this up to user error or my environment.

    Best Regards,
    Marc

On Thu, Dec 28, 2017 at 3:35 PM, Joe Witt <[hidden email]> wrote:

> +1 (binding) Release this package as nifi-registry-0.1.0
>
> Release verification process
> -pull source artifacts
> -verify sigs
> -verify commit id
> -verify commit history reflects latest changes (based off commit
> id/history)
> -verify source README
> -verify source L&N and that it is consistent with the work done in
>    https://issues.apache.org/jira/browse/NIFIREG-66
> -verify build w/contrib check
> -verify binary/assembly README
> -verify binary/assembly L&N and that it is consistent with work done in
>    https://issues.apache.org/jira/browse/NIFIREG-66
> -test registry on its own (manual/user testing)
> -review registry docs
> -setup certificate based secure reg setup/test
> - build nifi with registry integration PR
> - verify interaction with secure (certs based) nifi/secure registry
>
> Tests
> - create empty group
> - make local changes / view diffs / go to
> - make sure nifi cannot do anything with the registry when its cert
> lacks proxy auth
> - once proxy auth added all options available
> - verify can publish new versions/comments/ensure input is escaped
> - change versions on a live flow with and without enqueued data
>
> Observations
> - Having a default URL handler to show the 'you may have mistyped'
> type page from nifi would be nice
> - We should improve the logic of when components are started/stopped
> to make version changes.  For position changes only components should
> not start/stop
> - There are a lot of very cool features to add from here but this is a
> pretty awesome first version with a range of excellent security
> options/polish.
>
>
> This is going to be a huge step forward for the community!
>
> Thanks
> Joe
>
> On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende <[hidden email]> wrote:
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry 0.1.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> >
> > The Git tag is nifi-registry-0.1.0-RC1
> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> 81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> > Checksums of nifi-registry-0.1.0-source-release.zip:
> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 65 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320920&version=12340217
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> >
> > The vote will be open for 96 hours.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> >
> > The please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Aldrin Piri
In reply to this post by Joe Witt
+1, binding

Awesome stuff and a very welcomed enhancement to the NiFi ecosystem.
Definitely a lot of neat potential to build on from here.

Comments:
hashes and signatures good
build and contrib-check looked good.  Had some intermittent issues with NPM
in a clean environment, repeating the build eventually got a complete and
successful build.  Subsequent builds beyond that point had no issues.

minor:  DEPENDENCIES file should be excluded from source packaging. not
sure if this was a one-off from the release or could be prevented moving
forward
minor:  build-and-run.sh/stop.sh might should make a check to see if the
assembly exists
Nothing of note in a scan of the L&N

A quick start guide on integration in registry (and/or NiFi, didn't see it
in the PR) would be great to capture.  Had anticipated seeing this in the
user/admin guide.

Verified unsecured integration as highlighted in the helper.  Actions
seemed to make sense and work well after I got the flow mapped out
mentally.


On Thu, Dec 28, 2017 at 3:35 PM, Joe Witt <[hidden email]> wrote:

> +1 (binding) Release this package as nifi-registry-0.1.0
>
> Release verification process
> -pull source artifacts
> -verify sigs
> -verify commit id
> -verify commit history reflects latest changes (based off commit
> id/history)
> -verify source README
> -verify source L&N and that it is consistent with the work done in
>    https://issues.apache.org/jira/browse/NIFIREG-66
> -verify build w/contrib check
> -verify binary/assembly README
> -verify binary/assembly L&N and that it is consistent with work done in
>    https://issues.apache.org/jira/browse/NIFIREG-66
> -test registry on its own (manual/user testing)
> -review registry docs
> -setup certificate based secure reg setup/test
> - build nifi with registry integration PR
> - verify interaction with secure (certs based) nifi/secure registry
>
> Tests
> - create empty group
> - make local changes / view diffs / go to
> - make sure nifi cannot do anything with the registry when its cert
> lacks proxy auth
> - once proxy auth added all options available
> - verify can publish new versions/comments/ensure input is escaped
> - change versions on a live flow with and without enqueued data
>
> Observations
> - Having a default URL handler to show the 'you may have mistyped'
> type page from nifi would be nice
> - We should improve the logic of when components are started/stopped
> to make version changes.  For position changes only components should
> not start/stop
> - There are a lot of very cool features to add from here but this is a
> pretty awesome first version with a range of excellent security
> options/polish.
>
>
> This is going to be a huge step forward for the community!
>
> Thanks
> Joe
>
> On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende <[hidden email]> wrote:
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry 0.1.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> >
> > The Git tag is nifi-registry-0.1.0-RC1
> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;
> a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> > Checksums of nifi-registry-0.1.0-source-release.zip:
> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 65 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12320920&version=12340217
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/Release+
> Notes#ReleaseNotes-NiFiRegistry0.1.0
> >
> > The vote will be open for 96 hours.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> >
> > The please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Yolanda Davis
In reply to this post by Bryan Bende-2
+1, binding

Have been looking forward to this contribution; it is a great addition to
the community!

Following the release helper I verified signatures,  hashes as well as
the README,
NOTICE, and LICENSE. Successfully built the project per instructions and
built the NiFi project using the referenced PR.  From there I tested in
unsecured mode the basic test suggested in the helper guide.  Also tried
minor things such as deleting a flow from registry that was associated to a
PG to ensure NiFi updated as expected.

One thing that would be helpful is additional documentation on the NiFi
side on how to integrate with Registry. I also noticed on my test to delete
a flow where it seemed there was a pretty big lag when NiFi recognized the
change, even beyond my attempt to refresh.  Not sure if this is
configurable or just odd behavior on my end.

Another minor issue is when someone adds a process group, enters a name for
it and then selects import to use a flow in registry.  The name gets
overwritten by the flow (which makes sense) but wondering if there's a way
to either allow user to keep new name or at least let them know it will be
overwritten by version in registry?

Again great job!

-yolanda



On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende <[hidden email]> wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry 0.1.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1115/
>
> The Git tag is nifi-registry-0.1.0-RC1
> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> 81b99e7b04491eabb72ddf30754053ca12d0fcca
>
> Checksums of nifi-registry-0.1.0-source-release.zip:
> MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 65 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320920&version=12340217
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
>
> The vote will be open for 96 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
>
> The please vote:
>
> [ ] +1 Release this package as nifi-registry-0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>



--
--
[hidden email]
@YolandaMDavis
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Ben Qiu
In reply to this post by Bryan Bende-2
+1

On 2017-12-28 10:09, Bryan Bende <[hidden email]> wrote:

> Hello,>
>
> I am pleased to be calling this vote for the source release of Apache>
> NiFi Registry 0.1.0.>
>
> The source zip, including signatures, digests, etc. can be found at:>
> https://repository.apache.org/content/repositories/orgapachenifi-1115/>
>
> The Git tag is nifi-registry-0.1.0-RC1>
> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca>
>
https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca>

>
> Checksums of nifi-registry-0.1.0-source-release.zip:>
> MD5: 56244c3c296cdc9c3fcc6d22590b80d1>
> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca>
> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301>
>
> Release artifacts are signed with the following key:>
> https://people.apache.org/keys/committer/bbende.asc>
>
> KEYS file available here:>
> https://dist.apache.org/repos/dist/release/nifi/KEYS>
>
> 65 issues were closed/resolved for this release:>
>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12340217>

>
> Release note highlights can be found here:>
> https://cwiki.apache.org/confluence/display/NIFI/Release
Notes#ReleaseNotes-NiFiRegistry0.1.0>

>
> The vote will be open for 96 hours.>
>
> Please download the release candidate and evaluate the necessary items>
> including checking hashes, signatures, build from source, and test.>
>
> The please vote:>
>
> [ ]  1 Release this package as nifi-registry-0.1.0>
> [ ]  0 no opinion>
> [ ] -1 Do not release this package because...>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Koji Kawamura-2
+1 binding

This is really awesome!
I confirmed hashes and basic usages. Looks great for the 1st release.
Found couple of minor possible improvements on the NiFi side, and
posted comments to NiFi PR2219.
https://github.com/apache/nifi/pull/2219

Thanks for your work and effort, looking forward to use it in my daily
NiFi life!

Koji

On Sat, Dec 30, 2017 at 7:21 AM, Ben Qiu <[hidden email]> wrote:

> +1
>
> On 2017-12-28 10:09, Bryan Bende <[hidden email]> wrote:
>> Hello,>
>>
>> I am pleased to be calling this vote for the source release of Apache>
>> NiFi Registry 0.1.0.>
>>
>> The source zip, including signatures, digests, etc. can be found at:>
>> https://repository.apache.org/content/repositories/orgapachenifi-1115/>
>>
>> The Git tag is nifi-registry-0.1.0-RC1>
>> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca>
>>
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca>
>
>>
>> Checksums of nifi-registry-0.1.0-source-release.zip:>
>> MD5: 56244c3c296cdc9c3fcc6d22590b80d1>
>> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca>
>> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301>
>>
>> Release artifacts are signed with the following key:>
>> https://people.apache.org/keys/committer/bbende.asc>
>>
>> KEYS file available here:>
>> https://dist.apache.org/repos/dist/release/nifi/KEYS>
>>
>> 65 issues were closed/resolved for this release:>
>>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12340217>
>
>>
>> Release note highlights can be found here:>
>> https://cwiki.apache.org/confluence/display/NIFI/Release
> Notes#ReleaseNotes-NiFiRegistry0.1.0>
>>
>> The vote will be open for 96 hours.>
>>
>> Please download the release candidate and evaluate the necessary items>
>> including checking hashes, signatures, build from source, and test.>
>>
>> The please vote:>
>>
>> [ ]  1 Release this package as nifi-registry-0.1.0>
>> [ ]  0 no opinion>
>> [ ] -1 Do not release this package because...>
>>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Pierre Villard
+1 binding

Followed the release helper guide and everything looks good.
Made few tests in unsecured and secured environments.

Amazing work, thanks to everyone involved in this release!


2017-12-30 8:40 GMT+01:00 Koji Kawamura <[hidden email]>:

> +1 binding
>
> This is really awesome!
> I confirmed hashes and basic usages. Looks great for the 1st release.
> Found couple of minor possible improvements on the NiFi side, and
> posted comments to NiFi PR2219.
> https://github.com/apache/nifi/pull/2219
>
> Thanks for your work and effort, looking forward to use it in my daily
> NiFi life!
>
> Koji
>
> On Sat, Dec 30, 2017 at 7:21 AM, Ben Qiu <[hidden email]> wrote:
> > +1
> >
> > On 2017-12-28 10:09, Bryan Bende <[hidden email]> wrote:
> >> Hello,>
> >>
> >> I am pleased to be calling this vote for the source release of Apache>
> >> NiFi Registry 0.1.0.>
> >>
> >> The source zip, including signatures, digests, etc. can be found at:>
> >> https://repository.apache.org/content/repositories/orgapachenifi-1115/>
> >>
> >> The Git tag is nifi-registry-0.1.0-RC1>
> >> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca>
> >>
> > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> 81b99e7b04491eabb72ddf30754053ca12d0fcca>
> >
> >>
> >> Checksums of nifi-registry-0.1.0-source-release.zip:>
> >> MD5: 56244c3c296cdc9c3fcc6d22590b80d1>
> >> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca>
> >> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95ef
> d301>
> >>
> >> Release artifacts are signed with the following key:>
> >> https://people.apache.org/keys/committer/bbende.asc>
> >>
> >> KEYS file available here:>
> >> https://dist.apache.org/repos/dist/release/nifi/KEYS>
> >>
> >> 65 issues were closed/resolved for this release:>
> >>
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320920&version=12340217>
> >
> >>
> >> Release note highlights can be found here:>
> >> https://cwiki.apache.org/confluence/display/NIFI/Release
> > Notes#ReleaseNotes-NiFiRegistry0.1.0>
> >>
> >> The vote will be open for 96 hours.>
> >>
> >> Please download the release candidate and evaluate the necessary items>
> >> including checking hashes, signatures, build from source, and test.>
> >>
> >> The please vote:>
> >>
> >> [ ]  1 Release this package as nifi-registry-0.1.0>
> >> [ ]  0 no opinion>
> >> [ ] -1 Do not release this package because...>
> >>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Mark Payne
+1 (binding)

License & Hashes look good. Was able to verify signature. App starts up as expected and
functions as expected. The UI is looking great!

As we go forward, I am sure there are a lot of great features that we'll be able to add to
this. But knowing that this is what the team is releasing as an initial capability makes me
very proud to be a part of this community!

I am super excited about the possibilities that this opens up for us! Many thanks to all
who have contributed to this new Registry project. Very much look forward to seeing
where we can take this in the coming year.

Thanks again
-Mark



> On Dec 30, 2017, at 4:30 AM, Pierre Villard <[hidden email]> wrote:
>
> +1 binding
>
> Followed the release helper guide and everything looks good.
> Made few tests in unsecured and secured environments.
>
> Amazing work, thanks to everyone involved in this release!
>
>
> 2017-12-30 8:40 GMT+01:00 Koji Kawamura <[hidden email]>:
>
>> +1 binding
>>
>> This is really awesome!
>> I confirmed hashes and basic usages. Looks great for the 1st release.
>> Found couple of minor possible improvements on the NiFi side, and
>> posted comments to NiFi PR2219.
>> https://github.com/apache/nifi/pull/2219
>>
>> Thanks for your work and effort, looking forward to use it in my daily
>> NiFi life!
>>
>> Koji
>>
>> On Sat, Dec 30, 2017 at 7:21 AM, Ben Qiu <[hidden email]> wrote:
>>> +1
>>>
>>> On 2017-12-28 10:09, Bryan Bende <[hidden email]> wrote:
>>>> Hello,>
>>>>
>>>> I am pleased to be calling this vote for the source release of Apache>
>>>> NiFi Registry 0.1.0.>
>>>>
>>>> The source zip, including signatures, digests, etc. can be found at:>
>>>> https://repository.apache.org/content/repositories/orgapachenifi-1115/>
>>>>
>>>> The Git tag is nifi-registry-0.1.0-RC1>
>>>> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca>
>>>>
>>> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
>> 81b99e7b04491eabb72ddf30754053ca12d0fcca>
>>>
>>>>
>>>> Checksums of nifi-registry-0.1.0-source-release.zip:>
>>>> MD5: 56244c3c296cdc9c3fcc6d22590b80d1>
>>>> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca>
>>>> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95ef
>> d301>
>>>>
>>>> Release artifacts are signed with the following key:>
>>>> https://people.apache.org/keys/committer/bbende.asc>
>>>>
>>>> KEYS file available here:>
>>>> https://dist.apache.org/repos/dist/release/nifi/KEYS>
>>>>
>>>> 65 issues were closed/resolved for this release:>
>>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12320920&version=12340217>
>>>
>>>>
>>>> Release note highlights can be found here:>
>>>> https://cwiki.apache.org/confluence/display/NIFI/Release
>>> Notes#ReleaseNotes-NiFiRegistry0.1.0>
>>>>
>>>> The vote will be open for 96 hours.>
>>>>
>>>> Please download the release candidate and evaluate the necessary items>
>>>> including checking hashes, signatures, build from source, and test.>
>>>>
>>>> The please vote:>
>>>>
>>>> [ ]  1 Release this package as nifi-registry-0.1.0>
>>>> [ ]  0 no opinion>
>>>> [ ] -1 Do not release this package because...>
>>>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Joey Frazee
In reply to this post by Yolanda Davis
+1

- Verified checksums and signatures
- Successfully built and ran contrib-check w/ Oracle JDK 1.8.0_152
- Setup the registry w/ NIFI-4436
- Had some fun versioning PGs and rolling back and forth

Note: I ran into some trouble rolling back flows that include new funnels. It always results in an IllegalStateException with 'Funnel <ID> is the destination of another component'. There aren't any problems creating a new PG via Import or rolling forward a flow that newly includes a funnel. Will open an issue.

On Dec 29, 2017, 1:56 PM -0600, Yolanda Davis <[hidden email]>, wrote:

> +1, binding
>
> Have been looking forward to this contribution; it is a great addition to
> the community!
>
> Following the release helper I verified signatures, hashes as well as
> the README,
> NOTICE, and LICENSE. Successfully built the project per instructions and
> built the NiFi project using the referenced PR. From there I tested in
> unsecured mode the basic test suggested in the helper guide. Also tried
> minor things such as deleting a flow from registry that was associated to a
> PG to ensure NiFi updated as expected.
>
> One thing that would be helpful is additional documentation on the NiFi
> side on how to integrate with Registry. I also noticed on my test to delete
> a flow where it seemed there was a pretty big lag when NiFi recognized the
> change, even beyond my attempt to refresh. Not sure if this is
> configurable or just odd behavior on my end.
>
> Another minor issue is when someone adds a process group, enters a name for
> it and then selects import to use a flow in registry. The name gets
> overwritten by the flow (which makes sense) but wondering if there's a way
> to either allow user to keep new name or at least let them know it will be
> overwritten by version in registry?
>
> Again great job!
>
> -yolanda
>
>
>
> On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende <[hidden email]> wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry 0.1.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> >
> > The Git tag is nifi-registry-0.1.0-RC1
> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> > 81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> > Checksums of nifi-registry-0.1.0-source-release.zip:
> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 65 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12320920&version=12340217
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> >
> > The vote will be open for 96 hours.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> >
> > The please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>
>
>
> --
> --
> [hidden email]
> @YolandaMDavis
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

James Wing
In reply to this post by Bryan Bende-2
+1 (binding).  Ran through the release helper, verified hashes, LICENSE,
NOTICE, and README.  Built the source and performed light testing of the
resulting binary.

On Thu, Dec 28, 2017 at 10:09 AM, Bryan Bende <[hidden email]> wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry 0.1.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1115/
>
> The Git tag is nifi-registry-0.1.0-RC1
> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> 81b99e7b04491eabb72ddf30754053ca12d0fcca
>
> Checksums of nifi-registry-0.1.0-source-release.zip:
> MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 65 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320920&version=12340217
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
>
> The vote will be open for 96 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
>
> The please vote:
>
> [ ] +1 Release this package as nifi-registry-0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Scott Aslan
+1 (binding), Ran through the release helper. verified hashed, LICENSE,
NOTICE, and README.

Tests
- setup kerberos based secure reg setup/test with Nifi
- attempted to reproduce the npm issue, all looks well (Aldrin, I am
curious as to what caused npm to fail? any other info? maybe some other
software installed on your machine is causing conflicts?)


On Sat, Dec 30, 2017 at 6:16 PM, James Wing <[hidden email]> wrote:

> +1 (binding).  Ran through the release helper, verified hashes, LICENSE,
> NOTICE, and README.  Built the source and performed light testing of the
> resulting binary.
>
> On Thu, Dec 28, 2017 at 10:09 AM, Bryan Bende <[hidden email]> wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry 0.1.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> >
> > The Git tag is nifi-registry-0.1.0-RC1
> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> > 81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> > Checksums of nifi-registry-0.1.0-source-release.zip:
> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 65 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12320920&version=12340217
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> >
> > The vote will be open for 96 hours.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> >
> > The please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Matt Gilman
+1 (binding)

- build, hashes, etc look good
- set up a secure registry and nifi instance and everything worked as
expected

This is a very exciting release. Thanks Bryan for handling the release
manager duties and everyone who contributed!

Matt


On Sun, Dec 31, 2017 at 2:02 PM, Scott Aslan <[hidden email]> wrote:

> +1 (binding), Ran through the release helper. verified hashed, LICENSE,
> NOTICE, and README.
>
> Tests
> - setup kerberos based secure reg setup/test with Nifi
> - attempted to reproduce the npm issue, all looks well (Aldrin, I am
> curious as to what caused npm to fail? any other info? maybe some other
> software installed on your machine is causing conflicts?)
>
>
> On Sat, Dec 30, 2017 at 6:16 PM, James Wing <[hidden email]> wrote:
>
> > +1 (binding).  Ran through the release helper, verified hashes, LICENSE,
> > NOTICE, and README.  Built the source and performed light testing of the
> > resulting binary.
> >
> > On Thu, Dec 28, 2017 at 10:09 AM, Bryan Bende <[hidden email]> wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi Registry 0.1.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> > >
> > > The Git tag is nifi-registry-0.1.0-RC1
> > > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;
> a=commit;h=
> > > 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > >
> > > Checksums of nifi-registry-0.1.0-source-release.zip:
> > > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95ef
> d301
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/bbende.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 65 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12320920&version=12340217
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> > >
> > > The vote will be open for 96 hours.
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> > >
> > > The please vote:
> > >
> > > [ ] +1 Release this package as nifi-registry-0.1.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Kevin Doran
In reply to this post by Pierre Villard
+1 (non-binding)

- Verified sig, hashes, commit id
- Verified full build with contib-check, integration-tests, and jsUnitTests
- Checked README/NOTICE/LICENSE in source and target
- Verified unsecured [1] [2] and secured (client cert, ldap)
- Verified UI and REST API
- Verified persistence of buckets/flows and users/groups/policies across restarts
- Verified documentation [3]
- Verified NiFi integration using PR branch (this is really fun, nice work everyone who's contributed to this NiFi branch!)

Observations / Footnotes:

[1] Login page (/nifi-registry/login) should perhaps be disabled / redirect when running unsecured
[2] As others have noted, Policies lists/actions should be disabled in Bucket side-panel when running unsecured
[3] Agree with Aldrin that a quick start guide, in addition to the existing user and admin guides, would be nice to have in the next release.

Platform Info:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
Java version: 1.8.0_131, vendor: Oracle Corporation
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"

Nice work everyone!

Kevin

On 12/30/17, 04:31, "Pierre Villard" <[hidden email]> wrote:

    +1 binding
   
    Followed the release helper guide and everything looks good.
    Made few tests in unsecured and secured environments.
   
    Amazing work, thanks to everyone involved in this release!
   
   
    2017-12-30 8:40 GMT+01:00 Koji Kawamura <[hidden email]>:
   
    > +1 binding
    >
    > This is really awesome!
    > I confirmed hashes and basic usages. Looks great for the 1st release.
    > Found couple of minor possible improvements on the NiFi side, and
    > posted comments to NiFi PR2219.
    > https://github.com/apache/nifi/pull/2219
    >
    > Thanks for your work and effort, looking forward to use it in my daily
    > NiFi life!
    >
    > Koji
    >
    > On Sat, Dec 30, 2017 at 7:21 AM, Ben Qiu <[hidden email]> wrote:
    > > +1
    > >
    > > On 2017-12-28 10:09, Bryan Bende <[hidden email]> wrote:
    > >> Hello,>
    > >>
    > >> I am pleased to be calling this vote for the source release of Apache>
    > >> NiFi Registry 0.1.0.>
    > >>
    > >> The source zip, including signatures, digests, etc. can be found at:>
    > >> https://repository.apache.org/content/repositories/orgapachenifi-1115/>
    > >>
    > >> The Git tag is nifi-registry-0.1.0-RC1>
    > >> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca>
    > >>
    > > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
    > 81b99e7b04491eabb72ddf30754053ca12d0fcca>
    > >
    > >>
    > >> Checksums of nifi-registry-0.1.0-source-release.zip:>
    > >> MD5: 56244c3c296cdc9c3fcc6d22590b80d1>
    > >> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca>
    > >> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95ef
    > d301>
    > >>
    > >> Release artifacts are signed with the following key:>
    > >> https://people.apache.org/keys/committer/bbende.asc>
    > >>
    > >> KEYS file available here:>
    > >> https://dist.apache.org/repos/dist/release/nifi/KEYS>
    > >>
    > >> 65 issues were closed/resolved for this release:>
    > >>
    > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
    > projectId=12320920&version=12340217>
    > >
    > >>
    > >> Release note highlights can be found here:>
    > >> https://cwiki.apache.org/confluence/display/NIFI/Release
    > > Notes#ReleaseNotes-NiFiRegistry0.1.0>
    > >>
    > >> The vote will be open for 96 hours.>
    > >>
    > >> Please download the release candidate and evaluate the necessary items>
    > >> including checking hashes, signatures, build from source, and test.>
    > >>
    > >> The please vote:>
    > >>
    > >> [ ]  1 Release this package as nifi-registry-0.1.0>
    > >> [ ]  0 no opinion>
    > >> [ ] -1 Do not release this package because...>
    > >>
    >
   


Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Andrew Lim
In reply to this post by Bryan Bende-2
+1 (non-binding)

-Ran full clean install on OS X (10.11.6)
-Tested secure and unsecure Registry instances: creating/editing users, buckets, policies, special privileges; performed similar testing on group level
-Reviewed documentation
-Performed basic testing in NiFi: adding registry clients, putting a process group under version control, saving different versions, changing versions, importing a version, stopping version control

Awesome initial release for this project!

Drew


> On Dec 28, 2017, at 1:09 PM, Bryan Bende <[hidden email]> wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry 0.1.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1115/
>
> The Git tag is nifi-registry-0.1.0-RC1
> The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca
>
> Checksums of nifi-registry-0.1.0-source-release.zip:
> MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 65 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12340217
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
>
> The vote will be open for 96 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
>
> The please vote:
>
> [ ] +1 Release this package as nifi-registry-0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Jeff
+1 (binding)

- Ran through the helper guide
- Ran through the initial testing steps in the helper guide
- Ran through several use case scenarios, everything worked as expected,
with a minor exception described below.

NiFi Registry looks great!  I think this provides a huge quality of life
improvement for NiFi and its users, and this is only the initial release!
Amazing!

One thing I did notice, when working with two process groups referencing
the same versioned flow.  If one of these process groups is modified (for
example, a processor was added) and the changes are committed, the second
process group will report that it's up to do date, though it doesn't have
any of the changes that were committed.  It appears there's a period of
time between the commit of the changes and NiFi's retrieval/integration of
the updates from the registry. Refreshing the NiFi UI during this time
period will still show both process groups as up to date, though the
process group with the second instance of that versioned flow will still
not have the changes.  Some moments later, the second process group's icon
will report that there's a new version.  Updating that second process group
to the new version works as expected.

This is minor and doesn't effect NiFi Registry, but I thought I'd mention
it here.  I'll post this on the NiFi PR [1] as well.

[1] https://github.com/apache/nifi/pull/2219.

On Mon, Jan 1, 2018 at 11:30 AM Andrew Lim <[hidden email]>
wrote:

> +1 (non-binding)
>
> -Ran full clean install on OS X (10.11.6)
> -Tested secure and unsecure Registry instances: creating/editing users,
> buckets, policies, special privileges; performed similar testing on group
> level
> -Reviewed documentation
> -Performed basic testing in NiFi: adding registry clients, putting a
> process group under version control, saving different versions, changing
> versions, importing a version, stopping version control
>
> Awesome initial release for this project!
>
> Drew
>
>
> > On Dec 28, 2017, at 1:09 PM, Bryan Bende <[hidden email]> wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry 0.1.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> >
> > The Git tag is nifi-registry-0.1.0-RC1
> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> > Checksums of nifi-registry-0.1.0-source-release.zip:
> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 65 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12340217
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> >
> > The vote will be open for 96 hours.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> >
> > The please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Bryan Bende
+1 (binding)

On Mon, Jan 1, 2018 at 2:20 PM, Jeff <[hidden email]> wrote:

> +1 (binding)
>
> - Ran through the helper guide
> - Ran through the initial testing steps in the helper guide
> - Ran through several use case scenarios, everything worked as expected,
> with a minor exception described below.
>
> NiFi Registry looks great!  I think this provides a huge quality of life
> improvement for NiFi and its users, and this is only the initial release!
> Amazing!
>
> One thing I did notice, when working with two process groups referencing
> the same versioned flow.  If one of these process groups is modified (for
> example, a processor was added) and the changes are committed, the second
> process group will report that it's up to do date, though it doesn't have
> any of the changes that were committed.  It appears there's a period of
> time between the commit of the changes and NiFi's retrieval/integration of
> the updates from the registry. Refreshing the NiFi UI during this time
> period will still show both process groups as up to date, though the
> process group with the second instance of that versioned flow will still
> not have the changes.  Some moments later, the second process group's icon
> will report that there's a new version.  Updating that second process group
> to the new version works as expected.
>
> This is minor and doesn't effect NiFi Registry, but I thought I'd mention
> it here.  I'll post this on the NiFi PR [1] as well.
>
> [1] https://github.com/apache/nifi/pull/2219.
>
> On Mon, Jan 1, 2018 at 11:30 AM Andrew Lim <[hidden email]>
> wrote:
>
>> +1 (non-binding)
>>
>> -Ran full clean install on OS X (10.11.6)
>> -Tested secure and unsecure Registry instances: creating/editing users,
>> buckets, policies, special privileges; performed similar testing on group
>> level
>> -Reviewed documentation
>> -Performed basic testing in NiFi: adding registry clients, putting a
>> process group under version control, saving different versions, changing
>> versions, importing a version, stopping version control
>>
>> Awesome initial release for this project!
>>
>> Drew
>>
>>
>> > On Dec 28, 2017, at 1:09 PM, Bryan Bende <[hidden email]> wrote:
>> >
>> > Hello,
>> >
>> > I am pleased to be calling this vote for the source release of Apache
>> > NiFi Registry 0.1.0.
>> >
>> > The source zip, including signatures, digests, etc. can be found at:
>> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
>> >
>> > The Git tag is nifi-registry-0.1.0-RC1
>> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
>> >
>> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=81b99e7b04491eabb72ddf30754053ca12d0fcca
>> >
>> > Checksums of nifi-registry-0.1.0-source-release.zip:
>> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
>> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
>> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
>> >
>> > Release artifacts are signed with the following key:
>> > https://people.apache.org/keys/committer/bbende.asc
>> >
>> > KEYS file available here:
>> > https://dist.apache.org/repos/dist/release/nifi/KEYS
>> >
>> > 65 issues were closed/resolved for this release:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12340217
>> >
>> > Release note highlights can be found here:
>> >
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
>> >
>> > The vote will be open for 96 hours.
>> >
>> > Please download the release candidate and evaluate the necessary items
>> > including checking hashes, signatures, build from source, and test.
>> >
>> > The please vote:
>> >
>> > [ ] +1 Release this package as nifi-registry-0.1.0
>> > [ ] +0 no opinion
>> > [ ] -1 Do not release this package because...
>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache NiFi Registry 0.1.0

Andy LoPresto-2
In reply to this post by Yolanda Davis
+1, binding

* Verified the downloads worked
* Verified the signature (and that Bryan used SHA-512 for the underlying digest algorithm)
* Verified checksums
* Verified the Maven build worked and the RAT check passed
* Verified the presence of valid LICENSE, NOTICE, and README files
* Verified the git commit ID was correct
* Verified the RC was branched off the correct git commit ID
* Verified the RC binary contained valid LICENSE, NOTICE, and README files
* Verified the registry application worked as expected (standalone)
* Verified the NiFi PR 2219 built with the registry already installed
* Verified the integration between the two applications worked as expected
* Verified changes to a process group propagated to the registry and to cloned/imported process groups on the canvas
* Verified error message and that changes are not lost if committed when registry is unavailable

Notes:

* A couple minor formatting/whitespace issues in the root pom.xml 
* “No results match this query” is an off-putting message for the default. Before a user has created a bucket (no indicator from the default listing that one must go to settings to do so), there are obviously no results, but the user does not expect that they have executed a “query” (unless they are a DBA, probably). Can we change this to be “Go to Settings to add your first bucket” if count(buckets) == 0?
* After adding a bucket, I would expect “NiFi Registry/All” to show that bucket, not “No results match this query”. A user has to click the dropdown on “All” to see the new bucket listed. 
* Once entering the new bucket, the message displayed is still “No results match this query”. At this point, a new user has no idea what type of object would be a result at this level. Again, if the logic "count(flow) == 0”, I think a different message should be displayed like “Add versioned flows to this bucket from NiFi”. 
* I believe this is echoing Pierre, but I think the status icons in the PG and the toolbar need alt texts (both for 508 compliance and for people unfamiliar with the meaning of the icons). 
* If following the instructions provided in the release helper email, the local changes made to the first process group must be “Committed locally” in order for the imported PG to contain them. Otherwise, the imported PG will only contain the empty PG, while any changes made in the original are only in the originally and in a “locally modified” state. 
* When a PG is imported and an existing PG has the same name, the new PG should have the name “[Existing name] copy” or similar to indicate which is the original/source. 
* If a versioned PG is imported and is not at the most current version, local changes cannot be committed. Rather, “Change Version” and “Stop version control” are the only two options available. If a version upgrade is attempted, an error occurs and the local changes must be reverted. At this time, “Show local changes” and “Revert local changes” are made available in the version menu (not the error dialog). If these changes are non-conflicting, why does this occur? If this cannot be reconciled in the same flow snippet versioning chain, I suggest branching here and allowing it to be saved separately (i.e. provenance chain forking or git branching). Or at least warn the user on the first change made if the PG is not at the most recent version because a significant amount of work can be put in and then either lost or the ability to upgrade/save is lost with no user knowledge. 
* If the local changes are reverted, the menu options and state remain the same (conflicted) until a manual refresh occurs. 
* If changes are made to the cloned PG and committed, the changes are reflected in the registry UI and the original PG can be changed to that version, but it does not show the “a new version is available” indicator icon or notify the user that new changes are available (even after manual refresh). 

Despite all these notes, I think this is an excellent first release and will make NiFi much more useful for many users and open the possibilities for continued development that has been prevented up to this point. Thanks to everyone who worked on this. 

Andy LoPresto
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Dec 29, 2017, at 2:56 PM, Yolanda Davis <[hidden email]> wrote:

+1, binding

Have been looking forward to this contribution; it is a great addition to
the community!

Following the release helper I verified signatures,  hashes as well as
the README,
NOTICE, and LICENSE. Successfully built the project per instructions and
built the NiFi project using the referenced PR.  From there I tested in
unsecured mode the basic test suggested in the helper guide.  Also tried
minor things such as deleting a flow from registry that was associated to a
PG to ensure NiFi updated as expected.

One thing that would be helpful is additional documentation on the NiFi
side on how to integrate with Registry. I also noticed on my test to delete
a flow where it seemed there was a pretty big lag when NiFi recognized the
change, even beyond my attempt to refresh.  Not sure if this is
configurable or just odd behavior on my end.

Another minor issue is when someone adds a process group, enters a name for
it and then selects import to use a flow in registry.  The name gets
overwritten by the flow (which makes sense) but wondering if there's a way
to either allow user to keep new name or at least let them know it will be
overwritten by version in registry?

Again great job!

-yolanda



On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende <[hidden email]> wrote:

Hello,

I am pleased to be calling this vote for the source release of Apache
NiFi Registry 0.1.0.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1115/

The Git tag is nifi-registry-0.1.0-RC1
The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
81b99e7b04491eabb72ddf30754053ca12d0fcca

Checksums of nifi-registry-0.1.0-source-release.zip:
MD5: 56244c3c296cdc9c3fcc6d22590b80d1
SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/bbende.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

65 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12320920&version=12340217

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/
Release+Notes#ReleaseNotes-NiFiRegistry0.1.0

The vote will be open for 96 hours.

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.

The please vote:

[ ] +1 Release this package as nifi-registry-0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...




--
--
[hidden email]
@YolandaMDavis


signature.asc (859 bytes) Download Attachment