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

2022-02-17 Thread guimark
+1 Great works from Uma, Stephen, Istvan, Markton and all Ozone EC developers! We'll keep helping fix BUGs of EC to make the EC feature more and more robust. And we are really looking forward to start detailed design and discussions about the Offline Recovery feature, which is very important f

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

2022-02-17 Thread Aravindan Vijayan
+1 for merge (pending HDDS-6209). Kudos in getting this major feature to a stable v1 state. On Thu, Feb 17, 2022 at 1:10 PM Hanisha Koneru wrote: > +1 for merge with the compatibility issue addressed. > > Thanks Uma for putting this together. > > - Hanisha > > > On Feb 15, 2022, at 12:17 AM, Um

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

2022-02-17 Thread Hanisha Koneru
+1 for merge with the compatibility issue addressed. Thanks Uma for putting this together. - Hanisha > On Feb 15, 2022, at 12:17 AM, Uma gangumalla wrote: > > Dear Ozone Devs, > > As you may know, we have been actively developing Ozone Erasure Coding > support in a separate branch HDDS-3816-e

Ref use case links

2022-02-17 Thread Uma gangumalla
Hi Devs, I have a quick question: Do we have any wiki page which will have the links to current user use cases? If not, it may be a good idea to have one and provide the links. Links can be like: Any presentation slides about deployment use cases etc Regards, Uma

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

2022-02-17 Thread Uma gangumalla
I have just fixed the broken links in Wiki. Ethan also pointed about these in offline chat. Thanks On Thu, Feb 17, 2022 at 11:40 AM Uma gangumalla wrote: > Thanks Sidd for pointing that out. Yes I used ref doc from FSO, my bad > some link left out I think. I will fix it. > Thanks Arpit. > > Othe

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

2022-02-17 Thread Uma gangumalla
Thanks Sidd for pointing that out. Yes I used ref doc from FSO, my bad some link left out I think. I will fix it. Thanks Arpit. Others, please provide your feedback if any, otherwise we move to official vote soon after we track down the compat related issues. Regards, Uma On Thu, Feb 17, 2022 at

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

2022-02-17 Thread Siddharth Wagle
+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

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

2022-02-17 Thread Arpit Agarwal
Thanks for the detailed explanation. +1 to merge with HDDS-6209 addressed. > On Feb 16, 2022, at 10:49 AM, Uma gangumalla wrote: > > Thanks a lot Arpit for your feedback. > > [Arpit Wrote] - New client writing to old server with 3-way and 1-way > replication. > [Uma] As mentioned in the propo