The vote passes with 29 +1 (where 22 are binding) and without -1 or 0.
Thank you very much for all the votes/support.
As a next step, I will send the proposal and the result of this vote to
the ASF board.
Thanks again,
Marton
Hi,
The Hadoop community earlier decided to move out Ozone sub-project to a
separated Apache Top Level Project (TLP). [1]
For detailed history and motivation, please check the previous thread ([1])
Ozone community discussed and agreed on the initial version of the
project proposal, and
+1 (binding)
1. verified signatures
2. verified checksums
3. verified the output of `ozone version` (includes the good git revision)
4. verified that the source package matches the git tag
5. verified source can be used to build Ozone without previous state
(docker run -v ... -it maven ...
that there are some leftover
references to version "0.6.0" in upgrade scripts and tests
(HDDS-4139). Created a pull request to fix it, please consider
including it in the release.
thanks,
Attila
On Mon, Aug 24, 2020 at 3:55 PM Elek, Marton wrote:
+1 (binding)
1. verified sig
+1 (binding)
1. verified signatures
2. verified checksums
3. verified the output of `ozone version` (includes the good git revision)
4. verified that the source package matches the git tag
5. verified source can be used to build Ozone without previous state
(docker run -v ... -it maven
+1 (binding)
* checked signature
* built from source
* deployed binary package to kubernetes
* executed teragen with automatic tests [1]
* checked "hadoop version" and compared with git revision
* checked if the staging repository contains src packages
Thanks the work (and the toughness)
(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
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 +
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
+1
* signatures checked
* sha512 checked
* can be built from the source (without using my local mvn cache:
using apache/ozone-build docker image)
* created docker image with the provided Dockerfile
* Deployed to Kubernetes together with Yarn and Hdfs
* tested with 100G teragen (one
Thank you very much to work on this release Vinay, 1.0.0 is always a
hard work...
1. I downloaded it and I can build it from the source
2. Checked the signature and the sha512 of the src package and they are fine
3. Yetus seems to be included in the source package. I am not sure if
it's
Thanks for all the votes and feedback.
The vote is passed with no -1 and with many +1
The mailing lists will be created soon and the notification settings
will be updated.
Thank you for your patience.
Marton
On 10/27/19 9:25 AM, Elek, Marton wrote:
As discussed earlier in the thread
point
github to that?
On Sun, Oct 27, 2019 at 10:12 PM Dinesh Chitlangia
wrote:
+1
-Dinesh
On Sun, Oct 27, 2019, 4:25 AM Elek, Marton
As discussed earlier in the thread of "Hadoop-Ozone repository mailing
list configurations" [1] I suggested to solve the current
misconfiguration problem w
As discussed earlier in the thread of "Hadoop-Ozone repository mailing
list configurations" [1] I suggested to solve the current
misconfiguration problem with creating separated mailing lists
(dev/issues) for Hadoop Ozone.
It would have some additional benefit: for example it would make
Thanks to report this problem Rohith,
Yes, it seems to be configured with the wrong mailing list.
I think the right fix is to create ozone-dev@ and ozone-issues@ and use
them instead of hdfs-(dev/issues).
Is there any objections against creating new ozone-* mailing lists?
Thanks,
Marton
Sure. Will do it that way.
Thanks the feedback.
Marton
On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote:
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton wrote:
As the overall feedback was positive (in fact many of the answers were
simple +1 votes) I don't think the thread should
As discussed earlier Ozone is moved out from Hadoop trunk.
Please commit / create pull requests to the
--> https://github.com/apache/hadoop-ozone
in the future.
Remaining Ozone code will be deleted from Hadoop trunk with HDDS-2288.
Marton
+1
Thank you Nanda the enormous work to make this release happen.
* GPG Signatures are fine
* SHA512 signatures are fine
* Can be built from the source package (in isolated environment
without cached hadoop/ozone artifacts)
* Started the pseudo cluster with `compose/ozone`
* Executed
To be honest, I have no idea. I don't know about the historical meaning.
But as there is no other feedback, here are my guesses based on pure logic:
* current -> should point to the release with the highest number (3.2.1)
* stable -> to the stable 3.x release with the highest number (3.2.1
> Do you see a Submarine like split-also-into-a-TLP for Ozone? If not
now, sometime further down the line?
Good question, and I don't know what is the best answer right now. It's
definitely an option, But Submarine move hasn't been finished, so it's
not yet possible to learn form the
+1 (binding)
Thanks Rohith the work with the release.
* built from the source (archlinux)
* verified signatures
* verified sha512 checksums
* started a docker-based pseudo cluster
* tested basic HDFS operations with CLI
* Checked if the sources are uploaded to the maven staging repo
oes for filesystem contract
tests.
are you happy with that?
On Tue, Sep 17, 2019 at 10:48 AM Elek, Marton wrote:
TLDR; I propose to move Ozone related code out from Hadoop trunk and
store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
When Ozone was adopted as a new
TLDR; I propose to move Ozone related code out from Hadoop trunk and
store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
When Ozone was adopted as a new Hadoop subproject it was proposed[1] to
be part of the source tree but with separated release cadence, mainly
Thanks for all the positive feedback,
I opened INFRA-18777 to request the proposed change.
Marton
On 7/18/19 10:02 AM, Masatake Iwasaki wrote:
> +1
>
> Thanks,
> Masatake Iwasaki
>
> On 7/17/19 15:07, Elek, Marton wrote:
>> Hi,
>>
>> Github U
Hi,
Github UI (ui!) helps to merge Pull Requests to the proposed branch.
There are three different ways to do it [1]:
1. Keep all the different commits from the PR branch and create one
additional merge commit ("Create a merge commit")
2. Squash all the commits and commit the change as one
+1 (non-binding).
Thanks the continuous effort Ajay. This is the best Ozone release
package what I have ever seen:
I checked the following:
* Signatures are checked: OK
* sha512 checksums are checked: OK
* can be built from the source: OK
* smoketest executed from the bin package (after
+1 (non-binding)
- build from source
- run all the smoketest (from the fresh build based on the src package)
- run all the smoketest from the binary package
- signature files are checked
- sha512 checksums are verified
- ozone version shows the right commit information
Thanks Ajay all the
I don't know which one is the best approach, personally I prefer to
merge locally as in that case the commit can be signed by my local key.
Github PR can be closed with adding a "Closes #412" comment to the end
of the commit message and with this comment the final commit will be
linked under to
maven project version, which minimize
> version number management between maven and docker.
>
> Regards,
> Eric
>
> On 1/31/19, 8:59 AM, "Elek, Marton" wrote:
>
>
> Hi Eric,
>
> Thanks for the answers
>
>
+1 (non-binding)
(my arguments are in the discuss thread. small move, huge benefit)
Thanks,
Marton
On 2/1/19 11:15 PM, Wangda Tan wrote:
> Hi all,
>
> According to positive feedbacks from the thread [1]
>
> This is vote thread to start a new subproject named "hadoop-submarine"
> which follows
+1.
I like the idea.
For me, submarine/ML-job-execution seems to be a natural extension of
the existing Hadoop/Yarn capabilities.
And like the proposed project structure / release lifecycle, too. I
think it's better to be more modularized but keep the development in the
same project. IMHO it
> dockerfile-maven-plugin approach.
>
> Regards,
> Eric
>
> On 1/30/19, 12:56 AM, "Elek, Marton" wrote:
>
> Thanks Eric the suggestions.
>
> Unfortunately (as Anu wrote it) our use-case is slightly different.
>
> It was
YARN-7129 style of build process, and see this is a possible solution to
> solve docker image generation issue? Thanks
>
> Regards,
> Eric
>
> On 1/29/19, 3:44 PM, "Arpit Agarwal"
> wrote:
>
> I’ve request
TLDR;
I proposed to create a separated git repository for ozone docker images
in HDDS-851 (hadoop-docker-ozone.git)
If there is no objections in the next 3 days I will ask an Apache Member
to create the repository.
LONG VERSION:
In HADOOP-14898 multiple docker containers and helper
he pgp pool? That's what Nexus is validating
>> against. It might take time to propagate if you just pushed it.
>>
>> On Mon, Jan 14, 2019 at 9:59 AM Elek, Marton wrote:
>>
>>> Seems to be an INFRA issue for me:
>>>
>>> 1. I downloaded a sam
Seems to be an INFRA issue for me:
1. I downloaded a sample jar file [1] + the signature from the
repository and it was ok, locally I verified it.
2. I tested it with an other Apache project (Ratis) and my key. I got
the same problem even if it worked at last year during the 0.3.0
release. (I
Thanks Sunil to manage this release.
+1 (non-binding)
1. built from the source (with clean local maven repo)
2. verified signatures + checksum
3. deployed 3 node cluster to Google Kubernetes Engine with generated
k8s resources [1]
4. Executed basic HDFS commands
5. Executed basic yarn example
of the git.apache.org. It seems to be a mirror
page only for the old-style+svn repositories))
On 1/7/19 3:18 PM, Steve Loughran wrote:
> OK. so the original git://git.apache.org/hadoop.git is in fact deceased?
>
>
> On 7 Jan 2019, at 14:15, Elek, Marton
> mailto:e...@apache.org>&g
t;
>
>> On 7 Jan 2019, at 06:55, Akira Ajisaka > <mailto:aajis...@apache.org>> wrote:
>>
>> Thanks Ayush for the report and thanks Elek for the fix!
>>
>> -Akira
>>
>> 2019年1月3日(木) 0:54 Elek, Marton > <mailto:e...@apache.org>>:
>
ack is welcome,
Thanks,
Marton
On 10/5/18 5:51 PM, Elek, Marton wrote:
>
> Hi everybody,
>
>
> We start a new community call series about Apache Hadoop Ozone. It's an
> informal discussion about the current items, short-term plans,
> directions and contribution possibilities.
Thanks the report Ayush,
The bogus repository is removed by the INFRA:
https://issues.apache.org/jira/browse/INFRA-17526
And the cwiki page[1] is updated to use the gitbox url instead of
git.apache.org
Marton
[1] https://cwiki.apache.org/confluence/display/HADOOP/Git+And+Hadoop
On 1/2/19
On 12/12/18 12:27 PM, Akira Ajisaka wrote:
> Thank you for your positive feedback! I'll file a jira to INFRA in this
> weekend.
>
>> If I understood well the only bigger task here is to update all the jenkins
>> jobs. (I am happy to help/contribute what I can do)
> Thank you Elek for the
Thanks Akira,
+1 (non-binding)
I think it's better to do it now at a planned date.
If I understood well the only bigger task here is to update all the
jenkins jobs. (I am happy to help/contribute what I can do)
Marton
On 12/8/18 6:25 AM, Akira Ajisaka wrote:
> Hi all,
>
> Apache Hadoop
It gives me great pleasure to announce that the Apache Hadoop community
has voted to release Apache Hadoop Ozone 0.3.0-alpha (Arches).
Apache Hadoop Ozone is an object store for Hadoop built using Hadoop
Distributed Data Store.
This release contains a new S3 compatible interface and additional
Thank you very much the tests and the votes for all of you.
The vote is PASSED with the following details:
3 binding +1, (thanks Arpit, Anu, Jitendra)
6 non-binding +1, (thanks Dinesh, Shashikant, Lokesh, Mukul, Bharat)
together with my closing +1 [*]
no -1/0
Thanks again, will publish the
Thanks Akira to manage this release.
+1 (non-binding)
- verified signatures and checksums
- built from the source
- started docker based pseudo cluster from the binary tar file
- checked web uis and standard hdfs commands
Marton
On 11/19/18 11:30 AM, Lokesh Jain wrote:
> +1 (non-binding)
Hi all,
I've created the second release candidate (RC1) for Apache Hadoop Ozone
0.3.0-alpha including one more fix on top of the previous RC0 (HDDS-854)
This is the second release of Apache Hadoop Ozone. Notable changes since
the first release:
* A new S3 compatible rest server is added. Ozone
Unfortunately a memory issue is found with the default settings. Fixed
in HDDS-834 (thanks Mukul and Shashikant)
I cancel this vote and start a rc1 soon.
Marton
On 11/13/18 1:53 PM, Elek, Marton wrote:
> Hi all,
>
> I've created the first release candidate (RC0) for Apache Hadoop Ozon
Hi all,
I've created the first release candidate (RC0) for Apache Hadoop Ozone
0.3.0-alpha according to the plans shared here previously.
This is the second release of Apache Hadoop Ozone. Notable changes since
the first release:
* A new S3 compatible rest server is added. Ozone can be used
Hi all,
Since the previous 0.2.1-alpha ozone release more than 170 patches have
been committed to the apache trunk under hadoop-ozone/hadoop-hdds
subprojects.
The 0.3.0-alpha release carries an S3 compatible rest server. This
allows S3 applications to work against Ozone with zero-changes. The
part of our larger site?
>
> +Vinod
>
>
>> On Oct 1, 2018, at 5:24 PM, Elek, Marton wrote:
>>
>>
>> It gives me great pleasure to announce that the Apache Hadoop community has
>> voted to release Apache Hadoop Ozone 0.2.1-alpha.
>>
>> Apache Hadoo
Hi everybody,
We start a new community call series about Apache Hadoop Ozone. It's an
informal discussion about the current items, short-term plans,
directions and contribution possibilities.
Please join if you are interested or have questions about Ozone.
For more details, please check:
It gives me great pleasure to announce that the Apache Hadoop community
has voted to release Apache Hadoop Ozone 0.2.1-alpha.
Apache Hadoop Ozone is an object store for Hadoop built using Hadoop
Distributed Data Store.
For more information and to download, please check
Thank you very much the tests and the votes for all of you.
The vote is PASSED with the following details:
3 binding +1, (thanks Anu, Xiaoyu, Arpit)
10 non-binding +1, (thanks Hanisha, Bharat, Shashikant, Sandeep, Lokesh,
Nanda, Mukul, Ajay, Dinesh) together with my closing +1 [*]
no -1/0
refreshed. It seems like to need
some manually steps to refresh the website -if so, can you also update to
the wiki?
Thanks,
Junping
Elek, Marton 于2018年9月20日 周四下午1:40写道：
> Please try
>
> git clone https://gitbox.apache.org/repos/
repository is correct for clone?
I can clone readable repository (https://github.com/apache/hadoop-site)
successfully though but cannot push back changes which is expected.
Thanks,
Junping
Elek, Marton mailto:e...@apache.org>>于2018年9月17日
周一上午6:15写道：
Hi Junping,
Thank you t
Hi all,
After the recent discussion about the first Ozone release I've created
the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha.
This release is alpha quality: it’s not recommended to use in production
but we believe that it’s stable enough to try it out the feature set
Thank you all the feedback about the first ozone release.
I just cut ozone-0.2 branch from trunk.
This will be the base of the first ozone release.
I changed ozone/hdds version on the trunk to 0.3.0-SNAPSHOT.
Marton
On 08/06/2018 07:34 PM, Elek, Marton wrote:
Hi All,
I would like
with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
Thank you very much to bump up this thread
+1 (non-binding)
1. Built from the source package.
2. Checked the signature
3. Started docker based pseudo cluster and smoketested some basic
functionality (hdfs cli, ec cli, viewfs, yarn examples, spark word count
job)
Thank you very much the work Wangda.
Marton
On 08/02/2018 08:43 PM,
Hi All,
I would like to discuss creating an Alpha release for Ozone. The core
functionality of Ozone is complete but there are two missing features;
Security and HA, work on these features are progressing in Branches
HDDS-4 and HDDS-151. Right now, Ozone can handle millions of keys and
has a
.
- We then modify the existing web-site to say that there is a new
site/experience that folks can click on a link and navigate to
- As this new website matures and gets feedback & fixes, we finally pull the
plug at a later point of time when we think we are good to go.
Thoughts?
+Vinod
On Feb 16
+1 (non binding)
I did a full build from source code, created a docker container and did
various basic level tests with robotframework based automation and
docker-compose based pseudo clusters[1].
Including:
* Hdfs federation smoke test
* Basic ViewFS configuration
* Yarn example jobs
*
On 10/21/2017 02:41 AM, larry mccay wrote:
"We might want to start a security section for Hadoop wiki for each of the
services and components.
This helps to track what has been completed."
Do you mean to keep the audit checklist for each service and component
there?
Interesting idea, I
64 matches
Mail list logo
