Joining Ozone slack channel

Hi Devs, I’d like to join jour slack channel as the mailing list is not very active. As far as I understand apache slack workspace is not opened for everyone (just for apache commiters) but I’d like to join if you don’t mind. On the latest Ozone community call I was told that it’s ok to join your

[DISCUSS] HDDS-6634 datanode doesn't check cluster identity in runtime

Hi all, I would like to discuss https://issues.apache.org/jira/browse/HDDS-6634 . During our internal Ozone testing, we noticed that a datanode can be connected to another cluster (not the one the datanode had been initialized with). Although the

Re: [DISCUSS] HDDS-6634 datanode doesn't check cluster identity in runtime

> Thanks, > > Mukul > > On 25/04/22 3:19 pm, Maxim Myskov wrote: >> Hi all, >> I would like to discuss https://issues.apache.org/jira/browse/HDDS-6634 >> <https://issues.apache.org/jira/browse/HDDS-6634>. >> During our internal Ozone testing, we no

HDDS-7343 is a potential blocker to Ozone-1.3.0

Hi all, Please take a look at https://issues.apache.org/jira/browse/HDDS-7343 (and associated PR). I think is a blocker to Ozone 1.3.0

Re: [DISCUSS] Next Ozone major release 1.4.0

Hi devs, We've identified a critical bug that we believe is a blocker for the upcoming release. The issue is documented here: * https://issues.apache.org/jira/browse/HDDS-9817 S3 get secret endpoint returns 500 The issue is about S3 get secret endpoint returning a 500 error, causing our clien

Re: [DISCUSS] Next Ozone major release 1.4.0

Hi devs, HDDS-9817 <https://issues.apache.org/jira/browse/HDDS-9817> was an issue of our internal Ozone build. It is now closed (no code changes needed). > On 1 Dec 2023, at 13:05, Maxim Myskov wrote: > > Hi devs, > > We've identified a critical bug that we be

Re: [DISCUSS] Next Ozone major release 1.4.0

Hi devs, I propose backporting https://issues.apache.org/jira/browse/HDDS-9807 from the master branch to the 1.4.0 branch. This issue has an impact on the use of erasure coding, so the proposed fix will be beneficial for the upcoming release. > On 16 Dec 2023, at 00:18, Tsz Wo Sze wrote: > > H

Re: [DISCUSS] Ozone 1.4.1 Release

Hi Ozone Devs, I think it is important to merge remaining tickets to the 1.4.1 branch. It’s either bugfix or CVE fix, both are important. I can prepare a PR to merge these tickets. > On 3 Apr 2024, at 08:15, Sammi Chen wrote: > > Dear Ozone Devs, > > We have released 1.4.0 on Jan 19th. > No

Re: [DISCUSS] Apache Ozone 1.5.0 release

I would be glad to volunteer as the release manager for the 1.5.0 release. On Thu, Aug 22, 2024 at 10:23 PM Ethan Rose wrote: > +1 to start planning for 1.5.0. Our minor releases tend to take some time > so it's good to start early. For any committers looking to gain more > experience volunteeri