[HDDS-7797] Recon UI Changes and representation of heatmap in Recon

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: Ozone Recon
• Assignee: smita
• Reporter: Devesh Kumar Singh
• Created: 18/Jan/23 12:57
• Updated: 14/Dec/23 14:41
• Resolved: 06/Apr/23 06:34

Description

This requirement is to add a capability in Recon to tag storage entities at volume level, bucket level, key level, directory/sub-directory and file level for their access heat. In other words, recon should be able to tag entities with Most Frequently Accessed (MFA), Frequently Accessed (FA) and Less Frequently Accessed (LFA) or Cold data. This will help admin users determine the access pattern of various entities which will in turn help in tiering (Hot, Warm, Cold) of ozone data. Access pattern or heat can be determined based on both READ and WRITE operations on entities.

New Changes in UI

1. Change the API signature to take path as input instead of all 3 (volume, bucket, path). This "path"
   will be used as input to Solr query for "resName". Param name is "path" and do basic validations at UI like no junk character, no backward slashes allowed.
   2. Another input on UI for user to provide "Entity Type" which will have only 3 valid values (Volume, Bucket, Key). "entityType" is the param name for API. This willl be used as input to Solr Query as "resType".Values should be passed as lowercase. E.g For Volume, value will be "volume".
   3. Take input from UI for "HeatMap Based On Last <24H or 7Days or 90 Days or Custom Date Selector which
   cannot be more than 90 Days> Access MetaData".

Scope for 7.1.9 -> Show read access heatmap which shows top 100 heated paths across ozone based on read access for those respective paths. Tagging entities for storage tiering will be taken in future versions.

Issue Links

• Blocked: HDDS-7960 Recon: POC for Treemap for Buckets Volumes and Paths