Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)
+1 (binding) - Built from source on Ubuntu 21.10 and macOS 11.6 with Azul Zulu 11.0.12 and Azul Zulu 1.8.0.282 - Ran NiFi on Azul Zulu 11.0.12 and 1.8.0.282 - Verified Single User Authentication and OIDC Authentication with Keycloak - Verified updates to JWT client storage and cookie handling - Verified basic operation of NiFi Regstriy - NIFI-6617 Verified encrypted repository configuration using new properties with BCFKS and PKCS12 KeyStores - NIFI-7322 Verified SignContentPGP and VerifyContentPGP together with EncryptContentPGP and DecryptContentPGP using various properties - NIFI-8424 Verified absence of HtmlDocumentWriter warnings on startup - NIFI-8943 Built, launched, and restarted Docker container verifying persistence of random sensitive properties key - NIFI-9059 Ran simple data flow using NiFi Stateless on Java 11 - NIFI-9223 Verified ListenSyslog listens on 0.0.0.0 using default properties - NIFI-9251 Verified absence of unused generated password in NiFi Registry - NIFI-9266 Verified Azure Key Vault Secret Sensitive Property Provider configuration for nifi.properties - NIFI-9322 Verified corrected REST API documentation for OIDC and SAML resources - NIFI-9339 Verified JoltTransformJSON custom UI works as expected Thanks for managing the release process Joe! Regards, David Handermann On Thu, Nov 4, 2021 at 6:33 PM Matt Burgess wrote: > +1 Release this package as nifi-1.15.0 > > Ran through the release helper and some tests to verify various Jiras > were included. Thanks again for RM'ing Joe! > > On Wed, Nov 3, 2021 at 3:29 PM Joe Witt wrote: > > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 1.15.0. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1186 > > > > The source being voted upon and the convenience binaries can be found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/ > > > > A helpful reminder on how the release candidate verification process > works: > > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate > > > > The Git tag is nifi-1.15.0-RC3 > > The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b > > > > Checksums of nifi-1.15.0-source-release.zip: > > SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a > > SHA512: > 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/joewitt.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 234 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382 > > > > Release note highlights can be found here: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.0 > > > > The vote will be open for 72 hours. > > Please download the release candidate and evaluate the necessary items > > including checking hashes, signatures, build from source, and test. > > Then please vote: > > > > [ ] +1 Release this package as nifi-1.15.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... >
Re: [discuss] NiFi 1.15
Chris,
I am running through several verification steps, but I built 1.15.0 RC 3
from sources and then ran "mvn install -pl :dockermaven -P docker" to build
the Docker image. When starting with the following command, I was able to
use the generated username and password to access the running NiFi
container:
docker run --name nifi -p 8443:8443 apache/nifi:1.15.0-dockermaven
If you are still having issues, it would be helpful to provide any logs or
error messages you are seeing.
Regards,
David Handermann
On Thu, Nov 4, 2021 at 8:10 PM Kevin Doran wrote:
> Oh meant to send a link to this too:
>
> > ARG
> NIFI_BINARY_PATH=${NIFI_BINARY_PATH:-/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.zip}
>
>
> https://github.com/apache/nifi/blob/373498445fe589e2d4855a0730fbb9127f0b4452/nifi-docker/dockerhub/Dockerfile#L30
>
> > On Nov 4, 2021, at 9:09 PM, Kevin Doran wrote:
> >
> > Hi Joe and Chris,
> >
> > Our Dockerfile that we use to build the Dockerhub image defaults to
> looking for 1.15.0 instead of NiFi-1.15.0, but it is a variable that we can
> override, so this is easy to workaround incase the release folder does
> change. Agree its nice to keep the tree structure consistent when we can.
> >
> > I’m about to do my verification and will also check the single user with
> the docker image as part of that.
> >
> > Cheers,
> > Kevin
> >
> >> On Nov 4, 2021, at 6:44 PM, Joe Witt wrote:
> >>
> >> Chris,
> >>
> >> Yeah I should have just put it in 1.15.0 instead of nifi/1.15.0.
> >> Should generally not really matter so the docker angle there is
> >> interesting. Not sure why our docker images would have any
> >> relationship to our dist/dev storage. But when I move them into the
> >> release folder I can try to ensure I place them only in 1.15.0 instead
> >> of nifi/1.15.0.
> >>
> >> That directory the prov stuff makes does linger and can be annoying so
> >> thanks for tackling that. Saw the PR. Will take a look soon if
> >> nobody else has.
> >>
> >> Will keep an eye on your findings related to docker builds not working
> >> with username/password things. Hopefully others can chime in there.
> >>
> >> Thanks
> >> Send
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Thu, Nov 4, 2021 at 2:06 PM Chris Sampson
> >> wrote:
> >>>
> >>> Worryingly, when I do get the Docker Image to build (further changes
> to the
> >>> Dockerfile), the auto-generated username and password from the startup
> logs
> >>> aren't being accepted for login via my browser.
> >>>
> >>> I'll try to spend a little more time looking at this (but await input
> on my
> >>> earlier question/concern also).
> >>>
> >>>
> >>> ---
> >>> *Chris Sampson*
> >>> IT Consultant
> >>> chris.samp...@naimuri.com
> >>>
> >>>
> >>> On Thu, 4 Nov 2021 at 20:47, Chris Sampson
> >>> wrote:
> >>>
> I've got most of the way through the release check process in order to
> vote for 1.15.0, but I wanted to check on a change in the distribution
> release artifacts.
>
> For 1.14.0, the Dev artifacts were located at:
> https://dist.apache.org/repos/dist/dev/nifi/1.14.0/*
> For 1.15.0, the Dev artifacts are located at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/*
>
> i.e. there's been a change of directory/path from to
> nifi-.
>
> The reason I raise this is that I can no longer build a Docker Image
> using
> the dockerhub/DockerBuild.sh script because it cannot find the
> artifacts to
> download. This may not be a problem if the path change is only for
> the Dev
> artifacts, but if the same change is going to happen for the released
> artifacts, then the apache/nifi image (and presumably the
> apache/nifi-registry, apache/nifi-toolkit and any minifi) convenience
> images will no longer be possible as part of the Release, which will
> likely
> be an issue for a number of users that have deployments using these
> images.
>
> I spotted this after rebasing my outstanding PR [1] for NIFI-8779 [2]
>
>
> Additionally, I noted NIFI-9366 [3] after an unwanted directory was
> created by the unit tests executed during building and testing
> 1.15.0-RC3.
> I raised a PR [4] - this is a minor issue and not a reason to block
> any
> release.
>
>
>
> [1] https://github.com/apache/nifi/pull/5213
> [2] https://issues.apache.org/jira/browse/NIFI-8779
>
> [3] https://issues.apache.org/jira/browse/NIFI-9366
> [4] https://github.com/apache/nifi/pull/5510
>
> ---
> *Chris Sampson*
> IT Consultant
> chris.samp...@naimuri.com
>
>
> On Sat, 30 Oct 2021 at 01:52, Joe Witt wrote:
>
> > Otto
> >
> > Got ya. Yeah it was this way in 1.14 as well. And to be clear with
> every
> > release what we are actually voting upon is the source release. Now
> the
> > source release includes nifi, minifi, nifi registry, stateless nifi
>
Re: [discuss] NiFi 1.15
Oh meant to send a link to this too:
> ARG
> NIFI_BINARY_PATH=${NIFI_BINARY_PATH:-/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.zip}
https://github.com/apache/nifi/blob/373498445fe589e2d4855a0730fbb9127f0b4452/nifi-docker/dockerhub/Dockerfile#L30
> On Nov 4, 2021, at 9:09 PM, Kevin Doran wrote:
>
> Hi Joe and Chris,
>
> Our Dockerfile that we use to build the Dockerhub image defaults to looking
> for 1.15.0 instead of NiFi-1.15.0, but it is a variable that we can override,
> so this is easy to workaround incase the release folder does change. Agree
> its nice to keep the tree structure consistent when we can.
>
> I’m about to do my verification and will also check the single user with the
> docker image as part of that.
>
> Cheers,
> Kevin
>
>> On Nov 4, 2021, at 6:44 PM, Joe Witt wrote:
>>
>> Chris,
>>
>> Yeah I should have just put it in 1.15.0 instead of nifi/1.15.0.
>> Should generally not really matter so the docker angle there is
>> interesting. Not sure why our docker images would have any
>> relationship to our dist/dev storage. But when I move them into the
>> release folder I can try to ensure I place them only in 1.15.0 instead
>> of nifi/1.15.0.
>>
>> That directory the prov stuff makes does linger and can be annoying so
>> thanks for tackling that. Saw the PR. Will take a look soon if
>> nobody else has.
>>
>> Will keep an eye on your findings related to docker builds not working
>> with username/password things. Hopefully others can chime in there.
>>
>> Thanks
>> Send
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Nov 4, 2021 at 2:06 PM Chris Sampson
>> wrote:
>>>
>>> Worryingly, when I do get the Docker Image to build (further changes to the
>>> Dockerfile), the auto-generated username and password from the startup logs
>>> aren't being accepted for login via my browser.
>>>
>>> I'll try to spend a little more time looking at this (but await input on my
>>> earlier question/concern also).
>>>
>>>
>>> ---
>>> *Chris Sampson*
>>> IT Consultant
>>> chris.samp...@naimuri.com
>>>
>>>
>>> On Thu, 4 Nov 2021 at 20:47, Chris Sampson
>>> wrote:
>>>
I've got most of the way through the release check process in order to
vote for 1.15.0, but I wanted to check on a change in the distribution
release artifacts.
For 1.14.0, the Dev artifacts were located at:
https://dist.apache.org/repos/dist/dev/nifi/1.14.0/*
For 1.15.0, the Dev artifacts are located at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/*
i.e. there's been a change of directory/path from to
nifi-.
The reason I raise this is that I can no longer build a Docker Image using
the dockerhub/DockerBuild.sh script because it cannot find the artifacts to
download. This may not be a problem if the path change is only for the Dev
artifacts, but if the same change is going to happen for the released
artifacts, then the apache/nifi image (and presumably the
apache/nifi-registry, apache/nifi-toolkit and any minifi) convenience
images will no longer be possible as part of the Release, which will likely
be an issue for a number of users that have deployments using these images.
I spotted this after rebasing my outstanding PR [1] for NIFI-8779 [2]
Additionally, I noted NIFI-9366 [3] after an unwanted directory was
created by the unit tests executed during building and testing 1.15.0-RC3.
I raised a PR [4] - this is a minor issue and not a reason to block any
release.
[1] https://github.com/apache/nifi/pull/5213
[2] https://issues.apache.org/jira/browse/NIFI-8779
[3] https://issues.apache.org/jira/browse/NIFI-9366
[4] https://github.com/apache/nifi/pull/5510
---
*Chris Sampson*
IT Consultant
chris.samp...@naimuri.com
On Sat, 30 Oct 2021 at 01:52, Joe Witt wrote:
> Otto
>
> Got ya. Yeah it was this way in 1.14 as well. And to be clear with every
> release what we are actually voting upon is the source release. Now the
> source release includes nifi, minifi, nifi registry, stateless nifi and
> toolkits among all the other having always been there goodies.
>
> Some of these things we make available in the form of convenience binaries
> to make it easier on folks to consume.
>
> I think you dont need to do any verification you would not have done
> before.
>
> But I do hope folks help maintain various ways of easing more folks
> knowing
> what to vet with a given release
>
> On Fri, Oct 29, 2021 at 5:34 PM Otto Fowler
> wrote:
>
>> This release, we are verifying not only Nifi, but also Minifi Java. At
>> least that is my understanding.
>>
>> This would be my first time having *anything* to do with minifi, i’ve
> not
>> even run it before.
>>
>> As such, I
Re: [discuss] NiFi 1.15
Hi Joe and Chris, Our Dockerfile that we use to build the Dockerhub image defaults to looking for 1.15.0 instead of NiFi-1.15.0, but it is a variable that we can override, so this is easy to workaround incase the release folder does change. Agree its nice to keep the tree structure consistent when we can. I’m about to do my verification and will also check the single user with the docker image as part of that. Cheers, Kevin > On Nov 4, 2021, at 6:44 PM, Joe Witt wrote: > > Chris, > > Yeah I should have just put it in 1.15.0 instead of nifi/1.15.0. > Should generally not really matter so the docker angle there is > interesting. Not sure why our docker images would have any > relationship to our dist/dev storage. But when I move them into the > release folder I can try to ensure I place them only in 1.15.0 instead > of nifi/1.15.0. > > That directory the prov stuff makes does linger and can be annoying so > thanks for tackling that. Saw the PR. Will take a look soon if > nobody else has. > > Will keep an eye on your findings related to docker builds not working > with username/password things. Hopefully others can chime in there. > > Thanks > Send > > > > > > > > > > > On Thu, Nov 4, 2021 at 2:06 PM Chris Sampson > wrote: >> >> Worryingly, when I do get the Docker Image to build (further changes to the >> Dockerfile), the auto-generated username and password from the startup logs >> aren't being accepted for login via my browser. >> >> I'll try to spend a little more time looking at this (but await input on my >> earlier question/concern also). >> >> >> --- >> *Chris Sampson* >> IT Consultant >> chris.samp...@naimuri.com >> >> >> On Thu, 4 Nov 2021 at 20:47, Chris Sampson >> wrote: >> >>> I've got most of the way through the release check process in order to >>> vote for 1.15.0, but I wanted to check on a change in the distribution >>> release artifacts. >>> >>> For 1.14.0, the Dev artifacts were located at: >>> https://dist.apache.org/repos/dist/dev/nifi/1.14.0/* >>> For 1.15.0, the Dev artifacts are located at: >>> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/* >>> >>> i.e. there's been a change of directory/path from to >>> nifi-. >>> >>> The reason I raise this is that I can no longer build a Docker Image using >>> the dockerhub/DockerBuild.sh script because it cannot find the artifacts to >>> download. This may not be a problem if the path change is only for the Dev >>> artifacts, but if the same change is going to happen for the released >>> artifacts, then the apache/nifi image (and presumably the >>> apache/nifi-registry, apache/nifi-toolkit and any minifi) convenience >>> images will no longer be possible as part of the Release, which will likely >>> be an issue for a number of users that have deployments using these images. >>> >>> I spotted this after rebasing my outstanding PR [1] for NIFI-8779 [2] >>> >>> >>> Additionally, I noted NIFI-9366 [3] after an unwanted directory was >>> created by the unit tests executed during building and testing 1.15.0-RC3. >>> I raised a PR [4] - this is a minor issue and not a reason to block any >>> release. >>> >>> >>> >>> [1] https://github.com/apache/nifi/pull/5213 >>> [2] https://issues.apache.org/jira/browse/NIFI-8779 >>> >>> [3] https://issues.apache.org/jira/browse/NIFI-9366 >>> [4] https://github.com/apache/nifi/pull/5510 >>> >>> --- >>> *Chris Sampson* >>> IT Consultant >>> chris.samp...@naimuri.com >>> >>> >>> On Sat, 30 Oct 2021 at 01:52, Joe Witt wrote: >>> Otto Got ya. Yeah it was this way in 1.14 as well. And to be clear with every release what we are actually voting upon is the source release. Now the source release includes nifi, minifi, nifi registry, stateless nifi and toolkits among all the other having always been there goodies. Some of these things we make available in the form of convenience binaries to make it easier on folks to consume. I think you dont need to do any verification you would not have done before. But I do hope folks help maintain various ways of easing more folks knowing what to vet with a given release On Fri, Oct 29, 2021 at 5:34 PM Otto Fowler wrote: > This release, we are verifying not only Nifi, but also Minifi Java. At > least that is my understanding. > > This would be my first time having *anything* to do with minifi, i’ve not > even run it before. > > As such, I think the RC validation guide needs to be update to include the > information about now validating nifi and minifi together. > > > > > From: Joe Witt > Reply: dev@nifi.apache.org > Date: October 25, 2021 at 11:59:39 > To: dev@nifi.apache.org > Subject: [discuss] NiFi 1.15 > > Team, > > I thought I had already started such a thread but I dont see it so here > goes... >
Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)
+1 Release this package as nifi-1.15.0 Ran through the release helper and some tests to verify various Jiras were included. Thanks again for RM'ing Joe! On Wed, Nov 3, 2021 at 3:29 PM Joe Witt wrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi 1.15.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1186 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/ > > A helpful reminder on how the release candidate verification process works: > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate > > The Git tag is nifi-1.15.0-RC3 > The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b > > Checksums of nifi-1.15.0-source-release.zip: > SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a > SHA512: > 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/joewitt.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 234 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.0 > > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. > Then please vote: > > [ ] +1 Release this package as nifi-1.15.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
Re: [discuss] NiFi 1.15
Chris, Yeah I should have just put it in 1.15.0 instead of nifi/1.15.0. Should generally not really matter so the docker angle there is interesting. Not sure why our docker images would have any relationship to our dist/dev storage. But when I move them into the release folder I can try to ensure I place them only in 1.15.0 instead of nifi/1.15.0. That directory the prov stuff makes does linger and can be annoying so thanks for tackling that. Saw the PR. Will take a look soon if nobody else has. Will keep an eye on your findings related to docker builds not working with username/password things. Hopefully others can chime in there. Thanks Send On Thu, Nov 4, 2021 at 2:06 PM Chris Sampson wrote: > > Worryingly, when I do get the Docker Image to build (further changes to the > Dockerfile), the auto-generated username and password from the startup logs > aren't being accepted for login via my browser. > > I'll try to spend a little more time looking at this (but await input on my > earlier question/concern also). > > > --- > *Chris Sampson* > IT Consultant > chris.samp...@naimuri.com > > > On Thu, 4 Nov 2021 at 20:47, Chris Sampson > wrote: > > > I've got most of the way through the release check process in order to > > vote for 1.15.0, but I wanted to check on a change in the distribution > > release artifacts. > > > > For 1.14.0, the Dev artifacts were located at: > > https://dist.apache.org/repos/dist/dev/nifi/1.14.0/* > > For 1.15.0, the Dev artifacts are located at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/* > > > > i.e. there's been a change of directory/path from to > > nifi-. > > > > The reason I raise this is that I can no longer build a Docker Image using > > the dockerhub/DockerBuild.sh script because it cannot find the artifacts to > > download. This may not be a problem if the path change is only for the Dev > > artifacts, but if the same change is going to happen for the released > > artifacts, then the apache/nifi image (and presumably the > > apache/nifi-registry, apache/nifi-toolkit and any minifi) convenience > > images will no longer be possible as part of the Release, which will likely > > be an issue for a number of users that have deployments using these images. > > > > I spotted this after rebasing my outstanding PR [1] for NIFI-8779 [2] > > > > > > Additionally, I noted NIFI-9366 [3] after an unwanted directory was > > created by the unit tests executed during building and testing 1.15.0-RC3. > > I raised a PR [4] - this is a minor issue and not a reason to block any > > release. > > > > > > > > [1] https://github.com/apache/nifi/pull/5213 > > [2] https://issues.apache.org/jira/browse/NIFI-8779 > > > > [3] https://issues.apache.org/jira/browse/NIFI-9366 > > [4] https://github.com/apache/nifi/pull/5510 > > > > --- > > *Chris Sampson* > > IT Consultant > > chris.samp...@naimuri.com > > > > > > On Sat, 30 Oct 2021 at 01:52, Joe Witt wrote: > > > >> Otto > >> > >> Got ya. Yeah it was this way in 1.14 as well. And to be clear with every > >> release what we are actually voting upon is the source release. Now the > >> source release includes nifi, minifi, nifi registry, stateless nifi and > >> toolkits among all the other having always been there goodies. > >> > >> Some of these things we make available in the form of convenience binaries > >> to make it easier on folks to consume. > >> > >> I think you dont need to do any verification you would not have done > >> before. > >> > >> But I do hope folks help maintain various ways of easing more folks > >> knowing > >> what to vet with a given release > >> > >> On Fri, Oct 29, 2021 at 5:34 PM Otto Fowler > >> wrote: > >> > >> > This release, we are verifying not only Nifi, but also Minifi Java. At > >> > least that is my understanding. > >> > > >> > This would be my first time having *anything* to do with minifi, i’ve > >> not > >> > even run it before. > >> > > >> > As such, I think the RC validation guide needs to be update to include > >> the > >> > information about now validating nifi and minifi together. > >> > > >> > > >> > > >> > > >> > From: Joe Witt > >> > Reply: dev@nifi.apache.org > >> > Date: October 25, 2021 at 11:59:39 > >> > To: dev@nifi.apache.org > >> > Subject: [discuss] NiFi 1.15 > >> > > >> > Team, > >> > > >> > I thought I had already started such a thread but I dont see it so here > >> > goes... > >> > > >> > We have made a ton of progress again and there are some super > >> > important fixes as well. It is definitely time to kick out a 1.15. > >> > My intent will be to attempt to pull together an RC this week. > >> > Haven't done the analysis yet of what is hanging out there but will do > >> > so. A quick look at all the features and fixes already landed though > >> > make it clear we have more than enough to work with. > >> > > >> > Lets please use this thread for coordination on the RC rather than it > >> > becoming the wish list. We have new features/fixes arriving
Re: [discuss] NiFi 1.15
Worryingly, when I do get the Docker Image to build (further changes to the Dockerfile), the auto-generated username and password from the startup logs aren't being accepted for login via my browser. I'll try to spend a little more time looking at this (but await input on my earlier question/concern also). --- *Chris Sampson* IT Consultant chris.samp...@naimuri.com On Thu, 4 Nov 2021 at 20:47, Chris Sampson wrote: > I've got most of the way through the release check process in order to > vote for 1.15.0, but I wanted to check on a change in the distribution > release artifacts. > > For 1.14.0, the Dev artifacts were located at: > https://dist.apache.org/repos/dist/dev/nifi/1.14.0/* > For 1.15.0, the Dev artifacts are located at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/* > > i.e. there's been a change of directory/path from to > nifi-. > > The reason I raise this is that I can no longer build a Docker Image using > the dockerhub/DockerBuild.sh script because it cannot find the artifacts to > download. This may not be a problem if the path change is only for the Dev > artifacts, but if the same change is going to happen for the released > artifacts, then the apache/nifi image (and presumably the > apache/nifi-registry, apache/nifi-toolkit and any minifi) convenience > images will no longer be possible as part of the Release, which will likely > be an issue for a number of users that have deployments using these images. > > I spotted this after rebasing my outstanding PR [1] for NIFI-8779 [2] > > > Additionally, I noted NIFI-9366 [3] after an unwanted directory was > created by the unit tests executed during building and testing 1.15.0-RC3. > I raised a PR [4] - this is a minor issue and not a reason to block any > release. > > > > [1] https://github.com/apache/nifi/pull/5213 > [2] https://issues.apache.org/jira/browse/NIFI-8779 > > [3] https://issues.apache.org/jira/browse/NIFI-9366 > [4] https://github.com/apache/nifi/pull/5510 > > --- > *Chris Sampson* > IT Consultant > chris.samp...@naimuri.com > > > On Sat, 30 Oct 2021 at 01:52, Joe Witt wrote: > >> Otto >> >> Got ya. Yeah it was this way in 1.14 as well. And to be clear with every >> release what we are actually voting upon is the source release. Now the >> source release includes nifi, minifi, nifi registry, stateless nifi and >> toolkits among all the other having always been there goodies. >> >> Some of these things we make available in the form of convenience binaries >> to make it easier on folks to consume. >> >> I think you dont need to do any verification you would not have done >> before. >> >> But I do hope folks help maintain various ways of easing more folks >> knowing >> what to vet with a given release >> >> On Fri, Oct 29, 2021 at 5:34 PM Otto Fowler >> wrote: >> >> > This release, we are verifying not only Nifi, but also Minifi Java. At >> > least that is my understanding. >> > >> > This would be my first time having *anything* to do with minifi, i’ve >> not >> > even run it before. >> > >> > As such, I think the RC validation guide needs to be update to include >> the >> > information about now validating nifi and minifi together. >> > >> > >> > >> > >> > From: Joe Witt >> > Reply: dev@nifi.apache.org >> > Date: October 25, 2021 at 11:59:39 >> > To: dev@nifi.apache.org >> > Subject: [discuss] NiFi 1.15 >> > >> > Team, >> > >> > I thought I had already started such a thread but I dont see it so here >> > goes... >> > >> > We have made a ton of progress again and there are some super >> > important fixes as well. It is definitely time to kick out a 1.15. >> > My intent will be to attempt to pull together an RC this week. >> > Haven't done the analysis yet of what is hanging out there but will do >> > so. A quick look at all the features and fixes already landed though >> > make it clear we have more than enough to work with. >> > >> > Lets please use this thread for coordination on the RC rather than it >> > becoming the wish list. We have new features/fixes arriving all the >> > time - those can be addressed in normal channels. >> > >> > Thanks >> > >> > >> >
Re: [discuss] NiFi 1.15
I've got most of the way through the release check process in order to vote for 1.15.0, but I wanted to check on a change in the distribution release artifacts. For 1.14.0, the Dev artifacts were located at: https://dist.apache.org/repos/dist/dev/nifi/1.14.0/* For 1.15.0, the Dev artifacts are located at: https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/* i.e. there's been a change of directory/path from to nifi-. The reason I raise this is that I can no longer build a Docker Image using the dockerhub/DockerBuild.sh script because it cannot find the artifacts to download. This may not be a problem if the path change is only for the Dev artifacts, but if the same change is going to happen for the released artifacts, then the apache/nifi image (and presumably the apache/nifi-registry, apache/nifi-toolkit and any minifi) convenience images will no longer be possible as part of the Release, which will likely be an issue for a number of users that have deployments using these images. I spotted this after rebasing my outstanding PR [1] for NIFI-8779 [2] Additionally, I noted NIFI-9366 [3] after an unwanted directory was created by the unit tests executed during building and testing 1.15.0-RC3. I raised a PR [4] - this is a minor issue and not a reason to block any release. [1] https://github.com/apache/nifi/pull/5213 [2] https://issues.apache.org/jira/browse/NIFI-8779 [3] https://issues.apache.org/jira/browse/NIFI-9366 [4] https://github.com/apache/nifi/pull/5510 --- *Chris Sampson* IT Consultant chris.samp...@naimuri.com On Sat, 30 Oct 2021 at 01:52, Joe Witt wrote: > Otto > > Got ya. Yeah it was this way in 1.14 as well. And to be clear with every > release what we are actually voting upon is the source release. Now the > source release includes nifi, minifi, nifi registry, stateless nifi and > toolkits among all the other having always been there goodies. > > Some of these things we make available in the form of convenience binaries > to make it easier on folks to consume. > > I think you dont need to do any verification you would not have done > before. > > But I do hope folks help maintain various ways of easing more folks knowing > what to vet with a given release > > On Fri, Oct 29, 2021 at 5:34 PM Otto Fowler > wrote: > > > This release, we are verifying not only Nifi, but also Minifi Java. At > > least that is my understanding. > > > > This would be my first time having *anything* to do with minifi, i’ve not > > even run it before. > > > > As such, I think the RC validation guide needs to be update to include > the > > information about now validating nifi and minifi together. > > > > > > > > > > From: Joe Witt > > Reply: dev@nifi.apache.org > > Date: October 25, 2021 at 11:59:39 > > To: dev@nifi.apache.org > > Subject: [discuss] NiFi 1.15 > > > > Team, > > > > I thought I had already started such a thread but I dont see it so here > > goes... > > > > We have made a ton of progress again and there are some super > > important fixes as well. It is definitely time to kick out a 1.15. > > My intent will be to attempt to pull together an RC this week. > > Haven't done the analysis yet of what is hanging out there but will do > > so. A quick look at all the features and fixes already landed though > > make it clear we have more than enough to work with. > > > > Lets please use this thread for coordination on the RC rather than it > > becoming the wish list. We have new features/fixes arriving all the > > time - those can be addressed in normal channels. > > > > Thanks > > > > >
Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)
+1 (binding) Verified everything in the release helper and tested saving/importing flows to/from registry with inherited param contexts. On Thu, Nov 4, 2021 at 5:56 AM Kotaro Terada wrote: > > +1 (non-binding) > > - Verified hashes. > - Built from source with OpenJDK 8 and OpenJDK 11. > - Run a 3-node secure cluster. > - Tested a couple of flows. > - Tested new features (ExecuteStateless, inherited parameter context, etc). > > Thank you for working on this, Joe. > > Thanks, > Kotaro > > > On Thu, Nov 4, 2021 at 10:44 AM Otto Fowler wrote: > > > +1 > > Ran through verification, build and run > > > > From: Joe Witt > > Reply: dev@nifi.apache.org > > Date: November 3, 2021 at 15:29:41 > > To: dev@nifi.apache.org > > Subject: [VOTE] Release Apache NiFi 1.15.0 (rc3) > > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi 1.15.0. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1186 > > > > The source being voted upon and the convenience binaries can be found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/ > > > > A helpful reminder on how the release candidate verification process works: > > > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate > > > > The Git tag is nifi-1.15.0-RC3 > > The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b > > > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b > > > > Checksums of nifi-1.15.0-source-release.zip: > > SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a > > SHA512: > > > > 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f > > > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/joewitt.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 234 issues were closed/resolved for this release: > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382 > > > > Release note highlights can be found here: > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.0 > > > > The vote will be open for 72 hours. > > Please download the release candidate and evaluate the necessary items > > including checking hashes, signatures, build from source, and test. > > Then please vote: > > > > [ ] +1 Release this package as nifi-1.15.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > >
Re: Jira contributor access
I've added you as a contributor to Jira. Looking forward to your contributions. Marton On Thu, 4 Nov 2021 at 08:24, Vibhath Ileperuma wrote: > > Requesting Jira contributor access > > Username: Vibhath
Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)
+1 (non-binding) - Verified hashes. - Built from source with OpenJDK 8 and OpenJDK 11. - Run a 3-node secure cluster. - Tested a couple of flows. - Tested new features (ExecuteStateless, inherited parameter context, etc). Thank you for working on this, Joe. Thanks, Kotaro On Thu, Nov 4, 2021 at 10:44 AM Otto Fowler wrote: > +1 > Ran through verification, build and run > > From: Joe Witt > Reply: dev@nifi.apache.org > Date: November 3, 2021 at 15:29:41 > To: dev@nifi.apache.org > Subject: [VOTE] Release Apache NiFi 1.15.0 (rc3) > > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi 1.15.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1186 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/ > > A helpful reminder on how the release candidate verification process works: > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate > > The Git tag is nifi-1.15.0-RC3 > The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b > > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b > > Checksums of nifi-1.15.0-source-release.zip: > SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a > SHA512: > > 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f > > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/joewitt.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 234 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.0 > > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. > Then please vote: > > [ ] +1 Release this package as nifi-1.15.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
Jira contributor access
Requesting Jira contributor access Username: Vibhath
