Re: [VOTE] create ozone-dev and ozone-issues mailing lists
+1 (non-binding) On Sun, Oct 27, 2019 at 1:55 PM Elek, Marton wrote: > > As discussed earlier in the thread of "Hadoop-Ozone repository mailing > list configurations" [1] I suggested to solve the current > misconfiguration problem with creating separated mailing lists > (dev/issues) for Hadoop Ozone. > > It would have some additional benefit: for example it would make easier > to follow the Ozone development and future plans. > > Here I am starting a new vote thread (open for at least 72 hours) to > collect more feedback about this. > > Please express your opinion / vote. > > Thanks a lot, > Marton > > [1] > > https://lists.apache.org/thread.html/dc66a30f48a744534e748c418bf7ab6275896166ca5ade11560ebaef@%3Chdfs-dev.hadoop.apache.org%3E > > - > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > -- * Regards* * Sandeep Nemuri*
Re: [DISCUSS] Remove Ozone and Submarine from Hadoop repo
Tracking Ozone/HDDS modules here : https://issues.apache.org/jira/browse/HADOOP-16654 On Thu, Oct 24, 2019 at 1:21 PM 张铎(Duo Zhang) wrote: > +1 > > Akira Ajisaka 于2019年10月24日周四 下午3:21写道： > > > Hi folks, > > > > Both Ozone and Apache Submarine have separate repositories. > > Can we remove these modules from hadoop-trunk? > > > > Regards, > > Akira > > > -- * Regards* * Sandeep Nemuri*
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree
+1 (non-binding) On Wed, Sep 18, 2019 at 5:33 AM Weiwei Yang wrote: > +1 (binding) > > Thanks > Weiwei > > On Wed, Sep 18, 2019 at 6:35 AM Wangda Tan wrote: > > > +1 (binding). > > > > From my experiences of Submarine project, I think moving to a separate > repo > > helps. > > > > - Wangda > > > > On Tue, Sep 17, 2019 at 11:41 AM Subru Krishnan > wrote: > > > > > +1 (binding). > > > > > > IIUC, there will not be an Ozone module in trunk anymore as that was my > > > only concern from the original discussion thread? IMHO, this should be > > the > > > default approach for new modules. > > > > > > On Tue, Sep 17, 2019 at 9:58 AM Salvatore LaMendola (BLOOMBERG/ 731 > LEX) > > < > > > slamendo...@bloomberg.net> wrote: > > > > > > > +1 > > > > > > > > From: e...@apache.org At: 09/17/19 05:48:32To: > > > hdfs-...@hadoop.apache.org, > > > > mapreduce-...@hadoop.apache.org, common-dev@hadoop.apache.org, > > > > yarn-...@hadoop.apache.org > > > > Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk > > > > source tree > > > > > > > > > > > > TLDR; I propose to move Ozone related code out from Hadoop trunk and > > > > store it in a separated *Hadoop* git repository > apache/hadoop-ozone.git > > > > > > > > > > > > When Ozone was adopted as a new Hadoop subproject it was proposed[1] > to > > > > be part of the source tree but with separated release cadence, mainly > > > > because it had the hadoop-trunk/SNAPSHOT as compile time dependency. > > > > > > > > During the last Ozone releases this dependency is removed to provide > > > > more stable releases. Instead of using the latest trunk/SNAPSHOT > build > > > > from Hadoop, Ozone uses the latest stable Hadoop (3.2.0 as of now). > > > > > > > > As we have no more strict dependency between Hadoop trunk SNAPSHOT > and > > > > Ozone trunk I propose to separate the two code base from each other > > with > > > > creating a new Hadoop git repository (apache/hadoop-ozone.git): > > > > > > > > With moving Ozone to a separated git repository: > > > > > > > > * It would be easier to contribute and understand the build (as of > > now > > > > we always need `-f pom.ozone.xml` as a Maven parameter) > > > > * It would be possible to adjust build process without breaking > > > > Hadoop/Ozone builds. > > > > * It would be possible to use different Readme/.asf.yaml/github > > > > template for the Hadoop Ozone and core Hadoop. (For example the > current > > > > github template [2] has a link to the contribution guideline [3]. > Ozone > > > > has an extended version [4] from this guideline with additional > > > > information.) > > > > * Testing would be more safe as it won't be possible to change core > > > > Hadoop and Hadoop Ozone in the same patch. > > > > * It would be easier to cut branches for Hadoop releases (based on > > the > > > > original consensus, Ozone should be removed from all the release > > > > branches after creating relase branches from trunk) > > > > > > > > > > > > What do you think? > > > > > > > > Thanks, > > > > Marton > > > > > > > > [1]: > > > > > > > > > > > > > > https://lists.apache.org/thread.html/c85e5263dcc0ca1d13cbbe3bcfb53236784a39111b8 > > > > c353f60582eb4@%3Chdfs-dev.hadoop.apache.org%3E > > > > [2]: > > > > > > > > > > > > > > https://github.com/apache/hadoop/blob/trunk/.github/pull_request_template.md > > > > [3]: > > > https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute > > > > [4]: > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute+to+Ozone > > > > > > > > - > > > > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > > > > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > > > > > > > > > > > > > > > > -- * Regards* * Sandeep Nemuri*
Re: [VOTE] Move Submarine source code, documentation, etc. to a separate Apache Git repo
+1 (non-binding) On Mon, Aug 26, 2019 at 9:59 PM Wei-Chiu Chuang wrote: > +1 > given the scope of the future of Submarine, I think that makes sense. > I am also happy to see Hadoop contributors being able to commit to > Submarine repo. I think that'll help grow the Submarine community in the > long run. > > On Mon, Aug 26, 2019 at 9:26 AM Ayush Saxena wrote: > > > +1 > > > > -Ayush > > > On 26-Aug-2019, at 9:45 PM, Bharat Viswanadham < > > bviswanad...@cloudera.com.invalid> wrote: > > > > > > +1 (non-binding) > > > > > > Thanks, > > > Bharat > > > > > > On Mon, Aug 26, 2019 at 9:13 AM Sean Busbey > > > > > > wrote: > > > > > >> +1 (non-binding) > > >> > > >>> On Fri, Aug 23, 2019 at 9:06 PM Wangda Tan > > wrote: > > >>> > > >>> Hi devs, > > >>> > > >>> This is a voting thread to move Submarine source code, documentation > > from > > >>> Hadoop repo to a separate Apache Git repo. Which is based on > > discussions > > >> of > > >>> > > >> > > > https://lists.apache.org/thread.html/e49d60b2e0e021206e22bb2d430f4310019a8b29ee5020f3eea3bd95@%3Cyarn-dev.hadoop.apache.org%3E > > >>> > > >>> Contributors who have permissions to push to Hadoop Git repository > will > > >>> have permissions to push to the new Submarine repository. > > >>> > > >>> This voting thread will run for 7 days and will end at Aug 30th. > > >>> > > >>> Please let me know if you have any questions. > > >>> > > >>> Thanks, > > >>> Wangda Tan > > >> > > >> > > >> > > >> -- > > >> busbey > > >> > > >> - > > >> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > > >> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > >> > > >> > > > -- * Regards* * Sandeep Nemuri*
Re: [VOTE]: Hadoop Ozone 0.4.0-alpha RC0 release
Thanks Ajay for working on release. We've found an issue in DN where the root filesystem is getting filled after running the cluster for a while. This is because after importing a container successfully, datanode is not deleting the container tar.gz file from working directory(/tmp by default). More details in https://issues.apache.org/jira/browse/HDDS-1417 Thanks Sandeep On Tue, Apr 9, 2019 at 3:55 AM Ajay Kumar wrote: > Hi all, > > > > We have created the first release candidate (RC0) for Apache Hadoop Ozone > 0.4.0-alpha. > > > > This release contains security payload for Ozone. Below are some important > features in it: > > * Hadoop Delegation Tokens and Block Tokens supported for Ozone. > * Transparent Data Encryption (TDE) Support - Allows data blocks to be > encrypted-at-rest. > * Kerberos support for Ozone. > * Certificate Infrastructure for Ozone - Tokens use PKI instead of > shared secrets. > * Datanode to Datanode communication secured via mutual TLS. > * Ability secure ozone cluster that works with Yarn, Hive, and Spark. > * Skaffold support to deploy Ozone clusters on K8s. > * Support S3 Authentication Mechanisms like - S3 v4 Authentication > protocol. > * S3 Gateway supports Multipart upload. > * S3A file system is tested and supported. > * Support for Tracing and Profiling for all Ozone components. > * Audit Support - including Audit Parser tools. > * Apache Ranger Support in Ozone. > * Extensive failure testing for Ozone. > > > The RC artifacts are available at > https://home.apache.org/~ajay/ozone-0.4.0-alpha-rc0 > > > > The RC tag in git is ozone-0.4.0-alpha-RC0 (git hash > e5df6e94a5137b84cf7a6ee2e0ef7a8dae1b11a1) > > > > Please try out< > https://cwiki.apache.org/confluence/display/HADOOP/Running+via+Apache+Release>, > vote, or just give us feedback. > > > > The vote will run for 5 days, ending on April 13, 2019, 19:00 UTC. > > > > Thank you very much, > > Ajay > > -- * Regards* * Sandeep Nemuri*
Re: [VOTE] Propose to start new Hadoop sub project "submarine"
+1 (non-binding) On Mon, Feb 4, 2019 at 10:24 PM Xiaoyu Yao wrote: > +1 > > -Xiaoyu > > Sent from my iPhone > > > On Feb 4, 2019, at 7:54 AM, Suma Shivaprasad < > sumasai.shivapra...@gmail.com> wrote: > > > > +1 ( non binding) > > > > On Mon, Feb 4, 2019 at 7:23 AM Shashikant Banerjee < > > sbaner...@hortonworks.com> wrote: > > > >> +1 (non-binding) > >> > >> Thanks > >> Shashi > >> > >> On 2/4/19, 8:27 PM, "Elek, Marton" wrote: > >> > >>+1 (non-binding) > >> > >>(my arguments are in the discuss thread. small move, huge benefit) > >> > >>Thanks, > >>Marton > >> > >>>On 2/1/19 11:15 PM, Wangda Tan wrote: > >>> Hi all, > >>> > >>> According to positive feedbacks from the thread [1] > >>> > >>> This is vote thread to start a new subproject named > >> "hadoop-submarine" > >>> which follows the release process already established for ozone. > >>> > >>> The vote runs for usual 7 days, which ends at Feb 8th 5 PM PDT. > >>> > >>> Thanks, > >>> Wangda Tan > >>> > >>> [1] > >>> > >> > https://lists.apache.org/thread.html/f864461eb188bd12859d51b0098ec38942c4429aae7e4d001a633d96@%3Cyarn-dev.hadoop.apache.org%3E > >>> > >> > >>--------- > >>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: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > -- * Regards* * Sandeep Nemuri*
Re: [VOTE] - HDDS-4 Branch merge
+1 (non-binding) On Sat, Jan 12, 2019 at 8:49 AM Bharat Viswanadham < bviswanad...@hortonworks.com> wrote: > +1 (binding) > > > Thanks, > Bharat > > > On 1/11/19, 11:04 AM, "Hanisha Koneru" wrote: > > +1 (binding) > > Thanks, > Hanisha > > > > > > > > > > On 1/11/19, 7:40 AM, "Anu Engineer" wrote: > > >Since I have not heard any concerns, I will start a VOTE thread now. > >This vote will run for 7 days and will end on Jan/18/2019 @ 8:00 AM > PST. > > > >I will start with my vote, +1 (Binding) > > > >Thanks > >Anu > > > > > >-- Forwarded message - > >From: Anu Engineer > >Date: Mon, Jan 7, 2019 at 5:10 PM > >Subject: [Discuss] - HDDS-4 Branch merge > >To: , > > > > > >Hi All, > > > >I would like to propose a merge of HDDS-4 branch to the Hadoop trunk. > >HDDS-4 branch implements the security work for HDDS and Ozone. > > > >HDDS-4 branch contains the following features: > >- Hadoop Kerberos and Tokens support > >- A Certificate infrastructure used by Ozone and HDDS. > >- Audit Logging and parsing support (Spread across trunk and > HDDS-4) > >- S3 Security Support - AWS Signature Support. > >- Apache Ranger Support for Ozone > > > >I will follow up with a formal vote later this week if I hear no > >objections. AFAIK, the changes are isolated to HDDS/Ozone and should > not > >impact any other Hadoop project. > > > >Thanks > >Anu > > - > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > -- * Regards* * Sandeep Nemuri*
Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)
Hi Marton, +1 (non-binding) - Verified the Signature. - Built from source. - Ran Robot tests to verify all RPC and Rest commands. - Deployed Pseudo ozone cluster and verified basic commands. Thanks, Sandeep Nemuri On Thu, Sep 20, 2018 at 3:19 AM Elek, Marton wrote: > Hi all, > > After the recent discussion about the first Ozone release I've created > the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. > > This release is alpha quality: it’s not recommended to use in production > but we believe that it’s stable enough to try it out the feature set and > collect feedback. > > The RC artifacts are available from: > https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/ > > The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d) > > Please try the release and vote; the vote will run for the usual 5 > working days, ending on September 26, 2018 10pm UTC time. > > The easiest way to try it out is: > > 1. Download the binary artifact > 2. Read the docs at ./docs/index.html > 3. TLDR; cd compose/ozone && docker-compose up -d > > > Please try it out, vote, or just give us feedback. > > Thank you very much, > Marton > > ps: At next week, we will have a BoF session at ApacheCon North Europe, > Montreal on Monday evening. Please join, if you are interested, or need > support to try out the package or just have any feedback. > > > - > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > -- * Regards* * Sandeep Nemuri*
