Re: [DISCUSS] Alpha Release of Ozone
Thank you all the feedback about the first ozone release. I just cut ozone-0.2 branch from trunk. This will be the base of the first ozone release. I changed ozone/hdds version on the trunk to 0.3.0-SNAPSHOT. Marton On 08/06/2018 07:34 PM, Elek, Marton wrote: Hi All, I would like to discuss creating an Alpha release for Ozone. The core functionality of Ozone is complete but there are two missing features; Security and HA, work on these features are progressing in Branches HDDS-4 and HDDS-151. Right now, Ozone can handle millions of keys and has a Hadoop compatible file system, which allows applications like Hive, Spark, and YARN use Ozone. Having an Alpha release of Ozone will help in getting some early feedback (this release will be marked as an Alpha -- and not production ready). Going through a complete release cycle will help us flush out Ozone release process, update user documentation and nail down deployment models. Please share your thoughts on the Alpha release (over mail or in HDDS-214), as voted on by the community earlier, Ozone release will be independent of Hadoop releases. Thanks a lot, Marton Elek - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org - To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
Re: [DISCUSS] Alpha Release of Ozone
Thanks for reporting this issue. I have filed a JIRA to address this issue. https://issues.apache.org/jira/browse/HDDS-341 >So, consider this as a report. IMHO, cutting an Ozone release prior to a >Hadoop release ill-advised given the distribution impact and the requirements >of the merge vote. The Ozone release is being planned to address issues like these; In my mind if we go thru a release exercise, we will be able to identify all ozone and Hadoop related build and release issues. Ozone will tremendously benefit from a release exercise and the community review that comes from that. Thanks Anu On 8/8/18, 1:19 PM, "Allen Wittenauer" wrote: > On Aug 8, 2018, at 12:56 PM, Anu Engineer wrote: > >> Has anyone verified that a Hadoop release doesn't have _any_ of the extra ozone bits that are sprinkled outside the maven modules? > As far as I know that is the state, we have had multiple Hadoop releases after ozone has been merged. So far no one has reported Ozone bits leaking into Hadoop. If we find something like that, it would be a bug. There hasn't been a release from a branch where Ozone has been merged yet. The first one will be 3.2.0. Running create-release off of trunk presently shows bits of Ozone in dev-support, hadoop-dist, and elsewhere in the Hadoop source tar ball. So, consider this as a report. IMHO, cutting an Ozone release prior to a Hadoop release ill-advised given the distribution impact and the requirements of the merge vote.
Re: [DISCUSS] Alpha Release of Ozone
> On Aug 8, 2018, at 12:56 PM, Anu Engineer wrote: > >> Has anyone verified that a Hadoop release doesn't have _any_ of the extra >> ozone bits that are sprinkled outside the maven modules? > As far as I know that is the state, we have had multiple Hadoop releases > after ozone has been merged. So far no one has reported Ozone bits leaking > into Hadoop. If we find something like that, it would be a bug. There hasn't been a release from a branch where Ozone has been merged yet. The first one will be 3.2.0. Running create-release off of trunk presently shows bits of Ozone in dev-support, hadoop-dist, and elsewhere in the Hadoop source tar ball. So, consider this as a report. IMHO, cutting an Ozone release prior to a Hadoop release ill-advised given the distribution impact and the requirements of the merge vote. - To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
Re: [DISCUSS] Alpha Release of Ozone
> Given that there are some Ozone components spread out past the core maven > modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more > work going to go into segregating the Ozone components prior to release? The official release will be a source tarball, we intend to release an ozone only binaries to make it easy to for people to deploy. We are still formulating the plans and you are welcome to leave your comments on HDDS-214. > Has anyone verified that a Hadoop release doesn't have _any_ of the extra > ozone bits that are sprinkled outside the maven modules? As far as I know that is the state, we have had multiple Hadoop releases after ozone has been merged. So far no one has reported Ozone bits leaking into Hadoop. If we find something like that, it would be a bug. Thanks Anu On 8/8/18, 12:04 PM, "Allen Wittenauer" wrote: Given that there are some Ozone components spread out past the core maven modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more work going to go into segregating the Ozone components prior to release? Has anyone verified that a Hadoop release doesn't have _any_ of the extra ozone bits that are sprinkled outside the maven modules? - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org - To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
Re: [DISCUSS] Alpha Release of Ozone
Given that there are some Ozone components spread out past the core maven modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more work going to go into segregating the Ozone components prior to release? Has anyone verified that a Hadoop release doesn't have _any_ of the extra ozone bits that are sprinkled outside the maven modules? - To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
RE: [DISCUSS] Alpha Release of Ozone
+1. Looking forward to try the fresh Ozone release. Bests, Sammi -Original Message- From: Elek, Marton [mailto:e...@apache.org] Sent: Tuesday, August 7, 2018 1:34 AM To: common-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org; hdfs-...@hadoop.apache.org Subject: [DISCUSS] Alpha Release of Ozone Hi All, I would like to discuss creating an Alpha release for Ozone. The core functionality of Ozone is complete but there are two missing features; Security and HA, work on these features are progressing in Branches HDDS-4 and HDDS-151. Right now, Ozone can handle millions of keys and has a Hadoop compatible file system, which allows applications like Hive, Spark, and YARN use Ozone. Having an Alpha release of Ozone will help in getting some early feedback (this release will be marked as an Alpha -- and not production ready). Going through a complete release cycle will help us flush out Ozone release process, update user documentation and nail down deployment models. Please share your thoughts on the Alpha release (over mail or in HDDS-214), as voted on by the community earlier, Ozone release will be independent of Hadoop releases. Thanks a lot, Marton Elek - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org - To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
Re: [DISCUSS] Alpha Release of Ozone
+1. Good to see the progress here and would like to try Ozone on real cluster. Thanks, Junping 2018-08-07 1:34 GMT+08:00 Elek, Marton : > Hi All, > > I would like to discuss creating an Alpha release for Ozone. The core > functionality of Ozone is complete but there are two missing features; > Security and HA, work on these features are progressing in Branches HDDS-4 > and HDDS-151. Right now, Ozone can handle millions of keys and has a Hadoop > compatible file system, which allows applications like Hive, Spark, and > YARN use Ozone. > > Having an Alpha release of Ozone will help in getting some early feedback > (this release will be marked as an Alpha -- and not production ready). > > Going through a complete release cycle will help us flush out Ozone > release process, update user documentation and nail down deployment models. > > Please share your thoughts on the Alpha release (over mail or in > HDDS-214), as voted on by the community earlier, Ozone release will be > independent of Hadoop releases. > > Thanks a lot, > Marton Elek > > > > > - > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org > >
Re: [DISCUSS] Alpha Release of Ozone
+1, It will allow many users to get a first look at Ozone/HDDS. Thanks Anu On 8/6/18, 10:34 AM, "Elek, Marton" wrote: Hi All, I would like to discuss creating an Alpha release for Ozone. The core functionality of Ozone is complete but there are two missing features; Security and HA, work on these features are progressing in Branches HDDS-4 and HDDS-151. Right now, Ozone can handle millions of keys and has a Hadoop compatible file system, which allows applications like Hive, Spark, and YARN use Ozone. Having an Alpha release of Ozone will help in getting some early feedback (this release will be marked as an Alpha -- and not production ready). Going through a complete release cycle will help us flush out Ozone release process, update user documentation and nail down deployment models. Please share your thoughts on the Alpha release (over mail or in HDDS-214), as voted on by the community earlier, Ozone release will be independent of Hadoop releases. Thanks a lot, Marton Elek - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
