+1
- Verified all checksums and signatures.
- Checked LICENSE and NOTICE.
- Compared the files in the src tarball with the files in git.
- Built from source successfully.
- Passed all unit tests.
- Able to start a single node cluster and upload a file; see the
instructions in the attached file.
Tsz-Wo
On Wed, Dec 17, 2025 at 10:02 AM Tsz Wo Sze <[email protected]> wrote:
> Hi Chung-En,
>
> Thanks a lot for rolling out a new RC!
>
> Some quick comments:
>
> > Fingerprint: 02192AAA4CA0DF7D
>
> As shown in the gpg output, your public key fingerprint indeed is "6FF3
> ... DF7D" and "02192AAA4CA0DF7D" is your key id.
>
> % gpg --verify $GZ.asc $GZ
> gpg: Signature made Tue Dec 9 08:59:53 2025 PST
> gpg: using RSA key 6FF3418A9181D5030F0E2ACA02192AAA4CA0DF7D
> gpg: Good signature from "Chung-En Lee (Apache Release Signing Key) <
> [email protected]>" [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 6FF3 418A 9181 D503 0F0E 2ACA 0219 2AAA 4CA0 DF7D
>
> BTW, your public key is not found in
> https://dist.apache.org/repos/dist/dev/ozone/KEYS
>
> > RC2 and RC3 diff: ...
>
> It is better to also provide a diff of the previous 2.0.0 release. We
> should not require that someone, who is verifying RC3, has to go through
> all the previous RCs and discussions.
>
> - https://github.com/apache/ozone/compare/ozone-2.0.0...ozone-2.1.0-RC3
>
> These are just minor problems in the VOTE email but not the RC3
> artifacts. Will continue verifying RC3.
>
> Tsz-Wo
>
>
>
> On Mon, Dec 15, 2025 at 11:41 AM Attila Doroszlai <[email protected]>
> wrote:
>
>> > https://github.com/apache/ozone/releases/tag/ozone-2.1.0-RC3
>>
>> Thanks Chung-En for yet another RC.
>>
>> +1
>>
>> * Verified signatures, checksums
>> * Verified source matches ozone-2.1.0-RC3 tag
>> * Verified docs in binary tarball
>> * Verified `ozone version`
>>
>> -Attila
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
#################
# Step 1: set conf etc/hadoop/ozone-site.xml
<configuration>
<property>
<name>dfs.container.ratis.datanode.storage.dir</name>
<value>/Users/szetszwo/ozone/releases/2.1.0/cluster1/d1/ratis</value>
</property>
<property>
<name>ozone.metadata.dirs</name>
<value>/Users/szetszwo/ozone/releases/2.1.0/cluster1</value>
</property>
<property>
<name>ozone.scm.service.ids</name>
<value>cluster1</value>
</property>
<property>
<name>ozone.scm.nodes.cluster1</name>
<value>scm1</value>
</property>
<property>
<name>ozone.scm.address.cluster1.scm1</name>
<value>localhost</value>
</property>
</configuration>
#################
# Step 2: SCM
./bin/ozone --config etc/hadoop scm --init
./bin/ozone --config etc/hadoop scm
#################
# Step 3: OM
./bin/ozone --config etc/hadoop om --init
./bin/ozone --config etc/hadoop om
#################
# Step 4: datanode
./bin/ozone --config etc/hadoop datanode
#################
# Step 5: create a file with RATIS/ONE
./bin/ozone admin safemode exit
./bin/ozone sh volume create /vol1
./bin/ozone sh bucket create /vol1/buck1 -t RATIS -r ONE
./bin/ozone sh key put /vol1/buck1/a.txt a.txt
./bin/ozone sh key cat /vol1/buck1/a.txt
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
