[HDDS-378] Remove dependencies between hdds/ozone and hdfs proto files

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.3.0, 0.4.0
• Labels: newbie
• Target Version/s: 0.3.0
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 27/Aug/18 12:25
• Updated: 16/Oct/18 20:38
• Resolved: 16/Oct/18 17:41

Description

It would be great to make the hdds/ozone proto files independent from hdfs proto files. It would help as to start ozone with multiple version of hadoop version.

Also helps to make artifacts from the hdds protos: HDDS-220

Currently we have a few unused "hdfs.proto" import in the proto files and we use the StorageTypeProto from hdfs:

cd hadoop-hdds
grep -r "hdfs" --include="*.proto"
common/src/main/proto/ScmBlockLocationProtocol.proto:import "hdfs.proto";
common/src/main/proto/StorageContainerLocationProtocol.proto:import "hdfs.proto";

 cd ../hadoop-ozone
grep -r "hdfs" --include="*.proto"
common/src/main/proto/OzoneManagerProtocol.proto:import "hdfs.proto";
common/src/main/proto/OzoneManagerProtocol.proto:    required hadoop.hdfs.StorageTypeProto storageType = 5 [default = DISK];
common/src/main/proto/OzoneManagerProtocol.proto:    optional hadoop.hdfs.StorageTypeProto storageType = 6;

I propose to

1.) remove the hdfs import statements from the proto files
2.) Copy the StorageTypeProto and create a Hdds version from it (without PROVIDED)

Issue Links

• blocks: HDDS-220 Create maven artifacts with the hdds/ozone client proto files
• relates to: HDDS-669 Consider removing duplication of StorageType