Re: [DISCUSS] Apache Ozone 1.5.0 release

+1 for a .0 release with full HBase support. Best, Sid On Thu, Aug 22, 2024 at 11:55 AM Wei-Chiu Chuang wrote: > Hi community, > > I’d like to initiate a discussion about the 1.5.0 release. There have been > significant changes since 1.4.0 (January 2024) with 1,130 commits >

Re: Ozone Jira and PR guidelines

Thanks, Hemant for kicking off this thread! Jira and pull-requests hygiene are extremely important for posterity and overall significantly improve collaboration with developers especially cross timezones. This should be added to the contributing guide: https://github.com/apache/ozone/blob/master/C

Re: New committer: George Bijan Jahad

Congrats George J, welcome to the club! Best, Sid On Tue, Jun 27, 2023 at 5:05 PM Ethan Rose wrote: > Congratulations George! Thanks for all your work on Ozone so far. > > Ethan > > On Tue, Jun 27, 2023 at 4:46 PM Michel Sumbul > wrote: > > > Wouhouuu, congratulations George > > > > > > Le

Re: [DISCUSS] Proposal to merge Ozone feature branch HDDS-7733-Symmetric-Tokens to master

@Wei-Chiu Chuang AFAIK we adopted Hadoop bylaws. So it should be 3 committer +1s, right? - Sid On Wed, May 31, 2023 at 11:17 AM Wei-Chiu Chuang wrote: > What does it take to pass a vote? Does it require PMCs or can any > contributors can vote? > I checked around and don't think there's an Apac

Re: [NOTICE] Upcoming global changes to default GitHub Actions behavior for outside collaborators

+1 Sammi on your proposal. Thank you for bringing this back to the foreground. Best, Sid On Fri, Mar 24, 2023 at 1:07 AM Sammi Chen wrote: > Hi Folks, > > Currently, every PR/commit from non-committers needs approval from one > committer, which is not efficient and friendly for community contri

Re: Cutting Ozone 1.3.1

+1 for 1.3.1 with critical fixes. Best, Sid On Tue, Mar 14, 2023 at 12:53 AM Kota Uenishi wrote: > Hi, > > +1 (non-binding) from me. > > I'd also like to have HDDS-7755 included in the release. It's a tiny > fix, but fixed severe hang in our cluster, which was the original > source of HDDS-7701

Re: [VOTE] Proposal to merge HttpFS support in Ozone feature branch (HDDS-5447-httpfs) into master

+1 Best, Sid On Mon, Feb 27, 2023 at 11:12 PM Sadanand Shenoy wrote: > +1 for merge. > > -Sadanand > > On Tue, Feb 28, 2023 at 12:26 PM Yi-Sheng Lien wrote: > > > +1 for merging it. > > > > Zita Dombi 於 2023年2月27日 週一 下午11:01 寫道： > > > > > Hi Ozone Devs! > > > > > > I’m starting this vote thre

Re: [DISCUSS] Proposal to merge HttpFS support in Ozone feature branch (HDDS-5447-httpfs) into master

+1 for the merge. Thank you Zita for driving this with Pifta. Best, Sid On Mon, Feb 6, 2023 at 3:29 PM Ethan Rose wrote: > +1 for merge, thanks Zita and Pifta! > > - Ethan > > On Mon, Feb 6, 2023 at 2:58 PM Zita Dombi wrote: > > > Hi Ozone Devs! > > > > I am starting this discussion thread for

Re: [DISCUSS] How many days to wait if no response from reviewer?

Correction - I meant a follow-up Jira. - Sid On Wed, Feb 1, 2023 at 11:19 AM Siddharth Wagle wrote: > As a general rule of thumb, the open questions should be addressed in a > follow-up PR, opened by the patch author or on a suggestion from > the committer giving the binding +1. >

Re: [DISCUSS] How many days to wait if no response from reviewer?

As a general rule of thumb, the open questions should be addressed in a follow-up PR, opened by the patch author or on a suggestion from the committer giving the binding +1. This allows the reviewer, let's say who is on vacation to come back to it and still get their concerns addressed. Best, Sid

Re: [VOTE] Proposal to merge HDDS-6517 Ozone Snapshots

+1 for the merge. - Sid On Fri, Jan 20, 2023 at 11:21 AM Uma Maheswara Rao Gangumalla < umaganguma...@gmail.com> wrote: > +1 > > Regards, > Uma > > On Wed, Jan 18, 2023 at 11:08 AM Prashant Pogde > > wrote: > > > > > We would like to start this Vote thread for the proposal to merge > > https://

Re: [DISCUSS] Proposal to merge HDDS-6517 Ozone Snapshots

+1 on the need to address upgrade concerns in the wiki. Snapshots should be usable only after finalization. Whether a layout feature is needed or not, IMO if no current on-disk layout has changed we should not need it. Ethan? Best, Sid On Wed, Jan 11, 2023 at 9:53 AM Ethan Rose wrote: > Hey Pr

