[HDDS-156] Implement HDDSVolume to manage volume state

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.2.1
• Sprint: HDDS Acadia
• Assignee: Hanisha Koneru
• Reporter: Hanisha Koneru
• Created: 07/Jun/18 00:09
• Updated: 09/Jul/18 21:03
• Resolved: 14/Jun/18 20:30

Description

This Jira proposes the following:

1. Implement HDDSVolume to encompass VolumeInfo along with other HDDS specific fields.
   • VolumeInfo container disk specific information such as capacity, usage, storageType. HddsVolume has hdds specific fields for volume such as VolumeState, VolumeStats (will be added later).
2. Write volume level Version file
   • clusterID, storageID, datanodeUUID, creationTime and layoutVersion.
3. Read Version file while instantiating HDDSVolumes.
   • When the volume Version file already exists (for example, when a DN is restarted), then the version file is read for the stored clusterID, datanodeUuid, lahyoutVersion etc. Some checks will be performed to verify the sanity of the volume.
   • When a fresh Datanode is started, the Version file is not written to the volume uptill the clusterID is received from the SCM.

 

Issue Links

• blocks: HDDS-155 Implement KeyValueContainer and adopt new disk layout for the containers
• is related to: HDDS-97 Create Version File in Datanode