Affects Version/s: None
Fix Version/s: 0.2.1
According to the community vote, Ozone/Hdds release cycle should be independent from the Hadoop release cycle.
To make it possible we need a separated ozone package.
The current state:
We have just one output tar/directory under hadoop-dist (hadoop-3.2.0). It includes all the hdfs/yarn/mapreduce/hdds binaries and libraries. (Jar files are put in separated directory).
The hdds components and hdfs compobebts all could be started from the bin.
Create a sepearated hadoop-dist/ozone-2.1.0 which contains only the hdfs AND hdds components. Both the hdfs namenode and hdds datanode/scm/ksm could be started from the ozone-2.1.0 package.
Hdds packages would be removed from the original hadoop-3.2.0 directory.
This is a relatively small change. On further JIRAs we need to :
- Create a shaded datanode plugin which could be used with any existing hadoop cluster
- Use standalone ObjectStore/Ozone server instead of the Namenode+Datanod plugin.
- Add test cases for both the ozone-only and the mixed clusters (ozone + hdfs)