+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 merge the Ozone S3
> Multi-Tenancy feature branch (HDDS-4944) to the master branch.
>
> S3 multi-tenancy allows multiple S3-accessible vol
+1 for the merge. Thanks for the great work!
On Wed, Apr 6, 2022 at 9:45 PM Prashant Pogde
wrote:
> +1 for the EC branch merge.
>
> Regards,
> Prashant
>
> > On Apr 6, 2022, at 8:20 PM, Siddharth Wagle wrote:
> >
> > +1 for the EC branch merge.
> >
> > Best,
> > Sid
> >
> > On Wed, Apr 6, 202
+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
at 1:49 AM, Xiaoyu Yao wrote:
> >> >>>
> >> >>> +1
> >> >>>
> >> >>>> On Thu, Aug 26, 2021 at 12:23 PM Ethan Rose
> >> >> >>>
> >> >>>> wrote:
> >> >>>>
&g
Hello all,
It has been a few months since the Ozone 1.1.0 release, and we have had a
number of features (SCM HA, FSO, Non rolling upgrades) that have been
merged to master since then. I think this would be a good time to work on
the Ozone 1.2.0 release. Also, Ethan has volunteered to take up the r
ontinuous improvements.
>
> Marton
>
> On 6/21/21 8:04 PM, Aravindan Vijayan wrote:
> > Hello all,
> >
> > I'd like to start a formal VOTE to merge the non-rolling upgrades in
> Ozone
> > (HDDS-3698-nonrolling-upgrade) into the Ozone master branch. Please refer
Hello all,
I'd like to start a formal VOTE to merge the non-rolling upgrades in Ozone
(HDDS-3698-nonrolling-upgrade) into the Ozone master branch. Please refer
to the DISCUSS mail for the details of the design and implementation.
The github feature branch is here:
https://github.com/apache/ozone
Hello All,
Circling back to the upgrade branch VOTE thread after fixing issues
mentioned from last vote, and incorporating changes from HDDS-2939. Please
refer to the original VOTE mail for the details of the design and
implementation.
The github feature branch is here:
https://github.com/apache
+1 for merging HDDS-2939 to master. Thanks for driving this Rakesh.
On Wed, Jun 2, 2021 at 9:01 PM Arpit Agarwal
wrote:
> +1 for merging this feature to master.
>
>
> > On May 31, 2021, at 12:54 AM, Rakesh Radhakrishnan
> wrote:
> >
> > Hi All,
> >
> > Based on the positive feedback from the me
he
> framework of the feature itself is stable
> and will not do harm to any other parts. And it is a really big step
> towards the future 'rolling upgrade'.
> As elek pointed, there are some issues needs to be fixed, and I'd be very
> glad to help fix them :)
>
>
Since I do not see any objections to the DISCUSS thread, moving this to
VOTE thread.
On Mon, Apr 19, 2021 at 10:04 AM Aravindan Vijayan
wrote:
> Hello all,
>
> I would like to propose merging the work done for supporting non rolling
> upgrades in Ozone (HDDS-3698-nonrolling-upgra
han, 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
Thank you for reviewing this Marton!
The --upgrade flag is needed for the OM since it needs to be brought out of
"prepared" state after an upgrade.
Right now, there is no need to prepare an SCM, and hence support has not
been added for that. Hence, there is no --upgrade flag while starting SCM.
Hello all,
I would like to propose merging the work done for supporting non rolling
upgrades in Ozone (HDDS-3698-nonrolling-upgrade) into the Ozone master
branch.
As part of the upgrade framework, the following have been added
- Ability to create layout features & versions
- Ability to fin
+1 to merging this feature.
Rakesh, I will work with you to onboard this onto upgrades, which is also
close to merge.
On Fri, Apr 9, 2021 at 8:35 AM Ayush Saxena wrote:
> Thanx Rakesh for driving this.
> Quickly tried some basic stuff with this. Looks good.
>
> +1, Good Luck!!!
>
> -Ayush
>
> >
Thanks for working on this Prashant.
I see that the rc0 artifacts are incorrectly tagged as "*alpha*". Can we
remove that from the artifact names?
On Fri, Apr 2, 2021 at 6:15 PM Prashant Pogde
wrote:
> This Ozone 1.1.0 release includes 493 JIRAs,
>
>
> https://issues.apache.org/jira/issues/?jql
+1 for the merge. Thanks for working on this!
On Thu, Mar 18, 2021 at 11:20 PM Prashant Pogde
wrote:
> I have created 1.1.0-RC0 branch and we can promote this branch to 1.1.0
> later. We can continue merge to master.
>
> > On Mar 18, 2021, at 8:08 PM, Prashant Pogde wrote:
> >
> > +1
> >
> > I
+1 for the Go client.
On Thu, Mar 4, 2021, 8:34 PM Yi-Sheng Lien wrote:
> +1
> Thank you Marton for the idea.
>
> Yi-Sheng
>
> On Thu, Mar 4, 2021 at 7:53 PM Lokesh Jain
> wrote:
>
> > +1
> >
> > Regards
> > Lokesh
> >
> > > On 03-Mar-2021, at 9:57 PM, Xiaoyu Yao
> > wrote:
> > >
> > > +1
> >
Thanks for taking this up Marton.
I played around with Github issues, projects & milestones. I like the
simplicity of the UI and the one stop place for all things related to
development. However, the objection around the project management related
limitations of Github seem valid. I am OK with try
+1 for this proposal. Thanks Marton!
On Mon, Nov 2, 2020 at 12:49 AM Elek, Marton wrote:
>
>
> Hi,
>
> Today https://github.com/apache/ozone-docker repository contains the
> source of apache/ozone, apache/ozone-runner and apache/ozone-build
> docker images.
>
> As we had a subproject of Hadoop w
20 matches
Mail list logo