Re: Two years with Apache Ozone

Thank you, Kohei for sharing your experience and the blog post with the Apache Ozone community. As an early adopter, Preferred Networks are a key contributor to the Apache Ozone ecosystem and we at Cloudera are super excited to keep partnering with you in the open-source! There is active work ongo

Re: [DISCUSS] Proposal to merge HDDS-4454 Ozone Streaming Write Pipeline into master

+1 for merging the feature. Thanks, Nicholas for driving this! Best, Sid On Wed, Dec 7, 2022 at 5:11 AM Ayush Saxena wrote: > +1, skimmed over the code and tried some basic stuff. > > Thanx Tsz-Wo for the driving this!! > > -Ayush > > > On 06-Dec-2022, at 7:06 AM, Arpit Agarwal wrote: > > > >

Re: [VOTE] Apache Ozone 1.3.0 RC1

+1 (binding) Thanks, MingChao for driving this, Kudos! - Verified checksums - Built from source Best, Sid On Tue, Nov 29, 2022 at 1:33 AM Attila Doroszlai wrote: > Thanks MingChao for creating rc1. > > +1 > > * Verified signatures, checksums > * Verified docs in binary tarball > * Verified `o

Re: [VOTE] Merge Ozone S3 Multi-Tenancy feature branch (HDDS-4944) into master

+1 for the merge. Best, Sid On Wed, May 25, 2022 at 1:33 AM Sammi Chen wrote: > +1, > > Thanks Siyao and the feature dev team. Great Job! > > Bests, > Sammi > > > > On Tue, 24 May 2022 at 11:41, Siyao Meng wrote: > > > Dear Ozone devs, > > > > I am starting this vote thread for merging t

Re: [DISCUSS] Proposal to merge Ozone datanode side RocksDB merge feature branch (HDDS-3630) into master

+1 for merging this feature. Thank you Sammi and folks from Tencent for working on this critical improvement. Best, Sid On Mon, May 23, 2022, 5:49 AM Sammi Chen wrote: > Dear Ozone Devs, > > I 'm starting this discussion thread for the proposal to merge the Ozone > Datanode RocksDB merge feat

Re: [DISCUSS] Proposal to merge Ozone S3 Multi-Tenancy feature branch (HDDS-4944) into master

+1 for the merge, thanks Siyao for starting this thread. Best, Sid On Fri, May 13, 2022 at 11:40 AM Aravindan Vijayan wrote: > +1 (pending blocking JIRAs) > > On Tue, May 10, 2022 at 11:54 AM Siyao Meng wrote: > > > Hi Ozone devs, > > > > I am starting this discussion thread for proposing to

Re: [VOTE] - Merge HDDS-4440-s3-performance feature branch into master

+1 for the merge. Thanks, Neil for working on this perf improvement feature for Ozone. Best, Sid On Mon, Apr 25, 2022 at 9:00 AM Uma Maheswara Rao Gangumalla < umaganguma...@gmail.com> wrote: > Oh, Looks like Attila covered those comments already. > > Post addressing those. +1 for the branch me

Re: Re: [VOTE] Merge Ozone Erasure Coding branch (HDDS-3816-ec) into master

+1 for the EC branch merge. Best, Sid On Wed, Apr 6, 2022 at 8:05 PM guimark wrote: > Great news! > +1 to merge. > > > > > At 2022-04-06 22:18:31, "Stephen O'Donnell" > wrote: > >I have been working on the code on this branch for some time, and I > believe > >it is in a good state to merge now

Re: [DISCUSS] Proposal to merge Ozone Erasure Coding branch (HDDS-3816-ec) into master

+1 to merge the EC feature with read/write and online recovery part complete. Thanks, Uma for putting the wiki page with all of the details. Minor nit: The documentation link points to the wrong markdown (FSO) instead of the EC documentation. - Sid On Thu, Feb 17, 2022 at 8:29 AM Arpit Agarwal

CVE-2021-39236: Apache Ozone: Owners of the S3 tokens are not validated

Description: Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user. This issue is being tracked as HDDS-4763 Mitigation: Upgrade to Apache Ozone release version 1.2.0 Credit: Apache Ozone would like to thank Marton Elek for reporti

CVE-2021-41532: Apache Ozone: Unauthenticated access to Ozone Recon HTTP endpoints

Severity: moderate Description: Recon HTTP endpoints provide access to OM, SCM and Datanode metadata. Due to a bug, any unauthenticated user can access the data from these endpoints. This issue is being tracked as HDDS-5691 Mitigation: Upgrade to Apache Ozone release version 1.2.0 Credit: A

CVE-2021-39235: Apache Ozone: Access mode of block tokens are not enforced

Description: Ozone Datanode doesn't check the access mode parameter of the block token. Authenticated users with valid READ block token can do any write operation on the same block. This issue is being tracked as HDDS-4558,HDDS-4644 Mitigation: Upgrade to Apache Ozone release version 1.2.0

CVE-2021-39234: Apache Ozone: Raw block data can be read bypassing ACL/authorization

Description: Authenticated users knowing the ID of an existing block can craft specific request allowing access those blocks, bypassing other security checks like ACL. This issue is being tracked as HDDS-5061 Mitigation: Upgrade to Apache Ozone release version 1.2.0 Credit: Apache Ozone wou

CVE-2021-39233: Apache Ozone: Container-related datanode operations can be called without authorization

Description: Container related Datanode requests of Ozone Datanode were not properly authorized and can be called by any client. This issue is being tracked as HDDS-4729,HDDS-5236 Mitigation: Upgrade to Apache Ozone release version 1.2.0 Credit: Apache Ozone would like to thank Marton Elek

CVE-2021-39232: Apache Ozone: Missing admin check for SCM related admin commands

Description: Certain admin related SCM commands can be executed by any authenticated users, not just by admins. This issue is being tracked as HDDS-4530 Mitigation: Upgrade to Apache Ozone release version 1.2.0 Credit: Apache Ozone would like to thank Wei-Chiu Chuang for reporting this

CVE-2021-39231: Apache Ozone: Missing authentication/authorization on internal RPC endpoints

Description: Various internal server-to-server RPC endpoints are available for connections, making it possible for an attacker to download raw data from Datanode and Ozone manager and modify Ratis replication configuration. This issue is being tracked as HDDS-4704,HDDS-4730,HDDS-4496,HDDS-4788

CVE-2021-36372: Apache Ozone: Original block tokens are persisted and can be retrieved

Description: Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked. This issue is being tracked as HDDS-5315 Mitigation: Upgrade to Apache

Re: [VOTE] Apache Ozone 1.2.0 RC2

+1 for RC2 - Built from source - Verified hashes and checksums Thank you Ethan for the release work. Best, Sid On Fri, Nov 12, 2021 at 6:12 AM Yi-Sheng Lien wrote: > +1 > > Thank you Ethan bringing it ! > > Yi-Sheng > > > Attila Doroszlai 於 2021年11月11日 週四 上午5:32 寫道： > > > +1 > > > > * Verifi

Re: [VOTE] - Merge FSO branch HDDS-2939 to master

+1 for the merge. Rakesh, thank you for working on this feature. Best, Sid On Wed, Jun 2, 2021, 5:33 AM Wei-Chiu Chuang wrote: > I am +1. > > > Reviewed the benchmark report and liked it a lot! Yes, the rename and > delete was terrible before. This is going to make certain application > operati

Re: [DISCUSS] - Merge Non rolling upgrade branch - 'HDDS-3698-nonrolling-upgrade'

+1 for Upgrade branch merge. Thank you Aravindan, Ethan, Prashant, and Pifta for actively working on this important feature for Ozone, and everyone else who contributed with ideas and suggestions. Best, Sid On Mon, Apr 19, 2021 at 10:04 AM Aravindan Vijayan wrote: > Hello all, > > I would like

Re: [VOTE] - Merge SCM-HA Branch - HDDS-2823

+1 for merging this important feature. We should merge this into master right after cutting out the 1.1 branch. Thank you for all the community effort in pulling this off. Best, Sid On Thu, Mar 18, 2021 at 6:36 PM Dinesh Chitlangia wrote: > +1, the work done here is truly impressive, great >

Re: [DISCUSS] State of Ozone CSI support

Marton, this is what we had on the apache docs as of 2/17 when I last checked: S3 Fuse driver (goofys) Goofys is a S3 FUSE driver. It could be used to any mount any Ozone bucket as posix file system:goofys --endpoint http://localhost:9878 bucket1 /mount/bucket1 So +1 for the change above. Also,

Re: [DISCUSS] - Merge SCM-HA Branch - HDDS-2823

@Arpit: we discussed the checklist in the last community meeting. These are meant to be guidelines for feature developers to self-assess, it should not be a roadblock, IMO. Most of the items are probably easy to check off the list. @Marton: A discussion thread would be helpful to refine the page.

Re: [DISCUSS] 1.1.0 release

Hi Dinesh, Prashant had actually expressed interest in being the RM on a previous community meeting. I will let him reply to this thread if he wants to still be on the RM for 1.1. Best, Sid On Thu, Jan 7, 2021 at 10:08 PM Shashikant Banerjee wrote: > +1 > > Thanks > Shashi > > On Fri, Jan 8,

Re: Enabling Ratis on OM by default

+1 for this change. Best, Sid On Mon, Nov 23, 2020 at 11:19 AM Arpit Agarwal wrote: > +1 > > > > On Nov 23, 2020, at 10:35 AM, Hanisha Koneru > wrote: > > > > Hi All, > > > > I am proposing to enable Ratis by default on Ozone Manager - HDDS-4498 < > https://issues.apache.org/jira/browse/HDDS-4