+1 to keeping master shippable. In addition to config flags, for purposes
of the upgrade finalization, many new features would need to be gated, one
option would be to make the validators expect a version that is only
possible by hand tweaking the version in a dev build, thus ensuring that
unreleas
https://issues.apache.org/jira/browse/HDDS-7526 we merged, we
should cherry-pick it to 1.3 branch as well.
---Ritesh
On Thu, Dec 1, 2022 at 9:21 AM Kaijie Chen wrote:
> > There may be another issue:
> > If there is additional software included in the binary package (which
> most likely is true
+1 for this.
We can wait to gather a broader consensus for certain rare cases where we
add new APIs or public changes but if the reviewer's original review
comments were addressed then it should be ok to go ahead and merge post a
timeout value.
On Tue, Jan 31, 2023 at 2:51 PM Uma Maheswara Rao Gan
1+
Thank you @Zita Dombi and @Istvan Fajth
On Mon, Feb 6, 2023 at 7:06 PM Siyao Meng wrote:
> +1
>
> -Siyao
>
> On Feb 6, 2023 at 7:04:24 PM, Siddharth Wagle wrote:
>
> > +1 for the merge. Thank you Zita for driving this with Pifta.
> >
> > Best,
> > Sid
> >
> > On Mon, Feb 6, 2023 at 3:29 P
Folks,
As part of the debug for HDDS-7701, some bugs were fixed, and defensive
code changes were put in.
There were multiple bug fixes around block deletion execution.
In addition to that, multiple client leak fixes have been checked into the
master branch.
I recommend cherry-picking these critical
t; > > (+81)80-9299-2656 Preferred Networks, Inc.
> > >
> > > On Tue, Mar 14, 2023 at 4:03 PM Kaijie Chen wrote:
> > > >
> > > > +1, sound good
> > > >
> > > > I would like to propose two more fixes to the list.
> > > >
Hello,
This topic has been an active discussion internally at Cloudera and has
been a source of confusion while onboarding new customers. Please take a
look at the attached document.
This document discusses the differences between two bucket layouts in
Ozone, OBS (OBJECT_STORE) and FSO (FILE_SYST
easier ports from
> Hadoop file systems to ozone and avoid naming issues due to s3 naming
> conventions, proposing to port through OFS with FSO layout makes sound
> sense.
>
>
> Regards,
>
> Neil
>
> On Wed, Mar 29, 2023 at 10:04 PM Ritesh Shukla wrote:
>
>
Hello folks,
Sending this across for a couple of reasons
1. Slack and Jiras are invitations only for now
2. Slack messages are not google friendly.
GitHub allows discussions Ref:
https://github.com/kerneltime/ozone/discussions
I propose enabling GitHub discussions to ease the outreach to curious
c
able state, could you share the link here so
> others
> > can reference an example of how we could set up the sections to organize
> > questions, meeting minutes, etc?
> >
> > Ethan
> >
> > On Sun, Apr 23, 2023 at 11:12 PM Ritesh Shukla
> > >
>
.
On Mon, Apr 24, 2023 at 10:29 AM Ayush Saxena wrote:
> +1
> Sounds cool. Amongst the ones I know Airflow does that:
> https://github.com/apache/airflow/discussions
>
> -Ayush
>
> On Mon, 24 Apr 2023 at 11:42, Ritesh Shukla
> wrote:
> >
> > Hello folks,
> &g
We have discussions enabled!
https://github.com/apache/ozone/discussions
On Mon, May 1, 2023 at 7:58 PM Neil Joshi wrote:
> Thanks Ritesh for the demo and discussion.
>
> +1
>
> Regards,
> Neil
>
> On Mon, May 1, 2023 at 1:49 PM Ritesh Shukla
> wrote:
>
> &
https://github.com/apache/ozone/pull/4641
Will update the site shortly.
On Tue, May 2, 2023 at 10:40 AM Arpit Agarwal
wrote:
> This is great. Can we link this from our wiki page and website?
>
> Thanks,
> Arpit
>
> > On May 2, 2023, at 10:26 AM, Ritesh Shukla
>
https://github.com/apache/ozone-site/pull/35
On Tue, May 2, 2023 at 10:45 AM Ritesh Shukla wrote:
> https://github.com/apache/ozone/pull/4641
> Will update the site shortly.
>
> On Tue, May 2, 2023 at 10:40 AM Arpit Agarwal
> wrote:
>
>> This is great. Can we link thi
Also, please post the meeting minutes and recordings to
https://github.com/apache/ozone/discussions
Regards,
Ritesh
> On May 4, 2023, at 11:47 PM, Wei-Chiu Chuang wrote:
>
> Hello! and especially for community members who are in the Asia-Pacific
> region:
>
> Sammi's been running the commun
+1 from me (disclaimer, I worked with Duong on this project)
For those wanting the TLDR for this branch merge, we go from ~15k IOPS on
OM for reads in secure clusters to 100k IOPS (
https://issues.apache.org/jira/browse/HDDS-8574)
Merging this in and having more test time before 1.4 release is crit
We can include the block token work that is in the process of being merged.
That work considerably impacts performance, and delaying it to 1.5.0 will
lead to a negative experience with a secure Ozone cluster for
folks adopting Ozone in 1.4.0
Regards,
Ritesh
On Wed, Jun 7, 2023 at 9:49 AM Ethan Ros
Hi Pifta,
Thank you for chiming in.
I have actually not considered how to revive the mailing list for technical and
design discussions.
I am not sure why mailing lists are no longer as popular, in general I see a
decline of
using emails for discussions other than formal one way communication.
stones make
> > sense
> > > > there, since it gives people insight as to which Jiras or PRs to
> > follow.
> > > > Then people can subscribe to the threads they want on Jira or GitHub
> > > > without the entire dev base being blasted for niche feature specific
>
I have sent you an invite but I encourage you to use GitHub Discussions
https://github.com/apache/ozone/discussions over Slack. It is more active
and seen by a wider audience including google search.
---Ritesh (kerneltime)
On Mon, Jul 8, 2024 at 1:47 AM Александр Юнцевич
wrote:
> Hi Devs,
>
> I’
Should we wait for another Ratis dependency update to pick the work done
around zero copy?
On Thu, Aug 22, 2024 at 1:18 PM Maxim Myskov wrote:
> 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 pl
https://github.com/apache/ozone/pull/8107
> On Mar 18, 2025, at 6:30 PM, Ritesh Shukla wrote:
>
> I agree with Ethan before we take on the task of maintaining another site, we
> should finish the new Ozone site and then evaluate if we need a wiki.
> —Ritesh
>
>> On
I agree with Ethan before we take on the task of maintaining another site, we
should finish the new Ozone site and then evaluate if we need a wiki.
—Ritesh
> On Mar 18, 2025, at 5:15 PM, Ethan Rose wrote:
>
> I don't think GitHub wiki will help us. I would really like all Ozone
> content to be
+1
Thanks for working on this.
When do we update the Docker images and the examples/helm charts to use
them?
On Wed, Apr 9, 2025 at 1:34 PM Wei-Chiu Chuang wrote:
> Thanks! KEYS files are updated.
>
> On Wed, Apr 9, 2025 at 10:52 AM Tsz-Wo Nicholas Sze
> wrote:
>
> > Hi Wei-Chiu,
> >
> > Thank
Hi,
We should shift our design discussions from Google Docs to Markdown files
managed through GitHub Pull Requests. This approach would:
1. Keep our discussions in the same system as our code, creating a more
cohesive history
2. Make our design documents more accessible to developers alr
On Tue, Apr 15, 2025 at 9:34 AM Tsz Wo Sze wrote:
> +1 on md over google doc.
>
> > ... Google Docs do not show up in Google searches ...
>
> This is bad for our design docs. How about the other search engines?
>
>
> I don't know of any search engine that searches through all public docs
for a c
+1
Disclaimer: I am a sponsor and contributor for this work
On Tue, Jun 10, 2025 at 5:40 PM Ethan Rose wrote:
> Based on discussion in the community sync this week I want to add some more
> information.
> Code
>
> For those interested in checking out the code, these are some of the major
> class
27 matches
Mail list logo
