Ozone is a distributed key-value store that can efficiently manage both small and large files alike. While HDFS provides POSIX-like semantics, Ozone looks and behaves like an Object Store.
This series of articles will help you get started contributing to the Apache Hadoop Ozone project.
What is Ozone?
Ozone is a distributed key-value store designed to scale to billions of objects and run on clusters of thousands of nodes.
Ozone supports RPC and REST APIs as well as a Hadoop Compatible File System called OzoneFS.
Ozone is a work in progress and currently in alpha state. To try it out, you need to build it from the source code.
Try it out
You have two options to spin up an Ozone cluster on your development machine.
- Build a new Ozone cluster from the source code and start a cluster with docker (also useful for development)
- Build new Ozone cluster from the source code and start it with the startup scripts without docker.
Ozone is a part of the Apache Hadoop project. The bug tracking system for Ozone is under the Apache Jira project named HDDS.
If you are familiar with contributing to Apache Hadoop, then you already know everything you need to know to start filing Ozone bugs and submitting patches.
If you have never contributed to Apache Hadoop before, then you may find it useful to read How To Contribute.
What can I contribute?
We welcome contributions of:
- Code. File a bug and submit a patch, or pick up any one of the unassigned Jiras.
- Documentation Improvements. You can submit improvements to either:
- Ozone website. Instructions are here: Modifying the Ozone Website
- Developer docs. These are markdown files checked into the Apache Hadoop Source tree. E.g. https://github.com/apache/hadoop/blob/trunk/hadoop-ozone/docs/content/GettingStarted.md
- This wiki page. Please contact us at firstname.lastname@example.org and we can provide you write access to the wiki.
- Unit Tests (JUnit)
- Acceptance Tests. The Ozone source code includes a set of docker-based acceptance tests. See this guide for running the available acceptance tests - Running Ozone Smoke Tests and Unit Tests.
- or just file bugs. Bug reports pointing out broken functionality, docs, or suggestions for improvements are always welcome!
Who To Contact
If you have any questions, please don't hesitate to contact email@example.com.
To follow the progress of Ozone development you can check the JIRA dashboard
- A detailed discussion of Ozone file system and design docs can be found here.
- A detailed and work items for the security of Hadoop Distributed Storage Layer is tracked in this JIRA
The documentation is part of the source code, but you can check out directly from github: https://github.com/apache/hadoop/tree/trunk/hadoop-ozone/docs/content See the markdown files with Ozone prefix (Or you can generate a new site from the feature branch)