You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Elek, Marton" <el...@apache.org> on 2020/05/13 07:52:36 UTC
[DISCUSS] making Ozone a separate Apache project
I would like to start a discussion to make a separate Apache project for
Ozone
### HISTORY [1]
* Apache Hadoop Ozone development started on a feature branch of
Hadoop repository (HDFS-7240)
* In the October of 2017 a discussion has been started to merge it to
the Hadoop main branch
* After a long discussion it's merged to Hadoop trunk at the March of 2018
* During the discussion of the merge, it was suggested multiple times
to create a separated project for the Ozone. But at that time:
1). Ozone was tightly integrated with Hadoop/HDFS
2). There was an active plan to use Block layer of Ozone (HDDS or
HDSL at that time) as the block level of HDFS
3). The community of Ozone was a subset of the HDFS community
* The first beta release of Ozone was just released. Seems to be a
good time before the first GA to make a decision about the future.
### WHAT HAS BEEN CHANGED
During the last years Ozone became more and more independent both at
the community and code side. The separation has been suggested again and
again (for example by Owen [2] and Vinod [3])
From COMMUNITY point of view:
* Fortunately more and more new contributors are helping Ozone.
Originally the Ozone community was a subset of HDFS project. But now a
bigger and bigger part of the community is related to Ozone only.
* It seems to be easier to _build_ the community as a separated project.
* A new, younger project might have different practices
(communication, commiter criteria, development style) compared to old,
mature project
* It's easier to communicate (and improve) these standards in a
separated projects with clean boundaries
* Separated project/brand can help to increase the adoption rate and
attract more individual contributor (AFAIK it has been seen in Submarine
after a similar move)
* Contribution process can be communicated more easily, we can make
first time contribution more easy
From CODE point of view Ozone became more and more independent:
* Ozone has different release cycle
* Code is already separated from Hadoop code base
(apache/hadoop-ozone.git)
* It has separated CI (github actions)
* Ozone uses different (more strict) coding style (zero toleration of
unit test / checkstyle errors)
* The code itself became more and more independent from Hadoop on
Maven level. Originally it was compiled together with the in-tree latest
Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
Configuration...)
* It starts to use multiple version of Hadoop (on client side)
* Volume of resolved issues are already very high on Ozone side (Ozone
had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
together in the last 2-3 months)
Summary: Before the first Ozone GA release, It seems to be a good time
to discuss the long-term future of Ozone. Managing it as a separated TLP
project seems to have more benefits.
Please let me know what your opinion is...
Thanks a lot,
Marton
[1]: For more details, see:
https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
[2]:
https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
[3]:
https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Brahma Reddy Battula <br...@apache.org>.
+1
On Sat, 16 May 2020 at 12:09 AM, Subru Krishnan <su...@apache.org> wrote:
> +1.
>
> Thanks,
> Subru
>
> On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org>
> wrote:
>
> > +1
> >
> > -Akira
> >
> > On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> >
>
--
--Brahma Reddy Battula
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Brahma Reddy Battula <br...@apache.org>.
+1
On Sat, 16 May 2020 at 12:09 AM, Subru Krishnan <su...@apache.org> wrote:
> +1.
>
> Thanks,
> Subru
>
> On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org>
> wrote:
>
> > +1
> >
> > -Akira
> >
> > On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> >
>
--
--Brahma Reddy Battula
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Brahma Reddy Battula <br...@apache.org>.
+1
On Sat, 16 May 2020 at 12:09 AM, Subru Krishnan <su...@apache.org> wrote:
> +1.
>
> Thanks,
> Subru
>
> On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org>
> wrote:
>
> > +1
> >
> > -Akira
> >
> > On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> >
>
--
--Brahma Reddy Battula
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Brahma Reddy Battula <br...@apache.org>.
+1
On Sat, 16 May 2020 at 12:09 AM, Subru Krishnan <su...@apache.org> wrote:
> +1.
>
> Thanks,
> Subru
>
> On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org>
> wrote:
>
> > +1
> >
> > -Akira
> >
> > On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> >
>
--
--Brahma Reddy Battula
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Brahma Reddy Battula <br...@apache.org>.
+1
On Sat, 16 May 2020 at 12:09 AM, Subru Krishnan <su...@apache.org> wrote:
> +1.
>
> Thanks,
> Subru
>
> On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org>
> wrote:
>
> > +1
> >
> > -Akira
> >
> > On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> >
>
--
--Brahma Reddy Battula
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Subru Krishnan <su...@apache.org>.
+1.
Thanks,
Subru
On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org> wrote:
> +1
>
> -Akira
>
> On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Subru Krishnan <su...@apache.org>.
+1.
Thanks,
Subru
On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org> wrote:
> +1
>
> -Akira
>
> On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Subru Krishnan <su...@apache.org>.
+1.
Thanks,
Subru
On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org> wrote:
> +1
>
> -Akira
>
> On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Subru Krishnan <su...@apache.org>.
+1.
Thanks,
Subru
On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org> wrote:
> +1
>
> -Akira
>
> On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Subru Krishnan <su...@apache.org>.
+1.
Thanks,
Subru
On Thu, May 14, 2020 at 10:00 PM Akira Ajisaka <aa...@apache.org> wrote:
> +1
>
> -Akira
>
> On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Akira Ajisaka <aa...@apache.org>.
+1
-Akira
On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Mingliang Liu <li...@gmail.com>.
+1
On Mon, May 18, 2020 at 12:37 AM Elek, Marton <el...@apache.org> wrote:
>
>
> > One question, for the committers who contributed to Ozone before and got
> > the committer-role in the past (like me), will they carry the
> > committer-role to the new repo?
>
>
> In short: yes.
>
>
> In more details:
>
> This discussion (if there is an agreement) should be followed by a next
> discussion + vote about a very specific proposal which should contain
> all the technical information (including committer list)
>
> I support the the same approach what we followed with Submarine:
>
> ALL the existing (Hadoop) committers should have a free / opt-in
> opportunity to be a committer in Ozone.
>
> (After proposal is created on the wiki, you can add your name, or
> request to be added. But as the initial list can be created based on
> statistics from the Jira, your name can be already there ;-) )
>
>
>
> Marton
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
--
L
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Mingliang Liu <li...@gmail.com>.
+1
On Mon, May 18, 2020 at 12:37 AM Elek, Marton <el...@apache.org> wrote:
>
>
> > One question, for the committers who contributed to Ozone before and got
> > the committer-role in the past (like me), will they carry the
> > committer-role to the new repo?
>
>
> In short: yes.
>
>
> In more details:
>
> This discussion (if there is an agreement) should be followed by a next
> discussion + vote about a very specific proposal which should contain
> all the technical information (including committer list)
>
> I support the the same approach what we followed with Submarine:
>
> ALL the existing (Hadoop) committers should have a free / opt-in
> opportunity to be a committer in Ozone.
>
> (After proposal is created on the wiki, you can add your name, or
> request to be added. But as the initial list can be created based on
> statistics from the Jira, your name can be already there ;-) )
>
>
>
> Marton
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
--
L
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Mingliang Liu <li...@gmail.com>.
+1
On Mon, May 18, 2020 at 12:37 AM Elek, Marton <el...@apache.org> wrote:
>
>
> > One question, for the committers who contributed to Ozone before and got
> > the committer-role in the past (like me), will they carry the
> > committer-role to the new repo?
>
>
> In short: yes.
>
>
> In more details:
>
> This discussion (if there is an agreement) should be followed by a next
> discussion + vote about a very specific proposal which should contain
> all the technical information (including committer list)
>
> I support the the same approach what we followed with Submarine:
>
> ALL the existing (Hadoop) committers should have a free / opt-in
> opportunity to be a committer in Ozone.
>
> (After proposal is created on the wiki, you can add your name, or
> request to be added. But as the initial list can be created based on
> statistics from the Jira, your name can be already there ;-) )
>
>
>
> Marton
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
--
L
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Mingliang Liu <li...@gmail.com>.
+1
On Mon, May 18, 2020 at 12:37 AM Elek, Marton <el...@apache.org> wrote:
>
>
> > One question, for the committers who contributed to Ozone before and got
> > the committer-role in the past (like me), will they carry the
> > committer-role to the new repo?
>
>
> In short: yes.
>
>
> In more details:
>
> This discussion (if there is an agreement) should be followed by a next
> discussion + vote about a very specific proposal which should contain
> all the technical information (including committer list)
>
> I support the the same approach what we followed with Submarine:
>
> ALL the existing (Hadoop) committers should have a free / opt-in
> opportunity to be a committer in Ozone.
>
> (After proposal is created on the wiki, you can add your name, or
> request to be added. But as the initial list can be created based on
> statistics from the Jira, your name can be already there ;-) )
>
>
>
> Marton
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
--
L
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Mingliang Liu <li...@gmail.com>.
+1
On Mon, May 18, 2020 at 12:37 AM Elek, Marton <el...@apache.org> wrote:
>
>
> > One question, for the committers who contributed to Ozone before and got
> > the committer-role in the past (like me), will they carry the
> > committer-role to the new repo?
>
>
> In short: yes.
>
>
> In more details:
>
> This discussion (if there is an agreement) should be followed by a next
> discussion + vote about a very specific proposal which should contain
> all the technical information (including committer list)
>
> I support the the same approach what we followed with Submarine:
>
> ALL the existing (Hadoop) committers should have a free / opt-in
> opportunity to be a committer in Ozone.
>
> (After proposal is created on the wiki, you can add your name, or
> request to be added. But as the initial list can be created based on
> statistics from the Jira, your name can be already there ;-) )
>
>
>
> Marton
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
--
L
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
> One question, for the committers who contributed to Ozone before and got
> the committer-role in the past (like me), will they carry the
> committer-role to the new repo?
In short: yes.
In more details:
This discussion (if there is an agreement) should be followed by a next
discussion + vote about a very specific proposal which should contain
all the technical information (including committer list)
I support the the same approach what we followed with Submarine:
ALL the existing (Hadoop) committers should have a free / opt-in
opportunity to be a committer in Ozone.
(After proposal is created on the wiki, you can add your name, or
request to be added. But as the initial list can be created based on
statistics from the Jira, your name can be already there ;-) )
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
> One question, for the committers who contributed to Ozone before and got
> the committer-role in the past (like me), will they carry the
> committer-role to the new repo?
In short: yes.
In more details:
This discussion (if there is an agreement) should be followed by a next
discussion + vote about a very specific proposal which should contain
all the technical information (including committer list)
I support the the same approach what we followed with Submarine:
ALL the existing (Hadoop) committers should have a free / opt-in
opportunity to be a committer in Ozone.
(After proposal is created on the wiki, you can add your name, or
request to be added. But as the initial list can be created based on
statistics from the Jira, your name can be already there ;-) )
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
> One question, for the committers who contributed to Ozone before and got
> the committer-role in the past (like me), will they carry the
> committer-role to the new repo?
In short: yes.
In more details:
This discussion (if there is an agreement) should be followed by a next
discussion + vote about a very specific proposal which should contain
all the technical information (including committer list)
I support the the same approach what we followed with Submarine:
ALL the existing (Hadoop) committers should have a free / opt-in
opportunity to be a committer in Ozone.
(After proposal is created on the wiki, you can add your name, or
request to be added. But as the initial list can be created based on
statistics from the Jira, your name can be already there ;-) )
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
> One question, for the committers who contributed to Ozone before and got
> the committer-role in the past (like me), will they carry the
> committer-role to the new repo?
In short: yes.
In more details:
This discussion (if there is an agreement) should be followed by a next
discussion + vote about a very specific proposal which should contain
all the technical information (including committer list)
I support the the same approach what we followed with Submarine:
ALL the existing (Hadoop) committers should have a free / opt-in
opportunity to be a committer in Ozone.
(After proposal is created on the wiki, you can add your name, or
request to be added. But as the initial list can be created based on
statistics from the Jira, your name can be already there ;-) )
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
> One question, for the committers who contributed to Ozone before and got
> the committer-role in the past (like me), will they carry the
> committer-role to the new repo?
In short: yes.
In more details:
This discussion (if there is an agreement) should be followed by a next
discussion + vote about a very specific proposal which should contain
all the technical information (including committer list)
I support the the same approach what we followed with Submarine:
ALL the existing (Hadoop) committers should have a free / opt-in
opportunity to be a committer in Ozone.
(After proposal is created on the wiki, you can add your name, or
request to be added. But as the initial list can be created based on
statistics from the Jira, your name can be already there ;-) )
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Weiwei Yang <ww...@apache.org>.
+1
Thanks, Marton for starting the discussion.
One question, for the committers who contributed to Ozone before and got
the committer-role in the past (like me), will they carry the
committer-role to the new repo?
On Wed, May 13, 2020 at 9:07 AM Dinesh Chitlangia <di...@apache.org>
wrote:
> +1
> Thank you Marton for writing up the history and supporting comments.
>
> -Dinesh
>
> On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Weiwei Yang <ww...@apache.org>.
+1
Thanks, Marton for starting the discussion.
One question, for the committers who contributed to Ozone before and got
the committer-role in the past (like me), will they carry the
committer-role to the new repo?
On Wed, May 13, 2020 at 9:07 AM Dinesh Chitlangia <di...@apache.org>
wrote:
> +1
> Thank you Marton for writing up the history and supporting comments.
>
> -Dinesh
>
> On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Weiwei Yang <ww...@apache.org>.
+1
Thanks, Marton for starting the discussion.
One question, for the committers who contributed to Ozone before and got
the committer-role in the past (like me), will they carry the
committer-role to the new repo?
On Wed, May 13, 2020 at 9:07 AM Dinesh Chitlangia <di...@apache.org>
wrote:
> +1
> Thank you Marton for writing up the history and supporting comments.
>
> -Dinesh
>
> On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Weiwei Yang <ww...@apache.org>.
+1
Thanks, Marton for starting the discussion.
One question, for the committers who contributed to Ozone before and got
the committer-role in the past (like me), will they carry the
committer-role to the new repo?
On Wed, May 13, 2020 at 9:07 AM Dinesh Chitlangia <di...@apache.org>
wrote:
> +1
> Thank you Marton for writing up the history and supporting comments.
>
> -Dinesh
>
> On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Weiwei Yang <ww...@apache.org>.
+1
Thanks, Marton for starting the discussion.
One question, for the committers who contributed to Ozone before and got
the committer-role in the past (like me), will they carry the
committer-role to the new repo?
On Wed, May 13, 2020 at 9:07 AM Dinesh Chitlangia <di...@apache.org>
wrote:
> +1
> Thank you Marton for writing up the history and supporting comments.
>
> -Dinesh
>
> On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Dinesh Chitlangia <di...@apache.org>.
+1
Thank you Marton for writing up the history and supporting comments.
-Dinesh
On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
Thank you for all of your responses.
It seems that we have a strong agreement. This thread got ~ 25
+1/positive feedback without any arguments against the move.
The next step is on the Ozone community:
1. A proposal should be created for the new project which covers all
of the technical questions (HOW to do it...). This should be created and
agreed by the Ozone community
2. A second discussion thread will be started here (all Hadoop dev
lists) to discuss about the proposal itself.
3. When everybody is happy with the proposed way of the move we can
start the VOTE thread (based on the proposal) here
4. Voted proposal will be sent to the ASF board to be
discussed/decided/approved.
Thanks, again, all your feedback,
Marton
On 5/13/20 9:52 AM, Elek, Marton wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
>
> [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
Thank you for all of your responses.
It seems that we have a strong agreement. This thread got ~ 25
+1/positive feedback without any arguments against the move.
The next step is on the Ozone community:
1. A proposal should be created for the new project which covers all
of the technical questions (HOW to do it...). This should be created and
agreed by the Ozone community
2. A second discussion thread will be started here (all Hadoop dev
lists) to discuss about the proposal itself.
3. When everybody is happy with the proposed way of the move we can
start the VOTE thread (based on the proposal) here
4. Voted proposal will be sent to the ASF board to be
discussed/decided/approved.
Thanks, again, all your feedback,
Marton
On 5/13/20 9:52 AM, Elek, Marton wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
>
> [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wei-Chiu Chuang <we...@apache.org>.
+1
On Wed, May 13, 2020 at 8:32 AM anu engineer <an...@gmail.com> wrote:
> +1
> —Anu
>
> > On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
> >
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of Hadoop
> repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
> >
> > * During the discussion of the merge, it was suggested multiple times to
> create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a good
> time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at the
> community and code side. The separation has been suggested again and again
> (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated project.
> >
> > * A new, younger project might have different practices (communication,
> commiter criteria, development style) compared to old, mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on Maven
> level. Originally it was compiled together with the in-tree latest Hadoop
> snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wei-Chiu Chuang <we...@apache.org>.
+1
On Wed, May 13, 2020 at 8:32 AM anu engineer <an...@gmail.com> wrote:
> +1
> —Anu
>
> > On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
> >
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of Hadoop
> repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
> >
> > * During the discussion of the merge, it was suggested multiple times to
> create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a good
> time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at the
> community and code side. The separation has been suggested again and again
> (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated project.
> >
> > * A new, younger project might have different practices (communication,
> commiter criteria, development style) compared to old, mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on Maven
> level. Originally it was compiled together with the in-tree latest Hadoop
> snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wei-Chiu Chuang <we...@apache.org>.
+1
On Wed, May 13, 2020 at 8:32 AM anu engineer <an...@gmail.com> wrote:
> +1
> —Anu
>
> > On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
> >
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of Hadoop
> repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
> >
> > * During the discussion of the merge, it was suggested multiple times to
> create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a good
> time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at the
> community and code side. The separation has been suggested again and again
> (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated project.
> >
> > * A new, younger project might have different practices (communication,
> commiter criteria, development style) compared to old, mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on Maven
> level. Originally it was compiled together with the in-tree latest Hadoop
> snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wei-Chiu Chuang <we...@apache.org>.
+1
On Wed, May 13, 2020 at 8:32 AM anu engineer <an...@gmail.com> wrote:
> +1
> —Anu
>
> > On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
> >
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of Hadoop
> repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
> >
> > * During the discussion of the merge, it was suggested multiple times to
> create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a good
> time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at the
> community and code side. The separation has been suggested again and again
> (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated project.
> >
> > * A new, younger project might have different practices (communication,
> commiter criteria, development style) compared to old, mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on Maven
> level. Originally it was compiled together with the in-tree latest Hadoop
> snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wei-Chiu Chuang <we...@apache.org>.
+1
On Wed, May 13, 2020 at 8:32 AM anu engineer <an...@gmail.com> wrote:
> +1
> —Anu
>
> > On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
> >
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of Hadoop
> repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
> >
> > * During the discussion of the merge, it was suggested multiple times to
> create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a good
> time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at the
> community and code side. The separation has been suggested again and again
> (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated project.
> >
> > * A new, younger project might have different practices (communication,
> commiter criteria, development style) compared to old, mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on Maven
> level. Originally it was compiled together with the in-tree latest Hadoop
> snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by anu engineer <an...@gmail.com>.
+1
—Anu
> On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
>
>
>
> I would like to start a discussion to make a separate Apache project for Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of 2018
>
> * During the discussion of the merge, it was suggested multiple times to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at the community and code side. The separation has been suggested again and again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone. Originally the Ozone community was a subset of HDFS project. But now a bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices (communication, commiter criteria, development style) compared to old, mature project
>
> * It's easier to communicate (and improve) these standards in a separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and attract more individual contributor (AFAIK it has been seen in Submarine after a similar move)
>
> * Contribution process can be communicated more easily, we can make first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on Maven level. Originally it was compiled together with the in-tree latest Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC, Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time to discuss the long-term future of Ozone. Managing it as a separated TLP project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see: https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]: https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]: https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Ayush Saxena <ay...@gmail.com>.
+1
-Ayush
> On 13-May-2020, at 11:26 PM, Aravindan Vijayan <av...@cloudera.com.invalid> wrote:
>
> +1.
>
> Thank you for taking this up Marton.
>
>
>> On Wed, May 13, 2020 at 10:48 AM Uma Maheswara Rao G <ha...@gmail.com>
>> wrote:
>>
>> +1
>>
>> Regards,
>> Uma
>>
>>> On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>>>
>>>
>>>
>>> I would like to start a discussion to make a separate Apache project for
>>> Ozone
>>>
>>>
>>>
>>> ### HISTORY [1]
>>>
>>> * Apache Hadoop Ozone development started on a feature branch of
>>> Hadoop repository (HDFS-7240)
>>>
>>> * In the October of 2017 a discussion has been started to merge it to
>>> the Hadoop main branch
>>>
>>> * After a long discussion it's merged to Hadoop trunk at the March of
>>> 2018
>>>
>>> * During the discussion of the merge, it was suggested multiple times
>>> to create a separated project for the Ozone. But at that time:
>>> 1). Ozone was tightly integrated with Hadoop/HDFS
>>> 2). There was an active plan to use Block layer of Ozone (HDDS or
>>> HDSL at that time) as the block level of HDFS
>>> 3). The community of Ozone was a subset of the HDFS community
>>>
>>> * The first beta release of Ozone was just released. Seems to be a
>>> good time before the first GA to make a decision about the future.
>>>
>>>
>>>
>>> ### WHAT HAS BEEN CHANGED
>>>
>>> During the last years Ozone became more and more independent both at
>>> the community and code side. The separation has been suggested again and
>>> again (for example by Owen [2] and Vinod [3])
>>>
>>>
>>>
>>> From COMMUNITY point of view:
>>>
>>>
>>> * Fortunately more and more new contributors are helping Ozone.
>>> Originally the Ozone community was a subset of HDFS project. But now a
>>> bigger and bigger part of the community is related to Ozone only.
>>>
>>> * It seems to be easier to _build_ the community as a separated
>> project.
>>>
>>> * A new, younger project might have different practices
>>> (communication, commiter criteria, development style) compared to old,
>>> mature project
>>>
>>> * It's easier to communicate (and improve) these standards in a
>>> separated projects with clean boundaries
>>>
>>> * Separated project/brand can help to increase the adoption rate and
>>> attract more individual contributor (AFAIK it has been seen in Submarine
>>> after a similar move)
>>>
>>> * Contribution process can be communicated more easily, we can make
>>> first time contribution more easy
>>>
>>>
>>>
>>> From CODE point of view Ozone became more and more independent:
>>>
>>>
>>> * Ozone has different release cycle
>>>
>>> * Code is already separated from Hadoop code base
>>> (apache/hadoop-ozone.git)
>>>
>>> * It has separated CI (github actions)
>>>
>>> * Ozone uses different (more strict) coding style (zero toleration of
>>> unit test / checkstyle errors)
>>>
>>> * The code itself became more and more independent from Hadoop on
>>> Maven level. Originally it was compiled together with the in-tree latest
>>> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
>>> Configuration...)
>>>
>>> * It starts to use multiple version of Hadoop (on client side)
>>>
>>> * Volume of resolved issues are already very high on Ozone side (Ozone
>>> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
>>> together in the last 2-3 months)
>>>
>>>
>>> Summary: Before the first Ozone GA release, It seems to be a good time
>>> to discuss the long-term future of Ozone. Managing it as a separated TLP
>>> project seems to have more benefits.
>>>
>>>
>>> Please let me know what your opinion is...
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>>
>>>
>>>
>>>
>>> [1]: For more details, see:
>>> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>>>
>>> [2]:
>>>
>>>
>> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>>>
>>> [3]:
>>>
>>>
>> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Ayush Saxena <ay...@gmail.com>.
+1
-Ayush
> On 13-May-2020, at 11:26 PM, Aravindan Vijayan <av...@cloudera.com.invalid> wrote:
>
> +1.
>
> Thank you for taking this up Marton.
>
>
>> On Wed, May 13, 2020 at 10:48 AM Uma Maheswara Rao G <ha...@gmail.com>
>> wrote:
>>
>> +1
>>
>> Regards,
>> Uma
>>
>>> On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>>>
>>>
>>>
>>> I would like to start a discussion to make a separate Apache project for
>>> Ozone
>>>
>>>
>>>
>>> ### HISTORY [1]
>>>
>>> * Apache Hadoop Ozone development started on a feature branch of
>>> Hadoop repository (HDFS-7240)
>>>
>>> * In the October of 2017 a discussion has been started to merge it to
>>> the Hadoop main branch
>>>
>>> * After a long discussion it's merged to Hadoop trunk at the March of
>>> 2018
>>>
>>> * During the discussion of the merge, it was suggested multiple times
>>> to create a separated project for the Ozone. But at that time:
>>> 1). Ozone was tightly integrated with Hadoop/HDFS
>>> 2). There was an active plan to use Block layer of Ozone (HDDS or
>>> HDSL at that time) as the block level of HDFS
>>> 3). The community of Ozone was a subset of the HDFS community
>>>
>>> * The first beta release of Ozone was just released. Seems to be a
>>> good time before the first GA to make a decision about the future.
>>>
>>>
>>>
>>> ### WHAT HAS BEEN CHANGED
>>>
>>> During the last years Ozone became more and more independent both at
>>> the community and code side. The separation has been suggested again and
>>> again (for example by Owen [2] and Vinod [3])
>>>
>>>
>>>
>>> From COMMUNITY point of view:
>>>
>>>
>>> * Fortunately more and more new contributors are helping Ozone.
>>> Originally the Ozone community was a subset of HDFS project. But now a
>>> bigger and bigger part of the community is related to Ozone only.
>>>
>>> * It seems to be easier to _build_ the community as a separated
>> project.
>>>
>>> * A new, younger project might have different practices
>>> (communication, commiter criteria, development style) compared to old,
>>> mature project
>>>
>>> * It's easier to communicate (and improve) these standards in a
>>> separated projects with clean boundaries
>>>
>>> * Separated project/brand can help to increase the adoption rate and
>>> attract more individual contributor (AFAIK it has been seen in Submarine
>>> after a similar move)
>>>
>>> * Contribution process can be communicated more easily, we can make
>>> first time contribution more easy
>>>
>>>
>>>
>>> From CODE point of view Ozone became more and more independent:
>>>
>>>
>>> * Ozone has different release cycle
>>>
>>> * Code is already separated from Hadoop code base
>>> (apache/hadoop-ozone.git)
>>>
>>> * It has separated CI (github actions)
>>>
>>> * Ozone uses different (more strict) coding style (zero toleration of
>>> unit test / checkstyle errors)
>>>
>>> * The code itself became more and more independent from Hadoop on
>>> Maven level. Originally it was compiled together with the in-tree latest
>>> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
>>> Configuration...)
>>>
>>> * It starts to use multiple version of Hadoop (on client side)
>>>
>>> * Volume of resolved issues are already very high on Ozone side (Ozone
>>> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
>>> together in the last 2-3 months)
>>>
>>>
>>> Summary: Before the first Ozone GA release, It seems to be a good time
>>> to discuss the long-term future of Ozone. Managing it as a separated TLP
>>> project seems to have more benefits.
>>>
>>>
>>> Please let me know what your opinion is...
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>>
>>>
>>>
>>>
>>> [1]: For more details, see:
>>> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>>>
>>> [2]:
>>>
>>>
>> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>>>
>>> [3]:
>>>
>>>
>> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Ayush Saxena <ay...@gmail.com>.
+1
-Ayush
> On 13-May-2020, at 11:26 PM, Aravindan Vijayan <av...@cloudera.com.invalid> wrote:
>
> +1.
>
> Thank you for taking this up Marton.
>
>
>> On Wed, May 13, 2020 at 10:48 AM Uma Maheswara Rao G <ha...@gmail.com>
>> wrote:
>>
>> +1
>>
>> Regards,
>> Uma
>>
>>> On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>>>
>>>
>>>
>>> I would like to start a discussion to make a separate Apache project for
>>> Ozone
>>>
>>>
>>>
>>> ### HISTORY [1]
>>>
>>> * Apache Hadoop Ozone development started on a feature branch of
>>> Hadoop repository (HDFS-7240)
>>>
>>> * In the October of 2017 a discussion has been started to merge it to
>>> the Hadoop main branch
>>>
>>> * After a long discussion it's merged to Hadoop trunk at the March of
>>> 2018
>>>
>>> * During the discussion of the merge, it was suggested multiple times
>>> to create a separated project for the Ozone. But at that time:
>>> 1). Ozone was tightly integrated with Hadoop/HDFS
>>> 2). There was an active plan to use Block layer of Ozone (HDDS or
>>> HDSL at that time) as the block level of HDFS
>>> 3). The community of Ozone was a subset of the HDFS community
>>>
>>> * The first beta release of Ozone was just released. Seems to be a
>>> good time before the first GA to make a decision about the future.
>>>
>>>
>>>
>>> ### WHAT HAS BEEN CHANGED
>>>
>>> During the last years Ozone became more and more independent both at
>>> the community and code side. The separation has been suggested again and
>>> again (for example by Owen [2] and Vinod [3])
>>>
>>>
>>>
>>> From COMMUNITY point of view:
>>>
>>>
>>> * Fortunately more and more new contributors are helping Ozone.
>>> Originally the Ozone community was a subset of HDFS project. But now a
>>> bigger and bigger part of the community is related to Ozone only.
>>>
>>> * It seems to be easier to _build_ the community as a separated
>> project.
>>>
>>> * A new, younger project might have different practices
>>> (communication, commiter criteria, development style) compared to old,
>>> mature project
>>>
>>> * It's easier to communicate (and improve) these standards in a
>>> separated projects with clean boundaries
>>>
>>> * Separated project/brand can help to increase the adoption rate and
>>> attract more individual contributor (AFAIK it has been seen in Submarine
>>> after a similar move)
>>>
>>> * Contribution process can be communicated more easily, we can make
>>> first time contribution more easy
>>>
>>>
>>>
>>> From CODE point of view Ozone became more and more independent:
>>>
>>>
>>> * Ozone has different release cycle
>>>
>>> * Code is already separated from Hadoop code base
>>> (apache/hadoop-ozone.git)
>>>
>>> * It has separated CI (github actions)
>>>
>>> * Ozone uses different (more strict) coding style (zero toleration of
>>> unit test / checkstyle errors)
>>>
>>> * The code itself became more and more independent from Hadoop on
>>> Maven level. Originally it was compiled together with the in-tree latest
>>> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
>>> Configuration...)
>>>
>>> * It starts to use multiple version of Hadoop (on client side)
>>>
>>> * Volume of resolved issues are already very high on Ozone side (Ozone
>>> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
>>> together in the last 2-3 months)
>>>
>>>
>>> Summary: Before the first Ozone GA release, It seems to be a good time
>>> to discuss the long-term future of Ozone. Managing it as a separated TLP
>>> project seems to have more benefits.
>>>
>>>
>>> Please let me know what your opinion is...
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>>
>>>
>>>
>>>
>>> [1]: For more details, see:
>>> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>>>
>>> [2]:
>>>
>>>
>> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>>>
>>> [3]:
>>>
>>>
>> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Ayush Saxena <ay...@gmail.com>.
+1
-Ayush
> On 13-May-2020, at 11:26 PM, Aravindan Vijayan <av...@cloudera.com.invalid> wrote:
>
> +1.
>
> Thank you for taking this up Marton.
>
>
>> On Wed, May 13, 2020 at 10:48 AM Uma Maheswara Rao G <ha...@gmail.com>
>> wrote:
>>
>> +1
>>
>> Regards,
>> Uma
>>
>>> On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>>>
>>>
>>>
>>> I would like to start a discussion to make a separate Apache project for
>>> Ozone
>>>
>>>
>>>
>>> ### HISTORY [1]
>>>
>>> * Apache Hadoop Ozone development started on a feature branch of
>>> Hadoop repository (HDFS-7240)
>>>
>>> * In the October of 2017 a discussion has been started to merge it to
>>> the Hadoop main branch
>>>
>>> * After a long discussion it's merged to Hadoop trunk at the March of
>>> 2018
>>>
>>> * During the discussion of the merge, it was suggested multiple times
>>> to create a separated project for the Ozone. But at that time:
>>> 1). Ozone was tightly integrated with Hadoop/HDFS
>>> 2). There was an active plan to use Block layer of Ozone (HDDS or
>>> HDSL at that time) as the block level of HDFS
>>> 3). The community of Ozone was a subset of the HDFS community
>>>
>>> * The first beta release of Ozone was just released. Seems to be a
>>> good time before the first GA to make a decision about the future.
>>>
>>>
>>>
>>> ### WHAT HAS BEEN CHANGED
>>>
>>> During the last years Ozone became more and more independent both at
>>> the community and code side. The separation has been suggested again and
>>> again (for example by Owen [2] and Vinod [3])
>>>
>>>
>>>
>>> From COMMUNITY point of view:
>>>
>>>
>>> * Fortunately more and more new contributors are helping Ozone.
>>> Originally the Ozone community was a subset of HDFS project. But now a
>>> bigger and bigger part of the community is related to Ozone only.
>>>
>>> * It seems to be easier to _build_ the community as a separated
>> project.
>>>
>>> * A new, younger project might have different practices
>>> (communication, commiter criteria, development style) compared to old,
>>> mature project
>>>
>>> * It's easier to communicate (and improve) these standards in a
>>> separated projects with clean boundaries
>>>
>>> * Separated project/brand can help to increase the adoption rate and
>>> attract more individual contributor (AFAIK it has been seen in Submarine
>>> after a similar move)
>>>
>>> * Contribution process can be communicated more easily, we can make
>>> first time contribution more easy
>>>
>>>
>>>
>>> From CODE point of view Ozone became more and more independent:
>>>
>>>
>>> * Ozone has different release cycle
>>>
>>> * Code is already separated from Hadoop code base
>>> (apache/hadoop-ozone.git)
>>>
>>> * It has separated CI (github actions)
>>>
>>> * Ozone uses different (more strict) coding style (zero toleration of
>>> unit test / checkstyle errors)
>>>
>>> * The code itself became more and more independent from Hadoop on
>>> Maven level. Originally it was compiled together with the in-tree latest
>>> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
>>> Configuration...)
>>>
>>> * It starts to use multiple version of Hadoop (on client side)
>>>
>>> * Volume of resolved issues are already very high on Ozone side (Ozone
>>> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
>>> together in the last 2-3 months)
>>>
>>>
>>> Summary: Before the first Ozone GA release, It seems to be a good time
>>> to discuss the long-term future of Ozone. Managing it as a separated TLP
>>> project seems to have more benefits.
>>>
>>>
>>> Please let me know what your opinion is...
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>>
>>>
>>>
>>>
>>> [1]: For more details, see:
>>> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>>>
>>> [2]:
>>>
>>>
>> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>>>
>>> [3]:
>>>
>>>
>> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Ayush Saxena <ay...@gmail.com>.
+1
-Ayush
> On 13-May-2020, at 11:26 PM, Aravindan Vijayan <av...@cloudera.com.invalid> wrote:
>
> +1.
>
> Thank you for taking this up Marton.
>
>
>> On Wed, May 13, 2020 at 10:48 AM Uma Maheswara Rao G <ha...@gmail.com>
>> wrote:
>>
>> +1
>>
>> Regards,
>> Uma
>>
>>> On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>>>
>>>
>>>
>>> I would like to start a discussion to make a separate Apache project for
>>> Ozone
>>>
>>>
>>>
>>> ### HISTORY [1]
>>>
>>> * Apache Hadoop Ozone development started on a feature branch of
>>> Hadoop repository (HDFS-7240)
>>>
>>> * In the October of 2017 a discussion has been started to merge it to
>>> the Hadoop main branch
>>>
>>> * After a long discussion it's merged to Hadoop trunk at the March of
>>> 2018
>>>
>>> * During the discussion of the merge, it was suggested multiple times
>>> to create a separated project for the Ozone. But at that time:
>>> 1). Ozone was tightly integrated with Hadoop/HDFS
>>> 2). There was an active plan to use Block layer of Ozone (HDDS or
>>> HDSL at that time) as the block level of HDFS
>>> 3). The community of Ozone was a subset of the HDFS community
>>>
>>> * The first beta release of Ozone was just released. Seems to be a
>>> good time before the first GA to make a decision about the future.
>>>
>>>
>>>
>>> ### WHAT HAS BEEN CHANGED
>>>
>>> During the last years Ozone became more and more independent both at
>>> the community and code side. The separation has been suggested again and
>>> again (for example by Owen [2] and Vinod [3])
>>>
>>>
>>>
>>> From COMMUNITY point of view:
>>>
>>>
>>> * Fortunately more and more new contributors are helping Ozone.
>>> Originally the Ozone community was a subset of HDFS project. But now a
>>> bigger and bigger part of the community is related to Ozone only.
>>>
>>> * It seems to be easier to _build_ the community as a separated
>> project.
>>>
>>> * A new, younger project might have different practices
>>> (communication, commiter criteria, development style) compared to old,
>>> mature project
>>>
>>> * It's easier to communicate (and improve) these standards in a
>>> separated projects with clean boundaries
>>>
>>> * Separated project/brand can help to increase the adoption rate and
>>> attract more individual contributor (AFAIK it has been seen in Submarine
>>> after a similar move)
>>>
>>> * Contribution process can be communicated more easily, we can make
>>> first time contribution more easy
>>>
>>>
>>>
>>> From CODE point of view Ozone became more and more independent:
>>>
>>>
>>> * Ozone has different release cycle
>>>
>>> * Code is already separated from Hadoop code base
>>> (apache/hadoop-ozone.git)
>>>
>>> * It has separated CI (github actions)
>>>
>>> * Ozone uses different (more strict) coding style (zero toleration of
>>> unit test / checkstyle errors)
>>>
>>> * The code itself became more and more independent from Hadoop on
>>> Maven level. Originally it was compiled together with the in-tree latest
>>> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
>>> Configuration...)
>>>
>>> * It starts to use multiple version of Hadoop (on client side)
>>>
>>> * Volume of resolved issues are already very high on Ozone side (Ozone
>>> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
>>> together in the last 2-3 months)
>>>
>>>
>>> Summary: Before the first Ozone GA release, It seems to be a good time
>>> to discuss the long-term future of Ozone. Managing it as a separated TLP
>>> project seems to have more benefits.
>>>
>>>
>>> Please let me know what your opinion is...
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>>
>>>
>>>
>>>
>>> [1]: For more details, see:
>>> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>>>
>>> [2]:
>>>
>>>
>> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>>>
>>> [3]:
>>>
>>>
>> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Aravindan Vijayan <av...@cloudera.com.INVALID>.
+1.
Thank you for taking this up Marton.
On Wed, May 13, 2020 at 10:48 AM Uma Maheswara Rao G <ha...@gmail.com>
wrote:
> +1
>
> Regards,
> Uma
>
> On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Aravindan Vijayan <av...@cloudera.com.INVALID>.
+1.
Thank you for taking this up Marton.
On Wed, May 13, 2020 at 10:48 AM Uma Maheswara Rao G <ha...@gmail.com>
wrote:
> +1
>
> Regards,
> Uma
>
> On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Uma Maheswara Rao G <ha...@gmail.com>.
+1
Regards,
Uma
On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by anu engineer <an...@gmail.com>.
+1
—Anu
> On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
>
>
>
> I would like to start a discussion to make a separate Apache project for Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of 2018
>
> * During the discussion of the merge, it was suggested multiple times to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at the community and code side. The separation has been suggested again and again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone. Originally the Ozone community was a subset of HDFS project. But now a bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices (communication, commiter criteria, development style) compared to old, mature project
>
> * It's easier to communicate (and improve) these standards in a separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and attract more individual contributor (AFAIK it has been seen in Submarine after a similar move)
>
> * Contribution process can be communicated more easily, we can make first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on Maven level. Originally it was compiled together with the in-tree latest Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC, Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time to discuss the long-term future of Ozone. Managing it as a separated TLP project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see: https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]: https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]: https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Sunil Govindan <su...@apache.org>.
+1
Thanks
Sunil
On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Vinayakumar B <vi...@apache.org>.
+1
-Vinay
On Thu, 14 May 2020, 12:20 pm Surendra Singh Lilhore, <
surendralilhore@gmail.com> wrote:
> +1
>
> -Surendra
>
>
> On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
>
> > +1
> >
> > Thank you Marton for the detailed description.
> >
> >
> > Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> >
> > > +1
> > >
> > > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> > >
> > > >
> > > >
> > > > I would like to start a discussion to make a separate Apache project
> > for
> > > > Ozone
> > > >
> > > >
> > > >
> > > > ### HISTORY [1]
> > > >
> > > > * Apache Hadoop Ozone development started on a feature branch of
> > > > Hadoop repository (HDFS-7240)
> > > >
> > > > * In the October of 2017 a discussion has been started to merge it
> to
> > > > the Hadoop main branch
> > > >
> > > > * After a long discussion it's merged to Hadoop trunk at the March
> of
> > > > 2018
> > > >
> > > > * During the discussion of the merge, it was suggested multiple
> times
> > > > to create a separated project for the Ozone. But at that time:
> > > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > > 2). There was an active plan to use Block layer of Ozone (HDDS
> or
> > > > HDSL at that time) as the block level of HDFS
> > > > 3). The community of Ozone was a subset of the HDFS community
> > > >
> > > > * The first beta release of Ozone was just released. Seems to be a
> > > > good time before the first GA to make a decision about the future.
> > > >
> > > >
> > > >
> > > > ### WHAT HAS BEEN CHANGED
> > > >
> > > > During the last years Ozone became more and more independent both
> at
> > > > the community and code side. The separation has been suggested again
> > and
> > > > again (for example by Owen [2] and Vinod [3])
> > > >
> > > >
> > > >
> > > > From COMMUNITY point of view:
> > > >
> > > >
> > > > * Fortunately more and more new contributors are helping Ozone.
> > > > Originally the Ozone community was a subset of HDFS project. But now
> a
> > > > bigger and bigger part of the community is related to Ozone only.
> > > >
> > > > * It seems to be easier to _build_ the community as a separated
> > > project.
> > > >
> > > > * A new, younger project might have different practices
> > > > (communication, commiter criteria, development style) compared to
> old,
> > > > mature project
> > > >
> > > > * It's easier to communicate (and improve) these standards in a
> > > > separated projects with clean boundaries
> > > >
> > > > * Separated project/brand can help to increase the adoption rate
> and
> > > > attract more individual contributor (AFAIK it has been seen in
> > Submarine
> > > > after a similar move)
> > > >
> > > > * Contribution process can be communicated more easily, we can make
> > > > first time contribution more easy
> > > >
> > > >
> > > >
> > > > From CODE point of view Ozone became more and more independent:
> > > >
> > > >
> > > > * Ozone has different release cycle
> > > >
> > > > * Code is already separated from Hadoop code base
> > > > (apache/hadoop-ozone.git)
> > > >
> > > > * It has separated CI (github actions)
> > > >
> > > > * Ozone uses different (more strict) coding style (zero toleration
> of
> > > > unit test / checkstyle errors)
> > > >
> > > > * The code itself became more and more independent from Hadoop on
> > > > Maven level. Originally it was compiled together with the in-tree
> > latest
> > > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > > Configuration...)
> > > >
> > > > * It starts to use multiple version of Hadoop (on client side)
> > > >
> > > > * Volume of resolved issues are already very high on Ozone side
> > (Ozone
> > > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > > together in the last 2-3 months)
> > > >
> > > >
> > > > Summary: Before the first Ozone GA release, It seems to be a good
> time
> > > > to discuss the long-term future of Ozone. Managing it as a separated
> > TLP
> > > > project seems to have more benefits.
> > > >
> > > >
> > > > Please let me know what your opinion is...
> > > >
> > > > Thanks a lot,
> > > > Marton
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [1]: For more details, see:
> > > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > > >
> > > > [2]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > > >
> > > > [3]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Vinayakumar B <vi...@apache.org>.
+1
-Vinay
On Thu, 14 May 2020, 12:20 pm Surendra Singh Lilhore, <
surendralilhore@gmail.com> wrote:
> +1
>
> -Surendra
>
>
> On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
>
> > +1
> >
> > Thank you Marton for the detailed description.
> >
> >
> > Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> >
> > > +1
> > >
> > > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> > >
> > > >
> > > >
> > > > I would like to start a discussion to make a separate Apache project
> > for
> > > > Ozone
> > > >
> > > >
> > > >
> > > > ### HISTORY [1]
> > > >
> > > > * Apache Hadoop Ozone development started on a feature branch of
> > > > Hadoop repository (HDFS-7240)
> > > >
> > > > * In the October of 2017 a discussion has been started to merge it
> to
> > > > the Hadoop main branch
> > > >
> > > > * After a long discussion it's merged to Hadoop trunk at the March
> of
> > > > 2018
> > > >
> > > > * During the discussion of the merge, it was suggested multiple
> times
> > > > to create a separated project for the Ozone. But at that time:
> > > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > > 2). There was an active plan to use Block layer of Ozone (HDDS
> or
> > > > HDSL at that time) as the block level of HDFS
> > > > 3). The community of Ozone was a subset of the HDFS community
> > > >
> > > > * The first beta release of Ozone was just released. Seems to be a
> > > > good time before the first GA to make a decision about the future.
> > > >
> > > >
> > > >
> > > > ### WHAT HAS BEEN CHANGED
> > > >
> > > > During the last years Ozone became more and more independent both
> at
> > > > the community and code side. The separation has been suggested again
> > and
> > > > again (for example by Owen [2] and Vinod [3])
> > > >
> > > >
> > > >
> > > > From COMMUNITY point of view:
> > > >
> > > >
> > > > * Fortunately more and more new contributors are helping Ozone.
> > > > Originally the Ozone community was a subset of HDFS project. But now
> a
> > > > bigger and bigger part of the community is related to Ozone only.
> > > >
> > > > * It seems to be easier to _build_ the community as a separated
> > > project.
> > > >
> > > > * A new, younger project might have different practices
> > > > (communication, commiter criteria, development style) compared to
> old,
> > > > mature project
> > > >
> > > > * It's easier to communicate (and improve) these standards in a
> > > > separated projects with clean boundaries
> > > >
> > > > * Separated project/brand can help to increase the adoption rate
> and
> > > > attract more individual contributor (AFAIK it has been seen in
> > Submarine
> > > > after a similar move)
> > > >
> > > > * Contribution process can be communicated more easily, we can make
> > > > first time contribution more easy
> > > >
> > > >
> > > >
> > > > From CODE point of view Ozone became more and more independent:
> > > >
> > > >
> > > > * Ozone has different release cycle
> > > >
> > > > * Code is already separated from Hadoop code base
> > > > (apache/hadoop-ozone.git)
> > > >
> > > > * It has separated CI (github actions)
> > > >
> > > > * Ozone uses different (more strict) coding style (zero toleration
> of
> > > > unit test / checkstyle errors)
> > > >
> > > > * The code itself became more and more independent from Hadoop on
> > > > Maven level. Originally it was compiled together with the in-tree
> > latest
> > > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > > Configuration...)
> > > >
> > > > * It starts to use multiple version of Hadoop (on client side)
> > > >
> > > > * Volume of resolved issues are already very high on Ozone side
> > (Ozone
> > > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > > together in the last 2-3 months)
> > > >
> > > >
> > > > Summary: Before the first Ozone GA release, It seems to be a good
> time
> > > > to discuss the long-term future of Ozone. Managing it as a separated
> > TLP
> > > > project seems to have more benefits.
> > > >
> > > >
> > > > Please let me know what your opinion is...
> > > >
> > > > Thanks a lot,
> > > > Marton
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [1]: For more details, see:
> > > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > > >
> > > > [2]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > > >
> > > > [3]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Vinayakumar B <vi...@apache.org>.
+1
-Vinay
On Thu, 14 May 2020, 12:20 pm Surendra Singh Lilhore, <
surendralilhore@gmail.com> wrote:
> +1
>
> -Surendra
>
>
> On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
>
> > +1
> >
> > Thank you Marton for the detailed description.
> >
> >
> > Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> >
> > > +1
> > >
> > > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> > >
> > > >
> > > >
> > > > I would like to start a discussion to make a separate Apache project
> > for
> > > > Ozone
> > > >
> > > >
> > > >
> > > > ### HISTORY [1]
> > > >
> > > > * Apache Hadoop Ozone development started on a feature branch of
> > > > Hadoop repository (HDFS-7240)
> > > >
> > > > * In the October of 2017 a discussion has been started to merge it
> to
> > > > the Hadoop main branch
> > > >
> > > > * After a long discussion it's merged to Hadoop trunk at the March
> of
> > > > 2018
> > > >
> > > > * During the discussion of the merge, it was suggested multiple
> times
> > > > to create a separated project for the Ozone. But at that time:
> > > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > > 2). There was an active plan to use Block layer of Ozone (HDDS
> or
> > > > HDSL at that time) as the block level of HDFS
> > > > 3). The community of Ozone was a subset of the HDFS community
> > > >
> > > > * The first beta release of Ozone was just released. Seems to be a
> > > > good time before the first GA to make a decision about the future.
> > > >
> > > >
> > > >
> > > > ### WHAT HAS BEEN CHANGED
> > > >
> > > > During the last years Ozone became more and more independent both
> at
> > > > the community and code side. The separation has been suggested again
> > and
> > > > again (for example by Owen [2] and Vinod [3])
> > > >
> > > >
> > > >
> > > > From COMMUNITY point of view:
> > > >
> > > >
> > > > * Fortunately more and more new contributors are helping Ozone.
> > > > Originally the Ozone community was a subset of HDFS project. But now
> a
> > > > bigger and bigger part of the community is related to Ozone only.
> > > >
> > > > * It seems to be easier to _build_ the community as a separated
> > > project.
> > > >
> > > > * A new, younger project might have different practices
> > > > (communication, commiter criteria, development style) compared to
> old,
> > > > mature project
> > > >
> > > > * It's easier to communicate (and improve) these standards in a
> > > > separated projects with clean boundaries
> > > >
> > > > * Separated project/brand can help to increase the adoption rate
> and
> > > > attract more individual contributor (AFAIK it has been seen in
> > Submarine
> > > > after a similar move)
> > > >
> > > > * Contribution process can be communicated more easily, we can make
> > > > first time contribution more easy
> > > >
> > > >
> > > >
> > > > From CODE point of view Ozone became more and more independent:
> > > >
> > > >
> > > > * Ozone has different release cycle
> > > >
> > > > * Code is already separated from Hadoop code base
> > > > (apache/hadoop-ozone.git)
> > > >
> > > > * It has separated CI (github actions)
> > > >
> > > > * Ozone uses different (more strict) coding style (zero toleration
> of
> > > > unit test / checkstyle errors)
> > > >
> > > > * The code itself became more and more independent from Hadoop on
> > > > Maven level. Originally it was compiled together with the in-tree
> > latest
> > > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > > Configuration...)
> > > >
> > > > * It starts to use multiple version of Hadoop (on client side)
> > > >
> > > > * Volume of resolved issues are already very high on Ozone side
> > (Ozone
> > > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > > together in the last 2-3 months)
> > > >
> > > >
> > > > Summary: Before the first Ozone GA release, It seems to be a good
> time
> > > > to discuss the long-term future of Ozone. Managing it as a separated
> > TLP
> > > > project seems to have more benefits.
> > > >
> > > >
> > > > Please let me know what your opinion is...
> > > >
> > > > Thanks a lot,
> > > > Marton
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [1]: For more details, see:
> > > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > > >
> > > > [2]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > > >
> > > > [3]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Vinayakumar B <vi...@apache.org>.
+1
-Vinay
On Thu, 14 May 2020, 12:20 pm Surendra Singh Lilhore, <
surendralilhore@gmail.com> wrote:
> +1
>
> -Surendra
>
>
> On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
>
> > +1
> >
> > Thank you Marton for the detailed description.
> >
> >
> > Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> >
> > > +1
> > >
> > > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> > >
> > > >
> > > >
> > > > I would like to start a discussion to make a separate Apache project
> > for
> > > > Ozone
> > > >
> > > >
> > > >
> > > > ### HISTORY [1]
> > > >
> > > > * Apache Hadoop Ozone development started on a feature branch of
> > > > Hadoop repository (HDFS-7240)
> > > >
> > > > * In the October of 2017 a discussion has been started to merge it
> to
> > > > the Hadoop main branch
> > > >
> > > > * After a long discussion it's merged to Hadoop trunk at the March
> of
> > > > 2018
> > > >
> > > > * During the discussion of the merge, it was suggested multiple
> times
> > > > to create a separated project for the Ozone. But at that time:
> > > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > > 2). There was an active plan to use Block layer of Ozone (HDDS
> or
> > > > HDSL at that time) as the block level of HDFS
> > > > 3). The community of Ozone was a subset of the HDFS community
> > > >
> > > > * The first beta release of Ozone was just released. Seems to be a
> > > > good time before the first GA to make a decision about the future.
> > > >
> > > >
> > > >
> > > > ### WHAT HAS BEEN CHANGED
> > > >
> > > > During the last years Ozone became more and more independent both
> at
> > > > the community and code side. The separation has been suggested again
> > and
> > > > again (for example by Owen [2] and Vinod [3])
> > > >
> > > >
> > > >
> > > > From COMMUNITY point of view:
> > > >
> > > >
> > > > * Fortunately more and more new contributors are helping Ozone.
> > > > Originally the Ozone community was a subset of HDFS project. But now
> a
> > > > bigger and bigger part of the community is related to Ozone only.
> > > >
> > > > * It seems to be easier to _build_ the community as a separated
> > > project.
> > > >
> > > > * A new, younger project might have different practices
> > > > (communication, commiter criteria, development style) compared to
> old,
> > > > mature project
> > > >
> > > > * It's easier to communicate (and improve) these standards in a
> > > > separated projects with clean boundaries
> > > >
> > > > * Separated project/brand can help to increase the adoption rate
> and
> > > > attract more individual contributor (AFAIK it has been seen in
> > Submarine
> > > > after a similar move)
> > > >
> > > > * Contribution process can be communicated more easily, we can make
> > > > first time contribution more easy
> > > >
> > > >
> > > >
> > > > From CODE point of view Ozone became more and more independent:
> > > >
> > > >
> > > > * Ozone has different release cycle
> > > >
> > > > * Code is already separated from Hadoop code base
> > > > (apache/hadoop-ozone.git)
> > > >
> > > > * It has separated CI (github actions)
> > > >
> > > > * Ozone uses different (more strict) coding style (zero toleration
> of
> > > > unit test / checkstyle errors)
> > > >
> > > > * The code itself became more and more independent from Hadoop on
> > > > Maven level. Originally it was compiled together with the in-tree
> > latest
> > > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > > Configuration...)
> > > >
> > > > * It starts to use multiple version of Hadoop (on client side)
> > > >
> > > > * Volume of resolved issues are already very high on Ozone side
> > (Ozone
> > > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > > together in the last 2-3 months)
> > > >
> > > >
> > > > Summary: Before the first Ozone GA release, It seems to be a good
> time
> > > > to discuss the long-term future of Ozone. Managing it as a separated
> > TLP
> > > > project seems to have more benefits.
> > > >
> > > >
> > > > Please let me know what your opinion is...
> > > >
> > > > Thanks a lot,
> > > > Marton
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [1]: For more details, see:
> > > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > > >
> > > > [2]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > > >
> > > > [3]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Vinayakumar B <vi...@apache.org>.
+1
-Vinay
On Thu, 14 May 2020, 12:20 pm Surendra Singh Lilhore, <
surendralilhore@gmail.com> wrote:
> +1
>
> -Surendra
>
>
> On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
>
> > +1
> >
> > Thank you Marton for the detailed description.
> >
> >
> > Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> >
> > > +1
> > >
> > > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> > >
> > > >
> > > >
> > > > I would like to start a discussion to make a separate Apache project
> > for
> > > > Ozone
> > > >
> > > >
> > > >
> > > > ### HISTORY [1]
> > > >
> > > > * Apache Hadoop Ozone development started on a feature branch of
> > > > Hadoop repository (HDFS-7240)
> > > >
> > > > * In the October of 2017 a discussion has been started to merge it
> to
> > > > the Hadoop main branch
> > > >
> > > > * After a long discussion it's merged to Hadoop trunk at the March
> of
> > > > 2018
> > > >
> > > > * During the discussion of the merge, it was suggested multiple
> times
> > > > to create a separated project for the Ozone. But at that time:
> > > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > > 2). There was an active plan to use Block layer of Ozone (HDDS
> or
> > > > HDSL at that time) as the block level of HDFS
> > > > 3). The community of Ozone was a subset of the HDFS community
> > > >
> > > > * The first beta release of Ozone was just released. Seems to be a
> > > > good time before the first GA to make a decision about the future.
> > > >
> > > >
> > > >
> > > > ### WHAT HAS BEEN CHANGED
> > > >
> > > > During the last years Ozone became more and more independent both
> at
> > > > the community and code side. The separation has been suggested again
> > and
> > > > again (for example by Owen [2] and Vinod [3])
> > > >
> > > >
> > > >
> > > > From COMMUNITY point of view:
> > > >
> > > >
> > > > * Fortunately more and more new contributors are helping Ozone.
> > > > Originally the Ozone community was a subset of HDFS project. But now
> a
> > > > bigger and bigger part of the community is related to Ozone only.
> > > >
> > > > * It seems to be easier to _build_ the community as a separated
> > > project.
> > > >
> > > > * A new, younger project might have different practices
> > > > (communication, commiter criteria, development style) compared to
> old,
> > > > mature project
> > > >
> > > > * It's easier to communicate (and improve) these standards in a
> > > > separated projects with clean boundaries
> > > >
> > > > * Separated project/brand can help to increase the adoption rate
> and
> > > > attract more individual contributor (AFAIK it has been seen in
> > Submarine
> > > > after a similar move)
> > > >
> > > > * Contribution process can be communicated more easily, we can make
> > > > first time contribution more easy
> > > >
> > > >
> > > >
> > > > From CODE point of view Ozone became more and more independent:
> > > >
> > > >
> > > > * Ozone has different release cycle
> > > >
> > > > * Code is already separated from Hadoop code base
> > > > (apache/hadoop-ozone.git)
> > > >
> > > > * It has separated CI (github actions)
> > > >
> > > > * Ozone uses different (more strict) coding style (zero toleration
> of
> > > > unit test / checkstyle errors)
> > > >
> > > > * The code itself became more and more independent from Hadoop on
> > > > Maven level. Originally it was compiled together with the in-tree
> > latest
> > > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > > Configuration...)
> > > >
> > > > * It starts to use multiple version of Hadoop (on client side)
> > > >
> > > > * Volume of resolved issues are already very high on Ozone side
> > (Ozone
> > > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > > together in the last 2-3 months)
> > > >
> > > >
> > > > Summary: Before the first Ozone GA release, It seems to be a good
> time
> > > > to discuss the long-term future of Ozone. Managing it as a separated
> > TLP
> > > > project seems to have more benefits.
> > > >
> > > >
> > > > Please let me know what your opinion is...
> > > >
> > > > Thanks a lot,
> > > > Marton
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [1]: For more details, see:
> > > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > > >
> > > > [2]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > > >
> > > > [3]:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Surendra Singh Lilhore <su...@gmail.com>.
+1
-Surendra
On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
> +1
>
> Thank you Marton for the detailed description.
>
>
> Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
>
> > +1
> >
> > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Surendra Singh Lilhore <su...@gmail.com>.
+1
-Surendra
On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
> +1
>
> Thank you Marton for the detailed description.
>
>
> Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
>
> > +1
> >
> > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Surendra Singh Lilhore <su...@gmail.com>.
+1
-Surendra
On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
> +1
>
> Thank you Marton for the detailed description.
>
>
> Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
>
> > +1
> >
> > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Surendra Singh Lilhore <su...@gmail.com>.
+1
-Surendra
On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
> +1
>
> Thank you Marton for the detailed description.
>
>
> Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
>
> > +1
> >
> > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Surendra Singh Lilhore <su...@gmail.com>.
+1
-Surendra
On Thu, 14 May, 2020, 9:30 am yisheng lien, <yi...@apache.org> wrote:
> +1
>
> Thank you Marton for the detailed description.
>
>
> Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
>
> > +1
> >
> > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by yisheng lien <yi...@apache.org>.
+1
Thank you Marton for the detailed description.
Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> +1
>
> On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by yisheng lien <yi...@apache.org>.
+1
Thank you Marton for the detailed description.
Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> +1
>
> On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by yisheng lien <yi...@apache.org>.
+1
Thank you Marton for the detailed description.
Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> +1
>
> On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by yisheng lien <yi...@apache.org>.
+1
Thank you Marton for the detailed description.
Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> +1
>
> On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by yisheng lien <yi...@apache.org>.
+1
Thank you Marton for the detailed description.
Wanqiang Ji <ji...@apache.org> 於 2020年5月14日 週四 上午11:27 寫道：
> +1
>
> On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wanqiang Ji <ji...@apache.org>.
+1
On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Dinesh Chitlangia <di...@apache.org>.
+1
Thank you Marton for writing up the history and supporting comments.
-Dinesh
On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Sunil Govindan <su...@apache.org>.
+1
Thanks
Sunil
On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
Thank you for all of your responses.
It seems that we have a strong agreement. This thread got ~ 25
+1/positive feedback without any arguments against the move.
The next step is on the Ozone community:
1. A proposal should be created for the new project which covers all
of the technical questions (HOW to do it...). This should be created and
agreed by the Ozone community
2. A second discussion thread will be started here (all Hadoop dev
lists) to discuss about the proposal itself.
3. When everybody is happy with the proposed way of the move we can
start the VOTE thread (based on the proposal) here
4. Voted proposal will be sent to the ASF board to be
discussed/decided/approved.
Thanks, again, all your feedback,
Marton
On 5/13/20 9:52 AM, Elek, Marton wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
>
> [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Dinesh Chitlangia <di...@apache.org>.
+1
Thank you Marton for writing up the history and supporting comments.
-Dinesh
On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Akira Ajisaka <aa...@apache.org>.
+1
-Akira
On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by anu engineer <an...@gmail.com>.
+1
—Anu
> On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
>
>
>
> I would like to start a discussion to make a separate Apache project for Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of 2018
>
> * During the discussion of the merge, it was suggested multiple times to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at the community and code side. The separation has been suggested again and again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone. Originally the Ozone community was a subset of HDFS project. But now a bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices (communication, commiter criteria, development style) compared to old, mature project
>
> * It's easier to communicate (and improve) these standards in a separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and attract more individual contributor (AFAIK it has been seen in Submarine after a similar move)
>
> * Contribution process can be communicated more easily, we can make first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on Maven level. Originally it was compiled together with the in-tree latest Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC, Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time to discuss the long-term future of Ozone. Managing it as a separated TLP project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see: https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]: https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]: https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wanqiang Ji <ji...@apache.org>.
+1
On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by anu engineer <an...@gmail.com>.
+1
—Anu
> On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
>
>
>
> I would like to start a discussion to make a separate Apache project for Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of 2018
>
> * During the discussion of the merge, it was suggested multiple times to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at the community and code side. The separation has been suggested again and again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone. Originally the Ozone community was a subset of HDFS project. But now a bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices (communication, commiter criteria, development style) compared to old, mature project
>
> * It's easier to communicate (and improve) these standards in a separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and attract more individual contributor (AFAIK it has been seen in Submarine after a similar move)
>
> * Contribution process can be communicated more easily, we can make first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on Maven level. Originally it was compiled together with the in-tree latest Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC, Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time to discuss the long-term future of Ozone. Managing it as a separated TLP project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see: https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]: https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]: https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wanqiang Ji <ji...@apache.org>.
+1
On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
Thank you for all of your responses.
It seems that we have a strong agreement. This thread got ~ 25
+1/positive feedback without any arguments against the move.
The next step is on the Ozone community:
1. A proposal should be created for the new project which covers all
of the technical questions (HOW to do it...). This should be created and
agreed by the Ozone community
2. A second discussion thread will be started here (all Hadoop dev
lists) to discuss about the proposal itself.
3. When everybody is happy with the proposed way of the move we can
start the VOTE thread (based on the proposal) here
4. Voted proposal will be sent to the ASF board to be
discussed/decided/approved.
Thanks, again, all your feedback,
Marton
On 5/13/20 9:52 AM, Elek, Marton wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
>
> [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Dinesh Chitlangia <di...@apache.org>.
+1
Thank you Marton for writing up the history and supporting comments.
-Dinesh
On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Sunil Govindan <su...@apache.org>.
+1
Thanks
Sunil
On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Uma Maheswara Rao G <ha...@gmail.com>.
+1
Regards,
Uma
On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Akira Ajisaka <aa...@apache.org>.
+1
-Akira
On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Akira Ajisaka <aa...@apache.org>.
+1
-Akira
On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project(Internet mail)
Posted by Simon Su <ba...@gmail.com>.
+1.
Thanks Marton
timmycheng(程力) <ti...@tencent.com> 于2020年5月14日周四 下午3:04写道：
> +1.
>
> Thanks Marton.
>
> -Li
>
> On 2020/5/14, 2:55 PM, "Sammi Chen" <sa...@apache.org> wrote:
>
> +1，
>
> Thanks Marton for bring up the dicussion and providing the history
> info.
>
> Bests,
> Sammi
>
> On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project
> for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it
> to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March
> of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple
> times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS
> or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both
> at
> > the community and code side. The separation has been suggested again
> and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now
> a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to
> old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate
> and
> > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration
> of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree
> latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good
> time
> > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
> >
>
>
Re: [DISCUSS] making Ozone a separate Apache project(Internet mail)
Posted by "timmycheng (程力)" <ti...@tencent.com>.
+1.
Thanks Marton.
-Li
On 2020/5/14, 2:55 PM, "Sammi Chen" <sa...@apache.org> wrote:
+1，
Thanks Marton for bring up the dicussion and providing the history info.
Bests,
Sammi
On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Bharat Viswanadham <bv...@cloudera.com.INVALID>.
+1
Thank you Marton for bringing up the discussion.
Thanks,
Bharat
On Thu, May 14, 2020 at 1:21 AM Shashikant Banerjee
<sb...@cloudera.com.invalid> wrote:
> +1
>
> Thanks
> Shashi
>
> On Thu, May 14, 2020 at 12:25 PM Sammi Chen <sa...@apache.org> wrote:
>
> > +1，
> >
> > Thanks Marton for bring up the dicussion and providing the history info.
> >
> > Bests,
> > Sammi
> >
> > On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Shashikant Banerjee <sb...@cloudera.com.INVALID>.
+1
Thanks
Shashi
On Thu, May 14, 2020 at 12:25 PM Sammi Chen <sa...@apache.org> wrote:
> +1，
>
> Thanks Marton for bring up the dicussion and providing the history info.
>
> Bests,
> Sammi
>
> On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Sammi Chen <sa...@apache.org>.
+1，
Thanks Marton for bring up the dicussion and providing the history info.
Bests,
Sammi
On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Sunil Govindan <su...@apache.org>.
+1
Thanks
Sunil
On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wangda Tan <wh...@gmail.com>.
+1,
Thanks,
Wangda
On Thu, May 14, 2020 at 7:01 AM Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> Thanks
> - Tsuyoshi
>
> On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <
> rakeshr.ozone@gmail.com>
> wrote:
>
> > +1
> >
> > Thanks,
> > Rakesh
> >
> > On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wangda Tan <wh...@gmail.com>.
+1,
Thanks,
Wangda
On Thu, May 14, 2020 at 7:01 AM Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> Thanks
> - Tsuyoshi
>
> On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <
> rakeshr.ozone@gmail.com>
> wrote:
>
> > +1
> >
> > Thanks,
> > Rakesh
> >
> > On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wangda Tan <wh...@gmail.com>.
+1,
Thanks,
Wangda
On Thu, May 14, 2020 at 7:01 AM Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> Thanks
> - Tsuyoshi
>
> On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <
> rakeshr.ozone@gmail.com>
> wrote:
>
> > +1
> >
> > Thanks,
> > Rakesh
> >
> > On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wangda Tan <wh...@gmail.com>.
+1,
Thanks,
Wangda
On Thu, May 14, 2020 at 7:01 AM Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> Thanks
> - Tsuyoshi
>
> On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <
> rakeshr.ozone@gmail.com>
> wrote:
>
> > +1
> >
> > Thanks,
> > Rakesh
> >
> > On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wangda Tan <wh...@gmail.com>.
+1,
Thanks,
Wangda
On Thu, May 14, 2020 at 7:01 AM Tsuyoshi Ozawa <oz...@apache.org> wrote:
> +1
>
> Thanks
> - Tsuyoshi
>
> On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <
> rakeshr.ozone@gmail.com>
> wrote:
>
> > +1
> >
> > Thanks,
> > Rakesh
> >
> > On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
> >
> > >
> > >
> > > I would like to start a discussion to make a separate Apache project
> for
> > > Ozone
> > >
> > >
> > >
> > > ### HISTORY [1]
> > >
> > > * Apache Hadoop Ozone development started on a feature branch of
> > > Hadoop repository (HDFS-7240)
> > >
> > > * In the October of 2017 a discussion has been started to merge it to
> > > the Hadoop main branch
> > >
> > > * After a long discussion it's merged to Hadoop trunk at the March of
> > > 2018
> > >
> > > * During the discussion of the merge, it was suggested multiple times
> > > to create a separated project for the Ozone. But at that time:
> > > 1). Ozone was tightly integrated with Hadoop/HDFS
> > > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > > HDSL at that time) as the block level of HDFS
> > > 3). The community of Ozone was a subset of the HDFS community
> > >
> > > * The first beta release of Ozone was just released. Seems to be a
> > > good time before the first GA to make a decision about the future.
> > >
> > >
> > >
> > > ### WHAT HAS BEEN CHANGED
> > >
> > > During the last years Ozone became more and more independent both at
> > > the community and code side. The separation has been suggested again
> and
> > > again (for example by Owen [2] and Vinod [3])
> > >
> > >
> > >
> > > From COMMUNITY point of view:
> > >
> > >
> > > * Fortunately more and more new contributors are helping Ozone.
> > > Originally the Ozone community was a subset of HDFS project. But now a
> > > bigger and bigger part of the community is related to Ozone only.
> > >
> > > * It seems to be easier to _build_ the community as a separated
> > project.
> > >
> > > * A new, younger project might have different practices
> > > (communication, commiter criteria, development style) compared to old,
> > > mature project
> > >
> > > * It's easier to communicate (and improve) these standards in a
> > > separated projects with clean boundaries
> > >
> > > * Separated project/brand can help to increase the adoption rate and
> > > attract more individual contributor (AFAIK it has been seen in
> Submarine
> > > after a similar move)
> > >
> > > * Contribution process can be communicated more easily, we can make
> > > first time contribution more easy
> > >
> > >
> > >
> > > From CODE point of view Ozone became more and more independent:
> > >
> > >
> > > * Ozone has different release cycle
> > >
> > > * Code is already separated from Hadoop code base
> > > (apache/hadoop-ozone.git)
> > >
> > > * It has separated CI (github actions)
> > >
> > > * Ozone uses different (more strict) coding style (zero toleration of
> > > unit test / checkstyle errors)
> > >
> > > * The code itself became more and more independent from Hadoop on
> > > Maven level. Originally it was compiled together with the in-tree
> latest
> > > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > > Configuration...)
> > >
> > > * It starts to use multiple version of Hadoop (on client side)
> > >
> > > * Volume of resolved issues are already very high on Ozone side
> (Ozone
> > > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > > together in the last 2-3 months)
> > >
> > >
> > > Summary: Before the first Ozone GA release, It seems to be a good time
> > > to discuss the long-term future of Ozone. Managing it as a separated
> TLP
> > > project seems to have more benefits.
> > >
> > >
> > > Please let me know what your opinion is...
> > >
> > > Thanks a lot,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > > [1]: For more details, see:
> > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> > >
> > > [2]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> > >
> > > [3]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
Thanks
- Tsuyoshi
On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <ra...@gmail.com>
wrote:
> +1
>
> Thanks,
> Rakesh
>
> On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
Thanks
- Tsuyoshi
On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <ra...@gmail.com>
wrote:
> +1
>
> Thanks,
> Rakesh
>
> On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
Thanks
- Tsuyoshi
On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <ra...@gmail.com>
wrote:
> +1
>
> Thanks,
> Rakesh
>
> On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
Thanks
- Tsuyoshi
On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <ra...@gmail.com>
wrote:
> +1
>
> Thanks,
> Rakesh
>
> On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
+1
Thanks
- Tsuyoshi
On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <ra...@gmail.com>
wrote:
> +1
>
> Thanks,
> Rakesh
>
> On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
> > * Apache Hadoop Ozone development started on a feature branch of
> > Hadoop repository (HDFS-7240)
> >
> > * In the October of 2017 a discussion has been started to merge it to
> > the Hadoop main branch
> >
> > * After a long discussion it's merged to Hadoop trunk at the March of
> > 2018
> >
> > * During the discussion of the merge, it was suggested multiple times
> > to create a separated project for the Ozone. But at that time:
> > 1). Ozone was tightly integrated with Hadoop/HDFS
> > 2). There was an active plan to use Block layer of Ozone (HDDS or
> > HDSL at that time) as the block level of HDFS
> > 3). The community of Ozone was a subset of the HDFS community
> >
> > * The first beta release of Ozone was just released. Seems to be a
> > good time before the first GA to make a decision about the future.
> >
> >
> >
> > ### WHAT HAS BEEN CHANGED
> >
> > During the last years Ozone became more and more independent both at
> > the community and code side. The separation has been suggested again and
> > again (for example by Owen [2] and Vinod [3])
> >
> >
> >
> > From COMMUNITY point of view:
> >
> >
> > * Fortunately more and more new contributors are helping Ozone.
> > Originally the Ozone community was a subset of HDFS project. But now a
> > bigger and bigger part of the community is related to Ozone only.
> >
> > * It seems to be easier to _build_ the community as a separated
> project.
> >
> > * A new, younger project might have different practices
> > (communication, commiter criteria, development style) compared to old,
> > mature project
> >
> > * It's easier to communicate (and improve) these standards in a
> > separated projects with clean boundaries
> >
> > * Separated project/brand can help to increase the adoption rate and
> > attract more individual contributor (AFAIK it has been seen in Submarine
> > after a similar move)
> >
> > * Contribution process can be communicated more easily, we can make
> > first time contribution more easy
> >
> >
> >
> > From CODE point of view Ozone became more and more independent:
> >
> >
> > * Ozone has different release cycle
> >
> > * Code is already separated from Hadoop code base
> > (apache/hadoop-ozone.git)
> >
> > * It has separated CI (github actions)
> >
> > * Ozone uses different (more strict) coding style (zero toleration of
> > unit test / checkstyle errors)
> >
> > * The code itself became more and more independent from Hadoop on
> > Maven level. Originally it was compiled together with the in-tree latest
> > Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> > Configuration...)
> >
> > * It starts to use multiple version of Hadoop (on client side)
> >
> > * Volume of resolved issues are already very high on Ozone side (Ozone
> > had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> > together in the last 2-3 months)
> >
> >
> > Summary: Before the first Ozone GA release, It seems to be a good time
> > to discuss the long-term future of Ozone. Managing it as a separated TLP
> > project seems to have more benefits.
> >
> >
> > Please let me know what your opinion is...
> >
> > Thanks a lot,
> > Marton
> >
> >
> >
> >
> >
> > [1]: For more details, see:
> > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
> >
> > [2]:
> >
> >
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
> >
> > [3]:
> >
> >
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
> >
> >
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Rakesh Radhakrishnan <ra...@gmail.com>.
+1
Thanks,
Rakesh
On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Sunil Govindan <su...@apache.org>.
+1
Thanks
Sunil
On Wed, May 13, 2020 at 1:23 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wanqiang Ji <ji...@apache.org>.
+1
On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Dinesh Chitlangia <di...@apache.org>.
+1
Thank you Marton for writing up the history and supporting comments.
-Dinesh
On Wed, May 13, 2020 at 3:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by "Elek, Marton" <el...@apache.org>.
Thank you for all of your responses.
It seems that we have a strong agreement. This thread got ~ 25
+1/positive feedback without any arguments against the move.
The next step is on the Ozone community:
1. A proposal should be created for the new project which covers all
of the technical questions (HOW to do it...). This should be created and
agreed by the Ozone community
2. A second discussion thread will be started here (all Hadoop dev
lists) to discuss about the proposal itself.
3. When everybody is happy with the proposed way of the move we can
start the VOTE thread (based on the proposal) here
4. Voted proposal will be sent to the ASF board to be
discussed/decided/approved.
Thanks, again, all your feedback,
Marton
On 5/13/20 9:52 AM, Elek, Marton wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
>
> [3]:
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Wanqiang Ji <ji...@apache.org>.
+1
On Wed, May 13, 2020 at 3:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Akira Ajisaka <aa...@apache.org>.
+1
-Akira
On Wed, May 13, 2020 at 4:53 PM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] making Ozone a separate Apache project
Posted by anu engineer <an...@gmail.com>.
+1
—Anu
> On May 13, 2020, at 12:53 AM, Elek, Marton <el...@apache.org> wrote:
>
>
>
> I would like to start a discussion to make a separate Apache project for Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of 2018
>
> * During the discussion of the merge, it was suggested multiple times to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at the community and code side. The separation has been suggested again and again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone. Originally the Ozone community was a subset of HDFS project. But now a bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices (communication, commiter criteria, development style) compared to old, mature project
>
> * It's easier to communicate (and improve) these standards in a separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and attract more individual contributor (AFAIK it has been seen in Submarine after a similar move)
>
> * Contribution process can be communicated more easily, we can make first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on Maven level. Originally it was compiled together with the in-tree latest Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC, Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time to discuss the long-term future of Ozone. Managing it as a separated TLP project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see: https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]: https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]: https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: ozone-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] making Ozone a separate Apache project
Posted by Uma Maheswara Rao G <ha...@gmail.com>.
+1
Regards,
Uma
On Wed, May 13, 2020 at 12:53 AM Elek, Marton <el...@apache.org> wrote:
>
>
> I would like to start a discussion to make a separate Apache project for
> Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of
> Hadoop repository (HDFS-7240)
>
> * In the October of 2017 a discussion has been started to merge it to
> the Hadoop main branch
>
> * After a long discussion it's merged to Hadoop trunk at the March of
> 2018
>
> * During the discussion of the merge, it was suggested multiple times
> to create a separated project for the Ozone. But at that time:
> 1). Ozone was tightly integrated with Hadoop/HDFS
> 2). There was an active plan to use Block layer of Ozone (HDDS or
> HDSL at that time) as the block level of HDFS
> 3). The community of Ozone was a subset of the HDFS community
>
> * The first beta release of Ozone was just released. Seems to be a
> good time before the first GA to make a decision about the future.
>
>
>
> ### WHAT HAS BEEN CHANGED
>
> During the last years Ozone became more and more independent both at
> the community and code side. The separation has been suggested again and
> again (for example by Owen [2] and Vinod [3])
>
>
>
> From COMMUNITY point of view:
>
>
> * Fortunately more and more new contributors are helping Ozone.
> Originally the Ozone community was a subset of HDFS project. But now a
> bigger and bigger part of the community is related to Ozone only.
>
> * It seems to be easier to _build_ the community as a separated project.
>
> * A new, younger project might have different practices
> (communication, commiter criteria, development style) compared to old,
> mature project
>
> * It's easier to communicate (and improve) these standards in a
> separated projects with clean boundaries
>
> * Separated project/brand can help to increase the adoption rate and
> attract more individual contributor (AFAIK it has been seen in Submarine
> after a similar move)
>
> * Contribution process can be communicated more easily, we can make
> first time contribution more easy
>
>
>
> From CODE point of view Ozone became more and more independent:
>
>
> * Ozone has different release cycle
>
> * Code is already separated from Hadoop code base
> (apache/hadoop-ozone.git)
>
> * It has separated CI (github actions)
>
> * Ozone uses different (more strict) coding style (zero toleration of
> unit test / checkstyle errors)
>
> * The code itself became more and more independent from Hadoop on
> Maven level. Originally it was compiled together with the in-tree latest
> Hadoop snapshot. Now it depends on released Hadoop artifacts (RPC,
> Configuration...)
>
> * It starts to use multiple version of Hadoop (on client side)
>
> * Volume of resolved issues are already very high on Ozone side (Ozone
> had slightly more resolved issues than HDFS/YARN/MAPREDUCE/COMMON all
> together in the last 2-3 months)
>
>
> Summary: Before the first Ozone GA release, It seems to be a good time
> to discuss the long-term future of Ozone. Managing it as a separated TLP
> project seems to have more benefits.
>
>
> Please let me know what your opinion is...
>
> Thanks a lot,
> Marton
>
>
>
>
>
> [1]: For more details, see:
> https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md
>
> [2]:
>
> https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E
>
> [3]:
>
> https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>