+1
1. Verified checksums
2. Verified signatures
3. Local build
4. Started a 3 node cluster
5. Verified version
6. Ozone shell (volume, bucket, key commands)
7. Checked UIs
On Mon, Apr 12, 2021 at 2:33 PM Vivek Ratnavel
wrote:
> +1
>
> Thanks for the update Prashant!
>
> 1. Checked the signatur
+1
Thanks for the update Prashant!
1. Checked the signatures and verified the tag
2. Verified all the checksums on both source and binary
3. Built it from source
4. Created a docker cluster from binary and verified all the basic shell
commands work as expected
5. Verified Recon UI comes up fine a
+1(non-binding)
*Built from source.
*Verified Checksums
*Verified ozone version
*Ran basic shell commands
*Browsed through the UI.
Thanx Prashant for driving the release.
-Ayush
> On 12-Apr-2021, at 1:21 PM, Sammi Chen wrote:
>
> +1,
>
> Thanks Prashant for updating to RC2.
> One suggestion
You are absolutely right, the first and last mail contradict to each
other (even for me ;-) ).
Sorry for the confusion, and thanks for the suggestion to fix it.
Marton
ps: slightly unrelated, but ozone-go repository is/was used for an
interesting experiment with turning-on Github branch pr
+1,
Thanks Prashant for updating to RC2.
One suggestion is the location of your public key. Currently all public
keys of hadoop RM are under
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS, a central
place for anyone to retrieve.
- Verified signatures, checksums
- Verified `ozon
